Linux - Installed components

Updated 09/29/2021 09:52 AM

Linux - Installed components

The NVIDIA Accelerated Linux Driver Set consists of the following components (the file in parenthesis is the full name of the component after installation; "x.y.z" denotes the current version -- in these cases appropriate symlinks are created during installation):
  • An X driver (/usr/X11R6/lib/modules/drivers/nvidia_drv.o); this driver is needed by the X server to use your NVIDIA hardware. The nvidia_drv.o driver is binary compatible with XFree86 4.0.1 and greater, as well as the Xorg X server.

  • A GLX extension module for X (/usr/X11R6/lib/modules/extensions/; this module is used by the X server to provide server-side glx support.

  • An OpenGL library (/usr/lib/; this library provides the API entry points for all OpenGL and GLX function calls. It is linked to at run-time by OpenGL applications.

  • An OpenGL core library (/usr/lib/; 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.

  • Two XvMC (X-Video Motion Compensation) libraries: a static library and a shared library (/usr/X11R6/lib/libXvMCNVIDIA.a,/usr/X11R6/lib/; please see (app-p) APPENDIX P: XVMC SUPPORT for details.

  • 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.

  • OpenGL and GLX header files (/usr/share/doc/NVIDIA_GLX-1.0/include/GL/gl.h, and /usr/share/doc/NVIDIA_GLX-1.0/include/GL/glx.h); these files can also be installed in /usr/include/GL/ by passing the "--opengl-headers" option to the .run file during installation.

  • The nvidia-tls libraries (/usr/lib/ and /usr/lib/tls/; 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. Please see (sec-02) INSTALLING THE NVIDIA DRIVER for a more thorough description.

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 Driver Set, plus their symlinks):



/usr/X11R6/lib/modules/extensions/ ->


/usr/lib/ ->

/usr/lib/ ->


/usr/lib/ ->

/lib/modules/`uname -r`/video/nvidia.o, or /lib/modules/`uname -r`/kernel/drivers/video/nvidia.o

Installation will also create the /dev files:

crw-rw-rw- 1 root root 195, 0

Feb 15 17:21 nvidia0

crw-rw-rw- 1 root root 195, 1

Feb 15 17:21 nvidia1

crw-rw-rw- 1 root root 195, 2

Feb 15 17:21 nvidia2

crw-rw-rw- 1 root root 195, 3

Feb 15 17:21 nvidia3

crw-rw-rw- 1 root root 195, 255

Feb 15 17:21 nvidiactl

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/*" and "/usr/X11R6/lib/*".

If the libraries checks out, then verify that the application is using the correct libraries. For example, to check that the application /usr/X11R6/bin/gears is using the NVIDIA libraries, you would do:

$ ldd /usr/X11R6/bin/gears => /usr/lib/ (0x40014000) => /usr/lib/ (0x40046000) => /usr/lib/ (0x40062000) => /lib/ (0x4009f000) => /usr/X11R6/lib/ (0x4018d000) => /usr/X11R6/lib/ (0x40196000) => /usr/X11R6/lib/ (0x401ac000) => /usr/X11R6/lib/ (0x401c0000) => /usr/X11R6/lib/ (0x401cd000) => /usr/X11R6/lib/ (0x401d6000) => /usr/lib/ (0x402ab000) => /lib/ (0x4048d000) => /lib/ (0x404a9000)

/lib/ => /lib/ (0x40000000) => /usr/X11R6/lib/ (0x404ac000)

Note the files being used for libGL and libGLcore -- if they are something other than the NVIDIA libraries, then you will need to either remove the libraries that are getting in the way, or adjust your ld search path. If any of this seems foreign to you, then you may want to read the man pages for "ldconfig" and "ldd" for pointers.

Is this answer helpful?

Live Chat

Chat online with one of our support agents



Contact Support for assistance

Ask a Question