/[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.14 - (show annotations) (download) (as text)
Thu Apr 21 13:27:19 2005 UTC (9 years, 3 months ago) by swift
Branch: MAIN
Changes since 1.13: +40 -9 lines
File MIME type: application/xml
#88894 - Updates to PPC64 wrt IBM systems

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/1.0 -->
6
7 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml,v 1.13 2005/03/29 21:04:39 swift Exp $ -->
8
9 <sections>
10
11 <version>2.2</version>
12 <date>2005-04-20</date>
13
14 <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 On Linux/PPC64 we have only yaBoot as a bootloader untill grub2 is
29 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 You have to use yaboot-static instead of yaboot, because yaboot won't
43 compile on PPC64.
44 </impo>
45
46 <p>
47 There are two ways to configure yaBoot for your system. You can use the
48 new and improved <c>yabootconfig</c> included with
49 <path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If
50 for some reason you do not want to run <c>yabootconfig</c> to
51 automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo
52 on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit
53 the sample file already installed on your system.
54 </p>
55
56 <impo>
57 yabootconfig/ybin won't work on IBM. You have to install yaboot another way:
58 <uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri>
59 </impo>
60
61 <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 <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 set up dual and triple boot combinations with Linux, Mac OS, and Mac OS
83 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 # <i>emerge --update yaboot-static</i>
97 </pre>
98
99 <p>
100 Now run <c>yabootconfig</c>. The program will run and it will confirm
101 the location of the bootstrap partition. Type <c>Y</c> if it is correct. If
102 not, double check <path>/etc/fstab</path>. yabootconfig will then scan your
103 system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for
104 you. <c>mkofboot</c> is used to format the bootstrap partition, and install
105 the yaboot configuration file into it.
106 </p>
107
108 <p>
109 You might want to verify the contents of <path>/etc/yaboot.conf</path>. If
110 you make changes to <path>/etc/yaboot.conf</path> (like setting the
111 default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the
112 bootstrap partition.
113 </p>
114
115 <p>
116 Now continue with <uri link="#reboot">Rebooting your System</uri>.
117 </p>
118
119 </body>
120 </subsection>
121 <subsection id="manual_yaboot">
122 <title>Alternative: Manual yaBoot Configuration</title>
123 <body>
124
125 <p>
126 First make sure you have the latest <c>yaboot-static</c> installed on your
127 system:
128 </p>
129
130 <pre caption = "Installing yaboot">
131 # <i>emerge --update yaboot-static</i>
132 </pre>
133
134 <p>
135 Below you find a completed <path>yaboot.conf</path> file. Alter it at
136 will.
137 </p>
138
139 <pre caption = "/etc/yaboot.conf">
140 <comment>## /etc/yaboot.conf
141 ##
142 ## run: "man yaboot.conf" for details. Do not make changes until you have!!
143 ## see also: /usr/share/doc/yaboot/examples for example configurations.
144 ##
145 ## For a dual-boot menu, add one or more of:
146 ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
147
148 ## our bootstrap partition:</comment>
149
150 boot=/dev/hda2
151
152 <comment>## ofboot is the openfirmware way to specify the bootstrap partition.
153 ## If this isn't defined, yaboot fails on the G5 and some G4s (unless
154 ## you pass the necessary arguments to the mkofboot/ybin program).
155 ## hd:X means /dev/sdaX (or /dev/hdaX).</comment>
156
157 ofboot=hd:2
158
159 <comment>## hd: is open firmware speak for hda</comment>
160 device=hd:
161
162 delay=5
163 defaultos=macosx
164 timeout=30
165 install=/usr/lib/yaboot/yaboot
166 magicboot=/usr/lib/yaboot/ofboot
167
168 <comment>#################
169 ## This section can be duplicated if you have more than one kernel or set of
170 ## boot options - replace 2.6.9 with your kernel-version
171 #################</comment>
172 image=/boot/kernel-2.6.9
173 label=Linux
174 root=/dev/hda3
175 partition=3
176 sysmap=/boot/System.map-2.6.9
177 read-only
178
179 macos=hd:13
180 macosx=hd:12
181 enablecdboot
182 enableofboot
183 </pre>
184
185 <p>
186 Once <path>yaboot.conf</path> is set up the way you want it, you run
187 <c>mkofboot -v</c> to install the settings in the bootstrap partition.
188 <e>Don't forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new
189 filesystem.
190 </p>
191
192 <p>
193 If all goes well, and you have the same
194 options as the sample above, your next reboot will give you a simple,
195 five-entry boot menu. If you update your yaboot config later on, you'll
196 just need to run <c>ybin -v</c> to update the bootstrap partition -
197 <c>mkofboot</c> is for initial setup only.
198 </p>
199
200 <p>
201 For more information on yaboot, take a look at the <uri
202 link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For
203 now, continue the installation with <uri link="#reboot">Rebooting your
204 System</uri>.
205 </p>
206
207 </body>
208 </subsection>
209 </section>
210 <section id="yaboot-ibm">
211 <title>Using yaboot on IBM hardware</title>
212 <body>
213
214 <p>
215 On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the
216 folowing steps:
217 </p>
218
219 <ul>
220 <li>Install yaboot-static</li>
221 <li>Run 'dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX' (fill in XX
222 with your disk and partition for the PReP partition; this was in our
223 example /dev/sda1)</li>
224 <li>Next construct your own yaboot.conf file and place into /etc.
225 (Take a look at the config above, look into the man page of
226 yaboot.conf or look at the below yaboot.conf example)</li>
227 <li>Assuming your boot device in OF is pointing to the harddrive you
228 prep boot partition is on then it'll just work, otherwise at IPL time,
229 go into the multiboot menu and set the boot device to the one with
230 your prep boot partition.</li>
231 <li>That's it!</li>
232 </ul>
233
234 <pre caption = "yaboot.conf for IBM hardware">
235 device=disk:
236 partition=2
237 root=/dev/sda2
238 default=2.6.8-gentoo-r3
239 timeout=50
240
241 image=/boot/vmlinux-2.6.8-gentoo-r3
242 label=2.6.8-gentoo-r3
243 append="console=ttyS0,9600"
244 read-only
245 </pre>
246
247 <p>
248 For POWER4, POWER5, and blade-based hardware where the PReP disk partition
249 and the disk partition that contains your kernel are on the same physical disk,
250 you can use a simplified yaboot.conf. The following should be sufficient:
251 </p>
252
253 <pre caption="yaboot.conf for PReP hardware">
254 default = linux
255 timeout = 100
256 image=/boot/vmlinux
257 label=linux
258 read-only
259 root = /dev/sda2
260 append="root=/dev/sda2"
261 </pre>
262
263 <p>
264 To verify that yaboot has been copied to the PReP partition:
265 </p>
266
267 <pre caption="Verifying the yaboot install on PReP">
268 # <i>dd if=/dev/sda1 count=10 | grep ELF</i>
269 Binary file (standard input) matches
270 10+0 records in
271 10+0 records out
272 </pre>
273
274 <p>
275 A match signifies that yaboot was installed correctly.
276 </p>
277
278 </body>
279 </section>
280 <section id="reboot">
281 <title>Rebooting the System</title>
282 <subsection>
283 <body>
284
285 <p>
286 Exit the chrooted environment and unmount all mounted partitions. Then type in
287 that one magical command you have been waiting for: <c>reboot</c>.
288 </p>
289
290 <pre caption="Exiting the chroot, unmounting all partitions and rebooting">
291 # <i>exit</i>
292 ~# <i>cd</i>
293 ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo</i>
294 ~# <i>reboot</i>
295 </pre>
296
297 <p>
298 Of course, don't forget to remove the bootable CD, otherwise the CD will be
299 booted again instead of your new Gentoo system.
300 </p>
301
302 <p>
303 Once rebooted in your Gentoo installation, finish up with <uri
304 link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
305 </p>
306
307 </body>
308 </subsection>
309 </section>
310
311 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20