unable to run games
I just had a fresh install of Bazzite on an all AMD system with the gigabyte b550 mainboard and the Rx 6700 xt.
When I try to play a game (no matter if Gamescope or desktop) my GPU is always at 99% and I’m below 20FPS no matter the settings. On other distros the same setup performed much better (60-120FPS on same settings).
Someone already mentioned in the general chat that there is some weird bug with the latest drivers that underclock VRAM and I‘ve followed the instructions from their link to no avail. It seems the issue is related to something else. Especially because my vram goes to above 100Mhz unlike for the people affected by that issue.
33 Replies
I‘m on the Steam deck version btw 🙂
I noticed the Mhz value never goes above 500 it seems to be capped there… could that be the cause of this issue?
okay it appears my MCLK (whatever that is) is capped at 96 and that is supposedly bad is what i have gathered from this thread:
https://gitlab.freedesktop.org/drm/amd/-/issues/2657
No clue what to do about it though...
GitLab
6.4 kernel mclk stuck at lowest on rx 6900 xt (#2657) · Issues · dr...
When I updated to linux kernel 6.4 my amd gpu rx 6900 xt is now stuck at 96 mhz mlck. Before it was always at max mhz which...
It is being suggested to downgrade or upgrade to another kernel version to hope the issue does not exist there… is that even possible on Bazzite? If so, how would I go about doing that?
how is that happening on an AMD system?
It's not right now. I've seen other cases of this. Unfortunately everyone's going to have to wait for a kernel update
6.5 should land relatively soon
is this also an issue on the steam deck too?
No
what systems does this affect then?
Iirc it occurs at random. I've only seen reports from people running RDNA 2 cards
is it a bazzite issue or is it something with the kernel?
Oh fun. 6.6 it is
Kernel issue
If we could backport that patch as an akmod, it would be awesome
but I doubt it
I'm not sure that's easily done
I wasn't sure if it was a really weird bazzite only issue again
Yeah. Not us. It's the kernel
Unfortunate something so big missed the window
on the 3 dots menu button, go to the mangohud/performance tab and lock the TDP and then switch from 15 to 14 to 15w
oh, this isn´t a steamdeck... my bad
@KyleGospo I setup a Fedora distrobox, layered Steam after setting up RPM Fusion, and I was able to launch Elden Ring unlike before and run Portal (I didn't have the fix so the title screen is all buggy, but it does launch)
I'll try in a vanilla Arch distrobox next here in a couple hours
are you testing it on an NVIDIA system?
Yes. 3070
Running into the same issue on vanilla Arch. I was reading the Arch wiki and apparently the Nvidia driver doesn't like having other versions of Vulkan installed. The problem here is since Nvidia utils is just copied to the container, pacman doesn't know it's there so when installing Steam it asks to install it, which, as a result, doesn't work since the files are already there
if that's the case, merely clearing out the vulkan icds should fix it @EyeCantCU
if it does we can integrate that into our setup
we can even do a separate -nvidia image to make it easier
if needed
Deleting the other ICDs had no impact :/
can you confirm that normal arch + steam with nvidia drivers selected during install works?
if that does we can work around this with a new image
Yes. I can test that tonight
ty
sorry, wish I could help here
It's okay. I just want to see this fixed. It's weird it works under a Fedora distrobox but not under Arch
are you using distrobox-git?
Yeah
ok good
With all the ICDs there too looking closer
there should be a separate NVIDIA container image that doesn't use the --nvidia flag since it is already included
--nvidia will still be needed
the driver versions have to match exactly
(thanks nvidia)
Lol. Thanks indeed
archinstall has made things way easier
Not that they were bad