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

[BigHashMiner]

when is v0019 coming?

[1714177854]

1714177854

[1714177854]

1714177854

[gs777]

Isn't it crazy 



http://www.anandtech.com/show/11739/asus-announces-b250-expert-mining-motherboard-19-expansions-slots

[damNmad]

Isn't it crazy 



http://www.anandtech.com/show/11739/asus-announces-b250-expert-mining-motherboard-19-expansions-slots

yeah, mother of crazy indeed

[gs777]

Interesting who will make first OS to run one MoBo with 19xGPU
 

[damNmad]

Interesting who will make first OS to run one MoBo with 19xGPU
 

Probably Ubuntu is the best one for it.

[JudoFlash]

Hi all,

Has anyone incorporated ethminer 0.11.0 into this nvOC release? I managed to download it and can get it to run, but have been having the hardest time getting any results. I am running all GTX 1060 6GB cards (13 per rig), but am still getting about 21.5 Mh/s with mem OC.

I may not be the most adept at editing the 1bash though, and was having a difficult time finding a list of the flags (ethminer --help told me that ethminer wasn't a valid program).

Any thoughts?

[Bibi187]

Hi all,

Has anyone incorporated ethminer 0.11.0 into this nvOC release? I managed to download it and can get it to run, but have been having the hardest time getting any results. I am running all GTX 1060 6GB cards (13 per rig), but am still getting about 21.5 Mh/s with mem OC.

I may not be the most adept at editing the 1bash though, and was having a difficult time finding a list of the flags (ethminer --help told me that ethminer wasn't a valid program).

Any thoughts?

U dont have to put any miner os nvOC, miner is in nvOC. For eth u can use genoil as far i know is the one u can grab more mh/s per gpu
Copy past your 1bash file ( only the first part ) here and i will help you

[fullzero]

I'll try the to use new 1bash if I get unstable results in the future since now I had the rig up for over 28 hours. Also does the autoreboot in the SSH only mode works as it supposed to?

Hi,

autoreboot work fine on SSH mode, my rig reboot every 24 hours, i commented /etc/fstab my rig reboot in less then 30sec.

Fullzero i noticed something, if u run 1bash at root user, after u have to apply validation on rm file. Not so much important that from a miss leading from me, on launching 1bash at root user. Just for let u to know.

Thanks for you amazing work to as usual ...

You would have to add Maxximus007's flag for root as well as m1 to avoid needing to enter a password.  Why do you run 1bash as root?

[Bibi187]

I'll try the to use new 1bash if I get unstable results in the future since now I had the rig up for over 28 hours. Also does the autoreboot in the SSH only mode works as it supposed to?

Hi,

autoreboot work fine on SSH mode, my rig reboot every 24 hours, i commented /etc/fstab my rig reboot in less then 30sec.

Fullzero i noticed something, if u run 1bash at root user, after u have to apply validation on rm file. Not so much important that from a miss leading from me, on launching 1bash at root user. Just for let u to know.

Thanks for you amazing work to as usual ...

You would have to add Maxximus007's flag for root as well as m1 to avoid needing to enter a password.  Why do you run 1bash as root?

I dont take notice about what user i am when i launched it That only reason why ^^
I think i dont miss flag, but after my mistake root owned file so file get write protected and have to validate by hand to be deleted, this thing only happen one time after i launched 1bash as root user.
Is just a feedback not a real problem here ! Thanks for your attention as always

[fullzero]

Hi there guys !

Long time lurker and actual user of nvOC, i need help converting my 21 1080Ti's into rigs with 3 cards using HP DC7900 Small Form Factor pc's as the base for the rigs.
My issue is that although i can boot basically any live distro using a USB stick, i can't boot no matter what nvOC from a usb stick.
Does nvOC needs a UEFI compatible BIOS in order to be booted by older machines ?
Can i convert the image to be non-GPT  and hence bootable on older machines ?

Thanks a lot for your support !

There may be a bios setting related to Secure Boot or TPM; changing this setting or settings may allow boot.

If that doesn't work I would try this:

Image a live boot ubuntu USB.  Then boot from a different linux build.  Open gparted.  Copy the primary nvOC partition over the primary partition on the live boot USB.  If the live boot primary partition is smaller than 16gb, extend it first then copy over the primary nvOC partition.

[fullzero]

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'

Any idea guys??

What version of nvOC are you using?

Looking at this list of errors they are all essentially 1 error; which if I am correct is the equivalent of when you try to go to a webpage and are getting a certificate error from your browser.

When I directly use the url in a browser:  https://api.coinbase.com/v2/exchange-rates?currency=BTC the api is working; I would try doing this on your rig in a browser and see if it responds with a json.

Let me know if it does.

I'm using nvOC v18 with all the updated files provided on main post.

I've compared my 1bash file with the latest 1bash on 1st page, seems no difference apart from the changes I've made (coins added by myself).

Opened the switch python file; checked the url's on RIG's browser, seems ok; nothing stands out, not sure what is going on with my RIG, everything else works fine except the profit switching!!

It starts fine; prints the per day calculation after displaying the above error list; says mining starts on guake terminal; tab opens in guake terminal and 'screen -r miner' then 'There is no screen to be resumed matching miner' and again 'screen -r miner' then 'There is no screen to be resumed matching miner'.

My guess it is failing to find the miner but also the switch file failing to make connection with those API's!!

Yes

the switch file failing to make connection with those API

this is why I wanted you to:

When I directly use the url in a browser:  https://api.coinbase.com/v2/exchange-rates?currency=BTC the api is working; I would try doing this on your rig in a browser and see if it responds with a json.

Let me know if it does.

to help isolate if the problem is with your system or the script.

Thanks for the reply, sorry fullzero, I've already mentioned that i've tried both url's on Firefox

https://api.coinbase.com/v2/exchange-rates?currency=BTC  && https://api.nicehash.com/api?method=simplemultialgo.info

which are working as expected...getting the json file from coinbase URL and json result from nicehash URL

Just pasting the whole console history of the events, prob. gives any better idea!

Code:

workername: nvxxxxx


rig IP: xxx.xxx.xxx.xxx


01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)


Thu Aug 24 20:29:31 2017       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.47                 Driver Version: 384.47                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0  On |                  N/A |
|  0%   53C    P0    37W /  80W |    137MiB /  6072MiB |     48%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 106...  Off  | 00000000:02:00.0 Off |                  N/A |
|  0%   29C    P8     4W /  80W |      9MiB /  6072MiB |      2%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:03:00.0 Off |                  N/A |
|  0%   38C    P8     6W /  80W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:05:00.0 Off |                  N/A |
|  0%   31C    P8     6W /  80W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce GTX 106...  Off  | 00000000:06:00.0 Off |                  N/A |
|  0%   38C    P8     7W /  80W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce GTX 106...  Off  | 00000000:07:00.0 Off |                  N/A |
|  0%   37C    P8     6W /  80W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
|   6  GeForce GTX 106...  Off  | 00000000:08:00.0 Off |                  N/A |
|  0%   34C    P8     7W /  80W |      9MiB /  6072MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
|   7  GeForce GTX 106...  Off  | 00000000:0A:00.0 Off |                  N/A |
|  0%   36C    P8     6W /  80W |      9MiB /  6072MiB |      2%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1038    G   /usr/lib/xorg/Xorg                             107MiB |
|    0      1868    G   compiz                                          28MiB |
|    1      1038    G   /usr/lib/xorg/Xorg                               7MiB |
|    2      1038    G   /usr/lib/xorg/Xorg                               7MiB |
|    3      1038    G   /usr/lib/xorg/Xorg                               7MiB |
|    4      1038    G   /usr/lib/xorg/Xorg                               7MiB |
|    5      1038    G   /usr/lib/xorg/Xorg                               7MiB |
|    6      1038    G   /usr/lib/xorg/Xorg                               7MiB |
|    7      1038    G   /usr/lib/xorg/Xorg                               7MiB |
+-----------------------------------------------------------------------------+


ENVIRONMENTAL VARIBLES SET
Power limit for GPU 00000000:01:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:02:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:03:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:05:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:06:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:07:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:08:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:0A:00.0 was set to 80.00 W from 80.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.
/home/m1/1bash: line 803: [: ==: unary operator expected
LAUNCHING:  SALFTER_NICEHASH_PROFIT_SWITCHING 

____currency: USD
_____pwrcost: 0.2
__min_profit: 0.0
payment_addr: 3AbFfeS7jXbdu9x3B24HQGhUoZrXrgsuZc
__miner_name: RIGV180V05

daggerhashimoto_POWERLIMIT_WATTS: 80
__daggerhashimoto_CORE_OVERCLOCK: 100
daggerhashimoto_MEMORY_OVERCLOCK: 1300

equihash_POWERLIMIT_WATTS: 80
__equihash_CORE_OVERCLOCK: 150
equihash_MEMORY_OVERCLOCK: 80

neoscrypt_POWERLIMIT_WATTS: 80
__neoscrypt_CORE_OVERCLOCK: 100
neoscrypt_MEMORY_OVERCLOCK: 1100

lyra2rev2_POWERLIMIT_WATTS: 80
__lyra2rev2_CORE_OVERCLOCK: 100
lyra2rev2_MEMORY_OVERCLOCK: 1100

lbry_POWERLIMIT_WATTS: 80
__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)

neoscrypt: 0.00037516 BTC/day (1.19 USD/day)
lyra2rev2: -0.00006594 BTC/day (-0.21 USD/day)
daggerhashimoto: 0.00078480 BTC/day (2.50 USD/day)
lbry: -0.00003413 BTC/day (-0.11 USD/day)
equihash: 0.00070695 BTC/day (2.25 USD/day)


mining process in Guake Tab

on Guake Terminal

Code:

m1@m1-desktop:~$ screen -r miner
There is no screen to be resumed matching miner.
m1@m1-desktop:~$ screen -r miner
There is no screen to be resumed matching miner.
m1@m1-desktop:~$

getting this warning from the beginning of v18, thought of letting you know but keep forgetting about it, never caused any issue with mining though! compared with the latest 1bash, nothing stands out!!

Code:

/home/m1/1bash: line 803: [: ==: unary operator expected

&& this

Code:

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

-----------------------------

While doing another debug, I just realised replacing the 'bn.h' file in /usr/local/include/openssl/ to the one from 'openssl-1.0.1e' version for compiling the 'krnlx' version of ccminer (for mining 'sigt'). So it might've caused the issue of handshake error. Am I right thinking so? I haven't made a backup of that file, can someone please share that file so that I will try and conclude it.

or

If the switch file might've been corrupted or so! I highly doubt touching it before!! don't even remember opening it. can you please add the switch file to main post?

My bad; missed you had already tried that.  Glad you figured it out. 

[fullzero]

I got a random problem in one of my rigs and that is a random GPU wont get fully utilized and watch dog keep restarting the miner almost every 20-30 minutes.
Some times its GPU3, some times 0, some times 2 and ...
Only way is to reboot the rig and it will be ok most of the time.
Any idea what could cause it ?
Is there a reboot call in the system in case miner get started too many times in a given time? If not it could be a good option to add.
Example if miner restarted 3 times in less than an hour reboot the rig.

Another issue I faced is it takes so long to open nvidia-settings on both my rigs, long as 10-20 minutes after click it, is it normal ?
Where should I check for the problem?

If it is a different GPU at different times; my guess is that the image is bad.  I would try using another USB key or SSD and seeing if you have the same problem.

It is not normal to take 10+ minutes to open nvidia-settings.

Also what are your OC / Powerlimit settings and what GPUs are on this rig?

[fullzero]

Is any way we can dual mine NICE_ETHASH and SIA ?

Probably you can try, I mine DUAL with NICE_ETHASH and NICE_DECRED using claymore.

Haven't tried with SIA + NICE ETHASH

How did you setup you 1bash? can you share it please?

Yeah mate, why not!

Code:

COIN="DUAL_NICEHASH"

Define your worker pool and worker details etc;

make sure you add your own BTC address; can use same address for both coins;

Code:

DUAL_WORKER="$IP_AS_WORKER"
DUAL_BTC_ADDRESS=$BTC_ADDRESS
DUAL_ETHASH_POOL="stratum+tcp://daggerhashimoto.eu.nicehash.com:3353"
DUAL_DCR_POOL="stratum+tcp://decred.eu.nicehash.com:3354"
DUAL_EXTENTION_ARGUMENTS="-dcoin dcr -dcri 40 -esm 3 -allpools 1 -allcoins 1 -estale 0 -dbg -1"

In the bottom paste it in the right place;  

Code:

if [ $COIN == "DUAL_NICEHASH" ]
then

if [ $CLAYMORE_VERSION == "9_7" ]
then
HCD='/home/m1/eth/9_7/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "9_5" ]
then
HCD='/home/m1/eth/9_5/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "9_4" ]
then
HCD='/home/m1/eth/9_4/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "8_0" ]
then
HCD='/home/m1/eth/8_0/ethdcrminer64'
fi

ETHASH_ADDR="$DUAL_BTC_ADDRESS.$DUAL_WORKER"
DCR_ADDR="$DUAL_BTC_ADDRESS.$DUAL_WORKER"

screen -dmS miner $HCD -epool $DUAL_ETHASH_POOL -ewal $ETHASH_ADDR -epsw x -allpools 1 -dpool $DUAL_DCR_POOL -dwal $DCR_ADDR -dpsw x $DUAL_EXTENTION_ARGUMENTS

if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi

BITCOIN="theGROUND"

while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi

This should work as is if you just make sure you add your own BTC address in the BTC_ADDRESS variable

Hope it helps, let me know if you still have any questions?


EDIT:

You can tweak it to add SC by changing as following

Code:

DUAL_SC_POOL="xxxxxxxx"
DUAL_SC_ADDRESS="xxxxxxxx"
DUAL_EXTENTION_ARGUMENTS="-dcoin sc -dcri 40 -esm 3 -allpools 1 -allcoins 1 -estale 0 -dbg -1"

In the bottom;

Code:

ETHASH_ADDR="$DUAL_BTC_ADDRESS.$DUAL_WORKER"
#can use any, depending on the pool you use
#ADDR="$DUAL_SC_ADDRESS/$DUAL_WORKER"
ADDR="$DUAL_SC_ADDRESS.$DUAL_WORKER"

screen -dmS miner $HCD -epool $DUAL_ETHASH_POOL -ewal $ETHASH_ADDR -epsw x -allpools 1 -dpool $DUAL_SC_POOL -dwal $ADDR -dpsw x $DUAL_EXTENTION_ARGUMENTS

Thanks for adding COIN selections.

I also think moving the arguments you did to the EXTENSION_ARGUMENTS is a good idea.

[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.

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

In the second picture:

My guess is that you are hitting ctrl + c too quickly after seeing the mining process is launched message (the process is actually launched immediately after this is displayed, so it is possible to close it too soon)

At the bottom: you have already opened 1bash in nano without closing the process which is why you are getting that message.  Having 1bash open in nano while trying to launch 1bash might also be causing problems (although it shouldn't).

To manually launch 1bash use the command:

Code:

bash 1bash

nano is for editing 1bash

You also might need to use the cmd:

Code:

sudo reboot

to reboot the rig after changing the xorg for the first time.  It is probably best to only conditionally change the xorg; but making / testing a configuration that works more smoothly will be much easier with my own p106-100 rig. 

For now it is probably easier to use 1 normal 1060 as the primary GPU and avoid all of this. 

I would like to make my own p106-100 rig to test and better resolve all issues.  I find it very strange that these GPUs are not for sale in the US. 

What I did is joined. New 1bash downloaded, started the miner disconnect the monitor from the motherboard. Rebooted, logged in via SSH. Next: 1. Screen -Ls 2.bash 1bash -3.screen -R miner and here is the result

http://prntscr.com/gcnn4t
http://prntscr.com/gcno97

What version of nvOC are you using?

[fullzero]

when is v0019 coming?

I could release the current RC with all the stable tested changes; but it is better if I implement a few more requests before releasing it.

[JudoFlash]

Hi all,

Has anyone incorporated ethminer 0.11.0 into this nvOC release? I managed to download it and can get it to run, but have been having the hardest time getting any results. I am running all GTX 1060 6GB cards (13 per rig), but am still getting about 21.5 Mh/s with mem OC.

I may not be the most adept at editing the 1bash though, and was having a difficult time finding a list of the flags (ethminer --help told me that ethminer wasn't a valid program).

Any thoughts?

U dont have to put any miner os nvOC, miner is in nvOC. For eth u can use genoil as far i know is the one u can grab more mh/s per gpu
Copy past your 1bash file ( only the first part ) here and i will help you

Thank you. My apologies if I was not clear. I have been able to use the Genoil already in nvOC 18 (it automatically executes through my editing of 1bash). I have also managed to successfully download the later version of ethminer, which is supposed to get more Mh/s for GTX 1060 cards (which I have). The challenges I have are:
- These use different flags for the optimization.
- I cannot find a list of the flags, and going to the ethminer directory and typing "ethminer --help" tells me that ethminer is not a program (even though I can definitely get 0.11.0 to execute when pointing to it in 1bash, or simply dropping the new ethminer into the Genoil-U folder).

So really, I am hoping to find if anyone has had success configuring this later miner version and gotten the increased performance.

Any help would be awesome.

[fullzero]

Interesting who will make first OS to run one MoBo with 19xGPU
 

Probably Ubuntu is the best one for it.

16x should work with current Ubuntu systems.  v0018 should already have OC support for 16x GPUs.

Not sure if I like having 3x 24pin; using 3x pico is more expensive.  Although this is better if using ATX.

19x GPUs is also a lot of hash to lose if this rig goes down.

A 19x 1080ti would be one monster rig.

[fullzero]

Hi all,

Has anyone incorporated ethminer 0.11.0 into this nvOC release? I managed to download it and can get it to run, but have been having the hardest time getting any results. I am running all GTX 1060 6GB cards (13 per rig), but am still getting about 21.5 Mh/s with mem OC.

I may not be the most adept at editing the 1bash though, and was having a difficult time finding a list of the flags (ethminer --help told me that ethminer wasn't a valid program).

Any thoughts?

U dont have to put any miner os nvOC, miner is in nvOC. For eth u can use genoil as far i know is the one u can grab more mh/s per gpu
Copy past your 1bash file ( only the first part ) here and i will help you

Thank you. My apologies if I was not clear. I have been able to use the Genoil already in nvOC 18 (it automatically executes through my editing of 1bash). I have also managed to successfully download the later version of ethminer, which is supposed to get more Mh/s for GTX 1060 cards (which I have). The challenges I have are:
- These use different flags for the optimization.
- I cannot find a list of the flags, and going to the ethminer directory and typing "ethminer --help" tells me that ethminer is not a program (even though I can definitely get 0.11.0 to execute when pointing to it in 1bash, or simply dropping the new ethminer into the Genoil-U folder).

So really, I am hoping to find if anyone has had success configuring this later miner version and gotten the increased performance.

Any help would be awesome.

Adding the new ethminer with individual GPU output has already been requested by another member.  I will compile it (probably) tomorrow and tell you how it does / upload the files.

In the meantime:

On the ethminer executable you copied to the Genoil-U directory, open guake and type:

Code:

chmod 755 

with a space after 755 then drag the ethminer executable you copied to the Genoil-U directory to the guake terminal and let go.  It should add an absolute path to it after the chmod 755

press enter then try running ethminer again.

[papampi]

I got a random problem in one of my rigs and that is a random GPU wont get fully utilized and watch dog keep restarting the miner almost every 20-30 minutes.
Some times its GPU3, some times 0, some times 2 and ...
Only way is to reboot the rig and it will be ok most of the time.
Any idea what could cause it ?
Is there a reboot call in the system in case miner get started too many times in a given time? If not it could be a good option to add.
Example if miner restarted 3 times in less than an hour reboot the rig.

Another issue I faced is it takes so long to open nvidia-settings on both my rigs, long as 10-20 minutes after click it, is it normal ?
Where should I check for the problem?

If it is a different GPU at different times; my guess is that the image is bad.  I would try using another USB key or SSD and seeing if you have the same problem.

It is not normal to take 10+ minutes to open nvidia-settings.

Also what are your OC / Powerlimit settings and what GPUs are on this rig?

2 rigs, both with same config 6x1070, one shows those symptoms one works perfect.
Very mild oc :
Power: 130
Clock:  50
Mem: 250

Both rigs takes long time to open nvidia settings ... any idea why ?

[JudoFlash]

Hi all,

Has anyone incorporated ethminer 0.11.0 into this nvOC release? I managed to download it and can get it to run, but have been having the hardest time getting any results. I am running all GTX 1060 6GB cards (13 per rig), but am still getting about 21.5 Mh/s with mem OC.

I may not be the most adept at editing the 1bash though, and was having a difficult time finding a list of the flags (ethminer --help told me that ethminer wasn't a valid program).

Any thoughts?

U dont have to put any miner os nvOC, miner is in nvOC. For eth u can use genoil as far i know is the one u can grab more mh/s per gpu
Copy past your 1bash file ( only the first part ) here and i will help you

Thank you. My apologies if I was not clear. I have been able to use the Genoil already in nvOC 18 (it automatically executes through my editing of 1bash). I have also managed to successfully download the later version of ethminer, which is supposed to get more Mh/s for GTX 1060 cards (which I have). The challenges I have are:
- These use different flags for the optimization.
- I cannot find a list of the flags, and going to the ethminer directory and typing "ethminer --help" tells me that ethminer is not a program (even though I can definitely get 0.11.0 to execute when pointing to it in 1bash, or simply dropping the new ethminer into the Genoil-U folder).

So really, I am hoping to find if anyone has had success configuring this later miner version and gotten the increased performance.

Any help would be awesome.

Adding the new ethminer with individual GPU output has already been requested by another member.  I will compile it (probably) tomorrow and tell you how it does / upload the files.

In the meantime:

On the ethminer executable you copied to the Genoil-U directory, open guake and type:

Code:

chmod 755 

with a space after 755 then drag the ethminer executable you copied to the Genoil-U directory to the guake terminal and let go.  It should add an absolute path to it after the chmod 755

press enter then try running ethminer again.

Thank you! I will try that this evening and share anything worthwhile that I learn.