Disclaimer

I am not responsible if your devices send you back in time, explodes, implodes, bricks or flies into space from the use of any software I put up.

Search

Wednesday, September 1, 2010

Linux Nvidia Driver OverClocking

A lot of people don't read "README"s hence they missed a lot of things.

It reflects on the laziness of people of this generation refusal to read, write and learn with the only desire to enjoy and relax. Can't really blame them since it is how the world markets success.
I am guilty of that sometimes as well.



Anyway today I read through the Nvidia Propriety Driver's README and found a number of Nvidia XConfig options usually neglected.

I will only list interesting ones below, the full list is here, Read through it for more information.

To add them simply add the entries under /etc/X11/xorg.conf.
Something like this (in red):
.............................................
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "NoLogo" "on"
Option "Coolbits" "1"
Option "OnDemandVBlankInterrupts" "on"
EndSection
....................................


Interesting Sections below.............

Option "NoLogo" "boolean"
Disable drawing of the NVIDIA logo splash screen at X startup. Default: the logo is drawn for screens with depth 24.
This skips the Nvidia Splash Screen during boot up.

Option "ThermalConfigurationCheck" "boolean"
The NVIDIA X driver will fail initialization on a GPU if it detects that the GPU has a bad thermal configuration. This may indicate a problem with how your graphics board was built, or simply a driver bug. It is recommended that you contact your graphics board vendor if you encounter this problem. This option can be set to False to bypass this test. Default: true (the thermal configuration test is performed).
Turn On Thermal Protection on GPU.



Option "Coolbits" "integer"
Enables various unsupported features, such as support for GPU clock manipulation in the NV-CONTROL X extension. This option accepts a bit mask of features to enable.

WARNING: this may cause system damage and void warranties. This utility can run your computer system out of the manufacturer's design specifications, including, but not limited to: higher system voltages, above normal temperatures, excessive frequencies, and changes to BIOS that may corrupt the BIOS. Your computer's operating system may hang and result in data loss or corrupted images. Depending on the manufacturer of your computer system, the computer system, hardware and software warranties may be voided, and you may not receive any further manufacturer support. NVIDIA does not provide customer service support for the Coolbits option. It is for these reasons that absolutely no warranty or guarantee is either express or implied. Before enabling and using, you should determine the suitability of the utility for your intended use, and you shall assume all responsibility in connection therewith. When "1" (Bit 0) is set in the "Coolbits" option value, the nvidia-settings utility will contain a page labeled "Clock Frequencies" through which clock settings can be manipulated. On mobile GPUs, limited clock manipulation support is available when "1" is set in the "Coolbits" option value: clocks can be lowered relative to the default settings, but overclocking is not supported due to the thermal constraints of notebook designs.
When "2" (Bit 1) is set in the "Coolbits" option value, the NVIDIA driver will attempt to initialize SLI when using GPUs with different amounts of video memory.
When "4" (Bit 2) is set in the "Coolbits" option value, the nvidia-settings Thermal Monitor page will allow configuration of GPU fan speed, on graphics boards with programmable fan capability.
The default for this option is 0 (unsupported features are disabled).
In other word enable OverClocking of Nvidia GPU in Linux + SLI Mods.



Option "MultiGPU" "string"

This option controls the configuration of Multi-GPU rendering in supported configurations.
Value Behavior
0, no, off, false, Single Use only a single GPU when rendering
1, yes, on, true, Auto Enable Multi-GPU and allow the driver to automatically select the appropriate rendering mode.
AFR Enable Multi-GPU and use the Alternate Frame Rendering mode.
SFR Enable Multi-GPU and use the Split Frame Rendering mode.
AA Enable Multi-GPU and use antialiasing. Use this in conjunction with full scene antialiasing to improve visual quality.

Option "SLI" "string"

This option controls the configuration of SLI rendering in supported configurations.
Value Behavior
0, no, off, false, Single Use only a single GPU when rendering
1, yes, on, true, Auto Enable SLI and allow the driver to automatically select the appropriate rendering mode.
AFR Enable SLI and use the Alternate Frame Rendering mode.
SFR Enable SLI and use the Split Frame Rendering mode.
AA Enable SLI and use SLI Antialiasing. Use this in conjunction with full scene antialiasing to improve visual quality.
AFRofAA Enable SLI and use SLI Alternate Frame Rendering of Antialiasing mode. Use this in conjunction with full scene antialiasing to improve visual quality. This option is only valid for SLI configurations with 4 GPUs.
Mosaic Enable SLI and use SLI Mosaic Mode. Use this in conjunction with the MetaModes X configuration option to specify the combination of mode(s) used on each display.
SLI and Multirendering advance configuration.


Option "OnDemandVBlankInterrupts" "boolean"

Normally, VBlank interrupts are generated on every vertical refresh of every display device connected to the GPU(s) installed in a given system. This experimental option enables on-demand VBlank control, allowing the driver to enable VBlank interrupt generation only when it is required. This can help conserve power.

Default: off (on-demand VBlank control is disabled).

More power saving in Linux.

The rest are either enabled by default or nothing much interesting.

That is all.

No comments: