this post was submitted on 10 Jul 2026
107 points (95.0% liked)
Linux Gaming
26684 readers
242 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
Help:
- ProtonDB
- Are We Anticheat Yet?
- r/linux_gaming FAQ
- Fork of an earlier version of the above
- PCGamingWiki
- LibreGameWiki
Launchers/Game Library Managers:
General:
Discord:
IRC:
Matrix:
Telegram:
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I physically disconnected all drives to force the EFI partition on the actual Windows drive. It still shat all over boot settings after the first major update.
Someone recommended I try rEFInd and it's been great. No update has forced me back into the UEFI to set boot order since.
Might be an ASUS MB thing, I never figured it out or bothered afterwards.
There are interfaces that allow a sufficiently privileged process to change EFI settings from the OS. Those settings are stored in the UEFI chipset, independent from the bootloader.
I really hope Windows doesn't alter that. My Gigabyte motherboard forced me to boot into windows after a hios update, because the Linux bootloader was not registered...
Don't even get me started on fucking Gigabyte. With all my heart,
FUCK GIGABYTE.
It is the single worst manufacturer I've ever had to deal with in both a personal and professional capacity. We've had to RMA half a classroom over the last two years because of busted motherboards. In separate incidents, two power supplies violently self-destructed and took the motherboards and CPUs with them. My own Gigabyte 2060 Super's fans had to be replaced within two years because the bearings were crap.
Worse, even the motherboards that didn't mercifully explode are a fucking chore because Gigabyte's UEFI implementation is the worst on the fucking planet. No two versions work alike. Some options are in completely different menus. Sometimes CSM or SecureBoot are busted out of the box. If PXE is enabled (which we have to use frequently), it will ALWAYS put PXE at the start of the boot order. And if it can't connect to a PXE server, it doesn't fall back to the next boot option. It gracefully shits itself and sits on an error message until someone manually restarts it and interrupts the process.
Fuck Gigabyte.