Fix: Samsung Galaxy Book2 Pro Silent Speaker (SOF IPC4)

by Alex Johnson 56 views

Having trouble with the internal speakers on your Samsung Galaxy Book2 Pro Special Edition (950XGK)? You're not alone! This article dives deep into a specific issue where the built-in speakers remain silent while using the SOF (Sound Open Firmware) driver, even though headphones, HDMI audio, and Bluetooth work perfectly. Let's explore the problem, the hardware and software involved, the symptoms, troubleshooting steps, and potential solutions. This comprehensive guide is designed to help you diagnose and hopefully resolve this frustrating audio issue.

Understanding the Silent Speaker Issue

The main issue we're tackling here is the complete silence from the internal speakers on a Samsung Galaxy Book2 Pro Special Edition (950XGK) when using the SOF audio driver. This means that despite the system recognizing the speakers and allowing them to be selected as the default output, no sound is produced. This can be particularly frustrating as other audio outputs like headphones, HDMI connections, and Bluetooth devices function as expected. The problem seems to be isolated to the internal speakers when the SOF driver is in use. This issue has been observed on systems running Linux distributions, specifically those utilizing PipeWire and WirePlumber for audio management. The SOF driver is an open-source audio driver framework designed to provide modern audio support for Intel platforms, but in certain configurations, it can encounter compatibility issues that lead to the silent speaker problem. Identifying the root cause involves examining hardware configurations, software settings, and driver interactions to pinpoint the source of the audio failure. Understanding the problem is the first step toward finding a solution, and this article will guide you through the process.

Hardware and Software Configuration

To effectively troubleshoot this issue, it's crucial to understand the specific hardware and software components involved. Let's break down the key elements of the system:

Hardware Details

  • Laptop: Samsung Galaxy Book2 Pro Special Edition 950XGK
    • DMI: SAMSUNG ELECTRONICS CO., LTD. / 950XGK (This provides information about the system manufacturer and model)
  • Audio Controller: Intel Meteor Lake-P HD Audio Controller
    • 8086:7e28 (This is the PCI vendor and device ID, uniquely identifying the audio controller)
    • Subsystem: 144d:c896 (This identifies the specific subsystem, in this case, related to Samsung)
    • Driver: sof-audio-pci-intel-mtl (This confirms that the SOF driver is being used)
  • Codec: Realtek ALC298 (10ec:0298)
    • Subsystem: 144d:c896 (Again, indicating a Samsung-specific configuration)

Software Details

  • Distro: EndeavourOS (Arch-based) (This indicates the Linux distribution being used)
  • Kernel: 6.17.8-arch1-1 (The specific version of the Linux kernel)
  • Audio Stack: PipeWire + WirePlumber (These are modern audio server and session manager components)
  • SOF Bits (from dmesg):
    • Firmware: intel/sof-ipc4/mtl/sof-mtl.ri (The firmware file being used by the SOF driver)
    • Topology: intel/sof-ace-tplg/sof-hda-generic-2ch.tplg (The topology file defines the audio routing and connections)
    • Machine driver: skl_hda_dsp_generic (The specific machine driver used for this hardware configuration)

Knowing these details helps narrow down potential causes. The SOF driver, combined with the Realtek ALC298 codec on this Samsung laptop, seems to be the focal point of the issue. Furthermore, the interaction between the kernel, PipeWire, and SOF components needs careful consideration. Understanding these hardware and software components is vital for diagnosing the root cause of the silent speaker problem on the Samsung Galaxy Book2 Pro. Pinpointing the exact versions and configurations will aid in identifying potential driver conflicts, firmware bugs, or configuration errors.

Symptoms of the Silent Speaker Issue

Identifying the symptoms is crucial for a precise diagnosis. Here’s a breakdown of what users typically experience when this issue occurs:

  • ALSA Recognition: The Advanced Linux Sound Architecture (ALSA) correctly detects the HDA (High Definition Audio) card and associated devices. This means the system recognizes the hardware.
    • card 0: sof-hda-dsp - sof-hda-dsp (This indicates the SOF driver is managing the audio card)
    • Playback devices: HDA Analog (0), HDMI1 (3), HDMI2 (4), HDMI3 (5), Deepbuffer HDA Analog (31) (These are the available output devices)
    • Capture devices: HDA Analog (0), DMIC Raw (6) (These are the available input devices)
  • PipeWire Integration: PipeWire, the audio server, exposes a ...HiFi__Speaker__sink which can be selected as the default audio output. This shows that PipeWire sees the internal speakers as a valid output option.
  • No Sound from Internal Speakers: Despite being recognized and selectable, no sound is produced from the built-in speakers. This is the core symptom of the problem.
  • Successful ALSA Test (No Audio Output): Running a direct ALSA test, such as speaker-test on hw:0,0 (the analog device), completes successfully without errors, but no sound is audible from the internal speakers. This suggests the issue isn't a complete hardware failure or a basic ALSA misconfiguration.
  • Functional Alternative Audio Outputs: Headphone jack, HDMI audio, and Bluetooth audio all function correctly using the same kernel and audio stack. This highlights that the issue is specific to the internal speakers when using the SOF driver.
  • Mixer State: Mixer settings such as Master, Speaker, Pre Mixer Analog, and Post Mixer Analog are all set to 100% volume and are unmuted. Additionally, Auto-Mute Mode is disabled. This eliminates simple volume or mute settings as the cause.
  • Headphone Volume Irrelevant: Headphone volume is also unmuted during testing, but only the headphones produce sound, reinforcing the specificity of the issue to the internal speakers.

These symptoms collectively paint a clear picture: the system recognizes the internal speakers, software pathways are seemingly correct, yet no sound emerges. This points towards a more nuanced problem, potentially within the SOF driver, the codec configuration, or the interaction between them. By recognizing these symptoms, users can confidently narrow the scope of troubleshooting and focus on the relevant areas.

Troubleshooting Steps Taken

Several troubleshooting steps have been attempted to resolve the silent speaker issue. These steps cover a range of potential causes, from basic volume settings to more complex driver configurations. Here’s a summary of the actions taken:

  • Verified Volume and Mute State with amixer: The amixer command-line tool was used to check the volume and mute status of various audio controls, including:
    • Master
    • Speaker
    • Headphone
    • Pre Mixer Analog
    • Post Mixer Analog
    • Loopback Mixing This step ensures that none of the basic volume or mute settings are inadvertently causing the silence.
  • Tested Through PipeWire and Directly with ALSA: Audio output was tested both through the PipeWire audio server and directly using ALSA (with the speaker-test command on hw:0,0). This helps determine if the issue lies within PipeWire or if it's a lower-level problem with ALSA or the driver itself.
  • Tried necessary-verbs.sh Workaround (Issue #4055): A workaround suggested for a similar issue (found in GitHub issue #4055) was attempted. This involves using a script called necessary-verbs.sh and setting a specific hda_model option.
    • Specifically, the following option was added to /etc/modprobe.d/: options snd-sof-intel-hda-common hda_model=alc298-samsung-amp-v2-2-amps
    • This workaround aims to apply specific codec verbs (commands) that might be necessary for the audio chip to function correctly. However, in this case, it did not restore internal speaker output.

The fact that these steps didn't resolve the issue is significant. It suggests that the problem isn't a simple configuration error or a widely known bug with a readily available fix. It likely points towards a more specific compatibility issue between the SOF driver, the Realtek ALC298 codec, and the Samsung Galaxy Book2 Pro's specific hardware configuration. Further investigation is needed, potentially involving deeper analysis of the codec configuration, driver interactions, and firmware settings. The failure of these common troubleshooting steps highlights the complexity of the issue and the need for a more targeted approach.

Analyzing Logs and Dumps

To further diagnose the issue, various logs and system dumps were collected and analyzed. These files provide valuable insights into the system's audio configuration and potential error messages. Here's a summary of the key files and their significance:

  • codec0-alc298.txt: This file contains the output of /proc/asound/card0/codec#0, which provides detailed information about the Realtek ALC298 codec. Analyzing this output can reveal how the codec is configured, its supported features, and any potential issues in its initialization or operation. Examining register settings and pin configurations can help identify if the internal speakers are properly connected and enabled.
  • amixer-scontrols.txt and amixer-scontents.txt: These files contain the output of amixer scontrols and amixer scontents, respectively. They show the available mixer controls and their current settings. This is crucial for verifying that volume levels are correct, mute settings are disabled, and that the appropriate input and output devices are selected. Analyzing these outputs ensures that no software-level volume or mute settings are inadvertently silencing the internal speakers.
  • aplay-l.txt and arecord-l.txt: These files contain the output of aplay -l and arecord -l, respectively. They list the available ALSA playback and recording devices. This information confirms that ALSA recognizes the audio card and its associated devices, including the internal speakers. These outputs help verify that the system sees the internal speakers as a valid output option.
  • asound-cards.txt: This file contains the output of /proc/asound/cards and lists the detected sound cards in the system. It confirms the presence of the SOF-based audio card and its assigned card number. This ensures that the SOF driver is correctly loaded and managing the audio hardware.
  • dmi-sys_vendor.txt and dmi-product_name.txt: These files contain the output of commands that retrieve the system vendor and product name from the DMI (Desktop Management Interface). This information confirms the specific laptop model (Samsung Galaxy Book2 Pro 950XGK) and helps identify any model-specific quirks or known issues. Knowing the exact hardware model is crucial for finding relevant information and potential solutions.

By meticulously analyzing these logs and dumps, it's possible to gain a deeper understanding of the audio subsystem's state and identify potential discrepancies or errors. The codec information, mixer settings, and device listings provide a comprehensive view of the audio configuration. This detailed analysis is essential for pinpointing the root cause of the silent speaker issue and developing an effective solution.

Further Investigation and Potential Solutions

Based on the troubleshooting steps and log analysis, several areas warrant further investigation. Here are potential solutions to explore:

  1. SOF Firmware and Topology:

    • Verify the latest SOF firmware is installed. Outdated firmware can sometimes cause compatibility issues. Check the SOF project's website or your distribution's repositories for updates.
    • Experiment with different topology files. The sof-hda-generic-2ch.tplg topology might not be the optimal configuration for the Samsung Galaxy Book2 Pro. Investigate if a more specific topology file exists for this model or the Realtek ALC298 codec.

  2. Codec Verb Configuration:

    • Delve deeper into the codec verb configuration. The necessary-verbs.sh workaround attempted to address this, but it might not have been sufficient. Use tools like hdajackretask or manually send codec verbs using hda_codec_verb to experiment with different pin configurations and settings. This requires a thorough understanding of the ALC298 codec's specifications.

  3. Kernel Driver Options:

    • Explore additional kernel module options for snd-sof-intel-hda-common. There might be other hda_model options or other parameters that could influence the driver's behavior. Consult the driver's documentation and community forums for insights.

  4. PipeWire and WirePlumber Configuration:

    • Examine the PipeWire and WirePlumber configurations. While the symptoms suggest a lower-level issue, it's still worth verifying that these components are correctly configured to handle the internal speakers. Check the PipeWire and WirePlumber logs for any error messages or warnings.

  5. BIOS/UEFI Settings:

    • Check the laptop's BIOS/UEFI settings for any audio-related options. Some laptops have settings that can disable or alter the behavior of the internal speakers. Ensure that the internal speakers are enabled in the BIOS.

  6. Community and Bug Reports:

    • Search online forums, bug trackers (like the SOF project's GitHub issues), and distribution-specific resources for similar issues. Other users might have encountered the same problem and found a solution or workaround.

  7. Contact Support:

    • If all else fails, consider contacting Samsung support or the SOF project's community for assistance. They might have specific knowledge about the hardware or driver that could help resolve the issue.

Solving this silent speaker problem likely requires a combination of technical expertise, patience, and community collaboration. Thoroughly exploring the above solutions will increase the chances of restoring audio output to the internal speakers on the Samsung Galaxy Book2 Pro.

Conclusion

Troubleshooting silent internal speakers on a laptop, especially when using modern audio drivers like SOF, can be a complex task. This article has provided a comprehensive guide to diagnosing and potentially resolving this issue on a Samsung Galaxy Book2 Pro (950XGK). By understanding the hardware and software involved, analyzing symptoms, reviewing troubleshooting steps, and exploring potential solutions, you're well-equipped to tackle this problem. Remember to meticulously examine logs, experiment with configurations, and leverage community resources for support. Addressing this issue often requires a deep dive into the intricacies of audio drivers, codec configurations, and system-level settings. This guide has armed you with the knowledge and steps to embark on that journey. We hope that by following these steps, you'll be able to restore sound to your internal speakers and fully enjoy your Samsung Galaxy Book2 Pro. For more information on sound open firmware you can check the Sound Open Firmware Wiki.