this post was submitted on 18 Jan 2026
987 points (97.3% liked)
PC Gaming
13233 readers
1290 users here now
For PC gaming news and discussion.
PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
Interesting. I've been using Linux for nearly 6 years now, and I can definitely relate to pipewire and audio related issues (I'm a musician so I've suffered much in that area), but I can't say I've struggled so much with devices. I wonder if those are Bazzite specific issues or if our setups are just different.
i’m my case i am using apparently old hardware, i ran into the following issues with my set up:
won’t lie i had to use AI to RTFM though chat GPT bricked my stuff more then i should have let it. gemini was better at this
You say older hardware so just curious if you happen to have an Asus mobo? If we are talking AM4 era, heads up that Asus mobos saw a lot of firmware revisions in 2025 including patches for usb-related issues. I have a b550 board that has been troublesome but seems a bit more stable with the latest firmware.
i have a TUFF gaming motherboard. so yes i do have an asus motherboard. i may have to flash the bios, but that’s a bit of a yikes. i may want to replace my battery back up first
Wow you certainly learned a lot trouble shooting that.
I haven't had something that annoying happen, usually it's been install and use.
BUT putting Linux on an ancient dell box was a learning experience. I installed the system on the HDD. After shutdowns the aystem would wake back up. The solution was adding kernel quirks line to grub boot with a numeric code, which told the hardware to ignore the self wake up event from the USB bus.
Then when I wanted speed the bios didn't support NVME boot. So I had to add a small ssd for boot partition , but have rest of system on the NVME drive. I didn't want to reinstall and resetup so I was learning a lot about gparted and copy pasting partitions and editting fstab to cobble together a replicated set of partitions. It was a great way to understand how formatting, partitioning and mounts all worked.
mine it set to never let the usb sleep. the hub or device ubs controls HATE going to sleep only to wake up on time