Bug #1851518 “[950SBE/951SBE, Realtek ALC298, Speaker, Internal]...” : Bugs : linux package : Ubuntu

Revision history for this message

Martin S (martins4321) wrote on 2019-11-06:

#1

alsa-info.txt Edit (42.9 KiB, text/plain)
AlsaInfo.txt Edit (41.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (76.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (21.4 KiB, text/plain; charset="utf-8")
modified.conffile..etc.modprobe.d.alsa-base.conf.txt Edit (2.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Filipe Garrett (wowbaggerbr) wrote on 2019-11-07:

#2

I have a very similar issue with another Samsung laptop: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-08:

#3

Please collect an alsa-info.txt with coeff dumped:

sudo su
echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef
then run alsa-info and upload the log.

thx.

Revision history for this message

Martin S (martins4321) wrote on 2019-11-09:

#4

alsa-info-with-coefficients.txt Edit (46.1 KiB, text/plain)

In the last few days, I've tried a few more things (incl. re-installing alsa, pulseaudio multiple times), but still have the same issue: headphones are extremely quiet, and nothing coming out of the internal speakers. The alsa-info with coefficients is attached.

Thanks for looking.

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-10:

#5

I will find a machine wit alc298 next week, and compare the coeff with your machine.

thx.

Revision history for this message

Martin S (martins4321) wrote on 2019-11-10:

#6

alsa-info-with-coefficients-headphones-work.txt Edit (48.7 KiB, text/plain)

Made a little progress: headphones work with
/etc/modprobe.d/alsa-base.conf:
options snd-hda-intel model=mono-speakers

Volume is loud and clear, in stereo!

alsa-info.sh output is attached with coefficients. Headphones were not plugged in at that time to keep the diffs to a minimum.

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-11:

#7

Please test:
options snd-hda-intel model=headset-mode-no-hp-mic

Revision history for this message

Martin S (martins4321) wrote on 2019-11-11:

#8

alsa-info-with-coefficients-headset-mode-no-hp-mic.txt Edit (46.0 KiB, text/plain)

Using options snd-hda-intel model=headset-mode-no-hp-mic

Result:
Headphones: very very quiet
Internal speakers: Nothing

Alsa-info is attached.

Thank you.

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-11:

#9

Please remove the model=xxxx or keep model=headset-mode-no-hp-mic

When headphone is very very quiet, please run:
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8e
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x20
//check if headphone can output sound normally?

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x19
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x317
//check if headphone can output sound normally?

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x1110
//check if headphone can output sound normally?

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x4f
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xc429
//check if headphone can output sound normally?

Revision history for this message

Martin S (martins4321) wrote on 2019-11-12:

#10

Hi,
I was surprised, but none of these settings helped. Mode was set originally to
options snd-hda-intel model=headset-mode-no-hp-mic

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8e
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x20
//check if headphone can output sound normally?

Running speaker-test:
very very quiet

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x19
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x317
//check if headphone can output sound normally?

same result

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x1110
//check if headphone can output sound normally?

same result

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x4f
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xc429
//check if headphone can output sound normally?

same result

Revision history for this message

Martin S (martins4321) wrote on 2019-11-12:

#11

FYI: I just re-tested with model=mono-speakers, and there the headhpone output likewise does not change for any of the above settings: it works great the entire time.

Thanks,
Martin

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-12:

#12

Ah, please test model=dell-headset3, it should work.

And please also add options snd-hda-codec-realtek dyndbg, then boot the system without the headphone plugged.

after boot up, plug headphone, and test if it works well. If it works well, please upload the dmesg.

thx.

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-12:

#13

RtHDDump_V236.zip Edit (240.6 KiB, application/zip)

And for speaker's issue, please verify that both speaker and headphone work well under windows, then using this tool to collect a log under windows, the log is a useful reference for linux.

thx.

Revision history for this message

Martin S (martins4321) wrote on 2019-11-13:

#14

dmesg.txt Edit (74.3 KiB, text/plain)

<<<<<<<<<<<<<<<<<<<
Ah, please test model=dell-headset3, it should work.

And please also add options snd-hda-codec-realtek dyndbg, then boot the system without the headphone plugged.

after boot up, plug headphone, and test if it works well. If it works well, please upload the dmesg.
>>>>>>>>>>>>>>>>>>>>

Yes, headphones work well. dmesg output is attached.

Thank you.

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-13:

#15

If you have time, please run #13 on the windows10.

And If you have time, please redo the test of #10, after finishing all commands, please generate an alsa-info.txt-with-coeff, let us check if all those commands successfully executed.

Revision history for this message

Martin S (martins4321) wrote on 2019-11-13:

#16

RtHDDump.txt Edit (652.1 KiB, text/plain)

>>>>>>>>>>>>>>>>>>>>>
please verify that both speaker and headphone work well under windows, then using this tool to collect a log under windows, the log is a useful reference for linux.
<<<<<<<<<<<<<<<<<<<<<

Output attached; looks like this might be helpful to get the speakers to work.

Thank you,
Martin

Revision history for this message

Martin S (martins4321) wrote on 2019-11-13:

#17

alsa-info-dell-headset3-with-coefficients.txt Edit (46.5 KiB, text/plain)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
nd If you have time, please redo the test of #10, after finishing all commands, please generate an alsa-info.txt-with-coeff, let us check if all those commands successfully executed.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Option: dell-headset3
Headphone works, and does not seem to change when any of the below settings are applied. alsa-info output attached; it was generated after the last command in the sequence.

martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8e
nid = 0x20, verb = 0x500, param = 0x8e
value = 0x0
martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x20
nid = 0x20, verb = 0x400, param = 0x20
value = 0x0

>>>>>>>> NO change

martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x19
nid = 0x20, verb = 0x500, param = 0x19
value = 0x0
martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x317
nid = 0x20, verb = 0x400, param = 0x317
value = 0x0

>>>>>>>> NO change

martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
nid = 0x20, verb = 0x500, param = 0x67
value = 0x0
martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x1110
nid = 0x20, verb = 0x400, param = 0x1110
value = 0x0

>>>>>>>> NO change

martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x4f
nid = 0x20, verb = 0x500, param = 0x4f
value = 0x0
martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xc429
nid = 0x20, verb = 0x400, param = 0xc429
value = 0x0

>>>>>>>> NO change

Thanks,
Martin

Revision history for this message

Martin S (martins4321) wrote on 2019-11-13:

#18

alsa-info-dell-headset3-with-coefficients.txt Edit (50.0 KiB, text/plain)

Attachment to #17 was incorrect (forgot to turn on coefficients)

Attached is alsa-info with coefficients.

Revision history for this message

Hui Wang (hui.wang) wrote on 2019-11-13:

#19

set-coeff.sh Edit (2.1 KiB, text/x-sh)

Please remove any modle=xxxx from alsa-base.conf

Install the testing kernel and reboot, then test headphone and speaker with the testing kernel.
https://people.canonical.com/~hwang4/samsung-test/
(to install the testing kernel, sudo dpkg -i linux-modules-xxx.deb; sudo dpkg -i linux-image-xxx.deb; sudo dpkg -i linux-modules-extra-xxxx.deb)

If headphone and speaker still don't work, please run this script and retest the headphone and speaker again.

then upload the dmesg and alsa-info.txt-with-coeff

Revision history for this message

Martin S (martins4321) wrote on 2019-11-13:

#20

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Install the testing kernel and reboot,
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Couldn't boot after installing all 3 .deb's:

error: /boot/vmlinuz-5.3.0.23.25+samsung-test-generic has invalid signature
error: you need to load the kernel first

Press any key to continue...

Revision history for this message

Martin S (martins4321) wrote on 2019-11-13:

#21

alsa-info-with-coefficients-after-set-coeff.txt Edit (50.0 KiB, text/plain)

Hi,

1) Steps:
- Removed the option model=
- Rebooted
- turned off Secure Boot and booted with your test kernel.

Result:
No sound from speakers.
Very very quiet headphones.

2) Steps:
sudo set-coeff.sh
sudo su
echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef

Result:
No sound from speakers.
Very very quiet headphones.

alsa-info is attached.

Thanks,
Martin

Revision history for this message

Martin S (martins4321) wrote on 2019-11-13:

#22

dmesg.txt Edit (76.9 KiB, text/plain)

dmesg output attached from #21, step 2)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-11-27:

#23

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

Changed in alsa-driver (Ubuntu):
status:	New → Confirmed

Revision history for this message

Klaus Ahrenberg (klausahrenberg) wrote on 2019-12-01:

#24

RtHDDump.txt Edit (590.1 KiB, text/plain)

I own model NT950SBE, same issue: No sound at headphones and speaker. I tried Ubuntu and Manjaro with latest kernels - no progress. After changing Alss-config according to post #6, haedphones are working now. Thanks.

/etc/modprobe.d/alsa-base.conf:
options snd-hda-intel model=mono-speakers

I attach my Realtek dump-file made in Windows. Hope that helps a bit to get a solution for the problem.

Revision history for this message

Terry Magnus Drever (terrymagnusdrever) wrote on 2020-04-04:

#25

I have exactly the same problem on a Samsung Galaxy Flex Book.

Headphones are working with the following
options snd-hda-intel model=mono-speakers

Speakers do not work.

Revision history for this message

Terry Magnus Drever (terrymagnusdrever) wrote on 2020-04-07:

#26

RealTek Dump Edit (44.4 KiB, application/zip)

Attached my realtek dump.

Revision history for this message

Duke Fong (duke-c) wrote on 2020-04-11:

#27

Same problem with Samsung Galaxy Book Flex 930QCG.

The Samsung Galaxy Chromebook and Galaxy Book Flex look very similar, the sound chip should be the same, the Chromebook is open source and also uses the Linux kernel, can we refer to the Chromebook code?

Revision history for this message

Mike Pozulp (gannon1) wrote on 2020-04-13:

#28

RtHDDump.txt Edit (456.9 KiB, text/plain)

Exactly the same problem with Samsung Notebook 9 Pro (np930mbe-k04us) which also has an ALC298.

Headphones are working with model=mono-speakers.

I attached my Realtek dump.

I'm also soliciting the arch forum for help (I'm running arch):

https://bbs.archlinux.org/viewtopic.php?pid=1897858

Revision history for this message

Mike Pozulp (gannon1) wrote on 2020-04-13:

#29

RtHDDump.txt.headphonesInJack Edit (461.2 KiB, text/plain)

I attached the Realtek dump with my headphones plugged into the jack for comparison.

Revision history for this message

ironincoder (ironincoder) wrote on 2020-04-13:

#30

I have been trying to get ALC298 working for a while now and wanted to share my findings. This issue exist on all distros and is an ALSA problem (not pulseaudio). Verified it when found a fix for the headphone by using the kernel's early patching feature. To use this feature, write a simple patch (instructions here https://www.kernel.org/doc/html/v5.0/sound/hd-audio/notes.html):

[codec]
0x10ec0298 0x144dc169 0

[model]
auto

[verb]
0x1a 0x707 0xc5

and save it as /lib/firmware/alc298-sound-patch.fw then save:

options snd-hda-intel patch=alc298-sound-patch.fw,alc298-sound-patch.fw,alc298-sound-patch.fw,alc298-sound-patch.fw

to /etc/modprobe.d/alc298-sound-patch.conf

Then reboot the machine and try your headphones. Next speakers! unfortunately all three mixer pins in the hda codec are set to mute and I'm working like a maniac to find a way of unmuting them, hoping that would fix the speakers. Hope this helps someone.

Went from web development to system development over this issue. Some may call that progress!

Revision history for this message

ironincoder (ironincoder) wrote on 2020-04-17:

#31

Here's the full procedure to fix the headphones.

Step 1: Do the patch above, you can skip the [model] line if you wish since I found it had no effects on anything. Please note that the subsystem id can be different for various laptops (lenovo samsung etc...) so make sure you have the correct <vendor id> <subsystem id> <codec index> for the [codec] line values. To get these three values you can use https://github.com/jeremycline/hda-analyzer which requires python2 and pygtk module to run correctly. Another way is to use `sudo alsa-info.sh` command from terminal (press n when asked to upload information) to find the values. It will create a file under tmp folder which you can open via sudo vi or nano. Inside the file is a line !!HDA-Intel Codec information under which you will find the 3 values required for early patch to work, here's mine:
...
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0298
Subsystem Id: 0x144dc169
...

PS: if you experience issues with typing in firefox/chromium then add the variable mentioned at the beginning of this post and restart.

PS2: if you are a hero, then see gannon's C patch doing this same thing in a more reliable way (custom kernel).

Revision history for this message

ironincoder (ironincoder) wrote on 2020-04-17:

#32

for got the variable for browsers fix (if it happens to you). Add `GTK_IM_MODULE=xim` to /etc/security/pam_env.conf file.

Revision history for this message

Mike Pozulp (gannon1) wrote on 2020-04-24:

#33

ironincoder and I reported a kernel bug, https://bugzilla.kernel.org/show_bug.cgi?id=207423

Revision history for this message

Terry Magnus Drever (terrymagnusdrever) wrote on 2020-05-02:

#34

Quite some investigations you did there ironincoder, don't forget to post here if you manage to get the speakers going. ;) I was actually wondering where the correct place to post and get codec issues fixed is, because this probably isn't the place? Is there a bug tracker for Alsa?

Sebastien Bacher (seb128) on 2020-05-05

affects:

alsa-driver (Ubuntu) → linux (Ubuntu)

Revision history for this message

Mike Pozulp (gannon1) wrote on 2020-06-13:

#35

Good news! A very smart Arch user by the name of ronincoder discovered a fix for the headphone jack. I worked with ronincoder to make a kernel patch [1] and our patch made it into the 5.7 kernel release! It was also applied to the 5.4 LTS kernel. I booted both 5.7.2 and 5.4.46 and the headphone jack audio is loud and clear. :)

Does it work for you? It should if you have a Samsung Notebook 9 Pro NP930SBE-K01US or NP930MBE-K04US (ronincoder's is the former, mine is the latter). You can check your laptop model by running alsa_info.sh and looking at "Board Name". The Realtek ALC298 codec in the NP930SBE-K01US and NP930MBE-K04US identifies itself with "Subsystem Id" 0x144dc169 and 0x144dc176, respectively. If snd_hda_intel sees either of these ids it implements the fix.

What about the speakers? I reported the no-sound-on-internal-speakers issue on the kernel bugzilla [2]. Linux sound maintainer Jaroslav Kysela speculates that there may be some amplifiers connected to the HDA codec which are not initialized by the BIOS, and are thus not active in Linux. He suggests dumping the codec communication for the Windows driver using QEMU. We could then parse the dump and replay the communication in Linux using Early Patching [3] or writing another kernel patch. It's been a month since Jaroslav made this suggestion and I've made some progress but I still don't have a good dump. Please join the discussion on the kernel bugzilla if you'd like to help me. ^^

[1] For reference, our patch made it into Linus' tree as commit 14425f1f521f (ALSA: hda/realtek: Add quirk for Samsung Notebook).
[2] https://bugzilla.kernel.org/show_bug.cgi?id=207423
[3] https://www.kernel.org/doc/html/v4.17/sound/hd-audio/notes.html#early-patching

Revision history for this message

PowerKiKi (adrien-crivelli) wrote on 2020-07-29:

#37

I just installed a fresh Xubuntu 20.04 (Linux 5.4.0-42-generic) on my brand new Samsung Galaxy Book Ion NT950XCJ-X716A. And of course I do experience the issues described here: very low volume on headphones and no sound on speakers.

In pavucontrol, under "Output devices", I see 3 HDMI outputs, and the last one is "Speaker + Headphones". I would have expected to see something like "Built-in Audio Analog Stereo", but it's not there. Under "Configuration", I would also expect something related to built-in, but the only profiles available are "Play HiFi quality Music" and "Off".

From reading this thread it seems that a (partial?) fix is on the way. Is there a way for me try that patch already ?

And is there anything else I can do to help fix the remaining issues ? I am not sure what log are useful and how to get them ?

Revision history for this message

jhubuntu20 (jhubuntu20) wrote on 2020-08-11:

#38

I have the same computer and issue as PowerKiKi... the new Samsung Ion running ubuntu 20.04.

I have found that I can make the headset jack work temporarily if I issue this command :

sudo hda-verb /dev/snd/hwC0D0 0x1a SET_PIN_WIDGET_CONTROL 0x5

But it only lasts until the sound subsystem goes to sleep (i.e. no sound to play or changing sound sources). Is there some way to make this last without having to constantly reissue the command?

I have found no viable way to make the speakers work. One forum I read said it might be related to the AKG Smart Amp in these new Samsung devices, but I have no way to prove or disprove that.

Revision history for this message

PowerKiKi (adrien-crivelli) wrote on 2020-08-12:

#39

I can confirm that after installing the package `alsa-tools`, then the following command will restore sound on headphones instantaneously:

sudo hda-verb /dev/snd/hwC0D0 0x1a SET_PIN_WIDGET_CONTROL 0x5

In the meantime I did try a newer kernel, linux-headers-5.7.0-050700_5.7.0-050700.202006082127, but without success. I'll give 5.8.1 a try too...

Revision history for this message

PowerKiKi (adrien-crivelli) wrote on 2020-08-12:

#40

linux-headers-5.8.1-050801_5.8.1-050801.202008111432 and booting with secure boot disabled will not anything. Still no sound, and the command workaround still works.

On a side note, the built-in mic does work as expected. So I use bluetooth headphones for listening and built-in mic for speaking.

PS: John, did you find a way to get the keyboard backlight working ? and are you running on intel or nvidia gpu (in my case nvidia gpu will always freeze the whole computer after ~10-30 minutes of desktop usage) ?

Ubuntu Foundations Team Bug Bot (crichton) on 2020-08-17

tags:

added: patch

Kai-Heng Feng (kaihengfeng) on 2020-11-05

Changed in linux (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Mike (draamses) wrote on 2020-11-11:

#113

PLease disregard my last comment (#112). It happens in FF too, but on other websites.

Revision history for this message

Mike (draamses) wrote on 2020-11-11:

#114

Re: Metallic audio

Upgraded the kernel from 5.4.0-52 to 5.4.72 as I have on Manjaro.
Result: Metallic audio.

Booted again with 5.4.0-52
Result: Clean audio

Conclusion: quite likely a kernel issue.
How can we get this reported and fixed?

Revision history for this message

Mike (draamses) wrote on 2020-11-11:

#115

Decided to do more trial and error tests.
I tried multiple amd64 kerels from https://kernel.ubuntu.com/~kernel-ppa/mainline/
It seems that all kernels I tried produce metallic audio, I believe you can easily reproduce this by trying them.
Even the 5.4.52-050452.202007160732 kernel produced metallic sound, while the official Mint 5.4.0-52 kernel produces clean audio.
Official Mint kernel 5.8.0-28 also produces clean audio.

Any thoughts?

Revision history for this message

Mike (draamses) wrote on 2020-11-11:

#116

To answer my own question - I suppose the ubuntu kernels are more optimized and have multiple fixes and drivers that the mainline/upstream kernels do not and that's why I get the metallic audio...
I wonder what was fixed in Ubuntu's kernel to make this issue go away.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-11-11:

#117

Please check if your system id is included:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/pci/hda/patch_realtek.c#n7917

Revision history for this message

Mike (draamses) wrote on 2020-11-11:

#118

Yes, it is.
For some reason linux loads snd_hda_intel instead of snd_soc_skl_hda_dsp ALSA module and this causes the metallic audio.
How can I get it to load snd_soc_skl_hda_dsp ALSA module?

Revision history for this message

jhubuntu20 (jhubuntu20) wrote on 2020-11-11:

#119

@kaihengfeng

Yes, my model is included :

SND_PCI_QUIRK(0x144d, 0xc18a, "Samsung Galaxy Book Ion (NP930XCJ-K01US)", ALC298_FIXUP_SAMSUNG_HEADPHONE_VERY_QUIET),

However, the quirk called "ALC298_FIXUP_SAMSUNG_HEADPHONE_VERY_QUIET" is just the fix for the headphone jack only. So yes, that fix is now implemented, but what about fixing the actual speakers. Now that we have a sequence of verbs that enables speaker sound, can someone add those to another quirk so sound on the speakers works out of the box too?

Revision history for this message

jhubuntu20 (jhubuntu20) wrote on 2020-11-11:

#120

@draamses

I never encountered the metallic sound on my ion, so I am probably not much help on that one. I do recall reading about it when I was researching the speaker issue, so I do agree it is a separate issue. If you google around a bit, it seems like there was a separate fix for metallic sound already identified.

Revision history for this message

Mike (draamses) wrote on 2020-11-11:

#121

@jhubuntu20

I am pretty sure this is caused by snd_hda_intel being loaded instead of snd_soc_skl_hda_dsp
When I tested ubuntu kernel, the sound was clean and they all ladded snd_soc_skl_hda_dsp, however any mainline kernel produced metallic sound and those load snd_hda_intel
I have created a tutorial for Manjaro that may help people with other distors and similar laptops. It is largely based on your efforts, so thank you for that. :)
https://forum.manjaro.org/t/guide-how-to-set-up-the-audio-card-in-samsung-galaxy-book/37090

Revision history for this message

jhubuntu20 (jhubuntu20) wrote on 2020-11-12:

#122

@draamses

I am glad to hear it works on the flex. Thanks for the kind words, but Mike Pozulp deserves most of the credit. He seems to have disappeared here, but he had the key process for how to do it. For what its worth, I don't recognize snd_soc_skl_hda_dsp (of course I am not using Manjaro). On my ion with standard ubuntu 20.04 it was never metallic. From "lspci -nnv" on my system :

00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8]
DeviceName: Onboard - Sound
Subsystem: Samsung Electronics Co Ltd Device [144d:c18a]
Flags: bus master, fast devsel, latency 32, IRQ 166
Memory at 6023118000 (64-bit, non-prefetchable) [size=16K]
Memory at 6023000000 (64-bit, non-prefetchable) [size=1M]
Capabilities: <access denied>
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_sof_pci

Revision history for this message

Mike (draamses) wrote on 2020-11-12:

#123

Yes, if you check alsa-info (here is my output: http://alsa-project.org/db/?f=608b0585907cc0f959ebc2528e771f5260685382), you will find it:
!!Loaded ALSA modules
!!-------------------

snd_soc_skl_hda_dsp

snd_soc_skl_hda_dsp ALSAA module basically loads snd_sof_pci and that's why you don't have metallic audio...
Even if you launch alsamixer and press F6 you will see sof-hda-dsp and not HDA Intel PCH that those with metallic audio see.
You can easily get metallic audio by switching to a mainline kernel instead of ubuntu's.

Revision history for this message

Mike (draamses) wrote on 2020-11-12:

#124

And to fix that metallic sound with the mainline kernel, you will probably need to perform steps 4 & 5 from my guide (https://forum.manjaro.org/t/guide-how-to-set-up-the-audio-card-in-samsung-galaxy-book/37090) and then reboot.

Revision history for this message

Mike (draamses) wrote on 2020-11-12:

#125

Oh, one last thing, to hear the mettalic audio, simply launch a youtube video in Chrome (not Firefox)

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-11-13:

#126

Kailang, do you know how to power up the AMP?

Revision history for this message

Kailiang Yang (kailang) wrote on 2020-11-19:

#127

I don't know.
This is none Realtek AMP.

Revision history for this message

Kacper Michajłow (kasper93) wrote on 2021-05-18:

#128

I will ping you guys also here, since it seems to be more popular bug report. I've send a patch for speaker amp. You can find it here https://bugzilla.kernel.org/show_bug.cgi?id=207423#c40 and test if you'd like.

Revision history for this message

Aurélien (titou829) wrote on 2021-05-22:

#129

Hi,

I have a Samsung galaxy book and encounter the same problem with my ALC298 sound card. I tried everything you did but it didn't work with mine. In fact I even cannot hear something with the earphones.
I also tried to check the verbs used under windows (throught qemu) and it seems they are quite different. Unfortunately even when i try to set these verbs it doesn't work...
I tried to send to you an email @gannon1 / @Mike pozulp but I'm not sure you received it.

If someone can help me trying to solve this problem it would be so good!
Thanks a lot

Revision history for this message

PowerKiKi (adrien-crivelli) wrote on 2021-05-22:

#130

Aurélien, first thing to do is probably `sudo alsa-info --upload` to get and upload all your details. Then, we might compare it to mine: http://alsa-project.org/db/?f=f13c46c58bba7ed21035e65230899b18419cd337

Revision history for this message

Duke Fong (duke-c) wrote on 2022-02-27:

#131

@PowerKiKi
The to912 script needs to be re-run after the audio sleeps. I have been running it manually for two years. Yesterday, I wrote a script that runs automatically after booting. It is much more convenient now. The script snippet:

LAST=0
while true; do
#pacmd list-sink-inputs | grep -w state | grep -q RUNNING && CUR=1 || CUR=0
cat /proc/asound/card0/pcm0p/sub0/status | grep -q RUNNING && CUR=1 || CUR=0

    sleep 1
    [ $LAST != $CUR ] && echo "audio state: $LAST -> $CUR @ $(date)"
    if [ $LAST == 0 ] && [ $CUR == 1 ]; then
        echo "run fix_audio ..."
        ./to912_fix_audio.sh &> /dev/null
    fi
    LAST=$CUR
done

Revision history for this message

PowerKiKi (adrien-crivelli) wrote on 2022-03-11:

#132

Thanks for the news. I've been listening to a muted mp3 for two years now :-P

I am looking forward to Ubuntu 22.04 that should bring us the patched kernel we need...

Revision history for this message

Aurélien (titou829) wrote on 2022-09-05:

#133

@PowerKiki

I'm really sorry for the delay. My computer crashed and I needed to repair it.. I just finished...
After a year I reinstalled the latest kernel but the problem seems to persist.
Here is the result of the alsa-info.sh:
http://alsa-project.org/db/?f=08a95ec89e5a0a02f38d7183cf9b2078fadff751

Do you have any clues?

Revision history for this message

Drew R. (drew-rosoff) wrote on 2022-11-08:

#134

FYI - I have the NP950XEE (GalaxyBook2 Pro w/ Intel ARC graphics), have been struggling with the same problem and trying to fix for days now. I have perfect sound in headphones, no sound on speakers. I've implemented every fix discussed here, and haven't seen one single effect. I'm running 22.04. I tried upgrading kernels to 5.17 and 6.0 also, no effect. No matter what I try, headphones work, speakers not (and no metallic sound on headphones). Can anyone give any help/guidance, I'm stuck.

Revision history for this message

PowerKiKi (adrien-crivelli) wrote on 2022-11-08:

#135

It's been a while. Since then I upgraded to Xubuntu 22.04 (not fresh install), and I am running kernel 5.15.0, which is supposed to contains my patch according to tags on https://github.com/torvalds/linux/commit/8bcea6cb2cbc1f749e574954569323dec5e2920e.

So I expect the issue to be solved, but unfortunately it is still not solved. I still use the manual script that runs a few hundreds `sudo hda-verb ...` to enable sound on my speakers.

I am afraid I cannot offer much guidance, neither to Aurélien, nor to Drew R. :-/

Revision history for this message

Drew R. (drew-rosoff) wrote on 2022-11-09:

#136

Understood. I'd be super happy however if I could just get a manual script to work at least, and then I could call it a day...anything to just get any sound. But I've had no luck with that method, it seems to have no effect. (Assuming we are talking about the TO912.sh script. I tried to go down the whole road of setting up QEMU to record my own verbs, in case they're different, but couldn't get QEMU to compile. I have a windows partition, with latest drivers, and sound works in windows.

Revision history for this message

jhubuntu20 (jhubuntu20) wrote on 2022-11-10:

#137

Hi Drew,

Since creating the TO912.sh script I have also upgraded to a GalaxyBook2 Pro (NP930XED) running 22.04 and the script was required (i.e. the latest kernels don't automatically fix issue), but the script continues to work fine for me on both headphones are speakers. Personally I would recommend upgrading from the 5.15 kernel because it doesn't work fully with the intel grpahics (im running 6.0.6-060006-generic now), but that is unrelated. Here are the full steps I did again that work for me ... I still have not figured out how to make the screen brightness control functional on the book 2 pro, but also a different story...

- placed TO912.sh script and set as 777 +x
- Create daemon for boot

sudo gedit /etc/systemd/system/ionsound.service

                Add text in file
           [Unit]
           Description=Custom Sound

           [Service]
           Type=idle
          ExecStart={enter your path to script}/TO912.sh

[Install]
WantedBy=multi-user.target

sudo chmod 664 /etc/systemd/system/ionsound.service

- Create daemon for sleep exit

sudo gedit /etc/systemd/system/ionsoundsleep.service

                Add text in file
           [Unit]
           Description=Custom Sound Sleep Fix

           [Service]
           Type=idle
          ExecStart={enter your path to script}/TO912.sh

[Install]
WantedBy=suspend.target

sudo chmod 664 /etc/systemd/system/ionsoundsleep.service

- Activate daemons

  sudo systemctl daemon-reload
  sudo systemctl enable ionsound.service
  sudo systemctl enable ionsoundsleep.service

Note, I left the names as Ion because I was too lazy to change, but nothing in here is ion specific and this does work on your model. You can change naming if you like as long as you change it everywhere...

For the kernel part, if you haven't already discovered the mainline tool for kernel mgmt then I would highly recommend trying it....

sudo add-apt-repository ppa:cappelikan/ppa -y
sudo apt install mainline -y
Launch mainline GUI and pick kernel to install

Hi Drew,

Since creating the TO912.sh script I have also upgraded to a GalaxyBook2 Pro (NP930XED) running 22.04 and the script was required (i.e. the latest kernels don't automatically fix issue), but the script continues to work fine for me on both headphones are speakers.  Personally I would recommend upgrading from the 5.15 kernel because it doesn't work fully with the intel grpahics (im running  6.0.6-060006-generic now), but that is unrelated.  Here are the full steps I did again that work for me ...  I still have not figured out how to make the screen brightness control functional on the book 2 pro, but also a different story...

- placed TO912.sh script and set as 777 +x
- Create daemon for boot
	 
		sudo gedit /etc/systemd/system/ionsound.service

Add text in file
         		[Unit]
	         	Description=Custom Sound

[Service]
         		Type=idle
	        	ExecStart={enter your path to script}/TO912.sh

[Install]
         		WantedBy=multi-user.target

sudo chmod 664 /etc/systemd/system/ionsound.service

- Create daemon for sleep exit

sudo gedit /etc/systemd/system/ionsoundsleep.service	
		
                Add text in file 
         		[Unit]
	         	Description=Custom Sound Sleep Fix

[Service]
         		Type=idle
	        	ExecStart={enter your path to script}/TO912.sh

[Install]
         		WantedBy=suspend.target

sudo chmod 664 /etc/systemd/system/ionsoundsleep.service	
	
- Activate daemons

sudo systemctl daemon-reload
		sudo systemctl enable ionsound.service	
		sudo systemctl enable ionsoundsleep.service

Note, I left the names as Ion because I was too lazy to change, but nothing in here is ion specific and this does work on your model.  You can change naming if you like as long as you change it everywhere...

For the kernel part, if you haven't already discovered the mainline tool for kernel mgmt then I would highly recommend trying it....

sudo add-apt-repository ppa:cappelikan/ppa -y
	sudo apt install mainline -y
	Launch mainline GUI and pick kernel to install

Revision history for this message

Drew R. (drew-rosoff) wrote on 2022-11-11:

#138

Hi jhubuntu20,

First, hopefully I can do you a solid and tell you how I fixed my brightness control at least (cause mine is a Galaxy Book2 Pro also, but with the ARC graphics). What worked for me was:

    -Created /etc/modprobe.d/i915.conf with
        options i915 enable_dpcd_backlight=3
    - Regenerated the initramfs:
        sudo update-initramfs -u -k all

Hope that helps, unless you already tried.

On my side, I am running kernel 6.0.0-1006-oem (which I got from the linux-oem-22.04b package, as opposed to the mainline tool, which i may try though). I tried that in hopes it would help, in addition to many other things (disabling windows fast boot on my other drive, disabling secure boot and fast bios, setting probe_mask=1, iommu=off, and others). Also tried playing with hdajackretask, because I'd be happy with retasking / giving up my working headphone jack for the speakers, but haven't figured that out.

Also, when I tried your TO912.sh script (the first thing I tried actually), I was doing it following the instructions here -- https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090
This includes also blacklisting snd-hda-intel, removing alsa-conf, plus more. Should I not be doing that? (I've tried both ways though).

The problem is I just don't have the right mental model for what's going on, so trying everything too blindly... but I'm trying to understand more. Most things have no effect (i.e., headphones work, speakers don't). However, the one tweak that has made the most effect is:

options snd-intel-dspcfg dsp_driver=##

- When I set this to "3", or leave the setting out (i.e., as it was on fresh install), alsamixer shows "sof-hda-dsp" for "Card" and "Realtek ALC298" for "Chip". When I use hdajackretask, it hangs completely when applying the retasking (and I've stopped pulseaudio, etc.), and the machine will hang on next shutdown.
- But if I set it to "1", alsamixer then shows "HDA Intel PCH" for "Card", and still "Realtek..." for chip. I can use hdajackretask without it hanging up. And when I plug in headphones, I see a new "Headset or Headphone" GUI popup. But my mic doesn't look like it's working. (Also, I need to not blacklist snd-hda-intel for this config to work, otherwise I only have "Dummy Output")

Do you happen to know which of those situations seems "more right"? I fear that there's more than one problem going on at once, and I wonder which setting (3 vs 1) I should use as I experiment with the other possibilities (your script, etc.)

Lastly, I notice if I look in alsa-info, its reporting "line_outs=1", but "speaker_outs=0" in almost all configurations, and its not binding either line_out or speaker to anything in "/devices" (though it is binding the HDMIs, headphone, and sometimes the Mic). I checked my older laptop, however, which has speaker sound, and it reports the same (though its running a 4.xx kernel and the ALC256).

I don't know if any of this gives any clues, and I apologize for my posts length and poor formatting.. I'm just trying to make sense of all this.

Hi jhubuntu20,

First, hopefully I can do you a solid and tell you how I fixed my brightness control at least (cause mine is a Galaxy Book2 Pro also, but with the ARC graphics).  What worked for me was:

-Created /etc/modprobe.d/i915.conf with
        options i915 enable_dpcd_backlight=3
    - Regenerated the initramfs:
        sudo update-initramfs -u -k all

Hope that helps, unless you already tried.

On my side, I am running kernel 6.0.0-1006-oem (which I got from the linux-oem-22.04b package, as opposed to the mainline tool, which i may try though). I tried that in hopes it would help, in addition to many other things (disabling windows fast boot on my other drive, disabling secure boot and fast bios, setting probe_mask=1, iommu=off, and others).  Also tried playing with hdajackretask, because I'd be happy with retasking / giving up my working headphone jack for the speakers, but haven't figured that out.

Also, when I tried your TO912.sh script (the first thing I tried actually), I was doing it following the instructions  here -- https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090
This includes also blacklisting snd-hda-intel, removing alsa-conf, plus more.  Should I not be doing that?  (I've tried both ways though).

The problem is I just don't have the right mental model for what's going on, so trying everything too blindly... but I'm trying to understand more.  Most things have no effect (i.e., headphones work, speakers don't).  However, the one tweak that has made the most effect is:

options snd-intel-dspcfg dsp_driver=##

- When I set this to "3", or leave the setting out (i.e., as it was on fresh install), alsamixer shows "sof-hda-dsp" for "Card" and "Realtek ALC298" for "Chip".  When I use hdajackretask, it hangs completely when applying the retasking (and I've stopped pulseaudio, etc.), and the machine will hang on next shutdown.  
    - But if I set it to "1", alsamixer then shows "HDA Intel PCH" for "Card", and still "Realtek..." for chip.  I can use hdajackretask without it hanging up.  And when I plug in headphones, I see a new "Headset or Headphone" GUI popup.  But my mic doesn't look like it's working. (Also, I need to not blacklist snd-hda-intel for this config to work, otherwise I only have "Dummy Output")

Do you happen to know which of those situations seems "more right"?  I fear that there's more than one problem going on at once, and I wonder which setting (3 vs 1) I should use as I experiment with the other possibilities (your script, etc.)

Lastly, I notice if I look in alsa-info, its reporting "line_outs=1", but "speaker_outs=0" in almost all configurations, and its not binding either line_out or speaker to anything in "/devices" (though it is binding the HDMIs, headphone, and sometimes the Mic).  I checked my older laptop, however, which has speaker sound, and it reports the same (though its running a 4.xx kernel and the ALC256).

I don't know if any of this gives any clues, and I apologize for my posts length and poor formatting.. I'm just trying to make sense of all this.

Revision history for this message

jhubuntu20 (jhubuntu20) wrote on 2022-11-11:

#139

Download full text (3.5 KiB)

Thanks, I had tried a couple of things on the brightness, but it doesn't really bother me that much and I kind of forgot about it. I will try your approach.

So full disclaimer, I am usually an Angular architect and not a linux admin so try at your own risk, etc., etc., but here are my thoughts on your post... Back when I created the original script, the Ion and ubuntu 20.04 had several sound related issues. I had found fixes for the headphone jack and a few other issues initially, and then Mike Pozulp gave me a wonderful conceptual process and some key pointers for how to use qemu to get the verbs for the speakers. The process in that blog is the old, more complicated process. Fast forward to the galaxy book 2 and ubuntu 22.04, and on this laptop I didn't have to do most of the same steps because several of the issues were fixed in the base ubuntu version. So in general I would say you shouldn't need to do any of the hda retasking or alsmixer steps on your new laptop. In fact it was so easy on this laptop I didn't even install alsamixer or the other sound tools I had installed before to work on the ion. Here is the full entirety of everything I did on a fresh 22.04 install on the book 2 pro to get to working sound... perhaps one of these steps is the key...

1) Install pavucontrol. I don't think this was actually necessary, but I wanted the tool available just in case.

sudo apt install pavucontrol

2) Install alsa-tools. This is absolutely required because it installs the hda verb utility. If you try to run the script without the verb tool then it won't work, but I would assume you would have seen the errors.

sudo apt-get install alsa-tools

3) Kill the default alsa-base. Don't substitute or replace, just make sure this file is no longer present. I recommend rename instead of delete in case you ever want to back. This is likely the step your missing. Don't substitute a new file.

Go into folder and just rename this file so it is not present

/etc/modprobe.d/alsa-base.conf

4) Place the TO912.sh script and be sure to chmod the permissions to 777 and make it executable with +x

5) Create the two daemon files, making sure you did the chmod 664 step and making sure the paths to the TO912 script are updated.

6) Activate the daemons. be sure to do the reload before enabling.

    sudo systemctl daemon-reload
    sudo systemctl enable ionsound.service
    sudo systemctl enable ionsoundsleep.service

7) Turn off suspend on idle. This should not be needed to make it run, but keeps the change working through standby mode after it starts working

sudo gedit /etc/pulse/default.pa
Add comments to ### load-module module-suspend-on-idle

8) Reboot and verify

That's it, should be every thing you need to do from a fresh 22.04 to get full sound on headphones and speakers. I never actually tried running the TO script on this unit before doing these steps, so I can't say for sure if that works before removing alsa-base, but I have had to reload this laptop 3 times for other reasons and this process worked every time.

If it helps here is my output from sudo lspci -v | grep -i audio. you should seem someth...

Affects		Status	Importance	Assigned to	Milestone
	Linux	New	Undecided	Unassigned
	linux (Ubuntu)	Fix Released	Undecided	Unassigned

information type:	Public → Public Security
information type:	Public Security → Public

Ubuntu
linux package

[950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

Bug Description

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntulinux package

[950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

Bug Description

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntu
linux package