https://bugzilla.novell.com/show_bug.cgi?id=307456#c1 --- Comment #1 from Lenz Grimmer <lenz@grimmer.com> 2007-09-04 10:25:21 MST --- Created an attachment (id=161775) --> (https://bugzilla.novell.com/attachment.cgi?id=161775) SaX2 screenshot -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c3 --- Comment #3 from Lenz Grimmer <lenz@grimmer.com> 2007-09-04 10:27:01 MST --- Created an attachment (id=161777) --> (https://bugzilla.novell.com/attachment.cgi?id=161777) SaX.log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c5 Lenz Grimmer <lenz@grimmer.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lenz@grimmer.com | --- Comment #5 from Lenz Grimmer <lenz@grimmer.com> 2007-09-07 13:42:56 MST --- Hi Marcus, I tested this again with sax2 from 10.3b3 today. Attached please find a tarball with the following content: sax2 |-- connected | |-- SaX.log | `-- xorg.conf |-- detached | |-- SaX.log | `-- xorg.conf |-- detached_modified | |-- SaX.log | `-- xorg.conf `-- hwinfo.out "hwinfo.out" is the output of "hwinfo". The files in the "connected" directory contain the log file and the resulting xorg.conf when the monitor was attached before starting the configuration. Consequently, the files in the "detached" directory contain the log file and configuration file from letting SaX2 configure the internal display only (which worked fine). I performed each test from the console in runlevel 3 (VESA framebuffer in the native 1400x1050 resolution). SaX2 was started with the "-r" option, I removed any previous xorg.conf file before. I started it and accepted the proposed configuration. When the monitor was connected during this procedure, the resulting resolution on the internal screen seems to be correct at 1400x1050 (the mouse cursor is clearly visible), however the screen is garbled and there are pixel artifacts at the bottom. I will attach photographs that explain what I mean. Also the widgets are displayed at the wrong location, so you have to click "blindly" to hit a button. With the monitor connected from the beginning I was unable to perform the configuration, as the screen was so messed up. I then repeated the test by having the monitor unplugged at first, waiting for SaX2 to come up with the (correct) proposal for the internal screen. I then connected the second monitor and proceeded to change the configuration. The settings for Display 1 (the internal one) were displayed correctly, so I proceeded so set up the second head by "Activate Dual Head" -> "Configure..." "Second Monitor -> Change", selected "Samsung Syncmaster 940BW" from the list and confirmed. I then changed the resolution to "1440x900 (WXGA)". Next I checked "Xinerama Multihead" and changed the arrangement to "[1] [2]". I then confirmed the settings and proceeded to testing the resolution. The new X Server comes up, but xfine states it is using "2560x960"!. The internal display's resolution seems to be correct, but the external resolution is set to 1280x960, causing the monitor to scale it. Also, the screen scrolls on both monitors. So even though I selected the appropriate resolutions before, the resulting configuration is unusable. At this point I aborted the configuration and saved the resulting file, which you can find in the "detached_modified" directory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c7 --- Comment #7 from Lenz Grimmer <lenz@grimmer.com> 2007-09-07 13:59:45 MST --- Created an attachment (id=162804) --> (https://bugzilla.novell.com/attachment.cgi?id=162804) Tarball containing the aforementioned xorg.conf files and Sax.log files -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c9 --- Comment #9 from Lenz Grimmer <lenz@grimmer.com> 2007-09-07 14:05:58 MST --- Created an attachment (id=162806) --> (https://bugzilla.novell.com/attachment.cgi?id=162806) Shot of the external screen when configuring X with the monitor attached These two pictures show how the display looks like with the proposal from SaX2 when the external monitor is attached to the screen. As you can see, there are artifacts and random garbage at the bottom. Using the keyboard to navigate the popup window works, but hitting the right buttons with the mouse is impossible... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c11 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |sndirsch@novell.com Component|SaX2 |X.Org QAContact|qa@suse.de |xorg-maintainer-bugs@forge.provo.novell.com Summary|sax2: can't configure a working dualhead |radeon: MergedFB with different resolutions is |configuration |broken --- Comment #11 from Stefan Dirsch <sndirsch@novell.com> 2007-09-07 15:14:42 MST --- This driver is so broken. I'm seriously considering to add the 6.6.3 radeon driver as fallback (calling it "radeonold"). We had this before I know ... detached_modified/SaX.log -------------------------- [...] (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled [...] (II) RADEON(0): Valid mode using on-chip RMX: 1280x1024 [...] (--) RADEON(0): Virtual size is 1280x1024 (pitch 1280) (**) RADEON(0): Default mode "1400x1050": 85.0 MHz (scaled from 0.0 MHz), 53.1 kHz, 50.0 Hz [...] (WW) RADEON(0): Mode "1440x900" is not a supported mode for CRT2 (WW) RADEON(0): (Skipping metamode "1400x1050,1440x900") (WW) RADEON(0): Mode "1440x900" is not a supported mode for CRT2 (WW) RADEON(0): (Skipping metamode "1280x1024,1440x900") (II) RADEON(0): Merged "1280x960" (1280x960) and "1280x960" (1280x960) to 2560x960 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c13 --- Comment #13 from Lenz Grimmer <lenz@grimmer.com> 2007-09-07 15:35:16 MST --- Created an attachment (id=162820) --> (https://bugzilla.novell.com/attachment.cgi?id=162820) xorg.conf Thanks a lot for looking into this, Stefan! Yes, I dimly remember we had similar problems in the past - the radeon driver seems to move from one brokenness to the next. In any case, I am now using the xorg.conf file (attached) from my 10.2 installation, which I manually set up and configured without SaX2. It still works with the radeon driver on 10.3b3, and still has the same flaw that I reported here: MergedFB: Second head still scrolls despite having enabled "MergedNonRectangular" https://bugs.freedesktop.org/show_bug.cgi?id=11156 According to the report, everything will be good with randr1.2 - it remains to be seen if this is really the case :) Thanks for the link, I will take a look at it and see how it goes. This page also has some useful information: http://www.thinkwiki.org/wiki/Xorg_RandR_1.2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c14 --- Comment #14 from Stefan Dirsch <sndirsch@novell.com> 2007-09-07 15:42:53 MST --- Ok. At least then it's no regression. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307456#c16 --- Comment #16 from Stefan Dirsch <sndirsch@novell.com> 2007-10-15 21:00:04 MST ---

This driver is so broken. I'm seriously considering to add the 6.6.3 radeon driver as fallback (calling it "radeonold"). We had this before I know ... I really did this. It's on openSUSE 10.3 final.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.