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

[fullzero]

Anybody got X13 (DeepCoin) running in nvoc ? How much mh/s are you getting ?

I get 30 mh/s with 2x 1060 and 1x 1080 ti

Not sure if its worth...

I am not familiar with DeepCoin; if you have made a 1bash code block for it; please post it + pool settings and I will add it.

[fullzero]

If you are using the Maxximus007_AUTO_TEMPERATURE_CONTROL  ensure you are also changing the individual powerlimits for each GPU:

Code:

INDIVIDUAL_POWERLIMIT_0=75

INDIVIDUAL_POWERLIMIT_1=75

INDIVIDUAL_POWERLIMIT_2=75

for a 1080ti I recommend using between a 200 and 225 powerlimit.

If you have already done this:

It is also possible there are some bad sectors on your USB key and they are causing problems.  I have had 5x USB keys go bad so far; although I do reimage a lot with test rigs.

It might be a good idea to try using another USB key or SSD.

fullzero, sorry, problem was in riser. Thank you for NvOc.

Np; glad you found the problem.

[fullzero]

Witnessed an odd issue with v0018 today.  All 8 of my 1050Tis only report ~13 MH/s.   Thought it was risers and swapped a couple out, no change.  Re-imaged the SSD and upon initial boot up, everything was fine, reporting 14.7 MH/s.  As soon as I rebooted it dropped the hash back down to 13 MH/s.  Swapped out cards and booted with just a single card same result.   Re-imaged again, same result.  Any idea what would cause this?   

I am running ASUS Z270 Prime-A boards with Gigabyte 1050Ti Boost Clock 1506 cards.  I don't think it is an ETH difficulty issue as my other rigs have the same configuration and I am not seeing the same issue.  My power is set at 60watts, temp settings at 60, my fan setting 50, core OC is 0 and mem OC is 1450.  I changed around power and mem settings, but no difference.

Could one of the modules be adjusting this to match one of the above variables?  My cards never get hot enough for the fan to go above 50.

Autotemp could be lowering the powerlimit; but only after your fans go to max.  If they don't go above 50% then that is unlikely.  The current powerlimit is displayed by the autotemp readout, so you can verify if it has changed when this is the case.

If it has been; I would raise your temp target to 70.

Watchdog only restarts 1bash or the rig; it shouldn't make an OC changes.

What kind of risers are you using? Are you powering them direct with Pcie 6pin?  If not this may be the problem.

Also you can probably get the same MH/s with the minimum powerlimit and -100 or -200 cc.

[hatch789]

So interesting (scary) discovery last night. I built a brand new 7 GPU rig just like my other ones I have ...identical components. Brand new cards from newegg GTX 1060 3GB SC version. -I like these cards so I stick with them. Anyway my other rigs are using both the 1060 SC and regular 1060 (non SC) version without issue. The SC just run cooler but hash the same as their non SC counterpart. So my normal hashrates on my existing rigs is 23MH/s and I am quite pleased with that.

I did the very few bios updates on my Asus Z270A motherboard and slapped a pre-built nvOC USB Stick in ...away she went. However this is where it got bad. I was only getting about 18MH/s with the same exact OC ratings as my other rigs. I was getting lag and ERRORS as well. So OK ...thought maybe I have a bad riser card. I start disconnecting and removing everything to start with the first card only. Just 1 card in the first x16 slot closest to the CPU as it should be. Same thing.

Still getting 18MH/s and some hanging. So I change that riser card and cable out completely. Still the same thing. I reduce the OC to 0/0 and my MH/s drops to about 15MH/s now. But the system seems to be stable.

I'm really scratching my head on this guys. I futzed with this for over 3 hours last night trying all sorts of things. I'm starting to wonder if the Nvidia driver install doesn't update the bios on the video cards somehow. So the fact that the driver was already installed on this image, the cards never got "flashed"? My other rigs were part of windows builds from the ground up and cards were in the rig when I updated the video drivers. So if my theory is correct those GPU's got flashed at that time and hence they are fine with nvOC0018.

But this new rig only ever booted into a fully built nvOC0018. -Anyone run into this themselves? -I have another motherboard so I'm going to try that on the off-chance that I have a bad motherboard somehow? Help and suggestions welcome. Other similar experiences would be great.

[fullzero]

anybody know how to build TPccminer from source code?

I want to update TPccminer to the latest version, so I downloaded the source code from https://github.com/tpruvot/ccminer, run build.sh, it throws a couple of errors:

bignum.hpp:63:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
 class CBigNum : public BIGNUM
                        ^
In file included from /usr/local/include/openssl/bn.h:32:0,
                 from bignum.hpp:20,
                 from bignum.cpp:8:
/usr/local/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM {aka struct bignum_st}’
 typedef struct bignum_st BIGNUM;
                ^
In file included from bignum.cpp:8:0:
bignum.hpp: In constructor ‘CBigNum::CBigNum()’:
bignum.hpp:68:21: error: ‘BN_init’ was not declared in this scope
         BN_init(this);
                     ^
bignum.hpp: In copy constructor ‘CBigNum::CBigNum(const CBigNum&)’:
bignum.hpp:73:21: error: ‘BN_init’ was not declared in this scope
         BN_init(this);
                     ^
bignum.hpp:74:30: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)’

...........

I will try to add this today; I have been distracted by the Bitcoin events.

[fullzero]

I'm using claymore setup and problem is that usb disk is filling up very quickly and OS running out of free space.
Just imaged on ssd, extended the original 16gig partition to 100gig and same s... its already filled above 40gigs.. Couldn't find any similar issue on this thread..

I am not sure, but i think a read about this on this thread. That from watchdog log if i remenber correct.
nvOC18 (+ renew all config file ) fix this issue.

Check which directories are taking up all the space type :

du -hx -d1

Go into those directories and type the command again to see the listing of that directory.

Most likely you have some disk errors; which are causing this problem.  I would try using a different USB or SSD and see if the same problem occurs.

[fullzero]

Hello! I recently started to use v0018, previously I used windows 7, 8,10 and used to Teamviewer. Here is the problem with the launch of Teamviewer. I solved it thus:
Removed Teamviewer and installed it again.
Added to /etc/rc.local:

Code:

killall teamviewerd
/opt/teamviewer/tv_bin/scripts/teamviewer &
exit 0

In the file 1bash commented out the line:

Code:

if [ $TEAMVIEWER == "YES" ]
then
running=$(ps -ef | awk '$NF~"teamviewer" {print $2}')
if [ "$running" == "" ]
then
sudo teamviewer --daemon enable
sleep 2
guake -n teamviewer -r teamviewer -e "teamviewer"
running=""
fi
if [ $SLOW_USB_KEY_MODE == "YES" ]
then
sleep 6
fi
fi

if [ $TEAMVIEWER == "NO" ]
then
running=$(ps -ef | awk '$NF~"teamviewer" {print $2}')
if [ "$running" != "" ]
then
sudo teamviewer --daemon disable
sleep 2
running=""
fi
if [ $SLOW_USB_KEY_MODE == "YES" ]
then
sleep 6
fi
fi

After that Teamviewer was run at system start without problems!
Please forgive me for the bad English...

To enable / launch Teamviewer; in 1bash change:

Code:

TEAMVIEWER="NO"   

to

Code:

TEAMVIEWER="YES" 

If:

Code:

TEAMVIEWER="YES" 

is not launching teamviewer please let me know. 
 

[fullzero]

Thanks for your effort FullZero love your work.

I tried your NVOC on my 13 card 1070 rig, but an into a few issues.

- I couldn't get all 13 to be recognised. claymore continues to report only 6 GPUs (mobo is ASROCK H110 BTC)
- I tried to set powerlimit both global and individual to 105W, and it only holds the 105W limit for about 3-5 seconds, after that it quickly creeps up to 125W and holds at 125W. I have tried with the maximus script on and off no difference.

Anyone have any issues like this?

How are you powering this rig?  Have you joined the PSUs (using an adapter to connect them) if you are using multiple ones?  If not the system not recognizing all your GPUs is most likely related to this.


With the powerlimit:

Most likely you aren't setting: 

# Note you MUST set individual powerlimits if using Maxximus007_AUTO_TEMPERATURE_CONTROL

INDIVIDUAL_POWERLIMIT_0=75

INDIVIDUAL_POWERLIMIT_1=75

INDIVIDUAL_POWERLIMIT_2=75

INDIVIDUAL_POWERLIMIT_3=75

INDIVIDUAL_POWERLIMIT_4=75

INDIVIDUAL_POWERLIMIT_5=75

INDIVIDUAL_POWERLIMIT_6=75

INDIVIDUAL_POWERLIMIT_7=75

INDIVIDUAL_POWERLIMIT_8=75

INDIVIDUAL_POWERLIMIT_9=75

INDIVIDUAL_POWERLIMIT_10=75

INDIVIDUAL_POWERLIMIT_11=75

INDIVIDUAL_POWERLIMIT_12=75

INDIVIDUAL_POWERLIMIT_13=75

Also I recommend updating your 1bash and the other files with the ones from the bux fix download on the Original Post.  I know you aren't using the newest 1bash because your individual powerlimit is setting to 125 and not 75.

[fullzero]

Hi, guys!

I have a problem. My rig is 8 Nvidia 1080Ti on motherboard MSI Z170 M5, works on win 10 with nicehash ok all cards working, but windows is eating too much and time to time there are problems exactly with system. Anyway, I decided to try nvOC. Used to play with Linux in my childhood and respect it for stability and convenience.

With nvOC I have few issues: 1. It boots too long I think. 3-5 minutes on my rig.

2. It reboots every 5 minutes.

3. I'm trying to mine LBC, but every time it connects I get the message: Stratum identification failed.


What am I doing wrong? What to look at?

Thanks in advance. I enjoy using nvOC even for short time ))

Booting will take longer than Windows; eventually I will make a lite build that will boot faster: but this is not currently a priority vs other more useful improvements.

This is what is most likely happening:

You are not connecting successfully to the pool because you are using a pool where the workername must be predefined at the pool to be authorized.

Because it is not; when you try to connect the pool rejects the connection.  

This causes your GPU utilization to be below 90%

This causes the watchdog to restart 1bash; and eventually reboot your rig.


Go to your pool / login and make a workername, then change the workername on your rig to match.

Also if you are rebooting every 5 mins; You haven't downloaded the newest 1bash and files ( bug fix download link on the original post).


Let me know if this is; what is, in fact the case: or if the problem persists.

[fullzero]

So interesting (scary) discovery last night. I built a brand new 7 GPU rig just like my other ones I have ...identical components. Brand new cards from newegg GTX 1060 3GB SC version. -I like these cards so I stick with them. Anyway my other rigs are using both the 1060 SC and regular 1060 (non SC) version without issue. The SC just run cooler but hash the same as their non SC counterpart. So my normal hashrates on my existing rigs is 23MH/s and I am quite pleased with that.

I did the very few bios updates on my Asus Z270A motherboard and slapped a pre-built nvOC USB Stick in ...away she went. However this is where it got bad. I was only getting about 18MH/s with the same exact OC ratings as my other rigs. I was getting lag and ERRORS as well. So OK ...thought maybe I have a bad riser card. I start disconnecting and removing everything to start with the first card only. Just 1 card in the first x16 slot closest to the CPU as it should be. Same thing.

Still getting 18MH/s and some hanging. So I change that riser card and cable out completely. Still the same thing. I reduce the OC to 0/0 and my MH/s drops to about 15MH/s now. But the system seems to be stable.

I'm really scratching my head on this guys. I futzed with this for over 3 hours last night trying all sorts of things. I'm starting to wonder if the Nvidia driver install doesn't update the bios on the video cards somehow. So the fact that the driver was already installed on this image, the cards never got "flashed"? My other rigs were part of windows builds from the ground up and cards were in the rig when I updated the video drivers. So if my theory is correct those GPU's got flashed at that time and hence they are fine with nvOC0018.

But this new rig only ever booted into a fully built nvOC0018. -Anyone run into this themselves? -I have another motherboard so I'm going to try that on the off-chance that I have a bad motherboard somehow? Help and suggestions welcome. Other similar experiences would be great.

I don't think nvidia automatically updates bios firmware.  This would cause a ton of GPUs to be bricked, by users losing power / hard shutting down their computers while the bios updated.

Most likely you have lost the silicon lottery this time around:

The earlier GPUs most likely have better memory than the new ones.  I would guess the new ones have micron memory; and thus due to the combination of these GPUs having only 3gb and significantly worse memory they hash significantly lower.

You can see if the GPUs are of a different build model by using:

Code:

sudo lspci -v

on one of your older rigs and then the new one and comparing.

[sertix_T]

is not launching teamviewer please let me know. 
 

Yes, it works! And I'm an old man blind! Did not notice this setting! Went the other way! I do not know much English and worked too long under Windows...

[DJ ACK]

Not really v0018 related.  However, interesting to learn.  Received a batch of Gigabyte 1050Ti 1506 Boost Clock edition cards from Amazon last week.  Installed them in a rig and they hashed at an insanely low rate (single digits).  I swapped out risers, swapped cards between rigs, and they just would not hash.  You can tell these cards have issues because the DAG file % complete lags way behind the other cards during the DAG file build.  Running the card as a stand alone the DAG file builds quickly and the card hashes fine.  The minute you add it with another card the hash rate tanks.  Even with the same manufactured batch (serial number off by a couple digits).  After comparing the serial number to the 48 other Gigabyte 1050Ti cards I have, I noticed that the serial number is a very low/early edition number compared to all the rest of my cards.  My hunch is that these cards were sitting in a warehouse corner for years and they were a failed production batch with crap memory.  Sent them back to Amazon as defective.  

Anyone else had crap card inventory show up since May/June time frame?  

[fogcity]

Hey there --

I'm using v0018 with 6 gtx 1070s and an MSI Z-270A PRO to mine eth and all is working just fine.

I've searched the forum but can't seem to find an answer to what is probably a simple question.

Where do I assign my worker email address for my pool?  I'm using genoil (not Claymore) and nanopool. Perhaps it should be in the ETH_EXTENTION_ARGUMENT?  I would really appreciate it someone could tell me where it goes and provide me an example of how to do so.

Regards!!!

[alko67bi]

I have NV 1060. How I can change Performance Level from 2 to 3 in Nvidia X server settings?

[fullzero]

Hey there --

I'm using v0018 with 6 gtx 1070s and an MSI Z-270A PRO to mine eth and all is working just fine.

I've searched the forum but can't seem to find an answer to what is probably a simple question.

Where do I assign my worker email address for my pool?  I'm using genoil (not Claymore) and nanopool. Perhaps it should be in the ETH_EXTENTION_ARGUMENT?  I would really appreciate it someone could tell me where it goes and provide me an example of how to do so.

Regards!!!

For nanopool:

append / followed by your email address to the end of the worker; for example if my worker is nvOC and my email is bob@aol.com, I would use:

Code:

ETH_WORKER="nvOC/bob@aol.com"

[fullzero]

I have NV 1060. How I can change Performance Level from 2 to 3 in Nvidia X server settings?

in 1bash set:

Code:

GPUPowerMizerMode_Adjust="YES"

GPUPowerMizerMode=3

or open a new guake tab and enter:

Code:

sudo nvidia-settings -a [gpu:0]/GPUPowerMizerMode=3

changing the number in (gpu:0) for the GPU you are adjusting.

[fogcity]

Hey there --

I'm using v0018 with 6 gtx 1070s and an MSI Z-270A PRO to mine eth and all is working just fine.

I've searched the forum but can't seem to find an answer to what is probably a simple question.

Where do I assign my worker email address for my pool?  I'm using genoil (not Claymore) and nanopool. Perhaps it should be in the ETH_EXTENTION_ARGUMENT?  I would really appreciate it someone could tell me where it goes and provide me an example of how to do so.

Regards!!!

For nanopool:

append / followed by your email address to the end of the worker; for example if my worker is nvOC and my email is bob@aol.com, I would use:

Code:

ETH_WORKER="nvOC/bob@aol.com"

Full zero --

Thanks for the prompt reply!

So if I understand correctly, and if my email is bob@aol.com, I need to go into my 1bash file to where it's collecting my eth info (right beneath where you choose to use genoil or claymore) and replace the line that says:

     ETH_WORKER="nv$IP_AS_WORKER"

with

     ETH_WORKER="nv$IP_AS_WORKER/bob@aol.com"

Is that correct?

Thanks in advance for the help-- keep up the great work !!!

[DJ ACK]

Witnessed an odd issue with v0018 today.  All 8 of my 1050Tis only report ~13 MH/s.   Thought it was risers and swapped a couple out, no change.  Re-imaged the SSD and upon initial boot up, everything was fine, reporting 14.7 MH/s.  As soon as I rebooted it dropped the hash back down to 13 MH/s.  Swapped out cards and booted with just a single card same result.   Re-imaged again, same result.  Any idea what would cause this?  

I am running ASUS Z270 Prime-A boards with Gigabyte 1050Ti Boost Clock 1506 cards.  I don't think it is an ETH difficulty issue as my other rigs have the same configuration and I am not seeing the same issue.  My power is set at 60watts, temp settings at 60, my fan setting 50, core OC is 0 and mem OC is 1450.  I changed around power and mem settings, but no difference.

Could one of the modules be adjusting this to match one of the above variables?  My cards never get hot enough for the fan to go above 50.

Autotemp could be lowering the powerlimit; but only after your fans go to max.  If they don't go above 50% then that is unlikely.  The current powerlimit is displayed by the autotemp readout, so you can verify if it has changed when this is the case.

If it has been; I would raise your temp target to 70.

Watchdog only restarts 1bash or the rig; it shouldn't make an OC changes.

What kind of risers are you using? Are you powering them direct with Pcie 6pin?  If not this may be the problem.

Also you can probably get the same MH/s with the minimum powerlimit and -100 or -200 cc.

Well amazing.. that was it.. bumped the temp target up to 70, dropped the cc down to -200 and I found my missing hash. Now to tweak my other rigs.  Looks like you help me find another 65 MH/s for my entire setup.  Thank you very much.

That one rig has mixed molex and 6 pin type risers.  I will change out the molex when my new stock of risers comes in.

[rayd89]

Thanks for your effort FullZero love your work.

I tried your NVOC on my 13 card 1070 rig, but an into a few issues.

- I couldn't get all 13 to be recognised. claymore continues to report only 6 GPUs (mobo is ASROCK H110 BTC)
- I tried to set powerlimit both global and individual to 105W, and it only holds the 105W limit for about 3-5 seconds, after that it quickly creeps up to 125W and holds at 125W. I have tried with the maximus script on and off no difference.

Anyone have any issues like this?

How are you powering this rig?  Have you joined the PSUs (using an adapter to connect them) if you are using multiple ones?  If not the system not recognizing all your GPUs is most likely related to this.


With the powerlimit:

Most likely you aren't setting:  

# Note you MUST set individual powerlimits if using Maxximus007_AUTO_TEMPERATURE_CONTROL

INDIVIDUAL_POWERLIMIT_0=75

INDIVIDUAL_POWERLIMIT_1=75

INDIVIDUAL_POWERLIMIT_2=75

INDIVIDUAL_POWERLIMIT_3=75

INDIVIDUAL_POWERLIMIT_4=75

INDIVIDUAL_POWERLIMIT_5=75

INDIVIDUAL_POWERLIMIT_6=75

INDIVIDUAL_POWERLIMIT_7=75

INDIVIDUAL_POWERLIMIT_8=75

INDIVIDUAL_POWERLIMIT_9=75

INDIVIDUAL_POWERLIMIT_10=75

INDIVIDUAL_POWERLIMIT_11=75

INDIVIDUAL_POWERLIMIT_12=75

INDIVIDUAL_POWERLIMIT_13=75

Also I recommend updating your 1bash and the other files with the ones from the bux fix download on the Original Post.  I know you aren't using the newest 1bash because your individual powerlimit is setting to 125 and not 75.

Thanks for your swift reply!

I am connecting two PSU's together using a Add2PSU adaptor. Windows is able to see all 13 (but only hash with 8 )
Ubuntu is only seeing 6

I had changed all the individual settings to 105 before but i have not tried the latest 1bash file, i will give that a shot soon and return back with results! hopefully it fixes it

Thanks

[alko67bi]

I have NV 1060. How I can change Performance Level from 2 to 3 in Nvidia X server settings?

in 1bash set:

Code:

GPUPowerMizerMode_Adjust="YES"

GPUPowerMizerMode=3

or open a new guake tab and enter:

Code:

sudo nvidia-settings -a [gpu:0]/GPUPowerMizerMode=3

changing the number in (gpu:0) for the GPU you are adjusting.

"Valid values for 'GPUPowerMizerMode' are: 0, 1 and 2."
But in Nvidia X server settings displayed 0, 1, 2 and 3