public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Internal speakers not working on HP ProBook 455 G2
Date: Sat, 28 Feb 2015 15:03:41 +0900	[thread overview]
Message-ID: <54F15A3D.8050003@daenzer.net> (raw)
In-Reply-To: <s5hegpfel1l.wl-tiwai@suse.de>

On 24.02.2015 18:05, Takashi Iwai wrote:
> At Tue, 24 Feb 2015 17:43:10 +0900,
> Michel D4nzer wrote:
>> On 19.02.2015 20:38, Takashi Iwai wrote:
>>> At Thu, 19 Feb 2015 15:24:15 +0900,
>>> Michel D4nzer wrote:
>>>>
>>>> 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?
>>
>> No, it's the same with Debian's default 3.16 kernel.
> 
> What about even older one?

Are you thinking of any particular version(s)? How important is it to
test that?


>>>> In pavucontrol, the speakers appear as "Speakers (unavailable)", and in
>>>> the GNOME sound settings they don't appear at all.
>>
>> In the meantime, I've noticed that those symptoms are due to the
>> headphone jack being incorrectly detected as connected. And indeed, on a
>> different laptop I get all the same symptoms while headphones are
>> plugged in.
>>
>> So, it occurred to me to try 'the other OS' on this laptop, and the
>> behaviour there is weird as well: No sound from the speakers even while
>> nothing's plugged into the headphone jack. When I plug in headphones,
>> there's a notification: "Something was just unplugged from your
>> headphone jack" (!), then sound works as expected through the
>> headphones. When I unplug them again, there's a notification: "Something
>> was just plugged into your headphone jack".
> 
> So the plug state is inverted?

Not exactly. The notifications in Windows sound like that, but the
speakers don't work regardless of whether headphones are plugged in or
not (even in Windows).


>> In Linux, I haven't seen any visible change when plugging in or out the
>> headphones.
> 
> You can watch the output of "alsactl monitor".

When plugging in headphones:

card 1, #38 (0,0,0,Mic Jack,0) VALUE
card 1, #34 (2,0,0,Internal Mic Boost Volume,0) VALUE
card 1, #34 (2,0,0,Internal Mic Boost Volume,0) VALUE
card 1, #33 (2,0,0,Mic Boost Volume,0) VALUE
card 1, #33 (2,0,0,Mic Boost Volume,0) VALUE

When unplugging them again:

card 1, #38 (0,0,0,Mic Jack,0) VALUE
card 1, #33 (2,0,0,Mic Boost Volume,0) VALUE
card 1, #33 (2,0,0,Mic Boost Volume,0) VALUE
card 1, #34 (2,0,0,Internal Mic Boost Volume,0) VALUE
card 1, #34 (2,0,0,Internal Mic Boost Volume,0) VALUE


>> Do you think the hardware is defective? Any possible workarounds for the
>> incorrect headphone jack detection?
> 
> The question is whether it's an unreliable jack detection (sometimes /
> always doesn't report the event) or the jack detection is inverted by
> some reason (plug / unplug swapped).  In the latter case, you can set
> a hint "inv_jack_detect = 1".  See
> Documentation/sound/alsa/HD-Audio.txt, the section "Hint Strings",
> "HD-Audio Reconfiguration" and "Early Patching" sections.

Setting inv_jack_detect = 1 makes the speakers work by default, but then
plugging in headphones isn't detected.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2015-02-28  6:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  6:24 Internal speakers not working on HP ProBook 455 G2 Michel Dänzer
2015-02-19 11:38 ` Takashi Iwai
2015-02-24  8:43   ` Michel Dänzer
2015-02-24  9:05     ` Takashi Iwai
2015-02-28  6:03       ` Michel Dänzer [this message]
2015-02-28  7:58         ` Takashi Iwai
2015-03-24  8:09           ` Michel Dänzer
2015-03-24  8:23             ` Takashi Iwai
2015-06-23  6:37     ` Michel Dänzer

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=54F15A3D.8050003@daenzer.net \
    --to=michel@daenzer.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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