<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#c26">Comment # 26</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:skeggsb@gmail.com" title="Ben Skeggs <skeggsb@gmail.com>"> Ben Skeggs</a> <pre>(In reply to <a href="show_bug.cgi?id=76483#c25">comment #25</a>) > That fixed the garbled display. > > The monitor off/on thing is weird. When I was trying to get 3.14 to work > (before discovering this bug report), I tried the nvidia binary driver and > got the same flash off/on thing. However, dpms-off was working in 3.6.3, > which I unfortunately don't have lying around any more. It seems strange > that the monitor would break in this manner, so I guess the 3.6.x driver was > doing something to work around the monitor's response. (Also, the > monitor-off screensaver works when I am in OS/X.) If it's the same situation as Nouveau, then the binary driver probably ignored the HPD_IRQ pulse from the monitor. We need to care about it now (well, we were *supposed* to already, but anyway) for MST support particularly. I'm pretty sure I can work around the issue in the driver if we need to, so that's ok. > > I can get a log to verify if you like, later today. If there's anything I > can get from 3.6 to see if it's doing something different, let me know; I'm > sure I can find and build a 3.6 sometime in the next day or two if necessary. That'd be great, thanks. > > At least it's going in the right direction - thanks!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>