I got today my S3. One is working fine but the other one was not hashing at all because it had frequency set to 350 MHz.
I tried to reset settings but same so I manually edit the "asic-freq" file and set it to 218MHz. After that it start hashing around 440GH/S but it show a strange status page with double number of ASICs but half are "x".
Using ssh I notice that cgminer binary is different on the 2 systems. I tried copy the binary from the "good" one to the "bad" one but it does not hash at all.
The "bad" one also show fan speed of 0 for chain #2 but visually both fans are spinning at high speed.
I hope this is just an old firmware of something like that. I guess it will be fixed when Bitmain will release a firmware update for S3 and after that I'll get consistent Miner Status results on both units.
Power usage at the wall for the "good" is 337W and for the "bad" one is 323W.
I tried to reset settings but same so I manually edit the "asic-freq" file and set it to 218MHz. After that it start hashing around 440GH/S but it show a strange status page with double number of ASICs but half are "x".
Using ssh I notice that cgminer binary is different on the 2 systems. I tried copy the binary from the "good" one to the "bad" one but it does not hash at all.
The "bad" one also show fan speed of 0 for chain #2 but visually both fans are spinning at high speed.
I hope this is just an old firmware of something like that. I guess it will be fixed when Bitmain will release a firmware update for S3 and after that I'll get consistent Miner Status results on both units.
Power usage at the wall for the "good" is 337W and for the "bad" one is 323W.