Bug 132687

Summary:	display configured 1280x1024 in sax2 but starts as 800x600
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	michel munnix <michel.munnix>
Component:	SaX2	Assignee:	Stefan Dirsch <sndirsch>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P2 - High
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	xorg.conf Xorg.0.log new Xorg.0.log

Description michel munnix 2005-11-08 09:16:15 UTC

Installation has been performed in 1280x1024, so monitor and graphics adapter support it, but at first user login in Xwindow, it displays 800x600 whith a virtual display of 1280x1024.
In /var/log/Xorg.0.log there is something about CRT1 and CRT2 but there is only one vga connector present
hardware is IBM e-server xSeries 336 with ATI Radeon VE
monitor is IBM 6331

Comment 1 michel munnix 2005-11-08 09:17:29 UTC

Created attachment 56658 [details]
xorg.conf

Comment 2 michel munnix 2005-11-08 09:18:10 UTC

Created attachment 56659 [details]
Xorg.0.log

Comment 3 Marcus Schaefer 2005-11-08 11:22:17 UTC

really strange the driver is using MergedFB but the configuration
didn't told him to do that ?? Stefan, Matthias any idea why radeon told
us:

(II) RADEON(0): Generating MergedFB mode list
(II) RADEON(0): No MetaModes given, linking first modes by default
(II) RADEON(0): Merged 800x600 and 1280x1024 to 1280x1024 (Clone)

Thanks

Comment 4 Stefan Dirsch 2005-11-08 11:53:50 UTC

(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): Valid Mode from Detailed timing table: 800x600

The driver thinks CRT1 can only do 800x600. Then it tries to establish a mergedfb configuration and gets 1280x1024 on CRT2, which simply does *not* exist. This looks like a broken driver behaviour to me. Anyway, comment
the line 

  UseModes     "Modes[0]"

for now and let us know, whether this helps (including new logfile).

Comment 5 michel munnix 2005-11-08 12:50:32 UTC

Created attachment 56673 [details]
new Xorg.0.log

whith the line commented out, it works like a charm, now the display is in 1280x1024

Comment 6 Stefan Dirsch 2005-11-08 13:47:36 UTC

Looks like the driver does not like the SaX2 generated modelines ...

--- Xorg.0.log  2005-11-08 14:25:57.744186105 +0100
+++ Xorg.0.log.new      2005-11-08 14:24:06.959554993 +0100
 (II) RADEON(0): Validating modes on Primary head ---------
 (II) RADEON(0): Valid Mode from Detailed timing table: 800x600
-(II) RADEON(0): Total of 1 mode(s) found.
-(II) RADEON(0): Total number of valid DDC mode(s) found: 1
+(II) RADEON(0): Valid Mode from standard timing table: 640x480
+(II) RADEON(0): Valid Mode from standard timing table: 800x600
+(II) RADEON(0): Valid Mode from standard timing table: 1024x768
+(II) RADEON(0): Valid Mode from standard timing table: 1280x1024
+(II) RADEON(0): Valid Mode from established timing table: 1024x768
+(II) RADEON(0): Valid Mode from established timing table: 1024x768
+(II) RADEON(0): Valid Mode from established timing table: 800x600
+(II) RADEON(0): Valid Mode from established timing table: 800x600
+(II) RADEON(0): Valid Mode from established timing table: 640x480
+(II) RADEON(0): Valid Mode from established timing table: 640x480
+(II) RADEON(0): Total of 11 mode(s) found.
+(II) RADEON(0): Total number of valid DDC mode(s) found: 11

Comment 7 Stefan Dirsch 2005-11-08 16:43:05 UTC

AFAIK these issues have been fixed in X.Org CVS. Please reopen if you see these problems with 10.1 (Alpha) again.