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

[papampi]

Hi,

Does nvOC have a setting for auto shutdown when a certain temperature is reached on any of the video cards?
Thanks.

Nope, Temp Control tries to keep your cards temp bellow the TARGAET_TEMP from 1bash by adding 5 % steps to minimum fan speed.
If it cant get it down and fan speed reach 100% it start lowering GPU power until the temp reaches target and fan speed reaches 90%, then it reset values to default.

[Havesovgosh]

Hi Papampi, Hi all,

I've rig with 019 1.3, Motherboard : M250-mining edition, and 106-100 16xGPU's
It's running normally till the driver upgrade issue. So, made a fresh install of 2.0
But during the first boot my screen still remains black, I can see only ubuntu load, drive check with blocks and black screen. On this Mobo monitor connection is with HDMI port. On GPU's no monitor connection port, you can connect if you will remove first panel etc., but now I can't do it.
Also when I logged in with ssh and run 2unix, I saw this error in terminal:
-----------------------------------------------------------
m1@m1-desktop:~$ bash /home/m1/2unix
nvOC v0019-2.0 - Community Release

 nvOC v0019-2.0 - Community Release


/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_DISPLAY (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_SCREEN (screen)' failed
  from _keybinder import *

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

(guake:8165): 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

-------------------------------------------------

Please support.


 

[nkym_s1]

I've had nvOC running fairly stable for a few months, but recently a 'Storage Space Low' warning (can't remember exactly what it said) started appearing, and today it showed a message saying '0mb space left' (I think, because the message appeared for only a few seconds before the OS rebooted). Now when I start up the OS, the interface is missing. The terminal does start automatically, but nothing else shows.

Any ideas what's going on?
Any help would be appreciated.

[papampi]

Hi Papampi, Hi all,

I've rig with 019 1.3, Motherboard : M250-mining edition, and 106-100 16xGPU's
It's running normally till the driver upgrade issue. So, made a fresh install of 2.0
But during the first boot my screen still remains black, I can see only ubuntu load, drive check with blocks and black screen. On this Mobo monitor connection is with HDMI port. On GPU's no monitor connection port, you can connect if you will remove first panel etc., but now I can't do it.
Also when I logged in with ssh and run 2unix, I saw this error in terminal:
-----------------------------------------------------------
m1@m1-desktop:~$ bash /home/m1/2unix
nvOC v0019-2.0 - Community Release

 nvOC v0019-2.0 - Community Release


/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_DISPLAY (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_SCREEN (screen)' failed
  from _keybinder import *

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

(guake:8165): 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

-------------------------------------------------

Please support.


 

First tell me why you want to start 2unix manually?
2unix only start 3main.
Since you have only p106 you should run full headless, right?


So start the rig, check if 3main is running or not

Code:

ps ax | grep 3main

Then check if miner, watchdog, temp ,... running or not

Code:

ps ax | grep -i screen

[papampi]

I've had nvOC running fairly stable for a few months, but recently a 'Storage Space Low' warning (can't remember exactly what it said) started appearing, and today it showed a message saying '0mb space left' (I think, because the message appeared for only a few seconds before the OS rebooted). Now when I start up the OS, the interface is missing. The terminal does start automatically, but nothing else shows.

Any ideas what's going on?
Any help would be appreciated.

Older nvOC versions used to write logs to disk and if you have small disk or usb thats normal


Removing old log files should solve your problem
I think older mining log files are:

Code:

5_restarlog
6_templog
screenlog.0
7_alert*

They should be in /home/m1

As soon as rig started and terminal opened close it. Do your cleaning then open gnome-terminal

You can also set clear log files on boot in 1bash

Code:

CLEAR_LOGS_ON_BOOT="YES"

[Havesovgosh]

Hi Papampi, Hi all,

I've rig with 019 1.3, Motherboard : M250-mining edition, and 106-100 16xGPU's
It's running normally till the driver upgrade issue. So, made a fresh install of 2.0
But during the first boot my screen still remains black, I can see only ubuntu load, drive check with blocks and black screen. On this Mobo monitor connection is with HDMI port. On GPU's no monitor connection port, you can connect if you will remove first panel etc., but now I can't do it.
Also when I logged in with ssh and run 2unix, I saw this error in terminal:
-----------------------------------------------------------
m1@m1-desktop:~$ bash /home/m1/2unix
nvOC v0019-2.0 - Community Release

 nvOC v0019-2.0 - Community Release


/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_DISPLAY (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_SCREEN (screen)' failed
  from _keybinder import *

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

(guake:8165): 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

-------------------------------------------------

Please support.


 

First tell me why you want to start 2unix manually?
2unix only start 3main.
Since you have only p106 you should run full headless, right?


So start the rig, check if 3main is running or not

Code:

ps ax | grep 3main

Then check if miner, watchdog, temp ,... running or not

Code:

ps ax | grep -i screen

Hi,
thanks for soon response.

I have start the rig and no GUI are seen. So, I logged in with ssh and check does the miner starts or not. So, it's not started. that's why I want to check wha't going there.


Below are command:

m1@m1-desktop:~$ ps ax | grep 3main
 2132 pts/0    S+     0:00 grep --color=auto 3main


m1@m1-desktop:~$ ps ax | grep -i screen
 2164 pts/0    S+     0:00 grep --color=auto -i screen


Since you have only p106 you should run full headless, right?

Yes. and it's configured as 'YES'

[pzyxian]

I tried to mine SIBcoin. However, I see the "Stratum authentication failed" in the screen.

I used all defaults and the pool by default is sib.suprnova.cc:3458, intensity is set to 21.
I didn't modify worker name or anything else.
Suprnova seems to support anonymous mining on some coins (a few equihash ones) However, I'm not sure about SIB coin.  I might need to create an account.

Anyone wanna comment?

nvOC version community 2.0

[Rumo]

I tried to mine SIBcoin. However, I see the "Stratum authentication failed" in the screen.

I used all defaults and the pool by default is sib.suprnova.cc:3458, intensity is set to 21.
I didn't modify worker name or anything else.
Suprnova seems to support anonymous mining on some coins (a few equihash ones) However, I'm not sure about SIB coin.  I might need to create an account.

Anyone wanna comment?

nvOC version community 2.0

As far as i know Suprnova not supports anonymous mining. You need a account and you need to create the workers first on their website. Without the right worker you can not mine on Suprnova.

[papampi]

Hi Papampi, Hi all,

I've rig with 019 1.3, Motherboard : M250-mining edition, and 106-100 16xGPU's
It's running normally till the driver upgrade issue. So, made a fresh install of 2.0
But during the first boot my screen still remains black, I can see only ubuntu load, drive check with blocks and black screen. On this Mobo monitor connection is with HDMI port. On GPU's no monitor connection port, you can connect if you will remove first panel etc., but now I can't do it.
Also when I logged in with ssh and run 2unix, I saw this error in terminal:
-----------------------------------------------------------
m1@m1-desktop:~$ bash /home/m1/2unix
nvOC v0019-2.0 - Community Release

 nvOC v0019-2.0 - Community Release


/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_DISPLAY (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_SCREEN (screen)' failed
  from _keybinder import *

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

(guake:8165): 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

-------------------------------------------------

Please support.


  

First tell me why you want to start 2unix manually?
2unix only start 3main.
Since you have only p106 you should run full headless, right?


So start the rig, check if 3main is running or not

Code:

ps ax | grep 3main

Then check if miner, watchdog, temp ,... running or not

Code:

ps ax | grep -i screen

Hi,
thanks for soon response.

I have start the rig and no GUI are seen. So, I logged in with ssh and check does the miner starts or not. So, it's not started. that's why I want to check wha't going there.


Below are command:

m1@m1-desktop:~$ ps ax | grep 3main
 2132 pts/0    S+     0:00 grep --color=auto 3main


m1@m1-desktop:~$ ps ax | grep -i screen
 2164 pts/0    S+     0:00 grep --color=auto -i screen


Since you have only p106 you should run full headless, right?

Yes. and it's configured as 'YES'

Is auto start miner set to yes ?

Code:

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

Run

Code:

~/nvOC report

And see if all your settings are correct


Also try this:

Code:

      sudo nvidia-xconfig --enable-all-gpus --cool-bits=12
      cd /home/m1
      echo XORG_UPDATED > '/home/m1/xorg_flag'
      sudo reboot

[papampi]

I tried to mine SIBcoin. However, I see the "Stratum authentication failed" in the screen.

I used all defaults and the pool by default is sib.suprnova.cc:3458, intensity is set to 21.
I didn't modify worker name or anything else.
Suprnova seems to support anonymous mining on some coins (a few equihash ones) However, I'm not sure about SIB coin.  I might need to create an account.

Anyone wanna comment?

nvOC version community 2.0

you should add workers in suprnova,
it does not add them automatically like miningpoolhub

[papampi]

Hello, guys!

I use the system 0019 + miner "optiminer 2.0"
periodically I receive an error "Segmentation fault"

What i need to do?


GPU - 1060 6 gb
CPU - i3 Intel core
Moth - Asus PRIME Z370-A
Memory - Kingston ddr4 - 4 GB x 2 = 8 GB

Sorry I have no experience with optiminer
may be some one who has more experience with it can help you.

[Chieftec]

Good afternoon!

I have a problem that users previously described - at the start of the computer the error XORG Problem detected (reboot endlessly)

I inserted the cable into the video card, not the motherboard.
Tried without a cable - just log in to ssh, at the command bash 1bash neither errors, nor start.

What's the matter?

[papampi]

Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal AMD+NVIDIA GPU Miner v10.3 - LINUX

Update script for v0019-2.0
Run:

Code:

cd /home/m1/Downloads
wget https://www.dropbox.com/s/fudqtbbziy3bxey/claymore-10.3-update.sh
bash /home/m1/Downloads/claymore-10.3-update.sh

[papampi]

Good afternoon!

I have a problem that users previously described - at the start of the computer the error XORG Problem detected (reboot endlessly)

I inserted the cable into the video card, not the motherboard.
Tried without a cable - just log in to ssh, at the command bash 1bash neither errors, nor start.

What's the matter?

If you are in nvOC v0019-2.0 please run and post output of

Code:

~/nvOC report

[z-axis]

Did they died because of the Driver update issue??

Were you using the nvOC of version 19-1.3 or the version older than 19-1.3??

If this is the error you are having, I will post some solutions which were used last time when we had this issue.

This issue has been fixed from 19-1.4 and in the later versions too. I would recommend you to upgrade your RIG to the 2.0 version (where number of issues are dealt with).

Hope it helps.

Hey damNmad,

I am running a 19 GPU rig and can't rely on the auto-creation of xorg.conf because it will detect all 19 cards and will list all 19 in sections Server Layout, Screens, and Devices. If the Server Layout section has more than 16 screens listed in it, X will fail to start (see xorg.0.log) and without X starting, nvidia-settings cannot run and no overclocking will occur for any of the 19 cards.

The trick is to make it so that only 16 screens appear in Server Layout, but allow all 19 to be listed in both Screens and Devices. The result of this is that 16 GPUs will be OC'd and 3 won't. But that's better than none getting OC'd.

I *was* running 1.3 when it tanked. I worked on it until things just didn't seem right so I reflashed 1.3 back on my USB stick and I got it running again, but it was unstable and would either slow way down OR the miner process would totally quit. So I decided to move to the community version 1.4v2. This also has not solved my issue so far.

My only solution thusfar has been to force my version of xorg.conf on every boot, and for whatever reason, something changed and I'm getting some sort of default configuration written into xorg.conf that only has a few cards and they aren't detected as nvidia. So the miner never starts cuz there are no GPUs detected, I guess.

So where I am now is that I have to:

1. Edit /etc/init.d/gpu and commenting out the sections that mv xorg.conf to xorg.conf.backup and create a new one based on nvidia-smi queries.
2. Place my custom xorg.conf in /etc/X11
3. Take that same xorg.conf file, rename it to 52-nvidia.conf, and put it in /usr/share/X11/xorg.conf.d/

Any thoughts?

-z

[joshuajones02]

Is there a ccminer in nvOC that supports the PHI1612 algorithm? I think I can figure out how to add the coin if I can get the Linux miner installed on my clients, been trying to view through the directories and haven't found any of the ccminer's readme files that say they support it. Thanks

[z-axis]

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?

[LuKePicci]

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?

[CryptAtomeTrader44]

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?

The last time i had these guake errors, i read on this thread that i could resolve it by using this commands
apt  update
and
apt upgrade

I tried them, but i was really skeptcal iat the first time.

It effectively resolved my problem that i never seen again on my v19-2.0.

By reading you comments, having a 19 GPU MB seems more complicated than i thought :-(

I'm not able to help you more for your GPU Xorg detection.

Good luck for that

[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?