[alsa-devel] Since kernel-2.6.32, alsactl fails to restore defaults
I originally reported this issue downstream to: http://bugs.gentoo.org/show_bug.cgi?id=299362
Later to kernel: http://bugzilla.kernel.org/show_bug.cgi?id=15107
And they told me that this is an alsactl issue, since it's not exiting with 0 when it notices that the device doesn't need special quirks: # alsactl -f /var/lib/alsa/asound.state restore Unknown hardware: "VIA8237" "Realtek ALC658D" "AC97a:414c4781" "0x147b" "0x1415" Hardware is initialized using a guess method # echo $? 157
What could I do? Thanks for helping me, if you need more information, simply ask me for it :-)
On Sun, 14 Feb 2010, Pacho Ramos wrote:
I originally reported this issue downstream to: http://bugs.gentoo.org/show_bug.cgi?id=299362
Later to kernel: http://bugzilla.kernel.org/show_bug.cgi?id=15107
And they told me that this is an alsactl issue, since it's not exiting with 0 when it notices that the device doesn't need special quirks: # alsactl -f /var/lib/alsa/asound.state restore Unknown hardware: "VIA8237" "Realtek ALC658D" "AC97a:414c4781" "0x147b" "0x1415" Hardware is initialized using a guess method # echo $? 157
I agree, this value is bogus. I just fixed the code to return exit code 99 as described in init/00main:
http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=69c6bead434e7a4...
What could I do? Thanks for helping me, if you need more information, simply ask me for it :-)
There are two ways to fix this issue for your distro:
1) modify the script which calls alsactl and add a check for code 99 (it may ignore this exit code) - assuming that patch above is applied 2) change init/00main - EXIT="99" line to EXIT="0"
But from your gentoo bug, I guess that your system don't save the last soundcard state to /var/lib/alsa/asound.state correctly - it's looks like a bug in the init scripts for your distro.
Or it might be totaly different issue - could you send me your /var/lib/alsa/asound.state file and file test.state generated using 'alsactl -f test.state store' command?
Jaroslav
----- Jaroslav Kysela perex@perex.cz Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.
El dom, 14-02-2010 a las 19:20 +0100, Jaroslav Kysela escribió:
I agree, this value is bogus. I just fixed the code to return exit code 99 as described in init/00main:
http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=69c6bead434e7a4...
What could I do? Thanks for helping me, if you need more information, simply ask me for it :-)
There are two ways to fix this issue for your distro:
- modify the script which calls alsactl and add a check for code 99 (it may ignore this exit code) - assuming that patch above is applied
- change init/00main - EXIT="99" line to EXIT="0"
But from your gentoo bug, I guess that your system don't save the last soundcard state to /var/lib/alsa/asound.state correctly - it's looks like a bug in the init scripts for your distro.
Or it might be totaly different issue - could you send me your /var/lib/alsa/asound.state file and file test.state generated using 'alsactl -f test.state store' command?
Jaroslav
Yes, of course :-)
Thanks
On Sun, 14 Feb 2010, Pacho Ramos wrote:
El dom, 14-02-2010 a las 19:20 +0100, Jaroslav Kysela escribió:
I agree, this value is bogus. I just fixed the code to return exit code 99 as described in init/00main:
http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=69c6bead434e7a4...
What could I do? Thanks for helping me, if you need more information, simply ask me for it :-)
There are two ways to fix this issue for your distro:
- modify the script which calls alsactl and add a check for code 99 (it may ignore this exit code) - assuming that patch above is applied
- change init/00main - EXIT="99" line to EXIT="0"
But from your gentoo bug, I guess that your system don't save the last soundcard state to /var/lib/alsa/asound.state correctly - it's looks like a bug in the init scripts for your distro.
Or it might be totaly different issue - could you send me your /var/lib/alsa/asound.state file and file test.state generated using 'alsactl -f test.state store' command?
JaroslavYes, of course :-)
The files look good. The question is why the initialization is called when a default state already exists (it shouldn't).
Does 'alsactl -f test.state restore' show some messages? Use test.state file you sent me.
Jaroslav
----- Jaroslav Kysela perex@perex.cz Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.
El dom, 14-02-2010 a las 20:10 +0100, Jaroslav Kysela escribió:
The files look good. The question is why the initialization is called when a default state already exists (it shouldn't).
Does 'alsactl -f test.state restore' show some messages? Use test.state file you sent me.
Jaroslav
Jaroslav Kysela perex@perex.cz Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.
Yes, it shows: # alsactl -f test.state restore Unknown hardware: "VIA8237" "Realtek ALC658D" "AC97a:414c4781" "0x147b" "0x1415" Hardware is initialized using a guess method
El dom, 14-02-2010 a las 20:14 +0100, Pacho Ramos escribió:
El dom, 14-02-2010 a las 20:10 +0100, Jaroslav Kysela escribió:
The files look good. The question is why the initialization is called when a default state already exists (it shouldn't).
Does 'alsactl -f test.state restore' show some messages? Use test.state file you sent me.
Jaroslav
Jaroslav Kysela perex@perex.cz Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.
Yes, it shows: # alsactl -f test.state restore Unknown hardware: "VIA8237" "Realtek ALC658D" "AC97a:414c4781" "0x147b" "0x1415" Hardware is initialized using a guess method
Any news on this? Do you need any more information? Thanks a lot :-)
participants (2)
-
Jaroslav Kysela -
Pacho Ramos