[HP Pavilion x360 Convertible 14-ba1xx, Realtek ALC295, Speaker, Internal] No sound at all

[anoopjohn]

I have installed Ubuntu 19.04 and the laptop does not play any sound through the internal speakers. When I plug in the headphone I am able to listen sound though.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: anoopjohn 1718 F.... pulseaudio
 /dev/snd/pcmC0D0p: anoopjohn 1718 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 24 17:17:01 2019
InstallationDate: Installed on 2019-08-23 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: anoopjohn 1718 F.... pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP Pavilion x360 Convertible 14-ba1xx, Realtek ALC295, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/12/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.52
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83C4
dmi.board.vendor: HP
dmi.board.version: 31.61
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.52:bd11/12/2018:svnHP:pnHPPavilionx360Convertible14-ba1xx:pvrType1ProductConfigId:rvnHP:rn83C4:rvr31.61:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-ba1xx
dmi.product.sku: 5GR61UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-08-24T17:12:21.772103

[Hui Wang (hui.wang)]

Did the speaker ever work before?

[anoopjohn (anoop.john)]

Thanks for looking into this. The system comes pre-installed with Windows. The speaker works in Windows but I have not gotten it to work yet on Ubuntu yet.

I played around with hdajackretask, snd-hda-intel model but nothing seemed to work.

After I had posted this bug I was playing around with different solutions. It looks like I ran into something that made it work.

I saw a post about booting into windows, shutting down the system completely and then booting into Linux. It looks like that did the trick. I had earlier only rebooted from Windows into Ubuntu but never shutdown and reboot.

[anoopjohn (anoop.john)]

I believe that this is still a bug. Will be happy to help debug / provide more info.

[Hui Wang (hui.wang)]

Please collect two alsa-info.txt with dump_coef enabled:

1) boot into windows, shutdown, boot into ubuntu linux, make sure the speaker works, then sudo su; cat 1 > /sys/module/snd_hda_codec/parameters/dump_enable; collect an alsa-info.txt-spk-work by running alsa-info.sh

2) boot into ubuntu linux, make sure the speaker doesn't work. then sudo su, cat 1 > /sys/module/snd_hda_codec/parameters/dump_enable; collect an alsa-info.txt-spk-no-work by running alsa-info.sh

thx.

[anoopjohn (anoop.john)]

I was unable to run the dump_enable command as I was getting permission denied even when running as sudo su. This is the alsa-info when I booted into Ubuntu while rebooting from Windows and when there is no sound. I will do the same while booting from a shutdown state from windows.

[anoopjohn (anoop.john)]

Sorry, looks like I did not follow the full instructions. Here is the file with the proper name.

I am also documenting the steps so that somebody else can follow the instructions as well.

This is after booting into Windows and then rebooting into Ubuntu without a Windows shutdown

Stop pulseaudio

As user run

systemctl --user stop pulseaudio.socket
systemctl --user stop pulseaudio.service

Then run

sudo su

Then run

echo 1 > /sys/module/snd_hda_codec/parameters/dump_coefs

I was getting a permission denied error even as root. I was however able to change permission of the file and edit with vi and change the value -1 to 1

root@zyxware-aj:/home/anoopjohn# echo 1 > /sys/module/snd_hda_codec/parameters/dump_coefs
bash: /sys/module/snd_hda_codec/parameters/dump_coefs: Permission denied

Then run

cat 1 > /sys/module/snd_hda_codec/parameters/dump_enable

I was getting a Permission Denied error

root@zyxware-aj:/sys/module/snd_hda_codec/parameters# cat 1 > /sys/module/snd_hda_codec/parameters/dump_enable
bash: /sys/module/snd_hda_codec/parameters/dump_enable: Permission denied

I was not able to edit file with vi like with the dump_coefs file as the file did not exist and I could not create the file

alsa-info --no-upload --output alsa-info.txt-spk-no-work

Am uploading the file here.

[anoopjohn (anoop.john)]

Here is the alsa-info for the case where I booted into windows, shutdown completely, then boot into Ubuntu. Sound is working

Same permissions issues exist for writing the alsa parameters. I was able to set dump_coef but not dump_enable

[Hui Wang (hui.wang)]

Sorry, it was my fault. Correct #5, it should be "echo 1 >" instead of "cat 1 >". Anyway you generated the alsa-info.txt with coeff in the #7 and #8.

[Hui Wang (hui.wang)]

Please do a test:

When speaker doesn't work, run,

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x6ac8
// check if speaker works now

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0xd
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xa023
// check if speaker works now

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x31
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xd200
// check if speaker works now

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x37
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xfe05
// check if speaker works now

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x51
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x6f6f
// check if speaker works now

[anoopjohn (anoop.john)]

Apologies for the delay in getting back.

I booted into windows, rebooted into Ubuntu without shutdown, sound is not working. Ran speaker-test in a terminal and youtube video in firefox. No sound.

Ran the command sets one by one.

No sound came out after any set.

Please let me know what else need to be tested.

[anoopjohn (anoop.john)]

Found something interesting as well.

I had accidentally left the speaker-test running and closed the laptop without shutting it down. When the laptop was opened again ubuntu opened from sleep, sound was playing. However do note that I had run those commands in the same session.

So something that takes the system to sleep and back from sleep is allowing sound to come back again.

Will retry without running the commands after warm re-booting from windows again.

[anoopjohn (anoop.john)]

Retried with booting to windows, warm rebooting to Ubuntu, confirmed that sound is not working, closed laptop without shutting down, opened the laptop and sound is working.

Hope that helps.

[Glen Fletcher (fletch2770)]

I have the same problem that is initially solved in the same way. Closing the laptop and opening it again seems to restore sound. Running Ubuntu Studio v19.10 amd64 on a brand new, just bought HP Pavilion x360-14-dh1008ca. Any way I can help with full solution, let me know.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Daniel Hutzley (enderger)]

I have found this same bug in Ubuntu 20.04 on a HP Pavilion.