Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262315AbVCIB7s (ORCPT ); Tue, 8 Mar 2005 20:59:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262299AbVCIBz2 (ORCPT ); Tue, 8 Mar 2005 20:55:28 -0500 Received: from krusty.vfxcomputing.com ([66.92.20.10]:57560 "EHLO krusty.vfxcomputing.com") by vger.kernel.org with ESMTP id S262316AbVCIByK (ORCPT ); Tue, 8 Mar 2005 20:54:10 -0500 Date: Tue, 8 Mar 2005 20:53:41 -0500 (EST) From: Mark Canter To: Takashi Iwai cc: Pierre Ossman , Andrew Morton , rlrevell@joe-job.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 In-Reply-To: Message-ID: References: <4227085C.7060104@drzeus.cx> <29495f1d05030309455a990c5b@mail.gmail.com> <1109875926.2908.26.camel@mindpipe> <1109876978.2908.31.camel@mindpipe> <20050303154929.1abd0a62.akpm@osdl.org> <4227ADE7.3080100@drzeus.cx> <4228D013.8010307@drzeus.cx> <422CB68A.1050900@drzeus.cx> <422CFB6E.1020002@drzeus.cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1923 Lines: 44 I think I've gone through every possible value here from asound.state to each setting in KDE itself. Still, the only sound that works is the one coming from line-out, without the port replicator, no sound exists whatsoever. Both of the below controls are set to false in asound.state and cooresponding KDE settings in kmix. I think the concern becomes though, regardless of what kde was doing after the fact, this condition didn't exits in <= 2.6.10 when no other applications where changed around it. On Tue, 8 Mar 2005, Takashi Iwai wrote: > > My question is its 'value'. The entry in /etc/asound.state should > have a boolean value. > > Let me repeat the explanation of the situation: > > The existence of 'Headphone Jack Sense' and 'Line-in Jack Sense' > controls themselves are not the problem. If they are set off, the > behavior of the driver must be identical with the older version. > No regression. The patch I mentionted turns off them as default unless > the device is known to work. But the controls still exist, and you > can change them afterward manually. > > So, the solution is once to turn off these controls via a mixer and > save the state via alsactl (usually the system does at shutdown), so > that the correct states are restored at the next reboot. That's why I > asked you - to check the saved status of these controls. > > If the correct values are saved there and still the problem exists, > someone else must have changed the mixer status. For example, KDE > (kmix) seems to set up the mixer status by itself, and does not always > correctly. That was my suspect. I don't know GNOME does something > like that, too. > > > Takashi > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/