Summary: | 120 wakeups/s with Radeon XPress 200M | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Javier Kohen <jkohen> | ||||||||||||||
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: | x86 (IA32) | ||||||||||||||||
OS: | Linux (All) | ||||||||||||||||
Whiteboard: | |||||||||||||||||
i915 platform: | i915 features: | ||||||||||||||||
Attachments: |
|
Description
Javier Kohen
2007-12-11 22:32:47 UTC
XPRESS support is generally buggy as it was added by trial and error. Hopefully that will change soon. In any case, please attach your xorg log, config, and xrandr output. Created attachment 13050 [details]
XRandr output before --off/after --auto
Created attachment 13051 [details]
XRandr output after --off
Created attachment 13052 [details]
X.org configuration
Created attachment 13053 [details]
X.org log
Created attachment 13058 [details]
Simplified X.org configuration
Created attachment 13059 [details]
X.org log for simplified configuration
I found out that when X is restarted I get no interrupts from the card and 3D works alright. However, it goes up to 120 as soon as I switch back and forth from the Linux (text) console, so I guess switching to the console is what triggers this problem. I tried turning off DynamycClocks to no avail. I also tried enabling framebuffer on the console, but radeonfb caused so much trouble (crashes, frozen computer, garbage on the screet, etc.) that I didn't even get to test if it helped the issue. Also, I can't seem to get the interrupt back to 60Hz ―it's either 0 or 120 now― so that apparently was just another buggy case. |
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.