Summary: | PLLs chosen that cause flicker on dual-link DVI monitor. | ||
---|---|---|---|
Product: | xorg | Reporter: | Chris Ball <chris-fdbugs> |
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: | arequipeno |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Chris Ball
2008-08-13 16:17:32 UTC
Alex and I tried some PLL changes that had different results. Broken (post-patch): 268/9/3 Fixed (pre-patch): 1072/27/4 Almost working, still occasional flicker: 804/27/3 The 804/27/3 was reached via: <agd54> try changing line 232 of radeon_crtc.c <agd5f> change the '<' to '>' } else if ((flags & RADEON_PLL_PREFER_LOW_REF_DIV) && (ref_div < best_ref_div)) { fixed in git: 92ee21df344a989778e37369c7beb3904a00ead6 > fixed in git:
> 92ee21df344a989778e37369c7beb3904a00ead6
This gets me back to 804/27/3, which means that I still have the flicker regression behavior. Alex says he'll fix up the patch, and I'll retest then.
Mea culpa, stale driver. This correctly finds 1072/27/4, closing. I'm seeing something that may be the "occasional flicker" behavior. I suspect it may be PLL-related, because I am able to fix it with the radeonhd driver by using the "AtomBIOS" "pll=on" option. How can I determine if the driver version in Fedora 10 includes this fix? Thanks! (In reply to comment #5) > I'm seeing something that may be the "occasional flicker" behavior. I > suspect it may be PLL-related, because I am able to fix it with the > radeonhd driver by using the "AtomBIOS" "pll=on" option. > > How can I determine if the driver version in Fedora 10 includes this > fix? Do you have a 2560x1600 monitor? This bug and fix really only relates to high dot clocks. If you are using a different monitor please file a new bug and attach your xorg log and config. |
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.