Author

Topic: [ mining os ] nvoc - page 252. (Read 418546 times)

full member
Activity: 420
Merit: 106
https://steemit.com/@bibi187
August 29, 2017, 05:21:52 PM
So far nvOC0019 seems working good, i notice something weird, i actually lost 4 mh/s on my 8 x 1070 Asus compared to nvOC0018 on skunk algo, i use same miner as u input inside i assume, ccminer2.2 by tpruvot.

have you checked intensity??

Yeap i use -i 25 as usual i am between 29.5-30 before i was on 30-30.5
full member
Activity: 378
Merit: 104
nvOC forever
August 29, 2017, 05:14:52 PM
So far nvOC0019 seems working good, i notice something weird, i actually lost 4 mh/s on my 8 x 1070 Asus compared to nvOC0018 on skunk algo, i use same miner as u input inside i assume, ccminer2.2 by tpruvot.

have you checked intensity??
full member
Activity: 420
Merit: 106
https://steemit.com/@bibi187
August 29, 2017, 04:52:29 PM
So far nvOC0019 seems working good, i notice something weird, i actually lost 4 mh/s on my 8 x 1070 Asus compared to nvOC0018 on skunk algo, i use same miner as u input inside i assume, ccminer2.2 by tpruvot.
full member
Activity: 378
Merit: 104
nvOC forever
August 29, 2017, 04:39:59 PM
v0019 working solid so far. I jumped from v0017 so I missed some of the v0018 features.

I turned on Watchdog but I'm not sure if I need to tweak any settings. Is it as simple as just selecting "YES" in the one bash or do I need to change the settings in the IAmNotAJeep_and_Maxximus007_WATCHDOG file?
Its fine, no need to change settings.
newbie
Activity: 53
Merit: 0
August 29, 2017, 04:36:24 PM
v0019 working solid so far. I jumped from v0017 so I missed some of the v0018 features.

I turned on Watchdog but I'm not sure if I need to tweak any settings. Is it as simple as just selecting "YES" in the one bash or do I need to change the settings in the IAmNotAJeep_and_Maxximus007_WATCHDOG file?
newbie
Activity: 28
Merit: 0
August 29, 2017, 04:21:53 PM
Interesting. Thank you - I will try that.

I guess I will need to learn how to SSH.
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
August 29, 2017, 04:14:27 PM
Hello again,

Once more, I am unsure if this is quite nvOC on-topic or not, but with so many variables to a mining rig, and as helpful as everyone has been, I am giving it a shot.

I currently have two ASRock H110 BTC+ Pro boards, each running 13 GTX 1060 6GB GPU's. It took me a while to get there, but after checking connections, settings, etc. I have one of these that has been mining ETH rock-solid for over a week now on ethminer (it isn't getting the nice boost I expected, but c'est la vie).

The second setup, however, I cannot seem to get to stay running. I swapped out the risers and get 13 GPU's showing every time now, switched to v0019, and generally can boot, mine for a few hours, then freeze. Of course when I am frozen there is not a lot I can do from a diagnostic perspective to figure out what might have gone wrong. I had thought given the fact that I would get a couple of hours might mean a temperature issue, but I don't know really. I just took a picture of the crashed rig (while it might look fine, it is frozen):



I am not close to maxing out my PSU's, I am using powered risers that I believe are all getting power (no more than 2 per cable), and I have tried swapping out risers,

My OC is not aggressive, with the core being underclocked by 200, and memory OC at only 500. Temperature was dialed back to 70c max, with the power max at 75w per card.

Does anyone have any idea what I might try next for a stable system.

I had reset the machine when I took that screenshot 40 minutes ago, and the rig just froze again. Any suggestions would be amazing.

Thanks!
Disable teamviewer and check.
Its linux, better use ssh when u need to do anything.
sr. member
Activity: 1414
Merit: 487
YouTube.com/VoskCoin
August 29, 2017, 03:57:02 PM
What is the process of remoting in w/ nvoc19
newbie
Activity: 28
Merit: 0
August 29, 2017, 03:44:33 PM
Hello again,

Once more, I am unsure if this is quite nvOC on-topic or not, but with so many variables to a mining rig, and as helpful as everyone has been, I am giving it a shot.

I currently have two ASRock H110 BTC+ Pro boards, each running 13 GTX 1060 6GB GPU's. It took me a while to get there, but after checking connections, settings, etc. I have one of these that has been mining ETH rock-solid for over a week now on ethminer (it isn't getting the nice boost I expected, but c'est la vie).

The second setup, however, I cannot seem to get to stay running. I swapped out the risers and get 13 GPU's showing every time now, switched to v0019, and generally can boot, mine for a few hours, then freeze. Of course when I am frozen there is not a lot I can do from a diagnostic perspective to figure out what might have gone wrong. I had thought given the fact that I would get a couple of hours might mean a temperature issue, but I don't know really. I just took a picture of the crashed rig (while it might look fine, it is frozen):

https://s26.postimg.org/4ybqdi7s9/2017-08-29_16.02.08.jpg

I am not close to maxing out my PSU's, I am using powered risers that I believe are all getting power (no more than 2 per cable), and I have tried swapping out risers,

My OC is not aggressive, with the core being underclocked by 200, and memory OC at only 500. Temperature was dialed back to 70c max, with the power max at 75w per card.

Does anyone have any idea what I might try next for a stable system.

I had reset the machine when I took that screenshot 40 minutes ago, and the rig just froze again. Any suggestions would be amazing.

Thanks!
newbie
Activity: 31
Merit: 0
August 29, 2017, 11:23:29 AM
Is it normal that every time upPASTE reload config it start a new instance of 1bash ?

Code:
m1@m1-desktop-102:~$ ps aux | grep 1bash
m1        2201  0.0  0.0  13320  3876 pts/16   S+   11:43   0:00 bash /home/m1/1bash
m1        4482  0.0  0.0  13328  3840 pts/23   S+   12:14   0:00 bash /home/m1/1bash
m1       18432  0.0  0.0  13328  3836 pts/24   S+   16:18   0:00 bash /home/m1/1bash

Code:
m1@m1-desktop-101:~$ ps aux | grep 1bash
m1       13545  0.0  0.0  13324  3888 pts/17   S+   16:23   0:00 bash /home/m1/1bash
m1       13546  0.0  0.0  13332  3820 pts/23   S+   16:23   0:00 bash /home/m1/1bash
m1       13547  0.0  0.0  13328  3892 pts/21   S+   16:23   0:00 bash /home/m1/1bash


Problem is some times it create multiple miners :

Code:
m1@m1-desktop-101:~$ screen -r  miner
There are several suitable screens on:
14358.miner (08/29/17 16:23:44) (Detached)
14348.miner (08/29/17 16:23:44) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and multiple temp too

Code:
m1@m1-desktop-101:~$ screen -r temp
There are several suitable screens on:
13837.temp (08/29/17 16:23:36) (Detached)
13830.temp (08/29/17 16:23:36) (Detached)
13823.temp (08/29/17 16:23:36) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

The multiple miners only happens on one of my rigs, the other one dont have this issue.
Both has multiple 1bash running but one make multiple miners.
Sorry if I misunderstand.
In v19 you need to run 3main instead of 1bash or run 2unix to refresh the whole
no you don't, you just run 1bash as normal, 1bash has been split into 2 parts (1bash and 3main), where 1bash is a config file and 3main holds all the back end (for people who are not interested in editing it)
At v19 1bash is only a configuration file, there is absolutely no command to run the application in it: D
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
August 29, 2017, 10:40:19 AM
Is it normal that every time upPASTE reload config it start a new instance of 1bash ?

Code:
m1@m1-desktop-102:~$ ps aux | grep 1bash
m1        2201  0.0  0.0  13320  3876 pts/16   S+   11:43   0:00 bash /home/m1/1bash
m1        4482  0.0  0.0  13328  3840 pts/23   S+   12:14   0:00 bash /home/m1/1bash
m1       18432  0.0  0.0  13328  3836 pts/24   S+   16:18   0:00 bash /home/m1/1bash

Code:
m1@m1-desktop-101:~$ ps aux | grep 1bash
m1       13545  0.0  0.0  13324  3888 pts/17   S+   16:23   0:00 bash /home/m1/1bash
m1       13546  0.0  0.0  13332  3820 pts/23   S+   16:23   0:00 bash /home/m1/1bash
m1       13547  0.0  0.0  13328  3892 pts/21   S+   16:23   0:00 bash /home/m1/1bash


Problem is some times it create multiple miners :

Code:
m1@m1-desktop-101:~$ screen -r  miner
There are several suitable screens on:
14358.miner (08/29/17 16:23:44) (Detached)
14348.miner (08/29/17 16:23:44) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and multiple temp too

Code:
m1@m1-desktop-101:~$ screen -r temp
There are several suitable screens on:
13837.temp (08/29/17 16:23:36) (Detached)
13830.temp (08/29/17 16:23:36) (Detached)
13823.temp (08/29/17 16:23:36) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

The multiple miners only happens on one of my rigs, the other one dont have this issue.
Both has multiple 1bash running but one make multiple miners.
Sorry if I misunderstand.
In v19 you need to run 3main instead of 1bash or run 2unix to refresh the whole
no you don't, you just run 1bash as normal, 1bash has been split into 2 parts (1bash and 3main), where 1bash is a config file and 3main holds all the back end (for people who are not interested in editing it)


this is on v0018, not migrating to 19 yet.
full member
Activity: 378
Merit: 104
nvOC forever
August 29, 2017, 09:14:08 AM
Is it normal that every time upPASTE reload config it start a new instance of 1bash ?

Code:
m1@m1-desktop-102:~$ ps aux | grep 1bash
m1        2201  0.0  0.0  13320  3876 pts/16   S+   11:43   0:00 bash /home/m1/1bash
m1        4482  0.0  0.0  13328  3840 pts/23   S+   12:14   0:00 bash /home/m1/1bash
m1       18432  0.0  0.0  13328  3836 pts/24   S+   16:18   0:00 bash /home/m1/1bash

Code:
m1@m1-desktop-101:~$ ps aux | grep 1bash
m1       13545  0.0  0.0  13324  3888 pts/17   S+   16:23   0:00 bash /home/m1/1bash
m1       13546  0.0  0.0  13332  3820 pts/23   S+   16:23   0:00 bash /home/m1/1bash
m1       13547  0.0  0.0  13328  3892 pts/21   S+   16:23   0:00 bash /home/m1/1bash


Problem is some times it create multiple miners :

Code:
m1@m1-desktop-101:~$ screen -r  miner
There are several suitable screens on:
14358.miner (08/29/17 16:23:44) (Detached)
14348.miner (08/29/17 16:23:44) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and multiple temp too

Code:
m1@m1-desktop-101:~$ screen -r temp
There are several suitable screens on:
13837.temp (08/29/17 16:23:36) (Detached)
13830.temp (08/29/17 16:23:36) (Detached)
13823.temp (08/29/17 16:23:36) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

The multiple miners only happens on one of my rigs, the other one dont have this issue.
Both has multiple 1bash running but one make multiple miners.
Sorry if I misunderstand.
In v19 you need to run 3main instead of 1bash or run 2unix to refresh the whole
no you don't, you just run 1bash as normal, 1bash has been split into 2 parts (1bash and 3main), where 1bash is a config file and 3main holds all the back end (for people who are not interested in editing it)
sr. member
Activity: 861
Merit: 281
August 29, 2017, 08:34:44 AM
Hi all,

Hopefully this is not too off-topic, but in trying to get the latest ethminer working in nvOC (at the speeds expected for my GTX 1060 6gb cards), I had also been posting on their Github page. I am trying to figure out a few things, and would love to hear what you all have to say:

  • Someone on that thread suggested that with Linux-based mining, the overclock settings for memory people throw around (which, most things I read are for Windows) need to be doubled. As in, people usually say Samsung memory can get around an 850 memory OC, so they were saying for Ubuntu I would go with 1700? This felt wrong given the 1bash defaults, but I'd love verification
  • Is there any way anyone knows, without doing a Windows install, to learn what kind of memory my cards have? I'd rather not install Windows, and I have 26 cards I'd like to verify without changing their order or disconnecting if possible. I have not been successful in finding a Linux utility, but feel I may benefit from indvidual clock tuning
  • Has anyone gotten the 24-25 Mh/s the latest ethminer supposedly gets while using in nvOC? If so, what settings are you using?

I appreciate the input, as well as the fact that this build even exists, so any help here would be amazing.

Hi JudoFlash,

  • You are totally right for memory in linux, cause in linux u dont OC MemClock technically you OC MemoryTransferRate. MemClock = MemoryTransferRate % 2
  • Unfortunately on linux we don't have software that allow you to get memory brand version, easy way to do this is to boot your rig on a single windows card per card Wink
  • For this last one i dont have 1060, but i bet with nice OC u can grab this one. Remember to negative your CoreClock when u mine ETH Wink

Don't hesitate to ask more Wink

Well, Thank you for that explanation. I was trying to figure out on how the actual OC works on Linux but your post made it clear.
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
August 29, 2017, 08:34:06 AM












nvOC_v0019 Google Drive Link use this image for all mobos



nvOC_v0019 MEGA I will upload to mega later Link use this image for all mobos



Note: you still need to implement bios setting changes.  The SHA256 hash (for the zip) is:
Code:
9f461a33051568425f616a265d7811b6c3372f61bbcfdbae7d50fb627c57fb38

To verify the downloaded zip see this post Link


NOTE: You only need to configure the 1bash file in the Windows Partition.  If you don't have a text editor with syntax highlighting: open it with wordpad.  

I recommend downloading atom if you don't have a text editor with syntax highlighting .

Change OC and addresses to desired / your own.

When you are done configuring 1bash ensure that you save, then eject the USB.

Attach the USB key to your rig and power it on.

NOTE: first boot will take longer to start mining as 1bash must be converted

All files are in the nvOC folder Link.

nvOC uses the 384.47 Driver.

the root password for nvOC is:

    miner1






This is a short version of first post with links to the nv0019  download.  I have yet to download nv0019  will do so today.

full member
Activity: 420
Merit: 106
https://steemit.com/@bibi187
August 29, 2017, 08:19:38 AM
Is it normal that every time upPASTE reload config it start a new instance of 1bash ?

Code:
m1@m1-desktop-102:~$ ps aux | grep 1bash
m1        2201  0.0  0.0  13320  3876 pts/16   S+   11:43   0:00 bash /home/m1/1bash
m1        4482  0.0  0.0  13328  3840 pts/23   S+   12:14   0:00 bash /home/m1/1bash
m1       18432  0.0  0.0  13328  3836 pts/24   S+   16:18   0:00 bash /home/m1/1bash

Code:
m1@m1-desktop-101:~$ ps aux | grep 1bash
m1       13545  0.0  0.0  13324  3888 pts/17   S+   16:23   0:00 bash /home/m1/1bash
m1       13546  0.0  0.0  13332  3820 pts/23   S+   16:23   0:00 bash /home/m1/1bash
m1       13547  0.0  0.0  13328  3892 pts/21   S+   16:23   0:00 bash /home/m1/1bash


Problem is some times it create multiple miners :

Code:
m1@m1-desktop-101:~$ screen -r  miner
There are several suitable screens on:
14358.miner (08/29/17 16:23:44) (Detached)
14348.miner (08/29/17 16:23:44) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and multiple temp too

Code:
m1@m1-desktop-101:~$ screen -r temp
There are several suitable screens on:
13837.temp (08/29/17 16:23:36) (Detached)
13830.temp (08/29/17 16:23:36) (Detached)
13823.temp (08/29/17 16:23:36) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

The multiple miners only happens on one of my rigs, the other one dont have this issue.
Both has multiple 1bash running but one make multiple miners.

When upPASTE see modification between your 1bash and 1bash, he trigger a reboot of the process.
So are u sure u put right address of your upPASTE ?
That prolly from some weird permissions u cant kill your miner running. I got this trouble with multi launching miner. A new install fixed this Smiley
newbie
Activity: 31
Merit: 0
August 29, 2017, 08:06:14 AM
Is it normal that every time upPASTE reload config it start a new instance of 1bash ?

Code:
m1@m1-desktop-102:~$ ps aux | grep 1bash
m1        2201  0.0  0.0  13320  3876 pts/16   S+   11:43   0:00 bash /home/m1/1bash
m1        4482  0.0  0.0  13328  3840 pts/23   S+   12:14   0:00 bash /home/m1/1bash
m1       18432  0.0  0.0  13328  3836 pts/24   S+   16:18   0:00 bash /home/m1/1bash

Code:
m1@m1-desktop-101:~$ ps aux | grep 1bash
m1       13545  0.0  0.0  13324  3888 pts/17   S+   16:23   0:00 bash /home/m1/1bash
m1       13546  0.0  0.0  13332  3820 pts/23   S+   16:23   0:00 bash /home/m1/1bash
m1       13547  0.0  0.0  13328  3892 pts/21   S+   16:23   0:00 bash /home/m1/1bash


Problem is some times it create multiple miners :

Code:
m1@m1-desktop-101:~$ screen -r  miner
There are several suitable screens on:
14358.miner (08/29/17 16:23:44) (Detached)
14348.miner (08/29/17 16:23:44) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and multiple temp too

Code:
m1@m1-desktop-101:~$ screen -r temp
There are several suitable screens on:
13837.temp (08/29/17 16:23:36) (Detached)
13830.temp (08/29/17 16:23:36) (Detached)
13823.temp (08/29/17 16:23:36) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

The multiple miners only happens on one of my rigs, the other one dont have this issue.
Both has multiple 1bash running but one make multiple miners.
Sorry if I misunderstand.
In v19 you need to run 3main instead of 1bash or run 2unix to refresh the whole
newbie
Activity: 11
Merit: 0
August 29, 2017, 07:48:57 AM
Did anyone successfully set up teamviewer with custom resolutions without monitor(or dummy plug) on a headless rig?

Try
http://imgur.com/a/mzMNB

doesn't work on headless machine, resolution is 640X480
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
August 29, 2017, 06:55:20 AM
Is it normal that every time upPASTE reload config it start a new instance of 1bash ?

Code:
m1@m1-desktop-102:~$ ps aux | grep 1bash
m1        2201  0.0  0.0  13320  3876 pts/16   S+   11:43   0:00 bash /home/m1/1bash
m1        4482  0.0  0.0  13328  3840 pts/23   S+   12:14   0:00 bash /home/m1/1bash
m1       18432  0.0  0.0  13328  3836 pts/24   S+   16:18   0:00 bash /home/m1/1bash

Code:
m1@m1-desktop-101:~$ ps aux | grep 1bash
m1       13545  0.0  0.0  13324  3888 pts/17   S+   16:23   0:00 bash /home/m1/1bash
m1       13546  0.0  0.0  13332  3820 pts/23   S+   16:23   0:00 bash /home/m1/1bash
m1       13547  0.0  0.0  13328  3892 pts/21   S+   16:23   0:00 bash /home/m1/1bash


Problem is some times it create multiple miners :

Code:
m1@m1-desktop-101:~$ screen -r  miner
There are several suitable screens on:
14358.miner (08/29/17 16:23:44) (Detached)
14348.miner (08/29/17 16:23:44) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and multiple temp too

Code:
m1@m1-desktop-101:~$ screen -r temp
There are several suitable screens on:
13837.temp (08/29/17 16:23:36) (Detached)
13830.temp (08/29/17 16:23:36) (Detached)
13823.temp (08/29/17 16:23:36) (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

The multiple miners only happens on one of my rigs, the other one dont have this issue.
Both has multiple 1bash running but one make multiple miners.
newbie
Activity: 11
Merit: 0
August 29, 2017, 06:21:45 AM
So, v019 is more stable than 018. Thank a lot.
However, I still have a problem with a screen
http://imgur.com/a/UDHzF
Moreover to many times a detected all cards (12th cards is detected after 1-2min after 1st one and watchdog become said about low utilisation).
Also, in terminal, screen is not working and in best way if it will show in guake(f12) after writing "screen -r", but sometimes it also wrote that "there is no screen to be resumed".
newbie
Activity: 11
Merit: 0
August 29, 2017, 06:12:18 AM
v0019 is up on Google Drive see the OP for the Link:

I will upload to MEGA after sleeping.


Lots of changes I will update the OP after sleeping.


the SHA256 hash is:

Code:
9f461a33051568425f616a265d7811b6c3372f61bbcfdbae7d50fb627c57fb38


If you are using windows:


open a cmd prompt:

click the start button and type: 

Code:
cmd

then press enter:

type the following:

Code:
CertUtil -hashfile PATH_TO_IMAGE_ZIP_HERE SHA256

and press enter

if the result is:

Code:
9f461a33051568425f616a265d7811b6c3372f61bbcfdbae7d50fb627c57fb38

then the ZIP_containing_the_image is good

Note: you can find the file path by right clicking the zip and selecting properties


If you are using linux:

open a terminal and enter the following:

Code:
sha256sum 'PATH_TO_IMAGE_ZIP_HERE'

and press enter

if the result is:
Code:
9f461a33051568425f616a265d7811b6c3372f61bbcfdbae7d50fb627c57fb38

then the ZIP_containing_the_image is good

Note: you can also type sha256sum then drag the zip to the terminal window to add the absolute path without typing it.


If you are using OSX:

open a terminal and enter the following:

Code:
shasum -a 256 'PATH_TO_IMAGE_ZIP_HERE'

and press enter

if the result is:
Code:
9f461a33051568425f616a265d7811b6c3372f61bbcfdbae7d50fb627c57fb38

then the ZIP_containing_the_image is good




Thank you fullzero!
I'll wait for change log if it's worth migrating from 18 to 19.
Jump to: