Thanks for the unc2dsl how-to Felson - it appears to have worked fine on alsa.unc
All we need now is for WDef to make one of his excellent scripts to automate this...
Quote (roberts @ Mar. 07 2007,16:16)
You can, as many have, add commands to /opt/bootlocal.sh to achieve similar results.
I did some more checking on the alsa autoconfig on-boot:
For a machine with an integrated Intel 82801DB (ICH4) AC'97 Audio Controller with alsa.unc and rc2 - I get the following error on the boot screen:
../../alsa-kernel/pci/ac97/ac97_codec.c:1858: MC'97 1 converters and GPIO not ready (0xff00)
and the following errors in /var/log/messages:
Module snd loaded, with warnings Module snd-seq-device loaded, with warnings Module snd-rawmidi loaded, with warnings Module snd-mpu401-uart loaded, with warnings Module snd-page-alloc loaded, with warnings Module snd-timer loaded, with warnings Module snd-pcm loaded, with warnings Module gameport loaded, with warnings Module snd-ac97-codec loaded, with warnings Module snd-intel8x0 loaded, with warnings
For a machine with a Soundblaster 128 pci card with alsa.unc and rc1 - I get several of the "Module xxx loaded, with warnings" errors on the boot screen.
For the machine with the Intel sound (and 1GB RAM), if I use rc2 with a legacy boot, the alsa boot code and alsa.dsl (converted from alsa.unc) and gnu-utils.dsl loaded at boot, the boot messages indicate that alsa-autoconfig will run but it doesn't (per your earlier post, maybe you check for a legacy boot?). Using the command /etc/init.d/alsa-autoconfig after boot (or in bootlocal.sh) loads the alsa modules with the same error messages.
In all the cases above, the sound works so I guess the error messages are not that important.
Which makes most sense in the legacy boot case, to use the alsa boot code or the nosound boot code - or does it matter?Loading modules with warnings is not a fatal error.
I have decided to support both unc and dsl for alsa sound auto setup upon boot.
I have it working with:
boot: dsl legacy alsa
with alsa.dsl and gnu-utils.dsl in the mydsl search path.
I am going to rename the existing alsa.dsl (for dsl v2.x) as it will likely be less used.
This will be available in the next release.As v3.3. has the fixes for daylight savings time, I'm curious when it is actually going to release.
If it is going to be a while, perhaps a corrective extension could be created for existing DSL users?
Actually, an extension that fixes the problem might not be a bad idea anyway, so that people don't have to immediately throw away their old installations.I wanted to release but was denied. I don't control the release dates. I am glad to see that DST worked for me. It is always good to keep current as many bugs are fixed in the newer releases.Next Page...
original here.