From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64850] New: Second screen black on Pitcairn PRO
Date: Wed, 22 May 2013 06:04:39 +0000 [thread overview]
Message-ID: <bug-64850-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1344 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64850
Priority: medium
Bug ID: 64850
Assignee: dri-devel@lists.freedesktop.org
Summary: Second screen black on Pitcairn PRO
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: flocke@shadowice.org
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 79637
--> https://bugs.freedesktop.org/attachment.cgi?id=79637&action=edit
dmesg | grep drm right after boot (no X11)
I just installed my new Pitcairn PRO card (Radeon 7850) in my PC.
Every time I boot into linux (Arch Linux x86_64) my second monitor turns black
right at boot.
There are no errors and I can even start X11 with my dual-monitor configuration
and move the mouse from my first screen to the right. It is as if the screen is
there, only my monitor doesn't show it.
This happens not in X11, in fact the secend screen goes black as soon as the
kernel/kms is loaded.
I attached the output of 'dmesg | grep drm' with the drm.debug=15 kernel option
right after booting and befor starting X11 and I will attach the same commands
output after running X11.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2810 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-05-22 6:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 6:04 bugzilla-daemon [this message]
2013-05-22 6:05 ` [Bug 64850] Second screen black on Pitcairn PRO bugzilla-daemon
2013-05-22 6:20 ` bugzilla-daemon
2013-05-22 8:17 ` bugzilla-daemon
2013-05-22 12:44 ` bugzilla-daemon
2013-05-22 12:56 ` bugzilla-daemon
2013-05-22 16:32 ` bugzilla-daemon
2013-05-22 16:37 ` bugzilla-daemon
2013-05-22 16:43 ` bugzilla-daemon
2013-05-22 16:57 ` bugzilla-daemon
2013-05-22 16:58 ` bugzilla-daemon
2013-05-22 17:01 ` bugzilla-daemon
2013-05-22 17:04 ` bugzilla-daemon
2013-05-22 17:06 ` bugzilla-daemon
2013-05-22 17:07 ` bugzilla-daemon
2013-05-22 17:24 ` bugzilla-daemon
2013-05-23 14:51 ` bugzilla-daemon
2013-05-24 6:43 ` bugzilla-daemon
2013-05-28 8:38 ` bugzilla-daemon
2013-05-30 3:43 ` bugzilla-daemon
2013-07-03 12:44 ` bugzilla-daemon
2013-07-04 16:17 ` bugzilla-daemon
2013-07-05 8:12 ` bugzilla-daemon
2013-07-14 17:22 ` bugzilla-daemon
2013-07-15 7:43 ` bugzilla-daemon
2013-07-15 16:35 ` bugzilla-daemon
2013-08-19 17:14 ` bugzilla-daemon
2013-08-19 17:14 ` bugzilla-daemon
2013-08-19 18:43 ` bugzilla-daemon
2013-08-19 20:48 ` bugzilla-daemon
2013-09-16 20:28 ` bugzilla-daemon
2013-09-16 20:53 ` 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-64850-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).