|
Bugzilla – Full Text Bug Listing |
| Summary: | Update loses multi-head setting (Xinerama) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Richard Biener <rguenther> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | eich, lmuelle, suse-beta |
| Version: | Beta 7 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| 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 | ||
|
Description
Richard Biener
2006-03-09 12:27:41 UTC
Please attach the YaST logfiles and your changed /etc/X11/xorg.conf, if possible point out the correct settings there. 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. 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.
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* Ok, now using "radeonold" driver fixes this last issue. sax2 needs to know about this. Reassigning to Marcus. radeonold ... Stefan what shall we do with that problem ? 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). 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 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") reopen. 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. |