I recently bought a UHD television for use as a computer monitor. I also bought a high quality 18Gbps capable HDMI cable and a Club 3D DisplayPort 1.2 to HDMI 2.0 Active Adapter (CAC-1070).
My computer has Intel Core i7-4790k processor with integrated HD 4600 display adapter.
I recently had a chance to test my system with a UHD monitor and 2160p 60Hz worked flawlessly through DisplayPort. HD 4600 can only show 2160p 24Hz picture through HDMI so using it is not an option (videos are unwatchable because of judder, tearing and choppiness).
After unsuccessfull attempts to get 2160p 60Hz signal to work with said DP to HDMI adapter, I contacted Club 3D support and got a new firmware. After installing Windows 10 and updating the adapter, I created a custom display mode with CVT-RB timing as arupman advices in this thread: https://communities.intel.com/thread/99226. Now the adapter works perfectly: I get 2160p 60Hz image (59Hz actually) and all videos play silky smooth. On Windows.
Not so on Leap 42.2. For UHD resolution nothing above 47.35Hz works and gives only garbled or blank (black or pale green) image.
Videos seem to judder and/or tear if refreshrate is less than 60Hz for UHD desktop (or possibly 50Hz, I haven’t been able to test that).
1920x1080 @ 120.00 Hz works without problems.
Club 3D support informed me that Intel Windows drivers default to 32bit color mode and that demands too high bandwith from HDMI. Color mode should be 8bpp. Apparently newer Intel drivers fix the issue with the color mode being too high. After playing with UHD bandwith calculators it really seems to be a bandwidth issue. However Windows display properties shows 32bit mode even after creating a custom mode. I don’t know and don’t understand. Couldn’t find any further information. I tried to find out how to instruct Linux Intel drivers to use 8bpp. Perhaps modifying /etc/X11/xorg.conf.d/50-screen.conf?
:~> xwininfo -root | grep Depth:
Depth: 24
But isn’t that already 8bpp? This whole situation is way beyond my expertise.
I couldn’t find any information about HD 4600 maximum pixel clock if that even matters, nor do I understand (or have any energy left to learn) what are front and back porches and do I even have to care.
Frankly, even the thought of installing beta drivers or anything similar turns my stomach because if something goes wrong I have absolutely no knowledge how to fix that. However beta drivers are still an option if that is the only solution to get 2160p 60Hz to work.
Other option is to to buy a new display adapter but that brings a whole lot of new potential problems. (I have very bad experiences with Linux display adapter drivers and rather spend my time with productive work, not endlessly tweaking something I don’t understand.)
Here is the procedure I used to try different refreshrates:
:~> cvt -v 3840 2160 60
# 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz
Modeline "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync
:~> xrandr --newmode "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync
:~> xrandr --addmode DP1 3840x2160_60.00
:~> xrandr --output DP1 --mode 3840x2160_60.00
I also tried reverse blanking:
:~> cvt -v -r 3840 2160 60
With that my television reports 60Hz signal but the screen goes black or pale green.
And gtf
:~> gtf 3840 2160 60
with the same results.
I tried numerous different refresh rates with both cvt and gtf modelines but nothing worked above 47.35Hz (with gtf giving pixel clock of 553.09MHz and pixel clock of 553.50MHz given by cvt not working).
Does anybody have any idea how to fix 2160p 60Hz mode on Opensuse? What further information should I provide?
Or alternatively: does anybody know if Radeon RX 460 will work out-of-the-box, without proprietary drivers?