This section provides solutions to common problems associated with the NVIDIA SunOS x86 Driver.
|
My X server fails to start, and my X log file contains the error: (EE) NVIDIA(0): The NVIDIA kernel module does not appear to be receiving (EE) NVIDIA(0): interrupts generated by the NVIDIA graphics device. (EE) NVIDIA(0): Please see the FREQUENTLY ASKED QUESTIONS section in (EE) NVIDIA(0): the README for additional information. |
|
|
This can be caused by a variety of problems, such as PCI IRQ routing errors, I/O APIC problems or conflicts with other devices sharing the IRQ (or their drivers). If possible, configure your system such that your graphics card does not share its IRQ with other devices (try moving the graphics card to another slot if applicable, unload/disable the driver(s) for the device(s) sharing the card's IRQ, or remove/disable the device(s)). |
|
|
X starts for me, but OpenGL applications terminate immediately. |
|
|
If X starts but you have trouble with OpenGL, you most likely have a problem with other libraries in the way, or there are stale symlinks. See Appendix C, Installed Components for details. You should also check that the correct extensions are present;
% xdpyinfo
should show the “GLX” and “NV-GLX” extensions present. If these two extensions are not present, then there is most likely a problem loading the glx module, or it is unable to implicitly load GLcore. Check your X config file and make sure that you are loading glx (see Chapter 2, Configuring X for the NVIDIA Driver). If your X config file is correct, then check the X log file for warnings/errors pertaining to GLX. Also check that all of the necessary symlinks are in place (refer to Appendix C, Installed Components). |
|
|
When Xinerama is enabled, my stereo glasses are shuttering only when the stereo application is displayed on one specific X screen. When the application is displayed on the other X screens, the stereo glasses stop shuttering. |
|
|
This problem occurs with DDC and "blue line" stereo glasses, that get the stereo signal from one video port of the graphics card. When a X screen does not display any stereo drawable the stereo signal is disabled on the associated video port. Forcing stereo flipping allows the stereo glasses to shutter continuously. This can be done by enabling the OpenGL control "Force Stereo Flipping" in nvidia-settings, or by setting the X configuration option "ForceStereoFlipping" to "1". |
|
|
My X server fails to start, and my X log file contains the error: (EE) NVIDIA(0): Failed to load the NVIDIA kernel module! |
|
|
The X driver will abort with this error message if the NVIDIA
kernel module fails to load or the device files aren't present. If
you receive this error, you should check the output of
If |
|
|
CDE and JDS do not start when TwinView is enabled. |
|
|
When in TwinView, the NVIDIA X driver normally provides a Xinerama extension that X clients (such as window managers) can use to to discover the current TwinView configuration. Some window mangers can get confused by this information. Use the following option in the "device" section of the Xorg configuration file to disable this behavior: Option "NoTwinViewXineramaInfo" "1" |
|
|
When running multiple OpenGL applications concurrently, some appear to stall. |
|
|
Changing the default process scheduling class to the real-time class may help concurrent OpenGL applications render smoothly. To select real-time as the default scheduling class, run
dispadmin -d RT as
|
|
|
My system runs, but seems unstable. What is wrong? |
|
|
Your stability problems may be AGP-related. See Appendix F, Configuring AGP for details. |
|
|
OpenGL applications are running slowly |
|
|
The application is probably using a different library still on your system, rather than the NVIDIA supplied OpenGL library. Please see Appendix C, Installed Components for details. |
|
|
There are problems running Quake2. |
|
|
Quake2 requires some minor setup to get it going. First, in the
Quake2 directory, the install creates a symlink called
% 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 the same resolution as Quake2 to emulate full-screen mode. |
|
|
I am using either nForce of nForce2 internal graphics, and I see warnings like this in my X log file: Not using mode "1600x1200" (exceeds valid memory bandwidth usage) |
|
|
Integrated graphics have more strict memory bandwidth
limitations that limit 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 |
|
|
X takes a long time to start (possibly several minutes). |
|
|
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 X config option
|
|
|
Fonts are incorrectly sized after installing the NVIDIA driver. |
|
|
Incorrectly sized fonts are generally caused by incorrect DPI (Dots Per Inch) information. You can check what X thinks the physical size of your monitor is, by running: % xdpyinfo | grep dimensions This will report the size in pixels, and in millimeters. If these numbers are wrong, you can correct them by modifying the X server's DPI setting. See Appendix W, Dots Per Inch for details. |
|
|
General problems with ALi chipsets |
|
|
There are some known timing and signal integrity issues on ALi chipsets. The following tips may help stabilize problematic ALI systems:
|