No sound on Galaxy Book5 Pro 360

[manatails]

Recently bought this laptop and I am pleasantly surprised to find out that the Linux experience is much better than I expected to be. Thank you for your hard work on the drivers and the guides.

The only thing I am concerned about is the lack of onboard sound, and unfortunately the verb scripts didn't work on this model.

After looking into it further, I discovered that this model has a speaker amp MAX98390 from Maxim on Intel I2C bus. On Windows Device Manager it is registered as 'ADI Amp Device'.

The chip is already seemingly supported by the Linux kernel, but it does not work out of the box as on these laptops it appears as an ACPI device with ID 'MAX98390', but the existing driver only recognizes the ID 'MX98390'.

#ifdef CONFIG_ACPI
static const struct acpi_device_id max98390_acpi_match[] = {
	{ "MX98390", 0 }, // Change this to 'MAX98390'
	{},
};
MODULE_DEVICE_TABLE(acpi, max98390_acpi_match);
#endif

I updated the ACPI ID from sound/soc/codecs/max98390.c and recompiled the module, now it comes up on dmesg.

[ 4.525926] max98390 i2c-MAX98390:00: no optional property 'temperature_calib' found, default:
[ 4.525927] max98390 i2c-MAX98390:00: no optional property 'r0_calib' found, default:
[ 4.525928] max98390 i2c-MAX98390:00: max98390_i2c_probe: r0_calib: 0x0,temperature_calib: 0x0
[ 4.526182] max98390 i2c-MAX98390:00: MAX98390 revisionID: 0x42

Still, it seems that I need a topology file to activate the amp. But I lack expertise on those areas.
The audio codec on this model is ALC298 I believe, I would appreciate any guidance on enabling speaker output on this laptop.

[joshuagrisham]

Hi @manatails unfortunately I am not at all familiar with how this model differs from previous models. One thing from your message I am wondering, though: did you try any of the verb scripts AFTER you changed and installed the codec driver?

Otherwise have you tried to reach out to the module author to see if he has any insight?

But even without changing anything it sort of looks to me like soc-acpi-intel-ssp-common should actually pick this device up anyway? (see https://github.com/torvalds/linux/blob/e271ed52b344ac02d4581286961d0c40acc54c03/sound/soc/intel/common/soc-acpi-intel-ssp-common.c#L56) If you enable dyndbg for this module do you see the message like amp MAX98390 found printed in your kernel log (https://github.com/torvalds/linux/blob/e271ed52b344ac02d4581286961d0c40acc54c03/sound/soc/intel/common/soc-acpi-intel-ssp-common.c#L104)?

(for example you can add something like soc_acpi_intel_ssp_common.dyndbg=+p to your kernel boot parameters I think.. or however else you want to enable debug for this module of course!)

[melvyn2]

With this patch:

diff --git a/sound/soc/codecs/max98390.c b/sound/soc/codecs/max98390.c
index 76296176f948..beba1d66dc0a 100644
--- a/sound/soc/codecs/max98390.c
+++ b/sound/soc/codecs/max98390.c
@@ -1118,6 +1118,7 @@ MODULE_DEVICE_TABLE(of, max98390_of_match);
 #ifdef CONFIG_ACPI
 static const struct acpi_device_id max98390_acpi_match[] = {
 	{ "MX98390", 0 },
+	{ "MAX98390", 0 },
 	{},
 };
 MODULE_DEVICE_TABLE(acpi, max98390_acpi_match);

I get that the amp is found by its dedicated driver:

[    4.467579] max98390 i2c-MAX98390:00: no optional property 'temperature_calib' found, default:
[    4.467582] max98390 i2c-MAX98390:00: no optional property 'r0_calib' found, default:
[    4.467583] max98390 i2c-MAX98390:00: max98390_i2c_probe: r0_calib: 0x0,temperature_calib: 0x0
[    4.467829] max98390 i2c-MAX98390:00: MAX98390 revisionID: 0x42

But then the snd_soc_acpi_intel_match module doesn't pick up the amp:

> dmesg | grep '\bamp\b'
>

Even though dynamic debugging is clearly enabled for it with snd_soc_acpi_intel_match.dyndbg=+p:

> grep snd_soc_acpi_intel_match /proc/dynamic_debug/control
sound/soc/intel/common/soc-acpi-intel-ssp-common.c:87 [snd_soc_acpi_intel_match]snd_soc_acpi_intel_detect_codec_type =p "codec %s found\n"
sound/soc/intel/common/soc-acpi-intel-ssp-common.c:104 [snd_soc_acpi_intel_match]snd_soc_acpi_intel_detect_amp_type =p "amp %s found\n"

[manatails]

I am also getting the same results as @melvyn2, and unfortunately the verb scripts didn't work with the driver enabled either.

[topzyray]

I had similar issue. After several trials, testing and failure, I decided to created this issue with all the details about my device earlier today accessible via #80. Thanks to @joshuagrisham and drlucan of Manjaro Community Forum. I was able to get my Galaxy Book Ion 950XDA sound working perfectly today. After 4 days of frantic research, trials, failures, I was able to fix it. I decided to create a script to automate the fix using Bash and made it open source. @manatails you can checkout and review the script https://github.com/topzyray/galaxybook-linux-setup. I hope it works for you. Thank you.

Note: I use this hda-verb and modified the systemd so that it can persistence after reboot or suspend.

[CReimer]

Does not work on my Galaxy Book 5 Pro 360 (960QHA/NP960QHA-KG4DE)

[tope-taiwo]

Hi @CReimer . Sorry to hear that. Mine Galaxy Book 2 is perfectly running since the fix. Since you are still experiencing this issue, there are addtional checks to ensure things are right.

Can you confirm the following:

1. What is your Ubuntu and kernel version?
2. What specifically is not working? Internal speakers, microphone, or both?
3. Is sound available via headphones (I meant wired-headphone)?
4. Have you tried connected your device to a bluetooth device to see if you get sound?
5. Can you check if your device default sound card and verify if the sound channels are not muted using alsamixer?

Also, can you share the output of the following in a .md file?
1. sudo dmesg | grep -i 'sof\|snd\|audio' - this helps to show kernel messages related to sound open firmware, audio or the likes
2. lspci | grep -i audio - this will list your audio devices
3. ps -e | grep -E 'pipewire|pulseaudio' - to check if your sound system is active and confirm if your Ubuntu version uses pipewire or pulseaudio

These can help debug further. Thank you.

[CReimer]

1. Not Ubuntu. Archlinux. Kernel version is 6.15.8
2. Internal speaker show up, but do not work. Microphone works
3. Headphones work, too
4. I have not, but since headphones work this should work, too. I'm sure that bluetooth is working
5. Checked. Not muted

dmesg.md

lspci.md

ps.md

I'm happy to help. I'm currently on vacation, but I'll keep checking back on this issue.

[kimusan]

I am seeing similar results with the galaxy book5 pro 14" running Ubuntu 24.04 and kernel 6.16.0:

dmesg.txt

lspci.txt

ps.txt

When I go into alsamixer it always shows pipewire as card and chip. I can select the sof-hda-dsp card via the F6 menu and nothing seems to be muted besides spdif

[topzyray]

Since both devices for @CReimer and @kimusan have similar information, that means success at one should be success to the other.

[kimusan]

True, i guess we just need to figure out how to turn on the amps.

[topzyray]

I had similar issue like this. You may want to test with different hda-verb. Just update the one in the script before running it again. You can keep any audio playing, and also cross-check if your device is muted. I could remeber I used different hda-verb that didn't work. The link to the last hda-verb I found to work for my actual device is the one I referenced in the script.

In case you want to manually test, you can consider this resource that gave me more guidance in fixing mine: https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090.

Saifee also used similar approach if you look closely. This was the same approach that worked for me. That's will why I packaged and documented my process in my script.

[CReimer]

I tried to get qemu running with Windows 10 but failed. After some research I found out that I can just dual boot into my Windows 11 and run RtHDDump. Here are two dumps.

RtHDDump_2025-08-31_21-42-03-177.txt
RtHDDump_2025-08-31_21-42-36-753.txt

I also did two dumps in Linux to compare.

lin_codec-dump.txt
lin_codec-dump2.txt

I only found two differences which lead me to this script

hda-verb /dev/snd/hwC0D0 0x20 0x500 0x10
hda-verb /dev/snd/hwC0D0 0x20 0x400 0x0E21
hda-verb /dev/snd/hwC0D0 0x20 0x500 0x67
hda-verb /dev/snd/hwC0D0 0x20 0x400 0x1111

AND... Nothing. Still no sound in Linux

BTW: Most information I used is from here: https://asus-linux.org/blog/sound-2021-01-11/

[CReimer]

@joshuagrisham Do these dumps show you anything that I might have missed?

[GokuWorks]

Adding this here in case someone finds a way to make a temp patch out of it: thesofproject/linux#5616

[kimusan]

Adding this here in case someone finds a way to make a temp patch out of it: thesofproject/linux#5616

This is great work. Seems to fix it for both book4 and book5 series. Would love to see this go into the upstream kernel