Re: Re: ALSA - pnp OS bios option

[Takashi Iwai <tiwai@suse.de>]

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


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click