Bug 156423 - Update loses multi-head setting (Xinerama)
Summary: Update loses multi-head setting (Xinerama)
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-09 12:27 UTC by Richard Biener
Modified: 2008-07-16 15:45 UTC (History)
3 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
sax log file (manual config), old xorg.conf, new xorg.conf (210.00 KB, application/x-tar)
2006-03-09 13:44 UTC, Richard Biener 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Biener 2006-03-09 12:27:41 UTC 
After update my multi-head setting is cloned displays rather than Xinerama which it was before.
Comment 1 Michael Gross 2006-03-09 13:10:06 UTC 
Please attach the YaST logfiles and your changed /etc/X11/xorg.conf, if possible point out the correct settings there.
Comment 2 Richard Biener 2006-03-09 13:42:06 UTC 
log files are in attachment with id 71970

Basically, running sax2 manually it does not come up with a configuration X dialog, but requires -i invocation.

Manually configuring X with sax2 -i -r and selecting a Xinerama configuation still leaves me with a cloned display setup.  This did work in 10.0.
Comment 3 Richard Biener 2006-03-09 13:44:29 UTC 
Created attachment 71981 [details]
sax log file (manual config), old xorg.conf, new xorg.conf

Note that just using the old xorg.conf does not work, too, so it might be a change/bug in the driver used.
Comment 4 Richard Biener 2006-03-09 15:41:08 UTC 
Now I managed to get to a state where the logs from Xorg look similar to the 10.0 provided ones by selecting addtional options for the driver:

 - IgnoreEDID
 - MergedFB
 - CRT2HSync 30-81
 - CRT2VRefresh 56-75
 - CRT2Position RightOf
 - MetaModes 1280x1024,1280x1024

where MergedFB and MetaModes are critical, IgnoreEDID and others are only necessary because though detecting valid monitor information from the 2nd
output, the driver thinks otherwise and assumes defaults which later disable
MergedFB again.

Problem remaining: while my display is now 2560x1024, both displays show the left part of the Xinerama screen.  *sigh*
Comment 5 Richard Biener 2006-03-09 16:00:33 UTC 
Ok, now using "radeonold" driver fixes this last issue.

sax2 needs to know about this.
Comment 6 Michael Gross 2006-03-09 16:07:57 UTC 
Reassigning to Marcus.
Comment 7 Marcus Schaefer 2006-03-10 10:41:37 UTC 
radeonold ... Stefan what shall we do with that problem ?
Comment 8 Stefan Dirsch 2006-03-10 10:47:22 UTC 
One of the known regressions of the new driver. No fix available right now. Other known victims of this bug are Mike and Lars (both in Cc now).
Comment 9 Stefan Dirsch 2006-03-18 22:29:24 UTC 
We should test/investigate again with X.Org > 7.1 (SUSE > 10.1), which will include an updated radeon driver. There's still hope. ==> LATER
Comment 10 Stefan Dirsch 2006-03-28 19:16:12 UTC 
I've added the current ati-1-0-branch radeon driver to RC1. Some things 
might have been fixed. Give it a try with "sax2 -r -m 0=radeon10b". 
(The driver is called "radeon10b")
Comment 11 Stefan Dirsch 2006-05-30 19:09:29 UTC 
reopen.
Comment 12 Stefan Dirsch 2006-05-30 19:11:52 UTC 
Richard, you,  Mike and Lars all use the same gfx card and machine. Mike is now using the radeon10b driver since months. Simply replace "radeonold" with "radeon10b" to verify this.

Since it works with radeon10b, we can assume, that it will also work with X.Org 7.1 radeon driver on SUSE 10.2.