[ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING***

[tom99]

Got mine up and running, but while the web interface indicates 70 GH/s (with two H-boards), BTC Guild is only seeing about 24 GH/s.  Last night, I noticed that the locally-indicated hashrate was jumping all around.  I have a high-flow 120mm fan blowing across the boards, but don't yet have heatsinks installed.  Am I seeing thermal throttling as a result?  I have a bunch of heatsinks on order, but it'll be a while before they arrive. Since previous versions were designed to run at a slower rate with just air movement and no heatsinks, is there a temporary adjustment I can make to at least get 40-50 GH/s out of my rig while I'm waiting? 

   You can read more here https://bitcointalk.org/index.php?topic=287590.0

[1714608859]

1714608859

[1714608859]

1714608859

[1714608859]

1714608859

[Doff]

I managed to get my Unit working Stable, it seems these guys want to be cooled in a specific way. I added 3 120MM fans to the top with 1 Box fan pushing air across it from the side. The real trick is it did not like the air on the same side as the regulator, no clue why but once I moved it to the other side it has hashed at 575-580 for about 11 hours now.

Now I need to move it off my workbench to where its going stay for good, lets hope my results do not vary. At least I have an idea what to do I suppose.

I asked Mega to stop my RMA for now since all the Units appear to work fantastic with Proper cooling.

[JaredR26]

This is what goxed wrote up for me to update chainminer on a V1 M-board and it worked.

cd ~/

a) mkdir chainminer-temp
b) cd  chainminer-temp
c) wget https://github.com/bfsb/chainminer/archive/master.zip
d) unzip master.zip
e) cd chainminer-master
f) change line 6 in miner.h
  f.1) vim miner.h  (do you use vim?)
  f.2) i
  f.3) change the line
  f.4) Esc
  f.5) wq enter
  f.6) you can try nano otherwise (nano miner.h)
g) make
h) cd ..
i) mv /opt/bitfury/chainminer /opt/bitfury/chainminer_v1_original
j) cp -r chainminer-master /opt/bitfury/chainminer

Note: Some of the new changes I made might cause problems with our rigs with those steps.  They also will need to do this after building:

Code:

cp /opt/bitfury/chainminer/miner /opt/bitfury/chainminer/miner_customer
crontab -l | grep -v "auto-miner-config" | crontab -

The first line updates a file I was referencing to determine which miner to use.  The second line turns off my automatic configuration so that it won't run at all regardless.

[Keefe]

I accidentally cleared my crontab earlier, while trying to add my own logging script. Can someone show me their crontab for a v3 rig?

[Swimmer63]

Question - I am suppose to receive a second EOL board tomorrow.  How do order them on the M-board.
The higher hashing one second to the end and then the lower one at the end of the line?  Does it matter?
I don't want any screw ups as I'm adding two more regular h-boards on top of this.

[Keefe]

Question - I am suppose to receive a second EOL board tomorrow.  How do order them on the M-board.
The higher hashing one second to the end and then the lower one at the end of the line?  Does it matter?
I don't want any screw ups as I'm adding two more regular h-boards on top of this.

EOL cards must be at the end of a bank, because no cards after them (even other EOL cards) will be seen. Do you have a single-bank v1 M-board, or a 4-bank v2/v3?

[klondike_bar]

Question - I am suppose to receive a second EOL board tomorrow.  How do order them on the M-board.
The higher hashing one second to the end and then the lower one at the end of the line?  Does it matter?
I don't want any screw ups as I'm adding two more regular h-boards on top of this.

EOL must be in the 4th slot of a bank. You can use up to 4 EOL cards per hboard

[Swimmer63]

Question - I am suppose to receive a second EOL board tomorrow.  How do order them on the M-board.
The higher hashing one second to the end and then the lower one at the end of the line?  Does it matter?
I don't want any screw ups as I'm adding two more regular h-boards on top of this.

EOL cards must be at the end of a bank, because no cards after them (even other EOL cards) will be seen. Do you have a single-bank v1 M-board, or a 4-bank v2/v3?

I have one of the first ones shipped...order #12.  It's V1 m-board but I thought it had four banks.  Maybe not.  Right now I have 4 cards and the EOL.  EOL last.

[Keefe]

Question - I am suppose to receive a second EOL board tomorrow.  How do order them on the M-board.
The higher hashing one second to the end and then the lower one at the end of the line?  Does it matter?
I don't want any screw ups as I'm adding two more regular h-boards on top of this.

EOL cards must be at the end of a bank, because no cards after them (even other EOL cards) will be seen. Do you have a single-bank v1 M-board, or a 4-bank v2/v3?

I have one of the first ones shipped...order #12.  It's V1 m-board but I thought it had four banks.  Maybe not.  Right now I have 4 cards and the EOL.  EOL last.

Pretty sure you can only use one EOL card then. Want to sell one to me?

[optimator]

I accidentally cleared my crontab earlier, while trying to add my own logging script. Can someone show me their crontab for a v3 rig?

logged in as pi

crontab -l produces this output

Code:

#!/bin/bash
PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

# Edit this file to introduce tasks to be run by cron.
# 
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# 
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').# 
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# 
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
# 
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# 
# For more information see the manual pages of crontab(5) and cron(8)
# 
# m h  dom mon dow   command

@reboot /home/pi/auto-IP-configuration.pl 2>&1 > /home/pi/.ip_results.log
@reboot /home/pi/auto-miner-configuration.pl 2>&1 > /home/pi/.miner_results.log

[cypherdoc]

i have the entire Bank 1 at zero hashing (first 4 slots)    i have 3 140mm fans and one large box fan blowing at it.

have v2.2 H boards with v3 M board.  doesn't matter which H boards go into those slots.

any suggestions?

[Keefe]

I accidentally cleared my crontab earlier, while trying to add my own logging script. Can someone show me their crontab for a v3 rig?

logged in as pi

crontab -l produces this output

Code:

#!/bin/bash
PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

# Edit this file to introduce tasks to be run by cron.
# 
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# 
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').# 
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# 
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
# 
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# 
# For more information see the manual pages of crontab(5) and cron(8)
# 
# m h  dom mon dow   command

@reboot /home/pi/auto-IP-configuration.pl 2>&1 > /home/pi/.ip_results.log
@reboot /home/pi/auto-miner-configuration.pl 2>&1 > /home/pi/.miner_results.log

Thanks!

[Keefe]

i have the entire Bank 1 at zero hashing (first 4 slots)    i have 3 140mm fans and one large box fan blowing at it.

have v2.2 H boards with v3 M board.  doesn't matter which H boards go into those slots.

any suggestions?

I'd assume a problem with the M-board. RMA?

[frankenmint]

i have the entire Bank 1 at zero hashing (first 4 slots)    i have 3 140mm fans and one large box fan blowing at it.

have v2.2 H boards with v3 M board.  doesn't matter which H boards go into those slots.

any suggestions?

Im going through something sort of similar however I found that it was becasue my best.cnf file was not configured properly.

I'm tuning each chip to AIfDSo


Bank 1      Bank 2                Bank 3                            Bank 4
1: 35.137GH/s      5: 2.407GH/s      9: 32.583GH/s      13: 34.36GH/s
2: 31.768GH/s      6: 32.583GH/s      10: 0.815GH/s      14: 34.915GH/s
3: 32.175GH/s      7: 7.775GH/s      11: 36.581GH/s      15: 33.471GH/s
4: 34.915GH/s      8: 33.693GH/s      12: 35.804GH/s      16: 30.213GH/s
                  
Bank 1                           Bank 2      Bank 3                        Bank 4
1: 36.86GH/s      5: 34.456GH/s      9: 10.545GH/s      13: 19.936GH/s
2: 31.699GH/s      6: 18.045GH/s      10: 30.834GH/s      14: 20.129GH/s
3: 30.802GH/s      7: 34.424GH/s      11: 4.167GH/s      15: 18.045GH/s
4: 22.565GH/s      8: 20.417GH/s      12: 5.353GH/s      16: 15.353GH/s
                  
                  
                  
Bank 1                          Bank 2                 Bank 3      Bank 4
1: 30.68GH/s      5: 9.964GH/s      9: 35.004GH/s      13: 35.276GH/s
2: 32.212GH/s      6: 19.556GH/s      10: 28.576GH/s      14: 20.186GH/s
3: 32.227GH/s      7: 14.574GH/s      11: 23.293GH/s      15: 13.157GH/s
4: 13.085GH/s      8: 21.289GH/s      12: 23.221GH/s      16: 12.541GH/s
                  


This is my result from 3 tests at 5 minutes in on those settings - I saw a chron job 1-line script here that Keefe wrote that is supposed to reset stratum every 10 minutes, I want to try that script but to restart my miner every 5 minutes - seems like I'm getting solid hashrate within that 1st 5 minutes then everything runs - but as you can see from my past tests - my hashrate seems to drop every time after 5 minutes - I have 6 120 mm fans going and heatsinks so I have no idea what gives

[cypherdoc]

i have the entire Bank 1 at zero hashing (first 4 slots)    i have 3 140mm fans and one large box fan blowing at it.

have v2.2 H boards with v3 M board.  doesn't matter which H boards go into those slots.

any suggestions?

I'd assume a problem with the M-board. RMA?

i can't think of anything else.

[frankenmint]

This was it here to quote so that I can find it myself easily next time:

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:
Quote
*/10    *       *       *       *       sudo /opt/bitfury/start-stratumproxy.sh
4) save & exit

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.


I took this from the EU bitfury maitenance/tuning thread.

[changed mine to */10 * * * * sudo /opt/bitfury/start-miner.sh]

(crossing my fingers that this doesnt break anything and I'm hoping it keeps my hashrate high)

[cypherdoc]

anyone successfully connect to ozcoin or slush?  if so, what addresses are you using?  for instance, my typical addresses to connect aren't working:  stratum.ozco.in:3333, us.ozco.in:3333, stratum+tcp://stratum.ozco.in:3333.

my solo mining stratum port monitor 8889 hashrate shows a huge discrepancy vs. the hashrate advertised in the BF GUI.  i'd like to connect to a pool to see if i see the same discrepancy.

[frankenmint]

anyone successfully connect to ozcoin or slush?  if so, what addresses are you using?  for instance, my typical addresses to connect aren't working:  stratum.ozco.in:3333, us.ozco.in:3333, stratum+tcp://stratum.ozco.in:3333.

my solo mining stratum port monitor 8889 hashrate shows a huge discrepancy vs. the hashrate advertised in the BF GUI.  i'd like to connect to a pool to see if i see the same discrepancy.

to that note I'm also having problems connecting to pools except btcguild.  I cannot connect to neither eligius nor bitminter.  using mint.bitminter.com, 3333, usr, pwd,

[frankenmint]

I managed to get my Unit working Stable, it seems these guys want to be cooled in a specific way. I added 3 120MM fans to the top with 1 Box fan pushing air across it from the side. The real trick is it did not like the air on the same side as the regulator, no clue why but once I moved it to the other side it has hashed at 575-580 for about 11 hours now.

Now I need to move it off my workbench to where its going stay for good, lets hope my results do not vary. At least I have an idea what to do I suppose.

I asked Mega to stop my RMA for now since all the Units appear to work fantastic with Proper cooling.

I installed more heatsinks and I'm seeing this too from my tests - Looks like fans should not be on the "PULSE" chip side at all.

The startminer chronjob seems to keep my unit hashing at around the 500s between 5-600 when it restarts, but I don't know if I"m effectively increasing my hashrate overall as btcguild reports only half my speed (I did set the correct difficulty on the pool settings)

[tacotime]

Got antsy, so I cranked down the voltage on the trimpot to 0.840 V on my card that always shuts off.  I'll see if this makes the card last any longer.

Note for users: use a tiny philips screw driver and turn right to increase voltage, left to decrease voltage.