 Show Posts
|
|
Pages: [1] 2 3 »
|
COOL!
so are you mining solo? or so you mean you found the block somehow through slushs pool?
No, found it as part of the pool effort. It's the first time they've found one, quite chuffed |
|
|
|
Just noticed that one of my miners found a block; 313457. That's the first block I've found  and I've been mining since March |
|
|
|
|
Just hope this marathon run of a block find will be followed by lots of < 1 hour block finds to make up.
|
|
|
|
REFUNDS?  I keep asking this as well, but Bitmaintech are very quiet. I have even sent them a message on my Bitmaintech account, but no reply!!!!! |
|
|
|
|
I switched my S1's off as I needed the PSU to test a motherboard, and noticed how quiet the S3's are. Very quiet. S1's now hashing again.
|
|
|
|
OK, so one of my new S3 machines is hashing at 402.75Gh/s. Frequency is 218.75. One of the strings (if that is the word) is showing oooooxo-. Rebooting through the web interface, or physically power cycling doesn't fix it. Reading through this thread the suggestions are
1) Downclock to 212
2) Update firmware
3) Dismantle and replace thermal compound
Which of these is most likely to fix the hashing? Is there anything else I should try?
I've noticed that you can have the odd x in the ASIC status and either switch completely off and then after a minute switch back on at the PSU and when booted up occasionally the ASIC status 'x's will have gone or sometimes they disappear after running for a few hours say 12 hours. |
|
|
|
My 4 s3's are 'out for delivery' but I havn't paid the VAT yet (20%) Hopefully they'll deliver them with no import costs  They wont. UPS will collect payment for VAT when delivery takes place. Ah  When my two S3s were delivered I had to pay £122.65 for import duty and UPS handling charge. |
|
|
|
@ bitmain Please tell me how to get rid of the following issue: The web interface only shows this on startup: /usr/lib/lua/luci/dispatcher.lua:582: bad argument #1 to ´pairs´ (table expected, got nil)
[C]: in function ´pairs´
/usr/lib/lua/luci/dispatcher.lua:582: in function `createtree`
/usr/lib/lua/luci/dispatcher.lua:230: in function `dispatch`
/usr/lib/lua/luci/dispatcher.lua:195: in function </ursr/lib/lua/luci/dispatcher.lua:194> Have you attempted a complete shutdown and startup? Switch the PCI-e cables around or use 4 cables. |
|
|
|
|
I still haven't received my 7.7% BTC refund. Has anyone else received theirs yet? Come on Bitmaintech, you expect payment for orders within an hour but when it comes to a small refund we have to wait weeks. BTC is supposed to be instant.
|
|
|
|
|
What does a - mean in the ASIC status? My ASIC status on second S3 is now:
00000000 00000000
00000000 00000-00
How do you identify which chip it is?
|
|
|
|
|
Those of us who opted for a 7.7% refund on our B1-B3 S3 purchases, why have we not received the refund in our BTC wallets yet? When we buy Antminers Bitcointech expect payment to reach them within an hour.
|
|
|
|
Received my S3's today and set them up this evening. The first one has no lines in the 'ASIC status' but the second one has a single line in it's 2nd 'ASIC status':
00000000 00000000
00000000 000000-0
Both are running off an EVGA 1300 Gold PSU using two PCI-e cables each.
I took the lid off the second S3 and took the heat-sinks off and cleaned up all chips re-applied a small dot of thermal CPU paste, reassembled and the 'ASIC status' was initially all clear and then after a couple of reboots the line re-appeared in the 'ASIC status'. Any suggestions?
The first S3 has ~421 and ~420 GHs running at stock frequency of 218.75.
The second S3 has ~475 and ~419 GHs running at same stock frequency.
They've only been running for half an hour.
you can reboot the second one with the gui reboot option. if the _ sticks change the freq to 212.5 both of my miners won't mine well at 218.75 they have 1 or 2 constant _ but both are good at 212.5 I changed the second S3 to operate at freq of 212.5 and still have a '-' in the ASIC status!! I have one of those too. Or had. Yesterday when I got the miners I had it come back several times. A reboot would sometimes make it go away or change to an x but it kept coming back. First thing I did with both miners was try them at various freq but neither of them seemed to like OC very much. Hashrate was marginally better at each step but HW errors were a lot higher on both at any OC. I did try downclock also but it did not make the - go away and made the hash rate even more pathetic. Neither of my miners pull 441 Ghs at stock freq. Yesterday I took off the heat sinks for the one with the bad chip and the chips were not drenched in thermal paste as some people have seen, but actually seemed like they could have used a little more. I was pretty meticulous about putting it on the entire surface of each chip without a lot of extra (and cleaning it up on the sides where it did run off and pool a little). But even after that it was getting the -. But yesterday after having done that thermal paste cleanup I OC'd to 225 and left it for the night. What I noticed this morning was that the HW errors were much improved compared to when I first unboxed them - I thought it might be due to the cleanup of the thermal paste but it could also have been that bad chip being presumably left out of the loop (since it had a dash all night) so I thought maybe it had been the source of the HW errors before. So thinking to try and nudge it closer to the 441 advertised hash rate I bumped it up to 237.5 freq this morning. Now it is actually just getting 441 but the problematic chip has also been showing an o ever since also. I doubt it is really fixed but I am happy about the hashrate for now. But I won't be shocked if the chip shows an x after the next reboot either. As long as I get 441 out of it though I'll live with it. I also took off the heatsinks on my other miner since it also wasn't pulling 441. That one actually looked like it had a good job of thermal paste on both sides. No huge voids and not a ton dripping off the sides. But it still had a little bit pooled on one side or another of a couple chips. Again I was real meticulous about getting it just right and cleaning up the excess and lo and behold that one is suddenly working great at 250 freq with minimal HW errors. It's pulling 501 Ghs ave at 3 hours now. That one was a little weird though too, the 237.5 freq actually lowered the hash rate to about 400 so I was actually pretty surprised to see what happened at 250. I was pretty bummed with both of them yesterday but I am happier about it today with the one pulling such a high hash rate and the other at least making the advertised 441. I run them both with fans at full (blue wires disconnected) and covers off in a server room (ambient temps maintained below 70 Fahrenheit). The temps in the GUI are all mid 30's. I switched the PCI-e cables to the two rear sockets and the - in the ASIC status went. Are you using 4 PCI-e cables per S3? I am using 4 yes. I increased the freq and then got an x in the ASIC status, so took freq back to stock of 218.75 and the - returned to the ASIC status. I've now added a further 2 PCI-e cables (so running with 4 on the second S3) and all ok again at stock freq. I may try upping the freq slightly tomorrow. |
|
|
|
Received my S3's today and set them up this evening. The first one has no lines in the 'ASIC status' but the second one has a single line in it's 2nd 'ASIC status':
00000000 00000000
00000000 000000-0
Both are running off an EVGA 1300 Gold PSU using two PCI-e cables each.
I took the lid off the second S3 and took the heat-sinks off and cleaned up all chips re-applied a small dot of thermal CPU paste, reassembled and the 'ASIC status' was initially all clear and then after a couple of reboots the line re-appeared in the 'ASIC status'. Any suggestions?
The first S3 has ~421 and ~420 GHs running at stock frequency of 218.75.
The second S3 has ~475 and ~419 GHs running at same stock frequency.
They've only been running for half an hour.
you can reboot the second one with the gui reboot option. if the _ sticks change the freq to 212.5 both of my miners won't mine well at 218.75 they have 1 or 2 constant _ but both are good at 212.5 I changed the second S3 to operate at freq of 212.5 and still have a '-' in the ASIC status!! I have one of those too. Or had. Yesterday when I got the miners I had it come back several times. A reboot would sometimes make it go away or change to an x but it kept coming back. First thing I did with both miners was try them at various freq but neither of them seemed to like OC very much. Hashrate was marginally better at each step but HW errors were a lot higher on both at any OC. I did try downclock also but it did not make the - go away and made the hash rate even more pathetic. Neither of my miners pull 441 Ghs at stock freq. Yesterday I took off the heat sinks for the one with the bad chip and the chips were not drenched in thermal paste as some people have seen, but actually seemed like they could have used a little more. I was pretty meticulous about putting it on the entire surface of each chip without a lot of extra (and cleaning it up on the sides where it did run off and pool a little). But even after that it was getting the -. But yesterday after having done that thermal paste cleanup I OC'd to 225 and left it for the night. What I noticed this morning was that the HW errors were much improved compared to when I first unboxed them - I thought it might be due to the cleanup of the thermal paste but it could also have been that bad chip being presumably left out of the loop (since it had a dash all night) so I thought maybe it had been the source of the HW errors before. So thinking to try and nudge it closer to the 441 advertised hash rate I bumped it up to 237.5 freq this morning. Now it is actually just getting 441 but the problematic chip has also been showing an o ever since also. I doubt it is really fixed but I am happy about the hashrate for now. But I won't be shocked if the chip shows an x after the next reboot either. As long as I get 441 out of it though I'll live with it. I also took off the heatsinks on my other miner since it also wasn't pulling 441. That one actually looked like it had a good job of thermal paste on both sides. No huge voids and not a ton dripping off the sides. But it still had a little bit pooled on one side or another of a couple chips. Again I was real meticulous about getting it just right and cleaning up the excess and lo and behold that one is suddenly working great at 250 freq with minimal HW errors. It's pulling 501 Ghs ave at 3 hours now. That one was a little weird though too, the 237.5 freq actually lowered the hash rate to about 400 so I was actually pretty surprised to see what happened at 250. I was pretty bummed with both of them yesterday but I am happier about it today with the one pulling such a high hash rate and the other at least making the advertised 441. I run them both with fans at full (blue wires disconnected) and covers off in a server room (ambient temps maintained below 70 Fahrenheit). The temps in the GUI are all mid 30's. I switched the PCI-e cables to the two rear sockets and the - in the ASIC status went. Are you using 4 PCI-e cables per S3? |
|
|
|
For those getting the - status on the chip try changing the PCI plug location, instead of using front two try the back two or try one in the front and one in the back
Thanks, I switched the PCI-e plugs to the back two sockets and the ASIC status is all zeros, fantastic |
|
|
|
Received my S3's today and set them up this evening. The first one has no lines in the 'ASIC status' but the second one has a single line in it's 2nd 'ASIC status':
00000000 00000000
00000000 000000-0
Both are running off an EVGA 1300 Gold PSU using two PCI-e cables each.
I took the lid off the second S3 and took the heat-sinks off and cleaned up all chips re-applied a small dot of thermal CPU paste, reassembled and the 'ASIC status' was initially all clear and then after a couple of reboots the line re-appeared in the 'ASIC status'. Any suggestions?
The first S3 has ~421 and ~420 GHs running at stock frequency of 218.75.
The second S3 has ~475 and ~419 GHs running at same stock frequency.
They've only been running for half an hour.
you can reboot the second one with the gui reboot option. if the _ sticks change the freq to 212.5 both of my miners won't mine well at 218.75 they have 1 or 2 constant _ but both are good at 212.5 I changed the second S3 to operate at freq of 212.5 and still have a '-' in the ASIC status!! |
|
|
|
|
Received my S3's today and set them up this evening. The first one has no lines in the 'ASIC status' but the second one has a single line in it's 2nd 'ASIC status':
00000000 00000000
00000000 000000-0
Both are running off an EVGA 1300 Gold PSU using two PCI-e cables each.
I took the lid off the second S3 and took the heat-sinks off and cleaned up all chips re-applied a small dot of thermal CPU paste, reassembled and the 'ASIC status' was initially all clear and then after a couple of reboots the line re-appeared in the 'ASIC status'. Any suggestions?
The first S3 has ~421 and ~420 GHs running at stock frequency of 218.75.
The second S3 has ~475 and ~419 GHs running at same stock frequency.
They've only been running for half an hour.
|
|
|
|
There is no option for me to get the refund of 7.7% from S3 B1, anyone else?
And I'm seeing 2 coupons of 0.75 per order.
BITMAIN never said about a deadline anywhere to request the refund.
BITMAIN please reinstate the option to redeem as coupon or btc.
I think it stated on the website. If you don't choose the refund option they will default to coupons by the 22nd. I received an email today confirming my bitcoin address for the refunds. Yes, I read a message somewhere, I think it was in this forum that we had until 22nd July. I chose refund, and also received an email telling me that the refund will be paid into my BTC wallet, but didn't say when? So far, the refund hasn't turned up in my BTC wallet. |
|
|
|
When will be getting the BTC 7.7% refunds from Bitmaintech? |
|
|
|
|
I was notified early Sunday morning, 20/07/2014 that my units had been shipped and given the UPS tracking number. Since then, a day and a half, my packages have so far only been given a shipping label but according to the UPS tracking site:
"A UPS shipping label has been created. Once the shipment arrives at our facility, the tracking status--including the scheduled delivery date--will be updated."
So my order is also halted! Anyone know why no orders are now moving?
|
|
|
|
|
My batch 2 order is on its way.
Info from Bitmain Website
Order Placed
Date: 2014-07-04 12:56:46
Payment Confirmed:
Date 2014-07-04 14:07:48
Shipped:
Date 2014-07-20 08:18:59
Hopefully will receive on Tuesday, and hope all arrives safely.
|
|
|
|
|
