<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV50, bisected, RFC patch] xset dpms force {on,off} does not work over DP" href="https://bugs.freedesktop.org/show_bug.cgi?id=76483#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV50, bisected, RFC patch] xset dpms force {on,off} does not work over DP" href="https://bugs.freedesktop.org/show_bug.cgi?id=76483">bug 76483</a> from <a class="email" href="mailto:dd@crosstwine.com" title="Damien Diederen <dd@crosstwine.com>"> Damien Diederen</a> <pre>Created <a href="attachment.cgi?id=96281" name="attach_96281" title="[WIP,BROKEN] drm/nv50: Hack FORCE_DP_TRAIN method for DPMS power-on">attachment 96281</a> <a href="attachment.cgi?id=96281&action=edit" title="[WIP,BROKEN] drm/nv50: Hack FORCE_DP_TRAIN method for DPMS power-on">[details]</a> <a href='page.cgi?id=splinter.html&bug=76483&attachment=96281'>[review]</a> [WIP,BROKEN] drm/nv50: Hack FORCE_DP_TRAIN method for DPMS power-on Hi Ben, Excellent! (FYI: I, for one, don't need any backports.) In the meantime, I tried to kludge my way into getting the monitor to wake up with another horrible hack (attached), but did not succeed before running out of time. Any idea? I understand that both patches suffer from the race condition you were trying to avoid in the first place, but an always on/off monitor is a bit of a handicap :) Alternatively/in addition, I would welcome hints on how to make Nouveau survive power-cycling the monitor (e.g. by running a command over SSH to reset the display). The current behaviour is: [On, displaying] ↓ Turn off [Off] ↓ Turn on [Booting] ⋮ [OSD: No input; shutting down] ⋮ [Standby] Of course, feel free to suggest proper fixes, docs to read, and/or patches to test. Cheers, -D</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>