[Help] Audio devices disappear after reboot (EndeavourOS, Pipewire)

Hello! I’ve posted this a few weeks ago on /c/linux4noobs@programming.dev but I didn’t get much of an answer, I hope it’s okay to post it here as well.

I use 3 audio devices on my computer: my monitor’s speakers (through HDMI), my headphones (through line-out/built-in audio) and my microphone (line-in/built-in audio). They all work fine, but when I reboot my headphones / line-out don’t seem to get recognized at all.

The only solution I’ve found thus far is to re-install alsa-utils twice after rebooting. Upon the first reinstall, my line-out / headphones reappear but my line-in mic disappears, only to come back after the second reinstall. Technically my sound works perfectly fine after this, but it feels extremely dumb to reinstall a package twice after every reboot.

Any help would be greatly appreciated, thanks in advance :)

agent_flounder,
@agent_flounder@lemmy.world avatar

Reinstalling alsa utils twice? Interesting and weird.

Any chance some other software is messing things up? Is pulse audio installed too? Jack? Other? Just tossing out crazy ideas here, idk.

Wonder if the kernel version has a known issue with your specific hardware? What hardware is it, btw?

Like the other person said I would definitely want to see if there are any errors in the logs.

Evkob,
@Evkob@lemmy.ca avatar

Nope, I’ve checked and I don’t have any PulseAudio, JACK, or other audio packages that could interfere. This install has only ever used PipeWire for audio.

Could be kernel related, I don’t know. That’d be quite over my head, but I’ve had this issue using both the standard linux kernel and the zen kernel.

I didn’t see anything in journalctl’s logs that relates to audio as far as I can tell.

Reinstalling alsa utils twice? Interesting and weird.

Want to know what’s even more fun? I need to re-install alsa-utils thrice now after properly enabling pipewire.service like I did on that other comment thread :P

agent_flounder, (edited )
@agent_flounder@lemmy.world avatar

Sorry I didn’t get back to you sooner.

Nope, I’ve checked and I don’t have any PulseAudio, JACK, or other audio packages

Ok good. We should be able to rule that out.

Could be kernel related, I don’t know.

What version? The command uname -r will give it to you. More info here

Also… If you run dmesg do you see any audio related devices or errors? I should’ve thought to ask about that last time.

Want to know what’s even more fun? I need to re-install alsa-utils thrice now

Whee!™ Are we having fun yet lol

That is seriously bizarre.

Did I ask what audio hardware chipset you’re using?

It should show up in dmesg output. Or alternatively look up your motherboard specs and get it that way. Assuming you’re using the built in motherboard audio and not a separate card.

agent_flounder,
@agent_flounder@lemmy.world avatar

PS:

What pipewire packages are installed?

What alsa packages are installed?

I’m wondering if something is missing or borked for some reason.

AnEilifintChorcra,

I’m not very familiar with pipewire, I’ve always just been able to plug and play with any headphones but you can try runnning


<span style="color:#323232;">Journalctl -r
</span>

After your next reboot to see the most recent system logs and check for any errors with pipewire

I think you can also run


<span style="color:#323232;">Sudo systemctl status pipewire.service
</span>

After you reboot to make sure that it is enabled by default, if its not you should be able to run


<span style="color:#323232;">Sudo systemctl enable --now pipewire.service
</span>

This Reddit thread might be helpful Teddit alternative link

EndeavorOS also have a forum that might be helpful

Evkob,
@Evkob@lemmy.ca avatar

So this comment made me realize pipewire.service wasn’t enabled (I had to use the command ‘systemctl --now enable pipewire --user’ as the ones you provided didn’t work on my system.)

It’s up and running now, but after a reboot I still have the same issue.

skullgiver,
@skullgiver@popplesburger.hilciferous.nl avatar

Not sure if it’s related, but you should also check if your wireplumber service is running correctly, just in case.

Evkob, (edited )
@Evkob@lemmy.ca avatar

It wasn’t, but this still doesn’t fix the issue. I’m honestly perplexed and might just deal with triple reinstalling alsa-utils after every reboot. I’ll probably start from a fresh install soon enough anyway :P

Vilian,

do you have pipewire installed?

Evkob,
@Evkob@lemmy.ca avatar

Yeah, I included that in the title, should have restated it in the body though!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • linux@lemmy.ml
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #