328553 – X11 is starting only with a resolution of 1024x768 using xrandr allows more later

Bug 328553 - X11 is starting only with a resolution of 1024x768 using xrandr allows more later

Summary: X11 is starting only with a resolution of 1024x768 using xrandr allows more l...

Status:	RESOLVED DUPLICATE of bug 257746

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	X.Org (show other bugs)
Version:	RC 1
Hardware:	x86-64 openSUSE 10.3

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Stefan Dirsch
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-09-26 15:09 UTC by Dirk Laurenz
Modified:	2007-09-26 15:27 UTC (History)
CC List:	1 user (show)

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

Attachments
Xorg conf (4.29 KB, application/octet-stream) 2007-09-26 15:09 UTC, Dirk Laurenz	Details
the log file with error exceeds panel size (230.28 KB, text/x-log) 2007-09-26 15:10 UTC, Dirk Laurenz	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 Dirk Laurenz 2007-09-26 15:09:01 UTC

Created attachment 174877 [details]
Xorg conf 

I installed today 10.3 RC 1 on an Fujitsu Siemens Esprimo Q5020 with Intel 965 Chipset graphics. X refuses to start with more than 1024x768 and sax also although  sax recognizeses the monitor correctly. (Fujitsu Siemens P20-W)

setting the monitor resolution to 1680x1050 with xrandr -s 1680x1050 sets the resolution correctly. the monitor is connected directly via DVI. 

The esprimo only has a DVI port.

Comment 1 Dirk Laurenz 2007-09-26 15:10:22 UTC

Created attachment 174879 [details]
the log file with error exceeds panel size

Comment 2 Stefan Dirsch 2007-09-26 15:27:14 UTC

Known issue. See Bug #257746, comment #30 for a workaround for now. Check xorg.conf manual page.

*** This bug has been marked as a duplicate of bug 257746 ***