[ mining os ] nvoc

[CryptAtomeTrader44]

Questions about Vivo Coin, i need some advices about it :

It seems that this coin be stable and profitable since i can see it in WTM coin list, but we don't know who is behind this coin not even on their own official page ! 
Is this coin is more risky than others listed on WTM ? 
I wonder for weeks on this piece ...

1/ Is anyone tried this neoscrypt miner software ?
NSGminer : https://bitcointalk.org/index.php?topic=712650.0
if so, did you get better performance (hash rate and power consumption) than with other mining software?

2/ Is someone here mine Vivo coin ? If so, can you tell us which pool do you choose because there are a lot listed on their btctalk thread but, i can't détermine which is better to choose.
(https://bitcointalk.org/index.php?topic=2110690.0)

Nobody has answers to my questions about this mining software or the choice of pools for VIVO?

I tried to compile myself NSGminer but it seems that the scripts are no longer operational and I have a git error while running the file autogen.sh

Are my questions understandable or should I rephrase them?

help me please

[killeriq]

hello,

could you please add DSTM miner please? (https://bitcointalk.org/index.php?topic=2021765.0)

Thanks

Its already there with the ZM name

1bash:

Code:

ZM_or_EWBF="ZM"  # choose ZM or EWBF miner

# DSTM ZM Miner optional arguments add "--telemetry=$IPW:42000" if you want web info
ZM_OPTS=""

Ah ok thanks cos in version i just downloaded "v0019-1.4"

its only

Code:

ZM_or_EWBF="ZM"  # choose  ZM  or  EWBF

nothing else with "ZM" there also none "# DSTM ZM Miner optional arguments add "--telemetry=$IPW:42000" if you want web info
ZM_OPTS=""

Thanks

Added it like this:

ZEC_POOL="zec-eu1.nanopool.org"
ZEC_PORT="6666"
ZM_OPTS="--telemetry=0.0.0.0:4029"

but seems like web page doesnt work (using the same style on other mining OS)

[Stubo]

hello,

could you please add DSTM miner please? (https://bitcointalk.org/index.php?topic=2021765.0)

Thanks

Its already there with the ZM name

1bash:

Code:

ZM_or_EWBF="ZM"  # choose ZM or EWBF miner

# DSTM ZM Miner optional arguments add "--telemetry=$IPW:42000" if you want web info
ZM_OPTS=""

Ah ok thanks cos in version i just downloaded "v0019-1.4"

its only

Code:

ZM_or_EWBF="ZM"  # choose  ZM  or  EWBF

nothing else with "ZM" there also none "# DSTM ZM Miner optional arguments add "--telemetry=$IPW:42000" if you want web info
ZM_OPTS=""

Thanks

Added it like this:

ZEC_POOL="zec-eu1.nanopool.org"
ZEC_PORT="6666"
ZM_OPTS="--telemetry=0.0.0.0:4029"

but seems like web page doesnt work (using the same style on other mining OS)

Have you tried $IPW instead of 0.0.0.0? IIRC, DSTM's miner is picky about what is used for the IP and $IPW should be your rig's IP address as determined by code in 1bash.

[papampi]

hello,

could you please add DSTM miner please? (https://bitcointalk.org/index.php?topic=2021765.0)

Thanks

Its already there with the ZM name

1bash:

Code:

ZM_or_EWBF="ZM"  # choose ZM or EWBF miner

# DSTM ZM Miner optional arguments add "--telemetry=$IPW:42000" if you want web info
ZM_OPTS=""

Ah ok thanks cos in version i just downloaded "v0019-1.4"

its only

Code:

ZM_or_EWBF="ZM"  # choose  ZM  or  EWBF

nothing else with "ZM" there also none "# DSTM ZM Miner optional arguments add "--telemetry=$IPW:42000" if you want web info
ZM_OPTS=""

Thanks

Added it like this:

ZEC_POOL="zec-eu1.nanopool.org"
ZEC_PORT="6666"
ZM_OPTS="--telemetry=0.0.0.0:4029"

but seems like web page doesnt work (using the same style on other mining OS)

Those options are for 19-2.0 Community Release not 19-1.4

[killeriq]

ah ok , so pleaase where do i download the 19-2.0?

Also how do i get in there  this newer version DSTM 0.5.7 - many thinks fixed vs 0.5.2


thanks

EDIT:
Found it...find the upgrade script and then...

Download this script
nvOC_19-02_DSTM_ZM_MINER_0_5_7_UPDATE

And run :
Code:
bash nvOC_19-02_DSTM_ZM_MINER_0_5_7_UPDATE

so lets try;)

[CryptAtomeTrader44]

Questions about Vivo Coin, i need some advices about it :

It seems that this coin be stable and profitable since i can see it in WTM coin list, but we don't know who is behind this coin not even on their own official page !  
Is this coin is more risky than others listed on WTM ?  
I wonder for weeks on this piece ...

1/ Is anyone tried this neoscrypt miner software ?
NSGminer : https://bitcointalk.org/index.php?topic=712650.0
if so, did you get better performance (hash rate and power consumption) than with other mining software?

2/ Is someone here mine Vivo coin ? If so, can you tell us which pool do you choose because there are a lot listed on their btctalk thread but, i can't détermine which is better to choose.
(https://bitcointalk.org/index.php?topic=2110690.0)

Nobody has answers to my questions about this mining software or the choice of pools for VIVO?

I tried to compile myself NSGminer but it seems that the scripts are no longer operational and I have a git error while running the file autogen.sh

Are my questions understandable or should I rephrase them?

help me please

Since nobody answered me on the VIVO Pool I read again their thread btctalk and I chose the pool which seems to me the most promising in view of its hashrate in neoscrypt: https://www.unimining.net/ at 0.5% fee
This other pool has the interface quite similar to that of suprnova appears equally interesting: https://aikapool.com/vivo/index.php
but to check in the long term concerning its stability online because at the time I write these lines, the site is no longer reachable ..... 1% fee

On the other hand, I had to modify the file 0miner because of the password which makes it possible to indicate the coin to be mined.

so I deleted the variable

Code:

MINER_PWD = "x" # Set the miner password. Default: x

in the 0miner file, which produces this lines:

Line 394

Code:

  screen -dmSL miner $HCD -a neoscrypt -o stratum+tcp://$TZC_POOL:$TZC_PORT -u $ADDR -p c=TZC -i $TZC_INTENSITY

Line 401

Code:

  screen -dmSL miner $HCD -a neoscrypt -o stratum+tcp://$VIVO_POOL:$VIVO_PORT -u $ ADDR -p c=VIVO -i $VIVO_INTENSITY

In the 1bash, I modified like this:

Code:

#Trezarcoin (TZC)
# ## No need to add add stratum + tcp: // to server address
TZC_WORKER = "$ WORKERNAME"
TZC_ADDRESS = "TtpFnwJ9YnpMGk4YG93q5nuy2HkQH6jLe3" # Cryptopia Wallet Address
TZC_POOL = "pool.unimining.net"
TZC_PORT = "4237"
TZC_INTENSITY = "21"

Code:

#Vivo (VIVO)
# ## No need to add add stratum + tcp: // to server address
VIVO_WORKER = "$ WORKERNAME"
VIVO_ADDRESS = "VPnkB5GtGwnYV5TvvDT5NhvaAHRzvHbXbw" # Cryptopia Wallet Address
VIVO_POOL = "pool.unimining.net"
VIVO_PORT = "4233"
VIVO_INTENSITY = "21"

[killeriq]

Hello,

Please could someone explain me or point me to right direction?

Im bit confused about OC settings:

there are multiple OC parts:


1. This one i understand is the MAIN setting for all card/algo/hash

I either enable/disable PowerLimit, but the CORE and MEM stays

Code:

# OC (overclock) and Power Limit settings              #
#                                                      #
########################################################

POWERLIMIT="NO"            # YES or NO # Choose YES to set Global Power Limit for all GPU's

POWERLIMIT_WATTS=75         # Global Power Limit in watts for all GPU's. If enabled, INDIVIDUAL settings will override this. 

__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings

MEMORY_OVERCLOCK=100        # Global Memory overclock for all GPU's if not using INDIVIDUAL settings

2. Set this as NO - dont want to be ALGO (coin) specific

Code:

# Default values set at the end of 1bash are for 1060, remember to set yours accordingly.
ALGO_SPECIFIC_OC="NO"       # YES or NO # See the description above

3. This one i thought its hash (equihash) specific OC setting, but it wont take it - ignores
So what is it for? not sure what relation it has with FANs

Code:

# ENSURE YOU USE MINER_TEMP_CONTROL for fanspeed

equihash_POWERLIMIT_WATTS=115
__equihash_CORE_OVERCLOCK=110
equihash_MEMORY_OVERCLOCK=500

4. Those are per card in case i have different models in the rig

Code:

########################################################
#                                                      #
# INDIVIDUAL Power Limit, Temp and Clock settings      #
#                                                      #
########################################################

# Settings below are for rigs using INDIVIDUAL powerlimit / target temps / clocks only
# If set to YES, the INDIVIDUAL settings will override the GLOBAL settings

INDIVIDUAL_POWERLIMIT="NO"    # YES or NO

# Set individual powerlimits here if INDIVIDUAL_POWERLIMIT="YES"
INDIVIDUAL_POWERLIMIT_0=100
INDIVIDUAL_POWERLIMIT_1=100

5. Not sure why are also HASH specific OC settings and also ALGO/COIN specific - bit confused 

Code:

# ALGO_SPECIFIC_OC settings                            #
#                                                      #
########################################################

# ALGO_SPECIFIC_OC settings
# OC settings you can use based on COIN or ALGO (how ever you want to categorize them)
# Deafault values are for 1060 check http://krypto-mining.blogspot.co.uk/ for other OC values

if [ $ALGO_SPECIFIC_OC == "YES" ]
then

  # Equihash
  if [ $COIN == "BTG" -o $COIN == "ZEC" -o $COIN == "ZEN" -o $COIN == "HUSH" -o $COIN == "ZCL" -o $COIN == "KMD" -o $COIN == "ZPOOL_EQUIHASH" -o $COIN == "MPH_EQUIHASH" -o $COIN == "NICE_EQUIHASH" -o $COIN == "VOTE" ]
  then
    ALGORITHM="EQUIHASH"
    POWERLIMIT_WATTS=130
    __CORE_OVERCLOCK=150
    MEMORY_OVERCLOCK=800
  fi

[Moscut]

hi all - noob here.

is it possible to use Alexis78 miner for lyra2REv2 ? i get here much better results than other like tpruvot ...

also how can i install Teamviewer? Thanks

[papampi]

Hello,

Please could someone explain me or point me to right direction?

Im bit confused about OC settings:

there are multiple OC parts:


1. This one i understand is the MAIN setting for all card/algo/hash

I either enable/disable PowerLimit, but the CORE and MEM stays

Code:

# OC (overclock) and Power Limit settings              #
#                                                      #
########################################################

POWERLIMIT="NO"            # YES or NO # Choose YES to set Global Power Limit for all GPU's

POWERLIMIT_WATTS=75         # Global Power Limit in watts for all GPU's. If enabled, INDIVIDUAL settings will override this. 

__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings

MEMORY_OVERCLOCK=100        # Global Memory overclock for all GPU's if not using INDIVIDUAL settings

2. Set this as NO - dont want to be ALGO (coin) specific

Code:

# Default values set at the end of 1bash are for 1060, remember to set yours accordingly.
ALGO_SPECIFIC_OC="NO"       # YES or NO # See the description above

3. This one i thought its hash (equihash) specific OC setting, but it wont take it - ignores
So what is it for? not sure what relation it has with FANs

Code:

# ENSURE YOU USE MINER_TEMP_CONTROL for fanspeed

equihash_POWERLIMIT_WATTS=115
__equihash_CORE_OVERCLOCK=110
equihash_MEMORY_OVERCLOCK=500

4. Those are per card in case i have different models in the rig

Code:

########################################################
#                                                      #
# INDIVIDUAL Power Limit, Temp and Clock settings      #
#                                                      #
########################################################

# Settings below are for rigs using INDIVIDUAL powerlimit / target temps / clocks only
# If set to YES, the INDIVIDUAL settings will override the GLOBAL settings

INDIVIDUAL_POWERLIMIT="NO"    # YES or NO

# Set individual powerlimits here if INDIVIDUAL_POWERLIMIT="YES"
INDIVIDUAL_POWERLIMIT_0=100
INDIVIDUAL_POWERLIMIT_1=100

5. Not sure why are also HASH specific OC settings and also ALGO/COIN specific - bit confused 

Code:

# ALGO_SPECIFIC_OC settings                            #
#                                                      #
########################################################

# ALGO_SPECIFIC_OC settings
# OC settings you can use based on COIN or ALGO (how ever you want to categorize them)
# Deafault values are for 1060 check http://krypto-mining.blogspot.co.uk/ for other OC values

if [ $ALGO_SPECIFIC_OC == "YES" ]
then

  # Equihash
  if [ $COIN == "BTG" -o $COIN == "ZEC" -o $COIN == "ZEN" -o $COIN == "HUSH" -o $COIN == "ZCL" -o $COIN == "KMD" -o $COIN == "ZPOOL_EQUIHASH" -o $COIN == "MPH_EQUIHASH" -o $COIN == "NICE_EQUIHASH" -o $COIN == "VOTE" ]
  then
    ALGORITHM="EQUIHASH"
    POWERLIMIT_WATTS=130
    __CORE_OVERCLOCK=150
    MEMORY_OVERCLOCK=800
  fi

Your part 3 is for salfter auto switch... Don't know if there is a better way to show it

Code:

########################################################
#                                                      #
# SALFTER_NICEHASH_PROFIT_SWITCHING &                  #
# SALFTER_MPH_PROFIT_SWITCHING Settings                #
#                                                      #
########################################################

CURRENCY=USD

POWER_COST=0.20

MINIMUM_PROFIT=0.0

MPH_USERNAME=replace_with_your_MPH_username

PAYMENT_ADDRESS="$BTC_ADDRESS"

WORKER_NAME="$WORKERNAME"

PROFIT_CHECK_TIMEOUT=600

# ENSURE YOU USE MINER_TEMP_CONTROL for fanspeed

daggerhashimoto_POWERLIMIT_WATTS=120
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100

If you want individual OC its the last part of 1bash your part 5

[wi$em@n]

HI,
after applying the latest version of nvOC-19-2-update I've got this in the MINER_TEMP_CONTROL:

GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds

Why power has become "Not Supported"?

[CryptAtomeTrader44]

Since nobody answered me on the VIVO Pool I read again their thread btctalk and I chose the pool which seems to me the most promising in view of its hashrate in neoscrypt: https://www.unimining.net/ at 0.5% fee
This other pool has the interface quite similar to that of suprnova appears equally interesting: https://aikapool.com/vivo/index.php
but to check in the long term concerning its stability online because at the time I write these lines, the site is no longer reachable ..... 1% fee

On the other hand, I had to modify the file 0miner because of the password which makes it possible to indicate the coin to be mined.

so I deleted the variable

Code:

MINER_PWD = "x" # Set the miner password. Default: x

in the 0miner file, which produces this lines:

Line 394

Code:

  screen -dmSL miner $HCD -a neoscrypt -o stratum+tcp://$TZC_POOL:$TZC_PORT -u $ADDR -p c=TZC -i $TZC_INTENSITY

Line 401

Code:

  screen -dmSL miner $HCD -a neoscrypt -o stratum+tcp://$VIVO_POOL:$VIVO_PORT -u $ ADDR -p c=VIVO -i $VIVO_INTENSITY

In the 1bash, I modified like this:

Code:

#Trezarcoin (TZC)
# ## No need to add add stratum + tcp: // to server address
TZC_WORKER = "$ WORKERNAME"
TZC_ADDRESS = "TtpFnwJ9YnpMGk4YG93q5nuy2HkQH6jLe3" # Cryptopia Wallet Address
TZC_POOL = "pool.unimining.net"
TZC_PORT = "4237"
TZC_INTENSITY = "21"

Code:

#Vivo (VIVO)
# ## No need to add add stratum + tcp: // to server address
VIVO_WORKER = "$ WORKERNAME"
VIVO_ADDRESS = "VPnkB5GtGwnYV5TvvDT5NhvaAHRzvHbXbw" # Cryptopia Wallet Address
VIVO_POOL = "pool.unimining.net"
VIVO_PORT = "4233"
VIVO_INTENSITY = "21"

Well, in fact I have never succeed to mine VIVO and it seems that several pools have synchronization pb with this blockchain. I just read this on the BTCTalk thread of the pool I chose:
https://bitcointalk.org/index.php?topic=2156784.msg26264470#msg26264470

The post also talks about FORK of VIVO ...

It will wait until the end of the year, or even the next year for me to put the computing power

[Stubo]

HI,
after applying the latest version of nvOC-19-2-update I've got this in the MINER_TEMP_CONTROL:

GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds

Why power has become "Not Supported"?

Ah. Are you are using the 1050 GPU? For that GPU, Nvidia's linux API does not support reading the power. Hence, reading it returns [Not Supported]. It is the only GPU (so far) that we have seen like that. As far as I know, it has little to no impact on the temp control for 19-2.0 but leenoox can correct me if I am wrong.

[joshuajones02]

hi all - noob here.

(1)
is it possible to use Alexis78 miner for lyra2REv2 ? i get here much better results than other like tpruvot ...

(2)
also how can i install Teamviewer? Thanks

(1)
I'm not sure if Alexis version is there but you can download the version you want on the rig on your own and then update the dir for the location of the alexis miner under the coin that you are mining's settings in 3main.


(2)
You don't install it, just enable it in the 1bash file.

Code:

TEAMVIEWER="YES"                 # YES NO

[papampi]

hi all - noob here.

(1)
is it possible to use Alexis78 miner for lyra2REv2 ? i get here much better results than other like tpruvot ...

(2)
also how can i install Teamviewer? Thanks

(1)
I'm not sure if Alexis version is there but you can download the version you want on the rig on your own and then update the dir for the location of the alexis miner under the coin that you are mining's settings in 3main.


(2)
You don't install it, just enable it in the 1bash file.

Code:

TEAMVIEWER="YES"                 # YES NO

alexis ccminer is already available in nvoc

Code:

/home/m1/ASccminer

If you are on 19-2.0 its the default miner for lyra2rev2, if not you should edit 3main

[wi$em@n]

HI,
after applying the latest version of nvOC-19-2-update I've got this in the MINER_TEMP_CONTROL:

GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds

Why power has become "Not Supported"?

Ah. Are you are using the 1050 GPU? For that GPU, Nvidia's linux API does not support reading the power. Hence, reading it returns [Not Supported]. It is the only GPU (so far) that we have seen like that. As far as I know, it has little to no impact on the temp control for 19-2.0 but leenoox can correct me if I am wrong.

It is 1050ti. On nvOC-19-1.4 and early versions of nvOC-19-2 it was like this:

GPU 0, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70
GPU 1, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70
GPU 2, Target temp: 75, Current: 75, Diff: 0, Fan: 50, Power: 70
GPU 3, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70
GPU 4, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70
GPU 5, Target temp: 75, Current: 66, Diff: 9, Fan: 50, Power: 70

Sun Dec 17 11:52:06 MST 2017 - All good, will check again soon

[Stubo]

HI,
after applying the latest version of nvOC-19-2-update I've got this in the MINER_TEMP_CONTROL:

GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds

Why power has become "Not Supported"?

Ah. Are you are using the 1050 GPU? For that GPU, Nvidia's linux API does not support reading the power. Hence, reading it returns [Not Supported]. It is the only GPU (so far) that we have seen like that. As far as I know, it has little to no impact on the temp control for 19-2.0 but leenoox can correct me if I am wrong.

It is 1050ti. On nvOC-19-1.4 and early versions of nvOC-19-2 it was like this:

GPU 0, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70
GPU 1, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70
GPU 2, Target temp: 75, Current: 75, Diff: 0, Fan: 50, Power: 70
GPU 3, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70
GPU 4, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70
GPU 5, Target temp: 75, Current: 66, Diff: 9, Fan: 50, Power: 70

Sun Dec 17 11:52:06 MST 2017 - All good, will check again soon

Hmm. Try the this on your rig and see what it returns:

Code:

nvidia-smi --query-gpu=power.draw --format=csv

[killeriq]

Hello,

Please could someone explain me or point me to right direction?

Im bit confused about OC settings:

there are multiple OC parts:


1. This one i understand is the MAIN setting for all card/algo/hash

I either enable/disable PowerLimit, but the CORE and MEM stays

Code:

# OC (overclock) and Power Limit settings              #
#                                                      #
########################################################

POWERLIMIT="NO"            # YES or NO # Choose YES to set Global Power Limit for all GPU's

POWERLIMIT_WATTS=75         # Global Power Limit in watts for all GPU's. If enabled, INDIVIDUAL settings will override this. 

__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings

MEMORY_OVERCLOCK=100        # Global Memory overclock for all GPU's if not using INDIVIDUAL settings

2. Set this as NO - dont want to be ALGO (coin) specific

Code:

# Default values set at the end of 1bash are for 1060, remember to set yours accordingly.
ALGO_SPECIFIC_OC="NO"       # YES or NO # See the description above

3. This one i thought its hash (equihash) specific OC setting, but it wont take it - ignores
So what is it for? not sure what relation it has with FANs

Code:

# ENSURE YOU USE MINER_TEMP_CONTROL for fanspeed

equihash_POWERLIMIT_WATTS=115
__equihash_CORE_OVERCLOCK=110
equihash_MEMORY_OVERCLOCK=500

4. Those are per card in case i have different models in the rig

Code:

########################################################
#                                                      #
# INDIVIDUAL Power Limit, Temp and Clock settings      #
#                                                      #
########################################################

# Settings below are for rigs using INDIVIDUAL powerlimit / target temps / clocks only
# If set to YES, the INDIVIDUAL settings will override the GLOBAL settings

INDIVIDUAL_POWERLIMIT="NO"    # YES or NO

# Set individual powerlimits here if INDIVIDUAL_POWERLIMIT="YES"
INDIVIDUAL_POWERLIMIT_0=100
INDIVIDUAL_POWERLIMIT_1=100

5. Not sure why are also HASH specific OC settings and also ALGO/COIN specific - bit confused 

Code:

# ALGO_SPECIFIC_OC settings                            #
#                                                      #
########################################################

# ALGO_SPECIFIC_OC settings
# OC settings you can use based on COIN or ALGO (how ever you want to categorize them)
# Deafault values are for 1060 check http://krypto-mining.blogspot.co.uk/ for other OC values

if [ $ALGO_SPECIFIC_OC == "YES" ]
then

  # Equihash
  if [ $COIN == "BTG" -o $COIN == "ZEC" -o $COIN == "ZEN" -o $COIN == "HUSH" -o $COIN == "ZCL" -o $COIN == "KMD" -o $COIN == "ZPOOL_EQUIHASH" -o $COIN == "MPH_EQUIHASH" -o $COIN == "NICE_EQUIHASH" -o $COIN == "VOTE" ]
  then
    ALGORITHM="EQUIHASH"
    POWERLIMIT_WATTS=130
    __CORE_OVERCLOCK=150
    MEMORY_OVERCLOCK=800
  fi

Your part 3 is for salfter auto switch... Don't know if there is a better way to show it

Code:

########################################################
#                                                      #
# SALFTER_NICEHASH_PROFIT_SWITCHING &                  #
# SALFTER_MPH_PROFIT_SWITCHING Settings                #
#                                                      #
########################################################

CURRENCY=USD

POWER_COST=0.20

MINIMUM_PROFIT=0.0

MPH_USERNAME=replace_with_your_MPH_username

PAYMENT_ADDRESS="$BTC_ADDRESS"

WORKER_NAME="$WORKERNAME"

PROFIT_CHECK_TIMEOUT=600

# ENSURE YOU USE MINER_TEMP_CONTROL for fanspeed

daggerhashimoto_POWERLIMIT_WATTS=120
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100

If you want individual OC its the last part of 1bash your part 5

Ah the no.3 its only setting when im using the SALFTER_MPH_PROFIT_SWITCHING Settings  ?
If i dont use that switcher (this setting WTM_AUTO_SWITCH="NO"  ) it ignores the OC values. Did i get it right?

No.1

Code:

# OC (overclock) and Power Limit settings              #
#                                                      #
########################################################

POWERLIMIT="NO"            # YES or NO # Choose YES to set Global Power Limit for all GPU's

POWERLIMIT_WATTS=75         # Global Power Limit in watts for all GPU's. If enabled, INDIVIDUAL settings will override this. 

__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings

MEMORY_OVERCLOCK=100        # Global Memory overclock for all GPU's if not using INDIVIDUAL settings

Those are OC setting in TOP of other ?

POWERLIMIT="NO" - will be able to take Watts from values bellow ALGO OC (No.5) and Individual (No.4)

POWERLIMIT="YES" -  if i set POWERLIMIT_WATTS=75 other No.4/5 wont go above 75?

How are those 2 managed:
__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings
MEMORY_OVERCLOCK=100

- does it overwrite also ALGO OC? (No.5)?

Thanks

[monck]

Yes it should be terminated and start again
WTM Auto Switch Logic is :
if ALGO_SPECIFIC_OC="NO", it only restart miner and watchdog (to prevent wdog from catching low util and restart again)
if ALGO_SPECIFIC_OC="YES", it checks coins algo
if algo changed, it restart watchdog, temp control and 3main so specific algo takes effect
if algo not changed, it only restart watchdog and miner

You will see a miner terminated in gnome-terminal when algo not changed, if you check wtm tab you see it started with new command line and you can watch miner output log with:

Code:

~/nvOC miner-log

I have some ideas for next version to show the miner info in a new tab when miner terminated.

Thanks for explanation - the problem is that nothing is restarting after termination neither wtm nor watchdog and miner.
This behavior is on two independant rigs.
At the time I am running without Auto Switch
As I'am a Linux virgin - is there a possibility to give you more information for check?

I made a small change so the terminal keeps showing miner output even after switch.

papampi,
many thanks for your support - functionality is great and miner stays in terminal after coin switch.
But is this also possible for the Watchdog terminal - otherwise don't see whether the Watchdog is running or not?
Watchdog is terminated and not rectivating after coin change.

[Stubo]

Hello,

Please could someone explain me or point me to right direction?

Im bit confused about OC settings:

there are multiple OC parts:


1. This one i understand is the MAIN setting for all card/algo/hash

I either enable/disable PowerLimit, but the CORE and MEM stays

Code:

# OC (overclock) and Power Limit settings              #
#                                                      #
########################################################

POWERLIMIT="NO"            # YES or NO # Choose YES to set Global Power Limit for all GPU's

POWERLIMIT_WATTS=75         # Global Power Limit in watts for all GPU's. If enabled, INDIVIDUAL settings will override this. 

__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings

MEMORY_OVERCLOCK=100        # Global Memory overclock for all GPU's if not using INDIVIDUAL settings

2. Set this as NO - dont want to be ALGO (coin) specific

Code:

# Default values set at the end of 1bash are for 1060, remember to set yours accordingly.
ALGO_SPECIFIC_OC="NO"       # YES or NO # See the description above

3. This one i thought its hash (equihash) specific OC setting, but it wont take it - ignores
So what is it for? not sure what relation it has with FANs

Code:

# ENSURE YOU USE MINER_TEMP_CONTROL for fanspeed

equihash_POWERLIMIT_WATTS=115
__equihash_CORE_OVERCLOCK=110
equihash_MEMORY_OVERCLOCK=500

4. Those are per card in case i have different models in the rig

Code:

########################################################
#                                                      #
# INDIVIDUAL Power Limit, Temp and Clock settings      #
#                                                      #
########################################################

# Settings below are for rigs using INDIVIDUAL powerlimit / target temps / clocks only
# If set to YES, the INDIVIDUAL settings will override the GLOBAL settings

INDIVIDUAL_POWERLIMIT="NO"    # YES or NO

# Set individual powerlimits here if INDIVIDUAL_POWERLIMIT="YES"
INDIVIDUAL_POWERLIMIT_0=100
INDIVIDUAL_POWERLIMIT_1=100

5. Not sure why are also HASH specific OC settings and also ALGO/COIN specific - bit confused 

Code:

# ALGO_SPECIFIC_OC settings                            #
#                                                      #
########################################################

# ALGO_SPECIFIC_OC settings
# OC settings you can use based on COIN or ALGO (how ever you want to categorize them)
# Deafault values are for 1060 check http://krypto-mining.blogspot.co.uk/ for other OC values

if [ $ALGO_SPECIFIC_OC == "YES" ]
then

  # Equihash
  if [ $COIN == "BTG" -o $COIN == "ZEC" -o $COIN == "ZEN" -o $COIN == "HUSH" -o $COIN == "ZCL" -o $COIN == "KMD" -o $COIN == "ZPOOL_EQUIHASH" -o $COIN == "MPH_EQUIHASH" -o $COIN == "NICE_EQUIHASH" -o $COIN == "VOTE" ]
  then
    ALGORITHM="EQUIHASH"
    POWERLIMIT_WATTS=130
    __CORE_OVERCLOCK=150
    MEMORY_OVERCLOCK=800
  fi

Your part 3 is for salfter auto switch... Don't know if there is a better way to show it

Code:

########################################################
#                                                      #
# SALFTER_NICEHASH_PROFIT_SWITCHING &                  #
# SALFTER_MPH_PROFIT_SWITCHING Settings                #
#                                                      #
########################################################

CURRENCY=USD

POWER_COST=0.20

MINIMUM_PROFIT=0.0

MPH_USERNAME=replace_with_your_MPH_username

PAYMENT_ADDRESS="$BTC_ADDRESS"

WORKER_NAME="$WORKERNAME"

PROFIT_CHECK_TIMEOUT=600

# ENSURE YOU USE MINER_TEMP_CONTROL for fanspeed

daggerhashimoto_POWERLIMIT_WATTS=120
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100

If you want individual OC its the last part of 1bash your part 5

Ah the no.3 its only setting when im using the SALFTER_MPH_PROFIT_SWITCHING Settings  ?
If i dont use that switcher (this setting WTM_AUTO_SWITCH="NO"  ) it ignores the OC values. Did i get it right?

No.1

Code:

# OC (overclock) and Power Limit settings              #
#                                                      #
########################################################

POWERLIMIT="NO"            # YES or NO # Choose YES to set Global Power Limit for all GPU's

POWERLIMIT_WATTS=75         # Global Power Limit in watts for all GPU's. If enabled, INDIVIDUAL settings will override this. 

__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings

MEMORY_OVERCLOCK=100        # Global Memory overclock for all GPU's if not using INDIVIDUAL settings

Those are OC setting in TOP of other ?

POWERLIMIT="NO" - will be able to take Watts from values bellow ALGO OC (No.5) and Individual (No.4)

POWERLIMIT="YES" -  if i set POWERLIMIT_WATTS=75 other No.4/5 wont go above 75?

How are those 2 managed:
__CORE_OVERCLOCK=100        # Global Core overclock for all GPU's if not using INDIVIDUAL settings
MEMORY_OVERCLOCK=100

- does it overwrite also ALGO OC? (No.5)?

Thanks

Here is the order of precedence for OC:

1) If INDIVIDUAL_CLOCKS=YES, those will override any other OC settings
2) If damNmad_ALGO_SPECIFIC_OC=YES, settings in that section (bottom of 1bash) override __CORE_OVERCLOCK and MEMORY_OVERCLOCK
3) __CORE_OVERCLOCK and MEMORY_OVERCLOCK determine OC settings

Hope this helps.

[crazydane]

Rolled 19-2 out to all my rigs and no issues whatsoever.

I have rigs with 1050Tis, 1060's, 1070's, 1070Ti's and 1080Tis and each rig has between 3 and 9 GPUs, so a decent mix of GPU models and rig configurations.



http://www.cstone.net/~dk/19-2rollout.JPG

In a future version, I'd love to see a "summary" feature of the rig stats and I soon won't be able to fit them in a single browser window on a 4k monitor.