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:
my usb cable for the mic was crap. and because the signal was flaky, Bazzite put the port on low priority mode where it only checks in when asked
the usb cable was insufficient to push the data, i swear it came with the mic. still thing this was a dubious conclusion, but a new cable was 5$
Bazzite would ask my USB speaker and mic within milliseconds of receiving power what their designation was, and the controllers in the devices responded so slowly that Bazzite gave them new names and put them in passive mode. i had to bake in the command to treat that like legacy equipment (ouch) to sit and listen for a reply however long it takes.
the speakers are flipped in meat space, due to outlets and the length of available cable, i can not change this, so i had to flip it in software, i was recommended easyeffects, but pipewire hated its guts, and i was better off learning to bake it in via the terminal after i was able to find the devices actual name once i got them out of passive jail above.
i had to bin the flat pack versions of discord and my web browser Vivaldi. don’t want to get into a browser war i have had enough trying to siphon through redacted reddit posts about that
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
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.
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
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