sound driver persistent state

sound driver persistent state

[David Feuer]

People keep saying it's OK to start muted on boot, but I must say that I 
don't think this is really acceptable....  I may very well want to set my 
mixer and just leave it that way forever.... would there be any way to give 
the sound driver a scribble pad on disk to let it sa
--
This message has been brought to you by the letter alpha and the number pi.
David Feuer
David_Feuer@brown.edu

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

sound driver persistent state

[Steve VanDevender]

David Feuer writes:
 > People keep saying it's OK to start muted on boot, but I must say that I 
 > don't think this is really acceptable....  I may very well want to set my 
 > mixer and just leave it that way forever.... would there be any way to give 
 > the sound driver a scribble pad on disk to let it sa

You can't guarantee that the mixer will retain its settings across a
hardware reset, APM suspend/resume cycle, or power cycle.

The typical ALSA installation runs an "alsactl restore" after loading
the driver modules to set the initial mixer levels, and an "alsactl
store" on shutdown to save the mixer levels before unloading the
modules.  This seems to work fine on my laptop, and is in user space
where it belongs.  In fact, on my laptop the intel8x0 driver can't cope
with a suspend/resume cycle while loaded or it hangs after the resume,
so my APM scripts unload the ALSA drivers every time I suspend and
reload them every time I resume.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/