[ANN] Bitfury ASIC sales in EU and Europe

[ktbken]

#51x Tracking number received
Way to go

[Isokivi]

#51x Tracking number received
Way to go

Thats odd: 47X Processing.

[ktbken]

#51x Tracking number received
Way to go

Thats odd: 47X Processing.

Is yours a full kit? mine is a starter with a few extra cards

[vvhiteknight]

57x still processing...ordered starter kit and 13 hashing boards.

[punin]

Update:

We're progressing through orders in more or less consecutive fashion. We're now finishing late 400's and well into 500's. Some orders take more time to prepare, which is causing non-consecutive completion.

Thank you to all of you who chose to stay with us. We're working hard to deliver your gear in time. And as we used to say in Finnish Demo-scene "fuckings to lamers" (who cancel their order after we put so much work and effort into producing it on time as promised.) You're not many, and you won't be missed nor served in the future.

P.S. There are 2 satoshi -related easter eggs hidden in both our hardware and software. Can you find them? First to post both gets a FREE H-card, so don't post if you find only 1!

[jlsminingcorp]

Update:

We're progressing through orders in more or less consecutive fashion. We're now finishing late 400's and well into 500's. Some orders take more time to prepare, which is causing non-consecutive completion.

Thank you to all of you who chose to stay with us. We're working hard to deliver your gear in time. And as we used to say in Finnish Demo-scene "fuckings to lamers" (who cancel their order after we put so much work and effort into producing it on time as promised.) You're not many, and you won't be missed nor served in the future.

P.S. There are 2 satoshi -related easter eggs hidden in both our hardware and software. Can you find them? First to post both gets a FREE H-card, so don't post if you find only 1!

"fuckings to lamers" - nice saying! Not to be confused with "fucking the llamas", which is a bit different .

We're still with you Punin, you guys are doing an awesome job . Consistently delivering what you promised (and more) when you promised it (if not a bit earlier) - what more can you say.

[Spathi]

Update:

We're progressing through orders in more or less consecutive fashion. We're now finishing late 400's and well into 500's. Some orders take more time to prepare, which is causing non-consecutive completion.

Thank you to all of you who chose to stay with us. We're working hard to deliver your gear in time. And as we used to say in Finnish Demo-scene "fuckings to lamers" (who cancel their order after we put so much work and effort into producing it on time as promised.) You're not many, and you won't be missed nor served in the future.

P.S. There are 2 satoshi -related easter eggs hidden in both our hardware and software. Can you find them? First to post both gets a FREE H-card, so don't post if you find only 1!

Don't let the cancelers get you down, there will always be some people who order just in case they want it then cancel last minute.

Very much looking forward to receiving my order (although sucks to have a large order #)
Hopefully the two easter eggs wont be found before then!

[klondike_bar]

i just made a mistake with my h-board best.cnf file, and i may have saved the first chip to "545" instead of "54" because on reboot it read as 136 and 0.000 hashrate.

i fixed it to 54 and rebooted but the chip still appears unresponsive. any advice or tips? looks like voltage is still going to the chip, so did i ruin the chip or is it salvagable?

I would hate to think i accidentally crapped out the chip with this tuning attempt

[shapemaker]

i just made a mistake with my h-board best.cnf file, and i may have saved the first chip to "545" instead of "54" because on reboot it read as 136 and 0.000 hashrate.

i fixed it to 54 and rebooted but the chip still appears unresponsive. any advice or tips? looks like voltage is still going to the chip, so did i ruin the chip or is it salvagable?

I would hate to think i accidentally crapped out the chip with this tuning attempt

Don't worry, you can always remove it with a belt sander

[spiccioli]

i just made a mistake with my h-board best.cnf file, and i may have saved the first chip to "545" instead of "54" because on reboot it read as 136 and 0.000 hashrate.

i fixed it to 54 and rebooted but the chip still appears unresponsive. any advice or tips? looks like voltage is still going to the chip, so did i ruin the chip or is it salvagable?

I would hate to think i accidentally crapped out the chip with this tuning attempt

Chainminer code does not let you set a speed higher than 57, so your chip should be ok.

spiccioli

[klondike_bar]

i just made a mistake with my h-board best.cnf file, and i may have saved the first chip to "545" instead of "54" because on reboot it read as 136 and 0.000 hashrate.

i fixed it to 54 and rebooted but the chip still appears unresponsive. any advice or tips? looks like voltage is still going to the chip, so did i ruin the chip or is it salvagable?

I would hate to think i accidentally crapped out the chip with this tuning attempt

Chainminer code does not let you set a speed higher than 57, so your chip should be ok.

spiccioli

hmm so why would it show as 136 in .stat.log? like i said, its now no longer hashing. would using autotune or a set value other then 54 get the chip back up to operation?

EDIT: well shit, apparently whatever happened it changed "aIDSo" to "aidso" which would effectively have caused the issue - i just changed it back and am restarting the system now.

[spiccioli]

i just made a mistake with my h-board best.cnf file, and i may have saved the first chip to "545" instead of "54" because on reboot it read as 136 and 0.000 hashrate.

i fixed it to 54 and rebooted but the chip still appears unresponsive. any advice or tips? looks like voltage is still going to the chip, so did i ruin the chip or is it salvagable?

I would hate to think i accidentally crapped out the chip with this tuning attempt

Chainminer code does not let you set a speed higher than 57, so your chip should be ok.

spiccioli

hmm so why would it show as 136 in .stat.log? like i said, its now no longer hashing. would using autotune or a set value other then 54 get the chip back up to operation?

Try to switch-off you rig for a little time, 30 seconds-1 minute, then restart it.

You can also try to set all the chips of that board to

Code:

aIfDSo   55

and see if it starts hashing again.

Did you move your board from its slot?

spiccioli

[klondike_bar]

^see my edit to the post. turns out whatever switched it from 54[5] -> 136  also changed the aIfDSo -> aifdso

i returned it to the capitalised form and its active again     waiting for hashrate to climb and stabilize right now

[punin]

Did I mention we have delicious pizza for sale? Immediate delivery

[Spathi]

Did I mention we have delicious pizza for sale? Immediate delivery

Tasty Tasty Pizza.

[spiccioli]

^see my edit to the post. turns out whatever switched it from 54[5] -> 136  also changed the aIfDSo -> aifdso

i returned it to the capitalised form and its active again     waiting for hashrate to climb and stabilize right now

Good to know!

Because I was wrong, it reads what it finds!

Autotune does not go higher than 57, but during startup it reads what you have in your file, than it passes it to the function that programs chips and there I'm not sure it does not try to set it faster than 57, I have to spend some more time inside that code ...



spiccioli

[malignus]

Congratulations to the BFSB-Team for precisely meeting their delivery time  I guess this October a mining hardware manufacturer will have shipped all their orders within "two weeks".

Can I assume your customer service is a bit stressed out in the moment, because of all the shipping? Last week I was used to receive an answer within minutes or a few hours, but now I am waiting since friday for the confirmation of a refund. Punin, could you give an estimate on the response time for e-mail inquiries at the moment?

Thank you.

[Spathi]

Congratulations to the BFSB-Team for precisely meeting their delivery time  I guess this October a mining hardware manufacturer will have shipped all their orders within "two weeks".

Can I assume your customer service is a bit stressed out in the moment, because of all the shipping? Last week I was used to receive an answer within minutes or a few hours, but now I am waiting since friday for the confirmation of a refund. Punin, could you give an estimate on the response time for e-mail inquiries at the moment?

Thank you.

About a week ago the wait was about 9 days for an email.

I dunno whether this is still true or whether the email backlog is cleared.

[malignus]

Congratulations to the BFSB-Team for precisely meeting their delivery time  I guess this October a mining hardware manufacturer will have shipped all their orders within "two weeks".

Can I assume your customer service is a bit stressed out in the moment, because of all the shipping? Last week I was used to receive an answer within minutes or a few hours, but now I am waiting since friday for the confirmation of a refund. Punin, could you give an estimate on the response time for e-mail inquiries at the moment?

Thank you.

About a week ago the wait was about 9 days for an email.

I dunno whether this is still true or whether the email backlog is cleared.

It seems like it isn't at the moment, but last week the CS team responded rapidly.

[punin]

Congratulations to the BFSB-Team for precisely meeting their delivery time  I guess this October a mining hardware manufacturer will have shipped all their orders within "two weeks".

Can I assume your customer service is a bit stressed out in the moment, because of all the shipping? Last week I was used to receive an answer within minutes or a few hours, but now I am waiting since friday for the confirmation of a refund. Punin, could you give an estimate on the response time for e-mail inquiries at the moment?

Thank you.

We will process refunds after we process orders.