Announcement

Collapse
No announcement yet.

New tool for undervolt/overclock AMD K8L and K10 processors

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

  • #61
    Originally posted by blackshard View Post
    Hi kfgz, actually I had the chance to test a Phenom II 1055T and I had no problems with neither Windows or Linux.
    It just popped in my mind that there is a known problem with temperature reporting when a k10 processor get some cores/cache unlocked. Is yours unlocked?
    No, but I'll check some options in BIOS and let you know.

    Comment


    • #62
      You were right. I had ACC tured on. When I switch ACC off, tpc shows correct temperature.

      Comment


      • #63
        Originally posted by gtrawoger View Post
        @blackshard:

        Can you PM me your address? Package is ready!
        Hi blackshard,

        I need your address for the final shipping cost. If it's under $20 (which I think it will be), it'll be on me.

        Comment


        • #64
          I have a problem with the program. I do all the instructions of the manual, and compile the program.
          But when I execute de program, this is what I see in the terminal:

          djnardo@djnardo-HTPC:~/Turionpower/bin$ sudo ./compile_i386.sh
          sudo: ./compile_i386.sh: command not found
          djnardo@djnardo-HTPC:~/Turionpower/bin$ cd ../src
          djnardo@djnardo-HTPC:~/Turionpower/src$ sudo ./compile_i386.sh
          Griffin.cpp: In member function ‘virtual void Griffin:erfMonitorCPUUsage()’:
          Griffin.cpp:1151: warning: spurious trailing ‘%’ in format
          K10Processor.cpp: In member function ‘virtual void K10Processor:erfMonitorCPUUsage()’:
          K10Processor.cpp:1369: warning: spurious trailing ‘%’ in format
          djnardo@djnardo-HTPC:~/Turionpower/src$ cd ../bin
          djnardo@djnardo-HTPC:~/Turionpower/bin$ sudo modprobe cpuid
          djnardo@djnardo-HTPC:~/Turionpower/bin$ sudo modprobe msr
          djnardo@djnardo-HTPC:~/Turionpower/bin$ modprobe cpuid
          djnardo@djnardo-HTPC:~/Turionpower/bin$ find /dev/cpu
          /dev/cpu
          /dev/cpu/1
          /dev/cpu/1/msr
          /dev/cpu/1/cpuid
          /dev/cpu/0
          /dev/cpu/0/msr
          /dev/cpu/0/cpuid
          /dev/cpu/microcode
          djnardo@djnardo-HTPC:~/Turionpower/bin$ sudo TurionPowerControl
          sudo: TurionPowerControl: command not found
          djnardo@djnardo-HTPC:~/Turionpower/bin$ TurionPowerControl
          TurionPowerControl: orden no encontrada
          Sorry for my english, and thanks

          Comment


          • #65
            use ./ in front. "." is not in the path.

            Comment


            • #66
              Originally posted by gtrawoger View Post
              Hi blackshard,

              I need your address for the final shipping cost. If it's under $20 (which I think it will be), it'll be on me.
              I sent you a PM with the final address.
              If you wish I may pay one half of the shipping cost. I don't want to let you charge of the whole cost.

              Comment


              • #67
                Originally posted by Kano View Post
                use ./ in front. "." is not in the path.
                Thank you very much. I'm very novice, and I need to start the program on startup, but I don't understand the manual.
                I have to do a script that launchs the program, but before I need to execute modprobe, and I don't think how to do this.

                Sorry for the inconvenience.

                Comment


                • #68
                  Originally posted by djnardo View Post
                  Thank you very much. I'm very novice, and I need to start the program on startup, but I don't understand the manual.
                  I have to do a script that launchs the program, but before I need to execute modprobe, and I don't think how to do this.

                  Sorry for the inconvenience.
                  In the manual I suggest to use the rc.local file located in /etc directory.

                  It is a script automatically executed at the very end of the linux boot process.

                  Just put three lines inside the rc.local script:

                  modprobe cpuid
                  modprobe msr
                  /yourTPCFolder/bin/TurionPowerControl -blablabla

                  and then you're done. At next reboot those three lines will be executed automatically.
                  Obviously change "yourTPCFolder" with the correct path where you compiled the program.
                  To know the path where the program lies, put yourself in the bin directory of the program, write pwd and press enter.

                  Comment


                  • #69
                    Usually you write modules to be loaded on start into /etc/modules.

                    Comment


                    • #70
                      Originally posted by Kano View Post
                      Usually you write modules to be loaded on start into /etc/modules.
                      Good to know

                      Comment


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

                                Working...
                                X