Red Hat Bugzilla – Bug 202553
X dual head not configuring second monitor
Last modified: 2018-04-11 03:37:42 EDT
Description of problem:
Attempting to configure dual head mode in rawhide of 2006-08-14 fails
due to non-configuration of device by s-c-d(?)
Version-Release number of selected component (if applicable):
three different user attempts.
Steps to Reproduce:
1. install rawhide of 2006-08-14
2. configure dual head mode
see attached X logs
dual head operation.
Celeron (Coppermine) @ 600MHz 256MB RAM
video1: Trident Cyberblade/i1 - Compaq S710 monitor
video2: ATI (Mach 64) - Pionex monitor
VIA Chipsets, 160GB IDE disk, etc.
Created attachment 134180 [details]
xorg.conf generated by s-c-d for dual head mode (some modelines added)
Created attachment 134181 [details]
X log showing failure of ATI configuration
Created attachment 134909 [details]
Xorg.0.log showing failure to configure ATI(Mach64) video
Created attachment 134910 [details]
xorg.conf from FC5+ that is failing
This bug also applies to current FC5 X11 setups!
The ATI card fails to configure and start the second screen. See attachments for
the xorg.conf and Xorg.0.log files from FC5.
This is a fully updated FC5 install on the testbed machine.
This is still extant in rawhide of 2006-09-10
There is NO reason that this should still be outstanding. The X server is
failing to read and parse the configuration for the ATI card.
OK, I was able to generate a working dual-head configuration by entering run
state 3 and using X -configure to make a new xorg.conf file.
It seems to me that the critical difference is that Screen 1 is generated with a
"RightOf" instead of Screen 0 being given a "LeftOf" parameter. I'll
experiment a little and see if that makes any difference.
Since this bugzilla report was filed, there have been several major updates,
which may have resolved this issue. Users who have experienced this problem are
encouraged to upgrade their system to the latest version of their distribution
Please, if you experience this problem on the up-to-date system, let us now in
the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as
INSUFFICIENT_DATA. Thank you.
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.