/[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.14 - (hide annotations) (download) (as text)
Sat Nov 20 22:23:30 2004 UTC (9 years, 11 months ago) by neysx
Branch: MAIN
Changes since 1.13: +2 -2 lines
File MIME type: application/xml
Converted dates to YYYY-MM-DD format

1 swift 1.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 neysx 1.14 <!-- $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 swift 1.1
9     <sections>
10 swift 1.12
11     <version>1.11</version>
12 neysx 1.14 <date>2004-09-01</date>
13 swift 1.12
14 swift 1.1 <section>
15     <title>Timezone</title>
16     <body>
17    
18     <p>
19     You first need to select your timezone so that your system knows where it is
20     located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
21     symlink to <path>/etc/localtime</path> using <c>ln</c>:
22     </p>
23    
24     <pre caption="Setting the timezone information">
25     # <i>ls /usr/share/zoneinfo</i>
26     <comment>(Suppose you want to use GMT)</comment>
27     # <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
28     </pre>
29    
30     </body>
31     </section>
32     <section>
33     <title>Installing the Sources</title>
34     <subsection>
35     <title>Choosing a Kernel</title>
36     <body>
37    
38     <p>
39     The core around which all distributions are built is the Linux kernel. It is the
40     layer between the user programs and your system hardware. Gentoo provides its
41     users several possible kernel sources. A full listing with description is
42     available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
43     Guide</uri>.
44     </p>
45    
46     <p>
47 neysx 1.8 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
49 swift 1.13 perform a networkless installation. Beside those there is a special
50 neysx 1.8 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:
52 swift 1.1 </p>
53    
54     <pre caption="Installing a kernel source">
55 dertobi123 1.6 # <i>emerge gentoo-dev-sources</i>
56 swift 1.1 </pre>
57    
58     <p>
59     When you take a look in <path>/usr/src</path> you should see a symlink called
60     <path>linux</path> pointing to your kernel source:
61     </p>
62    
63     <pre caption="Viewing the kernel source symlink">
64     # <i>ls -l /usr/src/linux</i>
65 swift 1.13 lrwxrwxrwx 1 root root 12 Jul 10 10:55 /usr/src/linux -&gt; linux-2.6.9
66 swift 1.1 </pre>
67    
68     <p>
69     If this isn't the case (i.e. the symlink points to a different kernel source)
70     change the symlink before you continue:
71     </p>
72    
73     <pre caption="Changing the kernel source symlink">
74 swift 1.3 # <i>rm /usr/src/linux</i>
75     # <i>cd /usr/src</i>
76 swift 1.13 # <i>ln -s linux-2.6.9 linux</i>
77 swift 1.1 </pre>
78    
79     <p>
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
82     by the LiveCD. We explain the "manual" configuration first though, as it is
83     the best way to optimize your environment.
84     </p>
85    
86     <p>
87 swift 1.2 Continue now with <uri link="#manual">Manual Configuration</uri>.
88 swift 1.1 </p>
89    
90     </body>
91     </subsection>
92     </section>
93     <section id="manual">
94 swift 1.2 <title>Manual Configuration</title>
95 swift 1.1 <subsection>
96     <title>Introduction</title>
97     <body>
98    
99     <p>
100 neysx 1.10 Manually configuring a kernel is often seen as the most difficult procedure a
101 neysx 1.11 Linux user ever has to perform. Nothing is less true -- after configuring a
102 swift 1.1 couple of kernels you don't even remember that it was difficult ;)
103     </p>
104    
105     <p>
106     However, one thing <e>is</e> true: you must know your system when you start
107     configuring a kernel manually. Most information can be gathered by viewing the
108     contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
109     can also run <c>lsmod</c> to see what kernel modules the LiveCD uses (it might
110     provide you with a nice hint on what to enable).
111     </p>
112    
113     <p>
114     Now go to your kernel source directory and execute <c>make menuconfig</c>. This
115     will fire up an ncurses-based configuration menu.
116     </p>
117    
118     <pre caption="Invoking menuconfig">
119     # <i>cd /usr/src/linux</i>
120     # <i>make menuconfig</i>
121     </pre>
122    
123     <p>
124     You will be greeted with several configuration sections. We'll first list some
125     options you must activate (otherwise Gentoo will not function, or not function
126     properly without additional tweaks).
127     </p>
128    
129     </body>
130     </subsection>
131     <subsection>
132     <title>Activating Required Options</title>
133     <body>
134    
135     <p>
136     First of all, activate the use of development and experimental code/drivers.
137     You need this, otherwise some very important code/drivers won't show up:
138     </p>
139    
140     <pre caption="Selecting experimental code/drivers">
141     Code maturity level options ---&gt;
142     [*] Prompt for development and/or incomplete code/drivers
143     </pre>
144    
145     <p>
146     Now go to <c>File Systems</c> and select support for the filesystems you use.
147     <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
148     able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc
149     file system</c>, <c>/dev file system</c> + <c>Automatically mount at boot</c>:
150     </p>
151    
152     <pre caption="Selecting necessary file systems">
153 dertobi123 1.6 File systems ---&gt;
154     Pseudo Filesystems ---&gt;
155     [*] /proc file system support
156     [*] /dev file system support (OBSOLETE)
157     [*] Automatically mount at boot
158     [*] Virtual memory file system support (former shm fs)
159    
160 swift 1.1 <comment>(Select one or more of the following options as needed by your system)</comment>
161     &lt;*&gt; Reiserfs support
162     &lt;*&gt; Ext3 journalling file system support
163     &lt;*&gt; Second extended fs support
164     &lt;*&gt; XFS filesystem support
165     </pre>
166    
167     <p>
168     If you are using PPPoE to connect to the Internet or you are using a dial-up
169     modem, you will need the following options in the kernel:
170     </p>
171    
172     <pre caption="Selecting PPPoE necessary drivers">
173 neysx 1.4 Device Drivers ---&gt;
174     Networking support ---&gt;
175     &lt;*&gt; PPP (point-to-point protocol) support
176     &lt;*&gt; PPP support for async serial ports
177     &lt;*&gt; PPP support for sync tty ports
178 swift 1.1 </pre>
179    
180     <p>
181     The two compression options won't harm but are not definitely needed, neither
182     does the <c>PPP over Ethernet</c> option, that might only be used by
183     <c>rp-pppoe</c> when configured to do kernel mode PPPoE.
184     </p>
185    
186     <p>
187     If you require it, don't forget to include support in the kernel for your
188     ethernet card.
189     </p>
190    
191     <p>
192     Disable ADB raw keycodes:
193     </p>
194    
195     <pre caption="Disabling ADB raw keycodes">
196     Macintosh Device Drivers ---&gt;
197     [ ] Support for ADB raw keycodes
198     </pre>
199    
200     <p>
201     Also choose the correct RTC support (<e>disable</e> the <c>Enhanced RTC</c>
202     option):
203     </p>
204    
205     <pre caption="Activating the correct RTC option">
206     Character devices ---&gt;
207     [ ] Enhanced RTC
208    
209     General setup ---&gt;
210     [*] Support for /dev/rtc
211     </pre>
212    
213     <p>
214     Users of OldWorld machines will want HFS support so they can copy compiled
215     kernels to the MacOS partition.
216     </p>
217    
218     <pre caption="Activating HFS support">
219     File Systems ---&gt;
220     [*] HFS Support
221     </pre>
222    
223     <p>
224     When you're done configuring your kernel, continue with <uri
225     link="#compiling">Compiling and Installing</uri>.
226     </p>
227    
228     </body>
229     </subsection>
230     <subsection id="compiling">
231     <title>Compiling and Installing</title>
232     <body>
233    
234     <p>
235     Now that your kernel is configured, it is time to compile and install it. Exit
236 dertobi123 1.6 the configuration and run the commands which will compile the kernel:
237 swift 1.1 </p>
238    
239     <pre caption="Compiling the kernel">
240 neysx 1.8 # <i>make all &amp;&amp; make modules_install</i>
241 swift 1.1 </pre>
242    
243     <p>
244 neysx 1.10 When the kernel has finished compiling, copy the kernel image to
245 swift 1.1 <path>/boot</path>.
246     </p>
247    
248     <pre caption="Installing the kernel">
249 swift 1.13 <comment>replace 2.6.9 with your kernel-version</comment>
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.9</i>
252 swift 1.2 </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 swift 1.13 # <i>cp System.map /boot/System.map-2.6.9</i>
260 swift 1.1 </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 swift 1.13 # <i>cp .config /boot/config-2.6.9</i>
269 swift 1.1 </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>Configuring the Modules</title>
283     <body>
284    
285     <p>
286     You should list the modules you want automatically loaded in
287 pylon 1.7 <path>/etc/modules.autoload.d/kernel-2.6</path>.
288 swift 1.1 You can add extra options to the modules too if you want.
289     </p>
290    
291     <p>
292     To view all available modules, run the following <c>find</c> command. Don't
293     forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
294     just compiled:
295     </p>
296    
297     <pre caption="Viewing all available modules">
298     # <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
299     </pre>
300    
301     <p>
302     For instance, to automatically load the <c>3c59x.o</c> module, edit the
303 pylon 1.7 <path>kernel-2.6</path> file and enter the module
304 swift 1.1 name in it.
305     </p>
306    
307 dertobi123 1.6 <pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
308     # <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
309 swift 1.1 </pre>
310    
311 pylon 1.7 <pre caption="/etc/modules.autoload.d/kernel-2.6">
312 swift 1.1 3c59x
313     </pre>
314    
315     <p>
316     Now run <c>modules-update</c> to commit your changes to the
317     <path>/etc/modules.conf</path> file:
318     </p>
319    
320     <pre caption="Running modules-update">
321     # <i>modules-update</i>
322     </pre>
323    
324     <p>
325     Continue the installation with <uri link="?part=1&amp;chap=8">Configuring
326     your System</uri>.
327     </p>
328    
329     </body>
330     </subsection>
331     </section>
332     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20