[OS] nvOC easy-to-use Linux Nvidia Mining

[Stubo]

For any of you guys that like to keep things up to date, there is a new version of the DSTM ZM miner 0.5.6:

https://bitcointalk.org/index.php?topic=2021765.0

and there is a new nvidia driver 387.34 (previous for me was 387.12) if you run Ubuntu updates. I put a "nvOC-ized" version of the new DSTM miner up here if anybody wants to grab it:

http://www.cstone.net/~stu/nvOC/miners/DSTM_0.5.6.tar.gz

It basically just saves you the trouble of renaming the miner and the directory it is in.

Hope this helps.

[1714483717]

1714483717

[1714483717]

1714483717

[1714483717]

1714483717

[CryptAtomeTrader44]

Do you mean add BTG to WTM auto switch ?
If so, you can do it easily.

Add BTG to your 3main in the appropriate location:

Code:

if [ $COIN == "BTG" ]
then

  if [ $EWBF_VERSION == "3_3" ]
  then
    HCD='/home/m1/zec/v3_3/miner'
  fi

  if [ $EWBF_VERSION == "3_4" ]
  then
    HCD='/home/m1/zec/v3_4/miner'
  fi

  BTGADDR="$BTG_ADDRESS.$BTG_WORKER"

  if [ $ZM_or_EWBF == "ZM" ]
  then
    HCD='/home/m1/zec/zm/5_4/zm_miner'
    screen -dmSL miner $HCD --server $BTG_POOL --user $BTGADDR --pass $MINER_PWD --port $BTG_PORT   ;
  fi

  if [ $ZM_or_EWBF == "EWBF" ]
  then
    screen -dmSL miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $BTG_POOL --user $BTGADDR --pass $MINER_PWD --port $BTG_PORT  ;
  fi

if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi

BITCOIN="theGROUND"

while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi

change this line to your dstm latest version in /home/m1/zec/zm/:

Code:

    HCD='/home/m1/zec/zm/5_4/zm_miner'

Add BTG to your 1bash in coin details location:

Code:

#BTG
BTG_WORKER="$WORKERNAME"
BTG_ADDRESS="Your_mining_pool_hub_username"
BTG_POOL="europe.equihash-hub.miningpoolhub.com"
BTG_PORT="20595"

in 1bash :

Code:

WTM_AUTO_SWITCH_COINS="ZEC;ZEN;BTG" ### add any other coins you want : "ZEC;ETH;ETC;XMR"

restart PAPAMPI_WTM and 3main or reboot the rig:

Code:

pkill -f 3main
pkill -f PAPAMPI_WTM
bash /home/m1/PAPAMPI_WTM &

[

I'll add all theses changes in all files you mentionned here.

For the ZM miner, I'm skeptical, it seems to be a problem for me and he often crashes unlike ewbf.

I have to look for the latest version. Maybe it's less the case now.
On the other hand, I noticed that the dev had chosen a pool that fell a little ago and that it generated a lot of rig crash using its software worldwide.

whattomine.com added BTG since yesterday, you can turn on wtm auto switch again
https://whattomine.com/coins/214-btg-equihash

I did not understand because I did not see it, but actually, I did not see either that there were two other platforms added to the WTM comparator of fredeq

Thank you for this little visible but crucial information.

Yes it did,
Check your exchanges and add them all




It will show up then

 What is the problem with OC_Spécific Settings and how do you do for OC your mémory and GPU cards ? This feature is really great, it is a bad loss can't using it.

Sorry just saw this question ...

damNmad auto OC not works with wtm auto switch from z_papampi_versions, for now I use same coin algos to switch
But I'm working on integrating damNmad OC with the z_papampi_versions, and so many more improvements
Hopefully will be ready for next update.

In fact I tried your latest version that does not restart the 3main but it seems that it makes my rig less stable and reboots every two or three hours. so I went back and at the same time I can reuse the OC-SPECIFIC Setings.

The other problem is that I have a tab package "AUTO_GRAM in terminal guake.
Would there be no way to detect these useless tabs due to the telegram script and close them at each restart of 3main.
A test command before opening one or simply close this tab after running the script. and not open it at all and leave the script in the background?

[adisonu]

Hi guys,

I'm using nvoc for a week now with x 13 gpu's on Asrock H110+ pro. I have 5 mobos. 2 of them have constant problems. They are working for 2 days with a fresh install. After they freeze i restart them and the system is not booting. One of them is showing ubuntu loading screen and the other is showing "19_1_4 login:". The nvoc is v0019-1.4. What do you think?

Thanks

[CryptAtomeTrader44]

I tried your adaptations in the scripts as explained, but when I restart 3main, I do not see the occurrences nicehash founie by the site WTM appear in the list displayed by the papampi script.

I noted that WTma changed the "_" to "-" between the word nicehash and the word of each algorithm. So I modified your code as well in the WTM_AUTO_SWITCH file:

Code:

# filter WTM coins by user selection only

for i in reversed (data):
     if i ["tag"] == "NICEHASH":
        i ["tag"] = "NICE-" + i ["algorithm"]. upper ()

for i in reversed (data):
     if i ["tag"] not in includedCoins:
        data.remove (i)

Do you have any idea why I do not see the nicehash lines in the list of corners sorted by the papampi script?

EDIT : I also modified

NICE_SKUNKHASH;NICE_EQUIHASH;NICE_ETHASH;NICE_NEOSCRYPT;NICE_X11GOST;NICE_CRYPTONIGHT;NICE_LYRA2REV2

into

NICE-SKUNKHASH;NICE-EQUIHASH;NICE-ETHASH;NICE-NEOSCRYPT;NICE-X11GOST;NICE-CRYPTONIGHT;NICE-LYRA2REV2

in replacing the uderscores by hyphen/dash in WTM coin selection to the WTM coins in 1bash, i did the same replacements in the 3main associated launching minner's softwares comamnd lines. (what i placed a the end of file.

I don't know why fredeq changed "_" to "-"

If you use "-" in bash you have to cover it properly. So just don't do it. If you use my code as it was please have a look to the WTM.json file. Maybe NICE_SKUNKHASH;NICE_EQUIHASH;NICE_ETHASH;NICE_NEOSCRYPT;NICE_X11GOST;NICE_CRYPTONIGHT;NICE_LYRA2REV2 was not included in the file properly.

for i in reversed (data):
     if i ["tag"] not in includedCoins:
        data.remove (i)

will remove every coin that is not in the list.

hope this helps.

No pb in using "-" in all modifications you proposed, in all files. and my wtm_switch seems to be perfectly functionnal for nicehash in the coins sélection switchs.

NOTE : i modified my post several times after your responsee and i think I was cautious and checked to see if everything was ok with a tail -f screenlog.0.

I transferred my USB key to a good old HDD 2.5 "200 GB classic I put in a cheap case found at AliExpress I have a package of old 2.5" disks that drag. Here is an activity all found for them and suddenly I ordered a package of 4 box at Ali!
Holy Chinese!

[kedes]

Hello. I havent used any Linux before but trying to use nvOC for mining now. Was trying find answers on my questions in this thread but didnt find any. May be becasue i'm not good in english. So could anybody to help me:
1) I use ewbf miner. Sometimes i see that terminal says that gpu's utilization is zero and needs to restart. But i dont see what GPU has stopped and what reason (overlock or anything else). Was trying to find ewbf's logs but no luck. So where i can see ewbf's logs to check what GPUs was crushed because overlock?
2) How can i start mining manualy? Where ewbf miner placed? There is nothing in ewbf's folder
3) I use X Server to check GPU's overlocking. And there is core clocks looks like in MSI Afterburner (1800-1900Mhz for gtx 1070), but memory clocks are too large (8900-9000Mhz, MSI Afterburner displays 4400Mhz for same GPUs). Such big memory clocks is ok for ubuntu? Any other soft for checking Overlocking?
4) There are many different guides on narrow topics, helping to solve only some individual problems. But Is there the most complete and most detailed guide, how to configure everything from scratch and to be familiar as well as on windows?

[Stubo]

Hello. I havent used any Linux before but trying to use nvOC for mining now. Was trying find answers on my questions in this thread but didnt find any. May be becasue i'm not good in english. So could anybody to help me:
1) I use ewbf miner. Sometimes i see that terminal says that gpu's utilization is zero and needs to restart. But i dont see what GPU has stopped and what reason (overlock or anything else). Was trying to find ewbf's logs but no luck. So where i can see ewbf's logs to check what GPUs was crushed because overlock?
2) How can i start mining manualy? Where ewbf miner placed? There is nothing in ewbf's folder
3) I use X Server to check GPU's overlocking. And there is core clocks looks like in MSI Afterburner (1800-1900Mhz for gtx 1070), but memory clocks are too large (8900-9000Mhz, MSI Afterburner displays 4400Mhz for same GPUs). Such big memory clocks is ok for ubuntu? Any other soft for checking Overlocking?
4) There are many different guides on narrow topics, helping to solve only some individual problems. But Is there the most complete and most detailed guide, how to configure everything from scratch and to be familiar as well as on windows?

Not all but maybe some help for you:

1) Check /home/m1/screenlog.0 for miner output (assuming you are on 19-1.4)
3) See my post -> https://bitcointalk.org/index.php?topic=1854250.msg25217765#msg25217765

[CryptAtomeTrader44]

For any of you guys that like to keep things up to date, there is a new version of the DSTM ZM miner 0.5.6:

https://bitcointalk.org/index.php?topic=2021765.0

and there is a new nvidia driver 387.34 (previous for me was 387.12) if you run Ubuntu updates. I put a "nvOC-ized" version of the new DSTM miner up here if anybody wants to grab it:

http://www.cstone.net/~stu/nvOC/miners/DSTM_0.5.6.tar.gz

It basically just saves you the trouble of renaming the miner and the directory it is in.

Hope this helps.

Thx, i integrated it in all scripts files, it seems looking working good and a more hashrate results..but the 2% of dev fee make me grrrrrr

[CryptAtomeTrader44]

Do you mean add BTG to WTM auto switch ?
If so, you can do it easily.

Add BTG to your 3main in the appropriate location

restart PAPAMPI_WTM and 3main or reboot the rig:

Code:

pkill -f 3main
pkill -f PAPAMPI_WTM
bash /home/m1/PAPAMPI_WTM &

Done.

Everything looks good Expect that BTG profitabuility seems under ETH . I added to my list in WTM_Switch, but i think it's not sure that it is his glory time at the moment.... Wait & See

[papampi]

Do you mean add BTG to WTM auto switch ?
If so, you can do it easily.

Add BTG to your 3main in the appropriate location

restart PAPAMPI_WTM and 3main or reboot the rig:

Code:

pkill -f 3main
pkill -f PAPAMPI_WTM
bash /home/m1/PAPAMPI_WTM &

Done.

Everything looks good Expect that BTG profitabuility seems under ETH . I added to my list in WTM_Switch, but i think it's not sure that it is his glory time at the moment.... Wait & See

I think for better results its best to change your hash rates based on your real hash rates in wtm too.
I get much more hash rate from my 1060 and 1070 than the default values of wtm

For 1060 it says 270 sols for equihash but I get 300~310 with dstm, OC 150, mem 600, power 85
For 1070 it says 430  sols for equihash but I get 460~470 with dstm, OC 150, mem 600, power 125


BTG was at top all day with 110~140%, its time for it to rest and go up again

[papampi]

3) I use X Server to check GPU's overlocking. And there is core clocks looks like in MSI Afterburner (1800-1900Mhz for gtx 1070), but memory clocks are too large (8900-9000Mhz, MSI Afterburner displays 4400Mhz for same GPUs). Such big memory clocks is ok for ubuntu? Any other soft for checking Overlocking?

Linux take a different approach on Memory Clock, its double the value of what you use in windows.
Google it and read more about it

If you are on 1.4 you can see your rig error logs in webinfo too
rigip/index.html

[CryptAtomeTrader44]

Do you mean add BTG to WTM auto switch ?
If so, you can do it easily.

Add BTG to your 3main in the appropriate location

restart PAPAMPI_WTM and 3main or reboot the rig:

Code:

pkill -f 3main
pkill -f PAPAMPI_WTM
bash /home/m1/PAPAMPI_WTM &

Done.

Everything looks good Expect that BTG profitabuility seems under ETH . I added to my list in WTM_Switch, but i think it's not sure that it is his glory time at the moment.... Wait & See

I think for better results its best to change your hash rates based on your real hash rates in wtm too.
I get much more hash rate from my 1060 and 1070 than the default values of wtm

For 1060 it says 270 sols for equihash but I get 300~310 with dstm, OC 150, mem 600, power 85
For 1070 it says 430  sols for equihash but I get 460~470 with dstm, OC 150, mem 600, power 125


BTG was at top all day with 110~140%, its time for it to rest and go up again

Yes, i saw that with others than BTG.

but i had'n't seen this varible before !!!!???  :  

Code:

--pass $MINER_PWD 

Code:

 screen -dmSL miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $BTG_POOL --user $BTGADDR --pass $MINER_PWD --port $BTG_PORT  ;

Where did you added this varible ? In 1bash i présume ? But where in 1bash ?

I'ill put a x manually for the moment.

[papampi]

Do you mean add BTG to WTM auto switch ?
If so, you can do it easily.

Add BTG to your 3main in the appropriate location

restart PAPAMPI_WTM and 3main or reboot the rig:

Code:

pkill -f 3main
pkill -f PAPAMPI_WTM
bash /home/m1/PAPAMPI_WTM &

Done.

Everything looks good Expect that BTG profitabuility seems under ETH . I added to my list in WTM_Switch, but i think it's not sure that it is his glory time at the moment.... Wait & See

I think for better results its best to change your hash rates based on your real hash rates in wtm too.
I get much more hash rate from my 1060 and 1070 than the default values of wtm

For 1060 it says 270 sols for equihash but I get 300~310 with dstm, OC 150, mem 600, power 85
For 1070 it says 430  sols for equihash but I get 460~470 with dstm, OC 150, mem 600, power 125


BTG was at top all day with 110~140%, its time for it to rest and go up again

Yes, i saw that with others than BTG.

but i had'n't seen this varible before !!!!???  :  

Code:

--pass $MINER_PWD 

Code:

 screen -dmSL miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $BTG_POOL --user $BTGADDR --pass $MINER_PWD --port $BTG_PORT  ;

Where did you added this varible ? In 1bash i présume ? But where in 1bash ?

I'ill put a x manually for the moment.

Thats an edit/suggestion by Stubo for next update
You can either add the statement to your 1bash or remove it from the miner start line

Code:

# Set the miner password
MINER_PWD="x"

[Stubo]

Bug in IAmNotAJeep_and_Maxximus007_WATCHDOG?

I was reading over this script in attempt to answer some questions from a fellow nvOC user and ran across what I believe is a bug at the end. I reviewed the original versions include in both 19-1.3 and 19-1.4 and see this code at the end:

Code:

<cut>
else
#IAmNotAJeep MOD from V002
  COUNT=$((6 * $GPU_COUNT))
  echo "$(date) - 5 by 5: REMEMBER TO THANK IAmNotAJeep and Maxximus007"
#IAmNotAJeep MOD from V002
fi

  # No need for a reboot after a while
  if [ $REBOOTRESET -gt 5 ]
  then
    RESTART=0
    REBOOTRESET=0
    #reinit=6
  fi
done

I believe that the last if block should be within the if block that comes just before it since I think the idea behind the logic is to reset the RESTART counter if we make through the while loop 5 times without detecting any GPU's below the utilization THRESHOLD. As written, RESTART is reset to 0 every 5th time through the loop regardless, so the code should be:

Code:

   else
      # All is good, reset the counter
      COUNT=$((6 * $GPU_COUNT))
      echo "$(date) - 5 by 5: REMEMBER TO THANK IAmNotAJeep and Maxximus007"

      # No need for a reboot after 5 times through the main loop with no issues
      if [ $REBOOTRESET -gt 5 ]
      then
         RESTART=0
         REBOOTRESET=0
      fi
   fi
done

Am I misunderstanding the intent here?

[bwillyb]

Why my rig stops after 15 hours ?
I have 4X geeforce windforce gtx 1070

Temp: GPU0: 70C GPU1: 67C GPU2: 59C GPU3: 69C
GPU0: 443 Sol/s GPU1: 445 Sol/s GPU2: 453 Sol/s GPU3: 445 Sol/s
Total speed: 1786 Sol/s
+-----+-------------+--------------+
| GPU | Power usage |  Efficiency  |
+-----+-------------+--------------+
|  0  |    129W     |  3.43 Sol/W  |
|  1  |    135W     |  3.30 Sol/W  |
|  2  |    134W     |  3.38 Sol/W  |
|  3  |    133W     |  3.35 Sol/W  |
+-----+-------------+--------------+

I have a corsair 1200W
MB: ASUS PRIME Z270-A
now power wall is only 615W

power limit at 140W each one
__CORE_OVERCLOCK_1=150
MEMORY_OVERCLOCK_1=580

[papampi]

Bug in IAmNotAJeep_and_Maxximus007_WATCHDOG?

I was reading over this script in attempt to answer some questions from a fellow nvOC user and ran across what I believe is a bug at the end. I reviewed the original versions include in both 19-1.3 and 19-1.4 and see this code at the end:

Code:

<cut>
else
#IAmNotAJeep MOD from V002
  COUNT=$((6 * $GPU_COUNT))
  echo "$(date) - 5 by 5: REMEMBER TO THANK IAmNotAJeep and Maxximus007"
#IAmNotAJeep MOD from V002
fi

  # No need for a reboot after a while
  if [ $REBOOTRESET -gt 5 ]
  then
    RESTART=0
    REBOOTRESET=0
    #reinit=6
  fi
done

I believe that the last if block should be within the if block that comes just before it since I think the idea behind the logic is to reset the RESTART counter if we make through the while loop 5 times without detecting any GPU's below the utilization THRESHOLD. As written, RESTART is reset to 0 every 5th time through the loop regardless, so the code should be:

Code:

   else
      # All is good, reset the counter
      COUNT=$((6 * $GPU_COUNT))
      echo "$(date) - 5 by 5: REMEMBER TO THANK IAmNotAJeep and Maxximus007"

      # No need for a reboot after 5 times through the main loop with no issues
      if [ $REBOOTRESET -gt 5 ]
      then
         RESTART=0
         REBOOTRESET=0
      fi
   fi
done

Am I misunderstanding the intent here?

I tested both scenarios with a small change in your Debug code
Used ewbf and set threshold to 100 to see what happenes

added this at the end before done

Code:

    echo "Debug: JEEP=$JEEP, COUNT=$COUNT, RESTART=$RESTART REBOOTRESET=$REBOOTRESET"

With the original code, wdog resets REBOOTRESET after 5 cycles, with your proposal REBOOTRESET keeps adding up, and wont resets after 5.
So my conclusion is the original code should be correct. 

[papampi]

Why my rig stops after 15 hours ?
I have 4X geeforce windforce gtx 1070

Temp: GPU0: 70C GPU1: 67C GPU2: 59C GPU3: 69C
GPU0: 443 Sol/s GPU1: 445 Sol/s GPU2: 453 Sol/s GPU3: 445 Sol/s
Total speed: 1786 Sol/s
+-----+-------------+--------------+
| GPU | Power usage |  Efficiency  |
+-----+-------------+--------------+
|  0  |    129W     |  3.43 Sol/W  |
|  1  |    135W     |  3.30 Sol/W  |
|  2  |    134W     |  3.38 Sol/W  |
|  3  |    133W     |  3.35 Sol/W  |
+-----+-------------+--------------+

I have a corsair 1200W
MB: ASUS PRIME Z270-A
now power wall is only 615W

power limit at 140W each one
__CORE_OVERCLOCK_1=150
MEMORY_OVERCLOCK_1=580

Not enough info
Check your wdog logs, may be utilization dropped, internet had a hiccup, or .... 

[CyberGI]

GPU Card Specific settings question:

Y'all - I'm running 19-1.4 with three Zotec 1070 Minis. It spends a lot of time between ETH and FTC. I tried turning up the damNmad Algo-specific OC settings (stock in 1bash) and my ETH hashrate went from 82M to 66M. Is there a resource someone could point me to for recommended settings for these card?

Thanks,

Joe

[bwillyb]

Why my rig stops after 15 hours ?
I have 4X geeforce windforce gtx 1070

Temp: GPU0: 70C GPU1: 67C GPU2: 59C GPU3: 69C
GPU0: 443 Sol/s GPU1: 445 Sol/s GPU2: 453 Sol/s GPU3: 445 Sol/s
Total speed: 1786 Sol/s
+-----+-------------+--------------+
| GPU | Power usage |  Efficiency  |
+-----+-------------+--------------+
|  0  |    129W     |  3.43 Sol/W  |
|  1  |    135W     |  3.30 Sol/W  |
|  2  |    134W     |  3.38 Sol/W  |
|  3  |    133W     |  3.35 Sol/W  |
+-----+-------------+--------------+

I have a corsair 1200W
MB: ASUS PRIME Z270-A
now power wall is only 615W

power limit at 140W each one
__CORE_OVERCLOCK_1=150
MEMORY_OVERCLOCK_1=580

Not enough info
Check your wdog logs, may be utilization dropped, internet had a hiccup, or ....  

Mon Nov 27 00:30:56 CET 2017 - reboot in 10 seconds
Mon Nov 27 00:46:48 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 01:32:44 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 04:47:39 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 05:03:25 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 05:40:57 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 05:55:32 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 06:54:42 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 08:31:25 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 10:01:26 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 11:03:27 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 13:13:01 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 13:52:24 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 15:01:38 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 15:01:48 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 15:01:58 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 15:02:08 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 15:02:18 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 15:02:28 CET 2017 - Utilization is too low: restart 3main
Mon Nov 27 15:03:41 CET 2017 - Utilization is too low: restart 3main
Mon Nov 27 15:04:53 CET 2017 - Utilization is too low: restart 3main
Mon Nov 27 15:06:05 CET 2017 - Utilization is too low: restart 3main
Mon Nov 27 15:07:20 CET 2017 - Utilization is too low: restart 3main
Mon Nov 27 15:08:32 CET 2017 - Utilization is too low: reviving did not work so restarting system in 10 seconds
Mon Nov 27 16:57:48 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 17:11:23 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 17:45:45 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 18:14:25 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
Mon Nov 27 18:17:36 CET 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures

[CyberGI]

how check wdog logs?

In the bash shell, more/less/cat/tail (whichever is your favorite) 7_wdog_alertlog

Code:

~$ less 7_wdog_alertlog

HTH

[Stubo]

I tested both scenarios with a small change in your Debug code
Used ewbf and set threshold to 100 to see what happenes

added this at the end before done

Code:

    echo "Debug: JEEP=$JEEP, COUNT=$COUNT, RESTART=$RESTART REBOOTRESET=$REBOOTRESET"

With the original code, wdog resets REBOOTRESET after 5 cycles, with your proposal REBOOTRESET keeps adding up, and wont resets after 5.
So my conclusion is the original code should be correct.  

With the THRESHOLD set to 100, you would almost always have a utilization error so the miner would be restarting and eventually the host. This code is not intended for that situation. In fact, your test proves just the opposite of your conclusion. The REBOOTRESET should continue to increase until such a point as the watchdog detects normal mining operations at which point it will hit the else part part of the if (JEEP=0) and will find that REBOOTRESET is greater than 5 and will then set both REBOOTRESET and RESTART to 0.