Messages in this thread | | | Date | Tue, 10 Jan 2006 19:12:30 +0100 | From | Takashi Iwai <> | Subject | Re: [Alsa-devel] Re: ALSA - pnp OS bios option |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
| |