From: Nick Warne <nick@linicks.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Takashi Iwai <tiwai@suse.de>,
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: Sun, 12 Feb 2006 07:56:38 +0000 [thread overview]
Message-ID: <200602120756.38975.nick@linicks.net> (raw)
In-Reply-To: <1139687047.19342.91.camel@mindpipe>
On Saturday 11 February 2006 19:44, Lee Revell wrote:
> > 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?
>
> Probably you have two different alsactl's installed, one that's
> hardcoded to save the state in /etc/asound.state, and a distro version
> that wants to save it in /var/lib/whatever. It sounds like one is being
> run at boot and a different one at shutdown.
First thing I thought of - Slackware is a 'clean, straight' distro though, and
the only asound.state file I had was in /etc/ and only one alsactl in
default /usr/sbin
On Saturday 11 February 2006 22:07, Lee Revell wrote:
> > do we need to keep the alsa tools and
> > stuff current too?
>
> Yes - kernel upgrades should depend on alsa-lib upgrades (many distros
> seem to get this wrong). This should be fixed in the future, but it's
> been this way for some time.
Well, it appears to have fixed the issues I had. Several reboots since and no
problems now.
Looking back, originally I had a 2.4.x kernel - I have since upgraded to 2.6.x
series, plus built a lot of new tools and such from source - all except alsa
stuff, of course - so it does make sense and I kick myself for not thinking
about this in the beginning. One to remember.
Thanks,
Nick
--
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
prev parent reply other threads:[~2006-02-12 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:22 ALSA - pnp OS bios option Nick Warne
2006-01-10 9:01 ` 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
2006-02-11 19:47 ` Lee Revell
2006-02-11 22:07 ` Lee Revell
2006-02-11 19:44 ` Lee Revell
2006-02-12 7:56 ` Nick Warne [this message]
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=200602120756.38975.nick@linicks.net \
--to=nick@linicks.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--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