Fedora Workstation 41 is released! You can download Fedora Workstation 41 here .
Official Fedora 41 release announcement can be found here .
Installation Guide: Fedora 41 Installation on the Framework Laptop 16 - Framework Guides
Heads up on the Fedora 41 XFCE Spin: it has some kind of a kernel issue, or something that appears like a kernel issue, which is not present on the default F41 Workstation install (more below) which has the same kernel. TLDR: need a workaround to install the F41 XFCE spin, and installing all updates fixes the issue. I reproduced it on two different FW16’s, one from one of the initial batches, that I got late last spring, after a 4-month wait, and a new FW16 that was manufactured in October.
After booting the Fedora 41 XFCE Spin live image the keyboard /appears/ to be nonresponsive and typed text (into a terminal window, or at keyboard prompts in Anaconda) does not seem to be echoed back, or it may get echoed back after a lengthy delay.
After some experimentation I determined that this is some kind of an kernel I/O issue. If I move the mouse (or, rather, swipe on the touchpad), the accumualted text gets echoed back. So: I can type a bunch of stuff, wait a few seconds, touch the touchpad, and then all the typed text gets echoed back immediately.
This wasn’t affecting only keyboard input, but it also seemed to be affecting GUI operations too, although I have not narrowed down exactly what kind of UI activity gets “stuck”, until I touch the tochpad.
I was able to successfully install F41 XFCE Spin by, basically, dragging my finger across the touchpad, constantly, while Anaconda was copying the installation image to the HD. After the reboot the I/O issue persisted, but after installing all the updates, including a newer kernel, the problem went away.
I also downloaded the F41 Workstation live image, which has the same kernel, but which worked normally for me, and did not reproduce this issue. Only the F41 XFCE Spin live image is affected. I did not try any other spins.
This is interesting. I have similar problems since the latest kernel updates (6.11.x) on Fedora Workstation KDE Spin (KDE Plasma 6.2.x).
Most applications like Firefox behave normal, but e.g. in my terminal (yakuake) and when using video playback via mpv, vlc or smplayer, it is laggy (1-2 frames per second). While dragging the mouse/moving the mouse pointer during in the terminal/during playback everything is smooth.
This only happens on the internal screen. When I connect the Framework 16 to my ThinkPad USB Dock and use an external monitor everything is working fine.
I tried switching to a longterm kernel (6.6) using the kwizart repo: kwizart/kernel-longterm-6.6 Copr
For now video playback is smooth again (without moving the mouse). Would never have thought that this was some kind of kernel regression, but for the moment it seems like that.
You must be seeing a different issue.
What I saw was not a kernel issue. The problem did not occur with the F41 workstation live image which uses the same exact kernel as the F41 XFCE spin image that had the same kernel.
And my issue wasn’t run of the mill stuttering. Keyboard input was not being processed, at all, unless there was mouse activity. Not only keyboard input, but the spinner while F41 was actually getting installed was not moving at all unless I was moving the mouse.
OK, maybe you’re right and it’s a different problem. Or the problem only occurs in certain combinations of kernel version and desktop environment. Nevertheless, I had a very similar problem - even in the terminal, the written text was sometimes only displayed after a few seconds. On mouse movement, however, immediately.
It would be interesting to know which kernel version was used with the Fedora 41 XFCE Spin live image when the problem occurred. Was it the 6.11 or the 6.10 kernel?
The XFCE spin image used 6.11.4, same as the F41 workstation live image which has no issues.
So now we have:
-
same kernel, different desktop environments (me)
-
same desktop environment, different kernels (you)
After doing some more searching, I found this, which might indicate the same problem: Display freezes until mouse moves when upgrading above Kernel 6.11.2 / Kernel & Hardware / Arch Linux Forums
As of kernel 6.11.3, there seem to be these lags in some constellations - a user of a Framework 16 also reports there.
By the way, my Framework with the 6.6 kernel now also wakes up from standby without any problems which it didn’t with the 6.11 kernel.
Edit: Some more searching…
Might have to do with PSR (Panel Self-Refresh, power optimisation for laptop GPUs) which is activated in some environments while deactivated in others. Kernel > 6.11.2 might have introduced a PSR regression. This would also explain why I don’t experience the bug when connected to my external screen. That screen (or the connection to it) probably does not support PSR.
See this post (in the same thread as above): Display freezes until mouse moves when upgrading above Kernel 6.11.2 / Kernel & Hardware / Arch Linux Forums
Will test if adding the kernel parameter “amdgpu.dcdebugmask=0x10” will solve my problem for newer kernels when I find the time.
Have you tried to use a more up to date Live ISO:
https://dl.fedoraproject.org/pub/alt/live-respins/
Does it still happen with these newer ISOs?
Linux kernel 6.12.3 might contain a fix for this stuttering.
commit bd8a9576617439bdc907c9ce0875909aea4221cb
Author: Tom Chung (email redacted by mods)
Date: Tue Oct 29 17:28:23 2024 +0800
drm/amd/display: Fix Panel Replay not update screen correctly
Now that Kernel 6.12.4 is available on Fedora 41, I tried it. Unfortunately, no change. Video playback, terminal, etc. still stutters unless I am moving my mouse.
I then tried adding the kernel parameter “amdgpu.dcdebugmask=0x10” (see my earlier post), but again: no change. Went back to LTS kernel 6.6 and everything is working fine again.
Kernel 6.12 is the new LTS kernel, so I am not sure what to do. This is probably a major bug for users of the Framework Laptop 16 (and similar systems) with mobile AMD GPUs.
How can this be fixed? Where should I (and everyone else with this problem) report this?
1 Like
Kernel 6.12.5 still does not fix the issue in Fedora 41. Had to revert to LTS kernel 6.6.64. Please help!
I seem to be having the same issue with Fedora 41, the KDE spin.
I put the system to sleep and wake it it USUALLY resolves the issue. There are times it does not. I went ahead and did a clean install of Fedora 41, same behavior from time to time. I don’t get it but it has made the system all but unusable. I even tried it without the dGPU, reinstalled Fedora 41 with just the iGPU, same behavior. I’ll try the 6.6 kernel. Outside that I don’t know how to troubleshoot this as messages doesn’t seem to point to anything obvious.
Kernel is still too old. The bug was fixed later in the 1.12 series. I’m on Tumbleweed, had the same problem but that has been resolved for like a month now.
How can it be too old as Fedora now has the newest 6.12.11 kernel?
6.12.11 should include the fix, but the latest version I’ve seen here in the thread was 6.12.5, hence the assumption. Haven’t started any Fedora install (or Ubuntu) for half a year now. I’m on 6.13.0-1-default, but that’s due to Tumbleweed being a rolling release. It could be a Wayland issue, too, or KDE. I’m on X11 and XFCE4, respectively, so maybe compositor and/or desktop environment contribute to the problem.
.11 kernel was release like a week ago (23rd of January) so now wonder that posts from December are mentioning on older kernel.
EDIT: But yes, Fedora won’t get new kernel version before they have gone through the testing repo and automated tests (and user tests). Its usually about 5 days from release when they push it to stable.
Well in my case I reinstalled Fedora 41 with the KDE spin and brought it up to 6.12.11-200 and still had issues. So far after backtracking to vmlinuz-6.6.74-200.fc41.x86_64 I’ve had no issues in 24 hours.
The issue definitely has not happened in 2 days which it would have by now. The bigger issue is how do we figure out what the actual problem is? It’s speculated that it is Panel Self-Refresh. Uncertain how to verify that and where to report it? I don’t want to stay on an old kernel forever. 