[GUIDE] BitFury Miner Support/Tuning

[BTClobsta]

hey guys i am running in to a problem with my rigs. i have two full rigs (v2 h-card & v3 m-board)
for some reason both of them just stop hashing. what could the problem? i'm still able to go in to the web browser.

[BenTuras]

hey guys i am running in to a problem with my rigs. i have two full rigs (v2 h-card & v3 m-board)
for some reason both of them just stop hashing. what could the problem? i'm still able to go in to the web browser.

Hit save stratum info, wait for the confirmation.
hit stop miners, wait for the confirmation.
hit start miners, wait for the confirmation.

It should be hashing again in a minute or two, if not something else is wrong. (Internet connection working?)

[BTClobsta]

hey guys i am running in to a problem with my rigs. i have two full rigs (v2 h-card & v3 m-board)
for some reason both of them just stop hashing. what could the problem? i'm still able to go in to the web browser.

Hit save stratum info, wait for the confirmation.
hit stop miners, wait for the confirmation.
hit start miners, wait for the confirmation.

It should be hashing again in a minute or two, if not something else is wrong. (Internet connection working?)

its not working. i really don't know whats wrong it was working fine. internet is working correctly. i have other miners that are still running.
its still looks like it is hashing from the blinking green light. but on the site (bitfury admin page) it shows 0 hash.

[daddyfatsax]

Please forgive my ignorance on this, but can I put bfgminer or cgminer on the pi and use that instead of chainminer? From the bfgminer page, there is no support for the V3 M-board and I have not been able to get cgminer running. I can compile it with bitfury enabled, but when I start it up I get nothing.

[klondike_bar]

hey guys i am running in to a problem with my rigs. i have two full rigs (v2 h-card & v3 m-board)
for some reason both of them just stop hashing. what could the problem? i'm still able to go in to the web browser.

Hit save stratum info, wait for the confirmation.
hit stop miners, wait for the confirmation.
hit start miners, wait for the confirmation.

It should be hashing again in a minute or two, if not something else is wrong. (Internet connection working?)

its not working. i really don't know whats wrong it was working fine. internet is working correctly. i have other miners that are still running.
its still looks like it is hashing from the blinking green light. but on the site (bitfury admin page) it shows 0 hash.

sounds like the pool info is correct or recently changed. check its configured correctly and connected to internet, not just the home network

[cypherdoc]

hey guys i am running in to a problem with my rigs. i have two full rigs (v2 h-card & v3 m-board)
for some reason both of them just stop hashing. what could the problem? i'm still able to go in to the web browser.

Hit save stratum info, wait for the confirmation.
hit stop miners, wait for the confirmation.
hit start miners, wait for the confirmation.

It should be hashing again in a minute or two, if not something else is wrong. (Internet connection working?)

its not working. i really don't know whats wrong it was working fine. internet is working correctly. i have other miners that are still running.
its still looks like it is hashing from the blinking green light. but on the site (bitfury admin page) it shows 0 hash.

try sudo reboot

[cypherdoc]

Please forgive my ignorance on this, but can I put bfgminer or cgminer on the pi and use that instead of chainminer? From the bfgminer page, there is no support for the V3 M-board and I have not been able to get cgminer running. I can compile it with bitfury enabled, but when I start it up I get nothing.

i'm successfully running salfter's image of bfgminer from here:

https://asktom.cf/index.php?topic=251966.msg4511347#msg4511347

just installed it yesterday and the great news is it seems to have solved my "reset" problems i described earlier.  that was my first priority in evaluating bfgminer.  i still need to fine tune them as the hashing rate is not optimal with a fair # of HW errors on some rigs but i'm very much encouraged.

[daddyfatsax]

Please forgive my ignorance on this, but can I put bfgminer or cgminer on the pi and use that instead of chainminer? From the bfgminer page, there is no support for the V3 M-board and I have not been able to get cgminer running. I can compile it with bitfury enabled, but when I start it up I get nothing.

i'm successfully running salfter's image of bfgminer from here:

https://asktom.cf/index.php?topic=251966.msg4511347#msg4511347

just installed it yesterday and the great news is it seems to have solved my "reset" problems i described earlier.  that was my first priority in evaluating bfgminer.  i still need to fine tune them as the hashing rate is not optimal with a fair # of HW errors on some rigs but i'm very much encouraged.

Awesome. I wasn't sure about that one, but I will give it a try. Thanks for the help.

[cypherdoc]

Please forgive my ignorance on this, but can I put bfgminer or cgminer on the pi and use that instead of chainminer? From the bfgminer page, there is no support for the V3 M-board and I have not been able to get cgminer running. I can compile it with bitfury enabled, but when I start it up I get nothing.

i'm successfully running salfter's image of bfgminer from here:

https://asktom.cf/index.php?topic=251966.msg4511347#msg4511347

just installed it yesterday and the great news is it seems to have solved my "reset" problems i described earlier.  that was my first priority in evaluating bfgminer.  i still need to fine tune them as the hashing rate is not optimal with a fair # of HW errors on some rigs but i'm very much encouraged.

Awesome. I wasn't sure about that one, but I will give it a try. Thanks for the help.

make sure you change the pool settings as they currently are pointed at his pool 

[Inamatus]

My 400GH/s Bitfury rig is not hashing after sudo reboot command

Output of /run/shm/.stat.log after reboot:

1       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
2       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
3       AIfDSo  52      0.000   0.000   0       0       0       0       0      $

Output of /run/shm/.stat.log after a few minutes following reboot:

1       AiFDso  52      0.000   0.000   0       0       0       0       0      $
2       AiFDso  52      0.000   0.000   0       0       0       0       0      $
3       AiFDso  52      0.000   0.000   0       0       0       0       0      $

As you can see, the autotune is turning off the chips.

Please help!

=========
extra output

pi@0-6-249:~$ sudo /opt/bitfury/start-miner-console.sh
SPEED: min:52 def:52 max:53
M-Board version 2 detected
INIT: 256 chips detected

=========

speed:13312 noncerate[GH/s]:0.000 (0.000/chip) hashrate[GH/s]:0.000 good:0 errors:0 spi-err:0 miso-err:0 duplicates:0 jobs:0 cores:0% good:256 bad:0 off:0 (best[GH/s]:$
board-2 speed   nrate   hrate   good    errors  spi-err miso-er duplic  good    bad     off     per chip        good cores
0:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%      speed down
1:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
2:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
3:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
4:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
5:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
6:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
7:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
8:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
9:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
A:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
B:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
C:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
D:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
E:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%
F:      832     0.000   0.000   0       0       0       0       0       16      0       0       (0.000/chip)    0%


====================

[KNK]

Can someone running a full rig with chainminer and proxy, please provide some info about load average and CPU idle time?

[cypherdoc]

My 400GH/s Bitfury rig is not hashing after sudo reboot command

Output of /run/shm/.stat.log after reboot:

1       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
2       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
3       AIfDSo  52      0.000   0.000   0       0       0       0       0      $

Output of /run/shm/.stat.log after a few minutes following reboot:

1       AiFDso  52      0.000   0.000   0       0       0       0       0      $
2       AiFDso  52      0.000   0.000   0       0       0       0       0      $
3       AiFDso  52      0.000   0.000   0       0       0       0       0      $

As you can see, the autotune is turning off the chips.

Please help!

make sure you wait at least a few min for hashing to occur.  make sure you have enough cooling via fans +/- heatsinks.  try rearranging some h boards.  other than that, rebooting should've worked.

[Inamatus]

My 400GH/s Bitfury rig is not hashing after sudo reboot command

Output of /run/shm/.stat.log after reboot:

1       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
2       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
3       AIfDSo  52      0.000   0.000   0       0       0       0       0      $

Output of /run/shm/.stat.log after a few minutes following reboot:

1       AiFDso  52      0.000   0.000   0       0       0       0       0      $
2       AiFDso  52      0.000   0.000   0       0       0       0       0      $
3       AiFDso  52      0.000   0.000   0       0       0       0       0      $

As you can see, the autotune is turning off the chips.

Please help!

make sure you wait at least a few min for hashing to occur.  make sure you have enough cooling via fans +/- heatsinks.  try rearranging some h boards.  other than that, rebooting should've worked.

Thank you for taking the time to reply.

Couple things to add - Ive had this up and running since December. Ive had the speeds up to 55 (880) but AC kept turning off, so I lowered down to 52 until I got that fixed. The AC was fixed today so I bumped the speeds up to 55 again and proceeded with the reboot.

Logically followed it would imply that I screwed up the best.cnf file or something. This happened once before where I had did a search and replace all of 55 to 52, but forgot to go back and change the chip numbers 55, 155 and 255. Once I fixed this the miner started up fine. Knowing I had done this once before I manually checked all the chip numbers and they are sequentially correct.

Is there any way to make/restore a default best.cnf?

[cypherdoc]

My 400GH/s Bitfury rig is not hashing after sudo reboot command

Output of /run/shm/.stat.log after reboot:

1       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
2       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
3       AIfDSo  52      0.000   0.000   0       0       0       0       0      $

Output of /run/shm/.stat.log after a few minutes following reboot:

1       AiFDso  52      0.000   0.000   0       0       0       0       0      $
2       AiFDso  52      0.000   0.000   0       0       0       0       0      $
3       AiFDso  52      0.000   0.000   0       0       0       0       0      $

As you can see, the autotune is turning off the chips.

Please help!

make sure you wait at least a few min for hashing to occur.  make sure you have enough cooling via fans +/- heatsinks.  try rearranging some h boards.  other than that, rebooting should've worked.

Thank you for taking the time to reply.

Couple things to add - Ive had this up and running since December. Ive had the speeds up to 55 (880) but AC kept turning off, so I lowered down to 52 until I got that fixed. The AC was fixed today so I bumped the speeds up to 55 again and proceeded with the reboot.

Logically followed it would imply that I screwed up the best.cnf file or something. This happened once before where I had did a search and replace all of 55 to 52, but forgot to go back and change the chip numbers 55, 155 and 255. Once I fixed this the miner started up fine. Knowing I had done this once before I manually checked all the chip numbers and they are sequentially correct.

Is there any way to make/restore a default best.cnf?

Create /opt/bitfury/best.cnf like this to run all chips at speed 52 with autotune disabled or to whatever you desire:

Code:

rm /opt/bitfury/best.cnf ; for i in {1..256} ; do echo -e "$i\taIfDSo\t52" >> /opt/bitfury/best.cnf ; done

[Inamatus]

My 400GH/s Bitfury rig is not hashing after sudo reboot command

Output of /run/shm/.stat.log after reboot:

1       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
2       AIfDSo  52      0.000   0.000   0       0       0       0       0      $
3       AIfDSo  52      0.000   0.000   0       0       0       0       0      $

Output of /run/shm/.stat.log after a few minutes following reboot:

1       AiFDso  52      0.000   0.000   0       0       0       0       0      $
2       AiFDso  52      0.000   0.000   0       0       0       0       0      $
3       AiFDso  52      0.000   0.000   0       0       0       0       0      $

As you can see, the autotune is turning off the chips.

Please help!

make sure you wait at least a few min for hashing to occur.  make sure you have enough cooling via fans +/- heatsinks.  try rearranging some h boards.  other than that, rebooting should've worked.

Thank you for taking the time to reply.

Couple things to add - Ive had this up and running since December. Ive had the speeds up to 55 (880) but AC kept turning off, so I lowered down to 52 until I got that fixed. The AC was fixed today so I bumped the speeds up to 55 again and proceeded with the reboot.

Logically followed it would imply that I screwed up the best.cnf file or something. This happened once before where I had did a search and replace all of 55 to 52, but forgot to go back and change the chip numbers 55, 155 and 255. Once I fixed this the miner started up fine. Knowing I had done this once before I manually checked all the chip numbers and they are sequentially correct.

Is there any way to make/restore a default best.cnf?

Create /opt/bitfury/best.cnf like this to run all chips at speed 52 with autotune disabled or to whatever you desire:

Code:

rm /opt/bitfury/best.cnf ; for i in {1..256} ; do echo -e "$i\taIfDSo\t52" >> /opt/bitfury/best.cnf ; done

After I ran the stop-stratumproxy.sh, start-stratumproxy.sh, stop-miner.sh and start-miner.sh scripts it started working. No idea what was wrong.

[cypherdoc]

After I ran the stop-stratumproxy.sh, start-stratumproxy.sh, stop-miner.sh and start-miner.sh scripts it started working. No idea what was wrong.

Welcome to BitFury.

[benny32]

I have gone almost a month at 400+gh and now recently my reported speeds are more like 200-300 at the pool.  Reported rates on the unit itself are in the 300-350 range but they used to be almost 500.  I have applied heatsinks to the backs of the chips and voltage regulater area and this is a climate controlled room with cool air blowing over the cards.  This is the new version hardware as well.  I regularly have cards going to zero, I manually tune them as far as 49 and they work at low rates and another card goes to zero, always at least one card down, sometimes as many as three.  I am using a 1200w power supply as well so it's hard to believe it's because they aren't getting juice. 

Any thoughts?

[cypherdoc]

I have gone almost a month at 400+gh and now recently my reported speeds are more like 200-300 at the pool.  Reported rates on the unit itself are in the 300-350 range but they used to be almost 500.  I have applied heatsinks to the backs of the chips and voltage regulater area and this is a climate controlled room with cool air blowing over the cards.  This is the new version hardware as well.  I regularly have cards going to zero, I manually tune them as far as 49 and they work at low rates and another card goes to zero, always at least one card down, sometimes as many as three.  I am using a 1200w power supply as well so it's hard to believe it's because they aren't getting juice. 

Any thoughts?

this is my experience as well along with several others.

[Keefe]

I have gone almost a month at 400+gh and now recently my reported speeds are more like 200-300 at the pool.  Reported rates on the unit itself are in the 300-350 range but they used to be almost 500.  I have applied heatsinks to the backs of the chips and voltage regulater area and this is a climate controlled room with cool air blowing over the cards.  This is the new version hardware as well.  I regularly have cards going to zero, I manually tune them as far as 49 and they work at low rates and another card goes to zero, always at least one card down, sometimes as many as three.  I am using a 1200w power supply as well so it's hard to believe it's because they aren't getting juice.  

Any thoughts?

If the pool is reporting significantly lower hashrate than the miner, restart the proxies and/or chainminer.

If cards are acting up even at low speeds, power off, reseat all cards, power back on. Alternatively, without powering off, you could just rock the cards side to side and front to back to loosen any oxidation on the contacts without fully pulling them out of the rig. Restart chainminer after this to re-init all chips.

Restart proxies and/or chainminer if all chips are reporting 0GH.

[CCCrypto]

Do you put an 'X' of thermal paste on the back of heatsink, with glue at the four corners? I'd like to do this, but I'm finding conflicting advice online on how much paste to use, and how to apply it.

A small dab behind each chip, and superglue in between.

Sorry if I'm being annoying, but could someone explain how the dab of thermal paste doesn't short the chip connections on the back of the H-board?

I'm new to electrical engineering, and don't want to make a mistake.

EDIT: So far, this is the best explanation I've found. Could someone explain if it's correct? Thanks.

The thermal vias are all attached to the ground plane (I'm guessing it's ground) on the back of the board. Basically, they're all shorted together already.