Any update on this? I don’t know if I’m having the same issue or just something similar, but occasionally my screen will freeze, requiring a reboot. Any playing video/audio keeps playing as normal, but the screen is static (although no artifacting, etc.) I will note that whenever I first boot up and log in, there is a row of pixels on the top of the screen that flicker (typically blue) for a few seconds, and the screen may temporarily freeze for a few seconds, but usually within 15 seconds of boot and login everything works. The issue generally arises after waking from suspend which is usually when a hard reboot is needed. Can’t tell if this is a Wayland issue or a suspend issue or a hardware issue.
OS: Fedora 37, no LUKS, fairly stock install
Framework: 1240p + WD SN770 + 32GB 3200 + 4x USB C
Dont forget a reboot to make these changes active!
While my freezing IS fixed with psr=0, is that the correct command? I’ve got this following line in my notes from November (and mentioned around that time in this thread), and is the one i’m using. Is it different, or is one an alias of the other so effectively the same?: sudo grubby --update-kernel=ALL --args="i915.enable_psr=0".
…And just incase anyone would like to revert this change back to default (psr=1): sudo grubby --update-kernel=ALL --remove-args="i915.enable_psr=0"
One of essentially a more generic form of the other. I tested the one I posted, but yes, if someone wishes to have the less generic version, i915.enable_psr=0 works as well.
In my testing, the suggestion I made works, but ideally, either should accomplish the same with the graphics on 12th gen.
After having read through the whole thread I am still confused which kernel parameters might fix the problem (at least as a workaround). I found these possibilities on the Internet:
i915.enable_dc=0
i915.enable_psr=0
i915.enable_guc=0
Some people claim that enable_psr=0 solved the problem, while enable_guc=0 is mentioned in the Arch wiki.
I don’t want to blindly apply all of them since they disable features which are there for a good reason.
So, which one should I try first?
Fortunately the GPU freeze occurred only twice last week. The laptop is fairly new (bought/installed it 3 weeks ago, no problems in the first two weeks and then two freezes last week). The consequences were unpleasant: kwin_core crashed and I had to kill Xorg from a tty.
Mine has been behaving since the last time I checked in. I spent a solid workday teleworking over VMware Horizon, and it handled all of that H264 decoding just fine. I even paired a Keychron K2 and my Bluetooth ear buds… streamed music all day and banged out some YAML. No issues or freezes.
I will say, having followed some of the side discussions in this thread, that the Xorg/Wayland thing was a rabbit hole that I jumped down. What I found during my testing with a few different games at the time was that Xorg, while a little more stable, was not anywhere near as responsive or snappy as the Wayland session. I was able to reproduce crashes under both of them (F36, before I upgraded). This was also in both KDE Plasma and Gnome. I’ve had it crash in both desktop environments just by messing with each respective settings app.
The only thing that has consistently provided relieve from the crashes is the kernel option for the i915 module. I’ve also been seeing the same kind of feedback from folks who own 12th gen Intel laptops from other brands (Lenovo specifically). We even had a kernel regression at one point where they broke us and we had to wait for another update before i915.enable_psr=0 took effect again. I’m pretty sure this isn’t Fedora-specific or desktop environment-specific. It’s definitely not manufacturer-specific.
i’m with aggraxis on this; the fixes have all been coming from upstream kernel/mesa packages and not specific to Fedora. Thankfully due to Fedora’s ethos, these fixes have come frequently and i’ve had the same experiences as Matt_Hartley; 1240p, fully upto date Fedora37 KDEspin… psr=0 fixes it and it’s rock solid.
I’d rather have working PSR too, but stability > whatever battery life improvements PSR brings.
I’m getting hard freezes with similar scenario to @JHeffron
KDE Fedora 37, Linux 6.1.9, default KDE Wayland
12th gen Framework with a 500GB Samsung SSD
This happens so far when playing a low-intensity game (Corporate Clash) via WINE. Other than when playing games, it doesn’t happen, which is much better than my experience with Fedora Gnome, which incurred freezes like this all the time, doing basically nothing.
@nadb Oh you can ignore touchegg, I had it installed cause I was testing X11 session to see if it behaved better, and I guess I didn’t fully disable its backend before starting this Wayland session. I got the exact same crash before installing touchegg, so I highly doubt that’s part of the problem.
I got that error over and over for the entire couple hours prior to the crash in the log. The timing just looks suspicious
