Announcement

Collapse
No announcement yet.

X.Org ATI Driver Supports New Power Options

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

  • #16
    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.

    Comment


    • #17
      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.

      Comment


      • #18
        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.

        Comment


        • #19
          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.

          Comment


          • #20
            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...

            Comment


            • #21
              @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.

              Comment


              • #22
                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

                Comment


                • #23
                  This is awesome! Thanks!

                  Comment


                  • #24
                    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?

                    Comment


                    • #25
                      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.

                      Comment


                      • #26
                        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, 07:34 PM.

                        Comment


                        • #27
                          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

                          Comment


                          • #28
                            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 ?

                            Comment


                            • #29
                              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.

                              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, 08:11 PM.

                              Comment


                              • #30
                                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.

                                Comment

                                Working...
                                X