/[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.7 - (show annotations) (download) (as text)
Tue Aug 24 00:00:35 2004 UTC (10 years, 1 month ago) by pylon
Branch: MAIN
Changes since 1.6: +9 -38 lines
File MIME type: application/xml
Changes that has been known since the (inofficial) 2004.2 ppc-LiveCD has been released.

Mostly it's kernel-2.4 stuff that has been deleted.  And some updates about the Pegasos support.

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.6 2004/07/26 09:04:42 dertobi123 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 the both 2.6 kernel, <c>development-sources</c>
44 and <c>gentoo-dev-sources</c>. The latter is available when you perform a
45 networkless installation. Beside those there is special kernel-2.6-patchset for
46 the Pegasos: <c>pegasos-dev-sources</c>. 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 gentoo-dev-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 Jul 10 10:55 /usr/src/linux -&gt; linux-2.6.7-r9
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.7-r9 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.6.x kernel)</comment>
150 File systems ---&gt;
151 Pseudo Filesystems ---&gt;
152 [*] /proc file system support
153 [*] /dev file system support (OBSOLETE)
154 [*] Automatically mount at boot
155 [*] Virtual memory file system support (former shm fs)
156
157 <comment>(Select one or more of the following options as needed by your system)</comment>
158 &lt;*&gt; Reiserfs support
159 &lt;*&gt; Ext3 journalling file system support
160 &lt;*&gt; JFS filesystem support
161 &lt;*&gt; Second extended fs support
162 &lt;*&gt; XFS filesystem support
163 </pre>
164
165 <p>
166 If you are using PPPoE to connect to the Internet or you are using a dial-up
167 modem, you will need the following options in the kernel:
168 </p>
169
170 <pre caption="Selecting PPPoE necessary drivers">
171 <comment>(With a 2.6.x kernel)</comment>
172 Device Drivers ---&gt;
173 Networking support ---&gt;
174 &lt;*&gt; PPP (point-to-point protocol) support
175 &lt;*&gt; PPP support for async serial ports
176 &lt;*&gt; PPP support for sync tty ports
177 </pre>
178
179 <p>
180 The two compression options won't harm but are not definitely needed, neither
181 does the <c>PPP over Ethernet</c> option, that might only be used by
182 <c>rp-pppoe</c> when configured to do kernel mode PPPoE.
183 </p>
184
185 <p>
186 If you require it, don't forget to include support in the kernel for your
187 ethernet card.
188 </p>
189
190 <p>
191 Disable ADB raw keycodes:
192 </p>
193
194 <pre caption="Disabling ADB raw keycodes">
195 Macintosh Device Drivers ---&gt;
196 [ ] Support for ADB raw keycodes
197 </pre>
198
199 <p>
200 Also choose the correct RTC support (<e>disable</e> the <c>Enhanced RTC</c>
201 option):
202 </p>
203
204 <pre caption="Activating the correct RTC option">
205 Character devices ---&gt;
206 [ ] Enhanced RTC
207
208 General setup ---&gt;
209 [*] Support for /dev/rtc
210 </pre>
211
212 <p>
213 Users of OldWorld machines will want HFS support so they can copy compiled
214 kernels to the MacOS partition.
215 </p>
216
217 <pre caption="Activating HFS support">
218 File Systems ---&gt;
219 [*] HFS Support
220 </pre>
221
222 <p>
223 When you're done configuring your kernel, continue with <uri
224 link="#compiling">Compiling and Installing</uri>.
225 </p>
226
227 </body>
228 </subsection>
229 <subsection id="compiling">
230 <title>Compiling and Installing</title>
231 <body>
232
233 <p>
234 Now that your kernel is configured, it is time to compile and install it. Exit
235 the configuration and run the commands which will compile the kernel:
236 </p>
237
238 <pre caption="Compiling the kernel">
239 <comment>Kernel 2.6</comment>
240 (All) # <i>make all &amp;&amp; make modules_install</i>
241 </pre>
242
243 <p>
244 When the kernel is done compiling, copy over the kernel image to
245 <path>/boot</path>.
246 </p>
247
248 <pre caption="Installing the kernel">
249 <comment>replace 2.6.7 with your kernel-version</comment>
250 (Apple/IBM) # <i>cp vmlinux /boot/kernel-2.6.7</i>
251 (Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/kernel-2.6.7</i>
252 </pre>
253
254 <p>
255 Also don't forget to copy over the system map:
256 </p>
257
258 <pre caption="Copying the system map">
259 # <i>cp System.map /boot/System.map-2.6.7</i>
260 </pre>
261
262 <p>
263 It is also wise to copy over your kernel configuration file to
264 <path>/boot</path>, just in case :)
265 </p>
266
267 <pre caption="Backing up your kernel configuration">
268 # <i>cp .config /boot/config-2.6.7</i>
269 </pre>
270
271 <p>
272 Now continue with <uri link="#kernel_modules">Installing Separate Kernel
273 Modules</uri>.
274 </p>
275
276 </body>
277 </subsection>
278 </section>
279 <section id="kernel_modules">
280 <title>Installing Separate Kernel Modules</title>
281 <subsection>
282 <title>Installing Extra Modules</title>
283 <body>
284
285 <p>
286 If appropriate, you should emerge ebuilds for any additional hardware that is
287 on your system. Here is a list of kernel-related ebuilds that you could emerge:
288 </p>
289
290 <table>
291 <tcolumn width="1in"/>
292 <tcolumn width="4in"/>
293 <tcolumn width="2in"/>
294 <tr>
295 <th>Ebuild</th>
296 <th>Purpose</th>
297 <th>Command</th>
298 </tr>
299 </table>
300
301 <p>
302 Beware though, some of these ebuilds might deal with big dependencies. To verify
303 what packages will be installed by emerging an ebuild, use <c>emerge
304 --pretend</c>. For instance, for the <c>xfree-drm</c> package:
305 </p>
306
307 <pre caption="View full installation package listing">
308 # <i>emerge --pretend xfree-drm</i>
309 </pre>
310
311 </body>
312 </subsection>
313 <subsection>
314 <title>Configuring the Modules</title>
315 <body>
316
317 <p>
318 You should list the modules you want automatically loaded in
319 <path>/etc/modules.autoload.d/kernel-2.6</path>.
320 You can add extra options to the modules too if you want.
321 </p>
322
323 <p>
324 To view all available modules, run the following <c>find</c> command. Don't
325 forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
326 just compiled:
327 </p>
328
329 <pre caption="Viewing all available modules">
330 # <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
331 </pre>
332
333 <p>
334 For instance, to automatically load the <c>3c59x.o</c> module, edit the
335 <path>kernel-2.6</path> file and enter the module
336 name in it.
337 </p>
338
339 <pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
340 <comment>(Example for 2.6 kernels)</comment>
341 # <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
342 </pre>
343
344 <pre caption="/etc/modules.autoload.d/kernel-2.6">
345 3c59x
346 </pre>
347
348 <p>
349 Now run <c>modules-update</c> to commit your changes to the
350 <path>/etc/modules.conf</path> file:
351 </p>
352
353 <pre caption="Running modules-update">
354 # <i>modules-update</i>
355 </pre>
356
357 <p>
358 Continue the installation with <uri link="?part=1&amp;chap=8">Configuring
359 your System</uri>.
360 </p>
361
362 </body>
363 </subsection>
364 </section>
365 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20