The integrated audio controller on Intel Raptor Lake processors often fails to initialize during fresh Linux installations due to missing firmware or kernel module mismatches. This guide resolves the "No Sound Cards Found" error on ThinkPad L14 systems by updating the kernel, installing required firmware packages, and configuring ALSA settings to ensure proper hardware detection and output functionality.
Verifying Hardware Detection
Before modifying system configurations, it is essential to confirm whether the operating system recognizes the underlying hardware at all. The most common symptom of this issue is that
pactl list short sinks returns no output, or the sound settings GUI shows no available devices. You should first check if the PCI bus sees the audio device using the
lspci command filtered for multimedia controllers.
lspci | grep -i audio
If this command returns nothing, the kernel might not be loading the correct driver for the Intel High Definition Audio (HDA) interface found in Raptor Lake chips. In many cases, the device appears as an Intel Corporation Audio Controller but remains unassigned because the necessary kernel modules are either blacklisted or outdated. If you see the device listed here, proceed to verify which kernel version is currently active. Newer kernels include better support for recent Intel architectures, so running a very old kernel on a new CPU can lead to silent failures.
uname -r
For Raptor Lake specifically, kernels older than version 6.1 often lack complete support for the updated audio codecs. Ensure your system is fully updated before proceeding with software fixes. On Arch Linux, this involves syncing the package database and upgrading all installed packages.
sudo pacman -Syu
After the upgrade, reboot your system to load the latest kernel headers and drivers. This step alone resolves the majority of initialization issues where the hardware is present but the software stack cannot communicate with it effectively.
Installing Required Firmware
Intel audio controllers frequently rely on proprietary or semi-proprietary firmware blobs to function correctly. Without these files, the kernel module may load but fail to bind to the hardware, resulting in a missing sound card. The primary package responsible for providing this firmware on Arch-based distributions is
linux-firmware. Even if you have recently updated your system, manual reinstallation can sometimes fix corrupted or incomplete downloads.
sudo pacman -S linux-firmware
In some specific ThinkPad configurations, additional microcode updates are required to stabilize the chipset communication. While this primarily affects stability, it can indirectly resolve peripheral initialization issues including audio. Install the Intel microcode package if you are using an Intel processor.
sudo pacman -S intel-ucode
Once the firmware is in place, you must ensure that the userland tools for managing sound are also up to date. The PulseAudio and PipeWire stacks handle the actual audio routing. If you are using PulseAudio, ensure
pulseaudio and
alsa-utils are installed. For newer setups using PipeWire, install
pipewire-pulse and
pipewire-alsa.
sudo pacman -S alsa-utils pulseaudio pulseaudio-alsa
After installation, restart the audio service to apply any new firmware bindings. If you use systemd, restarting the PulseAudio user instance is often sufficient, though a full system reboot guarantees that all kernel modules reload with the new firmware context.
Configuring ALSA and Kernel Modules
Sometimes the kernel module loads but does not automatically activate the sound card interface. You can manually probe the ALSA sound card configuration to force the system to recognize the device. Use the
alsamixer utility to inspect the current state of the audio channels. Launch it from the terminal and look for any muted channels indicated by "MM" at the bottom of the bars.
alsamixer
Navigate through the cards using F6 if multiple devices are detected. Ensure that the master volume and PCM outputs are unmuted and set to reasonable levels. If
alsamixer lists no cards, the issue lies deeper in the kernel module loading sequence. You may need to explicitly load the HDA Intel module. Identify the correct module name, typically
snd_hda_intel, and load it temporarily.
sudo modprobe snd_hda_intel
If this command succeeds without errors, test the sound again. To make this persistent across reboots, add the module to your
/etc/modules-load.d/ directory or ensure it is not being blacklisted in
/etc/modprobe.d/. Check for any existing blacklist files that might contain
snd_hda_intel and remove them if found.
Testing Audio Output
With the driver loaded and firmware installed, generate a test tone to verify functionality. The
speaker-test utility is part of
alsa-utils and provides a reliable way to check channel output. Run the following command to send white noise to the default stereo output.
speaker-test -c 2 -t wav
You should hear a voice announcing "front left" and "front right" alternating. If you hear this, the kernel and ALSA layers are working correctly. If you still get no sound, check the default sink in PulseAudio or PipeWire. Use
pactl list short sinks to ensure a valid sink is marked as running. If the sink exists but produces no audio, check the application-specific volume controls within your desktop environment's sound settings.
Frequently Asked Questions
Why does my sound work after a reboot but fail after suspend?
This usually indicates a power management conflict with the audio codec. The kernel may fail to restore the hardware state correctly after waking from sleep. Adding the parameter
power_save=0 to the
snd_hda_intel module options in your modprobe configuration can disable aggressive power saving and prevent this resume failure.
Can I use HDMI audio instead of the built-in speakers?
Yes, if your ThinkPad is connected to an external monitor via HDMI or DisplayPort, the audio signal is often routed through that connection. Ensure that the external display supports audio passthrough. Select the HDMI output device in your sound settings GUI or via
pavucontrol when you want to route audio to the monitor speakers.
What should I do if alsamixer shows only dummy output?
Dummy output means the kernel has no driver loaded for the hardware. This confirms that the
snd_hda_intel module is either not loading or failing to detect the PCI ID. Verify that your kernel version is compatible with your Raptor Lake CPU and reinstall the
linux-firmware package to ensure no critical binary files are missing.
Does disabling Secure Boot affect audio drivers?
Disabling Secure Boot is generally not required for standard audio drivers, as they are included in the mainline kernel. However, if you are using custom unsigned modules or third-party DKMS packages, Secure Boot might block their loading. For stock Intel audio, keeping Secure Boot enabled is safe and recommended for system integrity.
How do I switch between PulseAudio and PipeWire?
You can switch by installing the desired stack and enabling its systemd services. To move to PipeWire, install
pipewire,
pipewire-pulse, and
wireplumber, then disable the PulseAudio service. The system will automatically use PipeWire as the drop-in replacement for PulseAudio, offering lower latency and better Bluetooth support.