Hello! I’ve posted this a few weeks ago on /c/[email protected] 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 :)

  • AnEilifintChorcra@sopuli.xyz
    link
    fedilink
    arrow-up
    3
    ·
    11 months ago

    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

    Journalctl -r
    

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

    I think you can also run

    Sudo systemctl status pipewire.service
    

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

    Sudo systemctl enable --now pipewire.service
    

    This Reddit thread might be helpful Teddit alternative link

    EndeavorOS also have a forum that might be helpful

    • Evkob@lemmy.caOP
      link
      fedilink
      arrow-up
      3
      ·
      11 months ago

      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.

        • Evkob@lemmy.caOP
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          11 months ago

          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