Summary: | X1650 dual-DVI "flickers" with different modelines | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Ian Pilcher <arequipeno> | ||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | 7.4 (2008.09) | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Ian Pilcher
2010-02-22 09:33:54 UTC
Please attach your xorg log and config, and if you are using KMS, your dmesg. Created attachment 33495 [details]
Xorg.0.log (identical modelines)
Created attachment 33496 [details]
dmesg (identical modelines)
Can you try this patch for KMS: http://people.freedesktop.org/~agd5f/0001-drm-radeon-kms-update-new-pll-algo.patch or xf86-video-ati git master for UMS? If you want to test UMS, add radeon.modeset=0 to your kernel command line. (In reply to comment #4) > Can you try this patch for KMS: > http://people.freedesktop.org/~agd5f/0001-drm-radeon-kms-update-new-pll-algo.patch I tried to rebuild the Fedora kernel SRPM, with that patch added, but I can't get that patch to apply at all. What kernel version is it against? (In reply to comment #5) > (In reply to comment #4) > > Can you try this patch for KMS: > > http://people.freedesktop.org/~agd5f/0001-drm-radeon-kms-update-new-pll-algo.patch > > I tried to rebuild the Fedora kernel SRPM, with that patch added, but I can't > get that patch to apply at all. What kernel version is it against? > It's against the drm-radeon-testing branch of airlied's drm tree: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing Also, does the patch on bug 26668 help? It should apply to just about any recent kernel. closing due to lack of feedback. |
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.