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.

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

Started mining with nvOC v0017 on Asrock B250M Pro4 motherboard, 2x Zotac gtx1070 Mini. During the first run, the Ubuntu loading screen hung for some time and did not go past the orange/white dots but after a restart the nvOC loaded properly and started mining zec at nicehash about 400sol/s per card @103-105W per card. Settings are: power limit 105, core 200, mem 10

Keep up the good work Fullzero!

Unless your power is very expensive; I recommend using a powerlimit of 125 or more when mining ZEC with 1070s.

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.

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.

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.

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.

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.

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.

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?

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.