public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: nvidia-guide.xml
Date: Tue, 13 Jul 2010 19:55:51 +0000 (UTC)	[thread overview]
Message-ID: <20100713195552.067E32CE14@corvid.gentoo.org> (raw)

nightmorph    10/07/13 19:55:51

  Modified:             nvidia-guide.xml
  Log:
  update nvidia driver installation instructions, link to xorg-server guide, fix kernel stuff. bug 307481.

Revision  Changes    Path
1.50                 xml/htdocs/doc/en/nvidia-guide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?rev=1.50&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?rev=1.50&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?r1=1.49&r2=1.50

Index: nvidia-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- nvidia-guide.xml	14 May 2010 22:22:26 -0000	1.49
+++ nvidia-guide.xml	13 Jul 2010 19:55:51 -0000	1.50
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v 1.49 2010/05/14 22:22:26 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v 1.50 2010/07/13 19:55:51 nightmorph Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide>
@@ -28,8 +28,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.40</version>
-<date>2010-05-14</date>
+<version>1.41</version>
+<date>2010-07-13</date>
 
 <chapter>
 <title>Introduction</title>
@@ -219,22 +219,22 @@
 </p>
 
 <p>
-First, you'll need to emerge <c>eselect</c> (if you don't already have it). If
-you are using <c>gentoo-sources-2.6.18-r4</c>, your kernel listing might look
+First, you'll need to choose the right kernel source using <c>eselect</c>. If
+you are using <c>gentoo-sources-2.6.34-r1</c>, your kernel listing might look
 something like this:
 </p>
 
 <pre caption="Check your /usr/src/linux symlink">
 # <i>eselect kernel list</i>
 Available kernel symlink targets:
-  [1]   linux-2.6.18-gentoo-r4 *
-  [2]   linux-2.6.20-gentoo-r7
-  [3]   linux-2.6.20-gentoo-r8
+  [1]   linux-2.6.34-gentoo-r1 *
+  [2]   linux-2.6.33-gentoo-r2
+  [3]   linux-2.6.32.9
 <comment>(Verify that the right kernel is marked with an asterisk</comment>
 </pre>
 
 <p>
-In the above output, you'll notice that the <c>linux-2.6.18-gentoo-r4</c> kernel
+In the above output, you'll notice that the <c>linux-2.6.34-gentoo-r1</c> kernel
 is marked with an asterisk (<b>*</b>) to show that it is the symlinked kernel.
 </p>
 
@@ -256,28 +256,29 @@
 <body>
 
 <p>
-Now it's time to install the drivers.
+Now it's time to install the drivers. You can do this by first following the
+<uri link="/doc/en/xorg-config.xml">X Server Configuration HOWTO</uri> and
+setting <c>VIDEO_CARDS="nvidia"</c> in <path>/etc/make.conf</path>. When you
+install the X server, it will then install the right version of
+<c>nvidia-drivers</c> for you.
 </p>
 
-<pre caption="Installing the nVidia drivers">
-# <i>emerge nvidia-drivers</i>
-</pre>
-
 <note>
-The drivers can be installed with the <c>gtk</c> USE flag set. This will install
+The drivers can be installed with the <c>gtk</c> USE flag set in
+<path>/etc/make.conf</path>. This will install
 <c>media-video/nvidia-settings</c>, a handy graphical tool for monitoring and
 configuring several aspects of your nVidia card.
 </note>
 
 <impo>
 Every time you <uri link="/doc/en/kernel-upgrade.xml">compile a new kernel</uri>
-or recompile the current one, you will need to run <c>emerge nvidia-drivers</c>
-to reinstall the nVidia modules. An easier way to keep track of modules
-installed by ebuilds (such as <c>nvidia-drivers</c>) is to install
-<c>sys-kernel/module-rebuild</c>. Once you've installed it, simply run
-<c>module-rebuild populate</c> to populate its database with a list of packages
-to be rebuilt. Once you've finished compiling or recompiling a kernel, just run
-<c>module-rebuild rebuild</c> to rebuild the drivers for your new kernel.
+or recompile the current one, you will need to reinstall the nVidia kernel
+modules. An easy way to keep track of modules installed by ebuilds (such as
+<c>nvidia-drivers</c>) is to install <c>sys-kernel/module-rebuild</c>. Once
+you've installed it, simply run <c>module-rebuild populate</c> to populate its
+database with a list of packages to be rebuilt. Once you've finished compiling
+or recompiling a kernel, just run <c>module-rebuild rebuild</c> to rebuild the
+drivers for your new kernel.
 </impo>
 
 <p>






             reply	other threads:[~2010-07-13 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 19:55 Joshua Saddler (nightmorph) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-12 16:26 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: nvidia-guide.xml Sven Vermeulen (swift)
2010-05-14 22:22 Joshua Saddler (nightmorph)
2009-01-26  8:20 Joshua Saddler (nightmorph)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100713195552.067E32CE14@corvid.gentoo.org \
    --to=nightmorph@gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox