https://bugs.freedesktop.org/show_bug.cgi?id=27184

--- Comment #18 from Oliver Winker oliverml1@oli1170.net 2011-11-14 14:01:30 PST --- (In reply to comment #17)

DPMS standby, suspend, and off states are all treated the same from the driver's perspective. The driver really only deals with 2 DPMS states on and off.

Ok, interesting to know. Now somehow the way using "xset dpms 240 0 0" (stand-by) quite surely made a difference for me at the time (<3.1) - but I can't prove and explain in detail.

Now currently I'm using "xset dpms 0 240 0" (suspend) with 3.1 and until now it wakes up quite reliable. Which would be in inline with your info, that the driver operates on the same two states, as with stand-by.

Maybe I'll also retest again the KDE power mgmt setting way, where I originally observed the wake-up problem. Maybe it's some screwed side effect in the end.

...

Anyway, I will also retry a bit and do some testing using "suspend" on a 3.1, to see if something changed.

When you say suspend, are you talking about the DPMS display state, or suspend and resume of the entire laptop? The two are very different.

No, no - I'm really talking about pure display suspend/resume, on a desktop with an Asus screen. Only the display is suspended and should nicely wakeup again, when I tick the mouse ;).