rootdude wrote:
Kires - what type of rigs are you running?
I don't seem to have the cgminer option with my Titans... though I am trying out the "failover-only" : true, option to see if it helps my registered hashrate at all (which is always suffering because of work restarts)...
I've got a pair of KNC Titans. I was one of the relatively lucky ones who at least got solid hardware out of the deal. The configuration I'm using for them is only possible to do via SSH access to the controller. You need to add the failover only string to the script that calls the miner, named bfgminer.sh. Once you ssh into it you'll need to:
Code: Select all
vi knc-asic/RPi_system/bfgminer.sh
If you don't know how to use vi, then use nano instead. Anyway, once you get the script open, it will look something like this:
Code: Select all
if [ -f /config/miner.conf ]; then
. /config/miner.conf
fi
if [ "$use_bfgminer" = true ] ; then
DAEMON=/home/pi/bfgminer/bfgminer
NAME=bfgminer
DESC="BFGMiner daemon"
EXTRA_OPT="-Q 10"
else
DAEMON=/usr/bin/cgminer
NAME=cgminer
DESC="Cgminer daemon"
EXTRA_OPT=
fi
set -e
test -x "$DAEMON" || exit 0
do_start() {
start-stop-daemon -b -S -c pi -d $(dirname "$DAEMON") -x /usr/bin/screen -- -S cgminer -t cgminer -m -d sh -c "while true; do waas >/dev/null 2>/dev/null ; $DAEMON --api-listen --api-allow="W:127.0.0.1/24,W:192.168.1.13" -c /config/cgminer.conf $EXTRA_OPT --failover-only --scrypt -S titan:auto; done"
}
...
It will
allegedly use CGMiner if the use_bfgminer variable is set to false in that first if statement. I'm not sure where that variable lives, though, so that'll take some digging. As for whether to use Cgminer or maybe even try for SGMiner, I'm reluctant
more like knock kneed little girl scared to experiment. I've got them running like a striped-assed ape and I'm afraid to mess with 'em after all the fun and games it's taken to get it working this well.
Anyway, setting the failover only flag is just a matter of adding it right after the $EXTRA_OPT in the line that begins with 'do_start'. I'm using this file, no password arguments (Prohashing sets my miners difficulty at 16384 which seems about right), and the url of
Code: Select all
stratum+tcp://prohashing.com:3333/#skipcbcheck
and my 2 Titans are actually
averaging about 650 Mashies here, which is about what they got mining straight LTC. I don't know if adding the failover only flag to the Manual Configuration File Editor in the web interface will work or not. But if ssh isn't your thing then give it a shot and let me know if it works.
Also, when I've broken my controller with a bad update, I was able to restore it by flashing it back to version 1.2 of the firmware, then upgrading it to each successive version through the interface. I was never able to get a fresh img of 2.0 to boot. YMMV.
When you have SSH'd into it, you may be tempted to upgrade the pi's software.
DO NOT DO THIS I tried to do it, and ended up bricking one of my miners. Apparently KNC's code only likes the specific version of some of the software because apt upgrade all blew it higher than up, and it took me a few hours to get it back up to speed.