/[gentoo]/xml/htdocs/doc/en/kernel-upgrade.xml
Gentoo

Diff of /xml/htdocs/doc/en/kernel-upgrade.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.12 Revision 1.13
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.12 2006/01/01 11:51:43 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.13 2006/01/08 15:16:15 neysx Exp $ -->
3 3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5<guide link="/doc/en/kernel-upgrade.xml"> 5<guide link="/doc/en/kernel-upgrade.xml">
6<title>Gentoo Linux Kernel Upgrade Guide</title> 6<title>Gentoo Linux Kernel Upgrade Guide</title>
7<author title="Author"> 7<author title="Author">
15 15
16<!-- The content of this document is licensed under the CC-BY-SA license --> 16<!-- The content of this document is licensed under the CC-BY-SA license -->
17<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 17<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
18<license/> 18<license/>
19 19
20<version>0.1.8</version> 20<version>0.2</version>
21<date>2005-10-11</date> 21<date>2006-01-06</date>
22 22
23<chapter> 23<chapter>
24<title>Introduction</title> 24<title>Introduction</title>
25<section> 25<section>
26<body> 26<body>
256<section> 256<section>
257<body> 257<body>
258 258
259<p> 259<p>
260If you use any kernel modules that are not included in the kernel source tree 260If you use any kernel modules that are not included in the kernel source tree
261but are provided elsewhere in portage (e.g. NVIDIA or ATI graphics drivers), 261but are provided elsewhere in Portage (e.g. ALSA drivers and NVIDIA or ATI
262then you must reinstall these after upgrading the kernel. This is as simple as 262graphics drivers), then you must reinstall these after upgrading the kernel.
263re-merging the packages involved. For more information, refer to the chapter on 263This is as simple as re-merging the packages involved. For more information,
264<e>Configuring the Kernel</e> in the <uri 264refer to the chapter on <e>Configuring the Kernel</e> in the <uri
265link="/doc/en/handbook/index.xml">Gentoo Handbook</uri>. 265link="/doc/en/handbook/">Gentoo Handbook</uri>. To ensure these
266To ensure these packages will build against the source tree at 266packages will build against the source tree at <path>/usr/src/linux</path>,
267<path>/usr/src/linux</path>, first uninstall the packages, then re-emerge them. 267first uninstall the packages, then re-emerge them. If old sources for these
268If old sources for these packages are kept by portage, this uninstall/re-emerge 268packages are kept by portage, this uninstall/re-emerge procedure will make sure
269procedure will make sure that they are rebuilt to work with the new kernel. 269that they are rebuilt to work with the new kernel.
270</p> 270</p>
271 271
272<p> 272<p>
273We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which 273We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which
274rebuilds all the kernel modules you have installed using separate ebuilds. 274rebuilds all the kernel modules you have installed using separate ebuilds (for
275the <b>currently running</b> kernel, not necessarily the one in
276<path>/usr/src/linux</path>). Its use is straightforward. After emerging it,
277simply run <c>module-rebuild populate</c> to populate the database with a list
278of packages that will need to be rebuilt after upgrading the kernel. Once you
279have finished upgrading or recompiling your kernel, run <c>module-rebuild
280rebuild</c> to rebuild the drivers for your new kernel before you reboot.
281</p>
282
283<p>
284For more information, run <c>module-rebuild</c> without any options to see a
285list of commands that can be passed to the utility.
275</p> 286</p>
276 287
277</body> 288</body>
278</section> 289</section>
279</chapter> 290</chapter>
292<p> 303<p>
293Hopefully, your system successfully boots with the new kernel, and you can log 304Hopefully, your system successfully boots with the new kernel, and you can log
294in to resume whatever you were doing. If this is the case, then the upgrade is 305in to resume whatever you were doing. If this is the case, then the upgrade is
295complete. 306complete.
296</p> 307</p>
297 308
298<p> 309<p>
299If you made a mistake and the system fails to boot with the new kernel, reboot 310If you made a mistake and the system fails to boot with the new kernel, reboot
300the system and select the entry from the boot loader that corresponds to the 311the system and select the entry from the boot loader that corresponds to the
301last known working kernel. You can then restart from the <uri link="#install"> 312last known working kernel. You can then restart from the <uri link="#install">
302Configuring, compiling, and installing the new kernel</uri> stage -- making 313Configuring, compiling, and installing the new kernel</uri> stage -- making

Legend:
Removed from v.1.12  
changed lines
  Added in v.1.13

  ViewVC Help
Powered by ViewVC 1.1.20