ChainMiner for M Board Version 2.X boards
DO not use this guide for Version 1x m-boards.
It will fry your chips.  This is only meant for Version 2 of the M-board.
I apologize for grammar as I took 2 sleeping pills and I can barely feel my fingers.

1.login as pi or root

2.  type "nano /run/shm/.stat.log"   if you wish to see the performance of all the chips on your board before upgrading chain miner.
(optional step)
3.(backup your chainminer version)  (this creates a copy of the folder)
a. sudo cp -a /opt/bitfury /usr/bitfury.backup
b. cd /opt/bitfury/
c. pwd  (make sure you are in /opt/bitfury)
d. ls -al (or type dir)
e. rm -rf chainminer  (this removes everything in the chainminer folder)
4.  make sure you are in the /opt/bitfury directory and not in /opt/bitfury/chainminer (it should be deleted anyway
5.  type "git clone https://github.com/bfsb/chainminer.git"
6.  it should now start getting the chainminer git.
7.  now type "cd chainminer"  you should now be in the chainminer directory
8.  type "make"
9.  Its going to take 5-10 minutes to create the chainminer...maybe longer.
 I got some warning but everything was fine after it all finished.
 it will go back to a  bash prompt when done.
9a.  Just wait...this is the longest part of doing this change..
10.  sudo reboot

verkaufst Du H Boards 1 - 3 Stk. auch einzeln  ?

i usually donot measure ohms, I measure the output voltage of the regulator. But I think it should be between 1.05 to 1.08K on the mounted resistor.

d) Pencil mod the board until voltage reaches 0.8V. One of my boards is at 0.8V another at 0.84V. I would say 0.85V is the max after which either the regulator will shut down or the hash rate will drop dramatically.

and get a dyndns.org address to your home ip, as its ip address might change. Put the dyndns details in your router, and you will always have minerXXXX.dyndns.org as your connecting point to your home network.
I'd recommend having some sort of VPN firewall setup if you really want to access home from outside..

Both are working on eligius, 60gh @diff 128, 45gh @diff 64. I tried 256, but it fell down to 30gh for 2hours tonight.

Guys heads up on pencil mod for overvolting and thus aiding overclocking.
Use pencil mod on R2F, make it around 1.1 - 1.2K, voltage goes from 0.66V to 0.81V. The default value is ~1.3K. It may blow the 30AFuse if you go too high; so make sure you do it only if you have a soldering station handy

After Mod (I have only 3 H cards )

I'm raising or lowering the speed of the chips, depending on the number of errors. I have also turned off the autotune. The point of manual tuning is that it works a little bit better than autotune.

Let's take the first chip as an example. Autotune is on (AIfDSo). It can be turned off by changing the capital A to a normal a (aIfDSo). Now the chip will always run at the speed you have set. Current speed is 55. Minimum is 52 and maximum is 57, higher the better of course. In this case I would raise the speed to 56 since there are practically no errors.

Chip two: change the "aifdso" to "aIfDSo" and let's see how it does (it won't work at all with aifdso).

Chip three: Something wrong with it. Turn off the autotune and keep the speed at 52. At least this is what I would do because 0,6 GH/s is still better than 0.

More info here http://punin.com/README_BFSB_v0.1.txt

Here is how I tune my chips manually:

- SSH into Pi (login "pi" password "raspberry").
- type "nano /run/shm/.stat.log"
- I'll edit the file and when done, press Ctrl+X
- It will ask "Save modified buffer" and I press Y as in yes.
- Now it says "File Name to Write: /run/shm/.stat.log". Just erase the whole file name with backspace and type "/opt/bitfury/best.cnf" and hit Enter.
- type "sudo reboot"

PSU considerations:

We also found a noticeable voltage drop on the IOVDD chain when all 16 cards are plugged in (down to 1V66 from 1V8). This will get fixed (hopefully) in next revision on M-boards, that is already in production. This should help lower the errors and noise on Bus D.