/[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.26 - (show annotations) (download) (as text)
Mon Feb 26 08:54:53 2007 UTC (10 years, 10 months ago) by nightmorph
Branch: MAIN
Changes since 1.25: +5 -9 lines
File MIME type: application/xml
removed USE=symlink by request of dsd as part of the USE flag removal from all kernel sources, bug 167703. also further vanilla-sources removals as it's unsupported.

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

  ViewVC Help
Powered by ViewVC 1.1.20