/[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.4 Revision 1.5
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.4 2005/05/23 18:35:47 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.5 2005/05/23 18:40:25 swift 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">
171 171
172<p> 172<p>
173You can also use extra parameters for other genkernel functionality. For 173You can also use extra parameters for other genkernel functionality. For
174example, if you wish to configure some extra kernel options using 174example, if you wish to configure some extra kernel options using
175<c>menuconfig</c> and you wish genkernel to automatically update your grub 175<c>menuconfig</c> and you wish genkernel to automatically update your grub
176bootloader config, then invoke genkernel as follows: 176boot loader configuration, then invoke genkernel as follows:
177</p> 177</p>
178 178
179<pre caption="Invoking genkernel with some common arguments"> 179<pre caption="Invoking genkernel with some common arguments">
180# <i>genkernel --menuconfig --bootloader=grub all</i> 180# <i>genkernel --menuconfig --bootloader=grub all</i>
181</pre> 181</pre>
226# <i>cp arch/i386/boot/bzImage /boot/bzImage-2.6.9-gentoo-r2</i> 226# <i>cp arch/i386/boot/bzImage /boot/bzImage-2.6.9-gentoo-r2</i>
227# <i>cp System.map /boot/System.map-2.6.9-gentoo-r2</i> 227# <i>cp System.map /boot/System.map-2.6.9-gentoo-r2</i>
228</pre> 228</pre>
229 229
230<p> 230<p>
231Finally, you should update your bootloader config, adding an entry for the 231Finally, you should update your boot loader configuration, adding an entry for
232new kernel (don't delete the old one just yet!) and unmount the 232the new kernel (don't delete the old one just yet!) and unmount the
233<path>/boot</path> partition. Again, refer to the 233<path>/boot</path> partition. Again, refer to the
234<uri link="/doc/en/handbook/index.xml">Gentoo Handbook</uri> 234<uri link="/doc/en/handbook/index.xml">Gentoo Handbook</uri>
235for detailed instructions on this procedure. 235for detailed instructions on this procedure.
236</p> 236</p>
237 237
266<section> 266<section>
267<body> 267<body>
268 268
269<p> 269<p>
270Next, close all applications and reboot your system. If you followed the above 270Next, close all applications and reboot your system. If you followed the above
271instructions correctly, the bootloader menu should include an entry for the 271instructions correctly, the boot loader menu should include an entry for the
272new kernel. Select the new kernel and let the system boot. 272new kernel. Select the new kernel and let the system boot.
273</p> 273</p>
274 274
275<p> 275<p>
276Hopefully, your system successfully boots with the new kernel, and you can log 276Hopefully, your system successfully boots with the new kernel, and you can log
278complete. 278complete.
279</p> 279</p>
280 280
281<p> 281<p>
282If you made a mistake and the system fails to boot with the new kernel, reboot 282If you made a mistake and the system fails to boot with the new kernel, reboot
283the system and select the entry from the bootloader that corresponds to the 283the system and select the entry from the boot loader that corresponds to the
284last known working kernel. You can then restart from the <uri link="#install"> 284last known working kernel. You can then restart from the <uri link="#install">
285Configuring, compiling, and installing the new kernel</uri> stage -- making 285Configuring, compiling, and installing the new kernel</uri> stage -- making
286the appropriate changes to correct your mistake. In some cases, you might not 286the appropriate changes to correct your mistake. In some cases, you might not
287even need to reboot to do this (e.g. you missed a driver for an audio device, 287even need to reboot to do this (e.g. you missed a driver for an audio device,
288ethernet adapter, etc.) 288Ethernet adapter, etc.)
289</p> 289</p>
290 290
291</body> 291</body>
292</section> 292</section>
293</chapter> 293</chapter>
304</p> 304</p>
305 305
306<p> 306<p>
307Switching between multiple kernels is as simple as leaving the kernel sources 307Switching between multiple kernels is as simple as leaving the kernel sources
308under <path>/usr/src/</path> and leaving the <path>bzImage</path> binaries on 308under <path>/usr/src/</path> and leaving the <path>bzImage</path> binaries on
309your <path>/boot</path> partition (referenced by entries in your bootloader 309your <path>/boot</path> partition (referenced by entries in your boot loader
310config). Every time you boot up, you will be presented with a choice of which 310configuration). Every time you boot up, you will be presented with a choice of
311kernel to boot into. 311which kernel to boot into.
312</p> 312</p>
313 313
314</body> 314</body>
315</section> 315</section>
316</chapter> 316</chapter>
346</p> 346</p>
347 347
348<p> 348<p>
349Finally, you can mount your <path>/boot</path> partition and remove the 349Finally, you can mount your <path>/boot</path> partition and remove the
350<path>bzImage</path> and <path>System.map</path> files for the kernel(s) 350<path>bzImage</path> and <path>System.map</path> files for the kernel(s)
351you are pruning. You should also edit your bootloader config so that it 351you are pruning. You should also edit your boot loader configuration so that it
352no longer references such kernel(s). 352no longer references such kernel(s).
353</p> 353</p>
354 354
355</body> 355</body>
356</section> 356</section>
379resulting in the user running into problems because they disabled options that 379resulting in the user running into problems because they disabled options that
380they really didn't want to. 380they really didn't want to.
381</p> 381</p>
382 382
383<p> 383<p>
384To reuse your old config, you simply need to copy it over and then run <c>make 384To reuse your old <path>.config</path>, you simply need to copy it over and then
385oldconfig</c>. In the following example, we take the config from 385run <c>make oldconfig</c>. In the following example, we take the configuration
386<c>gentoo-sources-2.6.9-r1</c> and import it into 386from <c>gentoo-sources-2.6.9-r1</c> and import it into
387<c>gentoo-sources-2.6.9-r2</c>. 387<c>gentoo-sources-2.6.9-r2</c>.
388</p> 388</p>
389 389
390<pre caption="Reusing your old config"> 390<pre caption="Reusing your old config">
391# <i>cd /usr/src/linux-2.6.9-gentoo-r2</i> 391# <i>cd /usr/src/linux-2.6.9-gentoo-r2</i>

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20