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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.56 - (hide annotations) (download) (as text)
Sat Apr 12 12:31:33 2014 UTC (5 months, 2 weeks ago) by swift
Branch: MAIN
CVS Tags: HEAD
Changes since 1.55: +3 -3 lines
File MIME type: application/xml
Fix bug #506140 - PPC64, not PPC, thanks to Vladimir Romanov

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 jkt 1.28 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 swift 1.1
7 swift 1.56 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v 1.55 2014/04/12 12:29:10 swift Exp $ -->
8 swift 1.1
9     <sections>
10 swift 1.10
11 nightmorph 1.42 <abstract>
12     You can install Gentoo in many ways. This chapter explains how to install
13     Gentoo using the minimal Installation CD.
14     </abstract>
15    
16 swift 1.56 <version>24</version>
17 swift 1.54 <date>2014-04-12</date>
18 swift 1.10
19 swift 1.1 <section>
20     <title>Hardware Requirements</title>
21     <subsection>
22     <title>Introduction</title>
23     <body>
24    
25     <p>
26     Before we start, we first list what hardware requirements you need to
27 swift 1.14 successfully install Gentoo on your box.
28 swift 1.1 </p>
29    
30     </body>
31     </subsection>
32     <subsection>
33 swift 1.14 <title>Hardware Requirements</title>
34 swift 1.1 <body>
35    
36 swift 1.14 <table>
37     <tr>
38     <th>CPU</th>
39     <ti>Any PowerPC64 CPU</ti>
40     </tr>
41     <tr>
42     <th>Systems</th>
43     <ti>
44 rane 1.23 IBM RS/6000s, Power Macintosh G5, IBM pSeries and IBM iSeries
45 swift 1.14 </ti>
46     </tr>
47     <tr>
48     <th>Memory</th>
49     <ti>64 MB</ti>
50     </tr>
51     <tr>
52     <th>Diskspace</th>
53     <ti>1.5 GB (excluding swap space)</ti>
54     </tr>
55     <tr>
56     <th>Swap space</th>
57     <ti>At least 256 MB</ti>
58     </tr>
59     </table>
60    
61 swift 1.1 <p>
62 swift 1.14 For a full list of supported systems, please go to
63 nightmorph 1.40 <uri>http://penguinppc.org/about/intro.php#hardware</uri>.
64 swift 1.1 </p>
65    
66     </body>
67     </subsection>
68     </section>
69 nightmorph 1.37
70 swift 1.14 <!-- START -->
71 swift 1.1 <section>
72 swift 1.54 <title>The Gentoo Installation CD</title>
73 swift 1.1 <subsection>
74 swift 1.54 <title>Gentoo Minimal Installation CD</title>
75 swift 1.1 <body>
76    
77     <p>
78 swift 1.54 The <e>Minimal Installation CD</e> is a bootable CD which contains a
79     self-sustained Gentoo environment. It allows you to boot Linux from the CD.
80 swift 1.1 During the boot process your hardware is detected and the appropriate drivers
81 swift 1.54 are loaded. The CD is maintained by Gentoo developers and allows you to install
82     Gentoo with an active Internet connection.
83 swift 1.1 </p>
84    
85     <p>
86 nightmorph 1.42 The Minimal Installation CD is called <c><keyval id="min-cd-name"/></c> and
87 swift 1.54 takes up around <keyval id="min-cd-size"/> MB of diskspace.
88 swift 1.1 </p>
89 neysx 1.27
90     </body>
91     </subsection>
92     <subsection>
93 swift 1.25 <title>The Stage3 Tarball</title>
94     <body>
95    
96     <p>
97 nightmorph 1.42 A stage3 tarball is an archive containing a minimal Gentoo environment,
98     suitable to continue the Gentoo installation using the instructions in this
99     manual. Previously, the Gentoo Handbook described the installation using one of
100     three stage tarballs. While Gentoo still offers stage1 and stage2 tarballs, the
101 swift 1.25 official installation method uses the stage3 tarball. If you are interested in
102     performing a Gentoo installation using a stage1 or stage2 tarball, please read
103 swift 1.52 the Gentoo FAQ on <uri link="https://wiki.gentoo.org/wiki/FAQ#How_do_I_Install_Gentoo_Using_a_Stage1_or_Stage2_Tarball.3F">How
104     do I Install Gentoo Using a Stage1 or Stage2 Tarball?</uri>
105 swift 1.25 </p>
106    
107 nightmorph 1.42 <p>
108     Stage3 tarballs can be downloaded from <path><keyval
109     id="release-dir"/>current-stage3/</path> on any of the <uri
110     link="/main/en/mirrors.xml">Official Gentoo Mirrors</uri> and are not provided
111     on the LiveCD.
112     </p>
113    
114 swift 1.25 </body>
115     </subsection>
116 nightmorph 1.33 <subsection>
117     <title>Choosing a userland</title>
118     <body>
119    
120     <p>
121 nightmorph 1.42 On PPC64, the kernel is 64-bit and the <e>userland</e> can be 32-bit or 64-bit.
122     The userland is basically the applications you are running, such as <c>bash</c>
123     or <c>firefox</c>. They can be compiled and run in either 64-bit or
124     32-bit modes. The Gentoo/PPC64 team provides both 32-bit and 64-bit userlands,
125     so which one should you use?
126 nightmorph 1.33 </p>
127    
128     <p>
129     You may have heard that 64-bit applications are better, but in fact, 32-bit
130     applications take up slightly less memory and often run a little bit faster than
131     64-bit applications.
132     </p>
133    
134     <p>
135     You really only need 64-bit applications when you need more memory than a 32-bit
136 nightmorph 1.42 userland allows, or if you do a lot of 64-bit number crunching. If you have 4GB
137     or more of memory or you run scientific applications, you should choose the
138     64-bit userland. Otherwise, choose the 32-bit userland, as it is recommended by
139     the Gentoo/PPC64 developers.
140 nightmorph 1.33 </p>
141    
142     <p>
143     Additionally, the 32-bit userland has been available in Portage longer than the
144     64-bit userland has. This means that there are more applications tested in the
145     32-bit userland that just work "out of the box." Many applications compiled for
146     the 64-bit userland may be just as stable as the 32-bit version, but they
147     haven't been tested yet. Though testing isn't difficult to do, it can be
148     annoying and time consuming if you want to use many untested 64-bit
149     applications. Also, some programs just won't run in the 64-bit userland until
150 swift 1.51 their code is fixed, such as LibreOffice.
151 nightmorph 1.33 </p>
152    
153     </body>
154     </subsection>
155 swift 1.1 </section>
156 swift 1.14 <!-- STOP -->
157 swift 1.1 <section>
158 swift 1.17 <title>Download, Burn and Boot a Gentoo Installation CD</title>
159 swift 1.1 <subsection>
160 swift 1.54 <title>Downloading and Burning the Installation CD</title>
161 swift 1.1 <body>
162    
163     <p>
164 swift 1.17 You have chosen to use a Gentoo Installation CD. We'll first start by
165     downloading and burning the chosen Installation CD. We previously discussed the
166 swift 1.54 Installation CD, but where can you find it?
167 swift 1.14 </p>
168    
169     <p>
170 swift 1.54 You can download the Installation CD from one of our <uri
171     link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in
172 nightmorph 1.42 the <path><keyval id="release-dir"/>current-iso/</path> directory.
173 swift 1.1 </p>
174    
175     <p>
176 swift 1.54 Inside that directory you'll find the ISO file. This is a full CD image
177 swift 1.1 which you can write on a CD-R.
178     </p>
179    
180     <p>
181 nightmorph 1.42 In case you wonder if your downloaded file is corrupted or not, you can check
182 swift 1.47 its SHA-2 checksum and compare it with the SHA-2 checksum we provide (such as
183     <path><keyval id="min-cd-name"/>.DIGESTS</path>). You can check the SHA-2
184     checksum with the <c>sha512sum</c> tool under Linux/Unix or <uri
185 swift 1.49 link="http://www.sinf.gr/en/hashcalc.html">Checksums calculator</uri> for Windows.
186 swift 1.1 </p>
187    
188 swift 1.53 <note>
189     The tool will attempt to verify the checksums in the list, even if the checksum
190     is made with a different algorithm. Therefore, the output of the command might
191     give both success (for SHA checksums) and failures (for other checksums). At
192     least one OK needs to be provided for each file.
193     </note>
194    
195 swift 1.48 <pre caption="Verifying the SHA-2 checksum">
196     $ <i>sha512sum -c &lt;downloaded iso.DIGESTS&gt;</i>
197     </pre>
198    
199     <note>
200     If you get the message that no properly formatted SHA checksum was found, take a
201     look at the DIGESTS file yourself to see what the supported checksums are.
202     </note>
203    
204 swift 1.1 <p>
205 swift 1.14 Another way to check the validity of the downloaded file is to use GnuPG to
206     verify the cryptographic signature that we provide (the file ending with
207 swift 1.46 <path>.asc</path>). Download the signature file and obtain the public keys whose
208     key ids can be found on the <uri link="/proj/en/releng/index.xml">release
209     engineering project site</uri>.
210 swift 1.1 </p>
211    
212 swift 1.14 <pre caption="Obtaining the public key">
213 swift 1.46 <comment>(... Substitute the key ids with those mentioned on the release engineering site ...)</comment>
214 swift 1.44 $ <i>gpg --keyserver subkeys.pgp.net --recv-keys 96D8BF6D 2D182910 17072058</i>
215 swift 1.1 </pre>
216    
217     <p>
218 swift 1.14 Now verify the signature:
219 swift 1.1 </p>
220    
221 nightmorph 1.42 <pre caption="Verify the files">
222     $ <i>gpg --verify &lt;downloaded iso.DIGESTS.asc&gt;</i>
223 swift 1.48 $ <i>sha512sum -c &lt;downloaded iso.DIGESTS.asc&gt;</i>
224 swift 1.14 </pre>
225 swift 1.1
226     <p>
227     To burn the downloaded ISO(s), you have to select raw-burning. How you
228 swift 1.55 do this is highly program-dependent. We will discuss <c>cdrecord</c>,
229     <c>K3B</c>, <c>Disk Utility</c> and <c>Disk Copy</c> here; more information can
230     be found in our <uri
231 swift 1.52 link="https://wiki.gentoo.org/wiki/FAQ#How_do_I_burn_an_ISO_file.3F">Gentoo FAQ</uri>.
232 swift 1.1 </p>
233    
234     <ul>
235     <li>
236 swift 1.50 With cdrecord, you simply type <c>cdrecord dev=/dev/sr0 &lt;downloaded iso
237     file&gt;</c> (replace <path>/dev/sr0</path> with your CD-RW drive's
238 swift 1.16 device path).
239 swift 1.1 </li>
240     <li>
241 nightmorph 1.35 With K3B, select <c>Tools</c> &gt; <c>Burn CD Image</c>. Then you can locate
242     your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>.
243 swift 1.1 </li>
244 swift 1.7 <li>
245     With Mac OS X Panther, launch <c>Disk Utility</c> from
246     <path>Applications/Utilities</path>, select <c>Open</c> from the
247     <c>Images</c> menu, select the mounted disk image in the main window and
248     select <c>Burn</c> in the <c>Images</c> menu.
249     </li>
250     <li>
251     With Mac OS X Jaguar, launch <c>Disk Copy</c> from
252     <path>Applications/Utilities</path>, select <c>Burn Image</c> from the
253     <c>File</c> menu, select the ISO and click the <c>Burn</c> button.
254     </li>
255 swift 1.1 </ul>
256    
257     </body>
258     </subsection>
259     <subsection>
260 swift 1.17 <title>Default: Booting the Installation CD on an Apple/IBM</title>
261 swift 1.1 <body>
262    
263     <p>
264 swift 1.17 Place the Installation CD in the CD-ROM and reboot the system. Hold down the
265     'C' key at bootup. You will be greeted by a friendly welcome message and a
266     <e>boot:</e> prompt at the bottom of the screen.
267 swift 1.1 </p>
268    
269     <p>
270     You are also able to tweak some kernel options at this prompt. The following
271     table lists the available boot options you can add:
272     </p>
273    
274     <table>
275     <tr>
276     <th>Boot Option</th>
277     <th>Description</th>
278     </tr>
279     <tr>
280     <ti><c>video</c></ti>
281     <ti>
282     This option takes one of the following vendor-specific tags:
283 nightmorph 1.32 <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c>, <c>nvidiafb</c>
284     or <c>ofonly</c>. You can follow this tag with the resolution and
285 nightmorph 1.33 refreshrate you want to use. For instance
286     <c>video=radeonfb:1280x1024@75</c>. If you are uncertain what to choose,
287     <c>ofonly</c> will most certainly work.
288 swift 1.1 </ti>
289     </tr>
290     <tr>
291     <ti><c>nol3</c></ti>
292     <ti>
293 nightmorph 1.33 Disables level 3 cache on some powerbooks (needed for at least the 17")
294 swift 1.1 </ti>
295     </tr>
296     <tr>
297     <ti><c>debug</c></ti>
298     <ti>
299     Enables verbose booting, spawns an initrd shell that can be used to debug
300 swift 1.17 the Installation CD
301 swift 1.1 </ti>
302     </tr>
303     <tr>
304     <ti><c>sleep=X</c></ti>
305     <ti>
306     Wait X seconds before continuing; this can be needed by some very old SCSI
307     CD-ROMs which don't speed up the CD quick enough
308     </ti>
309     </tr>
310     <tr>
311     <ti><c>bootfrom=X</c></ti>
312     <ti>
313     Boot from a different device
314     </ti>
315     </tr>
316 nightmorph 1.37 <tr>
317     <ti><c>dosshd</c></ti>
318     <ti>Starts <c>sshd</c>. Useful for unattended installs.</ti>
319     </tr>
320     <tr>
321     <ti><c>passwd=foo</c></ti>
322     <ti>
323     Sets whatever is after the = as the root password. Use with <c>dosshd</c>
324     for remote installs.
325     </ti>
326     </tr>
327 swift 1.1 </table>
328    
329     <p>
330     At this prompt, hit enter, and a complete Gentoo Linux environment will be
331     loaded from the CD. Continue with <uri link="#booted">And When You're
332     Booted...</uri>.
333     </p>
334    
335     </body>
336     </subsection>
337     <subsection>
338     <title>IBM pSeries</title>
339     <body>
340    
341     <p>
342 neysx 1.30 The CD should autoboot on your pSeries box, but sometimes it does not. In that
343     case, you have to set up your cdrom as a bootable device in the multi-boot
344     menu. If you start your machine with a monitor and a keyboard attached, you can
345     reach the multi-boot menu pressing the F1 key on startup. But if you start your
346     machine using the serial console, then you have to press <c>1</c>. Press the
347     key when you see the beginning of the following line on the serial console:
348 swift 1.1 </p>
349    
350 neysx 1.30 <pre caption="Hit the '1' key when this line appears">
351     memory keyboard network scsi speaker
352     </pre>
353    
354 swift 1.1 <p>
355 nightmorph 1.36 The other option is to jump into Open Firmware and do it from there:
356 swift 1.1 </p>
357 neysx 1.30
358     <ol>
359     <li>
360 nightmorph 1.36 Boot into Open Firmware: same procedure as getting into multi-boot
361 neysx 1.30 (described a few lines above), but use F8 and 8 instead of F1 and 1.
362     </li>
363     <li>Run the command 0> boot cdrom:1,yaboot</li>
364     <li>Stand back and enjoy!</li>
365     </ol>
366    
367     <note>
368 nightmorph 1.36 If you get something like the following output, then Open Firmware isn't set up
369 neysx 1.30 correctly. Please use the multi-boot option described above.
370     </note>
371    
372 nightmorph 1.36 <pre caption="Output if Open Firmware is not set up correctly">
373 neysx 1.30 0 > boot cdrom:1,yaboot
374     ok
375     0 >
376     </pre>
377 swift 1.1
378     </body>
379     </subsection>
380     <subsection id="booted">
381     <title>And When You're Booted...</title>
382     <body>
383    
384     <p>
385     You will be greeted by a root ("#") prompt on the current console. You can also
386     switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get
387     back to the one you started on by pressing Alt-fn-F1.
388     </p>
389    
390     <p>
391     If you are installing Gentoo on a system with a non-US keyboard, use
392     <c>loadkeys</c> to load the keymap for your keyboard. To list the available
393     keymaps, execute <c>ls /usr/share/keymaps/i386</c>.
394     </p>
395    
396     <pre caption="Listing available keymaps">
397 swift 1.56 <comment>(PPC64 uses x86 keymaps on most systems)</comment>
398 swift 1.1 # <i>ls /usr/share/keymaps/i386</i>
399     </pre>
400    
401     <p>
402     Now load the keymap of your choice:
403     </p>
404    
405     <pre caption="Loading a keymap">
406     # <i>loadkeys be-latin1</i>
407     </pre>
408    
409     <p>
410     Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>.
411     </p>
412    
413     </body>
414     </subsection>
415    
416     <subsection>
417 nightmorph 1.38 <include href="hb-install-bootconfig.xml"/>
418 swift 1.2 </subsection>
419 swift 1.1
420     </section>
421     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20