Linux

48328 readers

602 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

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

submitted 10 months ago by Evkob@lemmy.ca to c/linux@lemmy.ml

14 comments fedilink hide all child comments

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 :)

you are viewing a single comment's thread
view the rest of the comments

[–] AnEilifintChorcra@sopuli.xyz 3 points 10 months ago (3 children)

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.ca 3 points 10 months ago (1 children)

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.

load more comments (1 replies)