Summary: | Power management does not work on ATI RV530LE [Radeon X1600/X1650 PRO] => hot card | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Thierry Vignaud <thierry.vignaud> | ||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
Status: | RESOLVED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | 7.6 (2010.12) | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Thierry Vignaud
2011-08-16 18:35:18 UTC
Created attachment 50292 [details]
dmesg output
Created attachment 50293 [details]
copy of its vbios
Prior to r6xx, desktop asics rarely have low power modes. Is there a tool available to decode the vbios and check out? Was the proprietary driver having some kind of PM at that time? (In reply to comment #4) > Is there a tool available to decode the vbios and check out? You can use avivotool or AtomDis to look at the vbios tables. http://cgit.freedesktop.org/~airlied/radeontool/ http://cgit.freedesktop.org/~mhopf/AtomDis e.g., sudo avivotool romtables /path/to/vbios > Was the proprietary driver having some kind of PM at that time? Desktop cards generally only had 1 power state, or they only supported OverDrive (overclock) modes. e.g., from your vbios. Your card has the default mode, and an overclock mode. pp v 2 1 thermal controller: LM63 on 0x92 at 0x98 - int bitmap 0x02 2 power modes (lowest to highest) == power mode 0 == engine: 58800, memory: 69400 pcie lanes: 16 temp: 0 - 120 panel refresh: 60 voltage gpio id: 0x14 flags: VOLTAGE_DROP_SUPPORT VOLTAGE_DROP_ACTIVE_HIGH LOAD_BALANCE_EN DRIVER_DEFAULT_MODE == power mode 1 == engine: 0, memory: 0 pcie lanes: 16 temp: 0 - 0 panel refresh: 0 voltage gpio id: 0x14 flags: VOLTAGE_DROP_ACTIVE_HIGH LOAD_BALANCE_EN 3D_ACCELERATION_EN FS3D_OVERDRIVE_INFO |
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.