Description of problem:
Dual-headed xinerama worked fine on a Dell Latitude D600 with FC4 but when I
upgraded to FC5 the best I can do is clone the primary screen to the secondary.
Xinerama won't work. The secondary screen shows the blue background (somewhat
muddied) and it echos some of what's on the main screen. For example, if I open
a terminal window it'll be legible on the main screen but look like bad cable
scrambling on the second screen. If I drag a window to the second screen it
gets scrambled, but is restored when I drag it back to the primary.
All of that is with the fglrx driver. With the standard radeon driver the
second screen won't come on at all.
Version-Release number of selected component (if applicable):
Very. I've installed a fresh copy of FC4, got Xinerama working and upgraded via
CD to FC5.
Steps to Reproduce:
1. Install FC4. Set up xinerama
2. Install FC5
Second display doesn't come on with radeon drivers. With livna's fglrx the
second screen works ok as a clone, but is scrambled with xinerama enabled.
We do not support the proprietary fglrx driver (or any 3rd party driver).
For problems with fglrx, please contact ATI directly. If you're also having
a problem with the stock radeon driver, uninstall the fglrx driver completely,
and reinstall all of the mesa and Xorg packages to restore all of the files
the ATI installer overwrites when it installs.
Then run "system-config-display --reconfig" to generate an X config. You then
need to manually configure Xinerama by hand (our config tool pretends to
configure dualhead but never works properly). You may need assistance from
the firstname.lastname@example.org mailing list to get a proper working
Xinerama setup, as it varies with different hardware and setups how to
properly configure it.
If you still have problems after that, file a bug report in X.Org bugzilla
and attach the upstream bug URL here and we will track the issue in X.Org
Setting status to "NEEDINFO_REPORTER" and awaiting update and/or upstream
Thanks in advance.
No response from reporter, no activity for a long time, closing as
INSUFFICIENT_DATA. If anyone has some information on this bug, please, reopen
with additional data.