Bug 241098

Summary:	sax2 fails to configure external vga out correctly
Product:	[openSUSE] openSUSE 10.2	Reporter:	Sebastian Reitenbach <reitenbach>
Component:	SaX2	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	angie
Version:	Final
Target Milestone:	---
Hardware:	32bit
OS:	Linux
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	xorg.conf file created via SaX2

Description Sebastian Reitenbach 2007-02-01 14:11:09 UTC

the problem is more or less described here:
https://bugzilla.novell.com/show_bug.cgi?id=235127

as this bug was closed, as a duplicate, and the original bug was closed as fixed too, I installed the sax patch, and tried to reconfigure the screen.

the LCD is setup correctly, 1680x1050, and the external vga connector is configured with sax to be 1024x768. 
But when connecting the projector to it, the screen is 1024x1024@60Hz, on the left side, about 3-5 centimeters are missing (some contents I can see on the notebook lcd)

in /etc/sysconfig/videobios, the following is configured:
VIDEOBIOS_PARAMETERS="30 1680 1050"


with the above line, 915resolution -l shows the following:

Intel 800/900 Series VBIOS Hack : version 0.5.2

Chipset: 945GM965G
BIOS: TYPE 1
Mode Table Offset: $C0000 + $269
Mode Table Entries: 36

Mode 30 : 1680x1050, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1920x1440, 8 bits/pixel
Mode 41 : 1680x1050, 16 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4d : 1920x1440, 16 bits/pixel
Mode 50 : 1680x1050, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1920x1440, 32 bits/pixel

expected behaviour:
the external vga outlet should use the configured 1024x768@60Hz.

Comment 1 Sebastian Reitenbach 2007-02-01 14:12:04 UTC

Created attachment 116830 [details]
xorg.conf file created via SaX2

Comment 2 Marcus Schaefer 2007-02-01 14:26:24 UTC

Thank you for splitting up your issue, we are now on the right track again :-)
The resolution 1024x1024 sound quite strange to me and looks like a driver
problem. The attached configuration looks good to me.

Matthias I think you have checked dual head in Intel a bit, have you
seen this problem ? I remember a discussion that it is broken with Intel
as soon as the resolutions are different. Clone mode should be active
concerning this report

Comment 3 Sebastian Reitenbach 2007-02-12 13:29:23 UTC

I installed the MesaGLw-6.5.2-13, Mesa-devel-6.5.2-17, Mesa-6.5.2-17, libdrm-2.3.0-7 from http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/
because of the newer versions there available. SaX2, xorg-11 were the same as the installed ones I have on SuSE 10.2.

Now the resolution of the external VGA outlet is still set to 1024x1024, but at least the missing five centimeters are displayed on the wall. (when I use 3c as the mode in /etc/sysconfig/videobios, when I use e.g. 30 as the mode in /etc/sysconfig/videobios, then three centimeters of the screen are missing at the left side) It doesn't make a difference, whether I configure 1024x768 or 1200x1024 for the external port. Always 1024x1024 is used on the external vga port.

I also tried to use the system without the videobis hack. X11 starts up, with the wrong resolution on the Display, seems to be a 1280x1024, but not the 1680x1050. Therefore, I did an init 3, and started SaX2. It suggested the wrong resolution. Therefore changing the configuration, activating dual head mode, and 3D, I saw the correct resolution on the LCD, but on the external VGA output, still 1024x1024 (without the missing five centimeters on the left).
with this configuration, after a reboot, the wrong (too low) resolution is used on the LCD screen.
I cannot init 5 after using SaX, the X11 ends up with the error No screens found, I have to reboot, to be able to start X11 again.

Comment 4 Sebastian Reitenbach 2007-02-12 14:10:56 UTC

When I cycle through the resolutions via Ctrl+Alt+ + and Ctrl+Alt+ -, then inbetween the external resolution changes to 1024x768, unfortunately the virtual resolution is larger (seems to be the 1680x1050). If I remember correctly, some SuSE versions before, SaX had an option to configure the virtual resolution, which I cannot find anymore.
So I added lines: Virtual 1024 768 
to the Display SubSections in /etc/X11/xorg.conf
This fixed the problem for the external display, but now on the internal LCD, the resolution is also only 1024x768.

Comment 5 Sebastian Reitenbach 2007-02-13 17:15:11 UTC

I asked on the opensuse-laptop list, and got an answer, I should use the resapplet tool, which I did. While the resolution on the projector is fine 4>3, it is stretched on the LCD, but I am fine with that.
So if you do not want to take a close look why SaX fails in the first place to configure the external port, feel free to close it.

Thanks for looking into the issue.

Comment 6 Marcus Schaefer 2007-02-14 08:42:35 UTC

As there is no information from Matthias I will close this as a "remind"

Comment 7 Matthias Hopf 2007-03-02 16:50:18 UTC

Sorry for the delay.

The intel clone mode is an *exact* clone mode. That is, the external output will have the same signal as the internal one. Somehow, either the output driver or the projector/monitor mixes that up and says it is 1024x1024 while in fact it is 1680x1050.

Still you're lucky with your configuration. Just take it as it is, and use "xrandr" or the resolution selection tool of your favorite desktop (e.g. krandrtray) to select 1024x768 as resolution when you want to use the external output. Given your problem description this will work. Of course you will only have 1024x768 on your internal display then, but that's how clone mode works.

Comment 8 Matthias Hopf 2007-03-02 16:53:26 UTC

(In reply to comment #5)
> So if you do not want to take a close look why SaX fails in the first place to
> configure the external port, feel free to close it.

Sax didn't fail, as far as I read that.

Closing as INVALID, as in fact this whole thing is not a bug, but a limitation to the driver *and* to the general work mode in a cloned head environment.