CryptAtomeTrader44
Full Member
 Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
 |
December 17, 2017, 06:31:24 PM |
|
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.phpbut 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 MINER_PWD = "x" # Set the miner password. Default: x in the 0miner file, which produces this lines: Line 394 screen -dmSL miner $HCD -a neoscrypt -o stratum+tcp://$TZC_POOL:$TZC_PORT -u $ADDR -p c=TZC -i $TZC_INTENSITY Line 401 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: #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" #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#msg26264470The 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
"If you don't want people to know you're a scumbag then don't be a scumbag." -- margaritahuyan
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Stubo
Member
Offline
Activity: 224
Merit: 13
|
|
December 17, 2017, 06:38:03 PM |
|
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
|
|
December 17, 2017, 06:46:28 PM |
|
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. TEAMVIEWER="YES" # YES NO |
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
December 17, 2017, 06:55:52 PM |
|
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. TEAMVIEWER="YES" # YES NO alexis ccminer is already available in nvoc If you are on 19-2.0 its the default miner for lyra2rev2, if not you should edit 3main |
|
|
|
wi$em@n
Newbie
Offline
Activity: 46
Merit: 0
|
|
December 17, 2017, 06:56:47 PM |
|
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
Member
Offline
Activity: 224
Merit: 13
|
|
December 17, 2017, 07:22:51 PM |
|
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: nvidia-smi --query-gpu=power.draw --format=csv
|
|
|
|
|
killeriq
Newbie
Offline
Activity: 22
Merit: 0
|
|
December 17, 2017, 08:36:29 PM |
|
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 # 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 # 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 # 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 ########################################################
# #
# 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  # 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
########################################################
# #
# 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 # 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
Newbie
Offline
Activity: 15
Merit: 0
|
|
December 17, 2017, 08:54:53 PM |
|
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: 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
Member
Offline
Activity: 224
Merit: 13
|
|
December 17, 2017, 09:17:17 PM |
|
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 # 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 # 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 # 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 ########################################################
# #
# 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 # 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
########################################################
# #
# 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 # 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
|
|
December 18, 2017, 01:15:50 AM
Last edit: December 18, 2017, 04:13:21 AM by 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.JPGIn 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. |
|
|
|
|
|
martyroz
|
|
December 18, 2017, 02:10:08 AM |
|
Rolled 19-2 out to all my rigs and no issues whatsoever.
Is there a standalone download for 19_2.0? or are you typing some command to update? Right now I have two rigs on 19_1.4 mining Equihash, so not in a great hurry to upgrade. |
|
|
|
|
|
crazydane
|
|
December 18, 2017, 02:24:06 AM |
|
I used the upgrade script and had modified versions of 1bash ready to push to reach miner after the update script completed.
I believe papampi is working on a 19_2.0 image.
|
|
|
|
|
wi$em@n
Newbie
Offline
Activity: 46
Merit: 0
|
|
December 18, 2017, 02:44:11 AM |
|
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: nvidia-smi --query-gpu=power.draw --format=csv
It returns the same: m1@m1-desktop:~$ GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds |
|
|
|
|
|
|
wi$em@n
Newbie
Offline
Activity: 46
Merit: 0
|
|
December 18, 2017, 04:09:24 AM |
|
OK, that's the answer! The bad thing is that it does not only fails to read, but what is more important to set power limit. On older driver it did both correctly, I checked that with wattmeter. |
|
|
|
|
Tigel
Newbie
Offline
Activity: 66
Merit: 0
|
|
December 18, 2017, 05:39:13 AM |
|
|
|
|
|
|
|
joshuajones02
|
|
December 18, 2017, 05:44:50 AM |
|
what can I type in the terminal to modify GPU settings while miner is running for each GPU individually? i.e Power limit, oc core, & fan speed
|
|
|
|
Tigel
Newbie
Offline
Activity: 66
Merit: 0
|
|
December 18, 2017, 05:59:26 AM |
|
what can I type in the terminal to modify GPU settings while miner is running for each GPU individually? i.e Power limit, oc core, & fan speed
For GPU1: nvidia-smi -i 1 -pl 75 export DISPLAY=:0 nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=200 nvidia-settings -a [gpu:1]/GPUMemoryTransferRateOffset[3]=1000 nvidia-settings -a [gpu:1]/GPUFanControlState=1 nvidia-settings -a [fan:1]/GPUTargetFanSpeed=8 -- Tigel |
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
December 18, 2017, 06:46:16 AM |
|
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: 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. It is running in the background In a guake tab run |
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
December 18, 2017, 06:50:51 AM
Last edit: December 18, 2017, 08:34:20 AM by papampi |
|
Rolled 19-2 out to all my rigs and no issues whatsoever.
Is there a standalone download for 19_2.0? or are you typing some command to update? Right now I have two rigs on 19_1.4 mining Equihash, so not in a great hurry to upgrade. For now update scriptRun: Image install will be ready soon |
|
|
|
|
