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: Tue, 24 Mar 2015 17:09:00 +0900 [thread overview]
Message-ID: <55111B9C.5030900@daenzer.net> (raw)
In-Reply-To: <s5h385qii1k.wl-tiwai@suse.de>
On 28.02.2015 16:58, Takashi Iwai wrote:
> At Sat, 28 Feb 2015 15:03:41 +0900,
> Michel D4nzer wrote:
>>
>> 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.
[...]
>>>> 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
>
> So, your headphone is recognized wrongly as a microphone.
Actually, there are two pins for the (black) headphone jack, which BTW
has a headset icon next to it. Maybe some kind of headset quirk is
needed, or maybe one of the jacks should be gated by the other one?
> This implies that the pins aren't properly set up by BIOS. Maybe BIOS
> update will solve this?
>
> If no BIOS update doesn't solve (or you don't want it),
I already have the latest BIOS version.
> you have to figure out the right pin configuration by trial and error.
> hdajackretask and hda-analyzer would be your friend.
I've been playing around with them, but I don't really know what I'm
doing, and I haven't had much luck yet.
Something else I've noticed in the meantime: With inv_jack_detect
enabled, I can get sound from the speakers by choosing them for output
in the GNOME sound preferences. If I choose "Analog Output - Built-in
Audio" there, the sound comes out of the connected headphones.
--
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
next prev parent reply other threads:[~2015-03-24 8:09 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
2015-02-28 7:58 ` Takashi Iwai
2015-03-24 8:09 ` Michel Dänzer [this message]
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=55111B9C.5030900@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.