search for: scdc_tmds_config

I have a Gigabyte GeForce 1050 connected by DVI to a monitor (1920x1200 resolution @ 59.9502 Hz) and a TV via HDMI (3840x2160 @30 Hz). The problem is the TV used to work at 59.9685 Hz but then it started showing "No signal" on the TV. I was changing settings trying to get it to work again and I happened to change it to 30Hz and it worked. The specs are here:

This is the beginnings of HDMI 2.0 support. All of the "extra" features are left out, such as 12/16bpc, YUV420, etc. I've verified that with this code, a GP108 (GT1030) can switch between 4k at 60 and 1920x1080 at 60 on a LG 4K TV. Further, I've verified via i2c tools, that the SCDC writes really do happen. I suspect that the patch for keeping track of the high-speed TMDS

...ou turn the TV on, it doesn't work. In order to remedy this, you need to disable the display linux-side, and re-enable it. The indicator for this sort of issue would be something about SCDC reads/writes failing in dmesg -- do you see anything of the sort? (Something like "Failure to write SCDC_TMDS_CONFIG") If not, it's probably something else. But this seems like a likely candidate. On Tue, Aug 6, 2019 at 12:14 PM James <bjlockie at lockie.ca> wrote: > > I have a Gigabyte GeForce 1050 connected by DVI to a monitor (1920x1200 > resolution @ 59.9502 Hz) and a TV via HDMI (38...

...sn't work. In order to remedy this, you > need to disable the display linux-side, and re-enable it. > > The indicator for this sort of issue would be something about SCDC > reads/writes failing in dmesg -- do you see anything of the sort? > (Something like "Failure to write SCDC_TMDS_CONFIG") > > If not, it's probably something else. But this seems like a likely candidate. There is nothing in dmesg. Maybe nouveau needs a module parameter for debug logging? I'm going to try a different cable anyways. Is there something in /proc to check if "scrambling" is...