Search content
Sort by
Showing 15 of 15 results by 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
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.
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
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'
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
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.
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
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.
Re: [OS] nvOC Nvidia Mining OS FORK v PXA-1.9.5 (NEWLY UPDATED)
*****************************************
nvOC by PoisonXA
A fork of fullzeros nvOC
Current Version 1.9.5
##Updated Often|You can auto update to 1.9.5 from version 1.9.1 or higher
##Discord Link: https://discord.gg/bRndt86
For the latest patch notes go to: https://pastebin.com/VswytHD0
Thanks for your contributions: fullzero, papampi , kk003, damNmad, meligo and leenoox
*****************************************
nvOC by PoisonXA
A fork of fullzeros nvOC
Current Version 1.9.5
##Updated Often|You can auto update to 1.9.5 from version 1.9.1 or higher
##Discord Link: https://discord.gg/bRndt86
For the latest patch notes go to: https://pastebin.com/VswytHD0
Thanks for your contributions: fullzero, papampi , kk003, damNmad, meligo and leenoox
*****************************************
Our developer doesnt ask for a donation, but he provides the ability to donate less than 1% of your mining endeavors on rigs running on nvOC to help support the project. This donation is optional and if you select NO, then nothing will be taken. But, remember, he has a family to feed too (including a young baby)!
nvOC is a fork of the original fullzero nvOC mining operating system. Currently, the underlying operating system is Ubuntu 16.04 LTS. But, we are considering changing that for a more lightweight platform.
As of right now, nvOC supports telegram, SSH, and Teamviewer, all out of the box. Of course, you need to know your way around command line for SSH, but otherwise, the software is designed to be robust.
You can find our latest downloads in the #downloads channel of our Discord, where there are frequently posted updates for the software and fix bugs, also where the developer and his dinosaurs provides software support for free.
nvOC is fully supported from a USB boot drive and requires nothing fancy in terms of I/O usage or the like. In fact, we recommend you use USBs over a mechanical or SSD drive.
To use the software it is simple, download it from the #downloads channel in our Discord, unzip it, run the etcher software, select your USB drive, and Etch. No complicated editing of grub menus or frustrating linux quarks. Once etched, go ahead and boot up the USB and let the software check for any minor updates, the software will usually reboot after the update.
Everything you need is literally located in the $Home directory of the Ubuntu Install. In most cases, all you need to do is edit the 1Bash with your mining details and confirm which built in mining software you wish to you, and off you are.
Literally, youre done for a basic 1-coin configuration. Save the bash, and click on the terminal icon. That easy.
Features Set :
- Auto-overclocking technology: System will detect which manufacture makes your card, and apply overclocks to the card to maximize your performance on the fly.
Dual Windows for added system visability: See errors and an extensive log to make sure everything is optimal.
Watchdog: System will watch for system instability and take the appropriate action, either by restarting the system, the miner, or even each individual GPU that fails.
Individual overclocking parameters: You can set individual overclocks per card that you wish nvOC to maintain.
Quake and Terminal commands: Troubleshooting and managing your miners have never been easier.
Set Power limits, Fan Speeds, and Temperature Controls: all within the confinement of $HOME.
Built-in Profitability Detection System: Do you like to mine multiple coins, but dont like checking whattomine every second of the day? Well, nvOC will check the site for you and apply the set conditions that you want. This work was originally created by Papami, enhanced by PoisonXA
Algos Everywhere!!!: nvOC supports more algorithms than you thought ever existed. Head over to our pastebin for specific patch note details.
Support Every Day: PoisonXA and his dinosaurs are on Discord to help solve your problems. If we cant talk you through it, we can remote into your machine, once you enable TeamViewer and solve most problems within minutes.
The future and what it entails for PXA nvOC:
Quote
In the future I plan to make this OS as simple as possible. Future updates will allow users to control the system using a simple WEB user interface. You will be able to simply edit your address and pool and press start mining. The OS its self will automate setup and adjust all setting to work optimally with your components. You will have simple choices like, Optimal or Power Saving modes.
My Pledge to PXA's nvOC User Base:
Quote
I will never charge you for the program or services and will only work on an optional donation system. You can donate directly or donate hash power. Also, I will provide support via the Discord channel and continue improving nvOC based on the feedback of the community. If I am unable to maintain this commitment, I will notify the community and provide key members with any assistance they need to take over in my absence. nvOC is currently my primary focus as it helps me manage my own systems and provide for my family.
LATEST 1.9.5 Changes and Updates 1/1/2018
Code:
Update 1.9.5 (BRAND NEW) 1.1.2018
HAPPY NEW YEARS!!!
fixed more bugs plaguing the 1.9 update and all updates until this one
- fixed the donate bug
- fixed the global settings bug
Updated Watchdog
- added more checksum and delays for ccminer and the such
- added an automatic sensitivity adjuster no more needing to adjust ri
- added cc-miner checkers to allow cc-miner to connect
Updated Temp Control
- temp control now waits for cc-miner to connect before adjusting
- temp control now checks how many cards and adjusts itself for the amount of cards
- allowing temp control to adjust fans and power quicker than before
Updated Auto Overclocker
- auto overclocker now grabs its intelligence from the cloud and will be updated more frequently than before
- auto overclocker adjusts cards faster than before and closer to its max
- auto overclocker now saves its last recorded good overclock to its alerts/oclastlog file
- auto overclocker now recognizes more brands and cards and algos than before
Updated performance
- now the OS switches between miners seamlessly
- improved CPU allotment for miners for enhanced performance
- improved layout of all logs for better performance
- improved system layout overall for clarity
- added more files to ram on boot to allow less i/o to pen drive
- added a pxa menu for faster control of miners via local or remote
Updated WTM Switcher
- fixed a few bugs with switcher that didn't let it register switches
- fixed the dreaded no coin in 1bash issue
- a lot more bug fixes to list and features added but its NEW YEARS!
HAPPY NEW YEARS!!!
fixed more bugs plaguing the 1.9 update and all updates until this one
- fixed the donate bug
- fixed the global settings bug
Updated Watchdog
- added more checksum and delays for ccminer and the such
- added an automatic sensitivity adjuster no more needing to adjust ri
- added cc-miner checkers to allow cc-miner to connect
Updated Temp Control
- temp control now waits for cc-miner to connect before adjusting
- temp control now checks how many cards and adjusts itself for the amount of cards
- allowing temp control to adjust fans and power quicker than before
Updated Auto Overclocker
- auto overclocker now grabs its intelligence from the cloud and will be updated more frequently than before
- auto overclocker adjusts cards faster than before and closer to its max
- auto overclocker now saves its last recorded good overclock to its alerts/oclastlog file
- auto overclocker now recognizes more brands and cards and algos than before
Updated performance
- now the OS switches between miners seamlessly
- improved CPU allotment for miners for enhanced performance
- improved layout of all logs for better performance
- improved system layout overall for clarity
- added more files to ram on boot to allow less i/o to pen drive
- added a pxa menu for faster control of miners via local or remote
Updated WTM Switcher
- fixed a few bugs with switcher that didn't let it register switches
- fixed the dreaded no coin in 1bash issue
- a lot more bug fixes to list and features added but its NEW YEARS!
Zip File sha256:
Code:
8cf0c7e7e26fd0a5ab2413b2b4921ffebaae2d2d3669b1b4350d441f1c502fd5
Image File sha256:Code:
fdd89364baa3da4a319c4097adacc4dfd757c01a685ce02b4efe9807bba004a5
DONATION WALLETS
BTC: 15CCvL67dvDUkNxj7UXD1D73cngmZahr2v
LTC: Lg5uMeWq9UhmKfz6ABAef5NUvQfeEopJW6
BTG: GW9xzyCgtLC6JHwZu8kxYU7MyKX2YMyRMp
ETC: 0x9649cb67f838521545dbb842ff249c18db9e32eb
MONA: MDUH4mg6jTXz1VQR2ResJk2TLLfQLswsBm
ZEC: t1gSkECXrMJwjJ585ef15uYrsuFyaaLHu9D
CANN: CVZhGRDobu216u4sPHLiCanQ2c9NYAZJkG
VERT: VpMdKDUPcrGmkhBirNvanY15ZVhKDpZ6yZ
ETH: 0x88eAa1B1a234fCe6EC738789CEa80BBaBbcBF003
Thanks to all of you for your support!
LTC: Lg5uMeWq9UhmKfz6ABAef5NUvQfeEopJW6
BTG: GW9xzyCgtLC6JHwZu8kxYU7MyKX2YMyRMp
ETC: 0x9649cb67f838521545dbb842ff249c18db9e32eb
MONA: MDUH4mg6jTXz1VQR2ResJk2TLLfQLswsBm
ZEC: t1gSkECXrMJwjJ585ef15uYrsuFyaaLHu9D
CANN: CVZhGRDobu216u4sPHLiCanQ2c9NYAZJkG
VERT: VpMdKDUPcrGmkhBirNvanY15ZVhKDpZ6yZ
ETH: 0x88eAa1B1a234fCe6EC738789CEa80BBaBbcBF003
Thanks to all of you for your support!
Hi Poision,
After clean install can I use my old 1bash from 1.9.1?
Hi,
I'm trying to use telegram alerts, but didn't receive any messages. I can see in Guake the following error:
bash /home/m1/BaliMiner_TELEGRAM_ALERTS
m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
---------------------
I'm using NVOC 19 1.3.
I have tried to install curl, but the latest version already there.
What is the problem can someone help on this.
I'm trying to use telegram alerts, but didn't receive any messages. I can see in Guake the following error:
bash /home/m1/BaliMiner_TELEGRAM_ALERTS
m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
---------------------
I'm using NVOC 19 1.3.
I have tried to install curl, but the latest version already there.
What is the problem can someone help on this.
Its not a big problem, an error when system started and telegram checks miner up time but there is no miner up yet.
you can ignore it or in telegram find out where MINER_UP_TIME is and replace that line with this:
Code:
MINER_PID=$(ps ax | grep SCREEN | grep miner | awk '"miner" {print $1}' )
if [ -n "$MINER_PID" ]
then
MINER_UP_TIME=$(ps -p $MINER_PID -o etime | grep -v ELAPSED)
else
MINER_UP_TIME=("Not Running")
fi
if [ -n "$MINER_PID" ]
then
MINER_UP_TIME=$(ps -p $MINER_PID -o etime | grep -v ELAPSED)
else
MINER_UP_TIME=("Not Running")
fi
Hi Papampi,
Thx for info.
I have changed and it works good, but my GPU count is wrong in the message.
What do you mean by wrong?
It gets it value from nvidia-smi output, so if its not what it should be then all gpu are not utilized
@papampi, i think what he is trying to say is, he had x GPU's but on the telegram message it might be printing you have y GPU's.
@Havesovgosh Correct me if i am wrong mate.
I remember seeing this error before with one of the telegram MOD (probably mine too!!)
@damNmad Yes you are correct.
@papampi I have 16 GPU. In telegram message
GPU count: 2
but
GPU Utilization : shows all 16 GPUs utilization.
Hi,
I'm trying to use telegram alerts, but didn't receive any messages. I can see in Guake the following error:
bash /home/m1/BaliMiner_TELEGRAM_ALERTS
m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
---------------------
I'm using NVOC 19 1.3.
I have tried to install curl, but the latest version already there.
What is the problem can someone help on this.
I'm trying to use telegram alerts, but didn't receive any messages. I can see in Guake the following error:
bash /home/m1/BaliMiner_TELEGRAM_ALERTS
m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
---------------------
I'm using NVOC 19 1.3.
I have tried to install curl, but the latest version already there.
What is the problem can someone help on this.
Its not a big problem, an error when system started and telegram checks miner up time but there is no miner up yet.
you can ignore it or in telegram find out where MINER_UP_TIME is and replace that line with this:
Code:
MINER_PID=$(ps ax | grep SCREEN | grep miner | awk '"miner" {print $1}' )
if [ -n "$MINER_PID" ]
then
MINER_UP_TIME=$(ps -p $MINER_PID -o etime | grep -v ELAPSED)
else
MINER_UP_TIME=("Not Running")
fi
if [ -n "$MINER_PID" ]
then
MINER_UP_TIME=$(ps -p $MINER_PID -o etime | grep -v ELAPSED)
else
MINER_UP_TIME=("Not Running")
fi
Hi Papampi,
Thx for info.
I have changed and it works good, but my GPU count is wrong in the message.
Hi,
I'm trying to use telegram alerts, but didn't receive any messages. I can see in Guake the following error:
bash /home/m1/BaliMiner_TELEGRAM_ALERTS
m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
---------------------
I'm using NVOC 19 1.3.
I have tried to install curl, but the latest version already there.
What is the problem can someone help on this.
I'm trying to use telegram alerts, but didn't receive any messages. I can see in Guake the following error:
bash /home/m1/BaliMiner_TELEGRAM_ALERTS
m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
error: process ID list syntax error
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
curl: option -d: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
New Telegram in 180 seconds
---------------------
I'm using NVOC 19 1.3.
I have tried to install curl, but the latest version already there.
What is the problem can someone help on this.
Hi,
v0019-1.3 is now "STABLE" or still "BETA" version??
v0019-1.3 is now "STABLE" or still "BETA" version??
That version was and always will be a BETA. The latest stable version is 19 and the next planned is 20. The latest BETA is 19-1.4 and was released yesterday. I have been mining with it on all of my rigs for about 24 hours with no issues. At present, there is no upgrade path to it - you have to start with the full release (link on first page).
Hope this helps.
Thanks.
Hey Everyone,
If you have more than 16 GPUs, the key is to have no more than 16 cards listed in the ServerLayout part of your xorg.conf. Those are the ones that will OC. You will have all 19 listed in the Device and Screen sections and the three that remain will run but won't OC. If you add a 17th under ServerLayout, the miner will not be able to OC any because X will crash when it starts when it hits the 17th card.
If you look at nvidia-smi output, you *should* see, at the bottom an instance of X AND a miner process for each GPU. The ones that only have a miner process attached cannot be OC'd. For me this is GPUs 17, 18, 19.
I've had to edit my rclocal.sh to copy a custom xorg.conf from ~ into /etc/X11 to keep it correct. The problem (for me) is that the script that auto creates the xorg.conf won't stop at 16 in the ServerLayout section and thus makes it so that X won't start and thus none of them OC.
Also, for my Gigabyte P106 cards (I'm running 19) for those first 16 (which will OC), I've not been able to get beyond 100 core and 250 mem, producing 18-18.1 MH/s for ETH only.
Let me know if this helps!
-z
```
# xorg.conf for 19 P106 on Asus ME that gets me 16 OC and 3 non-OC
Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidiascreen-00"
Screen 1 "nvidiascreen-01"
Screen 2 "nvidiascreen-02"
Screen 3 "nvidiascreen-03"
Screen 4 "nvidiascreen-04"
Screen 5 "nvidiascreen-05"
Screen 6 "nvidiascreen-06"
Screen 7 "nvidiascreen-07"
Screen 8 "nvidiascreen-08"
Screen 9 "nvidiascreen-09"
Screen 10 "nvidiascreen-10"
Screen 11 "nvidiascreen-11"
Screen 12 "nvidiascreen-12"
Screen 13 "nvidiascreen-13"
Screen 14 "nvidiascreen-14"
Screen 15 "nvidiascreen-15"
Inactive "intel"
EndSection
Section "Device"
Identifier "intel"
Driver "modesetting"
BusID "PCI:0@0:2:0"
Option "AccelMethod" "None"
EndSection
Section "Screen"
Identifier "intel"
Device "intel"
EndSection
Section "Device"
Identifier "nvidia-00"
Driver "nvidia"
BusID "PCI:1@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-00"
Device "nvidia-00"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-01"
Driver "nvidia"
BusID "PCI:2@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-01"
Device "nvidia-01"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-02"
Driver "nvidia"
BusID "PCI:3@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-02"
Device "nvidia-02"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-03"
Driver "nvidia"
BusID "PCI:6@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-03"
Device "nvidia-03"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-04"
Driver "nvidia"
BusID "PCI:7@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-04"
Device "nvidia-04"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-05"
Driver "nvidia"
BusID "PCI:8@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-05"
Device "nvidia-05"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-06"
Driver "nvidia"
BusID "PCI:9@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-06"
Device "nvidia-06"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-07"
Driver "nvidia"
BusID "PCI:10@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-07"
Device "nvidia-07"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-08"
Driver "nvidia"
BusID "PCI:11@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-08"
Device "nvidia-08"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-09"
Driver "nvidia"
BusID "PCI:12@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-09"
Device "nvidia-09"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-10"
Driver "nvidia"
BusID "PCI:13@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-10"
Device "nvidia-10"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-11"
Driver "nvidia"
BusID "PCI:14@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-11"
Device "nvidia-11"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-12"
Driver "nvidia"
BusID "PCI:15@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-12"
Device "nvidia-12"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-13"
Driver "nvidia"
BusID "PCI:16@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-13"
Device "nvidia-13"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-14"
Driver "nvidia"
BusID "PCI:17@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-14"
Device "nvidia-14"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-15"
Driver "nvidia"
BusID "PCI:18@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-15"
Device "nvidia-15"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-16"
Driver "nvidia"
BusID "PCI:19@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-16"
Device "nvidia-16"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-17"
Driver "nvidia"
BusID "PCI:20@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-17"
Device "nvidia-17"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-18"
Driver "nvidia"
BusID "PCI:21@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-18"
Device "nvidia-18"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
```
If you have more than 16 GPUs, the key is to have no more than 16 cards listed in the ServerLayout part of your xorg.conf. Those are the ones that will OC. You will have all 19 listed in the Device and Screen sections and the three that remain will run but won't OC. If you add a 17th under ServerLayout, the miner will not be able to OC any because X will crash when it starts when it hits the 17th card.
If you look at nvidia-smi output, you *should* see, at the bottom an instance of X AND a miner process for each GPU. The ones that only have a miner process attached cannot be OC'd. For me this is GPUs 17, 18, 19.
I've had to edit my rclocal.sh to copy a custom xorg.conf from ~ into /etc/X11 to keep it correct. The problem (for me) is that the script that auto creates the xorg.conf won't stop at 16 in the ServerLayout section and thus makes it so that X won't start and thus none of them OC.
Also, for my Gigabyte P106 cards (I'm running 19) for those first 16 (which will OC), I've not been able to get beyond 100 core and 250 mem, producing 18-18.1 MH/s for ETH only.
Let me know if this helps!
-z
```
# xorg.conf for 19 P106 on Asus ME that gets me 16 OC and 3 non-OC
Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidiascreen-00"
Screen 1 "nvidiascreen-01"
Screen 2 "nvidiascreen-02"
Screen 3 "nvidiascreen-03"
Screen 4 "nvidiascreen-04"
Screen 5 "nvidiascreen-05"
Screen 6 "nvidiascreen-06"
Screen 7 "nvidiascreen-07"
Screen 8 "nvidiascreen-08"
Screen 9 "nvidiascreen-09"
Screen 10 "nvidiascreen-10"
Screen 11 "nvidiascreen-11"
Screen 12 "nvidiascreen-12"
Screen 13 "nvidiascreen-13"
Screen 14 "nvidiascreen-14"
Screen 15 "nvidiascreen-15"
Inactive "intel"
EndSection
Section "Device"
Identifier "intel"
Driver "modesetting"
BusID "PCI:0@0:2:0"
Option "AccelMethod" "None"
EndSection
Section "Screen"
Identifier "intel"
Device "intel"
EndSection
Section "Device"
Identifier "nvidia-00"
Driver "nvidia"
BusID "PCI:1@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-00"
Device "nvidia-00"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-01"
Driver "nvidia"
BusID "PCI:2@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-01"
Device "nvidia-01"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-02"
Driver "nvidia"
BusID "PCI:3@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-02"
Device "nvidia-02"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-03"
Driver "nvidia"
BusID "PCI:6@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-03"
Device "nvidia-03"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-04"
Driver "nvidia"
BusID "PCI:7@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-04"
Device "nvidia-04"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-05"
Driver "nvidia"
BusID "PCI:8@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-05"
Device "nvidia-05"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-06"
Driver "nvidia"
BusID "PCI:9@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-06"
Device "nvidia-06"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-07"
Driver "nvidia"
BusID "PCI:10@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-07"
Device "nvidia-07"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-08"
Driver "nvidia"
BusID "PCI:11@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-08"
Device "nvidia-08"
Option "Coolbits" "28"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-09"
Driver "nvidia"
BusID "PCI:12@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-09"
Device "nvidia-09"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-10"
Driver "nvidia"
BusID "PCI:13@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-10"
Device "nvidia-10"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-11"
Driver "nvidia"
BusID "PCI:14@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-11"
Device "nvidia-11"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-12"
Driver "nvidia"
BusID "PCI:15@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-12"
Device "nvidia-12"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-13"
Driver "nvidia"
BusID "PCI:16@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-13"
Device "nvidia-13"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-14"
Driver "nvidia"
BusID "PCI:17@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-14"
Device "nvidia-14"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-15"
Driver "nvidia"
BusID "PCI:18@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-15"
Device "nvidia-15"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-16"
Driver "nvidia"
BusID "PCI:19@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-16"
Device "nvidia-16"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-17"
Driver "nvidia"
BusID "PCI:20@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-17"
Device "nvidia-17"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
Section "Device"
Identifier "nvidia-18"
Driver "nvidia"
BusID "PCI:21@0:0:0"
Option "ConstrainCursor" "off"
EndSection
Section "Screen"
Identifier "nvidiascreen-18"
Device "nvidia-18"
Option "AllowEmptyInitialConfiguration" "on"
Option "Coolbits" "28"
Option "IgnoreDisplayDevices" "CRT"
EndSection
```
Hello,
what version is NVOC, 0019 or 0019 1.2
Hi! According to the same issue with all my P106-100 rigs, i suppose you need to do this:
1) check that you have set P106_100_FULL_HEADLESS_MODE="YES" in 1bash
2) check that you can control your rig without monitor attached (SSH or Teamviewer enabled)
3) disconnect monitor
4) run the following:
Code:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
sudo reboot
sudo reboot
After the rig reboots, overclocking will work as supposed to. Sometimes i had to do number 4 again after reboot to make it working.
Thanks, trying now. Did you have more than 16 GPUs?
(edit)I tried this and mining would not start. Had to do
Code:
sudo mv /etc/X11/xorg.conf.nvidia.backup /etc/X11/xorg.conf
to return it to being able to mine at all.I've read that you can add the coolbits part to either screen or device; the code you gave me I think put it in whichever was the wrong one.
Any other ideas?
Code:
sudo nvidia-xconfig -a --cool-bits=12 --allow-empty-initial-configuration
sudo reboot
sudo reboot
I have exactly the same situation (nvOs version 0019v1.3).
I have rig made only of p106-100. With monitor attached to mobo output the xorg.conf is overwritten on each reboot. If I modify xorg.conf with the commands given above, switch to remote ssh mode and reboot with monitor disconnected, the file xorg.conf is not being overwritten, but the mining process does not start. I am also unable to start it manually with 'bash 1bash' (which doesn't work for me at all, but that's another story)
Please help to solve the p106-100 overclocking problem once and for all. I am struggling with it for days now and it's driving me crazy, especially that some people write that it works for them!
Could anybody answer to the p106-100 overclocking problem please?
Below is my post where I solve this issue after very long time investigation and search. Maybe it will help.
Hi fullzero, Hi Guys,
I've found the solution. Also, I have changed to "YES" the IAmNotAJeep_and_Maxximus007_WATCHDOG. It's working fine around one hour. I'll monitor and let you know, if something new will come up.
Below is the steps:
1. Changes in 1bash:
LOCALorREMOTE="REMOTE"
SSH="YES"
P106_100_FULL_HEADLESS_MODE="NO"
2. Reboot
NO Monitors starting from now!!!
3.
sudo -i
rm /etc/X11/xorg.conf
nvidia-xconfig -a --allow-empty-initial-configuration --cool-bits=28 --use-display-device="DFP-0" --connected-monitor="DFP-0"
reboot
4. Change in 1bash:
__CORE_OVERCLOCK=100
MEMORY_OVERCLOCK=500 (getting 22 Mh/s)
Need to check in process tab. for all GPU's should be exists "Xorg - /usr/lib/xorg/Xorg"
-------------
m1@miner1:~$ nvidia-smi
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1073 G /usr/lib/xorg/Xorg 30MiB |
| 0 1646 G compiz 11MiB |
| 0 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
| 1 1073 G /usr/lib/xorg/Xorg 7MiB |
| 1 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
| 2 1073 G /usr/lib/xorg/Xorg 7MiB |
| 2 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
| 3 1073 G /usr/lib/xorg/Xorg 7MiB |
| 3 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
-----------------------------------------------------
Hope this will help also to others.
Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
are you using:
Code:
P106_100_FULL_HEADLESS_MODE="YES"
?
My configuration was set to "NO".
I changed on one rig to "YES" and getting this error in the "temp" screen:
----------------
Mon Oct 23 01:24:05 EDT 2017 - Adjusting Fan for gpu:8. Old: 50 New: 45 Temp: 46
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.
Mon Oct 23 01:24:05 EDT 2017 - All good, will check again soon
----------
Also there was an error related to "persistence mode". I have enabled it manually for all GPUs.
Please Help!
Hi fullzero, Guys,
I have digged and try lot of things.
Unfortunately, without good results.
Now, I'm sure that very small thing I have missed and that's killing me.
What is I'm doing wrong?? Please support.
Don't worry about persistence mode, it's not fatal, just ignore that message.
Not many of us have those P106 cards to help troubleshoot. Hopefuly someone that has them and have a working setup can help you.
Your problem might be related to your motherboard. Apperantly there is known problem where motherboard doesn't work well with more than 12 or was it 13 GPU's. Asus is aware of the problem and they intend to fix it with new bios update. Check if they released new bios.
Thx for your soon feedback. I'll check the bios update.
Hope someone can help!!
Hi fullzero, Hi Guys,
I've found the solution. Also, I have changed to "YES" the IAmNotAJeep_and_Maxximus007_WATCHDOG. It's working fine around one hour. I'll monitor and let you know, if something new will come up.
Below is the steps:
1. Changes in 1bash:
LOCALorREMOTE="REMOTE"
SSH="YES"
P106_100_FULL_HEADLESS_MODE="NO"
2. Reboot
NO Monitors starting from now!!!
3.
sudo -i
rm /etc/X11/xorg.conf
nvidia-xconfig -a --allow-empty-initial-configuration --cool-bits=28 --use-display-device="DFP-0" --connected-monitor="DFP-0"
reboot
4. Change in 1bash:
__CORE_OVERCLOCK=100
MEMORY_OVERCLOCK=500 (getting 22 Mh/s)
Need to check in process tab. for all GPU's should be exists "Xorg - /usr/lib/xorg/Xorg"
-------------
m1@miner1:~$ nvidia-smi
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1073 G /usr/lib/xorg/Xorg 30MiB |
| 0 1646 G compiz 11MiB |
| 0 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
| 1 1073 G /usr/lib/xorg/Xorg 7MiB |
| 1 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
| 2 1073 G /usr/lib/xorg/Xorg 7MiB |
| 2 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
| 3 1073 G /usr/lib/xorg/Xorg 7MiB |
| 3 6160 C /home/m1/eth/Genoil-U/ethminer 2253MiB |
-----------------------------------------------------
Hope this will help also to others.
Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
are you using:
Code:
P106_100_FULL_HEADLESS_MODE="YES"
?
My configuration was set to "NO".
I changed on one rig to "YES" and getting this error in the "temp" screen:
----------------
Mon Oct 23 01:24:05 EDT 2017 - Adjusting Fan for gpu:8. Old: 50 New: 45 Temp: 46
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.
Mon Oct 23 01:24:05 EDT 2017 - All good, will check again soon
----------
Also there was an error related to "persistence mode". I have enabled it manually for all GPUs.
Please Help!
Hi fullzero, Guys,
I have digged and try lot of things.
Unfortunately, without good results.
Now, I'm sure that very small thing I have missed and that's killing me.
What is I'm doing wrong?? Please support.
Don't worry about persistence mode, it's not fatal, just ignore that message.
Not many of us have those P106 cards to help troubleshoot. Hopefuly someone that has them and have a working setup can help you.
Your problem might be related to your motherboard. Apperantly there is known problem where motherboard doesn't work well with more than 12 or was it 13 GPU's. Asus is aware of the problem and they intend to fix it with new bios update. Check if they released new bios.
Thx for your soon feedback. I'll check the bios update.
Hope someone can help!!
Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
are you using:
Code:
P106_100_FULL_HEADLESS_MODE="YES"
?
My configuration was set to "NO".
I changed on one rig to "YES" and getting this error in the "temp" screen:
----------------
Mon Oct 23 01:24:05 EDT 2017 - Adjusting Fan for gpu:8. Old: 50 New: 45 Temp: 46
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.
Mon Oct 23 01:24:05 EDT 2017 - All good, will check again soon
----------
Also there was an error related to "persistence mode". I have enabled it manually for all GPUs.
Please Help!
Hi fullzero, Guys,
I have digged and try lot of things.
Unfortunately, without good results.
Now, I'm sure that very small thing I have missed and that's killing me.
What is I'm doing wrong?? Please support.
Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
are you using:
Code:
P106_100_FULL_HEADLESS_MODE="YES"
?
My configuration was set to "NO".
I changed on one rig to "YES" and getting this error in the "temp" screen:
----------------
Mon Oct 23 01:24:05 EDT 2017 - Adjusting Fan for gpu:8. Old: 50 New: 45 Temp: 46
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.
Mon Oct 23 01:24:05 EDT 2017 - All good, will check again soon
----------
Also there was an error related to "persistence mode". I have enabled it manually for all GPUs.
Please Help!
Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.
I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.
In first RIG In temp Screen I have following errors for all GPUs:
ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------
IN Second in temp Screen the following:
ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------
Please help, What I'm doing wrong or what is missing in my config.