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!