<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [GM45 DP-DVI dongle] KMS often does not set native display resolution" href="https://bugs.freedesktop.org/show_bug.cgi?id=89805#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [GM45 DP-DVI dongle] KMS often does not set native display resolution" href="https://bugs.freedesktop.org/show_bug.cgi?id=89805">bug 89805</a> from <a class="email" href="mailto:andreas.sturmlechner@gmail.com" title="andreas.sturmlechner@gmail.com">andreas.sturmlechner@gmail.com</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=89805#c5">comment #5</a>) > The external outputs will not be available when KMS takes over, and so they > will be hotplugged in later when the dock is enabled. As a result the initial > resolution is computed solely for the eDP, which will then be mirrored onto the > new outputs when they arrived. Except that 3.4.x on that particular setup and any other kernel on the same dock (but connected to a DP screen), together with i915.panel_ignore_lid=0 is always able to set the correct initial resolution - the dock is enabled from the start. It only happens in conjunction with the DP-DVI connector that it does not behave as expected (but much better than pre-4.0.0). I can send new debug logs on the weekend.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>