Bug 98534

Summary: Unable to start Xorg with radeon driver
Product: xorg Reporter: Mingcong Bai <jeffbai>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: 7.7 (2012.06)   
Hardware: PowerPC   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log (full)
none
lspci output
none
/proc/fb content
none
dmesg, grep'd "fb"
none
dmesg, grep'd "radeon" none

Description Mingcong Bai 2016-11-01 19:03:07 UTC 
I wasn't able to launch X with the "radeon" driver on my PowerMac G5. I had a problem with Xorg server choosing the wrong PCI slot for my graphics card, described here:

https://bugs.freedesktop.org/show_bug.cgi?id=98524 BusID disregarded in xorg.conf in dual graphics card and single monitor setup

So I ended up disabling the NVIDIA card (which caused the problem above) with the following udev command line:

ACTION=="add", KERNEL=="0000:0a:00.0", SUBSYSTEM=="pci", RUN+="/bin/sh -c 'echo 1 > /sys/bus/pci/devices/0000:0a:00.0/remove'"

And now the X server could choose the only right PCI slot for the graphics card, but the server still won't start, from the Xorg.0.log (attached below), I can see that the X server has chosen the right driver through probing - as I do not have any xorg.conf that specifies to use the "radeon" driver.

Attached above:

- Xorg.0.log
- dmesg outputs (grep'd "fb" and "radeon")
- /proc/fb content
- lspci output
Comment 1 Mingcong Bai 2016-11-01 19:03:26 UTC 
Created attachment 127665 [details]
Xorg.0.log (full)
Comment 2 Mingcong Bai 2016-11-01 19:03:38 UTC 
Created attachment 127666 [details]
lspci output
Comment 3 Mingcong Bai 2016-11-01 19:03:56 UTC 
Created attachment 127667 [details]
/proc/fb content
Comment 4 Mingcong Bai 2016-11-01 19:04:13 UTC 
Created attachment 127668 [details]
dmesg, grep'd "fb"
Comment 5 Mingcong Bai 2016-11-01 19:04:25 UTC 
Created attachment 127669 [details]
dmesg, grep'd "radeon"
Comment 6 Michel Dänzer 2016-11-02 01:28:23 UTC 
The "[KMS] Kernel modesetting enabled." message means that the driver's probe hook succeeded, so this is a Xorg issue. Resolving as a duplicate of your bug 98524, as those symptoms look basically the same there. Note that IIRC there was already at least one earlier report about the same issue.

*** This bug has been marked as a duplicate of bug 98524 ***

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.