-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display Corruptions with KMS and Overscan Margins on the RaspberryPi 4 #4475
Comments
Yes, we can see that here |
Also noticed that top right corner causes:
|
For the record, I noticed this this morning while debugging something else and just opened the issue so that it doesn't get forgotten. |
I'm finding that when the mouse is stationary everything is ok. However, if it moves and is within 62 pixels of the bottom or right edge then the corrupt appears. |
A possibly related issue is with kms, and two displays, from desktop rapidly switching mouse pointer between displays results in occasional glitches (on the framebuffer). It doesn't seem to be clock related (forcing it high doesn't avoid it). |
I've reverted most of #4441 and the screen corruption when cursor near edges and glitches when mouse pointer switches screens issues are gone. |
This should be resolved with latest rpi-update kernel. |
I reverted your revert and tried to fix all the pending bugs we had. I've been working on this one today and followed the suggestion from @timg236 on #4465 that it might be related to the core clock being too low on 4k. I'm seeing this on 1080p, but I still raised the core clock to 500MHz which is more than the double of what is computed (220MHz). I'm still getting both the corruptions (even though I'm getting less corruptions, possibly from my other fixes), and some timeouts. Moving the cursor in itself (using xdotool mousemove) doesn't trigger it, so it looks like it's the sequence of commits when moving the cursor that triggers it. |
For the record, this also affects rpi-5.15.y with a single display |
This was fixed by the PR #4895 |
Moving the cursor along the edges of the display creates some visual artifacts when disable_overscan isn't set.
To reproduce
Build a kernel based on current the rpi-5.10.y branch (7aa66c0 in my case), start X and move the cursor along the edges. Complete corruption of the display should occur.
Adding disable_overscan=1 to config.txt makes it behave properly.
The text was updated successfully, but these errors were encountered: