1 |
nightmorph 06/10/24 02:24:14 |
2 |
|
3 |
Modified: nvidia-guide.xml |
4 |
Log: |
5 |
Thorough overhaul of nVidia guide, as nvidia-kernel & glx have been removed from portage awhile ago; several functionality changes have taken place within the nvidia/legacy packages that prevent some errors from occuring, and we don't support the out-of-portage versions anyway. |
6 |
|
7 |
Revision Changes Path |
8 |
1.33 xml/htdocs/doc/en/nvidia-guide.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?rev=1.33&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?rev=1.33&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?r1=1.32&r2=1.33 |
13 |
|
14 |
Index: nvidia-guide.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v |
17 |
retrieving revision 1.32 |
18 |
retrieving revision 1.33 |
19 |
diff -u -r1.32 -r1.33 |
20 |
--- nvidia-guide.xml 2 Sep 2006 10:19:23 -0000 1.32 |
21 |
+++ nvidia-guide.xml 24 Oct 2006 02:24:14 -0000 1.33 |
22 |
@@ -1,5 +1,5 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v 1.32 2006/09/02 10:19:23 nightmorph Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v 1.33 2006/10/24 02:24:14 nightmorph Exp $ --> |
26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
27 |
|
28 |
<guide link="/doc/en/nvidia-guide.xml"> |
29 |
@@ -28,8 +28,8 @@ |
30 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
31 |
<license/> |
32 |
|
33 |
-<version>1.27</version> |
34 |
-<date>2006-09-02</date> |
35 |
+<version>1.28</version> |
36 |
+<date>2006-10-23</date> |
37 |
|
38 |
<chapter> |
39 |
<title>Introduction</title> |
40 |
@@ -38,37 +38,18 @@ |
41 |
|
42 |
<p> |
43 |
nVidia release their own Linux drivers which provide good performance and full |
44 |
-3D acceleration. There are two sets of drivers in portage. The first set is an |
45 |
-older set and split into two parts: <c>nvidia-kernel</c> and <c>nvidia-glx</c>. |
46 |
-The second set is newer, and is split into <c>nvidia-drivers</c> and |
47 |
-<c>nvidia-legacy-drivers</c>. If you are installing for the first time, you |
48 |
-should use the newer set. |
49 |
-</p> |
50 |
- |
51 |
-<p> |
52 |
-<c>nvidia-kernel</c> is a kernel driver which handles the low-level |
53 |
-communication with your video hardware. This is simply a kernel module, named |
54 |
-<c>nvidia</c>, which installs against your kernel sources and needs to be |
55 |
-loaded whenever you want to use the nvidia drivers. |
56 |
-</p> |
57 |
- |
58 |
-<p> |
59 |
-As well as the kernel driver, you need to install the X11 GLX layer |
60 |
-(<c>nvidia-glx</c>). This is used by X to render graphics, which internally |
61 |
-uses the <c>nvidia-kernel</c> kernel driver to interface with the hardware. |
62 |
-</p> |
63 |
- |
64 |
-<p> |
65 |
-The newer drivers have the functionality of both <c>nvidia-kernel</c> and |
66 |
-<c>nvidia-glx</c> in a single unified ebuild, much like how nVidia themselves |
67 |
-ship the drivers. |
68 |
+3D acceleration. There are two drivers in Portage. <c>nvidia-drivers</c> is for |
69 |
+newer nVidia graphics cards, while <c>nvidia-legacy-drivers</c> supports older |
70 |
+cards. |
71 |
</p> |
72 |
|
73 |
<note> |
74 |
-Both <c>nvidia-kernel</c> and <c>nvidia-glx</c> are deprecated, and will be |
75 |
-removed from the Portage tree in the future in favor of <c>nvidia-drivers</c> |
76 |
-and <c>nvidia-legacy-drivers</c>. If you use <c>nvidia-kernel</c> and |
77 |
-<c>nvidia-glx</c>, then you should migrate to the newer packages. |
78 |
+Previously, Gentoo provided separate ebuilds for the nVidia kernel module |
79 |
+(<c>nvidia-kernel</c>) and the X11 GLX libraries (<c>nvidia-glx</c>). These |
80 |
+ebuilds have since been removed from the Portage tree in favor of |
81 |
+<c>nvidia-drivers</c> and <c>nvidia-legacy-drivers</c>. If you use |
82 |
+<c>nvidia-kernel</c> and <c>nvidia-glx</c>, then you should migrate to the |
83 |
+newer packages. |
84 |
</note> |
85 |
|
86 |
</body> |
87 |
@@ -103,14 +84,13 @@ |
88 |
[*] MTRR (Memory Type Range Register) support |
89 |
</pre> |
90 |
|
91 |
-<p> |
92 |
-Also, you can optionally enable <c>agpgart</c> support to your kernel, either |
93 |
-compiled in or as a module. If you do not use the in-kernel agpgart, then the |
94 |
-drivers will use their own <c>agpgart</c> implementation, called <c>NvAGP</c>. |
95 |
-On certain systems, this performs better than the in-kernel agpgart, and on |
96 |
-others, it performs worse. You will need to evaluate this on your own system to |
97 |
-get the best performance. If you are unsure what to do, use the in-kernel |
98 |
-agpgart: |
99 |
+<p> Also, if you have an AGP graphics card, you can optionally enable |
100 |
+<c>agpgart</c> support to your kernel, either compiled in or as a module. If |
101 |
+you do not use the in-kernel agpgart, then the drivers will use their own |
102 |
+<c>agpgart</c> implementation, called <c>NvAGP</c>. On certain systems, this |
103 |
+performs better than the in-kernel agpgart, and on others, it performs worse. |
104 |
+You will need to evaluate this on your own system to get the best performance. |
105 |
+If you are unsure what to do, use the in-kernel agpgart: |
106 |
</p> |
107 |
|
108 |
<pre caption="Enabling agpgart"> |
109 |
@@ -173,11 +153,11 @@ |
110 |
<body> |
111 |
|
112 |
<p> |
113 |
-The <c>nvidia-kernel</c>, <c>nvidia-drivers</c>, and |
114 |
-<c>nvidia-legacy-drivers</c> ebuilds automatically discover your kernel version |
115 |
-based on the <path>/usr/src/linux</path> symlink. Please ensure that you have |
116 |
-this symlink pointing to the correct sources and that your kernel is correctly |
117 |
-configured. Please refer to the Configuring the Kernel section of the <uri |
118 |
+The <c>nvidia-drivers</c> and <c>nvidia-legacy-drivers</c> ebuilds |
119 |
+automatically discover your kernel version based on the |
120 |
+<path>/usr/src/linux</path> symlink. Please ensure that you have this symlink |
121 |
+pointing to the correct sources and that your kernel is correctly configured. |
122 |
+Please refer to the Configuring the Kernel section of the <uri |
123 |
link="/doc/en/handbook/">Installation Handbook</uri> for details on configuring |
124 |
your kernel. |
125 |
</p> |
126 |
@@ -221,9 +201,9 @@ |
127 |
|
128 |
<note> |
129 |
Unfortunately, certain legacy video cards are not supported by the newer |
130 |
-versions of <c>nvidia-drivers</c>, <c>nvidia-glx</c> and <c>nvidia-kernel</c>. |
131 |
-nVidia provides a <uri link="http://www.nvidia.com/object/IO_18897.html">list |
132 |
-of supported cards</uri>. Please check the list before installing the drivers. |
133 |
+versions of <c>nvidia-drivers</c>. nVidia provides a <uri |
134 |
+link="http://www.nvidia.com/object/IO_18897.html">list of supported |
135 |
+cards</uri>. Please check the list before installing the drivers. |
136 |
</note> |
137 |
|
138 |
<p> |
139 |
@@ -262,10 +242,7 @@ |
140 |
<body> |
141 |
|
142 |
<p> |
143 |
-Now it's time to install the drivers. The newer drivers are unified, so you |
144 |
-will only need to install a single package. The older drivers are split, so it |
145 |
-will require two packages to be installed. Since <c>nvidia-glx</c> depends on |
146 |
-<c>nvidia-kernel</c>, installing <c>nvidia-glx</c> is sufficient. |
147 |
+Now it's time to install the drivers. |
148 |
</p> |
149 |
|
150 |
<pre caption="Installing the nVidia drivers"> |
151 |
@@ -275,18 +252,11 @@ |
152 |
# <i>emerge nvidia-legacy-drivers</i> |
153 |
</pre> |
154 |
|
155 |
-<pre caption="Installing the nVidia drivers (deprecated method)"> |
156 |
-# <i>emerge nvidia-glx</i> |
157 |
-</pre> |
158 |
- |
159 |
<impo> |
160 |
Every time you <uri link="/doc/en/kernel-upgrade.xml">compile a new |
161 |
-kernel</uri> or recompile the current one, you have to run <c>emerge |
162 |
-nvidia-kernel</c> to reinstall the nVidia modules. <c>nvidia-glx</c> is |
163 |
-unaffected by a kernel change and doesn't even need to be rebuilt when you |
164 |
-recompile/upgrade X. If you are using the newer drivers, then you will need to |
165 |
-run <c>emerge nvidia-drivers</c> or <c>emerge nvidia-legacy-drivers</c> to |
166 |
-reinstall the nVidia modules. |
167 |
+kernel</uri> or recompile the current one, you will need to run <c>emerge |
168 |
+nvidia-drivers</c> or <c>emerge nvidia-legacy-drivers</c> to reinstall the |
169 |
+nVidia modules. |
170 |
</impo> |
171 |
|
172 |
<p> |
173 |
@@ -330,9 +300,8 @@ |
174 |
</p> |
175 |
|
176 |
<p> |
177 |
-Open <path>/etc/X11/xorg.conf</path> (or <path>/etc/X11/XF86Config</path> if you |
178 |
-still use the older configuration file location) with your favorite editor |
179 |
-(such as <c>nano</c> or <c>vim</c>) and go to the <c>Device</c> section. In that |
180 |
+Open <path>/etc/X11/xorg.conf</path> with your favorite editor (such as |
181 |
+<c>nano</c> or <c>vim</c>) and go to the <c>Device</c> section. In that |
182 |
section, change the <c>Driver</c> line: |
183 |
</p> |
184 |
|
185 |
@@ -361,7 +330,7 @@ |
186 |
<p> |
187 |
Next, in section <c>Screen</c>, make sure that either the <c>DefaultDepth</c> |
188 |
directive is set to 16 or 24, or that you only have <c>Display</c> subsections |
189 |
-with <c>Depth</c> settings of 16 or 24. Without it, the nvidia-glx extensions |
190 |
+with <c>Depth</c> settings of 16 or 24. Without it, the nVidia GLX extensions |
191 |
will not start. |
192 |
</p> |
193 |
|
194 |
@@ -399,7 +368,7 @@ |
195 |
|
196 |
<p> |
197 |
This might not be totally necessary if you aren't using <c>udev</c> but it |
198 |
-doesn't hurt either and makes your system future-proof :) |
199 |
+doesn't hurt either and makes your system future-proof. |
200 |
</p> |
201 |
|
202 |
</body> |
203 |
@@ -489,20 +458,6 @@ |
204 |
</body> |
205 |
</section> |
206 |
<section> |
207 |
-<title>I receive warnings about unsupported 4K stack sizes</title> |
208 |
-<body> |
209 |
- |
210 |
-<p> |
211 |
-<c>nvidia-kernel</c> packages older than 1.0.6106 only support kernels using an |
212 |
-8K stack size. More recent kernels (2.6.6 and higher) have support for 4K stack |
213 |
-size's as well. Do not select 4K stack size in your kernel configuration if |
214 |
-you are using such an <c>nvidia-kernel</c> package. You can find this option in |
215 |
-the section <c>Kernel Hacking</c>. |
216 |
-</p> |
217 |
- |
218 |
-</body> |
219 |
-</section> |
220 |
-<section> |
221 |
<title> |
222 |
When I attempt to load the kernel module I receive a "no such device" |
223 |
</title> |
224 |
@@ -521,50 +476,6 @@ |
225 |
|
226 |
</body> |
227 |
</section> |
228 |
-<section> |
229 |
-<title> |
230 |
- I get "no screens found" and the logs state "Failed to initialize the NVIDIA |
231 |
- kernel module!" |
232 |
-</title> |
233 |
-<body> |
234 |
- |
235 |
-<p> |
236 |
-You're most likely missing the <path>/dev/nvidia*</path> device files. Create |
237 |
-them using <c>NVmakedevices.sh</c>: |
238 |
-</p> |
239 |
- |
240 |
-<pre caption="Creating the nvidia device nodes"> |
241 |
-# <i>/sbin/NVmakedevices.sh</i> |
242 |
-</pre> |
243 |
- |
244 |
-<p> |
245 |
-If your <path>/dev/nvidia*</path> devices are still missing every time you |
246 |
-reboot, then it is most likely because udev is not automatically creating the |
247 |
-proper device nodes. You can fix this by re-running <c>NVmakedevices.sh</c>, |
248 |
-and then editing <path>/etc/conf.d/rc</path> as shown: |
249 |
-</p> |
250 |
- |
251 |
-<pre caption="Editing /etc/conf.d/rc"> |
252 |
-RC_DEVICE_TARBALL="yes" |
253 |
-</pre> |
254 |
- |
255 |
-<p> |
256 |
-This will preserve your <path>/dev/nvidia*</path> nodes even if you reboot. |
257 |
-</p> |
258 |
- |
259 |
-<note> |
260 |
-Alternatively, you might try emerging the latest <c>nvidia-kernel</c> and |
261 |
-<c>nvidia-glx</c> from the 8xxx series. At the time of this writing, both are |
262 |
-still marked ~arch. These drivers no longer rely on hotplug or udev to create |
263 |
-the proper device nodes, so you won't need to run <c>NVmakedevices.sh</c>. |
264 |
-Instead, the X driver itself will create your <path>/dev/nvidia*</path> files |
265 |
-when you start X. However, this will require you to use a recent kernel (2.6.14 |
266 |
-and greater). This is also true for all versions of <c>nvidia-drivers</c> and |
267 |
-<c>nvidia-legacy-drivers</c>. |
268 |
-</note> |
269 |
- |
270 |
-</body> |
271 |
-</section> |
272 |
</chapter> |
273 |
|
274 |
<chapter> |
275 |
@@ -584,8 +495,6 @@ |
276 |
$ <i>less /usr/share/doc/nvidia-drivers-*/README.gz</i> |
277 |
<comment>(for nvidia-legacy-drivers)</comment> |
278 |
$ <i>less /usr/share/doc/nvidia-legacy-drivers-*/README.gz</i> |
279 |
-<comment>(for nvidia-glx)</comment> |
280 |
-$ <i>less /usr/share/doc/nvidia-glx-*/README.txt.gz</i> |
281 |
</pre> |
282 |
|
283 |
</body> |
284 |
|
285 |
|
286 |
|
287 |
-- |
288 |
gentoo-doc-cvs@g.o mailing list |