Announcement

Collapse
No announcement yet.

X.Org ATI Driver Supports New Power Options

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Louise
    replied
    Originally posted by agd5f View Post
    The DynamicPM option shouldn't affect performance. It only switches to a low power mode during idle (DPMS active). When you are using the system, it switches back to the default power mode.
    You know a lot about this topic. Was it you who implemented it?

    Does this mean that AMD have finished writing the power management specs and released them to some developers?

    Leave a comment:


  • bugmenot
    replied
    This is awesome! Thanks!

    Leave a comment:


  • Niagra
    replied
    DynamicPM option

    Originally posted by agd5f View Post
    The DynamicPM option shouldn't affect performance. It only switches to a low power mode during idle (DPMS active). When you are using the system, it switches back to the default power mode.
    At the moment, this doesn't work for me. With activated DynamicPM option, the card always uses the lowest possible mode. But perhaps this isn't the right place for bug reports and of course it's still development code.

    But nevertheless thank you for bringing power management to R700 based cards on linux! This saves nearly 17W for me in regular system operation, since the Radeon 4670 is only actually powersaving when those powerplay features are activated.

    Niagra

    Leave a comment:


  • signor_rossi
    replied
    @Vighy
    There is a typo in the bugzilla link posted...

    @elsie
    I use it on a laptop, but mine hasn't a GPU fan.
    glxgears (not a benchmark TM) gives me around 1400 fps on my X600 with ForceLowPowerMode true. The GPU stays fine cool... )

    Direct Rendering and the xv overlay seem all to work.
    KDE doesn't start up properly because plasma crashes, I haven't figured out yet why Xfce hangs...
    EDIT: A clean config (I moved the .kde4 folder makes KDE start up fine...
    Last edited by signor_rossi; 04-15-2009, 05:49 PM.

    Leave a comment:


  • highlandsun
    replied
    Originally posted by agd5f View Post
    DynamicPM option switches to a lower power state when your PC is idle (DPMS has turned off the screen). It switches back to the default state when there is activity. The ForceLowPowerMode option forces the chip to always be in a low power state.
    But something that wasn't clear to me until I read the code: DynamicPM's low power state is lower than ForceLowPowerMode's low power state. For maximum savings, you should enable both options.

    I haven't noticed any lower temperatures on my HPdv5z with HD3450 yet. Will see if it makes any difference in battery life...

    Leave a comment:


  • agd5f
    replied
    Originally posted by dungeon View Post
    I'm a bit confused with these options, is "DynamicClocks" option is now just renamed to "ClockGating"? When only "DynamicPM" or with "ClockGating" also, gpu clock is always stay to 60 MHz (default is 238.5 MHz on my rV280), this downclock seems to not affect performance in 2D/video, but Mesa usage is affected - there are lines all over of
    any GL games, so is this normal behavior with "DynamicPM" "on"?
    DynamicClocks options was renamed to ClockGating and the code was cleaned up and unified. DynamicPM option switches to a lower power state when your PC is idle (DPMS has turned off the screen). It switches back to the default state when there is activity. The ForceLowPowerMode option forces the chip to always be in a low power state.

    Leave a comment:


  • elsie
    replied
    few questions....

    Has anyone tried these power options on a laptop?
    Does ForceLowPowerMode keep the fan quiet?
    What kind of performance do you get with ForceLowPowerMode? (glxgears fps anyone?)


    I'm still using an old fglrx driver primarily for the powerplay feature, low power mode (135/135) is permanently set. This keeps the fan almost silent.
    Using fglrx low power mode I get about 1000fps with my x1600 mobility.

    Leave a comment:


  • dungeon
    replied
    I'm a bit confused with these options, is "DynamicClocks" option is now just renamed to "ClockGating"? When only "DynamicPM" or with "ClockGating" also, gpu clock is always stay to 60 MHz (default is 238.5 MHz on my rV280), this downclock seems to not affect performance in 2D/video, but Mesa usage is affected - there are lines all over of
    any GL games, so is this normal behavior with "DynamicPM" "on"?

    P.S. Oh i see two another commits after, maybe i will wait a little and try again later.
    Last edited by dungeon; 04-15-2009, 05:11 PM.

    Leave a comment:


  • Vighy
    replied
    mhh I cannot reach the bugzilla now, it seems to me it's down (may temporary) but I notice a little corruption at the bottom-right of the pointer. In particular when it's animated.
    I've enabled DynamicPM (but it's not active since i'm using the PC ) and ClockGating.

    I'm gonna try more options and combinations and then report back.

    Leave a comment:


  • diverse_izzue
    replied
    Originally posted by agd5f View Post
    https://bugs.freedektop.org

    Each block on the chip (displays, 2D, 3D, overlay, etc.) can be clocked separately. If a particular block is not in use, the GPU can dynamically stop/start the clock to that block, saving power. Enabling ClockGating should save some power, however, the some bioses enabled this by default during boot up, so you may or may not see much savings from this option, depending on your system.
    Reported: #21208

    Thanks for the explanation.

    Leave a comment:

Working...
X