PipeWire doesn't recognize audio device

Issues & Assistance Unsupported hardware | Dual boot
1

I’ve installed Garuda Dragonized yesterday, it’s working fine except that i have no audio because pipewire does not seem to recognize my audio device. I’ve tried most things i’ve found in the forums with no help. I had this issue on Windows as well when i just installed it, but i only had to install the drivers from there then unplug then plug my headphones back in, then it worked. I have tried re-plugging my headphones on Garuda as well, did not work. ALSA does seem to recognize my audio device (ALC887) VD but not pipewire.

inxi output:

System:
Kernel: 6.14.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=df3ef74e-6819-4153-9575-25dd340a582b rw rootflags=subvol=@
quiet snd_hda_intel.dmic_detect=0 snd-intel-dspcfg.dsp_driver=1
resume=UUID=736adc79-f2ef-4789-9b7d-9e952713373d loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.13.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: issx-1230 product: issx-28652 v: issx-20593
serial: <superuser required> Chassis: issx-32095 type: 3 v: issx-20563
serial: <superuser required>
Mobo: issx-4316 model: issx-18776 v: issx-13769
serial: <superuser required> part-nu: issx-1062 uuid: <superuser required>
UEFI: issx-2265 v: issx-7631 date: 10/14/2016
CPU:
Info: model: Intel Core i5-7500 bits: 64 type: MCP arch: Kaby Lake
gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 9 microcode: 0xF8
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 1600 min/max: 800/3800 scaling: driver: intel_pstate
governor: powersave cores: 1: 1600 2: 1600 3: 1600 4: 1600 bogomips: 27199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI
driver: nvidia v: 570.144 alternate: nouveau,nvidia_drm
non-free: 550-570.xx+ status: current (as of 2025-04; EOL~2026-12-xx)
arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3
speed: 8 GT/s lanes: 16 ports: active: none off: DVI-D-1
empty: DP-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1c82 class-ID: 0300
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 93 s-size: 524x292mm (20.63x11.50")
s-diag: 600mm (23.62")
Monitor-1: DVI-D-1 mapped: DVI-D-0 note: disabled model: Asus VS247
serial: <filter> built: 2016 res: mode: 1920x1080 hz: 60 scale: 100% (1)
dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia nouveau drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: nouveau device: 2 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.144
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
memory: 3.91 GiB
API: Vulkan v: 1.4.309 layers: 6 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1050 Ti driver: nvidia v: 570.144 device-ID: 10de:1c82
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.7 256
bits) driver: mesa llvmpipe v: 25.0.4-arch1.1 (LLVM 19.1.7)
device-ID: 10005:0000 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403
API: ALSA v: k6.14.3-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: wg0-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 931.51 GiB used: 15.21 GiB (1.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-75WN4A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A01 scheme: GPT
Partition:
ID-1: / raw-size: 77.88 GiB size: 77.88 GiB (100.00%)
used: 15.21 GiB (19.5%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
ID-2: /boot/efi raw-size: 894.7 MiB size: 892.9 MiB (99.80%)
used: 612 KiB (0.1%) fs: vfat dev: /dev/sda8 maj-min: 8:8
ID-3: /home raw-size: 77.88 GiB size: 77.88 GiB (100.00%)
used: 15.21 GiB (19.5%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
ID-4: /var/log raw-size: 77.88 GiB size: 77.88 GiB (100.00%)
used: 15.21 GiB (19.5%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
ID-5: /var/tmp raw-size: 77.88 GiB size: 77.88 GiB (100.00%)
used: 15.21 GiB (19.5%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.57 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 4
dev: /dev/zram0
ID-2: swap-2 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda7 maj-min: 8:7
Sensors:
System Temperatures: cpu: 55.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.57 GiB used: 2.73 GiB (17.5%)
Processes: 286 Power: uptime: 1m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.22 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 1337 pm: pacman pkgs: 1325 libs: 379 tools: octopi,paru
pm: flatpak pkgs: 12 Compilers: gcc: 14.2.1 Shell: garuda-inxi default: fish
v: 4.0.2 running-in: konsole inxi: 3.3.38
Garuda (2.7.2-1):
System install date:     2025-04-21
Last full system update: 2025-04-23
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut(custom) mkinitcpio nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

‘aplay -l’ output:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0

‘pactl list short sinks’ output:

35      auto_null       PipeWire        float32le 2ch 48000Hz   SUSPENDED
2

Hi there, welcome to the forum.
Does the audio work in a live USB?
If so, you could try:

  • installing and booting with the linux-lts kernel (in the case this should be a kernel regression bug)
sudo pacman -S linux-lts linux-lts-headers
  • downgrading pipewire, to check if this is a pipewire regression
downgrade pipewire
  • Then you could also check if this is occurring also if you switch to pulseaudio. You can do this in RANI system settings. I’m not on my Garuda machine at the moment, but, if I remember correctly, you simply have to use the “Pulseaudio support” flag instead of the “Pipewire support” (default) and probably you should flag also “Alsa support” and “Jack support”. Take a note of what you have now, in case you need/want to go back to it.
3 Likes
3

The audio does not appear to work in a live USB.

4

If so, I’d try with pulseaudio…

1 Like
5

I tried with pulseaudio as well, still not finding my device.
Here is the output of ‘pactl list short sinks’ with pulseaudio:

0       auto_null       module-null-sink.c      s16le 2ch 48000Hz       SUSPENDED
6

If you dual boot with Windows, make sure you completely shut down when you are in Windows, disabling the “fast startup” feature. What Is “Fast Startup” Mode and How to Enable or Disable It? - MiniTool
Also a cold boot might help in this case.

3 Likes
7

I’m dual booting with Windows 11, and have already disabled ‘hibernation’ and stuff like that. I’ve tried cold booting and it still hasnt detected my audio device.

Another information, the microphone on my headphones are detected and works. Just not the output.

8

The Realtek ALC887-VD is always problematic on Linux, especially as it is usually caused by a faulty BIOS.

In addition, you have an ancient BIOS and I can’t find anything useful about this hardware.

Remove these kernel parameters, if I am not mistaken they are deprecated and no longer work on new kernels. Then reboot and then open a terminal and try this:

sudo tee /etc/modprobe.d/snd-hda-intel-fix.conf <<<'options snd-hda-intel probe_mask=1'

Then reboot again and check if the sound works w/o issues.

2 Likes
9

it turns out i plugged in my headphones in the wrong port :person_facepalming:
i have no idea why it worked on windows but i thought it was a linux issue, turns out it was just mine. thanks for the help though!

2 Likes
10

The main problem is usually about 60 cm in front of the screen. :sweat_smile:

3 Likes
11

the ports are actually in the back of the PC case so i think that explains how i could’ve missed that :rofl:

12

I think it is because it is a headset and not headphones. The fact that it works on windows is probably because Realtek has coded the windows drivers correctly so that it works on the appropriate port. But Realtek drivers are bad on Linux anyway.
I have marked your post as solution, maybe it will help one or the other with the same hardware/sound chip and/or a similar issue.

Have fun with Garuda Linux. :slightly_smiling_face:

3 Likes
13

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.