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

[koody]

ok, thanks.

[papampi_2]

Done.
New link added, hopefully all is good now.

[papampi_2]

Can somebody hlep me with OhGodAnETHlargementPill? How to run it on nvOC?

Just set it to yes in 1bash

Code:

OhGodAnETHlargementPill="NO"

change to:

Code:

OhGodAnETHlargementPill="YES"  

[fk2]

any chance for current 2.1 beta rigs to update to the latest 18.04 release with dual cuda support by remote/without imaging?

[LuKePicci]

any chance for current 2.1 beta rigs to update to the latest 18.04 release with dual cuda support by remote/without imaging?

Nope, if you really need dual_cuda support and you can't reimage right now, you could try installing the other cuda-9-2 runtime manually (use cuda distribution specific packages, never cuda runfiles), but you have to be very careful because it could mess with nvidia drivers and get you unable to boot or recover remotely.

[Brainfruit_Me]

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

[Hardforkman]

Hi! Any one can help me with login, user m1 pass miner1 not working, going to the same login windows

[LuKePicci]

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

Post some logs of the error and a full report, just in case.

[LuKePicci]

Hi! Any one can help me with login, user m1 pass miner1 not working, going to the same login windows

May not be a wrong password problem.

[papampi_2]

Hi! Any one can help me with login, user m1 pass miner1 not working, going to the same login windows

That could be xorg problem, try to ssh and restore xorg with

Code:

bash ~/NVOC/mining/nvOC restore-xorg

Is the onboard GPU disabled in bios?

[papampi_2]

any chance for current 2.1 beta rigs to update to the latest 18.04 release with dual cuda support by remote/without imaging?

Nope, if you really need dual_cuda support and you can't reimage right now, you could try installing the other cuda-9-2 runtime manually (use cuda distribution specific packages, never cuda runfiles), but you have to be very careful because it could mess with nvidia drivers and get you unable to boot or recover remotely.

Due to Ubuntu 18.04 libcurl3/4 limitations I will make a dual cuda 16.04 image when I find some free time

[papampi_2]

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

Post some logs of the error and a full report, just in case.

I noticed it on some of my rigs too, no idea why
And the error changes from GPU to GPU after each reboot
Same SSD works with no problems on a rig and shows that error on another almost identical rig.

[Brainfruit_Me]

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

Post some logs of the error and a full report, just in case.

I noticed it on some of my rigs too, no idea why
And the error changes from GPU to GPU after each reboot
Same SSD works with no problems on a rig and shows that error on another almost identical rig.

I finally just had to reflash the USB until it took. It still gets the error but it doesn't stop the miner from starting now, thankfully. Overall it was a bigger pain to initial boot compared to 19 - 2.0 but with the new cuda enhancements I can run a much more efficient miner. ~50% more hash rate and efficiency per watt!
Thanks for your continued work and support for nvoc!

[LuKePicci]

It still gets the error but it doesn't stop the miner from starting now, thankfully.

I'm not sure which error are you mentioning but if my guess is correct then you should be safe to ignore it. Just check if hashrates are what you expect.

[fk2]

my rig no 1 is currently constantly rebooting because watchdog loses gpu0-7 after a couple of minutes even though they are mining fine. I wanted to disable the watchdog/auto reboot but this is the opton "auto start miner = yes" which prevents the mining starting at all if set to no...

[LuKePicci]

Try reducing the utilization threshold, the default one is quite hight for miners like z_ewbf and is likely to get the watchdogs rebooting for no valid reason. I set mine to 55% if I remember correctly to avoid such behavior.

[fk2]

Even though the error was more like "lost" I will try that but what I was concerned about is that I am not able to start the system with bash nvOC start because the mining process won't start. Only when auto start option is active and that doesnt stop watchdog rebooting in fail case even when watchdog disabled.

In other words: a seperate option to start mining process once with script is requested. I can fire the whole command manually by myself but maybe not everyone is able to

[papampi_2]

Even though the error was more like "lost" I will try that but what I was concerned about is that I am not able to start the system with bash nvOC start because the mining process won't start. Only when auto start option is active and that doesnt stop watchdog rebooting in fail case even when watchdog disabled.

In other words: a seperate option to start mining process once with script is requested. I can fire the whole command manually by myself but maybe not everyone is able to

If there is a problem with a GPU temp control will do the rebooting too, as it catches the error when trying to get the temp.
So just disabling watchdog will not prevent rig with a faulty GPU from rebooting

[hallzero]

Hi there,

i have a strange problem. Updated a long running nvOC 19 2.0 community release rig consisting of 4 1050ti`s with one more 1050ti so it contains 5 now but it is only showing 4 GPU`s i can´t get nvOC to use the 5th gpu.

In order for you to spare a few hints i did the following.
On the hardware side i checked all risers and cables, also i swapped all cards within the rig, didn´t change anything it continues to mine with only 4 gpu`s. Then i swapped all cards into a different rig to see whether a card was faulty, it was not.

So, as far as hardware goes:
1. All risers and all cables check good
2. All gpu´s work (just not within this nvOC rig)

So i went on with the software side of things:

First i stopped everything with

Code:

./nvOC stop

then i checked the Nvidia X-Server it only shows gpu 0-3 so the 5th is missing

then i updated the nvOC installation with

Code:

sudo -- sh -c 'apt-get update; apt-get upgrade -y; apt-get dist-upgrade -y; apt-get autoremove -y; apt-get autoclean -y'

and rebooted.

No change it works and is mining with 4 gpu´s it does not recognize the 5th and i can´t get it to do so.

Using

Code:

./nvOC gpumap

only finds 4 gpu´s

Any ideas?

[WaveFront]

Hello,
I am considering upgrading from the 19-2.0 to the 19-2.1.
How mature do you think the 19-2.1 is? Is it at an advanced beta stage or is it better to stay on the non beta 19-2.0 release?