You are not logged in.
Hello. I'm using machine translation, sorry.
I have a Lenovo IdeaPad 5 14ALC05 laptop with a Ryzen 7 5700U processor and integrated graphics.
Everything works very well on kernel versions up to and including 6.1.
However, starting from 6.2 and up to the latest versions (even on 6.7-rc3) there is a problem.
Essence:
In heavy graphics applications (games, for example), the image moves jerkily. That is, it doesn't look like just low FPS. Let's say, for half a second the image slows down, perhaps even freezes for a short time, and for the second half of a second the image seems to “catch up” with the scene and display the missing frames. And as a result, the total FPS seems to be “normal”, but in fact the movement of the picture is extremely uneven. I hope I explained clearly. I can record a video demonstration if necessary.
Conditions for occurrence:
In fact, there is a workaround for this error. To do this, you need to completely disable compositing in X11. For example, there is no problem if you run openbox without picom, or if you disable compositing in Plasma by pressing ctrl+shift+f12.
Also, for some reason there is no error and everything works stably in Xfce with compositing enabled and in Gnome on X11.
There is no error on Gnome with Wayland either.
In KDE Plasma with Wayland, the error is MUCH worse, the picture slows down several times more, and long (about 300-500 ms) freezes appear.
I tried kernel 6.2-rc1 (from an old version of linux-mainline) and the error was already there. That is, it appeared between 6.1 and 6.2-rc1.
I tried to manually install the latest stable kernel from kernel.org (6.6.3), compiling it according to the instructions from the "Kernel/Traditional compilation" article from the Arch Wiki, and there was also a problem there.
As I understand it, the problem is in the upstream and the bug is in the kernel itself, and therefore this question does not belong here. But, to be honest, I don't know what to do. The 6.1 LTS kernel won't be supported for very long, I can't stay on it forever.
Does anyone have any idea what my problem is? How to diagnose it effectively? Who should I report it to? I'm not a developer, I don't know how to use git, mailing lists, I have an extremely superficial understanding of the kernel development process, and where it's actually worth reporting a bug and what should be attached to it.
Asking on the forum is much easier and clearer for me. I can't fully check the English translation of my post, so I hope there's nothing inappropriate in it. Thanks a lot.
Offline
Do you have higher than 60Hz refresh rate? There are some known problems with this/VRR and you might want to try whether things stabilize by setting it to 60. Alternatively potential clocking/power management issues in the kernel module, try: https://wiki.archlinux.org/title/AMDGPU … cy_problem
Offline
I have 60 Hz refresh rate.
I tried:
echo 'high' > /sys/class/drm/card1/device/power_dpm_force_performance_level
And it partially worked. On Plasma X11, the frequent jerks are gone, but every 3-7 seconds the picture freezes for a very short moment. However, this is much better, thank you very much!
On Plasma Wayland it seems to have gotten better, but it's still very bad. Frequent and long freezes. It seems to be a complex of several problems.
Offline
After reproduction of the issue, can you post a complete
sudo journalctl -b
qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation
Offline
Offline
Also please
xrandr --verbose
Offline
Offline
Why is there no edid?
for OUT in /sys/class/drm/card0*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
You'll need https://aur.archlinux.org/packages/edid-decode-git
Offline
I don't have "card0", but i have "card1".
[aerites@alap ~]$ ls -la /sys/class/drm/
итого 0
drwxr-xr-x 2 root root 0 дек 2 10:31 .
drwxr-xr-x 79 root root 0 дек 2 10:26 ..
lrwxrwxrwx 1 root root 0 дек 2 10:26 card1 -> ../../devices/pci0000:00/0000:00:08.1/0000:04:00.0/drm/card1
lrwxrwxrwx 1 root root 0 дек 2 10:26 card1-DP-1 -> ../../devices/pci0000:00/0000:00:08.1/0000:04:00.0/drm/card1/card1-DP-1
lrwxrwxrwx 1 root root 0 дек 2 10:26 card1-eDP-1 -> ../../devices/pci0000:00/0000:00:08.1/0000:04:00.0/drm/card1/card1-eDP-1
lrwxrwxrwx 1 root root 0 дек 2 10:26 card1-HDMI-A-1 -> ../../devices/pci0000:00/0000:00:08.1/0000:04:00.0/drm/card1/card1-HDMI-A-1
lrwxrwxrwx 1 root root 0 дек 2 10:26 renderD128 -> ../../devices/pci0000:00/0000:00:08.1/0000:04:00.0/drm/renderD128
-r--r--r-- 1 root root 4096 дек 2 10:30 version
Here is the output of your command, where "card0" is replaced with "card1":
https://pastebin.com/CevVcWn0
Offline
Try to add this modeline:
Modeline "1920x1080_60.00" 147.840 1920 1968 2000 2200 1080 1083 1089 1120 +HSync -VSync
Display supports continuous frequencies
That seems wrong? VRR outputs typically advertise much higher frequencies, yours won't even do "naive" FullHD @60Hz …
https://wiki.archlinux.org/title/Variab … e#Overview
Check whether it's enabled and disable it in case.
Offline
I added this line to "/etc/X11/xorg.conf.d/modeline.conf", after a reboot xorg does not start. Did I do something wrong?
VRR appears to be disabled.
[aerites@alap ~]$ xrandr --props | grep vrr
vrr_capable: 0
vrr_capable: 0
vrr_capable: 0
Offline
If that's literally the only line you put there you created an ill-formed X11 config, yes.
https://wiki.archlinux.org/title/Xrandr … esolutions
Offline
I did:
[aerites@alap ~]$ xrandr --newmode "1920x1080_60.00" 147.840 1920 1968 2000 2200 1080 1083 1089 1120 +HSync -VSync
[aerites@alap ~]$ xrandr --addmode eDP 1920x1080_60.00
[aerites@alap ~]$ xrandr --output eDP --mode 1920x1080_60.00
And nothing has changed.
I don’t understand this topic well, sorry if I keep doing the wrong thing.
Offline
You'd probably at least restart the compositor afterwards.
xrandr now suggests the proper mode is used?
b. that this is unrelated to the GPU nor powering up, https://bbs.archlinux.org/viewtopic.php … 1#p2134691
Offline
I don't know why, but I can't set the created mode "1920x1080_60.00", the mode "1920x1080" is selected instead. I restarted compositor, it didn't affect anything.
And by the way, at the beginning of the thread I said that it helped me a lot:
echo 'high' > /sys/class/drm/card1/device/power_dpm_force_performance_level
Now I rechecked, but for some reason it didn't work now. Very strange, I'm confused myself.
In fact, I still hope that there will be no need to work around the bug in the future. Now I'm thinking of just staying on 6.1 LTS. Still, as I understand it, the problem is known?
Offline
I can't set the created mode "1920x1080_60.00" … for some reason it didn't work now
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Post the commands you tried, the response (errors) and the impact on the xrandr output resp. the contents of "power_dpm_force_performance_level".
Offline