the alsasound script in /etc/init.d/ states that it should start before modules, which is necessary for a user to add alsa-oss-* driver for autoloading OSS emulation to modules.autoload. However, ALSA also depends on checkfs, which requires modules (LVM/RAID issues). ALSA starts after modules even without these 2 items in modules.autoload, but there is now issue then as the OSS modules haven't yet loaded the snd module. This blocks the autoload of OSS emulation for ALSA Reproducible: Always Steps to Reproduce: no steps. just watch where ALSA starts
I was having the same problems and I found a work-around for that problem. This will not fix your dependecy problem but you will be able to load the oss modules: 1.) Figure out what alsa driver are you loading for your card: snd-xxxx 2.) replace the four x above with the name of the matching driver ;) 3.) create a directory /etc/alsa.d if not exists already 4.) put in that directory a file called xxxx 5.) if you were clever you replace the four x above with the name from point 2.) 6.) write a nice shell-script in that file (chmod it correctly) what to expect: this file is run by the alsasound init script automatically after alsa-driver is loaded - believe it. It would be great to document this on a public place either. Sample: my sound-driver is: snd-trident my xxxx is: trident so my shellscript is: /etc/alsa.d/trident it's content: #!/bin/sh /sbin/modprobe snd-pcm-oss Hope this helps until this bug is finally fixed
the oss drivers are autoloaded by the init script. Please check the latest init script that I just added to portage (not on the rsync servers yet, so you cen get it from bug #41600).
