<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Unable to correctly set 3 monitor outputs with different resolution/clock on newer kernel/intel driver" href="https://bugs.freedesktop.org/show_bug.cgi?id=91900#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Unable to correctly set 3 monitor outputs with different resolution/clock on newer kernel/intel driver" href="https://bugs.freedesktop.org/show_bug.cgi?id=91900">bug 91900</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>The dmesgs don't seem to match your supposed xrandr calls very well. Looking at intel-dmesg-4.0-3-vgaonly, I see it doing the following 1. enables pipe A -> HDMI-A-1, picks DPLL A, clock is 106500kHz 2. enables pipe B -> HDMI-A-2, picks DPLL B, clock is 108000kHz 3. tries to enable pipe C -> VGA-1, fails to find a DPLL even though the clock is the same 108000kHz that DPLL B is already producing I don't see what could be different between DPLL settings between pipe B an C, both use the same PLL limits, and there should be no SSC/etc. things to worry about. Unfortunately the driver is being extremely unhelpful and doesn't print out any of the DPLL settings it's trying to match so I can't see what the actual difference is.</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>