Description of problem:
Enabling dual head w/Xinerama on ATI Technologies Inc RV380 [Radeon X600 (PCIE)]
causes the X server to crash on startup with a Signal 11 error and backtrace.
Clone-mode single head works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. s-c-display, enable dual-head
2. logout to let X restart
X server crashes
No crash. Dual-head, Xinerama mode (or whatever replaced MergedFB)
01:00.0 VGA compatible controller: ATI Technologies Inc RV380 [Radeon X600
(PCIE)] (prog-if 00 [VGA])
01:00.1 Display controller: ATI Technologies Inc RV380 [Radeon X600]
Created attachment 246041 [details]
xorg.conf dual-head Xinerama from Fedora 7
This is the manual xorg.conf I tried which works fine in Fedora 7. The F8
s-c-display automatically generated one had problems with BusID's when enabling
Created attachment 246051 [details]
Xorg.0.log file from Xinerama dual-head attempt
Xinearama isn't supported, yes I know we shouldn't crash I'll try and make it do
For dual-head you should just be able to use the xrandr command to set stuff..
Okay the crashing should now be fixed in updates-testing
You still won't get xinerama but at least it won't blow up if you try... the ATI
driver now uses randr-1.2 to configure things.
xorg-x11-drv-ati-6.7.196-2.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-ati'
xorg-x11-drv-ati-6.7.196-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.