Bug 538858

Summary: X.org built-in configuration won't let me utilize full resolutions when using two displays
Product: [openSUSE] openSUSE 11.2 Reporter: Jeff Mahoney <jeffm>
Component: X.OrgAssignee: Forgotten User Wum0mkMcd8 <forgotten_Wum0mkMcd8>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Major    
Priority: P5 - None CC: sndirsch
Version: Milestone 7   
Target Milestone: ---   
Hardware: All   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screen shot of failed display dialog
Xorg.0.log
Xorg.0.log

Description Jeff Mahoney 2009-09-14 02:18:34 UTC
Created attachment 318027 [details]
Screen shot of failed display dialog

My workstation is a notebook (Thinkpad T60p) with two external displays. One is connected via external VGA and the other is connected via external DVI-D. In the past, I've had to keep a copy of my manually-edited xorg.conf in order to get the displays to work as expected. Milestone 7 appears not to require an xorg.conf at all, which is pretty awesome.

The way my system has been configured for the past two years is to have the DVI-D display on the left with a resolution of 1680x1050 and the VGA monitor on the right with a resolution of 1600x1200. The internal display is turned off.

The configuration that it chooses limits the frame buffer to 2560x2560. Attempts to resize the screen via xrandr fail:

jeffm@galileo:~> xrandr --fb 3280x1280
xrandr: screen cannot be larger than 2560x2560 (desired size 3280x1280)

Likewise, attempts configure it this way using the GNOME tool fail. I've attached a screen shot.

The displays are limited to both being 1280x1024, which reaches the 2560 horizontal limit.
Comment 1 Jeff Mahoney 2009-09-14 02:22:03 UTC
Created attachment 318029 [details]
Xorg.0.log
Comment 2 Jeff Mahoney 2009-09-14 02:24:01 UTC
Created attachment 318030 [details]
Xorg.0.log
Comment 3 Jeff Mahoney 2009-09-14 02:24:18 UTC
*** Bug 538859 has been marked as a duplicate of this bug. ***
Comment 4 Stefan Dirsch 2009-09-14 02:57:04 UTC
dup.

*** This bug has been marked as a duplicate of bug 519261 ***
Comment 5 Stefan Dirsch 2009-09-14 03:00:30 UTC
*** Bug 538857 has been marked as a duplicate of this bug. ***