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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.34 Revision 1.49
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
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/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.34 2005/08/09 09:43:58 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.49 2007/05/15 13:07:41 neysx Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>2.11</version> 11<version>8.1</version>
12<date>2005-08-09</date> 12<date>2007-05-15</date>
13 13
14<section> 14<section>
15<title>Timezone</title> 15<title>Timezone</title>
16<body> 16<body>
17 17
18<p> 18<p>
19First, select your timezone so that your system knows where it is located. Look 19You first need to select your timezone so that your system knows where it is
20for your timezone in <path>/usr/share/zoneinfo</path>, then make a symlink to 20located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
21<path>/etc/localtime</path> using <c>ln</c>: 21it to <path>/etc/localtime</path>. Please avoid the
22<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
23indicate the expected zones. For instance, <path>GMT-8</path> is in fact
24GMT+8.
22</p> 25</p>
23 26
24<pre caption="Setting the timezone information"> 27<pre caption="Setting the timezone information">
25# <i>ls /usr/share/zoneinfo</i> 28# <i>ls /usr/share/zoneinfo</i>
26<comment>(Suppose you want to use GMT)</comment> 29<comment>(Suppose you want to use GMT)</comment>
27# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i> 30# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
28</pre> 31</pre>
29 32
30</body> 33</body>
31</section> 34</section>
32<section> 35<section>
33<title>Installing the Sources</title> 36<title>Installing the Kernel Sources</title>
34<subsection> 37<subsection>
35<title>Choosing a Kernel</title> 38<title>Choosing a Kernel</title>
36<body> 39<body>
37 40
38<p> 41<p>
39The base that all distributions are built upon is the Linux kernel. It is the 42The core around which all distributions are built is the Linux kernel. It is the
40layer between the your programs and your system hardware. Gentoo provides its 43layer between the user programs and your system hardware. Gentoo provides its
41users several possible kernel sources. A full listing with description is 44users several possible kernels to choose from. A full listing with description
45is available at the
42available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel 46<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>.
43Guide</uri>.
44</p>
45
46<p> 47</p>
47We suggest using either <c>vanilla-sources</c> or <c>gentoo-sources</c> 48
48on PPC, which are both 2.6 kernels. The latter is available when you
49perform a networkless installation. So let's continue with <c>emerge</c>'ing
50the kernel sources:
51</p> 49<p>
50We suggest using <c>gentoo-sources</c> on PPC, which is a recent 2.6 kernel.
51</p>
52 52
53<pre caption="Installing the kernel source"> 53<pre caption="Installing a kernel source">
54# <i>emerge gentoo-sources</i> 54# <i>emerge gentoo-sources</i>
55</pre> 55</pre>
56 56
57<note>
58The suggested sources at the time of the 2005.1 release are
59<c>gentoo-sources-2.6.12-r4</c> and <c>vanilla-sources-2.6.12.2</c>.
60</note>
61
62<p> 57<p>
63If you take a look in <path>/usr/src</path> you should see a symlink named 58If you take a look in <path>/usr/src</path> you should see a symlink named
64<path>linux</path> pointing to your current kernel source. Here, we will assume 59<path>linux</path> pointing to your current kernel source. In this case, the
65that the kernel source installed is <c>gentoo-sources-2.6.12-r4</c>: 60installed kernel source points to <c>gentoo-sources-<keyval
61id="kernel-version"/></c>. Your version may be different, so keep this in mind.
66</p> 62</p>
67 63
68<pre caption="Viewing the kernel source symlink"> 64<pre caption="Viewing the kernel source symlink">
69# <i>ls -l /usr/src/linux</i> 65# <i>ls -l /usr/src/linux</i>
70lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -&gt; linux-2.6.12-gentoo-r4 66lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -&gt; linux-<keyval id="kernel-gentoo"/>
71</pre> 67</pre>
72 68
73<p>
74If the symlink doesn't point to the kernel source of your choice (note that
75<c>linux-2.6.12-gentoo-r4</c> is merely an example) you should change it to the
76desired kernel sources:
77</p> 69<p>
78
79<pre caption="Changing the kernel source symlink">
80# <i>rm /usr/src/linux</i>
81# <i>cd /usr/src</i>
82# <i>ln -s linux-2.6.12-gentoo-r4 linux</i>
83</pre>
84
85<p>
86It is now time to configure and compile your kernel source. You can use 70Now it is time to configure and compile your kernel source. You can use
87<c>genkernel</c> to build a generic kernel similar to the one used by the 71<c>genkernel</c> for this, which will build a generic kernel as used by the
88Installation CD, or you can perform a manual configuration to best suit your 72Installation CD. We explain the "manual" configuration first though, as it is
89system. 73a more efficient configuration.
90</p> 74</p>
91 75
92<p> 76<p>
93If you want to manually configure your kernel, continue now with <uri 77If you want to manually configure your kernel, continue now with <uri
94link="#manual">Default: Manual Configuration</uri>. If you want to use 78link="#manual">Default: Manual Configuration</uri>. If you want to use
105<title>Introduction</title> 89<title>Introduction</title>
106<body> 90<body>
107 91
108<p> 92<p>
109Manually configuring a kernel is often seen as the most difficult procedure a 93Manually configuring a kernel is often seen as the most difficult procedure a
110Linux user ever has to perform. Nothing is less true, after configuring a 94Linux user ever has to perform. Nothing is less true -- after configuring a
111couple of kernels you won't even remember it being that difficult ;) 95few kernels you won't even remember that it was difficult ;)
112</p>
113
114<p> 96</p>
115Building a successful you must know what is in your system when 97
98<p>
99However, one thing <e>is</e> true: you must know your system when you start
116you start configuring a kernel manually. Most information can be gathered by 100configuring a kernel manually. Most information can be gathered by emerging
117emerging pciutils <c>emerge pciutils</c> which contains <c>lspci</c>. You 101pciutils (<c>emerge pciutils</c>) which contains the program
118can 102<c>lspci</c>. You will now be able to use <c>lspci</c> within the chrooted
119be able to use <c>lspci</c> within the chrooted environment. You may safely 103environment. You may safely ignore any <e>pcilib</e> warnings (such as pcilib:
120ignore any <e>pcilib</e> warnings (like pcilib: cannot open
121/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 104cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively,
122<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 105you can run <c>lspci</c> from a <e>non-chrooted</e> environment. The results
123You can also run <c>lsmod</c> to see what kernel modules the Installation CD 106are the same. You can also run <c>lsmod</c> to see what kernel modules the
124uses (it might provide you with a nice hint on what to enable). Another place 107Installation CD uses (it might provide you with a nice hint on what to enable).
125to look for clues as to what components to enable is to check the kernel 108Another place to look for clues as to what components to enable is to check the
126message logs from the successful boot that got you this far. Type <c>dmesg</c> 109kernel message logs from the successful boot that got you this far. Type
127to see the kernel messages. 110<c>dmesg</c> to see these kernel messages.
128</p>
129
130<p> 111</p>
131Now go to your kernel source directory and execute <c>make menuconfig</c>. This 112
132will fire up an ncurses-based configuration menu. 113<p>
114Now, go to your kernel source directory, it's time to configure your kernel.
115Start by configuring a kernel that will boot on most 32 Bit PowerPC machines
116by first running <c>make pmac32_defconfig</c>. After the default configuration
117has been generated, run <c>make menuconfig</c> to start an ncurses-based
118configuration menu.
133</p> 119</p>
134 120
135<pre caption="Invoking menuconfig"> 121<pre caption="Invoking menuconfig">
136# <i>cd /usr/src/linux</i> 122# <i>cd /usr/src/linux</i>
123# <i>make pmac32_defconfig</i>
137# <i>make menuconfig</i> 124# <i>make menuconfig</i>
138</pre> 125</pre>
139 126
140<p> 127<p>
141You will be greeted with several configuration sections. We'll first list some 128You will be greeted with several configuration sections. We'll first list some
152<p> 139<p>
153First of all, activate the use of development and experimental code/drivers. 140First of all, activate the use of development and experimental code/drivers.
154You need this, otherwise some very important code/drivers won't show up: 141You need this, otherwise some very important code/drivers won't show up:
155</p> 142</p>
156 143
157<pre caption="Selecting experimental code/drivers, General setup"> 144<pre caption="Selecting experimental code/drivers">
158Code maturity level options ---&gt; 145Code maturity level options ---&gt;
159 [*] Prompt for development and/or incomplete code/drivers 146 [*] Prompt for development and/or incomplete code/drivers
160General setup --->
161 [*] Support for hot-pluggable devices
162</pre> 147</pre>
163 148
164<p> 149<p>
165Now go to <c>File Systems</c> and select support for the filesystems you use. 150Now go to <c>File Systems</c> and select support for the filesystems you use.
166<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be 151<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
167able to mount your partitions. Also select <c>/proc file system</c> and 152able to mount your partitions. Also select the <c>/proc file system</c> and
168<c>Virtual memory</c>. Do <e>not</e> select the <c>/dev file system</c>. 153<c>Virtual memory</c>. Make sure that you also enable support for Amiga
154partitions if you are using a Pegasos, or Macintosh partitions if you are using
155an Apple computer.
169</p> 156</p>
170 157
171<pre caption="Selecting necessary file systems"> 158<pre caption="Selecting necessary file systems">
172File systems ---&gt; 159File systems ---&gt;
173 Pseudo Filesystems ---&gt; 160 Pseudo Filesystems ---&gt;
161<comment>(/proc may already be forced on by your configuration, if so, you'll see --- instead)</comment>
174 [*] /proc file system support 162 [*] /proc file system support
175 [ ] /dev file system support (OBSOLETE)
176 [*] Virtual memory file system support (former shm fs) 163 [*] Virtual memory file system support (former shm fs)
164 Partition Types ---&gt;
165 [*] Amiga partition table support
166 [*] Macintosh partition map support
177 167
178<comment>(Select one or more of the following options as needed by your system)</comment> 168<comment>(Select one or more of the following options as needed by your system)</comment>
169 &lt;*&gt; Reiserfs support
170 &lt;*&gt; Ext3 journalling file system support
179 &lt;*&gt; Second extended fs support 171 &lt;*&gt; Second extended fs support
180 &lt;*&gt; Ext3 journalling file system support
181 &lt;*&gt; Reiserfs support
182 &lt;*&gt; XFS filesystem support 172 &lt;*&gt; XFS filesystem support
173</pre>
174
175<p>
176Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld
177users require it for copying compiled kernels to the MacOS partition. NewWorld
178users require it for configuring the special Apple_Bootstrap partition:
179</p>
180
181<pre caption="Activating HFS support">
182File Systems ---&gt;
183 Miscellaneous filesystems ---&gt;
184 &lt;*&gt; Apple Macintosh file system support
185 &lt;*&gt; Apple Extended HFS file system support
183</pre> 186</pre>
184 187
185<p> 188<p>
186If you are using PPPoE to connect to the Internet or you are using a dial-up 189If you are using PPPoE to connect to the Internet or you are using a dial-up
187modem, you will need the following options in the kernel: 190modem, you will need the following options in the kernel:
188</p> 191</p>
189 192
190<pre caption="Selecting PPPoE necessary drivers"> 193<pre caption="Selecting PPPoE necessary drivers">
191Device Drivers ---&gt; 194Device Drivers ---&gt;
192 Networking support ---&gt; 195 Network device support ---&gt;
193 &lt;*&gt; PPP (point-to-point protocol) support 196 &lt;*&gt; PPP (point-to-point protocol) support
194 &lt;*&gt; PPP support for async serial ports 197 &lt;*&gt; PPP support for async serial ports
195 &lt;*&gt; PPP support for sync tty ports 198 &lt;*&gt; PPP support for sync tty ports
196</pre> 199</pre>
197 200
198<p> 201<p>
199The two compression options won't harm but are not definitely needed, neither 202The two compression options won't harm but are not always needed. The <c>PPP
200does the <c>PPP over Ethernet</c> option, that might only be used by 203over Ethernet</c> option might only be used by <c>ppp</c> when configured to
201<c>rp-pppoe</c> when configured to do kernel mode PPPoE. 204perform kernel mode PPPoE.
202</p>
203
204<p> 205</p>
205If you require it, don't forget to include support in the kernel for your 206
206ethernet card.
207</p> 207<p>
208 208Don't forget to include support in the kernel for your ethernet card! Most
209newer Apple computers use the SunGEM ethernet driver. Older iMacs commonly use
210the BMAC driver.
209<p> 211</p>
210Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld 212
211users require it for copying compiled kernels to the MacOS partition. NewWorld 213<pre caption="Selecting the network driver">
212users require it for configuring the special Apple_Bootstrap partition: 214Device Drivers ---&gt;
215 Network device support ---&gt;
216 Ethernet (10 or 100Mbit) ---&gt;
217 [*] Ethernet (10 or 100Mbit)
218 &lt;*&gt; Generic Media Independent Interface device support
219 &lt;*&gt; MACE (Power Mac ethernet) support
220 &lt;*&gt; BMAC (G3 ethernet) support
221 &lt;*&gt; Sun GEM support
222</pre>
223
213</p> 224<p>
214
215<pre caption="Activating HFS support">
216File Systems ---&gt;
217 [*] HFS Support
218</pre>
219
220<p>
221At this time, kernel preemption is still unstable on PPC and may cause 225At this time, full kernel preemption may still be unstable on PPC and may cause
222compilation failures and random segfaults. It is <e>strongly</e> suggested 226compilation failures and random segfaults. It is <e>strongly</e> suggested
223that you do not use this feature. 227that you do not use this featurea. Both <e>Voluntary Preemption</e> and
228<e>No Forced Preemption</e> should be safe.
224</p> 229</p>
225 230
226<pre caption="Ensure the Preemptible Kernel Option is Off"> 231<pre caption="Ensure the Preemptible Kernel Option is Off">
227Platform options ---&gt; 232Kernel options ---&gt;
228 [ ] Preemptible Kernel 233<comment>(Select One)</comment>
234 Preemption Model
235 (X) No Forced Preemption (Server)
236 (X) Voluntary Kernel Preemption (Desktop)
229</pre> 237</pre>
230 238
231<p> 239<p>
232If you're booting from Firewire, you'll need to enable these options. If you 240If you're booting from Firewire, you'll need to enable these options. If you do
233do not want to compile in support, you'll need to include these modules and 241not want to compile in support, you'll need to include these modules and their
234their dependencies in an initrd. 242dependencies in an initrd.
235</p> 243</p>
236 244
237<pre caption="Enable support for firewire devices on boot"> 245<pre caption="Enable support for firewire devices on boot">
238Device Drivers ---&gt; 246Device Drivers ---&gt;
239 IEEE 1394 (FireWire) support ---&gt; 247 IEEE 1394 (FireWire) support ---&gt;
261boot. If you are using an NVIDIA based chipset, you should use the OpenFirmware 269boot. If you are using an NVIDIA based chipset, you should use the OpenFirmware
262framebuffer. If you are using an ATI based chipset, you should select the 270framebuffer. If you are using an ATI based chipset, you should select the
263framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon). 271framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon).
264</p> 272</p>
265 273
266<pre caption="Chosing a Framebuffer Driver"> 274<pre caption="Choosing a Framebuffer Driver">
267Device Drivers ---&gt; 275Device Drivers ---&gt;
268 Graphics support ---&gt; 276 Graphics support ---&gt;
269 &lt;*&gt; Support for frame buffer devices 277 &lt;*&gt; Support for frame buffer devices
270 [*] Open Firmware frame buffer device support 278 [*] Open Firmware frame buffer device support
271 &lt;*&gt; ATI Radeon display support 279 &lt;*&gt; ATI Radeon display support
276</pre> 284</pre>
277 285
278<note> 286<note>
279If you select more than one framebuffer device, it may default to a less than 287If you select more than one framebuffer device, it may default to a less than
280optimal driver. Either use only one framebuffer device or specify which 288optimal driver. Either use only one framebuffer device or specify which
281to use by passing the driver to use to the kernel on boot such as 289to use by passing the driver to use to the kernel on boot by appending a video
282<c>video=radeonfb</c>. 290line such as: <c>video=radeonfb</c>.
283</note> 291</note>
284 292
285<p> 293<p>
286When you're done configuring your kernel, continue with <uri 294When you're done configuring your kernel, continue with <uri
287link="#compiling">Compiling and Installing</uri>. 295link="#compiling">Compiling and Installing</uri>.
293<title>Compiling and Installing</title> 301<title>Compiling and Installing</title>
294<body> 302<body>
295 303
296<p> 304<p>
297Now that your kernel is configured, it is time to compile and install it. Exit 305Now that your kernel is configured, it is time to compile and install it. Exit
298the configuration and run the commands which will compile the kernel: 306the configuration menu and run the following commands:
299</p> 307</p>
300 308
301<pre caption="Compiling the kernel"> 309<pre caption="Compiling the kernel">
302# <i>make &amp;&amp; make modules_install</i> 310# <i>make &amp;&amp; make modules_install</i>
303</pre> 311</pre>
304 312
305<p> 313<p>
306When the kernel has finished compiling, copy the kernel image to 314When the kernel has finished compiling, copy the kernel image to
307<path>/boot</path> (be sure that it is mounted properly on the Pegasos). 315<path>/boot</path> as shown below. If you have a separate boot partition, as
316on Pegasos computers, be sure that it is mounted properly. If you are using
317BootX to boot, we'll copy the kernel later.
318</p>
319
320<p>
321Yaboot and BootX expect to use an uncompressed kernel unlike many other
322bootloaders. The uncompressed kernel is called vmlinux and it is placed in
323<path>/usr/src/linux</path> after the kernel has finished compiling. If you are
324using a Pegasos machine, the Pegasos firmware requires a compressed kernel
325called zImage which can be found in
326<path>/usr/src/linux/arch/powerpc/boot/images</path>.
308</p> 327</p>
309 328
310<pre caption="Installing the kernel"> 329<pre caption="Installing the kernel">
311<comment>replace 2.6.12 with your kernel-version</comment> 330# <i>cd /usr/src/linux</i>
312(Apple/IBM) # <i>cp vmlinux /boot/kernel-2.6.12</i> 331<comment>Note, your kernel version might be different</comment>
313(Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/kernel-2.6.12</i> 332<comment>(Apple/IBM)</comment>
314</pre> 333# <i>cp vmlinux /boot/<keyval id="kernel-name"/></i>
315 334<comment>(Pegasos)</comment>
316<p> 335# <i>cp arch/powerpc/boot/images/zImage /boot/&lt;kernel-version&gt;</i>
317It is also wise to copy over your kernel configuration file to
318<path>/boot</path>, just in case :)
319</p>
320
321<pre caption="Backing up your kernel configuration">
322# <i>cp .config /boot/config-2.6.12-gentoo-r4</i>
323</pre> 336</pre>
324 337
325<p> 338<p>
326Now continue with <uri link="#kernel_modules">Installing Separate Kernel 339Now continue with <uri link="#kernel_modules">Installing Separate Kernel
327Modules</uri>. 340Modules</uri>.
335<subsection> 348<subsection>
336<title>Configuring the Modules</title> 349<title>Configuring the Modules</title>
337<body> 350<body>
338 351
339<p> 352<p>
340You should list the modules you want automatically loaded in 353You should list the modules you want automatically loaded in
341<path>/etc/modules.autoload.d/kernel-2.6</path>. 354<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
342You can add extra options to the modules too if needed. 355the modules if required.
343</p> 356</p>
344 357
345<p> 358<p>
346To view all available modules, run the following <c>find</c> command. Don't 359To view all available modules, run the following <c>find</c> command. Don't
347forget to substitute "&lt;kernel version&gt;" with the version of the kernel you 360forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
351<pre caption="Viewing all available modules"> 364<pre caption="Viewing all available modules">
352# <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i> 365# <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
353</pre> 366</pre>
354 367
355<p> 368<p>
356For instance, to automatically load the <c>3c59x.o</c> module, edit the 369For instance, to automatically load the <c>3c59x</c> module, edit the
357<path>kernel-2.6</path> file and enter the module 370<path>kernel-2.6</path> file and add the module to it, one module on a line.
358name in it.
359</p> 371</p>
360 372
361<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> 373<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
362# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> 374# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
363</pre> 375</pre>
377<section id="genkernel"> 389<section id="genkernel">
378<title>Alternative: Using genkernel</title> 390<title>Alternative: Using genkernel</title>
379<body> 391<body>
380 392
381<p> 393<p>
382If you are reading this section, you have chosen to use our <c>genkernel</c>
383script to configure your kernel for you.
384</p>
385
386<p>
387Now that your kernel source tree is installed, it's now time to compile your 394Now that your kernel source tree is installed, it's now time to compile your
388kernel by using our <c>genkernel</c> script to automatically build a kernel for 395kernel by using our <c>genkernel</c> script to automatically build a kernel for
389you. <c>genkernel</c> works by configuring a kernel nearly identically to the 396you. <c>genkernel</c> works by configuring a kernel nearly identically to the
390way our Installation CD kernel is configured. This means that when you use 397way our Installation CD kernel is configured. This means that when you use
391<c>genkernel</c> to build your kernel, your system will generally detect all 398<c>genkernel</c> to build your kernel, your system will generally detect all
392your hardware at boot-time, just like our Installation CD does. 399your hardware at boot-time, just like our Installation CD does. Because
393Because genkernel doesn't require any manual kernel configuration, it is an 400genkernel doesn't require any manual kernel configuration, it is an ideal
394ideal solution for those users who may not be comfortable compiling their own 401solution for those users who may not be comfortable compiling their own
395kernels. 402kernels.
396</p> 403</p>
397 404
398<p> 405<p>
399Now, let's see how to use genkernel. First, emerge the genkernel ebuild: 406Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
416If you are using firewire or USB to boot, you'll need to add modules to the 423If you are using firewire or USB to boot, you'll need to add modules to the
417initrd. Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change 424initrd. Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change
418<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or 425<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or
419<c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support. 426<c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support.
420</p> 427</p>
428
429<p>
430Before compiling your sources, the fstab needs a slight adjustment. The rest of
431the fstab will be completed during a later step, so don't worry about the
432details now. If you did not create a separate boot partition (NOT bootstrap,
433that's different), remove the line referencing <path>/boot</path> from
434<path>/etc/fstab</path>. This will need to be done on most Apple computers.
435</p>
436
437<pre caption="Removing /boot from /etc/fstab on machines without a boot partition">
438# <i>nano -w /etc/fstab</i>
439<comment>Remove this line</comment>
440/dev/BOOT /boot ext2 noauto,noatime 1 2
441</pre>
421 442
422<p> 443<p>
423Now, compile your kernel sources by running <c>genkernel --genzimage all</c>. 444Now, compile your kernel sources by running <c>genkernel --genzimage all</c>.
424For Pegasos, we will need to use a different config and create a zImage instead 445For Pegasos, we will need to use a different config and create a zImage instead
425of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> 446of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c>
428</p> 449</p>
429 450
430<p> 451<p>
431Note that, if your partition where the kernel should be located doesn't use ext2 452Note that, if your partition where the kernel should be located doesn't use ext2
432or ext3 as filesystem you might need to manually configure your kernel using 453or ext3 as filesystem you might need to manually configure your kernel using
433<c>genkernel --menuconfig --genzimage all</c> and add support for your 454<c>genkernel --menuconfig all</c> and add support for your
434filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or 455filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or
435LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as argument as 456LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as an argument as
436well. 457well.
437</p> 458</p>
438 459
439<pre caption="Running genkernel"> 460<pre caption="Running genkernel">
440# <i>genkernel all</i> 461# <i>genkernel all</i>
446 467
447<p> 468<p>
448Once <c>genkernel</c> completes, a kernel, full set of modules and 469Once <c>genkernel</c> completes, a kernel, full set of modules and
449<e>initial root disk</e> (initrd) will be created. We will use the kernel 470<e>initial root disk</e> (initrd) will be created. We will use the kernel
450and initrd when configuring a boot loader later in this document. Write 471and initrd when configuring a boot loader later in this document. Write
451down the names of the kernel and initrd as you will need it when writing 472down the names of the kernel and initrd as you will need them when writing
452the bootloader configuration file. The initrd will be started immediately after 473the bootloader configuration file. The initrd will be started immediately after
453booting to perform hardware autodetection (just like on the Installation CD) 474booting to perform hardware autodetection (just like on the Installation CD)
454before your "real" system starts up. Be sure to also copy down the required 475before your "real" system starts up. Be sure to also copy down the required
455boot arguments, these are required for a successful boot with genkernel. 476boot arguments, these are required for a successful boot with genkernel.
456</p> 477</p>
457 478
458<pre caption="Checking the created kernel image name and initrd"> 479<pre caption="Checking the created kernel image name and initrd">
459# <i>ls /boot/kernel* /boot/initrd*</i> 480<comment>Note, your kernel version might be different</comment>
460</pre> 481# <i>ls /boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> /boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/></i>
461
462<p>
463Now, let's perform one more step to get our system to be more like the
464Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects
465hardware that is needed to boot your system, <c>coldplug</c> autodetects
466everything else. To emerge and enable <c>coldplug</c>, type the following:
467</p>
468
469<pre caption="Emerging and enabling coldplug">
470# <i>emerge coldplug</i>
471# <i>rc-update add coldplug boot</i>
472</pre> 482</pre>
473 483
474<p> 484<p>
475Now continue with <uri link="?part=1&amp;chap=8">Configuring your System</uri>. 485Now continue with <uri link="?part=1&amp;chap=8">Configuring your System</uri>.
476</p> 486</p>
477 487
478</body> 488</body>
479</section> 489</section>
480
481</sections> 490</sections>
491

Legend:
Removed from v.1.34  
changed lines
  Added in v.1.49

  ViewVC Help
Powered by ViewVC 1.1.20