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

[TenaciousJ]

Thanks for links.   

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.

[1714225235]

1714225235

[1714225235]

1714225235

[1714225235]

1714225235

[1714225235]

1714225235

[fullzero]

First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.

Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

[fullzero]

So while I am not mining ZEC at the moment, when using nanopool with Nvoc, where would I add my email so I can change payout on nanopool.

Also could you elaborate on the Minimum profit = 0.0? is it like a percentage?

Btw on my toes for v0018!!! I can't wait super excited!

add to the end of the worker a / then your email like so:

Code:

ZEC_WORKER="nv$IP_AS_WORKER/EMAILHERE"

Code:

MINIMUM_PROFIT=0.0

means mining will stop if there is no coin that is profitable for you to mine (profit at 0.0 or less)

If you want to stop mining if profit is at -1$ you would set

Code:

MINIMUM_PROFIT=-1

[fullzero]

I have had a lot of requests for this; so here is a new oneBash and modded switch file which implement full integration of SALFTER_NICEHASH_PROFIT_SWITCHING

see the OP for links:

Replace your current oneBash with the new one.

extract switch and move it to the:

Code:

 /home/m1

directory

(the one which opens when you click the Files icon on the left)

configure the following in oneBash

Code:

SALFTER_NICEHASH_PROFIT_SWITCHING="YES"

# LOCAL will attach the mining process to the guake terminal
# REMOTE will leave it unattached / ready for SSH 
LOCALorREMOTE="LOCAL"       # LOCAL  or  REMOTE

CURRENCY=USD
POWER_COST=0.10
MINIMUM_PROFIT=0.0
# this is salfters BTC address:
PAYMENT_ADDRESS=1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2
WORKER_NAME=nv$IP_AS_WORKER

daggerhashimoto_POWERLIMIT_WATTS=125
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100
_______daggerhashimoto_FAN_SPEED=75

equihash_POWERLIMIT_WATTS=125
__equihash_CORE_OVERCLOCK=100
equihash_MEMORY_OVERCLOCK=100
_______equihash_FAN_SPEED=75

neoscrypt_POWERLIMIT_WATTS=125
__neoscrypt_CORE_OVERCLOCK=100
neoscrypt_MEMORY_OVERCLOCK=100
_______neoscrypt_FAN_SPEED=75

lyra2rev2_POWERLIMIT_WATTS=125
__lyra2rev2_CORE_OVERCLOCK=100
lyra2rev2_MEMORY_OVERCLOCK=100
_______lyra2rev2_FAN_SPEED=75

lbry_POWERLIMIT_WATTS=125
__lbry_CORE_OVERCLOCK=100
lbry_MEMORY_OVERCLOCK=100
_______lbry_FAN_SPEED=75

pascal_POWERLIMIT_WATTS=125
__pascal_CORE_OVERCLOCK=100
pascal_MEMORY_OVERCLOCK=100
_______pascal_FAN_SPEED=75

remember to thank salfter if you use this  

Thanks for implementing this, but for some odd reason I keep getting two instances of the miner screen running which causes the system to crash, I will do some more testing to try and figure out what is going on.

EDIT: Actually the kill code does not seem to work causing multiple miner screens, this is how the system is crashing.

Are you using LOCAL or REMOTE?

Please walk me through how you got multiple instances running so I can recreate this myself.

I am using REMOTE.  I am connecting via SSH attaching the screen with "screen -r miner"
for testing purposes I am altering the algo speed manually in the switch file waiting 10 mins for it to change and I noticed it is hit and miss for the kill code to function correctly.  I am also experiencing for LBRY and LYRA the mining process is executed twice.

Maybe I should start from scratch...

I tested the same way; changing the speed of one algo to force a switch.  I also changed the timeout in oneBash to 10 seconds instead of 600.

I tested this out and found salfters logic works well for switching between Ethash and Equihash; but not any of the other algos.  

It does seem to endlessly spawn new ccminer instances as well.  

I don't want to spend a lot of time on this; so I implemented killing all mining processes every time: then launching a new one.  It should work without issue now.

I also edited the oneBash logic to conditionally add salfters IPv6 fix, and reattach the screen to the guake terminal every reinit when in local mode.

If you have added the cronjob:

Code:

0,10,20,30,40,50 * * * * (cd /media/m1/1263-A96E && python2.7 switch.py)

I would remove it; as the oneBash implementation doesn't use it: and it may be (most likely is) causing additional launches of salfters original switch.

Note: I uploaded a new oneBash and switch with these changes.  They are linked on the OP.

Thank you, I use use the new switch now

Thanks for finding this problem; let me know if find any others.

No problem I will let you know if I find anything else.  Also do you believe killing the miner every 10 mins will impact performance/hash rates reporting to nicehash? Can this possibly mean less of a payout?

It might make a very marginal difference; less so, the less frequently you check profitability. 

You can always increase the sleep time (its in seconds) in oneBash to whatever you want.  It is currently set to 700 seconds.

Code:

  if [ $LOCALorREMOTE == "LOCAL" ]
  then
  python2.7 '/home/m1/switch'
  guake -r SALFTER_NICEHASH_PROFIT_SWITCHING -e "screen -r miner"
  echo ""
  echo "mining process in Guake Tab"
  echo ""
  sleep 700
  fi

  if [ $LOCALorREMOTE == "REMOTE" ]
  then
  python2.7 '/home/m1/switch'
  echo "ENTER:"
  echo "" 
  echo "screen -r miner"
  echo ""
  echo "in a terminal to view mining process"
  sleep 700
  fi

I will make the timeout seconds a variable to make it easier to change. 

Ultimately this will be implemented as intended; either by salfter, someone else or myself.

[fullzero]

Thanks for links.   

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.

Is the hashrate lower with the GPU running at 66%?

[DJ ACK]

First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.

Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

As fullzero mentioned the image or partioning on your USB stick may have issues.   Depends on how you installed the image.  I used Etcher in Ubuntu and had no problems (yes having Linux on another box saves you a lot of trouble).  When I installed nvOC 17 on my SSD, I had to change the 2Unix file.  By default the oneBash sits on the 9Gig partition.  I copied over to the home directory where the 2unix file sits and just changed the 2Unix file pointing it to the new location.  Problem solved.

Swapping out my MSI Z170 Gaming M5 boards for the ASUS Z270 Prime-A boards solved a lot of instability problems that I thought were riser related.  Additionally these boards are awesome for running 9 GPUs or more.  I have 9 x 1050Tis (1506 Boost Clock versions) running solid on these boards (0 Core OC, 1550 Mem OC, power limit 65, 133 MH/s per rig).

[TenaciousJ]

Thanks for links.    

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.

Is the hashrate lower with the GPU running at 66%?

yeah by about 100 sol/sec or so

EDIT: actually by about 130 sol/sec, and the power going to the card is only 2/3 most of the time... 145-150w for other cards, and only 85-110w for that one.

[S9k]

First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.

Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

hi, it is not problems of image.
these are problems of the FAT32 file system which falls after each incorrect reset. You can find such line in dmesg:

120.350515] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't trust FAT32 and have transferred oneBash to other place.
At me it is impossible to stabilize my system in any way. I observe a large number of restarts which I can't analyse.
Syslog doesn't contain anything useful.

m1@m1-desktop:~$ last reboot
reboot   system boot  4.4.0-83-generic Sun Jul  9 04:36   still running
reboot   system boot  4.4.0-83-generic Sun Jul  9 00:00   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 17:50   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 15:31   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:56   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:48   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 12:58   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 10:10   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 09:54   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 08:27   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 03:16   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 23:31   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 22:52   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 20:02   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 16:26   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 10:00   still running

I need methodology of a solution. How to find the reason of a collapse of an operating system and restart. What video card exceeds admissible values and is unstable? I think it it will be interesting to many. Thank you very much!

[TenaciousJ]

First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.

Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

hi, it is not problems of image.
these are problems of the FAT32 file system which falls after each incorrect reset. You can find such line in dmesg:

120.350515] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't trust FAT32 and have transferred oneBash to other place.
At me it is impossible to stabilize my system in any way. I observe a large number of restarts which I can't analyse.
Syslog doesn't contain anything useful.

m1@m1-desktop:~$ last reboot
reboot   system boot  4.4.0-83-generic Sun Jul  9 04:36   still running
reboot   system boot  4.4.0-83-generic Sun Jul  9 00:00   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 17:50   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 15:31   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:56   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:48   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 12:58   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 10:10   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 09:54   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 08:27   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 03:16   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 23:31   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 22:52   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 20:02   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 16:26   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 10:00   still running

I need methodology of a solution. How to find the reason of a collapse of an operating system and restart. What video card exceeds admissible values and is unstable? I think it it will be interesting to many. Thank you very much!

I had a problem with the fat32 partition on my images.  I just had to reimage it... use HDD Raw Copy.  It doesn't ALWAYS work, but it does most of the time.  Also, make sure your flash drive or hard drive is bigger than 16gb.  I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.

You could also use gparted to try to repair the partition which works sometimes.  Or use TestDisk if you're savvy with partition file table manipulation at all.

http://www.cgsecurity.org/wiki/TestDisk_Download

[S9k]

First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.

Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

hi, it is not problems of image.
these are problems of the FAT32 file system which falls after each incorrect reset. You can find such line in dmesg:

120.350515] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't trust FAT32 and have transferred oneBash to other place.
At me it is impossible to stabilize my system in any way. I observe a large number of restarts which I can't analyse.
Syslog doesn't contain anything useful.

m1@m1-desktop:~$ last reboot
reboot   system boot  4.4.0-83-generic Sun Jul  9 04:36   still running
reboot   system boot  4.4.0-83-generic Sun Jul  9 00:00   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 17:50   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 15:31   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:56   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:48   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 12:58   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 10:10   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 09:54   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 08:27   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 03:16   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 23:31   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 22:52   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 20:02   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 16:26   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 10:00   still running

I need methodology of a solution. How to find the reason of a collapse of an operating system and restart. What video card exceeds admissible values and is unstable? I think it it will be interesting to many. Thank you very much!

I had a problem with the fat32 partition on my images.  I just had to reimage it... use HDD Raw Copy.  It doesn't ALWAYS work, but it does most of the time.  Also, make sure your flash drive or hard drive is bigger than 16gb.  I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.

You could also use gparted to try to repair the partition which works sometimes.  Or use TestDisk if you're savvy with partition file table manipulation at all.

http://www.cgsecurity.org/wiki/TestDisk_Download

It isn't important at all as you do image what software and in what operating system. At the first loading everything is read perfectly!
Important the fact that after incorrect completion of nvOC (for example the system is too overclocked) data on FAT32 /dev/sda1 are damaged and you are stimulated every time to repair this partition and to do mount, remount. look above how many restarts of nvOC at me happen in days. Every time is a potential problem of damage of FAT32. IMHO needs to refuse this partition, to transfer oneBash to other directory and to modify it, using gnome (local) or ssh, sftp (remote).

Of course I will try to find the stable and balanced configuration of my system. I plunge into Linux more and more and I look for analysis techniques of system dumps.
           All of good luck!

[S9k]

With the 12x biostar nearly here, I don't think this is the right change to make.  If the biostar can actually run 12x GPUs then I will for sure; not make this alteration.  If it can only support 9x or less GPUs then I will consider making the change.

Speaking of 12gpu motherboards, I've got an ASRock 13 GPU board arriving next week.  Any thoughts on how to configure nvOC with an ASRock to get as many as possible of the GPUs running NVidia?  (my current board is an ASRock z270 that loads 6 GPUs without too much trouble, but the new board is H110, not Z270)  I've got 9 GPUs on hand to try - 8 1070s and a 980 ti.

In theory v0017+ can support 14 GPUs (13 + 1 via m2 adapter with that ASRock mobo).

But the chipset might not currently be supported and there are likely other system changes needed.  I need one of those mobos to test.  Where did you order one from?

https://www.aliexpress.com/item/New-in-BOX-ASRock-Technology-H110-PRO-BTC-H110-mining-board-support-13-graphics-card-DDR4/32822043486.html?spm=2114.13010608.0.0.GrsVzE

With the 12x biostar nearly here, I don't think this is the right change to make.  If the biostar can actually run 12x GPUs then I will for sure; not make this alteration.  If it can only support 9x or less GPUs then I will consider making the change.

Speaking of 12gpu motherboards, I've got an ASRock 13 GPU board arriving next week.  Any thoughts on how to configure nvOC with an ASRock to get as many as possible of the GPUs running NVidia?  (my current board is an ASRock z270 that loads 6 GPUs without too much trouble, but the new board is H110, not Z270)  I've got 9 GPUs on hand to try - 8 1070s and a 980 ti.

In theory v0017+ can support 14 GPUs (13 + 1 via m2 adapter with that ASRock mobo).

But the chipset might not currently be supported and there are likely other system changes needed.  I need one of those mobos to test.  Where did you order one from?

I got mine from Newegg.. according to ASRock, Newegg is expecting another shipment to arrive next week so you might want to setup an autonotify on the website.
He also did not provide any other distributors that I could check for stock, so newegg might be the only source for them right now.


https://www.newegg.com/Product/Product.aspx?Item=N82E16813157781

Thanks for links.   

https://cryptomined.com/index.php?main_page=product_info&cPath=240_276&products_id=269  SUPX LIMITED EDITION B250 12-GPU MOTHERBOARD
https://www.youtube.com/watch?v=exjRTIZu89Q  How to Build a 12 GPU Mining Rig   

[damNmad]

I can't thank enough fullZero (Hero as always ) for this really easy nvOC (valuable support) and other community members sharing their valuable time and info, it really really helped a lot of new miners like me to start and learn mining with out much hassle.
Although I've started mining very recently and mostly use google for all the information, it is going so far so good except for the following three things (tried googling but getting irrelevant information - all non nvOC stuff)

I would really appreciate your answers with explanation from our community.

1) Profitability switcher (from latest bash file)

I would like to know how it works? does it works with some particular coins only? What role Algo play in between and how to select a particular Algo?

for eg; in my case I'm mining ETH (dwarf pool) + SIA (Nano), does it help me to gain more with switching, if so can I get the code for it with little explanation.

I might consider myself noob in this case, But I would like to understand how it works and I would like to use it to increase my gains.

2) Using Nice Hash pools

How can I use Nice hash pools with nvOC?

I would like to mine DCR with "stratum+tcp://decred.eu.nicehash.com:3354", can someone please point me to right direction on how to mine and check shares per hour.

I think nice hash uses BTC address, I've tried it to mine with my BTC address (failed when I used DCR address), it was connecting fine and mining well but don't know how to check at what rate its mining (shares per hour etc).

3) DUAL Mining ETH_DCR

I've been using DUAL mining from past month on Ubuntu (not on nvOC), I couldn't figure out how to use pools like suprnova "dcr.suprnova.cc:3252" pool for DCR while dual mining with ETHEREUM (nano)

I do have account on suprnova with worker setup, but not sure how do use that worker with nvOC, can someone please guide me through it.

I would really really appreciate your help regarding this.

Good luck with your mining

Thanks.

[darklion84]

Hi!

Are you already discussed about "ERROR: Looks like GPU0 (or 1 or any) are stopped. Restart attempt" ?
I have this error on one of my 1050Ti cards in about 10 minutes after start Zcash mining.
No overclocking. Just as it is. And after card error all system hangs up deadly if I'm trying to close terminal window. If don't - mining continues but without one card.
And this rig works under win10 for days and weeks w/o problems!

So.. how to fix it?

[TenaciousJ]

I had a problem with the fat32 partition on my images.  I just had to reimage it... use HDD Raw Copy.  It doesn't ALWAYS work, but it does most of the time.  Also, make sure your flash drive or hard drive is bigger than 16gb.  I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.

You could also use gparted to try to repair the partition which works sometimes.  Or use TestDisk if you're savvy with partition file table manipulation at all.

http://www.cgsecurity.org/wiki/TestDisk_Download

It isn't important at all as you do image what software and in what operating system. At the first loading everything is read perfectly!
Important the fact that after incorrect completion of nvOC (for example the system is too overclocked) data on FAT32 /dev/sda1 are damaged and you are stimulated every time to repair this partition and to do mount, remount. look above how many restarts of nvOC at me happen in days. Every time is a potential problem of damage of FAT32. IMHO needs to refuse this partition, to transfer oneBash to other directory and to modify it, using gnome (local) or ssh, sftp (remote).

Of course I will try to find the stable and balanced configuration of my system. I plunge into Linux more and more and I look for analysis techniques of system dumps.
           All of good luck!
[/quote]

I don't disagree with you that oneBash on a fat32 part instead of exFat isn't ideal for a linux o/s to read.  I've run into problems today where my oneBash file was just empty entirely and so nvOC wouldn't boot.  

Copying oneBash to /home/m1/ on boot might be a more elegant solution to avoid these partition issues, or just avoid that partition entirely by downloading pastebin text directly to /home/m1.

Even windows doesn't like fat32 partitions that small... it forces you to format it in fat instead, so its no surprise that linux doesn't play nice with it I guess.

[TenaciousJ]

Thanks for links.   

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.

Is the hashrate lower with the GPU running at 66%?

Hey FZ - just wanted to let you know I resolved the issue with my underpowered GPU... turns out having 2 risers on one SATA power line is frowned upon... once I put all the GPUs on their own lines the system is back up at 100%

[fullzero]

First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.

Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

hi, it is not problems of image.
these are problems of the FAT32 file system which falls after each incorrect reset. You can find such line in dmesg:

120.350515] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't trust FAT32 and have transferred oneBash to other place.
At me it is impossible to stabilize my system in any way. I observe a large number of restarts which I can't analyse.
Syslog doesn't contain anything useful.

m1@m1-desktop:~$ last reboot
reboot   system boot  4.4.0-83-generic Sun Jul  9 04:36   still running
reboot   system boot  4.4.0-83-generic Sun Jul  9 00:00   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 17:50   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 15:31   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:56   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:48   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 12:58   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 10:10   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 09:54   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 08:27   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 03:16   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 23:31   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 22:52   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 20:02   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 16:26   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 10:00   still running

I need methodology of a solution. How to find the reason of a collapse of an operating system and restart. What video card exceeds admissible values and is unstable? I think it it will be interesting to many. Thank you very much!

I had a problem with the fat32 partition on my images.  I just had to reimage it... use HDD Raw Copy.  It doesn't ALWAYS work, but it does most of the time.  Also, make sure your flash drive or hard drive is bigger than 16gb.  I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.

You could also use gparted to try to repair the partition which works sometimes.  Or use TestDisk if you're savvy with partition file table manipulation at all.

http://www.cgsecurity.org/wiki/TestDisk_Download

It isn't important at all as you do image what software and in what operating system. At the first loading everything is read perfectly!
Important the fact that after incorrect completion of nvOC (for example the system is too overclocked) data on FAT32 /dev/sda1 are damaged and you are stimulated every time to repair this partition and to do mount, remount. look above how many restarts of nvOC at me happen in days. Every time is a potential problem of damage of FAT32. IMHO needs to refuse this partition, to transfer oneBash to other directory and to modify it, using gnome (local) or ssh, sftp (remote).

Of course I will try to find the stable and balanced configuration of my system. I plunge into Linux more and more and I look for analysis techniques of system dumps.
           All of good luck!

I don't disagree with you that oneBash on a fat32 part instead of exFat isn't ideal for a linux o/s to read.  I've run into problems today where my oneBash file was just empty entirely and so nvOC wouldn't boot. 

Copying oneBash to /home/m1/ on boot might be a more elegant solution to avoid these partition issues, or just avoid that partition entirely by downloading pastebin text directly to /home/m1.

Even windows doesn't like fat32 partitions that small... it forces you to format it in fat instead, so its no surprise that linux doesn't play nice with it I guess.

Most likely the problem is a combination of slow media (although it is possible to have the same problem with fast media) and too short of a timeout in this area of 2unix

Code:

sudo dos2unix /media/m1/1263-A96E/oneBash

sleep 2

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

I will increase the timeout in v0018 and most likely this will not be a problem.



I will make the following changes for v0018:

  The windows partition will be NTFS.

  On first boot (and only first boot) the following will occur:

    oneBash will be copied to '/home/m1/oneBash'

    dos2unix will run on '/home/m1/oneBash'

    the timeout afterwards will be 15 seconds

    the windows partition will be zeroized (and will not mount on the next boot)

 

[fullzero]

Thanks for links.   

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.

Is the hashrate lower with the GPU running at 66%?

Hey FZ - just wanted to let you know I resolved the issue with my underpowered GPU... turns out having 2 risers on one SATA power line is frowned upon... once I put all the GPUs on their own lines the system is back up at 100%

With 1080 or 1080ti that is best; especially if they are AM models.  I haven't heard of anyone needing to do this with 1070s or 1060s; what type of GPUs are you using?

[fullzero]

Hi!

Are you already discussed about "ERROR: Looks like GPU0 (or 1 or any) are stopped. Restart attempt" ?
I have this error on one of my 1050Ti cards in about 10 minutes after start Zcash mining.
No overclocking. Just as it is. And after card error all system hangs up deadly if I'm trying to close terminal window. If don't - mining continues but without one card.
And this rig works under win10 for days and weeks w/o problems!

So.. how to fix it?

What are is your powerlimit / mobo / CPU / all GPUs / what COIN are you mining / what mining client are you using?

[fullzero]

I can't thank enough fullZero (Hero as always ) for this really easy nvOC (valuable support) and other community members sharing their valuable time and info, it really really helped a lot of new miners like me to start and learn mining with out much hassle.
Although I've started mining very recently and mostly use google for all the information, it is going so far so good except for the following three things (tried googling but getting irrelevant information - all non nvOC stuff)

I would really appreciate your answers with explanation from our community.

1) Profitability switcher (from latest bash file)

I would like to know how it works? does it works with some particular coins only? What role Algo play in between and how to select a particular Algo?

for eg; in my case I'm mining ETH (dwarf pool) + SIA (Nano), does it help me to gain more with switching, if so can I get the code for it with little explanation.

I might consider myself noob in this case, But I would like to understand how it works and I would like to use it to increase my gains.

2) Using Nice Hash pools

How can I use Nice hash pools with nvOC?

I would like to mine DCR with "stratum+tcp://decred.eu.nicehash.com:3354", can someone please point me to right direction on how to mine and check shares per hour.

I think nice hash uses BTC address, I've tried it to mine with my BTC address (failed when I used DCR address), it was connecting fine and mining well but don't know how to check at what rate its mining (shares per hour etc).

3) DUAL Mining ETH_DCR

I've been using DUAL mining from past month on Ubuntu (not on nvOC), I couldn't figure out how to use pools like suprnova "dcr.suprnova.cc:3252" pool for DCR while dual mining with ETHEREUM (nano)

I do have account on suprnova with worker setup, but not sure how do use that worker with nvOC, can someone please guide me through it.

I would really really appreciate your help regarding this.

Good luck with your mining

Thanks.

1

First configure this section of oneBash:

Code:

SALFTER_NICEHASH_PROFIT_SWITCHING="YES"

# LOCAL will attach the mining process to the guake terminal
# REMOTE will leave it unattached / ready for SSH 
LOCALorREMOTE="LOCAL"       # LOCAL  or  REMOTE

CURRENCY=USD
POWER_COST=0.10
MINIMUM_PROFIT=0.0
# this is salfters BTC address:
PAYMENT_ADDRESS=1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2
WORKER_NAME=nv$IP_AS_WORKER

daggerhashimoto_POWERLIMIT_WATTS=125
__daggerhashimoto_CORE_OVERCLOCK=100
daggerhashimoto_MEMORY_OVERCLOCK=100
_______daggerhashimoto_FAN_SPEED=75

equihash_POWERLIMIT_WATTS=125
__equihash_CORE_OVERCLOCK=100
equihash_MEMORY_OVERCLOCK=100
_______equihash_FAN_SPEED=75

neoscrypt_POWERLIMIT_WATTS=125
__neoscrypt_CORE_OVERCLOCK=100
neoscrypt_MEMORY_OVERCLOCK=100
_______neoscrypt_FAN_SPEED=75

lyra2rev2_POWERLIMIT_WATTS=125
__lyra2rev2_CORE_OVERCLOCK=100
lyra2rev2_MEMORY_OVERCLOCK=100
_______lyra2rev2_FAN_SPEED=75

lbry_POWERLIMIT_WATTS=125
__lbry_CORE_OVERCLOCK=100
lbry_MEMORY_OVERCLOCK=100
_______lbry_FAN_SPEED=75

pascal_POWERLIMIT_WATTS=125
__pascal_CORE_OVERCLOCK=100
pascal_MEMORY_OVERCLOCK=100
_______pascal_FAN_SPEED=75

ensure:

Code:

SALFTER_NICEHASH_PROFIT_SWITCHING="YES"

and replace salfters BTC address with your own:

Code:

PAYMENT_ADDRESS=1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2

salfter implemented this for nicehash only.  It makes a call to a nicehash api and receives the current profitability data. 

Using your input power cost (and what I am guessing are salfters benchmarks for each algo using 2x 1070s) it calculates which coin is currently the most profitable to mine.

It then stops any mining process, and starts a new one with the most profitable coin and your OC settings for that coin.


2

You can use the SALFTER_NICEHASH_PROFIT_SWITCHING, or you can use the:

Code:

NICE_ETHASH

COIN selection

I still need to add all the other nicehash algos as normal COIN selections.

Nicehash does use a BTC payout address, when using the NICE_ETHASH COIN selection set this in this area of the oneBash settings:

Code:

# if YES ensure you update BTC_ADDRESS
VTC_AUTOCONVERT_TO_BTC="YES"        #YES  NO
VTC_WORKER="nv$IP_AS_WORKER"
VTC_ADDRESS="VsvtYL2mz3YFM3fpt5pb28zHodTbnJodRc"
VTC_POOL="stratum+tcp://lyra2v2.mine.zpool.ca:4533"

BTC_ADDRESS="18Y5HYe3BAwAhTAkFLbD52o8NqtrN3DtpF"

# NICE_ETHASH autoconverts to BTC: ensure you update BTC_ADDRESS if you use NICE_ETHASH
NICE_ETHASH_WORKER="nv$IP_AS_WORKER"
NICE_ETHASH_POOL="stratum+tcp://daggerhashimoto.usa.nicehash.com:3353"
GENOIL_NICE_ETHASH_POOL="daggerhashimoto.usa.nicehash.com:3353"
NICE_ETHASH_EXTENTION_ARGUMENTS=""   # add any additional claymore arguments desired here

this line:

Code:

BTC_ADDRESS="18Y5HYe3BAwAhTAkFLbD52o8NqtrN3DtpF"

3


at the top of oneBash ensure COIN is set to:

Code:

COIN="DUAL_ETH_DCR"

then set your ETH settings here:

Code:

ETHERMINEdotORG="NO"

CLAYMORE_VERSION="9_5"    # choose 9_5  or  9_4  or  8_0

GENOILorCLAYMORE="GENOIL"  # choose GENOIL  or  CLAYMORE


ETH_WORKER="nv$IP_AS_WORKER"
ETH_ADDRESS="0xe12bdd454997e443ec0cae6bebb6bb3c74242aae"
ETH_POOL="eth-us-east1.nanopool.org:9999"
ETH_EXTENTION_ARGUMENTS=""    # add any additional claymore arguments desired here

then set your DCR settings here:

Code:

DCR_WORKER="nv$IP_AS_WORKER"
DCR_ADDRESS="fullzero22"
DCR_POOL="stratum+tcp://dcr.suprnova.cc:3252"

Note that with supernova you need to set the workername beforehand, so I recommend changing the workername to whatever you have set already rather than making a new worker with the auto generated workername.

replace:  DCR_ADDRESS="fullzero22" with  your supernova username


Let me know if all this makes sense.

[darklion84]

Hi!

Are you already discussed about "ERROR: Looks like GPU0 (or 1 or any) are stopped. Restart attempt" ?
I have this error on one of my 1050Ti cards in about 10 minutes after start Zcash mining.
No overclocking. Just as it is. And after card error all system hangs up deadly if I'm trying to close terminal window. If don't - mining continues but without one card.
And this rig works under win10 for days and weeks w/o problems!

So.. how to fix it?

What are is your powerlimit / mobo / CPU / all GPUs / what COIN are you mining / what mining client are you using?

All default. Didn't touch anything. Powerlimit 100, all GPUs, Zcash on EWBF 0.3.4b from github.