Forwarding this bug from Ubuntu reporter mikelietz: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/556631 [Problem] With dual-head enabled, the rightmost screen shows the right portion of the screen is corrupted. [Original Description] I have a Sapphire X550 Radeon. I installed Lucid Beta 1. The left monitor is 1680x1050. The right monitor is 1280x1024. The rightmost portion of the right monitor is unusable - in the picture below it's the black and white stripe. Only the mouse cursor shows up on it. http://www.ubuntu-pics.de/bild/50764/desk_1_002_6L0A6g.png The middle portion between the (default) wallpaper and the aforementioned stripe shows a trail of whatever I drag through it. If I move the monitors from side to side instead to top and bottom I get a smaller unusable area at the bottom of the second screen. Architecture: i386 Date: Tue Apr 6 11:51:05 2010 DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory 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 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) MachineType: Hewlett-Packard HP Compaq dc7600 Convertible Minitower Package: xserver-xorg-video-radeon 1:6.12.191-1ubuntu2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=ead67149-8e87-4949-9b21-6c9af313f872 ro quiet splash ProcEnviron: LANGUAGE= LANG=en_US.utf8ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: xserver-xorg-video-ati Uname: Linux 2.6.32-16-generic i686 dmi.bios.date: 05/18/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786D1 v01.03 dmi.board.name: 09F0h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA621114Z dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786D1v01.03:bd05/18/2005:svnHewlett-Packard:pnHPCompaqdc7600ConvertibleMinitower:pvr:rvnHewlett-Packard:rn09F0h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc7600 Convertible Minitower dmi.sys.vendor: Hewlett-Packard glxinfo: Error: [Errno 2] No such file or directory system: codename: lucid architecture: i686 kernel: 2.6.32-16-generic [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:3010] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV370 [Sapphire X550 Silent] [1002:5b63] Subsystem: Diamond Multimedia Systems Device [1092:3000]
Created attachment 34789 [details] XorgLog.txt
Created attachment 34790 [details] CurrentDmesg.txt
Created attachment 34791 [details] BootDmesg.txt
Disable desktop effects. The max texture size on r3xx/r4xx hardware is 2048x2048 pixels and your desktop is larger than that. Compiz should check the max texture size and refuse to load.
Thanks Alex, silly me, I should have checked that. It appears there has been a regression in the checking algorithm in compiz or something. I've forwarded the bug to them to investigate. Seems there is also a situation where if the resolution is exactly equal to the max texture size, compiz tries to run, when it shouldn't. https://bugs.edge.launchpad.net/ubuntu/lucid/+source/compiz/+bug/428769/
(In reply to comment #5) > Thanks Alex, silly me, I should have checked that. > > It appears there has been a regression in the checking algorithm in compiz or > something. I've forwarded the bug to them to investigate. Seems there is also > a situation where if the resolution is exactly equal to the max texture size, > compiz tries to run, when it shouldn't. > https://bugs.edge.launchpad.net/ubuntu/lucid/+source/compiz/+bug/428769/ On r1xx/r2xx, IIRC, there is an issue with textures or render targets over 2047 pixels. R3xx+ should be fine.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.