/[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.32 Revision 1.33
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.32 2006/01/19 21:48:10 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.33 2006/02/27 00:55:34 fox2mike Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>2.8</version> 11<version>2.9</version>
12<date>2006-01-19</date> 12<date>2006-02-27</date>
13 13
14<section> 14<section>
15<title>Choosing a Bootloader</title> 15<title>Choosing a Bootloader</title>
16<subsection> 16<subsection>
17<title>Introduction</title> 17<title>Introduction</title>
41<body> 41<body>
42 42
43<impo> 43<impo>
44yaboot can only be used on NewWorld Apple or IBM machines! 44yaboot can only be used on NewWorld Apple or IBM machines!
45</impo> 45</impo>
46 46
47<p>
48In order to find the boot devices, yaboot needs access to the <path>/dev</path>
49filesystem. To do this, you will need to "bind-map" the <path>/dev</path>
50filesystem from the Installation CD to <path>/dev</path> inside of the chroot.
51</p> 47<p>
52 48In order to find the boot devices, yaboot needs access to the device nodes
49created by udev on startup and the sysfs filesystem. These two filesystems
50are found at <path>/dev</path> and <path>sys</path> respectively. To do this,
51you will need to "bind mount" these filesystems from the Installation CD's root
52to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot.
53If you have already bind mounted these filesystems, there is no need to do it
54again.
55</p>
56
53<pre caption="Bind-mounting the /dev filesystem"> 57<pre caption="Bind-mounting the device and sysfs filesystems">
54# <i>exit </i> # this will exit the chroot 58# <i>exit </i> # this will exit the chroot
55# <i>mount -o bind /dev /mnt/gentoo/dev</i> 59# <i>mount -o bind /dev /mnt/gentoo/dev</i>
60# <i>mount -o bind /sys /mnt/gentoo/sys</i>
56# <i>chroot /mnt/gentoo /bin/bash</i> 61# <i>chroot /mnt/gentoo /bin/bash</i>
57# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i> 62# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i>
58</pre> 63</pre>
59 64
60<p> 65<p>
71</note> 76</note>
72 77
73<pre caption="Adding genkernel boot arguments to yaboot.conf"> 78<pre caption="Adding genkernel boot arguments to yaboot.conf">
74<comment>########################################################### 79<comment>###########################################################
75## This section can be duplicated if you have more than one 80## This section can be duplicated if you have more than one
76## kernel or set of boot options - replace kernel-2.6.12 81## kernel or set of boot options - replace kernel-2.6.15
77## with the exact filename of your kernel. 82## with the exact filename of your kernel.
78###########################################################</comment> 83###########################################################</comment>
79image=/boot/kernel-2.6.12 84image=/boot/kernel-2.6.15
80 label=Linux 85 label=Linux
81 root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment> 86 root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment>
82 partition=3 87 partition=3
83 append="real_root=/dev/hda3 init=/linuxrc" 88 append="real_root=/dev/hda3 init=/linuxrc"
84 <comment># You can add additional kernel arguments to be appended such as 89 <comment># You can add additional kernel arguments to be appended such as
102 107
103<p> 108<p>
104<c>yabootconfig</c> will auto-detect the partitions on your machine and will 109<c>yabootconfig</c> will auto-detect the partitions on your machine and will
105set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X. 110set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X.
106</p> 111</p>
107 112
108<p> 113<p>
109To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition, 114To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
110and <path>/etc/fstab</path> must be configured with your Linux partitions. Both 115and <path>/etc/fstab</path> must be configured to reflect your Linux
111of these steps should have been completed already. First, make sure that you 116partitions. These steps should have already been completed before, but check
112have the latest version of <c>yaboot</c> installed. 117<path>/etc/fstab</path> before proceeding. Now, ensure that you have
118<c>yaboot</c> installed.
113</p> 119</p>
114 120
115<pre caption = "Installing yaboot with GRP"> 121<pre caption = "Installing yaboot">
116# <i>emerge --usepkg --update yaboot</i> 122# <i>emerge yaboot</i>
117</pre> 123</pre>
118 124
119<p> 125<p>
120Now, exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. It will 126Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First,
121ask you to confirm the location of the Apple_Bootstrap partition. Type <c>Y</c> 127the program will confirm the location of the bootstrap partition. If you are
122if it is correct. If not, check <path>/etc/fstab</path> and ensure that the 128using the suggested disk partitioning scheme, your bootstrap partition should
123device paths are correct. Once the bootstrap partition has been selected, 129be /dev/hda2. Type <c>Y</c> if the output is correct. If not, double check your
124<c>yabootconfig</c> will scan your system setup, create 130<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup,
125<path>/etc/yaboot.conf</path> and run <c>mkofboot</c>. <c>mkofboot</c> 131create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you.
126formats the Apple_Bootstrap partition, and installs the yaboot configuration 132<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install
127file onto it. After this is complete, enter the chroot again. 133the yaboot configuration file into it. After this enter the chroot again.
128</p> 134</p>
129 135
130<pre caption="Re-enter the chroot"> 136<pre caption="Re-enter the chroot">
131# <i>chroot /mnt/gentoo /bin/bash</i> 137# <i>chroot /mnt/gentoo /bin/bash</i>
132# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i> 138# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i>
148<subsection id="manual_yaboot"> 154<subsection id="manual_yaboot">
149<title>Alternative: Manual yaboot Configuration</title> 155<title>Alternative: Manual yaboot Configuration</title>
150<body> 156<body>
151 157
152<p> 158<p>
153First, make sure you have the latest version of <c>yaboot</c> installed. 159First, make sure you have <c>yaboot</c> installed.
154</p> 160</p>
155 161
156<pre caption = "Installing yaboot"> 162<pre caption = "Installing yaboot">
157# <i>emerge --usepkg --update yaboot</i> 163# <i>emerge yaboot</i>
158</pre> 164</pre>
159 165
160<p> 166<p>
161An example <path>yaboot.conf</path> file is given below, but you will need to 167An example <path>yaboot.conf</path> file is given below, but you will need to
162alter it to fit your needs. G5 users and users booting from firewire and USB 168alter it to fit your needs. G5 users and users booting from firewire and USB
311computer will boot into MacOS and then, during startup, load BootX which in turn 317computer will boot into MacOS and then, during startup, load BootX which in turn
312starts Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/"> 318starts Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">
313BootX home page</uri> for more information. 319BootX home page</uri> for more information.
314</p> 320</p>
315 321
322<impo>
323Make sure that you have support for HFS and HFS+ filesystems in your kernel,
324otherwise you will not be able to upgrade or change the kernel on your MacOS
325partition.
326</impo>
327
316<p> 328<p>
317Now reboot again and boot into Linux, then continue with <uri 329Now reboot again and boot into Linux, then continue with <uri
318link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>. 330link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
319</p> 331</p>
320 332
344kernel that we copied to your boot partition. 356kernel that we copied to your boot partition.
345</p> 357</p>
346 358
347<pre caption="Configuring quik.conf"> 359<pre caption="Configuring quik.conf">
348# Example of quik.conf 360# Example of quik.conf
349init-message = "Gentoo 2005.1\n" 361init-message = "Gentoo 2006.0\n"
350partition = 2 <comment># This is the boot partition</comment> 362partition = 2 <comment># This is the boot partition</comment>
351root = /dev/hda4 363root = /dev/hda4
352timeout = 30 364timeout = 30
353default = gentoo 365default = gentoo
354image = /vmlinux-2.6.12 366image = /vmlinux-2.6.15
355 label = gentoo 367 label = gentoo
356</pre> 368</pre>
357 369
358<p> 370<p>
359Your quik.conf file <e>must</e> be on the same disk as the quik boot images, 371Your quik.conf file <e>must</e> be on the same disk as the quik boot images,
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> 389# <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> 390# <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment>
379# <i>nvsetenv input-device kbd</i> 391# <i>nvsetenv input-device kbd</i>
380# <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment> 392# <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> 393# <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> 394# <i>nvsetenv boot-file /boot/vmlinux-2.6.15 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> 395# <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment>
384</pre> 396</pre>
385 397
386<note> 398<note>
387It is also possible to change your boot variables from MacOS. Depending 399It is also possible to change your boot variables from MacOS. Depending
462[SECTION] 474[SECTION]
463Local HD -> Morphos (Normal) 475Local HD -> Morphos (Normal)
464ide:0 boot2.img ramdebug edebugflags="logkprintf" 476ide:0 boot2.img ramdebug edebugflags="logkprintf"
465 477
466[SECTION] 478[SECTION]
467Local HD -> Linux 2.6.12 (Normal) 479Local HD -> Linux 2.6.15 (Normal)
468ide:0 linux-2.6.12 video=radeonfb:1024x768@70 root=/dev/hda3 480ide:0 linux-2.6.15 video=radeonfb:1024x768@70 root=/dev/hda3
469 481
470[SECTION] 482[SECTION]
471Local HD -> Genkernel (Normal) 483Local HD -> Genkernel (Normal)
472ide:0 kernelz-2.6.12 root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc 484ide:0 kernelz-2.6.15 root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc
473</pre> 485</pre>
474 486
475<p> 487<p>
476Finally, the <path>bootmenu</path> must be transformed into Forth and copied to 488Finally, the <path>bootmenu</path> must be transformed into Forth and copied to
477your boot partition so the SmartFirmware can read it. To do this, start 489your boot partition so the SmartFirmware can read it. To do this, start
490<p> 502<p>
491Now, continue the installation with 503Now, continue the installation with
492<uri link="#reboot">Rebooting the System</uri>. 504<uri link="#reboot">Rebooting the System</uri>.
493</p> 505</p>
494 506
495
496</body> 507</body>
497</section> 508</section>
498<section id="reboot"> 509<section id="reboot">
499<title>Rebooting the System</title> 510<title>Rebooting the System</title>
500<subsection> 511<subsection>

Legend:
Removed from v.1.32  
changed lines
  Added in v.1.33

  ViewVC Help
Powered by ViewVC 1.1.20