Skip to content

[BUG] No internal speaker audio on Samsung Galaxy Book4 (960QGK) - ALC298 / Intel Meteor Lake #5974

New issue
New issue
Open
Open
[BUG] No internal speaker audio on Samsung Galaxy Book4 (960QGK) - ALC298 / Intel Meteor Lake#5974
Labels
RealtekIssue with codec/Amp from Realtek

Description

@tl-owen
tl-owen
opened on Oct 12, 2026

Environment Details

  • Hardware: Samsung Galaxy Book4 (Model 960QGK)
  • Processor / Platform: Intel Core Ultra 7 155H (Meteor Lake)
  • Audio Codec: Realtek ALC298
  • OS / Kernel: Kubuntu 26.04 LTS (Kernel 7.0.0-38-generic 64-bit)
  • Sound Server: PipeWire / WirePlumber

Issue Description

The internal speakers on the Samsung Galaxy Book4 (960QGK) produce no audio output despite PipeWire showing active stream playback routing to the ALC298 Analog playback channels.

Behavior Summary

  • wpctl status confirms active streams are mapped to ALC298 Analog:playback_FL and playback_FR.
  • PipeWire streams cycle through [init] states initially before moving to [active], but no audible sound comes out of the physical speakers.
  • Mixer levels (alsamixer / Plasma Audio volume) are unmuted and set to audible levels.

Steps Taken / Verification

  1. Confirmed audio graph stream routing in PipeWire via wpctl status.
  2. Verified mixer channels are unmuted via alsamixer.
  3. Restarted PipeWire / WirePlumber services (systemctl --user restart wireplumber pipewire-pulse).

Attached Debug Logs

Attached is audio-debug-logs.tar.gz containing:

  • wpctl-status.txt (Current PipeWire audio graph and routing status)
  • audio-journal.txt (Systemd journal logs for PipeWire, WirePlumber, and kernel snd/sof/hda messages)

audio-debug-logs.tar.gz

Activity

  1. lgirdwood commented on Oct 12, 2026

    @lgirdwood
    lgirdwood
    on Oct 12, 2026
    Member

    Adding @thesofproject/realtek

  2. abonislawski
    transferred this issue fromthesofproject/sofon Oct 13, 2026

  3. bardliao commented on Oct 13, 2026

    @bardliao
    bardliao
    on Oct 13, 2026
    Collaborator

    @KailangYang FYI

  4. tl-owen commented on Oct 22, 2026

    @tl-owen
    tl-owen
    on Oct 22, 2026
    Author

    Environment Details

    • Hardware: Samsung Galaxy Book4 (Model 960QGK)
    • Processor / Platform: Intel Core Ultra 7 155H (Meteor Lake)
    • Audio Codec: Realtek ALC298 (Subsystem ID: 0x144dc892)
    • OS / Kernel: Kubuntu 26.04 LTS (Kernel 7.0.0-38-generic 64-bit)
    • Sound Server: PipeWire / WirePlumber

    Issue Description

    The internal speakers on the Samsung Galaxy Book4 produce no audio output despite PipeWire showing active stream routing to the ALC298 Analog playback channels (Node 0x17).

    Codec & GPIO Diagnostic Findings

    Inspecting the ALSA codec dump (/proc/asound/card0/codec#0) reveals that while the internal speaker pin (Node 0x17) is recognized and unmuted, all 8 GPIO pins are completely disabled (enable=0, dir=0):

    GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
  IO[0]: enable=0, dir=0, ... data=0
  IO[1]: enable=0, dir=0, ... data=0
  ... (IO[2] through IO[7] disabled)

This strongly indicates that the Linux kernel is missing a vendor-specific quirk for this Samsung subsystem ID (0x144dc892) to toggle the correct GPIO pin required to power on the physical amplifier.
Steps Taken / Verification

    Confirmed audio graph stream routing in PipeWire (wpctl status shows active sink routing to Built-in Audio Analog Stereo).

    Verified mixer channels and volume levels are unmuted via alsamixer.

    Checked system logs and extracted raw codec state (codec-dump.txt).

[codec-dump.txt](https://github.com/user-attachments/files/33846845/codec-dump.txt)
  5. bardliao
    added
    RealtekIssue with codec/Amp from Realtek
    on Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    RealtekIssue with codec/Amp from Realtek

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions