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: Wed, 04 Apr 2012 11:39:41 +0000 [thread overview]
Message-ID: <bug-27184-502-9bS5G9TJ35@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 #25 from tomi.orava@ncircle.nullnet.fi 2012-04-04 04:39:41 PDT ---
I just happened to test with this very same 3.3.0-rc3 kernel that while I was
in linux console ie. no X and the screen blanker got activated, the lcd display
was put into suspend mode ---> I hit the keyboard at this stage and the screen
came back without fuss. Last time when I tried all the different stages with
xset, none of them worked well. Is there an easy way to modify the states the
console screen saver is using (for testing purposes) ?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-04-04 11:39 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
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 [this message]
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-9bS5G9TJ35@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.