**US** BitFury Setup Guide

[-Redacted-]

You can't use http:// or stratum+tcp:// at the beginning of hostnames.   Also, it doesn't like 8332 (for eclipsemc.com, for example) as a port number - use 3333 instead.

[Morblias]

You can't use http:// or stratum+tcp:// at the beginning of hostnames...

Hmmm, my other cgminers have those in them as full path. without using stratum+tcp:// it doesn't seem like it is submitting shares to the pool I am using. My hashrate shows fine on the pool, but still has 0 accepted shares. Maybe it just takes a while before the pool updates, I will let it go for an hour or so.

[-Redacted-]

Yes, cgminer wants the http:// or stratum+tcp:// in front of the hostname.  Chainminer isn't cgminer, and it doesn't work if you use them.

[Morblias]

Yes, cgminer wants the http:// or stratum+tcp:// in front of the hostname.  Chainminer isn't cgminer, and it doesn't work if you use them.

Ok thanks, I will wait a while and see if the pool just needs time to update. Also, is there anyway in SSH to show the chainminer screen (like in minepeon screen -r to show the cgminer screen)? I tried the screen -r which comes up with no screen to attach, and am not sure if it's possible to show it or not. It would be nice to see what is going on with my miner in SSH

[-Redacted-]

Yes, but not so easy.  The screen is attached to root.  You'll see a selection of available screens using "sudo screen -r", and can reattach to them using "sudo screen -r <proc_number>".  Three of them are the stratum proxies,  none of them show much of anything interesting real-time, unfortunately.  The fourth shows some info about each chip as it gets programmed.

[Morblias]

Yes, but not so easy.  The screen is attached to root.  You'll see a selection of available screens using "sudo screen -r", and can reattach to them using "sudo screen -r <proc_number>".   None of them show anything interesting real-time, unfortunately.

Awesome! Thank you again. I got a screen open which shows the pool is accepting shares so I am all good. Just need the pool to update

[-Redacted-]

If you have a noncerate showing near at the top of the Bitfury admin page, you can be pretty sure that you're getting work and submitting shares.  I submit to BTCGuild and have each of the three admin pool entries using a different worker number...

[Swimmer63]

Double check the "address" entry in that file again, and/or check your router for the ip address.  If you successfully changed the gateway, it may have been assigned a different IP address.  On the Pi, you should be able to enter the ifconfig command and see a display like this that shows its IP:

pi@bitfury ~ $ ifconfig
eth0     Link encap:Ethernet  HWaddr b8:27:eb:9c:49:63
          inet addr:192.168.2.7  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:263752 errors:0 dropped:1 overruns:0 frame:0
          TX packets:397420 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:37925441 (36.1 MiB)  TX bytes:52238648 (49.8 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:30462510 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30462510 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4767221528 (4.4 GiB)  TX bytes:4767221528 (4.4 GiB)

I get an error trying to do iconfig.  But I put in the code line that Dave had us do to correct the gateway and it lists:
Address 192.168.1.249
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.0.1

I think this means it did not change it??

[-Redacted-]

It's "ifconfig".  On a windows machine on your network, go to a command prompt and type "ipconfig".  You'll see an entry for the correct gateway in what that command lists:

...

   Link-local IPv6 Address . . . . . : fe80::4072:c744:ac4e
   IPv4 Address. . . . . . . . . . . : 192.168.2.3
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1


It might be set to something other than 192.168.0.1, like mine is (my gateway is 192.168.2.1).

[Morblias]

1 more noob question, is there a command to check the chip temps? or is that in some log file somewhere?

[-Redacted-]

No.  There are no temperature sensors on these boards.

[zurg]

OK,  after much monitoring and troubleshooting I am thinking that my hashrate drop at Slushs's pool occurs about every 6 hours or so.
The only way to bring it back up is stopping the miner and restarting it.

Any way I can make it auto restart every 2 hours?

[superduh]

OK,  after much monitoring and troubleshooting I am thinking that my hashrate drop at Slushs's pool occurs about every 6 hours or so.
The only way to bring it back up is stopping the miner and restarting it.

Any way I can make it auto restart every 2 hours?

just switch to btcguild - heh

[Swimmer63]

It's "ifconfig".  On a windows machine on your network, go to a command prompt and type "ipconfig".  You'll see an entry for the correct gateway in what that command lists:

...

   Link-local IPv6 Address . . . . . : fe80::4072:c744:ac4e
   IPv4 Address. . . . . . . . . . . : 192.168.2.3
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1


It might be set to something other than 192.168.0.1, like mine is (my gateway is 192.168.2.1).

I'm away from my miner now, but I did do this and got the same gateway.  So I know that is correct. Tomorrow I will run ifconfig on the pi and check that and report.

[xstr8guy]

One of the units dropped to half speed overnight. When I hit the stop mining button and then the start button it seems to be recovering although its ramping up really slowly. Any thoughts as to what that could be about?

Almost something similar to what I was experiencing with Slash's pool yesterday. Not sure what happened.

I guess Slash has given up the guitar then?  Or did you mean Slush?   

[dracore]

My chips are acting weird again.  Anyone have ideas what is going on?

root@bitfury:/opt/bitfury# cat /run/shm/.stat.log
1       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:0]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
2       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:1]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
3       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:2]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
4       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:3]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
5       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:4]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
6       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:5]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
7       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:6]   36      0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
8       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:7]   36      0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
9       AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:8]   398     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
10      AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:9]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
11      AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:A]   36      0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
12      AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:B]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
13      AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:C]   36      0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
14      AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:D]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
15      AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:E]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
16      AIfDSo  55      0.000   0.000   0       0       0       0       0       [0:F]   0       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0         0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0        speed->0
speed:880 noncerate[GH/s]:0.000 (0.000/chip) hashrate[GH/s]:0.000 good:0 errors:0 spi-err:0 miso-err:0 jobs:326 cores:96% good:16 bad:0 off:0 (best[GH/s]:27.803) Thu Sep 12 06:11:21 2013
0:      880     0.000   0.000   0       0       0       0       16      0       0       (0.000/chip)    96%

[spiccioli]

OK,  after much monitoring and troubleshooting I am thinking that my hashrate drop at Slushs's pool occurs about every 6 hours or so.
The only way to bring it back up is stopping the miner and restarting it.

Any way I can make it auto restart every 2 hours?

just switch to btcguild - heh

just swith to HHTT - heh

spiccioli

[spiccioli]

I had a bunch of issues with mine when I first set them up due to fans. They caused the boards to vibrate slightly and that killed my hashrate.

I moved the fan a LOT further away where they just keep the air moving around the cards. Now there's no problem.

You might be seeing a similar issue depending on your setup.

Ha!

I thought this could be the reason, vibration induced by the flow, so I removed my fans from Spotswood case.

I'll try to have them reversed, so that they suck up air through the cards instead of pushing it, this should cause less vibrations.

We'll see.

spiccioli

Or you could put a bit more downward pressure onto the top edges of the h-boards by "raising" the rig a millimeter or two, by putting washers underneath each spacer (between the extrusion and the spacer).

Yes, this is another options,

but after I reversed the fans and let it run for nearly a day I did not see any difference in speed.

I'm not pencil modding it yet, but it seems that at around 25 C ambient temp you can run it without fans.

spiccioli

ps. you can also lower the bar that holds card stoppers (I don't know how to call them ) putting a washer or two between the bar and the extrusion.

[zurg]

One of the units dropped to half speed overnight. When I hit the stop mining button and then the start button it seems to be recovering although its ramping up really slowly. Any thoughts as to what that could be about?

Almost something similar to what I was experiencing with Slash's pool yesterday. Not sure what happened.

I guess Slash has given up the guitar then?  Or did you mean Slush?   

lol...
late night..

but in the other news after threatening my kit with a non stop reboots.., it's been rock solid overnight at 37gh/s, it jumped up an down a lot more before, lol

[btc4life]

When I first setup my full rig last night I noticed that only cards 1-6 were working with number 6 only running at 10 GH/s.    After noticing this I swapped the slow card to the last slot and and the rest of the cards starting working.
This appears to be an EOL card but it was not labeled as one.   I assumed that the full rigs would receive 16 fully functional cards or another mboard and hash cards to make up the difference.   Am I correct on this?

Looking through the logs it looks like chips 250-256 aren't showing up which would explain the slow card.    Anyone else experiencing a similar situation with a full rig?