this post was submitted on 23 Jul 2024
69 points (100.0% liked)
Linux Gaming
15802 readers
40 users here now
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I also have a 3080 and have been considering switching to AMD, but with the problems you describe. Maybe, I'll give Intel's offerings a shot assuming the graphics cards don't suffer the same way their cpu's are right now.
I have an Intel Arc A750 lying around that I used at the end of last year to test whether a specific problem I was having under Linux was related to NVIDIA or something else. The answer was NVIDIA basically all of the time, but keep in mind this was around the 535 driver version.
I didn't really test the Intel GPU long enough to tell you whether I'd recommend it. It worked well out of the box, but I'm not sure whether some of the game compatibility problems under Windows mirror over to Linux.
What was very cool when I was A-B testing some of the issues I had with the AMD card though, is that you can simply shut down the computer, swap the cards and it'll boot up just fine right away. No driver installs needed as the kernel just includes it - no driver conflicts either. With NVIDIA, the driver can have conflicts when using a card by a different vendor.
Also, so far the flicker/crash issue I had under KDE didn't happen under GNOME (with experimental VRR enabled). It's too early to tell (only about a week into using GNOME), but this issue might not occur under GNOME. It's kind of hard to pinpoint what the issue is related to anyway (kernel, firmware, Wayland, KDE/desktop environment, etc.).
I reported the issue here: https://gitlab.freedesktop.org/drm/amd/-/issues/3268 and pinpointed it to weird fluctuations with the memory frequency. Just workaround so far though, no fix.