Disregard My last post sorry about that I forgot to unzip the file before I checked the MD5 and yes the MD5 Code does match sorry again.
Well no time like the present then. Once more unto the breach, dear friends.
I am holding my breath ..... don't be long!
It flashed 2 x S3 one early batch, one later with QC sticker, and they took. Did direct flash over LAN cable not WIFI.
Give me 15min to get GHs reading, I've set mine at 231.25, no change to voltage (voltage blank). This was running fine in October firmware update. I will get back ASAP
15min Update: Both sitting at 0.44 Th/s and 0.45 Th/s on 5s, total average is a bit low, as didn't seem to spike at the beginning like they usually do.
Lets see how they do over the next couple of hours, as I was getting them dumping hash rate (50GH/s 100GH/s), and going bananas, after latest firmware.
GHash.IO 15min average 1.1 Th/s over 15min average, nice! From 2 x S3's
PS All help needed, don't supposed someone could help and potentially divert me from a bullet, and advice me on serial connection un-bricking an S3?
https://bitcointalk.org/index.php?topic=889206.msg9897190#msg9897190I'm sorry to say, It looks like I'm getting the same instability, that came from the latest firmware. Hash rates are dropping, and fluctuating, I'm down to 800Gh/s, even on one round it was recorded at 500 GH/s, so either network issue as mentioned above, or the hashing part of the firmware isn't correct.
Can someone advise as to whether it is worth putting in something into voltage section like : "0.8"
I have a solid 1200W running two S3's, which used to run three S3's at 450GH/s each for months until this stupid firmware.