Announcement

Collapse
No announcement yet.

Trying Out AMDGPU Overdrive Radeon Overclocking On Linux 4.15

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

  • Trying Out AMDGPU Overdrive Radeon Overclocking On Linux 4.15

    Phoronix: Trying Out AMDGPU Overdrive Radeon Overclocking On Linux 4.15

    A premium patron recently requested some fresh tests on Polaris and Vega trying out the AMDGPU OverDrive overclocking functionality on the latest Linux kernel... Here are those tests with a Radeon RX 580 and RX Vega 64...

    http://www.phoronix.com/scan.php?pag...ive-Linux-4.15

  • #2
    ahh - cool - i might have to try with some negative numbers on my vega64 (that is unfortunately not behaving properly at full load anymore)

    Comment


    • #3
      Hey Michael, got anymore of those... premium patron's? :P

      Nice results!

      Also, for those not on 4.15 and want to overclock their AMD cards, I've been using OhGodATool and it works great.

      Code:
      sudo sh -c "echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level"
      sudo ohgodatool -i 0 --set-fanspeed 40 --mem-state 1 --mem-clock 2100 --core-state 5 --core-clock 1191
      sudo sh -c "echo 5 > /sys/class/drm/card0/device/pp_dpm_sclk"
      Note that the 5 on the last line is not the percentage overclock, but the core state. For example on my RX480:

      Code:
      $ sudo ohgodatool -i 0 --show-mem --show-core
      Memory state 0:
          VDDC: 800
          VDDCI: 850
          VDDC GFX offset: 0
          MVDD: 1000
          Memory clock: 300
      Memory state 1:
          VDDC: 65282
          VDDCI: 950
          VDDC GFX offset: 0
          MVDD: 1000
          Memory clock: 2100
      
      DPM state 0:
          VDDC: 800 (voltage table entry 0)
          VDDC offset: 0
          Core clock: 300
      DPM state 1:
          VDDC: 65282 (voltage table entry 1)
          VDDC offset: -26
          Core clock: 608
      DPM state 2:
          VDDC: 65283 (voltage table entry 2)
          VDDC offset: -26
          Core clock: 910
      DPM state 3:
          VDDC: 65284 (voltage table entry 3)
          VDDC offset: -26
          Core clock: 1077
      DPM state 4:
          VDDC: 65285 (voltage table entry 4)
          VDDC offset: -26
          Core clock: 1145
      DPM state 5:
          VDDC: 65286 (voltage table entry 5)
          VDDC offset: -26
          Core clock: 1191
      DPM state 6:
          VDDC: 65287 (voltage table entry 6)
          VDDC offset: -26
          Core clock: 1236
      DPM state 7:
          VDDC: 65288 (voltage table entry 7)
          VDDC offset: 0
          Core clock: 1303
      The defaults on this card are 1303/2000

      Comment


      • #4
        That last tool seam to be better. OC by pourcent is just a no-go for me. I do all my rx480 OC with srbpolaris, that way I can put 1.35v for the gpu core if i want.

        Comment


        • #5
          Thank you for those tests

          I actually have a RX470 from MSI and I've got almost 7% performance increase in Unigine Heaven, so that's why I thought it could be a good idea to show how reasonable is the state of art of AMD Overdrive on Linux.

          Let's hope for more improvements on the near future.

          Comment


          • #6
            Originally posted by boxie View Post
            ahh - cool - i might have to try with some negative numbers on my vega64 (that is unfortunately not behaving properly at full load anymore)
            Is it running cool enough? Might also be your PSU

            Comment


            • #7
              I wonder where those minimum framerates come from on. I'm thinking the CPU is where we're limited here.
              Last edited by microcode; 03-03-2018, 05:26 PM.

              Comment


              • #8
                Originally posted by schmidtbag View Post
                Is it running cool enough? Might also be your PSU
                Yep - been down that road - all the temps are within scope for it.

                I think it is a power handling issue on the vega. Too much power forces it into a protection mode. I had a 390X in the system without any issue to test that out and it worked fine (delivery nearly as much power as the vega with no issue).

                at some stage in the near future I need to put it into somebody elses machine to confirm this.

                Comment


                • #9
                  Originally posted by boxie View Post
                  ahh - cool - i might have to try with some negative numbers on my vega64 (that is unfortunately not behaving properly at full load anymore)
                  I vaguely remember negative numbers not working and actually pegging it at the max possible OC. Has this changed?

                  Comment


                  • #10
                    Originally posted by Niarbeht View Post

                    I vaguely remember negative numbers not working and actually pegging it at the max possible OC. Has this changed?
                    Right, just tried it on my RX570;
                    Code:
                    echo -10 > /sys/class/drm/card0/device/pp_mclk_od
                    And it bumped the mem clock from default 1750Mhz to 2100Mhz, resulting in white screen and Kernel hang by amdgpu driver code.

                    Comment

                    Working...
                    X