/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml
Gentoo

Contents of /xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.5 - (show annotations) (download) (as text)
Sun Jul 18 10:29:59 2004 UTC (10 years, 5 months ago) by neysx
Branch: MAIN
Changes since 1.4: +1 -2 lines
File MIME type: application/xml
#57937: removed occurrences of xfs-sources, gaming-sources and [*] /dev/pts

1 <?xml version='1.0' encoding='UTF-8'?>
2 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4 <!-- The content of this document is licensed under the CC-BY-SA license -->
5 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6
7 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.4 2004/07/09 10:27:36 neysx Exp $ -->
8
9 <sections>
10 <section>
11 <title>Timezone</title>
12 <body>
13
14 <p>
15 You first need to select your timezone so that your system knows where it is
16 located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
17 symlink to <path>/etc/localtime</path> using <c>ln</c>:
18 </p>
19
20 <pre caption="Setting the timezone information">
21 # <i>ls /usr/share/zoneinfo</i>
22 <comment>(Suppose you want to use GMT)</comment>
23 # <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
24 </pre>
25
26 </body>
27 </section>
28 <section>
29 <title>Installing the Sources</title>
30 <subsection>
31 <title>Choosing a Kernel</title>
32 <body>
33
34 <p>
35 The core around which all distributions are built is the Linux kernel. It is the
36 layer between the user programs and your system hardware. Gentoo provides its
37 users several possible kernel sources. A full listing with description is
38 available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
39 Guide</uri>.
40 </p>
41
42 <p>
43 For PPC you can choose between <c>ppc-sources</c>, <c>ppc-sources-benh</c>,
44 <c>ppc-sources-dev</c>, <c>ppc-sources-crypto</c> and
45 <c>ppc-development-sources</c>. This latter kernel is available when you
46 perform a networkless installation. So let's continue with
47 <c>emerge</c>'ing the kernel sources:
48 </p>
49
50 <pre caption="Installing a kernel source">
51 # <i>emerge ppc-development-sources</i>
52 </pre>
53
54 <p>
55 When you take a look in <path>/usr/src</path> you should see a symlink called
56 <path>linux</path> pointing to your kernel source:
57 </p>
58
59 <pre caption="Viewing the kernel source symlink">
60 # <i>ls -l /usr/src/linux</i>
61 lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.1
62 </pre>
63
64 <p>
65 If this isn't the case (i.e. the symlink points to a different kernel source)
66 change the symlink before you continue:
67 </p>
68
69 <pre caption="Changing the kernel source symlink">
70 # <i>rm /usr/src/linux</i>
71 # <i>cd /usr/src</i>
72 # <i>ln -s linux-2.6.1 linux</i>
73 </pre>
74
75 <p>
76 Now it is time to configure and compile your kernel source. All architectures
77 can use <c>genkernel</c> for this, which will build a generic kernel as used
78 by the LiveCD. We explain the "manual" configuration first though, as it is
79 the best way to optimize your environment.
80 </p>
81
82 <p>
83 Continue now with <uri link="#manual">Manual Configuration</uri>.
84 </p>
85
86 </body>
87 </subsection>
88 </section>
89 <section id="manual">
90 <title>Manual Configuration</title>
91 <subsection>
92 <title>Introduction</title>
93 <body>
94
95 <p>
96 Manually configuring a kernel is often seen as the most difficult course every
97 Linux users ever has to go through. Nothing is less true -- after configuring a
98 couple of kernels you don't even remember that it was difficult ;)
99 </p>
100
101 <p>
102 However, one thing <e>is</e> true: you must know your system when you start
103 configuring a kernel manually. Most information can be gathered by viewing the
104 contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
105 can also run <c>lsmod</c> to see what kernel modules the LiveCD uses (it might
106 provide you with a nice hint on what to enable).
107 </p>
108
109 <p>
110 Now go to your kernel source directory and execute <c>make menuconfig</c>. This
111 will fire up an ncurses-based configuration menu.
112 </p>
113
114 <pre caption="Invoking menuconfig">
115 # <i>cd /usr/src/linux</i>
116 # <i>make menuconfig</i>
117 </pre>
118
119 <p>
120 You will be greeted with several configuration sections. We'll first list some
121 options you must activate (otherwise Gentoo will not function, or not function
122 properly without additional tweaks).
123 </p>
124
125 </body>
126 </subsection>
127 <subsection>
128 <title>Activating Required Options</title>
129 <body>
130
131 <p>
132 First of all, activate the use of development and experimental code/drivers.
133 You need this, otherwise some very important code/drivers won't show up:
134 </p>
135
136 <pre caption="Selecting experimental code/drivers">
137 Code maturity level options ---&gt;
138 [*] Prompt for development and/or incomplete code/drivers
139 </pre>
140
141 <p>
142 Now go to <c>File Systems</c> and select support for the filesystems you use.
143 <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
144 able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc
145 file system</c>, <c>/dev file system</c> + <c>Automatically mount at boot</c>:
146 </p>
147
148 <pre caption="Selecting necessary file systems">
149 <comment>(With a 2.4.x kernel)</comment>
150 File systems ---&gt;
151 [*] Virtual memory file system support (former shm fs)
152 [*] /proc file system support
153 [*] /dev file system support (EXPERIMENTAL)
154 [*] Automatically mount at boot
155 [ ] /dev/pts file system for Unix98 PTYs
156
157 <comment>(With a 2.6.x kernel)</comment>
158 File systems ---&gt;
159 Pseudo Filesystems ---&gt;
160 [*] /proc file system support
161 [*] /dev file system support (OBSOLETE)
162 [*] Automatically mount at boot
163 [*] Virtual memory file system support (former shm fs)
164
165 <comment>(Select one or more of the following options as needed by your system)</comment>
166 &lt;*&gt; Reiserfs support
167 &lt;*&gt; Ext3 journalling file system support
168 &lt;*&gt; JFS filesystem support
169 &lt;*&gt; Second extended fs support
170 &lt;*&gt; XFS filesystem support
171 </pre>
172
173 <p>
174 If you are using PPPoE to connect to the Internet or you are using a dial-up
175 modem, you will need the following options in the kernel:
176 </p>
177
178 <pre caption="Selecting PPPoE necessary drivers">
179 <comment>(With a 2.4.x kernel)</comment>
180 Network device support ---&gt;
181 &lt;*&gt; PPP (point-to-point protocol) support
182 &lt;*&gt; PPP support for async serial ports
183 &lt;*&gt; PPP support for sync tty ports
184
185 <comment>(With a 2.6.x kernel)</comment>
186 Device Drivers ---&gt;
187 Networking support ---&gt;
188 &lt;*&gt; PPP (point-to-point protocol) support
189 &lt;*&gt; PPP support for async serial ports
190 &lt;*&gt; PPP support for sync tty ports
191 </pre>
192
193 <p>
194 The two compression options won't harm but are not definitely needed, neither
195 does the <c>PPP over Ethernet</c> option, that might only be used by
196 <c>rp-pppoe</c> when configured to do kernel mode PPPoE.
197 </p>
198
199 <p>
200 If you require it, don't forget to include support in the kernel for your
201 ethernet card.
202 </p>
203
204 <p>
205 Disable ADB raw keycodes:
206 </p>
207
208 <pre caption="Disabling ADB raw keycodes">
209 Macintosh Device Drivers ---&gt;
210 [ ] Support for ADB raw keycodes
211 </pre>
212
213 <p>
214 Also choose the correct RTC support (<e>disable</e> the <c>Enhanced RTC</c>
215 option):
216 </p>
217
218 <pre caption="Activating the correct RTC option">
219 Character devices ---&gt;
220 [ ] Enhanced RTC
221
222 General setup ---&gt;
223 [*] Support for /dev/rtc
224 </pre>
225
226 <p>
227 Users of OldWorld machines will want HFS support so they can copy compiled
228 kernels to the MacOS partition.
229 </p>
230
231 <pre caption="Activating HFS support">
232 File Systems ---&gt;
233 [*] HFS Support
234 </pre>
235
236 <p>
237 When you're done configuring your kernel, continue with <uri
238 link="#compiling">Compiling and Installing</uri>.
239 </p>
240
241 </body>
242 </subsection>
243 <subsection id="compiling">
244 <title>Compiling and Installing</title>
245 <body>
246
247 <p>
248 Now that your kernel is configured, it is time to compile and install it. Exit
249 the configuration and run <c>make dep &amp;&amp; make vmlinux modules
250 modules_install</c> or on the Pegasos run <c>make dep &amp;&amp; make zImage
251 modules modules_install</c>:
252 </p>
253
254 <pre caption="Compiling the kernel">
255 (Apple/IBM) # <i>make dep &amp;&amp; make vmlinux modules modules_install</i>
256 (Pegasos) # <i>make dep &amp;&amp; make zImage modules modules_install</i>
257 </pre>
258
259 <p>
260 When the kernel is done compiling, copy over the kernel image to
261 <path>/boot</path>.
262 </p>
263
264 <pre caption="Installing the kernel">
265 (Apple/IBM) # <i>cp vmlinux /boot/kernel-2.4.24</i>
266 (Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/kernel-2.4.24</i>
267 </pre>
268
269 <p>
270 Also don't forget to copy over the system map:
271 </p>
272
273 <pre caption="Copying the system map">
274 # <i>cp System.map /boot/System.map-2.4.24</i>
275 </pre>
276
277 <p>
278 It is also wise to copy over your kernel configuration file to
279 <path>/boot</path>, just in case :)
280 </p>
281
282 <pre caption="Backing up your kernel configuration">
283 # <i>cp .config /boot/config-2.4.24</i>
284 </pre>
285
286 <p>
287 Now continue with <uri link="#kernel_modules">Installing Separate Kernel
288 Modules</uri>.
289 </p>
290
291 </body>
292 </subsection>
293 </section>
294 <section id="kernel_modules">
295 <title>Installing Separate Kernel Modules</title>
296 <subsection>
297 <title>Installing Extra Modules</title>
298 <body>
299
300 <p>
301 If appropriate, you should emerge ebuilds for any additional hardware that is
302 on your system. Here is a list of kernel-related ebuilds that you could emerge:
303 </p>
304
305 <table>
306 <tcolumn width="1in"/>
307 <tcolumn width="4in"/>
308 <tcolumn width="2in"/>
309 <tr>
310 <th>Ebuild</th>
311 <th>Purpose</th>
312 <th>Command</th>
313 </tr>
314 <tr>
315 <ti>xfree-drm</ti>
316 <ti>
317 Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and
318 other cards for XFree86. Please check the <c>IUSE_VIDEO_CARDS</c> variable
319 in the <path>/usr/portage/x11-base/xfree-drm</path> ebuilds to see what you
320 need to fill in as <c>yourcard</c>.
321 </ti>
322 <ti><c>VIDEO_CARDS="yourcard" emerge xfree-drm</c></ti>
323 </tr>
324 </table>
325
326 <p>
327 Beware though, some of these ebuilds might deal with big dependencies. To verify
328 what packages will be installed by emerging an ebuild, use <c>emerge
329 --pretend</c>. For instance, for the <c>xfree-drm</c> package:
330 </p>
331
332 <pre caption="View full installation package listing">
333 # <i>emerge --pretend xfree-drm</i>
334 </pre>
335
336 </body>
337 </subsection>
338 <subsection>
339 <title>Configuring the Modules</title>
340 <body>
341
342 <p>
343 You should list the modules you want automatically loaded in
344 <path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>).
345 You can add extra options to the modules too if you want.
346 </p>
347
348 <p>
349 To view all available modules, run the following <c>find</c> command. Don't
350 forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
351 just compiled:
352 </p>
353
354 <pre caption="Viewing all available modules">
355 # <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
356 </pre>
357
358 <p>
359 For instance, to automatically load the <c>3c59x.o</c> module, edit the
360 <path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module
361 name in it.
362 </p>
363
364 <pre caption="Editing /etc/modules.autoload.d/kernel-2.4">
365 <comment>(Example for 2.4 kernels)</comment>
366 # <i>nano -w /etc/modules.autoload.d/kernel-2.4</i>
367 </pre>
368
369 <pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6">
370 3c59x
371 </pre>
372
373 <p>
374 Now run <c>modules-update</c> to commit your changes to the
375 <path>/etc/modules.conf</path> file:
376 </p>
377
378 <pre caption="Running modules-update">
379 # <i>modules-update</i>
380 </pre>
381
382 <p>
383 Continue the installation with <uri link="?part=1&amp;chap=8">Configuring
384 your System</uri>.
385 </p>
386
387 </body>
388 </subsection>
389 </section>
390 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20