From: Takashi Iwai <tiwai@suse.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Lee Revell <rlrevell@joe-job.com>, Andrew Morton <akpm@osdl.org>,
Mark Canter <marcus@vfxcomputing.com>,
nish.aravamudan@gmail.com, linux-kernel@vger.kernel.org,
alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: intel 8x0 went silent in 2.6.11
Date: Mon, 07 Mar 2005 21:26:30 +0100 [thread overview]
Message-ID: <s5hbr9vurrd.wl@alsa2.suse.de> (raw)
In-Reply-To: <422CB5E3.3070208@drzeus.cx>
At Mon, 07 Mar 2005 21:13:23 +0100,
Pierre Ossman wrote:
>
> Lee Revell wrote:
>
> >So is there a bug or not? Mark seems to be the only one affected.
> >
> >It's important to follow up, because these so-called "ALSA regressions"
> >are generating bad press.
> >
> >Lee
> >
> >
> >
> I can generate the error using the following procedure:
>
> 1. Boot in 2.6.10. Remove /etc/asound.conf and store the current mixer
> settings.
> 2. Boot in 2.6.11 and let alsactl restore the mixer.
>
> Provided the machine is powered down between each attempt this gives the
> same result. 'Headphone Jack Sense' ends up not muted (which means that
> the built-in speakers are dead).
>
> I fail to find where FC saves/restores the mixer settings so I can't
> test without it. There are commands in modprobe.conf but asound.conf
> still gets updated when I remove these lines. So there must be some more
> place[s] where alsactl gets called.
Usually it's called either in init script or in udev configuration.
Or, it's not set up via alsactl but by other apps (e.g. kmix). I'm
not sure whether GNOME does anything special in this regard, though.
Takashi
next prev parent reply other threads:[~2005-03-08 3:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 12:51 intel 8x0 went silent in 2.6.11 Pierre Ossman
2005-03-03 17:45 ` Nish Aravamudan
2005-03-03 18:46 ` Mark Canter
2005-03-03 18:52 ` [Alsa-devel] " Lee Revell
2005-03-03 19:06 ` Mark Canter
2005-03-03 19:09 ` Lee Revell
[not found] ` <Pine.LNX.4.62.0503031410450.19015@krusty.vfxcomputing.com>
2005-03-03 19:22 ` Lee Revell
[not found] ` <29495f1d050303114379ab96b5@mail.gmail.com>
2005-03-03 19:47 ` Lee Revell
2005-03-03 20:33 ` Mark Canter
2005-03-03 23:49 ` Andrew Morton
2005-03-04 0:37 ` Pierre Ossman
2005-03-04 21:16 ` Pierre Ossman
2005-03-05 19:00 ` Lee Revell
2005-03-07 20:13 ` Pierre Ossman
2005-03-07 20:26 ` Takashi Iwai [this message]
2005-03-07 13:50 ` Takashi Iwai
2005-03-07 20:16 ` Pierre Ossman
2005-03-07 20:21 ` Takashi Iwai
2005-03-08 1:10 ` Pierre Ossman
2005-03-08 11:53 ` Takashi Iwai
2005-03-08 12:46 ` Pierre Ossman
2005-03-09 1:53 ` Mark Canter
2005-03-09 3:02 ` Lee Revell
2005-03-04 2:50 ` Mark Canter
2005-03-04 5:13 ` Jeff Garzik
2005-03-04 18:02 ` Lee Revell
2005-03-03 19:42 ` Nish Aravamudan
2005-03-04 20:40 ` Bill Davidsen
2005-03-04 20:44 ` Lee Revell
2005-03-04 20:44 ` Mark Canter
2005-03-04 0:36 ` Pierre Ossman
2005-03-04 20:36 ` Bill Davidsen
2005-03-04 21:06 ` Lee Revell
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=s5hbr9vurrd.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus@vfxcomputing.com \
--cc=nish.aravamudan@gmail.com \
--cc=rlrevell@joe-job.com \
/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