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

[fullzero]

Hello,

I have an issue on version 0015:
I have severals rigs on Asus Z270 Prime-P but I do not manage to boot nvOC on a Asus Z270 Prime-A:
I loaded default bios, used the setting on the first page, plugged 8 cards using a m2 adaptater --> The bios POST, so everything seems to be OK. Then, I have a black screen as is should start loading the OS, the USB key seems to be accessed as it gets hot, but the black screen never ends. I waited 5 mins, nothing: only a black screen.
I tried to redo an other USB key without luck.
Do you have any idea what is blocking the boot?

Thanks

I have same issue with 0.14, 0.15 and 0.16. I am waiting 15-30 min with black sxreen, before system boot on. I have no idea what to do. I have different motherbords, usb flashes but time for boot on is so long

With V0016 boot time should be (very) much shorter. Please do a BIOS reset (jumper on MB). After that set the recommended BIOS settings, and boot with more than one card (on risers), monitor on the first GPU. Hope it helps! It's one of the motherboards I have on my shortlist for my next rigs.

I did BIOS reset with my ASUS H270, set up just 4G enable, but nothing changed, i can;t load mvOS. but with old MB i have this USB works very fast. I have no idea why its slow with new ASUS H270 and MSI Z270 MB

Did you update the bios?

with this motherboard it can be done by connecting an ethernet cable and entering the EZ Flash 3 Utility.  

Select DHCP and download then install the update

[1714316942]

1714316942

[1714316942]

1714316942

[1714316942]

1714316942

[1714316942]

1714316942

[fullzero]

Very nice updates in v0016 fullzero.  

Other than that, manual GPUFANSPEED doesn't work on my z270-a prime/evga 1080 Ti sc black.

What does the top of the mining process display where it should be showing fan control state and fan speed messages?

[fullzero]

I will respond to all posts later today: sorry if I have taken a longtime to respond.  I will make sure I respond to everyone at some point tonight.

v0016 is out see the OP for a link.

I didn't implement all requested changes, but I think I got most of them.  If I missed yours with v0016 I will get to it soon.

I have only tested this build on 8 rigs; so let me know if you find any bugs.  

Change Log:
v0016
  auto repair xorg: fixes single GPU not OCing bug (will auto detect / repair / reboot if using a single GPU or the xorg file has otherwise been damaged)
  implemented Maxximus007 suggestion to enable expect-less oneBash
  Thanks Maxximus007  Smiley
  powerlimit not setting bug is fixed (even for very slow USB keys)
  added Teamviewer with oneBash YES / NO switch to enable / disable it
  added openssh-server switch in oneBash YES / NO switch to enable / disable it
  added Desktop Sharing RDP program (enable / setup with GUI on the taskbar)
  added ifconfig output to the top of mining process (easy to get rig IP)
  added EWBF v3.4
  added Claymore v9.5
  added EWBF and Claymore version selectors to oneBash
  added EXTENTION_ARGUMENTS for each Ethash COIN (to add additional Claymore parameters)
  increased Claymore stability
  reduced boot time
  will now work with slow USB keys
    VTC COIN selection with VTC or BTC payout
    ZEN COIN selection
    NICE COIN selection

keep getting low disk space
is something logging now?

There should be no logging other than the standard Ubuntu syslog; which should take up almost no space.

In v0016; to make the image smaller: I reduced the size of the primary partition by almost 1gb, which also reduced the free space available to the system. 

It is possible I removed too much, and should enlarge the partition for the next version.  Let me know if anything other than low disk messages happen; or if it appears performance is degraded in anyway as a result.

[fullzero]

Hi All,

I have decided to give nvOC a go, I am using an older Gigabyte GA-EX58-UD4P (Socket LGA1366) board and an i7 920 CPU.  I have two EVGA GTX 1080ti on risers in both PCI-E x16 slots.
I am able to boot fine but things just are not stable, I can run for about 15 hours but later GPU0 drops to about 150-170w and SOLs are suffering, I can reboot and get it working but it seems to happen again.

I have no idea if any BIOS changes need to be made to get this running stable or not, does anyone have any idea what I can try?

Also if I kill the mining process and make changes to the onebash config it doesn't seem to accept the changes, more specially the fan speed.  I attempt to launch the miner again and get the below error but the process does start;


Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

When the mining process starts do you see OC messages like this?

https://ip.bitcointalk.org/?u=https%3A%2F%2Fs13.postimg.org%2Fq08huqnyv%2FIMG_0270.jpg%26t%3D577%26c%3Dyq0szP4ICxv47w&t=577&c=q_tbQ_FaeljjYQ

If you don't:

At any point did you boot with the monitor connected to the motherboard?

Did you at anytime boot with only one GPU attached?

If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )

then follow this process:

https://bitcointalk.org/index.php?topic=1854250.msg19449945#msg19449945

I only booted with a monitor connected the first time, now it is completely headless.
Yes I might have booted with only one GPU attached at one point.
Thank you I will follow that process.  If I re-image the USB key and boot completely headless should I be seeing the OC messages via SSH as well?

With v0015 you would have to enable openssh server before you could SSH in.  You would also have to be able to know the rigs IP; which can be done in several ways.

With v0016 you can enable openssh server in oneBash, I would recommending trying it and seeing if it solves the problem.

I have now also tested with v0016, the mining process starts fine with all OC settings when viewing directly on the rig.  However I am still getting the error via SSH when trying to start.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

What type of OS is the client computer; and what are the IPs of the client and rig?

Windows 10 running putty, Rig: 192.168.1.19 Client: 192.168.1.6

So when you enter

m1@192.168.1.19   

using port 22

with SSH selected

and click open it gives you the error above?

Sorry let me try and clear some things up.  I am able to SSH into the rig just fine but when executing the miner via ssh, this is when i am getting the error, so clock settings, fan speed and power limits are not being set but the mining process still starts.

I also really appreciate your support and rapid response.

Are you killing the existing mining process before launching another via SSH?

Also; when you are launching the mining process via SSH are you using the cmd:

Code:

bash '/media/m1/1263-A96E/oneBash'

I am SSHing and executing the following commands.

ps aux | grep gnome-terminal - finding the gnome-server PID
kill PID
screen -S rig1
bash '/media/m1/1263-A96E/oneBash'

Just before the miner starts I see the above error in place of the "attribute" commands but the mining process still starts.

after you have SSHed in enter the cmd:

Code:

echo $DISPLAY

and tell me what it outputs

That does not output anything at all.

Ok, tomorrow I will try to replicate this error; and see if I can figure out what is happening.  My guess is X11 is having a problem trying to output graphically.

If you have a linux computer other than your rig and you SSH into the rig with it; does it have the same error?

[lbrasi]

Hi All,

I have decided to give nvOC a go, I am using an older Gigabyte GA-EX58-UD4P (Socket LGA1366) board and an i7 920 CPU.  I have two EVGA GTX 1080ti on risers in both PCI-E x16 slots.
I am able to boot fine but things just are not stable, I can run for about 15 hours but later GPU0 drops to about 150-170w and SOLs are suffering, I can reboot and get it working but it seems to happen again.

I have no idea if any BIOS changes need to be made to get this running stable or not, does anyone have any idea what I can try?

Also if I kill the mining process and make changes to the onebash config it doesn't seem to accept the changes, more specially the fan speed.  I attempt to launch the miner again and get the below error but the process does start;


Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

When the mining process starts do you see OC messages like this?

https://ip.bitcointalk.org/?u=https%3A%2F%2Fs13.postimg.org%2Fq08huqnyv%2FIMG_0270.jpg%26t%3D577%26c%3Dyq0szP4ICxv47w&t=577&c=q_tbQ_FaeljjYQ

If you don't:

At any point did you boot with the monitor connected to the motherboard?

Did you at anytime boot with only one GPU attached?

If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )

then follow this process:

https://bitcointalk.org/index.php?topic=1854250.msg19449945#msg19449945

I only booted with a monitor connected the first time, now it is completely headless.
Yes I might have booted with only one GPU attached at one point.
Thank you I will follow that process.  If I re-image the USB key and boot completely headless should I be seeing the OC messages via SSH as well?

With v0015 you would have to enable openssh server before you could SSH in.  You would also have to be able to know the rigs IP; which can be done in several ways.

With v0016 you can enable openssh server in oneBash, I would recommending trying it and seeing if it solves the problem.

I have now also tested with v0016, the mining process starts fine with all OC settings when viewing directly on the rig.  However I am still getting the error via SSH when trying to start.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

What type of OS is the client computer; and what are the IPs of the client and rig?

Windows 10 running putty, Rig: 192.168.1.19 Client: 192.168.1.6

So when you enter

m1@192.168.1.19   

using port 22

with SSH selected

and click open it gives you the error above?

Sorry let me try and clear some things up.  I am able to SSH into the rig just fine but when executing the miner via ssh, this is when i am getting the error, so clock settings, fan speed and power limits are not being set but the mining process still starts.

I also really appreciate your support and rapid response.

Are you killing the existing mining process before launching another via SSH?

Also; when you are launching the mining process via SSH are you using the cmd:

Code:

bash '/media/m1/1263-A96E/oneBash'

I am SSHing and executing the following commands.

ps aux | grep gnome-terminal - finding the gnome-server PID
kill PID
screen -S rig1
bash '/media/m1/1263-A96E/oneBash'

Just before the miner starts I see the above error in place of the "attribute" commands but the mining process still starts.

after you have SSHed in enter the cmd:

Code:

echo $DISPLAY

and tell me what it outputs

That does not output anything at all.

Ok, tomorrow I will try to replicate this error; and see if I can figure out what is happening.  My guess is X11 is having a problem trying to output graphically.

If you have a linux computer other than your rig and you SSH into the rig with it; does it have the same error?

I tested from a linux VM I have and the same result

[Plumbus]

When I try to run lbry I get an error. Something to the effect of "980ti: invalid device function"

Works fine with ZEC and ZEN

[ijduncan]

Amazing work ont eh update.

Got it working with no issues but then received the following error.  Dont know what to make of it.


 DCR: Stratum - connecting to 'dcr.suprnova.cc' <217.182.138.167> port 3252
ETH: Stratum - Connected (eth.suprnova.cc:5000)
 DCR: Stratum - Connected (dcr.suprnova.cc:3252)
 DCR: Authorized
 DCR: 06/22/17-00:04:37 - New job from dcr.suprnova.cc:3252

Received unknown response: {"id":null,"method":"mining.notify","params":["3247","129656acf5804305816f3dc0b32b47077c8cf4b8724f181efc529a93e4c1385b","999803e4fef6e5c5edd9968b3e00398713ca6f8d7f24812ea49ebf8373f11e8d",true]}
GPU0 t=54C fan=0%, GPU1 t=52C fan=0%, GPU2 t=49C fan=0%
ETH: Job timeout, disconnect, retry in 20 sec...


anybody have any thoughts?

[Tasbi]

Version 0016 installed, I just tried teamviewer, PL is working good.
I tried with 9x gtx 1060 3gb mining ETHEREUM at 22.5 each with 880 watts on the wall. TOTAL 202 Mh/s

POWERLIMIT="YES"
POWERLIMIT_WATTS=84
__CORE_OVERCLOCK=100
MEMORY_OVERCLOCK=1400

Working temp 58C - 64C / fan at 75%

I had the issue of SSHing and executing bash '/media/m1/1263-A96E/oneBash',
it gave me this error,:

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.

but now that I have teamviewer then I don´t need that anymore...

thanks fullzero

[Maxximus007]

I will respond to all posts later today: sorry if I have taken a longtime to respond.  I will make sure I respond to everyone at some point tonight.

v0016 is out see the OP for a link.

I didn't implement all requested changes, but I think I got most of them.  If I missed yours with v0016 I will get to it soon.

I have only tested this build on 8 rigs; so let me know if you find any bugs.  

Change Log:
v0016
  auto repair xorg: fixes single GPU not OCing bug (will auto detect / repair / reboot if using a single GPU or the xorg file has otherwise been damaged)
  implemented Maxximus007 suggestion to enable expect-less oneBash
  Thanks Maxximus007  Smiley
  powerlimit not setting bug is fixed (even for very slow USB keys)
  added Teamviewer with oneBash YES / NO switch to enable / disable it
  added openssh-server switch in oneBash YES / NO switch to enable / disable it
  added Desktop Sharing RDP program (enable / setup with GUI on the taskbar)
  added ifconfig output to the top of mining process (easy to get rig IP)
  added EWBF v3.4
  added Claymore v9.5
  added EWBF and Claymore version selectors to oneBash
  added EXTENTION_ARGUMENTS for each Ethash COIN (to add additional Claymore parameters)
  increased Claymore stability
  reduced boot time
  will now work with slow USB keys
    VTC COIN selection with VTC or BTC payout
    ZEN COIN selection
    NICE COIN selection

keep getting low disk space
is something logging now?

There should be no logging other than the standard Ubuntu syslog; which should take up almost no space.

In v0016; to make the image smaller: I reduced the size of the primary partition by almost 1gb, which also reduced the free space available to the system. 

It is possible I removed too much, and should enlarge the partition for the next version.  Let me know if anything other than low disk messages happen; or if it appears performance is degraded in anyway as a result.

You might want to run sudo apt update, sudo apt upgrade, sudo apt autoremove. This will remove around 1.5 Gb obsolete files. Apt was complaining about a file in /lib/modules/4.4.0-65.generic/kernel/drivers/media/usb/hdpvr/hdpvr.ko. I removed that PID file by hand, and ran sudo apt autoremove again. Currently 3.3Gb free space, that should be plenty.
** disclaimer ** it worked for me, YMMV

[Maxximus007]

Hi All,

I have decided to give nvOC a go, I am using an older Gigabyte GA-EX58-UD4P (Socket LGA1366) board and an i7 920 CPU.  I have two EVGA GTX 1080ti on risers in both PCI-E x16 slots.
I am able to boot fine but things just are not stable, I can run for about 15 hours but later GPU0 drops to about 150-170w and SOLs are suffering, I can reboot and get it working but it seems to happen again.

I have no idea if any BIOS changes need to be made to get this running stable or not, does anyone have any idea what I can try?

Also if I kill the mining process and make changes to the onebash config it doesn't seem to accept the changes, more specially the fan speed.  I attempt to launch the miner again and get the below error but the process does start;


Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

When the mining process starts do you see OC messages like this?

https://ip.bitcointalk.org/?u=https%3A%2F%2Fs13.postimg.org%2Fq08huqnyv%2FIMG_0270.jpg%26t%3D577%26c%3Dyq0szP4ICxv47w&t=577&c=q_tbQ_FaeljjYQ

If you don't:

At any point did you boot with the monitor connected to the motherboard?

Did you at anytime boot with only one GPU attached?

If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )

then follow this process:

https://bitcointalk.org/index.php?topic=1854250.msg19449945#msg19449945

I only booted with a monitor connected the first time, now it is completely headless.
Yes I might have booted with only one GPU attached at one point.
Thank you I will follow that process.  If I re-image the USB key and boot completely headless should I be seeing the OC messages via SSH as well?

With v0015 you would have to enable openssh server before you could SSH in.  You would also have to be able to know the rigs IP; which can be done in several ways.

With v0016 you can enable openssh server in oneBash, I would recommending trying it and seeing if it solves the problem.

I have now also tested with v0016, the mining process starts fine with all OC settings when viewing directly on the rig.  However I am still getting the error via SSH when trying to start.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

What type of OS is the client computer; and what are the IPs of the client and rig?

Windows 10 running putty, Rig: 192.168.1.19 Client: 192.168.1.6

So when you enter

m1@192.168.1.19   

using port 22

with SSH selected

and click open it gives you the error above?

Sorry let me try and clear some things up.  I am able to SSH into the rig just fine but when executing the miner via ssh, this is when i am getting the error, so clock settings, fan speed and power limits are not being set but the mining process still starts.

I also really appreciate your support and rapid response.

Are you killing the existing mining process before launching another via SSH?

Also; when you are launching the mining process via SSH are you using the cmd:

Code:

bash '/media/m1/1263-A96E/oneBash'

I am SSHing and executing the following commands.

ps aux | grep gnome-terminal - finding the gnome-server PID
kill PID
screen -S rig1
bash '/media/m1/1263-A96E/oneBash'

Just before the miner starts I see the above error in place of the "attribute" commands but the mining process still starts.

after you have SSHed in enter the cmd:

Code:

echo $DISPLAY

and tell me what it outputs

That does not output anything at all.

Ok, tomorrow I will try to replicate this error; and see if I can figure out what is happening.  My guess is X11 is having a problem trying to output graphically.

If you have a linux computer other than your rig and you SSH into the rig with it; does it have the same error?

I tested from a linux VM I have and the same result

Confirming the issue, SSH into rig, kill gnome-terminal, bash '/media/m1/1263-A96E/oneBash'. Power limits are set, after that:

Code:

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

** EDIT** Have this with V0015 as well, but that image was updated with apt, unsure that has anything to do with it.

[rampage999]

Hi,

Good work.

However it takes several minutes to boot from my USB 3.0 stick?
The booting seems have some problem.

V16 changed name to amdOC?

[f00ch0w]

Any guide on how to update from v0015 to v0016? Or it's required to reimage again?

[Maxximus007]

Any guide on how to update from v0015 to v0016? Or it's required to reimage again?

ATM the upgrade path is reimage indeed. -> Save your current oneBash: you have to mix and match with the V0016 oneBash to mine on your own accounts again, with desired OC, power and fan speeds.

[cryptosharks]

Hey @fullzero,

I have encountered an issue with ccminer after a reboot:

error while loading shared libraries: libcudart.so.x: cannot open shared object file: No such file or directory

Also, I have found a solution:

http://www.cs.virginia.edu/~mwb7w/cuda_support/libcudart.html

The above has been proven to get ccminer to start without any issues.

Also, I've been testing the latest nvOC version on 5 mining rigs - so far all looking good.

Cheers,

[Nexillus]

Fullzero,

I want to say that ver16 is much more stable then ver15 and great work on it overall!

Thank you so much for putting this together, disseminating it it and all the hard work you do!

[car1999]

I've run nvOC 7 hours on a gtx1050ti x 7 rig, very stable, very easy, awesome project, thanks!

[pixelizedchaos]

Hello! sorry but somewhat of a noob. I am really interested in SSH'ing into my rig from external networks, I have used Team viewer, but with local SSH it seems a lot more reliable.

So essentially I have two questions:
1) When I am connected through SSH and let's say I want to restart the gnome terminal back on the miner instead of my computer what command do I use to restart the PID that I initially closed.
2) How would I go about setting up a remote server which I can ssh into remotely, without being in the local area network?

Any help is appreciated! Also absolutely love your work, plan on showcasing it in videos once I learn a bit more about it! Thanks so much!
(Ps. if anyone has used ASUS Dual Series 1070's and found the optimal OC for them please let me know!)

[fullzero]

When I try to run lbry I get an error. Something to the effect of "980ti: invalid device function"

Works fine with ZEC and ZEN

I removed a timeout before the cmd that adds the link at each boot to solve this problem.  i thought I would be ok with all USBs this way but it apparently still needs the timeout.

You can fix this permentely by opening the home directory and opening the 2unix file.  on the line above the line:

Code:

sudo ldconfig /usr/local/cuda/lib64

add:

Code:

sleep 10 

You can also open the guake terminal ( f12 )

and manually enter the cmd at any time (but this will only solve for the current boot):

Code:

sudo ldconfig /usr/local/cuda/lib64

If you download and replace your existing oneBash with the newest one From the link on the OP it should solve this problem as well.

[fullzero]

Hi All,

I have decided to give nvOC a go, I am using an older Gigabyte GA-EX58-UD4P (Socket LGA1366) board and an i7 920 CPU.  I have two EVGA GTX 1080ti on risers in both PCI-E x16 slots.
I am able to boot fine but things just are not stable, I can run for about 15 hours but later GPU0 drops to about 150-170w and SOLs are suffering, I can reboot and get it working but it seems to happen again.

I have no idea if any BIOS changes need to be made to get this running stable or not, does anyone have any idea what I can try?

Also if I kill the mining process and make changes to the onebash config it doesn't seem to accept the changes, more specially the fan speed.  I attempt to launch the miner again and get the below error but the process does start;


Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

When the mining process starts do you see OC messages like this?

https://ip.bitcointalk.org/?u=https%3A%2F%2Fs13.postimg.org%2Fq08huqnyv%2FIMG_0270.jpg%26t%3D577%26c%3Dyq0szP4ICxv47w&t=577&c=q_tbQ_FaeljjYQ

If you don't:

At any point did you boot with the monitor connected to the motherboard?

Did you at anytime boot with only one GPU attached?

If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )

then follow this process:

https://bitcointalk.org/index.php?topic=1854250.msg19449945#msg19449945

I only booted with a monitor connected the first time, now it is completely headless.
Yes I might have booted with only one GPU attached at one point.
Thank you I will follow that process.  If I re-image the USB key and boot completely headless should I be seeing the OC messages via SSH as well?

With v0015 you would have to enable openssh server before you could SSH in.  You would also have to be able to know the rigs IP; which can be done in several ways.

With v0016 you can enable openssh server in oneBash, I would recommending trying it and seeing if it solves the problem.

I have now also tested with v0016, the mining process starts fine with all OC settings when viewing directly on the rig.  However I am still getting the error via SSH when trying to start.

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

What type of OS is the client computer; and what are the IPs of the client and rig?

Windows 10 running putty, Rig: 192.168.1.19 Client: 192.168.1.6

So when you enter

m1@192.168.1.19   

using port 22

with SSH selected

and click open it gives you the error above?

Sorry let me try and clear some things up.  I am able to SSH into the rig just fine but when executing the miner via ssh, this is when i am getting the error, so clock settings, fan speed and power limits are not being set but the mining process still starts.

I also really appreciate your support and rapid response.

Are you killing the existing mining process before launching another via SSH?

Also; when you are launching the mining process via SSH are you using the cmd:

Code:

bash '/media/m1/1263-A96E/oneBash'

I am SSHing and executing the following commands.

ps aux | grep gnome-terminal - finding the gnome-server PID
kill PID
screen -S rig1
bash '/media/m1/1263-A96E/oneBash'

Just before the miner starts I see the above error in place of the "attribute" commands but the mining process still starts.

after you have SSHed in enter the cmd:

Code:

echo $DISPLAY

and tell me what it outputs

That does not output anything at all.

Ok, tomorrow I will try to replicate this error; and see if I can figure out what is happening.  My guess is X11 is having a problem trying to output graphically.

If you have a linux computer other than your rig and you SSH into the rig with it; does it have the same error?

I tested from a linux VM I have and the same result

I tested this today and found there is a new problem resulting (most likely) from my adding support for up to 14 GPUs. 

I found that if I waited the screen would still connect to the mining process after failing to connect 3 or 4 times.

If you are using linux you can resolve this error by adding the following argument when SSHing into the rig:

Code:

-X

so that from a terminal I would enter:

Code:

ssh m1@rigipaddress -X

so for a rig with an ip of 192.168.1.22. I would use:

Code:

ssh m1@192.168.1.22 -X

If you are using putty with windows the -X will not work; but after showing the error 3 or 4  times the screen should still connect to the mining process


I also tested using the -dmS argument when calling screen.

if you call screen with:

Code:

screen -dmS rig1

screen with start as a background process (so you can disconnect your ssh session and the miner will continue to mine on its own)

after starting screen you will need to connect to the screen (as it is running in the background)

you do this by entering:

Code:

screen -r

you can close the ssh session whenever and then reSSH in and enter:

Code:

screen -r

to return to the mining process whenever desired.

[fullzero]

Hi,

Good work.

However it takes several minutes to boot from my USB 3.0 stick?
The booting seems have some problem.

V16 changed name to amdOC?

I think you downloaded the amd Beta; it is only for amd GPUs:

scroll further down on the OP and you should find the v0016 download link.