<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Haswell ULT max. resolution regression in KMS [HSW] [i915]" href="https://bugs.freedesktop.org/show_bug.cgi?id=101245#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Haswell ULT max. resolution regression in KMS [HSW] [i915]" href="https://bugs.freedesktop.org/show_bug.cgi?id=101245">bug 101245</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to Ville Syrjala from <a href="show_bug.cgi?id=101245#c9">comment #9</a>) > (In reply to Michael Mounteney from <a href="show_bug.cgi?id=101245#c8">comment #8</a>) > > > "Apparently HDMI->DVI dual mode adapter where we aren't able to infer the capabilities of the sink, and limit the clock rate to what we know works." > > It did work up to 4.8.17. I am using an Intel NUC with mini-HDMI to HDMI. > > No DVI-anything involved. > > [ 2.488338] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] NAK for addr: > 0040 w(1) > > Means there is no DP++ dongle involved. > > [ 11.111354] [drm:drm_add_edid_modes [drm]] HDMI: DVI dual 1, max TMDS > clock 250000 kHz > > This means the display itself is telling us that its max TMDS clock is lower > than clock required by the 4k and 25x16 modes. The fact that it's saying > dual link DVI and max TMDS clock > 165MHz in the same sentence is also a bit > nonsensical since that exceeds the DVI spec, and dual link HDMI doesn't > actually exist. Thanks for the clarification, Ville. I quickly looked at the dmesg, and refused to believe the display would do this. No idea why.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>