**US** BitFury Setup Guide

[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?

[dacman61]

Ok, I am about had it with Slashe's constant weird fluctuations.
Trying to setup Bitminter pool,.. but I just cant seem to figure it out.

2. Enabled (1 or 0), Pool address, port, user, password
Yes mint.bitminter.com 8332 workername_BF password

But when I fire that off just by itself Hashrate drops to 0 so I know it's not connecting.

Am I missing something?

Chainminer doesn't always like ports that aren't 3333.  It specifically doesn't like port 8332.  Change that to 3333 and it should work for you.

I got nothing.
Even tried port forwarding in the firewall...

Zurg,

For BitMinter for your username, make sure you type in your username as "username_workname"

Ex. dacman61_dacman61worker

I had the same problem as you...

Also I was using port 8332

[zurg]

Ok, I am about had it with Slashe's constant weird fluctuations.
Trying to setup Bitminter pool,.. but I just cant seem to figure it out.

2. Enabled (1 or 0), Pool address, port, user, password
Yes mint.bitminter.com 8332 workername_BF password

But when I fire that off just by itself Hashrate drops to 0 so I know it's not connecting.

Am I missing something?

Chainminer doesn't always like ports that aren't 3333.  It specifically doesn't like port 8332.  Change that to 3333 and it should work for you.

I got nothing.
Even tried port forwarding in the firewall...

Zurg,

For BitMinter for your username, make sure you type in your username as "username_workname"

Ex. dacman61_dacman61worker

I had the same problem as you...

Also I was using port 8332

Yeah, their instructions are not very clear. lol
I actually got ahold of the owner on IRC and we had it rolling shortly.
I did go back to Slush's pool for a bit now as it seems to be giving me the best bang for the hashrate. 8min, 9min per block.
So far in the fiasco I lost about 1/2 of mining or so..

At 1.6097 BTC at 1week and 20 hours.

[zurg]

Ok, today for some weird reason running nano /run/shm/.stat.log through SSH is reporting 240 chips, to bad after 25 they are all at 0, lol
Where before it would stop at 25.
I didn't reboot my Pi either.. go figure, lol.


Dave, I think my invisible boards past 2nd one are defective, please send new, lmao.

[jspielberg]

For what it is worth, my soldering attempts to jumper the "problem" chips and revive the rest of the board was unsuccessful. I have de-soldered the jumpers and I am back where I started.  I will probably need to cut the leads, which I am unlikely to do until more of my pre-orders start showing up.  Right now this board represents a large percent of my total hashing power.

[zurg]

For what it is worth, my soldering attempts to jumper the "problem" chips and revive the rest of the board was unsuccessful. I have de-soldered the jumpers and I am back where I started.  I will probably need to cut the leads, which I am unlikely to do until more of my pre-orders start showing up.  Right now this board represents a large percent of my total hashing power.

Ahh, quit being a wuss and cut it. lol

just kidding.

[dacman61]

Guys heads up on pencil mod for overvolting and thus aiding overclocking.
Use pencil mod on R2F, make it around 1.1 - 1.2K, voltage goes from 0.66V to 0.81V. The default value is ~1.3K. It may blow the 30AFuse if you go too high; so make sure you do it only if you have a soldering station handy

After Mod (I have only 3 H cards )

Code:

Bank 1
1: 30.781GH/s
2: 33.315GH/s
3: 30.022GH/s
4: 0GH/s

Do you know where you can find some good instructions for this "pencil mod"?

Thanks!

[juhakall]

Guys heads up on pencil mod for overvolting and thus aiding overclocking.
Use pencil mod on R2F, make it around 1.1 - 1.2K, voltage goes from 0.66V to 0.81V. The default value is ~1.3K. It may blow the 30AFuse if you go too high; so make sure you do it only if you have a soldering station handy

After Mod (I have only 3 H cards )

Code:

Bank 1
1: 30.781GH/s
2: 33.315GH/s
3: 30.022GH/s
4: 0GH/s

Do you know where you can find some good instructions for this "pencil mod"?

Thanks!

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

[Swimmer63]

Could use some help.  Unable to access the pi from a browser.  I believe I have corrected the default gateway address to our networks.  But when I try to pull up 192.168.1.249 in a browser I can't get in.  Says "Oops! Google Chrome could not connect to 192.168.1.249"
Miner appears to working.  Chips are hot.  Here are some screen shots.
 https://i.imgur.com/3rokbmB.jpg
https://i.imgur.com/cVDuT7g.jpg
Suggestions would be appreciated.

[mdbssm]

Could use some help.  Unable to access the pi from a browser.  I believe I have corrected the default gateway address to our networks.  But when I try to pull up 192.168.1.249 in a browser I can't get in.  Says "Oops! Google Chrome could not connect to 192.168.1.249"
Miner appears to working.  Chips are hot.  Here are some screen shots.
 https://i.imgur.com/3rokbmB.jpg
https://i.imgur.com/cVDuT7g.jpg
Suggestions would be appreciated.

Connect a screen to the HDMI port, and a USB keyboard and manually setup the network parameters.

My second rig came with 10.0.0.x addressing, not 192.x.x.x.

[Swimmer63]

Could use some help.  Unable to access the pi from a browser.  I believe I have corrected the default gateway address to our networks.  But when I try to pull up 192.168.1.249 in a browser I can't get in.  Says "Oops! Google Chrome could not connect to 192.168.1.249"
Miner appears to working.  Chips are hot.  Here are some screen shots.
 https://i.imgur.com/3rokbmB.jpg
https://i.imgur.com/cVDuT7g.jpg
Suggestions would be appreciated.

Connect a screen to the HDMI port, and a USB keyboard and manually setup the network parameters.

My second rig came with 10.0.0.x addressing, not 192.x.x.x.

Yes - the images are of the screen connected to the pi and the default IP has been changed to our network's default ip.  I added the photos so someone more advanced then myself could check my work, but I am pretty sure that issue has been corrected.  Followed Dave's instructions.  Took two time, but the pi did save the change on the second try.

[mdbssm]

Could use some help.  Unable to access the pi from a browser.  I believe I have corrected the default gateway address to our networks.  But when I try to pull up 192.168.1.249 in a browser I can't get in.  Says "Oops! Google Chrome could not connect to 192.168.1.249"
Miner appears to working.  Chips are hot.  Here are some screen shots.
 https://i.imgur.com/3rokbmB.jpg
https://i.imgur.com/cVDuT7g.jpg
Suggestions would be appreciated.

Connect a screen to the HDMI port, and a USB keyboard and manually setup the network parameters.

My second rig came with 10.0.0.x addressing, not 192.x.x.x.

Yes - the images are of the screen connected to the pi and the default IP has been changed to our network's default ip.  I added the photos so someone more advanced then myself could check my work, but I am pretty sure that issue has been corrected.  Followed Dave's instructions.  Took two time, but the pi did save the change on the second try.

The pics show a windows machine's network config's, not the pi. Are those the right pics?

[Swimmer63]

Could use some help.  Unable to access the pi from a browser.  I believe I have corrected the default gateway address to our networks.  But when I try to pull up 192.168.1.249 in a browser I can't get in.  Says "Oops! Google Chrome could not connect to 192.168.1.249"
Miner appears to working.  Chips are hot.  Here are some screen shots.
 https://i.imgur.com/3rokbmB.jpg
https://i.imgur.com/cVDuT7g.jpg
Suggestions would be appreciated.

Connect a screen to the HDMI port, and a USB keyboard and manually setup the network parameters.

My second rig came with 10.0.0.x addressing, not 192.x.x.x.

Yes - the images are of the screen connected to the pi and the default IP has been changed to our network's default ip.  I added the photos so someone more advanced then myself could check my work, but I am pretty sure that issue has been corrected.  Followed Dave's instructions.  Took two time, but the pi did save the change on the second try.

The pics show a windows machine's network config's, not the pi. Are those the right pics?

First pic of of the pi.  See the bottom line - "pi@bitfury"

[Foofighter]

the problem is oviously the wrong sub ip?

you are using: 192.168.0.xx

miner is using: 192.168.1.xx

[-Redacted-]

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