bitcoinorama mentioned KnC is planning to release PLL clock FW.
You can wait for KnCMiner and save the warranty,
or not.
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
orama also mentioned that KnCMiner considers 63A per GE DC/DC OK
https://bitcointalk.org/index.php?topic=170332.msg4106143#msg4106143Yikes!!!
That can make more heat than the ASIC can move to the heatsink IMneverHO
People wanting a different method.
This will not really lower the bar, but might help you over it.
(the sed thingy is about as easy as it can get)
More hints (a mini howto tangent)
You need vi or some other editor.
Almost every *nix system has vi on it FWIW
I only use a few commands in vi
A super abbreviated vi survival guide follows.
ESC = escape key, I start every vi command with escape to make sure I am not in insert mode.
i = insert
a = append
r = replace chr under cursor
cw = change word under cursor
x = delete chr under cursor
dd = delete line cursor is on (deleted line is copied to buffer (similar to CTL-x))
Y = yank(copy) line to buffer
P = pop(paste) line from buffer
: = start of command to vi (file ops etc.)
:w = write current file to disk
:q = quit
:wq = write file and quit editor
:q! = quit without saving changes(it's all fucked up start over
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
/ = search
Ex:
'cp /etc/init.d/cgminer.sh /config/zzz.001.sh'
'vi /config/zzz.001.sh'
hit the slash key '/' then type D1 and hit enter
Your cursor should now be on the line most reading this seek.
Yank the line to the buffer with 'Y'
Pop a copy of the buffer back into the file with 'P'
now you have 2 lines exactly the same
hit 'i' to insert text
put a '#' at the beginning of one the copies (turn it into a comment/reminder)
hit the ESCape key to get out of insert mode
move the cursor to the other copy of the line and over the 'D' in 0xD1
hit the 'r' key and replace the 'D' with a 'C'(slower) or an 'E' or an 'F'
hit Esc then ':wq'
thats it !
It's not hard just cryptic
It is possible to edit on a Win box and xfer the edited file with 'scp'
Google 'man scp' to learn more.
bfgminer is needed to adjust all die for best results.
With temp and HW error% seperated by ASIC no need for other Status webpage.
You still need the Advanced web page though.
cgminer can run the 'result' too but not provide much feedback during discovery.
I am a fan of BOTH cgminer and bfgminer FWIW both work well on KnCMiners.
Most of you lazy fornicators will try the seemingly easier softer way without bfgminer.
You will find it is not easier and softer if you cook an ASIC or VRM.
(permanent high HW error or worse)
bfgminer will not save the ASIC but it might let you know something is amiss in time to manually intervene.
KEY WORD = might
Clock specific mini bfgminer howto:
Use your newly minted vi skills
Go to this webpage
https://github.com/luke-jr/bfgminerClick on README.ASIC -->
https://github.com/luke-jr/bfgminer/blob/bfgminer/README.ASICScroll to the bottom and find and READ the KnC section
Copy the text with your mouse
Then on the miner do the following (in a SSH window)
'vi /config/BFG_build.sh'
hit the 'i' key to insert text
Right click and paste text copied from webpage
Look at the bottom of the file for 2 lines
/etc/init.d/cgminer.sh stop
./bfgminer -S knc:auto -c /config/cgminer.conf
They stop cgminer and start bfgminer as soon as it is built
You may not want to do this automatically as it does not use the mods this way.
To change this behavior,
move your cursor to the beginning of one of the lines,
hit 'i' and comment it out by inserting a '#' at the beginnig
move to the other line and hit '#' again.
Then they will look like this
#/etc/init.d/cgminer.sh stop
#./bfgminer -S knc:auto -c /config/cgminer.conf
hit Esc key
hit ':' (colon)
hit 'w'
hit 'q'
hit enter
Now run it to build bfgminer
'source /config/BFG_build.sh'
Wait (might be 10 minutes or so)
When it is done cd into the new bfgminer folder
'cd /config/bfgminer'
For our purposes we need the startup stuff cgminer uses (the file with the clock info)
'cp /etc/init.d/cgminer.sh /config/bfgminer/bfgminer.sh'
edit the file with
'vi /config/bfgminer/bfgminer.sh'
change the
DAEMON=/usr/bin/cgminer
to
DAEMON=/config/bfgminer/bfgminer
Change every instance that reads 'cgminer' so it reads 'bfgminer' instead.
EDIT*** except for the config file part.
Thx CYPER for pointing it out.
Should look like
start-stop-daemon -b -S -x screen -- -S bfgminer -t bfgminer -m -d "$DAEMON" --api-listen --default-config /config/cgminer.conf
Save the file ':wq'
Prepare your workspace
Treat every test as a pit stop with a plan A and a plan B
Test plan B first!!!!!
A good plan B might be
'/config/bfgminer/bfgminer.sh stop ; /etc/init.d/cgminer.sh restart'
open 3 SSH windows or tabs per miner
One for vi (just use Esc-colon-w and stay in the editor for fast fixes) or scp
One to start and stop modified and unmodified shell scripts (up arrow is your friend)
One to run screen -r (after you do it once just use up arrow and Enter)
One web page ALREADY open to the Advanced tuning page for temp/volt/current/watt
After starting the modified shell script this is the first place to tell how it works
A few seconds is all it takes.
3 flavors to look for
0 or very low die (ANY die)
10-15 watts (ANY die)
30 watts or more (ALL die)
The first 2 require immediate action, Plan B!
You might first QUICKLY try just restarting.
The third indicates some degree of success requiring further investigation.
Wasting power and punishing ASIC without extra hash at the pool is non productive.
Sometimes a die can show power consumption and not be contributing.
***
*** This can happen after it has been running OK for a while and be hard to find.
***
Review the pitstop plans one more time!!!
NOW stop cgminer and start bfgminer
'/etc/init.d/cgminer.sh stop'
'/config/bfgminer/bfgminer.sh restart'
(I always use restart even though it may not be running and start would be more correct, for easy reuse with the arrow keys for speed during pit stop)
In your ssh that was running the screen showing cgminer it drops back to command line
hit the up arrow and Enter(or type 'screen -r' again) and view bfgminer hashing
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
Suggest first run with bfgminer use unmodified clocks
If you got this far you are ready to add a section for each ASIC and die to COPY_OF.bfgminer.sh
!!!Also note!!!
The miner has a DC/DC monitor that is occasionally unhelpful.
(possibly because you are stopping cgminer and starting bfgminer when it looks)
If it does this it will start cgminer.
This can occasionally happen when restarting bfgminer.
The solution is '/etc/init.d/cgminer.sh stop ; /config/bfgminer/bfgminer.sh restart'
(Advanced web page shows it running but bfgminer says nada or 'screen -r' says already running or somesuch)
MAKE NOTES!!!
16 different die in one box can be confusing.
Other fun toys are in the bfgminer(or a cgminer) source directory too.
read the file README.RPC
'less /config/bfgminer/README.RPC'
then look at
miner.php
^^^^^^^^^
(I run this on my PC,
it collects all miners into one place,
and shows more status of each core)
also look at
api-example
api-example.php
api-example.py
A lot can be done with just api-example (and grep)
Don't reboot, rarely needed, else rebuild bfgminer again after.
Just 'q'uit and run unmodified
'/etc/init.d/cgminer.sh restart'
instead.
(ways around this limitation exist but are beyond the already large scope of this post)
Hope this helps someone get over the hump and wake a sleeper and possibly into new GH territory.
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)