Unfortunatly my monitor refreshes at 60Hz, so that rules that little idea out plus the frame rate in glxgears isn't rock solid, it can drop and rise (mostly drop though) and I don't have any sync to vblank options enabled, ( i've been through it all, on / off, on again, off again )
Originally Posted by fwojciec
One route I haven't been down yet is setting up the driver through modprobe options. Currently trying to read up on which options I may be able to use.
Plus I've just created another issue for myself.
Execert from Nvidia's Readme.
So I removed the nvidia driver last night and went through my system renaming any possible conflicting files that are mentioned in the README. Then re-installed the pacamn nvidia & nvidia-utils package hoping to start from a completly clean base.
The NVIDIA Accelerated Linux Graphics Driver consists of the following
components (filenames in parenthesis are the full names of the components
after installation; "x.y.z" denotes the current version. In these cases
appropriate symlinks are created during installation):
o An X driver (/usr/X11R6/lib/modules/drivers/nvidia_drv.so); this driver
is needed by the X server to use your NVIDIA hardware.
o A GLX extension module for X
(/usr/X11R6/lib/modules/extensions/libglx.so.x.y.z); this module is used
by the X server to provide server-side GLX support.
o An X module for wrapped software rendering
(/usr/X11R6/lib/modules/libnvidia-wfb.so.x.y.z and optionally,
/usr/X11R6/lib/modules/libwfb.so); this module is used by the X driver to
perform software rendering on GeForce 8 series GPUs. If libwfb.so already
exists, nvidia-installer will not overwrite it. Otherwise, it will create
a symbolic link from libwfb.so to libnvidia-wfb.so.x.y.z.
o An OpenGL library (/usr/lib/libGL.so.x.y.z); this library provides the
API entry points for all OpenGL and GLX function calls. It is linked to
at run-time by OpenGL applications.
o An OpenGL core library (/usr/lib/libGLcore.so.x.y.z); this library is
implicitly used by libGL and by libglx. It contains the core accelerated
3D functionality. You should not explicitly load it in your X config file
-- that is taken care of by libglx.
o Two XvMC (X-Video Motion Compensation) libraries: a static library and a
shared library (/usr/X11R6/lib/libXvMCNVIDIA.a,
/usr/X11R6/lib/libXvMCNVIDIA.so.x.y.z); see Appendix G for details.
o A kernel module (/lib/modules/`uname -r`/video/nvidia.o or
/lib/modules/`uname -r`/kernel/drivers/video/nvidia.o); this kernel
module provides low-level access to your NVIDIA hardware for all of the
above components. It is generally loaded into the kernel when the X
server is started, and is used by the X driver and OpenGL. nvidia.o
consists of two pieces: the binary-only core, and a kernel interface that
must be compiled specifically for your kernel version. Note that the
Linux kernel does not have a consistent binary interface like the X
server, so it is important that this kernel interface be matched with the
version of the kernel that you are using. This can either be accomplished
by compiling yourself, or using precompiled binaries provided for the
kernels shipped with some of the more common Linux distributions.
o OpenGL and GLX header files (/usr/include/GL/gl.h,
/usr/include/GL/glext.h, /usr/include/GL/glx.h, and
/usr/include/GL/glext.h); these are also installed in
/usr/share/doc/NVIDIA_GLX-1.0/include/GL/. You can request that these
files not be included in /usr/include/GL/ by passing the
"--no-opengl-headers" option to the .run file during installation.
o The nvidia-tls libraries (/usr/lib/libnvidia-tls.so.x.y.z and
/usr/lib/tls/libnvidia-tls.so.x.y.z); these files provide thread local
storage support for the NVIDIA OpenGL libraries (libGL, libGLcore, and
libglx). Each nvidia-tls library provides support for a particular thread
local storage model (such as ELF TLS), and the one appropriate for your
system will be loaded at run time.
o The application nvidia-installer (/usr/bin/nvidia-installer) is NVIDIA's
tool for installing and updating NVIDIA drivers. See Chapter 4 for a more
Problems will arise if applications use the wrong version of a library. This
can be the case if there are either old libGL libraries or stale symlinks left
lying around. If you think there may be something awry in your installation,
check that the following files are in place (these are all the files of the
NVIDIA Accelerated Linux Graphics Driver, as well as their symlinks):
/usr/X11R6/lib/modules/extensions/libglx.so -> libglx.so.x.y.z
(may also be in /usr/lib/modules or /usr/lib/xorg/modules)
/usr/lib/libGL.so.x -> libGL.so.x.y.z
/usr/lib/libGL.so -> libGL.so.x
/usr/lib/libGLcore.so.x -> libGLcore.so.x.y.z
/lib/modules/`uname -r`/video/nvidia.o, or
If there are other libraries whose "soname" conflicts with that of the NVIDIA
libraries, ldconfig may create the wrong symlinks. It is recommended that you
manually remove or rename conflicting libraries (be sure to rename clashing
libraries to something that ldconfig will not look at -- we have found that
prepending "XXX" to a library name generally does the trick), rerun
'ldconfig', and check that the correct symlinks were made. Some libraries that
often create conflicts are "/usr/X11R6/lib/libGL.so*" and
However, this morning as I ran compiz I now get an error to do with not being able to find libGLU.so. Which is not one the files I renamed so I presume it will be a symbolic link somewhere along the line, Strangly compiz now claims that "This will not work, yet it works just as well as it did before, with the basic set of plugins that I use (basically just desktop wall and emerald, don't go in for too much fancy-ness but I am a bit partial to translucent title bars ) Although on further examination, ccsm won't allow me to select any fancier effects such as expo or animations, blur etc etc.
Anyway, i'm gonna carry on fiddling, to see wot else I can screw up just to get fluid eye-candy