Announcement

Collapse
No announcement yet.

New tool for undervolt/overclock AMD K8L and K10 processors

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

  • #71
    I have Phenom X4 945 on AM2-motherboard and get the following readings.

    Code:
    Power States table:
    -- Core 0
    core 0 pstate 0 - En:1 VID:22 FID:14 DID:0 Freq:3000 VCore: 1.0000
    core 0 pstate 1 - En:1 VID:30 FID:7 DID:0 Freq:2300 VCore: 0.8000
    core 0 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 0.7625
    core 0 pstate 3 - En:1 VID:32 FID:0 DID:1 Freq:800 VCore: 0.7625
    core 0 pstate 4 - En:0 VID:32 FID:0 DID:1 Freq:800 VCore: 0.7625
    I assume that the VCore readings should be actual values which I get for example using K10stat. Is this an error of tpc or am I missing something obvious?

    Comment


    • #72
      Originally posted by zz13 View Post
      I have Phenom X4 945 on AM2-motherboard and get the following readings.

      Code:
      Power States table:
      -- Core 0
      core 0 pstate 0 - En:1 VID:22 FID:14 DID:0 Freq:3000 VCore: 1.0000
      core 0 pstate 1 - En:1 VID:30 FID:7 DID:0 Freq:2300 VCore: 0.8000
      core 0 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 0.7625
      core 0 pstate 3 - En:1 VID:32 FID:0 DID:1 Freq:800 VCore: 0.7625
      core 0 pstate 4 - En:0 VID:32 FID:0 DID:1 Freq:800 VCore: 0.7625
      I assume that the VCore readings should be actual values which I get for example using K10stat. Is this an error of tpc or am I missing something obvious?
      Yup, actually there's no error.
      Since you got an AM2 motherboard, core voltage is controlled by northbridge voltage. I hope you have version 0.30 of the program, because it is able to control northbridge voltage. Check the documentation too, it is described there also.

      Comment


      • #73
        I understand that the nbv = vcore in my case. But the readings are different and incorrect compared to the K10stat. For example the listing of the previous message is received the actual vcore voltage is 1.30v.

        Should this app work on the fly when running Linux (no need to specify values at boot time)? I have tried to undervolt but it has no effect when using tpc 0.30 under Linux.

        Comment


        • #74
          Originally posted by zz13 View Post
          I understand that the nbv = vcore in my case. But the readings are different and incorrect compared to the K10stat. For example the listing of the previous message is received the actual vcore voltage is 1.30v.
          I don't know how k10stat works, but actually it may detect your configuration and show you the northbridge voltage inside the core voltage field. Instead tpc shows exactly what is contained in the MSR registers of the processor about core voltage. You may change them, but they will have no effect at all because all is dominated by northbridge voltage.
          AFAIK such configurations like yours always show inconsistent values inside core voltage fields. Can you put the complete output of tpc -l switch?

          Originally posted by zz13 View Post
          Should this app work on the fly when running Linux (no need to specify values at boot time)? I have tried to undervolt but it has no effect when using tpc 0.30 under Linux.
          Of course it works on the fly. How did you try to undervolt and how did you check if it was working or it wasn't?

          Comment


          • #75
            Code:
            Turion Power States Optimization and Control - by blackshard - v0.30
            Detected CPU:
            Family: 0xf		Model: 0x4		Stepping: 0x3
            Extended Family: 0x10	Extended Model: 0x4
            Package Type: 0x1	BrandId: 0x1ad6	
            Detected Physical Cores: 4
            Detected processor: AMD Family 10h Processor
            Processor has 4 cores
            Processor has 5 p-states
            
            Power States table:
            -- Core 0
            core 0 pstate 0 - En:1 VID:22 FID:14 DID:0 Freq:3000 VCore: 1.0000
            core 0 pstate 1 - En:1 VID:30 FID:7 DID:0 Freq:2300 VCore: 0.8000
            core 0 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 0.7625
            core 0 pstate 3 - En:1 VID:52 FID:0 DID:1 Freq:800 VCore: 0.5125
            core 0 pstate 4 - En:0 VID:52 FID:0 DID:1 Freq:800 VCore: 0.5125
            
            >>>other cores have identical info, clipped
             
            Processor Maximum PState: 3
            Processor Startup PState: 3
            Processor Maximum Operating Frequency: 3000 MHz
            
            Minimum allowed VID: 63 (0.375v) - Maximum allowed VID 22 (1.000v)
            Processor AltVID: 34 (0.738v)
            Northbridge Power States table:
            PState 0 - NbVid 22 (1.0000) NbDid 0 NbFid 4
            PState 1 - NbVid 30 (0.8000) NbDid 0 NbFid 4
            PState 2 - NbVid 32 (0.7625) NbDid 0 NbFid 4
            PState 3 - NbVid 52 (0.5125) NbDid 0 NbFid 4
            PState 4 - NbVid 52 (0.5125) NbDid 0 NbFid 4
            Northbridge Maximum frequency: 2000
            * Warning: PVI mode is set. Northbridge voltage is used for processor voltage at given pstates!
            * Changing Northbridge voltage changes core voltage too.
            
            Core 0 C1E CMP halt bit is disabled
            Core 1 C1E CMP halt bit is disabled
            Core 2 C1E CMP halt bit is disabled
            Core 3 C1E CMP halt bit is disabled
            
            Voltage Regulator Slamming time register: 4
            Voltage Regulator Step Up Ramp Time: 8
            Voltage Regulator Step Down Ramp Time: 8
            Processor is using Parallel VID Interface (probably Single Plane mode)
            Processor PState Identifier: 0x3
            PSI_L bit not enabled
            Value 0.5125 on pstate 3 under Windows 85W (voltage dropped) and Linux (no effect) 105W measured with power consumption meter.

            Comment


            • #76
              Originally posted by zz13 View Post
              Code:
              Turion Power States Optimization and Control - by blackshard - v0.30
              Detected CPU:
              Family: 0xf		Model: 0x4		Stepping: 0x3
              Extended Family: 0x10	Extended Model: 0x4
              Package Type: 0x1	BrandId: 0x1ad6	
              Detected Physical Cores: 4
              Detected processor: AMD Family 10h Processor
              Processor has 4 cores
              Processor has 5 p-states
              
              Power States table:
              -- Core 0
              core 0 pstate 0 - En:1 VID:22 FID:14 DID:0 Freq:3000 VCore: 1.0000
              core 0 pstate 1 - En:1 VID:30 FID:7 DID:0 Freq:2300 VCore: 0.8000
              core 0 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 0.7625
              core 0 pstate 3 - En:1 VID:52 FID:0 DID:1 Freq:800 VCore: 0.5125
              core 0 pstate 4 - En:0 VID:52 FID:0 DID:1 Freq:800 VCore: 0.5125
              
              >>>other cores have identical info, clipped
               
              Processor Maximum PState: 3
              Processor Startup PState: 3
              Processor Maximum Operating Frequency: 3000 MHz
              
              Minimum allowed VID: 63 (0.375v) - Maximum allowed VID 22 (1.000v)
              Processor AltVID: 34 (0.738v)
              Northbridge Power States table:
              PState 0 - NbVid 22 (1.0000) NbDid 0 NbFid 4
              PState 1 - NbVid 30 (0.8000) NbDid 0 NbFid 4
              PState 2 - NbVid 32 (0.7625) NbDid 0 NbFid 4
              PState 3 - NbVid 52 (0.5125) NbDid 0 NbFid 4
              PState 4 - NbVid 52 (0.5125) NbDid 0 NbFid 4
              Northbridge Maximum frequency: 2000
              * Warning: PVI mode is set. Northbridge voltage is used for processor voltage at given pstates!
              * Changing Northbridge voltage changes core voltage too.
              
              Core 0 C1E CMP halt bit is disabled
              Core 1 C1E CMP halt bit is disabled
              Core 2 C1E CMP halt bit is disabled
              Core 3 C1E CMP halt bit is disabled
              
              Voltage Regulator Slamming time register: 4
              Voltage Regulator Step Up Ramp Time: 8
              Voltage Regulator Step Down Ramp Time: 8
              Processor is using Parallel VID Interface (probably Single Plane mode)
              Processor PState Identifier: 0x3
              PSI_L bit not enabled
              Value 0.5125 on pstate 3 under Windows 85W (voltage dropped) and Linux (no effect) 105W measured with power consumption meter.
              Mmmh...
              First of all it looks really strange to me that your processor is running at 3.0 Ghz with 1.000 voltage. Does k10stat tell the same power state table as tpc does? I'm worried about some voltage conversion errors (even if I double checked them).

              BTW, you should let the processor do a pstate transition to really apply new settings. I explain: when you use tpc and change the core voltage, the processor has to reenter in that pstate to apply new settings. When the pstate changed is the slowest pstate (the pstate used when the processor goes idling) you need to put a load to let the processor go out of the pstate and then reenter.

              Unfortunately I had no chance to test the behaviour on a AM2 motherboard with a AM2+ processor, so I can't be more detailed on this.

              Comment


              • #77
                Originally posted by blackshard View Post
                Mmmh...
                First of all it looks really strange to me that your processor is running at 3.0 Ghz with 1.000 voltage. Does k10stat tell the same power state table as tpc does? I'm worried about some voltage conversion errors (even if I double checked them).
                Well, this is the thing I have tried to tell. Tpc reports unlogical values. K10stat reports logical and probably correct values. By the way, also other Linux tool k10ctl have this wrong value problem.

                Originally posted by blackshard View Post
                BTW, you should let the processor do a pstate transition to really apply new settings.
                There has been transitions but still no effect.

                Comment


                • #78
                  Mmmh... what kind of motherboard do you have?

                  Anyway, I'm not really sure if the problem is related to Serial VID and Parallel VID settings.

                  Maybe you can try to force Serial VID and see if voltages became coherent with k10stat.

                  If you want to try, open K10Processor.cpp file and change line 473 from:

                  Code:
                  if (miscReg==0) return false; else return true;
                  to

                  Code:
                  return false;
                  According to the SVI VID table, VID 22 (your maximum voltage accepted) is equal to 1.2750v, and I think it is the correct value there. Can you confirm?

                  Comment


                  • #79
                    Originally posted by blackshard View Post
                    Mmmh... what kind of motherboard do you have?
                    Asus M2NPV-MX

                    Originally posted by blackshard View Post
                    Anyway, I'm not really sure if the problem is related to Serial VID and Parallel VID settings.

                    Maybe you can try to force Serial VID and see if voltages became coherent with k10stat.

                    If you want to try, open K10Processor.cpp file and change line 473 ...
                    With the code change the values are identical to K10stat.

                    Originally posted by blackshard View Post
                    According to the SVI VID table, VID 22 (your maximum voltage accepted) is equal to 1.2750v, and I think it is the correct value there. Can you confirm?
                    This is true.

                    I tested non-modifed tpc in OpenSuSE and it worked. There is something in my Gentoo kernel with rejects undervolting.

                    Thank you for your help and the nice app.

                    Comment


                    • #80
                      Originally posted by blackshard View Post
                      Mmmh... what kind of motherboard do you have?

                      Anyway, I'm not really sure if the problem is related to Serial VID and Parallel VID settings.

                      Maybe you can try to force Serial VID and see if voltages became coherent with k10stat.

                      If you want to try, open K10Processor.cpp file and change line 473 from:

                      Code:
                      if (miscReg==0) return false; else return true;
                      to

                      Code:
                      return false;
                      According to the SVI VID table, VID 22 (your maximum voltage accepted) is equal to 1.2750v, and I think it is the correct value there. Can you confirm?
                      Hi blackshard, thanks a lot for the update. I had exactly the same problem (extremely low voltage reported on my AM2 motherboard), and this fixed it. ./TurionPowerControl -l now says
                      Code:
                      Turion Power States Optimization and Control - by blackshard - v0.30
                      Detected CPU:
                      Family: 0xf             Model: 0x4              Stepping: 0x2
                      Extended Family: 0x10   Extended Model: 0x4
                      Package Type: 0x1       BrandId: 0x1a86
                      Detected Physical Cores: 4
                      Detected processor: AMD Family 10h Processor
                      Processor has 4 cores
                      Processor has 5 p-states
                      
                      Power States table:
                      -- Core 0
                      core 0 pstate 0 - En:1 VID:11 FID:19 DID:0 Freq:3500 VCore: 1.4125
                      core 0 pstate 1 - En:1 VID:24 FID:7 DID:0 Freq:2300 VCore: 1.2500
                      core 0 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 1.1500
                      core 0 pstate 3 - En:1 VID:32 FID:0 DID:1 Freq:800 VCore: 1.1500
                      core 0 pstate 4 - En:0 VID:0 FID:0 DID:0 Freq:1600 VCore: 1.5500
                      -- Core 1
                      core 1 pstate 0 - En:1 VID:11 FID:19 DID:0 Freq:3500 VCore: 1.4125
                      core 1 pstate 1 - En:1 VID:24 FID:7 DID:0 Freq:2300 VCore: 1.2500
                      core 1 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 1.1500
                      core 1 pstate 3 - En:1 VID:32 FID:0 DID:1 Freq:800 VCore: 1.1500
                      core 1 pstate 4 - En:0 VID:0 FID:0 DID:0 Freq:1600 VCore: 1.5500
                      -- Core 2
                      core 2 pstate 0 - En:1 VID:11 FID:19 DID:0 Freq:3500 VCore: 1.4125
                      core 2 pstate 1 - En:1 VID:24 FID:7 DID:0 Freq:2300 VCore: 1.2500
                      core 2 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 1.1500
                      core 2 pstate 3 - En:1 VID:32 FID:0 DID:1 Freq:800 VCore: 1.1500
                      core 2 pstate 4 - En:0 VID:0 FID:0 DID:0 Freq:1600 VCore: 1.5500
                      -- Core 3
                      core 3 pstate 0 - En:1 VID:11 FID:19 DID:0 Freq:3500 VCore: 1.4125
                      core 3 pstate 1 - En:1 VID:24 FID:7 DID:0 Freq:2300 VCore: 1.2500
                      core 3 pstate 2 - En:1 VID:32 FID:2 DID:0 Freq:1800 VCore: 1.1500
                      core 3 pstate 3 - En:1 VID:32 FID:0 DID:1 Freq:800 VCore: 1.1500
                      core 3 pstate 4 - En:0 VID:0 FID:0 DID:0 Freq:1600 VCore: 1.5500
                      Processor Maximum PState: 3
                      Processor Startup PState: 3
                      Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.
                      
                      Minimum allowed VID: 123 (0.013v) - Maximum allowed VID 0 (1.550v)
                      Processor AltVID: 34 (1.125v)
                      Northbridge Power States table:
                      PState 0 - NbVid 11 (1.4125) NbDid 0 NbFid 4
                      PState 1 - NbVid 24 (1.2500) NbDid 0 NbFid 4
                      PState 2 - NbVid 32 (1.1500) NbDid 0 NbFid 4
                      PState 3 - NbVid 32 (1.1500) NbDid 0 NbFid 4
                      PState 4 - NbVid 0 (1.5500) NbDid 0 NbFid 4
                      Northbridge Maximum frequency: 800
                      
                      Core 0 C1E CMP halt bit is disabled
                      Core 1 C1E CMP halt bit is disabled
                      Core 2 C1E CMP halt bit is disabled
                      Core 3 C1E CMP halt bit is disabled
                      
                      Voltage Regulator Slamming time register: 4
                      Voltage Regulator Step Up Ramp Time: 8
                      Voltage Regulator Step Down Ramp Time: 8
                      Processor is using Serial VID Interface (probably Dual Plane mode)
                      Processor PState Identifier: 0x2
                      PSI_L bit not enabled
                      There is only one thing which is not correctly reported - the frequency. I'm overclocking the processor in the BIOS from 15 x 200 = 3000 to 17.5 x 212 = 3710 Mhz. Memtest86+, dmesg, x86info correctly show "3710 mhz processor", but as you can see Tpc (as well as k10ctl) shows 3500 mhz (that is, 17.5 x 200, as if I hadn't touched the FSB). Simple benchmarks show that the CPU is actually running at 3710 Mhz. Maybe the BIOS is not updating the P-States information correctly? Thanks

                      Comment

                      Working...
                      X