[ mining os ] nvoc

[cc4l]

Hi everyone, quick question

What would one use to monitor his rigs? Like let's say a rig crashes, how would you receive a notification?

Or is it just to set it to auto-reboot with something like watchdog and watch weekly logs to see if a rig crashed too often?

Thanks for the help

[tomlev5]

Hi!

I am waiting on the next stable release with v0019. v0019-1.4 was BETA and I don't know about v0019-2.0, is v0019-2.0 a stable release?

Does v0019-2.0 have all auto-updates disabled? (I would prefer to have automatic driver updates and automatic system updates disabled, I am afraid they will bring instability)

[damNmad]

Hi!

I am waiting on the next stable release with v0019. v0019-1.4 was BETA and I don't know about v0019-2.0, is v0019-2.0 a stable release?

Does v0019-2.0 have all auto-updates disabled? (I would prefer to have automatic driver updates and automatic system updates disabled, I am afraid they will bring instability)

Yes, 2.0 is the stable update.

You can download it from here

https://nvoc-mining-os.com/downloads/download-page-nvidea/

and make sure you update the miners using the script the below instructions :

(for existing users please backup your 1bash just in case)

Go to Guake :

Navigate to Downloads

cd /home/m1/Downloads

Below command downloads the update script

wget https://www.dropbox.com/s/cyo86xoqotplges/nvOC-19-2-update

Then run the update script

bash /home/m1/Downloads/nvOC-19-2-update

Credits to @papampi

[tomlev5]

I am downloading v0019-2.0.
Thank you guys (The whole team)

[gs777]

Week ago I've switched all my rigs to v0019-2.0.
It works fine nothing to complain
just a question is it possible to mine ZCL with Miningspeed pool?

[papampi]

Week ago I've switched all my rigs to v0019-2.0.
It works fine nothing to complain
just a question is it possible to mine ZCL with Miningspeed pool?

It should work fine,
Have you tested and you got into any problems?

[papampi]

Hi!

I am waiting on the next stable release with v0019. v0019-1.4 was BETA and I don't know about v0019-2.0, is v0019-2.0 a stable release?

Does v0019-2.0 have all auto-updates disabled? (I would prefer to have automatic driver updates and automatic system updates disabled, I am afraid they will bring instability)

Yes, 2.0 is the stable update.

You can download it from here

https://nvoc-mining-os.com/downloads/download-page-nvidea/

and make sure you update the miners using the script the below instructions :

(for existing users please backup your 1bash just in case)

Go to Guake :

Navigate to Downloads

cd /home/m1/Downloads

Below command downloads the update script

wget https://www.dropbox.com/s/cyo86xoqotplges/nvOC-19-2-update

Then run the update script

bash /home/m1/Downloads/nvOC-19-2-update

Credits to @papampi

Just a note.

Its better to use :

Code:

wget -N https://www.dropbox.com/s/cyo86xoqotplges/nvOC-19-2-update

In case there was an existing old update file in downloads folder, wget replace it with new one.

Keep calm and carry on mining...

[papampi]

Hi everyone, quick question

What would one use to monitor his rigs? Like let's say a rig crashes, how would you receive a notification?

Or is it just to set it to auto-reboot with something like watchdog and watch weekly logs to see if a rig crashed too often?

Thanks for the help

You can use Telegram alerts and webinfo to check your rigs.

[chem1990]

Hello, just made again an update dowloading the script and everything went fine.

Im just supreised that claymore is still 10.2 or am i missing something?

just for info.
i have another rig with nvidia cards running on another mining distro and claymore was updated to 10.4 i had no problem since then from random reboots... stable as a rock...
dont know if that is the reason but it is the only thing changed..

[papampi]

nvOC v0019-2.0 Community Release - Miner Update Script

Miners Update Script:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/nvOC_miner_update.sh
bash /home/m1/Downloads/nvOC_miner_update.sh

Miner Versions:

Code:

Claymore                      10.6
ccminer Tpruvot               2.2.4
Bminer                        5.3.0
DSTM                          0.5.8
KlausT ccminer                8.20
KlaustT ccminer-cryptonight   2.06
Ethminer                      0.13.0
nanashi-ccminer               2.2-mod-r2	
vertminer	              1.0.2 Stable
ANXccminer 	

If you get any errors with compiled miners re-compile it on your rig with:

KlausT ccminer:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/compile-KTccminer.sh
bash /home/m1/Downloads/compile-KTccminer.sh

KlausT ccminer cryptonight:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/compile-KTccminer-cryptonight.sh
bash /home/m1/Downloads/compile-KTccminer-cryptonight.sh

Nanashi ccminer:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/compile-NAccminer.sh
bash /home/m1/Downloads/compile-NAccminer.sh

Tpruvot ccminer:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/compile-TPccminer.sh
bash /home/m1/Downloads/compile-TPccminer.sh

Vertminer:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/compile-vertminer.sh
bash /home/m1/Downloads/compile-vertminer.sh

ASccminer:

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_miners/master/compile-ASccminer.sh
bash /home/m1/Downloads/compile-ASccminer.sh

[papampi]

1bash and 0miner v0019-2.1 pre-release changes for Bminer and new coins

Some Changes

Code:

New Coins: LUX, SUMO, DSR, ELLA, XVG, GBX, CRC
Renamed ZM_OR_EWBF to EQUIHASH_MINER
Renamed ETHMINER_or_GENOIL_or_CLAYMORE to ETHASH_MINER
Added BMINER and BMINER_SSL and ANXccminer 

Its Better to download and update your 1bash with new 1bash

Or add new coins and Bminer :

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/1bash_19-2.1_pre_release.sh
bash /home/m1/Downloads/1bash_19-2.1_pre_release.sh

Get pre-release 0miner

Code:

cd /home/m1/Downloads
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/0miner
cp /home/m1/Downloads/0miner /home/m1/0miner

Backup your 1bash and 0miner before update to 19-2.1 pre-release!!!!

[damNmad]

@papampi

Thanks mate.

Going to add all the updates on discord #how_to_do section;

I have more coins coming soon, hope I will pass them soon.

Just want to check, have you added 'phi' (ANXccminer) miner to the list??

All the new coins I'm going to add doesn't need any new miners.

Also TPccminer (tpruvot), has been compiled on my RIG with out no issue.

Thanks.

[papampi]

@papampi

Thanks mate.

Going to add all the updates on discord #how_to_do section;

I have more coins coming soon, hope I will pass them soon.

Just want to check, have you added 'phi' (ANXccminer) miner to the list??

All the new coins I'm going to add doesn't need any new miners.

Also TPccminer (tpruvot), has been compiled on my RIG with out no issue.

Thanks.

Ooops, Sorry forgot to add that.
Google wont allow direct download with wget and its too big to add to github.
Can you please upload it to nvoc-mining-os.com ?
Then I will add it and edit the new miners update script.

Thanks.

[darkness137]

Having some issues with zm miner and zencash on 2 of my rigs. using miningspeed.com for the pool and port 3062. Rigs work fine for ZCL but when switched to ZEN i recieve an authorization failure notification. I mirrored what was done on my other rig which doesn't have this issue and still see the same message before the terminal shuts down. I would appreciate some help if anyone can offer it. Currently using 19_1.4 on all 3 rigs.

[Rig4p]

Having some issues with zm miner and zencash on 2 of my rigs. using miningspeed.com for the pool and port 3062. Rigs work fine for ZCL but when switched to ZEN i recieve an authorization failure notification. I mirrored what was done on my other rig which doesn't have this issue and still see the same message before the terminal shuts down. I would appreciate some help if anyone can offer it. Currently using 19_1.4 on all 3 rigs.

I just tried to open my ZEN wallet and it gives me a server error and will not open.
I am thinking your issue is a result of something wrong with ZEN and not the pool, your rigs or nvOC.

[darkness137]

Having some issues with zm miner and zencash on 2 of my rigs. using miningspeed.com for the pool and port 3062. Rigs work fine for ZCL but when switched to ZEN i recieve an authorization failure notification. I mirrored what was done on my other rig which doesn't have this issue and still see the same message before the terminal shuts down. I would appreciate some help if anyone can offer it. Currently using 19_1.4 on all 3 rigs.

I just tried to open my ZEN wallet and it gives me a server error and will not open.
I am thinking your issue is a result of something wrong with ZEN and not the pool, your rigs or nvOC.

I dont think its an issue with zen because i can still mine with one of my rigs. Which is also on nvoc and running just fine.

[Rig4p]

I have now added 2 GTX1060 GPUs to my rig that previously had only one GTX1080.
Hash rates look reasonable but I noticed that both of the GTX1060s were running below their expected power numbers, ~62W vs. 75W.
The GTX1080 is still running around 200W as before I added these two and that is expected.
So I monitored the "screen -r temp" printout for a while and noticed this:

Code:

ERROR: Error assigning value 75 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:2]) as
       specified in assignment '[fan:2]/GPUTargetFanSpeed=75' (Unknown Error).

I see a similar message that mentions the other GTX1060.
Is this problem occurring possibly because I have mixed GPUs now?
Do I need to set individual OC/power numbers?

Thanks for the help.

I have made some progress clearing up this ERROR and it has to do with the NVIDIA driver not recognizing a card as having a "SCREEN" setup in /etc/X11/xorg.conf
When I run this command:

Code:

sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration

After a reboot, I get full control of all parameters on all cards installed including the individual power, temp and clocks which is why the 1060s I added previously were not going to full requested power.
This holds true until I change something in the system that causes the XORG to balk on reboot, at which time it resorts back to the same error again.
I run the command above again and all is well.
For some reason, some system changes cause a reset of all the parameters in xorg.conf back to default values.
I can't explain it but through trial and error I am able to work around it.  

[NameTaken]

I have now added 2 GTX1060 GPUs to my rig that previously had only one GTX1080.
Hash rates look reasonable but I noticed that both of the GTX1060s were running below their expected power numbers, ~62W vs. 75W.
The GTX1080 is still running around 200W as before I added these two and that is expected.
So I monitored the "screen -r temp" printout for a while and noticed this:

Code:

ERROR: Error assigning value 75 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:2]) as
       specified in assignment '[fan:2]/GPUTargetFanSpeed=75' (Unknown Error).

I see a similar message that mentions the other GTX1060.
Is this problem occurring possibly because I have mixed GPUs now?
Do I need to set individual OC/power numbers?

Thanks for the help.

I have made some progress clearing up this ERROR and it has to do with the NVIDIA driver not recognizing a card as having a "SCREEN" setup in /etc/X11/xorg.conf
When I run this command:

Code:

sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration

After a reboot, I get full control of all parameters on all cards installed including the individual power, temp and clocks which is why the 1060s I added previously were not going to full requested power.
This holds true until I change something in the system that causes the XORG to balk on reboot, at which time it resorts back to the same error again.
I run the command above again and all is well.
For some reason, some system changes cause a reset of all the parameters in xorg.conf back to default values.
I can't explain it but through trial and error I am able to work around it.  

I create a systemd service to run nvidia-xconfig every boot before X starts.

Code:

[Unit]                                                                                                                                                                                                     
Description=Generate xorg.conf
Before=lightdm.service

[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=/usr/bin/nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration

[Install]
WantedBy=multi-user.target

[Rig4p]

My Linux system file knowledge is rusty and was very limited when well oiled! 

Would you care to help explain where this code was added and what location?
I see /etc/systemd/
With several files and folders inside.
Thanks for any help.

[NameTaken]

My Linux system file knowledge is rusty and was very limited when well oiled!  

Would you care to help explain where this code was added and what location?
I see /etc/systemd/
With several files and folders inside.
Thanks for any help.

Code:

# cat <<EOF> /etc/systemd/system/nvidia-xconfig.service
[Unit]
Description=Generate xorg.conf
Before=lightdm.service

[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=/usr/bin/nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration

[Install]
WantedBy=multi-user.target
EOF

# systemctl enable nvidia-xconfig