I have a Sony XBR 4K TV connected to the Haswell Refresh graphics on my i7-4790K. The following appears in the xorg log: [ 9.308] (II) intel(0): Not using mode "4096x2160" (bad mode clock/interlace/doublescan) [ 9.308] (II) intel(0): Not using mode "4096x2160" (bad mode clock/interlace/doublescan) [ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode clock/interlace/doublescan) [ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode clock/interlace/doublescan) [ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode clock/interlace/doublescan) [ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode clock/interlace/doublescan) [ 9.308] (II) intel(0): Not using mode "3840x2160" (bad mode clock/interlace/doublescan) This seems to appear for no better reason than because the EDID claims a max pixel clock of 165.0MHz. If the EDID contains modes that exceed the EDID's own claimed max pixel clock, the max pixel clock should be adjusted. This appears to be what the nVidia proprietary driver does.
Please attach your Xorg.0.log and xrandr --verbose.
Created attachment 111056 [details] xorg log
Created attachment 111057 [details] xrandr output
commit d6c8d7509727060b8e2358b9ed1c0e17b2ec3401 Author: Damien Lespiau <damien.lespiau@intel.com> Date: Wed Jul 31 19:16:45 2013 +0100 xfree86: Use the TMDS maximum frequency to prune modes Instead of only relying on the Range section, we can do better on HDMI to find out what is the max dot clock the monitor supports. The HDMI CEA vendor block adds a TMDS max freq we can use. This makes X not prune 4k resolutions on HDMI. v2: Replace X_INFO by X_PROBED in the message that prints the max TMDS frequency (Chris Wilson) Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com> Needs Xorg-1.16.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.