this post was submitted on 06 Jul 2023
301 points (95.7% liked)

Linux Gaming

15377 readers
298 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.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 1 year ago
MODERATORS
 

TLDR: From my experience, in 2023, the Mesa drivers with an AMD GPU provide an experience that is way better than NVIDIA with their proprietary drivers. And if you're helping a friend get into linux, and or linux gaming I think you should steer them towards an AMD GPU.

"It just works", is how I would describe my computer after making the switch to an AMD GPU.

Having migrated from Windows I came over with an NVIDIA GPU, and for a long while my experience with using the proprietary NVIDIA drivers was fine. I had started with Manjaro, then moved to EndeavourOS after getting tired of Manjaro forgetting to renew their keys. EndeavourOS was an order of magnitude better, but eventually I got tired of tending to Arch and settled onto Fedora. Everything worked well enough so when I upgraded away from a 2070 Super I sought out a 3080 Ti, and again things were smooth. Issues didn't start cropping up until I upgraded monitors.

I went from 2560x1440@144hz to 3440x1440@240hz and on Fedora running under Wayland I could only get a max of 144hz. I tried using both HDMI and Displayport and could never budge past 144hz. Another issue that arose was I would need to manually turn my monitor on before booting my computer, otherwise I would not get an image, this was also the case for waking the computer having to manually turn on the monitor. Even after a fresh install of Fedora 38 these issues persisted.

Eventually I got tired of the issues I was experiencing on Fedora and decided to just try vanilla Arch. Using archinstall I was up and running with in no time, and to my surprise I was getting 240hz under X11 and Wayland. Tearing, and stuttering on X was detracting too much from the whole experience, so naturally I wanted to use Wayland.

Having gone with Gnome the amount of work required from my end to use Wayland was just too high. Even after getting the Wayland session up and running I still noticed odd graphical glitches, with enough frequency that I couldn't just live with them.

Eventually my 7900 XTX arrived, did a clean install with archinstall, and that's that. Everything just worked out of the box. It was refreshing that config changes I made were only because I wanted to, and not to enable basic functionality.

As a nice bonus seeing Processing Vulkan Shaders has become a rare occurrence after switching.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -2 points 1 year ago (11 children)

Did they fix the issue where installing Steam would nuke the desktop?

[–] [email protected] 5 points 1 year ago (10 children)

IIRC it was already fixed when Linus did this, just not distributed. It was caused by the bluntness Linus developed due to unmeaningful Windows warnings in the 1st place.

[–] [email protected] -1 points 1 year ago (9 children)

It's so crazy that such a bug ever made it to production. I guess that's the cost of FOSS: installing Steam can nuke your entire desktop.

[–] mccord 9 points 1 year ago (1 children)

It's nothing exclusive to open source. Eve Online removing boot.ini and bricking Windows installs was hilarious.

[–] [email protected] -1 points 1 year ago

I googled that. 2007 right? Looks like the Eve devs bungled that. In this case it was the Pop_OS devs who introduced the bug.

load more comments (7 replies)
load more comments (7 replies)
load more comments (7 replies)