Pages:
Author

Topic: HOW TO SET UP OVERCLOCKING AND FAN CONTROL ON UBUNTU 16.04 FOR NVIDIA CARDS - page 2. (Read 54990 times)

newbie
Activity: 3
Merit: 0
BTW after you are able to control your fans manually you can setup tool to do it in proper (smart) way.
It was designed especially for rigs.
https://github.com/ktsol/karlson
member
Activity: 144
Merit: 10
THIS!!!!!!!!!!!

you absolutly dont know how much i like this guide
it solved everything ...

only 1 thing: i realized that (at least) for 1070ti is needed coolbits sets on 12 ... then i can OC every card Smiley

THANKS THANKS and again THANKS
newbie
Activity: 3
Merit: 0
I'm searching for similar solution. How may I shut the system's xorg auto reset on reboot. Maybe after that editing the xorg will remain permanent and the display attached wont be needed...

In my case gpumanager was rewriting xorg.conf. You can check the logs: /var/log/gpu-manager.log

I solved by disabling gpumanager at startup adding nogpumanager in grub loader.
See https://askubuntu.com/a/732004 for details
newbie
Activity: 23
Merit: 0
Everytime, when I tried to Overclock or change Fan speed Im getting "The control display is undefined"

Only one think which working is to enable PL: "nvidia-smi -pm 1"
And set TDP: "nvidia-smi -i 0 -pl 151"



Fun speed control do not working:
-----------------------
root@ja:~# nvidia-settings -a '[gpu:0]/GPUFanControlState=1'
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.
------------------------


Overclocking do not working:
-----------------------
root@jatrovka:~# nvidia-settings -a '[gpu:0]/GPUGraphicsMemoryOffset[3]=100'
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.
--------------------------




Dont you know what to do?

Im using Ubuntu 17.10 with proprietary Nvidia drivers:

root@jatrovka:~# nvidia-smi
Sat Dec 23 18:03:58 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.90                 Driver Version: 384.90                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 00000000:04:00.0 Off |                  N/A |
| 69%   69C    P2   158W / 220W |    540MiB /  8111MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 108...  Off  | 00000000:0C:00.0  On |                  N/A |
| 60%   70C    P2   243W / 250W |    601MiB / 11172MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 108...  Off  | 00000000:0D:00.0 Off |                  N/A |
| 65%   78C    P2   248W / 250W |    592MiB / 11172MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0       914      G   /usr/lib/xorg/Xorg                            10MiB |
|    0      1016      G   /usr/bin/gnome-shell                           8MiB |
|    0      1344      C   ./zm                                         509MiB |
|    1       914      G   /usr/lib/xorg/Xorg                            15MiB |
|    1      1344      C   ./zm                                         573MiB |
|    2       914      G   /usr/lib/xorg/Xorg                             7MiB |
|    2      1344      C   ./zm                                         573MiB |
+-----------------------------------------------------------------------------+


========================================
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 384.90  (buildmeister@swio-display-x86-rhel47-05)  Tue Sep 19 18:13:03 PDT 2017

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    Screen      1  "Screen1" RightOf "Screen0"
    Screen      2  "Screen2" RightOf "Screen1"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection
Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1070"
    BusID          "PCI:4:0:0"
    Option         "Coolbits" "31"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1080 Ti"
    BusID          "PCI:12:0:0"
    Option         "Coolbits" "31"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1080 Ti"
    BusID          "PCI:13:0:0"
    Option         "Coolbits" "31"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "31"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "31"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "31"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

legendary
Activity: 1092
Merit: 1004
This is the output from nvidia-smi -q -d CLOCK:

Code:
==============NVSMI LOG==============

Timestamp                           : Mon Dec  4 19:05:48 2017
Driver Version                      : 384.98

Attached GPUs                       : 2
GPU 00000000:01:00.0
    Clocks
        Graphics                    : 1657 MHz
        SM                          : 1657 MHz
        Memory                      : 3802 MHz
        Video                       : 1480 MHz
    Applications Clocks
        Graphics                    : N/A
        Memory                      : N/A
    Default Applications Clocks
        Graphics                    : N/A
        Memory                      : N/A
    Max Clocks
        Graphics                    : 1974 MHz
        SM                          : 1974 MHz
        Memory                      : 4004 MHz
        Video                       : 1708 MHz
    Max Customer Boost Clocks
        Graphics                    : N/A
    SM Clock Samples
        Duration                    : 4.36 sec
        Number of Samples           : 100
        Max                         : 1733 MHz
        Min                         : 1620 MHz
        Avg                         : 1682 MHz
    Memory Clock Samples
        Duration                    : 4.36 sec
        Number of Samples           : 100
        Max                         : 3802 MHz
        Min                         : 3802 MHz
        Avg                         : 3802 MHz
    Clock Policy
        Auto Boost                  : N/A
        Auto Boost Default          : N/A

- Does Graphics: 1657 MHz stand for CPU Clock?
- Does Max Clocks / Graphics: 1900 MHz means I can rise it to 1900 without any harm to the GPU?

I've noticed that chaning GPUGraphicsMemoryOffset changes Graphics precisely. Changing GPUMemoryTransferRateOffset affect Memory but a bit weird, e.g.:

Code:
 Attribute 'GPUMemoryTransferRateOffset' (ubuntu:0[gpu:0]) assigned value 400.

Will set Memory to 3999 (4000 is the max value??).

Can someone with more experience provide some explanation?

So. let's say the memory is at running at 7600mhz. You put 400mhz on the GPUMemoryTransferRateOffset to reach 8GHz
newbie
Activity: 18
Merit: 0
This is the output from nvidia-smi -q -d CLOCK:

Code:
==============NVSMI LOG==============

Timestamp                           : Mon Dec  4 19:05:48 2017
Driver Version                      : 384.98

Attached GPUs                       : 2
GPU 00000000:01:00.0
    Clocks
        Graphics                    : 1657 MHz
        SM                          : 1657 MHz
        Memory                      : 3802 MHz
        Video                       : 1480 MHz
    Applications Clocks
        Graphics                    : N/A
        Memory                      : N/A
    Default Applications Clocks
        Graphics                    : N/A
        Memory                      : N/A
    Max Clocks
        Graphics                    : 1974 MHz
        SM                          : 1974 MHz
        Memory                      : 4004 MHz
        Video                       : 1708 MHz
    Max Customer Boost Clocks
        Graphics                    : N/A
    SM Clock Samples
        Duration                    : 4.36 sec
        Number of Samples           : 100
        Max                         : 1733 MHz
        Min                         : 1620 MHz
        Avg                         : 1682 MHz
    Memory Clock Samples
        Duration                    : 4.36 sec
        Number of Samples           : 100
        Max                         : 3802 MHz
        Min                         : 3802 MHz
        Avg                         : 3802 MHz
    Clock Policy
        Auto Boost                  : N/A
        Auto Boost Default          : N/A

- Does Graphics: 1657 MHz stand for CPU Clock?
- Does Max Clocks / Graphics: 1900 MHz means I can rise it to 1900 without any harm to the GPU?

I've noticed that chaning GPUGraphicsMemoryOffset changes Graphics precisely. Changing GPUMemoryTransferRateOffset affect Memory but a bit weird, e.g.:

Code:
 Attribute 'GPUMemoryTransferRateOffset' (ubuntu:0[gpu:0]) assigned value 400.

Will set Memory to 3999 (4000 is the max value??).

Can someone with more experience provide some explanation?
legendary
Activity: 1092
Merit: 1004
Thanks.  Is there anything I need to do to install that driver?  Do I need to remove the old one first?

Depends how you are installing them, usually you need to be in the non-Nvidia Ubuntu default driver called Noveau.
newbie
Activity: 21
Merit: 0
Thanks.  Is there anything I need to do to install that driver?  Do I need to remove the old one first?
newbie
Activity: 1
Merit: 0
hi all,

drivers 378 can be found at :

http://us.download.nvidia.com/XFree86/Linux-x86_64/378.13/NVIDIA-Linux-x86_64-378.13.run

and for my french mate just change us.download.nvidia.com by fr.download.nvidia.com  Wink

usually any driver version could be found at :

http://us.download.nvidia.com/XFree86/Linux-x86_64//NVIDIA-Linux-x86_64-.run

additionnal info with :

http://us.download.nvidia.com/XFree86/Linux-x86_64//README

but config modification in README is often outdated

legendary
Activity: 1092
Merit: 1004
How do you install 378 drivers?  Ubuntu wants to update to the latest ones

It appears they have been withdrawn, which is weird.

You can access Nvidia Driver Archive and install via that method and I have old method for installing them listed below the current drivers.
newbie
Activity: 21
Merit: 0
How do you install 378 drivers?  Ubuntu wants to update to the latest ones
legendary
Activity: 1092
Merit: 1004
When running the Optiminer in Ubuntu the performance level of all GPUs changes from the max one (3) to 2 (Nvidia X Server Settings). So the memory becomes 7604 instead of 8008 (GTX1060). Is this somehow fixable? Couldnt find any info.

No, this was hard set by Nvidia for compute workloads due to memory instability issue for Micron modules at launch. A later bio update fixed the issue, but because not everyone updated their bios the memory defaults down to the lower speed still on Ubuntu.

This is why the guide shows how to enable overclocking and you can set the correct memory speed or set a higher speed.
legendary
Activity: 1092
Merit: 1004
full member
Activity: 169
Merit: 100
i do nvidia-smi -pl 110 and i shave off about 15-20 watts per card and only lose a marginal amount of hashing power and gain efficiency. this is with my gtx 1060. getting about 296 sols/s @ 110w from 120-125 watts.
full member
Activity: 169
Merit: 100
cant this all be done through nvidia-smi command? i dont run my gpus with xserver installed. i just install ubuntu server 16.10 and the nvidia drivers and go but i need to get more power efficiency and i cant seem to get my overclocks right.
legendary
Activity: 1512
Merit: 1000
quarkchain.io
I'm searching for similar solution. How may I shut the system's xorg auto reset on reboot. Maybe after that editing the xorg will remain permanent and the display attached wont be needed...
legendary
Activity: 1901
Merit: 1024
I did not see this guide at first, I had problems making it run without monitor + manage OC on all cards but I had to make and edit xorg.conf both in etc/X11 but first make it here /usr/share/X11/xorg.conf.d/xorg.conf
Also I used edit.bin there, now it works but as miners are far from me, I can not test this way explained here
newbie
Activity: 73
Merit: 0
When running the Optiminer in Ubuntu the performance level of all GPUs changes from the max one (3) to 2 (Nvidia X Server Settings). So the memory becomes 7604 instead of 8008 (GTX1060). Is this somehow fixable? Couldnt find any info.
newbie
Activity: 5
Merit: 0
Hello,

Went through this guide to OC my 1060 cards, but was not able to do it.

After this command "sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration", on Reboot xorg.conf file is being reset to default. Coolbits option was not found in the file  Huh and Overclocking is not enabled on GPU's.
Is there any possible solution for this? Please let me know.. Thanks

Using Ubuntu 16.04, nvidia-384 drivers.
xorg.conf file after coolbits command:
Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 384.90  (buildmeister@swio-display-x86-rhel47-05)  Tue Sep 19 18:13:03 PDT 2017

Section "ServerLayout"
    Identifier     "layout"
    Screen      0  "Screen0"
    Screen      1  "Screen1" RightOf "Screen0"
    Screen      2  "Screen2" RightOf "Screen1"
    Inactive       "intel"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "keyboard"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 6GB"
    BusID          "PCI:2:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 6GB"
    BusID          "PCI:3:0:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 6GB"
    BusID          "PCI:6:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

xorg.conf file after reboot:
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: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
legendary
Activity: 1092
Merit: 1004
Interesting, I did test with six GTX 1060 3GB and there were no issues.

Try using the 378 drivers - those have been validated by Ubuntu and optimised for the OS

There are various bugs in using Nvidia driver release that are not optimised by developers of Ubuntu OS.

Should that fail, you can always get a couple of cheap dummy HDMI monitor plugs for those 2 cards.
Pages:
Jump to: