Chapter 5. Listing of Installed Components

The NVIDIA Accelerated Linux Graphics Driver consists of the following components (filenames in parentheses are the full names of the components after installation). Some paths may be different on different systems (e.g., X modules may be installed in /usr/X11R6/ rather than /usr/lib/xorg/).

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/lib/xorg/modules/extensions/ ->

    /usr/lib/ ->;
    /usr/lib/ ->

    ( is the name of the libglvnd client-side GLX ICD loader
    library included with the NVIDIA Linux driver. A compatible ICD loader
    provided by your distribution may have a slightly different filename.)


    /usr/lib/ ->

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

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. An example of a library that often creates conflicts is "/usr/lib/mesa/*".

If the libraries appear to be correct, then verify that the application is using the correct libraries. For example, to check that the application /usr/bin/glxgears is using the libglvnd GLX libraries, run:

    % ldd /usr/bin/glxgears (0x00007ffc8a5d4000) => /usr/lib/x86_64-linux-gnu/ (0x00007f6593896000) => /lib/x86_64-linux-gnu/ (0x00007f65934f8000) => /usr/lib/x86_64-linux-gnu/ (0x00007f65931c0000) => /lib/x86_64-linux-gnu/ (0x00007f6592dcf000) => /usr/lib/x86_64-linux-gnu/ (0x00007f6592b9e000) => /usr/lib/x86_64-linux-gnu/ (0x00007f65928e8000) => /lib/x86_64-linux-gnu/ (0x00007f65926c9000)
    /lib64/ (0x00007f6593d28000) => /usr/lib/x86_64-linux-gnu/ (0x00007f65924a1000) => /lib/x86_64-linux-gnu/ (0x00007f659229d000) => /usr/lib/x86_64-linux-gnu/ (0x00007f6592099000) => /usr/lib/x86_64-linux-gnu/ (0x00007f6591e93000) => /lib/x86_64-linux-gnu/ (0x00007f6591c7e000) => /lib/x86_64-linux-gnu/ (0x00007f6591a76000)

In the example above, the list of libraries reported by ldd includes and If the GLX client library is something other than the GLVND, then you will need to either remove the library that is getting in the way or adjust your dynamic loader search path using the LD_LIBRARY_PATH environment variable. You may want to consult the man pages for ldconfig and ldd.