Bug 13067

Summary:

Radeon driver doesn't respect virtual desktop size

Product:

xorg

Reporter:

Andreas Pakulat <apaku>

Component:

Driver/Radeon

Assignee:

xf86-video-ati maintainers <xorg-driver-ati>

Status:

RESOLVED INVALID

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

Version:

7.3 (2007.09)

Hardware:

Other

OS:

All

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
xorg.conf for 3080x1050 desktop	none
xorg.log for trying a 3080x1050 desktop	none

Description Andreas Pakulat 2007-11-02 17:01:13 UTC

Using XRandR 1.2 with the latest git version (last log entry is from Sun Oct 28th 21:10) of the radeon driver I can't get a virtual desktop of 3080x1050.

I have a Laptop with a widescreen display running on 1680x1050 and a CRT which can run 1600x1200 at max. With Xorg 7.2 and Xinerama I've used a 1400x1050 resolution on the CRT, but this doesn't work anymore with XRandR.

When using the attached xorg.conf I get the xrandr output that the minimum size is 320x200, current size is 3360x1050 and the maximum is 3080x1050. And the display is broken too, as part of my xterm is cloned on the outer right of the right display.

I can force the CRT to run at 1680x1050 with an according modeline, however that distorts all fonts and stretches them vertically.

I'll also attach the Xorg.log

Comment 1 Andreas Pakulat 2007-11-02 17:02:48 UTC

Created attachment 12325 [details]
xorg.conf for 3080x1050 desktop

Comment 2 Andreas Pakulat 2007-11-02 17:03:29 UTC

Created attachment 12327 [details]
xorg.log for trying a 3080x1050 desktop

Comment 3 Alexander Goomenyuk 2007-11-30 13:47:52 UTC

I had the similar problem.

I had got wxsga+ monitor (22'). And I tried to use 1680x1050 mode. But I always got 1400x1050 resolution. Until I set UseFBDev. After that resolution is fine.

Comment 4 Alex Deucher 2007-11-30 13:56:44 UTC

(In reply to comment #3)
> I had the similar problem.
> 
> I had got wxsga+ monitor (22'). And I tried to use 1680x1050 mode. But I always
> got 1400x1050 resolution. Until I set UseFBDev. After that resolution is fine.
> 

UseFBDev is no longer a valid option so you must be using an old version of the driver.

Comment 5 Alex Deucher 2007-11-30 14:03:01 UTC

(In reply to comment #0)
> Using XRandR 1.2 with the latest git version (last log entry is from Sun Oct
> 28th 21:10) of the radeon driver I can't get a virtual desktop of 3080x1050.
> 
> I have a Laptop with a widescreen display running on 1680x1050 and a CRT which
> can run 1600x1200 at max. With Xorg 7.2 and Xinerama I've used a 1400x1050
> resolution on the CRT, but this doesn't work anymore with XRandR.

Does it work ok if you turn off the CRT and them use xrandr to set up dualhead?
xrandr --output VGA-0 --off
xrandr --output VGA-0 --mode 1400x1050_85.00
xrandr --output VGA-0 --left-of LVDS

Comment 6 Andreas Pakulat 2007-11-30 17:47:17 UTC

(In reply to comment #5)
> (In reply to comment #0)
> > Using XRandR 1.2 with the latest git version (last log entry is from Sun Oct
> > 28th 21:10) of the radeon driver I can't get a virtual desktop of 3080x1050.
> > 
> > I have a Laptop with a widescreen display running on 1680x1050 and a CRT which
> > can run 1600x1200 at max. With Xorg 7.2 and Xinerama I've used a 1400x1050
> > resolution on the CRT, but this doesn't work anymore with XRandR.
> 
> Does it work ok if you turn off the CRT and them use xrandr to set up dualhead?
> xrandr --output VGA-0 --off
> xrandr --output VGA-0 --mode 1400x1050_85.00
> xrandr --output VGA-0 --left-of LVDS

See bug: http://bugs.freedesktop.org/show_bug.cgi?id=13068
can't use that method, though from the "looks" on the VGA it seems to work, i.e. the text seems to have the same proportion on both screens.

Comment 7 Alex Deucher 2008-12-03 00:41:21 UTC

Is this still an issue with a newer driver (6.9.0 or newer)?

Comment 8 Alex Deucher 2010-10-19 15:42:42 UTC

closing due to lack of feedback.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.