Announcement

Collapse
No announcement yet.

More Radeon Power Management Improvements

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

  • #61
    I am pretty sure Linux 2.6.35rc4 has the latest PM functions integrated.

    Comment


    • #62
      The code is already included in 2.6.35. See this post for more information on using it:
      http://lists.freedesktop.org/archive...ay/000492.html
      Note that there is also now a "mid" profile.

      Comment


      • #63
        If I wanted low profile to be used by default on boot, what would be the preferred location to set it?

        Comment


        • #64
          Beyond the flicker, is there any downside to frequent reclocking? Shortened hw life?

          Comment


          • #65
            Originally posted by agd5f View Post
            The code is already included in 2.6.35. See this post for more information on using it:
            http://lists.freedesktop.org/archive...ay/000492.html
            Note that there is also now a "mid" profile.
            Oh, thank you. This key information hasn't spread far enough, AFAICS.

            FYI, some power consumptions tests (KMS, Xorg with radeon driver from yesterdays git snapshot, one head enabled, no relevant CPU load):

            default: ~144W
            auto: 127..132W
            high: 137..141W
            mid: 128..131W
            low: 100..103W (pretty close to normal idle state with fglrx)
            low (with both heads enabled): 118..121W (also close to fglrx w/ multihead)

            My naive conclusion is that "auto" mode is not aggressive enough or doesn't get enough information to control efficiently. But I am sure you know better.

            Comment


            • #66
              Originally posted by curaga View Post
              Beyond the flicker, is there any downside to frequent reclocking? Shortened hw life?
              You should hope not, your CPU is doing it constantly too. As are most of your mobile electronics and such.

              If you're thinking of the HDD lifetime issues with the power management in some Linux configurations that come up a few years back, remember that those things have complex moving parts, and it was the strain on those which led to their decreased lifetime, not the electronics.

              Comment


              • #67
                Power management makes the hardware live longer, not shorter. HW life is shortened when you don't use PM.

                Comment


                • #68
                  Yep. The power management code only programs non-permanent registers - there's no writing to non-volatile memory or anything that would detract from lifetime. The proprietary drivers also dynamically reclock the chips.

                  Comment


                  • #69
                    You should hope not, your CPU is doing it constantly too.
                    No it doesn't, my desktop board BIOS doesn't support that
                    No speedstep or C states beyond C1.

                    Comment


                    • #70
                      Does 2.6.35-rc4 support undervolting? Can it show gpu temperature?
                      ## VGA ##
                      AMD: X1950XTX, HD3870, HD5870
                      Intel: GMA45, HD3000 (Core i5 2500K)

                      Comment


                      • #71
                        Originally posted by nanonyme View Post
                        If I wanted low profile to be used by default on boot, what would be the preferred location to set it?
                        In Arch Linux I did the following:

                        http://wiki.archlinux.org/index.php/Ati#Early_KMS_start

                        and added line

                        Code:
                        echo low > /sys/class/drm/card0/device/power_profile
                        in file
                        Code:
                        /etc/rc.local
                        I don't know if the first step has any effect other than getting the right resolution earlier, but it's still nicer that way. And I use the kernel from

                        http://gtklocker.tiven.org/radeon-repo/x86_64/

                        Comment


                        • #72
                          Originally posted by Ivaldi View Post
                          Oh, thank you. This key information hasn't spread far enough, AFAICS.

                          FYI, some power consumptions tests (KMS, Xorg with radeon driver from yesterdays git snapshot, one head enabled, no relevant CPU load):

                          default: ~144W
                          auto: 127..132W
                          high: 137..141W
                          mid: 128..131W
                          low: 100..103W (pretty close to normal idle state with fglrx)
                          low (with both heads enabled): 118..121W (also close to fglrx w/ multihead)

                          My naive conclusion is that "auto" mode is not aggressive enough or doesn't get enough information to control efficiently. But I am sure you know better.
                          As noted in the page I linked, "auto" only lowers the clock when on battery and when the screen is blanked. To dynamically raise and lower the clocks, you can enable the dynpm method, but you will likely experience problems until that is sorted out better.

                          Comment


                          • #73
                            Originally posted by Ivaldi View Post
                            default: ~144W
                            auto: 127..132W
                            high: 137..141W
                            mid: 128..131W
                            low: 100..103W (pretty close to normal idle state with fglrx)
                            low (with both heads enabled): 118..121W (also close to fglrx w/ multihead)

                            My naive conclusion is that "auto" mode is not aggressive enough or doesn't get enough information to control efficiently. But I am sure you know better.
                            My understanding is that auto switches only between high and mid (as long as the screen is on at least) so when in your case the auto rate is the same as the mid rate that sounds like as good as it gets. It will not switch to low because low is not working so well for everybody ATM.

                            Comment


                            • #74
                              Originally posted by tormod View Post
                              My understanding is that auto switches only between high and mid (as long as the screen is on at least) so when in your case the auto rate is the same as the mid rate that sounds like as good as it gets. It will not switch to low because low is not working so well for everybody ATM.
                              Not sure auto even switches anything when AC is on.
                              Here with 2.6.35rc4 + drm-radeon-testing, GPU is running at full blast as long as power is plugged.

                              On the other hand, "dynpm" was working really great with 2.6.34 mainline and was very efficient but now there's noticeable flickering / micro-freezes on every state change, maybe due to additional memory reclock and/or voltage tweaking...

                              Comment


                              • #75
                                "auto" only changes the clocks when switching from battery to ac and vice versa (mid <-> high) and when the monitors blank (low).

                                Comment

                                Working...
                                X