Thinkpad T30: Auto-detection selects wrong screen resolution

Bug #657113 reported by Daniel Kulesz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I was trying to execute various Test Cases from http://testcases.qa.ubuntu.com/Plans/LaptopTesting with 10.10-rc i386 on a Thinkpad T30 (see https://wiki.ubuntu.com/Testing/Laptop/Reports/IBMThinkpadT30 for Details).

The machine seems to boot up with the wrong screen resolution. It detects and sets a resolution of 1600x1024 pixels instead of the real 1400x1050, leading to a garbled screen output (especially on the right side of the screen). After switching the resolution to 1400x1050 via the control panel, the screen looks okay, but video playback seems to be broken and moving windows along is extremely slow.
---
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:
DistroRelease: Ubuntu 10.10
GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
Lsusb:
 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:0001 Linux Foundation 1.1 root hub
MachineType: IBM 236692G
Package: xorg 1:7.5+6ubuntu3
PackageArchitecture: i386
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Tags: maverick maverick
Uname: Linux 2.6.35-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/16/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1IET71WW (2.10 )
dmi.board.name: 236692G
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:bvr1IET71WW(2.10):bd06/16/2006:svnIBM:pn236692G:pvrNotAvailable:rvnIBM:rn236692G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 236692G
dmi.product.version: Not Available
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

Revision history for this message
Daniel Kulesz (kuleszdl) wrote :

Additional information: The problem has not been observed in the first beta release.

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Hi Daniel,
  I've flipped this bug to the Xorg package; can you run

apport-collect 657113

it should add a load of extra diagnostics about your machines X config to this bug.

Dave

affects: linux (Ubuntu) → xorg (Ubuntu)
Revision history for this message
Daniel Kulesz (kuleszdl) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Daniel Kulesz (kuleszdl) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : DRM.card0.SVIDEO.1.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : Dependencies.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : GdmLog.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : Lspci.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : PciDisplay.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : ProcModules.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : UdevDb.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : UdevLog.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : XorgLog.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : XorgLogOld.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : Xrandr.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : peripherals.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : setxkbmap.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : xdpyinfo.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote : xkbcomp.txt

apport information

Revision history for this message
Daniel Kulesz (kuleszdl) wrote :

Okay, seems like it arrived. Why does apport-collect not put everything in one posting? :(

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

OK, put to the ATI xserver.
I could swear this is the 2nd one I've seen like this in the last few days.

affects: xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Yeh it's bug 654170 that looks suspiciously similar to me.

Dave

Revision history for this message
Daniel Kulesz (kuleszdl) wrote :

It seems like the machine / graphics card in bug651470 is pretty different, but the symptoms seem to be the same. If you want, mark this one as duplicate.

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Well their both Radeons and their both laptops misidentifying LCD sizes ; so it doesn't seem too far a stretch.

I wasn't going to dupe this, I'll let the guys who know the inside of the server figure it out.

dave

Revision history for this message
Daniel Kulesz (kuleszdl) wrote :

Well, the other reporter has a much newer R420-based Radeon, and I got the very first Radeon 7500. I thought newer Radeon GPUs would run the new radeonhd, while older ones (like mine) are running the old Radeon driver. I didn't inspect the logs in detail, but if the same driver was used, I suspect this could be the same problem.

Bryce Harrington (bryce)
tags: added: maverick
bugbot (bugbot)
tags: added: resolution
Revision history for this message
bugbot (bugbot) wrote :

Hey Daniel,

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.

Changed in xserver-xorg-video-ati (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel Kulesz (kuleszdl) wrote :

Sorry, I have sold the T30 a few weeks ago, thus I can not contribute to this bug anymore.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

ok, closing the bug.

Changed in xserver-xorg-video-ati (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.