neysx 06/01/08 15:16:15 Modified: xml/htdocs/doc/en kernel-upgrade.xml Log: #118060 add a blurb about module-rebuild
Revision Changes Path 1.13 +25 -14 xml/htdocs/doc/en/kernel-upgrade.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.13&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.13&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml.diff?r1=1.12&r2=1.13&cvsroot=gentoo Index: kernel-upgrade.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- kernel-upgrade.xml 1 Jan 2006 11:51:43 -0000 1.12 +++ kernel-upgrade.xml 8 Jan 2006 15:16:15 -0000 1.13 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.12 2006/01/01 11:51:43 neysx Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.13 2006/01/08 15:16:15 neysx Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/kernel-upgrade.xml"> @@ -17,8 +17,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>0.1.8</version> -<date>2005-10-11</date> +<version>0.2</version> +<date>2006-01-06</date> <chapter> <title>Introduction</title> @@ -258,20 +258,31 @@ <p> If you use any kernel modules that are not included in the kernel source tree -but are provided elsewhere in portage (e.g. NVIDIA or ATI graphics drivers), -then you must reinstall these after upgrading the kernel. This is as simple as -re-merging the packages involved. For more information, refer to the chapter on -<e>Configuring the Kernel</e> in the <uri -link="/doc/en/handbook/index.xml">Gentoo Handbook</uri>. -To ensure these packages will build against the source tree at -<path>/usr/src/linux</path>, first uninstall the packages, then re-emerge them. -If old sources for these packages are kept by portage, this uninstall/re-emerge -procedure will make sure that they are rebuilt to work with the new kernel. +but are provided elsewhere in Portage (e.g. ALSA drivers and NVIDIA or ATI +graphics drivers), then you must reinstall these after upgrading the kernel. +This is as simple as re-merging the packages involved. For more information, +refer to the chapter on <e>Configuring the Kernel</e> in the <uri +link="/doc/en/handbook/">Gentoo Handbook</uri>. To ensure these +packages will build against the source tree at <path>/usr/src/linux</path>, +first uninstall the packages, then re-emerge them. If old sources for these +packages are kept by portage, this uninstall/re-emerge procedure will make sure +that they are rebuilt to work with the new kernel. </p> <p> We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which -rebuilds all the kernel modules you have installed using separate ebuilds. +rebuilds all the kernel modules you have installed using separate ebuilds (for +the <b>currently running</b> kernel, not necessarily the one in +<path>/usr/src/linux</path>). Its use is straightforward. After emerging it, +simply run <c>module-rebuild populate</c> to populate the database with a list +of packages that will need to be rebuilt after upgrading the kernel. Once you +have finished upgrading or recompiling your kernel, run <c>module-rebuild +rebuild</c> to rebuild the drivers for your new kernel before you reboot. +</p> + +<p> +For more information, run <c>module-rebuild</c> without any options to see a +list of commands that can be passed to the utility. </p> </body> @@ -294,7 +305,7 @@ in to resume whatever you were doing. If this is the case, then the upgrade is complete. </p> - + <p> If you made a mistake and the system fails to boot with the new kernel, reboot the system and select the entry from the boot loader that corresponds to the -- [email protected] mailing list
