From: Takashi Iwai Subject: Re: Internal speakers not working on HP ProBook 455 G2 Date: Thu, 19 Feb 2015 12:38:02 +0100 Message-ID: References: <54E5818F.9020105@daenzer.net> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 3C23226057D for ; Thu, 19 Feb 2015 12:38:03 +0100 (CET) In-Reply-To: <54E5818F.9020105@daenzer.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Michel D4nzer Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Thu, 19 Feb 2015 15:24:15 +0900, Michel D4nzer wrote: > > Hi, > > > the built-in speakers of my HP ProBook 455 G2 are not working by > default. I'm attaching the output of alsa-info.sh. Is this a regression from earlier kernels? > In pavucontrol, the speakers appear as "Speakers (unavailable)", and in > the GNOME sound settings they don't appear at all. > > > After some playing around with HDAAnalyzer, I discovered that enabling > the 'OUT' widget control of pin 0x14 makes the speakers emit sound, see > the diff below. Interesting. This behavior doesn't appear on the emulator, so something else must have cleared the pin ctl. To be sure, load snd-hda-intel module with probe_only=1,1 option. You can check /proc/asound/card1/codec#0 to see which value is set to the pin 0x14 by BIOS as default. Then, enable the tracing via # echo 1 > /sys/kernel/debug/tracing/events/hda/enable and configure the codec via # echo 1 > /sys/class/sound/hwC1D0/reconfigure This will set up the PCM and the mixer. Get the events from /sys/kernel/debug/tracing/trace. At this point. Then check again whether pin 0x14 is set or not. Better to check the above without PulseAudio, i.e. do it in runlevel 3 on Linux console. Once when the problem is confirmed (the pin control is still 0x00), try to check the events log you got. The bits 28-32 of the event value indicates the codec address, the bits 20-28 the widget nid, and the rest 20 bits the combo of verb + parameter. So, the command SET_PIN_WIDGET_CONTROL for the widget 0x14 should appear like 0x01470740 where 0x707 is SET_PIN_WIDGET_CONTROL verb and 0x40 is the pin control value. thanks, Takashi