Revision 20 as of 2007-11-04 15:13:00

Clear message
  • Immutable Page
  • Info
  • Attachments

General nvidia intro goes here

Supported Cards

CompizFusion requires compatible HW with driver support and sufficient performance.

Tested OK

Cards tested to work, driver required, and performance notes:

  • (card / driver / notes)

Compatible Specs

Cards theoretically compatible by specs, driver required, and performance notes:

  • (card / driver / notes)

Tested FAIL

Cards tested to fail, driver(s) tested, and specific failures:

  • (card / driver(s) / notes)

Available Drivers

  • Legacy (1.0.7xxx)

  • New Legacy (1.0.96xx)

  • Latest (1.0.97xx - 100.x.x)

System Setup

For information about which drivers can run Xorg (NVIDIA) and which can run Xgl, see ["Setup"].

Additional Configuration

Some of the following options may be worth trying to improve performance or fix bugs:

  • This option is not really needed with newer drivers as it is enabled by default at 9746 and newer.

     Option "RenderAccel" "True" 
  • This option helps performance. It is currently incompatible with SLI and MultiGPU modes.

     Option "DamageEvents" "True"
  • Use this option with caution as it may not work on all systems.

     Option "UseEvents" "False" 
  • Do NOT use this option if you have less than 128mb vram and always with Sync2Vblank enabled at nvidia-settings both for OpenGL and XV.

     Option "TripleBuffer" "True" 
  • Use this options with caution as it may not work on all systems, especially with 6 series GeForce cards (it is known to cause freezes with compiz) but give it a try because it helps performance. It can also break Xinerama.

     Option "BackingStore" "True" 

    The option "BackingStore" is a Xorg option not Nvidia. This option is used to enable the server's support for backing store, a mechanism by which pixel data for occluded window regions is remembered by the server thereby alleviating the need to send expose events to X clients when the data needs to be redisplayed. Note that this can significantly increase performance in nVidia TwinView setups.

{i} For further documentation on these settings please refer to the readme file of the particular Nvidia driver you are using. Here is the readme for driver 100.14.19

Setup nvidia-settings to start on login

This information is intended to help you start nvidia-settings options on login.

The fact that we can set AA and FSAA settings using an export command in various locations including manually in a terminal after login or in /etc/init.d/xdm or /etc/profile or /etc/env.d/03opengl or even /home/user/.bashrc, this does not help us with the other options available to us in nvidia-settings, including Cursor Shadows, Vibrance Controls and others. After much searching I have found a solution to this which will enable us to take advantage of all the options in nvidia-settings by executing the settings file itself in our /home/user/.bashrc. To accomplish this of course you will need to have nvidia-settings installed, then using this tool you will need to make the changes you want to the different options. Once this is accomplished you can then edit your local /home/user/.bashrc file and add the following near the top of the file.

if [ $DISPLAY ] && [ $TERM == "dumb" ]; then
# Load nvidia-settings
nvidia-settings -load-config-only > /dev/null 2>&1

Keep in mind this can also be added to /etc/init.d/xdm or /etc/profile to make the settings global. And of course your settings file would have to be in /root. Not the best solution in my opinion for obvious reasons.

There is also a Texture Filtering option in CCSM you can activate to take advantage of this. In CCSM go to General Options --> Display Settings --> Texture Filter = "BEST"

Now you may be wondering where do I find the proper settings for my Nvidia card. The vsync, AA and, FSAA settings can be found in the readme file of your driver.

To understand these settings and figure out how best to set them I recommend reading pages 9-11 here.

Please understand this is only one solution and not the most elegant but I found it to be a simple solution.

(!) When FSAA is enabled (the __GL_FSAA_MODE environment variable is set to a value that enables FSAA and a multisample visual is chosen), the rendering may be corrupted when resizing the window.