[Karmic,Lucid] 82G33/G31 Card Fails to detect proper resolutions

Bug #578460 reported by Evan Huus
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: xorg

Started at Jaunty, everything worked great.

Upgraded to Karmic yesterday, saw the issue. Upgraded to lucid today, the issue persists.

The monitor should be at 1680x1050. The Preferences>Monitors dialog reports the current resolution as 1360x768, but the monitor itself reports it as 1280x768.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Mon May 10 15:55:42 2010
DkmsStatus:
 virtualbox-ose, 3.1.6, 2.6.31-21-generic, x86_64: built
 virtualbox-ose, 3.1.6, 2.6.32-22-generic, x86_64: installed
MachineType: Dell Inc. Vostro 200
ProcCmdLine: root=UUID=612943a2-c964-401b-95b5-5de3264a6a64 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 06/23/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.15
dmi.board.name: 0CU409
dmi.board.vendor: Dell Inc.
dmi.board.version: ���
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/23/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Vostro 200
dmi.sys.vendor: Dell Inc.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

Revision history for this message
Evan Huus (eapache) wrote :
Bryce Harrington (bryce)
affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Evan Huus (eapache) wrote :

Oddly enough, after three reboots the situation has changed slightly.

Now the monitor is detected 'correctly' (it is listed as a "Dell 22 Inch" instead of "unknown"), but the list of resolutions is even worse than before. It can only go up to 1024x768, and has no 16x9 or 16x10 resolutions available.

I didn't apply any updates or change any configuration that I can recall.

Revision history for this message
Evan Huus (eapache) wrote :

And after another reboot it's back to the old behavior. I'll try and nail down what causes the different behaviors, but at this point it seems completely random.

Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Evan Huus (eapache) wrote :

A little more progress. Disabling kernel mode-setting (with nomodeset in grub) seems to consistently force it into the state described by comment #2 (correctly named, with an even smaller list of available resolutions).

Revision history for this message
Evan Huus (eapache) wrote :

Very peculiar.

I managed to get my hands on a second machine with the same graphics card, and it works fine (using the exact same monitor). Here's the card's section of lspci on the second machine:

00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)
 Subsystem: Dell Device 0238
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 26
 Region 0: Memory at fdf00000 (32-bit, non-prefetchable) [size=512K]
 Region 1: I/O ports at ff00 [size=8]
 Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M]
 Region 3: Memory at fdb00000 (32-bit, non-prefetchable) [size=1M]
 Capabilities: <access denied>
 Kernel driver in use: i915
 Kernel modules: i915

Also, Fedora 13 (using Xorg 1.8) works fine on both. When I have some time I'll see if using 1.8 from the xorg-edgers ppa fixes it on the other machine.

Revision history for this message
penalvch (penalvch) wrote :

Evan Huus, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg-server (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Evan Huus (eapache) wrote :

I haven't had that hardware in a couple of years, so this can expire unless anybody else is still experiencing it.

Revision history for this message
penalvch (penalvch) wrote :

Evan Huus, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/578460/comments/7 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in xorg-server (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.