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

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

very same with me, yea. though i was having so many problems with easyeffects i was gun shy using another program to manage the speakers when i just wanted the one change. so i baked in a rule for that named speaker only into the os

from what i gather that means you reach for the 9mm when you don’t know how to say please?

i think the real issue is my computer has been silently suffering for all these years as windows just didn’t tell me my hardware is borked and old. and just has a shot gun full of code that fixes whatever it can stick to. and Bazzite either does not have that, or i fell into an exception in use due to hatred and old hardware.

but getting into the weeds was very difficult, and my desk is not as flat as it once was

i can only imagine the horrors of what button combination i need to save and close and get my terminal back on the next one…

i could not get them to play nice with the hardware, pipewire, or each other. and they don’t like being messed with

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

i think i learned that there was a lot wrong with my set up that windows just shoved under the rug. and maybe windows is right to do so, figuring i was willing to dig in deep this time, but my friends… not so much, and i don’t think i have the capability to help them if they run into issues like i did.

the reason ‘I’ learned to dislike flat packs is that it puts the software in its own little isolation bubble from what i understand. and i get where people are coming from. but they REALLY don’t like connecting to hardware, or sharing nice with other apps.

keep in mind i am a fairly adroit user of windows, diving in head first, so a lot of this is learning the hard way (nano anyone?) and i learned a lot. but yea bumpy.

i switched over to Bazzite about a week ago, and it has been super frustrating. though it’s not in where you think. the game my group is playing (Arc Raiders) worked without a hitch.

• but my speaker system, and microphone forced me to learn a whole lot about USB hand shakes,
• ghost usb profiles,
• usb cable choice,
• what a flatpac is and why people hate it,
• nano eccentricities (including how to save and quit, just labeling ctrl-o as save and not overwrite would stop so much bs),
• sink states,
• device name resolution,
• pipewire,
• pipe plumber,
• pipe wire holding devices hostage,
• usb power flapping because i plugged my speakers and my mic to close to each other causing the os to just give up on the both of them.
• the timing of when the os asks for usb identifiers, verses when the usb devices are given power
• out dated guides relying on depreciated methods and acceptable code used in modifiers to os procedure.

my experience and days of trouble shooting the “easy” replacement os for gaming has frightened my friend group far away from linux.