this post was submitted on 15 Mar 2026
432 points (98.9% liked)
Linux Gaming
28380 readers
57 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.
That includes posts generated by LLMs. It doesn’t matter if you “don’t have the time” or “would’ve written the same anyway”, or if “everyone’s doing it geez get with the times”.
For now it’ll also include “AI”-assisted projects that haven't had at least two months of (public, verifiable) dev time behind them.
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
Mind letting us know why or how? When I installed it almost a year ago on my desktop, I did install it as a dual boot option with no issues. Of course this doesn't mean there aren't issues I just didn't run into. I'm also not new to Linux and didn't pick a fully default install, if that makes a difference. So I could've probably fixed it if it did break, but it never gave me any issues.
The only thing that I dislike, and that could probably cause issues, is that for my installation the mount point for the efi/boot partition isn't specified in fstab using a uuid, but using the device name (which isn't fixed and can change with hardware changes). That is a very weird (and unnecessary) decision IMHO.
Well in my case, using systemd-boot:
Window's default EFI partition was too small to hold the kernel, but CachyOS setup didn't check for this and just failed to boot linux. You wouldn't run into this issue on a second disk I suppose, but I did on a single NVMe shared with Windows.
Sometimes, if you do share an EFI partition between Windows/Linux, Windows Update will randomly nuke it and break your linux install.
I also had an instance where systemd-boot just stopped detecting Windows after awhile, and it needed some manual fixing.
Basically, trying to install linux on the default EFI partition next to Windows is a risky default, and Windows users new to linux aren't going to know anything about how to fix it.
The fix is to just make a second EFI partition on the drive, but the installer doesn't do this by default. And I encountered this a long time ago, but noticed the issue was still present when testing Cachy on another PC, by chance.