I can report that the binary drops in and replaces the old one, matches the architecture, and runs without exploding in a ball of flames!
So I've pointed my S4, running this new binay, back at Slush's pool to see how it goes. Probably too soon to tell, but initially it reported hashing over 2TH via the web ui (as it always does) while Slush was showing it doing only about ~450GH, poolside.
After a few minutes that climbed up to and settled around 1TH and has been sitting there.
The Web UI also reports the Diff column (of the Slush row in the Pools table) as 1.05K, but I'm not sure if that indicates a problem...
I also dug into the init script to see what comman line params it gets run with, and they are:
/usr/bin/cgminer --bitmain-dev /dev/bitmain-asic \
--bitmain-options 115200:32:8:7:200:0782:0725 \
--bitmain-checkn2diff \
--bitmain-hwerror \
--queue 8192 \
--api-listen \
--default-config /config/cgminer.conf
and:
root@ant:~# cat /config/cgminer.conf contains:
{
"pools" : [
{
"url" : "stratum.bitcoin.cz:3333",
"user" : "gigawatt.ant-bambam",
"pass" : "x"
},
{
"url" : "",
"user" : "",
"pass" : ""
},
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"api-listen" : true,
"api-network" : true,
"api-allow" : "W:0/0",
"bitmain-nobeeper" : true,
"bitmain-freq" : "7:218.75:1106",
"bitmain-voltage" : "0725"
}
What the heck does the --bitmain-checkn2diff option do (play chicken with the diff? lol) google not so helpful here, not was the cgminer readme.
I tried adding --suggest-diff 2048 (as one google search result suggested) but that command line option was rejected by cgminer as "unrecognized" {sniff}
Well, glad it works for starters. At least we know it managed to get up to higher diff which was half the problem to begin with. I doubt that getting it to diff 2k would help any further. So if it hashes lower than that then there's still some remaining issue, and likely it's the choice of a halfway diff. Checkn2diff is a hack used by the slow bitmain products to round off diff to the nearest power of 2 since they're so slow at confirming hashes. There's a chance it may not be needed with the hack I added to the driver, so try removing that command line option. As for suggest_diff, only ckpools have that implemented at the pool end anyway so I didn't bother adding it to the driver (though it's easy enough for me to do). So try without checkn2diff next.