this post was submitted on 19 Nov 2025
29 points (89.2% liked)

Linux Gaming

22180 readers
917 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

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia@lemmy.world
29
Fedora and AMD GPUs? (lemmy.ml)
submitted 2 days ago* (last edited 13 hours ago) by benagain@lemmy.ml to c/linux_gaming@lemmy.world
12 comments fedilink hide all child comments
 

I picked up an AMD 9060 XT the other week and tested it out by dual-booting Bazzite. Helldivers 2, TRYP FPV Drone Racing, Mud Runner all ran as expected, it was wicked.

"Nice," I thought, "This works great, time to boot back into Fedora."

And... not so nice? Apparently Fedora doesn't have hardware acceleration when using AMD GPUs and a bunch of the apps I normally use are whinging about it. It was fine with the older NVIDIA card I had been using but I wasn't getting the performance benefits of gamescope.

Dabbled in the dark arts of trying to swap mesa drivers to the freeworld one and ended up nuking my login screen so probably going to have to roll back. I thought Bazzite was based on Silver Blue so kinda confused, I guess they've done some AMD-friendly tweaks?

Edit: Thanks for all the help everyone. I was on Fedora 42 and after installing updates today it started working again. I really wish I new what specifically was causing the issue.

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 3 points 13 hours ago* (last edited 12 hours ago)

Nope, KDE doesn't deal with anything at the driver level. Pretty sure it was a combo of removing the Nvidia packages, and then you probably got a kernel update which forced the kernel modules to rebuild and it detected and included your new AMD hardware.

This is normally done automatically, HOWEVER, if you have something like the Nvidia stack of drivers on your system, you can get weird behavior because the package maintainers pull all kinds of ugly tricks to force Nvidia bits and pieces to stick to where they need to be.

In the future, you can trigger a sort of rebuild with whatever your running kernel is like so to force changes: https://brandonrozek.com/blog/rebuildkernelakmod/

This is probably what happened when you did that update, and it refreshed the device table and made sure the AMD modules were loaded properly.