으아.... 도와주세요~ mplayer 에서 fatal error가... @_@;;

NVIDIA Accelerated Linux Driver Set README & Installation Guide

Last Updated: $Date: 2003/07/16 $
Most Recent Driver: 1.0-4496

The NVIDIA Accelerated Linux Driver Set brings both accelerated 2D
functionality and high performance OpenGL support to Linux x86 with the
use of NVIDIA graphics processing units (GPUs).

These drivers provide optimized hardware acceleration of OpenGL
applications via a direct-rendering X Server and support nearly all
NVIDIA graphics chips (please see APPENDIX A for a complete list of
supported chips). TwinView, TV-Out and flat panel displays are also
supported.

This README describes how to install, configure, and use the NVIDIA
Accelerated Linux Driver Set. This file is posted on NVIDIA's web site
(www.nvidia.com), and is installed in /usr/share/doc/NVIDIA_GLX-1.0/.

__________________________________________________________________________

CONTENTS:

(sec-01) CHOOSING THE NVIDIA PACKAGES APPROPRIATE FOR YOUR SYSTEM
(sec-02) INSTALLING THE NVIDIA DRIVER
(sec-03) EDITING YOUR XF86CONFIG FILE
(sec-04) FREQUENTLY ASKED QUESTIONS
(sec-05) CONTACTING US
(sec-06) FURTHER RESOURCES

(app-a) APPENDIX A: SUPPORTED NVIDIA GRAPHICS CHIPS
(app-b) APPENDIX B: MINIMUM SOFTWARE REQUIREMENTS
(app-c) APPENDIX C: INSTALLED COMPONENTS
(app-d) APPENDIX D: XF86CONFIG OPTIONS
(app-e) APPENDIX E: OPENGL ENVIRONMENT VARIABLE SETTINGS
(app-f) APPENDIX F: CONFIGURING AGP
(app-g) APPENDIX G: ALI SPECIFIC ISSUES
(app-h) APPENDIX H: TNT SPECIFIC ISSUES
(app-i) APPENDIX I: CONFIGURING TWINVIEW
(app-j) APPENDIX J: CONFIGURING TV-OUT
(app-k) APPENDIX K: CONFIGURING A LAPTOP
(app-l) APPENDIX L: PROGRAMMING MODES
(app-m) APPENDIX M: PAGE FLIPPING, WINDOW FLIPPING, AND UBB
(app-n) APPENDIX N: KNOWN ISSUES
(app-o) APPENDIX O: PROC INTERFACE
(app-p) APPENDIX P: XVMC SUPPORT
(app-q) APPENDIX Q: GLX SUPPORT
(app-r) APPENDIX R: CONFIGURING MULTIPLE X SCREENS ON ONE CARD
(app-s) APPENDIX S: POWER MANAGEMENT SUPPORT

Please note that, in order to keep the instructions more concise, most
caveats and frequently encountered problems are not detailed in the
installation instructions, but rather in the FREQUENTLY ASKED QUESTIONS
section. Therefore, it is recommended that you read this entire README
before proceeding to perform any of the steps described.

__________________________________________________________________________

(sec-01) CHOOSING THE NVIDIA PACKAGES APPROPRIATE FOR YOUR SYSTEM
__________________________________________________________________________

NVIDIA has a unified driver architecture model; this means that one driver
set can be used with all supported NVIDIA graphics chips. Please see
Appendix A for a list of the NVIDIA graphics chips supported by the
current drivers.

Driver release 1.0-4349 introduced a new packaging
and installation mechanism, which greatly simplifies the
installation process. There is only a single file to download:
NVIDIA-Linux-x86-1.0-1.0-4496-pkg1.run. This contains
everything previously contained by the old NVIDIA_kernel and NVIDIA_GLX
packages.

Driver release 1.0-4496 introduces a package suffix ("-pkg#") to
the .run file. This is used to distinguish between packages containing
the same driver, but with different precompiled kernel interfaces.
If there is any confusion, just download the .run file with the largest
pkg number.

__________________________________________________________________________

(sec-02) INSTALLING THE NVIDIA DRIVER
__________________________________________________________________________

BEFORE YOU BEGIN DRIVER INSTALLATION

Before beginning the driver installation, you should exit the X server.
In addition you should set your default run level so you will boot to a
vga console and not boot directly into X (please consult the documentation
that came with your Linux distribution if you are unsure how to do this;
this is normally done by modifying your /etc/inittab file). This will
make it easier to recover if there is a problem during the installation.
After installing the driver you must edit your XF86Config file before
the newly installed driver will be used. See the section below entitled
EDITING YOUR XF86CONFIG FILE.

INTRODUCTION TO THE NEW NVIDIA DRIVER INSTALLER

After you have downloaded NVIDIA-Linux-x86-1.0-4496-pkg1.run,
begin installation by exiting X, cd'ing into the directory containing
the downloaded file, and run:

sh NVIDIA-Linux-x86-1.0-4496-pkg1.run

The .run file is a self-extracting archive. When the .run file is
executed, it extracts the contents of the archive, and runs the contained
`nvidia-installer` utility, which will walk you through installation of
the NVIDIA driver.

The .run file accepts many commandline options. Here are a few of the
more common options:

--info
Print embedded info about the .run file and exit.

--check
Check integrity of the archive and exit.

--extract-only
Extract the contents of ./NVIDIA-Linux-x86-1.0-4496.run,
but do not run 'nvidia-installer'.

--help
Print usage information for the common commandline options
and exit.

--advanced-options
Print usage information for the common commandline options as
well as the advanced options, and then exit.

Installation will also install the utility `nvidia-installer`, which may
be later used to uninstall drivers, auto-download updated drivers, etc.

KERNEL INTERFACES

The NVIDIA kernel module has a kernel interface layer which must be
compiled specifically for the configuration and version of the kernel
you are running. NVIDIA distributes the source code to this kernel
interface layer, as well as a precompiled version for many of the kernels
distributed by some popular distributions.

When the installer is run, it will determine if it has a precompiled
kernel interface for the kernel you are running. If it does not have
one, it will check if there is one on the NVIDIA ftp site (assuming you
have an internet connection), and download it.

If a precompiled kernel interface is found that matches your kernel,
then that will be linked[1] against the binary portion of the NVIDIA
kernel module. The result of this operation will be a kernel module
appropriate for your kernel.

If no matching precompiled kernel interface is found, then the installer
will compile the kernel interface for you. However, first it will
check that you have the correct kernel headers intalled on your system.
If the installer must compile the kernel interface, then you must install
the kernel-sources package for your kernel.

[1] NOTE: installation requires that you have a linker installed.
The linker, usually '/usr/bin/ld', is part of the binutils package;
please be sure you have this package installed prior to installing the
NVIDIA driver.

FEATURES OF NVIDIA-INSTALLER

o Uninstall: Driver installation will backup any conflicting files
and record what new files are installed on the system. You may run:

nvidia-installer --uninstall

to uninstall the current driver; this will remove any files that
were installed on the system, and restore any backed up files.
Installing new drivers implicitly uninstalls any previous drivers.

o Auto-Updating: If you run:

nvidia-installer --latest

the utility will connect to NVIDIA's FTP site, and report the latest
driver version and the url to the latest driver file.

If you run:

nvidia-installer --update

the utility will connect to NVIDIA's FTP site, download the most recent
driver file, and install it.

o Multiple user interfaces: The installer will use an ncurses-based
user interface if it can find the correct ncurses library, otherwise,
it will fall back to a simple commandline user interface. To disable
use of the ncurses user interface, use the option '--ui=none'.

o Updated Kernel Interfaces: The installer has the ability to
download updated precompiled kernel interfaces from the NVIDIA
FTP site (for kernels that were released after the NVIDIA driver
release).

NVIDIA-INSTALLER FAQ

Q: How do I extract the contents of the .run file without actually
installing the driver?

A: Run:

sh NVIDIA-Linux-x86-1.0-4496-pkg1.run --extract-only

This will create the directory NVIDIA-Linux-x86-1.0-4496-pkg1
which contains the uncompressed contents of the .run file.

Q: How can I see the source code to the kernel interface layer?

A: The source files to the kernel interface layer are in the usr/src/nv
directory of the extracted .run file. To get to these sources, run:

sh NVIDIA-Linux-x86-1.0-4496-pkg1.run --extract-only
cd NVIDIA-Linux-x86-1.0-4496-pkg1/usr/src/nv/

Q: I just upgraded my kernel, and now the NVIDIA kernel module won't
load. What's wrong?

A: The kernel interface layer of the NVIDIA kernel module must be
compiled specifically for the configuration and version of your kernel.
If you upgrade your kernel, then the simplest solution is to reinstall
the driver.

ADVANCED: You can install the NVIDIA kernel module for a non
running kernel (for example: in the situation where you just built
and installed a new kernel, but haven't rebooted yet) with a command
line such as this:

sh NVIDIA-Linux-x86-1.0-4496-pkg1.run --kernel-name='KERNEL_NAME'

Where 'KERNEL_NAME' is what `uname -r` would report if the target
kernel were running.

Q: Why does NVIDIA not provide rpms anymore?

A: Not every Linux distribution uses rpm, and NVIDIA wanted a single
solution that would work across all Linux distributions. As indicated
in the NVIDIA Software License, Linux distributions are welcome to
repackage and redistribute the NVIDIA Linux driver in whatever package
format they wish.

Q: nvidia-installer doesn't work on my computer. How can I install the
driver contained within the .run file?

A: To install the NVIDIA driver contained within the .run file without
using nvidia-installer, you can use the included Makefile:

sh ./NVIDIA-Linux-x86-1.0-4496-pkg1.run --extract-only
cd NVIDIA-Linux-x86-1.0-4496-pkg1
make install

This method of installation is not recommended, and is only provided
as a last resort, should nvidia-installer not work correctly on
your system.

Q: Can the nvidia-installer use a proxy server?

A: Yes, because the ftp support in nvidia-installer is based on snarf,
it will honor the FTP_PROXY, SNARF_PROXY, and PROXY environment
variables.

Q: What is the significance of the "pkg#" suffix on the .run file?

A: The "pkg#" suffix is used to distinguish between .run files containing
the same driver, but different sets of precompiled kernel interfaces.
If a distribution releases a new kernel after an NVIDIA driver is
released, the current NVIDIA driver can be repackaged to include
a precompiled kernel interface for that newer kernel (in addition
to all the precompiled kernel interfaces that were included in the
previous package of the driver).

.run files with the same version number, but different pkg numbers,
only differ in what precompiled kernel interfaces are included.
Additionally, .run files with higher pkg numbers will contain
everything the .run files with lower .pkg numbers contain.

Q: I have already installed NVIDIA-Linux-x86-1.0-4496-pkg1.run,
but I see that NVIDIA-Linux-x86-1.0-4496-pkg2.run was just
posted on the NVIDIA Linux driver download page. Should I download
and install NVIDIA-Linux-x86-1.0-4496-pkg2.run?

A: This is not necessary. The driver contained within all
1.0-4496 .run files will be identical. There is no need
to reinstall.

Q: Can I add my own precompiled kernel interfaces to a .run file?

A: Yes, the "--add-this-kernel" .run file option will unpack the .run
file, build a precompiled kernel interface for the currently running
kernel, and repackage the .run file, appending "-custom" to the file
name. This may be useful, for example. if you administer multiple
Linux machines, each running the same kernel.

Q: Where can I find the source code for the nvidia-installer utility?

A: The nvidia-installer utility is released under the
GPL. The latest source code for it is available at:
ftp://download.nvidia.com/XFree86/nvidia-installer/

NVIDIA-INSTALLER ACKNOWLEDGEMENTS

nvidia-installer was inspired by the loki_update tool:
(http://www.lokigames.com/development/loki_update.php3.)

The ftp and http support in nvidia-installer is based upon snarf 7.0:
(http://www.xach.com/snarf/).

The self-extracting archive (aka ".run file") is generated using
makeself.sh: (http://www.megastep.org/makeself/)

__________________________________________________________________________

(sec-03) EDITING YOUR XF86CONFIG FILE
__________________________________________________________________________

When XFree86 4.0 was released, it used a slightly different XF86Config
file syntax than the 3.x series did, and so to allow both 3.x and 4.x
versions of XFree86 to co-exist on the same system, it was decided that
XFree86 4.x was to use the configuration file "/etc/X11/XF86Config-4"
if it existed, and only if that file did not exist would the file
"/etc/X11/XF86Config" be used (actually, that is an over-simplification
of the search criteria; please see the XF86Config man page for a complete
description of the search path). Please make sure you know what
configuration file XFree86 is using. If you are in doubt, look for a
line beginning with "(==) Using config file:" in your XFree86 log file
("/var/log/XFree86.0.log"). This README will use "XF86Config" to refer
to your configuration file, whatever it is named.

If you do not have a working XF86Config file, there are several ways
to start: there is a sample config file that comes with XFree86,
and there is a sample config file included with the NVIDIA driver
package (it gets installed in /usr/share/doc/NVIDIA_GLX-1.0/).
You could also use a program like 'xf86config'; some distributions
provide their own tool for generating an XF86Config file. For more
on XF86Config file syntax, please refer to the man page.

If you already have an XF86Config file working with a different driver
(such as the 'nv' or 'vesa' driver), then all you need to do is find
the relevant Device section and replace the line:

Driver "nv"
(or Driver "vesa")

with

Driver "nvidia"

In the Module section, make sure you have:

Load "glx"

You should also remove the following lines:

Load "dri"
Load "GLcore"

if they exist. There are also numerous options that can be added to
the XF86Config file to fine-tune the NVIDIA XFree86 driver. Please see
Appendix D for a complete list of these options.

Once you have configured your XF86Config file, you are ready to restart
X and begin using the accelerated OpenGL libraries. After you restart X,
you should be able to run any OpenGL application and it will automatically
use the new NVIDIA libraries. If you encounter any problems, please
see the FREQUENTLY ASKED QUESTIONS section below.

__________________________________________________________________________

(sec-04) FREQUENTLY ASKED QUESTIONS
__________________________________________________________________________

Q: Where should I start when diagnosing display problems?

A: One of the most useful tools for diagnosing problems is the XFree86
log file in /var/log (the file is named: "/var/log/XFree86.<#>.log",
where "<#>" is the server number -- usually 0). Lines that begin with
"(II)" are information, "(WW)" are warnings, and "(EE)" are errors.
You should make sure that the correct config file (ie the config file
you are editing) is being used; look for the line that begins with:
"(==) Using config file:". Also check that the NVIDIA driver is being
used, rather than the 'nv' or 'vesa' driver; you can look for: "(II)
LoadModule: "nvidia"", and lines from the driver should begin with:
"(II) NVIDIA(0)".

Q: How can I increase the amount of data printed in the XFree86 log file?

A: By default, the NVIDIA X driver prints relatively few messages to
stderr and the XFree86 log file. If you need to troubleshoot, then
it may be helpful to enable more verbose output by using the XFree86
command line options "-verbose" and "-logverbose" which can be used
to set the verbosity level for the stderr and log file messages,
respectively. The NVIDIA X driver will output more messages when the
verbosity level is at or above 5 (XFree86 defaults to verbosity level
1 for stderr and level 3 for the log file). So, to enable verbose
messaging from the NVIDIA X driver to both the log file and stderr,
you could start X by doing the following: 'startx -- -verbose 5
-logverbose 5'.

Q: My X server fails to start, and my XFree86 log file contains the error:

"(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!"

A: Nothing will work if the NVIDIA kernel module doesn't function
properly. If you see anything in the X log file like "(EE)
NVIDIA(0): Failed to initialize the NVIDIA kernel module!" then
there is most likely a problem with the NVIDIA kernel module.
First, you should verify that if you installed from rpm that
the rpm was built specifically for the kernel you are using.
You should also check that the module is loaded ('/sbin/lsmod');
if it is not loaded try loading it explicitly with 'insmod' or
'modprobe' (be sure to exit the X server before installing a new
kernel module). If you receive errors about unresolved symbols,
then the kernel module has most likely been built using header files
for a different kernel revision than what you are running. You can
explicitly control what kernel header files are used when building
the NVIDIA kernel module with the --kernel-include-dir option (see
`sh NVIDIA-Linux-x86-1.0-4496-pkg1.run --advanced-options`
for details).

Please note that the convention for the location of kernel header
files changed approximately at the time of the 2.4.0 kernel release,
as did the location of kernel modules. If the kernel module fails to
load properly, modprobe/insmod may be trying to load an older kernel
module (assuming you've upgraded). cd'ing into the directory with
the new kernel module and doing 'insmod ./nvidia.o' may help.

Another cause may be that the /dev/nvidia* device files may be missing.

Finally, the NVIDIA kernel module may print error messages indicating
a problem -- to view these messages please check /var/log/messages, or
wherever syslog is directed to place kernel messages. These messages
are prepended with "NVRM".

Q: X starts for me, but OpenGL applications terminate immediately.

A: If X starts, but OpenGL causes problems, you most likely have a
problem with other libraries in the way, or there are stale symlinks.
See Appendix C for details. Sometimes, all it takes is to rerun
'ldconfig'.

You should also check that the correct extensions are present;
'xdpyinfo' should show the "GLX", "NV-GLX" and "NVIDIA-GLX" extensions
present. If these three extensions are not present, then there is
most likely a problem with the glx module getting loaded or it is
unable to implicitly load GLcore. Check your XF86Config file and make
sure that you are loading glx (see "Editing Your XF86Config File"
above). If your XF86Config file is correct, then check the XFree86
log file for warnings/errors pertaining to GLX. Also check that all
of the necessary symlinks are in place (refer to Appendix C).

Q: Installing the NVIDIA kernel module gives an error message like:
#error Modules should never use kernel-headers system headers
#error but headers from an appropriate kernel-source

A: You need to install the source for the Linux kernel. In most
situations you can fix this problem by installing the kernel-source
package for your distribution

Q: OpenGL applications exit with the following error message:

Error: Could not open /dev/nvidiactl because the permissions
are too restrictive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
to correct.

A: It is likely that a security module for the PAM system may be
changing the permissions on the NVIDIA device files. In most cases
this security system works, but it can get confused. To correct this
problem it is recommended that you disable this security feature.
Different Linux distributions have different files to control this;
please consult with your distributor for the correct method of
disabling this security feature. As an example, if your system has
the file
/etc/security/console.perms
then you should edit the file and remove the line that starts with
"<dri>" (we have also received reports that additional references to
<dri> in console.perms must be removed, but this has not been verified
by NVIDIA). If instead your system has the file
/etc/logindevperms
then you should edit the file and remove the line that lists
/dev/nvidiactl. The above steps will prevent the PAM security system
from modifying the permissions on the NVIDIA device files. Next,
you will need to reset the permissions on the device files back
to their original permissions and owner. You can do that with the
following commands:
chmod 0666 /dev/nvidia* chown root /dev/nvidia*

Q: OpenGL applications crash and print out the following warning:

WARNING: Your system is running with a buggy dynamic loader.
This may cause crashes in certain applications. If you
experience crashes you can try setting the environment
variable __GL_SINGLE_THREADED to 1. For more information
please consult the FREQUENTLY ASKED QUESTIONS section in
the file /usr/share/doc/NVIDIA_GLX-1.0/README.

A: The dynamic loader on your system has a bug which will cause
applications linked with pthreads, and that dlopen() libGL multiple
times, to crash. This bug is present in older versions of the dynamic
loader. Distributions that shipped with this loader include but
are not limited to Red Hat Linux 6.2 and Mandrake Linux 7.1. Version
2.2 and later of the dynamic loader are known to work properly. If
the crashing application is single threaded then setting the environment
variable __GL_SINGLE_THREADED to 1 will prevent the crash.
In the bash shell you would enter:
export __GL_SINGLE_THREADED=1
and in csh and derivatives use:
setenv __GL_SINGLE_THREADED 1
Previous releases of the NVIDIA Accelerated Linux Driver Set attempted
to work around this problem, however the workaround caused problems with
other applications and was removed after version 1.0-1541.

Q: When I run Quake3, it crashes when changing video modes; what's wrong?

A: You are probably experiencing the problem described above. Please
check the text output for the "WARNING" message describe in the
previous hint. Setting __GL_SINGLE_THREADED to 1 as described
above, before running Quake3 will fix the problem.

Q: My system runs, but seems unstable. What's wrong?

A: Your stability problems may be AGP-related. See Appendix F for
details.

Q: The kernel module doesn't get loaded dynamically when X starts;
I always have to do 'modprobe nvidia' first. What's wrong?

A: Make sure the line "alias char-major-195 nvidia" appears in
your module configuration file, generally one of "/etc/conf.modules",
"/etc/modules.conf" or "/etc/modutils/alias"; consult the documentation
that came with your distribution for details.

Q: I can't build the NVIDIA kernel module, or I can build the NVIDIA
kernel module, but modprobe/insmod fails to load the module into
my kernel. What's wrong?

A: These problems are generally caused by the build using the wrong kernel
header files (ie header files for a different kernel version than
the one you are running). The convention used to be that kernel
header files should be stored in "/usr/include/linux/", but that
is deprecated in favor of "/lib/modules/`uname -r`/build/include".
The nvidia-installer should be able to determine the location on your
system; however, if you encounter a problem you can force the build
to use certain header files by using the --kernel-include-dir option.
Obviously, for this to work, you need the appropriate kernel header
files installed on your system. Consult the documentation that came
with your distribution; some distributions don't install the kernel
header files by default, or they install headers that don't coincide
properly with the kernel you are running.

Q: Why do OpenGL applications run so slow?

A: The application is probably using a different library still on your
system, rather than the NVIDIA supplied OpenGL library. Please see
APPENDIX C for details.

Q: There are problems running Quake2.

A: Quake2 requires some minor setup to get it going. First, in the Quake2
directory, the install creates a symlink called libGL.so that points
at libMesaGL.so. This symlink should be removed or renamed. Then,
to run Quake2 in OpenGL mode, you would type: 'quake2 +set vid_ref glx
+set gl_driver libGL.so'. Quake2 does not seem to support any kind of
full-screen mode, but you can run your X server at whatever resolution
Quake2 runs at to emulate full-screen mode.

Q: There are problems running Heretic II.

A: Heretic II also installs, by default, a symlink called libGL.so in
the application directory. You can remove or rename this symlink, since
the system will then find the default libGL.so (which our
drivers install in /usr/lib). From within Heretic II you
can then set your render mode to OpenGL in the video menu.
There is also a patch available to Heretic II from lokigames at:
http://www.lokigames.com/products/heretic2/updates.php3

Q: Where can I get gl.h or glx.h so I can compile OpenGL programs?

A: Most systems come with these header files preinstalled. However,
NVIDIA provides its own gl.h and glx.h files which get installed
in /usr/share/doc/NVIDIA_GLX-1.0/include/GL/. To use these
files, either manually copy them into /usr/include/GL/,
or instruct the installer to install these files in
/usr/include/GL/ by passing the '--opengl-headers' option to the
NVIDIA-Linux-x86-1.0-4496-pkg1.run file during installation.

Q: Can I receive email notification of new NVIDIA Accelerated Linux
Driver Set releases?

A: Yes. Fill out the form at:
http://www.nvidia.com/view.asp?FO=driver_update

Q: My system hangs when vt-switching if I have rivafb enabled.

A: Using both rivafb and the NVIDIA kernel module at the same time is
currently broken. In general, using two independent software drivers
to drive the same piece of hardware is a bad idea.

Q: Compiling the NVIDIA kernel module gives this error:

You appear to be compiling the NVIDIA kernel module with
a compiler different from the one that was used to compile
the running kernel. This may be perfectly fine, but there
are cases where this can lead to unexpected behaviour and
system crashes.

If you know what you are doing and want to override this
check, you can do so by setting IGNORE_CC_MISMATCH.

In any other case, set the CC environment variable to the
name of the compiler that was used to compile the kernel.

A: You should compile the NVIDIA kernel module with the same compiler
version that was used to compile your kernel. Some Linux kernel data
structures are dependent on the version of gcc used to compile it;
for example, in include/linux/spinlock.h:

...
* Most gcc versions have a nasty bug with empty initializers.
*/
#if (__GNUC__ > 2)
typedef struct { } rwlock_t;
#define RW_LOCK_UNLOCKED (rwlock_t) { }
#else
typedef struct { int gcc_is_buggy; } rwlock_t;
#define RW_LOCK_UNLOCKED (rwlock_t) { 0 }
#endif

If the kernel is compiled with gcc 2.x, but gcc 3.x is used when the
kernel interface is compiled (or vice versa), the size of rwlock_t
will vary, and things like ioremap will fail.

To check what version of gcc was used to compile your kernel, you
can examine the output of:

cat /proc/version

To check what version of gcc is currently in your $PATH, you can
examine the output of:

gcc -v

Q: X fails with error "Failed to allocate LUT context DMA"

A: This is one of the possible consequences of compiling the NVIDIA
kernel interface with a different gcc version than used to compile
the Linux kernel (see above).

Q: What is NVIDIA's policy towards development series Linux kernels?

A: NVIDIA does not officially support development series kernels.
However, all the kernel module source code that interfaces with the
Linux kernel is available in the usr/src/nv/ directory of the .run file.
NVIDIA encourages members of the Linux community to develop patches
to these source files to support development series kernels. A google
search will most likely yield several community supported patches.

Q: I recently updated various libraries on my system using my Linux
distributor's update utility, and the NVIDIA graphics driver no
longer works. What's wrong?

A: Conflicting libraries may have been installed by your
distribution's update utility; please see APPENDIX C: INSTALLED
COMPONENTS for details on how to diagnose this.

Q: `rpm --rebuild` gives an error "unknown option".

A: Recent versions of rpm no longer support the "--rebuild" option;
if you have such a version of rpm, you should instead use the command
`rpmbuild --rebuild`. The `rpmbuild` executable is provided by the
rpm-build package.

Q: I'm using either nForce of nForce2 internal graphics, and I see
warnings like this in my XFree86.0.log file:

Not using mode "1600x1200" (exceeds valid memory bandwidth usage)

A: Integrated graphics have stricter memory bandwidth limitations
that restrict the resolution and refresh rate of the modes you
request. To work around this, you can reduce the maximum refresh
rate by lowering the upper value of the "VertRefresh" range in the
Monitor section of your XF86Config file. Though not recommended,
you can disable the memory bandwidth test with the "NoBandWidthTest"
XF86Config file option.

Q: I've rebuilt the NVIDIA kernel module, but when I try to insert
it, I get a message telling me I have unresolved symbols.

A. Unresolved symbols are most often caused by a mismatch between your
kernel sources and your running kernel. They must match for the
NVIDIA kernel module to build correctly. Please make sure your kernel
sources are installed and configured to match your running kernel.

Q: How do I tell if I have my kernel sources installed?

A: If you're running on a distro that uses RPM (Red Hat, Mandrake, SuSE,
etc), then you can use RPM to tell you. At a shell prompt, type:

`rpm -qa | grep kernel`

and look at the output. You should see a package that corresponds
to your kernel (often named something like kernel-2.4.18-3)
and a kernel source package with the same version (often named
something like kernel-source-2.4.18-3). If none of the lines seem
to correspond to a source package, then you'll probably need to
install it. If the versions listed mismatch (ex: kernel-2.4.18-10 vs.
kernel-source-2.4.18-3), then you'll need to update the kernel-source
package to match the installed kernel. If you have multiple kernels
installed, you need to install the kernel-source package that
corresponds to your *running* kernel (or make sure your installed
source package matches the running kernel). You can do this by
looking at the output of 'uname -r' and matching versions.

Q: Why am I unable to load the NVIDIA kernel module that I compiled
for the Red Hat Linux 7.3 2.4.18-3bigmem kernel?

A: The kernel header files Red Hat Linux distributes for Red Hat Linux 7.3
2.4.18-3bigmem kernel are misconfigured. NVIDIA's precompiled kernel
module for this kernel can be loaded, but if you wish to compile the
NVIDIA kernel interface files yourself for this kernel, then you'll
need to perform the following:

cd /lib/modules/`uname -r`/build/
cp configs/kernel-2.4.18-i686-bigmem.config .config
make mrproper oldconfig dep

Note: Red Hat Linux ships kernel header files that are simultaneously
configured for ALL of their kernels for a particular distribution
version. A header file generated at boot time sets up a few parameters
that select the correct configuration. Rebuilding the kernel headers
with the above commands will create header files suitable for the
Red Hat Linux 7.3 2.4.18-3bigmem kernel configuration only, thus trashing
the header files for the other configurations.

Q: X takes a long time to start (possibly several minutes). What can
I do?

A: Most of the startx delay problems we have found are caused by incorrect
data in video BIOSes about what display devices are possibly connected
or what i2c port should be used for detection. You can work around
these problems with the XF86Config option "IgnoreDisplayDevices"
(please see the description in (app-d) APPENDIX D: XF86CONFIG OPTIONS).

Q: Why does X use so much memory?

A: When measuring any application's memory usage, you must be
careful to distinguish between physical system RAM used and virtual
mappings of shared resources. For example, most shared libraries exist
only once in physical memory but are mapped into multiple processes.
This memory should only be counted once when computing total memory
usage. In the same way, the video memory on a graphics card or
register memory on any device can be mapped into multiple processes.
These mappings do not consume normal system RAM.

This has been a frequently discussed topic on XFree86 mailing
lists; see, for example:

http://marc.theaimsgroup.com/?l=xfree-xpert&m=96835767116567&w=2

The `pmap` utility described in the above thread and available here:

http://web.hexapodia.org/~adi/pmap.c

is a useful tool in distinguishing between types of memory mappings.
For example, while `top` may indicate that X is using several hundred
MB of memory, the last line of output from pmap:

mapped: 287020 KB writable/private: 9932 KB shared: 264656 KB

reveals that X is really only using roughly 10MB of system RAM
(the "writable/private" value).

Note, also, that X must allocate resources on behalf of X clients (the
window manager, your web browser, etc); X's memory usage will increase
as more clients request resources such as pixmaps, and decrease as
you close X applications.

Q: OpenGL applications leak significant amounts of memory on my system!

A: If your kernel is making use of the -rmap VM, the system may be leaking
memory due to a memory management optimization introduced in -rmap14a.
The -rmap VM has been adopted by several popular distributions, the
memory leak is known to be present in some of the distribution kernels;
it has been fixed in -rmap15e.

If you suspect that your system is affected, please try upgrading your
kernel or contact the distribution's vendor for assistance.

Q: Some OpenGL applications (like Quake3 Arena) crash when I start them
on Red Hat Linux 9.0.

A: Some versions of the glibc package shipped by Red Hat that support
TLS do not properly handle using dlopen() to access shared libraries
which utilize some TLS models. This problem is exhibited, for example,
when Quake3 Area dlopen()'s NVIDIA's libGL library. Please obtain
at least glibc-2.3.2-11.9 which is available as an update from Red Hat.

Q: I've installed the driver, but my Enable 3D Acceleration checkbox is still
greyed out! What did I do wrong?

A: Most distribution-provided configuration applets aren't aware of the NVIDIA
accelerated driver, and consequently won't update themselves when you install
the driver. Your driver, if it has been installed properly, should function
fine.

Q: Where can I find the tarballs?

A: Please visit ftp://download.nvidia.com/XFree86/1.0-4496/.

Q: Where can I find older driver versions?

A: Please visit ftp://download.nvidia.com/XFree86_40/.

Q: X does not restore the vga console when run on a TV. I get this
error message in my XFree86 log file:

Unable to initialize the XFree86 int10 module; the console may not
be restored correctly on your TV.

A: The NVIDIA XFree86 driver uses the XFree86 Int10 module to save
and restore console state on TV out, and will not be able to
restore the console correctly if it cannot use the Int10 module.
If you have built XFree86 yourself, please be sure you have
built the Int10 module. If you are using a build of XFree86
provided by a Linux distribution, and are missing the Int10
module, please contact your distributor,

__________________________________________________________________________

(sec-05) CONTACTING US
__________________________________________________________________________

There is an NVIDIA Linux Driver web forum. You can access it by going
to www.nvnews.net and following the "Forum" and "Linux Discussion Area"
links. This is the preferable tool for seeking help; users can post
questions, answer other users' questions, and search the archives of
previous postings.

If all else fails, you can contact NVIDIA for support at:
linux-bugs@nvidia.com. But please, only send email to this address
after you've followed the FREQUENTLY ASKED QUESTIONS section in this
README and asked for help on the nvnews.net web forum.

__________________________________________________________________________

(sec-06) FURTHER RESOURCES
__________________________________________________________________________

Linux OpenGL ABI
http://oss.sgi.com/projects/ogl-sample/ABI/

NVIDIA Linux HowTo
http://www.tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html

OpenGL
www.opengl.org

The XFree86 Project
www.xfree86.org

#nvidia (irc.openprojects.net)

__________________________________________________________________________

(app-a) APPENDIX A: SUPPORTED NVIDIA GRAPHICS CHIPS
__________________________________________________________________________

NVIDIA CHIP NAME DEVICE PCI ID

o RIVA TNT 0x0020
o RIVA TNT2 0x0028
o RIVA TNT2 Ultra 0x0029
o Vanta 0x002C
o RIVA TNT2 Model 64 0x002D
o Aladdin TNT2 0x00A0
o GeForce 256 0x0100
o GeForce DDR 0x0101
o Quadro 0x0103
o GeForce2 MX/MX 400 0x0110
o GeForce2 MX 100/200 0x0111
o GeForce2 Go 0x0112
o Quadro2 MXR/EX/Go 0x0113
o GeForce2 GTS 0x0150
o GeForce2 Ti 0x0151
o GeForce2 Ultra 0x0152
o Quadro2 Pro 0x0153
o GeForce4 MX 460 0x0170
o GeForce4 MX 440 0x0171
o GeForce4 MX 420 0x0172
o GeForce4 MX 440-SE 0x0173
o GeForce4 440 Go 0x0174
o GeForce4 420 Go 0x0175
o GeForce4 420 Go 32M 0x0176
o GeForce4 460 Go 0x0177
o Quadro4 550 XGL 0x0178
o GeForce4 440 Go 64M 0x0179
o Quadro4 NVS 0x017A
o Quadro4 500 GoGL 0x017C
o GeForce4 410 Go 16M 0x017D
o GeForce4 MX 440 with AGP8X 0x0181
o GeForce4 MX 440SE with AGP8X 0x0182
o GeForce4 MX 420 with AGP8X 0x0183
o Quadro4 580 XGL 0x0188
o Quadro4 280 NVS 0x018A
o Quadro4 380 XGL 0x018B
o GeForce4 448 Go 0x0186
o GeForce4 488 Go 0x0187
o GeForce2 Integrated GPU 0x01A0
o GeForce4 MX Integrated GPU 0x01F0
o GeForce3 0x0200
o GeForce3 Ti 200 0x0201
o GeForce3 Ti 500 0x0202
o Quadro DCC 0x0203
o GeForce4 Ti 4600 0x0250
o GeForce4 Ti 4400 0x0251
o GeForce4 Ti 4200 0x0253
o Quadro4 900 XGL 0x0258
o Quadro4 750 XGL 0x0259
o Quadro4 700 XGL 0x025B
o GeForce4 Ti 4800 0x0280
o GeForce4 Ti 4200 with AGP8X 0x0281
o GeForce4 Ti 4800 SE 0x0282
o GeForce4 4200 Go 0x0286
o Quadro4 980 XGL 0x0288
o Quadro4 780 XGL 0x0289
o Quadro4 700 GoGL 0x028C
o GeForce FX 5800 Ultra 0x0301
o GeForce FX 5800 0x0302
o GeForce FX 5600 Ultra 0x0311
o GeForce FX 5600 0x0312
o GeForce FX 5200 Ultra 0x0321
o GeForce FX 5200 0x0322
o Quadro FX 2000 0x0308
o Quadro FX 1000 0x0309
o Quadro FX 500 0x032B

Please note that the RIVA 128/128ZX chips are supported by the open
source 'nv' driver for XFree86, but not by the NVIDIA Accelerated Linux
Driver Set.

If you want to check your Device PCI IDs for comparison with the table
above, you can use either `cat /proc/pci` or `lspci -n`; in the later
case, look for the device with vendor id "10de", eg:

02:00.0 Class 0300:10de:0100 (rev 10)

__________________________________________________________________________

(app-b) APPENDIX B: MINIMUM SOFTWARE REQUIREMENTS
__________________________________________________________________________

o linux kernel 2.2.12 # cat /proc/version
o XFree86 4.0.1 # XFree86 -version
o Kernel modutils 2.1.121 # insmod -V

If you need to build the NVIDIA kernel module:

o binutils 2.9.5 # size --version
o GNU make 3.77 # make --version
o gcc 2.91.66 # gcc --version

If you build from source rpms:

o spec-helper rpm # rpm -qi spec-helper

All official stable kernel releases from 2.2.12 and up are supported;
"prerelease" versions such as "2.4.3-pre2" are not supported, nor are
development series kernels such as 2.3.x or 2.5.x. The linux kernel
can be downloaded from www.kernel.org or one of its mirrors.

binutils and gcc can be retrieved from www.gnu.org or one of its mirrors.

If you are using XFree86, but do not have a file /var/log/XFree86.0.log,
then you probably have a 3.x version of XFree86 and must upgrade.

If you are setting up XFree86 4.x for the first time, it is often easier
to begin with one of the open source drivers that ships with XFree86
(either 'nv', 'vga' or 'vesa'). Once XFree86 is operating properly with
the open source driver, then it is easier to switch to the nvidia driver.

Note that newer NVIDIA GPUs may not work with older versions of the "nv"
driver shipped with XFree86. For example, the "nv" driver that shipped
with XFree86 version 4.0.1 did not recognize the GeForce2 family and
the Quadro2 MXR GPUs. However, this was fixed in XFree86 version 4.0.2
(XFree86 can be retrieved from www.xfree86.org).

These software packages may also be available through your linux
distributor.

__________________________________________________________________________

(app-c) APPENDIX C: 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):

o An XFree86 driver (/usr/X11R6/lib/modules/drivers/nvidia_drv.o);
this driver is needed by XFree86 to use your NVIDIA hardware.
The nvidia_drv.o driver is binary compatible with XFree86 4.0.1
and greater.

o A GLX extension module for XFree86
(/usr/X11R6/lib/modules/extensions/libglx.so.x.y.z); this module is
used by XFree86 to provide server-side glx support.

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 XF86Config 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); please see (app-p) APPENDIX P:
XVMC SUPPORT 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 XFree86
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 XFree86, 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/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.

o ELF TLS OpenGL and OpenGL core libraries
(/usr/lib/tls/libGL.so.x.y.z and /usr/lib/tls/libGLcore.so.x.y.z).
Linux systems that utilize glibc 2.3 or greater with tls support
enabled, use a new mechanism for thread local storage (TLS).
This mechanism is incompatible with NVIDIA's previous thread
local storage support; therefore, special ELF TLS libraries are
provided, and installed in /usr/lib/tls/ on systems that support it.
The runtime loader will select between the OpenGL libraries installed
in /usr/lib/, and those installed in /usr/lib/tls/.

It should also be noted that this new TLS mechanism also affects
the GLX extension module (libglx.so.x.y.z). However, because the
XFree86 loader does not know how to select between tls and non-tls
libraries, the correct libglx library is automatically installed
in /usr/X11R6/lib/modules/extensions/.

You can determine if your glibc uses the new thread local
storage mechanism by executing the command:

/lib/libc.so.6 | grep "Thread-local storage support included."

The above command will print "Thread-local storage support
included." on systems that support the new thread local storage.

o The application nvidia-installer (/usr/bin/nvidia-installer) is
NVIDIA's tool for installing and updating NVIDIA drivers. Please see
(sec-03) EDITING YOUR XF86CONFIG FILE 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/drivers/nvidia_drv.o

/usr/X11R6/lib/modules/extensions/libglx.so.x.y.z
/usr/X11R6/lib/modules/extensions/libglx.so -> libglx.so.x.y.z

/usr/lib/libGL.so.x.y.z
/usr/lib/libGL.so.x -> libGL.so.x.y.z
/usr/lib/libGL.so -> libGL.so.x

/usr/lib/libGLcore.so.x.y.z
/usr/lib/libGLcore.so.x -> libGLcore.so.x.y.z

/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 won't look at
-- we've 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 "/usr/X11R6/lib/libGLcore.so*".

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
libglut.so.3 => /usr/lib/libglut.so.3 (0x40014000)
libGLU.so.1 => /usr/lib/libGLU.so.1 (0x40046000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x40062000)
libc.so.6 => /lib/libc.so.6 (0x4009f000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x4018d000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40196000)
libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x401ac000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x401c0000)
libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x401cd000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401d6000)
libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0x402ab000)
libm.so.6 => /lib/libm.so.6 (0x4048d000)
libdl.so.2 => /lib/libdl.so.2 (0x404a9000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (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.

__________________________________________________________________________

(app-d) APPENDIX D: XF86CONFIG OPTIONS
__________________________________________________________________________

The following driver options are supported by the NVIDIA XFree86 driver:

Option "NvAGP" "integer"
Configure AGP support. Integer argument can be one of:
0 : disable agp
1 : use NVIDIA's internal AGP support, if possible
2 : use AGPGART, if possible
3 : use any agp support (try AGPGART, then NVIDIA's AGP)
Please note that NVIDIA's internal AGP support cannot
work if AGPGART is either statically compiled into your
kernel or is built as a module, but loaded into your
kernel (some distributions load AGPGART into the kernel
at boot up). Default: 3 (the default was 1 until after
1.0-1251).

Option "NoLogo" "boolean"
Disable drawing of the NVIDIA logo splash screen at
X startup. Default: the logo is drawn.

Option "RenderAccel" "boolean"
Enable or disable hardware acceleration of the RENDER
extension. THIS OPTION IS EXPERIMENTAL. ENABLE IT AT YOUR
OWN RISK. There is no correctness test suite for the
RENDER extension so NVIDIA can not verify that RENDER
acceleration works correctly. Default: hardware
acceleration of the RENDER extension is disabled.

Option "NoRenderExtension" "boolean"
Disable the RENDER extension. Other than recompiling
the X-server, XFree86 doesn't seem to have another way of
disabling this. Fortunatly, we can control this from the
driver so we export this option. This is useful in depth
8 where RENDER would normally steal most of the default
colormap. Default: RENDER is offered when possible.

Option "UBB" "boolean"
Enable or disable Unified Back Buffer on any Quadro
based GPUs (Quadro4 NVS excluded); please see
Appendix M for a description of UBB. This option has
no affect on non-Quadro chipsets. Default: UBB is on
for Quadro chipsets.

Option "WindowFlip" "boolean"
Enable or disable window flipping when UBB is enabled;
please see Appendix M for a description. This has no
affect when UBB is off. This may improve performance
for 3D applications. Default: Window flipping is off
by default even when UBB is enabled.

Option "PageFlip" "boolean"
Enable or disable page flipping; please see Appendix M
for a description. Default: page flipping is enabled.

Option "DigitalVibrance" "integer"
Enables Digital Vibrance Control. The range of valid
values are 0 through 255. This feature is not available
on products older than GeForce2. Default: 0.

Option "Dac8Bit" "boolean"
Most Quadro parts by default use a 10 bit color look
up table (LUT) by default; setting this option to TRUE forces
these graphics chips to use an 8 bit (LUT). Default:
a 10 bit LUT is used, when available.

Option "Overlay" "boolean"
Enables RGB workstation overlay visuals. This is only
supported on Quadro4 and Quadro FX chips (Quadro4 NVS
excluded) in depth 24. This option causes the server to
advertise the SERVER_OVERLAY_VISUALS root window property
and GLX will report single and double buffered, Z-buffered
16 bit overlay visuals. The transparency key is pixel
0x0000 (hex). There is no gamma correction support in
the overlay plane. This feature requires XFree86 version
4.1.0 or newer. NV17/18 based Quadros (ie. 500/550 XGL)
have additional restrictions, namely, overlays are not
supported in TwinView mode or with virtual desktops
larger than 2046x2047 in any dimension (eg. it will not
work in 2048x1536 modes). Quadro 7xx/9xx and Quadro FX
will offer overlay visuals in these modes (TwinView, or
virtual desktops larger than 2046x2047), but the overlay
will be emulated with a substantial performance penalty.
Default: off.

Option "CIOverlay" "boolean"
Enables Color Index workstation overlay visuals with
identical restrictions to Option "Overlay" above.
The server will offer visuals both with and without a
transparency key. These are depth 8 PseudoColor visuals.
Enabling Color Index overlays on X servers older than
XFree86 4.3 will force the RENDER extension to be disabled
due to bugs in the RENDER extension in older X servers.
Default: off.

Option "TransparentIndex" "integer"
When color index overlays are enabled, this option allows
the user to choose which pixel is used for the transparent
pixel in visuals featuring transparent pixels. This value
is clamped between 0 and 255 (Note: some applications
such as Alias/Wavefront's Maya require this to be zero
in order to work correctly). Default: 0.

Option "OverlayDefaultVisual" "boolean"
When overlays are used, this option sets the default
visual to an overlay visual thereby putting the root
window in the overlay. This option is not recommended
for RGB overlays. Default: off.

Option "SWCursor" "boolean"
Enable or disable software rendering of the X cursor.
Default: off.

Option "HWCursor" "boolean"
Enable or disable hardware rendering of the X cursor.
Default: on.

Option "CursorShadow" "boolean" Enable or disable use of a
shadow with the hardware accelerated cursor; this is a
black translucent replica of your cursor shape at a
given offset from the real cursor. This option is
only available on GeForce2 or better hardware (ie
everything but TNT/TNT2, GeForce 256, GeForce DDR and
Quadro). Default: no cursor shadow.

Option "CursorShadowAlpha" "integer"
The alpha value to use for the cursor shadow; only
applicable if CursorShadow is enabled. This value must
be in the range [0, 255] -- 0 is completely transparent;
255 is completely opaque. Default: 64.

Option "CursorShadowXOffset" "integer"
The offset, in pixels, that the shadow image will be
shifted to the right from the real cursor image; only
applicable if CursorShadow is enabled. This value must
be in the range [0, 32]. Default: 4.

Option "CursorShadowYOffset" "integer"
The offset, in pixels, that the shadow image will be
shifted down from the real cursor image; only applicable
if CursorShadow is enabled. This value must be in the
range [0, 32]. Default: 2.

Option "ConnectedMonitor" "string"
Allows you to override what the NVIDIA kernel module
detects is connected to your video card. This may
be useful, for example, if you use a KVM (keyboard,
video, mouse) switch and you are switched away when
X is started. In such a situation, the NVIDIA kernel
module can't detect what display devices are connected,
and the NVIDIA X driver assumes you have a single CRT.

Valid values for this option are "CRT" (cathode ray
tube), "DFP" (digital flat panel), or "TV" (television);
if using TwinView, this option may be a comma-separated
list of display devices; e.g.: "CRT, CRT" or "CRT, DFP".

NOTE: anything attached to a 15 pin VGA connector is
regarded by the driver as a CRT. "DFP" should only be
used to refer to flatpanels connected via a DVI port.

Default: string is NULL.

Option "UseEdidFreqs" "boolean"
This option causes the X server to use the HorizSync
and VertRefresh ranges given in a display device's EDID,
if any. EDID provided range information will override
the HorizSync and VertRefresh ranges specified in the
Monitor section. If a display device does not provide an
EDID, or the EDID doesn't specify an hsync or vrefresh
range, then the X server will default to the HorizSync
and VertRefresh ranges specified in the Monitor section.

Option "IgnoreEDID" "boolean"
Disable probing of EDID (Extended Display Identification
Data) from your monitor. Requested modes are compared
against values gotten from your monitor EDIDs (if any)
during mode validation. Some monitors are known to lie
about their own capabilities. Ignoring the values that
the monitor gives may help get a certain mode validated.
On the other hand, this may be dangerous if you don't
know what you are doing. Default: Use EDIDs.

Option "NoDDC" "boolean"
Synonym for "IgnoreEDID"

Option "FlatPanelProperties" "string"
Requests particular properties of any connected flat
panels as a comma-separated list of property=value pairs.
Currently, the only two available properties are 'Scaling'
and 'Dithering'. The possible values for 'Scaling' are:
'default' (the driver will use whatever scaling state
is current), 'native' (the driver will use the flat
panel's scaler, if it has one), 'scaled' (the driver
will use the NVIDIA scaler, if possible), 'centered'
(the driver will center the image, if possible),
and 'aspect-scaled' (the driver will scale with the
NVIDIA scaler, but keep the aspect ratio correct).
The possible values for 'Dithering' are: 'default'
(the driver will decide when to dither), 'enabled' (the
driver will always dither when possible), and 'disabled'
(the driver will never dither). If any property is not
specified, it's value shall be 'default'. An example
properties string might look like:

"Scaling = centered, Dithering = enabled"

Option "UseInt10Module" "boolean"
Enable use of the XFree86 Int10 module to soft-boot all
secondary cards, rather than POSTing the cards through
the NVIDIA kernel module. Default: off (POSTing is
done through the NVIDIA kernel module).

Option "TwinView" "boolean"
Enable or disable TwinView. Please see APPENDIX I for
details. Default: TwinView is disabled.

Option "TwinViewOrientation" "string"
Controls the relationship between the two display devices
when using TwinView. Takes one of the following values:
"RightOf" "LeftOf" "Above" "Below" "Clone". Please see
APPENDIX I for details. Default: string is NULL.

Option "SecondMonitorHorizSync" "range(s)"
This option is like the HorizSync entry in the Monitor
section, but is for the second monitor when using
TwinView. Please see APPENDIX I for details. Default:
none.

Option "SecondMonitorVertRefresh" "range(s)"
This option is like the VertRefresh entry in the Monitor
section, but is for the second monitor when using
TwinView.

mplayer -vo help 하면 여러가지 video out 종류들이 나오는데 -vo x11, -vo sdl 등등 이런것도 시도해 보심이...