<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - kms blackscreen ATI RV620 FirePro 2260, res: 2560*1600" href="https://bugs.freedesktop.org/show_bug.cgi?id=54273#c43">Comment # 43</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - kms blackscreen ATI RV620 FirePro 2260, res: 2560*1600" href="https://bugs.freedesktop.org/show_bug.cgi?id=54273">bug 54273</a> from <a class="email" href="mailto:agd5f@yahoo.com" title="Alex Deucher <agd5f@yahoo.com>"> Alex Deucher</a> <pre>(In reply to <a href="show_bug.cgi?id=54273#c42">comment #42</a>) > Adding/setting a modeline in xrandr for the native resolution at 80hz > (instead of 60hz) works around this problem in X. I noticed my dell monitor > was outputting at 56hz when it should have been at 75hz on a lower > resolution. There seems to be a 3/4 ratio between what the display sees and > what xrandr sees. It sounds like your monitor may prefer a different DP lane count and clock rate than the driver wants to use. The link training appears to complete successfully, but the monitor doesn't seem to like the selected lane/rate. Bumping the clock up to 80Hz, you're probably getting a different lane/rate combination that the monitor prefers. See radeon_dp_set_link_config() in atombios_dp.c.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>