Summary: | [RV370] Portion of second monitor unusable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||
Status: | RESOLVED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | normal | ||||||||||
Priority: | high | CC: | codger | ||||||||
Version: | 7.4 (2008.09) | ||||||||||
Hardware: | x86 (IA32) | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Bryce Harrington
2010-04-07 20:27:13 UTC
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.