Page 3 of 12 FirstFirst 12345 ... LastLast
Results 21 to 30 of 113

Thread: X.Org ATI Driver Supports New Power Options

  1. #21
    Join Date
    Feb 2008
    Posts
    20

    Default

    @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 at 06:49 PM.

  2. #22
    Join Date
    Apr 2009
    Posts
    1

    Thumbs up DynamicPM option

    Quote 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

  3. #23
    Join Date
    Nov 2007
    Location
    Die trolls, die!
    Posts
    525

    Default

    This is awesome! Thanks!

  4. #24
    Join Date
    May 2008
    Posts
    598

    Default

    Quote 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?

  5. #25
    Join Date
    Nov 2007
    Posts
    1,024

    Default

    Quote Originally Posted by Louise View Post
    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?
    Alex works for AMD, so him having info means nothing about it being released publicly.

  6. #26
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,578

    Default

    Yeah, agd5f wrote the code.

    I believe all the information used was already available, except for changing the # of PCIE lanes on 6xx/7xx (the registers moved).

    This is the functionality we have been saying for months that someone could write
    Last edited by bridgman; 04-15-2009 at 08:34 PM.

  7. #27
    Join Date
    May 2008
    Posts
    598

    Default

    Quote Originally Posted by elanthis View Post
    Alex works for AMD, so him having info means nothing about it being released publicly.
    I see

    Otherwise I'd say that would justify an article and a few comments from the AMD folks

  8. #28
    Join Date
    May 2008
    Posts
    598

    Default

    Quote Originally Posted by bridgman View Post
    Yeah, agd5f wrote the code.

    I believe all the information used was already available, except for changing the # of PCIE lanes on 6xx/7xx (the registers moved).
    It's pretty cool that these things can be changed without crashing the GPU!

    How many pages would you say the final power management specs would be? 10 pages, 100 pages, 1000 pages ?

  9. #29
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,578

    Default

    Quote Originally Posted by Louise View Post
    It's pretty cool that these things can be changed without crashing the GPU
    This code only adjusts the engine clock so far, not the memory clock; changing engine speed is pretty safe because you can block acceleration while changing the clock. Changing the memory clock reliably is more difficult. You also need some pretty complex logic to make sure that the memory clock doesn't get too low for your display bandwidth and latency requirements, or you start to get artifacts on the screen very quickly.

    Remember that dynamic power management is governed by Schmidt's law -- "if you mess with something enough, it'll break".

    Note that this code probably needs to be moved into the drm if we want to have full activity-based power management. The X driver doesn't know about 3D driver activity, just 2D and video, but the drm knows about all the acceleration activity.

    Quote Originally Posted by Louise View Post
    How many pages would you say the final power management specs would be? 10 pages, 100 pages, 1000 pages ?
    We'll probably try to identify a subset of the information which gives the biggest power savings without being too painful to code for on all the different GPUs and systems. As with 6xx 3D, we will probably release a mix of documentation and code.

    Probably more than 10 pages but not a lot more, although if you count things like display bandwidth and latency calculations the numbers go up quickly.
    Last edited by bridgman; 04-15-2009 at 09:11 PM.

  10. #30
    Join Date
    Jun 2007
    Location
    .ro/.ca
    Posts
    232

    Default

    Doesn't seem to work (yet?) for my 4870x2. I get a blank screen/hard lock with ForceLowPowerMode, and the problem seems to be
    Code:
    [drm] wait idle failed status : 0xA0003028 0x00000002
    last message repeated 174 times
    but I can't be sure due to the hard lock (messages may not be sync'ed to disk).

    Can't reach buzilla either, so I can't report it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •