|
Lines 17-24
Link Here
|
| 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.1.9</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> |
|
Lines 258-277
Link Here
|
| 258 |
|
258 |
|
| 259 |
<p> |
259 |
<p> |
| 260 |
If you use any kernel modules that are not included in the kernel source tree |
260 |
If you use any kernel modules that are not included in the kernel source tree |
| 261 |
but are provided elsewhere in portage (e.g. NVIDIA or ATI graphics drivers), |
261 |
but are provided elsewhere in Portage (e.g. ALSA drivers and NVIDIA or ATI |
| 262 |
then you must reinstall these after upgrading the kernel. This is as simple as |
262 |
graphics drivers), then you must reinstall these after upgrading the kernel. |
| 263 |
re-merging the packages involved. For more information, refer to the chapter on |
263 |
This is as simple as re-merging the packages involved. For more information, |
| 264 |
<e>Configuring the Kernel</e> in the <uri |
264 |
refer to the chapter on <e>Configuring the Kernel</e> in the <uri |
| 265 |
link="/doc/en/handbook/index.xml">Gentoo Handbook</uri>. |
265 |
link="/doc/en/handbook/index.xml">Gentoo Handbook</uri>. To ensure these |
| 266 |
To ensure these packages will build against the source tree at |
266 |
packages 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. |
267 |
first uninstall the packages, then re-emerge them. If old sources for these |
| 268 |
If old sources for these packages are kept by portage, this uninstall/re-emerge |
268 |
packages are kept by portage, this uninstall/re-emerge procedure will make sure |
| 269 |
procedure will make sure that they are rebuilt to work with the new kernel. |
269 |
that they are rebuilt to work with the new kernel. |
| 270 |
</p> |
270 |
</p> |
| 271 |
|
271 |
|
| 272 |
<p> |
272 |
<p> |
| 273 |
We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which |
273 |
We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which |
| 274 |
rebuilds all the kernel modules you have installed using separate ebuilds. |
274 |
rebuilds all the kernel modules you have installed using separate ebuilds (for |
|
|
275 |
the <b>currently running</b> kernel, not necessarily the one in |
| 276 |
<path>/usr/src/linux</path>). Its use is straightforward. After emerging it, |
| 277 |
simply run <c>module-rebuild populate</c> to populate the database with a list |
| 278 |
of packages that will need to be rebuilt after upgrading the kernel. Once you |
| 279 |
have finished upgrading or recompiling your kernel, run <c>module-rebuild |
| 280 |
rebuild</c> to rebuild the drivers for your new kernel before you reboot. |
| 281 |
</p> |
| 282 |
|
| 283 |
<p> |
| 284 |
For more information, run <c>module-rebuild</c> without any options to see a |
| 285 |
list of commands that can be passed to the utility. |
| 275 |
</p> |
286 |
</p> |
| 276 |
|
287 |
|
| 277 |
</body> |
288 |
</body> |
