Reinstalled EOS and suddenly 5.1ch audio has become unstable

Hello.

I recently switched audio setup and ran 5.1ch audio for over a day without issue.

As I have been wanting to reinstall EOS for a while I tried doing so today and i can’t understand why audio isn’t working as it should.

Nothing on the amp has changed.
But now the connection keeps dropping and is later restarting after seconds of silence leading to an audible glitch.

the output device is an IEC958/AC3 and i tried copying the previous contents of /home/fox/.local/state/wireplumber/ and replacing that without success

I thought that since there were some differences that I could restore the previous configuration by doing this but that was useless.

How can I get stable audio again?

Please post the output of:

inxi -FGAxxc0z

Before reinstalling, when was the last time you updated?
Also, have you tried booting with different kernels?

Fallback or not, latest lts or 6.13.5 doesn’t make a difference

As i have been away many days over a longer period of time the “eos welcome center” was showing me 6-7 updates at logon.

System:
  Kernel: 6.13.5-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A wm: kwin_wayland dm: 1: LightDM
    2: SDDM note: stopped Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: X470 Taichi serial: <superuser required>
    UEFI: American Megatrends v: P10.31 date: 08/22/2024
CPU:
  Info: 8-core model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen 2
    rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
  Speed (MHz): avg: 1756 min/max: 550/4560 boost: enabled cores: 1: 1756
    2: 1756 3: 1756 4: 1756 5: 1756 6: 1756 7: 1756 8: 1756 9: 1756 10: 1756
    11: 1756 12: 1756 13: 1756 14: 1756 15: 1756 16: 1756 bogomips: 124803
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 570.124.04
    arch: Pascal pcie: speed: 8 GT/s lanes: 16 ports: active: none
    off: DP-3,DVI-D-1,HDMI-A-1 empty: DP-1,DP-2 bus-ID: 0e:00.0
    chip-ID: 10de:1b80
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    d-rect: 6400x1440 display-ID: 0
  Monitor-1: DP-3 pos: center model: Asus ROG PG278Q res: 2560x1440 hz: 144
    dpi: 109 diag: 686mm (27")
  Monitor-2: DVI-D-1 pos: right model: Dell P2211H res: 1920x1080 hz: 60
    dpi: 102 diag: 547mm (21.5")
  Monitor-3: HDMI-A-1 pos: primary,left model: Dell P2211H res: 1920x1080
    hz: 60 dpi: 102 diag: 547mm (21.5")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.124.04 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.4.304 surfaces: xcb,xlib,wayland device: 0
    type: discrete-gpu driver: N/A device-ID: 10de:1b80
  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: NVIDIA GP104 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: speed: 8 GT/s lanes: 16 bus-ID: 0e:00.1 chip-ID: 10de:10f0
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASRock driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 10:00.4 chip-ID: 1022:1487
  API: ALSA v: k6.13.5-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 08:00.0 chip-ID: 8086:24fb
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
    pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 0a:00.0 chip-ID: 8086:1539
  IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-9:3 chip-ID: 8087:0aa7
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
Drives:
  Local Storage: total: 16.8 TiB used: 12.62 GiB (0.1%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: PM961 NVMe 512GB
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 34.9 C
  ID-2: /dev/nvme1n1 vendor: Mushkin model: MKNSSDHL1TB-D8 size: 931.51 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 41.9 C
  ID-3: /dev/sda vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-4: /dev/sdb vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-5: /dev/sdc vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-6: /dev/sdd vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-7: /dev/sde vendor: SanDisk model: SSD PLUS 480GB size: 447.14 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-8: /dev/sdf vendor: SanDisk model: SSD PLUS 480GB size: 447.14 GiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 467.4 GiB used: 11.92 GiB (2.6%) fs: ext4 dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 38.1 C mobo: 36.2 C
  Fan Speeds (rpm): fan-1: 943
Info:
  Memory: total: 64 GiB note: est. available: 62.71 GiB used: 2.68 GiB (4.3%)
  Processes: 327 Power: uptime: 6m wakeups: 0 Init: systemd v: 257
    default: graphical
  Packages: pm: pacman pkgs: 1076 Compilers: gcc: 14.2.1 Shell: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.37

This:

Doesn’t really answer this:

When, as in last week, last month, 3 months ago?
So, not how many updates were available prior to updating, but rather when was the last time updates were available and you actually installed them?

The point of this question is only to see if the 6.6.xx LTS kernel was the last kernel you had when things were working just fine prior to reinstalling.

That said, having issue after reinstalling when they weren’t present prior to reinstalling makes it kind of strange either way. Unless you did have issues, but didn’t notice them after adding the new hardware.

Another question is, does your new setup include an external display or audio device?

Displays haven’t changed.

The only hardware that’s changed was getting rid of a usb audio device and purely analog amplifier. Now I’m using toslink output from motherboard connected to a new amp.

i do not remember last time i ran a system update. 6-8 months i guess?
my only reference is the amount of updates available.

While it can be done, Arch-based distros are not meant to go that long without an update.
If you aren’t an Arch expert, or don’t watch some vids or read through some instructions, it becomes nearly impossible for a non-expert after about 3 months.

In the future, update at least bi-weekly.

Now, as for why this has gone bad, about a month ago the LTS kernel was at 6.6.xx. Now, it is at 6.12.xx. It is possible that the newer kernels, including 6.13.xx (the mainline kernel) are having compatibility issues with your device.

Please show the output of the below so we can see what you have installed:

pacman -Q | grep -A 0 -E "(wire|pulse|grub|systemd|dracut|mkinitcpio|linux|headers)"

If updating is something you forget to do regularly, even when you are not away, you can either use an update reminder or use another non-Arch-based distro that doesn’t update as frequently. When using an Arch-based distro, users who do any kind of art (3D, music, etc.), play video games, coding, etc. usually have new updates available every day.

This exactly why i wanted to reinstall in the first place. (Haven’t had the time to keep it updated for a period of time because of temporarily changed work location. Keeping the system online 24/7 isn’t feasible). Normally i check for updates on a roughly weekly basis. (which has worked fine when that was an option).

archlinux-keyring 20250123-1
--
dracut 106-1
--
gst-plugin-pipewire 1:1.2.7-1
--
kernel-install-for-dracut 1.11-1
--
kpipewire 6.3.2-1
--
lib32-libpulse 17.0+r43+g3e2bb8a1e-1
--
lib32-systemd 257.4-1
--
lib32-util-linux 2.40.4-1
--
libpipewire 1:1.2.7-1
--
libpulse 17.0+r43+g3e2bb8a1e-1
--
libwireplumber 0.5.8-1
--
linux 6.13.5.arch1-1
linux-api-headers 6.13-1
linux-firmware 20250210.5bc5868b-1
linux-firmware-whence 20250210.5bc5868b-1
linux-headers 6.13.5.arch1-1
linux-lts 6.12.17-1
linux-lts-headers 6.12.17-1
--
pipewire 1:1.2.7-1
pipewire-alsa 1:1.2.7-1
pipewire-audio 1:1.2.7-1
pipewire-jack 1:1.2.7-1
pipewire-pulse 1:1.2.7-1
--
pulseaudio-qt 1.7.0-1
--
systemd 257.3-1
systemd-libs 257.3-1
systemd-resolvconf 257.3-1
systemd-sysvcompat 257.3-1
--
util-linux 2.40.4-1
util-linux-libs 2.40.4-1
--
vulkan-headers 1:1.4.304.1-2
--

edit: missed to copy last line: wireplumber 0.5.8-1

Okay. Try the following. Install wireplumber, update your boot menu, then rename the folder you mentioned earlier in the article and reboot and select the LTS kernel from the boot options menu.

sudo pacman -Syu wireplumber
sudo reinstall-kernels
mv .local/state/wireplumber .local/state/wireplumber-bkp

Reboot into the LTS kernel.

Hopefully, the issue was just that you didn’t have the wireplumber package.
Not sure why it wasn’t installed, though. :thinking:

EDIT: Made a mistake with the 3rd command. It’s correct now.

my mistake, when copying the output i didn’t get the last line to come along.
wireplumber 0.5.8-1 is installed.

Okay. Still do ALL the steps because sometimes that folder is the only issue.

If it doesn’t work, boot into the 6.13.xx kernel, uninstall the LTS, then install the older LTS.
After this, update your boot menu, reboot and select the 6.6xx LTS kernel.

sudo pacman -Rs linux-lts linux-lts-headers && yay -Syu linux-lts66 linux-lts66-headers
sudo reinstall-kernels
mv .local/state/wireplumber .local/state/wireplumber-bkp

Yes, redo everything. That folder is finicky.

no dice after doing that. also: low hum has appeared when the connection is active (there is no hum if i switch to 2ch output)

Actually, i think i was on 6.5.13 before reinstall

After doing what? I gave you two different sets of suggestions.

i tried both and neither was a success or changed anything

Well, then I have two more suggestions, a new one and one already made:

  1. Check if you have BIOS updates by going to your device manufacture’s website
  2. Use a distro that updates less often so you don’t have to worry about missing some

1: N/A am already on latest
2: doesn’t seem like there is a middleground between ancient packages (ubuntu/fedora) and arch derivatives. Also got no reason to miss updates now :person_shrugging:

There are two. Well, three, but I would never suggest it.

The two are Void Linux and KaOS. Actually, no. There are more. Debian Sid based distros are good for this too. Like Siduction Linux.

Also, if you learn to use Distrobox, which has a very easy learning curve, you could use a static release distro, but use Arch packages inside it. I do this with MX Linux.

FWIW: if i boot into an older iso “Cassini” (2024-04-20) which i had laying around; and switch to 5.1ch output it stays active with no significant hum.

But that’s using PulseAudio…

Well, I think you can still use Pulseaudio. But you’ll need to use the '-Rdd command, I think. Because almost every app will say they require Pipewire when you’re trying to switch.

The other option, again, is another distro that uses an older kernel.

i’d rather poke around with WirePlumber config but am not sure what I’m supposed to look for.

edit: i did stumble upon aplay /dev/null which can keep the connection alive but it’s not ideal and there is still the weird hum to deal with.

1 Like