dual monitor - corruption (partial or complete) or flimmering or out of range

[Bastian]

Binary package hint: xserver-xorg-video-ati

multiple problems with external display enabled on laptop with x300 card

1) internal 1024x768, external 1680x1050
half of background and part of panel of internal display corrupted
(see attached png);
only with kms and compiz enabled. disabling compiz solves this. In the actual lucid version compiz is automaticly disabled for this situation;

2) mirroring (both 1024x768)
ok with and without compiz

3) side by side with same resolution (1024x768)
both display complete corrupted (with and without compiz)

4) external 1024x768, internal off
external flimmering (with and without compiz)

5) external 1680x1050, internal off
out off range (with and without compiz)

6) internal 1024x768, external off
all ok (with and without compiz)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-ati 1:6.13.1-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CurrentDmesg:
 [ 36.768055] eth4: no IPv6 routers present
 [ 76.190423] lib80211_crypt: registered algorithm 'WEP'
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: 1024x768 800x600 848x480 720x480 640x480
 edid-base64:
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1360x768 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
 edid-base64: AP///////wANrygiAQEBAQURAQNoLx54LsWFpFlJmiQSUFS/7wCBgIFAcU+VAJUPswCBwIvAITmQMGIaJ0BosDYA2SgRAAAcAAAA/QA4TB5SFQAKICAgICAgAAAA/ABDTUMgMjIgVwogICAgAAAA/wAwCiAgICAgICAgICAgAKU=
Date: Wed Oct 6 16:39:52 2010
DkmsStatus:
 tp-smapi, 0.40, 2.6.35-22-generic, i686: installed
 tp-smapi, 0.40, 2.6.35-14-generic, i686: installed
 tp-smapi, 0.40, 2.6.36-999-generic, i686: installed
 tp-smapi, 0.40, 2.6.35-20-generic, i686: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
MachineType: IBM 266844G
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic root=/dev/mapper/hostname-root ro quiet splash
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-ati
dmi.bios.date: 11/07/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1YET59WW (1.24 )
dmi.board.name: 266844G
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:bvr1YET59WW(1.24):bd11/07/2005:svnIBM:pn266844G:pvrThinkPadT43:rvnIBM:rn266844G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 266844G
dmi.product.version: ThinkPad T43
dmi.sys.vendor: IBM
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[Bastian (jemand-habmalnefrage)]

cannot reproduce part 3 (side by side with same resolution (1024x768)) anymore

[bugbot (bugbot)]

Hey Bastian,

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.