Quote from: entr04y on December 02, 2014, 01:52:45 AM

Quote from: ckolivas on December 02, 2014, 01:25:06 AM

Quote from: IYFTech on December 02, 2014, 01:23:26 AM

Might be worth while asking ckolivas if the S3 binary he done to fix the stale shares filtering can also be used in the C1? I don't have a C1, but it might be compatible......

If S3 binaries run on the C1, my binary is compatible.

Doesn't look like it:

Code:

root@ant1:~# /usr/bin/cgminer --help
/usr/bin/cgminer: line 1: syntax error: unexpected "("

$ file cgminer
cgminer: ELF 32-bit MSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), dynamically linked (uses shared libs), with unknown capability 0x41000000 = 0xf676e75, with unknown capability 0x10000 = 0x70403, stripped

$ file cgminer.orig
cgminer.orig: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, stripped

cgminer.orig is the one that came with the c1.

The S4 binary seems to run ok (actually it seems to give quite a boost in hash rate), but the GH/s (5s) field is 0 (the avg field looks right) and the discarded field is really high... p2pool says 1.34THS/s and 5.5% discard rate, and the temperature seemed stable. I've switched back to the original binary for now... it seems like it was running too fast and if the GH/s field isn't working, I'm not sure that I trust the rest of the stats on the miner.

ckolivas (or anyone else), any opinion on running the s4 binary on a c1?