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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.27 - (hide annotations) (download) (as text)
Fri Jul 13 08:40:58 2007 UTC (7 years, 5 months ago) by nightmorph
Branch: MAIN
Changes since 1.26: +3 -3 lines
File MIME type: application/xml
made Open Firmware usage consistent for all handbooks and translations, as suggested by grahl and rane on IRC, and approved by JoseJX. s/openfirmware/Open Firmware/g, so no revbump.

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.17 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 swift 1.1
7 nightmorph 1.27 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml,v 1.26 2007/05/07 18:11:41 nightmorph Exp $ -->
8 swift 1.1
9     <sections>
10 swift 1.5
11 nightmorph 1.26 <version>8.0</version>
12     <date>2007-05-07</date>
13 swift 1.5
14 swift 1.1 <section>
15     <title>Making your Choice</title>
16     <subsection>
17     <title>Introduction</title>
18     <body>
19    
20     <p>
21     Now that your kernel is configured and compiled and the necessary system
22     configuration files are filled in correctly, it is time to install a
23     program that will fire up your kernel when you start the system. Such a
24     program is called a <e>bootloader</e>.
25     </p>
26    
27     <p>
28 jkt 1.16 On Linux/PPC64 we have only yaBoot as a bootloader until grub2 is
29 swift 1.1 finished.
30     </p>
31    
32     </body>
33     </subsection>
34     </section>
35     <section id="yaboot">
36     <title>Using yaBoot</title>
37     <subsection>
38     <title>Introduction</title>
39     <body>
40    
41     <impo>
42 fox2mike 1.23 If you are using a 64-bit userland, you must use the <c>yaboot-static</c>
43     package because yaboot cannot be compiled as a 64-bit application. The 32-bit
44     userlands should use the regular yaboot package.
45 swift 1.1 </impo>
46    
47     <p>
48 nightmorph 1.26 There are two ways to configure yaBoot for your system. You can use the new and
49     improved <c>yabootconfig</c> included with <path>yaboot-1.3.8-r1</path> and
50     later to automatically set up yaboot. If for some reason you do not want to run
51     <c>yabootconfig</c> to automatically set up <path>/etc/yaboot.conf</path> or you
52     are installing Gentoo on a G5 (on which <c>yabootconfig</c> does not always
53     work), you can just edit the sample file already installed on your system.
54 swift 1.1 </p>
55    
56     <impo>
57     yabootconfig/ybin won't work on IBM. You have to install yaboot another way:
58 swift 1.14 <uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri>
59 swift 1.1 </impo>
60    
61 swift 1.13 <note>
62     If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a
63     kernel parameter. JFS must be able to replay its log in read-only mode before it
64     gets mounted read-write.
65     </note>
66    
67 swift 1.1 <ul>
68     <li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li>
69     <li>
70     <uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri>
71     </li>
72     </ul>
73    
74     </body>
75     </subsection>
76     <subsection id="yabootconfig">
77     <title>Default: Using yabootconfig</title>
78     <body>
79    
80     <p>
81     <c>yabootconfig</c> will auto-detect the partitions on your machine and will
82 swift 1.4 set up dual and triple boot combinations with Linux, Mac OS, and Mac OS
83 swift 1.1 X.
84     </p>
85    
86     <p>
87     To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and
88     <path>/etc/fstab</path> must be configured with your Linux partitions. Both of
89     these should have been done already in the steps above. To start, ensure that
90     you have the latest version of yaboot installed by running <c>emerge --update
91     yaboot-static</c>. This is necessary as the latest version will be available via
92     Portage, but it may not have made it into the stage files.
93     </p>
94    
95     <pre caption = "Installing yaboot-static">
96 fox2mike 1.23 <comment>(For 64-bit users)</comment>
97 swift 1.1 # <i>emerge --update yaboot-static</i>
98 fox2mike 1.23
99     <comment>(For 32-bit users)</comment>
100     # <i>emerge yaboot</i>
101 swift 1.1 </pre>
102    
103     <p>
104 nightmorph 1.26 Now run <c>yabootconfig</c>. The program will run and it will confirm the
105     location of the bootstrap partition. Type <c>Y</c> if it is correct. If not,
106     double check <path>/etc/fstab</path>. yabootconfig will then scan your system
107     setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you.
108     <c>mkofboot</c> is used to format the bootstrap partition, and install the
109     yaboot configuration file into it.
110 swift 1.1 </p>
111    
112     <p>
113 nightmorph 1.26 You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you
114     make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot
115     OS), make sure to rerun <c>ybin -v</c> to apply changes to the bootstrap
116     partition.
117 swift 1.1 </p>
118    
119     <p>
120     Now continue with <uri link="#reboot">Rebooting your System</uri>.
121     </p>
122    
123     </body>
124     </subsection>
125     <subsection id="manual_yaboot">
126     <title>Alternative: Manual yaBoot Configuration</title>
127     <body>
128    
129     <p>
130     First make sure you have the latest <c>yaboot-static</c> installed on your
131     system:
132     </p>
133    
134     <pre caption = "Installing yaboot">
135 fox2mike 1.23 <comment>(For 64-bit users)</comment>
136 swift 1.1 # <i>emerge --update yaboot-static</i>
137 fox2mike 1.23
138     <comment>(For 32-bit users)</comment>
139     # <i>emerge yaboot</i>
140 swift 1.1 </pre>
141    
142     <p>
143     Below you find a completed <path>yaboot.conf</path> file. Alter it at
144     will.
145     </p>
146    
147     <pre caption = "/etc/yaboot.conf">
148     <comment>## /etc/yaboot.conf
149     ##
150     ## run: "man yaboot.conf" for details. Do not make changes until you have!!
151     ## see also: /usr/share/doc/yaboot/examples for example configurations.
152     ##
153     ## For a dual-boot menu, add one or more of:
154     ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
155    
156     ## our bootstrap partition:</comment>
157    
158 swift 1.8 boot=/dev/hda2
159 swift 1.1
160 nightmorph 1.27 <comment>## ofboot is the Open Firmware way to specify the bootstrap partition.
161 swift 1.8 ## If this isn't defined, yaboot fails on the G5 and some G4s (unless
162     ## you pass the necessary arguments to the mkofboot/ybin program).
163     ## hd:X means /dev/sdaX (or /dev/hdaX).</comment>
164 swift 1.1
165     ofboot=hd:2
166    
167 nightmorph 1.27 <comment>## hd: is Open Firmware speak for hda</comment>
168 swift 1.1 device=hd:
169    
170     delay=5
171     defaultos=macosx
172     timeout=30
173     install=/usr/lib/yaboot/yaboot
174     magicboot=/usr/lib/yaboot/ofboot
175    
176     <comment>#################
177     ## This section can be duplicated if you have more than one kernel or set of
178 nightmorph 1.26 ## boot options - replace <keyval id="kernel-name"/> with your kernel-version
179 swift 1.1 #################</comment>
180 nightmorph 1.26 image=/boot/<keyval id="kernel-name"/>
181 swift 1.1 label=Linux
182 swift 1.8 root=/dev/hda3
183     partition=3
184 swift 1.1 read-only
185    
186 swift 1.8 macos=hd:13
187     macosx=hd:12
188 swift 1.1 enablecdboot
189     enableofboot
190     </pre>
191    
192     <p>
193 nightmorph 1.26 Once <path>yaboot.conf</path> is set up the way you want it, you run <c>mkofboot
194     -v</c> to install the settings in the bootstrap partition. <e>Don't forget
195     this!</e> Confirm when <c>mkofboot</c> asks you to create a new filesystem.
196 swift 1.8 </p>
197    
198     <p>
199 nightmorph 1.26 If all goes well, and you have the same options as the sample above, your next
200     reboot will give you a simple, five-entry boot menu. If you update your yaboot
201     config later on, you'll just need to run <c>ybin -v</c> to update the bootstrap
202     partition - <c>mkofboot</c> is for initial setup only.
203 swift 1.1 </p>
204    
205     <p>
206     For more information on yaboot, take a look at the <uri
207 nightmorph 1.26 link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For now,
208     continue the installation with <uri link="#reboot">Rebooting your System</uri>.
209 swift 1.1 </p>
210    
211     </body>
212     </subsection>
213     </section>
214     <section id="yaboot-ibm">
215 swift 1.14 <title>Using yaboot on IBM hardware</title>
216 swift 1.1 <body>
217    
218     <p>
219 swift 1.14 On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the
220 neysx 1.18 following steps:
221 swift 1.1 </p>
222    
223     <ul>
224     <li>Install yaboot-static</li>
225 nightmorph 1.26 <li>
226     Run <c>dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX</c> (fill in XX with
227     your disk and partition for the PReP partition; this was in our example
228     <path>/dev/sda1</path>)
229     </li>
230     <li>
231     Next construct your own <path>yaboot.conf</path> file and place into
232     <path>/etc</path>. (Take a look at the config above, look into the man page
233     of yaboot.conf or look at the below <path>yaboot.conf</path> example.)
234     </li>
235     <li>
236     Assuming your boot device in OF is pointing to the harddrive you prep boot
237     partition is on then it'll just work, otherwise at IPL time, go into the
238     multiboot menu and set the boot device to the one with your prep boot
239     partition
240     </li>
241 swift 1.1 <li>That's it!</li>
242     </ul>
243    
244 neysx 1.19 <pre caption="yaboot.conf for IBM hardware">
245 swift 1.11 device=disk:
246     partition=2
247     root=/dev/sda2
248 neysx 1.24 default=linux
249 swift 1.11 timeout=50
250    
251 nightmorph 1.26 image=/boot/<keyval id="kernel-name"/>
252 neysx 1.24 label=linux
253 swift 1.15 append="console=ttyS0,9600"
254     read-only
255 swift 1.11 </pre>
256    
257 swift 1.14 <p>
258 nightmorph 1.26 For POWER4, POWER5, and blade-based hardware where the PReP disk partition and
259     the disk partition that contains your kernel are on the same physical disk, you
260     can use a simplified <path>yaboot.conf</path>. The following should be
261     sufficient:
262 swift 1.14 </p>
263    
264     <pre caption="yaboot.conf for PReP hardware">
265     default = linux
266     timeout = 100
267 nightmorph 1.26 image=/boot/<keyval id="kernel-name"/>
268 swift 1.14 label=linux
269     read-only
270     root = /dev/sda2
271     append="root=/dev/sda2"
272     </pre>
273    
274     <p>
275     To verify that yaboot has been copied to the PReP partition:
276     </p>
277    
278     <pre caption="Verifying the yaboot install on PReP">
279     # <i>dd if=/dev/sda1 count=10 | grep ELF</i>
280     Binary file (standard input) matches
281     10+0 records in
282     10+0 records out
283     </pre>
284    
285     <p>
286     A match signifies that yaboot was installed correctly.
287     </p>
288    
289 swift 1.1 </body>
290     </section>
291 swift 1.2 <section id="reboot">
292 swift 1.1 <title>Rebooting the System</title>
293     <subsection>
294     <body>
295    
296     <p>
297     Exit the chrooted environment and unmount all mounted partitions. Then type in
298     that one magical command you have been waiting for: <c>reboot</c>.
299     </p>
300    
301     <pre caption="Exiting the chroot, unmounting all partitions and rebooting">
302     # <i>exit</i>
303 swift 1.12 ~# <i>cd</i>
304 neysx 1.22 ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
305 swift 1.12 ~# <i>reboot</i>
306 swift 1.1 </pre>
307    
308     <p>
309     Of course, don't forget to remove the bootable CD, otherwise the CD will be
310     booted again instead of your new Gentoo system.
311     </p>
312    
313     <p>
314     Once rebooted in your Gentoo installation, finish up with <uri
315     link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
316     </p>
317    
318     </body>
319     </subsection>
320     </section>
321    
322     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20