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

[LuKePicci]

@fk2 I can't see any error from the miner output in any of logs you reported, try repeating the same thing using miner-log instead of master-log to focus only on miner output. Also report here the output you see in the gnome terminal including the "SCREEN …" command line used to launch the miner. Repeat all those tests with watchdog disabled otherwise it is hard to debug given it continuously try to recover
ewbf is closed source so you can't compile it, for the others may be you need a recompile but let's check if this is the actual issue.

@parentibule you still have nvCO installed as a service you have to uninstall or disable it by doing "sudo systemctl disable nvoc"

[gs777]

Thank you guys for nvOC v19.2.1
It works great! trying to mining BTG
The only issue I still can not upgrade EWBF to v3.0
I already run
cd ~/NVOC/mining
bash nvOC upgrade and miner upgrade
I upgraded NVidia driver to 390 version
but it always starts EWBF v0.4 with lots of rejects
Can you help me how to get EWBF v3.0 ruining?

also why do we need to set up BTG wallet address if we use MPH?

[LuKePicci]

ewbf 0.4 is the latest one for new equihash variants
read here: https://bitcointalk.org/index.php?topic=4466962.0

We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".

If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.

[gs777]

ewbf 0.4 is the latest one for new equihash variants
read here: https://bitcointalk.org/index.php?topic=4466962.0

We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".

If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.

Got it! Thanks for the info LuKePicci.
Quiet confusing...
My rigs work fine with equihash-MPH
but when I switch to BTG mining (EWBF v0.4) it was working with lots of rejects and eventually rig start to loosing cards/rebooting itself.
Last time before reboot 3 cards show 0 hash rate. This rig has 13 gtx1080
Also My BTG-MPH dashboard shows 0 kh/s all the time.
so I switched back to ZCL.
Now I'm trying to understand what I was doing wrong.
Can you help me?

[papampi_2]

ewbf 0.4 is the latest one for new equihash variants
read here: https://bitcointalk.org/index.php?topic=4466962.0

We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".

If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.

Got it! Thanks for the info LuKePicci.
Quiet confusing...
My rigs work fine with equihash-MPH
but when I switch to BTG mining (EWBF v0.4) it was working with lots of rejects and eventually rig start to loosing cards/rebooting itself.
Last time before reboot 3 cards show 0 hash rate. This rig has 13 gtx1080
Also My BTG-MPH dashboard shows 0 kh/s all the time.
so I switched back to ZCL.
Now I'm trying to understand what I was doing wrong.
Can you help me?

What are your BTG settings?
These are working with no problems for me

Code:

# Bitcoin Gold (BTG)
BTG_ADDRESS="username"
BTG_EXTENSION_ARGUMENTS="--algo 144_5 --pers BgoldPoW"
BTG_POOL="europe.equihash-hub.miningpoolhub.com"
BTG_PORT="20595"
BTG_WORKER="$WORKERNAME"

[LuKePicci]

My 11x1070 is also mining without issues on BTG, no rejects at all. Check your settings or ask in ewnf miner thread.

[gs777]

I had re flushed SSD because I wanna try it with old Nvidia drivers and disabled OC
so tomorrow I'll try it again.
My 13 GTX1080 is hashing only with Bminer.
With DSTM I have another problem
Somehow when nvOC starts few cards temperature control starts from 2C
not as other cards from min temp 30C even I have similar global setting for all cards.
Also few cards hash rate about 1/3 of the rest of the cards.
 
btw EWBF thread considers Cuda 8/EWBF v0.3 as a most stable BTG miner configuration

[fk2]

@fk2 I can't see any error from the miner output in any of logs you reported, try repeating the same thing using miner-log instead of master-log to focus only on miner output. Also report here the output you see in the gnome terminal including the "SCREEN …" command line used to launch the miner. Repeat all those tests with watchdog disabled otherwise it is hard to debug given it continuously try to recover
ewbf is closed source so you can't compile it, for the others may be you need a recompile but let's check if this is the actual issue.

Code:

m1@m1-desktop:~/NVOC/testing$ screen -r miner
There is no screen to be resumed matching miner.
m1@m1-desktop:~/NVOC/testing$

Code:

m1@m1-desktop:~$nvOC miner-log
    SCREEN -c /home/m1/NVOC/testing/screenrc-miner -dmSL miner /home/m1/NVOC/testing/miners/vertminer/ccminer -a lyra2v2 -o stratum+tcp://hub.miningpoolhub.com:20507 -u LuisenMine2.LuisenMine02 -p x -i 0
*** vertminer 1.0.2 for nVidia GPUs by turekaj ***
    Built with the nVidia CUDA Toolkit 8.0

  Originally based on tpruvot ccminer
VTC donation address:  VdMVwYLairTcYhz3QnNZtDNrB2wpaHE21q (turekaj)

1 percent dev fee to turekaj for miner improvements
1 percent dev fee to Vertcoin Dev Team (vertcoin.org)

[LuKePicci]

@gs777 let us know if old drivers behaves differently. The previous 0.3 version had a big problem, it was detecting one card at time very slowly, it took me 2 minutes to reach full hashrate, 0.4 detects all cards immediately.

@fk2 so the miner launches correctly, try to run it directly with the same command line you see in the output:

Code:

/home/m1/NVOC/testing/miners/vertminer/ccminer -a lyra2v2 -o stratum+tcp://hub.miningpoolhub.com:20507 -u LuisenMine2.LuisenMine02 -p x -i 0

You should be able to see any error message it produces.

[fk2]

ty Luke, after I did a nvOC miner-update with recomplile all it works again. Good to know how to approach problems the next time though, appreciate your help mate

[gs777]

Thank you guys for your help!!!

Wow, ZCL now is a king of the hill
Acording https://mining.alekseirubin.com/ right now it's even better then BTG.

I'll try it a bit later.

[fk2]

somebody knows if I can use i.e. 'NICE_NEOSCRYPT' or 'ZPOOL_NEOSCRYPT' as a switchable coin in the WTM profit switcher selection?
e: if so, what about adding new algos? simply add details in 1bash is enough or need to add some more info somewhere else??

[LuKePicci]

The short answer is: yes, you will be able to define new algos and miners by only editing 1bash and adding the necessary miner without editing any other file, not sure if already in 2.1 or in the next version but such a thing is on its way.

A little longer: you will have to define the new coin, map the new coin to this new algo, select a new miner for this algo, and eventually add configurations for the new miner, in 1bash. Under the hood, this requires the new miner package to self-contain some specific information like its command line template and a set of instructions that nvOC can execute to extract reporting data from its output (for example your current hashrate). The only thing you can do right now in 2.1-beta (without editing other files) is to define new coins, for existing algos, using one of the miner we have in the miners repository.

[LuKePicci]

somebody knows if I can use i.e. 'NICE_NEOSCRYPT' or 'ZPOOL_NEOSCRYPT' as a switchable coin in the WTM profit switcher selection?

Sure you can, even if nicehash in months from now decides to add Zhash support you can just define NICE_ZHASH and you are good to go since there is already ZHASH algo defined and a compatible miner.

[fk2]

reporting some problems

NICE_NEOSCRYPT:

Code:

m1@m1-desktop:~/NVOC/testing$ /home/m1/NVOC/testing/miners/KTccminer/ccminer -a neoscrypt -o stratum+tcp://neoscrypt.eu.nicehash.com:3341 -u 37MABGxni53Vwgjx6bkLALxkJBQiCUCcJu.ANYMine02 -p x -i 0                                                      ccminer 8.20-KlausT (64bit) for nVidia GPUs
Compiled with GCC 5.4 using Nvidia CUDA Toolkit 8.0

Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.

Illegal instruction

NICE_CRYPTONIGHT: Miner doesn't start because --i is invalid option. When I manually start the miner without -i it works.

NICE_ETHASH: Claymore miner starts but fails with 'can not convert blob3 data'

bash nvOC: when I 'bash nvOC restart:

Code:

m1@m1-desktop:~$nvOC restart
Failed to get unit file state for nvoc.service: No such file or directory
Stopping nvOC processes...

gnome-screensav killed (pid 3628)

...done.
Restarting nvOC tasks....

m1@m1-desktop:~/NVOC/testing$

seems to work but unfortunately

Code:

m1@m1-desktop:~/NVOC/testing$ screen -r miner
There is no screen to be resumed matching miner.
m1@m1-desktop:~/NVOC/testing$

so I

Code:

m1@m1-desktop:~/NVOC/testing$ sudo reboot -f
Rebooting.

wich does the trick

REPORT:

Code:

Operating System info:
Kernel        :  4.4.0-97-generic
OS            :  Ubuntu 16.04.3 LTS
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
nvidia driver :  387.34

nvOC info:
nvOC path     :  /home/m1/NVOC/testing
nvOC          :  nvOC_Ver=nvOC v0019-2.1 - Community Release" # Do not edit this
Report        :  0012
1bash         :  v0019-2.1.0029
1bash.template:  0033
3main         :  0024
5watchdog     :  0020
6tempcontrol  :  0006
wtm switch    :  0022
wtm profit    :  0004
pool switch   :  0002
minerinfo     :  0009

Hardware info:
Motherboard   :  ASUS STRIX Z270F GAMING  Rev 1.xx
BIOS ver.     :  1203 12/26/2017
CPU Model     :  Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores     :  2 (Cores + Threads)
Mem Total     :         3984516 kB
Mem Free      :         3179580 kB
Swap Total    :               0 kB
Swap Free     :               0 kB
Ethernet      :  Intel I219-V

CUDA SDK version
nvcc path     : /usr/local/cuda-8.0/bin/nvcc
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Tue_Jan_10_13:22:03_CST_2017
Cuda compilation tools, release 8.0, V8.0.61

nvOC is not installed as a service

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN   VENDOR   MODEL             REV MOUNTPOINT
sda    55.9G        disk    0       0 sata   ATA      Patriot Flare    21.1
├─sda1    9M vfat   part    0       0
├─sda2 51.9G ext4   part    0       0                                       /
└─sda3    4G swap   part    0       0

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1)

Local git branch and submodules status:
## 19-2.1...origin/19-2.1
 08e99b804d5f8a02acae076b53ddec7335d0d0d7 miners (remotes/origin/19-2.1)
## HEAD (no branch)
 cd6fab68823e247bb84dd1fa0448d5f75ec4917d ANXccminer/src (heads/master)
 aafe2d19b6d9eb07d942d70ced3049e9aed1c241 ASccminer/src (1.5.3-tpruvot-81-gaafe2d1)
 31865e0b846ad98e2ce99aeb9b28bb51d3be22db KTccminer-cryptonight/src (2.06)
 c5ab73837c8024f1e6b8fe7ad46e6881fb8366e6 KTccminer/src (1.4.6-tpruvot-1293-gc5ab738)
 7d41d49b92db27b9ab80270adaa92f6b06d1ef78 KXccminer/src (0.1)
 78dad7dd659eae72a07d2448de62b1946c1f2b41 MSFTccminer/src (2.2.5-rvn)
 8affcb9cd09edd917d33c1ed450f23400f571bdb NAccminer/src (v2.2-mod-r2)
 9e86bdd24ed7911b698f1d0ef61a4028fcbd13c5 SPccminer/src (1.5.81)
 c800f1a803e1b2074ed2a7c15023c096d0772048 SUPRminer/src (1.5)
 a81ab0f7a557a12a21d716dd03537bc8633fd176 TPccminer/src (2.2.5-tpruvot)
-bfd1c002f98f2d63f2174618838afc28cf4ffffe cpuOPT/src
 48b170a5828256600ca71e66d4c114af4e114236 vertminer/src (v1.0-beta.2)
 c0ab1734332d6472225d8ac7394f6fcba71aabc9 xmr-stak/src (2.4.4)

1bash settings:
1bash version .............: v0019-2.1.0029
LOCAL or REMOTE ...........: REMOTE
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO

Watchdog ..................: YES
SYSRQ Reboot ..............: NO
Watchdog Cycle ............: 15
GPU Utilization Threshold .: 70
Alternate Pool ............: NO

Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 65
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 50
MAXIMAL_FAN_SPEED .........: 95

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: NO
TELEGRAM_ALERTS ...: NO

HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: YES

POWERLIMIT MODE ...........: GPU_SPECIFIC
GPU0 Power Limit ..........: 170
GPU1 Power Limit ..........: 160
GPU2 Power Limit ..........: 160
GPU3 Power Limit ..........: 120
OVERCLOCK MODE ............: GPU_SPECIFIC
GPU0 Core Overclock ........: 120
GPU0 Memory Overclock ......: 1200
GPU1 Core Overclock ........: 120
GPU1 Memory Overclock ......: 1000
GPU2 Core Overclock ........: 120
GPU2 Memory Overclock ......: 1200
GPU3 Core Overclock ........: 120
GPU3 Memory Overclock ......: 1700

GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: LuisenMine02
plusCPU ...................: NO

AUTO_SWITCH ...............: NO
COIN ......................: NICE_ETHASH
ALGO ......................: ETHASH
MINER .....................: CLAYMORE
NICE_ETHASH WORKER ................: LuisenMine02
NICE_ETHASH ADDRESS ...............: ...
NICE_ETHASH POOL ..................: daggerhashimoto.usa.nicehash.com
NICE_ETHASH PORT ..................: 3353

[Muhammadaffandi10]

This is all very interesting to me because I currently use Windows 8.1 for my Nvidia Rig but in the past I have mined with my AMD rigs using EthOS and found it much more stable and reliable, and using much lower resources, etc - so a Linux solution for an Nvidia rig sounds great. I was considering trying the PiMP Nvidia version but when I tried that for my AMD rigs it confused the hell out of me.

Anyway, I have one big question because it doesn't seem clear to me from the small amount of info in this thread whether it will suit my rig. Reason being, my rig is currently 2 x  Gigabyte  gtx1070 G1 Gaming cards and 2 x Galax gtx 1060 6GB cards.

It seems from what I read above that when you set cc & mc overclock and powerlimit - this is one setting to apply to all cards on the rig. This is obviously suitable for the typical situation where people commonly use  multiple instances of 1 type of card on a rig, which I understand - people choose a GPU, buy however many of them and populate the rig with them.

What about a situation like mine though, where I have 2 of one GPU and 2 of another, so I need to be able to specify different OC and powerlimits for the different cards.

Currently in Windows 8.1 I just use MSI afterburner and set each card individually, so for example I mine ZEC and the 1070s are powerlimited to around 68%, core OC to +70 and mem OC to +700, while the 1060s are powerlimited to about 75%, core OC to +50 and me OC to +500. Using EWBF this is giving me approximately 1400sol/s using 500W at the wall.

Since the powerlimit in Linux seems to be set in watts rather than percent, one setting in a percentage (70% would probably work) but I would need to be able to set the 1070s to around 125W and the 160s to around 85W. The CC could all conceivably be set to +60 and MC to +500 or +600 but is there a way to set powerlimits individually for each card?

oh so gitu means more height so much

[gs777]

@gs777 let us know if old drivers behaves differently. The previous 0.3 version had a big problem, it was detecting one card at time very slowly, it took me 2 minutes to reach full hashrate, 0.4 detects all cards immediately.

@fk2 so the miner launches correctly, try to run it directly with the same command line you see in the output:

Code:

/home/m1/NVOC/testing/miners/vertminer/ccminer -a lyra2v2 -o stratum+tcp://hub.miningpoolhub.com:20507 -u LuisenMine2.LuisenMine02 -p x -i 0

You should be able to see any error message it produces.

Thank you papampi_2 and LuKePicci for your advises!

As appear problem was related to new drivers.
For current setup I re-flush SSD and didn't upgrade nothing
For now mining BTG for 12 hours without problem

Also I find out that on equihash minig
gtx1080 hushrate slightly improves when max temp set up to 74C and gtx1070 max temp 65C
In terms to get this I've setup Min fan temp to 30C and temp increment to 2C
I'm using external fans as well

[fk2]

somehow WTM switching between coins is failing regulary on 2.1 for me. I observed today ac ouple of times when one coin stops and the next one continues. Unfortunately nothing happens and then because of low GPU usage the watchdog reboots. After reboot the new coin runs fine.

Now I observe one where nothing happens:

Code:

[2018-07-28 09:53:17] GPU #3: Zotac GTX 1080, 38.41 MH/s
[2018-07-28 09:53:29] lyra2v2 block 2379190, diff 100802.726
[2018-07-28 09:53:38] lyra2v2 block 2379191, diff 100802.726

Error: Cannot find master process to attach to!
m1@m1-desktop:~$ screen -r miner
There is no screen to be resumed matching miner.
m1@m1-desktop:~$ screen -r miner
There is no screen to be resumed matching miner.
m1@m1-desktop:~$ screen -r miner
There is no screen to be resumed matching miner.

wihich logfiles could contain helpful informations to this?

edit: also saw this:

Code:

m1@m1-desktop:~$ nvidia-smi
Sat Jul 28 10:05:42 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.34                 Driver Version: 387.34                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 108...  Off  | 00000000:01:00.0 Off |                  N/A |
| 50%   44C    P0    89W / 170W |     47MiB / 11171MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 108...  Off  | 00000000:02:00.0 Off |                  N/A |
| 50%   33C    P8    10W / 160W |      9MiB / 11172MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 108...  Off  | 00000000:04:00.0 Off |                  N/A |
| 50%   30C    P8    10W / 160W |      9MiB / 11172MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 1080    Off  | 00000000:05:00.0 Off |                  N/A |
|ERR!   43C    P0   ERR! / 120W |      9MiB /  8114MiB |     79%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0       985      G   /usr/lib/xorg/Xorg                            31MiB |
|    0      1641      G   compiz                                        13MiB |
|    1       985      G   /usr/lib/xorg/Xorg                             6MiB |
|    2       985      G   /usr/lib/xorg/Xorg                             6MiB |
|    3       985      G   /usr/lib/xorg/Xorg                             6MiB |
+-----------------------------------------------------------------------------+
m1@m1-desktop:~$

[LuKePicci]

@fk2 let's see what we can do for each one:
 NICE_NEOSCRYPT: KTccminer illegal instruction should solve if you recompile KTccminer, at least this is how I usually sove such kind of errors, let me know it this solves, I see you have got already its sources so if you compiled it already it is a problem

 NICE_CRYPTONIGHT: default cryptonight miner is TPccminer, it does support the -i option as well but as I can see from the help the minimum valid value is 8, but nvOC has 0 by default in 1bash, please confirm me that setting intensity to somewhat valid solves the issue

*** ccminer 2.2.5 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 9.1 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some kernels from alexis78, djm34, djEzo, tsiv and krnlx.

Usage: ccminer [OPTIONS]
Options:
  ...
  -i  --intensity=N[,N] GPU intensity 8.0-25.0 (default: auto)
                        Decimals are allowed for fine tuning

 NICE_ETHASH: somebody else already got this error, this happens with claymore on nicehash only, you have to set some extra arguments to mine ethahs on nicehash with claymore, see some posts above from @papampi. You should also have a tip for this in a comment near NICE_ETHASH_EXTENSION_ARGUMENTS in 1bash

 nvOC restart: you can ignore that error about missing nvoc.service we will avoid this from showing up as well

 miner not starting: both nvOC restart command and WTM switcher restarts nvOC the same way, so the problem is the same, let us know to which coin it is switching. The only log that can help you troubleshoot this is the gnome-terminal window when nvOC runs in gnome-terminal. Search for lines starting with "SCREEN ... miner ..". If  the miner started but terminated immediately with errors you should be able to see it in nvOC miner-log command. You should see the previous miner output, then the same previously mentioned new miner command line starting with "SCREEN ...", then the new miner output/error. May not be related, but, what you have set in 1bash for "CONTROL_GPU_LED" ?

[fk2]

@Luke

NICE_NEOSCRYPT: I already did a recompile so that didn't fix

NICE_CRYPTONIGHT:

Code:

m1@m1-desktop:~/NVOC/testing$ /home/m1/NVOC/testing/miners/KTccminer-cryptonight/ccminer -o stratum+tcp://cryptonight.eu.nicehash.com:3355:3355 -u 37MQHRxni53Vwgjx6bkLALxkJBQiCUCcJu.LuisenMine02 -p x -i 8
    *** ccminer-cryptonight 2.06 (64 bit) for nVidia GPUs by tsiv and KlausT
    *** Built with GCC 5.4 using the Nvidia CUDA Toolkit 8.0

 tsiv's BTC donation address:   1JHDKp59t1RhHFXsTw2UQpR3F9BBz3R3cs
 KlausT's BTC donation address: 1QHH2dibyYL5iyMDk3UN4PVvFVtrWD8QKp
 for more donation addresses please read the README.txt
-----------------------------------------------------------------
[2018-07-29 00:03:42] 4 CUDA devices detected
/home/m1/NVOC/testing/miners/KTccminer-cryptonight/ccminer: invalid option -- 'i'

seems like it is not using the current version?! 2.06 vs  2.2.5 you mentioned

Code:

m1@m1-desktop:~/NVOC/testing/miners/KTccminer-cryptonight$ cat version
2.06
m1@m1-desktop:~/NVOC/testing/miners/KTccminer-cryptonight$ cd ..
m1@m1-desktop:~/NVOC/testing/miners$ cd KTccminer
m1@m1-desktop:~/NVOC/testing/miners/KTccminer$ cat version
8.20

NICE: ETHASH: Unfortunately there are no tips at the NICE options. I already added -allpools 1 which seems to be neccessary as stated by CLAYMORE. I removed -esm 2 which is neccessary for MPOH at the general claymore options. Now I receive

Code:

Received unknown response: {"id":null,"method":"mining.notify","params":["e0cf","0x9fe8b9220df9a7b1f0cac2b305b373c7c9586040b05e68161c5266d4b50774cd","0xaae835dbeaf495aa1ad8f3e09d05adbbd9612ae9f04f191df5de60f858aaaf56","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7",true]}
    SCREEN -c /home/m1/NVOC/testing/screenrc-miner -dmSL miner /home/m1/NVOC/testing/miners/claymore/latest/ethdcrminer64 -epool europe.ethash-hub.miningpoolhub.com:20555 -ewal LuisenMine2.LuisenMine02 -epsw x -mode 1 -dbg -1

edit: I get the same error when mining general coin with claymore without -esm 2 so this option seems to be neccessary

nvOC restart: It is not about the error message, its about that there is no mining process restarting.

miner not starting: well I'm strictly using the rig by remote so I won't be able to deliver any gnome-terminal stuff. Will be hard to anaylze this because I'm not able to watch console for every day. CONTROL_GPU_LED="YES"

edit: I think I was able to observer one more bad switching behaviour: was mining ETH and switched to ZCL, seems like it crashed the whole rig for today connection is timing out. last thing I was able to check is miner-log:

Code:

ETH: GPU0 50.051 Mh/s, GPU1 51.256 Mh/s, GPU2 50.041 Mh/s, GPU3 36.574 Mh/s

Sun Jul 29 01:11:33 MST 2018 - Miner is running, 3main killing miner
    SCREEN -c /home/m1/NVOC/testing/screenrc-miner -dmSL miner /home/m1/NVOC/testing/miners/bminer/latest/bminer -uri stratum://anyMine2.anyMine02:x@europe.equihash-hub.miningpoolhub.com:20594