From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
alsa-devel@lists.sourceforge.net,
Mark Canter <marcus@vfxcomputing.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: intel 8x0 went silent in 2.6.11
Date: Fri, 04 Mar 2005 01:36:17 +0100 [thread overview]
Message-ID: <4227AD81.9000606@drzeus.cx> (raw)
In-Reply-To: <29495f1d05030309455a990c5b@mail.gmail.com>
Nish Aravamudan wrote:
>On Thu, 03 Mar 2005 13:51:40 +0100, Pierre Ossman <drzeus-list@drzeus.cx> wrote:
>
>
>>I just upgraded to Linux 2.6.11 and the soundcard on my machine went
>>silent. All volume controls are correct and there are no errors
>>reported. But no sound coming from the speakers. And here's the kicker,
>>the headphones work fine!
>>2.6.10 still works so the bug appeared in one of the patches in between.
>>The sound card is the one integrated into intels mobile ICH4 chipset.
>>
>>
>
>There was some discussion of this on LKML a while ago. Are you sure
>you have disabled "Headphone Jack Sense" and "Line Jack Sense" in
>alsamixer?
>
>Thanks,
>Nish
>
>
This has been rather wildly debated now but yes, muting those enables
sound. I don't have a docking station so I can't try any effects there.
I wouldn't say that it's intuitive to mute two channels to get speakers
working though.
Rgds
Pierre
next prev parent reply other threads:[~2005-03-04 0:44 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
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 [this message]
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=4227AD81.9000606@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus@vfxcomputing.com \
--cc=nish.aravamudan@gmail.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