[M7 LW] [RV250] resolution incorrectly detected on various radeon cards

[Jamie Strandboge]

Binary package hint: xorg

In the installer, in gdm and on login, the resolution of my 1400x1050 display is incorrectly detected as 1600x1024. This results in banding and other issues. I can choose 1400x1050 by going to System/Preferences/Monitors and then my login session is fine (gdm is still wrong of course).

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 i686
Architecture: i386
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1400x1050 1280x1024 1280x960 1280x854 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Wed Sep 22 11:24:47 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100922)
Lsusb:
 Bus 004 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 2378RRU
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=abcbf331-1453-44ee-9d63-b4dfe39046c0 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 2378RRU
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2378RRU:pvrThinkPadT42:rvnIBM:rn2378RRU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2378RRU
dmi.product.version: ThinkPad T42
dmi.sys.vendor: IBM
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[Zsolt Tarsoly (tarsoly-zsolt)]

I have same problem with my IBM thinkpad t43. My original desktop resolution 1024x768, but the ubuntu default is 1360x768. (in gdm, or in new user desktop before settings monitor ...)

[Uwe Geuder (ubuntulp-ugeuder)]

Happens also on my IBM Thinkpad T40.

ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2,

Reproduced with http://cdimage.ubuntu.com/daily-live/current/ 24-Sep-2010

Work-around: xrandr --output LVDS --mode 1400x1050

[dpg77 (dpg77)]

also affect my ibm t42 with max res 1024x768 on ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]

this is not an issue with beta cdimage fresh install only after doing dist-upgrade it is affected

workaround i have been using at the gdm login screen pressing the fn f7 screen gets it to re-detect the screen resolution to 1024x768 and you can log in then. then desktop is ok after that

[Illogic_Gate (illogicgate)]

Having the same problem, though this bug seems to be a duplicate of bug <a href="https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/641525">#641525<a>

A way to fix the symptoms is also present at that bug page, though I suspect that the actual resolution detection issue is not really gone.

[Tormod Volden (tormodvolden)]

This is another example of gnome-settings-daemon trying to be smarter than the X server, see bug 640807.

Interestingly, the faulty 1600 mode does not show up in the modes list in the apport-collected bug summary, so it must have been injected later. Does g-s-d add new modes?

MrMacman2u, please file a bug report on your issue. You can refer to this and other bug reports in your report, but please make a complete report with all needed information, by using "ubuntu-bug xserver-xorg-video-ati".

[Tormod Volden (tormodvolden)]

From looking at Xorg.0.log it seems like xorg makes up the 1600 mode itself.

[dpg77 (dpg77)]

Last nights updates seem to of fixed it all working fine now.

[Uwe Geuder (ubuntulp-ugeuder)]

Yes, it works after applying the latest updates. There was no update to xorg-xserver-video-ati though, so it must have been a bug somewhere else. I had too many updates at once, cannot guess which one could have fixed this issue.

[Uwe Geuder (ubuntulp-ugeuder)]

oops sorry: I meant it works on my ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2, cannot speak for others.

[bugbot (bugbot)]

Hey Jamie,

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.