Why does my audio not output anything when I start my computer up?

General system Kernel, boot, graphics & hardware
1

Ever since I changed my motherboard, CPU, Graphics card and RAM but kept the same drive and OS, sometimes when I boot up booting into EndeavourOS for the first time, when I play something from any application, there is no audio. The way to get it to work is just doing random things such as running systemctl --user restart pipewire-pulse, disconnecting and connecting to microphone jack, stopping what I am playing and starting again etc. In other cases I have removed the headphones from the headphones jack for 20 seconds and reconnected it or reconnecting it multiple times before it works. This issue does not continue if I put my PC to sleep or hibernate.

EndeavorOS does detect the headphones as it shows me disconnecting and reconnecting headphones however no sound.

I have tried:

mv wireplumber/ wireplumber1/

But to no avail.

I have ran journalctl --user -b | grep -Ei 'pipewire|wireplumber and this is the output:

May 31 17:07:55 joe-z97xsoc systemd[4757]: Listening on PipeWire PulseAudio.
May 31 17:07:55 joe-z97xsoc systemd[4757]: Listening on PipeWire Multimedia System Sockets.
May 31 17:07:55 joe-z97xsoc systemd[4757]: Started PipeWire Multimedia Service.
May 31 17:07:55 joe-z97xsoc systemd[4757]: Started PipeWire PulseAudio.
May 31 17:07:57 joe-z97xsoc wireplumber[4908]: spa.bluez5: BlueZ system service is not available
May 31 17:07:57 joe-z97xsoc wireplumber[4908]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
May 31 17:07:57 joe-z97xsoc wireplumber[4908]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
May 31 17:10:20 joe-z97xsoc systemd[4757]: Stopping PipeWire PulseAudio...
May 31 17:10:20 joe-z97xsoc systemd[4757]: Stopped PipeWire PulseAudio.
May 31 17:10:20 joe-z97xsoc systemd[4757]: Started PipeWire PulseAudio.

Any way to fix this? Is there some additional packages I need to install?

I have booted up Windows from the same computer and I don’t have issues on Windows at all meaning I don’t think its a hardware issue.

2

Hi @unix_lover ,
Shameful or not I wrote into the URL field of FF: pipewire issues after hardware change in arch linux
Quote
1. Reset WirePlumber Cache (Most Common Fix)

WirePlumber remembers the configuration of your old hardware. Clearing its state forces it to scan and detect your new setup from scratch.

Open your terminal and run:

systemctl --user stop wireplumber pipewire pipewire-pulse
rm -rf ~/.local/state/wireplumber/
systemctl --user start wireplumber pipewire pipewire-pulse

2. Verify Hardware Detection

Make sure ALSA and PipeWire can physically see your new hardware.

  1. List your available audio devices with: aplay -l
  2. Open the volume and routing manager: pavucontrol
  3. Go to the Configuration tab in pavucontrol and ensure your new hardware is set to an active profile (e.g., Analog Stereo Duplex or Pro Audio) instead of “Off”

3. Clear PipeWire Cache

If resetting WirePlumber isn’t enough, you can clear all PipeWire settings to restore defaults

systemctl --user stop pipewire.socket pipewire-pulse.socket
rm -rf ~/.config/pipewire/
systemctl --user start pipewire.socket pipewire-pulse.socket

4. Adjust PipeWire/ALSA Power Management

Sometimes new hardware (especially USB DACs or Bluetooth devices) goes to sleep too quickly or suffers from crackling. You can disable ALSA suspend features by creating a custom override file:

mkdir -p ~/.config/wireplumber/main.lua.d/
cat << 'EOF' > ~/.config/wireplumber/main.lua.d/51-disable-suspension.lua
rule = {
  matches = {
    { { "node.name", "matches", "alsa_output.*" } },
  },
  apply_properties = {
    ["session.suspend-timeout-seconds"] = 0,
  },
}
table.insert(alsa_monitor.rules, rule)
EOF

having done this
systemctl --user restart wireplumber
Unquote
UR a day ahead of me.

3

Thanks mate will try all this when the issue arises the next time :slight_smile:

4

Hi it turns out even on cachyOS and Windows all have the same issue, it might have something to do with the motherboard.

5

I would definitely check if there are any bios updates available. In case it has been a new motherboard, and the issue also is present when you boot from a live media, it might be an hardware issue and I would reach out to the manufacturer in that case.

6

Just did that and still issue persists, I have made a post on asrock and see if anyone has a solution otherwise I will likely make a warranty claim and replace it with another motherboard.