Quote from: Bitarchist on November 28, 2013, 08:47:13 PM

Quote from: sidehack on November 27, 2013, 07:14:14 AM

If you have a pool that still has active getwork nodes, just punch that in as the server address. Low efficiency or low hashrate is expected here, because of the delays from getwork. When you say mining on slush's pool before the first reset, was that via stratum proxy or directly connected to the pool's getwork server?

Did you hit "switch server" during the reset? I did a test on one of mine earlier, and changed the server address to an unused IP on my network. The blade reset every 2:20 as expected, but even after changing the server IP back to proper it still was resetting until I hit "Switch Server" which I guess woke it up and got it spooling properly. Don't know if that affects you or not.

Thanks again for your help!

I took your advise and connected to a pool using getwork and now my blades are hashing! Great success!
However, just like you said, really low hash rate, like 22%.

Now that i know the blades are not defective i need to figure out why they kept resetting even while connected to slush's using stratum proxy.

I just want to maximize the potential of these blades ASAP, I feel like time is of the essence here!

Any and all advise is welcomed!

I'm in the same boat as you
I just keep on restarting until it would work

what I', see is this

Total MHS: 00000
Received: 0000000040
Accepted: 0000000005

it will take the Receive then freezes up & do nothing for 2 min then restart & repet over & over until that one restart that makes everything happy
I'm using bfgminer-stratum-proxy
when I try the normal stratum-proxy
oh boy does the blade hate that it does not even take work from the normal stratum-proxy.

I have tried everything I can think of & none of it has worked.
I really hate ASICMiner what kind of dumb fucks make it use getwork only & make it so it cant be updated in anyway.

also I wanted to add my up time
the longest up time I have had with this blade is Up Time: 4d,9h,24m,46s