Speakers suddenly stop working

Ask Fedora
1

I’m using Fedora 44 Workstation on my HP Envy x360 15-fh0xxx and I have this weird issue where my external speakers connected to the laptop via jack stop producing sound. They are still detected in gnome settings, but they produce no sound.
When I reboot the system, the speakers work normally. But if I play sound (music, videos, etc) and then I stop playing the sound (even muting for 1 second), they stop working.
This was also a problem in Fedora 43 so I don’t think that’s the problem.

My system:

System:
  Host: hpenvyx360fh Kernel: 6.19.14-300.fc44.x86_64 arch: x86_64 bits: 64
  Desktop: GNOME v: 50.1 Distro: Fedora Linux 44 (Workstation Edition)
Machine:
  Type: Convertible System: HP product: HP Envy x360 2-in-1 Laptop 15-fh0xxx
    v: Type1ProductConfigId serial: <superuser required>
  Mobo: HP model: 8BE9 v: 75.44 serial: <superuser required> Firmware: UEFI
    vendor: Insyde v: F.14 date: 12/03/2025
Battery:
  ID-1: BAT1 charge: 56 Wh (100%) condition: 56/55.7 Wh (100.6%)
CPU:
  Info: 6-core model: AMD Ryzen 5 7530U with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 1996 min/max: 411/2000 cores: 1: 1996 2: 1996 3: 1996
    4: 1996 5: 1996 6: 1996 7: 1996 8: 1996 9: 1996 10: 1996 11: 1996 12: 1996
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Barcelo driver: amdgpu v: kernel
  Device-2: Quanta HP Wide Vision 5MP Camera
    driver: hid-sensor-hub,usbhid,uvcvideo type: USB
  Display: wayland server: X.Org v: 24.1.10 with: Xwayland v: 24.1.10
    compositor: gnome-shell driver: dri: radeonsi gpu: amdgpu resolution:
    1: 1920x1080~60Hz 2: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.0.3 renderer: AMD Radeon
    Graphics (radeonsi renoir ACO DRM 3.64 6.19.14-300.fc44.x86_64)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
    driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor
    driver: snd_rn_pci_acp3x
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
    driver: snd_hda_intel
  API: ALSA v: k6.19.14-300.fc44.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.6.4 status: active
Network:
  Device-1: Realtek RTL8852CE PCIe 802.11ax Wireless Network
    driver: rtw89_8852ce
  IF: wlo1 state: up mac: 0e:92:d7:16:b7:d5
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
  IF: enp4s0f3u1u4u2 state: down mac: 6c:1f:f7:72:95:12
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb type: USB
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: 58:96:71:BB:60:F7 bt-v: 5.3
Drives:
  Local Storage: total: 1.4 TiB used: 28.1 GiB (2.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL4512HBLU-00BH1
    size: 476.94 GiB
  ID-2: /dev/sda vendor: A-Data model: SE760 size: 953.87 GiB type: USB
Partition:
  ID-1: / size: 474.34 GiB used: 26.84 GiB (5.7%) fs: btrfs dev: /dev/dm-0
  ID-2: /boot size: 1.9 GiB used: 599.1 MiB (30.8%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 474.34 GiB used: 26.84 GiB (5.7%) fs: btrfs
    dev: /dev/dm-0
Swap:
  ID-1: swap-1 type: zram size: 7.06 GiB used: 613.2 MiB (8.5%)
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 55.6 C mobo: N/A gpu: amdgpu temp: 53.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 7.06 GiB used: 3.66 GiB (51.8%)
  Processes: 418 Uptime: 1h 40m Shell: Bash inxi: 3.3.40

Result of grep Codec /proc/asound/card*/codec* 

/proc/asound/card0/codec#0:Codec: ATI R6xx HDMI
/proc/asound/card1/codec#0:Codec: Realtek ALC245

Result of lspci -nnk | grep -A3 -i audio

04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir/Cezanne HDMI/DP Audio Controller [1002:1637]
	Subsystem: Hewlett-Packard Company Device [103c:8be9]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
--
04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor [1022:15e2] (rev 01)
	Subsystem: Hewlett-Packard Company Device [103c:8be9]
	Kernel driver in use: snd_rn_pci_acp3x
	Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70
04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Ryzen HD Audio Controller [1022:15e3]
	Subsystem: Hewlett-Packard Company Device [103c:8be9]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

Things I’ve tried:

  • Reinstall pipewire pipewire-pulseaudio pipewire-alsa wireplumber
  • Restart pipewire, pipewire-pulse wireplumber services
  • Tried using pavucontrol but I wasn’t sure what I was doing

If anyone knows a way to fix this I’d appreciate the help. Just a way to ‘restart’ my speakers so they work again without rebooting would be enough for me.

2

It sounds a bit like a power management bug.

04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor [1022:15e2] (rev 01)
	Subsystem: Hewlett-Packard Company Device [103c:8be9]
	Kernel driver in use: snd_rn_pci_acp3x
	Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70
04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Ryzen HD Audio Controller [1022:15e3]
	Subsystem: Hewlett-Packard Company Device [103c:8be9]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

I see that that snd_rn_pci_acp3x module has a “acp power gating” setting.

$ modinfo -p snd_rn_pci_acp3x
acp_power_gating:Enable acp power gating (int)
dmic_acpi_check:Digital microphone presence (-1=auto, 0=none, 1=force) (bint)

Is that enabled? [1] Do you see any error messages associated with it in your system logs? [2] Does disabling the power gating work around the problem? [3]

See also: https://www.youtube.com/watch?v=aoYoGw8KsX8&t=737

Also, you might likewise experiment with disabling the power_save setting of the snd_hda_intel driver.

  1. To see if it is enabled, try cat /sys/module/snd_rn_pci_acp3x/parameters/acp_power_gating. ↩︎

  2. To check the system logs, try sudo journalctl -t kernel -g snd_rn_pci_acp3x . ↩︎

  3. To disable the power gating, try creating a /etc/modprobe.d/sound.conf file containing options snd_rn_pci_acp3x acp_power_gating=0 and reboot your system. ↩︎

3

Hi, thank you for your help.

  1. snd_rn_pci_acp3x seems to be enabled. cat /sys/module/snd_rn_pci_acp3x/parameters/acp_power_gating returns 0
  2. I don’t see any error messages in the logs.
  3. I created a file /etc/modprobe.d/sound.conf containing options snd_rn_pci_acp3x acp_power_gating=0 just to be sure, but that also didn’t help.

Here are some of the most recent entries in the logs:
sudo journalctl -r -t kernel -g snd_rn_pci_acp3x

-- Boot afe3d539d8c241beadec8b1fa824dcfe --
Apr 30 07:09:03 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 3d6400787f4841c29dc61c3b34683ac1 --
Apr 29 21:42:20 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 939d101d382641fe987db254de614250 --
Apr 29 21:29:49 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot ea7fe295d1f0445b90a533b2fce77f1d --
Apr 29 20:44:03 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 53d8e21bacc34d06a59ce0c67bbf9458 --
Apr 29 20:12:58 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 38b6988987704c639b001da6f809716d --
Apr 29 17:16:19 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 0db7eddf3e5d4bf2a153facba665477f --
Apr 29 17:09:56 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot c08144f761cf42d2a0baf8e8e0020864 --
Apr 29 17:04:21 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 3f7c0fb3c1df484eaeddb82b81a754d2 --
Apr 29 16:58:57 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 78f3edd1a1374de0bd97fa29e1d408e7 --
Apr 29 16:35:37 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 341764013d2c4e48b40d3043af0d15c5 --
Apr 29 16:29:37 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 7c0956d0279f497b818523593d5a99a4 --
Apr 29 16:22:33 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 462d79d722f045e3ac3d484f37b0ca47 --
Apr 29 16:10:52 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot c85759ece2824aff99901c0d68d5bbf0 --
Apr 29 08:15:37 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 29e52644de544ea1b15fffd1cacd9ebe --
Apr 29 08:09:08 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot dfe74a25c67e4281af3442500d773d63 --
Apr 29 07:24:15 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 4002dff2d5ae48b487961aa19e3cd9d3 --
Apr 28 22:48:10 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 85d78110fdd2407c9cbea0e6d7b1dee0 --
Apr 28 22:44:07 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot f6264828038940a48bcfcb55c4f2ef6d --
Apr 28 22:37:10 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot f2a100db867e43829f9cd367d0c4afe2 --
Apr 28 22:32:18 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 900e3f246ca14992b5960bc1c923ab71 --
Apr 28 12:47:37 hpenvyx360fh kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
-- Boot 1f94a1cdcf134d6a85722b89e3ee9578 --

I also tried adding options snd_hda_intel power_save=0 to another .conf file in /etc/modprobe.d/ but that also didn’t help.

4

Sorry, that was my best guess. We’ll probably need to find some sort of error message in the logs to diagnose this problem any further.

Just as a clumsy workaround, the following might work.

5

Thank you so much for your help.

I think I found what was causing the issue: I used this guide to make the LEDs on my audio-mute and mic-mute buttons work, and they did. But testing the individual commands to turn the LEDs on and off caused my speakers to stop working.

I have tested my speakers without using the scripts in the guide and they seem to work without any issues, so I’m going to mark this as solved.

I’ve seen this post on the arch linux forum trying to solve the same LED problem so I’m going to investigate and see if I can come up with a similar fix for my system.