Topic: Hacking The KNC Firmware: Overclocking - page 37. (Read 144377 times)

Hi all, for some strange reason i gave a go for the wizkids version again. Now driven with 315-setting, my wattage on bertmod shows 435 and average hashrate on poolside 470-480gh/s. This is great but I wonder why it didnt show this before. Perhaps i different settings for better for the 3.9.0 and some for 3.8.5, dunno.. Im just happy =)

yes i've been tuning individual dies since going on 251...been a struggle but Nil's graph has helped me tremendously...just now got it down to .38% and i hope it says that low..might be lower if i could disable the core that get 160hw errors an hr but oh well

told you my spi settings...tryed your 256k freq and i don't think it helped, but i might start trying diff. volt n freq next as i think i got the die volts locked in almost

3rd...i don't understand this question...but i'm on a 1000w seasonic plat. psu, but you might be able to swing it if you keep the vrms cool enough

thx!

In a "normal operating range," yes.. but as you get to the design limits and beyond, it is the current that makes a board melt, not a watt.

For example - properly insulated, you could push 40,000V at 1A through a thin wire, getting 40,000W in the circuit, and the wire would live.
But if you reduce to 1V and tried to get 40,000A through that same wire, the wire wouldn't live.

That's why power distribution lines run at a very high voltage, to keep the current within the wire's limits. Hope that helps.

You are my hero

1) have you changed the settings of the individual die (more volts ?) ?

2) or just general spi ? (in addition to frequency)?

3) How many amps and watts marks every single day? With a cooler master V850 can set the miner to 251 according to you?

Now I have 666 average with 231 setting  (3.3 spi and 256 k freq) with october jupiter and 4 45 degrees fans and 1 megaflow

shouldnt WATT be more important as A? in the end its the wattage that leads to temperature.

yes 251 very high...have 10 fans cooling it and still have have amps...my spi volts are 3.3 and the freq is 201442

after running it all nite...pool reported as high 723gh and cgminer avg settled at 714...thinking about trying the next step up or 261 but idk...amps are pretty high on one board

ok, did not see this option in 99.2 ..thank you!

+1

ok 251 is very high for october ? Could you please tell me you spi settings with frequency ? ( screenshot please ?)

1. Make a copy of cgminer.sh before you install bertmod in your /config directory. Use that to modify and stop and start the miner.
2. Don't use Bertmod for bfgminer, use the latest firmware from KnC it has bertmod installed.
3. You will need to search for a modified cgminer.sh to use after you installed the latest firmware, it works with both cgminer or bfgminer to add back the overclocking parts of the script. There are a few floating around in this thread I believe

i don't get it. how did you use bfgminer for the stats for each asic and had the possibility to try the 251 settings. After flashing bertmod 0.4 for the use of bfgminer the cgminer.sh is an other. and after changing the volts all amp are droping(wellknown) and than it is not possible to change the values in cgminer.sh and restart bfgminer.

Whats more important for the safety of those VRMs? Ampere or Watt?

I have one VRM with 60A and 46Watt.

I've noticed that too, but my unit almost does it every time...if you mess with the spi freq. that can do it i think...cause i just increased mine and it didn't do it anymore...went back to stock and it did it again...

well on 251 with oct. jup...thxs to the graph i was able to finally get the hw error down to .4% and 718-723gh/s on cgminer, bertmod says 700w same as 241, but that was before better cooling fans added...have one board at 240a :O hope it doesn't fry..and also 1 board at 200a but its at 42c Hopefully pool will report higher hash now that i got the hw % down i'll know morrow morning

@new_pilot: Where would I be able to see die speed on november unit? Can i just run october tuning with november unit or what to do?!

Just tried setting 301 (changed the last to from 5 to 1 ) It start hashing at the same rate, if a hint less ie like 459gh with 305 and 450gh with 301. It was short test but tolip is correct i think.

I think i need to start lowering that 12V input voltage to asic-vrm as to lower the power consumption in them 

It was asked earlier the location of the temp measurement IC

It is located straight in from the ribbon cable connection at the corner of the ASIC package.

Repeating.........

The corner of the ASIC is not an ideal location (it is cooler at the corners)
The ASIC is easily 10C hotter than the temp chip.
I measured back side of PCB and see higher temps.
(measured both IR (gun) and direct contact thermocouple)

The VRM's are WAY hotter than the temp chip on both sides of PCB.
The VRM's are designed for airflow in the direction of inside to outside (as placed by KnCMiner) FWIW

Don't forget you need some air to flow UNDER the PCB too, it is a heatsink also!


Thx for thr thermal pics!

YMMV

@temen

What speed is each 'die' running at?
(48 core per die, 4 die per ASIC)

clock settings ending in 5 are likely the same as ending in 1
The last digit is the divisor but may only recognise lowest 2 bits


ie: 265 prolly the same as 261 (975MHz)

I'm prepared to be proven wrong but need die speed to do so!

YMMV

mekadeka, thank you! Thats my first ever donation received, gonna put it on the wall=)

I think the consumption is part of many different parameters. I would love to lower the volts. That 265 might just "fit" in between clocks etc. Like somekind of "best time to open transistor gate, capacitance pumped full just before" etc.

Setting 5D6 works for me also, just has to be restarted many many times before it "catches" that=). It has somehow lower poewr consumption and it settles for 450gh/s after a while. I tried with 5E6 and 5F6 but even initially showing fast hash-rate it always settles to 450gh with this.

Before i used to have that 340gh/s as a norm. Then installed 3.8.5 and once i noticed that when starting and immediately with screen -dr seeing what happens it started right away like 2 times faster, then got up to 4 times and after that initial sequence it settled for 370gh/s.

If i want to get better gh/s even with 305, I have to start many times, best result is when initially on the screen there is reading like 700+ gh/s, after that if shows 1,68 th/s and then fluctuates between 500-700 gh/s for moment. Then it settles to 459 (cgminer) which on the poolside shows 488 =) Not normally that much but now it seems to be that.

If the gh-speed doesnt start initially from high value, then miner settles down to lower value. This is strange but perhaps there is some "initial modification" done on cgminer that sets the rate for rest of the session.

Sometimes i have to restart like 10 times to get this "high catch" effect. Its pain to wait in between, because without delay you just get fault 96/97 on vrms. Which means restarting the miner from the page (I dont like to switch off power but had to do that some times)I always wait like at least 45 seconds if vrms have been running for a while to let them cool down.

Hi, feedback. Yes, I am measuring at the pool, too. Currently, the miner GUI is showing 341gh. Cgminer is showing 338g/341. The pool is showing 316g with .13% rejects. I have not looked at the error rate on cgminer yet to see if it fills the gap. Instead, I am going to reset the pool worker's stats, since I have some things to do this morning. I'll report back.