The new FL13 arrived a few days ago, which I’ll be daily driving for a few weeks while waiting for my FL16 and then set up for my sister.
I also experienced flickering/strobing at 30Hz between full screen white with few black spots and my normal screen. It happened after returning from sleep or launching for example rocket league, both in Plasma and hyprland (both in Wayland, didn’t try it in X11). Luckily I’m not epileptic, that was really intense.
Since I’m on arch, I already was on the newest kernel (6.7.5, upgraded to 6.7.6 in between), added the kernel parameter and switched to the game mode in uefi.
After using it for a day, this seems to have fixed it!
The only issues remaining are a double tactile click in the bottom right of the touch pad (might contact customer support and fix it with some tape on the bottom or sth) and rocket league only launching to a black screen.
Not sure if my Rocket League issue relates to any of this, but I’ll just ask anyways.
Basically the game launches and stays black - it still runs, as I can hear music in the epic games version that definitely comes from rocket league. It doesn’t crash, but I found the logs in the proton prefix and the only issue they state is “Timed out while waiting for GPU to catch up. (500 ms)”.
Also, Dead by Daylight runs at less than 1 FPS, while loading two cores constantly. Using nvtop I saw that the dedicated 4GB of VRAM are almost full, but it should be able to allocate up to 32GB of my 64GBs of RAM (which mostly were unused). I might try to change the clock speed from 5600MHz to 4800MHz and/or use memtest to check its stability. However, I doubt that this is actually the issue.
Is this the right thread to ask? Otherwise I’ll start a new one for this specific issue.
Well I’m back. It’s been a while but I have had graphical corruption issues again. It started a few weeks ago, but I’ve been to busy to post. When I posted the first time the specific corruption I had looked like what mopac posted in October (white blocky artifacts). In order to get rid of them I would have to restart my computer. They occured more often when the computer had been powered on for a few days. amdgpu.sg_display=0 ultimatly fixed it and I haven’t had any issues for months.
This new graphical corruption looks more like what tokanda posted (colorful and with a seemingly more random distribution with minimal banding). It does not seem to matter how long my computers been up. And I don’t experience it often. I have only seen it happen after suspend or after my lock screen appears due to idling. Also this version of corruption has gone away without me restarting the computer just by letting it sleep after idling (but that behavior is not consistant). It also doesn’t happen very often (I’ve seen it probably 2 or three times.) and I have no idea how to reproduce it.
@Kenneth_L_Rountree I presume you are running an Linux Kernel earlier than 6.8. A lot of fixes for AMDGPU have gone in for 6.8 and i’m running without “amdgpu.sg_display=0” for a few weeks now and haven’t had any issues in this regard anymore…
@Kenneth_L_Rountree Well, i’m on NixOS and have been running release candidate kernels for the 6.8 series, but it is released now and i imagine, it should appear pretty quickly in the fedora repositories… I’m running 6.8.1 now to be precise. Perhaps also of interest for other users: It appears that there is no need to run with “rtc_cmos.use_acpi_alarm=1” anymore, since, iirc, this has become the new default for AMD systems also, thanks to @Mario_Limonciello. Getting there, IMHO…
I was encountering display strobing similar to what is described here, in addition to GPU hangs when playing 3D games, on Debian 12 (thread on the latter issue), even after backporting the kernel and firmware, and I suspect it’s a related issue. Working around it, for me, required both updating Mesa to a newer version than Debian provided (I eventually just moved to Debian testing), and setting the kernel parameter amdgpu.sg_display=0. I also turned on UMA_GAME_OPTIMIZED in BIOS settings at around the same time I set that kernel parameter.
Thanks Mario,
I’ve pulled Debian’s Trixie firmware packages and the git kernel repo for firmware and copied it in on my current kernel, updated initram and rebooted.
You’ll see 6.8 in fedora 40, since thats the active branch most 6.8 kernel builds will be there, FC 40 beta was postponed to 3/26. 6.8.0-63.fc40.1.x86_64
I still manage to trigger it on each suspend with UMA_AUTO and amdgpu.sg_display=0 unset, I have also been able to reliably trigger it by changing gnomes scaling offset.
This is great news! I’ll remove it and try the suspend script again and see if it passes.
On Rawhide (40) and 6.8 kernels I have been able to trigger it with sg disabled and UMA pumped to 4GB when I am using HDMI external display.
I was running a tradebooth screen off my Framework 13 a couple of weeks ago and managed to get it to trigger with disconnects/reconnects of the external screen. The eDP panel remained unaffected but I got the familar whiteout/banding on the external display after a couple of plug/replug events.
I also still occasionally observe the white-screen flashing on Arch, which is currently on kernel 6.8.1, with UMA_GAME_OPTIMIZED enabled.
I need to do more testing to find out what, exactly, triggers it, but I’m leaning towards external monitors, XWayland, and/or GPU intensive applications (such as MS Windows games, which perhaps not coincidentally also tend to use XWayland). It would be interesting to find out if I can still reproduce the issue with Wayland native apps.
Also pointing out that switching back-and-forth between TTYs (ctrl+alt+F2/F3/F… in Gnome; or sudo chvt 2 on the terminal, where chvt 1 should switch you back) will generally restore stuff to normal. sudo systemctl soft-reboot also tends to work, but that tends to cause my wifi device to be unavailable.
This thread is becoming way too long, is there a place that give the current status and the possible workaround ? in the KB for instance ?
Just to say also under fedora 40 the graphical corruption is get worse.
the key combo I used were ctrl+alt+F3 then ctrl+alt+F2.