| … | |
… | |
| 2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 3 | |
3 | |
| 4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 6 | |
6 | |
| 7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.12 2004/11/09 13:01:52 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.13 2004/11/15 12:47:47 swift Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>1.11</version> |
11 | <version>1.11</version> |
| 12 | <date>September 1, 2004</date> |
12 | <date>September 1, 2004</date> |
| … | |
… | |
| 44 | </p> |
44 | </p> |
| 45 | |
45 | |
| 46 | <p> |
46 | <p> |
| 47 | For PPC you can choose between <c>development-sources</c> and |
47 | For PPC you can choose between <c>development-sources</c> and |
| 48 | <c>gentoo-dev-sources</c> (both 2.6 kernels). The latter is available when you |
48 | <c>gentoo-dev-sources</c> (both 2.6 kernels). The latter is available when you |
| 49 | perform a networkless installation. Beside those there is special |
49 | perform a networkless installation. Beside those there is a special |
| 50 | kernel-2.6-patchset for the Pegasos: <c>pegasos-dev-sources</c>. So let's |
50 | kernel-2.6-patchset for the Pegasos: <c>pegasos-dev-sources</c>. So let's |
| 51 | continue with <c>emerge</c>'ing the kernel sources: |
51 | continue with <c>emerge</c>'ing the kernel sources: |
| 52 | </p> |
52 | </p> |
| 53 | |
53 | |
| 54 | <pre caption="Installing a kernel source"> |
54 | <pre caption="Installing a kernel source"> |
| … | |
… | |
| 60 | <path>linux</path> pointing to your kernel source: |
60 | <path>linux</path> pointing to your kernel source: |
| 61 | </p> |
61 | </p> |
| 62 | |
62 | |
| 63 | <pre caption="Viewing the kernel source symlink"> |
63 | <pre caption="Viewing the kernel source symlink"> |
| 64 | # <i>ls -l /usr/src/linux</i> |
64 | # <i>ls -l /usr/src/linux</i> |
| 65 | lrwxrwxrwx 1 root root 12 Jul 10 10:55 /usr/src/linux -> linux-2.6.7-r9 |
65 | lrwxrwxrwx 1 root root 12 Jul 10 10:55 /usr/src/linux -> linux-2.6.9 |
| 66 | </pre> |
66 | </pre> |
| 67 | |
67 | |
| 68 | <p> |
68 | <p> |
| 69 | If this isn't the case (i.e. the symlink points to a different kernel source) |
69 | If this isn't the case (i.e. the symlink points to a different kernel source) |
| 70 | change the symlink before you continue: |
70 | change the symlink before you continue: |
| 71 | </p> |
71 | </p> |
| 72 | |
72 | |
| 73 | <pre caption="Changing the kernel source symlink"> |
73 | <pre caption="Changing the kernel source symlink"> |
| 74 | # <i>rm /usr/src/linux</i> |
74 | # <i>rm /usr/src/linux</i> |
| 75 | # <i>cd /usr/src</i> |
75 | # <i>cd /usr/src</i> |
| 76 | # <i>ln -s linux-2.6.7-r9 linux</i> |
76 | # <i>ln -s linux-2.6.9 linux</i> |
| 77 | </pre> |
77 | </pre> |
| 78 | |
78 | |
| 79 | <p> |
79 | <p> |
| 80 | Now it is time to configure and compile your kernel source. All architectures |
80 | Now it is time to configure and compile your kernel source. All architectures |
| 81 | can use <c>genkernel</c> for this, which will build a generic kernel as used |
81 | can use <c>genkernel</c> for this, which will build a generic kernel as used |
| … | |
… | |
| 244 | When the kernel has finished compiling, copy the kernel image to |
244 | When the kernel has finished compiling, copy the kernel image to |
| 245 | <path>/boot</path>. |
245 | <path>/boot</path>. |
| 246 | </p> |
246 | </p> |
| 247 | |
247 | |
| 248 | <pre caption="Installing the kernel"> |
248 | <pre caption="Installing the kernel"> |
| 249 | <comment>replace 2.6.7 with your kernel-version</comment> |
249 | <comment>replace 2.6.9 with your kernel-version</comment> |
| 250 | (Apple/IBM) # <i>cp vmlinux /boot/kernel-2.6.7</i> |
250 | (Apple/IBM) # <i>cp vmlinux /boot/kernel-2.6.9</i> |
| 251 | (Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/kernel-2.6.7</i> |
251 | (Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/kernel-2.6.9</i> |
| 252 | </pre> |
252 | </pre> |
| 253 | |
253 | |
| 254 | <p> |
254 | <p> |
| 255 | Also don't forget to copy over the system map: |
255 | Also don't forget to copy over the system map: |
| 256 | </p> |
256 | </p> |
| 257 | |
257 | |
| 258 | <pre caption="Copying the system map"> |
258 | <pre caption="Copying the system map"> |
| 259 | # <i>cp System.map /boot/System.map-2.6.7</i> |
259 | # <i>cp System.map /boot/System.map-2.6.9</i> |
| 260 | </pre> |
260 | </pre> |
| 261 | |
261 | |
| 262 | <p> |
262 | <p> |
| 263 | It is also wise to copy over your kernel configuration file to |
263 | It is also wise to copy over your kernel configuration file to |
| 264 | <path>/boot</path>, just in case :) |
264 | <path>/boot</path>, just in case :) |
| 265 | </p> |
265 | </p> |
| 266 | |
266 | |
| 267 | <pre caption="Backing up your kernel configuration"> |
267 | <pre caption="Backing up your kernel configuration"> |
| 268 | # <i>cp .config /boot/config-2.6.7</i> |
268 | # <i>cp .config /boot/config-2.6.9</i> |
| 269 | </pre> |
269 | </pre> |
| 270 | |
270 | |
| 271 | <p> |
271 | <p> |
| 272 | Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
272 | Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
| 273 | Modules</uri>. |
273 | Modules</uri>. |
| … | |
… | |
| 276 | </body> |
276 | </body> |
| 277 | </subsection> |
277 | </subsection> |
| 278 | </section> |
278 | </section> |
| 279 | <section id="kernel_modules"> |
279 | <section id="kernel_modules"> |
| 280 | <title>Installing Separate Kernel Modules</title> |
280 | <title>Installing Separate Kernel Modules</title> |
| 281 | <!-- |
|
|
| 282 | <subsection> |
|
|
| 283 | <title>Installing Extra Modules</title> |
|
|
| 284 | <body> |
|
|
| 285 | |
|
|
| 286 | <p> |
|
|
| 287 | If appropriate, you should emerge ebuilds for any additional hardware that is |
|
|
| 288 | on your system. Here is a list of kernel-related ebuilds that you could emerge: |
|
|
| 289 | </p> |
|
|
| 290 | |
|
|
| 291 | <table> |
|
|
| 292 | <tcolumn width="1in"/> |
|
|
| 293 | <tcolumn width="4in"/> |
|
|
| 294 | <tcolumn width="2in"/> |
|
|
| 295 | <tr> |
|
|
| 296 | <th>Ebuild</th> |
|
|
| 297 | <th>Purpose</th> |
|
|
| 298 | <th>Command</th> |
|
|
| 299 | </tr> |
|
|
| 300 | </table> |
|
|
| 301 | |
|
|
| 302 | <p> |
|
|
| 303 | Beware though, some of these ebuilds might deal with big dependencies. To verify |
|
|
| 304 | what packages will be installed by emerging an ebuild, use <c>emerge |
|
|
| 305 | - -pretend</c>. For instance, for the <c>xfree-drm</c> package: |
|
|
| 306 | </p> |
|
|
| 307 | |
|
|
| 308 | <pre caption="View full installation package listing"> |
|
|
| 309 | # <i>emerge - -pretend xfree-drm</i> |
|
|
| 310 | </pre> |
|
|
| 311 | |
|
|
| 312 | </body> |
|
|
| 313 | </subsection> |
|
|
| 314 | --> |
|
|
| 315 | <subsection> |
281 | <subsection> |
| 316 | <title>Configuring the Modules</title> |
282 | <title>Configuring the Modules</title> |
| 317 | <body> |
283 | <body> |
| 318 | |
284 | |
| 319 | <p> |
285 | <p> |
Parent Directory
| 
Revision Log
| 
Patch