Internal speakers are completely silent on the Samsung Galaxy Book5 Pro 14" (Update: Found MAX98390 on I2C)

[Norrox]

Internal speakers are silent. Headphones and HDMI work perfectly. After dumping the DSDT, I confirmed this laptop uses a Quad-Maxim MAX98390 topology on I2C, not Cirrus Logic as initially suspected.

Hardware

• Model: Samsung Galaxy Book5 Pro 14" (NP940XHA)
  

• CPU: Intel Core Ultra 200V series (Lunar Lake-M)
  

• Audio Codec: Realtek ALC1308 (ACPI ID: 10EC1308)
  

• Amplifiers: 4 × Maxim MAX98390 (Smart Amp)
  

• Amp Connection: I2C Bus 2
  

• Kernel tested: 6.12.x – 6.17.x (Arch/CachyOS)
  

Symptoms

• snd-soc-max98390 does not load automatically.
  

• System falls back to generic HDA (sof-hda-generic), detecting the codec but failing to drive the amps.
  

• Speaker pin (Node 0x17) is detected, but no audio output.
  

Key Evidence (ACPI/DSDT) The amplifiers are defined in the DSDT under _SB.PC00.I2C2. The device ID is explicitly MAX98390 and it reserves four I2C addresses (indicating a 4-speaker setup).

Scope (_SB.PC00.I2C2)
{
    Device (MX98)
    {
        Name (_HID, "MAX98390")  // Hardware ID
        Name (_UID, One)
        Name (RBUF, ResourceTemplate ()
        {
            // Four I2C addresses reserved for Quad-Speaker setup
            I2cSerialBusV2 (0x0038, ControllerInitiated, ... "\\_SB.PC00.I2C2", ...)
            I2cSerialBusV2 (0x0039, ControllerInitiated, ... "\\_SB.PC00.I2C2", ...)
            I2cSerialBusV2 (0x003C, ControllerInitiated, ... "\\_SB.PC00.I2C2", ...)
            I2cSerialBusV2 (0x003D, ControllerInitiated, ... "\\_SB.PC00.I2C2", ...)
        })
    }
}

Root Cause The Intel sound machine driver for Lunar Lake appears to lack a match table entry for this specific topology (LNL CPU + Maxim 98390 on I2C). As a result, the kernel does not instantiate the amplifier driver.

Requested Fix Please add support for the Samsung Galaxy Book5 Pro 14" (LNL + MAX98390) to the relevant machine driver (likely sound/soc/intel/boards or sound/soc/intel/common).

acpi.txt
dsdt.txt

[stuhenderson]

This report is a little confusing.
CS35L41_HDA_DEV doesn't appear to ever have been defined in the kernel, nor HID_SST.
There's also no explanation as to why we think the CS35L41 part is in this laptop.

Can you explain where the requested fix came from (did you test it?) and why you think the CS35L41 is in this SKU?

[rfvirgil]

Please install acpica-tools package and get a dump of your ACPI with:

sudo acpidump >acpi.dump

then attach that dump to this ticket.

[Norrox]

This report is a little confusing. CS35L41_HDA_DEV doesn't appear to ever have been defined in the kernel, nor HID_SST. There's also no explanation as to why we think the CS35L41 part is in this laptop.

Can you explain where the requested fix came from (did you test it?) and why you think the CS35L41 is in this SKU?

Apologies for the confusion in the original report. You are correct—the code I posted was illustrative pseudo-code, and my assumption about the CS35L41 was wrong.

I have performed a full DSDT dump to verify the actual hardware. This laptop uses a Quad-Maxim 98390 configuration on I2C, not Cirrus Logic.

Correct Hardware Topology:

CPU: Lunar Lake (LNL)

Amplifiers: Maxim MAX98390 (_HID: "MAX98390")

Bus: I2C Bus 2 (Scope _SB.PC00.I2C2)

Addresses: 0x38, 0x39, 0x3C, 0x3D (4-speaker setup)

Codec: Realtek ALC1308 (_HID: "10EC1308")

Evidence from DSDT:

Scope (_SB.PC00.I2C2)
{
    Device (MX98)
    {
        Name (_HID, "MAX98390")
        Name (_UID, One)
        Name (RBUF, ResourceTemplate ()
        {
            I2cSerialBusV2 (0x0038, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.PC00.I2C2", ...)
            I2cSerialBusV2 (0x0039, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.PC00.I2C2", ...)
            I2cSerialBusV2 (0x003C, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.PC00.I2C2", ...)
            I2cSerialBusV2 (0x003D, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.PC00.I2C2", ...)
        })
    }
}

Currently, lsmod shows snd-soc-max98390 is not loaded. The system falls back to sof-hda-dsp (Generic HDA), likely because the machine driver lacks a match table entry for the LNL + MAX98390 combination.

[Andycodeman]

For anyone looking for an easy way to apply these fixes — I've packaged tested, automated install scripts for both the speaker and webcam issues on Samsung Galaxy Book4 (and others) laptops:

https://github.com/Andycodeman/samsung-galaxy-book4-linux-fixes

Speaker fix: DKMS driver for the MAX98390 I2C amplifiers (based on thesofproject/linux PR #5616). Auto-rebuilds on kernel updates and auto-removes itself when native kernel support lands.

curl -sL https://github.com/Andycodeman/samsung-galaxy-book4-linux-fixes/archive/refs/heads/main.tar.gz | tar xz && cd samsung-galaxy-book4-linux-fixes-main/speaker-fix && sudo ./install.sh && sudo reboot

Webcam fix: Handles IVSC module loading, Intel IPU6 camera HAL setup, v4l2loopback relay, and PipeWire device classification. Works with Firefox, Chrome, Zoom, Teams, OBS, mpv, and more.

curl -sL https://github.com/Andycodeman/samsung-galaxy-book4-linux-fixes/archive/refs/heads/main.tar.gz | tar xz && cd samsung-galaxy-book4-linux-fixes-main/webcam-fix && ./install.sh && sudo reboot

Tested on: Samsung Galaxy Book4 Ultra, Ubuntu 24.04 LTS, kernel 6.17 (HWE). The upstream speaker PR (#5616) has also been confirmed working on the Book4 Pro, Pro 360, and Pro 16-inch by other users. If you're on a Galaxy Book5 or a different distro (Fedora, Arch, Manjaro, Debian, etc.), the fixes may still work since the underlying hardware (ALC298 + MAX98390 amps, IPU6 + OV02C10 sensor) is shared across models — but only the Ultra on Ubuntu has been directly verified. Reports from other configurations are welcome.

Note: The built-in microphones (DMIC) do not work yet on any of these models — that requires SOF driver support which is expected in kernel 7.0 (April 2026) or 7.1 (June 2026). See the repo README for details and workarounds.