All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27184] Radeon, KMS, 6.12.99: Sleeping screen doesn't wake up reliably
Date: Mon, 14 Nov 2011 22:01:30 +0000	[thread overview]
Message-ID: <bug-27184-502-S4uMnAvFOP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-27184-502@http.bugs.freedesktop.org/>

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 ;).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-11-14 22:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-27184-502@http.bugs.freedesktop.org/>
2011-11-12 21:23 ` [Bug 27184] Radeon, KMS, 6.12.99: Sleeping screen doesn't wake up reliably bugzilla-daemon
2011-11-12 21:23 ` bugzilla-daemon
2011-11-13 10:54 ` bugzilla-daemon
2011-11-13 20:02 ` bugzilla-daemon
2011-11-14 22:01 ` bugzilla-daemon [this message]
2012-02-14 18:43 ` bugzilla-daemon
2012-02-14 19:07 ` bugzilla-daemon
2012-02-14 20:36 ` bugzilla-daemon
2012-02-15  6:49 ` bugzilla-daemon
2012-02-27  7:29 ` bugzilla-daemon
2012-02-27  7:31 ` bugzilla-daemon
2012-02-27 14:00 ` bugzilla-daemon
2012-04-04 11:39 ` bugzilla-daemon
2012-04-04 13:07 ` bugzilla-daemon
2012-05-11 20:14 ` bugzilla-daemon
2013-11-24 18:39 ` bugzilla-daemon
2013-11-24 18:41 ` bugzilla-daemon
2013-11-24 22:52 ` bugzilla-daemon
2019-11-19  8:10 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27184-502-S4uMnAvFOP@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.