dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64850] Second screen black on Pitcairn PRO
Date: Fri, 24 May 2013 06:43:21 +0000	[thread overview]
Message-ID: <bug-64850-502-7pJBuodCfz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64850-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]

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

--- Comment #17 from Jakob Nixdorf <flocke@shadowice.org> ---
Created attachment 79737
  --> https://bugs.freedesktop.org/attachment.cgi?id=79737&action=edit
ROM Dump

I played around some more. I compiled my kernel with UMS enabled and booted
with 'radeon.modeset=0' which resultet in the 'radeon' module beeing loaded
successful and without the 'Invalid ROM contents' error. Also both screens are
active in the TTY.
After running 'rmmod radeon && modprobe -v radeon modeset=1' the DVI-0 screen
goes black again and the TTY is only shown on HDMI-0. Also the 'Invalid ROM
contents' error shows up again.

Additionally I made a dump of the ROM ('echo 1 >
/sys/bus/pci/devices/0000:01:00.0/rom && cat
/sys/bus/pci/devices/0000:01:00.0/rom > rom-dump'), because this error somehow
bugs me ;) maybe it can help.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1813 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

  parent reply	other threads:[~2013-05-24  6:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  6:04 [Bug 64850] New: Second screen black on Pitcairn PRO bugzilla-daemon
2013-05-22  6:05 ` [Bug 64850] " 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 [this message]
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-7pJBuodCfz@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