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

[papampi]

I'm back!

So after all that, I don't get miner, watchdog, temp screens. So I tried to kick start it with ./2unix and got this lovely response:

Code:

/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
/usr/lib/python2.7/dist-packages/keybinder/__init__.py:26: GtkWarning: IA__gdk_keymap_get_for_display: assertion 'GDK_IS_DISP
LAY (display)' failed
  from _keybinder import *
/usr/lib/python2.7/dist-packages/keybinder/__init__.py:26: GtkWarning: IA__gdk_screen_get_root_window: assertion 'GDK_IS_SCRE
EN (screen)' failed
  from _keybinder import *

** (main.py:2023): WARNING **: keybinder_init: Unable to open display

(guake:2023): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/guake/main.py", line 239, in <module>
    exec_main()
  File "/usr/lib/python2.7/dist-packages/guake/main.py", line 230, in exec_main
    if not test_gconf():
  File "/usr/lib/python2.7/dist-packages/guake/common.py", line 52, in test_gconf
    return c.dir_exists('/apps/guake')
glib.GError: No D-BUS daemon running

Any ideas?

In 1bash you set local or remote to remote?

[1714534233]

1714534233

[1714534233]

1714534233

[1714534233]

1714534233

[1714534233]

1714534233

[1714534233]

1714534233

[FNT]

Hi guys,

I'm using lastest stable version 19.2.-003. Thanks a lot for development!
With "auto switch", three coins. works good so far.

I'm using 2x1080, 2x1070, 2x1070TI, 1x1060 GPUs and want to use an "auto OC" or good settings for the cards.
Any ideas where to set this?
The old "version" 1.4. - I think - had an "auto OC" option...

Thanks a lot and bye!

PS: I don't want to use the individual setting option.

[papampi]

Hi guys,

I'm using lastest stable version 19.2.-003. Thanks a lot for development!
With "auto switch", three coins. works good so far.

I'm using 2x1080, 2x1070, 2x1070TI, 1x1060 GPUs and want to use an "auto OC" or good settings for the cards.
Any ideas where to set this?
The old "version" 1.4. - I think - had an "auto OC" option...

Thanks a lot and bye!

PS: I don't want to use the individual setting option.

You cant set ALGO_SPECIFIC_OC to match all your different cards, you should set individual settings for each card.
ALGO_SPECIFIC_OC only works on rigs with same cards.

You may get what you want from PXA fork, with Auto OC.

[FNT]

Hi,

thanks for info.
Don't want to setup image new, as rig is running ok. PXA

Are there any thoughts about to implement Auto OC in your version?
Why do you excluded it?

Thanks and bye, FNT

[papampi]

Hi,

thanks for info.
Don't want to setup image new, as rig is running ok. PXA

Are there any thoughts about to implement Auto OC in your version?
Why do you excluded it?

Thanks and bye, FNT

fullzero's nvOC never had Auto OC and It was never included in community release to get excluded.
Community Release is based on fullzero works and beliefs, he never liked the idea of rigs settings be hosted on remote servers and we believe that too.

I think a mild/normal overclock will give much more profit in long run than push the cards to the limit and change the OC all the time to get a little more hash rate, and PXA fork already has it, so if any one wants Auto OC they can use it 

So the answer to your question will be no. there are no plans to have Auto OC, and I don't think there ever be.

[papampi]

KlausT ccminer 8.19pre compiled with cuda 9.1

Change log:

Code:

fix x17 for Linux builds without NVML
trying to fix crashes under Linux
change exit behaviour
show default intensity when not using the -i option
add gpu number to the cuda error messages

Known Problems:
With some algos Linux users will get validation errors. In this case please use the option --no-cpu-verify.
On some systems ccminer will crash when there are connection problems.

I tested it and it gave me around 630 Kh/s on Neoscrypt with zotac 1060 (PL 70, OC 100, MC 400):

Code:

[ccminer 8.19-KlausT (64bit) for nVidia GPUs
Compiled with GCC 5.4 using Nvidia CUDA Toolkit 9.1

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.

[2018-01-13 15:23:16] NVML GPU monitoring enabled.
[2018-01-13 15:23:16] 2 miner threads started, using 'neoscrypt' algorithm.
[2018-01-13 15:23:16] Starting Stratum on stratum+tcp://hub.miningpoolhub.com:20510
0 
[2018-01-13 15:23:16] Stratum difficulty set to 2048
[2018-01-13 15:23:17] Stratum difficulty set to 64
[2018-01-13 15:23:19] GPU #0: using default intensity 13.000
[2018-01-13 15:23:25] hub.miningpoolhub.com:20510 neoscrypt block 2045653
[2018-01-13 15:23:27] GPU #0: Zotac GTX 1060 6GB, 626.99 kH/s
[2018-01-13 15:23:35] accepted: 1/1 (100.00%), 626.99 kH/s yay!!!

Code:

cd /home/m1/Downloads/miners
wget https://www.dropbox.com/s/wisateri7w3ipp4/KTccminer-8.19-pre.tar.gz
tar -xzvf KTccminer-8.19-pre.tar.gz

Please test it first on your rig before replace with your current version
Test it with:
Stop miner, watchdog ,...

Code:

pkill -e screen

Run miner:

Code:

/home/m1/Downloads/miners/KTccminer-8.19-pre/ccminer -a ALGO -o SERVER_ADDRESS:PORT   -u USERNAME.WORKERNAME -p x

If all was ok copy it to KTccminer folder

Code:

cp /home/m1/Downloads/miners/KTccminer-8.19-pre/* /home/m1/KTccminer/

Restart normal jobs:

Code:

pkill -f 3main

[papampi]

Nice android app for auto switchers who mine on MiningPoolHub: MPH Stats
Its great, shows all your workers in 1 page, no need to scroll through all mph web site to find out your workers ...

Info:

Code:

Load your Mining Pool Hub balances page and view it as a single Crypto Currency or FIAT currency.
Supported base currencies:
FIAT: USD, CAD, GBP, EUR
Crypto: BTC, ETH, LTC, XMR

The amount you'll see in the app is the sum of your balance, unconfirmed balance, auto-exchange, unconfirmed auto-exchange and on exchange.

Also monitor your workers, the coin each worker mine and the current hash rate.

[NameTaken]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

[papampi]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

On v0019-2.0
Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Earlier ... No Option.

[NameTaken]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Using nvOC_v0019_1.4 and I don't see AUTO_START_MINER in 1bash.

[papampi]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Using nvOC_v0019_1.4 and I don't see AUTO_START_MINER in 1bash.

Sorry, Edited my original message

Edit:
You can close gnome-terminal as soon as it opened.

[NameTaken]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Using nvOC_v0019_1.4 and I don't see AUTO_START_MINER in 1bash.

sorry, Edited my original message

Edit:
You can close gnome-terminal as soon as it opened.

This is for headless rigs. Downloading V0019-2.0 now. For AUTO_UPDATE is there a choice to disable it or do I have to edit 10periodic and 20auto-upgrades?

[papampi]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Using nvOC_v0019_1.4 and I don't see AUTO_START_MINER in 1bash.

sorry, Edited my original message

Edit:
You can close gnome-terminal as soon as it opened.

This is for headless rigs. Downloading V0019-2.0 now. For AUTO_UPDATE is there a choice to disable it or do I have to edit 10periodic and 20auto-upgrades?

We dont have 10periodic and 20auto-upgrades in 19-2.0, I think you are talking about PXA fork.

[NameTaken]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Using nvOC_v0019_1.4 and I don't see AUTO_START_MINER in 1bash.

sorry, Edited my original message

Edit:
You can close gnome-terminal as soon as it opened.

This is for headless rigs. Downloading V0019-2.0 now. For AUTO_UPDATE is there a choice to disable it or do I have to edit 10periodic and 20auto-upgrades?

We dont have 10periodic and 20auto-upgrades in 19-2.0, I think you are talking about PXA fork.

I Googled how to disable nvOC update which lead me to https://nvoc-mining-os.com/2017/10/25/how-to-prevent-automatic-updates/. Is nvoc-mining-os.com not nvOC's official website?

[papampi]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Using nvOC_v0019_1.4 and I don't see AUTO_START_MINER in 1bash.

sorry, Edited my original message

Edit:
You can close gnome-terminal as soon as it opened.

This is for headless rigs. Downloading V0019-2.0 now. For AUTO_UPDATE is there a choice to disable it or do I have to edit 10periodic and 20auto-upgrades?

We dont have 10periodic and 20auto-upgrades in 19-2.0, I think you are talking about PXA fork.

I Googled how to disable nvOC update which lead me to https://nvoc-mining-os.com/2017/10/25/how-to-prevent-automatic-updates/. Is nvoc-mining-os.com not nvOC's official website?

Oh, You meant ubuntu updates in /etc/apt/ ... sorry my bad thought yo are talking about nvOC updates.

Yes thats the way to do it. its already disabled in 19-2.0

Edot:
You can also run the update script, instead of downloading full image.

Code:

cd /home/m1/Downloads
wget https://www.dropbox.com/s/cyo86xoqotplges/nvOC-19-2-update
bash /home/m1/Downloads/nvOC-19-2-update

Edit 2:
I think I forgot to disable updates in update script, will add it to update script tomorrow.

[arsen_a]

Hi all! My rig has yet to be built but reading about the full headless mode for P106_100 made me think on this aspect of my project I don't resolved yet. Does nvOC also supports full headless mode for other nvidia cards with video outputs? I mean, can I run nvOC on a rig made only of 1070s without a monitor attached after all setup is completed?

Hi LuKePicci,

Yes, you can! I have 4 rigs running with nvOC and no any monitor attached.
All I need is SSH 

[NameTaken]

I turned almost everything off in 1bash but how to configure 1bash to disable auto starting mining process?

Bellow COIN="xxxx"

Code:

AUTO_START_MINER="YES"      # YES or NO # Set this to NO when troubleshooting, this will prevent the watchdog restarting the rig

Using nvOC_v0019_1.4 and I don't see AUTO_START_MINER in 1bash.

sorry, Edited my original message

Edit:
You can close gnome-terminal as soon as it opened.

This is for headless rigs. Downloading V0019-2.0 now. For AUTO_UPDATE is there a choice to disable it or do I have to edit 10periodic and 20auto-upgrades?

We dont have 10periodic and 20auto-upgrades in 19-2.0, I think you are talking about PXA fork.

I Googled how to disable nvOC update which lead me to https://nvoc-mining-os.com/2017/10/25/how-to-prevent-automatic-updates/. Is nvoc-mining-os.com not nvOC's official website?

Oh, You meant ubuntu updates in /etc/apt/ ... sorry my bad thought yo are talking about nvOC updates.

Yes thats the way to do it. its already disabled in 19-2.0

Edot:
You can also run the update script, instead of downloading full image.

Code:

cd /home/m1/Downloads
wget https://www.dropbox.com/s/cyo86xoqotplges/nvOC-19-2-update
bash /home/m1/Downloads/nvOC-19-2-update

Edit 2:
I think I forgot to disable updates in update script, will add it to update script tomorrow.

I'm going to dd more USB drives so I want the update to date image.

Code:

AUTO_UPDATE="STABLE"        # STABLE or BETA # To update to the latest STABLE or BETA releases, manually run 4update in guake terminal

4update will only run manually instead of automatically by some daemon, is that correct?

[CryptAtomeTrader44]

KlausT ccminer 8.19pre compiled with cuda 9.1

Change log:

Code:

fix x17 for Linux builds without NVML
trying to fix crashes under Linux
change exit behaviour
show default intensity when not using the -i option
add gpu number to the cuda error messages

Known Problems:
With some algos Linux users will get validation errors. In this case please use the option --no-cpu-verify.
On some systems ccminer will crash when there are connection problems.

I tested it and it gave me around 630 Kh/s on Neoscrypt with zotac 1060 (PL 70, OC 100, MC 400):

Code:

[ccminer 8.19-KlausT (64bit) for nVidia GPUs
Compiled with GCC 5.4 using Nvidia CUDA Toolkit 9.1

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.

[2018-01-13 15:23:16] NVML GPU monitoring enabled.
[2018-01-13 15:23:16] 2 miner threads started, using 'neoscrypt' algorithm.
[2018-01-13 15:23:16] Starting Stratum on stratum+tcp://hub.miningpoolhub.com:20510
0 
[2018-01-13 15:23:16] Stratum difficulty set to 2048
[2018-01-13 15:23:17] Stratum difficulty set to 64
[2018-01-13 15:23:19] GPU #0: using default intensity 13.000
[2018-01-13 15:23:25] hub.miningpoolhub.com:20510 neoscrypt block 2045653
[2018-01-13 15:23:27] GPU #0: Zotac GTX 1060 6GB, 626.99 kH/s
[2018-01-13 15:23:35] accepted: 1/1 (100.00%), 626.99 kH/s yay!!!

Code:

cd /home/m1/Downloads/miners
wget https://www.dropbox.com/s/wisateri7w3ipp4/KTccminer-8.19-pre.tar.gz
tar -xzvf KTccminer-8.19-pre.tar.gz

Please test it first on your rig before replace with your current version
Test it with:
Stop miner, watchdog ,...

Code:

pkill -e screen

Run miner:

Code:

/home/m1/Downloads/miners/KTccminer-8.19-pre/ccminer -a ALGO -o SERVER_ADDRESS:PORT   -u USERNAME.WORKERNAME -p x

If all was ok copy it to KTccminer folder

Code:

cp /home/m1/Downloads/miners/KTccminer-8.19-pre/* /home/m1/KTccminer/

Restart normal jobs:

Code:

pkill -f 3main

I did not install CUDA 9 on my rig, but how many KH did you gain compared to Klaust version 8.17?

[NameTaken]

Taking a quick look at the update script, you can condense things by instead of

Code:

wget -c https://www.dropbox.com/s/ys9pgw0cvmfwd0y/ccminer-2.2.3-tpruvot.tar.gz
tar -xvzf ccminer-2.2.3-tpruvot.tar.gz
rm ccminer-2.2.3-tpruvot.tar.gz
cp -R /home/m1/Downloads/miners/TPccminer/* /home/m1/TPccminer/

converting it to a one-liner.

Code:

wget -O- https://www.dropbox.com/s/ys9pgw0cvmfwd0y/ccminer-2.2.3-tpruvot.tar.gz | tar -xzC /home/m1/TPccminer/ --strip 1

Also instead of echoing everything, just add

Code:

#!/bin/bash
set -x

to print to STDOUT the commands this script is running.

[Tigel]

fullzero's nvOC never had Auto OC and It was never included in community release to get excluded.
Community Release is based on fullzero works and beliefs, he never liked the idea of rigs settings be hosted on remote servers and we believe that too.

I think a mild/normal overclock will give much more profit in long run than push the cards to the limit and change the OC all the time to get a little more hash rate, and PXA fork already has it, so if any one wants Auto OC they can use it 

So the answer to your question will be no. there are no plans to have Auto OC, and I don't think there ever be.

I tried Auto OC with PXA fork and it was not my thing. Regardless, have you considered something which could be considered "algorythm based individual overclocking" ? I believe there are quite a few people who have built rigs by bying one GPU from here and another GPU from there, resulting in seriously mixed configurations. And they might be willing to tweak the hell out of it. And tbh, isn't that part of the deal.

And, yes, I understand this would bloat config files beyond imagination.

--
Tigel