If your soundcard driver (for example snd_cs46xx) was loaded early in the boot cycle by hotplug/coldplug, the alsasound script will fail to load the oss compatibility modules. It detects that alsa drivers are already loaded and punts. alsa-utils-1.0.6 with kernel ALSA drivers from gentoo-dev-sources-2.5.9-r13 Reproducible: Always Steps to Reproduce: 1. Use kernel ALSA drivers (built as modules) and use a soundcard that has hotplug/coldplug information (in my case cs46xx). 2. Make sure "coldplug" is in your "boot" runlevel, and "alsasound" is in your "default" runlevel. 3. Boot. Actual Results: The alsa sound drivers will be loaded, but the OSS compatibility modules will not - the boot process will print "ALSA Detected" and fail to load the auxiliary modules. Expected Results: The auxiliary modules should be loaded, even if the alsa modules were already loaded. A workaround is to put the module for your soundcard into /etc/hotplug/blacklist - this will keep it from getting hot/coldplugged, and the alsasound script will load all of the required modules.
can you please try the latest alsasound init script... the behavior you describe does not sound like something the current script would do.
Yes. The alsa-utils-1.0.7 alsasound script seems to do the right thing.
emerge --sync
Problem is that alsa-utils-1.0.7 is still ~x86.
Whoops - my mistake. I didn't see that the alsasound script isn't version-dependent. Seems like there should be some way for portage to warn that you need to remerge a package because auxiliary files have changed/improved...
