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

[papampi]

I rather not use api to kill my miner every once in a while just to see the web page stats
better enable screen log and use tail

change
from:

Code:

screen -dmS miner $HCD ...  

To:

Code:

screen -dmSL miner $HCD ...

Then ssh to your rig and use this :

Code:

tail -f screenlog.0

My miners running flawlessly for 2-3 days with no restart
 

True I could do that, but pointing a browser to the API seems like a much more elegant solution, plus I could get creative and do up a local html page and use iframe to show all the miners in a single browser tab.  Tailing log files just seems very "old school".  

Agree that tailing log is old school, but restarting miner just to see how its working is not a good idea too
We need some one to make a web page from logs for nvoc.

Any one interested in the idea ?
Post your thoughts and solutions.
I'm not good with writing html and web pages, but can extract any info needed from logs with bash

[bdog1234]

Is there any need to edit it in windows before starting the first time ? other than for the reason so that you can mine right away after boot ?

The first one I set up I edited it first the next four rigs I built I did it after. You might lose out on five minutes of mining. I burn the USB and stick it straight in the rig and turn it on. Once it is up and running I edit the 1bash (which is much easier in Linux with the highlighting) and then save it and reboot.

I had an issue one time with a bad usb image. Not sure what happened but making sure it boots with the default setup before taking the time to edit the 1bash seems like a good time saving idea to me.

The only downside is you may not have your payment addresses where you can access them on the new Linux boot up. I HATE manually typing them out and always prefer to copy and paste. With multiple rigs I just SSH to another rig and copy and paste from one 1bash to another.

[papampi]

Is there any need to edit it in windows before starting the first time ? other than for the reason so that you can mine right away after boot ?

The first one I set up I edited it first the next four rigs I built I did it after. You might lose out on five minutes of mining. I burn the USB and stick it straight in the rig and turn it on. Once it is up and running I edit the 1bash (which is much easier in Linux with the highlighting) and then save it and reboot.

I had an issue one time with a bad usb image. Not sure what happened but making sure it boots with the default setup before taking the time to edit the 1bash seems like a good time saving idea to me.

The only downside is you may not have your payment addresses where you can access them on the new Linux boot up. I HATE manually typing them out and always prefer to copy and paste. With multiple rigs I just SSH to another rig and copy and paste from one 1bash to another.

Easier way is to create yor 1bash and save it to pastebin as instructed in upPASTE,
On first boot open 1bash and setup upPASTE and reboot
upPASTE will read from pastebin and update your 1bash.

[rayd89]

Yes
My 13 card 1070 rig showed only use of 2.61gb of ram

I took a 4GB stick out and left it with 4GB ram and it’s running like a champ

But yeah this CPU core saturation issue is bad.

ah thanks will unplug the other 4gb next maintanance
so the core usage is high for unknown reasons ?

not sure.  i can't even edit mine in windows. 

is SSH enabled? what's the default username/password?

m1/miner1 mate

I’m not sure why core usage is so high, I’m waiting on fullzero to respond

[damNmad]

Here's some info:

https://steemit.com/mining/@mtsmayad/bitcore-btx-mining

I don't really know anything, but I'm worried you can't mine Bitcore on Linux since I only saw a Windows miner available.

Guys we can mine 'BTX' using nvOC v19.xx with the following additions:

Code:

COIN="BTX"

Coin Details :

Code:

BTX_WORKER="yourSuprNovaWorker"
BTX_ADDRESS="yourSuprNovaLogin"
BTX_POOL="stratum+tcp://btx.suprnova.cc:3629"
BTX_INTENSITY="21"

add this in 3main at right place

Code:

if [ $COIN == "BTX" ]
then
HCD='/home/m1/KTccminer/ccminer'
ADDR="$BTX_ADDRESS.$BTX_WORKER"

screen -dmS miner $HCD -a timetravel10 -o $BTX_POOL -u $ADDR -p x -i $BTX_INTENSITY

if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi

BITCOIN="theGROUND"

while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi

I've tested this and it is working as expected, I am not sure about the earnings are up to the par, please tune the oc settings accordingly to get better yield!

If you have any issue mining this coin just reply to this message.

[TAKCuCT]

Here's some info:

https://steemit.com/mining/@mtsmayad/bitcore-btx-mining

I don't really know anything, but I'm worried you can't mine Bitcore on Linux since I only saw a Windows miner available.

Guys we can mine 'BTX' using nvOC v19.xx with the following additions:

Code:

COIN="BTX"

Coin Details :

Code:

BTX_WORKER="yourSuprNovaWorker"
BTX_ADDRESS="yourSuprNovaLogin"
BTX_POOL="stratum+tcp://btx.suprnova.cc:3629"
BTX_INTENSITY="21"

add this in 3main at right place

Code:

if [ $COIN == "BTX" ]
then
HCD='/home/m1/KTccminer/ccminer'
ADDR="$BTX_ADDRESS.$BTX_WORKER"

screen -dmS miner $HCD -a timetravel10 -o $BTX_POOL -u $ADDR -p x -i $BTX_INTENSITY

if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi

BITCOIN="theGROUND"

while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi

I've tested this and it is working as expected, I am not sure about the earnings are up to the par, please tune the oc settings accordingly to get better yield!

If you have any issue mining this coin just reply to this message.

An error here:

m1@m1-desktop:~$ /home/m1/KTccminer/ccminer -a timetravel10 -o $BTX_POOL -u $ADDR -p x -i $BTX_INTENSITY
ccminer 8.13-KlausT (64bit) for nVidia GPUs
Compiled with GCC 5.4 using Nvidia CUDA Toolkit 8.0

Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.

Illegal instruction

[IAmNotAJeep]

Is there any need to edit it in windows before starting the first time ? other than for the reason so that you can mine right away after boot ?

The first one I set up I edited it first the next four rigs I built I did it after. You might lose out on five minutes of mining. I burn the USB and stick it straight in the rig and turn it on. Once it is up and running I edit the 1bash (which is much easier in Linux with the highlighting) and then save it and reboot.

I had an issue one time with a bad usb image. Not sure what happened but making sure it boots with the default setup before taking the time to edit the 1bash seems like a good time saving idea to me.

The only downside is you may not have your payment addresses where you can access them on the new Linux boot up. I HATE manually typing them out and always prefer to copy and paste. With multiple rigs I just SSH to another rig and copy and paste from one 1bash to another.

Easier way is to create yor 1bash and save it to pastebin as instructed in upPASTE,
On first boot open 1bash and setup upPASTE and reboot
upPASTE will read from pastebin and update your 1bash.

Another way to streamline ops is to create a master image.
You can actually mount the image directly and edit 1bash, then boot straight into known config the first time and start mining (so all config can be done offline)
In cases where you use static IPs/static rig name/any additional routes not passed on from DHCP/or custom miners not included in stock nvOC I found the following really helped instead of recompiling or copying things around:

1 Take the image with all your pretty customizations/compiles etc
2 Boot that image on every board at least once
3 set any static settings you require during that time (ip/worker name/static routes) then once you've done this for all the rigs, image that USB and it becomes your master (every rigs ethernet interface will be remembered as a separate interface, it helps to identify them as well at the time you're editing static settings).
Once you have your master image you can drop in the necessary 1bash or specific configs before you image your target USB.

3.5 create an image, this now becomes the master image for all your rigs.

4 It's a good idea to keep all the latest miner specific configs on the image - I use the 10Mb partition to keep 1bash and any other specific configs on the master image and copy the desired config as needed before imaging the usb.

This has saved me lots of time between upgrades as well as USB failures, I've had 3 USBs die in past few months and having one spare ready to go for any rig really helps minimizing downtime.

Editing an .img can be done as follows:

Code:

cd /path/to/where/saved/your/image
sudo losetup -d /dev/loop0
sudo modprobe loop
sudo losetup -f
sudo losetup /dev/loop0 your master_image_file.img
sudo partprobe /dev/loop0

You should be able to browse the partitions on the image and add/edit any files (this is actually how I update the master with new functionality)

The commands below will help you resize any partitions on the image directly - was more useful before v0019 when the USB image required a true 16G USB, but this can still be useful for cloning from a larger SSD to a smaller one etc, or simply if you had chosen a larger usb to be the master, and then have to boot at least one rig from a smaller USB:

Code:

#to resize the partition
sudo gparted /dev/loop0
#(14230M) <-this is what I found fits on most 16Gig USBs
sudo losetup -d /dev/loop0

fdisk -l master_image_file.img.img
# find the ending sector of your last partition - in the case if v0019 and a 1423M partition it seems to be sector 29163519
# the command below truncates your image one sector after the last partition sector - therefore shrinking the image to your desired capacity
truncate --size=$[(29163519+1)*512] master_image_file.img.img

[VoskCoin]

I agree this is an ewbf linux bug.  Unfortunately the author does not seem to be active these days.  My friend that is having the exact same issue took a look at the watchdog script and ripped out some logic to create an "apicheck" bash script.  It goes like this:

Code:

#!/bin/bash

source ~/1bash

#########################################################################

API_IS_UP=0

if nc -vzw1 $IPW 42000;
then
   API_IS_UP=1
fi

echo ""

if [[ $API_IS_UP == 0 ]]
then
   echo "$(date) - Miner api is down: reinitializing now"
   
   # If miner runs in screen 'miner' kill the screen to be sure it's gone
   pkill -e miner
 
   # Kill 3main to re-init
   target=$(ps -ef | awk '$NF~"3main" {print $2}')
   kill $target
else
   echo "$(date) - Miner api is up"
   echo ""
fi

If would be awesome if the above logic could be incorporated into the official watchdog.  It would also mean adding something like this to 1bash:

Code:

USE_EWBF_API=”YES”

EWBF_API_PORT=”42000” 

And modify 3main to launch EWBF with the api flag.  Something along these lines:

Code:

screen -dmS miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $ZEN_POOL --user $ZENADDR --pass z --port $ZEN_PORT --api $IP:$EWBF_API_PORT;

Thanks

It just happened again.   Here are my 4 miners, the one running ewbf on windows recovered fine, but the 3 running nvOC never did:



And here you can see the connectivity glitch on the pool right around 11am:



So adding the above tweaks to the distro should solve this.

EDIT: My friend who is already running the above tweaks confirmed it worked perfectly.

Thanks

What interface is that ^? (not zhashpro)

[crazydane]

@VoskCoin That is the API build into the EWBF miner.  When you launch EWBF you can add the following to the script:

--api minerip:42000

Where minerip is the IP address of your rig.

You then simply point a browser to minerip:42000 to get the above stats.  They update about every 30 seconds or so when new work is assigned.

[VoskCoin]

So I had a three card riser-less build (well actually one was on a riser since the AORUS are huge, no issues with this setup)

1080 ti / 1080 ti / 1070  mini

I moved to a 6 card riser build and now I have this issue . . any ideas?
(1070 mini 1070 mini 1080 TI 1080 TI 1070 mini 1070 mini
software or hardware and then what?

This should be a 3k average sols rig

Added more details below ////




2x 1080 TI + 1070 earning the same as 2x 1080 TI 4x 1070

(1.8k sol rig avg)


3k sol rig, avg 2.6k due to error, but its as if all 3 of the 1070s on the second PSU (connected add2psu PSU1 to mobo/cpu/all risers +pata to Add2psu / PSU2 mobo to add2psu+3x 1070 mini


nvOC_19 on both . .


@crazydane On average I get the best daily returns from suprnova/luck/zhash roughly maybe in that order? if my miner finds a block on luck it obviously comes out ahead. I'm using luck because it's easy to look at basic stats individually



Also in other news . . that's actually good news. .  my bitmain antminer d3 has arrived and is hashing away 2 gh/s higher than advertised from 15.5 to 17.5 iirc




When is antOC_19 coming out fullzero? xD

Hey guys still dealing with this issue . . . can anyone lend me a hand here at a bit of a loss

https://luckpool.org/workers/znVUjim9waxP73P5jQ76ezdMpvgTYVnPp3r

It's averaged out to be a bout correct but a couple times a day its still completely dropping. .

It looks like your client is softcrashing and watchdog is restarting it.  If you are using a mixed rig the most likely reason is the GPU index is counter intutive ( I have had this problem many times with mixed rigs)  try using the cmd:

Code:

sudo echo 'export CUDA_DEVICE_ORDER=PCI_BUS_ID' | sudo tee -a /etc/profile.d/cuda-device-order.sh

in the guake terminal then reboot and ensure your GPUs are OCed / PLed in the same index as the system recognizes them.

If it works Thank:  car1999 + leenoox

I added this to the -1 update.

Let me know if this works.

Just quoting this here as I'm going to be working on this today and update with a link to watch (if anyones interested) in a bit

[VoskCoin]

@VoskCoin That is the API build into the EWBF miner.  When you launch EWBF you can add the following to the script:

--api minerip:42000

Where minerip is the IP address of your rig.

You then simply point a browser to minerip:42000 to get the above stats.  They updated about every 30 seconds or so.

Thanks

What are your thoughts on 3.3 vs 3.4 + could I load this feature into 3.3?

I haven't done too much research on this yet, but if 3.3 has no fee and 3.4 has a fee - does 3.4 work my rigs harder to get the 2% increase that pays for the 2% fee?  I have a rig that averages about 3k, it averaged about 3k on 3.4 and 3.3 . .  so if the average is relatively the same wouldn't we be better off using 3.3?

[VoskCoin]

v0019-1 update:

Lots of changes; please keep in mind this update is beta: it will most likely have some bugs, if you don't want to deal with any bugs you can wait until any issues have already been found and fixed by the community.

Before updating; please copy your 1bash (and any other files you have changed/customized) to a different directory (such as the desktop).

To update:

open 1bash with gedit and ensure:

Code:

AUTO_UPDATE="BETA" 

close any terminal currently open; then:

open a guake terminal ( press f12 ) and type the following, then press enter:

Code:

bash 4update

This will launch 4update which will update your 2unix file.  

When 4update is done; gnome-terminal will auto launch.  

The new 2unix will detect your v0019 is not -1 and launch the update.

The update will install all system updates including the newest Nvidia driver.  Then update nvOC files.

When it is done your rig will reboot automatically.  

Your 1bash will be copied to a file named: your_old_1bash as a new version is required for some of the updates.  

You can copy and paste your pools / addresses into the new 1bash.  ( I will eventually automate this)

v0019-1 can support up to 19x GPUs; however it is unlikely you will be able to get more than 13x GPUs to work correctly with the new Asus 19x mobo.

Edit Additional info:

Lots of new COIN selections from damNmad and some from papampi.  I will add a full change log to the OP later today.

how can i update to 19.1 and not 19.2?

[Razvan17]

        Is there any v19.1.2 img file available for download? I mean to directly burn the usb stick with nvOC V19.1.2 and to not be needed to update it according the instructions posted before.

[jmayniac]

how can i update to 19.1 and not 19.2?

I don't think you can, unless you can get the bash files from someone and replace the ones in the v0019 img.

[jmayniac]

       Is there any v19.1.2 img file available for download? I mean to directly burn the usb stick with nvOC V19.1.2 and to not be needed to update it according the instructions posted before.

I haven't seen where there has been a newer .img file released.  The only way is to burn v0019 and update to -1.2.

[crazydane]

What are your thoughts on 3.3 vs 3.4 + could I load this feature into 3.3?

I haven't done too much research on this yet, but if 3.3 has no fee and 3.4 has a fee - does 3.4 work my rigs harder to get the 2% increase that pays for the 2% fee?  I have a rig that averages about 3k, it averaged about 3k on 3.4 and 3.3 . .  so if the average is relatively the same wouldn't we be better off using 3.3?

I believe the API was introduced in 3.4, but I'm not 100% (never ran 3.3).

It is my understand as well that 3.4 is 2% faster but has the 2% dev as you mention.  As to the rig working 2% harder in 3.4, that's an interesting through, but one that I have not looked into deeper.  In theory, if 3.4 truly work the GPU's a little harder, perhaps there is a little more headroom in 3.3 to allow slightly higher clock boosts?

Your quote of my earlier question about which pool is better for ZEN, I have now been on both Luck and Zhash, and my findings were as follows:



Granted I wasn't mining on the same days on both, but for me, I'd say Zhash gives a far better return than Luck.  I will try to get 2 identical rigs, and have each mine a different pool at the same time so see what my results will be.

[VoskCoin]

Is there a full list of commands for nvOC? / If not could we compile one? / whats the command to kill the miner process

[car1999]

@VoskCoin That is the API build into the EWBF miner.  When you launch EWBF you can add the following to the script:

--api minerip:42000

Where minerip is the IP address of your rig.

You then simply point a browser to minerip:42000 to get the above stats.  They updated about every 30 seconds or so.

Thanks

What are your thoughts on 3.3 vs 3.4 + could I load this feature into 3.3?

I haven't done too much research on this yet, but if 3.3 has no fee and 3.4 has a fee - does 3.4 work my rigs harder to get the 2% increase that pays for the 2% fee?  I have a rig that averages about 3k, it averaged about 3k on 3.4 and 3.3 . .  so if the average is relatively the same wouldn't we be better off using 3.3?

I use 3.3， get hashrate from pool api, get GPU usage from nvidia-smi, don't need the miner's api. if all of us use 3.3, globla hashrate drops, that's interesting.

[crazydane]

Run top, make note of the PID for the miner process (should show up at the top of the list after a few seconds, hit 'q', then do:

Code:

sudo kill -9 PID

Then wait 30 seconds or so for the watchdog to restart the miner.  If you don't want the miner to restart, you have to stop the watchdog too.

[VoskCoin]

What are your thoughts on 3.3 vs 3.4 + could I load this feature into 3.3?

I haven't done too much research on this yet, but if 3.3 has no fee and 3.4 has a fee - does 3.4 work my rigs harder to get the 2% increase that pays for the 2% fee?  I have a rig that averages about 3k, it averaged about 3k on 3.4 and 3.3 . .  so if the average is relatively the same wouldn't we be better off using 3.3?

I believe the API was introduced in 3.4, but I'm not 100% (never ran 3.3).

It is my understand as well that 3.4 is 2% faster but has the 2% dev as you mention.  As to the rig working 2% harder in 3.4, that's an interesting through, but one that I have not looked into deeper.  In theory, if 3.4 truly work the GPU's a little harder, perhaps there is a little more headroom in 3.3 to allow slightly higher clock boosts?

Your quote of my earlier question about which pool is better for ZEN, I have now been on both Luck and Zhash, and my findings were as follows:



Granted I wasn't mining on the same days on both, but for me, I'd say Zhash gives a far better return than Luck.  I will try to get 2 identical rigs, and have each mine a different pool at the same time so see what my results will be.

Definitely want to look into that I can help you with whatever I can -- but its beyond my scope of skills really :C

Ultimately though the 2% increase has to come from somewhere O_o

Those are interesting findings, my luckpool and really zen earnings in general have been very low compared to the previous period. zhash suffered from the fake miner attack recently (miningspeed suffered from this as well) and I'm not sure if luckpool did . . but the earnings the last week or so definitely seemed like it. . .

Today is actually the best day in awhile for me on luck aside from when I found a block a couple days ago
https://luckpool.org/workers/znWcPtNkPCj6VfLRfMhf6i44DvHoeEfNbcd

here's a minez zone link
https://minez.zone/workers/zngoZCdezZLWvkZkTPg42rePGG46JLs63H5

I had a rig on zhash but all the issues the pool was having caused me to be profiting zero

I need to lookup the exact day count, but all 3 of these rigs were launcheda t the same time

suprnova
/
luckpool
/
minez zone

Fresh wallets + can be verified on zen explorer