On T400 with integrated Radeon HD 3400 cannot xrandr --fb 3200x1200

[mback]

Binary package hint: xorg

Previous to this weekend's x.org update, the max resolution possible on this cpu/chipset (ThinkPad T400 with integrated Radeon HD 3400) was 3200x1200 (I use this for dual external monitors). I am instead currently limited to 3040x1200 which is not enough to drive dual external 1600x1200 monitors. This symptom is evident under either fglrx or mesa drivers. Here is my current xrandr output:

$ xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 3040 x 1200
LVDS connected 1440x900+0+0 (normal left inverted right x axis y axis) 304mm x 190mm
   1440x900 60.2*+ 50.0
   1280x800 60.0 + 50.0
   1152x864 60.0 + 50.0
   1280x768 59.9 + 50.0
   1280x720 60.0 + 50.0
   1024x768 60.0 + 50.0
   1024x600 60.4 + 50.0
   800x600 60.3 + 50.0
   800x480 60.0 + 50.0
   720x480 60.0 + 50.0
   640x480 60.0 + 50.0
DFP1 connected (normal left inverted right x axis y axis)
   1600x1200 60.0 +
   1400x1050 60.0 +
   1440x900 59.9 +
   1152x648 60.0 +
   1280x1024 85.0 75.0 60.0
   1280x960 60.0
   1280x800 85.0 75.0 60.0
   1152x864 85.0 75.0 60.0
   1280x768 59.9
   1280x720 60.0
   1024x768 85.0 75.0 70.1 60.0
   1024x600 60.0
   800x600 85.1 75.0 70.0 60.3
   800x480 60.0
   720x480 60.0
   640x480 85.0 75.0 60.0
CRT1 connected (normal left inverted right x axis y axis)
   1600x1200 60.0 + 75.0
   1400x1050 60.0
   1280x1024 85.0 75.0 60.0
   1440x900 59.9
   1280x960 60.0
   1280x800 85.0 75.0 60.0
   1152x864 85.0 75.0 60.0
   1280x768 59.9
   1280x720 60.0
   1024x768 85.0 75.0 70.1 60.0
   1024x600 60.0
   800x600 85.1 75.0 70.0 60.3
   800x480 60.0
   720x480 60.0
   640x480 85.0 75.0 60.0
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
$

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue Sep 28 09:54:47 2010
DkmsStatus: fglrx, 8.780, 2.6.35-22-generic, x86_64: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
MachineType: LENOVO 2767A15
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=37a88bd3-6f84-44d0-9bbd-41bb980023bb ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 10/13/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET79WW (3.09 )
dmi.board.name: 2767A15
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7UET79WW(3.09):bd10/13/2009:svnLENOVO:pn2767A15:pvrThinkPadT400:rvnLENOVO:rn2767A15:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2767A15
dmi.product.version: ThinkPad T400
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

[bugbot (bugbot)]

Hey mback,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.