76
Recommended linux variant for gaming.
(lemmy.world)
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.
WWW:
Discord:
IRC:
Matrix:
Telegram:
It started with conflicts between the preinstalled gnome extensions - namely the desktop icons broke other extensions, like Pop!_shell for window tiling. So I had to disable desktop icons.
My latest installed kernel (6.5.11) breaks screen detection - The resolution is stuck at 1024x768.
My PC gets stuck (probably on self test) after reboot or switching it on, after Nobara has shut down. Solution: Pull the power plug, wait 10 seconds, reconnect and turn it on.
I expect more to break with the next updates.
On nobara I have never had any of these issues on nvidia and on KDE.If you wanna give it a try you can even get it to look like GNOME.
Alrighty then: Now I have a reason to switch graphics cards and install Nobara on my other SSD. I bought a Radeon RX 7600 for this setup, because of AMD's praised open-source drivers. My spare GPU is an RTX 3060, so I can actually test both worlds.
Nah AMD works much better than nvidia, my statement was meant to be like "works even on nvidia" you should definetly stay AMD
That's what folks over here tell me, and you are most probably right. There is still one more issue scratching my head though: RayTracing performance on Cyberpunk 2077: It works great on high settings with stable 50 FPS minimum on my Windows 10 + Nvidia build, but it's quite the opposite on this Nobara + AMD system. 5FPS and slowdowns are just unplayable. I expected the bad AMD performance being fixed by today. I think I should swap GPUs between both systems and test again.
I am also getting like 20 fps less on linux than windows, I think its just how it is with cyberpunk. Testing can't hurt
For that last one, try disabling Fast Boot in your BIOS/UEFI. That may be the culprit.