| Summary: | radeon : Screen flickers on the right side with visual effects enabled | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Luca Bonora <dragon_fog> |
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Luca Bonora
2009-06-21 00:54:31 UTC
This is because driver is missing RDR (redirected rendering) support. It will be added to opengl driver with KMS (kernel modesetting) and DRI2. If you don't mind testing code that is not yet stable you can try Ubuntu live CD from https://launchpad.net/~xorg-edgers/+archive/radeon-kms Hopefully we will see this fixed in Karmic Koala (9.10). *** This bug has been marked as a duplicate of bug 9253 *** I tried the live CD right now and it works!The issue is fixed!Do you think it's possible to install it on Jaunty?How can I do it? You forgot to read the instruction part in that radeon-kms page :) "If you install these packages on Jaunty (nobody said you should try that), add Driver "ati" to your xorg.conf." Problem with that is there is still quite a number of outstandting bugs so you might be lucky not to have problems with them or suddenly everything might turn to be unusable. So if you are ready to be beta tester for new driver that is just about to move to bug fixing. I just want to make sure tht you understand that what is in radeon-kms page. It is alpa/beta quality driver that might just barely be able to make to next Ubuntu release. (and might well have outstanding problem still in October) Actually the flickering is probably due to underflow in the display engine due to improper display watermark setup. I fixed this is git a while ago. Note, I think the watermark code still needs to be ported to kms. |
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.