Pages:
Author

Topic: [ANN] Bitfury ASIC sales in EU and Europe - page 47. (Read 250482 times)

sr. member
Activity: 378
Merit: 250
Hehe Punin no offence here, but after the announcement of a lot better than expected performance KNC 28nm chip you begin  55nm chips sale started.
All we  known that soon BF chip will be worth a penny.
I'm very curious what we see here http://avalon-asics.com/

they are trying to squeeze the maximum of btc from you guys

this is called greed in clear language

and as i said to bitfury when he decided not to respect  his comitment,noone will go far with this type of behaviour

sr. member
Activity: 259
Merit: 250
Dig your freedom
Hehe Punin no offence here, but after the announcement of a lot better than expected performance KNC 28nm chip you begin  55nm chips sale started.
All we  known that soon BF chip will be worth a penny.
I'm very curious what we see here http://avalon-asics.com/
legendary
Activity: 1148
Merit: 1001
things you own end up owning you
Punin ! any news on when you will have stock again ? as I understood you will be shipping from stock when you are open for ordering, did I got that right ?


legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
^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  Cheesy   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 ...

Smiley

spiccioli

well as i said, theres no way i set 136 as the timing value. I was changing it from 55 to 54, so 554 or 545 are the conceivable saved numbers. how it uncapitalised the aifdso command i have not a clue - failsafe perhaps?
newbie
Activity: 19
Merit: 0
Congratulations to the BFSB-Team for precisely meeting their delivery time  Grin 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.

Thanks for you answer. I just wasn't sure whether you even received my mail or not, because I was used to shorter response times. But when you say that at this time longer response times are normal, I'll be calm.
I was a little nervous, because I originally received the refund in BTC, then determined that this sum was not the equivalent to the paid sum in Euro, and then sent the BTC back with Niko's agreement to now receive the refund via SEPA.
hero member
Activity: 560
Merit: 500
hero member
Activity: 560
Merit: 500
Congratulations to the BFSB-Team for precisely meeting their delivery time  Grin 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.
newbie
Activity: 19
Merit: 0
Congratulations to the BFSB-Team for precisely meeting their delivery time  Grin 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.
newbie
Activity: 50
Merit: 0
Congratulations to the BFSB-Team for precisely meeting their delivery time  Grin 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.
newbie
Activity: 19
Merit: 0
Congratulations to the BFSB-Team for precisely meeting their delivery time  Grin 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.
legendary
Activity: 1379
Merit: 1003
nec sine labore
^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  Cheesy   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 ...

Smiley

spiccioli
newbie
Activity: 50
Merit: 0
Did I mention we have delicious pizza for sale? Immediate delivery Smiley

Tasty Tasty Pizza.
hero member
Activity: 560
Merit: 500
Did I mention we have delicious pizza for sale? Immediate delivery Smiley

legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
^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  Cheesy   waiting for hashrate to climb and stabilize right now
legendary
Activity: 1379
Merit: 1003
nec sine labore
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 Sad

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

legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
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 Sad

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.

legendary
Activity: 1379
Merit: 1003
nec sine labore
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 Sad

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

spiccioli
full member
Activity: 238
Merit: 100
I run Linux on my abacus.
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 Sad

Don't worry, you can always remove it with a belt sander Grin
legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
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 Sad
newbie
Activity: 50
Merit: 0
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! Wink

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!
Pages:
Jump to: