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

[Rizao]

Hey there. I've gotta a problem while mining XMR. It shows : Result rejected by the pool.
Im running nvOC_v0019-1.4

Anyone had this?

[Stubo]

@stubo every time you open a gnome-terminal to its default profile nvOC runs again from scratch, it is like this from fullzero nvOC autostart method design. If you just need a shell open guake or lauch gnome-terminale with another profile. There is an alternative to gnome-terminal autostart based on systemd. Dig further in the code, the initial setup install may suffer some rough edges but in the end works like a charm, and the restart/stop commands are much more reliable.

The option in firstboot to use a different path works, but you simply can't use your user profile home as the root of a git repo. You must specify an empty folder where the m1 user has write access. Regarding the target branch name, it has to be an existing branch of the git repo. Go to github, whatever you see as git branch name is a valid string to put there, release (latest stable release, currently fed up from 3.0-stable, will upgrade to 4.0 whenever released), 19-2.1 (old dev branch), 3.0-stable (the current stable branch), 3.1-dev (the current dev branch) or any other feature branch of whatever is not merged yet, including your own branches if you have push rights to the git repo.

If you would like to write some good doc about firstboot.json options would be just awesome.

Thanks for the tips. I don't have much time to devote to this unlike this time last year. I will say again what a great job you guys have done here and I realize how hard it is to be perfect, but you have to try, right?

So, I have it up and running on my test rig now and I just noticed that "nvoc start" now works in REMOTE mode. This is AWESOME as it gives one the ability to do lots of things like change OC, COIN, etc. on the fly without a reboot. Start never did work in 19-2.0 when in REMOTE but it worked fine for LOCAL. I am very happy to see you guys got it working fully.

[Stubo]

Hey Devs:

I found a bug in the nvOC script. I noted that it was not reporting the max power limit for GPUs correctly so I dug in. On line 196 of the 3.0-stable release, you have this:

Code:

    POWERMAX=$(echo "$PWRLIMIT/1" | bc)

but it should be

Code:

    POWERMAX=$(echo "$POWERMAX/1" | bc)

Also, where can I find more info on this (from 1bash of 3.0-stable):

Code:

#        - Pro Settings are not for the faint-hearted. Dont use if you dont know what they are. 

I scoured 1bash and 3main for this release and don't see anything else about it. Perhaps it is in a different release branch?

Thanks.

[LuKePicci]

Open a quick issue on github for the powerlimit reporting bug, such that we will be able to remember to fix this the next time attaching this to another more urgent PR.

That line about "pro settings" just refers to more complex policies for OC levels, like algo specific with gpu offset. They are quite complex to understand at a first glance but will be clear what they do once someone realize he needs such useful policies.

[Stubo]

That line about "pro settings" just refers to more complex policies for OC levels, like algo specific with gpu offset. They are quite complex to understand at a first glance but will be clear what they do once someone realize he needs such useful policies.

That type of OC is just what I want as I have 2 hosts with GPUs that are the same model (e.g., 1080 Ti) but from different vendors so they require different power and clocks. Ideally, I would like to be able to OC per model/vendor and again for algo. Currently, I do this with different 1bash files named 1bash_$coin. I suppose that is the least painful way to do it. My point was that I see this one mention of it in 1bash but no support for it in 3main. Which branch has it?

[LuKePicci]

It's supported for sure, it's the first thing I pushed into nvOC.

Tweaking per-vendor or model is a no go because of the silicon lottery, so use the algo specific with offset and you will be happy.

edit: it is everywhere mentioned in 3main, just search for "offset"
https://github.com/papampi/nvOC_by_fullzero_Community_Release/blob/3.0-stable/3main

[fk2]

I went to my colocation host yesterday with a fresh ssd and latest nvOC to get the latest mining software, i.e. X16R, for my 1080 rig. Unfortunately the ssd did not want to boot so I had to leave without new system. Before I go for another trip, is it maybe possible to update the following system to latest nvOC with latest cuda in order to get x16r working?:

Code:

Operating System info:
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 :  396.45

nvOC info:
nvOC path     :  /home/m1/NVOC/testing
nvOC          :  0019-2.1

[LuKePicci]

Sure, just install cuda-9-2 following instructions about installing cuda from specific ppa packages.

Here is the detailed installation guide: https://docs.nvidia.com/cuda/archive/9.2/cuda-installation-guide-linux/index.html#ubuntu-installation
Here is the ppa (and a recap of the same install steps) for 16.04: https://developer.nvidia.com/cuda-92-download-archive?target_os=Linux&target_arch=x86_64&target_distro=Ubuntu&target_version=1604&target_type=debnetwork

Just use cuda-9-2 package instead of the generic cuda metapackage in the last step.

[Rizao]

Hey there. I've gotta a problem while mining XMR. It shows : Result rejected by the pool.
Im running nvOC_v0019-1.4

Anyone had this?

Please guys, I really want to mine xmr. Help a bro out

[CryptAtomeTrader44]

Hey there. I've gotta a problem while mining XMR. It shows : Result rejected by the pool.
Im running nvOC_v0019-1.4

Anyone had this?

Please guys, I really want to mine xmr. Help a bro out

I think you should réimage with new image ubuntu 18.04 LTS  : https://github.com/papampi/nvOC_by_fullzero_Community_Release

and use command on remote ssh connection :  nvOC upgrade to update scripts

then complete new 1bash file.

You can look here https://github.com/papampi/nvOC_by_fullzero_Community_Release/wiki/nvOC-19-2.1-beta-testing

Don't forget to upgrade your monero wallet and download his blockchain https://github.com/monero-project/monero-gui/releases (~60Go)

You can also compile xmr-stak yourself https://github.com/fireice-uk/xmr-stak/releases
How To compile : https://github.com/fireice-uk/xmr-stak/blob/master/doc/compile_Linux.md

I note in passing to Lukepicci and Papampi that a new corrective version was published on 25/10/2018 on their github. This one improves the hashrate which had strongly diminished due to the questions of adjustments for hashing cryptonight_v8.

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

[papampi_2]

nvOC_19-3.x, Ubuntu 16.04, Dual-Cuda 8+9.2, Nvidia 410, 2018-10-27

Mega Download Link
OneDrive Download Link

[CryptAtomeTrader44]

nvOC_19-3.x, Ubuntu 16.04, Dual-Cuda 8+9.2, Nvidia 410, 2018-10-27

Download Link

Why come back to version 16.04 of ubuntu?
What was the problem with version 18.04?

I admit that for my part, I did not appreciate the problem of DNS that takes too much time to synchronize properly.

As soon as I finish syncing my Monero wallet I download it and install it on a new disk.

The idea of a 1 bash.template lite is good, I complete my 1 bash faster this way.

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

[LuKePicci]

First, only cuda-10 is officially supported by nvidia in ubuntu 18.
Second, this new image fills the gap in having a dual cuda image ready to load on your disk, the previous ubuntu 16 image included cuda-8 only.
Third, more than a thing is not working at its best in ubuntu 18, there are some problems, more or less significant with curl, tempcontrol and compilation in general because of the updated gcc suite.
In short, as long as you run miners designed for cuda 8/9 I recommend to go with ubuntu 16. Te other images are still valid, it's all up to your preferences or experiences.

[CryptAtomeTrader44]

First, only cuda-10 is officially supported by nvidia in ubuntu 18.
Second, this new image fills the gap in having a dual cuda image ready to load on your disk, the previous ubuntu 16 image included cuda-8 only.
Third, more than a thing is not working at its best in ubuntu 18, there are some problems, more or less significant with curl, tempcontrol and compilation in general because of the updated gcc suite.
In short, as long as you run miners designed for cuda 8/9 I recommend to go with ubuntu 16. Te other images are still valid, it's all up to your preferences or experiences.

Thanks for theses explanations details Lukepicci.

As i said in my last message, i will install it after i synchronized my XMR wallet with his new CNV8 blockchain database

[gs777]

First, only cuda-10 is officially supported by nvidia in ubuntu 18.
Second, this new image fills the gap in having a dual cuda image ready to load on your disk, the previous ubuntu 16 image included cuda-8 only.
Third, more than a thing is not working at its best in ubuntu 18, there are some problems, more or less significant with curl, tempcontrol and compilation in general because of the updated gcc suite.
In short, as long as you run miners designed for cuda 8/9 I recommend to go with ubuntu 16. Te other images are still valid, it's all up to your preferences or experiences.

That's the reason why I switched back to 16.04 from 18.04.
It is more stable
 

[gs777]

Was mining RVN last two days but my daily mining profit was
about 50% of whattomone RVN calculation.
Mined with zenemyminer/nvOC 19.3
Just wondering is anyone have same experience?

[Stubo]

I am on nvOC 19-3.0-stable and noticed that BCI was top of the heap (earnings on WTM) a few hours ago so I decided to dig into it and look into how/if it is supported in this version. The first thing that I noticed is that BCI is listed in 1bash but it appears as an equihash algo coin. Obviously, that is old as BCI is now progPow so it requires a different miner.

Before I re-invent the wheel and modify my 1bash and 0 miner to handle progPow and BCI, is this available in a new branch that I am unaware of?

Thanks in advance.

[LuKePicci]

That is not. You should be able to define the new algo/miner mapping entirely in 1bash, and adding the new required miner binary into miners/{minername}/{minerversion}/ folder. Then create in that same folder a file like this one and name it nvoc-miner.json, you can skip minerinfo/install/compile sections, they are optional. You can see some other examples for more complex miner packages like the xmr-stak that makes use of a wrapper script to handle specific operations. When it's working, if you want,  share it here.

[LuKePicci]

Hey there. I've gotta a problem while mining XMR. It shows : Result rejected by the pool.
Im running nvOC_v0019-1.4

Anyone had this?

Please guys, I really want to mine xmr. Help a bro out

I'm sorry, you are using a very old version of nvOC which I don't know/remember anything about. I can't help you, maybe someone else who is currently mining xmr on the old images could.

[gs777]

Mining with nvOC 19.30 N410 at 13x1080 Great hash rate!
But temp control dead after first few minutes of start
Is anyone has same issue