Topic: **US** BitFury Setup Guide - page 28. (Read 53265 times)
Did you jump the green and black wires on the 24 pin connector? PSU won't run unless you do...
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?
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?
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 ....
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 ....
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.
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.
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.
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'
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.?
Dave will that be a free replacement or a paid one.?
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.
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.
lolNo changes + or -
Ok, which one do I believe here?
BF is reporting 37GH/s
Slash's Pool is showing 16.5GH/s
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
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
#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!
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
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...
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
#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
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
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??
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.
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 .
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.
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.
You can't run cgminer for this - the Raspberry Pi has a miner set up already. Point a webpage at the IP address of your RasPi and configure your pool information on that page.
Hey guys,
I got a my starter kit assembled, fired up, changed the host ip, so I get internet access working.
Forgive my noob situatuon here, but I cannot get cgminer onto the pi, and have been looking around the net for some help to no avail.
Can someone please write out what to type in the lxterminal for linux ? I have my bitcoin wallet, address all set up, and know about that.
I just got lost typing the commands trying to get it to install/fire up cgminer and directed to my wallet.
This is my first rig, so be gentle now.
lol.
Thanks ahead of time for the help, and thanks to Dave for such a great job with the turnaround time!
I got a my starter kit assembled, fired up, changed the host ip, so I get internet access working.
Forgive my noob situatuon here, but I cannot get cgminer onto the pi, and have been looking around the net for some help to no avail.
Can someone please write out what to type in the lxterminal for linux ? I have my bitcoin wallet, address all set up, and know about that.
I just got lost typing the commands trying to get it to install/fire up cgminer and directed to my wallet.
This is my first rig, so be gentle now.
lol.Thanks ahead of time for the help, and thanks to Dave for such a great job with the turnaround time!
Ok, which one do I believe here?
BF is reporting 37GH/s
Slash's Pool is showing 16.5GH/s
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.
Ok, which one do I believe here?
BF is reporting 37GH/s
Slash's Pool is showing 16.5GH/s
BF is reporting 37GH/s
Slash's Pool is showing 16.5GH/s
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
We're putting it on a public IP, and after setting the parameters in /etc/networking/interfaces, we get no IP address showing up when doing an ifconfig. The address, netmask, and gateway are all correct in the file. Is there ANYTHING that we can look at to see why the networking service isn't configuring the interface?
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
Hey guys - I just got word that we sent out your rPi's configured with a weird gateway IP. This is going to make it hard for your rigs to reach the outside world.
To fix this you'll need to connect direct to your rPi. Either use keyboard/monitor, or use ssh to connect to it 192.168.1.249 (unless you changed IP).
use arrow keys to get down to
change this to
type
reboot the rPi
Sorry for the trouble!
To fix this you'll need to connect direct to your rPi. Either use keyboard/monitor, or use ssh to connect to it 192.168.1.249 (unless you changed IP).
Code:
sudo nano /etc/network/interfaces
use arrow keys to get down to
Code:
gateway 192.168.1.3
change this to
Code:
gateway 192.168.1.1
...or whatever your gateway IP is.type
Code:
ctrl-X[enter]
Yes[enter]
Yes[enter]
reboot the rPi
Sorry for the trouble!
We're putting it on a public IP, and after setting the parameters in /etc/networking/interfaces, we get no IP address showing up when doing an ifconfig. The address, netmask, and gateway are all correct in the file. Is there ANYTHING that we can look at to see why the networking service isn't configuring the interface?
Might want to check your system startup logs for any errors /var/log/syslog
Jump to: