Search content
Sort by

Showing 15 of 15 results by z-axis
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Nvidia Mining OS FORK v PXA-1.9.6.1 ( UPDATED 1.10.2018 )
by
z-axis
on 20/03/2018, 14:04:36 UTC
Hey master81,

I saw your message and will reply to it when I get a second.

-z
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Nvidia Mining OS FORK v PXA-1.9.6.1 ( UPDATED 1.10.2018 )
by
z-axis
on 16/03/2018, 03:05:16 UTC
our xorg self populates on every reboot so no need to modify it and our autooverclocker clocks cards to perfection we will be releasing a new platform soon so stay tuned.

Great...but xorg self populates for all the distros. That's the problem with >=16 GPUs. If you let the screen section populate with 19, X will not start and no OC will happen. This is why I had to make it so it doesn't auto-populate, resulting in 16 OC and 3 SC. So have you tested on >=19?
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Nvidia Mining OS FORK v PXA-1.9.6.1 ( UPDATED 1.10.2018 )
by
z-axis
on 15/03/2018, 04:40:20 UTC
Hey poisonxa,

Thanks for your fork. I'm looking forward to trying it.

Currently on nvOC v0019-v1.3 mining ETH only with Claymore 10.0
I did a lot of work getting nvOC to run 19 OC'd P106-100s headless on a ME mobo but only managed to get 16 OC stable at 18.1 MH/s and 3 stock clocks at 17.5 MH/s.
Yes I know for P106 that's slow but they are Gigabyte with Hynix. ;-(

My apologies if this has been discussed already, but how does your fork handle >16 cards OC? And if that works, I'd love to hear how you did it as I ran into limits with X and thus had to customize xorg.conf device and screen sections to list only 16 screens but have 19 devices.

Thanks and hope to hear from you.
-z

Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
z-axis
on 14/01/2018, 00:59:12 UTC
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
    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?

It's REMOTE.

If there is one question that might help solve this that I can't seem to find a straight answer for is:

- Where is nvidia-settings called from which results in the creation of xorg.conf?
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
z-axis
on 12/01/2018, 22:06:52 UTC
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
    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?
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
z-axis
on 12/01/2018, 21:07:08 UTC

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
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
z-axis
on 11/01/2018, 22:32:55 UTC
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
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
z-axis
on 31/10/2017, 22:23:32 UTC

Have you attached 3rd PSU?
One PSU = 7 GPU
Two PSU's = 13 GPU
Three PSU's = 19 GPU

Partial support means that not all GPU's can be overclocked, first 16 GPU can be overclocked, last 3 GPU will work on stock settings. See the post from two pages back regarding TB250

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

You can do it all with one PSU if it’s strong enough, but you have to power the risers and GPUs directly from the PSU. The three PSU connectors are only to sync on/off the 2nd and 3rd ones, and the three molex mobo attachments are only if you are attempting to power the risers via the mobo.


Hello,
what version is NVOC, 0019 or 0019 1.2 Huh

1.3
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
z-axis
on 30/10/2017, 20:36:38 UTC
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

```
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3
by
z-axis
on 25/10/2017, 16:11:02 UTC

Max GPUs i have in one rig is 13. In case this doesn't help we need to see nvidia-xconfig output and xorg.conf that it makes, so we can try to find what's wrong.

Also you can try to reflash the latest version of nvOC to usb stick, edit 1bash at windows partition (don't forget to enable headless mode) and make the first boot from usb stick without monitor attached. After the first boot in headless mode you need to wait for autoconfiguration and auto reboot. Then use network scanner or see DHCP leases on the server side to find the IP of your rig (in most cases it will be the same as in previous attempts), ssh to it and see if xorg was correctly configured.


Thank you very much for your help!
My rig is now running with all those settings: New USB, Headless, no monitor attached, know IP, have SSH and mining. Here's the weird thing: See below for my current xorg.conf that is running and I'm getting all 19 GPUs mining but only the 1st one is OC'd. What's weird about it is that:

When I run
Code:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
I get a new xorg.conf that does two things:
Bus IDs lose the "@" symbol, and mining does not work.

Any ideas why some BusIDs use the @ while most I've seen don't, and why this seems to be allowing mining to run?
Also weird is that if you notice, there are only BusIDs for 0-3 (4 and 5 are missing), then it continues from 6-11 and that's it.

What are your thoughts on this?

Current xorg.conf:
Code:
Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    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"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:2@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:3@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:6@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:7@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:8@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:9@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:10@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:11@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection



current lspci:
Code:
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (
00:02.0 VGA compatible controller: Intel Corporation Device 1902
00:14.0 USB controller: Intel Corporation Device a2af
00:16.0 Communication controller: Intel Corporation Device a2ba
00:1b.0 PCI bridge: Intel Corporation Device a2eb (rev f0)
00:1b.5 PCI bridge: Intel Corporation Device a2ec (rev f0)
00:1b.6 PCI bridge: Intel Corporation Device a2ed (rev f0)
00:1b.7 PCI bridge: Intel Corporation Device a2ee (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a294 (rev f0)
00:1c.5 PCI bridge: Intel Corporation Device a295 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a296 (rev f0)
00:1c.7 PCI bridge: Intel Corporation Device a297 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0)
00:1d.1 PCI bridge: Intel Corporation Device a299 (rev f0)
00:1d.2 PCI bridge: Intel Corporation Device a29a (rev f0)
00:1d.3 PCI bridge: Intel Corporation Device a29b (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a2c8
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.4 SMBus: Intel Corporation Device a2a3
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connecti
01:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
02:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
03:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
04:00.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:01.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:02.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:03.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:04.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:05.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:06.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:07.0 PCI bridge: ASMedia Technology Inc. Device 1187
06:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
07:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
08:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
09:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0a:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0b:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0c:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0d:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0e:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0f:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
10:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
11:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
12:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
13:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
14:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
15:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)

Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3
by
z-axis
on 25/10/2017, 02:32:00 UTC

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

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?
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3
by
z-axis
on 24/10/2017, 20:12:48 UTC
Hey Linux Gurus:

Any idea how to allow a 19x P106-100 rig to OC in nvOC? I can't get my OC settings to apply though mining does work for all 19.

Suggestions appreciated!
PM me if you'd prefer.

-z
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3
by
z-axis
on 24/10/2017, 15:25:43 UTC

Code:
AUTO_UPDATE_CHECKS="NO"
Thats nvOC updates not OS updates,
You may have had the latest updates installed when you updated to 19-1.3

thanks papampi, good to know. Do you have any idea about my question about where the nvOC OC scripting is?
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3
by
z-axis
on 24/10/2017, 14:31:07 UTC
Please excuse my n00b questions:

- I'd like to read the OC script to understand it; can somebody give me the path to it?
- Is there a log of the OC process so I can see if they get applied (instead of just looking at nvidia-smi)?

Thanks!

Hey all, glad to hear you got your rigs back up. Mine never stopped but that might be that I had
AUTO_UPDATE_CHECKS="NO"

On another note, would somebody point me to where/how the OC script is run? I'm trying to get my 19x P106 headless rig beyond stock clocks (OC settings aren't applying).

Thanks in advance.
-z
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3
by
z-axis
on 23/10/2017, 21:28:20 UTC
Please excuse my n00b questions:

- I'd like to read the OC script to understand it; can somebody give me the path to it?
- Is there a log of the OC process so I can see if they get applied (instead of just looking at nvidia-smi)?

Thanks!