Bug 19535 - Screen doesn't come up when trying to run X on secondary display card
Summary: Screen doesn't come up when trying to run X on secondary display card
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Luc Verhaegen
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-13 08:43 UTC by Maciej Cencora
Modified: 2011-11-07 15:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log when rv620 is primary (working) (99.64 KB, text/plain)
2009-01-13 08:43 UTC, Maciej Cencora
no flags Details
Xorg log when rv620 is secondary (not working) (263.00 KB, text/plain)
2009-01-13 08:44 UTC, Maciej Cencora
no flags Details
lspci -v output when rv620 is primary (8.90 KB, text/plain)
2009-01-13 08:44 UTC, Maciej Cencora
no flags Details
lspci -v output when rv620 is secondary (8.80 KB, text/plain)
2009-01-13 08:45 UTC, Maciej Cencora
no flags Details

Description Maciej Cencora 2009-01-13 08:43:26 UTC
Created attachment 21938 [details]
Xorg log when rv620 is primary (working)

Primary VGA: RS690 (onboard)
Secondary VGA: RV620 (Powercolor Radeon HD3450)

Screen won't come up when trying to run X on RV620.
If RV620 is set as primary it works.
Comment 1 Maciej Cencora 2009-01-13 08:44:15 UTC
Created attachment 21939 [details]
Xorg log when rv620 is secondary (not working)
Comment 2 Maciej Cencora 2009-01-13 08:44:50 UTC
Created attachment 21940 [details]
lspci -v output when rv620 is primary
Comment 3 Maciej Cencora 2009-01-13 08:45:15 UTC
Created attachment 21941 [details]
lspci -v output when rv620 is secondary
Comment 4 Michael Cree 2009-03-14 17:32:12 UTC
(In reply to comment #0)
> Screen won't come up when trying to run X on RV620.
> If RV620 is set as primary it works.

(In reply to comment #1)
> Created an attachment (id=21939) [details]
> Xorg log when rv620 is secondary (not working)

Note the following line in your Xorg log:

(EE) RADEONHD(0): The fglrx kernel module is loaded. This can have obvious
     or subtle side effects. See radeonhd(4) for details.

Make sure the fglrx module cannot be loaded before running X.  (Removing the fglrx module if it gets loaded is apparently not sufficient to reverse its deleterious effect on radeonhd.)

Michael.
Comment 5 Martijn Bastiaan 2009-03-15 03:17:51 UTC
Hello Michael,
I've got the same problem as Maciej. Without fglrx I have the same problem. It could be solved with the setpci command (see radeonhd wiki), however this doesn't work for me.

Martijn
Comment 6 Jeremy Huddleston Sequoia 2011-10-16 15:57:12 UTC
Does this issue occur with the preferred ati driver (xf86-vide-ati)?  If so, please move this to the Driver/Radeon component.  

Development of radeonhd has pretty much halted and development focus is on the ati driver.  Please see http://www.x.org/wiki/radeonhd

If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Comment 7 Jeremy Huddleston Sequoia 2011-11-07 15:08:52 UTC
Closing due to lack of response.  Please reopen and move to the Driver/Radeon 
component if this issue persists with xf86-video-ati


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.