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