<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 1 September 2005), see www.w3.org">
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii">
<title>Chapter 7. Frequently Asked Questions</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
<link rel="start" href="index.html" title=
"NVIDIA Accelerated Linux Graphics Driver README and Installation Guide">
<link rel="up" href="part-01.html" title=
"Part I. Installation and Configuration Instructions">
<link rel="prev" href="chapter-06-section-02.html" title=
"Manually Editing the Configuration File">
<link rel="next" href="chapter-08.html" title=
"Chapter 8. Common Problems">
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Chapter 7. Frequently
Asked Questions</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href=
"chapter-06-section-02.html">Prev</a> </td>
<th width="60%" align="center">Part I. Installation and
Configuration Instructions</th>
<td width="20%" align="right"> <a accesskey="n" href=
"chapter-08.html">Next</a></td>
</tr>
</table>
<hr></div>
<div class="chapter" lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="faq" id=
"faq"></a>Chapter 7. Frequently Asked Questions</h2>
</div>
</div>
</div>
<p>This section provides answers to frequently asked questions
associated with the NVIDIA Linux x86_64 Driver and its
installation. Common problem diagnoses can be found in <a href=
"chapter-08.html" title=
"Chapter 8. Common Problems">Chapter 8, <i>Common
Problems</i></a> and tips for new users can be found in <a href=
"appendix-h.html" title=
"Appendix H. Tips for New Linux Users">Appendix H,
<i>Tips for New Linux Users</i></a>. Also, detailed information for
specific setups is provided in the <a href=
"part-02.html">Appendices</a>.</p>
<div class="qandaset">
<table border="0" summary="Q and A Set">
<col align="left" width="1%">
<tbody>
<tr class="qandadiv">
<td align="left" valign="top" colspan="2">
<h3 class="title"><a name="id301766" id="id301766"></a>7.1.
NVIDIA-INSTALLER</h3>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301771" id=
"id301771"></a><a name="id301773" id="id301773"></a></td>
<td align="left" valign="top">
<p><b>How do I extract the contents of the</b> <code class=
"filename">.run</code> <b>without actually installing the
driver?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Run the installer as follows:</p>
<pre class="screen">
# sh NVIDIA-Linux-x86_64-173.14.31-pkg1.run --extract-only
</pre>
<p>This will create the directory
NVIDIA-Linux-x86_64-173.14.31-pkg1, containing the uncompressed
contents of the <code class="filename">.run</code> file.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301784" id=
"id301784"></a><a name="id301786" id="id301786"></a></td>
<td align="left" valign="top">
<p><b>How can I see the source code to the kernel interface
layer?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>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:</p>
<pre class="screen">
# sh NVIDIA-Linux-x86-1.0-6629-pkg1.run --extract-only
# cd NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/
</pre>
<p></p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301804" id=
"id301804"></a><a name="id301806" id="id301806"></a></td>
<td align="left" valign="top">
<p><b>How and when are the the NVIDIA device files created?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Depending on the target system's configuration, the NVIDIA
device files used to be created in one of three different ways:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>at installation time, using mknod</p>
</li>
<li>
<p>at module load time, via devfs (Linux device file system)</p>
</li>
<li>
<p>at module load time, via hotplug/udev</p>
</li>
</ul>
</div>
<p>With current NVIDIA driver releases, device files are created or
modified by the X driver when the X server is started.</p>
<p>By default, the NVIDIA driver will attempt to create device
files with the following attributes:</p>
<pre class="screen">
UID: 0 - 'root'
GID: 0 - 'root'
Mode: 0666 - 'rw-rw-rw-'
</pre>
<p>Existing device files are changed if their attributes don't
match these defaults. If you want the NVIDIA driver to create the
device files with different attributes, you can specify them with
the "NVreg_DeviceFileUID" (user), "NVreg_DeviceFileGID" (group) and
"NVreg_DeviceFileMode" NVIDIA Linux kernel module parameters.</p>
<p>For example, the NVIDIA driver can be instructed to create
device files with UID=0 (root), GID=44 (video) and Mode=0660 by
passing the following module parameters to the NVIDIA Linux kernel
module:</p>
<pre class="screen">
NVreg_DeviceFileUID=0
NVreg_DeviceFileGID=44
NVreg_DeviceFileMode=0660
</pre>
<p>The "NVreg_ModifyDeviceFiles" NVIDIA kernel module parameter
will disable dynamic device file management, if set to 0.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301860" id=
"id301860"></a><a name="id301862" id="id301862"></a></td>
<td align="left" valign="top">
<p><b>Why does NVIDIA not provide RPMs anymore?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>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.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301874" id=
"id301874"></a><a name="id301876" id="id301876"></a></td>
<td align="left" valign="top">
<p><b>Can the nvidia-installer use a proxy server?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Yes, because the FTP support in nvidia-installer is based on
snarf, it will honor the <code class="envar">FTP_PROXY</code>,
<code class="envar">SNARF_PROXY</code>, and <code class=
"envar">PROXY</code> environment variables.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301898" id=
"id301898"></a><a name="id301901" id="id301901"></a></td>
<td align="left" valign="top">
<p><b>What is the significance of the</b> <code class=
"filename">pkg#</code> <b>suffix on the</b> <code class=
"filename">.run</code> <b>file?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>The <code class="filename">pkg#</code> suffix is used to
distinguish between <code class="filename">.run</code> 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).</p>
<p><code class="filename">.run</code> files with the same version
number, but different pkg numbers, only differ in what precompiled
kernel interfaces are included. Additionally, <code class=
"filename">.run</code> files with higher pkg numbers will contain
everything the <code class="filename">.run</code> files with lower
pkg numbers contain.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301964" id=
"id301964"></a><a name="id301966" id="id301966"></a></td>
<td align="left" valign="top">
<p><b>I have already installed
NVIDIA-Linux-x86_64-173.14.31-pkg1.run, but I see that
NVIDIA-Linux-x86_64-173.14.31-pkg2.run was just posted on the
NVIDIA Linux driver download page. Should I download and install
NVIDIA-Linux-x86_64-173.14.31-pkg2.run?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>This is not necessary. The driver contained within all 173.14.31
<code class="filename">.run</code> files will be identical. There
is no need to reinstall.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id301986" id=
"id301986"></a><a name="id301988" id="id301988"></a></td>
<td align="left" valign="top">
<p><b>Can I add my own precompiled kernel interfaces to a</b>
<code class="filename">.run</code> <b>file?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Yes, the <code class="option">--add-this-kernel</code>
<code class="filename">.run</code> file option will unpack the
<code class="filename">.run</code> file, build a precompiled kernel
interface for the currently running kernel, and repackage the
<code class="filename">.run</code> file, appending <code class=
"filename">-custom</code> to the filename. This may be useful, for
example. if you administer multiple Linux computers, each running
the same kernel.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302034" id=
"id302034"></a><a name="id302036" id="id302036"></a></td>
<td align="left" valign="top">
<p><b>Where can I find the source code for the</b> <code class=
"filename">nvidia-installer</code> <b>utility?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>The <code class="filename">nvidia-installer</code> utility is
released under the GPL. The latest source code for it is available
at: <a href="ftp://download.nvidia.com/XFree86/nvidia-installer"
target=
"_top">ftp://download.nvidia.com/XFree86/nvidia-installer</a></p>
</td>
</tr>
<tr class="qandadiv">
<td align="left" valign="top" colspan="2">
<h3 class="title"><a name="id302104" id="id302104"></a>7.2. NVIDIA
Driver</h3>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302110" id=
"id302110"></a><a name="id302112" id="id302112"></a></td>
<td align="left" valign="top">
<p><b>Where should I start when diagnosing display
problems?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>One of the most useful tools for diagnosing problems is the X
log file in <code class="filename">/var/log</code>. Lines that
begin with <code class="computeroutput">(II)</code> are
information, <code class="computeroutput">(WW)</code> are warnings,
and <code class="computeroutput">(EE)</code> are errors. You should
make sure that the correct config file (i.e. the config file you
are editing) is being used; look for the line that begins with:</p>
<pre class="screen">
(==) Using config file:
</pre>
<p>Also make sure that the NVIDIA driver is being used, rather than
the “<span class="quote">nv</span>” or
“<span class="quote">vesa</span>” driver. Search
for</p>
<pre class="screen">
(II) LoadModule: "nvidia"
</pre>
<p>Lines from the driver should begin with:</p>
<pre class="screen">
(II) NVIDIA(0)
</pre>
<p></p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="xverboselog" id=
"xverboselog"></a><a name="id302184" id="id302184"></a></td>
<td align="left" valign="top">
<p><b>How can I increase the amount of data printed in the X log
file?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>By default, the NVIDIA X driver prints relatively few messages
to stderr and the X log file. If you need to troubleshoot, then it
may be helpful to enable more verbose output by using the X command
line options <code class="option">-verbose</code> and <code class=
"option">-logverbose</code>, which can be used to set the verbosity
level for the <code class="filename">stderr</code> and log file
messages, respectively. The NVIDIA X driver will output more
messages when the verbosity level is at or above 5 (X defaults to
verbosity level 1 for <code class="filename">stderr</code> and
level 3 for the log file). So, to enable verbose messaging from the
NVIDIA X driver to both the log file and <code class=
"filename">stderr</code>, you could start X with the verbosity
level set to 5, by doing the following</p>
<pre class="screen">
% startx -- -verbose 5 -logverbose 5
</pre>
<p></p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302522" id=
"id302522"></a><a name="id302524" id="id302524"></a></td>
<td align="left" valign="top">
<p><b>Where can I get</b> <code class="filename">gl.h</code>
<b>or</b> <code class="filename">glx.h</code><b>so I can compile
OpenGL programs?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Most systems come with these header files preinstalled. However,
NVIDIA provides its own <code class="filename">gl.h</code> and
<code class="filename">glx.h</code> files, which get installed by
default as part of driver installation. If you prefer that the
NVIDIA-distributed OpenGL header files not be installed, you can
pass the <code class="option">--no-opengl-headers</code> option to
the <code class=
"filename">NVIDIA-Linux-x86_64-173.14.31-pkg1.run</code> file
during installation.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302570" id=
"id302570"></a><a name="id302572" id="id302572"></a></td>
<td align="left" valign="top">
<p><b>Can I receive email notification of new NVIDIA Accelerated
Linux Graphics Driver releases?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Yes. Fill out the form at: <a href=
"http://www.nvidia.com/view.asp?FO=driver_update" target=
"_top">http://www.nvidia.com/view.asp?FO=driver_update</a></p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302590" id=
"id302590"></a><a name="id302592" id="id302592"></a></td>
<td align="left" valign="top">
<p><b>What is NVIDIA's policy towards development series Linux
kernels?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>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 <code class=
"filename">usr/src/nv/</code> directory of the <code class=
"filename">.run</code> file. NVIDIA encourages members of the Linux
community to develop patches to these source files to support
development series kernels. A web search will most likely yield
several community supported patches.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302616" id=
"id302616"></a><a name="id302619" id="id302619"></a></td>
<td align="left" valign="top">
<p><b>Why does X use so much memory?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>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.</p>
<p>This has been a frequently discussed topic on XFree86 mailing
lists; see, for example:</p>
<p><a href=
"http://marc.theaimsgroup.com/?l=xfree-xpert&m=96835767116567&w=2"
target=
"_top">http://marc.theaimsgroup.com/?l=xfree-xpert&m=96835767116567&w=2</a></p>
<p>The <span><strong class="command">pmap</strong></span> utility
described in the above thread is available here: <a href=
"http://web.hexapodia.org/~adi/pmap.c" target=
"_top">http://web.hexapodia.org/~adi/pmap.c</a> and is a useful
tool in distinguishing between types of memory mappings. For
example, while <span><strong class="command">top</strong></span>
may indicate that X is using several hundred MB of memory, the last
line of output from pmap:</p>
<pre class="screen">
mapped: 287020 KB writable/private: 9932 KB shared: 264656 KB
</pre>
<p>reveals that X is really only using roughly 10MB of system RAM
(the "writable/private" value).</p>
<p>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.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302683" id=
"id302683"></a><a name="id302685" id="id302685"></a></td>
<td align="left" valign="top">
<p><b>Where can I find the tarballs?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Plain tarballs are no longer available. The <code class=
"filename">.run</code> file is a tarball with a shell script
prepended. You can execute the <code class="filename">.run</code>
file with the <code class="option">--extract-only</code> option to
unpack the tarball.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302712" id=
"id302712"></a><a name="id302714" id="id302714"></a></td>
<td align="left" valign="top">
<p><b>How do I tell if I have my kernel sources installed?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>If you are running on a distro that uses RPM (Red Hat, Mandrake,
SuSE, etc), then you can use <span><strong class=
"command">rpm</strong></span> to tell you. At a shell prompt,
type:</p>
<pre class="screen">
% rpm -qa | grep kernel
</pre>
<p>and look at the output. You should see a package that
corresponds to your kernel (often named something like
kernel-2.6.15-7) and a kernel source package with the same version
(often named something like kernel-devel-2.6.15-7 or
kernel-source-2.4.18-3). If none of the lines seem to correspond to
a source package, then you will probably need to install it. If the
versions listed mismatch (e.g., kernel-2.6.15-7 vs.
kernel-devel-2.6.15-10), then you will need to update the
kernel-devel package to match the installed kernel. If you have
multiple kernels installed, you need to install the kernel-devel
package that corresponds to your <span class=
"emphasis"><em>running</em></span> kernel (or make sure your
installed source package matches the running kernel). You can do
this by looking at the output of <span><strong class=
"command">uname -r</strong></span> and matching versions.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302753" id=
"id302753"></a><a name="id302755" id="id302755"></a></td>
<td align="left" valign="top">
<p><b>Where can I find older driver versions?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Please visit <a href="ftp://download.nvidia.com/XFree86_40/"
target="_top">ftp://download.nvidia.com/XFree86_40/</a></p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302772" id=
"id302772"></a><a name="id302774" id="id302774"></a></td>
<td align="left" valign="top">
<p><b>What is SELinux and how does it interact with the NVIDIA
driver ?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Security-Enhanced Linux (SELinux) is a set of modifications
applied to the Linux kernel and utilities that implement a security
policy architecture. When in use it requires that the security type
on all shared libraries be set to 'shlib_t'. The installer detects
when to set the security type, and sets it on all shared libraries
it installs. The option <code class="option">--force-selinux</code>
passed to the <code class="filename">.run</code> file overrides the
detection of when to set the security type.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302847" id=
"id302847"></a><a name="id302849" id="id302849"></a></td>
<td align="left" valign="top">
<p><b>Why do applications that use DGA graphics fail?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>The NVIDIA driver does not support the graphics component of the
XFree86-DGA (Direct Graphics Access) extension. Applications can
use the XDGASelectInput() function to acquire relative pointer
motion, but graphics-related functions such as XDGASetMode() and
XDGAOpenFramebuffer() will fail.</p>
<p>The graphics component of XFree86-DGA is not supported because
it requires a CPU mapping of framebuffer memory. As graphics cards
ship with increasing quantities of video memory, the NVIDIA X
driver has had to switch to a more dynamic memory mapping scheme
that is incompatible with DGA. Furthermore, DGA does not cooperate
with other graphics rendering libraries such as Xlib and OpenGL
because it accesses GPU resources directly.</p>
<p>NVIDIA recommends that applications use OpenGL or Xlib, rather
than DGA, for graphics rendering. Using rendering libraries other
than DGA will yield better performance and improve interoperability
with other X applications.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302875" id=
"id302875"></a><a name="id302877" id="id302877"></a></td>
<td align="left" valign="top">
<p><b>My kernel log contains messages that are prefixed with "Xid";
what do these messages mean?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>"Xid" messages indicate that a general GPU error occurred, most
often due to the driver misprogramming the GPU or to corruption of
the commands sent to the GPU. These messages provide diagnostic
information that can be used by NVIDIA to aid in debugging reported
problems.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302891" id=
"id302891"></a><a name="id302893" id="id302893"></a></td>
<td align="left" valign="top">
<p><b>On what NVIDIA hardware is the EXT_framebuffer_object OpenGL
extension supported?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>EXT_framebuffer_object is supported on GeForce FX, Quadro FX,
and newer GPUs.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302904" id=
"id302904"></a><a name="id302907" id="id302907"></a></td>
<td align="left" valign="top">
<p><b>I use the Coolbits overclocking interface to adjust my
graphics card's clock frequencies, but the defaults are reset
whenever X is restarted. How do I make my changes
persistent?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>Clock frequency settings are not saved/restored automatically by
default to avoid potential stability and other problems that may be
encountered if the chosen frequency settings differ from the
defaults qualified by the manufacturer. You can use the command
line below in <code class="filename">~/.xinitrc</code> to
automatically apply custom clock frequency settings when the X
server is started:</p>
<pre class="screen">
# nvidia-settings -a GPUOverclockingState=1 -a GPU2DClockFreqs=<GPU>,<MEM> -a GPU3DClockFreqs=<GPU>,<MEM>
</pre>
<p>Here <code class="filename"><GPU></code> and <code class=
"filename"><MEM></code> are the desired GPU and video memory
frequencies (in MHz), respectively.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302947" id=
"id302947"></a><a name="id302950" id="id302950"></a></td>
<td align="left" valign="top">
<p><b>Why is the refresh rate not reported correctly by utilities
that use the XRandR X extension (e.g., the GNOME "Screen Resolution
Preferences" panel, `xrandr -q`, etc)?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>The XRandR X extension is not presently aware of multiple
display devices on a single X screen; it only sees the MetaMode
bounding box, which may contain one or more actual modes. This
means that if multiple MetaModes have the same bounding box, XRandR
will not be able to distinguish between them.</p>
<p>In order to support DynamicTwinView, the NVIDIA X driver must
make each MetaMode appear to be unique to XRandR. Presently, the
NVIDIA X driver accomplishes this by using the refresh rate as a
unique identifier.</p>
<p>You can use `nvidia-settings -q RefreshRate` to query the actual
refresh rate on each display device.</p>
<p>This behavior can be disabled by setting the X configuration
option "DynamicTwinView" to FALSE.</p>
<p>For details, see <a href="chapter-13.html" title=
"Chapter 13. Configuring TwinView">Chapter 13,
<i>Configuring TwinView</i></a>.</p>
</td>
</tr>
<tr class="question">
<td align="left" valign="top"><a name="id302987" id=
"id302987"></a><a name="id302989" id="id302989"></a></td>
<td align="left" valign="top">
<p><b>Why does starting certain applications result in Xlib error
messages indicating extensions like "XFree86-VidModeExtension" or
"SHAPE" are missing?</b></p>
</td>
</tr>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top">
<p>If your X config file has a <code class=
"computeroutput">Module</code> section that does not list the
"extmod" module, some X server extensions may be missing, resulting
in error messages of the form:</p>
<pre class="screen">
Xlib: extension "SHAPE" missing on display ":0.0"
Xlib: extension "XFree86-VidModeExtension" missing on display ":0.0"
Xlib: extension "XFree86-DGA" missing on display ":0.0"
</pre>
<p>You can solve this problem by adding the line below to your X
config file's <code class="computeroutput">Module</code>
section:</p>
<pre class="screen">
Load "extmod"
</pre>
<p></p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href=
"chapter-06-section-02.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href=
"part-01.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href=
"chapter-08.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Manually Editing the
Configuration File </td>
<td width="20%" align="center"><a accesskey="h" href=
"index.html">Home</a></td>
<td width="40%" align="right" valign="top">
Chapter 8. Common Problems</td>
</tr>
</table>
</div>
</body>
</html>
distrib
>
Mageia
>
1
>
x86_64
>
media
>
nonfree-updates
>
by-pkgid
>
7c5f85a6dcfdc4e75aab3daa74fdae93
>
files
>
20
