Announcement

Collapse
No announcement yet.

More Radeon Power Management Improvements

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

  • #41
    You can manually select a power state and clock mode:
    echo 3.0 > /sys/class/drm/card0/device/power_state
    will select power state 3, clock mode 0.

    Comment


    • #42
      yeah, thats what I did, I was asking, is it possible to make dynpm to use state 3, not state 1

      Comment


      • #43
        You'd need to adjust the power state selection algo in r600_get_power_state() in r600.c

        Comment


        • #44
          hm, i guess this should be enough then

          if (rdev->pm.num_power_states > 2)
          - min_power_state_index = 1;
          + min_power_state_index = 3;

          Comment


          • #45
            Originally posted by agd5f View Post
            You can manually select a power state and clock mode:
            echo 3.0 > /sys/class/drm/card0/device/power_state
            will select power state 3, clock mode 0.
            Uhm, somehow this does not exist here:

            Code:
            2.6.34-0.38.rc5.git0.fc14.i686 #1 SMP
            Which is the latest Kernel from Fedora and should hold all the pm-stuff in it. Latest drm, mesa and ddx and I booted with dynpm=1 and

            Code:
            [drm] radeon: power management initialized
            indicates that power management is working. However, I saw no improvement on lowered GPU temperatures whatsoever.

            What did I miss?

            Comment


            • #46
              You need the drm-radeon-testing branch of the drm:

              Comment


              • #47
                Originally posted by agd5f View Post
                You need the drm-radeon-testing branch of the drm:
                http://git.kernel.org/?p=linux/kerne...radeon-testing
                It is not enough to use drm-radeon-testing kernel. Some X parts must be rebuilt as well: http://www.phoronix.com/forums/showthread.php?t=20484

                Anyway I am using drm-radeon-testing. Everything seems to be working. I can change profiles in sysfs but my GPU is still getting hot (Currently 89 degrees). I was trying to change profiles but nothing has helped. As well I see following messages in log:

                [ 1223.517620] radeon 0000:01:05.0: efd38000 reserve failed for wait
                [ 1325.118109] radeon 0000:01:05.0: efd38000 reserve failed for wait
                [ 1328.719790] radeon 0000:01:05.0: efd38000 reserve failed for wait
                [ 1433.991376] radeon 0000:01:05.0: efd38000 reserve failed for wait
                [ 1489.719272] radeon 0000:01:05.0: efd38000 reserve failed for wait
                [ 1576.114701] radeon 0000:01:05.0: efd38000 reserve failed for wait
                [ 1975.846892] radeon 0000:01:05.0: efd38000 reserve failed for wait
                [ 2022.020323] radeon 0000:01:05.0: efd38000 reserve failed for wait

                Comment


                • #48
                  Originally posted by daliusd View Post
                  It is not enough to use drm-radeon-testing kernel. Some X parts must be rebuilt as well: http://www.phoronix.com/forums/showthread.php?t=20484
                  Huh, what makes you think so?

                  Neither the DDX nor mesa do interface with the pm AFAIK, so why would it be necessary to rebuild X components?

                  Comment


                  • #49
                    since alex's last commit ( http://git.kernel.org/?p=linux/kerne...86c041340079db )

                    messages about changing clocks arent displaying in dmesg now, is there any way to check if reclocking actualy works and not failing due to - gui not idle ?

                    Comment


                    • #50
                      I run glxgears then change profile from high to low, and doesnt see any noticable fps change

                      Comment

                      Working...
                      X