On Wed, 21 Mar 2012 02:53:23 -0500
Jonathan Nieder <jrnie...@gmail.com> wrote:
> A. Costa wrote:
>
> > Sorry, but I'm confused. How can this bug exist in v3.2.10-1, when
> > there's good sound on bootup, without any 'amixer' tweaking?
>
> The "Auto-Mute Mode" setting persists across reboots...
Aha, I'd (mistakenly) believed the opposite. Does an "Auto-Mute Mode"
setting also persist between kernel upgrades?
> ...See /etc/init.d/alsa-utils for details.
OK, so where does that init script store its persistent 'mute' mode
state? That's what should be compared between kernels and bootups I'd
suppose. Here maybe:
% grep -n -A 2 restore_levels\( /etc/init.d/alsa-utils
53:restore_levels()
54-{
55- [ -f /var/lib/alsa/asound.state ] || return 1
Line #55 names a likely file. Looking there:
% grep -n -A 8 -B 2 -i mute /var/lib/alsa/asound.state
95- control.9 {
96- iface MIXER
97: name 'Auto-Mute Mode'
98- value Disabled
99- comment {
100- access 'read write'
101- type ENUMERATED
102- count 1
103- item.0 Disabled
104- item.1 Enabled
105- }
So, before rebooting, (and after), what should line #98 be? Assuming,
of course, that 'asound.state' is relevant.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120326021614.5e2219b7a463d4be6cdeb...@gis.net
