From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: alsamixer Doesn't save volume settings
Date: Fri, 07 May 2004 06:36:59 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20040507062943.01f20198@celine> (raw)
In-Reply-To: <20040507092707.63689.qmail@web61006.mail.yahoo.com>
At 10:27 AM 5/7/2004 +0100, sumit kalra wrote:
[...]
>The script /etc/init.d/alsasound is present but
>/etc/rc6.d/ and /etc/rc3.d/ directories don't have
>symlinks to it. I created these links by hand, but it
>didn't help.
>[...]
>Interestingly, after rebooting if I run "alsactl
>restore" before runnign "alsamixer", my previous
>settings are restored. This means that the file
>/etc/asound.state is correctly storing the settings
>across reboots but alsamixer is somehow not re-reading
>it after rebooting.
alsamixer is not supposed to re-read it. The alsasound init script runs
"alsactl restore" to handle this ... and includes what looks like decent
error handling, so it should log an error if it itself runs but cannot for
some reason run alsactl. So make sure it is running properly on init.
>How do we get around this?
Is 3 *really* the default runlevel on RH systems? (Debian uses 2.)
Did you install alsactl as /usr/sbin/alsactl (that is where the alsasound
script expects to find it)?
Is the pseudo-directory /proc/asound present on your system (dieing
silently if it is not is the one error-reporting weakness I can see in
alsasound)?
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-05-07 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 4:34 alsamixer Doesn't save volume settings sumit kalra
2004-05-07 6:36 ` Ray Olszewski
2004-05-07 9:27 ` sumit kalra
2004-05-07 13:36 ` Ray Olszewski [this message]
2004-05-10 4:44 ` sumit kalra
2004-05-07 22:09 ` Theo. Sean Schulze
2004-05-13 9:11 ` Dominique Sidiropoulos
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=5.1.0.14.1.20040507062943.01f20198@celine \
--to=ray@comarre.com \
--cc=linux-newbie@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