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

[engineerking]

I am experiencing the exact same problems almost verbatim as the poster above. I was thinking it is related to a bad flash drive possibly. I am trying a different one. Also version 14 and 15 seem to work better than 17 and 18. I am getting lag and freezes and random reboots just trying to use you ubuntu with no mining software running.

[1713503890]

1713503890

[1713503890]

1713503890

[1713503890]

1713503890

[1713503890]

1713503890

[1713503890]

1713503890

[1713503890]

1713503890

[ijduncan]

How about the option to set auto shutdown when the power button is pressed?  I often need to move rigs and want to shut them down without plugging in or remoting in.

I have been running the following:

gsettings set org.gnome.settings-daemon.plugins.power button-power 'shutdown'

cheers

[Nexillus]

fullzero,

After testing this week it seems the problems were the flash drive nothing more.

It must have been getting write errors for quite some time that finally it just died causing the rig instability. 

I appreciate all the hard work!

[ijduncan]

I am seeing a new error i have not seen before.

There is no screen to be resumed matching miner.  

In the terminal window right before the miner of choice starts.  And the mining still does seem to start in the background.

Could it have something to do with a high resolution screen being present?

I have tried another image and the same thing occurred.

[WoolF911]

I am seeing a new error i have not seen before.
There is no screen to be resumed matching miner.
In the terminal window right before the miner of choice starts.  And the mining still does seem to start in the background.

Yes, same problem.

[newmz]

Hi @fullzero

when I recently upgraded my rig to run nvOC 0018, it did something nasty to an ssd that was connected to the rig which had a Windows 8.1 install on it. I remember reading something after it booted about how it was doing something to Windows partitions, and now if I remove the USB stick so the BIOs tries to boot from the SSD it says something like "NO OPERATING SYSTEM INSTALLED".

I do like to be able to swap to Windows to try out different things - do you have any idea how I may be able to repair the SSD so Windows will boot again? Or do I just have to go through the pain of installing it from scratch and unplug it when I use nvOC?

Install from scratch.

Then make sure it is not attached or you will kill it

BUMMER! A warning would have been nice.

Newmz, I had the identical thing happen to me. Most likely what happened is the boot record was wiped out on the hard drive where you had windows installed. I have not tried to recover mine yet but it should be a very simple thing. I would try something before taking philipma1957's advice; I would try putting a windows install disk into your DVD or USB key. Then run a recover. There is also (if I recall) an FSISK /MBR you can run.

I am going to try this myself but your windows partition should be fine, you're just missing an MBR. -No big deal really!

So give that some googling and you'll find it's easy to recover. Otherwise when I get to it this weekend. I will try to recover mine and let you know what I did to hopefully fix the issue.

My apologies; I had done a quick test to see if this would happen: but I realize now I needed to do a test with a standard option windows install; as I have used custom partitions will all the windows installs I have.  

I will add a warning to the OP; and add more logic to 2unix for v0019.

hatch789 is correct in that if you used a standard windows partition set; your primary ( C Drive ) partition is still on that SSD.  



A longer way to recover it with minimal risk ( and also make a backup of the primary partition ) You will need 3 additional SSDs of the same or larger capacity to do this:



Get SSD to be used as the primary partition backup ready:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

an SSD that is empty or has data / an install you are willing to delete.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and the SSD populate in the Disks app

select the SSD (its background should become orange)

at the top right of the application there is an icon with 3 horizontal lines

click this icon

and select Format Disk

set Erase to:  Quick

set Partioning to:  MBR / DOS

and Format the ssd

when it is done: underneath the orange horizontal bar that depicts the disk partitions:

click the

 +

set Erase to:  Quick

set Partitioning to:  NTFS

click Create

when it is done shutdown the computer.





Make an iso Backup of the primary Windows partition:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

the SSD that you just got ready and

the original SSD with the affected windows install.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and two SSDs populated in the Disks app

select the SSD (its background should become orange)

look at its partitions; if there are multiple then it is the affected SSD

if not and you see the single bar; select the other ssd from the list on the left.

select the primary partition: the largest and most likely furtherest to the right (its background should become orange)

underneath the horizontal bar that depicts the disk partitions:

click the

gear

select:

Create Partition Image

enter a title for the partition backup image ( leave the .img extention )

Save in Folder: select the Other SSD we got ready earlier

start imaging / enter password to authorize when prompted.

When imaging is complete power down and remove the affected SSD, the SSD with the created image and the nvOC USB key  ( make sure you mark the SSD with the created image for reference )





Make an new Windows install:

make a new windows install on another SSD which is the same or larger capacity as the one with the lost first partition.

just the initial install (no need to update or anything); ensure the primary partition is same size or larger as the one on the disabled ssd

When this is done, power down the computer





Restore the iso Backup of the primary Windows partition over the new Windows installs Primary partition:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

the SSD that you just created the image on

ensure the SSD you just installed Windows on is still attached.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and two SSDs populated in the Disks app

select the SSD (its background should become orange)

look at its partitions; if there are multiple then it is the affected USB

if not and you see the single bar; select the other ssd from the list on the left.

select the primary partition: the largest and most likely furtherest to the right (its background should become orange)

underneath the horizontal bar that depicts the disk partitions:

click the

gear

select:

Restore Partition Image

Select the Created Image from the other SSD

Click:

Start Restoring

and enter password to authorize when prompted.

When restoration is complete power down and remove the SSD with the created image and the nvOC USB key




Boot the windows SSD and see if it is a working version of your original install.


There are faster ways to do this with less SSDs: this way should minimize errors and be safe.

Thank you @fullzero for that long and detailed fix, but I just ended up doing a new clean install of windows 8.

Sorry to waste your time but I couldn't wait so just went ahead and did it myself.

[newmz]

Hello, is anyone successfully using the Asrock Z87-Killer Socket 1150 motherboard with nvOC?

It has 7 PCIe sockets so I bought one hoping I could expand my 5 GPU rig to a 7 (Nvidia) GPU rig and get rid of some of my power hungry AMD R9 290s.

Any reason why it wont work?

[newmz]

I am seeing a new error i have not seen before.

There is no screen to be resumed matching miner.  

In the terminal window right before the miner of choice starts.  And the mining still does seem to start in the background.

Could it have something to do with a high resolution screen being present?

I have tried another image and the same thing occurred.

go to the quake terminal window and type "screen -r miner" and you should see your miner running

[newmz]

Why did my hash rate mining ETH on Claymore 9.7 go from 23.5 on Windows 7 down to 18.9 on nvOC?  I have the power set to 94 and the mc set to 825.  Is the latest driver that bad for 1060 cards? I am pretty sure I have the latest driver on Windows.

The OC curve for Linux is different than Windows.  You need to set a higher OC to get the same results in linux.  Also in Windows power limit is in % TDP; in linux it is in watts. 

Try a mc of 1000, then keep bumping it up until you see a soft crash.

If your 1060s have the standard TDP of 125: to set an equalivent power limit you need to use 0.87 * 125 (or whatever the exact TDP of your model is) = 109 watts

I have 2 1070s and 3 1060s. When mining eth, I set core overclock to -200 and memory overclock to 1300. I get approx 135mh/s whereas stock it's somewhere in the region of 95mh/s.

[hatch789]

Hi Guys,

There appears to be a bug with the Maxximus007_AUTO_TEMPERATURE_CONTROL. I verified in the nvoc0018 version and also in the updated patch to nv0018. I wanted to make sure the bug was still in the patched version before saying anything but now I have verified it is still there.

SO the bug is that whatever your individual power limit (MAIN ONE) is set to, is used only right in the beginning when the rig starts up. After the Maxximus007_AUTO_TEMPERATURE_CONTROL takes over it starts using whatever power limits are set in the INDIVIDUAL section.

The only way to fix this right now is set each individual power limit to whatever you want.

Obviously you have to restart 1bash for the new changes to take effect or reboot the rig.

[fullzero]

I would change

Code:

ZEC_PORT="3337"

to

Code:

ZEC_PORT="3333"

But your ZEC config looks like it should work with DwarfPool.

It is also worth trying removing the workername:

Code:

ZEC_WORKER="nv$IP_AS_WORKER"

to

Code:

ZEC_WORKER=""

With:

Also I have the error "Utilization is too low: restart 1bash" and multiple "Maxximus007_AUTO_TEMPERATURE_CONTROL" tabs. What it's mean? Maybe this is a reason of problem?

Due to some changes I made in the last 1bash; currently when in LOCAL mode: each restart of 1bash will kill the existing Maxximus007_AUTO_TEMPERATURE_CONTROL process, but not kill the tab containing it; then a new Maxximus007_AUTO_TEMPERATURE_CONTROL tab will be created with a new process inside.

The problem is likely that you are not connecting to the pool for some reason; when this happens the watchdog will detect low utilization and restart 1bash.  

You can see if you can reach the pool by opening a new guake tab and entering the following cmd:

Code:

ping zec-ru1.dwarfpool.com

I would try to use a different pool and see if you can connect.  For now while troubleshooting; I would set :

Code:

IAmNotAJeep_and_Maxximus007_WATCHDOG="NO"

fullzero, thank you for your reply. I'm sure that is no problem with connection to the pool, also ping is ok. I think it's a some problem with powerlimit, because when I disabled watchdog and trying to change some parameters, include powerlimit, my hashrate is growing to 200 Sol/s, also when I changed some parameters I seen my hashrate grow to 400 Sol/s, but I don't remember parameters what I changed. So at this moment I have hashrate 200 Sol/s with powerlimit 200, when I trying to change it to 250 I have lower hashrate. Cc 150, mc 900 as you wrote in the first message here. Also console showed power consumption lower than I set powerlimit. Any idea?

If you are using the Maxximus007_AUTO_TEMPERATURE_CONTROL  ensure you are also changing the individual powerlimits for each GPU:

Code:

INDIVIDUAL_POWERLIMIT_0=75

INDIVIDUAL_POWERLIMIT_1=75

INDIVIDUAL_POWERLIMIT_2=75

for a 1080ti I recommend using between a 200 and 225 powerlimit.

If you have already done this:

It is also possible there are some bad sectors on your USB key and they are causing problems.  I have had 5x USB keys go bad so far; although I do reimage a lot with test rigs.

It might be a good idea to try using another USB key or SSD.

[fullzero]

I am experiencing the exact same problems almost verbatim as the poster above. I was thinking it is related to a bad flash drive possibly. I am trying a different one. Also version 14 and 15 seem to work better than 17 and 18. I am getting lag and freezes and random reboots just trying to use you ubuntu with no mining software running.

Let me know if you have the same problems with a different USB key or SSD.

[fullzero]

How about the option to set auto shutdown when the power button is pressed?  I often need to move rigs and want to shut them down without plugging in or remoting in.

I have been running the following:

gsettings set org.gnome.settings-daemon.plugins.power button-power 'shutdown'

cheers

If you hold down the power button for ( I believe it is 5 seconds it should shutdown) .  Is this shutdown different other than it acting immediately?

[fullzero]

I am seeing a new error i have not seen before.
There is no screen to be resumed matching miner.
In the terminal window right before the miner of choice starts.  And the mining still does seem to start in the background.

Yes, same problem.

I am seeing a new error i have not seen before.

There is no screen to be resumed matching miner. 

In the terminal window right before the miner of choice starts.  And the mining still does seem to start in the background.

Could it have something to do with a high resolution screen being present?

I have tried another image and the same thing occurred.

go to the quake terminal window and type "screen -r miner" and you should see your miner running

Have you set:

Code:

LOCALorREMOTE="REMOTE" 

if so then this is expected

as newmz indicated:

open a terminal and enter

Code:

screen -r miner

to attach the mining process

[fullzero]

Hello, is anyone successfully using the Asrock Z87-Killer Socket 1150 motherboard with nvOC?

It has 7 PCIe sockets so I bought one hoping I could expand my 5 GPU rig to a 7 (Nvidia) GPU rig and get rid of some of my power hungry AMD R9 290s.

Any reason why it wont work?

Most likely you need the system files for the z87 chipset.  I don't have one; so the image doesn't have those files.

[WarwickNZ]

Would it be possible/easy to please add/explain how I can add a Genoil switch for EXP? It seems to default to claymore...

Thanks!

[fullzero]

Hi @fullzero

when I recently upgraded my rig to run nvOC 0018, it did something nasty to an ssd that was connected to the rig which had a Windows 8.1 install on it. I remember reading something after it booted about how it was doing something to Windows partitions, and now if I remove the USB stick so the BIOs tries to boot from the SSD it says something like "NO OPERATING SYSTEM INSTALLED".

I do like to be able to swap to Windows to try out different things - do you have any idea how I may be able to repair the SSD so Windows will boot again? Or do I just have to go through the pain of installing it from scratch and unplug it when I use nvOC?

Install from scratch.

Then make sure it is not attached or you will kill it

BUMMER! A warning would have been nice.

Newmz, I had the identical thing happen to me. Most likely what happened is the boot record was wiped out on the hard drive where you had windows installed. I have not tried to recover mine yet but it should be a very simple thing. I would try something before taking philipma1957's advice; I would try putting a windows install disk into your DVD or USB key. Then run a recover. There is also (if I recall) an FSISK /MBR you can run.

I am going to try this myself but your windows partition should be fine, you're just missing an MBR. -No big deal really!

So give that some googling and you'll find it's easy to recover. Otherwise when I get to it this weekend. I will try to recover mine and let you know what I did to hopefully fix the issue.

My apologies; I had done a quick test to see if this would happen: but I realize now I needed to do a test with a standard option windows install; as I have used custom partitions will all the windows installs I have.  

I will add a warning to the OP; and add more logic to 2unix for v0019.

hatch789 is correct in that if you used a standard windows partition set; your primary ( C Drive ) partition is still on that SSD.  



A longer way to recover it with minimal risk ( and also make a backup of the primary partition ) You will need 3 additional SSDs of the same or larger capacity to do this:



Get SSD to be used as the primary partition backup ready:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

an SSD that is empty or has data / an install you are willing to delete.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and the SSD populate in the Disks app

select the SSD (its background should become orange)

at the top right of the application there is an icon with 3 horizontal lines

click this icon

and select Format Disk

set Erase to:  Quick

set Partioning to:  MBR / DOS

and Format the ssd

when it is done: underneath the orange horizontal bar that depicts the disk partitions:

click the

 +

set Erase to:  Quick

set Partitioning to:  NTFS

click Create

when it is done shutdown the computer.





Make an iso Backup of the primary Windows partition:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

the SSD that you just got ready and

the original SSD with the affected windows install.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and two SSDs populated in the Disks app

select the SSD (its background should become orange)

look at its partitions; if there are multiple then it is the affected SSD

if not and you see the single bar; select the other ssd from the list on the left.

select the primary partition: the largest and most likely furtherest to the right (its background should become orange)

underneath the horizontal bar that depicts the disk partitions:

click the

gear

select:

Create Partition Image

enter a title for the partition backup image ( leave the .img extention )

Save in Folder: select the Other SSD we got ready earlier

start imaging / enter password to authorize when prompted.

When imaging is complete power down and remove the affected SSD, the SSD with the created image and the nvOC USB key  ( make sure you mark the SSD with the created image for reference )





Make an new Windows install:

make a new windows install on another SSD which is the same or larger capacity as the one with the lost first partition.

just the initial install (no need to update or anything); ensure the primary partition is same size or larger as the one on the disabled ssd

When this is done, power down the computer





Restore the iso Backup of the primary Windows partition over the new Windows installs Primary partition:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

the SSD that you just created the image on

ensure the SSD you just installed Windows on is still attached.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and two SSDs populated in the Disks app

select the SSD (its background should become orange)

look at its partitions; if there are multiple then it is the affected USB

if not and you see the single bar; select the other ssd from the list on the left.

select the primary partition: the largest and most likely furtherest to the right (its background should become orange)

underneath the horizontal bar that depicts the disk partitions:

click the

gear

select:

Restore Partition Image

Select the Created Image from the other SSD

Click:

Start Restoring

and enter password to authorize when prompted.

When restoration is complete power down and remove the SSD with the created image and the nvOC USB key




Boot the windows SSD and see if it is a working version of your original install.


There are faster ways to do this with less SSDs: this way should minimize errors and be safe.

Thank you @fullzero for that long and detailed fix, but I just ended up doing a new clean install of windows 8.

Sorry to waste your time but I couldn't wait so just went ahead and did it myself.

np; I created the situation: so I needed to show a way out.  Especially if the primary partition contained important files.

I recommend backing up every drive you have locally; and not depending on cloud services.

[ijduncan]

I am seeing a new error i have not seen before.

There is no screen to be resumed matching miner.  

In the terminal window right before the miner of choice starts.  And the mining still does seem to start in the background.

Could it have something to do with a high resolution screen being present?

I have tried another image and the same thing occurred.

go to the quake terminal window and type "screen -r miner" and you should see your miner running

So it's by design then?

[fullzero]

Hi Guys,

There appears to be a bug with the Maxximus007_AUTO_TEMPERATURE_CONTROL. I verified in the nvoc0018 version and also in the updated patch to nv0018. I wanted to make sure the bug was still in the patched version before saying anything but now I have verified it is still there.

SO the bug is that whatever your individual power limit (MAIN ONE) is set to, is used only right in the beginning when the rig starts up. After the Maxximus007_AUTO_TEMPERATURE_CONTROL takes over it starts using whatever power limits are set in the INDIVIDUAL section.

The only way to fix this right now is set each individual power limit to whatever you want.

Obviously you have to restart 1bash for the new changes to take effect or reboot the rig.

With the big fix 1bash and files you should not need to: restart 1bash for the new changes to take effect or reboot the rig.

It is the case that when using Maxximus007_AUTO_TEMPERATURE_CONTROL:

Code:

POWERLIMIT="YES"     

POWERLIMIT_WATTS=75 

only are initially applied

and then autotemp uses the powerlimits from:

# Note you MUST set individual powerlimits if using Maxximus007_AUTO_TEMPERATURE_CONTROL

INDIVIDUAL_POWERLIMIT_0=75

INDIVIDUAL_POWERLIMIT_1=75

INDIVIDUAL_POWERLIMIT_2=75

INDIVIDUAL_POWERLIMIT_3=75

INDIVIDUAL_POWERLIMIT_4=75

INDIVIDUAL_POWERLIMIT_5=75

INDIVIDUAL_POWERLIMIT_6=75

INDIVIDUAL_POWERLIMIT_7=75

INDIVIDUAL_POWERLIMIT_8=75

INDIVIDUAL_POWERLIMIT_9=75

INDIVIDUAL_POWERLIMIT_10=75

INDIVIDUAL_POWERLIMIT_11=75

INDIVIDUAL_POWERLIMIT_12=75

INDIVIDUAL_POWERLIMIT_13=75

I realize this is overly complicated; I could change this in the next version. 

Right now I am leaning towards an individual GPU settings 1bash and a general GPU settings 1bash for the next version; which would both be in a folder in the windows partition.  Then members can use the the general unless they have a mixed rig.

[ijduncan]

How about the option to set auto shutdown when the power button is pressed?  I often need to move rigs and want to shut them down without plugging in or remoting in.

I have been running the following:

gsettings set org.gnome.settings-daemon.plugins.power button-power 'shutdown'

cheers

If you hold down the power button for ( I believe it is 5 seconds it should shutdown) .  Is this shutdown different other than it acting immediately?

My understanding, and I may be completely wrong. Is that holding the power button is the same as turning off the power.