Post
Topic
Board Mining support
Re: Hacking The KNC Firmware: Overclocking
by
mwarrior
on 19/12/2013, 05:07:58 UTC
I second that.  I'm getting between 575 and 625 on my day 1 shipment miner (which arrived on day 5) .  The Beaglebone board went south on mine the second week I had it and I lost 2 weeks due to incompetence by KNC.  This is truly amazing and I thank you so very much for sharing the info.  Still wish I had my 2 weeks back when the difficulty was still 86,933,018, but this takes a little pain away from the wound and I salute you for it.  Curious if any of you guys bit on the new miner?  If so I look forward to seeing what you can accomplish.  I didn't bite on that one myself after getting burned the first time... but will be watching.  Many thanks!


- .m.w. -


and all you did was issue this:

sed sBD1BF1B /config/zzz.sh ; /config/zzz.sh restart

??

The sed command changes one register and gives you a mild 7% boost in speed. In order to see the fastest speeds you need to read though the hieroglyphics on this thread and figure out what they are saying. when I figured it out, I am getting almost 15% over factory speeds.

The main thing you need to do is ssh into your miner and use a text editor to edit /etc/init.d/cgminer.sh

try:
vi /etc/init.d/cgminer.sh


Use the cursor keys on your keyboard to scroll down till you see this code, the important parts you will change are in bold:

Quote
                                                           
                                if [ $p -eq 2 ]                                            
                                then                                                      
                                        cmd=$(printf "0x86,0x%02X,0x01,0xF1" $c)          
                                        if [ $c -eq 1 ]                                    
                                        then                                              
                                                cmd=$(printf "0x86,0x%02X,0x03,0xE2" $c)  
                                        fi                                                

When you see someone say "Try 201" (which gives about 12% speed increase) you would edit the code to look like:

Quote
                                                           
                                if [ $p -eq 2 ]                                            
                                then                                                      
                                        cmd=$(printf "0x86,0x%02X,0x02,0x01" $c)          
                                        if [ $c -eq 1 ]                                    
                                        then                                              
                                                cmd=$(printf "0x86,0x%02X,0x03,0xE2" $c)  
                                        fi                                                

Hit escape when finished. Then hit the : key, then x to save.

relaunch cgminer with the command line:
/etc/init.d/cgminer.sh restart

Don't blame me if shit blows up. I'm just one newbie helping another.


I personally use 211, but have extra fans inside the case for extra cooling, just to be safe. A list of codes and corresponding speeds are listed several times in this thread, I suggest trying several until you find one that gives you a good boost in speed without going over 40-42watts per die, since they are rated at 40W per VRM.

Good luck.


Wow.  I must say hieroglyphics / Greek / anything I can't understand fits this fits just perfect.  After about 5 hours I figured it out.  I think a lot of people are looking for an exact match to the (p) values in the code etc. Thanks for this info.  I was able to bump my 8 VRM jupiter up to a 15% increase as well and it is running great.  Temps are fine as it's running in the garage and cold as balls down there.  I have 1 chip running at 55° and the other 3 are between 35° and 38°.  What is the max temp you want to get these  while overclocking?  The whole vi editor seems very antiquated to me but I most certainly see where it is useful (and I'm sure all the old school mainframe guys at work know it well).  With what you did above,  does it adjust all chips or just one?  I'm pretty sure I saw that you should have a section for each ASIC, but it also looks like the code might perform a wham bam thank you man and do all at once.  Still trying to figure that part out.   Thanks!