FC3 T2 alsactl store issues unresolved
maxer1
maxer1 at xmission.com
Sat Sep 25 17:53:15 UTC 2004
Michael Schwendt wrote:
>On Fri, 24 Sep 2004 17:37:31 -0600, maxer1 wrote:
>
>
>
>>Latest dev after FC3T2 upgrade.
>>
>>Here is what I have in modprobe.conf. This hasn't changed to my
>>knowledge in over the last several iterations of Fedora:
>>
>>alias snd-card-0 snd-emu10k1
>>install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 &&
>>/usr/sbin/alsactl restore >/dev/null 2>&1 || :
>>remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
>>/sbin/modprobe -r --ignore-remove snd-emu10k1
>>alias snd-card-1 snd-intel8x0
>>install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 &&
>>/usr/sbin/alsactl restore >/dev/null 2>&1 || :
>>remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
>>/sbin/modprobe -r --ignore-remove snd-intel8x0
>>
>>I can get the sound to work after I go to either gnome-volume-control
>>(unmute) or do a re-detect in system-config-soundcard after boot.
>>
>>Any ideas why alsactl store doesn't appear to be working at all?
>>
>>Is this a problem in initscripts?
>>
>>
>
>Can you 'alsactl store' and 'alsactl restore' the mixer settings
>manually? When was /etc/asound.state last written to on your
>machine? What audio applications do you try?
>
>
Last time asound.state was written to was on the 20th. If I attempt
alsactl store, of course
asound.state is immediately written to. Upon reboot doing the restore
does restore the
previous settings. Apparently we're back to the mode of storing and
restoring to keep the settings?
Now in FC3T1 alsa remembered the settings without having to do alsactl
restore etc.
RaXeT
More information about the test
mailing list