From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70207] New: rs690: kernel can't bring lvds in dpms on mode
Date: Sun, 06 Oct 2013 18:27:34 +0000 [thread overview]
Message-ID: <bug-70207-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1076 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70207
Priority: medium
Bug ID: 70207
Assignee: dri-devel@lists.freedesktop.org
Summary: rs690: kernel can't bring lvds in dpms on mode
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: david.heidelberger@ixit.cz
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
After some time, LVDS display get into off mode in console. After pressing keys
it display stay black. Only way, how to get it working again is using "vbetool
dpms on", then it lights up correctly.
It only applies in console, in X11 session is display powered just fine after
passing event to key/mouse/touchpad.
This behaviour is here for long time, 100% since 3.9 to 3.11.4, but probably
much more (I'd like to test, but it took lot of time).
This is laptop Toshiba A210-15j, RS690 card.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2388 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-10-06 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 18:27 bugzilla-daemon [this message]
2013-10-07 11:44 ` [Bug 70207] rs690: kernel can't bring lvds in dpms on mode bugzilla-daemon
2014-02-14 14:28 ` bugzilla-daemon
2014-06-07 19:47 ` bugzilla-daemon
2014-06-09 1:08 ` bugzilla-daemon
2014-06-27 13:32 ` bugzilla-daemon
2014-06-27 13:49 ` bugzilla-daemon
2014-06-27 15:00 ` bugzilla-daemon
2014-07-15 13:37 ` 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-70207-502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).