I've just created a kncminer branch on my github and have imported their most current code and built my first binary for this. It is not a full firmware and the only thing users may note is the hashrate won't lie with this one, as it won't count hardware errors as hashrate. Also my hardware error count is significantly lower with this on the Saturn dev machine I was sent.
Here's a direct link to the binary:
http://ck.kolivas.org/apps/cgminer/kncminer/cgminerYou'll have to ssh into the kncminer and copy and use that file directly. Hopefully the libraries all match between my dev environment and the default kncminer operating system which means the binary should just work if you run it like on any other OS.
the honestly is nice but might scare people
can we have control on disabling/enabling cores? bfgminer has it but seems to only makes changes on a restart (tallys and marks them, but i saw HW errors still grow on cores that were marked off during current run)
Even if we can just change the '10 HW errors in a row' to whatever we want and also if/when to try to enable cores. I saw the code in the driver they posted
DPoS
at the moment I'm running bfgminer compiled form github repo @ 0a2c45816a813bc921f69c95f6c849f643d53277 (so before luke implement the mechanisms to automatically disable and re-enable problematic cores), and this is what I do every time I need to restart the miner sw:
- /etc/init.d/cgminer.sh start
the script loop through all your cores and among other things it enables all of them
- let knc cgminer version to run for a at least 20 mins.
that way all the faulty/too hw error prone cores will be disabled.
- stop cgminer and start bgfminer.
using this steps I'm able to get a lower HW % and more stable hashrate and maybe a few GH/s more i terms of performance.
As soon as I will be able to regain remote access to the miners I'll test also ckolivas cgminer version.