public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Clemens Ladisch <clemens@ladisch.de>,
	linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net
Subject: Re: Re: ALSA - pnp OS bios option
Date: Sat, 11 Feb 2006 10:54:50 +0000	[thread overview]
Message-ID: <200602111054.50947.nick@linicks.net> (raw)
In-Reply-To: <s5hek3geyup.wl%tiwai@suse.de>

On Tuesday 10 January 2006 18:12, Takashi Iwai wrote:

> > 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.

OK, sorry for a delay in reply - I haven't rebooted since last mail.

I have something _really_ peculiar ongoing on here (ignoring PnP - this isn't 
my issue now, I feel).

Info (lspci):
00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
00:0f.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 
07)


This morning I built and installed 2.6.15.4.  On reboot, I got control errors 
again ('alsactl restore' is run from rc.local):


Sorting SB Live! sound (alsactl restore)...
alsactl: set_control:894: warning: name mismatch (Sigmatel Surround Playback 
Volume/Sigmatel Surround Playback Switch) for control #47
alsactl: set_control:896: warning: index mismatch (0/0) for control #47
alsactl: set_control:1008: bad control.47.value index


Ummm.  At the command line, same errors also.  So I deleted /etc/asound.state 
and reconfigured alsamixer from scratch.  Then following 'alsactl store', 
'alsactl restore' completes without issue (i.e. works clean).

If I then reboot, the same damn control #47 errors happen again.  It's as if 
something changes my asound.state file at boot time time?

Ideas?  This is driving me potty.

Nick
-- 
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb


-------------------------------------------------------
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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-11 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200601092022.56244.nick@linicks.net>
2006-01-10  9:01 ` ALSA - pnp OS bios option 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
2006-02-11 10:54         ` Nick Warne [this message]
2006-02-11 13:56           ` [Alsa-devel] " Nick
2006-02-11 19:47             ` Lee Revell
2006-02-11 22:07             ` [Alsa-devel] " 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=200602111054.50947.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --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