The alsasound init script presently fails at the start of the start() subroutine if the alsa-drivers have been insmod'ed. At present, the Gentoo desktop HOWTO instructs users to add snd-emu10k1 (or whatever card you use) and snd-pcm-oss to /etc/modules.autoload, which of course means that the alsasound init script will always fail at that point, which also means that while the drivers will be loaded just fine, mixer settings are not restored, sequencer modules will not be loaded, and card-specific scripts are not run. Perhaps, the eerror() statement should be changed to an non-fatal ewarn()?
You probably have alsasound init script in your 'default' runlevel. If you added it to 'boot' runlevel instead, it should be started before the modules from modules.autoload get loaded. That said, the desktop howto needs to be updated. Could you open a separate bug report for that, assigning it to me? The right way to load the alsa modules is to edit /etc/modules.d/alsa file and then run `update-modules'. Thanks.
The alsasound script does not work correctly with hotplug if started during boot. If alsasound is in default section and if I add "after hotplug" it seems to work correctly with hotplug.
