**US** BitFury Setup Guide

[tom99]

Ok, got mine working with some help from JWU42. Seems my network won't accept the rPi with static IP. I have no idea why. DHCP worked excellent.

Question:

At the beginning of this guide it seems to say that the extra proxy's are not for fail over. Am I reading that correctly? If that is the case, what are they for? I only configured the first one and everything seems to work fine.

  notthing to do with static ip but gateway ip need to change to  xxx.xxx.1.xxx .

[arorts]

Same here. This looks correct and allows me to connect when I set my laptops ip to 192.168.169.177 and direct connect the ethernet cable to the rPi but won't work when connected to the LAN.

auto lo

iface lo inet loopback
iface eth0 inet static
address 192.168.169.175
netmask 255.255.255.0
network 192.168.169.0
broadcast 192.168.169.255
gateway 192.168.169.168

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

 I hate dynamic IP. I like a predictable IP. This issue is probably related to lack of DNS definition but then the  question is how to setup DNS??? Does anyone know how to make static IP work??

[Doff]

All you should need in your interface file for a static ip is below. One last edit reading back it looks like a few of just need to add the last line for DNS to make this work. Without the DNS it has no idea where to go thats why the dhcp is fixing it, its adding the DNS from the router

#Put you own IPs here these are just examples

auto eth0
    iface eth0 inet static
        address 192.0.2.7
        netmask 255.255.255.0
        gateway 192.0.2.254

# This is for dns, my example is using the open-dns ips

dns-nameservers 208.67.222.222  208.67.220.220

[-Redacted-]

Same here. This looks correct and allows me to connect when I set my laptops ip to 192.168.169.177 and direct connect the ethernet cable to the rPi but won't work when connected to the LAN.

auto lo

iface lo inet loopback
iface eth0 inet static
address 192.168.169.175
netmask 255.255.255.0
network 192.168.169.0
broadcast 192.168.169.255
gateway 192.168.169.168

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

 I hate dynamic IP. I like a predictable IP. This issue is probably related to lack of DNS definition but then the  question is how to setup DNS??? Does anyone know how to make static IP work??

That last line also needs to be changed - it forces the use of dhcp...

[arorts]

All you should need in your interface file for a static ip is below. One last edit reading back it looks like a few of just need to add the last line for DNS to make this work. Without the DNS it has no idea where to go thats why the dhcp is fixing it, its adding the DNS from the router

#Put you own IPs here these are just examples

auto eth0
    iface eth0 inet static
        address 192.0.2.7
        netmask 255.255.255.0
        gateway 192.0.2.254

# This is for dns, my example is using the open-dns ips

dns-nameservers 208.67.222.222  208.67.220.220

Yes, that last command seems to be the answer so as to not need any DCHP at all! Will give it a try. I think the values need to be hardcoded, because not sure if I can just set the gateway IP as the DNS. Probably not. I can perhaps just add a public DNS, like 8.8.8.8 correct? Thx! 

[zurg]

Ok, which one do I believe here?

BF is reporting 37GH/s
Slash's Pool is showing 16.5GH/s

I believe that I saw there being an issue on Slush's pool discussed on the EU bitfury thread.

Yeah, I read it a bit.. Couldn't make sense of anything, lol, maybe I was just me trying to drive and read on the phone..
But when I got home I stopped and started the miner from GUI and it seems to have been running stable now overnight.
FB reporting 38 to 40, with Slash's 38.
Although Slash's still showing Average hashrate in last 10 rounds: 34717 Mhash/s

[zurg]

WOW - these boards LOVE warm temps.

I have a 400GH/s kit setup, and got the following:

300GH/s average rate over 1 hour - 2 x 120mm fan at 2500RPM blowing over them
420GH/s average rate over 1 hour - ZERO air flow, 78F ambient tempterature

This is probably the only instance I can remember where I have seen processors that do NOT like cooler temps.

Interesting, I am going to give this a shot...
My server room is at 60F, I just took the fan off the 2 boards , lol.., timer started.

Will update soon.

Well, after an hour I report nothing. lol
No changes + or -

[americandesi]

Anyone has an idea when the V2 M boards will be sent to the customers.?

Dave will that be a free replacement or a paid one.?

[arorts]

WOW - these boards LOVE warm temps.

I have a 400GH/s kit setup, and got the following:

300GH/s average rate over 1 hour - 2 x 120mm fan at 2500RPM blowing over them
420GH/s average rate over 1 hour - ZERO air flow, 78F ambient tempterature

This is probably the only instance I can remember where I have seen processors that do NOT like cooler temps.

Interesting, I am going to give this a shot...
My server room is at 60F, I just took the fan off the 2 boards , lol.., timer started.

Will update soon.

You can fry your chips at those temps.  Dave already has emphasized more than once to blow air on them and still people insist. Lol. At your own risk.  Just sayin'

[zurg]

WOW - these boards LOVE warm temps.

I have a 400GH/s kit setup, and got the following:

300GH/s average rate over 1 hour - 2 x 120mm fan at 2500RPM blowing over them
420GH/s average rate over 1 hour - ZERO air flow, 78F ambient tempterature

This is probably the only instance I can remember where I have seen processors that do NOT like cooler temps.

Interesting, I am going to give this a shot...
My server room is at 60F, I just took the fan off the 2 boards , lol.., timer started.

Will update soon.

You can fry your chips at those temps.  Dave already has emphasized more than once to blow air on them and still people insist. Lol. At your own risk.  Just sayin'

Yeah, I already have my fan back on them after monitoring them closely. Not worth the risk.

[darkfriend77]

I have done 2 test runs ....

temperature was measured from the PCB.

without fans:

PCB @ 60° ... avg. Hashingrate around 41.5 GH
with fans:

PCB @ 41° ... avg. Hashingrate around 42.0 GH

So my conclusion is ... that they do work more or less the same cooled or uncooled ....

[superduh]

question as i have no idea how long it will take dave's tech support to answer.
if someone follows the guide and did everything correctly! and the rasperry pi doesn't turn on (no status lights) and nothing showing up on router.
the psu is low humming. didn't do anything with the atx 24 cable. help?

[-Redacted-]

Did you jump the green and black wires on the 24 pin connector?  PSU won't run unless you do...

[zurg]

I actually tried firing up my 2 card kit with a 300w HP power supply.
Used SATA to 6pin (only 5 wires with middle yellow missing) but that wasn't powering it up even though PS's fans were spinning and power light on it was on, so I opened my 1KW PS fir right now until my OCZ one shows up.

[superduh]

Did you jump the green and black wires on the 24 pin connector?  PSU won't run unless you do...

nope . dave's guide was for the more sophisticated.  wish i knew this ahead of time
also, someone posted this in main thread http://www.robotshop.com/cytron-atx-power-supply-breakout-board-right-angle-3.html
as a nice long term solution.
or a worse version: http://www.frys.com/product/6489932?site=sr:SEARCH:MAIN_RSLT_PG

[-Redacted-]

I actually tried firing up my 2 card kit with a 300w HP power supply.
Used SATA to 6pin (only 5 wires with middle yellow missing) but that wasn't powering it up even though PS's fans were spinning and power light on it was on, so I opened my 1KW PS fir right now until my OCZ one shows up.

Guess what, it's the yellow wire that's important.  You can't use SATA connector to power the kit - you need at least one PCIe 6 pin for the starter.

[-Redacted-]

Did you jump the green and black wires on the 24 pin connector?  PSU won't run unless you do...

nope . dave's guide was for the more sophisticated.  wish i knew this ahead of time
also, someone posted this in main thread http://www.robotshop.com/cytron-atx-power-supply-breakout-board-right-angle-3.html
as a nice long term solution.
or a worse version: http://www.frys.com/product/6489932?site=sr:SEARCH:MAIN_RSLT_PG

There's about a million different descriptions around, including pictures, of how to do this with just a paperclip...

[zurg]

Did you jump the green and black wires on the 24 pin connector?  PSU won't run unless you do...

nope . dave's guide was for the more sophisticated.  wish i knew this ahead of time
also, someone posted this in main thread http://www.robotshop.com/cytron-atx-power-supply-breakout-board-right-angle-3.html
as a nice long term solution.
or a worse version: http://www.frys.com/product/6489932?site=sr:SEARCH:MAIN_RSLT_PG

Yeah, but... a paperclip cut to 1/2 pushed in and taped over with electrical tape is so much cheaper.

[zurg]

I actually tried firing up my 2 card kit with a 300w HP power supply.
Used SATA to 6pin (only 5 wires with middle yellow missing) but that wasn't powering it up even though PS's fans were spinning and power light on it was on, so I opened my 1KW PS fir right now until my OCZ one shows up.

Guess what, it's the yellow wire that's important.  You can't use SATA connector to power the kit - you need at least one PCIe 6 pin for the starter.

yeah, I was seeing if I could do it on the cheap. lol

[pixl8tr]

I actually tried firing up my 2 card kit with a 300w HP power supply.
Used SATA to 6pin (only 5 wires with middle yellow missing) but that wasn't powering it up even though PS's fans were spinning and power light on it was on, so I opened my 1KW PS fir right now until my OCZ one shows up.

Guess what, it's the yellow wire that's important.  You can't use SATA connector to power the kit - you need at least one PCIe 6 pin for the starter.

Doesn't matter what color the wire is, as long as you have +12v, + GND and can carry the current load.  - LOL all my wires are black coming into my PCIe connector from the PSU.