[OS] nvOC easy-to-use Linux Nvidia Mining - page 9.

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: zloyneo on October 24, 2018, 08:52:25 AM

I updated the nvidia drivers to 410.66. And now I have a problem. How to update Cuda ?

ERROR Driver not support CUDA 5.5 API!!

I think its easier to use one of the latest images from nvOC GitHub ReadMe
Have no idea about cuda 5.5

Stubo

member

Activity: 224

Merit: 13

Hey Pap and All:

It has been a long time and it would appear that lots of work has been done.

What is the best way to get started from nothing and get up to the latest version? My rigs are all on 19.2.0 and I just want to start over and hopefully get the latest Ubuntu and Cuda toolkit. I want to play around with mining RVN and the latest Z-enemy miner seems to require at least Cuda 9 and I am stuck at Cuda 8 with my older versions.

Thanks in advance.

zloyneo

newbie

Activity: 40

Merit: 0

I updated the nvidia drivers to 410.66. And now I have a problem. How to update Cuda ?

ERROR Driver not support CUDA 5.5 API!!

zloyneo

newbie

Activity: 40

Merit: 0

Quote from: papampi_2 on October 24, 2018, 04:40:33 AM

Quote from: zloyneo on October 23, 2018, 05:20:39 PM

Good day. Please help me to upgrade to version 3.0. Or tell me how to configure mining x16г ? My version of the current 19-2.0

If you want to use same image and dont want to flash/write new SSD, create NVOC folder, clone release branch, make a copy of 1bash.template, save it as 1bash and edit it.

Code:

mkdir ~/NVOC
git clone --depth 1 --branch release https://github.com/papampi/nvOC_by_fullzero_Community_Release.git /home/m1/NVOC/mining
cp ~/NVOC/mining/1bash.template ~/NVOC/mining/1bash
cd ~/NVOC/mining
git submodule update --init --depth 1 --remote miners

Use gedit or nano to edit your new 1bash

Code:

gedit ~/NVOC/mining/1bash
nano ~/NVOC/mining/1bash

Run nvOC upgrade to make the changes for the latest miners

Code:

bash ~/NVOC/mining/nvOC upgrade

Check nvOC beta testing "Step 2" for how to create new gnome-terminal mining profile or just edit the current mining profile and change the command
from:

Code:

/home/m1/2unix

to:

Code:

/home/m1/NVOC/mining/2unix

You can also check nvOC GitHub README.md

Many thanks. really help. it worked. You are super!

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: zloyneo on October 23, 2018, 05:20:39 PM

Good day. Please help me to upgrade to version 3.0. Or tell me how to configure mining x16г ? My version of the current 19-2.0

If you want to use same image and dont want to flash/write new SSD, create NVOC folder, clone release branch, make a copy of 1bash.template, save it as 1bash and edit it.

Code:

mkdir ~/NVOC
git clone --depth 1 --branch release https://github.com/papampi/nvOC_by_fullzero_Community_Release.git /home/m1/NVOC/mining
cp ~/NVOC/mining/1bash.template ~/NVOC/mining/1bash
cd ~/NVOC/mining
git submodule update --init --depth 1 --remote miners

Use gedit or nano to edit your new 1bash

Code:

gedit ~/NVOC/mining/1bash
nano ~/NVOC/mining/1bash

Run nvOC upgrade to make the changes for the latest miners

Code:

bash ~/NVOC/mining/nvOC upgrade

Check nvOC beta testing "Step 2" for how to create new gnome-terminal mining profile or just edit the current mining profile and change the command
from:

Code:

/home/m1/2unix

to:

Code:

/home/m1/NVOC/mining/2unix

You can also check nvOC GitHub README.md

zloyneo

newbie

Activity: 40

Merit: 0

Good day. Please help me to upgrade to version 3.0. Or tell me how to configure mining x16г ? My version of the current 19-2.0

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: fk2 on October 23, 2018, 10:52:56 AM

saw that there was no NICE_X16R in X16R Algo list so added that

fixed

Quote

the 3.0 script generates double :: port

fixed

Quote

it fails because of stratum auth. I can see a . in front of my USER which is not in 1bash

the x16r miner command line -u parameter is built as follows:

NICE_ADDRESS + X16R_WALLET_FORMAT + NICE_X16R_WORKERNAME

I guess the . appears because of X16R_WALLET_FORMAT defaults to the global WALLET_FORMAT which is . by default

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: CryptAtomeTrader44 on October 22, 2018, 06:14:24 PM

You have to use precedent ISO and use git to push 3.0 new stable branch on your system in another folder near from mining folder from 19.2.1.

This is not mandatory, you can just use nvOC upgrade^* on your existing 2.1 install, and versions number will get bumped to 3.0. Re-running firstboot scripts, either manually or by doing a reimage will have the very same effect. Any image released so far for nvoc 2.1+ by default install whatever is in the current release branch. If you have already downloaded in the past one of this images and it installed 2.1 that same image will now install 3.0 if you do a reimage.

3.0 is the finalization of the 2.1 dev cycle. While 2.1 was getting major updates during development, now, as 3.0, this will only get bugfixes, miners and maintenance patches. That's why I would not suggest you to keep both 2.1 and 3.0 side-by-side. Instead you may want to keep both 3.0-stable and 3.1-dev. This last one will get new features when ready.

* if you do nvOC upgrade from 2.1 to 3.0, the miners submodule is currently left behind at 2.1: a fix for this is ready, you won't need to do anything to unlock this situation, just continue doing upgrades normally as usual

fk2

jr. member

Activity: 67

Merit: 2

Quote from: papampi_2 on October 23, 2018, 05:25:53 AM

Quote from: fk2 on October 22, 2018, 06:16:41 AM

Where can we find 3.0 image?

Both 16.04 and 18.04 images will clone the latest release at first boot.

Just edit the firstboot.json in small fat partition and set branch to "release"

I was waiting with another 4x 1080 rig for this release so right now I was hddrawcoping the latest image 18.04 to a ssd. firstboot.json was edited already as you explained so hooked it up and gave it a boot. Gave it 10 minutes to boot until the gpu fans spinned up and logged in with SSH. checked version numbering withr eport and was on 3.0, so I edited minimal configuration info in 1bash and had a reboot. I was really looking forward for NICE_X16R but unfortunately rig reboots and idles

Code:

Operating System info:
Kernel : 4.15.0-33-generic
OS : Ubuntu 18.04.1 LTS
System : (gcc 7.3.0 7.3.0-16ubuntu3)) #36-Ubuntu
nvidia driver : 396.54

nvOC info:
nvOC path : /home/m1/NVOC/mining
nvOC : 0019-3.0
Report : 0012
1bash : 0045
1bash.template: 0045
3main : 0026
5watchdog : 0022
6tempcontrol : 0008
wtm switch : 0023
wtm profit : 0004
pool switch : 0002
minerinfo : 0012

Hardware info:
Motherboard : ASUS PRIME Z270-A Rev 1.xx
BIOS ver. : 1203 12/25/2017
CPU Model : Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores : 2 (Cores + Threads)
Mem Total : 3978180 kB
Mem Free : 2730960 kB
Swap Total : 0 kB
Swap Free : 0 kB
Ethernet : Intel I219-V

CUDA SDK version
nvcc path : /usr/local/cuda/bin/nvcc
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Tue_Jun_12_23:07:04_CDT_2018
Cuda compilation tools, release 9.2, V9.2.148

nvOC is not installed as a service

HDD and Partion info:
NAME SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR MODEL REV MOUNTPOINT
sda 55.9G disk 0 0 sata ATA Patriot Flare 21.1
├─sda1 9M vfat part 0 0
└─sda2 55.9G ext4 part 0 0 /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)

Local git branch and submodules status:
## release...origin/release
+38cdf9e424b2387c324520f674c3ef5c649e4fa7 miners (heads/3.0-miners)
## HEAD (no branch)
-cd6fab68823e247bb84dd1fa0448d5f75ec4917d ANXccminer/src
-baf6c9e4e36c9cc1b67698ee2977d445f598c573 ASccminer/src
-24c65cf166bbb3332d60e2baef859ceb604e5d49 ETHMINER/src
-c5ab73837c8024f1e6b8fe7ad46e6881fb8366e6 KTccminer/src
-bedaf007d4619fc4157aeafb59b44850f08d93f1 KTccminer_cryptonight/src
-7d41d49b92db27b9ab80270adaa92f6b06d1ef78 KXccminer/src
-78dad7dd659eae72a07d2448de62b1946c1f2b41 MSFTccminer/src
-8affcb9cd09edd917d33c1ed450f23400f571bdb NAccminer/src
-9e86bdd24ed7911b698f1d0ef61a4028fcbd13c5 SPccminer/src
-c800f1a803e1b2074ed2a7c15023c096d0772048 SUPRminer/src
-a81ab0f7a557a12a21d716dd03537bc8633fd176 TPccminer/src
-48b170a5828256600ca71e66d4c114af4e114236 VERTMINER/src
-c0ab1734332d6472225d8ac7394f6fcba71aabc9 XMR_Stak/src
-bfd1c002f98f2d63f2174618838afc28cf4ffffe cpuOPT/src

1bash settings:
1bash version .............: 0045
LOCAL or REMOTE ...........: REMOTE
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO

Watchdog ..................: YES
SYSRQ Reboot ..............: NO
Watchdog Cycle ............: 15
GPU Utilization Threshold .: 50
Alternate Pool ............: NO

Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 75
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 70
MAXIMAL_FAN_SPEED .........: 95

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

TELEGRAM_MESSAGES .: NO
TELEGRAM_ALERTS ...: NO

HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: YES

POWERLIMIT MODE ...........: GPU_SPECIFIC
GPU0 Power Limit ..........: 160
GPU1 Power Limit ..........: 160
GPU2 Power Limit ..........: 160
GPU3 Power Limit ..........: 160
OVERCLOCK MODE ............: GPU_SPECIFIC
GPU0 Core Overclock ........: 120
GPU0 Memory Overclock ......: 1200
GPU1 Core Overclock ........: 120
GPU1 Memory Overclock ......: 1200
GPU2 Core Overclock ........: 120
GPU2 Memory Overclock ......: 1200
GPU3 Core Overclock ........: 120
GPU3 Memory Overclock ......: 1200

GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: Icemine02
plusCPU ...................: NO

AUTO_SWITCH ...............: NO
COIN ......................: NICE_X16R
ALGO ......................: UNDEFINED
MINER .....................:
NICE_X16R WORKER ................: Icemine02
NICE_X16R ADDRESS ...............: ...
NICE_X16R POOL ..................: x16r.eu.nicehash.com:
NICE_X16R PORT ..................: 3366

Code:

m1@m1-desktop:~$nvOC master-log
==> /home/m1/NVOC/mining/nvoc_logs/screenlog.0 <==

==> /home/m1/NVOC/mining/nvoc_logs/tempcontrol-screenlog.0 <==

GPU 0, Target temp: 75, Current: 19, Diff: -56, Fan: 70, Power: 9.78
GPU 1, Target temp: 75, Current: 14, Diff: -61, Fan: 70, Power: 12.44
GPU 2, Target temp: 75, Current: 18, Diff: -57, Fan: 70, Power: 11.45
GPU 3, Target temp: 75, Current: 16, Diff: -59, Fan: 70, Power: 10.70
Tue Oct 23 10:51:30 EDT 2018 - All good, will check again in 18.0 seconds

==> /home/m1/NVOC/mining/nvoc_logs/watchdog-screenlog.0 <==
Watchdog for nvOC v0019-3.0
Version: v0019-3.0.0022

Watchdog for nvOC v0019-3.0
Version: v0019-3.0.0022

tail: cannot open '/home/m1/NVOC/mining/nvoc_logs/8_wtmautoswitchlog' for reading: No such file or directory

==> /home/m1/NVOC/mining/nvoc_logs/tempcontrol-screenlog.0 <==
GPU 0, Target temp: 75, Current: 19, Diff: -56, Fan: 70, Power: 10.03
GPU 1, Target temp: 75, Current: 14, Diff: -61, Fan: 70, Power: 12.54
GPU 2, Target temp: 75, Current: 18, Diff: -57, Fan: 70, Power: 10.86
GPU 3, Target temp: 75, Current: 16, Diff: -59, Fan: 70, Power: 11.24
Tue Oct 23 10:51:48 EDT 2018 - All good, will check again in 18.0 seconds

miner-log is empty, auto_start_miner is enabled in 1bash. What to do?

edit1: saw that there was no NICE_X16R in X16R Algo list so added that. Next problem:

Code:

m1@m1-desktop:~$nvOC miner-log
[NOTICE ] 18/10/23 10:54:16 Starting on stratum+tcp://x16r.eu.nicehash.com::3366
[ERROR ] 18/10/23 10:54:16 Stratum connection failed: Port number ended with ':'
[ERROR ] 18/10/23 10:54:16 ...retry after 30 seconds
[INFO ] 18/10/23 10:54:16 GPU monitoring enabled (NVML).
[INFO ] 18/10/23 10:54:16 Mining 'x16r' with 4 threads.
[X16 ] 18/10/23 10:54:16 Hashorder algorithm legend: Slow Medium Fast
[ERROR ] 18/10/23 10:54:46 Stratum connection failed: Port number ended with ':'
[ERROR ] 18/10/23 10:54:46 ...retry after 30 seconds
[ERROR ] 18/10/23 10:55:16 Stratum connection failed: Port number ended with ':'
[ERROR ] 18/10/23 10:55:16 ...retry after 30 seconds

the 3.0 script generates double :: port. when I start the command with just one : it fails because of stratum auth. I can see a . in front of my USER which is not in 1bash

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: Rig4p on October 22, 2018, 03:22:33 PM

Quote from: LuKePicci on October 21, 2018, 07:17:30 PM

xmr-stak is updated already in the stable branch, so if you perform upgrade you will have them fetched also

Thank you LuKePicci. Is there a list of the latest miner versions picked up by nvOC? The 3.0 stable release?

Check nvOC miners repo

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: fk2 on October 22, 2018, 06:16:41 AM

Where can we find 3.0 image?

Both 16.04 and 18.04 images will clone the latest release at first boot.

Just edit the firstboot.json in small fat partition and set branch to "release"

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: CryptAtomeTrader44 on October 22, 2018, 06:14:24 PM

Quote from: fk2 on October 22, 2018, 06:16:41 AM

Where can we find 3.0 image?

LukePicci or Papampi
Can you give us back, or remember the links and procedures to install the new version without rewriting a complete image on the disk?

Just rename your current ~/NVOC/mining to some thing else like ~/NVOC/mining_old
Then run:

Code:

git clone --depth 1 --branch release https://github.com/papampi/nvOC_by_fullzero_Community_Release.git /home/m1/NVOC/mining

It will make a new mining folder and clone the release branch inside.
Edit and copy your 1bash to the new ~/NVOC/mining

Run nvOC upgrade to fetch miners

Code:

bash ~/NVOC/mining/nvOC upgrade

Or to keep both, clone to a new folder and make the changes in gnome-terminal default profile.

You can also have a look at nvOC beta testing wiki

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: fk2 on October 22, 2018, 06:16:41 AM

Where can we find 3.0 image?

There is not an image.

You have to use precedent ISO and use git to push 3.0 new stable branch on your system in another folder near from mining folder from 19.2.1.

I had to learn to use git but it is not very complicated.

On the other hand you will have to recompile all the minning software and for my part, the papampi script did not work. It downloads the sources from github, from the dedicated page, but can not properly compile the mining software in stride.

And XMR-Stak seems to be slower once compiled by hand.

I guess it's due to cryptonight v8, but we'd have to see if other mining software is more efficient. Too bad because I appreciate Xmr-Stak which is very stable. I was doing 6.5 KHs, and I lost about 1 to 1.5 KHs. I now have 4.5 to 5KHs :-(
Note that I have not tried to push the overcloking as on the previous version. I realized that paradoxically I was wasting power overclocking and I had a big difference between the pool and the software display. What does not seem to be the case with this new version. Si i will try again to overclock and verify if the pool display the same hashrate with OC. My pool for monero is pool.supportxmr.com. the second in hashrate power.
Note : th tx cost must be lower with this bulleproof and POW hard fork, but i don't verified yet. If someone can confirm, with a tx address, i accept to see it.

I still can not get auto start XMR-stak running with all scripts as it should. For some reasons unknown to me, I was able to launch it by hand yesterday, but not via nvOC scripts.

Another problem, from the system this time, is about DNS resolution. Systemd took control of the name resolution and it works very badly for me. Ubuntu loose more than 10 minutes before finding a normal name resolution. grrrrrrr
As soon as I put the nameserver in the resolv.conf file everything works fine immediately. Except for every startup, the resolv.conf file is restored by default without the line I added. grrrr
I wonder about the usefulness of having done so in ubuntu 18.04 ...

LukePicci or Papampi
Can you give us back, or remember the links and procedures to install the new version without rewriting a complete image on the disk?

Translated from French with Google translation and not re-read for correction.

Rig4p

newbie

Activity: 59

Merit: 0

Quote from: LuKePicci on October 21, 2018, 07:17:30 PM

xmr-stak is updated already in the stable branch, so if you perform upgrade you will have them fetched also

Thank you LuKePicci. Is there a list of the latest miner versions picked up by nvOC? The 3.0 stable release?

fk2

jr. member

Activity: 67

Merit: 2

Where can we find 3.0 image?

gs777

member

Activity: 118

Merit: 10

Also how to kill screensaver in Ubuntu 18.04?
It's quiet annoying

gs777

member

Activity: 118

Merit: 10

Can anyone try to mine RVN from nvOC 19.21 Huh

Doesn't matter what I was trying it simply doesn't start. At all!

LuKePicci

jr. member

Activity: 128

Merit: 1

xmr-stak is updated already in the stable branch, so if you perform upgrade you will have them fetched also

Rig4p

newbie

Activity: 59

Merit: 0

Do we know if the monero_v8 versions of xmr_stak and cpuminer will update in 3.0 using the upgrade function?

LuKePicci

jr. member

Activity: 128

Merit: 1

The 2.1 cycle is over, nvOC 3.0 is the final release after the long-tested 2.1 develops, and will receive bugfix and miners updates/additions. Any new feature from now on will go directly into the next development branch named 3.1-dev, you are free to install nvOC targeting this dev branch the same way you may have done with 2.1, but for stable mining you should stick on 3.0-stable. It is also very unlikely from now on that the 3.0 1bash.template gets patched in such a way that you will need to start creating your 1bash from scratch after an update, so you should find very easy to get minor updates by the nvOC upgrade command.
By default any recent nvOC image has the "release" branch as default target selected in firstboot.json. When a minor bugfix or patch is submitted to the 3.0-stable branch it gets merged into the release branch as soon as it gets tested. If you participated to 2.1 beta testing from early phases running it on top of a legacy 2.0 image, or you explicitly targeted the 19-2.1 branch in firstboot.json you will not get any more update from 3.0-stable / release because you are still on the old 19-2.1 branch. If this is the case, please, fetch and checkout an active branch. You can read your current branch name from nvOC report command.

Topic: [OS] nvOC easy-to-use Linux Nvidia Mining - page 9. (Read 417954 times)