stroller at stellar
May 7, 2012, 6:53 PM
Post #5 of 5
On 8 May 2012, at 01:35, Walter Dnes wrote:
Re: asound.state bug? Can anyone else reproduce this, please?
[In reply to]
> On Mon, May 07, 2012 at 09:40:41PM +0100, Stroller wrote
>> I'm also seeing that maybe alsa's default state is muted, so that
>> the muted state would be correct even if the sound state is not being
> According to the Alsa-Project HDA Intel page
> and probably applicable for all cards. The quote is...
>> Now adjust your soundcard's volume levels. All mixer channels are
>> muted by default. You must use a native mixer program to unmute
>> appropriate channels, for example alsamixer from the alsa-utils
Right, but you snipped the important part of my quoted text:
That's fine - restore the previous backup of sound from when audio was
playing (`cp ~/asound.state.bu /var/lib/alsa/asound.state`) and reboot
the system. Now the unmuted state is restored and you can listen to
your music without starting /etc/init.d/alsasound.
Alternatively, you can ensure that the alsa startup script is stopped and disabled (`/etc/init.d/alsasound stop && rc-update del alsasound default`), manually ensure the sound is unmuted (play music), run `/etc/init.d/alsasound save` and reboot the system - the *unmuted* state is restored, even though /etc/init.d/alsasound has never been started.
So the default muting is overridden, even though this has not been requested.
This appears to contradict the option in /etc/conf.d/alsasound - RESTORE_ON_START.
We can set RESTORE_ON_START="no" and yet the setting is overridden - the sound (unmuting) *is* restored on start!
This is obviously easiest to see and demonstrate using muting, but volume levels and so on are restored, too.
I kinda feel silly making a distinction about this, because "of course" a muted soundcard is useless, and of course I want sound to be restored. But I've been trying to figure my way through how ALSA works, and it seems to be via the /etc/init.d/alsasound script, and yet I find that script is just being ignored and that the last state is restored, irrespective of that script's directives. And I guess that bugs me.
I mean, the statement "of course a muted soundcard is useless" begs the question of why ALSA ships like that in the first place (but the ALSA mailing list remains silent in response to my previous question, so let's not go there). But if it makes sense for ALSA to ship with channels muted by default, surely it makes sense for the distro not to override that without the user specifying otherwise.
I hope this makes sense. I'm not used to doing desktoppy stuff on Linux, and I do kinda feel like I'm walking in bizarro-land with this one.