From: Steve VanDevender <stevev@efn.org>
To: David Feuer <David_Feuer@brown.edu>
Cc: linux-kernel@vger.kernel.org
Subject: sound driver persistent state
Date: Mon, 6 Nov 2000 23:20:23 -0800 [thread overview]
Message-ID: <14855.44343.68279.953178@localhost.efn.org> (raw)
In-Reply-To: <4.3.2.7.2.20001106230925.00ac6370@postoffice.brown.edu>
In-Reply-To: <4.3.2.7.2.20001106230925.00ac6370@postoffice.brown.edu>
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/
prev parent reply other threads:[~2000-11-07 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 4:11 sound driver persistent state David Feuer
2000-11-07 7:20 ` Steve VanDevender [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14855.44343.68279.953178@localhost.efn.org \
--to=stevev@efn.org \
--cc=David_Feuer@brown.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox