Quote from: crazyates on August 23, 2014, 07:26:16 PM

Another question: I just set up and configured one of my S3s, and it was hashing fine, until I rebooted it. Now, it never starts hashing. The miner status page never shows anything, it never pulls more than 45W, I'm not getting any shares, but 'top' tells me cgminer is using 2-30% CPU every couple of minutes, which I'm assuming is it checking into the pool and prepping more work (that never gets used...).

Ok, I put it asside, and moved onto setting up my next one. Idk what I'm doing wrong, but this one's doing the same thing. I've narrowed it down to when I change the pool info, but I'm using the exact same pool info as all my other Ants (Ctrl C+V right out of a spreadsheet), and cgminer isn't loading once I change the pool info. I've tried just one pool, then the other.

Quote from: Biodom on August 23, 2014, 07:38:14 PM

Quote from: crazyates on August 23, 2014, 07:26:16 PM

Another question: I just set up and configured one of my S3s, and it was hashing fine, until I rebooted it.

Is this normal?

rebooted how: cgminer, power cycling or poweoff -d command in ssh?
In my opinion S3 does not "like" to be power cycled, especially if you don't give it 10-20 sec before turning it back "ON"
try rebooting the cgminer in . It might work.

Yep I usually reboot them through the web page. When that didn't work, I did power cycle it for ~10-15 seconds. See above, as I think it's just a config issues...