[ mining os ] nvoc - page 157. | Bitcointalksearch.org

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Any one has kworker high cpu usage ?
Any idea how to solve it ?

Code:

PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 1797 root      20   0       0      0      0 S  44.9  0.0   0:53.41 kworker/3:16
 6504 root      20   0       0      0      0 R  21.0  0.0   0:40.13 kworker/3:2
 6751 m1        20   0  0.170t 1.165g 0.982g S   5.6 15.0   1:27.05 ethminer

Stubo

member

Activity: 224

Merit: 13

So, in my effort to thoroughly understand nvOC at a reasonably low level, I am stumped by one question. What is calling/launching 2unix at boot and again if 3main is killed and 2unix "falls out"?

It appears to be part of gnome-session but I am not yet familiar enough with Ubuntu to find it. I see the auto login setup in /etc/lightdm/lightdm.conf but I don't see anything launching that explicitly in .bashrc or .profile. What am I missing?

Thanks in advance.

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: Stubo on October 31, 2017, 02:43:20 PM

Quote from: burntone on October 31, 2017, 01:39:27 PM

Also, can I update to the latest Claymore`s (https://bitcointalksearch.org/topic/claymores-dual-ethereum-amdnvidia-gpu-miner-v150-windowslinux-1433925) without breaking something in nvOC?

Thanks!

I just looked into this. nvOC 19-1.4 includes version 10.0 of this miner. If you want the latest as per the link, then you can download the binary (was surprised they had it instead of just source). Then you need to create subdirectory "10_1" in /home/m1/eth on your miner, put the downloaded file here and unzip/untar it. Lastly, you need to modify this line of your 1bash to use it:

Code:

CLAYMORE_VERSION="10_0"    # choose 10_0  or  9_8  or  9_7  or  9_5  or  9_4  or  8_0

to

CLAYMORE_VERSION="10_1"    # choose 10_0  or  9_8  or  9_7  or  9_5  or  9_4  or  8_0

Hope this helps.

Perfect @Stubo, feels amazing how big our community has grown and number of people supporting others has tremendously grown recently.

Quote

nvOC - Together we make it Better

This line suits nvOC

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: papampi on November 01, 2017, 06:13:49 AM

Quote from: leenoox on October 31, 2017, 11:40:38 PM

Quote from: papampi on October 31, 2017, 03:27:47 PM

So which memories are the good and which one are bad ?
I know Samsung is good, but other good ones ?

Samsung memory is best, then Micron, then Hynix.
From my experience with 1060's mining ETH
Samsung: 25 MH/s
Micron: 22 MH/s
Hynix: 19 MH/s

Unfortunately there is no way to check memory vendor under linux (yet). You have to check under Windows with GPU-Z

Thanks a lot mate
looks like I should setup a windows on an ssd to test the new cards

We could also possibly check them by testing out the various OC settings available, based on the stable results you get, you can decide which manufacturer does the memory belongs to.

Pick a card, start with samsung OC, it will fail in the first run if its not, then try with Micron, FAIL?, then Hynix.

I propose this only for people who don't have Windows machine or who don't have physical access to RIG!!

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: hurvajs77 on November 01, 2017, 12:45:03 PM

@damNmad:

I found a small bug in your telegram configuration. Command which use for getting GPUs count is invalid when rig have installed over 9 cards...

Your command:

Code:

GPU_COUNT=$(nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }'
2

There isn't any reason, why use awk. Easier way is use wc only.

So, fix:

Code:

GPU_COUNT=$(nvidia-smi -L | wc -l')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | wc -l
11

Thanks for pointing this out, i will update it, basically I had that for my 8 GPU rig, so never had issues with it, but now lots of people started using it, so i need to update it

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: medi91 on November 02, 2017, 01:38:17 AM

Quote from: papampi on November 01, 2017, 06:11:38 AM

Quote from: medi91 on October 31, 2017, 08:26:45 PM

Quote from: leenoox on October 30, 2017, 08:43:55 PM

Quote from: medi91 on October 30, 2017, 08:20:49 PM

Tried my best to search for an answer, but no luck so far...

has anyone successfully gotten rid of the login loop issue?

Ive console logged in, did a re-image, tried different versions, and every ubuntu based fix i could find online (clear and .Xauthority fixes)

Board is a HP z400 board

Try this:
press CTRL- ALT- F1 together, terminal window will open. Login as m1, pass miner1

type:

Code:

sudo apt update && sudo apt upgrade && sudo reboot

Please reply with results

Unfortunately did not get rid of the login loop

Broken nvidia driver

Code:

sudo dpkg-reconfigure --all

Is there something in that dpkg menu to select in particular?

It should be nvidia-387 or nvidia-384 that are broken because wdog restart system when dpkg was running

thaelin

newbie

Activity: 64

Merit: 0

@medi91
I did the disable updates patch and now run stable. I do get a popup that says updates are available but just dismiss.
I am by the way still at ver 19.1.2 but works so why mess with it until a 20 stable comes out.

At least now I know what caused this before when I tried to use 16.04 LTS for mining zcash. Just a broken update in the
background.

thay

medi91

newbie

Activity: 13

Merit: 0

Quote from: papampi on November 01, 2017, 06:11:38 AM

Quote from: medi91 on October 31, 2017, 08:26:45 PM

Quote from: leenoox on October 30, 2017, 08:43:55 PM

Quote from: medi91 on October 30, 2017, 08:20:49 PM

Tried my best to search for an answer, but no luck so far...

has anyone successfully gotten rid of the login loop issue?

Ive console logged in, did a re-image, tried different versions, and every ubuntu based fix i could find online (clear and .Xauthority fixes)

Board is a HP z400 board

Try this:
press CTRL- ALT- F1 together, terminal window will open. Login as m1, pass miner1

type:

Code:

sudo apt update && sudo apt upgrade && sudo reboot

Please reply with results

Unfortunately did not get rid of the login loop

Broken nvidia driver

Code:

sudo dpkg-reconfigure --all

Is there something in that dpkg menu to select in particular?

Stubo

member

Activity: 224

Merit: 13

Quote from: papampi on November 01, 2017, 04:52:09 PM

dstm zminer 5.3 is amazing,

I just rolled it out to my miners mining ZEC and I am not overly impressed once the miner reaches steady state. The initial numbers are pretty impressive but after a few minutes, it settles in to just about where 5.2 was, perhaps just a tick higher. My GPUs consist of 1070's and 1080 Ti's only.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

dstm zminer 5.3 is amazing,
I was getting 270 sol/s with EWBF on 1060 now getting 290

Version 0.5.3
cpu: reduce cpu load
con: fix recon loop
con: network latency measurement
ui: add accepted/rejected shares ratio
ui: add network latency
ui: add information about selected devices

Linux x64:
sha1 0583d59930a6160f80db612eae089c84712b5f44
https://drive.google.com/file/d/0B5QcL4Z6nYEPcHRuZk5LV3NXOUE

Download
Easy workaround :
Put it in

Code:

/home/m1/zec/zm/5_2

then

Code:

chmod +x /home/m1/zec/zm/5_2/zm_miner

Or put it in

Code:

/home/m1/zec/zm/5_3

and change all 3main zm lines from 5_2 to 5_3

Code:

HCD='/home/m1/zec/zm/5_3/zm_miner'

then

Code:

chmod +x /home/m1/zec/zm/5_3/zm_miner

MentalNomad

member

Activity: 83

Merit: 10

Quote from: BlackwidowZA on November 01, 2017, 03:56:52 PM

Hi all

Just a quick question if a new miner version comes out does nvOC automatically download the new miner or only when there is a new nvoc system update and you knew about it to include?

Miner updates are not automatic on nvOC.

BlackwidowZA

newbie

Activity: 14

Merit: 0

Hi all

Just a quick question if a new miner version comes out does nvOC automatically download the new miner or only when there is a new nvoc system update and you knew about it to include? I’m asking as it seems that dstm zm miner is getting a lot of updates the past few weeks

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: hurvajs77 on November 01, 2017, 12:45:03 PM

@damNmad:

I found a small bug in your telegram configuration. Command which use for getting GPUs count is invalid when rig have installed over 9 cards...

Your command:

Code:

GPU_COUNT=$(nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }'
2

There isn't any reason, why use awk. Easier way is use wc only.

So, fix:

Code:

GPU_COUNT=$(nvidia-smi -L | wc -l')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | wc -l
11

I used to use same cmd, fixed it with this one for 1.4:

Code:

nvidia-smi --query-gpu=count --format=csv,noheader,nounits | tail -1

hurvajs77

newbie

Activity: 46

Merit: 0

@damNmad:

I found a small bug in your telegram configuration. Command which use for getting GPUs count is invalid when rig have installed over 9 cards...

Your command:

Code:

GPU_COUNT=$(nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1} ; { print SUM }'
2

There isn't any reason, why use awk. Easier way is use wc only.

So, fix:

Code:

GPU_COUNT=$(nvidia-smi -L | wc -l')

and result:

Code:

m1@rig-bafomet:~$ nvidia-smi -L | wc -l
11

Stubo

member

Activity: 224

Merit: 13

Quote from: leenoox on November 01, 2017, 08:20:04 AM

Great idea!!!

The one minor tweak I made to beautify_bash.py is to the indentation. I have always used 3 spaces whereas the script uses 2. Of course, I read it and it is very easy to change to your own liking. Just change:

Code:

self.tab_size = 2

to

Code:

self.tab_size = 3

on line 33.

leenoox

full member

Activity: 200

Merit: 101

Quote from: kk003 on November 01, 2017, 07:20:26 AM

Quote from: Stubo on November 01, 2017, 06:28:11 AM

I have been spending a bit of time reading through all of the bash scripts that make up nvOC. I urge everybody to do that because then you will learn both how it works and how you may be to take advantage of some of the vast functionality that is offered. To make that easier to do, I found a python script "beautify_bash.py" that you can run against them (1bash, 2unix, 3main, etc.) to make them more readable.

https://github.com/ewiger/beautify_bash

It basically just reformats the code with the proper syntax indentation for loops and if statements. The first thing that I did with the 19-1.4 release the other day was to beautify all of the scripts, then make my personal miner tweaks to those versions and finally deploy those to my miners. I have found no issues from doing this. The basic steps to get it going are:

-Download the zip file to your PC, unzip it to get to beautify_bash.py
-Use WinSCP or suitable substitute to sftp it down to your rig(s) in /home/m1 directory
-Login to rig, make the script executable "chmod 750 beautify_bash.py"
-Execute against the scripts you use:
./beautify_bash.py 1bash
./beautify_bash.py 2unix
./beautify_bash.py 3main
./beautify_bash.py 4update
./beautify_bash.py IAmNotAJeep_and_Maxximus007_WATCHDOG
..etc

It will beautify the script and leave a copy of the original as ~. Perhaps there is some reason for releasing the scripts with no syntax formatting as they are but I have yet to find it.

Hope this helps.

I hate mal formated scripts such as when I upload a well formated one to pastebin.com and it makes a mess of it.
This will help, thx.

Great idea!!!

leenoox

full member

Activity: 200

Merit: 101

Quote from: kk003 on November 01, 2017, 06:36:43 AM

Quote from: papampi on November 01, 2017, 02:23:36 AM

Quote from: leenoox on November 01, 2017, 12:56:19 AM

It's really nice to add more features to nvOC and I would encourage everyone to try and contribute to this great project but I would strongly advice against using unnecessary extreme writing in logs to accomplish the proposed feature. Especialy recording the screen in screenlog...

You see people complainig every day of corrupted USB sticks, freezing, running out of space, boot problems, etc. USB stick as a medium is not designed for such operations, constant writing to USB stick is not recommended, it messes the controller, makes USB perform very slow after a while and kills memory cells which leads to corruption and lock-ups.

If nvOC was explicitly recommended as SSD/HDD OS, the logs would be fine but the reality is that 90% of people use nvOC from USB sticks.

To all devs: please avoid usage of logs as much as possible or at least log as little as possible.

Hint: if you want to show output from the miner in your script/program/telegram/web page (definetely a nice feature to show), record the output from the miner (or nvidia api) into memory then show it in your program on a per need basis. This is more easily done with PHP and Perl but it can be accomplished in Bash as well. Record stdout and stderr into rotating array (you can use shift for the array). You can record 10, 20, 100, even 500 lines and you won't run out of memory, then show the live output from the array into your featured program.

We miners are spending thousands on our rigs and when it comes to stability and life span we forget the most important part and thats where the OS is installed on, we think small and go cheap with a 5-10$ USB when we can have much smoother system with a 30$ SSD.

Using USB as daily use is not recommended in any distro, The most important difference other than USB read/write limit is there's no way for a USB drive to mark bad cells as 'do not use' whereas the SSD may develop bad areas it can ignore them. With a USB drive one cell goes bad and the whole drive is useless.

I'm Not saying that you shouldn't use a USB for bootable OS, just that it's not a good idea to have it as your main boot drive and only use them for diagnostic / testing purposes.
No mining system should be run from USB as a daily hardcore mining system, but run it on usb, test OS and see if you like it, then install it on SSD.

I think mining with nvOC on USB is only good for those who want to mine when their pc is not in use, so they boot with usb, mine for a while then reboot back to their main OS...

I agree. I have to say that if system is using a hdd or ssd (better) it should not have any problem with log files as long as the system is healthy. If system has a very high cpu load/gpu instability etc, then is better not to log, at less in a productive system.
Linux is good at login but system must be healthy.
Got a rig (installed in a old hdd) with high cpu load (2 cores and 2.5 cpu load average) and log files for miners go around 150MB+... no problem. I don't think this would work on a usb stick.

I agree, nvOC should be run from SSD and USB sticks should be used for evaluation or short term use only. Maybe fullzero should note/recommend this in the OP.

However, as a programmers we should do due diligence and optimize the code to run as smooth as possible including running off USB sticks Wink

kk003

member

Activity: 117

Merit: 10

Quote from: Stubo on November 01, 2017, 06:28:11 AM

I have been spending a bit of time reading through all of the bash scripts that make up nvOC. I urge everybody to do that because then you will learn both how it works and how you may be to take advantage of some of the vast functionality that is offered. To make that easier to do, I found a python script "beautify_bash.py" that you can run against them (1bash, 2unix, 3main, etc.) to make them more readable.

https://github.com/ewiger/beautify_bash

It basically just reformats the code with the proper syntax indentation for loops and if statements. The first thing that I did with the 19-1.4 release the other day was to beautify all of the scripts, then make my personal miner tweaks to those versions and finally deploy those to my miners. I have found no issues from doing this. The basic steps to get it going are:

-Download the zip file to your PC, unzip it to get to beautify_bash.py
-Use WinSCP or suitable substitute to sftp it down to your rig(s) in /home/m1 directory
-Login to rig, make the script executable "chmod 750 beautify_bash.py"
-Execute against the scripts you use:
./beautify_bash.py 1bash
./beautify_bash.py 2unix
./beautify_bash.py 3main
./beautify_bash.py 4update
./beautify_bash.py IAmNotAJeep_and_Maxximus007_WATCHDOG
..etc

It will beautify the script and leave a copy of the original as ~. Perhaps there is some reason for releasing the scripts with no syntax formatting as they are but I have yet to find it.

Hope this helps.

I hate mal formated scripts such as when I upload a well formated one to pastebin.com and it makes a mess of it.
This will help, thx.

cryptosg

newbie

Activity: 1

Merit: 0

Hi anyone know to connect to Ubiq pool?

UBQ_WORKER=$WORKERNAME
UBQ_ADDRESS="replace_with_your_UBIQ_address"
UBQ_POOL="stratum+tcp://us.ubiqpool.io:8008"
UBQ_EXTENSION_ARGUMENTS=""

Do we need to change the pool address?
Try change to below 3, dun works
Getwork
http://us.ubiqpool.io:8888

Stratum
stratum+tcp://us.ubiqpool.io:8008

Stratum 2
stratum+tcp://us2.ubiqpool.io:8008

kk003

member

Activity: 117

Merit: 10

Quote from: papampi on November 01, 2017, 02:23:36 AM

Quote from: leenoox on November 01, 2017, 12:56:19 AM

It's really nice to add more features to nvOC and I would encourage everyone to try and contribute to this great project but I would strongly advice against using unnecessary extreme writing in logs to accomplish the proposed feature. Especialy recording the screen in screenlog...

You see people complainig every day of corrupted USB sticks, freezing, running out of space, boot problems, etc. USB stick as a medium is not designed for such operations, constant writing to USB stick is not recommended, it messes the controller, makes USB perform very slow after a while and kills memory cells which leads to corruption and lock-ups.

If nvOC was explicitly recommended as SSD/HDD OS, the logs would be fine but the reality is that 90% of people use nvOC from USB sticks.

To all devs: please avoid usage of logs as much as possible or at least log as little as possible.

Hint: if you want to show output from the miner in your script/program/telegram/web page (definetely a nice feature to show), record the output from the miner (or nvidia api) into memory then show it in your program on a per need basis. This is more easily done with PHP and Perl but it can be accomplished in Bash as well. Record stdout and stderr into rotating array (you can use shift for the array). You can record 10, 20, 100, even 500 lines and you won't run out of memory, then show the live output from the array into your featured program.

We miners are spending thousands on our rigs and when it comes to stability and life span we forget the most important part and thats where the OS is installed on, we think small and go cheap with a 5-10$ USB when we can have much smoother system with a 30$ SSD.

Using USB as daily use is not recommended in any distro, The most important difference other than USB read/write limit is there's no way for a USB drive to mark bad cells as 'do not use' whereas the SSD may develop bad areas it can ignore them. With a USB drive one cell goes bad and the whole drive is useless.

I'm Not saying that you shouldn't use a USB for bootable OS, just that it's not a good idea to have it as your main boot drive and only use them for diagnostic / testing purposes.
No mining system should be run from USB as a daily hardcore mining system, but run it on usb, test OS and see if you like it, then install it on SSD.

I think mining with nvOC on USB is only good for those who want to mine when their pc is not in use, so they boot with usb, mine for a while then reboot back to their main OS...

I agree. I have to say that if system is using a hdd or ssd (better) it should not have any problem with log files as long as the system is healthy. If system has a very high cpu load/gpu instability etc, then is better not to log, at less in a productive system.
Linux is good at login but system must be healthy.
Got a rig (installed in a old hdd) with high cpu load (2 cores and 2.5 cpu load average) and log files for miners go around 150MB+... no problem. I don't think this would work on a usb stick.

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