**US** BitFury Setup Guide

[jspielberg]

Congrats Af_newbie -

To get the extra performance, did you manually configure autotune disabled from the problem chips and then set their speed to 0?

[1715466983]

1715466983

[1715466983]

1715466983

[1715466983]

1715466983

[1715466983]

1715466983

[af_newbie]

Congrats Af_newbie -

To get the extra performance, did you manually configure autotune disabled from the problem chips and then set their speed to 0?

Thanks. 

All of the above plus, a strong AC fan AND pencil mod to bring R02F to 1.23K from 1.3K (on board measurement).

The bad chips (not sure if it is the chips or the mounting issue) did not bring anything to the table.  Created more errors than actual work.
I figured, they might actually slow things down for other chips so I took turned them off.  This probably lowers the power draw which should offset the pencil mod.

[Sitarow]

I have what feels like a newb issue, but not sure what to do.

Starter kit all set up.  I think everything connected properly, no lose wires and it matches other's install pictures.
But when I turn the power on (manual switch, I get a green light), it starts but my monitor's "Power" and "Menu" light just pulse on and off.  No picture on the screen.  Those lights never pulse.
I just took the monitor off a working PC and it's fine.  I did have to buy a HDMI to DVI adapter for the monitor but that should not be the issue.
Any thoughts would be appreciated.  Thanks in advance!

When you power on the raspberry pi you should see a red led indicating power and activity led light will flash at about the same time if your SDCard is inserted and detected.

If all you get is the Red LED then perhaps the sd card is the issue?

Thanks guys I'll try both tomorrow. Rig is not with me now. Is the Rpi light on the bottom or top?

its in the bottom right on the board to the right of the usb ports.

[mwk13]

Can someone tell me why I'm seeing the below hashrate differences for my 400 gh/s kit?

Bitfury admin pages noncerate is 417.51 gh/s. Slush's pool is 2.9 gh/s!

Bitfury admin page 1 (xxx.xxx.x.250)
Noncerate: 45.04GH/s
pool config: stratum.bitcoin.cz, 3333, idxxx.worker1

Bitfury admin page 2 (xxx.xxx.x.251)
Noncerate: 372.474GH/s
pool config: stratum.bitcoin.cz, 3333, idxxx.worker2

Slush's Pool
                     curr                                                sugg.
login               shares  score         Mhash/s   stratum  diff.
idxxx.worker1   954      2043.1946  1411.922   yes       32
idxxx.worker2   1009    2129.3236  1493.323   yes        256

Average hashrate in last 10 rounds: 3708 Mhash/s
Unconfirmed reward: 0.01430835 BTC
Confirmed reward:   0.00182180 BTC
These rewards are for about 1 day of mining.


Thank you.

[tom99]

Can someone tell me why I'm seeing the below hashrate differences for my 400 gh/s kit?

Bitfury admin pages noncerate is 417.51 gh/s. Slush's pool is 2.9 gh/s!

Bitfury admin page 1 (xxx.xxx.x.250)
Noncerate: 45.04GH/s
pool config: stratum.bitcoin.cz, 3333, idxxx.worker1

Bitfury admin page 2 (xxx.xxx.x.251)
Noncerate: 372.474GH/s
pool config: stratum.bitcoin.cz, 3333, idxxx.worker2

Slush's Pool
                     curr                                                sugg.
login               shares  score         Mhash/s   stratum  diff.
idxxx.worker1   954      2043.1946  1411.922   yes       32
idxxx.worker2   1009    2129.3236  1493.323   yes        256

Average hashrate in last 10 rounds: 3708 Mhash/s
Unconfirmed reward: 0.01430835 BTC
Confirmed reward:   0.00182180 BTC
These rewards are for about 1 day of mining.


Thank you.

set your diff 22  and 190 wait for 30 minutes or more

[af_newbie]

Can someone tell me why I'm seeing the below hashrate differences for my 400 gh/s kit?

Bitfury admin pages noncerate is 417.51 gh/s. Slush's pool is 2.9 gh/s!

Bitfury admin page 1 (xxx.xxx.x.250)
Noncerate: 45.04GH/s
pool config: stratum.bitcoin.cz, 3333, idxxx.worker1

Bitfury admin page 2 (xxx.xxx.x.251)
Noncerate: 372.474GH/s
pool config: stratum.bitcoin.cz, 3333, idxxx.worker2

Slush's Pool
                     curr                                                sugg.
login               shares  score         Mhash/s   stratum  diff.
idxxx.worker1   954      2043.1946  1411.922   yes       32
idxxx.worker2   1009    2129.3236  1493.323   yes        256

Average hashrate in last 10 rounds: 3708 Mhash/s
Unconfirmed reward: 0.01430835 BTC
Confirmed reward:   0.00182180 BTC
These rewards are for about 1 day of mining.


Thank you.

Try EMC or btcguild.  You should see the correct rates in 15 min.

[Swimmer63]

Thanks Sitarow!

[dracore]

Hi all,

I just noticed I am running into problems after 2 days hashing on slush.  It is now showing 0 noncerate.  I've tried start/stop miner but no good.  ssh'd in and tried this:

root@bitfury:/opt/bitfury# ./start-miner-console.sh
INIT: 0 chips detected
./start-miner-console.sh: line 1:  2274 Floating point exception/opt/bitfury/chainminer/miner

Also tried rebooting rpi.  The only thing I haven't done is power off the whole unit -- which I cannot do till I get home.

Did something die?

[Sitarow]

Hi all,

I just noticed I am running into problems after 2 days hashing on slush.  It is now showing 0 noncerate.  I've tried start/stop miner but no good.  ssh'd in and tried this:

root@bitfury:/opt/bitfury# ./start-miner-console.sh
INIT: 0 chips detected
./start-miner-console.sh: line 1:  2274 Floating point exception/opt/bitfury/chainminer/miner

Also tried rebooting rpi.  The only thing I haven't done is power off the whole unit -- which I cannot do till I get home.

Did something die?

check what your /opt/bitfury/proxy_pools.conf is set too.

I would consider also restarting the stratum server first before restarting the miner.

[dracore]

check what your /opt/bitfury/proxy_pools.conf is set too.

I would consider also restarting the stratum server first before restarting the miner.

Yup I did all that and found that it didn't help.  I think there's a problem with the card.  Sometimes it hashes at regular rates, other times it stops hashing for some time.  It's like sometimes the chips are partially failing...

[Sitarow]

check what your /opt/bitfury/proxy_pools.conf is set too.

I would consider also restarting the stratum server first before restarting the miner.

Yup I did all that and found that it didn't help.  I think there's a problem with the card.  Sometimes it hashes at regular rates, other times it stops hashing for some time.  It's like sometimes the chips are partially failing...

check also that the cards are properly seated in the socket. Also if you get any chips that are operating at sub 1.0 speed then set it to disabled and see if that helps.


type this in ssh console

nano /run/shm/.stat.log

scroll to the bottom by pressing page down and see if you have any bad or off chips that may have been detected by autotune.

If you do i start by disabling them to get the board working good.

[dracore]

check also that the cards are properly seated in the socket. Also if you get any chips that are operating at sub 1.0 speed then set it to disabled and see if that helps.


type this in ssh console

nano /run/shm/.stat.log

scroll to the bottom by pressing page down and see if you have any bad or off chips that may have been detected by autotune.

If you do i start by disabling them to get the board working good.

Thanks.  Where can I find out what each column represents?

[Sitarow]

check also that the cards are properly seated in the socket. Also if you get any chips that are operating at sub 1.0 speed then set it to disabled and see if that helps.


type this in ssh console

nano /run/shm/.stat.log

scroll to the bottom by pressing page down and see if you have any bad or off chips that may have been detected by autotune.

If you do i start by disabling them to get the board working good.

Thanks.  Where can I find out what each column represents?

http://punin.com/README_BFSB_v0.1.txt

[jddebug]

check what your /opt/bitfury/proxy_pools.conf is set too.

I would consider also restarting the stratum server first before restarting the miner.

Yup I did all that and found that it didn't help.  I think there's a problem with the card.  Sometimes it hashes at regular rates, other times it stops hashing for some time.  It's like sometimes the chips are partially failing...

check also that the cards are properly seated in the socket. Also if you get any chips that are operating at sub 1.0 speed then set it to disabled and see if that helps.


type this in ssh console

nano /run/shm/.stat.log

scroll to the bottom by pressing page down and see if you have any bad or off chips that may have been detected by autotune.

If you do i start by disabling them to get the board working good.

Sitarow,

This is what mine displays. Looks like 5 bad and one off?

What would I look for now and how to disable?

speed:6710 noncerate[GH/s]:220.432 (1.722/chip) hashrate[GH/s]:237.606 good:15397 errors:860 spi-err:5 miso-err:0 jobs:322 cores:95% good:122 bad:5 off:1 (best[GH/s]:229.165) Tue Sep 10 01:42:09 2013
0:      825     29.936  31.836  2091    100     0       0       15      1       0       (1.871/chip)    95%
1:      880     31.081  33.083  2171    101     0       0       16      0       0       (1.943/chip)    100%
2:      880     28.146  30.821  1966    35      0       0       16      0       0       (1.759/chip)    98%
3:      770     26.285  29.690  1836    193     1       0       14      2       0       (1.643/chip)    86%
4:      770     25.641  28.031  1791    145     1       0       14      2       0       (1.603/chip)    92%
5:      825     29.664  31.286  2072    85      1       0       15      0       1       (1.854/chip)    93%
6:      880     21.289  22.873  1487    94      1       0       16      0       0       (1.331/chip)    97%
7:      880     28.390  29.986  1983    107     1       0       16      0       0       (1.774/chip)    99%

My other looks worse:

speed:7260 noncerate[GH/s]:203.467 (1.413/chip) hashrate[GH/s]:224.172 good:14212 errors:749 spi-err:6 miso-err:0 jobs:323 cores:89% good:132 bad:8 off:4 (best[GH/s]:212.257) Tue Sep 10 01:47:15 2013

[Sitarow]

check what your /opt/bitfury/proxy_pools.conf is set too.

I would consider also restarting the stratum server first before restarting the miner.

Yup I did all that and found that it didn't help.  I think there's a problem with the card.  Sometimes it hashes at regular rates, other times it stops hashing for some time.  It's like sometimes the chips are partially failing...

check also that the cards are properly seated in the socket. Also if you get any chips that are operating at sub 1.0 speed then set it to disabled and see if that helps.


type this in ssh console

nano /run/shm/.stat.log

scroll to the bottom by pressing page down and see if you have any bad or off chips that may have been detected by autotune.

If you do i start by disabling them to get the board working good.

Sitarow,

This is what mine displays. Looks like 5 bad and one off?

What would I look for now and how to disable?

speed:6710 noncerate[GH/s]:220.432 (1.722/chip) hashrate[GH/s]:237.606 good:15397 errors:860 spi-err:5 miso-err:0 jobs:322 cores:95% good:122 bad:5 off:1 (best[GH/s]:229.165) Tue Sep 10 01:42:09 2013
0:      825     29.936  31.836  2091    100     0       0       15      1       0       (1.871/chip)    95%
1:      880     31.081  33.083  2171    101     0       0       16      0       0       (1.943/chip)    100%
2:      880     28.146  30.821  1966    35      0       0       16      0       0       (1.759/chip)    98%
3:      770     26.285  29.690  1836    193     1       0       14      2       0       (1.643/chip)    86%
4:      770     25.641  28.031  1791    145     1       0       14      2       0       (1.603/chip)    92%
5:      825     29.664  31.286  2072    85      1       0       15      0       1       (1.854/chip)    93%
6:      880     21.289  22.873  1487    94      1       0       16      0       0       (1.331/chip)    97%
7:      880     28.390  29.986  1983    107     1       0       16      0       0       (1.774/chip)    99%

My other looks worse:

speed:7260 noncerate[GH/s]:203.467 (1.413/chip) hashrate[GH/s]:224.172 good:14212 errors:749 spi-err:6 miso-err:0 jobs:323 cores:89% good:132 bad:8 off:4 (best[GH/s]:212.257) Tue Sep 10 01:47:15 2013

First move the boards with 880 to the front of the line then the 825 ones and the 770 to the back.

so I would start with
Move 7 to 0 and put 0 on 4 and put 4 to 6
Move 6 to 7 as I think that one has chips that auto tune is still having troubles with.
Move 5 to 3 and 3 to 5.

After you do that then wait about 30 minutes, then run nano /run/shm/.stat.log

If you notice any chips pushing 0.600 or below turn them off by replacing AIfDSo to aifdso on the same line number as the chip. This is important because auto tuning will keep working with them if it can causing errors that may throw off some pools.

Note: I would only consider turning off auto tuning if I am in a temperature controlled environment where the ambient temperature is constant. OR if I am not as aggresive on my speed settings of the chips.

Below is an example of an "EOL" board that was included with my kit. I have simply turned off those chips but will be later cleaning the board with isopropyl alcohol to see if i can clear up some potential issues.

240     aifdso  50      0.000   0.000   0       0       0       0       0       [E:F]   756    
241     AIfDSo  55      1.432   1.871   100     4       0       0       177     [F:0]   36      
242     AIfDSo  55      1.632   1.807   114     3       0       0       171     [F:1]   72      
243     aifdso  51      0.000   0.000   0       0       0       0       0       [F:2]   756    
244     AIfDSo  55      1.761   1.575   123     4       0       0       149     [F:3]   0      
245     AIfDSo  55      1.775   1.733   124     0       0       0       164     [F:4]   42      
246     AIfDSo  55      1.933   1.881   135     2       0       0       178     [F:5]   0      
247     AIfDSo  55      1.847   1.892   129     2       0       0       179     [F:6]   21    
248     AIfDSo  55      1.747   1.797   122     1       0       0       170     [F:7]   0      
249     aifdso  50      0.000   0.000   0       0       0       0       0       [F:8]   756    
250     AIfDSo  55      1.904   1.924   133     2       0       0       182     [F:9]   0      
251     AIfDSo  55      1.675   1.786   117     2       0       0       169     [F:A]   0      
252     AIfDSo  55      1.432   1.776   100     5       1       0       168     [F:B]   72      
253     aifdso  50      0.000   0.000   0       0       0       0       0       [F:C]   756  
254     AIfDSo  55      2.090   1.860   146     1       0       0       176     [F:D]   0      
255     AIfDSo  55      1.689   1.934   118     3       0       0       183     [F:E]   72      
256     AIfDSo  55      1.804   1.913   126     0       0       0       181     [F:F]   36

F:      715     23.179  23.739  1619    26      0       0       13      0       3       (1.449/chip)    78%


I used the CPU speed as a marker for my personal notes for later review. The chips I set to aifdso 50 is the first wave of disabled chips that showed obvious problems. The ones set with 51 are for me to note my second wave of disabled chips.

Remember to only tweak the file after you have moved the cards to the more appropriate slots.
Remember to save the file to /opt/bitfury/best.cnf so that it will keep the changes you made to the file.

[jddebug]

check what your /opt/bitfury/proxy_pools.conf is set too.

I would consider also restarting the stratum server first before restarting the miner.

Yup I did all that and found that it didn't help.  I think there's a problem with the card.  Sometimes it hashes at regular rates, other times it stops hashing for some time.  It's like sometimes the chips are partially failing...

check also that the cards are properly seated in the socket. Also if you get any chips that are operating at sub 1.0 speed then set it to disabled and see if that helps.


type this in ssh console

nano /run/shm/.stat.log

scroll to the bottom by pressing page down and see if you have any bad or off chips that may have been detected by autotune.

If you do i start by disabling them to get the board working good.

Sitarow,

This is what mine displays. Looks like 5 bad and one off?

What would I look for now and how to disable?

speed:6710 noncerate[GH/s]:220.432 (1.722/chip) hashrate[GH/s]:237.606 good:15397 errors:860 spi-err:5 miso-err:0 jobs:322 cores:95% good:122 bad:5 off:1 (best[GH/s]:229.165) Tue Sep 10 01:42:09 2013
0:      825     29.936  31.836  2091    100     0       0       15      1       0       (1.871/chip)    95%
1:      880     31.081  33.083  2171    101     0       0       16      0       0       (1.943/chip)    100%
2:      880     28.146  30.821  1966    35      0       0       16      0       0       (1.759/chip)    98%
3:      770     26.285  29.690  1836    193     1       0       14      2       0       (1.643/chip)    86%
4:      770     25.641  28.031  1791    145     1       0       14      2       0       (1.603/chip)    92%
5:      825     29.664  31.286  2072    85      1       0       15      0       1       (1.854/chip)    93%
6:      880     21.289  22.873  1487    94      1       0       16      0       0       (1.331/chip)    97%
7:      880     28.390  29.986  1983    107     1       0       16      0       0       (1.774/chip)    99%

My other looks worse:

speed:7260 noncerate[GH/s]:203.467 (1.413/chip) hashrate[GH/s]:224.172 good:14212 errors:749 spi-err:6 miso-err:0 jobs:323 cores:89% good:132 bad:8 off:4 (best[GH/s]:212.257) Tue Sep 10 01:47:15 2013

First move the boards with 880 to the front of the line then the 825 ones and the 770 to the back.

so I would start with
Move 7 to 0 and put 0 on 4 and put 4 to 6
Move 6 to 7 as I think that one has chips that auto tune is still having troubles with.
Move 5 to 3 and 3 to 5.

After you do that then wait about 30 minutes, then run nano /run/shm/.stat.log

If you notice any chips pushing 0.600 or below turn them off by replacing AIfDSo to aifdso on the same line number as the chip. This is important because auto tuning will keep working with them if it can causing errors that may throw off some pools.

Note: I would only consider turning off auto tuning if I am in a temperature controlled environment where the ambient temperature is constant. OR if I am not as aggresive on my speed settings of the chips.

Below is an example of an "EOL" board that was included with my kit. I have simply turned off those chips but will be later cleaning the board with isopropyl alcohol to see if i can clear up some potential issues.

240     aifdso  50      0.000   0.000   0       0       0       0       0       [E:F]   756    
241     AIfDSo  55      1.432   1.871   100     4       0       0       177     [F:0]   36      
242     AIfDSo  55      1.632   1.807   114     3       0       0       171     [F:1]   72      
243     aifdso  51      0.000   0.000   0       0       0       0       0       [F:2]   756    
244     AIfDSo  55      1.761   1.575   123     4       0       0       149     [F:3]   0      
245     AIfDSo  55      1.775   1.733   124     0       0       0       164     [F:4]   42      
246     AIfDSo  55      1.933   1.881   135     2       0       0       178     [F:5]   0      
247     AIfDSo  55      1.847   1.892   129     2       0       0       179     [F:6]   21    
248     AIfDSo  55      1.747   1.797   122     1       0       0       170     [F:7]   0      
249     aifdso  50      0.000   0.000   0       0       0       0       0       [F:8]   756    
250     AIfDSo  55      1.904   1.924   133     2       0       0       182     [F:9]   0      
251     AIfDSo  55      1.675   1.786   117     2       0       0       169     [F:A]   0      
252     AIfDSo  55      1.432   1.776   100     5       1       0       168     [F:B]   72      
253     aifdso  50      0.000   0.000   0       0       0       0       0       [F:C]   756  
254     AIfDSo  55      2.090   1.860   146     1       0       0       176     [F:D]   0      
255     AIfDSo  55      1.689   1.934   118     3       0       0       183     [F:E]   72      
256     AIfDSo  55      1.804   1.913   126     0       0       0       181     [F:F]   36

F:      715     23.179  23.739  1619    26      0       0       13      0       3       (1.449/chip)    78%


I used the CPU speed as a marker for my personal notes for later review. The chips I set to aifdso 50 is the first wave of disabled chips that showed obvious problems. The ones set with 51 are for me to note my second wave of disabled chips.

Remember to only tweak the file after you have moved the cards to the more appropriate slots.
Remember to save the file to /opt/bitfury/best.cnf so that it will keep the changes you made to the file.

Sitarow, thank you. That as a very detailed reply that I was able to actually follow. I'll be working on it tomorrow.

Question: why move the boards position? I'm just curious.

[Sitarow]

check what your /opt/bitfury/proxy_pools.conf is set too.

I would consider also restarting the stratum server first before restarting the miner.

Yup I did all that and found that it didn't help.  I think there's a problem with the card.  Sometimes it hashes at regular rates, other times it stops hashing for some time.  It's like sometimes the chips are partially failing...

check also that the cards are properly seated in the socket. Also if you get any chips that are operating at sub 1.0 speed then set it to disabled and see if that helps.


type this in ssh console

nano /run/shm/.stat.log

scroll to the bottom by pressing page down and see if you have any bad or off chips that may have been detected by autotune.

If you do i start by disabling them to get the board working good.

Sitarow,

This is what mine displays. Looks like 5 bad and one off?

What would I look for now and how to disable?

speed:6710 noncerate[GH/s]:220.432 (1.722/chip) hashrate[GH/s]:237.606 good:15397 errors:860 spi-err:5 miso-err:0 jobs:322 cores:95% good:122 bad:5 off:1 (best[GH/s]:229.165) Tue Sep 10 01:42:09 2013
0:      825     29.936  31.836  2091    100     0       0       15      1       0       (1.871/chip)    95%
1:      880     31.081  33.083  2171    101     0       0       16      0       0       (1.943/chip)    100%
2:      880     28.146  30.821  1966    35      0       0       16      0       0       (1.759/chip)    98%
3:      770     26.285  29.690  1836    193     1       0       14      2       0       (1.643/chip)    86%
4:      770     25.641  28.031  1791    145     1       0       14      2       0       (1.603/chip)    92%
5:      825     29.664  31.286  2072    85      1       0       15      0       1       (1.854/chip)    93%
6:      880     21.289  22.873  1487    94      1       0       16      0       0       (1.331/chip)    97%
7:      880     28.390  29.986  1983    107     1       0       16      0       0       (1.774/chip)    99%

My other looks worse:

speed:7260 noncerate[GH/s]:203.467 (1.413/chip) hashrate[GH/s]:224.172 good:14212 errors:749 spi-err:6 miso-err:0 jobs:323 cores:89% good:132 bad:8 off:4 (best[GH/s]:212.257) Tue Sep 10 01:47:15 2013

First move the boards with 880 to the front of the line then the 825 ones and the 770 to the back.

so I would start with
Move 7 to 0 and put 0 on 4 and put 4 to 6
Move 6 to 7 as I think that one has chips that auto tune is still having troubles with.
Move 5 to 3 and 3 to 5.

After you do that then wait about 30 minutes, then run nano /run/shm/.stat.log

If you notice any chips pushing 0.600 or below turn them off by replacing AIfDSo to aifdso on the same line number as the chip. This is important because auto tuning will keep working with them if it can causing errors that may throw off some pools.

Note: I would only consider turning off auto tuning if I am in a temperature controlled environment where the ambient temperature is constant. OR if I am not as aggresive on my speed settings of the chips.

Below is an example of an "EOL" board that was included with my kit. I have simply turned off those chips but will be later cleaning the board with isopropyl alcohol to see if i can clear up some potential issues.

240     aifdso  50      0.000   0.000   0       0       0       0       0       [E:F]   756    
241     AIfDSo  55      1.432   1.871   100     4       0       0       177     [F:0]   36      
242     AIfDSo  55      1.632   1.807   114     3       0       0       171     [F:1]   72      
243     aifdso  51      0.000   0.000   0       0       0       0       0       [F:2]   756    
244     AIfDSo  55      1.761   1.575   123     4       0       0       149     [F:3]   0      
245     AIfDSo  55      1.775   1.733   124     0       0       0       164     [F:4]   42      
246     AIfDSo  55      1.933   1.881   135     2       0       0       178     [F:5]   0      
247     AIfDSo  55      1.847   1.892   129     2       0       0       179     [F:6]   21    
248     AIfDSo  55      1.747   1.797   122     1       0       0       170     [F:7]   0      
249     aifdso  50      0.000   0.000   0       0       0       0       0       [F:8]   756    
250     AIfDSo  55      1.904   1.924   133     2       0       0       182     [F:9]   0      
251     AIfDSo  55      1.675   1.786   117     2       0       0       169     [F:A]   0      
252     AIfDSo  55      1.432   1.776   100     5       1       0       168     [F:B]   72      
253     aifdso  50      0.000   0.000   0       0       0       0       0       [F:C]   756  
254     AIfDSo  55      2.090   1.860   146     1       0       0       176     [F:D]   0      
255     AIfDSo  55      1.689   1.934   118     3       0       0       183     [F:E]   72      
256     AIfDSo  55      1.804   1.913   126     0       0       0       181     [F:F]   36

F:      715     23.179  23.739  1619    26      0       0       13      0       3       (1.449/chip)    78%


I used the CPU speed as a marker for my personal notes for later review. The chips I set to aifdso 50 is the first wave of disabled chips that showed obvious problems. The ones set with 51 are for me to note my second wave of disabled chips.

Remember to only tweak the file after you have moved the cards to the more appropriate slots.
Remember to save the file to /opt/bitfury/best.cnf so that it will keep the changes you made to the file.

Sitarow, thank you. That as a very detailed reply that I was able to actually follow. I'll be working on it tomorrow.

Question: why move the boards position? I'm just curious.

Not sure if it helps with power distribution and potentially moving noisy bad chips away from good chips. However one thing I know for sure it makes it easy to detect problems as they will stand out and be more obvious. Also later on if you do happen to get better boards you can add them in place of the poor performing ones.

[superduh]

so which pool works best with bitfury ? people should have an idea by now
friend reporting huge difference between slushs pool and web panel

[zurg]

so which pool works best with bitfury ? people should have an idea by now
friend reporting huge difference between slushs pool and web panel

My Slashes pool went bonkers overnight... BF reporting ~38Gh/s with Slashes was just under 7Gh/s
Now all rebooting etc.. 38Gh/s at BF and 12.6Gh/s at Slashes.. grrrrr

[zurg]

1       AIfDSo  55      1.360   1.575   95      10      0       1       149     [0:0]   665     6 7 7 7 7 6 4 5 6 6 3 6 6 6 6 7         1 0 0 0 0 1 2 1 0 0 3 0 0 1 1 0
2       AIfDSo  55      1.374   1.501   96      6       0       0       142     [0:1]   665     6 6 5 6 5 5 6 6 7 6 6 7 7 6 6 6         0 0 1 0 1 1 0 1 0 1 1 0 0 0 0 0
3       AIfDSo  55      0.816   1.533   57      24      0       0       145     [0:2]   702     3 3 4 5 2 5 3 3 4 3 4 4 3 3 5 3         2 2 1 0 3 0 2 2 2 2 1 1 2 2 0 2
4       AIfDSo  55      1.432   1.543   100     8       0       0       146     [0:3]   660     7 5 6 7 7 7 7 7 6 6 5 7 6 6 5 6         0 2 1 0 0 0 0 0 1 1 2 0 0 0 1 0
5       AIfDSo  55      1.417   1.501   99      6       0       0       142     [0:4]   663     6 7 7 6 5 5 5 6 6 6 5 7 7 7 7 7         1 0 0 0 1 1 1 0 0 0 2 0 0 0 0 0
6       AIfDSo  55      1.074   1.522   75      10      0       0       144     [0:5]   686     4 6 2 5 5 5 5 5 4 5 4 4 4 6 6 5         2 0 3 0 0 0 0 0 1 0 1 1 1 0 0 1
7       AIfDSo  55      1.460   1.554   102     3       0       0       147     [0:6]   658     6 6 6 5 7 7 7 7 7 7 7 7 5 6 6 6         0 0 0 2 0 0 0 0 0 0 0 0 1 0 0 0
8       AIfDSo  55      1.475   1.501   103     8       0       0       142     [0:7]   658     6 7 6 7 7 7 7 7 6 6 7 6 6 6 6 6         1 0 1 0 0 0 0 0 1 1 0 1 0 1 1 1
9       AIfDSo  55      1.847   1.638   129     1       0       0       155     [0:8]   641     8 8 8 8 8 8 8 9 8 8 8 8 8 8 8 8         0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0
10      AIfDSo  55      1.632   1.607   114     8       0       0       152     [0:9]   647     8 7 7 7 8 7 6 7 6 7 7 8 8 7 7 7         0 1 1 1 0 0 1 0 1 0 0 0 0 1 1 1
11      AIfDSo  55      1.646   1.575   115     5       0       0       149     [0:A]   648     8 7 7 7 7 7 7 7 7 7 8 8 7 7 7 7         0 0 0 0 0 0 0 0 0 1 0 0 1 1 1 1
12      AIfDSo  55      1.403   1.501   98      3       0       0       142     [0:B]   669     6 5 6 6 6 6 6 6 5 7 6 7 7 7 6 6         0 1 0 0 0 0 0 0 1 0 1 0 0 0 0 0
13      AIfDSo  55      1.475   1.522   103     5       0       0       144     [0:C]   660     7 6 7 7 6 7 6 6 6 5 7 7 6 7 7 6         0 1 0 0 1 0 0 0 0 1 0 0 1 0 0 1
14      AIfDSo  55      1.432   1.564   100     6       0       0       148     [0:D]   664     6 5 6 6 6 6 5 6 7 7 7 7 7 7 6 6         1 1 0 0 0 0 1 1 0 0 0 0 0 0 1 1
15      AIfDSo  55      1.532   1.564   107     4       0       0       148     [0:E]   654     7 7 7 7 7 6 7 7 6 6 5 7 7 7 7 7         0 0 0 0 0 1 0 0 1 1 1 0 0 0 0 0
16      AIfDSo  55      1.646   1.554   115     5       0       0       147     [0:F]   648     7 6 6 7 8 8 8 8 8 8 7 7 7 7 7 6         0 1 1 1 0 0 0 0 0 0 1 0 0 0 0 1
17      AIfDSo  55      1.790   1.913   125     3       0       0       181     [1:0]   641     8 7 8 8 8 8 8 8 8 8 8 8 8 7 8 7         0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 1
18      AIfDSo  55      2.004   2.082   140     3       0       0       197     [1:1]   631     9 8 9 8 9 9 9 9 9 8 9 9 9 9 9 8         0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 1
19      AIfDSo  55      1.804   1.850   126     4       0       0       175     [1:2]   642     8 8 7 8 8 8 8 8 8 8 8 8 7 8 8 8         0 0 1 0 0 0 0 1 1 0 0 0 1 0 0 0
20      AIfDSo  55      2.248   1.924   157     4       0       0       182     [1:3]   615     10 10 10 9 10 10 8 10 10 11 10 10 9 10 10 10    0 0 0 1 0 0 2 0 0 0 0 0 1 0 0 0
21      AIfDSo  55      1.689   1.955   118     3       0       0       185     [1:4]   645     8 8 8 8 7 8 7 8 7 7 7 7 7 7 7 7         0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 1
22      AIfDSo  55      1.546   1.638   108     9       0       0       155     [1:5]   654     6 5 6 7 6 7 7 8 7 8 8 7 7 6 7 6         1 2 1 0 1 0 0 0 1 0 0 1 0 1 0 1
23      AIfDSo  55      1.646   1.903   115     2       0       0       180     [1:6]   656     7 7 7 7 7 7 7 7 7 7 7 8 7 7 8 8         0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0
24      AIfDSo  55      2.004   1.892   140     5       0       0       179     [1:7]   628     9 9 8 9 9 9 9 9 8 10 6 9 9 9 9 9        0 0 1 0 0 0 0 0 1 0 3 0 0 0 0 0
25      AIfDSo  55      0.000   2.072   0       0       0       0       196     [1:8]   756     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:1375 noncerate[GH/s]:37.753 (1.510/chip) hashrate[GH/s]:41.983 good:2637 errors:145 spi-err:0 miso-err:1 jobs:371 cores:13% good:25 bad:0 off:0 (best[GH/s]:0.000) Tue Sep 10 11:24:38 2013
0:      880     23.021  24.754  1608    112     0       1       16      0       0       (1.439/chip)    12%
1:      495     14.732  17.229  1029    33      0       0       9       0       0       (1.637/chip)    14%


Who can decipher this? I am clueless right now as to what I should even be looking at, lol.