Summary: | DisplayPort on 3650 | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Mike Burns <mike> | ||||||||||||||||
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 | ||||||||||||||||||
Version: | 7.5 (2009.10) | ||||||||||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||||||||||
OS: | Linux (All) | ||||||||||||||||||
Whiteboard: | |||||||||||||||||||
i915 platform: | i915 features: | ||||||||||||||||||
Attachments: |
|
Description
Mike Burns
2010-02-08 10:57:55 UTC
Please attach dmesg and xorg log. Created attachment 33184 [details]
Xorg.log
My fault; I thought I had attached it before but I didn't double-check.
Created attachment 33185 [details]
dmesg
Is there anything else I can do to assist this ticket? Patches to try, git branches to compile, etc? can you check with latest kernel 2.6.33-rc8 or so? (In reply to comment #5) > can you check with latest kernel 2.6.33-rc8 or so? Same results. Attaching new dmesg and X log. Created attachment 33332 [details]
dmesg 2.6.33-rc8
Created attachment 33333 [details]
xorg.0.log with 2.6.33-rc8
Created attachment 33893 [details]
Linux 2.6.33 dmesg
Upgraded to Linux 2.6.33, attaching the dmesg.
Created attachment 33894 [details]
Xorg log
Updated to the latest xf86-video-ati driver from git, attaching the Xorg log.
Created attachment 33895 [details]
xrandr
Upgraded to the latest xf86-video-ati from git, attaching the xrandr output.
You are mixing a KMS drm with UMS in the ddx. Make sure the radeon drm is loaded before you start X otherwise both drivers (drm and ddx) will attempt to drive the hardware. Alex, that tip fixed it. Thank you. I added `radeon' to /etc/modules and it now works. |
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.