Bug 106999

Created attachment 140274 [details]
Xorg.0.log

Created attachment 140275 [details]
Dmesg no 60Hz

Created attachment 140276 [details]
EDID

If I use the modesetting DDX (with Xorg from git - to include the PCIIDs for Raven) X no longer starts and I get an error in the dmesg

Created attachment 140277 [details]
Dmesg with error

Strange I've just tried to do this again with modesetting and X starts but the higher than 30Hz options aren't selectable, and 60Hz exactly is still missing

Xrandr now with modesetting

xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384
HDMI-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 1872mm x 1053mm
   4096x2160     30.00    25.00    24.00    24.00    29.97    23.98
   3840x2160     59.97    30.00*   30.00    25.00    25.00    24.00    24.00    29.97    23.98
   3200x1800     59.96    59.94
   2880x1620     59.96    59.97
   2560x1600     59.99    59.97
   2560x1440     59.99    59.96    59.95
   2048x1536     75.00    60.00
   1920x1440     75.00    60.00
   1856x1392     75.00    60.01
   1792x1344     75.00    60.01
   2048x1152     59.99    59.98    59.90    59.91
   1920x1200     59.88    59.95
   1920x1080     60.01    59.97    59.96    60.00    60.00    50.00    59.94    59.93    30.00    25.00    24.00    29.97    23.98
   1600x1200     75.00    70.00    65.00    60.00
   1680x1050     59.95    59.88
   1400x1050     74.76    59.98
   1600x900      59.99    59.94    59.95    60.00    59.82
   1280x1024     75.02    60.02
   1440x900      59.90
   1400x900      59.96    59.88
   1280x960      60.00
   1440x810      60.00    59.97
   1368x768      59.88    59.85
   1366x768      59.79
   1280x800      59.99    59.97    59.81    59.91
   1152x864      75.00
   1280x720      60.00    59.99    59.86    60.00    60.00    50.00    59.94    59.74
   1024x768      75.05    60.04    75.03    70.07    60.00
   960x720       75.00    60.00
   928x696       75.00    60.05
   896x672       75.05    60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   832x624       74.55
   960x540       59.96    59.99    59.63    59.82
   800x600       75.00    70.00    65.00    60.00    72.19    75.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   720x576       50.00
   700x525       74.76    59.98
   800x450       59.95    59.82
   720x480       60.00    59.94
   640x512       75.02    60.02
   700x450       59.96    59.88
   640x480       60.00    75.00    72.81    75.00    66.67    60.00    59.94
   720x405       59.51    58.99
   720x400       70.08
   684x384       59.88    59.85
   640x400       59.88    59.98
   576x432       75.00
   640x360       59.86    59.83    59.84    59.32
   512x384       75.03    70.07    60.00
   512x288       60.00    59.92
   416x312       74.66
   480x270       59.63    59.82
   400x300       72.19    75.12    60.32    56.34
   432x243       59.92    59.57
   320x240       72.81    75.00    60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
HDMI-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)
HDMI-4 disconnected (normal left inverted right x axis y axis)

Created attachment 140278 [details]
Xorg.0.log with modesetting

I have a feeling that Kwin was trying to modeset back to 60Hz which was causing Xorg to crash and the error to appear in the dmesg

I'll post the Xorg.0.logs if I manage to reproduce the issue

Is this different from bug 106959?

It might be the same, the EDID says the TV is capable of both 10bit and 12bit colour, I was under the impression that HDMI 2 was able to do 2160p@60Hz at those colour depths

From what I can see the HDMI 2.0 spec only supports 4k@60 at 8 bpc.  I think you need HDMI 2.1 for 4k@60 with 10 bpc or greater.

What is Raven capable of? I know my SkyQ box outputs at 2160@60Hz in 10bit colour

(In reply to Mike Lothian from comment #13)
> I know my SkyQ box outputs at 2160@60Hz in 10bit colour

https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_HDR10_video

4k@60@10bpc needs YUV 4:2:2 for HDMI 2.0, so it can't handle RGB (or YUV 4:4:4). That's probably the discrepancy - there's currently no great way for userspace to select which encoding variant is to be used (or what bpc to send it at).