Trying to tune 16 core 62xx ES

tear said:
Still seems a bit hot to me -- my ILs in a different board: http://hardforum.com/showpost.php?p=1039246693&postcount=17 (folding an 8102) with noctuas though so not exactly apples-to-apples... but still, overall power draw of the IL system is lower (800W) than the MC system (900W), both at 3.0.

Ambient is about 70F.

Are you still running stock or OC? Can you post output of: sudo TurionPowerControl -l | grep 0.pstate.[0-2]
Click to expand...

I'm running overclocked at 3.0 GHz.
As requested:
Code: 
fredrik@fredrik-H8QGL:~$ sudo tpc -l | grep 0.pstate.2
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
core 0 pstate 2 (p0) - En:1 VID:30 FID:14 DID:0.00 Freq:3000 VCore:1.1750
fredrik@fredrik-H8QGL:~$ sudo tpc -temp
Turion Power States Optimization and Control - by blackshard - v0.43

Detected processor: Family 15h (Bulldozer/Interlagos/Valencia) Processor
Machine has 8 nodes
Processor has 8 cores
Processor has 7 p-states
Processor has 2 boost states
Processor temperature slew rate:9.0°C

Temperature table:
Node 0	C0:55	C1:55	C2:55	C3:55	C4:55	C5:55	C6:55	C7:55	
Node 1	C0:55	C1:55	C2:55	C3:55	C4:55	C5:55	C6:55	C7:55	
Node 2	C0:40	C1:40	C2:40	C3:40	C4:40	C5:40	C6:40	C7:40	
Node 3	C0:39	C1:39	C2:39	C3:39	C4:39	C5:39	C6:39	C7:39	
Node 4	C0:53	C1:53	C2:53	C3:53	C4:53	C5:53	C6:53	C7:53	
Node 5	C0:53	C1:53	C2:53	C3:53	C4:53	C5:53	C6:53	C7:53	
Node 6	C0:46	C1:46	C2:46	C3:46	C4:46	C5:46	C6:46	C7:46	
Node 7	C0:46	C1:46	C2:46	C3:46	C4:46	C5:46	C6:46	C7:46	

Done.
 
DrFredrik said:
I have not been able to get my 1.6 GHz MC ES chips to work for folding. Problems with HT-retries and NB Watch Dog Error made me finally give up. I believe others have had similar problems too. If you manage to solve the problem, please let us know!

see this post for example: http://hardforum.com/showthread.php?t=1713779
Click to expand...

Well that will suck because I bought them from a member here on the forum who knew I was going to be folding for the [H]
 
402's problem that Fredrik quoted turned out to be caused by the PSU, _not_ the chips
(spontaneous reboot issue continued to manifest even w/retail chips and with a different
board, too).

In general, you should be fine with rev. D1 chips (part number ending with E25). Just pay
attention to die temperatures (TurionPowerControl -temp) and other weird phenomena
(coils squealing) as these could contribute to motherboard's demise.

Rev. D0 chips (part number ending with E21) are generally a miss though (from data
we've gathered)...

Feel free to start a thread whenever you decide to get them going -- we'll do our best
to assist :)
 
The "wind tunnel" was first researched/implemented by firedfly, IIRC.

He's the one! I only spread the word ;-)
 
Managed to get the temperatures down another 5 degrees by opening the side panel of the HAF 932 and laying it down (apparently not enough airflow in the HighAirFlow - HAF 932).

Tested upgrading to Ubuntu 12.10 for a short while - NOT recommended! CPU allocation to FAH decreased almost 100% (of 6400%) due to kworker processes. Back to 10.10 and TPF now 10:45 for WU 8101 @ 3.0 GHz. "If it works - don't fix it..."

P.S. Found some code that determines the clock speed here I have not fully tested it yet but it seems to work also on the OCNG bios for MCs.
 
Last edited:
Was that 12.10 server or desktop?
 
You could get very low CPU temperatures if replacing the stock fans with some super high-power fans (>1A current). A temperature decreasing of 15 to 20 degree is possible.
But those high-power fans would be very noisy.

DrFredrik said:
Managed to get the temperatures down another 5 degrees by opening the side panel of the HAF 932 and laying it down (apparently not enough airflow in the HighAirFlow - HAF 932).
Click to expand...
 
Last edited:
DrFredrik said:
Tested upgrading to Ubuntu 12.10 for a short while - NOT recommended! CPU allocation to FAH decreased almost 100% (of 6400%) due to kworker processes. Back to 10.10 and TPF now 10:45 for WU 8101 @ 3.0 GHz. "If it works - don't fix it..."
Click to expand...
I... doubt it. Did you reinstall thekraken?

Generic (universal) kworkers are substitutes for dedicated worker threads, so you have
~CPUNUM workers (or so)...
Code: 
$ ps auxw | grep [^]]/11
root        38  0.0  0.0      0     0 ?        S    Sep26   0:00 [migration/11]
root        39  0.0  0.0      0     0 ?        S    Sep26   0:00 [kworker/11:0]
root        40  0.0  0.0      0     0 ?        S    Sep26   0:00 [ksoftirqd/11]
root       464  0.0  0.0      0     0 ?        S    Sep26   0:49 [kworker/11:1]
... instead of CPUNUM*N workers ...
Code: 
$ ps auxw | grep [^]]/11
root        36  0.0  0.0      0     0 ?        S    Sep29   0:00 [migration/11]
root        37  0.0  0.0      0     0 ?        S    Sep29   0:03 [ksoftirqd/11]
root        38  0.0  0.0      0     0 ?        S    Sep29   0:00 [watchdog/11]
root        50  0.0  0.0      0     0 ?        S    Sep29   0:18 [events/11]
root        69  0.0  0.0      0     0 ?        S    Sep29   0:00 [kintegrityd/11]
root        81  0.0  0.0      0     0 ?        S    Sep29   0:00 [kblockd/11]
root        96  0.0  0.0      0     0 ?        S    Sep29   0:00 [ata/11]
root       163  0.0  0.0      0     0 ?        S    Sep29   0:00 [aio/11]
root       175  0.0  0.0      0     0 ?        S    Sep29   0:00 [crypto/11]
root       511  0.0  0.0      0     0 ?        S    Sep29   0:00 [xfslogd/11]
root       523  0.0  0.0      0     0 ?        S    Sep29   0:00 [xfsdatad/11]
root       535  0.0  0.0      0     0 ?        S    Sep29   0:00 [xfsconvertd/11]

While there have been non-FAH reports of "excess kworker CPU usage" we haven't
seen them around here.

Think of kworker as a "service guy". Kworker consuming cycles == someone _else_
(some facility) gave it something to do, kworker just does what it was told. Root cause
of such "issue" would be outside kworker itself...

P.S. Found some code that determines the clock speed here I have not fully tested it yet but it seems to work also on the OCNG bios for MCs.
Click to expand...
Yeah, it mostly works but is not yet universal. One day it will be :)
 
Well - maybe my conclusion was a bit premature, but I noticed significantly lower PPD and a lot of new processes that consumed 1-2 % CPU time each (this was not the case in previous versions of ubuntu desktop). If there is something to gain for folding IL by upgrading to 12.10 then I would like to know about it, but for now I will stay with 10.10
Tear: Have you tried running your ILs at 3.2 GHz? Your temperatures seemed fine so...
 
Last edited:
If there is something to gain for folding IL by upgrading to 12.10 then I would like to know about it, but for now I will stay with 10.10.
Click to expand...
There really isn't. 10.10 is absolutely fine.

I wasn't making an argument, btw; merely tried to explain that it's not the kworker itself
that is to blame but whoever gave it stuff to do :)

Tear: Have you tried running your ILs at 3.2 GHz? Your temperatures seemed fine so...
Click to expand...
I did try going > 3.0 but the board (S8812) would shut off after a while. Moving CPUs to GL
would most likely open some options but I haven't had enough spare time to do that...
 
What is the power draw when the board would shut off? I think 4p ILs should be easy to work at 3.2ghz while 4p MCs is a bit difficult.
 
tear said:
In general, you should be fine with rev. D1 chips (part number ending with E25). Just pay
attention to die temperatures (TurionPowerControl -temp) and other weird phenomena
(coils squealing) as these could contribute to motherboard's demise.

Rev. D0 chips (part number ending with E21) are generally a miss though (from data
we've gathered)...
Click to expand...

Hrm... All of mine are the E21 series. Looks like I need to fire them up and see how they go. But I am looking at some E25s on the 'bay right now too.
 
Last edited:
quickz said:
What is the power draw when the board would shut off? I think 4p ILs should be easy to work at 3.2ghz while 4p MCs is a bit difficult.
Click to expand...

I am now running at 3.1 GHz with vCore 1.175 Volt and temps below 52deg C.

Edit: TPF about 10:00 to 10:15 on WU 8101 and PPD well above 500 000.
No info on power consumption yet, but will check later.

Edit2: Increased to 3.2 GHz at 1.175 V - same temps. TPF below 10 min and PPD around 550 000 for 8101. So far so good...
 
Last edited:
It's nice. What is the TPF and power draw number for your rig @3.1GHz?
In my opinion, 3.1GHz is a fairly safe frequency for Opteron 6200s. The stock frequency of 6200s is much higher than 6100s, and 3.1GHz is just the default all-core turbo frequency of Opteron 6284SE. I feel strange why few people try it before. And I think you should be able to work at higher frequency without problems if your PSU is okay and you could find better heatsinks for your rig.

DrFredrik said:
I've am now running at 3.1 GHz with vCore 1.175 Volt and temps below 52deg C
Click to expand...
 
quickz said:
What is the power draw when the board would shut off? I think 4p ILs should be easy to work at 3.2ghz while 4p MCs is a bit difficult.
Click to expand...
I don't honestly remember, quickz. It was long time ago...
 
My B1 stepping IL chips are now running happily at 3.2 GHz with vCore 1.175 V
However I have some B0 stepping chips that experience random shutdowns already at 3.0 GHz and the same vCore. That rig is water cooled and temps are below 50 deg C. I have now decreased the frequency to 2.9 GHz and the vCore setting to 1.1625 V to see if the shutdown behavior depends on temps/vCore.
Any suggestions on what more I can do?
 
I suggest you try to increase the vCore of those B0 chips, and see if it becomes more stable or doing shutdown more quickly.
BTW, B1 chips are believed to be much better at overclocking than B0, why not upgrade all of your chips with B1 ones?

DrFredrik said:
My B1 stepping IL chips are now running happily at 3.2 GHz with vCore 1.175 V
However I have some B0 stepping chips that experience random shutdowns already at 3.0 GHz and the same vCore. That rig is water cooled and temps are below 50 deg C. I have now decreased the frequency to 2.9 GHz and the vCore setting to 1.1625 V to see if the shutdown behavior depends on temps/vCore.
Any suggestions on what more I can do?
Click to expand...
 
Any progress? 1.175v vcore is not too high at all, your B1 chips should be able to work at 3.3GHz or even higher without problems.

DrFredrik said:
My B1 stepping IL chips are now running happily at 3.2 GHz with vCore 1.175 V
However I have some B0 stepping chips that experience random shutdowns already at 3.0 GHz and the same vCore. That rig is water cooled and temps are below 50 deg C. I have now decreased the frequency to 2.9 GHz and the vCore setting to 1.1625 V to see if the shutdown behavior depends on temps/vCore.
Any suggestions on what more I can do?
Click to expand...
 
quickz said:
Any progress? 1.175v vcore is not too high at all, your B1 chips should be able to work at 3.3GHz or even higher without problems.
Click to expand...

B1 chips are running stable at 3.2 GHz and 1.175 vCore with temps in the low 50s..
B0 chips were running stable at 2.9 GHz and 1.1625 vCore but the board suddenly died unexplicably. Does not post, no fans running... Thought the PSU had broken first, but it worked with another board. Had already ordered another H8QGL-IF+ board that hopefully should arrive soon... but will run B1 chips on that one instead of dubious B0.
 
I've had B0 chips for many months now and they're running fine in S8812 at 3.0.
 
OK, I have a question, how do we tell if it's B0 or B1?
I thought I had the B1 stepping but just wanted to be sure...
 
Try "cat /proc/cpuinfo | grep stepping", 0 and 1 represent for stepping B0 and B1, respectively.

theGryphon said:
OK, I have a question, how do we tell if it's B0 or B1?
I thought I had the B1 stepping but just wanted to be sure...
Click to expand...
 
quickz said:
It's nice. What is the TPF and power draw number for your rig @3.1GHz?
In my opinion, 3.1GHz is a fairly safe frequency for Opteron 6200s. The stock frequency of 6200s is much higher than 6100s, and 3.1GHz is just the default all-core turbo frequency of Opteron 6284SE. I feel strange why few people try it before. And I think you should be able to work at higher frequency without problems if your PSU is okay and you could find better heatsinks for your rig.
Click to expand...

At 3.2 GHz the power draw is about 950 W when running a 8101 WU (the meter is jumping between about 880 and 1000 W). I will probably step up to 3.3 pretty soon as the temperatures outside are dropping below freezing soon (which helps cooling the rig too). Will not change heat sinks - just upgrade the fans if necessary. The PSU is a 1000 W Fractal Design Newton R2 and should cope with a bit higher vCore (wall draw 1250 W at 80% is 1000 W after all...)
 
You might only need to increase vcore very slightly, according brainbug's vcore setting (3.6GHz @ 1.3275V (1.3250?)), I think 1.2V vcore should be enough for 3.3GHz.
 
quickz said:
Try "cat /proc/cpuinfo | grep stepping", 0 and 1 represent for stepping B0 and B1, respectively.
Click to expand...
As there have been Ax rev chips out there I'd also recommend checking model name;
ending with G44 -- B0, ending with G45 -- B1.
 
quickz said:
You might only need to increase vcore very slightly, according brainbug's vcore setting (3.6GHz @ 1.3275V (1.3250?)), I think 1.2V vcore should be enough for 3.3GHz.
Click to expand...

I'm running 3.3 GHz now with the same vCore 1.1750 V. Power draw about 1000 W at the wall and temps low 50s. TPF 09:24 for WU 8101 which gives a PPD of 600 000. It is freezing outside now (-5 degC), and the rig is close to an open vent. Pretty cool stuff!
 
Very nice! It's even better than expected. Your TPF also seems to scale very well.


DrFredrik said:
I'm running 3.3 GHz now with the same vCore 1.1750 V. Power draw about 1000 W at the wall and temps low 50s. TPF 09:24 for WU 8101 which gives a PPD of 600 000. It is freezing outside now (-5 degC), and the rig is close to an open vent. Pretty cool stuff!
Click to expand...
 
I can not OC my 6276.
Can someone tell me what is wrong
Code: 
 --- Node 7:
Processor Maximum PState: 6
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.013v) - Maximum allowed VID 0 (1.550v)
Processor AltVID: 50 (0.925v)

root@amdd6276:~# TurionPowerControl -set core all pstate 1 frequency 2800 vcore 1.175
Turion Power States Optimization and Control - by blackshard - v0.43

All nodes all cores pstate 1 - set frequency to 2800.000 (rounded to 1600)
All nodes all cores pstate 1 - set core voltage to 1.175 (rounded to 1.5500)
*** -set parsing completed
Done.

root@amdd6276:~/# TurionPowerControl -l | grep 0.pstate.1
core 0 pstate 1 (p0) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 0 pstate 1 (p0) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 0 pstate 1 (p0) - En:1 VID:38 FID:10 DID:0.00 Freq:2600 VCore:1.0750
core 0 pstate 1 (p0) - En:1 VID:38 FID:10 DID:0.00 Freq:2600 VCore:1.0750
core 0 pstate 1 (p0) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 0 pstate 1 (p0) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 0 pstate 1 (p0) - En:1 VID:36 FID:10 DID:0.00 Freq:2600 VCore:1.1000
core 0 pstate 1 (p0) - En:1 VID:36 FID:10 DID:0.00 Freq:2600 VCore:1.1000
 
Output seems fine. Been folding this setup with 6180 SE for months. Now I update bios to version 3.0 supporting 6300 and also upgrade ubuntu to 12.04 desktop.

It folds perfectly fine with tpc -psmax 1 for several days. I just try to OC today and not getting any change.

Code: 
root@amdd6276:~# tpc -dram
Turion Power States Optimization and Control - by blackshard - v0.43


DRAM Configuration Status

Node 0 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58

Node 1 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58

Node 2 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=60
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=60

Node 3 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58

Node 4 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58

Node 5 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58

Node 6 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=59
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=59

Node 7 ---
DCT0: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58
DCT1: DDR3 frequency: 1333 MHz
Tcl=9 Trcd=9 Trp=9 Tras=24 Access Mode:1T Trtp=5 Trc=33 Twr=10 Trrd=4 Tcwl=7 Tfaw=0
TrwtWB=8 TrwtTO=7 Twtr=5 Twrrd=1 Twrwrsdsc=1 Trdrdsdsc=1 Tref=2 Trfc0=2 Trfc1=4 Trfc2=4 Trfc3=4 MaxRdLatency=58


Done.
root@amdd6276:~# locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
root@amdd6276:~#
 
Sorry, my bad .... looks like it is working now :eek:

Code: 
root@amdd6276:~# TurionPowerControl -l | grep 0.pstate.1
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
core 0 pstate 1 (p0) - En:1 VID:30 FID:12 DID:0.00 Freq:2800 VCore:1.1750
 
I am using 4 x 6276ES ZS232545TGG45 stepping B1 in a SM H8QGI-F mobo. I have installed TPC v0.43 and have run: sudo tpc -psmax 1

The thing is now running at 2.6GHz folding on a 8101, TPF = 11:57, PPD = 420K

How do I overclock this chips to a higher level? I have tried tear´s http://hardforum.com/showpost.php?p=...20&postcount=7
without any luck.
 
Last edited:
Are you using the stock version of tpc 0.43? That is bugous and would not work for overclocking at all.
Try tear's version please:
http://darkswarm.org/tpc/tpc-svn64-tear4.tar.gz

-alias- said:
I am using 4 x 6276ES stepping B1 in a SM H8QGI-F mobo. I have installed TPC v0.43 and have run: sudo tpc -psmax 1

The thing is now running at 2.6GHz folding on a 8101, TPF = 11:57, PPD = 420K

How do I overclock this chips to a higher level? I have tried tear´s http://hardforum.com/showpost.php?p=...20&postcount=7
without any luck.
Click to expand...
 
I did use this one that musky made last month: http://hardforum.com/showthread.php?t=1669698 I first tried that one you pointing to, but was not able to make it work. I got an error message 127 or something.

Oputput of:
vidar@G34Rigg3:~$ sudo tpc -l | grep "pstate 1"

HTML: 
core 0 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 1 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 2 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 3 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 4 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 5 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 6 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 7 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
core 7 pstate 1 (pb1) - En:1 VID:37 FID:10 DID:0.00 Freq:2600 VCore:1.0875
I have a change in WU in about one hour, and will try tear's version again after the change!

quickz said:
Are you using the stock version of tpc 0.43? That is bugous and would not work for overclocking at all.
Try tear's version please:
http://darkswarm.org/tpc/tpc-svn64-tear4.tar.gz
Click to expand...
 
Last edited:
How do I change to tear´s version? I am quite stupid in use of Linux in general.
 
Just download and compile it:
Code: 
wget http://darkswarm.org/tpc/tpc-svn64-tear4.tar.gz
tar -zxf tpc-svn64-tear4.tar.gz
cd tpc-svn64-tear4
make
make install
TurionPowerControl -l

-alias- said:
How do I change to tear´s version? I am quite stupid in use of Linux in general.
Click to expand...
 
It look like I did something right this time, output like this at the end:
Code: 
-- Node: 7 Core 7
core 7 pstate 0 (pb0) - En:1 VID:19 FID:16 DID:0.00 Freq:3200 VCore:1.3125
core 7 pstate 1 (pb1) - En:1 VID:38 FID:10 DID:0.00 Freq:2600 VCore:1.0750
core 7 pstate 2 (p0) - En:1 VID:44 FID:7 DID:0.00 Freq:2300 VCore:1.0000
core 7 pstate 3 (p1) - En:1 VID:46 FID:5 DID:0.00 Freq:2100 VCore:0.9750
core 7 pstate 4 (p2) - En:1 VID:47 FID:2 DID:0.00 Freq:1800 VCore:0.9625
core 7 pstate 5 (p3) - En:1 VID:49 FID:0 DID:0.00 Freq:1600 VCore:0.9375
core 7 pstate 6 (p4) - En:1 VID:51 FID:12 DID:1.00 Freq:1400 VCore:0.9125

 --- Node 0:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 50 (0.9250V)

 --- Node 1:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 50 (0.9250V)

 --- Node 2:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 50 (0.9250V)

 --- Node 3:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 50 (0.9250V)

 --- Node 4:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 50 (0.9250V)

 --- Node 5:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 50 (0.9250V)

 --- Node 6:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 51 (0.9125V)

 --- Node 7:
Processor Maximum PState: 1
Processor Startup PState: 5
Processor Maximum Operating Frequency: No maximum defined. Unlocked multiplier.

Minimum allowed VID: 123 (0.0125V) - Maximum allowed VID 0 (1.5500V)
Processor AltVID: 51 (0.9125V)

Done.
vidar@G34Rigg3:~/tpc-svn64-tear4$
What to do then to make it run in 3GHz?


quickz said:
Just download and compile it:
Code: 
wget http://darkswarm.org/tpc/tpc-svn64-tear4.tar.gz
tar -zxf tpc-svn64-tear4.tar.gz
cd tpc-svn64-tear4
make
make install
TurionPowerControl -l
Click to expand...
 
You must log in or register to reply here.
Back
Top