From: Nick <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: [Alsa-devel] Re: ALSA - pnp OS bios option
Date: Sat, 11 Feb 2006 13:56:07 +0000 [thread overview]
Message-ID: <7c3341450602110556u75c4bfffq@mail.gmail.com> (raw)
In-Reply-To: <200602111054.50947.nick@linicks.net>
> 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...
I updated alsa-lib and alsa-utils to1.0.11rc3/rc2 This fixed my issues.
Now the question - there have been a lot of alsa changes (since my
alsa-tools was built Slack 10) - do we need to keep the alsa tools and
stuff current too?
Nick
next prev parent reply other threads:[~2006-02-11 13:56 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 ` Nick [this message]
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=7c3341450602110556u75c4bfffq@mail.gmail.com \
--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