[HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones

Bug #1901926 reported by Sarto Carneiro
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

There is no sound at all from the headphones (p3 out). Speakers work fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sartojr 2255 F.... pulseaudio
 /dev/snd/controlC0: sartojr 2255 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 28 13:48:59 2020
InstallationDate: Installed on 2020-01-14 (287 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: HDA NVidia - HDA NVidia
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sartojr 2255 F.... pulseaudio
 /dev/snd/controlC0: sartojr 2255 F.... pulseaudio
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago)
dmi.bios.date: 11/04/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P03REZ.041.191104.FL
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP760XBE-XW1BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.family: Notebook 7 Series
dmi.product.name: 760XBE
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
dmi.product.version: P03REZ
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083

Revision history for this message
Sarto Carneiro (sartojr) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
Marcus Aurelius (marcuscf) wrote :

I'm facing a similar problem. May I ask your alsa-utils version? Is it 1.2.2-1ubuntu2 or 1.2.2-1ubuntu1?

My issues started when the system updated to alsa-utils 1.2.2-1ubuntu2.

Revision history for this message
Sebastien Bacher (seb128) wrote :

@Marcu, do you mean if you go back to 1.2.2-1ubuntu1 the issue resolves itself?

Revision history for this message
Sebastien Bacher (seb128) wrote :

If that that would be a regression from bug #1899745

Hui could you investigate if that's correct?

tags: added: regression-update
Revision history for this message
Hui Wang (hui.wang) wrote :

@Marcus,

could you please upload the log of pa-info (pa-info > pa-info.txt) both with alsa-utils 1.2.2-1ubuntu1 and ubuntu2?

Revision history for this message
Marcus Aurelius (marcuscf) wrote :

While generating the logs I found out that maybe it's not alsa-utils version.

It could also be a combination of the following:

- Booting up with earphones plugged in makes the sound come out from the internal speakers (and not the earphones).
- Changing the sound output device in the settings app to the earphones doesn't work (they remain silent - I tested using the test window)
- Unplugging the earphones and plugging them back in works, but only if the settings app is closed. In all cases a window pops up asking what kind of device I plugged in (phones, phones+mic, mic), but the end result differs.
- Audacity seems to reset _something_ when it starts up so whatever state the system was in before launching Audacity might need to be set up again (e.g. unplugging and plugging my earphones yet again).
- There was another update in the meantime including libasound2, libasound2-data, systemd, libudev1, etc. so that could be related too.

Of course I performed most tests using the settings app, that would explain why I couldn't get any sound on my earphones by normal means.

I will upload my logs when I have some kind of consistent and reproducible state (unless you want me to send them anyway).

Revision history for this message
Marcus Aurelius (marcuscf) wrote :
Revision history for this message
Marcus Aurelius (marcuscf) wrote :

OK, I'm attaching the logs since I could reproduce the bug again.

When upgrading from alsa-utils 1.2.2-1ubuntu1 to alsa-utils 1.2.2-1ubuntu2 with speakers plugged in the 3.5mm jack, I could clearly hear a "thump" sound when the 3.5mm jack stopped working. Neither a reboot or a cold boot solved it.

What's weird is that I couldn't reproduce that same thing earlier today, doing basically the same steps. The only differences were: [1] I had tested with earphones+mic earlier today and now I'm testing with speakers (in the same jack) and [2] When I upgraded with speakers connected I could hear the exact moment when something wrong happened.

As you can guess from the file names ("01" and "07") I have intermediate log files that I'm not sending yet to avoid attaching superfluous info.

Revision history for this message
Marcus Aurelius (marcuscf) wrote :

I'm not an expert at all but I noticed these lines in my logs:

When sound works:

Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
[...]
  Pin-ctls: 0xc0: OUT HP

When it doesn't work:

Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
[...]
  Pin-ctls: 0x00:

OP has the first form. Would that mean that we are experiencing two different issues?

Revision history for this message
Hui Wang (hui.wang) wrote :

@Marcus,

Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
[...]
  Pin-ctls: 0x00:

With this setting, the headphone jack can't output any sound.

When you plug a headphone or spakers in the audio jack, please select speakers from the pop-up dialogue, if you plug a headset (headphone with a mic), please select headset-mic from the dialogue, if you plug a pure microphone, please select the microphones from the dialogue. The audio jack on your machine is a multi-function audio jack, you need to correctly select what audio device you plugged in.

According to the log of #9, after you plu the headphone, either the dialogue didn't popup or you select the microphone from the dialogue by a mistake.

Revision history for this message
Marcus Aurelius (marcuscf) wrote :

@hui.wang

Thanks for looking into it and explaining how it works.

What you describe is compatible with what I'm seeing, but I don't think I misclicked on that dialog that many times :-) I will test it again soon though.

Is there any possibility that the dialog has some kind of issue where it can't apply the user selection or that its default option has changed when the dialog doesn't pop up or something else goes wrong? It's extremely unlikely that I misclicked "Mic" everytime (I may have clicked on it once or twice just to experiment a little).

Do you know if there's some command or tool that will show that popup again allowing me to confirm/fix my selection after plugging it in and getting no sound? That would be easier to test than unplugging the headphones over and over. If there's a command-line tool that does the same thing and prints out better diagnostics, that would be helpful to understand what's going on.

Revision history for this message
Sarto Carneiro (sartojr) wrote : Re: [Bug 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
Download full text (3.3 KiB)

Hello, my alsa is 1.2.2-1ubuntu2, but i had this problem since ubuntu
18.04. Now I'm using 20.04.

Em qui., 5 de nov. de 2020 às 16:03, Marcus Aurelius <
<email address hidden>> escreveu:

> I'm facing a similar problem. May I ask your alsa-utils version? Is it
> 1.2.2-1ubuntu2 or 1.2.2-1ubuntu1?
>
> My issues started when the system updated to alsa-utils 1.2.2-1ubuntu2.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1901926
>
> Title:
> [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
>
> Status in alsa-driver package in Ubuntu:
> Confirmed
>
> Bug description:
> There is no sound at all from the headphones (p3 out). Speakers work
> fine.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: alsa-base 1.0.25+dfsg-0ubuntu5
> ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
> Uname: Linux 5.4.0-52-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.10
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: sartojr 2255 F.... pulseaudio
> /dev/snd/controlC0: sartojr 2255 F.... pulseaudio
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> Date: Wed Oct 28 13:48:59 2020
> InstallationDate: Installed on 2020-01-14 (287 days ago)
> InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
> PackageArchitecture: all
> ProcEnviron:
> LANGUAGE=pt_BR:pt:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=pt_BR.UTF-8
> SHELL=/bin/bash
> SourcePackage: alsa-driver
> Symptom: audio
> Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH
> successful
> Symptom_Card: HDA NVidia - HDA NVidia
> Symptom_DevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: sartojr 2255 F.... pulseaudio
> /dev/snd/controlC0: sartojr 2255 F.... pulseaudio
> Symptom_PulsePlaybackTest: PulseAudio playback test successful
> Symptom_Type: No sound at all
> Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
> UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago)
> dmi.bios.date: 11/04/2019
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: P03REZ.041.191104.FL
> dmi.board.asset.tag: No Asset Tag
> dmi.board.name: NP760XBE-XW1BR
> dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
> dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
> dmi.chassis.version: N/A
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
> dmi.product.family: Notebook 7 Series
> dmi.product.name: 760XBE
> dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
> dmi.product.version: P03REZ
> dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
> mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083
>
>...

Read more...

Revision history for this message
Sarto Carneiro (sartojr) wrote :
Download full text (4.3 KiB)

In my case unplugging and puggling the headphones makes no difference at
all, and doesn't pop up anything.

Em sex., 6 de nov. de 2020 às 13:55, Marcus Aurelius <
<email address hidden>> escreveu:

> While generating the logs I found out that maybe it's not alsa-utils
> version.
>
> It could also be a combination of the following:
>
> - Booting up with earphones plugged in makes the sound come out from the
> internal speakers (and not the earphones).
> - Changing the sound output device in the settings app to the earphones
> doesn't work (they remain silent - I tested using the test window)
> - Unplugging the earphones and plugging them back in works, but only if
> the settings app is closed. In all cases a window pops up asking what kind
> of device I plugged in (phones, phones+mic, mic), but the end result
> differs.
> - Audacity seems to reset _something_ when it starts up so whatever state
> the system was in before launching Audacity might need to be set up again
> (e.g. unplugging and plugging my earphones yet again).
> - There was another update in the meantime including libasound2,
> libasound2-data, systemd, libudev1, etc. so that could be related too.
>
> Of course I performed most tests using the settings app, that would
> explain why I couldn't get any sound on my earphones by normal means.
>
> I will upload my logs when I have some kind of consistent and
> reproducible state (unless you want me to send them anyway).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1901926
>
> Title:
> [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
>
> Status in alsa-driver package in Ubuntu:
> Confirmed
>
> Bug description:
> There is no sound at all from the headphones (p3 out). Speakers work
> fine.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: alsa-base 1.0.25+dfsg-0ubuntu5
> ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
> Uname: Linux 5.4.0-52-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.10
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: sartojr 2255 F.... pulseaudio
> /dev/snd/controlC0: sartojr 2255 F.... pulseaudio
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> Date: Wed Oct 28 13:48:59 2020
> InstallationDate: Installed on 2020-01-14 (287 days ago)
> InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
> PackageArchitecture: all
> ProcEnviron:
> LANGUAGE=pt_BR:pt:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=pt_BR.UTF-8
> SHELL=/bin/bash
> SourcePackage: alsa-driver
> Symptom: audio
> Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH
> successful
> Symptom_Card: HDA NVidia - HDA NVidia
> Symptom_DevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: sartojr 2255 F.... pulseaudio
> /dev/snd/controlC0: sartojr 2255 F.... pulseaudio
> Symptom_PulsePlaybackTest: PulseAudio playback test successful
> Symptom_Type: No sound at all
> Title: [HDA-Intel - HDA Intel PCH, playback] ...

Read more...

Revision history for this message
Marcus Aurelius (marcuscf) wrote :

FYI my problem seems to be solved after a bunch of updates to several alsa packages a few weeks ago.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.