I have been gaming on my framework 16 without the dGPU for a while now without much issue. I’m on Arch with KDE Plasma (6.12.1-zen1-1-zen kernel). I just got the dGPU 7700s upgrade, and after some testing, found that whenever I launch a game that opens in fullscreen the game runs fine but my screen freezes, often at a black image with a cursor. I can hear audio in the background, and sometimes I’m able to hit the super key to pull up a task bar. The moment focus is lost on the window the screen unfreezes. Sometimes I can’t seem to give any input, and even switching to another TTY takes a long time.
I wasn’t having any of these issues on the 780m chip, does anyone have some troubleshooting/fix suggestions for me?
So far I’ve tried disabling adaptive sync and disabling the enter fullscreen animation.
I’ve also noticed that the gpu stats don’t appear in mango hud, but that’s likely a separate issue.
Update: I have determined that Gnome does not seem to have this issue.
I also noticed that mangohud properly displays GPU information on gnome, whereas it doesn’t on plasma. Could this be related to the gpu drivers in use?
Weird, I did some more testing in gnome, and when I came back to plasma I stopped having the issue. While I’m glad I’ve been able to launch some games and at leat benchmark the 7700s, if I don’t know what fixed it I don’t know why/how it was broken before, and it may break again at any point.
Edit: To little surprise, the issue returned with little indication as to why.
I’ve been having this issue for now. Is there a bug report filed somewhere so that people can know about this kernel regression? Would be good to get it fixed soon.
As a side note, I’ve found running games through gamescope appears to fix things as well, if you’d rather do that instead of a kernel downgrade.
It’s pointless to report a bug without any useful information. I have no idea what causes it, I just know it happens.
Also, not sure if this is truly a bug introduced by AMD kernel team, or Kwin uses an obsolete/bad way to access GPU, or some issue specific from Framework itself (BIOS/hardware)
Using kernel 6.12.1 also gives me random artifacts at screen. Not always, but happens.
We could try and do a kernel bisection to figure out the exact change that causes the issue. I’d say that’d be useful enough information for a bug report. It’s not a process I’m all too familiar with, though, but I’ve seen it done before to pinpoint similar issues.
It seems to me this problem starts where this problem ends.
I don’t think it was properly fixed, or it caused another problem.
That update broke Ultimaker Cura, saying “This program requires OpenGL 2.0 or higher.”
As per a guide i found about the same issue on windows, I’ve deleted all of its files i could find, aside from the appimage itself, but it has no effect.
With this new problem, I used to mainly get temporary screen freezes whenever a fullscreen game has literally anything displaying over it. it got worse over time with consistent permanent freezes, but setting the display refresh rate to match the game and disabling adaptive sync made it only temporary again.
I still get freezes on vlc too, although more rare than ever now.
Worst thing is that nothing shows up in crashed process viewer this time.
If you’re getting content not updating when launching (certain) games fullscreen, but can sometimes bring up the start menu (which makes the game display again), you might be enjoying this particular bug: [BUG] [PSA] : GPU bug causes crashes on KDE Plasma.
For some folks the KWIN_DRM_NO_DIRECT_SCANOUT workaround seems to be fine, for me it doesn’t help at all, and when I play games that struggle like this I’m switching to swaywm for now (or you could use Gnome) until the bug is resolved.
I’ll give that environment variable a try later. I have my doubts about it being the same issue, though, as that seems to have been a problem for much longer than this has. As others already mentioned, this issue didn’t exist before kernel 6.11, and it looks like that issue has been around for months (maybe years?). 6.11 was released before that post was made, but I don’t think most distros were on it yet… iirc fedora wasn’t, at the very least. But someone else in the thread mentioned the issue being around for 2 years. Could be related, but I’m unsure.
I wasted away my weekend grinding out some raider.io in WoW, and learned a couple things about this issue I’m encountering. It appears to be quite inconsistent. I was able to launch a game fine twice in a row, but then on the 3rd launch some time later it failed at the frozen black screen. A reboot allowed me to successfully launch once more, but it appears to me as if whether a launch will be successful or not is entirely random, and if it fails, it will always fail until something changes (e.g. via a reboot).
I am more than happy to provide logs for a bug report, but I do not know what logs to grab.
Alright it’s been a while but I finally tested the environment variable change and it had no effect, issue is still there. So seems to be a different issue as I suspected. Also updated bios and drivers today because that update appeared and it did nothing too. Still thinking it’s a kernel issue. Unfortunately I can’t really downgrade to 6.10.9 because that version was never built for fedora 41.
It is a Wayland issue, but not sure if KWIN is responsible. I think something changed from AMDGPU and broke KWIN in the process. The issue only happens after 6.11.3 or 6.11.4.
But I do prefer wayland because X makes my life miserable with VFIO GPU. It crashes because it doesn’t disconnect properly as Wayland does.
Installed some old kernels and found 6.11.3 works fine but 6.11.4 does not, so hopefully that narrows things down a little.
I know we don’t have a ton of info - but I do really think we should report this regression somewhere. Seems like a pretty major issue to me and kernel regressions are generally taken quite seriously.
edit: looking into doing a kernel bisect now to narrow down the issue further, if I can find an exact commit that caused the issue I think that would be more than enough to report.
Is this only happening to you with the dGPU? I’m having similar issues but also with the iGPU. I’m using Fedora 41, so I’m also on a very new kernel and tried it today on Ubuntu 24.04, which worked fine. I only noticed this issue after upgrading to the 03.05 firmware. Maybe it is also related to that. What firmware are you on?
I was having the issue before the 3.05 firmware/bios update as well, so there’s that. I’ll see if I can run the game off the integrated graphics later - currently in the midst of the kernel bisection which takes a while.
