Joined: Sep. 2005
||Posted: Mar. 08 2007,10:10
|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?