**US** BitFury Setup Guide

[Swimmer63]

Since your network is 192.168.0.xxx, it may not be liking the xxx.xxx.1.xxx address that's assigned.  

First thing to try, assign it an address of 192.168.0.249, then "sudo reboot" and try to access it at 192.168.0.249 after a minute or two.

Next thing to try, set it up to automatically get an IP address assigned by your router.   Make your interfaces file look like this, and your router should automatically assign it an IP inside your network.  The important lines are bolded.  Note that I have address, network, and broadcast commented out.

auto lo

iface lo inet loopback
iface eth0 inet dhcp
#address 192.168.1.50
netmask 255.255.255.0
#network 192.168.1.0
#broadcast 192.168.1.255
gateway 192.168.0.1

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

Excellent.  Let me give these a try.  Thanks Redacted!

[Swimmer63]

Since your network is 192.168.0.xxx, it may not be liking the xxx.xxx.1.xxx address that's assigned.  

First thing to try, assign it an address of 192.168.0.249, then "sudo reboot" and try to access it at 192.168.0.249 after a minute or two.

Next thing to try, set it up to automatically get an IP address assigned by your router.   Make your interfaces file look like this, and your router should automatically assign it an IP inside your network.  The important lines are bolded.  Note that I have address, network, and broadcast commented out.

auto lo

iface lo inet loopback
iface eth0 inet dhcp
#address 192.168.1.50
netmask 255.255.255.0
#network 192.168.1.0
#broadcast 192.168.1.255
gateway 192.168.0.1

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

Excellent.  Let me give these a try.  Thanks Redacted!

I'm in!  Now to get this guy pointed to the right pool.  Thanks again.  Probably will be back for more help at some point.

[Swimmer63]

Since your network is 192.168.0.xxx, it may not be liking the xxx.xxx.1.xxx address that's assigned.  

First thing to try, assign it an address of 192.168.0.249, then "sudo reboot" and try to access it at 192.168.0.249 after a minute or two.

Next thing to try, set it up to automatically get an IP address assigned by your router.   Make your interfaces file look like this, and your router should automatically assign it an IP inside your network.  The important lines are bolded.  Note that I have address, network, and broadcast commented out.

auto lo

iface lo inet loopback
iface eth0 inet dhcp
#address 192.168.1.50
netmask 255.255.255.0
#network 192.168.1.0
#broadcast 192.168.1.255
gateway 192.168.0.1

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

Excellent.  Let me give these a try.  Thanks Redacted!

I'm in!  Now to get this guy pointed to the right pool.  Thanks again.  Probably will be back for more help at some point.

OK - I'm hashing.  Two boards -one at 19 GH/s and one at 4 GH/s.  Hmmm.  Two under-performing boards and still not quite 25 GH/s.

[Syke]

OK - I'm hashing.  Two boards -one at 19 GH/s and one at 4 GH/s.  Hmmm.  Two under-performing boards and still not quite 25 GH/s.

Post the contents of /run/shm/.stat.log to find out what's going on.

[Swimmer63]

OK - I'm hashing.  Two boards -one at 19 GH/s and one at 4 GH/s.  Hmmm.  Two under-performing boards and still not quite 25 GH/s.

Post the contents of /run/shm/.stat.log to find out what's going on.

I assume I type that into the pi.  I get Permission denied.

[Syke]

OK - I'm hashing.  Two boards -one at 19 GH/s and one at 4 GH/s.  Hmmm.  Two under-performing boards and still not quite 25 GH/s.

Post the contents of /run/shm/.stat.log to find out what's going on.

I assume I type that into the pi.  I get Permission denied.

Type "cat /run/shm/.stat.log" and post the output.

[arorts]

How do I set a fixed share difficulty in the stratum proxy? My miner keeps asking for a higher share difficulty but the pool doesn't seem to increase it and the miner stays mostly idle...

[juhakall]

How do I set a fixed share difficulty in the stratum proxy? My miner keeps asking for a higher share difficulty but the pool doesn't seem to increase it and the miner stays mostly idle...

Use a pool that works around that bug in stratum proxy, or one that allows setting a fixed / minimum difficulty. BTC Guild, Eligius (with minimum diff) or Bitparking should work OK.

[TheOtherGuy]

My EOL card is only hashing on the first two chips. I inspected the board for defects/solder shorts and everything looks ok to me.

Any suggestions to get the other chips running?



1       AIfDSo  55      1.761   1.723   123     4       0       0       163    [0:0]    0       8 7 7 8 8 8 7 6 8 8 8 8 8 8 8 8         0 1 1 0 0 0 1 1 0 0 0 0 0 0 0 0
2       AIfDSo  55      1.632   1.691   114     8       0       0       160    [0:1]    0       8 8 8 8 7 8 5 7 7 6 7 6 7 6 8 8         0 0 0 0 1 0 2 0 0 1 0 1 1 2 0 0
3       AIfDSo  55      1.403   1.691   98      9       0       0       160    [0:2]    36      6 5 5 6 5 6 5 7 7 6 6 7 7 7 6 7         0 1 1 0 1 1 2 0 0 1 1 0 0 0 1 0
4       AIfDSo  55      1.546   1.628   108     6       0       0       154    [0:3]    0       7 7 7 8 7 6 7 7 6 7 7 7 6 7 6 6         0 0 1 0 0 1 0 0 1 0 0 0 1 0 1 1
5       AIfDSo  55      1.417   1.617   99      2       0       0       153    [0:4]    0       6 6 6 5 7 7 6 7 7 7 6 6 6 6 6 5         0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0
6       AIfDSo  55      1.575   1.617   110     8       0       0       153    [0:5]    0       6 8 8 7 7 5 6 6 7 7 7 7 7 8 8 6         2 0 0 0 0 2 1 1 0 0 0 0 0 0 0 2
7       AIfDSo  55      1.446   1.723   101     5       0       0       163    [0:6]    72      7 7 7 6 5 7 7 6 7 7 6 6 5 6 6 6         0 0 0 1 2 0 0 1 0 0 0 0 1 0 0 0
8       AIfDSo  55      1.761   1.765   123     7       0       0       167    [0:7]    0       8 8 8 8 8 7 9 8 6 7 8 7 8 8 8 7         0 0 0 0 0 2 0 0 2 1 0 1 0 0 0 1
9       aIfDSo  52      0.401   1.406   28      40      0       0       133    [0:8]    520     2 3 3 1 1 2 1 2 1 3 1 1 3 0 2 2         2 1 1 3 3 2 4 3 4 2 3 3 1 4 2 2
10      AIfDSo  55      1.503   1.702   105     4       0       0       161    [0:9]    36      7 7 7 7 6 7 7 7 6 5 7 6 6 6 7 7         0 0 0 0 1 0 0 0 1 2 0 0 0 0 0 0
11      AIfDSo  55      1.747   1.681   122     4       0       0       159    [0:A]    0       8 8 8 7 7 8 8 8 7 8 8 7 7 7 8 8         0 0 0 1 1 0 0 0 1 0 0 0 0 1 0 0
12      AIfDSo  55      1.288   1.607   90      6       0       0       152    [0:B]    108     6 6 6 6 5 6 6 6 6 4 5 5 6 6 6 5         0 0 0 0 1 0 0 0 0 2 1 1 0 0 0 1
13      AIfDSo  55      1.875   1.659   131     4       0       0       157    [0:C]    0       8 7 7 8 8 9 9 8 9 9 9 9 7 8 8 8         0 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0
14      AIfDSo  55      1.546   1.649   108     6       0       0       156    [0:D]    0       6 6 6 7 7 7 6 8 6 7 7 7 7 7 7 7         1 1 1 0 0 0 1 0 2 0 0 0 0 0 0 0
15      AIfDSo  55      1.460   1.755   102     5       0       0       166    [0:E]    0       6 5 5 6 6 6 7 7 7 6 6 7 7 7 7 7         1 1 1 0 0 0 0 0 0 1 1 0 0 0 0 0
16      AIfDSo  55      1.603   1.850   112     10      0       0       175    [0:F]    36      7 6 6 5 7 8 8 8 7 8 8 7 7 7 6 7         0 1 1 3 1 0 0 0 1 0 0 1 1 0 1 0
17      AIfDSo  55      2.119   2.029   148     4       0       0       192    [1:0]    0       9 10 10 10 10 10 10 10 8 9 9 8 8 9 9 9  1 0 0 0 0 0 0 0 1 0 0 1 1 0 0 0
18      AIfDSo  55      1.747   2.124   122     8       0       0       201    [1:1]    0       8 8 8 8 8 8 6 7 8 8 8 8 8 7 7 7         0 0 0 1 1 0 2 1 0 0 0 0 0 1 1 1
speed:987 noncerate[GH/s]:27.831 (1.546/chip) hashrate[GH/s]:30.916 good:1944 errors:140 spi-err:0 miso-err:0 jobs:326 cores:94% good:18 bad:0 off:0 (best[GH/s]:29.635) Sun Sep 15 15:21:09 2013
0:      877     23.966  26.762  1674    128     0       0       16      0      0(1.498/chip)    93%
1:      110     3.865   4.154   270     12      0       0       2       0      0(1.933/chip)    100%

[dracore]

Isn't it unusual that chip 9 tends to be the one with problems?

I've seen 3 people with this problem so far

[zurg]

Isn't it unusual that chip 9 tends to be the one with problems?

I've seen 3 people with this problem so far

My 9th is shot also. Can't even bypass it.

[TheOtherGuy]

Maybe it is a repeating problem with the pcb.

[buzzdave]

My EOL card is only hashing on the first two chips. I inspected the board for defects/solder shorts and everything looks ok to me.

Any suggestions to get the other chips running?



1       AIfDSo  55      1.761   1.723   123     4       0       0       163    [0:0]    0       8 7 7 8 8 8 7 6 8 8 8 8 8 8 8 8         0 1 1 0 0 0 1 1 0 0 0 0 0 0 0 0
2       AIfDSo  55      1.632   1.691   114     8       0       0       160    [0:1]    0       8 8 8 8 7 8 5 7 7 6 7 6 7 6 8 8         0 0 0 0 1 0 2 0 0 1 0 1 1 2 0 0
3       AIfDSo  55      1.403   1.691   98      9       0       0       160    [0:2]    36      6 5 5 6 5 6 5 7 7 6 6 7 7 7 6 7         0 1 1 0 1 1 2 0 0 1 1 0 0 0 1 0
4       AIfDSo  55      1.546   1.628   108     6       0       0       154    [0:3]    0       7 7 7 8 7 6 7 7 6 7 7 7 6 7 6 6         0 0 1 0 0 1 0 0 1 0 0 0 1 0 1 1
5       AIfDSo  55      1.417   1.617   99      2       0       0       153    [0:4]    0       6 6 6 5 7 7 6 7 7 7 6 6 6 6 6 5         0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0
6       AIfDSo  55      1.575   1.617   110     8       0       0       153    [0:5]    0       6 8 8 7 7 5 6 6 7 7 7 7 7 8 8 6         2 0 0 0 0 2 1 1 0 0 0 0 0 0 0 2
7       AIfDSo  55      1.446   1.723   101     5       0       0       163    [0:6]    72      7 7 7 6 5 7 7 6 7 7 6 6 5 6 6 6         0 0 0 1 2 0 0 1 0 0 0 0 1 0 0 0
8       AIfDSo  55      1.761   1.765   123     7       0       0       167    [0:7]    0       8 8 8 8 8 7 9 8 6 7 8 7 8 8 8 7         0 0 0 0 0 2 0 0 2 1 0 1 0 0 0 1
9       aIfDSo  52      0.401   1.406   28      40      0       0       133    [0:8]    520     2 3 3 1 1 2 1 2 1 3 1 1 3 0 2 2         2 1 1 3 3 2 4 3 4 2 3 3 1 4 2 2
10      AIfDSo  55      1.503   1.702   105     4       0       0       161    [0:9]    36      7 7 7 7 6 7 7 7 6 5 7 6 6 6 7 7         0 0 0 0 1 0 0 0 1 2 0 0 0 0 0 0
11      AIfDSo  55      1.747   1.681   122     4       0       0       159    [0:A]    0       8 8 8 7 7 8 8 8 7 8 8 7 7 7 8 8         0 0 0 1 1 0 0 0 1 0 0 0 0 1 0 0
12      AIfDSo  55      1.288   1.607   90      6       0       0       152    [0:B]    108     6 6 6 6 5 6 6 6 6 4 5 5 6 6 6 5         0 0 0 0 1 0 0 0 0 2 1 1 0 0 0 1
13      AIfDSo  55      1.875   1.659   131     4       0       0       157    [0:C]    0       8 7 7 8 8 9 9 8 9 9 9 9 7 8 8 8         0 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0
14      AIfDSo  55      1.546   1.649   108     6       0       0       156    [0:D]    0       6 6 6 7 7 7 6 8 6 7 7 7 7 7 7 7         1 1 1 0 0 0 1 0 2 0 0 0 0 0 0 0
15      AIfDSo  55      1.460   1.755   102     5       0       0       166    [0:E]    0       6 5 5 6 6 6 7 7 7 6 6 7 7 7 7 7         1 1 1 0 0 0 0 0 0 1 1 0 0 0 0 0
16      AIfDSo  55      1.603   1.850   112     10      0       0       175    [0:F]    36      7 6 6 5 7 8 8 8 7 8 8 7 7 7 6 7         0 1 1 3 1 0 0 0 1 0 0 1 1 0 1 0
17      AIfDSo  55      2.119   2.029   148     4       0       0       192    [1:0]    0       9 10 10 10 10 10 10 10 8 9 9 8 8 9 9 9  1 0 0 0 0 0 0 0 1 0 0 1 1 0 0 0
18      AIfDSo  55      1.747   2.124   122     8       0       0       201    [1:1]    0       8 8 8 8 8 8 6 7 8 8 8 8 8 7 7 7         0 0 0 1 1 0 2 1 0 0 0 0 0 1 1 1
speed:987 noncerate[GH/s]:27.831 (1.546/chip) hashrate[GH/s]:30.916 good:1944 errors:140 spi-err:0 miso-err:0 jobs:326 cores:94% good:18 bad:0 off:0 (best[GH/s]:29.635) Sun Sep 15 15:21:09 2013
0:      877     23.966  26.762  1674    128     0       0       16      0      0(1.498/chip)    93%
1:      110     3.865   4.154   270     12      0       0       2       0      0(1.933/chip)    100%

You can try bypassing it.  I've also seen some chip tuning that actually allows the chip to work again:
navigate to /run/shm/
edit .chip-cnf
change 55 to 53 for the last chip in the config
save .chip-cnf as .chip.cnf

*tuning may not persist - don't restart the miner. 

We are working a lot of good UI to allow for troubleshooting and tuning options.

If it doesn't work, the chip is actually broken and can't pass spi under any conditions.

Tune chips to different values at your peril - please don't try other values it can damage your boards!

[TheOtherGuy]

You can try bypassing it.  I've also seen some chip tuning that actually allows the chip to work again:
navigate to /run/shm/
edit .chip-cnf
change 55 to 53 for the last chip in the config
save .chip-cnf as .chip.cnf

*tuning may not persist - don't restart the miner. 

We are working a lot of good UI to allow for troubleshooting and tuning options.

If it doesn't work, the chip is actually broken and can't pass spi under any conditions.

Tune chips to different values at your peril - please don't try other values it can damage your boards!

Editing the .chip.cnf didn't change anything.

When you say to bypass it, do you mean physically? If so, how is that done. Have any links?

[bitrocket]

Guys I received my Aug full kit a few days ago and have been troubleshooting it ever since. It was DOA out of the box due to networking issues (the Gateway IP was set to something like 10.10.2.1). After that was corrected it wouldn't respond on the web server port for some reason. I bought a new router and set it up on it's own isolated network and hooked the raspberry pi directly up to a keyboard and monitor to get that resolved.

The unit has been hashing for two days now but having stability issues. On power up everything starts out at full speed but then it loses hash rate over time. I have optimized the cards by putting the highest rate cards in the first few slots and the worst performing cards at the end. One card stopped hashing completely and was removed.



I have tried two different pools and tried adjusting the difficulty at the pool. It's currently on BTCguild with a difficulty setting of 512. The unit is directly in front of an air conditioner with good air flow across all cards. It's powered by a 760W platinum power supply. None of my other ASIC rigs have this kind of fluctuation in hash rate.

To date this 400Ghash unit has mined less than one bitcoin. Please let me know the next step for troubleshooting.

[dracore]

Guys I received my Aug full kit a few days ago and have been troubleshooting it ever since. It was DOA out of the box due to networking issues (the Gateway IP was set to something like 10.10.2.1). After that was corrected it wouldn't respond on the web server port for some reason. I bought a new router and set it up on it's own isolated network and hooked the raspberry pi directly up to a keyboard and monitor to get that resolved.

The unit has been hashing for two days now but having stability issues. On power up everything starts out at full speed but then it loses hash rate over time. I have optimized the cards by putting the highest rate cards in the first few slots and the worst performing cards at the end. One card stopped hashing completely and was removed.

My board stop hashing about 2 days or so.  All chips show up as 0.000 in my stat logs and will remain in that state for a long long time (if not indefinitely).  So the only thing I do now is power cycle the whole unit.  It seems to recover afterwards for another 2.x days

[spiccioli]

Guys,

you can start from here:

https://bitcointalk.org/index.php?topic=287590.msg3079405#msg3079405

Remove air conditioner though, chips like to be warm

spiccioli

[klondike_bar]

Guys I received my Aug full kit a few days ago and have been troubleshooting it ever since. It was DOA out of the box due to networking issues (the Gateway IP was set to something like 10.10.2.1). After that was corrected it wouldn't respond on the web server port for some reason. I bought a new router and set it up on it's own isolated network and hooked the raspberry pi directly up to a keyboard and monitor to get that resolved.

The unit has been hashing for two days now but having stability issues. On power up everything starts out at full speed but then it loses hash rate over time. I have optimized the cards by putting the highest rate cards in the first few slots and the worst performing cards at the end. One card stopped hashing completely and was removed.

I have tried two different pools and tried adjusting the difficulty at the pool. It's currently on BTCguild with a difficulty setting of 512. The unit is directly in front of an air conditioner with good air flow across all cards. It's powered by a 760W platinum power supply. None of my other ASIC rigs have this kind of fluctuation in hash rate.

To date this 400Ghash unit has mined less than one bitcoin. Please let me know the next step for troubleshooting.

I'm under the impression that a dificulty of 256 might be more in line with a 400Ghash unit. How were you cooling it, and any mods (pencil mod included)?

[-Redacted-]

Guys I received my Aug full kit a few days ago and have been troubleshooting it ever since. It was DOA out of the box due to networking issues (the Gateway IP was set to something like 10.10.2.1). After that was corrected it wouldn't respond on the web server port for some reason. I bought a new router and set it up on it's own isolated network and hooked the raspberry pi directly up to a keyboard and monitor to get that resolved.

The unit has been hashing for two days now but having stability issues. On power up everything starts out at full speed but then it loses hash rate over time. I have optimized the cards by putting the highest rate cards in the first few slots and the worst performing cards at the end. One card stopped hashing completely and was removed.

My board stop hashing about 2 days or so.  All chips show up as 0.000 in my stat logs and will remain in that state for a long long time (if not indefinitely).  So the only thing I do now is power cycle the whole unit.  It seems to recover afterwards for another 2.x days

https://bitcointalk.org/index.php?topic=250249.msg3171841;topicseen#msg3171841

I personally use /30 - restarting the proxies every ten minutes seems a little excessive.

[americandesi]

I just posted dropbox links to the V1 & V2 rPi images and chainminer code if you guys need to remake your SD Cards.  Please be sure to use the correct image - especially make sure not to use the V2 image or chainminer code on a V1 board!

Check the OP for the support thread I posted (see my sig for link).

The M-boards we shipped out today are all V2, so remember that these boards use 4 distinct SPI channels.  If you have 4 hashing cards, you can load them in the slot 1 of each bank for best results.

Also be sure to use two separate PCI-e cables from your PSU to the plugs on the M-board.  Using one cable that has two plugs will just put extra load on that cable, possibly dangerous as you increase H-cards.

Tracking numbers should have come to you via email (when FedEx label was printed).  If not, I'll check with the shipping team to see whats up.

With regards to Dave's message above. If i have 2 EOL boards, does anyone know if i can connect them to the same M-board in separate SPI channels / banks.
Will that work.?