somehow it generate lots of video noise and freezes this rig up.
Is anyone has similar problem and how to fix it?
Topic: [OS] nvOC easy-to-use Linux Nvidia Mining - page 11. (Read 418313 times)
btw trying to mine ETH with my 13x1080
somehow it generate lots of video noise and freezes this rig up.
Is anyone has similar problem and how to fix it?
somehow it generate lots of video noise and freezes this rig up.
Is anyone has similar problem and how to fix it?
I have this error when I want to mine XMR:
Code:
/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution
Are you sure you used the correct name? because the variable is pointed to "xmr-stak_VERSION" but it should be "XMR_Stak_VERSION"
Ok, i tried again with you code and finally, it's Ok.
But i had this code for memory huge page like this :
Quote
## CRYPTONIGHTV7
elif [[ $ALGO == CRYPTONIGHTV7 || $ALGO == CRYPTONIGHTHEAVY ]];
then
# Large memory page support
sudo sysctl -w vm.nr_hugepages=128
# Remove nvidia.txt if cards count changed
if [ -f ~/nvidia.txt ]
then
if [ "$(grep -c "// gpu:" ~/nvidia.txt)" != "$(nvidia-smi -i 0 --query-gpu=count --format=csv,noheader,nounits)" ]
then
rm ~/nvidia.txt
fi
fi
# Change verbosity to show hashrate in output log
if [ -f ~/config.txt ]
then
if grep -q '"verbose_level" : 3' ~/config.txt
then
sed -i 's/"verbose_level" : 3/"verbose_level" : 4/g' ~/config.txt
fi
fi
if [[ $ALGO == "CRYPTONIGHTV7" ]]
then
UCCALGO="--currency monero7"
elif [[ $ALGO == "CRYPTONIGHTHEAVY" ]]
then
UCCALGO="-a cryptonight-heavy"
fi
HCD=${NVOC}/miners/XMR_Stak/"${!xversion}"/xmr-stak
eval $LAUNCH $HCD $UCCALGO --noCPU --noAMD -o "${!xpool}":"${!xport}" -u "${!xaddr}" -p "$MINER_PWD" -i 0
elif [[ $ALGO == CRYPTONIGHTV7 || $ALGO == CRYPTONIGHTHEAVY ]];
then
# Large memory page support
sudo sysctl -w vm.nr_hugepages=128
# Remove nvidia.txt if cards count changed
if [ -f ~/nvidia.txt ]
then
if [ "$(grep -c "// gpu:" ~/nvidia.txt)" != "$(nvidia-smi -i 0 --query-gpu=count --format=csv,noheader,nounits)" ]
then
rm ~/nvidia.txt
fi
fi
# Change verbosity to show hashrate in output log
if [ -f ~/config.txt ]
then
if grep -q '"verbose_level" : 3' ~/config.txt
then
sed -i 's/"verbose_level" : 3/"verbose_level" : 4/g' ~/config.txt
fi
fi
if [[ $ALGO == "CRYPTONIGHTV7" ]]
then
UCCALGO="--currency monero7"
elif [[ $ALGO == "CRYPTONIGHTHEAVY" ]]
then
UCCALGO="-a cryptonight-heavy"
fi
HCD=${NVOC}/miners/XMR_Stak/"${!xversion}"/xmr-stak
eval $LAUNCH $HCD $UCCALGO --noCPU --noAMD -o "${!xpool}":"${!xport}" -u "${!xaddr}" -p "$MINER_PWD" -i 0
Thanks
Added huge page support for xmr-stak to 0miner
Thank you guys for your heavy work and new nvOC 19-2.1 releas!!!
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
Try change the intensity valid values for CryptoDredge are 1 to 6
Thank man it works!
Installed nvOC with Ubuntu 18.04 on 10x1070 rig and 13x1080. 10x1070 works perfect (except screensaver, can't disable it)
But on 13x1080 it freezes rig. I managed to start one time but I've started TPccminer with no OC,
later restart wtih gpu custom OC and later restarted with CryptoDredge. After reboot it has stopped to work and
I rolled back to 16.04 version which works no problem.
18.04 is experimental
nvidia-396 installed on 18.04 is short lived version and may have some problems too.
I recommend 16.04 for production rigs.
I will make a new ubuntu 16.04 image as soon as the new long live nvidia-driver for cuda 9.2 released.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
Beauty of GPU mining is that you can mine whatever algo is currently profitable.
ASIC's story is different - it can mine only one and if you extremely lucky it will reach break even.
From my personal experience, most likely ASIC investment will end up with loss
ASIC's story is different - it can mine only one and if you extremely lucky it will reach break even.
From my personal experience, most likely ASIC investment will end up with loss
I understand but i think all GPU rigs are not profitable since begenning of september 2018 or before. ANd if each algo become ASIC compatible, GPU minning will die soon. For sure.
GPU minnin don't become more profitable because ASIC minng isn't profitable.
ALl GPU rigs with 1080 Ti cards are not profitables anymore. So GPU rigs with GPu under theses 1080, are not too.
Execpt if you don't pay your électricity that become more and more costly because of ecologist renewables that are paid by consummers and tax payers.
Beauty of GPU mining is that you can mine whatever algo is currently profitable.
ASIC's story is different - it can mine only one and if you extremely lucky it will reach break even.
From my personal experience, most likely ASIC investment will end up with loss
ASIC's story is different - it can mine only one and if you extremely lucky it will reach break even.
From my personal experience, most likely ASIC investment will end up with loss
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
Another algorithm will toogle to ASIC minning :-(
https://www.asicminervalue.com/miners/dayun/zig-z1
There is not a month that passes without the minning of a new algo is compatible with ASICS chips.
Here are some more corners that will go into the ASICS section of WTM:
WTM Lyra2Rev2 ASICS minning 24-09-2018
https://imgur.com/a/R0TcDFS
Translated from French with Google translation
https://www.asicminervalue.com/miners/dayun/zig-z1
There is not a month that passes without the minning of a new algo is compatible with ASICS chips.
Here are some more corners that will go into the ASICS section of WTM:
WTM Lyra2Rev2 ASICS minning 24-09-2018
https://imgur.com/a/R0TcDFS
Translated from French with Google translation
Thank you guys for your heavy work and new nvOC 19-2.1 releas!!!
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
Try change the intensity valid values for CryptoDredge are 1 to 6
Thank man it works!
Installed nvOC with Ubuntu 18.04 on 10x1070 rig and 13x1080. 10x1070 works perfect (except screensaver, can't disable it)
But on 13x1080 it freezes rig. I managed to start one time but I've started TPccminer with no OC,
later restart wtih gpu custom OC and later restarted with CryptoDredge. After reboot it has stopped to work and
I rolled back to 16.04 version which works no problem.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
I have this error when I want to mine XMR:
Code:
/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution
Are you sure you used the correct name? because the variable is pointed to "xmr-stak_VERSION" but it should be "XMR_Stak_VERSION"
Ok, i tried again with you code and finally, it's Ok.
But i had this code for memory huge page like this :
Quote
## CRYPTONIGHTV7
elif [[ $ALGO == CRYPTONIGHTV7 || $ALGO == CRYPTONIGHTHEAVY ]];
then
# Large memory page support
sudo sysctl -w vm.nr_hugepages=128
# Remove nvidia.txt if cards count changed
if [ -f ~/nvidia.txt ]
then
if [ "$(grep -c "// gpu:" ~/nvidia.txt)" != "$(nvidia-smi -i 0 --query-gpu=count --format=csv,noheader,nounits)" ]
then
rm ~/nvidia.txt
fi
fi
# Change verbosity to show hashrate in output log
if [ -f ~/config.txt ]
then
if grep -q '"verbose_level" : 3' ~/config.txt
then
sed -i 's/"verbose_level" : 3/"verbose_level" : 4/g' ~/config.txt
fi
fi
if [[ $ALGO == "CRYPTONIGHTV7" ]]
then
UCCALGO="--currency monero7"
elif [[ $ALGO == "CRYPTONIGHTHEAVY" ]]
then
UCCALGO="-a cryptonight-heavy"
fi
HCD=${NVOC}/miners/XMR_Stak/"${!xversion}"/xmr-stak
eval $LAUNCH $HCD $UCCALGO --noCPU --noAMD -o "${!xpool}":"${!xport}" -u "${!xaddr}" -p "$MINER_PWD" -i 0
elif [[ $ALGO == CRYPTONIGHTV7 || $ALGO == CRYPTONIGHTHEAVY ]];
then
# Large memory page support
sudo sysctl -w vm.nr_hugepages=128
# Remove nvidia.txt if cards count changed
if [ -f ~/nvidia.txt ]
then
if [ "$(grep -c "// gpu:" ~/nvidia.txt)" != "$(nvidia-smi -i 0 --query-gpu=count --format=csv,noheader,nounits)" ]
then
rm ~/nvidia.txt
fi
fi
# Change verbosity to show hashrate in output log
if [ -f ~/config.txt ]
then
if grep -q '"verbose_level" : 3' ~/config.txt
then
sed -i 's/"verbose_level" : 3/"verbose_level" : 4/g' ~/config.txt
fi
fi
if [[ $ALGO == "CRYPTONIGHTV7" ]]
then
UCCALGO="--currency monero7"
elif [[ $ALGO == "CRYPTONIGHTHEAVY" ]]
then
UCCALGO="-a cryptonight-heavy"
fi
HCD=${NVOC}/miners/XMR_Stak/"${!xversion}"/xmr-stak
eval $LAUNCH $HCD $UCCALGO --noCPU --noAMD -o "${!xpool}":"${!xport}" -u "${!xaddr}" -p "$MINER_PWD" -i 0
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
I have this error when I want to mine XMR:
Code:
/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution
Are you sure you used the correct name? because the variable is pointed to "xmr-stak_VERSION" but it should be "XMR_Stak_VERSION"
Yes, i corrected this Name With uppercase like you suggested, but i had the same error.
But if i look here :
Code:
########################################################
# Builtin GPU miners settings#
########################################################
CLAYMORE_VERSION="latest"
CLAYMORE_OPTS=" -ejobtimeout 3 -retrydelay 5 -checkcert 0"
ETHMINER_OPTS=""
DSTM_OPTS=""
EWBF_PERCENT="0"
EWBF_OPTS=""
EWBF_VERSION="3_4"
Z_EWBF_PERCENT="0"
Z_EWBF_OPTS=""
Z_EWBF_VERSION="latest"
BMINER_OPTS=""
CCMINER_OPTS=""
ASccminer_VERSION=""
KTccminer_VERSION="recommended"
KTccminer_cryptonight_VERSION="recommended"
TPccminer_VERSION="recommended"
ZENEMYminer_VERSION="recommended"
i don't see any XMR_Stak_VERSION like others minning softwares !
Is it Normal ?
Thank you guys for your heavy work and new nvOC 19-2.1 releas!!!
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
Try change the intensity valid values for CryptoDredge are 1 to 6
I have this error when I want to mine XMR:
Code:
/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution
Are you sure you used the correct name? because the variable is pointed to "xmr-stak_VERSION" but it should be "XMR_Stak_VERSION"
Thank you guys for your heavy work and new nvOC 19-2.1 releas!!!
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
Been trying to mine MONA with cryptodrege but it always under load half of GPU in the rig
have to switch to tpccminer
Can anyone help?
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
I have several problems with xmr-stak 2.4.7 on CUDA 9.2
1- That code only works from within the script, if you run it individually the variable will not be recognized
2- Input for compiling xmr-stak is X (uppercase x) not x
3- I dont have much experience with xmr-stak to help with. You may ask in their from for the parameters and add them to:
Code:
XMR_EXTENSION_ARGUMENTS=""
Or let us know if it needs some adjustments in 0miner.
4- There is already a miner password in 1bash what other passwords you are looking for?
Code:
MINER_PWD="x" # Set the miner password. Default: x
1/ I think your variable
Code:
"${!xversion}"/2/ Ok, i noticed it. But i finally recompiled it me myself by downloading the source from their GITHUB. It was very long to compile the two cuda backend.
3/I think the -r options to define name of the rig will be a good solution in this extension arguments. I will test it. Because without this,i experienced that xmr-stak ask to press enter at startup
4/ supportxmr pool give us possibility to add options in password option. they create and account to modify minimum payout if you put your email address as password.
Because i will mine only xmr, it's not a problem for me, but if someone want to mine with profit switching on supportxmr instead of nanopool it can't modify his password that is often "x" (lowercase)
Another problem with xmr-stak is to define largest memory page before starting minning software with the command :
Code:
sudo sysctl -w vm.nr_hugepages=128
I added it in cryptonight section on 0miner file
and modifying this file : /etc/security/limits.conf like developers explained in the config.txt file.
Quote
* LARGE PAGE SUPPORT
* Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
* but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
* meant as a backup, you won't get stellar results there. If you are running into trouble, especially
* on Windows, please read the common issues in the README.
*
* By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
* You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
*
* 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
* 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
* 3. Expand Security Settings, and then expand Local Policies.
* 4. Select the User Rights Assignment folder.
* 5. The policies will be displayed in the details pane.
* 6. In the pane, double-click Lock pages in memory.
* 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
* 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
* 9. Reboot for change to take effect.
*
* Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
* to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
*
* On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
* ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
* and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
* recommended for security reasons.
*
* Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
* command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
* locked and unlocked memory. If that is your setup see option "no_mlck".
* Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
* but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
* meant as a backup, you won't get stellar results there. If you are running into trouble, especially
* on Windows, please read the common issues in the README.
*
* By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
* You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
*
* 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
* 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
* 3. Expand Security Settings, and then expand Local Policies.
* 4. Select the User Rights Assignment folder.
* 5. The policies will be displayed in the details pane.
* 6. In the pane, double-click Lock pages in memory.
* 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
* 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
* 9. Reboot for change to take effect.
*
* Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
* to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
*
* On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
* ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
* and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
* recommended for security reasons.
*
* Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
* command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
* locked and unlocked memory. If that is your setup see option "no_mlck".
I give here my CC, MC and PL settings with FAN SPEED at 40 RPM
Code:
#####################################################################
# Individual GPU_SPECIFIC Power Limit, Temp and Clock settings #
#####################################################################
# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=65 # GTX 1070
TARGET_TEMP_1=65 # GTX 1060
TARGET_TEMP_2=65 # GTX 1060
TARGET_TEMP_3=65 # GTX 1070
TARGET_TEMP_4=65 # GTX 1060
TARGET_TEMP_5=65 # GTX 1070
TARGET_TEMP_6=65 # GTX 1070
TARGET_TEMP_7=65 # GTX 1060
TARGET_TEMP_8=65 # GTX 1060
TARGET_TEMP_9=65 # GTX 1070
# Set individual powerlimits here if POWERLIMIT_MODE is GPU_SPECIFIC
INDIVIDUAL_POWERLIMIT_0=100
INDIVIDUAL_POWERLIMIT_1=100
INDIVIDUAL_POWERLIMIT_2=100
INDIVIDUAL_POWERLIMIT_3=100
INDIVIDUAL_POWERLIMIT_4=100
INDIVIDUAL_POWERLIMIT_5=100
INDIVIDUAL_POWERLIMIT_6=100
INDIVIDUAL_POWERLIMIT_7=100
INDIVIDUAL_POWERLIMIT_8=100
INDIVIDUAL_POWERLIMIT_9=100
# Set individual clocks here if OVERCLOCK_MODE is GPU_SPECIFIC
__CORE_OVERCLOCK_0=115 # GTX 1070
MEMORY_OVERCLOCK_0=1400 # GTX 1070
__CORE_OVERCLOCK_1=115 # GTX 1060
MEMORY_OVERCLOCK_1=1400 # GTX 1060
__CORE_OVERCLOCK_2=115 # GTX 1060
MEMORY_OVERCLOCK_2=1400 # GTX 1060
__CORE_OVERCLOCK_3=115 # GTX 1070
MEMORY_OVERCLOCK_3=1500 # GTX 1070
__CORE_OVERCLOCK_4=115 # GTX 1060
MEMORY_OVERCLOCK_4=1400 # GTX 1060
__CORE_OVERCLOCK_5=115 # GTX 1070
MEMORY_OVERCLOCK_5=1400 # GTX 1070
__CORE_OVERCLOCK_6=115 # GTX 1070
MEMORY_OVERCLOCK_6=1400 # GTX 1070
__CORE_OVERCLOCK_7=115 # GTX 1060
MEMORY_OVERCLOCK_7=1400 # GTX 1060
__CORE_OVERCLOCK_8=115 # GTX 1060
MEMORY_OVERCLOCK_8=1400 # GTX 1060
__CORE_OVERCLOCK_9=115 # GTX 1070
MEMORY_OVERCLOCK_9=1600 # GTX 1070
The results of these settings are :
Quote
HASHRATE REPORT - NVIDIA
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 725.1 | 724.6 | (na) | 1 | 517.5 | 517.0 | (na) |
| 2 | 518.1 | 518.0 | (na) | 3 | 734.2 | 733.7 | (na) |
| 4 | 516.9 | 516.9 | (na) | 5 | 725.2 | 724.9 | (na) |
| 6 | 723.9 | 723.8 | (na) | 7 | 549.4 | 549.4 | (na) |
| 8 | 549.2 | 549.1 | (na) | 9 | 741.3 | 741.3 | (na) |
Totals (NVIDIA): 6300.8 6298.7 0.0 H/s
-----------------------------------------------------------------
Totals (ALL): 6300.8 6298.7 0.0 H/s
Highest: 6308.8 H/s
-----------------------------------------
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 725.1 | 724.6 | (na) | 1 | 517.5 | 517.0 | (na) |
| 2 | 518.1 | 518.0 | (na) | 3 | 734.2 | 733.7 | (na) |
| 4 | 516.9 | 516.9 | (na) | 5 | 725.2 | 724.9 | (na) |
| 6 | 723.9 | 723.8 | (na) | 7 | 549.4 | 549.4 | (na) |
| 8 | 549.2 | 549.1 | (na) | 9 | 741.3 | 741.3 | (na) |
Totals (NVIDIA): 6300.8 6298.7 0.0 H/s
-----------------------------------------------------------------
Totals (ALL): 6300.8 6298.7 0.0 H/s
Highest: 6308.8 H/s
-----------------------------------------
EDIT, IT seems after several hours that theses settings looks making my rig unstable. So i returned my olds settings what i used before for mining ETH and others algos :
Quote
# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=65 # GTX 1070
TARGET_TEMP_1=65 # GTX 1060
TARGET_TEMP_2=65 # GTX 1060
TARGET_TEMP_3=65 # GTX 1070
TARGET_TEMP_4=65 # GTX 1060
TARGET_TEMP_5=65 # GTX 1070
TARGET_TEMP_6=65 # GTX 1070
TARGET_TEMP_7=65 # GTX 1060
TARGET_TEMP_8=65 # GTX 1060
TARGET_TEMP_9=65 # GTX 1070
TARGET_TEMP_10=75
TARGET_TEMP_11=75
TARGET_TEMP_12=75
TARGET_TEMP_13=75
TARGET_TEMP_14=75
TARGET_TEMP_15=75
TARGET_TEMP_16=75
TARGET_TEMP_17=75
TARGET_TEMP_18=75
# Set individual powerlimits here if POWERLIMIT_MODE is GPU_SPECIFIC
INDIVIDUAL_POWERLIMIT_0=105
INDIVIDUAL_POWERLIMIT_1=105
INDIVIDUAL_POWERLIMIT_2=105
INDIVIDUAL_POWERLIMIT_3=105
INDIVIDUAL_POWERLIMIT_4=100
INDIVIDUAL_POWERLIMIT_5=100
INDIVIDUAL_POWERLIMIT_6=100
INDIVIDUAL_POWERLIMIT_7=110
INDIVIDUAL_POWERLIMIT_8=110
INDIVIDUAL_POWERLIMIT_9=115
INDIVIDUAL_POWERLIMIT_10=100
INDIVIDUAL_POWERLIMIT_11=100
INDIVIDUAL_POWERLIMIT_12=100
INDIVIDUAL_POWERLIMIT_13=100
INDIVIDUAL_POWERLIMIT_14=100
INDIVIDUAL_POWERLIMIT_15=100
INDIVIDUAL_POWERLIMIT_16=100
INDIVIDUAL_POWERLIMIT_17=100
INDIVIDUAL_POWERLIMIT_18=100
# Set individual clocks here if OVERCLOCK_MODE is GPU_SPECIFIC
__CORE_OVERCLOCK_0=100 # GTX 1070
MEMORY_OVERCLOCK_0=1125 # GTX 1070
__CORE_OVERCLOCK_1=100 # GTX 1060
MEMORY_OVERCLOCK_1=1050 # GTX 1060
__CORE_OVERCLOCK_2=100 # GTX 1060
MEMORY_OVERCLOCK_2=1050 # GTX 1060
__CORE_OVERCLOCK_3=100 # GTX 1070
MEMORY_OVERCLOCK_3=1050 # GTX 1070
__CORE_OVERCLOCK_4=100 # GTX 1060
MEMORY_OVERCLOCK_4=1000 # GTX 1060
__CORE_OVERCLOCK_5=100 # GTX 1070
MEMORY_OVERCLOCK_5=1050 # GTX 1070
__CORE_OVERCLOCK_6=100 # GTX 1070
MEMORY_OVERCLOCK_6=1050 # GTX 1070
__CORE_OVERCLOCK_7=100 # GTX 1060
MEMORY_OVERCLOCK_7=1300 # GTX 1060
__CORE_OVERCLOCK_8=100 # GTX 1060
MEMORY_OVERCLOCK_8=1300 # GTX 1060
__CORE_OVERCLOCK_9=100 # GTX 1070
MEMORY_OVERCLOCK_9=1500 # GTX 1070
TARGET_TEMP_0=65 # GTX 1070
TARGET_TEMP_1=65 # GTX 1060
TARGET_TEMP_2=65 # GTX 1060
TARGET_TEMP_3=65 # GTX 1070
TARGET_TEMP_4=65 # GTX 1060
TARGET_TEMP_5=65 # GTX 1070
TARGET_TEMP_6=65 # GTX 1070
TARGET_TEMP_7=65 # GTX 1060
TARGET_TEMP_8=65 # GTX 1060
TARGET_TEMP_9=65 # GTX 1070
TARGET_TEMP_10=75
TARGET_TEMP_11=75
TARGET_TEMP_12=75
TARGET_TEMP_13=75
TARGET_TEMP_14=75
TARGET_TEMP_15=75
TARGET_TEMP_16=75
TARGET_TEMP_17=75
TARGET_TEMP_18=75
# Set individual powerlimits here if POWERLIMIT_MODE is GPU_SPECIFIC
INDIVIDUAL_POWERLIMIT_0=105
INDIVIDUAL_POWERLIMIT_1=105
INDIVIDUAL_POWERLIMIT_2=105
INDIVIDUAL_POWERLIMIT_3=105
INDIVIDUAL_POWERLIMIT_4=100
INDIVIDUAL_POWERLIMIT_5=100
INDIVIDUAL_POWERLIMIT_6=100
INDIVIDUAL_POWERLIMIT_7=110
INDIVIDUAL_POWERLIMIT_8=110
INDIVIDUAL_POWERLIMIT_9=115
INDIVIDUAL_POWERLIMIT_10=100
INDIVIDUAL_POWERLIMIT_11=100
INDIVIDUAL_POWERLIMIT_12=100
INDIVIDUAL_POWERLIMIT_13=100
INDIVIDUAL_POWERLIMIT_14=100
INDIVIDUAL_POWERLIMIT_15=100
INDIVIDUAL_POWERLIMIT_16=100
INDIVIDUAL_POWERLIMIT_17=100
INDIVIDUAL_POWERLIMIT_18=100
# Set individual clocks here if OVERCLOCK_MODE is GPU_SPECIFIC
__CORE_OVERCLOCK_0=100 # GTX 1070
MEMORY_OVERCLOCK_0=1125 # GTX 1070
__CORE_OVERCLOCK_1=100 # GTX 1060
MEMORY_OVERCLOCK_1=1050 # GTX 1060
__CORE_OVERCLOCK_2=100 # GTX 1060
MEMORY_OVERCLOCK_2=1050 # GTX 1060
__CORE_OVERCLOCK_3=100 # GTX 1070
MEMORY_OVERCLOCK_3=1050 # GTX 1070
__CORE_OVERCLOCK_4=100 # GTX 1060
MEMORY_OVERCLOCK_4=1000 # GTX 1060
__CORE_OVERCLOCK_5=100 # GTX 1070
MEMORY_OVERCLOCK_5=1050 # GTX 1070
__CORE_OVERCLOCK_6=100 # GTX 1070
MEMORY_OVERCLOCK_6=1050 # GTX 1070
__CORE_OVERCLOCK_7=100 # GTX 1060
MEMORY_OVERCLOCK_7=1300 # GTX 1060
__CORE_OVERCLOCK_8=100 # GTX 1060
MEMORY_OVERCLOCK_8=1300 # GTX 1060
__CORE_OVERCLOCK_9=100 # GTX 1070
MEMORY_OVERCLOCK_9=1500 # GTX 1070
That give me less hashrate displayed on miner but more hash because more shares on pool :
Quote
HASHRATE REPORT - NVIDIA
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 702.6 | 703.9 | 703.6 | 1 | 496.8 | 496.7 | 496.8 |
| 2 | 497.5 | 497.4 | 497.3 | 3 | 698.5 | 698.9 | 698.7 |
| 4 | 494.5 | 494.4 | 494.4 | 5 | 697.8 | 697.1 | 697.4 |
| 6 | 697.3 | 697.5 | 697.1 | 7 | 543.4 | 543.3 | 543.3 |
| 8 | 543.2 | 542.9 | 543.1 | 9 | 735.8 | 735.9 | 735.9 |
Totals (NVIDIA): 6107.4 6107.9 6107.7 H/s
-----------------------------------------------------------------
Totals (ALL): 6107.4 6107.9 6107.7 H/s
Highest: 6155.3 H/s
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 702.6 | 703.9 | 703.6 | 1 | 496.8 | 496.7 | 496.8 |
| 2 | 497.5 | 497.4 | 497.3 | 3 | 698.5 | 698.9 | 698.7 |
| 4 | 494.5 | 494.4 | 494.4 | 5 | 697.8 | 697.1 | 697.4 |
| 6 | 697.3 | 697.5 | 697.1 | 7 | 543.4 | 543.3 | 543.3 |
| 8 | 543.2 | 542.9 | 543.1 | 9 | 735.8 | 735.9 | 735.9 |
Totals (NVIDIA): 6107.4 6107.9 6107.7 H/s
-----------------------------------------------------------------
Totals (ALL): 6107.4 6107.9 6107.7 H/s
Highest: 6155.3 H/s
Miner displayed before : 6,3 KHs but pool displayed average hashrate was 4.5 - 5KHs
Now : Miner display 6.1 KHs but pools display average 6 kHs minimum with top at 9KHs !
I have several problems with xmr-stak 2.4.7 on CUDA 9.2
1- That code only works from within the script, if you run it individually the variable will not be recognized
2- Input for compiling xmr-stak is X (uppercase x) not x
3- I dont have much experience with xmr-stak to help with. You may ask in their from for the parameters and add them to:
Code:
XMR_EXTENSION_ARGUMENTS=""
Or let us know if it needs some adjustments in 0miner.
4- There is already a miner password in 1bash what other passwords you are looking for?
Code:
MINER_PWD="x" # Set the miner password. Default: x
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
Ok, for this point 5. Choosed current profit instead of current revenue. If the script launch the most profitable coin every 12 min but show them in disarray, i'm agree whith that. I just want to be sure that this display will not affect the choice of more profitable coin to mine at this check. I do not yet verified me myself
What about my problem with xmr-stak ?
/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution
If you set both sorts with current rev or profit and current difficulty, it should sort them correctly, if not post the output and your url to check.
I think xmr-stak name changed to XMR_Stak in latest 1bash, check the "Available builtin miners" for miner names
I have several problems with xmr-stak 2.4.7 on CUDA 9.2
1/ There is a problem with this commande line :
Code:
HCD=${NVOC}/miners/XMR_Stak/"${!xversion}"/xmr-stakCode:
HCD="/home/m1/NVOC/mining/miners/XMR_Stak/2.4.7/xmr-stak"
And after this modification i saw the command line displayed on the terminal 3main window that laucnh all the scripts
I think the problem that i reported before is because the variable
Code:
"${!xversion}"2/ I tried to launch miner in the xmr-stak directory but this software impératively needs to be recompiled like this usual error message can make him think :
Code:
~/NVOC/mining/miners/XMR_Stak/2.4.7$ ./xmr-stak
Illegal instruction
So i tried to use miners update script like this
Quote
~/NVOC/mining/miners$ ./nvOC_miner_update.sh
Updating miners for nvOC V0019-2.1
Will check and restart miner if needed
Checking EWBF version 3.4
EWBF already is on version 3.4
Checking Z_EWBF version 0.5
Z_EWBF already is on version 0.5
Checking DSTM version 0.6.1
DSTM already is on version 0.6.1
Checking ETHMINER (cuda
version 0.14.0
ETHMINER already is on version 0.14.0
Checking ETHMINER (cuda 9.2) version 0.15.0
ETHMINER already is on version 0.15.0
Checking CLAYMORE version 11.9
CLAYMORE already is on version 11.9
Checking BMINER version 10.2.0
BMINER already is on version 10.2.0
Checking XMR_Stak (cuda version 2.4.4
XMR_Stak already is on version 2.4.4
Checking XMR_Stak (cuda 9.2) version 2.4.7
XMR_Stak already is on version 2.4.7
Checking cpuOPT version 3.8.8.1
cpuOPT already is on version 3.8.8.1
Checking ASccminer (cuda version 1.0
ASccminer already is on version 1.0
Checking ANXccminer (cuda version 1.0
ANXccminer already is on version 1.0
Checking CryptoDredge version 0.8.3
CryptoDredge already is on version 0.8.3
Checking KTccminer (cuda version 8.20
KTccminer already is on version 8.20
Checking KTccminer (cuda 9.2) version 8.22
KTccminer already is on version 8.22
Checking KTccminer_cryptonight (cuda version 2.06
KTccminer_cryptonight already is on version 2.06
Checking KTccminer_cryptonight (cuda 9.2) version 3.05
KTccminer_cryptonight already is on version 3.05
Checking KXccminer (cuda version 0.1
KXccminer already is on version 0.1
Checking MSFTccminer (cuda version 2.2.5
MSFTccminer already is on version 2.2.5
Checking NAccminer (cuda version 2.2
NAccminer already is on version 2.2
Checking SILENTminer (cuda version 1.10
SILENTminer already is on version 1.10
Checking SPccminer (cuda version 1.8.2
SPccminer already is on version 1.8.2
Checking SUPRminer (cuda version 1.5
SUPRminer already is on version 1.5
Checking TPccminer (cuda version 2.2.5
TPccminer already is on version 2.2.5
Checking TPccminer (cuda 9.2) version 2.3
TPccminer already is on version 2.3
Checking VERTMINER (cuda version 1.0.2
VERTMINER already is on version 1.0.2
Checking ZENEMYminer (cuda version 1.10
ZENEMYminer already is on version 1.10
Checking ZENEMYminer (cuda 9.2) version 1.19
ZENEMYminer already is on version 1.19
Extracting and checking miners finished
Do you want to re-compile your miners (y/N)? y
Checking if bn.h bignum error is fixed for compiling miners or not
ERROR: cannot verify www.openssl.org's certificate, issued by ‘CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US’:
Unable to locally verify the issuer's authority.
To connect to www.openssl.org insecurely, use `--no-check-certificate'.
tar (child): openssl-1.0.1e.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
cp: cannot create regular file '/home/m1/Downloads/openssl-1.0.1e/bn.h.backup': No such file or directory
cp: cannot stat '/home/m1/Downloads/openssl-1.0.1e/crypto/bn/bn.h': No such file or directory
bn.h openssl fixed for compiling miners
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libgcrypt20:i386 libsystemd0:i386 libuuid1:i386
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
cmake-data libcurl4 librhash0 libuv1
Suggested packages:
cmake-doc ninja-build
The following packages will be REMOVED:
libcurl3
The following NEW packages will be installed:
cmake cmake-data libcurl4 librhash0 libuv1
0 upgraded, 5 newly installed, 1 to remove and 0 not upgraded.
Need to get 4,826 kB of archives.
After this operation, 24.4 MB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 cmake-data all 3.10.2-1ubuntu2 [1,331 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libcurl4 amd64 7.58.0-2ubuntu3 [214 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 librhash0 amd64 1.3.6-2 [78.1 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libuv1 amd64 1.18.0-3 [64.4 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 cmake amd64 3.10.2-1ubuntu2 [3,138 kB]
Fetched 4,826 kB in 23s (210 kB/s)
(Reading database ... 196754 files and directories currently installed.)
Removing libcurl3:amd64 (7.58.0-2ubuntu2) ...
Selecting previously unselected package cmake-data.
(Reading database ... 196748 files and directories currently installed.)
Preparing to unpack .../cmake-data_3.10.2-1ubuntu2_all.deb ...
Unpacking cmake-data (3.10.2-1ubuntu2) ...
Selecting previously unselected package libcurl4:amd64.
Preparing to unpack .../libcurl4_7.58.0-2ubuntu3_amd64.deb ...
Unpacking libcurl4:amd64 (7.58.0-2ubuntu3) ...
Selecting previously unselected package librhash0:amd64.
Preparing to unpack .../librhash0_1.3.6-2_amd64.deb ...
Unpacking librhash0:amd64 (1.3.6-2) ...
Selecting previously unselected package libuv1:amd64.
Preparing to unpack .../libuv1_1.18.0-3_amd64.deb ...
Unpacking libuv1:amd64 (1.18.0-3) ...
Selecting previously unselected package cmake.
Preparing to unpack .../cmake_3.10.2-1ubuntu2_amd64.deb ...
Unpacking cmake (3.10.2-1ubuntu2) ...
Setting up libuv1:amd64 (1.18.0-3) ...
Setting up libcurl4:amd64 (7.58.0-2ubuntu3) ...
Setting up cmake-data (3.10.2-1ubuntu2) ...
Setting up librhash0:amd64 (1.3.6-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up cmake (3.10.2-1ubuntu2) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Updating miners for nvOC V0019-2.1
Will check and restart miner if needed
Checking EWBF version 3.4
EWBF already is on version 3.4
Checking Z_EWBF version 0.5
Z_EWBF already is on version 0.5
Checking DSTM version 0.6.1
DSTM already is on version 0.6.1
Checking ETHMINER (cuda
version 0.14.0ETHMINER already is on version 0.14.0
Checking ETHMINER (cuda 9.2) version 0.15.0
ETHMINER already is on version 0.15.0
Checking CLAYMORE version 11.9
CLAYMORE already is on version 11.9
Checking BMINER version 10.2.0
BMINER already is on version 10.2.0
Checking XMR_Stak (cuda
version 2.4.4XMR_Stak already is on version 2.4.4
Checking XMR_Stak (cuda 9.2) version 2.4.7
XMR_Stak already is on version 2.4.7
Checking cpuOPT version 3.8.8.1
cpuOPT already is on version 3.8.8.1
Checking ASccminer (cuda
version 1.0ASccminer already is on version 1.0
Checking ANXccminer (cuda
version 1.0ANXccminer already is on version 1.0
Checking CryptoDredge version 0.8.3
CryptoDredge already is on version 0.8.3
Checking KTccminer (cuda
version 8.20KTccminer already is on version 8.20
Checking KTccminer (cuda 9.2) version 8.22
KTccminer already is on version 8.22
Checking KTccminer_cryptonight (cuda
version 2.06KTccminer_cryptonight already is on version 2.06
Checking KTccminer_cryptonight (cuda 9.2) version 3.05
KTccminer_cryptonight already is on version 3.05
Checking KXccminer (cuda
version 0.1KXccminer already is on version 0.1
Checking MSFTccminer (cuda
version 2.2.5MSFTccminer already is on version 2.2.5
Checking NAccminer (cuda
version 2.2NAccminer already is on version 2.2
Checking SILENTminer (cuda
version 1.10SILENTminer already is on version 1.10
Checking SPccminer (cuda
version 1.8.2SPccminer already is on version 1.8.2
Checking SUPRminer (cuda
version 1.5SUPRminer already is on version 1.5
Checking TPccminer (cuda
version 2.2.5TPccminer already is on version 2.2.5
Checking TPccminer (cuda 9.2) version 2.3
TPccminer already is on version 2.3
Checking VERTMINER (cuda
version 1.0.2VERTMINER already is on version 1.0.2
Checking ZENEMYminer (cuda
version 1.10ZENEMYminer already is on version 1.10
Checking ZENEMYminer (cuda 9.2) version 1.19
ZENEMYminer already is on version 1.19
Extracting and checking miners finished
Do you want to re-compile your miners (y/N)? y
Checking if bn.h bignum error is fixed for compiling miners or not
ERROR: cannot verify www.openssl.org's certificate, issued by ‘CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US’:
Unable to locally verify the issuer's authority.
To connect to www.openssl.org insecurely, use `--no-check-certificate'.
tar (child): openssl-1.0.1e.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
cp: cannot create regular file '/home/m1/Downloads/openssl-1.0.1e/bn.h.backup': No such file or directory
cp: cannot stat '/home/m1/Downloads/openssl-1.0.1e/crypto/bn/bn.h': No such file or directory
bn.h openssl fixed for compiling miners
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libgcrypt20:i386 libsystemd0:i386 libuuid1:i386
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
cmake-data libcurl4 librhash0 libuv1
Suggested packages:
cmake-doc ninja-build
The following packages will be REMOVED:
libcurl3
The following NEW packages will be installed:
cmake cmake-data libcurl4 librhash0 libuv1
0 upgraded, 5 newly installed, 1 to remove and 0 not upgraded.
Need to get 4,826 kB of archives.
After this operation, 24.4 MB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 cmake-data all 3.10.2-1ubuntu2 [1,331 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libcurl4 amd64 7.58.0-2ubuntu3 [214 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 librhash0 amd64 1.3.6-2 [78.1 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libuv1 amd64 1.18.0-3 [64.4 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 cmake amd64 3.10.2-1ubuntu2 [3,138 kB]
Fetched 4,826 kB in 23s (210 kB/s)
(Reading database ... 196754 files and directories currently installed.)
Removing libcurl3:amd64 (7.58.0-2ubuntu2) ...
Selecting previously unselected package cmake-data.
(Reading database ... 196748 files and directories currently installed.)
Preparing to unpack .../cmake-data_3.10.2-1ubuntu2_all.deb ...
Unpacking cmake-data (3.10.2-1ubuntu2) ...
Selecting previously unselected package libcurl4:amd64.
Preparing to unpack .../libcurl4_7.58.0-2ubuntu3_amd64.deb ...
Unpacking libcurl4:amd64 (7.58.0-2ubuntu3) ...
Selecting previously unselected package librhash0:amd64.
Preparing to unpack .../librhash0_1.3.6-2_amd64.deb ...
Unpacking librhash0:amd64 (1.3.6-2) ...
Selecting previously unselected package libuv1:amd64.
Preparing to unpack .../libuv1_1.18.0-3_amd64.deb ...
Unpacking libuv1:amd64 (1.18.0-3) ...
Selecting previously unselected package cmake.
Preparing to unpack .../cmake_3.10.2-1ubuntu2_amd64.deb ...
Unpacking cmake (3.10.2-1ubuntu2) ...
Setting up libuv1:amd64 (1.18.0-3) ...
Setting up libcurl4:amd64 (7.58.0-2ubuntu3) ...
Setting up cmake-data (3.10.2-1ubuntu2) ...
Setting up librhash0:amd64 (1.3.6-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up cmake (3.10.2-1ubuntu2) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Code:
The following packages will be REMOVED:
libgcrypt20:i386 libsystemd0:i386 libuuid1:i386
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 1,828 kB disk space will be freed.
(Reading database ... 199137 files and directories currently installed.)
Removing libsystemd0:i386 (237-3ubuntu10.3) ...
Removing libgcrypt20:i386 (1.8.1-4ubuntu1.1) ...
Removing libuuid1:i386 (2.31.1-0.4ubuntu3.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Select miners to compile (multiple comma separated values: 1,6,7)
1 - ASccminer
2 - KTccminer
3 - KTccminer_cryptonight
4 - KXccminer
5 - NAccminer
6 - SPccminer
7 - TPccminer
8 - VERTMINER
9 - ANXccminer
C - cpuminer
R - MSFTccminer (RVN)
U - SUPRminer
X - xmr-stak
Do your Choice: [A]LL [1] [2] [3] [4] [5] [6] [7] [8] [9] [C] [R] [U] [X] [E]xit: x
x[/quote]
Code:
Alas for me, the xmr-stak update and build script does not seem to work because it can not find the tarball package path :-(
[quote]find: ‘/home/m1/NVOC/mining/miners/x’: No such file or directory
Are you kidding me???
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
cmake-data librhash0 libuv1
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
cmake libcurl4
The following NEW packages will be installed:
libcurl3
0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 214 kB of archives.
After this operation, 17.3 MB disk space will be freed.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcurl3 amd64 7.58.0-2ubuntu2 [214 kB]
Fetched 214 kB in 32s (6,770 B/s)
(Reading database ... 199131 files and directories currently installed.)
Removing cmake (3.10.2-1ubuntu2) ...
Removing libcurl4:amd64 (7.58.0-2ubuntu3) ...
Selecting previously unselected package libcurl3:amd64.
(Reading database ... 199113 files and directories currently installed.)
Preparing to unpack .../libcurl3_7.58.0-2ubuntu2_amd64.deb ...
Unpacking libcurl3:amd64 (7.58.0-2ubuntu2) ...
Setting up libcurl3:amd64 (7.58.0-2ubuntu2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
cmake-data librhash0 libuv1
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 7,097 kB disk space will be freed.
(Reading database ... 199119 files and directories currently installed.)
Removing cmake-data (3.10.2-1ubuntu2) ...
Removing librhash0:amd64 (1.3.6-2) ...
Removing libuv1:amd64 (1.18.0-3) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
I know how to decompress a file "tar.gz", but I'm a little less practicing files "tar.xz" also I do not know how to recompile xmr-stak and update the script of update of the software of mining written by papampi
In addition, I know it's probably a bit more complicated than previous versions of NVOC since there are now two versions of CUDA installed on the system.
Please Help !
3/ Problem with XMR pool choice
You all know as well as me that as minor as it is better to have several pools of handning the most balanced possible, but now NVOC, if I use XMR-STAK (which I think that is the best for this algorithm) , I can't mine on another pool than nanopool pool.
This concentrates mining hasrate on nanopool and limits the possibilities for miners. Can you modify this in the 0miner others scripts ?
The default pool is nanopool and I would like to try to mine on supportxmr.com (http://Https://www.supportxmr.com/#/help/getting_started) but the parameters are not arranged in the same way on supportxmr.com pool...
I think I'm not the only one who wants to mine on this other pool which is still the second largest after nanopool (100 to 115 MH/s on average compared to 160 to 190 MH/s on nanopool)
Also, The payout is lower at 0.3 XMR, and i thonk it's a better minimum payout in view of the increase in the difficulty of mining monero.
Otherwise, miner is monopolized for at least 1 month and may even be more only for monero minning.
Translated from French with Google translation
Would it be possible to revise this part of the script to put a Password variable (-p) in the 1bash file?
Translated from French with Google translation
Note : i have some time this weekedn, so i can make some tests with your propositions. PM me if its necessary.
Note 5: I observed that WTM_Switching no longer sorts the values retrieved from the WTM website in decreasing order. In addition, the displayed values do not indicate profitability but income since the values are positive whereas they should be negative as on the WTM website.
WTM switch preserve the sorting as returned by wtm's api. If you want wtm to top profit coin you need to set "sort by current profit" in whattomine when generating the url. If you select different sorting criteria (e.g. 24h/7d profitability) those criteria will apply. Displayed values are revenues, not profits, because wtm api do not return profit in json output.
Note 5: I observed that WTM_Switching no longer sorts the values retrieved from the WTM website in decreasing order. In addition, the displayed values do not indicate profitability but income since the values are positive whereas they should be negative as on the WTM website.
Check your WTM URL
That usually happens when you sort not by current revenue and difficulty
Ok, for this point 5. Choosed current profit instead of current revenue. If the script launch the most profitable coin every 12 min but show them in disarray, i'm agree whith that. I just want to be sure that this display will not affect the choice of more profitable coin to mine at this check. I do not yet verified me myself
What about my problem with xmr-stak ?
/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution
If you set both sorts with current rev or profit and current difficulty, it should sort them correctly, if not post the output and your url to check.
I think xmr-stak name changed to XMR_Stak in latest 1bash, check the "Available builtin miners" for miner names
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
Note 5: I observed that WTM_Switching no longer sorts the values retrieved from the WTM website in decreasing order. In addition, the displayed values do not indicate profitability but income since the values are positive whereas they should be negative as on the WTM website.
Check your WTM URL
That usually happens when you sort not by current revenue and difficulty
Ok, for this point 5. Choosed current profit instead of current revenue. If the script launch the most profitable coin every 12 min but show them in disarray, i'm agree whith that. I just want to be sure that this display will not affect the choice of more profitable coin to mine at this check. I do not yet verified me myself
What about my problem with xmr-stak ?
/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution
Usually lost GPU is caused by hardware problems or high OC.
As soon as it gives that error, kill all running screens so it wont reboot:
As soon as it gives that error, kill all running screens so it wont reboot:
Code:
pkill -ef screenrc
then run nvidia-smi and post the output This is what happend:
Code:
==> /home/m1/NVOC/testing/nvoc_logs/screenlog.0 <==
m 09:08:54|ethminer| Speed 181.23 Mh/s gpu/0 22.98 gpu/1 22.46 gpu/2 22.98 gpu/3 22.37 gpu/4 21.50 gpu/5 22.98 gpu/6 22.89 gpu/7 23.07 [A3+0:R0+0:F0] Time: 00:02
m 09:08:59|ethminer| Speed 181.14 Mh/s gpu/0 22.98 gpu/1 22.46 gpu/2 22.98 gpu/3 22.28 gpu/4 21.41 gpu/5 22.98 gpu/6 22.89 gpu/7 23.16 [A3+0:R0+0:F0] Time: 00:02
ℹ 09:09:00|stratum | New job #bbbcf560… daggerhashimoto.eu.nicehash.com [172.65.195.169:3353]
==> /home/m1/NVOC/testing/nvoc_logs/tempcontrol-screenlog.0 <==
WARNING: Mon Sep 17 09:09:07 MST 2018 - Problem detected! GPU0 is not responding. Will give watchdog 60 seconds to react, if not we will reboot!
==> /home/m1/NVOC/testing/nvoc_logs/screenlog.0 <==
m 09:09:04|ethminer| Speed 180.37 Mh/s gpu/0 22.88 gpu/1 22.40 gpu/2 22.98 gpu/3 22.21 gpu/4 21.26 gpu/5 22.88 gpu/6 22.78 gpu/7 22.98 [A3+0:R0+0:F0] Time: 00:02
m 09:09:09|ethminer| Speed 177.32 Mh/s gpu/0 22.88 gpu/1 22.40 gpu/2 22.88 gpu/3 22.12 gpu/4 21.26 gpu/5 22.98 gpu/6 19.83 gpu/7 22.98 [A3+0:R0+0:F0] Time: 00:02
==> /home/m1/NVOC/testing/nvoc_logs/watchdog-screenlog.0 <==
Load Average: 1.04, 1.25, 0.60
Mon Sep 17 09:09:03 MST 2018 - [INFO] - GPU0 Utilization: 100%
Mon Sep 17 09:09:04 MST 2018 - [INFO] - GPU1 Utilization: 100%
Mon Sep 17 09:09:05 MST 2018 - [INFO] - GPU2 Utilization: 100%
Mon Sep 17 09:09:05 MST 2018 - [INFO] - GPU3 Utilization: 100%
Mon Sep 17 09:09:06 MST 2018 - [INFO] - GPU4 Utilization: 100%
Mon Sep 17 09:09:06 MST 2018 - [INFO] - GPU5 Utilization: 100%
Mon Sep 17 09:09:07 MST 2018 - [INFO] - GPU6 Utilization: Unable%
Mon Sep 17 09:09:07 MST 2018 - [CRITICAL] - Lost GPU6 so restarting system. Found GPU's:
Unable to determine the device handle for GPU 0000:08:00.0: GPU is lost. Reboot the system to recover this GPU
m 09:08:54|ethminer| Speed 181.23 Mh/s gpu/0 22.98 gpu/1 22.46 gpu/2 22.98 gpu/3 22.37 gpu/4 21.50 gpu/5 22.98 gpu/6 22.89 gpu/7 23.07 [A3+0:R0+0:F0] Time: 00:02
m 09:08:59|ethminer| Speed 181.14 Mh/s gpu/0 22.98 gpu/1 22.46 gpu/2 22.98 gpu/3 22.28 gpu/4 21.41 gpu/5 22.98 gpu/6 22.89 gpu/7 23.16 [A3+0:R0+0:F0] Time: 00:02
ℹ 09:09:00|stratum | New job #bbbcf560… daggerhashimoto.eu.nicehash.com [172.65.195.169:3353]
==> /home/m1/NVOC/testing/nvoc_logs/tempcontrol-screenlog.0 <==
WARNING: Mon Sep 17 09:09:07 MST 2018 - Problem detected! GPU0 is not responding. Will give watchdog 60 seconds to react, if not we will reboot!
==> /home/m1/NVOC/testing/nvoc_logs/screenlog.0 <==
m 09:09:04|ethminer| Speed 180.37 Mh/s gpu/0 22.88 gpu/1 22.40 gpu/2 22.98 gpu/3 22.21 gpu/4 21.26 gpu/5 22.88 gpu/6 22.78 gpu/7 22.98 [A3+0:R0+0:F0] Time: 00:02
m 09:09:09|ethminer| Speed 177.32 Mh/s gpu/0 22.88 gpu/1 22.40 gpu/2 22.88 gpu/3 22.12 gpu/4 21.26 gpu/5 22.98 gpu/6 19.83 gpu/7 22.98 [A3+0:R0+0:F0] Time: 00:02
==> /home/m1/NVOC/testing/nvoc_logs/watchdog-screenlog.0 <==
Load Average: 1.04, 1.25, 0.60
Mon Sep 17 09:09:03 MST 2018 - [INFO] - GPU0 Utilization: 100%
Mon Sep 17 09:09:04 MST 2018 - [INFO] - GPU1 Utilization: 100%
Mon Sep 17 09:09:05 MST 2018 - [INFO] - GPU2 Utilization: 100%
Mon Sep 17 09:09:05 MST 2018 - [INFO] - GPU3 Utilization: 100%
Mon Sep 17 09:09:06 MST 2018 - [INFO] - GPU4 Utilization: 100%
Mon Sep 17 09:09:06 MST 2018 - [INFO] - GPU5 Utilization: 100%
Mon Sep 17 09:09:07 MST 2018 - [INFO] - GPU6 Utilization: Unable%
Mon Sep 17 09:09:07 MST 2018 - [CRITICAL] - Lost GPU6 so restarting system. Found GPU's:
Unable to determine the device handle for GPU 0000:08:00.0: GPU is lost. Reboot the system to recover this GPU
reboot so quick I couldnt look at nvidia-smi. But I tried a xorg restore and now it is running for 30mins now... knocksonwood*
Note 5: I observed that WTM_Switching no longer sorts the values retrieved from the WTM website in decreasing order. In addition, the displayed values do not indicate profitability but income since the values are positive whereas they should be negative as on the WTM website.
Check your WTM URL
That usually happens when you sort not by current revenue and difficulty
Jump to: