[ANN] Bitfury ASIC sales in EU and Europe

[dani]

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 guess I'm just very unlucky, ordering 50gh and receiving 45gh..    

I changed i to I, d to D, in every possible way, no way to turn on 38 or any later chip..
Thank you guys for your help, I will try to fire up the 2nd masterboard with the faulty hcard and another psu, but my hopes are already crushed.

Right now its hashing with 20gh, what the..

[WynX]

I guess I'm just very unlucky, ordering 50gh and receiving 45gh..    

I changed i to I, d to D, in every possible way, no way to turn on 38 or any later chip..
Thank you guys for your help, I will try to fire up the 2nd masterboard with the faulty hcard and another psu, but my hopes are already crushed.

Right now its hashing with 20gh, what the..

Have you checked for bad soldering on that particular board? Also the underside of the M-card?
See for ref pics: http://imgur.com/a/t3AKx

EDIT: especially the I/O pins shorting on that chip 38 would match that behaviour (if you can locate it?)

[Micky25]

My opinion: we should be happy having received anything at all  

[tccd]

I have one suspicious chip too:

http://img28.imageshack.us/img28/8028/ojwe.png

Look at number 16 on board 1. Just tried spiccioli's 50 value but the noncerate is still 0 for this chip.

[dani]

I'm not giving up on this so easily. I seperated that faulty board and put it on a m-board as a single. Strange thing:



it just works "fine" (by all means) except for 3 chips, I don't care right now.

Even more strange? The two hboards left on the first mboard perform badly, one between 10 and 15 and the other around 10-12. I saw both hashing at >20 happily before.

I also checked the mboards for soldering issues, they look pretty clean, no problems. I'll try to put the other two hboards one by one to the second master board, let's see how this works out. Maybe its a faulty mboard after all?

Edit:
Did that. Getting around 18gh + 18gh on the 2nd mboard and 19gh on the single left on the original mboard. Anyone else finds this interesting? 
They still do a pretty bad job compared to others I've seen. But a little tuning should help, right Mxrider? 

[Meizirkki]

I'm not giving up on this so easily. I seperated that faulty board and put it on a m-board as a single. Strange thing:



it just works "fine" (by all means) except for 3 chips, I don't care right now.

Even more strange? The two hboards left on the first mboard perform badly, one between 10 and 15 and the other around 10-12. I saw both hashing at >20 happily before.

I also checked the mboards for soldering issues, they look pretty clean, no problems. I'll try to put the other two hboards one by one to the second master board, let's see how this works out. Maybe its a faulty mboard after all?

or a bad raspi, maybe? Those things corrupt memorycards a lot, you might want to check that too

[MXRider]

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 guess I'm just very unlucky, ordering 50gh and receiving 45gh..    

I changed i to I, d to D, in every possible way, no way to turn on 38 or any later chip..
Thank you guys for your help, I will try to fire up the 2nd masterboard with the faulty hcard and another psu, but my hopes are already crushed.

Right now its hashing with 20gh, what the..

Change it to  "aIfDSo 54". Every letter has it's own meaning so you can't try upper and lower case letters randomly. I,D and S need to be on (CAPS = on).

Some chips are just bad or even dead. I have some bad ones too. Great thing in Bitfury's gear is that other chips hash faster if one is turned off/dead.

[MXRider]

I have one suspicious chip too:



Look at number 16 on board 1. Just tried spiccioli's 50 value but the noncerate is still 0 for this chip.

Just turn it off by setting the speed to zero.. That will help other chips to perform better.

[Micky25]

stable since hours



these pals need love and a cosy environment

[darkfriend77]

... runnning in the case ...

[Syke]

... runnning in the case ...

Very nice.

[punin]

... runnning in the case ...

Mmmm... red light district.. We had some nice asian food there with Intron and Cscape

[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

During the night, the half-dead card got worse, now it is at 5 GH/s with a little more than 1/4 of the chips still mining.

I've already removed auto-tuning, but it had no effect, even chips that yesterday night were mining now show 0.

This afternoon I'll start visually inspecting all the cards to see if I have soldering defects.

spiccioli

[k. naata]

I have found that the best config is to set everything to:
aIfDSo 56

and don't care about errors. With higher speed even the bad chips find nonce sometimes.

Also setting speed to same with every chip in one bank seems to be better than setting them individually.

[Isokivi]

I have found that the best config is to set everything to:
aIfDSo 56

and don't care about errors. With higher speed even the bad chips find nonce sometimes.

Also setting speed to same with every chip in one bank seems to be better than setting them individually.

For me this produces about 2Ghs loss (49.x to 47.x Gh/s) when compared to the hand tuned configuration, "noncerateperchip": seems to stay 60-80 lower than what I allready had.

[dani]

I don't want to spam this thread, but maybe others have similar difficulties, so I don't know any better place yet to post.

Anyway, I switched the last (good) hboard to the other two that didnt perform so well (16gh each), and the magic happend: 60gh coming out of these babies. Nice. Same settings for the first 32 chips (with autotune off, I tweaked it a little bit last night, but with not too good results). The third board is autotune on, performing 17.452GH/s, 19.9GH/s, 23.336GH/s. Still some more tweaking to be done, but I'm fine for now

Also I received another starterkit for my friend (who somehow managed to go on vacation) and plugged those two right into the first mboard. Working fine: 24.796GH/s and 20.845GH/s

Update:


3 Hboards, 1 mboard. swining between 60 and 65gh as seen here http://eligius.st/~wizkid057/newstats/userstats.php/14cbUKDLpZPJUMfr3DcKWZXmiaQRYpaZbd

[BTstarter]

Anyway, I switched the last (good) hboard to the other two that didnt perform so well (16gh each), and the magic happend: 60gh coming out of these babies. Nice. Same settings for the first 32 chips (with autotune off, I tweaked it a little bit last night, but with not too good results). The third board is autotune on, performing 17.452GH/s, 19.9GH/s, 23.336GH/s. Still some more tweaking to be done, but I'm fine for now

60 GH/s? Whats your exact settings for this?

[cimpex]

always post your settings too. thanks!

[Isokivi]

Anyway, I switched the last (good) hboard to the other two that didnt perform so well (16gh each), and the magic happend: 60gh coming out of these babies. Nice. Same settings for the first 32 chips (with autotune off, I tweaked it a little bit last night, but with not too good results). The third board is autotune on, performing 17.452GH/s, 19.9GH/s, 23.336GH/s. Still some more tweaking to be done, but I'm fine for now

60 GH/s? Whats your exact settings for this?

3 H-boards.

[dani]

I think they want to see the .stat.log, I will update my post shortly, did just a reboot to check if turning faulty chips (0 nonce, >1000 errors) off by switching from I to i, but this brought many chips offline. strg+z and now no chips working, needed to stop/start miner, ramping up again.