Hello,
On 545.29.06 I get no signal on a wayland session on my HDMI 120hz TV, while on the latest vulkan dev 535.43.20 that is not an issue.
what is interesting is that the logs do not indicate what seems to be the problem.
EDIT: Small update this also seems to be broken under an xorg session as well. Additionally this seems to be only when the display is 4K@120hz, on 1440p@120hz it’s fine
Hi @amrits and @kodatarule, this issue has persisted for me on 550.54 and 550.67. Manjaro, kernel 6.7.10. I’ve had this issue on Pop OS and Fedora as well (545/550 drivers).
120hz simply fails on both X11 and Wayland. EDID is good, 120hz worked on live CD with 535.
@agoinshdmi_deepcolor=1 fixed my issue, I haven’t seen any driver updates so I would prefer not to remove it. I am using an LG C2 over PC mode with Deep Color: 10bit RGB, 3840x2160@120 VRR.
I can confirm that specifying nvidia-modeset.hdmi_deepcolor=0 as kernel module parameter does help 120hz to work now, but 144hz still is mish mash, it is a Samsung TV 43 inch QN90B model.
Hi @kodatarule
I retried repro lately on Arch Linux with display model LG 27GP95R with resolution 4k and refresh rate as 120 Hz and 144z respectively but could not repro issue.
I will check internally for TV which supports 4k and refresh rate as 144Hz and will reattempt for local repro.
Perhaps the Issue could be related to hdmi 2.1 connection, that is how I’ve hooked up my TV, on windows 144hz works(when I tested with usb preinstalled environment) but on linux same cable, starting from 550 on both X11 and Wayland I get 80% of the screen is black or glitched and some snowflakes at the top when I choose 144hz, while 120hz is just fine.
EDIT: Forgot to mention that I do need to specify the earlier environment var nvidia-modeset.hdmi_deepcolor=0 to avoid issues with 120hz mode.
Hi,
I tested with 565.77 - 120hz even with hdmi_deepcolor=0 doesn’t display anything but I can set it in settings just fine, 144hz freezes kde plasma and I cannot access tty even.