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

Diff of /xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.27 Revision 1.28
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.27 2005/06/14 10:18:25 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.28 2005/08/09 09:43:58 swift Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>2.4</version> 11<version>2.5</version>
12<date>2005-05-12</date> 12<date>2005-08-09</date>
13 13
14<section> 14<section>
15<title>Making your Choice</title> 15<title>Choosing a Bootloader</title>
16<subsection> 16<subsection>
17<title>Introduction</title> 17<title>Introduction</title>
18<body> 18<body>
19 19
20<p> 20<p>
21Now that your kernel is configured and compiled and the necessary system 21Now that the kernel is configured and compiled, you'll need a <e>bootloader</e>
22configuration files are filled in correctly, it is time to install a 22to start your new linux installation. The <e>bootloader</e> that you use will
23program that will fire up your kernel when you start the system. Such a 23depend upon the type of PPC machine you have.
24program is called a <e>bootloader</e>. But before you start, consider
25your options...
26</p>
27
28<p> 24</p>
29Several bootloaders exist for Linux/PPC. We have <uri link="#yaboot">yaboot</uri> 25
30(for NewWorld Apple and IBM machines) and <uri link="#bootx">BootX</uri> (for 26<p>
31OldWorld Apple machines). The Pegasos does not require a bootloader, but 27If you are using a NewWorld Apple or IBM machine, you need to use
32we included the <uri link="#bootcreator">BootCreator</uri> for creating a 28<uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options,
33SmartFirmware bootmenu. 29<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>.
30The Pegasos does not require a bootloader, but you will need to emerge
31<uri link="#bootcreator">BootCreator</uri> to create SmartFirmware bootmenus.
34</p> 32</p>
35 33
36</body> 34</body>
37</subsection> 35</subsection>
38</section> 36</section>
41<subsection> 39<subsection>
42<title>Introduction</title> 40<title>Introduction</title>
43<body> 41<body>
44 42
45<impo> 43<impo>
46yaboot can only be used on NewWorld Apple and IBM systems! 44yaboot can only be used on NewWorld Apple or IBM machines!
47</impo> 45</impo>
48 46
49<p> 47<p>
50First we have to create the <path>/dev</path> files in our new home, which is 48In order to find the boot devices, yaboot needs access to the <path>/dev</path>
51needed during the bootloader installation. This could be done by "bind"-mapping 49filesystem. To do this, you will need to "bind-map" the <path>/dev</path>
52the <path>/dev</path>-filesystem from the Installation CD: 50filesystem from the Installation CD to <path>/dev</path> inside of the chroot.
53</p> 51</p>
54 52
55<pre caption="Bind-mounting the /dev-filesystem"> 53<pre caption="Bind-mounting the /dev filesystem">
56# <i>exit </i> # this will exit the chroot 54# <i>exit </i> # this will exit the chroot
57# <i>mount -o bind /dev /mnt/gentoo/dev</i> 55# <i>mount -o bind /dev /mnt/gentoo/dev</i>
58# <i>chroot /mnt/gentoo /bin/bash</i> 56# <i>chroot /mnt/gentoo /bin/bash</i>
59# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i> 57# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i>
60</pre> 58</pre>
61 59
62<p> 60<p>
63There are two ways to configure yaboot for your system. You can use the 61To set up yaboot, you can use <c>yabootconfig</c> to automatically create a
64included <c>yabootconfig</c> to automatically set up yaboot. If 62configuration file for you. If you are installing Gentoo on a G5 (where
65for some reason you do not want to run <c>yabootconfig</c> to 63<c>yabootconfig</c> does not always work), or you plan to boot from firewire
66automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo 64or USB, you will need to manually configure yaboot.
67on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit
68the sample file already installed on your system.
69</p> 65</p>
70 66
71<note> 67<note>
72You may need to edit the yaboot.conf file if using genkernel. The arguments 68You will need to manually edit the yaboot.conf when using genkernel, even if
73provided by the genkernel ebuild need to be added as an option to the kernel 69yabootconfig is used. The kernel image section of yaboot.conf should be
74image section. The relevant section of yaboot.conf is given below: 70modified as follows:
75</note> 71</note>
76 72
77<pre caption="Adding boot arguments to yaboot.conf"> 73<pre caption="Adding genkernel boot arguments to yaboot.conf">
78<comment>################# 74<comment>###########################################################
79## This section can be duplicated if you have more than one kernel or set of 75## This section can be duplicated if you have more than one
80## boot options - replace 2.6.9 with your kernel-version 76## kernel or set of boot options - replace kernel-2.6.12
81#################</comment> 77## with the exact filename of your kernel.
78###########################################################</comment>
82image=/boot/kernel-2.6.9 79image=/boot/kernel-2.6.12
83 label=Linux 80 label=Linux
84 root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment> 81 root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment>
85 partition=3 82 partition=3
86 sysmap=/boot/System.map-2.6.9 83 append="real_root=/dev/hda3 init=/linuxrc"
87 append="real_root=/dev/hda3 init=/linuxrc" <comment># Add arguments to this line</comment> 84 <comment># You can add additional kernel arguments to append such as
85 # rootdelay=10 for a USB/Firewire Boot</comment>
88 read-only 86 read-only
89<comment>##################</comment> 87<comment>##########################################################</comment>
90</pre> 88</pre>
91 89
92<ul> 90<ul>
93 <li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> 91 <li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li>
94 <li> 92 <li>
108</p> 106</p>
109 107
110<p> 108<p>
111To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition, 109To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
112and <path>/etc/fstab</path> must be configured with your Linux partitions. Both 110and <path>/etc/fstab</path> must be configured with your Linux partitions. Both
113of these should have been done already in the steps above. To start, ensure that 111of these steps should have been completed already. First, make sure that you
114you have the latest <c>yaboot</c> installed. 112have the latest version of <c>yaboot</c> installed.
115</p> 113</p>
116 114
117<pre caption = "Installing yaboot with GRP"> 115<pre caption = "Installing yaboot with GRP">
118# <i>emerge --usepkg --update yaboot</i> 116# <i>emerge --usepkg --update yaboot</i>
119</pre> 117</pre>
120 118
121<p> 119<p>
122Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. The 120Now, exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. It will
123program will run and it will confirm the location of the bootstrap partition. 121ask you to confirm the location of the Apple_Bootstrap partition. Type <c>Y</c>
124Type <c>Y</c> if it is correct. If not, double check <path>/etc/fstab</path>. 122if it is correct. If not, check <path>/etc/fstab</path> and ensure that the
123device paths are correct. Once the bootstrap partition has been selected,
125yabootconfig will then scan your system setup, create 124<c>yabootconfig</c> will scan your system setup, create
126<path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. <c>mkofboot</c> 125<path>/etc/yaboot.conf</path> and run <c>mkofboot</c>. <c>mkofboot</c>
127is used to format the Apple_Bootstrap partition, and install the yaboot 126formats the Apple_Bootstrap partition, and installs the yaboot configuration
128configuration file into it. After this enter the chroot again. 127file onto it. After this is complete, enter the chroot again.
129</p> 128</p>
129
130<pre caption="enter chroot"> 130<pre caption="Re-enter the chroot">
131# <i>chroot /mnt/gentoo /bin/bash</i> 131# <i>chroot /mnt/gentoo /bin/bash</i>
132# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i> 132# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i>
133</pre> 133</pre>
134 134
135<p> 135<p>
136You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you 136You may want to verify the contents of <path>/etc/yaboot.conf</path>. If you
137make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot 137make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot
138OS), make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap 138OS), make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap
139partition. 139partition.
140</p> 140</p>
141 141
148<subsection id="manual_yaboot"> 148<subsection id="manual_yaboot">
149<title>Alternative: Manual yaboot Configuration</title> 149<title>Alternative: Manual yaboot Configuration</title>
150<body> 150<body>
151 151
152<p> 152<p>
153First make sure you have the latest <c>yaboot</c> installed on your 153First, make sure you have the latest version of <c>yaboot</c> installed.
154system:
155</p> 154</p>
156 155
157<pre caption = "Installing yaboot"> 156<pre caption = "Installing yaboot">
158# <i>emerge --usepkg --update yaboot</i> 157# <i>emerge --usepkg --update yaboot</i>
159</pre> 158</pre>
160 159
161<p> 160<p>
162Below you find a completed <path>yaboot.conf</path> file. Alter it at 161An example <path>yaboot.conf</path> file is given below, but you will need to
163will. G5 users should be aware that their disks are Serial ATA disks which are 162alter it to fit your needs. G5 users and users booting from firewire and USB
164seen as SCSI disks by the Linux kernel (so substitute <path>/dev/hda</path> with 163should be aware that their disks are seen as SCSI disks by the Linux kernel, so
165<path>/dev/sda</path>). 164you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>).
166</p> 165</p>
167 166
168<pre caption = "/etc/yaboot.conf"> 167<pre caption = "/etc/yaboot.conf">
169<comment>## /etc/yaboot.conf 168<comment>## /etc/yaboot.conf
170## 169##
182## If this isn't defined, yaboot fails on the G5 and some G4s (unless 181## If this isn't defined, yaboot fails on the G5 and some G4s (unless
183## you pass the necessary arguments to the mkofboot/ybin program). 182## you pass the necessary arguments to the mkofboot/ybin program).
184## hd:X means /dev/sdaX (or /dev/hdaX). 183## hd:X means /dev/sdaX (or /dev/hdaX).
185## 184##
186## G5 users should uncomment this line!! 185## G5 users should uncomment this line!!
187
188#ofboot=hd:2 186#ofboot=hd:2
189 187
190## hd: is open firmware speak for hda</comment> 188## Users booting from firewire should use something like this line:
189# ofboot=fw/node/sbp-2/disk@0:
190
191## Users booting from USB should use something like this line:
192# ofboot=usb/disk@0:
193
194## hd: is shorthand for the first hard drive OpenFirmware sees</comment>
191device=hd: 195device=hd:
196
197<comment>## Firewire and USB users will need to specify the whole OF device name
198## This can be found using ofpath, which is included with yaboot.
199
200# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0:
201</comment>
192 202
193delay=5 203delay=5
194defaultos=macosx 204defaultos=macosx
195timeout=30 205timeout=30
196install=/usr/lib/yaboot/yaboot 206install=/usr/lib/yaboot/yaboot
202#################</comment> 212#################</comment>
203image=/boot/kernel-2.6.9 213image=/boot/kernel-2.6.9
204 label=Linux 214 label=Linux
205 root=/dev/hda3 215 root=/dev/hda3
206 partition=3 216 partition=3
207 sysmap=/boot/System.map-2.6.9 217<comment># append="rootdelay=10" # Required for booting USB/Firewire</comment>
208 read-only 218 read-only
209<comment>################## 219<comment>##################
210 220
211## G5 users and some G4 users should set 221## G5 users and some G4 users should set
212## macos=hd:13 222## macos=hd:13
217enablecdboot 227enablecdboot
218enableofboot 228enableofboot
219</pre> 229</pre>
220 230
221<p> 231<p>
222Once <path>yaboot.conf</path> is set up the way you want it, you run 232Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format
223<c>mkofboot -v</c> to install the settings in the bootstrap partition. <e>Don't 233the Apple_bootstrap partition and install the settings. If you change
224forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new 234yaboot.conf after the Apple_bootstrap partition has been created, you can
225filesystem. 235update the settings by running <c>ybin -v</c>
226</p>
227
228<p>
229If all goes well, and you have the same options as the sample
230above, your next reboot will give you a simple, five-entry boot menu. If you
231update your yaboot config later on, you'll just need to run <c>ybin -v</c> to
232update the bootstrap partition - <c>mkofboot</c> is for initial setup only.
233</p> 236</p>
234 237
235<p> 238<p>
236For more information on yaboot, take a look at the <uri 239For more information on yaboot, take a look at the <uri
237link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For 240link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For
264cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> 267cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i>
265cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels"</i> 268cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels"</i>
266</pre> 269</pre>
267 270
268<p> 271<p>
269If genkernel is used, the kernel is located in a different place and the initrd 272If genkernel is used, both the kernel and initrd will need to be copied to the
270will need to be copied as well. 273MacOS partition.
271</p> 274</p>
272 275
273<pre caption="Copying the Genkernel kernel and initrd to the MacOS partition"> 276<pre caption="Copying the Genkernel kernel and initrd to the MacOS partition">
274# <i>exit</i> 277# <i>exit</i>
275cdimage ~# <i>mkdir /mnt/mac</i> 278cdimage ~# <i>mkdir /mnt/mac</i>
277cdimage ~# <i>cp /mnt/gentoo/boot/kernel-* "/mnt/mac/System Folder/Linux Kernels"</i> 280cdimage ~# <i>cp /mnt/gentoo/boot/kernel-* "/mnt/mac/System Folder/Linux Kernels"</i>
278cdimage ~# <i>cp /mnt/gentoo/boot/initrd-* "/mnt/mac/System Folder"</i> 281cdimage ~# <i>cp /mnt/gentoo/boot/initrd-* "/mnt/mac/System Folder"</i>
279</pre> 282</pre>
280 283
281<p> 284<p>
282Now that the kernel is copied over, unmount all mounted filesystems and enter 285Now that the kernel is copied over, we'll need to reboot to set up BootX.
283that one magical command that you have been waiting for: <c>reboot</c>.
284</p> 286</p>
285 287
286<pre caption="Unmounting all partitions and rebooting"> 288<pre caption="Unmounting all partitions and rebooting">
287cdimage ~# <i>cd /</i> 289cdimage ~# <i>cd /</i>
288cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo /mnt/mac</i> 290cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo /mnt/mac</i>
289cdimage ~# <i>reboot</i> 291cdimage ~# <i>reboot</i>
290</pre> 292</pre>
291 293
292<p> 294<p>
293Of course, don't forget to remove all bootable media, MacOS needs to boot this 295Of course, don't forget to remove all bootable media, since MacOS needs to boot
294time. 296this time.
295</p>
296
297<p> 297</p>
298
299<p>
298Now that the machine has booted into MacOS, open the BootX control panel and 300Once the machine has booted into MacOS, open the BootX control panel. If you're
299Select <c>Options</c> and uncheck <c>Used specified RAM disk</c> if not using 301not using genkernel, select <c>Options</c> and uncheck <c>Used specified RAM
300genkernel. If using genkernel, ensure that the genkernel initrd is selected 302disk</c>. If you are using genkernel, ensure that the genkernel initrd is
301instead of the Installation CD initrd. If not using genkernel, there is now 303selected instead of the Installation CD initrd. If not using genkernel,
302an option to specify the machine's Linux root disk and partition. Fill these 304there is now an option to specify the machine's Linux root disk and partition.
303in with the appropriate values. Depending upon the kernel configuration, some 305Fill these in with the appropriate values. Depending upon the kernel
304boot arguments may need to be applied. 306configuration, additional boot arguments may need to be applied.
305</p> 307</p>
306 308
307<p> 309<p>
308BootX can be configured to start Linux upon boot. If you chose to do this, the 310BootX can be configured to start Linux upon boot. If you chose to do this, the
309computer will boot into MacOS and then during startup load BootX which in turn 311computer will boot into MacOS and then, during startup, load BootX which in turn
310starts Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/"> 312starts Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">
311Boot X home page</uri> for more information. 313BootX home page</uri> for more information.
312</p> 314</p>
313 315
314<p> 316<p>
315Now reboot again and boot into Linux, then continue with <uri 317Now reboot again and boot into Linux, then continue with <uri
316link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>. 318link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
319</p>
320
321</body>
322</section>
323<section id="quik">
324<title>Alternative: quik</title>
325<body>
326
327<p>
328quik allows OldWorld Macs to boot without MacOS. However, it isn't well
329supported and has a number of quirks. If you have the option, it is recommended
330that you use BootX instead since it is much more reliable and easier to set up
331than quik.
332</p>
333
334<p>
335First, we'll need to install quik:
336</p>
337
338<pre caption="Emerge quik">
339# <i>emerge quik</i>
340</pre>
341
342<p>
343Next, we'll need to set it up. Edit /etc/quik.conf and set your image to the
344kernel that we copied to your boot partition.
345</p>
346
347<pre caption="Configuring quik.conf">
348# Example of quik.conf
349init-message = "Gentoo 2005.1\n"
350partition = 2 <comment># This is the boot partition</comment>
351root = /dev/hda4
352timeout = 30
353default = gentoo
354image = /vmlinux-2.6.12
355 label = gentoo
356</pre>
357
358<p>
359Your quik.conf file <e>must</e> be on the same disk as the quik boot images,
360however it can be on a different partition on the same disk, although it is
361recommended to move it to your boot partition.
362</p>
363
364<pre caption="Moving quik.conf to /boot">
365# <i>mv /etc/quik.conf /boot/quik.conf</i>
366</pre>
367
368<p>
369We will now set your boot variables so that quik loads on boot. To do this,
370we'll use a program called <c>nvsetenv</c>. The variables that you want to
371set vary from machine to machine, it's best to find your machine's
372<uri link="http://penguinppc.org/bootloaders/quik/quirks.php">quirks</uri>
373before attempting this.
374</p>
375
376<pre caption="Setting the boot variables">
377# <i>nvsetenv auto-boot true</i> <comment># Set to false if you want to boot into OF, not all models can display the OF output</comment>
378# <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment>
379# <i>nvsetenv input-device kbd</i>
380# <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment>
381# <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment>
382# <i>nvsetenv boot-file /boot/vmlinux-2.6.12 root=/dev/hda4</i> <comment>First item is the path to the kernel, the second is the root partition. You may append any kernel options to the end of this line.</comment>
383# <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment>
384</pre>
385
386<note>
387It is also possible to change your boot variables from MacOS. Depending
388upon the model, either
389<uri link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or
390<uri link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin">
391Apple System Disk</uri> should be used. Please see the quik quirks page
392above for more information.
393</note>
394
395<p>
396Now that we've set up our machine to boot, we'll need to make sure the boot
397images are installed correctly. Run <c>quik -v -C /boot/quik.conf</c>. It
398should tell you that it has installed the first stage QUIK boot block.
399</p>
400
401<note>
402If something has gone wrong, you can always reset your PRAM back to the default
403values by holding down <c>command + option + p + r</c> before powering on your
404machine. This will clear the values you set with nvsetenv and should allow you
405to boot either a MacOS bootdisk or a Linux bootdisk.
406</note>
407
408<p>
409Now, continue the installation with
410<uri link="#reboot">Rebooting the System</uri>.
317</p> 411</p>
318 412
319</body> 413</body>
320</section> 414</section>
321<section id="bootcreator"> 415<section id="bootcreator">
322<title>Alternative: BootCreator</title> 416<title>Alternative: BootCreator</title>
323<body> 417<body>
324 418
325<impo> 419<impo>
326BootCreator will build a nice SmartFirmware bootmenu written in Forth for the 420BootCreator will build a SmartFirmware boot menu written in Forth for the
327Pegasos. 421Pegasos.
328</impo> 422</impo>
329 423
330<p> 424<p>
331First make sure you have the latest <c>bootcreator</c> installed on your 425First, ensure that you have <c>bootcreator</c> installed on your system:
332system:
333</p> 426</p>
334 427
335<pre caption = "Installing bootcreator"> 428<pre caption = "Installing bootcreator">
336# <i>emerge --usepkg --update bootcreator</i> 429# <i>emerge bootcreator</i>
337</pre> 430</pre>
338 431
339<p> 432<p>
340Now copy the file <path>/etc/bootmenu.example</path> into 433Now copy the file <path>/etc/bootmenu.example</path> into
341<path>/etc/bootmenu</path> and edit it to your needs: 434<path>/etc/bootmenu</path> and edit it to suit your needs:
342</p> 435</p>
343 436
344<pre caption = "Edit the bootcreator config file"> 437<pre caption = "Edit the bootcreator config file">
345# <i>cp /etc/bootmenu.example /etc/bootmenu</i> 438# <i>cp /etc/bootmenu.example /etc/bootmenu</i>
346# <i>nano -w /etc/bootmenu</i> 439# <i>nano -w /etc/bootmenu</i>
347</pre> 440</pre>
348 441
349<p> 442<p>
350Below you find a completed <path>/etc/bootmenu</path> config file. Alter it at 443An example <path>/etc/bootmenu</path> config file is included below.
351will.
352</p> 444</p>
353 445
354<pre caption = "bootcreator config file"> 446<pre caption = "bootcreator config file">
355<comment># 447<comment>#
356# Example description file for bootcreator 1.1 448# Example description file for bootcreator 1.1
370[SECTION] 462[SECTION]
371Local HD -> Morphos (Normal) 463Local HD -> Morphos (Normal)
372ide:0 boot2.img ramdebug edebugflags="logkprintf" 464ide:0 boot2.img ramdebug edebugflags="logkprintf"
373 465
374[SECTION] 466[SECTION]
375Local HD -> Linux 2.6.10 (Normal) 467Local HD -> Linux 2.6.12 (Normal)
376ide:0 linux-2.6.10 video=radeonfb:1024x768@70 root=/dev/hda3 468ide:0 linux-2.6.12 video=radeonfb:1024x768@70 root=/dev/hda3
377 469
470[SECTION]
471Local HD -> Genkernel (Normal)
472ide:0 kernelz-2.6.12 root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc
378</pre> 473</pre>
379 474
380<p> 475<p>
381Finally the <path>bootmenu</path> must be transfered into Forth and copied to 476Finally, the <path>bootmenu</path> must be transformed into Forth and copied to
382your boot partition, so that the SmartFirmware can read it. Therefore you have 477your boot partition so the SmartFirmware can read it. To do this, start
383to call <c>bootcreator</c>: 478<c>bootcreator</c>:
384</p> 479</p>
385 480
386<pre caption = "Install the bootmenu"> 481<pre caption = "Install the bootmenu">
387# <i>bootcreator /etc/bootmenu /boot/menu</i> 482# <i>bootcreator /etc/bootmenu /boot/menu</i>
388</pre> 483</pre>
389 484
390<note> 485<note>
391Be sure to have a look into the SmartFirmware's settings when you reboot, that 486Be sure to check the SmartFirmware's settings when you reboot, and ensure that
392<path>menu</path> is the file that will be loaded by default. 487<path>menu</path> is the file that will be loaded by default.
393</note> 488</note>
394 489
395<p> 490<p>
396For now, continue the installation with <uri link="#reboot">Rebooting the 491Now, continue the installation with
397System</uri>. 492<uri link="#reboot">Rebooting the System</uri>.
398</p> 493</p>
399 494
400 495
401</body> 496</body>
402</section> 497</section>
404<title>Rebooting the System</title> 499<title>Rebooting the System</title>
405<subsection> 500<subsection>
406<body> 501<body>
407 502
408<p> 503<p>
409Exit the chrooted environment and unmount all mounted partitions. Then type in 504Exit the chrooted environment and unmount all mounted partitions so we can
410that one magical command you have been waiting for: <c>reboot</c>. 505reboot cleanly, then <c>reboot</c>.
411</p> 506</p>
412 507
413<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> 508<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
414# <i>exit</i> 509# <i>exit</i>
415livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo</i> 510livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo</i>
416livecd ~# <i>reboot</i> 511livecd ~# <i>reboot</i>
417</pre> 512</pre>
418 513
419<p> 514<p>
420Once rebooted in your Gentoo installation, finish up with <uri 515Once your new Gentoo installation has booted, finish up with <uri
421link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>. 516link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
422</p> 517</p>
423 518
424</body> 519</body>
425</subsection> 520</subsection>

Legend:
Removed from v.1.27  
changed lines
  Added in v.1.28

  ViewVC Help
Powered by ViewVC 1.1.20