public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Nick <nick@linicks.net>
Cc: Takashi Iwai <tiwai@suse.de>,
	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 14:47:23 -0500	[thread overview]
Message-ID: <1139687243.19342.95.camel@mindpipe> (raw)
In-Reply-To: <7c3341450602110556u75c4bfffq@mail.gmail.com>

On Sat, 2006-02-11 at 13:56 +0000, Nick wrote:
> > 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.
> >
> 
> OK, talking to myself (testing, testing, 1-2-3) - I have resolved this
> issue after spending 2 hours trying to get my Mic to work again in
> Teamspeak (why is there _so_ many frigging mixers
> (alsamixer/amixer/aumix/kmix/arts) that all seem to do different
> things...

Because people keep writing half-assed mixers, rather than fixing the
existing ones, and distros inexplicably include 5 of them.  Half the
mixers out there only speak OSS, and distros ship them anyway.

Lee



-------------------------------------------------------
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 19:47 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
2006-02-11 13:56           ` [Alsa-devel] " Nick
2006-02-11 19:47             ` Lee Revell [this message]
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=1139687243.19342.95.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    --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