[ mining os ] nvoc

[JayneL]

yup i do.... still figuring out now...

[damNmad]

yup i do.... still figuring out now...

Have you followed the below instructions?? Please try the below again, if it doesn't work. happy to help you via teamviewer.

Hi guys,

i do a little "how to" if some people want to mine SIGT / skunk algo.

First of all i use Palginmodccminer ( the SP_MOD is faster but u have to pay )

FIRST STEP GET THE CLIENT

### Be in home dir ###

cd /home/m1/

### Create a directory for your new miner ###

mkdir PMccminer

### Go in new dir ###

cd PMccminer/

### Download miner client ###

wget https://github.com/palginpav/ccminer/releases/download/1.1/palginmod_1.1_Ubuntu.tar.gz

### Extract the file ###

tar -zxvf palginmod_1.1_Ubuntu.tar.gz

### Delete start.sh ###

rm start.sh

### Back to home dir ###

cd /home/m1/

SECOND STEP EDIT BASH

### Open 1bash

nano 1bash

### Add SIGT  and  SIGT_BTC to the coin selection

# CHOOSE COIN FROM:
# DMD  GRS  ZPOOL_LYRA2V2  ZPOOL_BLAKE2S
# ZEC   ZCOIN  HUSH   ZEN  ZCL   SIGT  SIGT_BTC
# NICE_ETHASH  ETH    MUSIC  ETC  EXP  DCR  PASC
# MONA  VTC    DGB    SIA  FTC  LBC
# DUAL_ETC_DCR    DUAL_ETC_PASC    DUAL_ETC_LBC    DUAL_ETC_SC
# DUAL_EXP_DCR    DUAL_EXP_PASC    DUAL_EXP_LBC    DUAL_EXP_SC
# DUAL_ETH_DCR    DUAL_ETH_PASC    DUAL_ETH_LBC    DUAL_ETH_SC
# DUAL_MUSIC_DCR  DUAL_MUSIC_PASC  DUAL_MUSIC_LBC  DUAL_MUSIC_SC

### Add SIGT and SIGT_BTC specs ( u have to modify SIGT_WORKER and SIGT_ADDRESS by your seting )

SIGT_WORKER="SIGT"
SIGT_ADDRESS="Bibi187"
SIGT_POOL="stratum+tcp://sigt.suprnova.cc:7106"
 
###SIGT_BTC use BTC adresses###
SIGT_BTC_POOL="stratum+tcp://skunk.mine.zpool.ca:8433"

### If u use SIGT_BTC, be sure to get correct ( your BTC adress )

BTC_ADDRESS="3JJaMUVBJp55BNsGvYynaJhDXRyUf95hyG"

### Add miner specs to the end of ur file between the two last "fi"   ( ensure ur worker have x password on suprnova pool, or modify the "-p x" by "-p YourPassword" in the SIGT section )

if [ $COIN == "SIGT_BTC" ]
then
HCD='/home/m1/PMccminer/ccminer'
ADDR="$BTC_ADDRESS"
 
screen -dmS miner $HCD -a skunk -o $SIGT_BTC_POOL -u $ADDR -p c=SIGT
 
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
 
BITCOIN="theGROUND"
 
while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi
 
if [ $COIN == "SIGT" ]
then
HCD='/home/m1/PMccminer/ccminer'
ADDR="$SIGT_ADDRESS.$SIGT_WORKER"
 
screen -dmS miner $HCD -a skunk -o $SIGT_POOL -u $ADDR -p x
 
if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi
 
BITCOIN="theGROUND"
 
while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi

THIRD STEP OC SETTING ( ASUS 1070 GTX 8OG / prolly ok for most 1070 gtx )

First of all this algo, gona get a lot of heat from your card, he use core, not memory.

CoreClock : 120
MemClock : -2000
PowerLimit at default : 150W
Temp Target 70°
Fan between 95% - 75%  ( I use watchdog )

This fine tunning work like a charm 213mh/s on suprnova, 211mh/s on zpool

U have to disable

IAmNotAJeep_and_Maxximus007_WATCHDOG="NO"

Or your RIG gona get restart for nothing, i dont modify IAmNotAJeep_and_Maxximus007_WATCHDOG, if i do prolly i can get him work with this setup but more simple to stop him for this coin


Et voila

thanks for the walkthrough. there is a few things that i think are backwards on your instructions. on my nvoc the directories are /home/m1/ and you have /m1/home/ in your instructions.
also, with the settings i am entering into the fields for the suprnova pool info, i dont know if they are right or what is going on...i am getting a error when i run the terminal "stratum authentication failed" then trying again in 30 seconds. your settings show:
SIGT_WORKER="SIGT"
SIGT_ADDRESS="Bibi187"
SIGT_POOL="stratum+tcp://sigt.suprnova.cc:7106"

in suprnova, my worker is "firstname.systemnumber" example "lovecoin.sys1" - so would i make my settings look like SIGT_WORKER="lovecoin.sys1" ? also what am i editing to sigt_address?

Nice point about the path, the true one is /home/m1, i edit the post
SIGT_WORKER="sys1"
SIGT_ADDRESS="lovecoin"

Will do the job

[car1999]

Hey, ty for adding teamviewer to nvOC!

But i got a problem: teamviewer never start on boot, i always need to enter this on guake terminal :

sudo teamviewer --daemon enable


My rigs are not at home, and if i need to reboot this, i can't control after the reboot :-(, please help me.

On your 1bash be sure to set

TEAMVIEWER="YES"

Oh thanks, there is a way to edit the 1bash in ubuntu ? if yes it need a restart ? thanks!

Yes, you can. It is in the home directory. Please search in home folder (where you see all miners)

EDIT:

For restart, to apply the 1bash changes you don't need to restart whole rig, you can kill the mining process using 'CTRL + c' and it should restart the process with new changes, if it doesn't just close the terminal after 'CTRL+c' and close the terminal and restart the terminal (not the rig)

press CTRL+c, it restarts 1bash, do you know how to disable this feature?
 I'd like to exit the terminal when I press CTRL+c, thanks.  

[hwlgraka]

Hello,

I have two scenarios, where I don't have a solution. And I'm not able to search only in this entire thread, is that possible?

Maxximus007_AUTO_TEMPERATURE_CONTROL is disabled
Config is set to REMOTE

1) Sometimes the miner get stuck. This means, that I can still open the session (screen -r miner), but I cannot kill it (pkill -e miner).
If I happen to be in that situation, how do I kill the miner? Sending a pkill -9 -e miner also doesn't help.

2) After the miner gets killed (via pkill -e miner), there is no screen session opened again (screen -ls returns nothing). How can I manually start the 1bash script again, so that it starts the corresponding and correct screen session?

Thanks very much in advance.
Kind regards

[Bibi187]

Hello,

I have two scenarios, where I don't have a solution. And I'm not able to search only in this entire thread, is that possible?

Maxximus007_AUTO_TEMPERATURE_CONTROL is disabled
Config is set to REMOTE

1) Sometimes the miner get stuck. This means, that I can still open the session (screen -r miner), but I cannot kill it (pkill -e miner).
If I happen to be in that situation, how do I kill the miner? Sending a pkill -9 -e miner also doesn't help.

2) After the miner gets killed (via pkill -e miner), there is no screen session opened again (screen -ls returns nothing). How can I manually start the 1bash script again, so that it starts the corresponding and correct screen session?

Thanks very much in advance.
Kind regards

When u are on the miner terminal do CTRL+C interrupt your miner.
To launch a new 1bash just do "bash 1bash"
Let him do the work, when u see the final line do CTRL+C
"screen -ls" gona show you new miner

[JayneL]

thanks guys i finally manage to make it run for couple of hours now, heres the new problem i plug all my 6 GPU in my Biostar TB250-BTC PRO but only 5 was working
bios already set to mining above 6gpu, pcie set to GEN1, i plug my monitor on the 1x16 pcie all fans are working. and im lost

[uat88]

I've managed to make it work with my RIG, it seems working fine (issue was with path as mentioned in one of the replies).

Getting around 125 MH with my 8x 1060 6GB ASUS (oc:0,mc:0,pl:80), please share you OC settings if you think I'm getting low hashrate.

Thanks.

I dont know about 1060, but on skunk algo, u dont care about mc so put them in lower value, max as u can for 1070 is -2000.
Up your powerlimit to the default powerlimit and Clockmemory step by step start at 100, wait 24h and increment by 10 after every 24hours before crash.
When crash occur reduce to the previous step, wait again more 24h if stable lower your powerlimit to get a better ratio watt / hashrate.

So for my ASUS 1070 GTX 8OG
MemClock : -2000
CoreClock : 130 ( the 24hours step, i go push to 130 just now )
PowerLimit : 150W per gpu
TempLimit : 70c
Fan range : 95-75 ( autotemp ON )  

As SIGT is running good for 2500 blocks after reward get halved, i suggest you to get a stable setting cause watchdog is disable, so if your RIG crash, he dont gona reboot him self

Thanks mate for the suggestions and sharing your OC settings, i will try to increase as per your suggestions and see how it goes.

Will share my OC settings if it improves.

Is getting around 125 MH with my 8x 1060 6GB considered low hashrate?
What should be the ideal for this GTX 1060 or 1070?

[damNmad]

I've managed to make it work with my RIG, it seems working fine (issue was with path as mentioned in one of the replies).

Getting around 125 MH with my 8x 1060 6GB ASUS (oc:0,mc:0,pl:80), please share you OC settings if you think I'm getting low hashrate.

Thanks.

I dont know about 1060, but on skunk algo, u dont care about mc so put them in lower value, max as u can for 1070 is -2000.
Up your powerlimit to the default powerlimit and Clockmemory step by step start at 100, wait 24h and increment by 10 after every 24hours before crash.
When crash occur reduce to the previous step, wait again more 24h if stable lower your powerlimit to get a better ratio watt / hashrate.

So for my ASUS 1070 GTX 8OG
MemClock : -2000
CoreClock : 130 ( the 24hours step, i go push to 130 just now )
PowerLimit : 150W per gpu
TempLimit : 70c
Fan range : 95-75 ( autotemp ON )  

As SIGT is running good for 2500 blocks after reward get halved, i suggest you to get a stable setting cause watchdog is disable, so if your RIG crash, he dont gona reboot him self

Thanks mate for the suggestions and sharing your OC settings, i will try to increase as per your suggestions and see how it goes.

Will share my OC settings if it improves.

Is getting around 125 MH with my 8x 1060 6GB considered low hashrate?
What should be the ideal for this GTX 1060 or 1070?

Well, from my experiments, i came to conclusion that the following settings are good (maybe not!!) I think.

cc :150
mc:-1500
pl  :80

gave me around 138MH

But I just found this

https://bitcointalk.org/index.php?topic=2070862

Testing it now, will keep you posted.

Please let me know if the above OC settings has made any improvement?

 

[tomlev5]

Hi!
I'm about to build a rig with Pentium G4400.
But after reading about Skylake issues with hyper threading don't know
should I use it or better to return and exchange it with i3?

i have a rig runs 8 cards with G3900, no problem.

I have a rig with G3900 and 10 cards, but it seems that the G3900 is bottlenecking the system. First core uses 100%, the other around 20%.

Is there a way to split the workload on both cores (If I could run EWBF miner in two terminals or is there some other way)?

Can somebody please help me, i'm a noob in linux.


nvOC is a great system. Thanks for all the work.

I tried opening two miners in two screens with some change in 1bash:

screen -dmS minerX1 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 0 1 2 3 4 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;
screen -dmS minerX2 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 5 6 7 8 9 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;

After the change there are two processes in System monitor, but CPU usage is still the same (100% one core, 20% second core).

Is it possible that System monitor doesn't show the correct CPU utilization?
Will it help if I change the CPU from G3900 to i3 or perhaps i5?

Fullzero, I see You have 13 GPUs on Asrock H110 PRO BTC (I am using the same motherboard). What kind of CPU do you have so that everything is working smoothly?

[salfter]

@salfter :

I'd like to suggest an idea to your switcher: when the most profitable algorithm is Ethash, give the option to dual-mine automatically with the second most profitable algorithm if it's able to do so.

Of course I'm oversimplifying, as the switching itself will have to consider a higher power limit, more complex profit calculation and perform a "switch inside a switch" (Ethash fixed + switching second algo). But I think we can get a few more bucks this way, at least from my short mining experience it's usually profitable to dual-mine when Ethash is the most profitable.

My somewhat limited experience is that it only squeezes out a few more cents, not dollars.  I'd also need to redo miner benchmarks, as I've been using Genoil's ethminer.

[dbolivar]

I tried opening two miners in two screens with some change in 1bash:

screen -dmS minerX1 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 0 1 2 3 4 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;
screen -dmS minerX2 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 5 6 7 8 9 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;

After the change there are two processes in System monitor, but CPU usage is still the same (100% one core, 20% second core).

Is it possible that System monitor doesn't show the correct CPU utilization?
Will it help if I change the CPU from G3900 to i3 or perhaps i5?

I don't have experience with your particular hardware, but from the specs of your CPU, it supports up to 16 PCIe lanes, so at least I/O shouldn't be a problem (https://ark.intel.com/products/90741/Intel-Celeron-Processor-G3900-2M-Cache-2_80-GHz), as long as you use all your cards with risers, so they all run at PCIe 1x.

You can check the following in your Linux installation:

1) In "top" or "system monitor", what's the breakdown of the CPU usage for USER, SYSTEM, NICE and WAIT? This will help identify where the bottleneck could be.

2) Which are the top 3 processes using more CPU?

3) Check if you have the process "irqbalance" running with the correct parameters: "ps aux | grep irqbalance".

[salfter]

Sorry but that's not really related to my question. It's no problem how loud the graphic cards are, they should just run at 100%. The cooler the card, the longer the lifespan. And at the moments in the room I really need them to run at 100%. They get 70 degree at 50% which is too much.

I thought I read somewhere that running the fans much past 85% won't do much in the way of additional cooling, but it will run up additional wear on the motors.  

[tomlev5]

I tried opening two miners in two screens with some change in 1bash:

screen -dmS minerX1 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 0 1 2 3 4 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;
screen -dmS minerX2 $HCD --eexit 3 --fee $EWBF_PERCENT --cuda_devices 5 6 7 8 9 --pec --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT;

After the change there are two processes in System monitor, but CPU usage is still the same (100% one core, 20% second core).

Is it possible that System monitor doesn't show the correct CPU utilization?
Will it help if I change the CPU from G3900 to i3 or perhaps i5?

I don't have experience with your particular hardware, but from the specs of your CPU, it supports up to 16 PCIe lanes, so at least I/O shouldn't be a problem (https://ark.intel.com/products/90741/Intel-Celeron-Processor-G3900-2M-Cache-2_80-GHz), as long as you use all your cards with risers, so they all run at PCIe 1x.

You can check the following in your Linux installation:

1) In "top" or "system monitor", what's the breakdown of the CPU usage for USER, SYSTEM, NICE and WAIT? This will help identify where the bottleneck could be.

2) Which are the top 3 processes using more CPU?

3) Check if you have the process "irqbalance" running with the correct parameters: "ps aux | grep irqbalance".

When I start the miner in single process:

1) breakdown of the CPU usage after about 20 minutes of uptime:
      1x process miner used 3:51
      14x process kworker (they used from 0:40 to 1:20)
      9x irq nvidia (they used from 0:40 to 1:03)

2) in the top twenty processes are miner, kworker, irq nvidia (nothing else)

3) if I type "ps aux | grep irqbalance" in Guake terminal i get two processes: one is root the other is m1.
What parameters can I check?

Thanks for helping dbolivar. I am stuck, because I have no experience with linux.

[fogcity]

Hey there --

I'm running v0018 on a single rig with 6x 1070 GPUs (1x EVGA & 5x ASUS).  I have all the GPUs over-clocked to where my total eth mining MHz is ~180MHz and I'm quite content to just let it run.

That being said, my rig crashed today.  The error on the screen was:

CUDA error in function 'search' at line 346 : the launch timed out and was terminated

This error was repeated for all 6x cudaminers (cudaminer0 thru cudaminer5) at the same system clock time, and then the rig halted.

Can anyone possibly tell me what caused this issue and what I can do to avoid it happening again?

Thanks in advance!

Fogcity

[dbolivar]

When I start the miner in single process:

1) breakdown of the CPU usage after about 20 minutes of uptime:
      1x process miner used 3:51
      14x process kworker (they used from 0:40 to 1:20)
      9x irq nvidia (they used from 0:40 to 1:03)

2) in the top twenty processes are miner, kworker, irq nvidia (nothing else)

3) if I type "ps aux | grep irqbalance" in Guake terminal i get two processes: one is root the other is m1.
What parameters can I check?

Thanks for helping dbolivar. I am stuck, because I have no experience with linux.

It's OK to have a high CPU usage time* for kworker and irq/nvidia, these account for internal kernel worker threads and interrupts for GPU I/O (expected on a multi-GPU rig mining). What I'm really looking for is how much CPU usage is for user processes, system processes, and I/O wait, that's why I asked these values. Try this: run the "top" utility, it will be constantly updating -- type "1", it will expand the third line (CPU usage summary) to show each CPU. Then paste the values here, like that:

%Cpu0  :  0.3 us,  1.0 sy,  0.0 ni, 98.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu1  :  0.3 us,  1.3 sy,  0.0 ni, 98.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
...
%CpuN  : ....

Regarding irqbalance, running the command I suggested, you should get one line like this:

root       874  0.0  0.0  19536  2232 ?        Ss   Aug06   0:12 /usr/sbin/irqbalance --pid=/var/run/irqbalance.pid

* EDIT: high CPU usage TIME (which accumulates until the next reboot), not a constant high CPU usage percentual.

[BigSmurf]

hi,
i have Asrock H110 btc+ pro, and 13xMining/P106-100 (1060 6gb) GPU-z everything works fine and stable with other OS-es, but with your OS it keeps restarting and restarting because of not being able to see/find xorg file.

We managed to start the OS via GTX 1060 card and then added the Mining P106-100 (1060 6gb) cards, but no go with only the Mining P106-100 (1060 6gb) cards. can you look in to this ? i would like to use your OS but dont want to have a normal gaming card, don't need it when using all Mining cards.

Can you also make a explination on overckloking as we tried via the file but failed. we only managed to individually overclock via the Nvidia x server.

thank you.
BigSmurf

[philipma1957]

Hi,

I got a gainward 1060 today and it is the first card that ignores the power-limit out of 8 cards (gigabyte, asus) wether I set it by bash or nvidia-smi. ie. sucks 100w/80w. card damaged?

still using v0017

btw: any planned date for v0019? I much appretiate this OS!

best regards

I am not familiar with gainward.  The GPU may not be properly recognized by X; in turn causing OC and PL to not work on it.  I usually test GPUs that have a problem in a rig; by moving them to a mobo 16x slot direct (only GPU on the mobo) and testing if the same problems manifest.

There are a lot of changes for v0019; I want to test them before releasing.  

skunk on zpool please  thanks phil

[dbolivar]

@fullzero

Have you considered moving the configuration, or at least the key configuration parameters like pools and coin to mine, to a separate file? I sometimes change pools and coins, for instance, and currently I have several "1bash_xxx" files for each configuration, controlling the active one with a symlink to "1bash". One idea would be a config file like this (for instance in INI format, but just to illustrate):

::: 1bash.conf :::
[defaults]
# Every configuration option

# Below just what's different from default. Users define their config keys,
# specifying the active one in 1bash
[zec-nanopool]
COIN="ZEC"
ZEC_POOL="zec-us-east1.nanopool.org"

[eth-dwarfpool]
COIN="ETH"
ETH_POOL="eth-us.dwarfpool.com"

::: 1bash :::
# 1) Read default options
# 2) Read user options
USER_CONF="zec-nanopool"
...

Just an idea. I may be able to help you with that, if you want and find it a good idea. I know Bash doesn't have a built-in parser for INI (or whatever) config files, but there's some code around to do that.

[damNmad]

Hi guys, if posted prior my apologies as I tried to search this thread and the global threads.

My question is in regards to 'Maximus007_Auto_Temperature_control'

When I have it on it doesnt matter what I set the 'target_temp' for each card at it seems to like running the cards at 70 to 80 degrees and will up and down scale the fans to keep them there.  Fans are at 30 - 35%.

I prefer a temp of 55 to 60.

Then I thought I would turn it off but even if I set manual fan to yes and the auto temp to 'no' my fan speed of 65% is not reflected so I think the script runs regardless of what you put in 1bash.

Anyone had this issue and either (a) found a way to make it respect the selected temperature or (b) disable it and allow for manual fans?


Many thanks!

change:

Code:

TARGET_TEMP_0=60

TARGET_TEMP_1=60

TARGET_TEMP_2=60

TARGET_TEMP_3=60

TARGET_TEMP_4=60

TARGET_TEMP_5=60

TARGET_TEMP_6=60

TARGET_TEMP_7=60

TARGET_TEMP_8=60

TARGET_TEMP_9=60

TARGET_TEMP_10=60

TARGET_TEMP_11=60

TARGET_TEMP_12=60

TARGET_TEMP_13=60

for b see:

https://bitcointalk.org/index.php?topic=1854250.msg20730240#msg20730240

Hi Fullzero,

With a fresh install of NvOC , changing target temps doesnt do anything on my rig.  The fans do move up and down but they dont maintain target temp.

For example I set target temp as per your note to 60 and the cards run at 80.  The fans go up and down on each card to maintain 80.  The expected result is that they go faster to say 55% so the card runs at 60.

If I follow the steps in (b) this doesnt do anything different.  

I am using v17 , was this an issue in 17?  Or could it be my cards causing the issue
I am in Australia and we have celcius as our default temperature and you guys use farenheit could that be an issue somewhere?

In version v15 if I set manual fans to 70% they ran at 70% - for me in this version they seem to do their own thing

I think living in Australia doesn't have anything to do with 'Maximus007_Auto_Temperature_control' script

I would suggest try V18 and try the above suggested options, there were issues in v17 (I had similar one) so better try v18.

If the issue still persists in V18 share your 1bash with me, i will compare it to mine and see if there is any issue.

EDIT :

Lets give fullzero max time on development getting done for next releases by solving the minor issues ourselves

[ivoldemar]

Hey, ty for adding teamviewer to nvOC!

But i got a problem: teamviewer never start on boot, i always need to enter this on guake terminal :

sudo teamviewer --daemon enable


My rigs are not at home, and if i need to reboot this, i can't control after the reboot :-(, please help me.

On your 1bash be sure to set

TEAMVIEWER="YES"

Oh thanks, there is a way to edit the 1bash in ubuntu ? if yes it need a restart ? thanks!

Yes, you can. It is in the home directory. Please search in home folder (where you see all miners)

EDIT:

For restart, to apply the 1bash changes you don't need to restart whole rig, you can kill the mining process using 'CTRL + c' and it should restart the process with new changes, if it doesn't just close the terminal after 'CTRL+c' and close the terminal and restart the terminal (not the rig)

press CTRL+c, it restarts 1bash, do you know how to disable this feature?
 I'd like to exit the terminal when I press CTRL+c, thanks.  

The way everything is setup; is to expect this to occur.  You can change this but; it will break a lot of other things.

When gnome terminal is open go to the top left of the screen and click terminal, then preferences, then profiles.  select mining and click edit.  Click the command tab.  Change when command exits: to Exit the terminal.

Friend, look, please. It's in your interests. I need to collect 30 farms for 12 Mining Edition cards and I want to do this on NVOC and I need to collect it before the end of the week, but without overclocking there is no sense at all.
I sent you access to private messages.

Very much I ask you, to solve a situation.