HDMI 2.0 4K @ 60hz 4:4:4 TV problems on 352.09?

Graphics / Linux Linux
1

Why wouldn’t 4k @ 60hz work on 352.09, I thought it was fixed on 349.12?

Update: I was using xrandr 1.1 style on 1.2, the defaults black screen because of the issue with 4K @ 60hz.

[s]Has anyone tried doing anything in Linux with Nvidia proprietary non-free drivers and a 4K hdmi 2.0 display, particularly a Samsung TV. I’m amazed that I haven’t seen a single bug report on the matter. I’m working on one but it would be nice to know if anyone else can replicate it.

Essentially, doing anything on any distro with any proprietary driver 340-352 will black screen on HDMI 2.0 with a 4K TV.[/s]

2

There’s been couple of threads for that already. For working 4k60Hz over hdmi you need at least 349.12 beta driver.

i.e. Check this thread:

3

I’m using the 352 driver. I have a Samsung UN55HU6950

Will look into it further with logs later today. Hopefully 353 works @ 60hz. I bought some adapters to use the DVI and Displayport connections. I also moved my computer closer to the 1080p TV for testing… that one works flawlessly.

UPDATE: I was using xrandr 1.1 option style. But I still can’t get 4K @ 60hz with HDMI 2.0 on driver 352.09

Strange, I get no output when connecting to an HDMI 2.0 4:4:4 TV whatsoever, even if I tell xrandr to -s 1920x1080, it fails to set the resolution. Tried all ports on the TV, nothing. Same thing with 720p.

4

[url]https://cf05b0be643f49f11ecf58cf79e765768b62d422.googledrive.com/host/0BzxXaPUM9KPJNFdOcDl3WjlxaTA/nvidia-bug-report-349.16.log.gz[/url]

[url]https://cf05b0be643f49f11ecf58cf79e765768b62d422.googledrive.com/host/0BzxXaPUM9KPJNFdOcDl3WjlxaTA/nvidia-bug-report-352.09.log.gz[/url]

Bug report for when switching to 4K at 60hz. My display does support 4:4:4 and I had all the correct settings to do that, aka “UHD Color” and the “PC” input name.

The first dump is for 349 on ubuntu
the second dump is for 352 on ubuntu

My OS of choice is Fedora though.

5

xrandr --verbose: shows its supported .

HDMI-0 connected primary 3840x2160+0+0 (0x1e0) normal (normal left inverted right x axis y axis) 1110mm x 620mm
Identifier: 0x1d6
.
.
.
_ConnectorLocation: 4
3840x2160 (0x1d7) 594.0MHz +HSync +VSync +preferred
h: width 3840 start 4016 end 4104 total 4400 skew 0 clock 135.0KHz
v: height 2160 start 2168 end 2178 total 2250 clock 60.0Hz
4096x2160 (0x1d8) 593.4MHz +HSync +VSync
h: width 4096 start 4184 end 4272 total 4400 skew 0 clock 134.9KHz
v: height 2160 start 2168 end 2178 total 2250 clock 59.9Hz
4096x2160 (0x1d9) 594.0MHz +HSync +VSync
h: width 4096 start 5064 end 5152 total 5280 skew 0 clock 112.5KHz
v: height 2160 start 2168 end 2178 total 2250 clock 50.0Hz
4096x2160 (0x1da) 296.7MHz +HSync +VSync
h: width 4096 start 4184 end 4272 total 4400 skew 0 clock 67.4KHz
v: height 2160 start 2168 end 2178 total 2250 clock 30.0Hz
4096x2160 (0x1db) 297.0MHz +HSync +VSync
h: width 4096 start 5064 end 5152 total 5280 skew 0 clock 56.2KHz
v: height 2160 start 2168 end 2178 total 2250 clock 25.0Hz
4096x2160 (0x1dc) 297.0MHz +HSync +VSync
h: width 4096 start 5116 end 5204 total 5500 skew 0 clock 54.0KHz
v: height 2160 start 2168 end 2178 total 2250 clock 24.0Hz
4096x2160 (0x1dd) 296.8MHz +HSync +VSync
h: width 4096 start 5116 end 5204 total 5500 skew 0 clock 54.0KHz
v: height 2160 start 2168 end 2178 total 2250 clock 24.0Hz
3840x2160 (0x1de) 593.4MHz +HSync +VSync
h: width 3840 start 4016 end 4104 total 4400 skew 0 clock 134.9KHz
v: height 2160 start 2168 end 2178 total 2250 clock 59.9Hz
3840x2160 (0x1df) 594.0MHz +HSync +VSync
h: width 3840 start 4896 end 4984 total 5280 skew 0 clock 112.5KHz
v: height 2160 start 2168 end 2178 total 2250 clock 50.0Hz
3840x2160 (0x1e0) 296.7MHz +HSync +VSync *current
h: width 3840 start 4016 end 4104 total 4400 skew 0 clock 67.4KHz
v: height 2160 start 2168 end 2178 total 2250 clock 30.0Hz
3840x2160 (0x1e1) 297.0MHz +HSync +VSync
h: width 3840 start 4896 end 4984 total 5280 skew 0 clock 56.2KHz
v: height 2160 start 2168 end 2178 total 2250 clock 25.0Hz
3840x2160 (0x1e2) 296.8MHz +HSync +VSync

6

It does show that it is supported and makes it the default resolution at login, but it won’t display at all. I ran the reports right after running the xrandr commands and getting the black screen. I’m currently looking for a way to lower the refresh rate on the login screen, as 60hz results in black screen… I’ve tried two high end HDMI cables from different manufacturers.

I’ve managed to force lower the refresh rate by using an active DP to HDMI 1.4a adapter. Still, I bought the card exclusively for its HDMI 2.0 prowess, the one thing it’s failing to do in Linux.

7

Will try with Windows 8.1 tonight, I am still not able to see anything when in 4K @ 60hz

Update: I can only seem to get it working for 4:2:0 chroma on 353 with windows. I’m running out of ideas. Will call evga again.

Update #2: strange behavior. It’s beyond finicky, I’ve gotten it to work on two separate occasions. Bought 3 adapters and new HDMI cable… had 3.

Update #3:
Restarting with CMS on HDMI 2.0 will result in no output from UEFI. Possibly due to fast boot?

Update #4:
So I’m still getting the fedora crashes on the UEFI with the CMS module, but once I managed to install fedora with a secondary monitor, install the RPMfusion 246 driver and then upgrade to the 349, I managed to get 4K@60hz with 444 chroma. The missing piece was the 18gbps cable… for the most part I was using high end looking HDMI cables that didn’t do the trick. The razorfish 8 feet 18gbps cable did the trick.