/[gentoo]/xml/htdocs/doc/en/nvidia-guide.xml
Gentoo

Contents of /xml/htdocs/doc/en/nvidia-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.11 - (show annotations) (download) (as text)
Fri Feb 25 09:25:33 2005 UTC (9 years, 5 months ago) by swift
Branch: MAIN
Changes since 1.10: +22 -3 lines
File MIME type: application/xml
#83063 - Adding nvidia use flag information

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v 1.10 2004/12/02 17:26:32 swift Exp $ -->
3 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4
5 <guide link="/doc/en/nvidia-guide.xml">
6 <title>Gentoo Linux nVidia Guide</title>
7
8 <author title="Author">
9 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
10 </author>
11
12 <abstract>
13 Many Gentooists have an nVidia chipset on their system. nVidia provides specific
14 Linux drivers to boost the performance of your card. This guide informs you how
15 to install and configure these drivers.
16 </abstract>
17
18 <license/>
19
20 <version>1.8</version>
21 <date>2005-02-25</date>
22
23 <chapter>
24 <title>Configuring your Card</title>
25 <section>
26 <title>Installing the Appropriate Drivers</title>
27 <body>
28
29 <p>
30 The nVidia drivers include kernel modules that must integrate in your current
31 kernel. To accomplish this, your kernel must support the loading of kernel
32 modules. If you used <c>genkernel</c> to configure the kernel for you then
33 you're all set. If not, double check your kernel configuration so that this
34 support is enabled:
35 </p>
36
37 <pre caption="Enabling the Loading of Kernel Modules">
38 Loadable module support ---&gt;
39 [*] Enable loadable module support
40 </pre>
41
42 <p>
43 You also need to enable <e>Memory Type Range Register</e> in your kernel:
44 </p>
45
46 <pre caption="Enabling MTRR">
47 Processor and Features ---&gt;
48 [*] MTRR (Memory Type Range Register) support
49 </pre>
50
51 <p>
52 nVidia's modules and libraries are combined in two packages: <c>nvidia-glx</c>
53 and <c>nvidia-kernel</c>. The former are the X11 GLX libraries while the latter
54 are the kernel modules. Since <c>nvidia-glx</c> depends on <c>nvidia-kernel</c>,
55 installing <c>nvidia-glx</c> is sufficient:
56 </p>
57
58 <pre caption="Installing the nVidia modules">
59 # <i>emerge nvidia-glx</i>
60 </pre>
61
62 <p>
63 Once the installation has finished, run <c>modprobe nvidia</c> to load the
64 kernel module into memory.
65 </p>
66
67 <pre caption="Loading the kernel module">
68 # <i>modprobe nvidia</i>
69 </pre>
70
71 <p>
72 You probably want to have this done each time you boot your system, so edit
73 <path>/etc/modules.autoload.d/kernel-2.6</path> (or <path>kernel-2.4</path>) and
74 add <c>nvidia</c> to it. Don't forget to run <c>modules-update</c> afterwards!
75 </p>
76
77 <pre caption="Running modules-update">
78 # <i>modules-update</i>
79 </pre>
80
81 </body>
82 </section>
83 <section>
84 <title>Configuring the X Server</title>
85 <body>
86
87 <p>
88 Once the appropriate drivers are installed you need to configure your X Server
89 (XFree86 or Xorg) to use the <c>nvidia</c> driver instead of the default
90 <c>nv</c> driver.
91 </p>
92
93 <p>
94 Open <path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) with
95 your favorite editor (such as <c>nano</c> or <c>vim</c>) and go to the
96 <c>Device</c> section. In that section, change the <c>Driver</c> line:
97 </p>
98
99 <pre caption="Changing nv to nvidia in the X Server configuration">
100 Section "Device"
101 Identifier "nVidia Inc. GeForce2"
102 <i>Driver "nvidia"</i>
103 VideoRam 65536
104 EndSection
105 </pre>
106
107 <p>
108 Then go to the <c>Module</c> section and make sure the <c>glx</c> module gets
109 loaded while the <c>dri</c> module doesn't:
110 </p>
111
112 <pre caption="Updating the Module section">
113 Section "Module"
114 <comment>(...)</comment>
115 <i># Load "dri"
116 Load "glx"</i>
117 <comment>(...)</comment>
118 EndSection
119 </pre>
120
121 <p>
122 Run <c>opengl-update</c> so that the X Server uses the nVidia GLX libraries:
123 </p>
124
125 <pre caption="Running opengl-update">
126 # <i>opengl-update nvidia</i>
127 </pre>
128
129 </body>
130 </section>
131 <section>
132 <title>Adding your Users to the video Group</title>
133 <body>
134
135 <p>
136 You have to add your user to the <c>video</c> group so he has access to the
137 nvidia device files:
138 </p>
139
140 <pre caption="Adding your user to the video group">
141 # <i>gpasswd -a youruser video</i>
142 </pre>
143
144 <p>
145 This might not be totally necessary if you aren't used <c>udev</c> but it
146 doesn't hurt either and makes your system future-proof :)
147 </p>
148
149 </body>
150 </section>
151 <section>
152 <title>Testing your Card</title>
153 <body>
154
155 <p>
156 To test your nVidia card, fire up X and run the <c>glxinfo | grep direct</c>
157 command. It should say that direct rendering is activated:
158 </p>
159
160 <pre caption="Checking the direct rendering status">
161 $ <i>glxinfo | grep direct</i>
162 direct rendering: Yes
163 </pre>
164
165 <p>
166 To monitor your FPS, run <c>glxgears</c>.
167 </p>
168
169 </body>
170 </section>
171 <section>
172 <title>Enabling nvidia Support</title>
173 <body>
174
175 <p>
176 Some tools, such as <c>mplayer</c> and <c>xine-lib</c>, use a local USE flag
177 called "nvidia" which enables XvMCNVIDIA support, useful when watching high
178 resolution movies. Add in "nvidia" in your USE variable in
179 <path>/etc/make.conf</path> or add it as USE flag to <c>media-video/mplayer</c>
180 and/or <c>media-libs/xine-lib</c> in <path>/etc/portage/package.use</path>.
181 </p>
182
183 <p>
184 Then, run <c>emerge -uD --newuse world</c> to rebuild the applications that
185 benefit from the USE flag change.
186 </p>
187
188 </body>
189 </section>
190 </chapter>
191
192 <chapter>
193 <title>Troubleshooting</title>
194 <section>
195 <title>Getting 2D to work on machines with 4Gb or more memory</title>
196 <body>
197
198 <p>
199 If you are having troubles with the nVidia 2D acceleration it is likely that you
200 are unable to set up a write-combining range with MTRR. To verify, check the
201 contents of <path>/proc/mtrr</path>:
202 </p>
203
204 <pre caption="Checking if you have write-combining enabled">
205 # <i>cat /proc/mtrr</i>
206 </pre>
207
208 <p>
209 Every line should contain "write-back" or "write-combining". If you see a line
210 with "uncachable" in it you will need to change a BIOS setting to fix this.
211 </p>
212
213 <p>
214 Reboot and enter the BIOS, then find the MTRR settings (probably under "CPU
215 Settings"). Change the setting from "continuous" to "discrete" and boot back
216 into Linux. You will now find out that there is no "uncachable" entry anymore
217 and 2D acceleration now works without any glitches.
218 </p>
219
220 </body>
221 </section>
222 <section>
223 <title>I receive warnings about unsupported 4K stack sizes</title>
224 <body>
225
226 <p>
227 <c>nvidia-kernel</c> packages older than 1.0.6106 only support kernels using an
228 8K stack size. More recent kernels (2.6.6 and higher) have support for 4K stack
229 size's as well. Do not select 4K stack size in your kernel configuration if you
230 are using such an <c>nvidia-kernel</c> package. You can find this option in the
231 section <c>Kernel Hacking</c>.
232 </p>
233
234 </body>
235 </section>
236 </chapter>
237
238 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20