Gentoo Archives: gentoo-doc-cvs

From: Joseph Jezak <josejx@××××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: hb-install-ppc-kernel.xml
Date: Mon, 02 Apr 2007 02:41:14
Message-Id: E1HYCTb-0007Wr-P5@stork.gentoo.org
1 josejx 07/04/02 02:40:59
2
3 Modified: hb-install-ppc-kernel.xml
4 Log:
5 Sync'd to draft version.
6
7 Revision Changes Path
8 1.3 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?rev=1.3&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?rev=1.3&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?r1=1.2&r2=1.3
13
14 Index: hb-install-ppc-kernel.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml,v
17 retrieving revision 1.2
18 retrieving revision 1.3
19 diff -u -r1.2 -r1.3
20 --- hb-install-ppc-kernel.xml 2 Apr 2007 00:49:18 -0000 1.2
21 +++ hb-install-ppc-kernel.xml 2 Apr 2007 02:40:59 -0000 1.3
22 @@ -4,12 +4,12 @@
23 <!-- The content of this document is licensed under the CC-BY-SA license -->
24 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
25
26 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml,v 1.2 2007/04/02 00:49:18 nightmorph Exp $ -->
27 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml,v 1.3 2007/04/02 02:40:59 josejx Exp $ -->
28
29 <sections>
30
31 <version>8.0</version>
32 -<date>2007-03-12</date>
33 +<date>2007-04-01</date>
34
35 <section>
36 <title>Timezone</title>
37 @@ -33,7 +33,7 @@
38 </body>
39 </section>
40 <section>
41 -<title>Installing the Sources</title>
42 +<title>Installing the Kernel Sources</title>
43 <subsection>
44 <title>Choosing a Kernel</title>
45 <body>
46 @@ -41,17 +41,17 @@
47 <p>
48 The core around which all distributions are built is the Linux kernel. It is the
49 layer between the user programs and your system hardware. Gentoo provides its
50 -users several possible kernel sources. A full listing with description is
51 -available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
52 -Guide</uri>.
53 +users several possible kernels to choose from. A full listing with description
54 +is available at the
55 +<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>.
56 </p>
57
58 <p>
59 -We suggest using <c>gentoo-sources</c> on PPC, which is a 2.6 kernel.
60 +We suggest using <c>gentoo-sources</c> on PPC, which is a recent 2.6 kernel.
61 </p>
62
63 <pre caption="Installing a kernel source">
64 -# <i>emerge gentoo-sources</i>
65 +# <i>emerge --usepkg gentoo-sources</i>
66 </pre>
67
68 <p>
69 @@ -67,10 +67,10 @@
70 </pre>
71
72 <p>
73 -Now it is time to configure and compile your kernel source. You
74 -can use <c>genkernel</c> for this, which will build a generic kernel as used
75 -by the Installation CD. We explain the "manual" configuration first though, as
76 -it is the best way to optimize your environment.
77 +Now it is time to configure and compile your kernel source. You can use
78 +<c>genkernel</c> for this, which will build a generic kernel as used by the
79 +Installation CD. We explain the "manual" configuration first though, as it is
80 +a more efficient configuration.
81 </p>
82
83 <p>
84 @@ -92,29 +92,29 @@
85 <p>
86 Manually configuring a kernel is often seen as the most difficult procedure a
87 Linux user ever has to perform. Nothing is less true -- after configuring a
88 -couple of kernels you don't even remember that it was difficult ;)
89 +few kernels you won't even remember that it was difficult ;)
90 </p>
91
92 <p>
93 However, one thing <e>is</e> true: you must know your system when you start
94 configuring a kernel manually. Most information can be gathered by emerging
95 -pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now
96 -be able to use <c>lspci</c> within the chrooted environment. You may safely
97 -ignore any <e>pcilib</e> warnings (like pcilib: cannot open
98 -/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
99 -<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same.
100 -You can also run <c>lsmod</c> to see what kernel modules the Installation CD
101 -uses (it might provide you with a nice hint on what to enable). Another place
102 -to look for clues as to what components to enable is to check the kernel
103 -message logs from the successful boot that got you this far. Type <c>dmesg</c>
104 -to see the kernel messages.
105 +pciutils (<c>emerge --usepkg pciutils</c>) which contains the program
106 +<c>lspci</c>. You will now be able to use <c>lspci</c> within the chrooted
107 +environment. You may safely ignore any <e>pcilib</e> warnings (such as pcilib:
108 +cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively,
109 +you can run <c>lspci</c> from a <e>non-chrooted</e> environment. The results
110 +are the same. You can also run <c>lsmod</c> to see what kernel modules the
111 +Installation CD uses (it might provide you with a nice hint on what to enable).
112 +Another place to look for clues as to what components to enable is to check the
113 +kernel message logs from the successful boot that got you this far. Type
114 +<c>dmesg</c> to see these kernel messages.
115 </p>
116
117 <p>
118 Now, go to your kernel source directory, it's time to configure your kernel.
119 -It is recommended that you add the default settings to your configuration by
120 -first running <c>make pmac32_defconfig</c>. After the default configuration has
121 -been generated, run <c>make menuconfig</c> which will fire up an ncurses-based
122 +Start by configuring a kernel that will boot on most 32 Bit PowerPC machines
123 +by first running <c>make pmac32_defconfig</c>. After the default configuration
124 +has been generated, run <c>make menuconfig</c> to start an ncurses-based
125 configuration menu.
126 </p>
127
128 @@ -158,6 +158,7 @@
129 <pre caption="Selecting necessary file systems">
130 File systems ---&gt;
131 Pseudo Filesystems ---&gt;
132 +<comment>(/proc may already be forced on by your configuration, if so, you'll see --- instead)</comment>
133 [*] /proc file system support
134 [*] Virtual memory file system support (former shm fs)
135 Partition Types ---&gt;
136 @@ -179,7 +180,9 @@
137
138 <pre caption="Activating HFS support">
139 File Systems ---&gt;
140 - [*] HFS Support
141 + Miscellaneous filesystems ---&gt;
142 + &lt;*&gt; Apple Macintosh file system support
143 + &lt;*&gt; Apple Extended HFS file system support
144 </pre>
145
146 <p>
147 @@ -189,16 +192,16 @@
148
149 <pre caption="Selecting PPPoE necessary drivers">
150 Device Drivers ---&gt;
151 - Networking support ---&gt;
152 + Network device support ---&gt;
153 &lt;*&gt; PPP (point-to-point protocol) support
154 &lt;*&gt; PPP support for async serial ports
155 &lt;*&gt; PPP support for sync tty ports
156 </pre>
157
158 <p>
159 -The two compression options won't harm but are not definitely needed, neither
160 -does the <c>PPP over Ethernet</c> option, that might only be used by
161 -<c>rp-pppoe</c> when configured to do kernel mode PPPoE.
162 +The two compression options won't harm but are not always needed. The
163 +<c>PPP over Ethernet</c> option might only be used by <c>rp-pppoe</c> when
164 +configured to perform kernel mode PPPoE.
165 </p>
166
167 <p>
168 @@ -207,15 +210,30 @@
169 the BMAC driver.
170 </p>
171
172 +<pre caption="Selecting the network driver">
173 +Device Drivers ---&gt;
174 + Network device support ---&gt;
175 + Ethernet (10 or 100Mbit) ---&gt;
176 + [*] Ethernet (10 or 100Mbit)
177 + &lt;*&gt; Generic Media Independent Interface device support
178 + &lt;*&gt; MACE (Power Mac ethernet) support
179 + &lt;*&gt; BMAC (G3 ethernet) support
180 + &lt;*&gt; Sun GEM support
181 +</pre>
182 +
183 <p>
184 -At this time, kernel preemption is still unstable on PPC and may cause
185 +At this time, full kernel preemption may still be unstable on PPC and may cause
186 compilation failures and random segfaults. It is <e>strongly</e> suggested
187 -that you do not use this feature.
188 +that you do not use this featurea. Both <e>Voluntary Preemption</e> and
189 +<e>No Forced Preemption</e> should be safe.
190 </p>
191
192 <pre caption="Ensure the Preemptible Kernel Option is Off">
193 Kernel options ---&gt;
194 - Preemption Model (No Forced Preemption (Server))
195 +<comment>(Select One)</comment>
196 + Preemption Model
197 + (X) No Forced Preemption (Server)
198 + (X) Voluntary Kernel Preemption (Desktop)
199 </pre>
200
201 <p>
202 @@ -268,8 +286,8 @@
203 <note>
204 If you select more than one framebuffer device, it may default to a less than
205 optimal driver. Either use only one framebuffer device or specify which
206 -to use by passing the driver to use to the kernel on boot such as
207 -<c>video=radeonfb</c>.
208 +to use by passing the driver to use to the kernel on boot by appending a video
209 +line such as: <c>video=radeonfb</c>.
210 </note>
211
212 <p>
213 @@ -285,7 +303,7 @@
214
215 <p>
216 Now that your kernel is configured, it is time to compile and install it. Exit
217 -the configuration and run the commands which will compile the kernel:
218 +the configuration menu and run the following commands:
219 </p>
220
221 <pre caption="Compiling the kernel">
222 @@ -301,11 +319,11 @@
223
224 <p>
225 Yaboot and BootX expect to use an uncompressed kernel unlike many other
226 -bootloaders. The uncompressed kernel is called vmlinux and it is placed in
227 -<path>/usr/src/linux</path> after the kernel has finished compiling. If you are
228 +bootloaders. The uncompressed kernel is called vmlinux and it is placed in
229 +<path>/usr/src/linux</path> after the kernel has finished compiling. If you are
230 using a Pegasos machine, the Pegasos firmware requires a compressed kernel
231 -called zImage.chrp which can be found in
232 -<path>/usr/src/linux/arch/ppc/boot/images</path>.
233 +called zImage which can be found in
234 +<path>/usr/src/linux/arch/powerpc/boot/images</path>.
235 </p>
236
237 <pre caption="Installing the kernel">
238 @@ -314,7 +332,7 @@
239 <comment>(Apple/IBM)</comment>
240 # <i>cp vmlinux /boot/&lt;kernel-version&gt;</i>
241 <comment>(Pegasos)</comment>
242 -# <i>cp arch/ppc/boot/images/zImage.chrp /boot/&lt;kernel-version&gt;</i>
243 +# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name"/></i>
244 </pre>
245
246 <p>
247 @@ -333,8 +351,8 @@
248
249 <p>
250 You should list the modules you want automatically loaded in
251 -<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
252 -the modules too if you want.
253 +<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
254 +the modules if required.
255 </p>
256
257 <p>
258 @@ -348,8 +366,8 @@
259 </pre>
260
261 <p>
262 -For instance, to automatically load the <c>3c59x.o</c> module, edit the
263 -<path>kernel-2.6</path> file and enter the module name in it.
264 +For instance, to automatically load the <c>3c59x</c> module, edit the
265 +<path>kernel-2.6</path> file and add the module to it, one module on a line.
266 </p>
267
268 <pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
269 @@ -410,10 +428,10 @@
270
271 <p>
272 Before compiling your sources, the fstab needs a slight adjustment. The rest of
273 -the fstab will be completed during a later step, so don't worry about the
274 +the fstab will be completed during a later step, so don't worry about the
275 details now. If you did not create a separate boot partition (NOT bootstrap,
276 -that's different), remove the line referencing /boot from
277 -<path>/etc/fstab</path>. This will need to be done on most Apple computers.
278 +that's different), remove the line referencing <path>/boot</path> from
279 +<path>/etc/fstab</path>. This will need to be done on most Apple computers.
280 </p>
281
282 <pre caption="Removing /boot from /etc/fstab on machines without a boot partition">
283 @@ -435,7 +453,7 @@
284 or ext3 as filesystem you might need to manually configure your kernel using
285 <c>genkernel --menuconfig all</c> and add support for your
286 filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or
287 -LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as arguments as
288 +LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as an argument as
289 well.
290 </p>
291
292 @@ -451,7 +469,7 @@
293 Once <c>genkernel</c> completes, a kernel, full set of modules and
294 <e>initial root disk</e> (initrd) will be created. We will use the kernel
295 and initrd when configuring a boot loader later in this document. Write
296 -down the names of the kernel and initrd as you will need it when writing
297 +down the names of the kernel and initrd as you will need them when writing
298 the bootloader configuration file. The initrd will be started immediately after
299 booting to perform hardware autodetection (just like on the Installation CD)
300 before your "real" system starts up. Be sure to also copy down the required
301 @@ -468,6 +486,5 @@
302
303 </body>
304 </section>
305 -
306 </sections>
307
308
309
310
311 --
312 gentoo-doc-cvs@g.o mailing list