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

[sizzlephizzle]

Dear all who work on this. Thank you so much for everything. The 19-1.4 version was great, but the 2.0 is much better for me so I'm sticking with community builds going forward.

Would love to help, but I'm not the greatest scriptkiddie.

Couple of suggestions for 19-2.1:

1: Can we add GPU support for GPU19 (b250 mining board). I can manually add this myself with simple copy and paste etc, but it would be good to just have that rolled out to all.

2: I see in the community page on nvoc-mining that states, under the updatelog: There are community builds that have numerous bug fixes and 1 community build has an auto overclocker.
Is this just expressing the ability to overclock with the config files or has someone scripted nvidia-smi -q | grep -A 5 "Max Clocks" | grep "Memory" to compile the max settings for each card and then automatically overclock your cards? (I'm using a multi-model rig with different nvidias for benchmarking. 1060 3gb/6gb/1070 etc. Hoping to obtain more soon.) I started working on this, but ultimately I keep getting the failed mir error and lost my attempt when updating to 19-2.

3: Rather than dual mining, can we integrate two separate miners? I scripted the following to allow hynix memory to mine ZEC as they only suffer when mining ETHash.

Code:

#!/bin/bash

#Ask for GPUs to use
echo "Enter the GPU numbers separated by spaces (e.g. 0 1 2 3)"
read gpus

ZEC_WORKER="19.4_0"
# replace_with_your_ZEC_address
ZEC_ADDRESS="t1Uzd2zmuJyxYGPfpLs1wZaGqjE33TM72c3"
ZEC_POOL="zec-us-east1.nanopool.org"
ZEC_PORT="6666"

ZECADDR="$ZEC_ADDRESS.$ZEC_WORKER"

#if [ $ZM_or_EWBF == "ZM" ]
HCD='/home/m1/zec/zm/5_2/zm_miner'
screen -dmSL MultiMiner $HCD --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT --dev $gpus

echo ""
echo "Starting Ande's MultiMiner on GPU's $gpus"

It's all stolen from the 3main file (now 0miner). I start mining ETH and any card performing under the benchmark of the others gets disabled (number key in claymore), then I run ./multi and enter "3 5 6" and this starts mining just those cards.

That may be specific to my setup and not included, that's no problem, just thinking it might help others.

Something like 1bash addition:

Code:

BI-MINING="YES" #YES or NO

#DECLARE COIN
BI_GPU0="ETH"
BI_GPU1="ETH"
BI_GPU2="ETH"
BI_GPU3="ZEC"
BI_GPU4="ETH"
BI_GPU5="ZEC"
BI_GPU6="ZEC"
BI_GPU7="ETH"
BI_GPU8="ETH"

3main addition:

Code:

if [ BI-MINING == "YES" ]
 for i in $BI_GPU $i
      if [ echo $BI_GPU$i == ZEC ]
       screen -S miner -X exec $i ##This command doesn't work, it's a failed attempt to enter screen and press the GPU that is needed for equihash.
$i+1 loop until maxed
fi

-------

Not sure what will be of use and what wont, but thanks again, even if these are useless to the community, I'm really glad I found nvOC. Excellent work guys.

#New2Mining
#New2Forum
#NoSignature
#Hashtag

[1714566963]

1714566963

[1714566963]

1714566963

[sizzlephizzle]

Oh - one final improvement for the upgrade process:

Can we have a separate wallet file? If our ***_ADDRESS= was in a separate file, then when we upgrade, there would be no need to migrate stuff from 1bash.
Integrity check would be needed though eg:

Code:

If /home/m1/wallets.user does not exist, echo (dev wallets for all coins) > /home/m1/wallets.user, else echo 'newadditions' >> /home/m1/wallets.user fi

.
This way we can update nvOC in the future and all our wallets will not need copy and pasting from the old one. Just saves a little downtime and produces a more professional/effortless/autonomous upgrade.

Siz

[tomlev5]

Hello guys.

Today i tried to log into the rig (both rigs) through SSH with m1 / miner1.
I got error "Access denied", but I didn't change the password.

Does somebody know what could be the problem?
Is there some other standard password for nvOC?

EDIT: Now I have successfully logged in. I don't know what was wrong before, but it wasn't a typo (I tried many times on both rigs with the same keyboard as now)

[sizzlephizzle]

I got error "Access denied", but I didn't change the password.

if it's still miner1, you should really change it. (passwd m1)
Also, use command history
This'll show you if anything has been done during the "access denied" period.

[bumbu100]

Asus B250 MINING EXPERT - 13-18 ASUS P104-100 GPU !!!
Does anyone solved that? Anything looks fine, until start terminal. When i use 13+ cards, not working.
I am using the new ASUS p104-100 GPU's. NOT mixed.

[sizzlephizzle]

Asus B250 MINING EXPERT - 13-18 ASUS P104-100 GPU !!!
Does anyone solved that? Anything looks fine, until start terminal. When i use 13+ cards, not working.
I am using the new ASUS p104-100 GPU's. NOT mixed.

Is the board showing all 18 detected green?
Have you done the Asus board update in EZ Setup Flash Utility?

[bumbu100]

Asus B250 MINING EXPERT - 13-18 ASUS P104-100 GPU !!!
Does anyone solved that? Anything looks fine, until start terminal. When i use 13+ cards, not working.
I am using the new ASUS p104-100 GPU's. NOT mixed.

Is the board showing all 18 detected green?
Have you done the Asus board update in EZ Setup Flash Utility?

Absolutely, all is green.
Last BIOS.

[tomlev5]

I got error "Access denied", but I didn't change the password.

if it's still miner1, you should really change it. (passwd m1)
Also, use command history
This'll show you if anything has been done during the "access denied" period.

I checked command history (with command: history) and everything looked fine (no command for password change).
The miner is hidden behind a firewall so i am OK with this default password ...

[sizzlephizzle]

Miners Update Script:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/nvOC_miner_update.sh
bash /home/m1/Downloads/nvOC_miner_update.sh

For reference - I did this and my miner is no longer detecting nvidia cards.
cudaGetDeviceCount returned error 3 (Google advises drivers out of date)
"no nvidia devices detected" when starting claymore miner.

sudo apt-get update
sudo apt list --upgradeable showed me the nvidia packages needed updating
sudo apt-get upgrade

nvidia installs, reboots, same problem.

re-ran the nvoc19-2 script, rebooted, still hung.

Output of ./2unix :

Code:

All done.
Power limit for GPU 00000000:0F:00.0 was set to 76.00 W from 75.00 W.
All done.
Power limit for GPU 00000000:10:00.0 was set to 76.00 W from 75.00 W.
All done.
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found

LAUNCHING:  MINER TEMPCONTROL

process in screen temp; ~/nvOC temp-log

Looking through the re-compile instructions, claymore isn't there.
Appears to be a case of reinstall and rebuild?

DamNmad told me about nvOC report:

Code:

 
Software info: 
Report ver    :  v0019-2.0.002 
nvOC (1bash)  :  nvOC v0019-2.0 - Community Release 
nvOC (3main)  :  nvOC v0019-2.0 - Community Release   
1bash ver     :  v0019-2.0.003 
3main ver     :  v0019-2.0.006                   
5watchdog ver :  v0019-2.0.011    
6tempcontrol v:  v0019-2.0.003    
wtm switch ver:  v0019-2.0.0011   
Kernel        :  4.4.0-97-generic 
OS            :  Ubuntu 16.04.3 LTS 
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 
nvidia driver :  387.34 
 
Hardware info: 
Motherboard   :  ASUS B250 MINING EXPERT  Rev X.0x 
BIOS ver.     :  1001 12/13/2017 
CPU Model     :  Pentium(R) CPU G4400 @ 3.30GHz 
CPU Cores     :  2 (Cores + Threads) 
Mem Total     :         4002352 kB 
Mem Free      :          635636 kB 
Swap Total    :               0 kB 
Swap Free     :               0 kB 
Ethernet      :  Intel I219-V

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR  MODEL       REV MOUNTPOINT
sda    28.7G        disk    1       1 usb  SanDisk Ultra      1.00 
├─sda1    9M vfat   part    1       1                              /media/m1/12D
└─sda2 13.7G ext4   part    1       1                              /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b84 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
10:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)

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

Temp Control ..............: YES
TARGET_TEMP ...............: 65
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 90
MINIMAL_FAN_SPEED .........: 48

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

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

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

GLOBAL_WORKERNAME .........: YES
AUTO_WORKERNAME ...........: HOST
WORKERNAME ................: 034
plusCPU ...................: NO

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

COIN ......................: ETH
ETH_WORKER ................: 034
ETH_ADDRESS ...............: 0x1ae7b3...
ETH_POOL ..................: eu1.ethermine.org
ETH_PORT ..................: 4444

Siz

[leenoox]

Hello, I have a question, is it possible to set a Temp limit like in Afterburner? The problem is that the card has a minimum of 100w = 50% en AB set in a permanent bios, to go down below I have to set AB Temp limit 60 degrees c then the card works at 35% pl = 78watt in windows.

I am not sure how afterburner is lowering the power limit below the limit set in vbios, maybe nvidia driver for windows allows this. To my knowledge the nvidia linux driver will not allow setting power limit below what is set in the GPU's vbios.
You could flash vbios from different vendor that might have lower setting for PL but that's kinda risky... not recommended.

[leenoox]

Hello!

I was update Nvidia drivers, and get this line now:

Code:

[error] OpenCL error: Failed to list OpenCL platforms! (Unknown OpenCL error -1001)

How to recovery driver? or what i need to do?

Have you resolved this?

[papampi]

Miners Update Script:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/nvOC_miner_update.sh
bash /home/m1/Downloads/nvOC_miner_update.sh

For reference - I did this and my miner is no longer detecting nvidia cards.
cudaGetDeviceCount returned error 3 (Google advises drivers out of date)
"no nvidia devices detected" when starting claymore miner.

sudo apt-get update
sudo apt list --upgradeable showed me the nvidia packages needed updating
sudo apt-get upgrade

nvidia installs, reboots, same problem.

re-ran the nvoc19-2 script, rebooted, still hung.

Output of ./2unix :

Code:

All done.
Power limit for GPU 00000000:0F:00.0 was set to 76.00 W from 75.00 W.
All done.
Power limit for GPU 00000000:10:00.0 was set to 76.00 W from 75.00 W.
All done.
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found

LAUNCHING:  MINER TEMPCONTROL

process in screen temp; ~/nvOC temp-log

Looking through the re-compile instructions, claymore isn't there.
Appears to be a case of reinstall and rebuild?

DamNmad told me about nvOC report:

Code:

 
Software info: 
Report ver    :  v0019-2.0.002 
nvOC (1bash)  :  nvOC v0019-2.0 - Community Release 
nvOC (3main)  :  nvOC v0019-2.0 - Community Release   
1bash ver     :  v0019-2.0.003 
3main ver     :  v0019-2.0.006                   
5watchdog ver :  v0019-2.0.011    
6tempcontrol v:  v0019-2.0.003    
wtm switch ver:  v0019-2.0.0011   
Kernel        :  4.4.0-97-generic 
OS            :  Ubuntu 16.04.3 LTS 
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 
nvidia driver :  387.34 
 
Hardware info: 
Motherboard   :  ASUS B250 MINING EXPERT  Rev X.0x 
BIOS ver.     :  1001 12/13/2017 
CPU Model     :  Pentium(R) CPU G4400 @ 3.30GHz 
CPU Cores     :  2 (Cores + Threads) 
Mem Total     :         4002352 kB 
Mem Free      :          635636 kB 
Swap Total    :               0 kB 
Swap Free     :               0 kB 
Ethernet      :  Intel I219-V

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR  MODEL       REV MOUNTPOINT
sda    28.7G        disk    1       1 usb  SanDisk Ultra      1.00 
├─sda1    9M vfat   part    1       1                              /media/m1/12D
└─sda2 13.7G ext4   part    1       1                              /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b84 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
10:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)

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

Temp Control ..............: YES
TARGET_TEMP ...............: 65
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 90
MINIMAL_FAN_SPEED .........: 48

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

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

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

GLOBAL_WORKERNAME .........: YES
AUTO_WORKERNAME ...........: HOST
WORKERNAME ................: 034
plusCPU ...................: NO

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

COIN ......................: ETH
ETH_WORKER ................: 034
ETH_ADDRESS ...............: 0x1ae7b3...
ETH_POOL ..................: eu1.ethermine.org
ETH_PORT ..................: 4444

Siz

Claymore is closed source and no binaries available so we cant compile it, ask in claymore thread see if there is a problem in latest version,
Download older versions and put in ~/eth/claymore/latest

[sizzlephizzle]

Claymore is closed source and no binaries available so we cant compile it, ask in claymore thread see if there is a problem in latest version,
Download older versions and put in ~/eth/claymore/latest

Cheers Papampi. It's actually working now, just trying to see if there's a bug with that script. Will update when I know more.

[sizzlephizzle]

Scrap all of that.
5/6 reboots later and it's working as it should.
Sheesh! haha.

[leenoox]

Dear all who work on this. Thank you so much for everything. The 19-1.4 version was great, but the 2.0 is much better for me so I'm sticking with community builds going forward.

Would love to help, but I'm not the greatest scriptkiddie.

Couple of suggestions for 19-2.1:

1: Can we add GPU support for GPU19 (b250 mining board). I can manually add this myself with simple copy and paste etc, but it would be good to just have that rolled out to all.

2: I see in the community page on nvoc-mining that states, under the updatelog: There are community builds that have numerous bug fixes and 1 community build has an auto overclocker.
Is this just expressing the ability to overclock with the config files or has someone scripted nvidia-smi -q | grep -A 5 "Max Clocks" | grep "Memory" to compile the max settings for each card and then automatically overclock your cards? (I'm using a multi-model rig with different nvidias for benchmarking. 1060 3gb/6gb/1070 etc. Hoping to obtain more soon.) I started working on this, but ultimately I keep getting the failed mir error and lost my attempt when updating to 19-2.

3: Rather than dual mining, can we integrate two separate miners? I scripted the following to allow hynix memory to mine ZEC as they only suffer when mining ETHash.

Code:

#!/bin/bash

#Ask for GPUs to use
echo "Enter the GPU numbers separated by spaces (e.g. 0 1 2 3)"
read gpus

ZEC_WORKER="19.4_0"
# replace_with_your_ZEC_address
ZEC_ADDRESS="t1Uzd2zmuJyxYGPfpLs1wZaGqjE33TM72c3"
ZEC_POOL="zec-us-east1.nanopool.org"
ZEC_PORT="6666"

ZECADDR="$ZEC_ADDRESS.$ZEC_WORKER"

#if [ $ZM_or_EWBF == "ZM" ]
HCD='/home/m1/zec/zm/5_2/zm_miner'
screen -dmSL MultiMiner $HCD --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT --dev $gpus

echo ""
echo "Starting Ande's MultiMiner on GPU's $gpus"

It's all stolen from the 3main file (now 0miner). I start mining ETH and any card performing under the benchmark of the others gets disabled (number key in claymore), then I run ./multi and enter "3 5 6" and this starts mining just those cards.

That may be specific to my setup and not included, that's no problem, just thinking it might help others.

Something like 1bash addition:

Code:

BI-MINING="YES" #YES or NO

#DECLARE COIN
BI_GPU0="ETH"
BI_GPU1="ETH"
BI_GPU2="ETH"
BI_GPU3="ZEC"
BI_GPU4="ETH"
BI_GPU5="ZEC"
BI_GPU6="ZEC"
BI_GPU7="ETH"
BI_GPU8="ETH"

3main addition:

Code:

if [ BI-MINING == "YES" ]
 for i in $BI_GPU $i
      if [ echo $BI_GPU$i == ZEC ]
       screen -S miner -X exec $i ##This command doesn't work, it's a failed attempt to enter screen and press the GPU that is needed for equihash.
$i+1 loop until maxed
fi

-------

Not sure what will be of use and what wont, but thanks again, even if these are useless to the community, I'm really glad I found nvOC. Excellent work guys.

#New2Mining
#New2Forum
#NoSignature
#Hashtag

LOL, you've got the term "scriptkiddie" mixed... it refers to hacker-wannabes, the "hackers" that use scripts/programs made by real hackers but have no clue on how and why those scripts work
It has nothing to do with developers that code the scripts

Anyway,
#1. The support for 19 GPU's is already implemented. Numbering starts at GPU0, ends at GPU18, That's a total of 19 GPU's. However, this board had problems with more than 13 GPU's. To get 19 working you need 13 regular + 6 GP106. Asus was promising to fix this with a bios update but to my knowledge it hasn't been fixed yet.

#2. The Comunity Release does not have auto overclock feature. There is another fork that is experimenting with auto overclock but my understanding is that it is hit and miss. It works for some people, it doesn't for other. IMO, the implementation is not mature, not stable and not recommended unless you are willing to risk the lifespan of your GPU's and/Or willing to risk downtime due to freezing.

#3. The multi-miner feature is planned and under development. It probably won't be ready for 19-2.1, hopefully will be implemented in the next release after 2.1.
It requires a complete overhaul of nvoc's operation to make sure it works for all (most) miners while properly overclocking the assigned GPU's to the proper algo chosen. I don't want to rush this feature and release a buggy code... let's make it right.

Thanks for choosing nvoc and for your support and feedback.

[leenoox]

Oh - one final improvement for the upgrade process:

Can we have a separate wallet file? If our ***_ADDRESS= was in a separate file, then when we upgrade, there would be no need to migrate stuff from 1bash.
Integrity check would be needed though eg:

Code:

If /home/m1/wallets.user does not exist, echo (dev wallets for all coins) > /home/m1/wallets.user, else echo 'newadditions' >> /home/m1/wallets.user fi

.
This way we can update nvOC in the future and all our wallets will not need copy and pasting from the old one. Just saves a little downtime and produces a more professional/effortless/autonomous upgrade.

Siz

It's not only addresses that need to be edited in 1bash, there are lots of other settings that need to be edited when reimage or upgraded. While it will definitely save time re-entering addresses it will add extra file that needs to be initially edited.
A while ago this was discussed but decided to stick with one file.

For now everything stays in one config file, although we might revisit this decision again, especially if/when we add algo specific individual GPU settings which will make 1bash huge and painfull to edit.

[leenoox]

Miners Update Script:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/nvOC_miner_update.sh
bash /home/m1/Downloads/nvOC_miner_update.sh

For reference - I did this and my miner is no longer detecting nvidia cards.
cudaGetDeviceCount returned error 3 (Google advises drivers out of date)
"no nvidia devices detected" when starting claymore miner.

sudo apt-get update
sudo apt list --upgradeable showed me the nvidia packages needed updating
sudo apt-get upgrade

nvidia installs, reboots, same problem.

re-ran the nvoc19-2 script, rebooted, still hung.

Output of ./2unix :

Code:

All done.
Power limit for GPU 00000000:0F:00.0 was set to 76.00 W from 75.00 W.
All done.
Power limit for GPU 00000000:10:00.0 was set to 76.00 W from 75.00 W.
All done.
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found

LAUNCHING:  MINER TEMPCONTROL

process in screen temp; ~/nvOC temp-log

Looking through the re-compile instructions, claymore isn't there.
Appears to be a case of reinstall and rebuild?

DamNmad told me about nvOC report:

Code:

 
Software info: 
Report ver    :  v0019-2.0.002 
nvOC (1bash)  :  nvOC v0019-2.0 - Community Release 
nvOC (3main)  :  nvOC v0019-2.0 - Community Release   
1bash ver     :  v0019-2.0.003 
3main ver     :  v0019-2.0.006                   
5watchdog ver :  v0019-2.0.011    
6tempcontrol v:  v0019-2.0.003    
wtm switch ver:  v0019-2.0.0011   
Kernel        :  4.4.0-97-generic 
OS            :  Ubuntu 16.04.3 LTS 
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 
nvidia driver :  387.34 
 
Hardware info: 
Motherboard   :  ASUS B250 MINING EXPERT  Rev X.0x 
BIOS ver.     :  1001 12/13/2017 
CPU Model     :  Pentium(R) CPU G4400 @ 3.30GHz 
CPU Cores     :  2 (Cores + Threads) 
Mem Total     :         4002352 kB 
Mem Free      :          635636 kB 
Swap Total    :               0 kB 
Swap Free     :               0 kB 
Ethernet      :  Intel I219-V

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR  MODEL       REV MOUNTPOINT
sda    28.7G        disk    1       1 usb  SanDisk Ultra      1.00 
├─sda1    9M vfat   part    1       1                              /media/m1/12D
└─sda2 13.7G ext4   part    1       1                              /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b84 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
10:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)

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

Temp Control ..............: YES
TARGET_TEMP ...............: 65
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 90
MINIMAL_FAN_SPEED .........: 48

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

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

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

GLOBAL_WORKERNAME .........: YES
AUTO_WORKERNAME ...........: HOST
WORKERNAME ................: 034
plusCPU ...................: NO

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

COIN ......................: ETH
ETH_WORKER ................: 034
ETH_ADDRESS ...............: 0x1ae7b3...
ETH_POOL ..................: eu1.ethermine.org
ETH_PORT ..................: 4444

Siz

Try setting the P106_100_FULL_HEADLESS_MODE to YES

[sizzlephizzle]

Oh - one final improvement for the upgrade process:

Can we have a separate wallet file? If our ***_ADDRESS= was in a separate file, then when we upgrade, there would be no need to migrate stuff from 1bash.
Integrity check would be needed though eg:

Code:

If /home/m1/wallets.user does not exist, echo (dev wallets for all coins) > /home/m1/wallets.user, else echo 'newadditions' >> /home/m1/wallets.user fi

.
This way we can update nvOC in the future and all our wallets will not need copy and pasting from the old one. Just saves a little downtime and produces a more professional/effortless/autonomous upgrade.

Siz

It's not only addresses that need to be edited in 1bash, there are lots of other settings that need to be edited when reimage or upgraded. While it will definitely save time re-entering addresses it will add extra file that needs to be initially edited.
A while ago this was discussed but decided to stick with one file.

For now everything stays in one config file, although we might revisit this decision again, especially if/when we add algo specific individual GPU settings which will make 1bash huge and painfull to edit.

Thanks for the replies Leenoox. Good answers to all of them, appreciate it.

Regarding the miners-update: It managed to fix itself after the 6th reboot. It was sprouting two of each screen which is where the problem was caused. One miner was red full of errors. The other miner was happily mining.

All the best and thanks again.

[damNmad]

Hello guys,

I'm actually using the newest version of NVOC 19.2 (the one that the grateful @Papampi have in his signature) and I want to add LuxCoin. Can you help me with that guys?

In fact, I would like to know how to add any coin. I scrolled the post and I can't find anything about that.

Thanks for the compliment

Have a look at these 2 posts :

1bash and 0miner v0019-2.1 pre-release changes for Bminer and new coins


nvOC v0019-2.0 Community Release - Miner Update Script

Hello guys, thanks again,

Actually, I pasted the code : cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/1bash_19-2.1_pre_release.sh
bash /home/m1/Downloads/1bash_19-2.1_pre_release.sh

In my Gwake terminal

Then after that, I pasted that code at the same place :

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/0miner
cp /home/m1/Downloads/0miner /home/m1/0miner

I tryed to mine the LUX coin and then I check after from my office with TeamViewer. And now my rig is offline. Do I made something wrong ?


Thanks again, I'm a bit noob with this. Plus, I'm loosing kinda a lot of money (for my perspective) because that rig support 12 gpu 1070 ti


Thanks again Papampi and DamNmad

That's a new 1bash file (settings file). You have to edit it, choose coin, add address, OC settings, etc. Once you edit and save, restart your rig and make sure it starts mining before leaving.

I was just checking LUX coin in 0miner that damNmad sent me, dont know how LUX pool works, but should the miner password set to worker ?

Code:

if [ $COIN == "LUX" ]
then
  HCD='/home/m1/ANXccminer/ccminer'
  ADDR="$LUX_ADDRESS"
  screen -dmSL miner $HCD -a phi -o stratum+tcp://$LUX_POOL:$LUX_PORT -u $ADDR -p $LUX_WORKER -i $LUX_INTENSITY
fi

If not change it to :

Code:

if [ $COIN == "LUX" ]
then
  HCD='/home/m1/ANXccminer/ccminer'
  ADDR="$LUX_ADDRESS.$LUX_WORKER"
  screen -dmSL miner $HCD -a phi -o stratum+tcp://$LUX_POOL:$LUX_PORT -u $ADDR -p $MINER_PWD -i $LUX_INTENSITY
fi

Please let me know, if it needs to be changed.
Thanks.

Sorry guys, it was my mistake, I was testing it with different settings forgot to change it prior to the push.

yiimp expects to see c=LUX in the password for successful LUX mining.

I've edited that in my 0miner and changed it on my previous post too.

I have a different plan of handling this c=COIN_NAME, doing some tests will share it once I have a working one.

Thanks.

[CryptAtomeTrader44]

##############################################
#                                                                                                      #
#   There is any way to change XMR CPU miner with VRM CPU miner?    #
#                                                                                                      #
##############################################

no way?

Give us more information. Du you have some links for linux version ? Source code to compile ? Did you tried to compile yourself ?

What are the minings commands for example ?

Propose something to modify scripts files like 0miner and/or 1bash by trying to copy another command from another miner.

your request in the state we can not answer it if you do not bring us a little information and that we are obliged to seek it in your place whereas it is you who asks this software that nobody here does not seem know.

Is this miner more efficient than XMR Stack CPU ?

In addition, XMR difficulty has become very difficult to sustain in recent weeks. Until the outbreak of BTC (and also ALTcoins) in December, the difficulty allowed really profitable mining with CPU or few GPU, but since this peak of BTC, it is really hard and continue to clim highly and rapidly.

One more effort, you registered, and put a question on this thread, you can also push the scmilblick  and we will look at your asks.

Yes, is a few times better than XMR, especially if you have CPU with AES instructions set. I've got $70/month with one  ESXI VM machine with 70% 2x8Core Xeon CPU.

VeriumMiner Linux Binaries: https://github.com/fireworm71/veriumMiner/releases/download/v1.4/cpuminer_1.4_linux_x64_O2_GCC7.zip
Sources: https://github.com/fireworm71/veriumMiner
syntax: ./cpuminer -o stratum+tcp://eu.vrm.mining-pool.ovh:3032 -u Weblogin.WorkerName -p WorkerPassword

Well that's enough to easily add the minor and modify the mining of Monero with this minor.

Just a question about your Monero miner: You say you are using a virtualization server equipped with 2 Xeon 8 Hearts. But it is known that servers of this type also have large amounts of memories. So your mining software may be better at using RAM.
Cryptonight is also known to be a heavy consumer algorithm of RAM.
How many RAM have your maachine ?

I think you will have papampi or Leenoox replies with this information, otherwise, I could make you a simplified modification proposal that would not necessarily be the best by filling in one by the other. But I think it's better to keep the two miners in the same way as EWBF and ZM Miner.This requires a little more modifications and "complexity" in the commands to launch and test.

EDIT : did you know if this miner is able to mine with GPU ? Beacause XMR STAK GPU is flawlessy efficient.