Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753927AbbEUJTI (ORCPT ); Thu, 21 May 2015 05:19:08 -0400 Received: from cantor2.suse.de ([195.135.220.15]:57878 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751765AbbEUJTD (ORCPT ); Thu, 21 May 2015 05:19:03 -0400 Date: Thu, 21 May 2015 11:19:02 +0200 Message-ID: From: Takashi Iwai To: Martin Steigerwald Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [REGRESSION] 4.1-rc4: Sound muted after boot In-Reply-To: <2273195.tahhRQoM4G@merkaba> References: <1902192.Ae1uPbIBnJ@merkaba> <2273195.tahhRQoM4G@merkaba> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.5 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3100 Lines: 71 At Thu, 21 May 2015 11:08:36 +0200, Martin Steigerwald wrote: > > Am Donnerstag, 21. Mai 2015, 06:28:24 schrieb Takashi Iwai: > > At Wed, 20 May 2015 16:31:55 +0200, > > > > Martin Steigerwald wrote: > > > Hello! > > > > > > On ThinkPad T520 (Intel Sandybridge) with 4.14-rc4 + two BTRFS patches > > > and one Intel P-State debug patch I have no sound output on internal > > > Intel HD audio codec. > > > > > > According to ThinkPad T520 LED with striked-through speaker the loud > > > speaker is in disabled state. Also KDE´s Phonon says a soundcard is > > > missing. In alsa-mixer I see nothing as MM for muted. If I press the > > > key next to the LED I get a notification on the desktop that loud > > > speaker has been enabled / disabled, but the LED still is on for it > > > being disabled. > > One clarification: Phonon still seems to see a sound card… but it reports a > change to the list of soundcards. > > And another observation: The speaker disable LED is switched on KDE/Plasma > 4.14.2 session startup, I just rebooted to 4.1-rc4 after I gathered debug > output of 4.0.1, and there on boot the speaker disable LED was off during > boot. > > So there seems Phonon is confused about some difference in ALSA between these > two kernel versions and probably doesn´t fully find the sound card or mutes > it, but on the other hand I can´t see it in alsa-mixer as muted. > > And alsa-mixer still finds the internal sound. > > Also this does not happen for external USB JBL Pebbles speakers (excellent > ones!) at home, sound just works with 4.1-rc4 with these. > > I am now on 4.1-rc4 again so could try to dig out more what KDE Phonon sees > as a difference. In trainings breaks. Now need to continue with the course I > hold. > > Phonon runs without PulseAudio here, cause PulseAudio creates additional > issues with sound. Okay, this is the message I get: > > KDE hat festgestellt, dass eines oder mehrere interne Geräte entfernt > wurden. > Soll KDE die Informationen zu diesen Geräten dauerhaft löschen? > Dies ist die Liste der Geräte, die entfernt werden können: > Aufnahme: HDA Intel PCH (CX20590 Analog) > Wiedergabe: HDA Intel PCH (CX20590 Analog) > > Which means: KDE has found that one or more internal devices were removed. > > So it seems KDE really does not find the sound card anymore, while alsa-mixer > finds it, yet, also aplay does not produce any sound. > > But then I still have a "HDA Intel PCH (CX20590 Analog)" in systemsettings > for Phonon. There is one greyed out and another one which is not greyed out, > but does not produce any sound on clicking the test button either. All of these sound like a problem with Phonon. There is no change in the interface and device names of your board between 4.0 and 4.1 in the kernel level. You can compare alsa-info.sh outputs. 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/