Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 95411 Details for
Bug 140316
update to nvidia-guide (http://www.gentoo.org/doc/en/nvidia-guide.xml)
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
nvidia-guide.xml.diff
nvidia.diff (text/plain), 6.92 KB, created by
Chris Gianelloni (RETIRED)
on 2006-08-29 12:53:59 UTC
(
hide
)
Description:
nvidia-guide.xml.diff
Filename:
MIME Type:
Creator:
Chris Gianelloni (RETIRED)
Created:
2006-08-29 12:53:59 UTC
Size:
6.92 KB
patch
obsolete
>Index: nvidia-guide.xml >=================================================================== >RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v >retrieving revision 1.30 >diff -u -b -B -r1.30 nvidia-guide.xml >--- nvidia-guide.xml 26 Jul 2006 09:50:06 -0000 1.30 >+++ nvidia-guide.xml 29 Aug 2006 19:45:20 -0000 >@@ -14,6 +14,9 @@ > <author title="Editor"> > <mail link="nightmorph@gentoo.org">Joshua Saddler</mail> > </author> >+<author title="Editor"> >+ <mail link="wolf31o2@gentoo.org">Chris Gianelloni</mail> >+</author> > > <abstract> > Many Gentooists have an nVidia chipset on their system. nVidia provides specific >@@ -25,8 +28,8 @@ > <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> > <license/> > >-<version>1.26</version> >-<date>2006-07-25</date> >+<version>1.27</version> >+<date>2006-08-29</date> > > <chapter> > <title>Introduction</title> >@@ -35,8 +38,11 @@ > > <p> > nVidia release their own Linux drivers which provide good performance and full >-3D acceleration. The driver releases are split up into two parts: >-<c>nvidia-kernel</c> and <c>nvidia-glx</c>. >+3D acceleration. There are two sets of drivers in portage. The first set is an >+older set and split into two parts: <c>nvidia-kernel</c> and <c>nvidia-glx</c>. >+The second set is newer, and is split into <c>nvidia-drivers</c> and >+<c>nvidia-legacy-drivers</c>. If you are installing for the first time, you >+should use the newer set. > </p> > > <p> >@@ -52,6 +58,18 @@ > uses the <c>nvidia-kernel</c> kernel driver to interface with the hardware. > </p> > >+<p> >+The newer drivers have the functionality of both nvidia-kernel and nvidia-glx in >+a single unified ebuild, much like how nVidia themselves ship the drivers. >+</p> >+ >+<note> >+Both nvidia-kernel and nvidia-glx are deprecated, and will be removed from the >+portage tree in the future in favor of nvidia-drivers and nvidia-legacy-drivers. >+If you use nvidia-kernel and nvidia-glx, then you should migrate to the newer >+packages. >+</note> >+ > </body> > </section> > </chapter> >@@ -85,8 +103,12 @@ > </pre> > > <p> >-Also, you will have to add <c>agpgart</c> support to your kernel, either >-compiled in or as a module: >+Also, you can optionally enable <c>agpgart</c> support to your kernel, either >+compiled in or as a module. If you do not use the in-kernel agpgart, then the >+drivers will use their own agpgart implementation, called NvAGP. On certain >+systems, this performs better than the in-kernel agpgart, and on others, it >+performs worse. You will need to evaluate this on your own system to get the >+best performance. If you are unsure what to do, use the in-kernel agpgart: > </p> > > <pre caption="Enabling agpgart"> >@@ -126,12 +148,13 @@ > > <p> > Then, under "VESA driver type" select either <c>vesafb</c> or >-<c>vesafb-tng</c>: >+<c>vesafb-tng</c>. If you are using an AMD64 processor, you should select vesafb >+rather than vesafb-tng: > </p> > > <pre caption="Select framebuffer type"> >-( ) vesafb >-(X) vesafb-tng >+(X) vesafb >+( ) vesafb-tng > </pre> > > <p> >@@ -148,13 +171,8 @@ > <body> > > <p> >-nVidia's modules and libraries are combined in two packages: <c>nvidia-glx</c> >-and <c>nvidia-kernel</c>. The former are the X11 GLX libraries while the latter >-are the kernel modules. >-</p> >- >-<p> >-The nvidia-kernel ebuild auto discovers your kernel version based on the >+The nvidia-kernel, nvidia-drivers, and nvidia-legacy drivers ebuilds >+automatically discover your kernel version based on the > <path>/usr/src/linux</path> symlink. Please ensure that you have this symlink > pointing to the correct sources and that your kernel is correctly configured. > Please refer to the Configuring the Kernel section of the <uri >@@ -202,8 +220,7 @@ > <note> > Unfortunately, certain legacy video cards are not supported by the newer > versions of <c>nvidia-glx</c> and <c>nvidia-kernel</c>. nVidia provides a <uri >-link="http://www.nvidia.com/object/IO_18897.html">list of supported cards</uri>. >-Please check the list before installing the drivers. >+link="http://www.nvidia.com/object/IO_18897.html">list of supported cards</uri>. Please check the list before installing the drivers. > </note> > > <p> >@@ -231,15 +248,10 @@ > </pre> > > <p> >-If you own one of these cards, you will have to mask the newer versions of the >-nVidia drivers, and install an older version: >+If your card is listed in the legacy list, then you will be required to install >+the <c>nvidia-legacy-drivers</c> package to get 3D support. > </p> > >-<pre caption="Masking newer drivers"> >-# <i>echo ">media-video/nvidia-kernel-1.0.6629-r5" >> /etc/portage/package.mask</i> >-# <i>echo ">media-video/nvidia-glx-1.0.6629-r7" >> /etc/portage/package.mask</i> >-</pre> >- > </body> > </section> > <section> >@@ -247,12 +259,20 @@ > <body> > > <p> >-Now it's time to install <c>nvidia-kernel</c> and <c>nvidia-glx</c>. Since >-<c>nvidia-glx</c> depends on <c>nvidia-kernel</c>, installing <c>nvidia-glx</c> >-is sufficient. >+Now it's time to install the drivers. The newer drivers are unified, so you will >+only need to install a single package. The older drivers are split, so it will >+require two packages to be installed. Since <c>nvidia-glx</c> depends on >+<c>nvidia-kernel</c>, installing <c>nvidia-glx</c> is sufficient. > </p> > >-<pre caption="Installing the nVidia modules"> >+<pre caption="Installing the nVidia drivers"> >+(If you have a card not listed in the legacy list above) >+# <i>emerge nvidia-drivers</i> >+(If your card is listed in the legacy list) >+# <i>emerge nvidia-legacy-drivers</i> >+</pre> >+ >+<pre caption="Installing the nVidia drivers (alternate)"> > # <i>emerge nvidia-glx</i> > </pre> > >@@ -261,15 +281,19 @@ > kernel</uri> or recompile the current one, you have to run <c>emerge > nvidia-kernel</c> to reinstall the nVidia modules. <c>nvidia-glx</c> is > unaffected by a kernel change and doesn't even need to be rebuilt when you >-recompile/upgrade X. >+recompile/upgrade X. If you are using the newer drivers, then you will need to >+run <c>emerge nvidia-drivers</c> or <c>emerge nvidia-legacy-drivers</c> to >+reinstall the nVidia modules. > </impo> > > <p> > Once the installation has finished, run <c>modprobe nvidia</c> to load the >-kernel module into memory. >+kernel module into memory. If this is an upgrade, you should remove the >+previous module first. > </p> > > <pre caption="Loading the kernel module"> >+# <i>lsmod | grep nvidia && rmmod nvidia</i> > # <i>modprobe nvidia</i> > </pre> > >@@ -299,8 +323,7 @@ > > <p> > Once the appropriate drivers are installed you need to configure your X Server >-(XFree86 or Xorg) to use the <c>nvidia</c> driver instead of the default >-<c>nv</c> driver. >+to use the <c>nvidia</c> driver instead of the default <c>nv</c> driver. > </p> > > <p> >@@ -532,7 +555,8 @@ > the proper device nodes, so you won't need to run <c>NVmakedevices.sh</c>. > Instead, the X driver itself will create your <path>/dev/nvidia*</path> files > when you start X. However, this will require you to use a recent kernel (2.6.14 >-and greater). >+and greater). This is also true for all versions of <c>nvidia-drivers</c> and >+<c>nvidia-legacy-drivers</c>. > </note> > > </body>
<b>You cannot view the attachment while viewing its details because your browser does not support IFRAMEs. <a href="attachment.cgi?id=95411">View the attachment on a separate page</a>.</b>
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 140316
:
95267
| 95411
