I had RGB static similar to what you have, after I upgraded my mainboard from Intel 13th gen to AMD 7640U. In my case, disconnecting and reconnecting the display cable to the mainboard fixed it. I see you already tried that, though, so I have no other suggestions.
At any rate, I would think this isn’t a software issue (i.e. it’s not an issue with the distro or the kernel or the display drivers), but instead a hardware issue.
RGB static still exists tho. What other debugging techniques can I try?
I’m still skeptical of the possibility of a hardware issue because of the Manjaro Linux link from above mentioning some fix in Kernel 6.6.
Same with Fedora 39 (since I have an empty disk, why not try installing all the things! (separately, with erasing))
I think the only last thing I can try is to try to rule out if it’s a display issue by temporarily connecting the display from the other frame.work laptop to this one’s mainboard, and seeing if the problem is the same (which would reveal display is fine, mainboard or software has issues).
I just created a ticket a few minutes ago with the same symptoms.
Difficulty: I use Windows 11.
It seems fine until Windows takes over. Then I get RGB static all over the place. I wondered if it might be grounding, so I removed and reinstalled screws to see if that might help. It seemed to help a little?
I also noticed that external displays are not affected, including Displayport displays via MST. Digitally-speaking, everything seems fine.
I also see RGB (mostly green, some red) static on the laptop screen, not on external monitor. Not really noticeable except on solid black screen, so more of an annoyance. Does seem to be load-related, if I start something up to saturate all the CPUs it becomes much more noticeable, even on a normal screen with a lot of things going on.
Here is a video of System Monitor and a black background. You can see the static intensify under load. I’m running a parallel version of Conway’s Life written in rust to saturate all CPU cores. https://gitlab.com/makr17/rust-life
The first two attempts don’t last very long, but you can see the static spike (the program found a cycle and exited). The third attempt ramps up the CPU nicely and you can see the static intensify with it and stay strong. Video demonstrating the issue
I’m not sure why Google Drive’s Preview won’t play the video, I shot it on one of their phones (a Pixel 8).
If you can try taking some very focused (tapping the phone screen) photos, perhaps I can see this better. I have tried watching the video provided and I am not seeing the green and red on the laptop screen. I’m sure it’s there, I am just not seeing it in the video.
This looks good, this is correct.
When you repeat this process, try doing so two terminal tabs open:
sudo dmesg -w
We should see some activity happen pretty quickly when you repeat the steps to create the issue. In a pinch, using these real time follow modes allow us to see where the error appears to be happening pretty quickly. Also saves us digging through the logs looking for the event as we can catch it in real time.
Based on the images and the lack luster logs, plus assuming that was supposed to be a solid dark/black screen, that looks like a bad screen connection or a screen itself. Please file a ticket and link to this thread.