[i915] Regression from Lucid DVI + LVDS screen corrupted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
In Lucid I had dual monitor setup with my Dell D610 laptop connected to Dock station.
I've had DVI(1280x1024)
After upgrade to Maverick same setup behaves weird. In Preferences-
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
DRM.card0.DVI.D.1:
status: connected
enabled: enabled
dpms: On
modes: 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
edid-base64: AP/////
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1400x1050
edid-base64: AP/////
DRM.card0.VGA.1:
status: unknown
enabled: disabled
dpms: Off
modes: 1024x768 800x600 800x600 848x480 640x480
edid-base64:
Date: Sat Oct 2 14:33:48 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
MachineType: Dell Inc. Latitude D610
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=UUID=
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 10/02/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0D4571
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D610
dmi.sys.vendor: Dell Inc.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-22-generic
affects: | xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu) |
tags: | added: lucid |
tags: | added: corruption |
Hey Chaostya,
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.