<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Monitor on DisplayPort doesn't wake up"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86320#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Monitor on DisplayPort doesn't wake up"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86320">bug 86320</a>
from <span class="vcard"><a class="email" href="mailto:wolfgang.rupprecht@gmail.com" title="Wolfgang Rupprecht <wolfgang.rupprecht@gmail.com>"> <span class="fn">Wolfgang Rupprecht</span></a>
</span></b>
<pre>Sitting in the initial bios screen and turning off the monitor with either the
front soft power switch or the back/top real power switch does indeed cause it
to go and stay into power-save mode with a slow blinking of the front blue led.
My motherboard has the same problem you observe. (Asus F2A85-M Pro, bios 6601
(the latest))
One thing that I should mention is that under X the monitor will sometimes wake
up with a "not optimal mode, 2560 x 1440" small moving box displayed on the
screen. This happens some of the time when I turn the monitor off/on or switch
displays vea alt-ctl-f3 and then back again. It may be because the two
2560x1440 monitors prefer a slightly different refresh rate. Xrandr seems to
think the monitors want 59.xx hz instead of 60.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>