I don’t know what to call this so I will just call it flickering. I think there is a disconnect with the Nvidia 520 drivers and the refresh rate on my Gigabyte M32U (4k-144hz)…
Using Ubuntu MATE and the Proprietary driver 520… Refresh rate of 144 doesn’t appear in the driver settings. Have items like vsync on.
For some reason the driver is identifying the signal as “TMDS” as opposed to HDMI
I apologize, I don’t know what happened. I was able to bypass getting locked up at boot by using my iGPU as the primary graphics device. I could no remove nvidia packages due to an issue relating to nvidia modules (kernel?). for whatever reason, I updated my system of which included a kernel update and I was able to roll back to the working nvidia 510 driver…which now reflects 144hz… what the hell am I doing…I need a better understanding of these things.
Technically everything in a modern PC is TMDS.
I hope that’s something as simple as drivers. I’d be worried it’s hardware level artifacting. Had a problem with that recently, made recordings, notice problem, watched recording and notice even more instances similar to that.
Is that Gimp? I’d probably call it texture flicker.
Is it a card that allows clock adjustments? Drop them to the floor and see if it still happens. If that fixes it, the GPU is going out. If that doesn’t fix it, might still be going out.
Pretty screwed though. There is a bug in the older driver that caused excessive power draw at idle, 80-100W for me and the newer one, well it’s not working well with my M32U.
Can’t get refresh rates above 60hz pretty pissed.