Summary: | "scroll bar" image deformation | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Brian Paterni <bpaterni> | ||||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | bpaterni, freedesktop | ||||||||
Version: | git | ||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Brian Paterni
2009-05-19 11:14:45 UTC
What chip are you using? Please attach your xorg log. Created attachment 26009 [details] [review] xorg.log whoops, ya I'm using an rv630 chip :: Radeon HD 2600 XT. Created attachment 26046 [details]
good image
Looks like it doesn't repeat the pattern (properly) but stretches it. *** Bug 22139 has been marked as a duplicate of this bug. *** fixed in ec1a3ccdf61c2226617b571cc4a209a542e9d7e3 Can confirm the fix resolves my issue. Thanks for all your work! This bug is certainly fixed on my desktop machine, but it apparently isn't on my laptop and I'm not sure why. My laptop has pretty much the same chip as my desktop (Mobility HD 2600 -- rv630) and is at latest git as well. However the fix presented in ec1a3ccdf61c2226617b571cc4a209a542e9d7e3 doesn't seem to be working on it. I've attempted to get kms/3d running on my laptop and as a result, I've compiled and installed off-distro programs. So I'm wondering if this could be the problem. (In reply to comment #8) > This bug is certainly fixed on my desktop machine, but it apparently isn't on > my laptop and I'm not sure why. > > My laptop has pretty much the same chip as my desktop (Mobility HD 2600 -- > rv630) and is at latest git as well. However the fix presented in > ec1a3ccdf61c2226617b571cc4a209a542e9d7e3 doesn't seem to be working on it. > > I've attempted to get kms/3d running on my laptop and as a result, I've > compiled and installed off-distro programs. So I'm wondering if this could be > the problem. > This bug was only present on git master. Make sure you are using the latest git master. 6.12-branch stable releases are not affected. Also, KMS is not supported yet on r6xx/r7xx chips. (In reply to comment #9) > This bug was only present on git master. Make sure you are using the latest git > master. 6.12-branch stable releases are not affected. Also, KMS is not > supported yet on r6xx/r7xx chips. > I believe I was on latest git master. To be certain however I did a fresh clone in a separate directory and built from there. And the bug is still present when I restart X. I've also tried out my distro provided package which is at 6.12.2 (I did uninstall my git driver before doing so) and it's still there. I'm not sure what is going on here since the bug is fixed on my desktop. Is there something besides radeon that could be causing this behavior? (In reply to comment #10) > I believe I was on latest git master. To be certain however I did a fresh clone > in a separate directory and built from there. And the bug is still present when > I restart X. > > I've also tried out my distro provided package which is at 6.12.2 (I did > uninstall my git driver before doing so) and it's still there. I'm not sure > what is going on here since the bug is fixed on my desktop. Is there something > besides radeon that could be causing this behavior? > Sounds like the versions you've built are not actually being used. By default the driver installs in /usr/local. Make sure the correct driver is being used when you start X. Also make sure you stop and start X rather than just logging out and back in. Yep, it turns I needed to remove a ModulePath from xorg.conf to prevent it from loading an old version of the driver. Thanks for your time Alex, although it did turn out to be human error in the end. |
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.