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

[fullzero]

P106-100 BOUNTY

The person who will be able to unlock the overclock of my 13x P106 Rig (on the ASRock H110 BTC) with nvOC will get

1 ETH

I only got pure P106-rigs and no non-mining cards mixtures.

PM me and I will give you access to one of my Rigs.

Thanks!

I'm ready to make a donation too, if the issue with P106 cards is finally solved, but it's been so long already ...

Download the pure P106-100 1bash for headless SSH operation from the link on the OP; replace the 1 bash on your rig with it.  

Add your pool / addresses / workername to the 1bash.

Note: for this version don't use:

Maxximus007_AUTO_TEMPERATURE_CONTROL

or

IAmNotAJeep_and_Maxximus007_WATCHDOG

ensure they are both set to "NO"

Run the mining process; it should not OC at this time.  This is expected; it will alter the xorg.conf as needed.  

Note the Rig IP; write it down.

If you are not already running fully headless; ensure that you reboot: disconnecting any monitor from integrated graphics on the mobo before the rig reboots.

With your rig IP ssh into the rig after it boots ( see guide on the OP for more information on how to do this.  If from a linux system use the cmd from terminal:

Code:

ssh m1@your_rig_ip_here

you will be prompted

enter:

Code:

yes

the password is:

Code:

miner1

once you are logged in via SSH; enter:

Code:

screen -ls

if there is already a screen named miner use the cmd:

Code:

screen -r miner

to reconnect to the mining process and ignore the rest of this guide


if there is not; enter the cmd:

Code:

bash 1bash

to launch the mining process

once you see the message:

process in screen miner; attach with: screen -r miner

hit

Code:

ctrl + c

then enter:

Code:

screen -r miner

If you have problems with this; let me know.  I can't test this directly as I don't have these GPUs; but this should work unless I made a typo in the 1bash.


Also; you can edit the 1bash via SSH with the cmd:

Code:

nano 1bash

note this is a visual editor; again see the SSH guide for more info on nano.

[fullzero]

Your photo link doesn't work.

Whoops sorry about that, here is the link! http://i999.photobucket.com/albums/af112/Ben_klink/E411BAAB-938C-42A3-BDE6-0B6B5610CF6A_zpskweq0qgp.jpg

Thanks!

This is still broken; I recommend using a different service like: https://postimages.org/

Sweet fancy Moses, hopefully this works lol.
https://postimg.org/image/h4z1mpgf1/
https://s30.postimg.org/aeikd9t9d/IMG_3303.jpg

I'll try 2 links from postimg lol

I'm guessing this is a 1080ti rig?

I haven't seen this error before (which is rare).  What are the components that comprise your rig?

[fullzero]

Hi, i managed to connect 13*p106-100 gpu-z with no display output but when i log on via teamviewer the resolution is too small to do anything, could you fix this so that the resolution is normal ? Then i can do everything easily and test to my will:)

Edit: i get this in restart log :
Sun Aug 20 18:10:35 CEST 2017 - Utilization is too low: reviving did not work so restarting system in 10 seconds

Sun Aug 20 18:13:03 CEST 2017 - Starting miner restart script.

what does it mean

You would have to use a custom edid to increase the teamviewer resolution without a display.   It is not worth your time to do this; the easier way to test this is to ensure 1bash is configured to use SSH and REMOTE; then SSH into the rig and run commands via console.  I will most likely connect to lards rig later today and try this out.  I expect that all the GPUs will run as expected via console (nvoc isn't configured to use console mode, but you can manually start mining by launching 1bash or 2unix manually); the OC commands are also different from console.

ok thank you i will check.

can you tell me about the second part of the question ? the Rig or Program restarts, and in 4restart file i found this :

Sun Aug 20 18:10:35 CEST 2017 - Utilization is too low: reviving did not work so restarting system in 10 seconds

Sun Aug 20 18:13:03 CEST 2017 - Starting miner restart script.

what does it mean ??

That from WATCHDOG, scrypt check your GPU volatily, if your GPU get stuck scrypt detect it and relaunch mining process. Cause when one GPU crash all GPU crash. Is like a auto reboot if something working wrong.  

Bibi187 is correct this is from the watchdog.  I recommend updating to the newest one (the purple download link at the top of the OP; it fixes a number of problems.

[fullzero]

Can you please make step by step guide? I think it will help a lot of people, Thanks

Sure, will try my best.
First check to see if you have swap enabled or not by free command:
Then:
Open Gparted, it will ask for root password, Locate your drive, you will see a 16gb used space and a big not used at the end,
Right click on the unused partition and create new partition, Type : Swap make the size you want ( 1Gb to ...) and move it to the end of drive.  Apply.
Then right clcik on the primary 16gb partition and resize/move , resize it to the desired (better to give it all). Apply
Now right click on the swap partition and get the info, copy the UUID
open /etc/fstab with

Code:

gksudo gedit /etc/fstab

You will see a line which refers to a swap partition during installation ...
Some thing similar to this :

Code:

# swap was on /dev/sda5 during installation
UUID=cdba7b01-5ae6-4104-9a6e-f723b8bd87ac none            swap    sw              0       0

Now change the UUID with the one you copied from newly made swap partition.
save and close gedit.
now in your  terminal type :

Code:

sudo swapon --all

It will read your fstab and enable the swap partition.
check it with free command in  terminal

Code:

#free
              total        used        free      shared  buff/cache   available
Mem:        8171388     3020388     2637404      142044     2513596     4647472
Swap:       8123388           0     8123388

reboot and it should be all good

Thanks for making a guide. 

[Thagodeus]

I'm guessing this is a 1080ti rig?

I haven't seen this error before (which is rare).  What are the components that comprise your rig?

So that specific rig is gigabyte Z270p-d3 mobo, 4 gb ballistix ram, 32 gb lexar usb, intel g4400 processor, 2 gigabyte gtx 1080ti and 1 1060 mini, and gold 750 power supply. nvOC v17, only changes made are to powerlimits, 1080's at 180w and 1060 at 125w (my buddy had me do that, I don't know much about setting them up for efficiency)

Reimaged multiple times and every time it tells me the error about the power limit and persistence mode, and always throws the teamviewer error. Only once has it actually kicked the power limit and just ran up to 250 on its own

[fullzero]

Wow. Thank you dbolivar!

The slow boot time has always been my only issue with nvOC. Especially when I've got a sick riser that I'm hunting for. I commented out the swap line in /etc/fstab and BAM! It was like a rocket ship booting up.

SO loving this OS now. Even more than before! Thank you again FullZero for this awesome OS.

Great!! But don't thank me for identifying this invalid entry in /etc/fstab, it was the merit of another user, as I mentioned, but I forgot his username! Nevertheless, Fullzero is aware of this, and said it will be fixed in v19.

You can do this on any nvOC or rxOC rig by entering the following in the guake terminal:

Code:

gksu gedit /etc/fstab

then commenting out this line by appending a # to the front of it changing:

Code:

UUID=cdba7b01-5ae6-4104-9a6e-f723b8bd87ac none            swap    sw              0       0

to:

Code:

#UUID=cdba7b01-5ae6-4104-9a6e-f723b8bd87ac none            swap    sw              0       0

then close the gedit and reboot.

I applied this change to the v0019_rc a long time ago when osnwt brought it to my attention:  https://bitcointalk.org/index.php?topic=1854250.msg20492062#msg20492062

[fullzero]

I'm guessing this is a 1080ti rig?

I haven't seen this error before (which is rare).  What are the components that comprise your rig?

So that specific rig is gigabyte Z270p-d3 mobo, 4 gb ballistix ram, 32 gb lexar usb, intel g4400 processor, 2 gigabyte gtx 1080ti and 1 1060 mini, and gold 750 power supply. nvOC v17, only changes made are to powerlimits, 1080's at 180w and 1060 at 125w (my buddy had me do that, I don't know much about setting them up for efficiency)

Reimaged multiple times and every time it tells me the error about the power limit and persistence mode, and always throws the teamviewer error. Only once has it actually kicked the power limit and just ran up to 250 on its own

My guess is the indexing of the GPUs is different than expected so a 1060 is trying to apply a 1080ti powerlimit and a 1080ti is trying to apply a 1060 powerlimit.

To test this set:

Code:

INDIVIDUAL_POWERLIMIT="NO"

and

Code:

POWERLIMIT="NO"  

then save 1bash and restart the mining process.

Let me know what happens.

[papampi]

Feature Request:
1-
Add IP address to hostname at first boot to setup individual names for each rig.
So rigs names will become : m1-desktop-101 , m1-desktop-102 ....
I know we can edit our hostnames in /etc/hosts and /etc/hostanme.
It just make nvOC looks better at first start  

2-
Remind user to change the m1 password at first boot.
Its not safe.

[damNmad]

Any one had this sort of issue while using SALFTER_NICEHASH_PROFIT_SWITCHING ??

Code:

__lbry_CORE_OVERCLOCK: 100
lbry_MEMORY_OVERCLOCK: 1100

Traceback (most recent call last):
  File "/home/m1/switch", line 210, in <module>
    exchrate=float(json.loads(urllib.urlopen("https://api.coinbase.com/v2/exchange-rates?currency=BTC").read())["data"]["rates"][currency])
  File "/usr/lib/python2.7/urllib.py", line 87, in urlopen
    return opener.open(url)
  File "/usr/lib/python2.7/urllib.py", line 213, in open
    return getattr(self, name)(url)
  File "/usr/lib/python2.7/urllib.py", line 443, in open_https
    h.endheaders(data)
  File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 897, in _send_output
    self.send(msg)
  File "/usr/lib/python2.7/httplib.py", line 859, in send
    self.connect()
  File "/usr/lib/python2.7/httplib.py", line 1278, in connect
    server_hostname=server_hostname)
  File "/usr/lib/python2.7/ssl.py", line 353, in wrap_socket
    _context=self)
  File "/usr/lib/python2.7/ssl.py", line 601, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 830, in do_handshake
    self._sslobj.do_handshake()
IOError: [Errno socket error] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)

[Bibi187]

Any one had this sort of issue while using SALFTER_NICEHASH_PROFIT_SWITCHING ??

Code:

__lbry_CORE_OVERCLOCK: 100
lbry_MEMORY_OVERCLOCK: 1100

Traceback (most recent call last):
  File "/home/m1/switch", line 210, in <module>
    exchrate=float(json.loads(urllib.urlopen("https://api.coinbase.com/v2/exchange-rates?currency=BTC").read())["data"]["rates"][currency])
  File "/usr/lib/python2.7/urllib.py", line 87, in urlopen
    return opener.open(url)
  File "/usr/lib/python2.7/urllib.py", line 213, in open
    return getattr(self, name)(url)
  File "/usr/lib/python2.7/urllib.py", line 443, in open_https
    h.endheaders(data)
  File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 897, in _send_output
    self.send(msg)
  File "/usr/lib/python2.7/httplib.py", line 859, in send
    self.connect()
  File "/usr/lib/python2.7/httplib.py", line 1278, in connect
    server_hostname=server_hostname)
  File "/usr/lib/python2.7/ssl.py", line 353, in wrap_socket
    _context=self)
  File "/usr/lib/python2.7/ssl.py", line 601, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 830, in do_handshake
    self._sslobj.do_handshake()
IOError: [Errno socket error] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)

Can u check date and hours on your linux / network ?
Failed certificate verify error came from this habitually

[damNmad]

Any one had this sort of issue while using SALFTER_NICEHASH_PROFIT_SWITCHING ??

Code:

__lbry_CORE_OVERCLOCK: 100
lbry_MEMORY_OVERCLOCK: 1100

Traceback (most recent call last):
  File "/home/m1/switch", line 210, in <module>
    exchrate=float(json.loads(urllib.urlopen("https://api.coinbase.com/v2/exchange-rates?currency=BTC").read())["data"]["rates"][currency])
  File "/usr/lib/python2.7/urllib.py", line 87, in urlopen
    return opener.open(url)
  File "/usr/lib/python2.7/urllib.py", line 213, in open
    return getattr(self, name)(url)
  File "/usr/lib/python2.7/urllib.py", line 443, in open_https
    h.endheaders(data)
  File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 897, in _send_output
    self.send(msg)
  File "/usr/lib/python2.7/httplib.py", line 859, in send
    self.connect()
  File "/usr/lib/python2.7/httplib.py", line 1278, in connect
    server_hostname=server_hostname)
  File "/usr/lib/python2.7/ssl.py", line 353, in wrap_socket
    _context=self)
  File "/usr/lib/python2.7/ssl.py", line 601, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 830, in do_handshake
    self._sslobj.do_handshake()
IOError: [Errno socket error] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)

Can u check date and hours on your linux / network ?
Failed certificate verify error came from this habitually

I've changed the time zone long back to my local time (GMT London), the profit switching was working even after the time zone change! Haven't touched/changed anything related to profit switching!!

[car1999]

Feature Request:
1-
Add IP address to hostname at first boot to setup individual names for each rig.
So rigs names will become : m1-desktop-101 , m1-desktop-102 ....
I know we can edit our hostnames in /etc/hosts and /etc/hostanme.
It just make nvOC looks better at first start  

2-
Remind user to change the m1 password at first boot.
Its not safe.

for 2, adding some reminder texts is fine, but don't force user to change password.

[damNmad]

Any one had this sort of issue while using SALFTER_NICEHASH_PROFIT_SWITCHING ??

Code:

__lbry_CORE_OVERCLOCK: 100
lbry_MEMORY_OVERCLOCK: 1100

Traceback (most recent call last):
  File "/home/m1/switch", line 210, in <module>
    exchrate=float(json.loads(urllib.urlopen("https://api.coinbase.com/v2/exchange-rates?currency=BTC").read())["data"]["rates"][currency])
  File "/usr/lib/python2.7/urllib.py", line 87, in urlopen
    return opener.open(url)
  File "/usr/lib/python2.7/urllib.py", line 213, in open
    return getattr(self, name)(url)
  File "/usr/lib/python2.7/urllib.py", line 443, in open_https
    h.endheaders(data)
  File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 897, in _send_output
    self.send(msg)
  File "/usr/lib/python2.7/httplib.py", line 859, in send
    self.connect()
  File "/usr/lib/python2.7/httplib.py", line 1278, in connect
    server_hostname=server_hostname)
  File "/usr/lib/python2.7/ssl.py", line 353, in wrap_socket
    _context=self)
  File "/usr/lib/python2.7/ssl.py", line 601, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 830, in do_handshake
    self._sslobj.do_handshake()
IOError: [Errno socket error] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)

Can u check date and hours on your linux / network ?
Failed certificate verify error came from this habitually

I've changed the time zone long back to my local time (GMT London), the profit switching was working even after the time zone change! Haven't touched/changed anything related to profit switching!!

UPDATE :

Now I'm not getting the above error but get different issue; main terminal says mining starts in guake terminal; but on guake 'There is no screen to be resumed matching miner' error appears.

Will compare it with latest 1bash and see if there are any differences.

EDIT :

Sorry, I've overlooked, I'm still getting the above error and on guake getting this 'There is no screen to be resumed matching miner'

[cryptolover1981]

P106-100 BOUNTY

The person who will be able to unlock the overclock of my 13x P106 Rig (on the ASRock H110 BTC) with nvOC will get

1 ETH

I only got pure P106-rigs and no non-mining cards mixtures.

PM me and I will give you access to one of my Rigs.

Thanks!

I'm ready to make a donation too, if the issue with P106 cards is finally solved, but it's been so long already ...

Download the pure P106-100 1bash for headless SSH operation from the link on the OP; replace the 1 bash on your rig with it.  

Add your pool / addresses / workername to the 1bash.

Note: for this version don't use:

Maxximus007_AUTO_TEMPERATURE_CONTROL

or

IAmNotAJeep_and_Maxximus007_WATCHDOG

ensure they are both set to "NO"

Run the mining process; it should not OC at this time.  This is expected; it will alter the xorg.conf as needed.  

Note the Rig IP; write it down.

If you are not already running fully headless; ensure that you reboot: disconnecting any monitor from integrated graphics on the mobo before the rig reboots.

With your rig IP ssh into the rig after it boots ( see guide on the OP for more information on how to do this.  If from a linux system use the cmd from terminal:

Code:

ssh m1@your_rig_ip_here

you will be prompted

enter:

Code:

yes

the password is:

Code:

miner1

once you are logged in via SSH; enter:

Code:

screen -ls

if there is already a screen named miner use the cmd:

Code:

screen -r miner

to reconnect to the mining process and ignore the rest of this guide


if there is not; enter the cmd:

Code:

bash 1bash

to launch the mining process

once you see the message:

process in screen miner; attach with: screen -r miner

hit

Code:

ctrl + c

then enter:

Code:

screen -r miner

If you have problems with this; let me know.  I can't test this directly as I don't have these GPUs; but this should work unless I made a typo in the 1bash.


Also; you can edit the 1bash via SSH with the cmd:

Code:

nano 1bash

note this is a visual editor; again see the SSH guide for more info on nano.

Thank you so much for the quick respond. I'm getting GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered in claymore and CUDA failure 77: an illegal memory access was encountered ; in Genoil, after a few seconds of mining.

Also in ZEC it says CUDA: Device: 3 Thread exited with code: 77
or CUDA: Device: 3 Thread exited with code: 64

Am I doing something wrong?


I will make a donation for your lovely p106 1bash.

best regards

[dbolivar]

Thank you so much for the quick respond. I'm getting GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered in claymore and CUDA failure 77: an illegal memory access was encountered ; in Genoil, after a few seconds of mining.

Also in ZEC it says CUDA: Device: 3 Thread exited with code: 77
or CUDA: Device: 3 Thread exited with code: 64

Try a lower memory overclock offset: I get these errors when I overclock too much. To confirm, check the output of "dmesg" in the terminal; if you get messages like these:

[139035.343237] NVRM: Xid (PCI:0000:02:00): 31, Ch 0000001b, engmask 00000101, intr 10000000

Most probably that's the issue. If you get these messages but with a different Xid (in this example it's 31), report here, as each code has a different meaning.

[Bibi187]

For people want to have log in direct terminal with perma update a simply command do the job and let u know which GPU fail and why
Open a terminal and type

tail -f /var/log/kern.log

[lards]

Hey everyone.

As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours )  , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.

Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.

Can you advise on what should I do in that case?

[salfter]

It appears the site previously used extremely limits bandwidth on large downloads

nvOC 17 high speed download below
https://www.mediafire.com/download/oi84ue7e6z9epn9

...and this one blocks adblockers. 

I'm uploading a copy I'd originally downloaded from Google Drive (or was it Mega?) to my VPS.  I'll post a link once it's up.  SHA256 hash on the file is d11929368d186acf73651be1b9d90234cfe6ef8a097eff56668dee4cbbe69e8c, as announced here.

[ivoldemar]

P106-100 BOUNTY

The person who will be able to unlock the overclock of my 13x P106 Rig (on the ASRock H110 BTC) with nvOC will get

1 ETH

I only got pure P106-rigs and no non-mining cards mixtures.

PM me and I will give you access to one of my Rigs.

Thanks!

I'm ready to make a donation too, if the issue with P106 cards is finally solved, but it's been so long already ...

Download the pure P106-100 1bash for headless SSH operation from the link on the OP; replace the 1 bash on your rig with it.  

Add your pool / addresses / workername to the 1bash.

Note: for this version don't use:

Maxximus007_AUTO_TEMPERATURE_CONTROL

or

IAmNotAJeep_and_Maxximus007_WATCHDOG

ensure they are both set to "NO"

Run the mining process; it should not OC at this time.  This is expected; it will alter the xorg.conf as needed.  

Note the Rig IP; write it down.

If you are not already running fully headless; ensure that you reboot: disconnecting any monitor from integrated graphics on the mobo before the rig reboots.

With your rig IP ssh into the rig after it boots ( see guide on the OP for more information on how to do this.  If from a linux system use the cmd from terminal:

Code:

ssh m1@your_rig_ip_here

you will be prompted

enter:

Code:

yes

the password is:

Code:

miner1

once you are logged in via SSH; enter:

Code:

screen -ls

if there is already a screen named miner use the cmd:

Code:

screen -r miner

to reconnect to the mining process and ignore the rest of this guide


if there is not; enter the cmd:

Code:

bash 1bash

to launch the mining process

once you see the message:

process in screen miner; attach with: screen -r miner

hit

Code:

ctrl + c

then enter:

Code:

screen -r miner

If you have problems with this; let me know.  I can't test this directly as I don't have these GPUs; but this should work unless I made a typo in the 1bash.


Also; you can edit the 1bash via SSH with the cmd:

Code:

nano 1bash

note this is a visual editor; again see the SSH guide for more info on nano.

http://prntscr.com/gc8g0n / http://prntscr.com/gc8agx ((

[BigSmurf]

Hey everyone.

As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours )  , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.

Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.

Can you advise on what should I do in that case?

Hi all,
I can also confirm that all 13*P106-100 are working.
Dual mining ETH/PASC at CC 0, MC 1300, Powerlimit 115, i get eth 307/pascal 3070. 6 hours stable.