**US** BitFury Setup Guide

[woobone]

Ok, something funky is going on.....

This is normal stats from BF:
{ "stats":
 {"speed": 1320, "noncerate": 46.071, "noncerateperchip":1.843, "hashrate":48.842, "good":3218, "errors":174, "spi-errors":0, "miso-errors":0, "jobs":297, "record":47.746
,"boards": [
{ "slot": "0", "speed": 880, "noncerate":29.592, "hashrate": 31.624, "good": 2067, "errors": 122, "spi-errors": 0, "miso-errors":0 }
,
{ "slot": "1", "speed": 440, "noncerate":16.478, "hashrate": 17.218, "good": 1151, "errors": 52, "spi-errors": 0, "miso-errors":0 }

 ]
 } }

This is my stats from BitMinter:
4th column is my actual hashrate. (somehow the 10Gh/s difference is MIA somewhere?)

18196   2013-09-22 18:07    1h 28m   36,551.384   112,628,548   0.00049664   0.40054681   55,936   45,113,006
18195   2013-09-22 16:39    1h 28m   36,580.303   112,628,548   0.00049721   0.40192240   56,000   45,267,937
18194   2013-09-22 15:10    1h 29m   35,940.086   112,628,548   0.00047107   0.40053465   53,056   45,111,636
18193   2013-09-22 13:39    1h 30m   35,626.368   112,628,548   0.00052108   0.40027895   58,688   45,082,837
18192   2013-09-22 12:08    1h 31m   35,453.413   112,628,548   0.00048300   0.40060774   54,400   45,119,868
18191   2013-09-22 10:37    1h 31m   35,342.286   112,628,548   0.00053699   0.40147082   60,480   45,217,076
18190   2013-09-22 09:05    1h 31m   35,269.357   112,628,548   0.00050403   0.40086111   56,768   45,148,405
18189   2013-09-22 07:33    1h 30m   35,870.429   112,628,548   0.00054721   0.40079650   61,632   45,141,128
18188   2013-09-22 06:02    1h 31m   35,241.676   112,628,548   0.00050744   0.40032794   57,152   45,088,355
18187   2013-09-22 04:30    1h 31m   35,277.083   112,628,548   0.00054324   0.40073015   61,184   45,133,655
18186   2013-09-22 02:58    1h 32m   35,173.704   112,628,548   0.00051653   0.40173719   58,176   45,247,077
18185   2013-09-22 01:26    1h 31m   35,298.837   112,628,548   0.00048869   0.40105023   55,040   45,169,705
18184   2013-09-21 23:54    1h 31m   35,264.687   112,628,548   0.00050232   0.40073514   56,576   45,134,217
18182   2013-09-21 22:22    1h 30m   35,876.132   112,628,548   0.00050289   0.40086022   56,640   45,148,305
18181   2013-09-21 20:52    1h 30m   35,812.913   112,628,548   0.00047334   0.40067208   53,312   45,127,115
18180   2013-09-21 19:21    1h 29m   36,233.704   112,628,548   0.00045857   0.40043621   51,648   45,100,549

hey zurg the 4th column are total hashrate not your hashrate .

[zurg]

Ok, something funky is going on.....

This is normal stats from BF:
{ "stats":
 {"speed": 1320, "noncerate": 46.071, "noncerateperchip":1.843, "hashrate":48.842, "good":3218, "errors":174, "spi-errors":0, "miso-errors":0, "jobs":297, "record":47.746
,"boards": [
{ "slot": "0", "speed": 880, "noncerate":29.592, "hashrate": 31.624, "good": 2067, "errors": 122, "spi-errors": 0, "miso-errors":0 }
,
{ "slot": "1", "speed": 440, "noncerate":16.478, "hashrate": 17.218, "good": 1151, "errors": 52, "spi-errors": 0, "miso-errors":0 }

 ]
 } }

This is my stats from BitMinter:
4th column is my actual hashrate. (somehow the 10Gh/s difference is MIA somewhere?)

18196   2013-09-22 18:07    1h 28m   36,551.384   112,628,548   0.00049664   0.40054681   55,936   45,113,006

hey zurg the 4th column are total hashrate not your hashrate .

Err, opps...
Well, I have bigger problems now, lol

Just checked my hashrate and it took a dive again..
logged SSH

15      AIfDSo  55      2.004   1.998   140     2       0       0       189     [0:E]   52      9 9 9 9 9 9 9 9 9 9 8 8 8 9 8 9         0 0 0 $
16      AIfDSo  55      1.818   2.008   127     4       0       0       190     [0:F]   43      8 8 8 8 8 8 9 7 8 8 8 7 8 8 8 8         0 0 0 $
17      AiFDso  55      0.000   0.159   0       330     14      351     15      [1:0]   695     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         22 20 $
18      AiFDso  55      0.000   0.814   0       996     84      20      77      [1:1]   754     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         20 22 $
19      AiFDso  55      0.000   0.074   0       111     8       109     7       [1:2]   755     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         5 5 7 $


Looks like my chip 17 took a dump. Maybe my EOL card is 100% dead now instead of 50%.
Guess I'll wait to mess with it until I get to work tomorrow.
20Gh/s overnight is way better then 0 if the SD card is popping errors again.

[klondike_bar]

Ok, something funky is going on.....

This is normal stats from BF:
{ "stats":
 {"speed": 1320, "noncerate": 46.071, "noncerateperchip":1.843, "hashrate":48.842, "good":3218, "errors":174, "spi-errors":0, "miso-errors":0, "jobs":297, "record":47.746
,"boards": [
{ "slot": "0", "speed": 880, "noncerate":29.592, "hashrate": 31.624, "good": 2067, "errors": 122, "spi-errors": 0, "miso-errors":0 }
,
{ "slot": "1", "speed": 440, "noncerate":16.478, "hashrate": 17.218, "good": 1151, "errors": 52, "spi-errors": 0, "miso-errors":0 }

 ]
 } }

This is my stats from BitMinter:
4th column is my actual hashrate. (somehow the 10Gh/s difference is MIA somewhere?)

18196   2013-09-22 18:07    1h 28m   36,551.384   112,628,548   0.00049664   0.40054681   55,936   45,113,006

hey zurg the 4th column are total hashrate not your hashrate .

Err, opps...
Well, I have bigger problems now, lol

Just checked my hashrate and it took a dive again..
logged SSH

15      AIfDSo  55      2.004   1.998   140     2       0       0       189     [0:E]   52      9 9 9 9 9 9 9 9 9 9 8 8 8 9 8 9         0 0 0 $
16      AIfDSo  55      1.818   2.008   127     4       0       0       190     [0:F]   43      8 8 8 8 8 8 9 7 8 8 8 7 8 8 8 8         0 0 0 $
17      AiFDso  55      0.000   0.159   0       330     14      351     15      [1:0]   695     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         22 20 $
18      AiFDso  55      0.000   0.814   0       996     84      20      77      [1:1]   754     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         20 22 $
19      AiFDso  55      0.000   0.074   0       111     8       109     7       [1:2]   755     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         5 5 7 $


Looks like my chip 17 took a dump. Maybe my EOL card is 100% dead now instead of 50%.
Guess I'll wait to mess with it until I get to work tomorrow.
20Gh/s overnight is way better then 0 if the SD card is popping errors again.

use the webgui to stop and start the miner. sometimes that throws a 'stalled' chip back into gear. I sometimes find my unit running only 15 chips, and this fixes it

[zurg]

Ok, got to work.
Tried to reboot the Pi and as expected the whole thing crashed out. Bad SD card.
I bought 2 8GB Class 10 cards from Microcenter.
Loaded one up and WOW the response is so much quicker!
Back up hashing now no miso errors.

Actually... there has always been that 1 miso error on chip 1, but it doesn't appear to propagate to the rest and eventually disappears when I pull logs.

Yay

[klondike_bar]

What exactly are the miso errors? I usually get 3-5 of them in my stat.log file, and have seen a single chip stop hashing from time to time. Is it related to voltage mod, or something inherent to the board? Hash rate stays fairly stable.

Also, i ran the RPI's 'sudo shutdown' command to turn off the unit (previously I just powered off the psu), and on restart am unable to ssh to the pi. (I enter user, enter password, then get "server unexpectedly closed network connection" from the putty program). Did my shutdown method alter the ssh file or settings? The bitfury Web guide and bit miner both show normal hashing

[zurg]

What exactly are the miso errors? I usually get 3-5 of them in my stat.log file, and have seen a single chip stop hashing from time to time. Is it related to voltage mod, or something inherent to the board? Hash rate stays fairly stable.

Also, i ran the RPI's 'sudo shutdown' command to turn off the unit (previously I just powered off the psu), and on restart am unable to ssh to the pi. (I enter user, enter password, then get "server unexpectedly closed network connection" from the putty program). Did my shutdown method alter the ssh file or settings? The bitfury Web guide and bit miner both show normal hashing

Few are ok., last night I had like 400 on 1 chip and then it propagated to a 2nd onee at like 3XX some.. it rendered my 2nd card useless until I rebooted today.

[cet]

What exactly are the miso errors? I usually get 3-5 of them in my stat.log file, and have seen a single chip stop hashing from time to time. Is it related to voltage mod, or something inherent to the board? Hash rate stays fairly stable.

Also, i ran the RPI's 'sudo shutdown' command to turn off the unit (previously I just powered off the psu), and on restart am unable to ssh to the pi. (I enter user, enter password, then get "server unexpectedly closed network connection" from the putty program). Did my shutdown method alter the ssh file or settings? The bitfury Web guide and bit miner both show normal hashing

miso = master in, slave out.  It doesn't take many of these types of errors before it causes the whole h-board to auto tune down to next to nothing.  The problem is that the error tends to spread from one bad chip to all other chips.  So far I've been lucky and located the correct chip the first try but it's possible that it might take multiple attempts at shutting down different chips to correct the problem.  I don't think this type of error is normally resolved by slowing the clock.  rebooting can solve it for a short while (half hour or so from what I've seen) but it quickly starts happening again.

I suspect that your other problem with logging into the rPI was a timing issue, it takes a little longer for the rPI to respond to login attempts than it does for the rPI to bring up the built in website.

/cet

[klondike_bar]

^i could ssh fine until I used the shutdown command rather than a forced power off.

[cet]

^i could ssh fine until I used the shutdown command rather than a forced power off.

after a shutdown command you will need to recycle the power before it will come back up.

/cet

[klondike_bar]

^i could ssh fine until I used the shutdown command rather than a forced power off.

after a shutdown command you will need to recycle the power before it will come back up.

/cet

I've power cycled with psu shutoff, and used the stop/start miner a few times, and still no ssh ability. I could redo the sd card but I'd rather avoid the work and downtime, especially when I'm hashing around 32-33ghash average which I'm happy with until I get more heat sink or an 80mm fan that should arrive soon.

Has anyone tried or looked into replacing the 30a voltage converter? I don't have the skill and tools to replace it myself but an uriius whether anyone has done this to enable overclocking past 35ghash reliably. (I could get to 37ghash but errors increased and id see a [random] chip drop to 0 hashing, which I attribute to either the higher heat or strain on the voltage converter/regulator - noncerate was closer to 34.5ghash)

Main reason I want to ssh is to monitor whether all 16 are running, or if my current hash rate is from 15 chips, since that will help guide me as I tweak the resistance (1.165 was the problematic 32-37ghash range, 1.178 is quite stable between 31-34ghash)

[-Redacted-]

I'd suggest a keyboard and monitor to see what's going on.   If ssh somehow got disabled, you can run sudo raspi-config to turn it back on.  Doesn't make sense that a shutdown would disable it where a power-off wouldn't.  Something very odd there...

[mo_mo]

i just got my shipment today, with the v2 board, there are no cables , do I need anything extra to assemble this.
kind of clueless where to start.

[mo_mo]

what do i use to power rasp pi

[Trongersoll]

what do i use to power rasp pi

I believe that the motherboard powers the Pi.

[Morblias]

i just got my shipment today, with the v2 board, there are no cables , do I need anything extra to assemble this.
kind of clueless where to start.

Need a PSU with 2 PCI-E connectors to connect to M-board. The RPi plugs into M-board and gets its power from that.

[xstr8guy]

i just got my shipment today, with the v2 board, there are no cables , do I need anything extra to assemble this.
kind of clueless where to start.

Sorry to state the obvious but check your box very carefully.  You should have two connectors in the box.  If not you'll have to create your own or wait for Dave to ship you some.

Oh wait, that was August ver. 1 M boards.  For ver. 2, I think you just need PCI-e connectors that come with your PSU.

[klondike_bar]

i just got my shipment today, with the v2 board, there are no cables , do I need anything extra to assemble this.
kind of clueless where to start.

Need a PSU with 2 PCI-E connectors to connect to M-board. The RPi plugs into M-board and gets its power from that.

This. Once the hardware is connected up, you need to change the default ip thats on the SD card. You can do this via a linux workstation. (I used ubuntu, using the terminal to move to the directory for my sd card (marked as 3.7gb filesystem, with its name being a long hexstring, and:

sudo sed -i 's/10.10.11.249/192.168.1.249/' etc/network/interfaces
sudo sed -i 's/255.0.0.0/255.255.255.0/' etc/network/interfaces
sudo sed -i 's/10.1.1.1/192.168.1.1/' etc/network/interfaces

and you should be able to throw the card in your system, power it on (turn on PSU), and find the webgui at 192.168.1.249 (you may change if using a different ip range)

[mo_mo]

thanks, now i plugged in the rasp pi but it's not hanging down like the images i saw.
what do I do when I see"bitfury login"

[xstr8guy]

thanks, now i plugged in the rasp pi but it's not hanging down like the images i saw.
what do I do when I see"bitfury login"

You need to firmly grasp the rPi and yank it forcefully downward until it matches the photo exactly.  NO... just kidding, don't do that!

But seriously, start at the beginning of this thread and READ!  Dave posted step-by-step instructions.

[Morblias]

thanks, now i plugged in the rasp pi but it's not hanging down like the images i saw.
what do I do when I see"bitfury login"

login: pi
password: raspberry

I believe it then asks what IP you want to use. After you set that IP, on your browser (on another computer) go to that IP to set the pools and such then hit start mining.