I had been using BTC Guild since I had gotten my miner, and everything was fine up until last night when BTC Guild got hit with a DDoS attack. Since then, I am not able to connect to BTC Guild or any other pool (I've tried 50BTC, Eclipse, and Bitminter). Does anyone have any suggestions?
EDIT: Eclipse MC worked when using port 3333 instead of 8337. Good enough for me, thanks tom99.
Topic: **US** BitFury Setup Guide - page 10. (Read 53176 times)
I don't know why, but my bitfury won't talk to slush, so it is BTCguild for that, where it is happily mining at 26Gh/s. sad because Slush's pool needs all the help it can get lately.
you're telling me! yesterday i got confident and cocky that slush might NOW accept my bitfury. connected to the pool right in the middle of the goddam 15-hour block that hit CDF 99.8% or something like that.
12 hours later on another block, i see that with 1 worker it wont show more than 6 GH/s - back to bitminter i guess.
ps: seriously, i know everyone likes the frequent payouts, but stop using btcguild. 33% of block solves is ridiculous, and they should increase their fees to >4% to force some people to use other pools. bitminter is only 1% fee + 0.3% if you want api use
I had that phenomenon as well. After I used this cronjob I hash constantly at max. rate. I use /60 and restart the stratum proxy every hour.
Someone may find this useful... If your pool reports your hashrate dropping regularly DESPITE bitfury admin showing steady noncerate:
1) ssh into your pi
2) run command: crontab -e
3) add this line at the end of file:
It will restart your stratum proxy every 10 minutes from now on. If you want to cancel it, just run the command again and delete the line.
1) ssh into your pi
2) run command: crontab -e
3) add this line at the end of file:
Quote
*/10 * * * * sudo /opt/bitfury/start-stratumproxy.sh
4) save & exitIt will restart your stratum proxy every 10 minutes from now on. If you want to cancel it, just run the command again and delete the line.
once the miner is up and running stable, can we close the browser window? will it keep going with out it?
Yep you can close it
once the miner is up and running stable, can we close the browser window? will it keep going with out it?
I don't know why, but my bitfury won't talk to slush, so it is BTCguild for that, where it is happily mining at 26Gh/s. sad because Slush's pool needs all the help it can get lately.
you're telling me! yesterday i got confident and cocky that slush might NOW accept my bitfury. connected to the pool right in the middle of the goddam 15-hour block that hit CDF 99.8% or something like that.
12 hours later on another block, i see that with 1 worker it wont show more than 6 GH/s - back to bitminter i guess.
ps: seriously, i know everyone likes the frequent payouts, but stop using btcguild. 33% of block solves is ridiculous, and they should increase their fees to >4% to force some people to use other pools. bitminter is only 1% fee + 0.3% if you want api use
I don't know why, but my bitfury won't talk to slush, so it is BTCguild for that, where it is happily mining at 26Gh/s. sad because Slush's pool needs all the help it can get lately.
Yes, I have the bottom two proxies turned off, and I'm getting 67 Gh/s at Slush with my 2 h-cards. I haven't seen any hash-rate troubles running either 1, 2, or 3 proxies. If I enable all three, I get an almost perfect 22.34 Gh/s split between all three pools or workers. With just one, all 67 GH/s seems to go exactly where it's supposed to. This might be a different story with more cards, but it's working exactly right for me with my two cards.
Noncerate: 68.519GH/s
Bank 1
1: 33.239GH/s
2: 34.149GH/s
Here's from running three at BTCG - the top three lines are all three proxies in use as three workers:
These Bitfurys are perfect, but boring - they just sit there and hash silently, hour after hour. No fiddling around with them required - they don't seem to like being fiddled-around-with once they settle in. I switch to different pools from time to time, just to have something new to look at and to convince myself that I'm doing something useful.
Noncerate: 68.519GH/s
Bank 1
1: 33.239GH/s
2: 34.149GH/s
Here's from running three at BTCG - the top three lines are all three proxies in use as three workers:
These Bitfurys are perfect, but boring - they just sit there and hash silently, hour after hour. No fiddling around with them required - they don't seem to like being fiddled-around-with once they settle in. I switch to different pools from time to time, just to have something new to look at and to convince myself that I'm doing something useful.
Yes - Looks like this:
hmmm... i'll play with it tomorrow, no light in that room and it is starting to get dark out. At least it is hashing somewhere. currently BTCguild is showing it at 23,928.54 MH/s continuously rising.
On your picture....use all 3 pool spots, leave them enabled. they can be the same worker or 3 different workers to the same pool or different pool...my best advice is use all 3 slots. I notice you have the bottom 2 turned off.
Yes - Looks like this:
hmmm... i'll play with it tomorrow, no light in that room and it is starting to get dark out. At least it is hashing somewhere. currently BTCguild is showing it at 23,928.54 MH/s continuously rising.
try: nano /run/shm/.stat.log to see whats going on with the chips. Maybe your h-board is not fully inserted
you probably have the wrong (default) ip in use. did you change to your home network (usually 192.168.1.249 / 255.255.255.0 / 192.168.1.1 for ip/dns/gateway)
edit: saw you can ping out, so your net is probably ok. try another pool like
mint.bitminter.com 3333 klondike.guest x
you probably have the wrong (default) ip in use. did you change to your home network (usually 192.168.1.249 / 255.255.255.0 / 192.168.1.1 for ip/dns/gateway)
edit: saw you can ping out, so your net is probably ok. try another pool like
mint.bitminter.com 3333 klondike.guest x
Correct me if I'm wrong but shouldn't the syntax here ... "klondike.guest" be "klondike_guest" for BitMinter (and BTCGuild). And Slush uses "." Or does it work both ways when entering workername?
you're not wrong, i was.
mint.bitminter.com 3333 klondike_guest x
Yes - Looks like this:
Just pointed it there. I have no problem running 1, 2, or 3 workers. Takes about an hour for the hash rate to climb up to where it belongs - Slush uses shares submitted over the last hour to estimate hash rate.
Redacted, did you do it like this?
stratum.bitcoin.cz 3333 Trongersoll.Ruby thepassword
Just pointed it there. I have no problem running 1, 2, or 3 workers. Takes about an hour for the hash rate to climb up to where it belongs - It seems like Slush uses shares submitted over the last hour to estimate hash rate.
Make sure you're using username.worker_name and port 3333 on stratum.bitcoin.cz
Make sure you're using username.worker_name and port 3333 on stratum.bitcoin.cz
Unless you're running a version 2 M-board, you won't be updating the software.
Yes, I am running V2 MB. How did you get yours to run on Slush?
Unless you're running a version 2 M-board, you won't be updating the software.
There are a lot of usefull posts in this thread https://bitcointalksearch.org/topic/guide-bitfury-miner-supporttuning-287590
First I would change the slots and check, if the boards seat even (the chips face the pi, don't they?), then I would check if they are hashing with
sudo nano /run/shm/.stat.log
and
sudo nano /run/shm/.putstat.log
This should show results immediately or after some seconds.
First I would change the slots and check, if the boards seat even (the chips face the pi, don't they?), then I would check if they are hashing with
sudo nano /run/shm/.stat.log
and
sudo nano /run/shm/.putstat.log
This should show results immediately or after some seconds.
.stat.log shows everything zero and 16 bad.
;putstat.log doesn't exist.
oddly. after doing a stop and start at the web interface .stat.log says "good:16"
It appears to be hashing slow, but it will need time to settle out. tomorrow i'll update the miner software.
There are a lot of usefull posts in this thread https://bitcointalksearch.org/topic/guide-bitfury-miner-supporttuning-287590
First I would change the slots and check, if the boards seat even (the chips face the pi, don't they?), then I would check if they are hashing with
sudo nano /run/shm/.stat.log
and
sudo nano /run/shm/.putstat.log
This should show results immediately or after some seconds.
First I would change the slots and check, if the boards seat even (the chips face the pi, don't they?), then I would check if they are hashing with
sudo nano /run/shm/.stat.log
and
sudo nano /run/shm/.putstat.log
This should show results immediately or after some seconds.
.stat.log shows everything zero and 16 bad.
;putstat.log doesn't exist.
oddly. after doing a stop and start at the web interface .stat.log says "good:16"
try: nano /run/shm/.stat.log to see whats going on with the chips. Maybe your h-board is not fully inserted
you probably have the wrong (default) ip in use. did you change to your home network (usually 192.168.1.249 / 255.255.255.0 / 192.168.1.1 for ip/dns/gateway)
edit: saw you can ping out, so your net is probably ok. try another pool like
mint.bitminter.com 3333 klondike.guest x
you probably have the wrong (default) ip in use. did you change to your home network (usually 192.168.1.249 / 255.255.255.0 / 192.168.1.1 for ip/dns/gateway)
edit: saw you can ping out, so your net is probably ok. try another pool like
mint.bitminter.com 3333 klondike.guest x
Correct me if I'm wrong but shouldn't the syntax here ... "klondike.guest" be "klondike_guest" for BitMinter (and BTCGuild). And Slush uses "." Or does it work both ways when entering workername?
There are a lot of usefull posts in this thread https://bitcointalksearch.org/topic/guide-bitfury-miner-supporttuning-287590
First I would change the slots and check, if the boards seat even (the chips face the pi, don't they?), then I would check if they are hashing with
sudo nano /run/shm/.stat.log
and
sudo nano /run/shm/.putstat.log
This should show results immediately or after some seconds.
First I would change the slots and check, if the boards seat even (the chips face the pi, don't they?), then I would check if they are hashing with
sudo nano /run/shm/.stat.log
and
sudo nano /run/shm/.putstat.log
This should show results immediately or after some seconds.
.stat.log shows everything zero and 16 bad.
;putstat.log doesn't exist.
try: nano /run/shm/.stat.log to see whats going on with the chips. Maybe your h-board is not fully inserted
you probably have the wrong (default) ip in use. did you change to your home network (usually 192.168.1.249 / 255.255.255.0 / 192.168.1.1 for ip/dns/gateway)
edit: saw you can ping out, so your net is probably ok. try another pool like
mint.bitminter.com 3333 klondike.guest x
you probably have the wrong (default) ip in use. did you change to your home network (usually 192.168.1.249 / 255.255.255.0 / 192.168.1.1 for ip/dns/gateway)
edit: saw you can ping out, so your net is probably ok. try another pool like
mint.bitminter.com 3333 klondike.guest x
Yeah, i can also ping the Pi from another machine on the LAN.
Jump to: