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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.32 - (show annotations) (download) (as text)
Fri Aug 3 10:48:04 2007 UTC (11 years, 4 months ago) by nightmorph
Branch: MAIN
Changes since 1.31: +2 -2 lines
File MIME type: application/xml
2.6 kernels use .ko; 2.4 kernels (which are unsupported) use .o; fixed for all handbooks. no revbump either as it's basically a typo fix at this point.

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/2.5 -->
6
7 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v 1.31 2007/07/29 22:48:00 nightmorph Exp $ -->
8
9 <sections>
10
11 <version>8.2</version>
12 <date>2007-07-29</date>
13
14 <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 copy
21 it to <path>/etc/localtime</path>. Please avoid the
22 <path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
23 indicate the expected zones. For instance, <path>GMT-8</path> is in fact
24 GMT+8.
25 </p>
26
27 <pre caption="Setting the timezone information">
28 # <i>ls /usr/share/zoneinfo</i>
29 <comment>(Suppose you want to use GMT)</comment>
30 # <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
31 </pre>
32
33 </body>
34 </section>
35 <section>
36 <title>Installing the Sources</title>
37 <subsection>
38 <title>Choosing a Kernel</title>
39 <body>
40
41 <p>
42 The core around which all distributions are built is the Linux kernel.
43 It is the layer between the user programs and your system hardware.
44 Gentoo provides its users several possible kernel sources. A full
45 listing with description is available at the <uri
46 link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>.
47 </p>
48
49 <p>
50 For PPC64 you should use <c>gentoo-sources</c>.
51 </p>
52
53 <pre caption="Installing a kernel source">
54 # <i>emerge gentoo-sources</i>
55 </pre>
56
57 <p>
58 When you take a look in <path>/usr/src</path> you should see a symlink called
59 <path>linux</path> pointing to your kernel source. In this case, the installed
60 kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
61 Your version may be different, so keep this in mind.
62 </p>
63
64 <pre caption="Viewing the kernel source symlink">
65 # <i>ls -l /usr/src/linux</i>
66 lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
67 </pre>
68
69 <p>
70 Now it is time to configure and compile your kernel source. There is the
71 ability to use "genkernel" which would create a generic kernel like the
72 ones used on the installation CDs, but it is not fully functional for PPC64 at
73 the moment.
74 </p>
75
76 <p>
77 Continue now with <uri link="#manual">Manual Configuration</uri>.
78 </p>
79
80 </body>
81 </subsection>
82 </section>
83 <section id="manual">
84 <title>Manual Configuration</title>
85 <subsection>
86 <title>Introduction</title>
87 <body>
88
89 <p>
90 Manually configuring a kernel is often seen as the most difficult procedure a
91 Linux user ever has to perform. Nothing is less true -- after configuring a
92 couple of kernels you don't even remember that it was difficult ;)
93 </p>
94
95 <p>
96 However, one thing <e>is</e> true: you must know your system when you
97 configuring a kernel manually. Most information can be gathered by emerging
98 pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now
99 be able to use <c>lspci</c> within the chrooted environment. You may safely
100 ignore any <e>pcilib</e> warnings (like pcilib: cannot open
101 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
102 <c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same.
103 You can also run <c>lsmod</c> to see what kernel modules the Installation CD
104 uses (it might provide you with a nice hint on what to enable).
105 </p>
106
107 <pre caption="Invoking menuconfig">
108 # <i>cd /usr/src/linux</i>
109 <comment>Important: In case you are in 32-bit userland, you must edit the top
110 level Makefile in /usr/src/linux and change the CROSS_COMPILE option to
111 CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run
112 make menuconfig or it may result in kernel compilation problems.</comment>
113 # <i>make menuconfig</i>
114 </pre>
115
116 <p>
117 You will be greeted with several configuration sections. We'll first
118 list some options you must activate (otherwise Gentoo will not function,
119 or not function properly without additional tweaks).
120 </p>
121
122 </body>
123 </subsection>
124 <subsection>
125 <title>Activating Required Options</title>
126 <body>
127
128 <p>
129 First of all, activate the use of development and experimental
130 code/drivers. You need this, otherwise some very important code/drivers
131 won't show up:
132 </p>
133
134 <pre caption="Selecting experimental code/drivers, General setup">
135 Code maturity level options ---&gt;
136 [*] Prompt for development and/or incomplete code/drivers
137 </pre>
138
139 <p>
140 Now go to <c>File Systems</c> and select support for the filesystems you use.
141 <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
142 able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc file
143 system</c>, and <c>/dev/pts file system for Unix98 PTYs</c>:
144 </p>
145
146 <pre caption="Selecting necessary file systems">
147 File systems ---&gt;
148 [*] Virtual memory file system support (former shm fs)
149 [*] /proc file system support
150 [*] /dev/pts file system for Unix98 PTYs
151
152 <comment>(Select one or more of the following options as needed by your system)</comment>
153 &lt;*&gt; Reiserfs support
154 &lt;*&gt; Ext3 journalling file system support
155 &lt;*&gt; JFS filesystem support
156 &lt;*&gt; Second extended fs support
157 &lt;*&gt; XFS filesystem support
158 </pre>
159
160 <note>
161 You will find some of the mentioned options under <c>Pseudo
162 filesystems</c> which is a subpart of <c>File systems</c>.
163 </note>
164
165 <p>
166 If you are using PPPoE to connect to the Internet or you are using a
167 dial-up modem, you will need the following options in the kernel (you
168 will find the mentioned options under <c>Networking support</c> which is
169 a subpart of <c>Device Drivers</c>):
170 </p>
171
172 <pre caption="Selecting PPPoE necessary drivers">
173 Network device 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 <c>ppp</c>
182 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 When you're done configuring your kernel, continue with <uri
201 link="#compiling">Compiling and Installing</uri>.
202 </p>
203
204 </body>
205 </subsection>
206 <subsection id="compiling">
207 <title>Compiling and Installing</title>
208 <body>
209
210 <p>
211 Now that your kernel is configured, it is time to compile and install it. Exit
212 the configuration and start the compilation process:
213 </p>
214
215 <pre caption="Compiling the kernel">
216 (Apple/IBM) # <i>make &amp;&amp; make modules_install</i>
217 </pre>
218
219 <p>
220 When the kernel has finished compiling, copy the kernel image to
221 <path>/boot</path>. Remember to replace <path>&lt;kernel-version&lt;</path>
222 with your actual kernel version:
223 </p>
224
225 <pre caption="Installing the kernel">
226 (Apple/IBM) # <i>cp vmlinux /boot/&lt;kernel-version&gt;</i>
227 </pre>
228
229 <p>
230 Now continue with <uri link="#kernel_modules">Configuring the Modules</uri>.
231 </p>
232
233 </body>
234 </subsection>
235 </section>
236 <section id="kernel_modules">
237 <title>Configuring the Modules</title>
238 <body>
239
240 <p>
241 You should list the modules you want automatically loaded in
242 <path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra
243 options to the modules too if you want.
244 </p>
245
246 <p>
247 To view all available modules, run the following command:
248 </p>
249
250 <pre caption="Viewing all available modules">
251 # <i>modprobe -l</i>
252 </pre>
253
254 <p>
255 For instance, to automatically load the <c>3c59x.ko</c> module, edit the
256 <path>kernel-2.6</path> file and enter the module name in it.
257 </p>
258
259 <pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
260 # <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
261 </pre>
262
263 <pre caption="/etc/modules.autoload.d/kernel-2.6">
264 3c59x
265 </pre>
266
267 <p>
268 Continue the installation with <uri link="?part=1&amp;chap=8">Configuring
269 your System</uri>.
270 </p>
271
272 </body>
273 </section>
274 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20