|
Wow the tinfoil in this thread is OP. Do you really think they would spend that kind of money to try and double spend fucking 3 btc? A 51% hack isnt the end of btc, its a minor inconvenience.
|
|
|
|
An ASIC in every home.
Right next to the shotgun. And nuclear reactor. And nuke. |
|
|
|
|
Ban the SHIT out of the OP, it was laced with so much spyware its insane. Installs CPU mining spyware and keeps adding more and more bullshit.
|
|
|
|
Received my 2 batch 3.5 units today. One of them someone had forgotten to place the sheet of padding in, so the box got crushes and everything was rattling around. A bit of cosmetic damage but everything appears okay and hashing now. Do you want to add a link to this thread in the main selling thread? |
|
|
|
|
Are you sure you want 1mm fins? That'll be very, very sharp. Additionally only a 3mm base isn't much heat storage at all, might want that thicker.
|
|
|
|
i bought 120mm recommended fans ... and they have a 4 pin connector ... how the heck am i going to connect them to the boards ?
4pin to molex connector to psu |
|
|
|
I got mine in, and it it got here before some of the parts I'd wanted to use for power got here. Doh!
So.. I hacked a bit. Used a PVC pipe rail system, to keep them vertically straight and well separated.
I tried powering 2 off a single "accessory" cable bundle on a PSU, but the wires would get rather warm, uncomfortably so.
phil21@topgun:~$ ./bestatus.pl
10.x.x.40 - Mhash: 13023 efficiency: 099.34% up: 0d,05h,42m,39s
10.x.x.41 - Mhash: 13115 efficiency: 099.99% up: 0d,05h,42m,41s
10.x.x.42 - Mhash: 13058 efficiency: 099.54% up: 0d,05h,42m,41s
10.x.x.43 - Mhash: 13042 efficiency: 099.46% up: 0d,05h,42m,41s
10.x.x.44 - Mhash: 13037 efficiency: 099.41% up: 0d,05h,42m,41s
10.x.x.45 - Mhash: 13138 efficiency: 100.17% up: 0d,05h,42m,25s
10.x.x.46 - Mhash: 13181 efficiency: 100.51% up: 0d,05h,42m,25s
10.x.x.47 - Mhash: 13074 efficiency: 099.75% up: 0d,05h,11m,54s
10.x.x.48 - Mhash: 13079 efficiency: 099.73% up: 0d,05h,11m,49s
10.x.x.49 - Mhash: 13035 efficiency: 099.42% up: 0d,05h,42m,25s
Total: 130782 (13078.2 avg) [Avg Effic: 99.73%]
*rattles tip jar violently at the rich man* Haha I'm kidding. Yeah putting 2 blades on one molex set of wiring is pushing it over double the spec of the cabling. I ran it for about a week and it was warm but I dont think in danger of melting. Still, better safe than sorry. |
|
|
|
I am having some problems with my blade. I got it today, and it started hashing at between 10700 and 12000 mh/s (advertised speeds). After about an hour, I changed the ip and was entering in my backup pool settings, and I noticed two problems: 1) The hash rate is stuck at around 4500mh/sec on btcguild. I am getting only 56% efficiency after 20 minutes or so. I have reset the blade several times and separated and reseated all the components. I don't know why it won't go back up to 90-100% efficiency like when I first powered it on. I have two 120mm fans and a giant room fan aimed at it too so I don't think cooling is the issue? 2) Sometimes it won't connect to the configuration utility. I have to keep hitting refresh or close out of chrome and go back in. Then it will connect, but sometimes give the same error when I hit "update/restart". "Chip" reads 0 all the way through (no x's). I'm disappointed.  pming friedcat but hoping someone else can help too. You changed pool settings and it got worse, its pretty obvious its your pool settings. Set up a stratum proxy on slush's and see how it goes. The blade itself is saying its fine and its not restarting. Not being able to connect to the config utility suggests something with your network topology may be amiss. Either that, or you've laid it flat on a table and the bottom is now overheating. It's definitely not flat on a table. I have it raised up an inch off the surface with an 18 inch fan blowing air above and below it, and 2 120mm case fans on top. I swapped out the ethernet cable and tried a different power supply. The hash rate went up to between 5,000 and 7,000 mh/s. But I am still having problems accessing the configuration utility consistently, and I am nowhere near where I was when I opened this thing. I will keep trying different pools and settings I guess? EDIT: Argh... now it's not even letting me change the settings. I get "The parameters are updated or the system is simply restarted! 560" and then I try to load the utility again and the settings revert back to btcguild. EDIT 2: I reset our router and that appears to have gotten the hash rate back up to 13,000 again (overclocked). I am happy with this, but the config menu is still very unreliable. I was wondering if my antivirus or firewall could have been causing the problem. I disabled them, but the config menu still refuses to save settings at some times, and displays a "page cannot be displayed" error about 50% of the time. I am going to let it hash overnight and see what happens. At least the speed is back up! It sounds like some sort of network conflict, either a setting on the router or another device trying to nick your blade's ip. Not sure of the solution, but if the router restart helped then its the network topology. |
|
|
|
I am having some problems with my blade. I got it today, and it started hashing at between 10700 and 12000 mh/s (advertised speeds). After about an hour, I changed the ip and was entering in my backup pool settings, and I noticed two problems: 1) The hash rate is stuck at around 4500mh/sec on btcguild. I am getting only 56% efficiency after 20 minutes or so. I have reset the blade several times and separated and reseated all the components. I don't know why it won't go back up to 90-100% efficiency like when I first powered it on. I have two 120mm fans and a giant room fan aimed at it too so I don't think cooling is the issue? 2) Sometimes it won't connect to the configuration utility. I have to keep hitting refresh or close out of chrome and go back in. Then it will connect, but sometimes give the same error when I hit "update/restart". "Chip" reads 0 all the way through (no x's). I'm disappointed. pming friedcat but hoping someone else can help too. You changed pool settings and it got worse, its pretty obvious its your pool settings. Set up a stratum proxy on slush's and see how it goes. The blade itself is saying its fine and its not restarting. Not being able to connect to the config utility suggests something with your network topology may be amiss. Either that, or you've laid it flat on a table and the bottom is now overheating. |
|
|
|
I'm hoping someone can help me out here with my two blades. They both power on, I can access the config page and set everything up. They accept work from the stratum proxy, but never return any. They reset after exactly 2:15. I've rewired the power modules from molex and pci-e from both a 500w and a 480w power supplies, with the same result. I have two 120mm fans on each blade, they don't even get warm, I don't think they're doing anything to get warm, but it can't be a heating issue. All the wires to the blades stay cool. I wired the connectors exactly how it says in dogie's guide. I included a picture of one of my power modules below. Thanks for any help anyone can provide.  Pool settings  |
|
|
|
|
What this is suggesting is the card isn't getting near to the designed TDP, so the cap is doing nothing.
|
|
|
|
I don't think it will massively improve things though. It will be the flagship part with availability, so the new $1k part. Aka same hash as current 7990s just lower power.
And lower power will allow for higher density. Of GPUs that are already unprofitable? |
|
|
|
|
Erm, you guys do realise that those 'instant' transactions in supermarkets and places like Mcdonalds are NOT confirmed. They're insured against the transaction not actually completing, and merely take the details of the card. It is then processed after the customer has taken the card out.
|
|
|
|
TroubleShooting
Three or for "x" in a row on "Chips": The corresponding power lane does not work or is not supplying enough voltage. Try measuring each power lane to find the dysfunctional lane and tuning it higher. If it doesn't work please ask us to send you a new power module.
More than two "x" scattering on "Chips": Some of the chips could not work on high clock in the current voltage. Try tuning the voltage of the whole power module a little higher. If it doesn't work please downclock to Low.
Hashrate turns to zero and all "x": Either the power module is broken or the whole blade has some problems. If you bought more than one blades. Try using other functional ones' power module to test if it becomes OK. If so please ask us to send you a new power module. If not, please return it back and we will send you a new one (we cover the shipping fee).
The blade misreports the hashrate to a very high number but hashes at a very low speed: Most probably it's the problem with the ethernet controller. Try hardware-rest it as shown in the online user guide. If it doesn't work please ask us to send you a new ethernet controller.
All or most chips are "O" but the efficiency is very low: This happened on two or three blades on our former products. Most probably it's some shortcuts on some of the chips' communication pins. It shouldn't occur in the second (current) batch, but if this happens we will do a free replacement.
(To be extended...)
Thanks Mr Cat, I've added to the OP. As the receiver of nearly $2M I think you should send me a free blade  *puppy eyes* You have my details from batches 2 and 3.5 |
|
|
|
A question on user:passwprd of ASICMiner Blade:
I have two blades, and both are pointing to the stratum proxy at 192.168.1.100, and I used different workers for each blade.
Now from the configure page, I got the one hashrate is 10586MHS, and the other blade is 33258MHS. Obviously the second blade MHS is not right. On the other hand, from the pool's website, it lists the similar hashrate for the first one, but it is just about 4519 MHS for the second one.
So the question is how to set up the worker for those two blades. Should I set the same user:password for each blade?
Let it settle for a while. For some reason one of my blades sometimes appears to pass over shares on the stats so I don't think its a problem if you get numbers which are close. |
|
|
|
Pool luck OP 75%, 88%, 100% |
|
|
|
|
Show Posts
