[ mining os ] nvoc

[bumbu100]

Hello guys

There is anybody who are mining with P106-100?
I have low rate on eth, under 21. Using algo specific OC.

[z-axis]

Hey guys

It's been a while since I've posted cuz my rig has been humming along pretty well but yesterday the flash drive on it died and I had customized nvOC a bit and am trying to get it working again at OC speeds. I need just a little pointer from you:

- What script kicks off nvidia-settings? I have a custom xorg.conf file that need to not be overwritten. On SMOS, it's /root/utils/rclocal.sh, and with that, I can edit the script to NOT make a new xorg.conf file, but instead copy my working xorg.conf file from ~ to /etc/X11/. I can't figure out where I did this on nvOC, or how to prevent xorg.conf from being overwritten.

Can somebody remind me?

Thanks,
z

[damNmad]

Hey guys

It's been a while since I've posted cuz my rig has been humming along pretty well but yesterday the flash drive on it died and I had customized nvOC a bit and am trying to get it working again at OC speeds. I need just a little pointer from you:

- What script kicks off nvidia-settings? I have a custom xorg.conf file that need to not be overwritten. On SMOS, it's /root/utils/rclocal.sh, and with that, I can edit the script to NOT make a new xorg.conf file, but instead copy my working xorg.conf file from ~ to /etc/X11/. I can't figure out where I did this on nvOC, or how to prevent xorg.conf from being overwritten.

Can somebody remind me?

Thanks,
z

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.

ERROR : "Failed to initialize NVML: Driver/library version mismatch"

If you are on SSH try this to update your drivers first (some users confirmed that after doing this RIG is back to normal)

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

For now follow this to disable auto update on nvidia drivers (directly on Linux)

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

use these instructions if you use remote

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

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.

[damNmad]

Hello guys

There is anybody who are mining with P106-100?
I have low rate on eth, under 21. Using algo specific OC.

Hi Mate,

Algo specific OC values are for my GTX 1060 6GB cards which has samsung memory.

I'm not sure whether those values actually work with your P106-100 cards.

I will try to find the best values, mean while if you find then please share it with me, I will try to update my blog with the latest OC setting values over here :

http://krypto-mining.blogspot.co.uk/

[keno1234]

Guys this community version is still capable with 16Gb right?

I just downloaded 19-2.0. The .img file size is 16.01Gb. So I think it's not capable with 16Gb drive.

[Moordact]

Guy's

I just tried to use pampampi autoswitcher.

However I have feeling it's totally not efficient?

I only choose ZEC/ZCL/ZEN. After 8 hours It seems i have gotten very little of each?

Can you guys share me optimal settings for profit switching?

I feel maybe 24H switch or 12h switch could be better?

[papampi]

Guys this community version is still capable with 16Gb right?

I just downloaded 19-2.0. The .img file size is 16.01Gb. So I think it's not capable with 16Gb drive.

I created the image on a sandisk cruzer 16Gb
Some usb sticks has smaller or larger filesystem, try other brands or save yourself lots of trouble and get a 40Gb SSD for less than 30$

[papampi]

Guy's

I just tried to use pampampi autoswitcher.

However I have feeling it's totally not efficient?

I only choose ZEC/ZCL/ZEN. After 8 hours It seems i have gotten very little of each?

Can you guys share me optimal settings for profit switching?

I feel maybe 24H switch or 12h switch could be better?

Thats natural to feel you get less, but if you convert all your earning to btc and compare you will see you got more than what you should have earned in past 24 hour from mining one of your coins.
We usually get 5-10% less than what wtm shows for single mining.

These are the valuse I use for my self:

Code:

WTM_AUTO_SWITCH_SYNC_INTERVAL="3" # Time to sync with WTM for best coin
WTM_MIN_DIFFERENCE="8" 

About 24H, 3 days,... those are the value of past, you are not mining in past, you should chose current for both difficulty and profit.

[Moordact]

Guys this community version is still capable with 16Gb right?

I just downloaded 19-2.0. The .img file size is 16.01Gb. So I think it's not capable with 16Gb drive.

I created the image on a sandisk cruzer 16Gb
Some usb sticks has smaller or larger filesystem, try other brands or save yourself lots of trouble and get a 40Gb SSD for less than 30$

Well i have several 60gb ssd , but if i need to re-image it's more time consuming than just swapping an usb

Guy's

I just tried to use pampampi autoswitcher.

However I have feeling it's totally not efficient?

I only choose ZEC/ZCL/ZEN. After 8 hours It seems i have gotten very little of each?

Can you guys share me optimal settings for profit switching?

I feel maybe 24H switch or 12h switch could be better?

Thats natural to feel you get less, but if you convert all your earning to btc and compare you will see you got more than what you should have earned in past 24 hour from mining one of your coins.
We usually get 5-10% less than what wtm shows for single mining.

These are the valuse I use for my self:

Code:

WTM_AUTO_SWITCH_SYNC_INTERVAL="3" # Time to sync with WTM for best coin
WTM_MIN_DIFFERENCE="8" 

About 24H, 3 days,... those are the value of past, you are not mining in past, you should chose current for both difficulty and profit.

What minimum mining time do you have?

Also do you use telegram service, if so what settings you have ?

Oh and I didn't realise you are papampi xD , thanks for you contributions to this wonderfull OS!

[papampi]

Guys this community version is still capable with 16Gb right?

I just downloaded 19-2.0. The .img file size is 16.01Gb. So I think it's not capable with 16Gb drive.

I created the image on a sandisk cruzer 16Gb
Some usb sticks has smaller or larger filesystem, try other brands or save yourself lots of trouble and get a 40Gb SSD for less than 30$

Well i have several 60gb ssd , but if i need to re-image it's more time consuming than just swapping an usb

Guy's

I just tried to use pampampi autoswitcher.

However I have feeling it's totally not efficient?

I only choose ZEC/ZCL/ZEN. After 8 hours It seems i have gotten very little of each?

Can you guys share me optimal settings for profit switching?

I feel maybe 24H switch or 12h switch could be better?

Thats natural to feel you get less, but if you convert all your earning to btc and compare you will see you got more than what you should have earned in past 24 hour from mining one of your coins.
We usually get 5-10% less than what wtm shows for single mining.

These are the valuse I use for my self:

Code:

WTM_AUTO_SWITCH_SYNC_INTERVAL="3" # Time to sync with WTM for best coin
WTM_MIN_DIFFERENCE="8" 

About 24H, 3 days,... those are the value of past, you are not mining in past, you should chose current for both difficulty and profit.

What minimum mining time do you have?

Also do you use telegram service, if so what settings you have ?

Oh and I didn't realise you are papampi xD , thanks for you contributions to this wonderfull OS!

Minimum mining is disabled in latest version v0011 because it was causing wtm to stop working.
If you have v0008 just set it to 0

I only use telegram alerts, no periodic messages.


Any thing to help the community

[matrix17]

Hi,

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

[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