On Thu, 15 Jan 2004 16:44:36 -0500 (EST)That's what I have. With 2.6.0 it's fine, but with 2.6.1, the mixer settings are lost. I can do "/etc/init.d/alsasound restart" and the settings stay put though.
Joe Budafuco <[EMAIL PROTECTED]> wrote:
Just finished installing Kernel 2.6.1 and the Alsa module.
Sound works great but everytime I reboot (and the
modules are reloaded) the volumes are all set to zero
and muted. I have to run alsamixer and turn them back
on. Is there a config file for alsamixer that can be
read when the module is loaded. Looking at the man
page for alsamixer I don't see and command line
options that can set the volumes.
alsactl writes/reads the current settings to /etc/asound.state
Arrange for alsactl store to run before shutdown and
alsactl restore
on start up.
The ALSA init script (mine is in /etc/init.d/alsasound) should do this
already, though.
However, at boot time, alsasound says "ALSA driver is already running". It would appear that /proc/asound exists before alsasound starts. Something somewhere is loading the ALSA drivers early. I'm not sure what, but I see a lot of modprobe failures as well for other sound cards I don't have.
Running "/etc/init.d/alsasond restart" after the machine has come up though unloads the ALSA modules and then the mixer settings are correctly loaded.
jch
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
