From: Nick Warne <nick@linicks.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>, Pavel Machek <pavel@suse.cz>,
tiwai@suse.de, ghrt@dial.kappa.ro, perex@suse.cz,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: No sound from SB live!
Date: Sun, 19 Feb 2006 20:20:36 +0000 [thread overview]
Message-ID: <200602192020.36343.nick@linicks.net> (raw)
In-Reply-To: <1140377394.2733.341.camel@mindpipe>
On Sunday 19 February 2006 19:29, Lee Revell wrote:
> > And now the confusing bit. If I run alsamixer but DO NOT DO ANYTHING,
> > exit, then issue 'alsactl store', then 'alsactl restore' works again
> > OK - until next reboot...
>
> Sounds like you have 2 different alsactls installed. The ALSA default
> one saves the mixer state in /etc/asound.state but lots of distros hack
> it up to save the state somewhere under /var.
>
> Use "alsactl -f" to force a restore of mixer state even if the mixer
> controls have changed (distros should do this by default but don't).
Lee,
Everybody here keeps saying that to me - I _don't_ have two alsactl's, I
_don't_ have 2 asound.states (or more/any other alsactl files).
My base is Slackware 10 - a pretty clean distro.
Tonight my MIC is not working again from a reboot, and I can't get it going
like I did before (??)...
Every reboot 'alsactl restore' breaks on one control or another now.
You mean -F too? I don't understand why I should have to use --force.
It's a mystery?
Nick
--
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
next prev parent reply other threads:[~2006-02-19 20:21 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 23:14 No sound from SB live! Pavel Machek
2006-02-18 23:27 ` ghrt
2006-02-18 23:48 ` Pavel Machek
2006-02-19 0:33 ` Richard Mittendorfer
2006-02-19 21:42 ` Pavel Machek
2006-02-19 22:07 ` Richard Mittendorfer
2006-02-19 0:58 ` Lee Revell
2006-02-19 21:44 ` Pavel Machek
2006-02-20 0:33 ` Lee Revell
2006-02-20 0:39 ` Pavel Machek
2006-02-20 1:33 ` Alistair John Strachan
2006-02-20 23:55 ` Pavel Machek
2006-02-19 11:04 ` Jesper Juhl
2006-02-19 11:18 ` Nick Warne
2006-02-19 19:29 ` Lee Revell
2006-02-19 20:20 ` Nick Warne [this message]
2006-02-19 20:31 ` Lee Revell
2006-02-20 19:18 ` Nick Warne
2006-02-20 19:31 ` D. Hazelton
2006-02-19 20:33 ` Lee Revell
2006-02-19 20:51 ` Nishanth Aravamudan
2006-02-19 21:30 ` Lee Revell
2006-02-19 21:47 ` Pavel Machek
2006-02-19 21:50 ` Lee Revell
2006-02-19 23:23 ` Alistair John Strachan
2006-02-19 23:32 ` Lee Revell
2006-02-19 23:46 ` Pavel Machek
2006-02-19 23:53 ` Lee Revell
2006-02-20 0:04 ` Nishanth Aravamudan
2006-02-20 0:11 ` Lee Revell
2006-02-20 0:57 ` Nishanth Aravamudan
2006-02-20 0:26 ` Pavel Machek
2006-02-20 0:30 ` Lee Revell
2006-02-20 0:42 ` Pavel Machek
2006-02-20 0:52 ` Lee Revell
2006-02-19 23:56 ` Alistair John Strachan
2006-02-20 0:05 ` Lee Revell
2006-02-20 0:12 ` David Lang
2006-02-20 0:16 ` Alistair John Strachan
2006-02-20 0:17 ` Lee Revell
2006-02-19 21:49 ` Pavel Machek
2006-02-19 21:54 ` Lee Revell
2006-02-19 22:25 ` Pavel Machek
2006-02-19 22:28 ` Lee Revell
2006-02-19 23:04 ` Lee Revell
2006-02-20 11:15 ` Takashi Iwai
2006-02-20 11:41 ` Pavel Machek
2006-02-20 19:50 ` Vojtech Pavlik
2006-02-20 19:52 ` Pavel Machek
2006-02-19 19:19 ` Pavel Machek
2006-02-22 14:05 ` Takashi Iwai
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=200602192020.36343.nick@linicks.net \
--to=nick@linicks.net \
--cc=ghrt@dial.kappa.ro \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.de \
/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