Bug 47405 – Alsa restore mixer settings on startup failing

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Tarragon M. Allen 2004-04-09 20:08:30 UTC]

media-libs/alsa-lib : 1.0.4
sys-kernel/gentoo-dev-sources : 2.6.5
# lspci | grep -i audio
00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)

On startup I get a complaint from the /etc/init.d/alsasound script that the command /usr/sbin/alsactl can't find a particular file, and my mixer levels were not restored.

I found that putting a 'sleep 2' into the /etc/init.d/alsasound script right at the end of the load driver routine (line 108 in my version of the script) resolved the problem. I'd say that all the modules hadn't had a change to fully initialise before the "Restore Mixer Levels" part is run, causing the error.

[Comment 1 Jeremy Huddleston (RETIRED) 2004-04-10 08:21:46 UTC]

*** This bug has been marked as a duplicate of 47286 ***

[Comment 2 Tarragon M. Allen 2004-04-10 09:35:46 UTC]

Um, not to be disrecpectful, but I did look at bug 47286 and also bug 44940 and neither of them seemed to match my problem. 

The problem has nothing to do with certain custom mixer settings being set up, as in bug 47286.

The problem isn't that alsa fails to load as in bug 44940 (it loads just fine, every time), it's that the mixer levels are restored too quickly - the modules haven't had time to fully initialise, and thus the call to set the mixer levels fail.

I've even outlined a fix, which was to put a small delay between loading the modules and restoring the mixer settings.

How is this a duplicate of either of those bugs?

[Comment 3 Jeremy Huddleston (RETIRED) 2004-04-10 10:07:35 UTC]

sorry... marked wrong bug number

*** This bug has been marked as a duplicate of 39345 ***