Quote from: cypherdoc on January 22, 2014, 08:40:07 AM

Quote from: allinvain on January 22, 2014, 06:42:12 AM

Quote from: Doff on January 22, 2014, 03:06:21 AM

Quote from: cypherdoc on January 21, 2014, 09:02:59 PM

Quote from: Morblias on January 21, 2014, 06:04:25 PM

Quote from: cypherdoc on January 21, 2014, 04:28:27 PM

however, when i try to update bfgminer with:

Code:

cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now

i get this:

Code:

error: Your local changes to the following files would be overwritten by merge:
driver-bfsb.c
Please, commit your changes or stash them before you can merge.
Aborting

how can i fix this error?

I had that problem back when I tried to update cgminer in minepeon. Kano used this as a solution back then:

Quote from: kano on August 17, 2013, 12:04:11 AM

git checkout etc/miner.conf.donate
git pull

So I am guessing (might be wrong) your solution might be something like this:

Code:

cd bfgminer && git checkout driver-bfsb.c && git pull && make && sudo make install && sudo shutdown -r now

worked great Morblias, thank you.

my stratum connection is rock solid now and i'm continuing to tweek chip settings.

Can you actually tune individual chips with MFG?

There is but it's not as userfriendly as editing the best.cnf or .stats.log as with chainminer.

Care to elaborate?

It works the way described in this quote by punin. You essentially have to tell bfgminer at startup the speed for each individual chip. As you can see it can result in a very long command line argument (naturally you can script this by creating a shell script):

Quote

compile with --enable-bitfury
con is not going to make support for our hardware because it only runs on linux, pi and needs root access
so this is as far as cgminer support will go from our side Sad
./cgminer --help
--bitfury-board-type Bitfury board type, 0=i2c, 1=mboardv1, 2=mboardv2 (default: 0)
--bitfury-options Set bitfury chip options chip:speed,chip.. eg. 0:55,1:56... default: ALL:54
old M-board probably doesn't work because no-one has tested it
so use --bitfury-board-type 2