From: Takashi Iwai <tiwai@suse.de>
To: Nick Warne <nick@linicks.net>
Cc: Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: ALSA - pnp OS bios option
Date: Tue, 10 Jan 2006 19:12:30 +0100 [thread overview]
Message-ID: <s5hek3geyup.wl%tiwai@suse.de> (raw)
In-Reply-To: <200601101759.20707.nick@linicks.net>
At Tue, 10 Jan 2006 17:59:20 +0000,
Nick Warne wrote:
>
> On Tuesday 10 January 2006 11:27, Takashi Iwai wrote:
>
> > > > Set_Control:894 Name mismatch ... Control #47
> > > > 896: Index mismatch (0/0) for Control #47
> > > > 1008: Bad control.47.value
> > >
> > > This usually happens when you use a different driver version that has
> > > different mixer controls so that the saved state in /etc/asound.state
> > > doesn't match.
> >
> > Use -F option for alsactl in your init script.
>
> I see - specify the asound.state file to use.
>
> So bios pnp OS ON/OFF both use different alsa drivers (or parts _of_ the
> driver) then - which in turn require different asound.state files?
No, I meant -F (a capical F), which means to force to set up the
controls even the number id mismatches. This avoid the errors like
above. (The default behavior of alsactl is a bit too strict.)
But, anyway, it's better to do the following:
- Boot with PnP ON, run "alsactl -f state-with-pnp store"
- Boot with PnP OFF, run "alsactl -f state-wo-pnp store"
then compare these two files.
Takashi
next prev parent reply other threads:[~2006-01-10 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:22 Nick Warne
2006-01-10 9:01 ` Clemens Ladisch
2006-01-10 11:27 ` [Alsa-devel] " Takashi Iwai
2006-01-10 17:59 ` Nick Warne
2006-01-10 18:12 ` Takashi Iwai [this message]
2006-02-11 10:54 ` Nick Warne
2006-02-11 13:56 ` Nick
2006-02-11 19:47 ` Lee Revell
2006-02-11 22:07 ` Lee Revell
2006-02-11 19:44 ` Lee Revell
2006-02-12 7:56 ` Nick Warne
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=s5hek3geyup.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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
Powered by JetHome