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

[papampi]

Is there a script for a “rig offline” telegram notification that I’m missing? The telegram messages are awesome, but would be good to know if it powers down and stay down.

If system is going to be rebooted you will get notified from script that send the reboot command (watchdog or temp control), but if your rig freeze there is nothing to do.
You can set up an external watchdog like an RPi to check your rigs ping and ssh port and send you message if they were unreachable.

[LuKePicci]

Hi again, I have some news to share with you.

First of all, ethminer is finally adding an amazing "exit on cuda error" feature, I bet somebody here will love this.

Second, my extensive ethash miners testing revealed something strange with newer versions of all major miners, so I asket ethminer devs to give me some kind of changelog for the new stable release, and they did it.

Code:

ethminer 0.13.0 
 chfast released this 13 days ago 

Move stale detection to the source, eliminate solution reporting inefficiencies.
Minor cosmetic console output changes.
CUDA: Much faster job switch time. Higher stable hash rate.
CUDA: Refactored host software. Efficiency and simplification.
OCL: Added support for experimental kernel. Performs better on some cards.
Dropped support for CUDA 8.0
Blank API server fields correctly populated.
Compiler and linker build options optimized.

So I have to ask here, does the update script also update CUDA to version 9? If no how can I safely do that?

Last thing, I agreed with the ethminer devs it would be nice to have OC settings reported near the miner crash report, they said it wouldn't be so easy to do so I would ask here if it would be possible to include the output of "nvOC gpuinfo" near the error log snapshot.

[papampi]

Hi again, I have some news to share with you.

First of all, ethminer is finally adding an amazing "exit on cuda error" feature, I bet somebody here will love this.

Second, my extensive ethash miners testing revealed something strange with newer versions of all major miners, so I asket ethminer devs to give me some kind of changelog for the new stable release, and they did it.

Code:

ethminer 0.13.0 
 chfast released this 13 days ago 

Move stale detection to the source, eliminate solution reporting inefficiencies.
Minor cosmetic console output changes.
CUDA: Much faster job switch time. Higher stable hash rate.
CUDA: Refactored host software. Efficiency and simplification.
OCL: Added support for experimental kernel. Performs better on some cards.
Dropped support for CUDA 8.0
Blank API server fields correctly populated.
Compiler and linker build options optimized.

So I have to ask here, does the update script also update CUDA to version 9? If no how can I safely do that?

Last thing, I agreed with the ethminer devs it would be nice to have OC settings reported near the miner crash report, they said it wouldn't be so easy to do so I would ask here if it would be possible to include the output of "nvOC gpuinfo" near the error log snapshot.

Update script wont install cuda 9 because so many miners still don't have cuda 9 support and it will break them. You can use Nvidia Documentation on how to install Cuda 9.

I installed cuda 9 on a test rig and many miners start giving all kinds of errors, but I'm mining with ethminer 0.13.0 on my rigs with cuda 8 with no problems.

I have no idea how come some miners work and some doesn't with different cuda versions.
It would be nice if someone explain it to us

[WaveFront]

Hello,
What exactly is the difference in running "nvOC-19-2-update" and "./nvOC patch"?
Cheers

[papampi]

Hello,
What exactly is the difference in running "nvOC-19-2-update" and "./nvOC patch"?
Cheers

nvOC-19-2-update script, updates the nvOC miners, scripts and other mining related softwares.
./nvOC patch, stops all nvOC and mining processes and updates/upgrade ubuntu softwares so that no package gets broken.

[WaveFront]

Hello,
What exactly is the difference in running "nvOC-19-2-update" and "./nvOC patch"?
Cheers

nvOC-19-2-update script, updates the nvOC miners, scripts and other mining related softwares.
./nvOC patch, stops all nvOC and mining processes and updates/upgrade ubuntu softwares so that no package gets broken.

Thanks for the answer.
So both are necessary.

[Rig4p]

Having some more issues with the SALFTER_MPH switching setup.
When a Equihash or Ethash algo is determined to be the most profitable all is well.
Occasionally when a different algo is picked the miner crashes and shuts down after a while.
I am almost never watching the terminal at that time but decided to do some testing of the miner start lines in 3main to see if I could find the problem.

First problem I find is I cannot get the skein algo to start properly.
This is what my test command line looks like:

Code:

/home/m1/ASccminer/ccminer -a skein -x stratum+tcp://hub.miningpoolhub.com:12016 -u username.test -p x

And this is the resulting failure:

Code:

*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)

*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. project
*** Include some of the work of djm34, sp, tsiv and klausT.

[2018-02-05 12:39:28] Starting on stratum+tcp://hub.miningpoolhub.com:12016
[2018-02-05 12:39:28] NVML GPU monitoring enabled.
[2018-02-05 12:39:28] 1 miner thread started, using 'skein' algorithm.
[2018-02-05 12:39:28] Stratum authentication failed
[2018-02-05 12:39:28] ...retry after 30 seconds

Every algo in 3main I try this type test with seems to have a Stratum problem.
I have a valid username that I am using successfully with non-switching mining on MPH so I do not believe that is the issue.
I'm still working on it but thought asking for help was also wise. 

[fk1]

try editing the 1bash config with "sudo nano 1bash"
start mining with bash 2unix
try without stratum+tcp:// prefix

[papampi]

Having some more issues with the SALFTER_MPH switching setup.
When a Equihash or Ethash algo is determined to be the most profitable all is well.
Occasionally when a different algo is picked the miner crashes and shuts down after a while.
I am almost never watching the terminal at that time but decided to do some testing of the miner start lines in 3main to see if I could find the problem.

First problem I find is I cannot get the skein algo to start properly.
This is what my test command line looks like:

Code:

/home/m1/ASccminer/ccminer -a skein -x stratum+tcp://hub.miningpoolhub.com:12016 -u username.test -p x

And this is the resulting failure:

Code:

*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)

*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. project
*** Include some of the work of djm34, sp, tsiv and klausT.

[2018-02-05 12:39:28] Starting on stratum+tcp://hub.miningpoolhub.com:12016
[2018-02-05 12:39:28] NVML GPU monitoring enabled.
[2018-02-05 12:39:28] 1 miner thread started, using 'skein' algorithm.
[2018-02-05 12:39:28] Stratum authentication failed
[2018-02-05 12:39:28] ...retry after 30 seconds

Every algo in 3main I try this type test with seems to have a Stratum problem.
I have a valid username that I am using successfully with non-switching mining on MPH so I do not believe that is the issue.
I'm still working on it but thought asking for help was also wise.  

I think your test line should be :

Code:

/home/m1/ASccminer/ccminer -a skein -o stratum+tcp://hub.miningpoolhub.com:17016 -u username.test -p x

-o for server address and 17xxx for port

@fk1: no sudo needed  to edit 1bash

[Rig4p]

Having some more issues with the SALFTER_MPH switching setup.
When a Equihash or Ethash algo is determined to be the most profitable all is well.
Occasionally when a different algo is picked the miner crashes and shuts down after a while.
I am almost never watching the terminal at that time but decided to do some testing of the miner start lines in 3main to see if I could find the problem.

First problem I find is I cannot get the skein algo to start properly.
This is what my test command line looks like:

Code:

/home/m1/ASccminer/ccminer -a skein -x stratum+tcp://hub.miningpoolhub.com:12016 -u username.test -p x

And this is the resulting failure:

Code:

*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)

*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. project
*** Include some of the work of djm34, sp, tsiv and klausT.

[2018-02-05 12:39:28] Starting on stratum+tcp://hub.miningpoolhub.com:12016
[2018-02-05 12:39:28] NVML GPU monitoring enabled.
[2018-02-05 12:39:28] 1 miner thread started, using 'skein' algorithm.
[2018-02-05 12:39:28] Stratum authentication failed
[2018-02-05 12:39:28] ...retry after 30 seconds

Every algo in 3main I try this type test with seems to have a Stratum problem.
I have a valid username that I am using successfully with non-switching mining on MPH so I do not believe that is the issue.
I'm still working on it but thought asking for help was also wise.  

I think your test line should be :

Code:

/home/m1/ASccminer/ccminer -a skein -o stratum+tcp://hub.miningpoolhub.com:17016 -u username.test -p x

-o for server address and 17xxx for port

@fk1: no sudo needed  to edit 1bash

You are correct . That was one of my last attempts that also failed.
So when I test using your line I get:

Code:

*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)

*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. project
*** Include some of the work of djm34, sp, tsiv and klausT.

[2018-02-05 14:52:45] Starting on stratum+tcp://hub.miningpoolhub.com:17016
[2018-02-05 14:52:45] NVML GPU monitoring enabled.
[2018-02-05 14:52:45] 1 miner thread started, using 'skein' algorithm.
Illegal instruction

And at that point the miner fails back to the command line.

[LuKePicci]

Hi again, I have some news to share with you.

First of all, ethminer is finally adding an amazing "exit on cuda error" feature, I bet somebody here will love this.

Second, my extensive ethash miners testing revealed something strange with newer versions of all major miners, so I asket ethminer devs to give me some kind of changelog for the new stable release, and they did it.

Code:

ethminer 0.13.0 
 chfast released this 13 days ago 

Move stale detection to the source, eliminate solution reporting inefficiencies.
Minor cosmetic console output changes.
CUDA: Much faster job switch time. Higher stable hash rate.
CUDA: Refactored host software. Efficiency and simplification.
OCL: Added support for experimental kernel. Performs better on some cards.
Dropped support for CUDA 8.0
Blank API server fields correctly populated.
Compiler and linker build options optimized.

So I have to ask here, does the update script also update CUDA to version 9? If no how can I safely do that?

Last thing, I agreed with the ethminer devs it would be nice to have OC settings reported near the miner crash report, they said it wouldn't be so easy to do so I would ask here if it would be possible to include the output of "nvOC gpuinfo" near the error log snapshot.

Update script wont install cuda 9 because so many miners still don't have cuda 9 support and it will break them. You can use Nvidia Documentation on how to install Cuda 9.

I installed cuda 9 on a test rig and many miners start giving all kinds of errors, but I'm mining with ethminer 0.13.0 on my rigs with cuda 8 with no problems.

I have no idea how come some miners work and some doesn't with different cuda versions.
It would be nice if someone explain it to us

Sounds reasonable. Actually I started getting frequent cuda errors as soon as I updated to 0.13.0, I removed any OC and the error frequency drastically reduced but I was still getting errors too often (1,2 times per hour) with both latest claymore and latest ethminer. Meanwhile I noticed the reported OC'd hashrates from the ethminer log increased a little from an average of 179.5 MH/s to something around 182 but apart from the crashes my effective average hashrate reported by ethermine (the pool) with both ethminer and claymore (latest stable version of both) dropped from ~175 to 145 after a full-day test. The situation recovered as soon as I switched back to 0.12.0. I'm running 6x1070 and the currently installed nvidia driver version is 387.34

Have you noticed any improvements to the effective share rate after updating your miner? Which gpus/driver are you using?

After some minutes spent in the dev channel of ethminer I saw thare should exist a "kern.log" file from which we should be able to understand, also in case of OC-related crashes, which gpu actually crashed. I'm looking for it because every time I got a crash there were -I think always- CUDA errors reported in the console for all gpu's. Is it normal?

[CryptAtomeTrader44]

Having some more issues with the SALFTER_MPH switching setup.
When a Equihash or Ethash algo is determined to be the most profitable all is well.
Occasionally when a different algo is picked the miner crashes and shuts down after a while.
I am almost never watching the terminal at that time but decided to do some testing of the miner start lines in 3main to see if I could find the problem.

First problem I find is I cannot get the skein algo to start properly.
This is what my test command line looks like:

Code:

/home/m1/ASccminer/ccminer -a skein -x stratum+tcp://hub.miningpoolhub.com:12016 -u username.test -p x

And this is the resulting failure:

Code:

*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)

*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. project
*** Include some of the work of djm34, sp, tsiv and klausT.

[2018-02-05 12:39:28] Starting on stratum+tcp://hub.miningpoolhub.com:12016
[2018-02-05 12:39:28] NVML GPU monitoring enabled.
[2018-02-05 12:39:28] 1 miner thread started, using 'skein' algorithm.
[2018-02-05 12:39:28] Stratum authentication failed
[2018-02-05 12:39:28] ...retry after 30 seconds

Every algo in 3main I try this type test with seems to have a Stratum problem.
I have a valid username that I am using successfully with non-switching mining on MPH so I do not believe that is the issue.
I'm still working on it but thought asking for help was also wise.  

I think your test line should be :

Code:

/home/m1/ASccminer/ccminer -a skein -o stratum+tcp://hub.miningpoolhub.com:17016 -u username.test -p x

-o for server address and 17xxx for port

@fk1: no sudo needed  to edit 1bash

You are correct . That was one of my last attempts that also failed.
So when I test using your line I get:

Code:

*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)

*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. project
*** Include some of the work of djm34, sp, tsiv and klausT.

[2018-02-05 14:52:45] Starting on stratum+tcp://hub.miningpoolhub.com:17016
[2018-02-05 14:52:45] NVML GPU monitoring enabled.
[2018-02-05 14:52:45] 1 miner thread started, using 'skein' algorithm.
Illegal instruction

And at that point the miner fails back to the command line.

TRy /home/m1/TPccminer/ccminer fior minning skein algo.

When i search "skein" in 0miner script, i found these lines for DGB :

Code:

if [ $COIN == "DGB" ]
		then
			HCD='/home/m1/TPccminer/ccminer'
			ADDR="$DGB_ADDRESS"
			screen -dmSL miner $HCD -a skein -o stratum+tcp://$DGB_POOL:$DGB_PORT -u $ADDR -p $MINER_PWD -i $DGB_INTENSITY
fi

and theses lines for ZPOOL_SKEIN

Code:

if [ $COIN == "ZPOOL_SKEIN" ]
		then
			HCD='/home/m1/ASccminer/ccminer'
			screen -dmSL miner $HCD -a skein -o stratum+tcp://$ZPOOL_SKEIN_POOL:$ZPOOL_SKEIN_PORT -u $BTC_ADDRESS -p $MINER_PWD -i $ZPOOL_SKEIN_INTENSITY
fi

You can Also try all minning softwares and tell us which is the best for minning skein and for sure submit modifications for minning skein Algo.

Or simply try lower OC settings for mémory first and for CPU at last. be carefull with power too

[Rig4p]

Thanks for the tips. Unfortunately I get the same "Illegal instruction" error using TPccminer, ASccminer and KTccminer.
I'm sure it must be something in my command structure but I'm getting old and slow! 

[hashmasta83]

Another thing: I wanted to know what happened to this story of a guy who had posted and which he proposed to share the source of his code with us although he develloped for him initially.

Leenoox had asked him to share his code with graphics and statistics but I do not know if he did something ...

No idea, he just posted some screen shots.
The thing is writing a code for yourself and for everyone's use has many differences.

When you write for yourself there are bugs and limitations that you know them and you may or may not put time to fix them.
But when you publish a free code for public usage, some people think just because you share your code, they paid you for it and they let themselves tell you whatever they like.
Thats why so many people don't like to post their codes and just use it privately instead of posting it for public usage.

Sometimes I think that's the reason fullzero left his own project and maybe we should do the same too.
Just write for ourselves and use as it suits us ...

Honestly papampi and the developers if you ever feel like this, I (and probably many) would have no problem with you guys setting up a permanent 1% fee for using your OS.  Its only fair, as it takes a lot of your time and effort to develop, de-bug, and answer everyone's questions.  It's something you don't have to do but you do anyway.  I for one appreciate your efforts.

[Rig4p]

Likewise. I am not sure where people get off downing all the "free" work you guys are doing because your time is valuable.
I see pay-SW blogs on bitcointalk.org that are much less responsive than what the unofficial support crew is here.
I will say again that I greatly appreciate the effort and time spent.
Thanks!

[papampi]

Thanks for the tips. Unfortunately I get the same "Illegal instruction" error using TPccminer, ASccminer and KTccminer.
I'm sure it must be something in my command structure but I'm getting old and slow!  

Try to recompile them on your own rig, see how it goes ...

Have a look Here


P.S: Illegal instruction can be high intensity too, try with a lower like -i 14

[car1999]

Hi again, I have some news to share with you.

First of all, ethminer is finally adding an amazing "exit on cuda error" feature, I bet somebody here will love this.

Second, my extensive ethash miners testing revealed something strange with newer versions of all major miners, so I asket ethminer devs to give me some kind of changelog for the new stable release, and they did it.

Code:

ethminer 0.13.0 
 chfast released this 13 days ago 

Move stale detection to the source, eliminate solution reporting inefficiencies.
Minor cosmetic console output changes.
CUDA: Much faster job switch time. Higher stable hash rate.
CUDA: Refactored host software. Efficiency and simplification.
OCL: Added support for experimental kernel. Performs better on some cards.
Dropped support for CUDA 8.0
Blank API server fields correctly populated.
Compiler and linker build options optimized.

So I have to ask here, does the update script also update CUDA to version 9? If no how can I safely do that?

Last thing, I agreed with the ethminer devs it would be nice to have OC settings reported near the miner crash report, they said it wouldn't be so easy to do so I would ask here if it would be possible to include the output of "nvOC gpuinfo" near the error log snapshot.

Update script wont install cuda 9 because so many miners still don't have cuda 9 support and it will break them. You can use Nvidia Documentation on how to install Cuda 9.

I installed cuda 9 on a test rig and many miners start giving all kinds of errors, but I'm mining with ethminer 0.13.0 on my rigs with cuda 8 with no problems.

I have no idea how come some miners work and some doesn't with different cuda versions.
It would be nice if someone explain it to us

I've installed cuda9 in my rigs.It works well.
use cuda9:
sudo ln -s -T -f /usr/local/cuda-9.0 /usr/local/cuda
switch to cuda8:
sudo ln -s -T -f /usr/local/cuda-8.0 /usr/local/cuda

[LuKePicci]

You did it by repo packages or runfile?

[l4ncel0t]

Is there a script for a “rig offline” telegram notification that I’m missing? The telegram messages are awesome, but would be good to know if it powers down and stay down.

If system is going to be rebooted you will get notified from script that send the reboot command (watchdog or temp control), but if your rig freeze there is nothing to do.
You can set up an external watchdog like an RPi to check your rigs ping and ssh port and send you message if they were unreachable.

Hi
About this, does nvOC use the linux kernel watchdog ?

[WaveFront]

Hello,

Ever since I made the general nvOC upgrade (both using "nvOC-19-2-update" and "./nvOC patch"). I get a pretty annoying bug.
Every time that the miner is switching to XVG, 3main is freezing with the following errors:

Code:

LAUNCHING:  MINER
    
    
    SCREEN -dmSL miner /home/m1/ASccminer/ccminer -a lyra2v2 -o stratum+tcp://xvg-lyra.suprnova.cc:2596 -u WaveFront.orange-deep -p c=XVG -i 21
    
[screen is terminating]
/home/m1/3main: line 1129:   443 Terminated              screen -r miner

In order to add XVG as a coin I edited 0miner and 1bash.
I am running 2.0. now but maybe I could give a try to 2.1.




Here is my configuration

Code:

      Report generator v0019-2.0.002 by leenoox      


[code]
 
Software info: 
Report ver    :  v0019-2.0.002 
nvOC (1bash)  :  nvOC v0019-2.0 - Community Release 
nvOC (3main)  :  nvOC v0019-2.0 - Community Release   
1bash ver     :  v0019-2.0.003 
3main ver     :  v0019-2.0.006                   
5watchdog ver :  v0019-2.0.011    
6tempcontrol v:  v0019-2.0.003    
wtm switch ver:  v0019-2.0.0011   
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 
 
Hardware info: 
Motherboard   :  ASRock H110 Pro BTC+           
BIOS ver.     :  P1.10 06/20/2017 
CPU Model     :  Core(TM) i3-7100T CPU @ 3.40GHz 
CPU Cores     :  4 (Cores + Threads) 
Mem Total     :         4001032 kB 
Mem Free      :          475092 kB 
Swap Total    :               0 kB 
Swap Free     :               0 kB 
Ethernet      :  Intel I219-V (rev 31)

HDD and Partion info:
NAME     SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR   MODEL             REV MOUNTPOINT
sda    115.7G        disk    1       1 usb  SanDisk  Ultra Fit        1.00 
|-sda1     9M vfat   part    1       1                                     /media/m1/12D3-A869
`-sda2  13.7G ext4   part    1       1                                     /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)

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

Temp Control ..............: YES
TARGET_TEMP ...............: 73
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 90
MINIMAL_FAN_SPEED .........: 50

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: YES
REBOOT_TIMEOUT_IN_MINUTES .: 2880
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: NO
TELEGRAM_ALERTS .: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 60
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN

P106_100_FULL_HEADLESS_MODE: NO
GPUPowerMizerMode_Adjust...: NO
POWERLIMIT (global) .......: YES
POWERLIMIT_WATTS ..........: 80
CORE_OVERCLOCK (global)....: 120
MEMORY_OVERCLOCK (global) .: 100
MANUAL_FAN ................: NO
ALGO_SPECIFIC_OC ..........: YES

GLOBAL_WORKERNAME .........: YES
AUTO_WORKERNAME ...........: CUSTOM
CUSTOM_WORKERNAME .........: orange-deep
plusCPU ...................: NO

ZM_or_EWBF ................: ZM

COIN ......................: XVG
XVG_WORKER ................: orange-deep
XVG_ADDRESS ...............: WaveFron...
XVG_POOL ..................: xvg-lyra.suprnova.cc
XVG_PORT ..................: 2596
XVG_INTENSITY .............: 21

[/code]