From b1a6c50794149b389c637df6eb38e5c1bc310f0f Mon Sep 17 00:00:00 2001 From: m1 Date: Sun, 23 Jul 2017 17:47:29 -0700 Subject: [PATCH] update README --- README.md | 32 +++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index b26937a..42f54b6 100644 --- a/README.md +++ b/README.md @@ -23,12 +23,12 @@ be invoked manually if you add/remove GPUs so it can reconfigure /etc/X11/xorg.conf, but it otherwise isn't used. To keep gnome-terminal from sucking down CPU cycles by constantly restarting the 2unix script, you might want to include something like "sleep 86400" at the end. -4. Edit the block of constants at the top of switch.py. You'll set your -power cost and the mining rates and power consumption of various algorithms -here. You can extend the performance list to include additional mining -algorithms supported by both NiceHash and the miners included with nvOC. -Your Bitcoin address and rig name also go here...though if you want to mine -to my tipjar, I won't complain. :-) +4. Edit conf.json. You'll set your power cost and the mining rates and power +consumption of various algorithms here. You can extend the performance list +to include additional mining algorithms supported by both NiceHash and the +miners included with nvOC. Your Bitcoin address and rig name also go here... +though if you want to mine to my tipjar, I won't complain. :-) Comments as +to what's what in conf.json can still be found at the top of switch.py. 5. If your network is IPv6-enabled, note that nvOC (as of v17) has a problem connecting to IPv6 hosts. NiceHash makes its API available over both IPv6 and IPv4, so to force it to use IPv4 in the meantime, edit /etc/hosts as @@ -37,8 +37,7 @@ follows: `104.20.158.21 api.nicehash.com` 6. Set switch.py to launch with a cronjob: - `0,10,20,30,40,50 * * * * (cd /media/m1/1263-A96E && python2.7 switch.py)` - + `0,10,20,30,40,50 * * * * (cd /media/m1/1263-A96E && python2.7 switch.py conf.json)` Every 10 minutes (which is how often NiceHash recalculates profitability), the script will run and determine which miner needs to start up. If it's @@ -50,12 +49,19 @@ current-profit is a text file that will be updated on every run of switch.py to show which is currently the most profitable. It provides profit values in BTC and your local currency. +algo-log is a list of algorithms the switcher has selected when run. If you +start seeing repeats of the same algo every 10 minutes, that's a sign that +something has gone wrong with your GPUs and you might want to consider a +reboot. + The power and hashrate numbers in the stock configuration are for my rig, -which currently uses two GeForce GTX 1070s (one reference-design, one a bit -factory-overclocked and with a massive cooler) on an Asus Prime Z270-AR, -driven by a Thermaltake 650W 80+ Bronze power supply. Wall power is -measured with a Kill-a-Watt. Some miners (such as the EWBF miner) show -power usage at the card. +which currently uses three GeForce GTX 1070s (one reference-design, the +others a bit factory-overclocked and with massive coolers) on an Asus Prime +Z270-AR, driven by a Thermaltake 650W 80+ Bronze power supply. Wall power +is measured with a Kill-a-Watt. Some miners (such as the EWBF miner) show +power usage at the card. I'm in the middle of recalculating the power- +consumption numbers, so perhaps the ones included in earlier commits would +be more useful for now. Miners are started in Screen sessions (http://www.gnu.org/software/screen) that can be viewed over an ssh login session: