Multi Nvidia GPU overclocking for computations (CUDA)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have seen in forums and manuals that you have to add
Option "Coolbits" "value"
to xorg.conf or similar files.
I have been able to get this working for the first GPU, the one rendering the display. I have not been able to get overclocking options in nvidia-settings for the second GPU, not rendering any display.
I have tried things like
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
BusID "PCI:2:00:0"
Option "Coolbits" "12"
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
BusID "PCI:3:00:0"
Option "Coolbits" "12"
EndSection
in the various files: xorg.conf, 99-nvidia.conf, nvidia-xorg.conf. Everything I have tried has led to black screens, no overclocking capability or overclocking capability on the first GPU only.
Is it possible to unlock overclocking for both GPUs, if so how?
I have not found this question asked anywhere. I am running 346.59 drivers on Fedora 21.
nvidia gpu
add a comment |
I have seen in forums and manuals that you have to add
Option "Coolbits" "value"
to xorg.conf or similar files.
I have been able to get this working for the first GPU, the one rendering the display. I have not been able to get overclocking options in nvidia-settings for the second GPU, not rendering any display.
I have tried things like
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
BusID "PCI:2:00:0"
Option "Coolbits" "12"
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
BusID "PCI:3:00:0"
Option "Coolbits" "12"
EndSection
in the various files: xorg.conf, 99-nvidia.conf, nvidia-xorg.conf. Everything I have tried has led to black screens, no overclocking capability or overclocking capability on the first GPU only.
Is it possible to unlock overclocking for both GPUs, if so how?
I have not found this question asked anywhere. I am running 346.59 drivers on Fedora 21.
nvidia gpu
Did you ever solve this issue?
– nbubis
Sep 8 '15 at 13:40
No I have the slower of the two GPUs on the display so I can OC it to the level of the other GPU. I havn't found a proper solution.
– Agade
Sep 9 '15 at 19:43
I have solved it on my machine, and added an answer. Give it a try?
– nbubis
Sep 10 '15 at 8:24
Had trouble because Fedora doesn't have a xorg.conf by default and the tools to generate it were giving invalid ones. Once I had a xorg.conf your method was quick to work.
– Agade
Sep 10 '15 at 14:55
add a comment |
I have seen in forums and manuals that you have to add
Option "Coolbits" "value"
to xorg.conf or similar files.
I have been able to get this working for the first GPU, the one rendering the display. I have not been able to get overclocking options in nvidia-settings for the second GPU, not rendering any display.
I have tried things like
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
BusID "PCI:2:00:0"
Option "Coolbits" "12"
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
BusID "PCI:3:00:0"
Option "Coolbits" "12"
EndSection
in the various files: xorg.conf, 99-nvidia.conf, nvidia-xorg.conf. Everything I have tried has led to black screens, no overclocking capability or overclocking capability on the first GPU only.
Is it possible to unlock overclocking for both GPUs, if so how?
I have not found this question asked anywhere. I am running 346.59 drivers on Fedora 21.
nvidia gpu
I have seen in forums and manuals that you have to add
Option "Coolbits" "value"
to xorg.conf or similar files.
I have been able to get this working for the first GPU, the one rendering the display. I have not been able to get overclocking options in nvidia-settings for the second GPU, not rendering any display.
I have tried things like
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
BusID "PCI:2:00:0"
Option "Coolbits" "12"
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
BusID "PCI:3:00:0"
Option "Coolbits" "12"
EndSection
in the various files: xorg.conf, 99-nvidia.conf, nvidia-xorg.conf. Everything I have tried has led to black screens, no overclocking capability or overclocking capability on the first GPU only.
Is it possible to unlock overclocking for both GPUs, if so how?
I have not found this question asked anywhere. I am running 346.59 drivers on Fedora 21.
nvidia gpu
nvidia gpu
asked May 5 '15 at 12:52
AgadeAgade
3316
3316
Did you ever solve this issue?
– nbubis
Sep 8 '15 at 13:40
No I have the slower of the two GPUs on the display so I can OC it to the level of the other GPU. I havn't found a proper solution.
– Agade
Sep 9 '15 at 19:43
I have solved it on my machine, and added an answer. Give it a try?
– nbubis
Sep 10 '15 at 8:24
Had trouble because Fedora doesn't have a xorg.conf by default and the tools to generate it were giving invalid ones. Once I had a xorg.conf your method was quick to work.
– Agade
Sep 10 '15 at 14:55
add a comment |
Did you ever solve this issue?
– nbubis
Sep 8 '15 at 13:40
No I have the slower of the two GPUs on the display so I can OC it to the level of the other GPU. I havn't found a proper solution.
– Agade
Sep 9 '15 at 19:43
I have solved it on my machine, and added an answer. Give it a try?
– nbubis
Sep 10 '15 at 8:24
Had trouble because Fedora doesn't have a xorg.conf by default and the tools to generate it were giving invalid ones. Once I had a xorg.conf your method was quick to work.
– Agade
Sep 10 '15 at 14:55
Did you ever solve this issue?
– nbubis
Sep 8 '15 at 13:40
Did you ever solve this issue?
– nbubis
Sep 8 '15 at 13:40
No I have the slower of the two GPUs on the display so I can OC it to the level of the other GPU. I havn't found a proper solution.
– Agade
Sep 9 '15 at 19:43
No I have the slower of the two GPUs on the display so I can OC it to the level of the other GPU. I havn't found a proper solution.
– Agade
Sep 9 '15 at 19:43
I have solved it on my machine, and added an answer. Give it a try?
– nbubis
Sep 10 '15 at 8:24
I have solved it on my machine, and added an answer. Give it a try?
– nbubis
Sep 10 '15 at 8:24
Had trouble because Fedora doesn't have a xorg.conf by default and the tools to generate it were giving invalid ones. Once I had a xorg.conf your method was quick to work.
– Agade
Sep 10 '15 at 14:55
Had trouble because Fedora doesn't have a xorg.conf by default and the tools to generate it were giving invalid ones. Once I had a xorg.conf your method was quick to work.
– Agade
Sep 10 '15 at 14:55
add a comment |
4 Answers
4
active
oldest
votes
Changing the xorg.conf file to add virtual X servers for each of the cards (even those not connected to a monitor) solved the issue.
Basically, you want to have a server layout section with all of your real and virtual screens:
Section "ServerLayout"
Identifier "Layout0"
# Our real monitor
Screen 0 "Screen0" 0 0
# Our virtual monitors
Screen 1 "Screen1"
Screen 2 "Screen2"
# ....
Screen 3 "Screen3"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections, differing only by their identifiers, which in the following are N
, but should be repaced by the card number, 0
,1
, etc. Note that at least the parameters for the real monitor should correspond to what you currently have in your xorg.conf
file, i.e. in the following I have CRT
since it's an old VGA monitor.
Section "Screen"
Identifier "ScreenN"
Device "DeviceN"
Monitor "MonitorN"
DefaultDepth 24
Option "ConnectedMonitor" "CRT"
Option "Coolbits" "5"
Option "TwinView" "0"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Monitor"
Identifier "MonitorN"
VendorName "Unknown"
ModelName "CRT-N"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "DeviceN"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Your Card name here"
BusID "PCI:X:Y:Z"
EndSection
You write Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections but then you showScreen
,Monitor
andDevice
notDisplay
sections. What's the truth?
– Piotr Dobrogost
Jun 29 '17 at 12:28
Many thanks for the tip, I also had the same issue with overclocking settings not showing up. I managed to get my system work by adding just a screen for each device.
– Pejvan
Jul 4 '17 at 11:01
It can be very hard to get this to work by editing this file manually. Running this commandsudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
will automatically make the changes for you to thexorg.conf
file. Then you just need to reboot and you should be good to go.
– Doug
Jul 22 '17 at 11:39
add a comment |
I never was able to get it to work by hand editing xorg.conf. What did work was to execute on the command line which sets it all up for you:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
Then edit xorg.conf. For me that was sudo vi /etc/X11/xorg.conf
and prepend "#" to each line containing allow-empty-initial-configuration to comment it out.
Reboot.
Then to overclock run:
/usr/bin/nvidia-settings
To restore your settings after a reboot create an executable file that you call from startup applications containing the text below which will set the gpu clock offset and set the gpu to prefer maximum performance. My example sets the offset to 50. Don't set the offset too high in the file for your actual display gpu until you know for sure what you want or you may end up with a system where the display won't work:
nvidia-settings -a [gpu:0]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:1]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:2]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:3]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:3]/GPUGraphicsClockOffset[3]=50
If you want to overclock memory too it's
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=800
And of related interest, you can also modify power to the cards. To see the valid values enter a value of 1000
sudo -n nvidia-smi -i 0 --persistence-mode=1
sudo -n nvidia-smi -i 0 --power-limit=145
And just to display power
nvidia-smi
This worked for me, but you do not need to comment outAllow Empty Initial Configuration
. And if you are going to comment out these lines anyway, just run the command without the--allow-empty-initial-configuration
parameter.
– Doug
Jul 22 '17 at 11:36
On my system I did.
– DarthMouse
Jul 22 '17 at 21:17
If I don't comment out those lines I get duplicate icons on my panel. I have no idea why.
– DarthMouse
Feb 17 '18 at 22:22
add a comment |
If you want to apply the same settings to all cards, a shorthand would be:
nvidia-settings -a GpuPowerMizerMode=1
nvidia-settings -a GPUGraphicsClockOffset[3]=50
add a comment |
Sudo Nvidia-settings -a crashed my desktop.
I had to delete /etc/X11/xorg.conf for it to work again.
I have 2 dgpus, with only 1 monitor connected
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f200553%2fmulti-nvidia-gpu-overclocking-for-computations-cuda%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Changing the xorg.conf file to add virtual X servers for each of the cards (even those not connected to a monitor) solved the issue.
Basically, you want to have a server layout section with all of your real and virtual screens:
Section "ServerLayout"
Identifier "Layout0"
# Our real monitor
Screen 0 "Screen0" 0 0
# Our virtual monitors
Screen 1 "Screen1"
Screen 2 "Screen2"
# ....
Screen 3 "Screen3"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections, differing only by their identifiers, which in the following are N
, but should be repaced by the card number, 0
,1
, etc. Note that at least the parameters for the real monitor should correspond to what you currently have in your xorg.conf
file, i.e. in the following I have CRT
since it's an old VGA monitor.
Section "Screen"
Identifier "ScreenN"
Device "DeviceN"
Monitor "MonitorN"
DefaultDepth 24
Option "ConnectedMonitor" "CRT"
Option "Coolbits" "5"
Option "TwinView" "0"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Monitor"
Identifier "MonitorN"
VendorName "Unknown"
ModelName "CRT-N"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "DeviceN"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Your Card name here"
BusID "PCI:X:Y:Z"
EndSection
You write Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections but then you showScreen
,Monitor
andDevice
notDisplay
sections. What's the truth?
– Piotr Dobrogost
Jun 29 '17 at 12:28
Many thanks for the tip, I also had the same issue with overclocking settings not showing up. I managed to get my system work by adding just a screen for each device.
– Pejvan
Jul 4 '17 at 11:01
It can be very hard to get this to work by editing this file manually. Running this commandsudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
will automatically make the changes for you to thexorg.conf
file. Then you just need to reboot and you should be good to go.
– Doug
Jul 22 '17 at 11:39
add a comment |
Changing the xorg.conf file to add virtual X servers for each of the cards (even those not connected to a monitor) solved the issue.
Basically, you want to have a server layout section with all of your real and virtual screens:
Section "ServerLayout"
Identifier "Layout0"
# Our real monitor
Screen 0 "Screen0" 0 0
# Our virtual monitors
Screen 1 "Screen1"
Screen 2 "Screen2"
# ....
Screen 3 "Screen3"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections, differing only by their identifiers, which in the following are N
, but should be repaced by the card number, 0
,1
, etc. Note that at least the parameters for the real monitor should correspond to what you currently have in your xorg.conf
file, i.e. in the following I have CRT
since it's an old VGA monitor.
Section "Screen"
Identifier "ScreenN"
Device "DeviceN"
Monitor "MonitorN"
DefaultDepth 24
Option "ConnectedMonitor" "CRT"
Option "Coolbits" "5"
Option "TwinView" "0"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Monitor"
Identifier "MonitorN"
VendorName "Unknown"
ModelName "CRT-N"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "DeviceN"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Your Card name here"
BusID "PCI:X:Y:Z"
EndSection
You write Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections but then you showScreen
,Monitor
andDevice
notDisplay
sections. What's the truth?
– Piotr Dobrogost
Jun 29 '17 at 12:28
Many thanks for the tip, I also had the same issue with overclocking settings not showing up. I managed to get my system work by adding just a screen for each device.
– Pejvan
Jul 4 '17 at 11:01
It can be very hard to get this to work by editing this file manually. Running this commandsudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
will automatically make the changes for you to thexorg.conf
file. Then you just need to reboot and you should be good to go.
– Doug
Jul 22 '17 at 11:39
add a comment |
Changing the xorg.conf file to add virtual X servers for each of the cards (even those not connected to a monitor) solved the issue.
Basically, you want to have a server layout section with all of your real and virtual screens:
Section "ServerLayout"
Identifier "Layout0"
# Our real monitor
Screen 0 "Screen0" 0 0
# Our virtual monitors
Screen 1 "Screen1"
Screen 2 "Screen2"
# ....
Screen 3 "Screen3"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections, differing only by their identifiers, which in the following are N
, but should be repaced by the card number, 0
,1
, etc. Note that at least the parameters for the real monitor should correspond to what you currently have in your xorg.conf
file, i.e. in the following I have CRT
since it's an old VGA monitor.
Section "Screen"
Identifier "ScreenN"
Device "DeviceN"
Monitor "MonitorN"
DefaultDepth 24
Option "ConnectedMonitor" "CRT"
Option "Coolbits" "5"
Option "TwinView" "0"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Monitor"
Identifier "MonitorN"
VendorName "Unknown"
ModelName "CRT-N"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "DeviceN"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Your Card name here"
BusID "PCI:X:Y:Z"
EndSection
Changing the xorg.conf file to add virtual X servers for each of the cards (even those not connected to a monitor) solved the issue.
Basically, you want to have a server layout section with all of your real and virtual screens:
Section "ServerLayout"
Identifier "Layout0"
# Our real monitor
Screen 0 "Screen0" 0 0
# Our virtual monitors
Screen 1 "Screen1"
Screen 2 "Screen2"
# ....
Screen 3 "Screen3"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections, differing only by their identifiers, which in the following are N
, but should be repaced by the card number, 0
,1
, etc. Note that at least the parameters for the real monitor should correspond to what you currently have in your xorg.conf
file, i.e. in the following I have CRT
since it's an old VGA monitor.
Section "Screen"
Identifier "ScreenN"
Device "DeviceN"
Monitor "MonitorN"
DefaultDepth 24
Option "ConnectedMonitor" "CRT"
Option "Coolbits" "5"
Option "TwinView" "0"
Option "Stereo" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Monitor"
Identifier "MonitorN"
VendorName "Unknown"
ModelName "CRT-N"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "DeviceN"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Your Card name here"
BusID "PCI:X:Y:Z"
EndSection
answered Sep 10 '15 at 8:23
nbubisnbubis
4042518
4042518
You write Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections but then you showScreen
,Monitor
andDevice
notDisplay
sections. What's the truth?
– Piotr Dobrogost
Jun 29 '17 at 12:28
Many thanks for the tip, I also had the same issue with overclocking settings not showing up. I managed to get my system work by adding just a screen for each device.
– Pejvan
Jul 4 '17 at 11:01
It can be very hard to get this to work by editing this file manually. Running this commandsudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
will automatically make the changes for you to thexorg.conf
file. Then you just need to reboot and you should be good to go.
– Doug
Jul 22 '17 at 11:39
add a comment |
You write Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections but then you showScreen
,Monitor
andDevice
notDisplay
sections. What's the truth?
– Piotr Dobrogost
Jun 29 '17 at 12:28
Many thanks for the tip, I also had the same issue with overclocking settings not showing up. I managed to get my system work by adding just a screen for each device.
– Pejvan
Jul 4 '17 at 11:01
It can be very hard to get this to work by editing this file manually. Running this commandsudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
will automatically make the changes for you to thexorg.conf
file. Then you just need to reboot and you should be good to go.
– Doug
Jul 22 '17 at 11:39
You write Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections but then you show
Screen
, Monitor
and Device
not Display
sections. What's the truth?– Piotr Dobrogost
Jun 29 '17 at 12:28
You write Then, for each your cards, you can put in (almost) identical "Monitor", "Screen" and "Display" sections but then you show
Screen
, Monitor
and Device
not Display
sections. What's the truth?– Piotr Dobrogost
Jun 29 '17 at 12:28
Many thanks for the tip, I also had the same issue with overclocking settings not showing up. I managed to get my system work by adding just a screen for each device.
– Pejvan
Jul 4 '17 at 11:01
Many thanks for the tip, I also had the same issue with overclocking settings not showing up. I managed to get my system work by adding just a screen for each device.
– Pejvan
Jul 4 '17 at 11:01
It can be very hard to get this to work by editing this file manually. Running this command
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
will automatically make the changes for you to the xorg.conf
file. Then you just need to reboot and you should be good to go.– Doug
Jul 22 '17 at 11:39
It can be very hard to get this to work by editing this file manually. Running this command
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
will automatically make the changes for you to the xorg.conf
file. Then you just need to reboot and you should be good to go.– Doug
Jul 22 '17 at 11:39
add a comment |
I never was able to get it to work by hand editing xorg.conf. What did work was to execute on the command line which sets it all up for you:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
Then edit xorg.conf. For me that was sudo vi /etc/X11/xorg.conf
and prepend "#" to each line containing allow-empty-initial-configuration to comment it out.
Reboot.
Then to overclock run:
/usr/bin/nvidia-settings
To restore your settings after a reboot create an executable file that you call from startup applications containing the text below which will set the gpu clock offset and set the gpu to prefer maximum performance. My example sets the offset to 50. Don't set the offset too high in the file for your actual display gpu until you know for sure what you want or you may end up with a system where the display won't work:
nvidia-settings -a [gpu:0]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:1]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:2]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:3]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:3]/GPUGraphicsClockOffset[3]=50
If you want to overclock memory too it's
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=800
And of related interest, you can also modify power to the cards. To see the valid values enter a value of 1000
sudo -n nvidia-smi -i 0 --persistence-mode=1
sudo -n nvidia-smi -i 0 --power-limit=145
And just to display power
nvidia-smi
This worked for me, but you do not need to comment outAllow Empty Initial Configuration
. And if you are going to comment out these lines anyway, just run the command without the--allow-empty-initial-configuration
parameter.
– Doug
Jul 22 '17 at 11:36
On my system I did.
– DarthMouse
Jul 22 '17 at 21:17
If I don't comment out those lines I get duplicate icons on my panel. I have no idea why.
– DarthMouse
Feb 17 '18 at 22:22
add a comment |
I never was able to get it to work by hand editing xorg.conf. What did work was to execute on the command line which sets it all up for you:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
Then edit xorg.conf. For me that was sudo vi /etc/X11/xorg.conf
and prepend "#" to each line containing allow-empty-initial-configuration to comment it out.
Reboot.
Then to overclock run:
/usr/bin/nvidia-settings
To restore your settings after a reboot create an executable file that you call from startup applications containing the text below which will set the gpu clock offset and set the gpu to prefer maximum performance. My example sets the offset to 50. Don't set the offset too high in the file for your actual display gpu until you know for sure what you want or you may end up with a system where the display won't work:
nvidia-settings -a [gpu:0]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:1]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:2]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:3]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:3]/GPUGraphicsClockOffset[3]=50
If you want to overclock memory too it's
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=800
And of related interest, you can also modify power to the cards. To see the valid values enter a value of 1000
sudo -n nvidia-smi -i 0 --persistence-mode=1
sudo -n nvidia-smi -i 0 --power-limit=145
And just to display power
nvidia-smi
This worked for me, but you do not need to comment outAllow Empty Initial Configuration
. And if you are going to comment out these lines anyway, just run the command without the--allow-empty-initial-configuration
parameter.
– Doug
Jul 22 '17 at 11:36
On my system I did.
– DarthMouse
Jul 22 '17 at 21:17
If I don't comment out those lines I get duplicate icons on my panel. I have no idea why.
– DarthMouse
Feb 17 '18 at 22:22
add a comment |
I never was able to get it to work by hand editing xorg.conf. What did work was to execute on the command line which sets it all up for you:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
Then edit xorg.conf. For me that was sudo vi /etc/X11/xorg.conf
and prepend "#" to each line containing allow-empty-initial-configuration to comment it out.
Reboot.
Then to overclock run:
/usr/bin/nvidia-settings
To restore your settings after a reboot create an executable file that you call from startup applications containing the text below which will set the gpu clock offset and set the gpu to prefer maximum performance. My example sets the offset to 50. Don't set the offset too high in the file for your actual display gpu until you know for sure what you want or you may end up with a system where the display won't work:
nvidia-settings -a [gpu:0]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:1]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:2]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:3]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:3]/GPUGraphicsClockOffset[3]=50
If you want to overclock memory too it's
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=800
And of related interest, you can also modify power to the cards. To see the valid values enter a value of 1000
sudo -n nvidia-smi -i 0 --persistence-mode=1
sudo -n nvidia-smi -i 0 --power-limit=145
And just to display power
nvidia-smi
I never was able to get it to work by hand editing xorg.conf. What did work was to execute on the command line which sets it all up for you:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
Then edit xorg.conf. For me that was sudo vi /etc/X11/xorg.conf
and prepend "#" to each line containing allow-empty-initial-configuration to comment it out.
Reboot.
Then to overclock run:
/usr/bin/nvidia-settings
To restore your settings after a reboot create an executable file that you call from startup applications containing the text below which will set the gpu clock offset and set the gpu to prefer maximum performance. My example sets the offset to 50. Don't set the offset too high in the file for your actual display gpu until you know for sure what you want or you may end up with a system where the display won't work:
nvidia-settings -a [gpu:0]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:1]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:2]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[3]=50
nvidia-settings -a [gpu:3]/GpuPowerMizerMode=1
nvidia-settings -a [gpu:3]/GPUGraphicsClockOffset[3]=50
If you want to overclock memory too it's
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=800
And of related interest, you can also modify power to the cards. To see the valid values enter a value of 1000
sudo -n nvidia-smi -i 0 --persistence-mode=1
sudo -n nvidia-smi -i 0 --power-limit=145
And just to display power
nvidia-smi
edited Feb 17 '18 at 22:49
answered Feb 19 '17 at 15:31
DarthMouseDarthMouse
7113
7113
This worked for me, but you do not need to comment outAllow Empty Initial Configuration
. And if you are going to comment out these lines anyway, just run the command without the--allow-empty-initial-configuration
parameter.
– Doug
Jul 22 '17 at 11:36
On my system I did.
– DarthMouse
Jul 22 '17 at 21:17
If I don't comment out those lines I get duplicate icons on my panel. I have no idea why.
– DarthMouse
Feb 17 '18 at 22:22
add a comment |
This worked for me, but you do not need to comment outAllow Empty Initial Configuration
. And if you are going to comment out these lines anyway, just run the command without the--allow-empty-initial-configuration
parameter.
– Doug
Jul 22 '17 at 11:36
On my system I did.
– DarthMouse
Jul 22 '17 at 21:17
If I don't comment out those lines I get duplicate icons on my panel. I have no idea why.
– DarthMouse
Feb 17 '18 at 22:22
This worked for me, but you do not need to comment out
Allow Empty Initial Configuration
. And if you are going to comment out these lines anyway, just run the command without the --allow-empty-initial-configuration
parameter.– Doug
Jul 22 '17 at 11:36
This worked for me, but you do not need to comment out
Allow Empty Initial Configuration
. And if you are going to comment out these lines anyway, just run the command without the --allow-empty-initial-configuration
parameter.– Doug
Jul 22 '17 at 11:36
On my system I did.
– DarthMouse
Jul 22 '17 at 21:17
On my system I did.
– DarthMouse
Jul 22 '17 at 21:17
If I don't comment out those lines I get duplicate icons on my panel. I have no idea why.
– DarthMouse
Feb 17 '18 at 22:22
If I don't comment out those lines I get duplicate icons on my panel. I have no idea why.
– DarthMouse
Feb 17 '18 at 22:22
add a comment |
If you want to apply the same settings to all cards, a shorthand would be:
nvidia-settings -a GpuPowerMizerMode=1
nvidia-settings -a GPUGraphicsClockOffset[3]=50
add a comment |
If you want to apply the same settings to all cards, a shorthand would be:
nvidia-settings -a GpuPowerMizerMode=1
nvidia-settings -a GPUGraphicsClockOffset[3]=50
add a comment |
If you want to apply the same settings to all cards, a shorthand would be:
nvidia-settings -a GpuPowerMizerMode=1
nvidia-settings -a GPUGraphicsClockOffset[3]=50
If you want to apply the same settings to all cards, a shorthand would be:
nvidia-settings -a GpuPowerMizerMode=1
nvidia-settings -a GPUGraphicsClockOffset[3]=50
answered Jul 4 '17 at 10:44
PejvanPejvan
1033
1033
add a comment |
add a comment |
Sudo Nvidia-settings -a crashed my desktop.
I had to delete /etc/X11/xorg.conf for it to work again.
I have 2 dgpus, with only 1 monitor connected
add a comment |
Sudo Nvidia-settings -a crashed my desktop.
I had to delete /etc/X11/xorg.conf for it to work again.
I have 2 dgpus, with only 1 monitor connected
add a comment |
Sudo Nvidia-settings -a crashed my desktop.
I had to delete /etc/X11/xorg.conf for it to work again.
I have 2 dgpus, with only 1 monitor connected
Sudo Nvidia-settings -a crashed my desktop.
I had to delete /etc/X11/xorg.conf for it to work again.
I have 2 dgpus, with only 1 monitor connected
answered 11 mins ago
H BH B
32
32
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f200553%2fmulti-nvidia-gpu-overclocking-for-computations-cuda%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you ever solve this issue?
– nbubis
Sep 8 '15 at 13:40
No I have the slower of the two GPUs on the display so I can OC it to the level of the other GPU. I havn't found a proper solution.
– Agade
Sep 9 '15 at 19:43
I have solved it on my machine, and added an answer. Give it a try?
– nbubis
Sep 10 '15 at 8:24
Had trouble because Fedora doesn't have a xorg.conf by default and the tools to generate it were giving invalid ones. Once I had a xorg.conf your method was quick to work.
– Agade
Sep 10 '15 at 14:55