From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757550AbZF3OfM (ORCPT ); Tue, 30 Jun 2009 10:35:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753344AbZF3Oe7 (ORCPT ); Tue, 30 Jun 2009 10:34:59 -0400 Received: from cantor.suse.de ([195.135.220.2]:35929 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753425AbZF3Oe7 (ORCPT ); Tue, 30 Jun 2009 10:34:59 -0400 Date: Tue, 30 Jun 2009 16:34:59 +0200 Message-ID: From: Takashi Iwai To: "Rafael J. Wysocki" Cc: LKML , alsa-devel@alsa-project.org Subject: Re: Problems with snd-hda-intel on hp 6930p (2.6.30) In-Reply-To: <200906301615.38244.rjw@sisk.pl> References: <200906292037.09597.rjw@sisk.pl> <200906301529.56598.rjw@sisk.pl> <200906301615.38244.rjw@sisk.pl> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.3 (x86_64-suse-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Tue, 30 Jun 2009 16:15:37 +0200, Rafael J. Wysocki wrote: > > On Tuesday 30 June 2009, Rafael J. Wysocki wrote: > > On Tuesday 30 June 2009, Takashi Iwai wrote: > > > At Mon, 29 Jun 2009 20:37:09 +0200, > > > Rafael J. Wysocki wrote: > > > > > > > > Hi Takashi, > > > > > > > > I have a problem with snd-hda-intel from 2.6.30 on an hp EliteBook 6930p, which > > > > is that the sound is not audible, although everything appears to work just > > > > fine. Except maybe that when the box is rebooted and KDE (3.5) is started, > > > > the master control is "muted" and the led indicator next to the keyboard shows > > > > "no sound". Then, changing the "muted" status of the master control doesn't > > > > change the state of the led indicator and vice versa (the two things appear to > > > > be totally independent of each other). > > > > > > > > Can you please tell me what I can do to debug this issue? > > > > > > Could you run alsa-info.sh with --no-upload option on both "muted" > > > and "not muted" states, and attach the generated files? > > > > Sure. In the meantime it turned out that after a power off and cold boot the > > status of the master control is 'on', but the led indicator shows 'no sound', so > > there are 5 outputs: > > * alsa-info-postboot.txt - after power off and cold boot > > * alsa-info-led.txt - led indicator switched to 'on' when it was in the > > alsa-info-postboot.txt state > > Now I switched to AC power and rebooted the box without powering off: > > * alsa-info-muted.txt - initial state with the 'muted' master control > > * alsa-info-on.txt - master control switched to 'on' when it was in the > > alsa-info-muted.txt state > > * alsa-info.txt - led indicator switched to 'on' when it was in the > > alsa-info-on.txt state > > > > > If it's a regression (heh :), please give alsa-info.sh output on > > > older kernels. > > > > No, it's not a regression. At least not from 2.6.27. > > > > Please let me know if you need more information. > > One more thing. The headphones output actually works regardless of the > led indicator status, so only the built-in speakers output seems to be > affected. How can you turn on/off LED? From your explanation, it seems not directly bound with the audio mute. Anyway, try model=mobile or model=laptop for snd-hda-intel module option. Does the speaker work? Takashi