Fix Sound Card Drivers Not Detected on Pardus Linux 23

On Pardus Linux 23, a speaker icon with no output device can look like a missing sound card driver. The cause may be lower in the stack—a kernel driver or firmware issue—or higher up, where the desktop audio service has selected the wrong output. A quick check of the PCI or USB device list and ALSA’s card list will show which layer to investigate before you install packages or change configuration.

This guide applies to Pardus 23 desktops, including XFCE and GNOME installations. Pardus 23 release notes list XFCE 4.18 as the default desktop for the original release and a Linux 6.1 kernel; later Pardus 23 images and updates can differ. Check your installed kernel with uname -r rather than assuming every 23.x system has the same build. The Pardus 23 release notes also list the official repository components, including non-free-firmware. See the Pardus 23 release notes.

First, find out what “not detected” means

Linux audio has distinct layers. ALSA supplies the kernel audio interface and sound-card drivers; a desktop audio server such as PulseAudio or PipeWire sits above it and routes audio to speakers, headphones, HDMI, or USB devices. The Debian Reference audio section describes this split between ALSA drivers and audio servers. Therefore, an output missing from the desktop menu does not prove that Pardus lacks a sound-card driver. Check the hardware and ALSA layers first, then check the audio server.

Open a terminal and run:

lspci -nnk | grep -A3 -i audio
lsusb
aplay -l
cat /proc/asound/cards

lspci lists internal PCI audio hardware and its kernel driver when one is bound. lsusb helps with external USB audio devices. aplay -l and /proc/asound/cards show sound cards ALSA can see. If a command is missing, install the relevant diagnostic utility from the configured Pardus repository; alsa-utils provides tools such as aplay and alsamixer, while pciutils provides lspci.

1. If ALSA sees the card, check the output and mixer

When aplay -l lists a card but the desktop does not play sound, start with the selected output. Open the sound or audio settings in your desktop and choose the actual speaker or headphone output rather than HDMI, a dock, a monitor, or an unplugged device. Connect headphones and speakers directly to the computer for one test, and disconnect unused USB or HDMI audio devices temporarily so the output list is easier to read.

Check the ALSA mixer too:

alsamixer

If more than one card is listed, press F6 and select the card that matches the output you are testing. Look for muted playback controls and low levels. In alsamixer, M toggles mute for the selected control; raise the Master, Speaker, or PCM level gradually. The alsa-utils alsamixer manual documents the mixer controls. Some laptops have separate hardware mute keys, so test those as well. Save no configuration yet—first verify whether unmuting or selecting the correct device restores sound.

For a short ALSA playback test, use the card and device numbers shown by aplay -l. For example, speaker-test -c 2 -t wav tests the current default device; stop it with Ctrl+C. If the direct ALSA test works but normal desktop applications remain silent, investigate the desktop sound server and its output profile rather than installing a different kernel driver.

2. If the hardware appears in PCI or USB but ALSA has no card

If lspci or lsusb identifies the audio hardware but aplay -l shows no sound card, the problem is more likely to involve the kernel module, firmware, or device initialization. Gather the boot-time audio messages and loaded sound modules:

sudo journalctl -k -b | grep -i -E 'snd|hda|sof|audio|firmware'
lsmod | grep '^snd'

Look for a line naming a missing firmware file, a failed device initialization, or a module that did not load. Compare the PCI vendor and device IDs from lspci -nnk with the module and firmware mentioned in the logs. Hardware families vary: snd_hda_intel is common for Intel High Definition Audio, but newer systems and non-Intel devices may use different drivers, including Sound Open Firmware (SOF) modules. Do not force-load a guessed module or blacklist another one without confirming the chipset and the documented driver path.

Update Pardus packages before adding a driver

If this is an older or partially updated Pardus 23 installation, install available updates from Pardus Update or use the standard Pardus package workflow:

sudo apt update
sudo apt upgrade

Restart after kernel, firmware, or ALSA-related packages are updated, then run the detection commands again. Pardus 23 release notes document the distribution’s own repositories; avoid adding Debian repositories or installing random driver packages from download sites, since mixing repositories can replace core libraries or leave the system in an unsupported state.

If the kernel log names a missing firmware file, identify the exact audio chipset and firmware filename first. Search the Pardus package repository or the Pardus help documentation for that component, then install only the matching package from a supported repository. Pardus publishes a separate firmware installation note for certain devices, but it uses an experimental firmware repository. Treat that as a hardware-specific path: follow it only when its instructions match your device and you accept the repository tradeoff. Do not enable an experimental repository merely because the audio device is absent. See Pardus’s firmware installation guidance.

3. If ALSA sees the device but the desktop does not

Find which audio server your session is using before restarting anything. Run:

pactl info
wpctl status

pactl info reports the PulseAudio-compatible server; a PipeWire installation may provide PulseAudio compatibility through pipewire-pulse. wpctl status lists PipeWire devices and nodes when PipeWire and WirePlumber are installed. It is normal for one of these commands to be unavailable on a system using the other audio stack. Debian documents that its desktop environments can use different sound servers and lists the PipeWire setup for Debian 12 and later; do not assume Pardus XFCE and GNOME have identical audio-service setups.

If the command output identifies PipeWire, inspect whether PipeWire and WirePlumber are active in your user session before restarting them. If it identifies PulseAudio, check its user-session status and whether it can see the ALSA card. Do not install PipeWire and PulseAudio side by side as a first fix or run restart commands for both stacks blindly. First correct the device selection or service that is actually in use, then sign out and back in or restart that user service using the procedure appropriate to the installed packages.

4. If the audio hardware does not appear at all

If neither lspci nor lsusb shows the device, a desktop audio setting cannot fix it. For onboard audio, check the BIOS or UEFI setup for an enabled audio controller, then power the machine off completely and check again after reboot. For a USB sound adapter, reconnect it directly to another port and run lsusb again. For a virtual machine, confirm that the hypervisor exposes an audio device to the guest; a Linux guest cannot load a driver for hardware it has not been given.

If the device is present in hardware listings but has no “Kernel driver in use” line, record its vendor and device ID, the Pardus version, uname -r, and the relevant kernel log lines. Search Pardus or chipset-vendor documentation for that exact ID. This is more reliable than choosing a driver based only on a laptop model name, which may ship with different audio revisions.

Common assumptions to avoid

• “No sound icon means there is no driver.” Not necessarily. If ALSA lists the card, focus on the desktop output, mute state, or sound server. Check aplay -l before changing drivers.
• “Every Pardus 23 system uses PipeWire.” The audio stack can depend on the installed desktop and packages. Read pactl info and wpctl status before following PulseAudio- or PipeWire-specific instructions.
• “The Intel driver works for any sound card.” Driver choice depends on the actual chipset and kernel. Use the PCI ID and kernel log to identify the correct module; do not add a generic module blacklist or vendor driver without evidence.
• “A firmware error means I should enable every non-free or experimental repository.” Firmware packages are device-specific, and Pardus documents a separate experimental source for selected cases. Match the named firmware to your hardware before changing repository sources.

Confirm the fix

After each change, repeat aplay -l and check the desktop’s output list. The card should appear in ALSA, the intended speaker or headphone output should be selectable, and the volume controls should not be muted. Play audio from two applications and test both the built-in speakers and headphones if available. If audio vanishes after reboot, record the current kernel version and compare it with the last working one; that can point to a kernel, firmware, or boot-time module change.

If the hardware is visible but still has no ALSA card, or the kernel log repeatedly reports a missing firmware file or failed probe, keep the PCI or USB ID and log excerpt when asking Pardus support. Those details identify the problem far more precisely than “sound driver not detected,” and they help distinguish a driver issue from a desktop audio-routing problem.