[ANN] Bitfury ASIC sales in EU and Europe

[achimsmile]

Dani I hope you'll be able to solve the problem soon!

Ok now, noob alarm!  I'm here 
I'm not good with ssh, so I ask you guys if I'm doing this right:

I login as pi, go to the stat.log file and edit it with "pico .stat.log". I don't have write permission when editing it. Did I do ok so far?

Now I see 3 chips that are shut down:

11      AIfDSo  0 
16      AIfDSo  0 
20      AIfDSo  0

and I set that to a(=Autotune off) 54(=Speed)

11      aIfDSo  54
16      aIfDSo  54
20      aIfDSo  54

Now I want to save the file to /opt/bitfury/best.cnf

I press Ctrl+X, and it asks me if I want to save the file. I change the name to best.cnf

Ok now the embarassing question: How can I save it in the right directory?.... yes I'm really that bad at it.

After that I would just restart the miner and the chips should come to life?

Thank you for helping me out!

[Micky25]

dani, you mine on a pool? What's your difficulty?

[-Redacted-]

change the file name to /opt/bitfury/best.cnf

The chips may or may not come back to life.  Depends.

[MXRider]

Dani I hope you'll be able to solve the problem soon!

Ok now, noob alarm!  I'm here  
I'm not good with ssh, so I ask you guys if I'm doing this right:

I login as pi, go to the stat.log file and edit it with "pico .stat.log". I don't have write permission when editing it. Did I do ok so far?

Now I see 3 chips that are shut down:

11      AIfDSo  0  
16      AIfDSo  0  
20      AIfDSo  0

and I set that to a(=Autotune off) 54(=Speed)

11      aIfDSo  54
16      aIfDSo  54
20      aIfDSo  54

Now I want to save the file to /opt/bitfury/best.cnf

I press Ctrl+X, and it asks me if I want to save the file. I change the name to best.cnf

Ok now the embarassing question: How can I save it in the right directory?.... yes I'm really that bad at it.

After that I would just restart the miner and the chips should come to life?

Thank you for helping me out!

Here is how I tune my chips manually:

- SSH into Pi (login "pi" password "raspberry").
- type "sudo nano /run/shm/.stat.log"
- I'll edit the file and when done, press Ctrl+X
- It will ask "Save modified buffer" and I press Y as in yes.
- Now it says "File Name to Write: /run/shm/.stat.log". Just erase the whole file name with backspace and type "/opt/bitfury/best.cnf" and hit Enter.
- type "sudo reboot"

[achimsmile]

aaah now I see! I have to enter the whole directory for "File Name to Write"!

Thank you MXRider and -Redacted-!!

Now I can play around with the values!

[mr_rulezzz]

Here is how I tune my chips manually:

- SSH into Pi (login "pi" password "raspberry").
- type "nano /run/shm/.stat.log"
- I'll edit the file and when done, press Ctrl+X
- It will ask "Save modified buffer" and I press Y as in yes.
- Now it says "File Name to Write: /run/shm/.stat.log". Just erase the whole file name with backspace and type "/opt/bitfury/best.cnf" and hit Enter.
- type "sudo reboot"

what exactly did you edit?

"2   AIfDSo   55   1.432   1.596   100   1   0   0   151   [0:1]   227   6 6 6 6 6 7 6 7 7 7 6 6 6 6 6 6    0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0" 

--- good chip

"14   aifdso   54   0.000   0.000   0   0   0   0   0   [0:D]   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 "

--- bad chip

"31   AIfDSo   52   0.616   1.216   43   39   0   0   115   [4:E]   482   3 2 2 3 2 2 1 4 4 3 4 3 3 3 2 2    2 3 3 2 3 3 4 1 1 3 2 2 2 2 3 3"

--- whats wrong with him?

[Micky25]

my stuff runs steady at 65 GH/s. 1 M and 3 H-boards. Pool at diff. 16. No direct air flow. Check proper seating of the hashing boards, this seems error-prone.

[MXRider]

I'm raising or lowering the speed of the chips, depending on the number of errors. I have also turned off the autotune. The point of manual tuning is that it works a little bit better than autotune.

Let's take the first chip as an example. Autotune is on (AIfDSo). It can be turned off by changing the capital A to a normal a (aIfDSo). Now the chip will always run at the speed you have set. Current speed is 55. Minimum is 52 and maximum is 57, higher the better of course. In this case I would raise the speed to 56 since there are practically no errors.

Chip two: change the "aifdso" to "aIfDSo" and let's see how it does (it won't work at all with aifdso).

Chip three: Something wrong with it. Turn off the autotune and keep the speed at 52. At least this is what I would do because 0,6 GH/s is still better than 0.

More info here http://punin.com/README_BFSB_v0.1.txt

[Isokivi]

Let's take the first chip as an example. Autotune is on (AIfDSo). It can be turned off by changing the capital A to a normal a (aIfDSo). Now the chip will always run at the speed you have set. Current speed is 55. Minimum is 52 and maximum is 57, higher the better of course. In this case I would raise the speed to 56 since there are practically no errors.

In my (limited) experience there is no sweet spot between 1 and 10+ errors. I've only been raising the speed on chips that constantly have 0 errors. This ofcourse is something that should be discussed more. Whats the efective hashing speed gain when raising one chip by 1 ? ..and subsequently whats the error persentage that justifies the gain ?

I would collect a sample on it myself, but am for now in the middle of trying to find a correlation between temperature, noncerate and errors.

[mr_rulezzz]

I'm raising or lowering the speed of the chips, depending on the number of errors. I have also turned off the autotune. The point of manual tuning is that it works a little bit better than autotune.

Let's take the first chip as an example. Autotune is on (AIfDSo). It can be turned off by changing the capital A to a normal a (aIfDSo). Now the chip will always run at the speed you have set. Current speed is 55. Minimum is 52 and maximum is 57, higher the better of course. In this case I would raise the speed to 56 since there are practically no errors.

Chip two: change the "aifdso" to "aIfDSo" and let's see how it does (it won't work at all with aifdso).

Chip three: Something wrong with it. Turn off the autotune and keep the speed at 52. At least this is what I would do because 0,6 GH/s is still better than 0.

More info here http://punin.com/README_BFSB_v0.1.txt

thank you very much! =) ... (every time i fall in this trap, read teh fckn manual)

[arorts]

Sorry for the delay guys.. Lot's of things happening here..

Here are photos of some of the soldering issues we've encountered. Please check your boards!

Thanks for the heads-up, Punin!

Just to get a feel of how likely I'll run into this issue, approx what percentage of boards are having this issues?

[dani]

dani, you mine on a pool? What's your difficulty?

Yes, on eligius, set the difficulty to 32 over there before i left the house, seems like it didnt change anything. I'll be home in 30mins, then i can check it.

Can i put the third card inti c2 oder D1? Maybe the card has an issue with the pins?

[Micky25]

maybe you want to try 16. This seems to work nice for me.

[mr_rulezzz]

sooo ... now i have chip.cnf with not tuned lines in and best.cnf with auto tune on selected chips only ... i start from webface new ... which cnf ist now in use?

[dani]

No, not that much.

Could you post another picture (or a link to that picture) of the .stat.log -file. I'm pretty sure you have autotune on and several chips are turned off.

sure, here we go:

https://i.imgur.com/pqaq5Qo.png

[Micky25]

Can i put the third card inti c2 oder D1? Maybe the card has an issue with the pins?

the h-boards should work in any slot, but optimal in a1 b1 c1 d1. Probably its only some kind of voodoo.

[Isokivi]

No, not that much.

Could you post another picture (or a link to that picture) of the .stat.log -file. I'm pretty sure you have autotune on and several chips are turned off.

sure, here we go:

https://i.imgur.com/pqaq5Qo.png

Im not entirely sure, but I'd say that chip 38 is dead and since they are chained any chips beyond it will not function.

[Micky25]

I would try different slots and make sure the boards sit really good. But probably Isokivi is right. I'm no pro.

[spiccioli]

Im not entirely sure, but I'd say that chip 38 is dead and since they are chained any chips beyond it will not function.

I have a h-card with chips 7-16 inclusive which are dead, chip 16 barely hashes setting its speed at 50, but throws a ton of miso-errors.

spiccioli

[spiccioli]

Im not entirely sure, but I'd say that chip 38 is dead and since they are chained any chips beyond it will not function.

I have a h-card with chips 7-16 inclusive which are dead, chip 16 barely hashes setting its speed at 50, but throws a ton of miso-errors.

spiccioli

I know that speed range should be 52-57 but I've found that I can go as low as 50 when I have a problematic chip, see this for example

Code:

24	aIfDSo	50	0.786	1.250	52	39	0	0	112	[4:7]	707	2 3 4 4 2 2 2 2 4 4 4 3 3 4 5 4 	4 3 2 2 3 3 3 3 1 2 2 3 3 2 1 2 

spiccioli