en/handbook/hb-install-alpha-bootloader.xml

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-bootloader.xml,v 1.14 2005/03/29 21:04:39 swift Exp $ -->

<sections>

<version>2.2</version>
<date>2006-01-19</date>

<section>
<title>Making your Choice</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that your kernel is configured and compiled and the necessary system
configuration files are filled in correctly, it is time to install a
program that will fire up your kernel when you start the system. Such a
program is called a <e>bootloader</e>. 
</p>

<p>
Several bootloaders exist for Linux/Alpha. You must choose one of the supported
bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri>
and <uri link="#milo">MILO</uri>.
</p>

</body>
</subsection>
</section>
<section id="aboot">
<title>Default: Using aboot</title>
<body>

<p>
We first install aboot on our system. Of course we use <c>emerge</c> to
do so:
</p>

<pre caption = "Installing aboot">
# <i>emerge --usepkg aboot</i>
</pre>

<p>
The next step is to make our bootdisk bootable. This will start
<c>aboot</c> when you boot your system. We make our bootdisk bootable by
writing the <c>aboot</c> bootloader to the start of the disk.
</p>

<pre caption = "Making your bootdisk bootable">
# <i>swriteboot -f3 /dev/sda /boot/bootlx</i> 
# <i>abootconf /dev/sda 2</i>
</pre>

<note>
If you use a different partitioning scheme than the one we use
throughout this chapter, you have to change the commands accordingly.
Please read the appropriate manual pages (<c>man 8 swriteboot</c> and
<c>man 8 abootconf</c>). Also, if your root filesystem is ran using the JFS
filesystem, make sure it gets mounted read-only at first by adding <c>ro</c> as
a kernel option.
</note>

<p>
Additionally, you can make Gentoo boot automatically by setting up the 
aboot configuration file and some SRM variables.  You can try setting 
these variables from Linux, but it may be easier to do so from the SRM 
console itself.
</p>

<pre caption = "Automatically booting Gentoo">
# <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' &gt; /etc/aboot.conf</i>
# <i>cd /proc/srm_environment/named_variables</i>
# <i>echo -n 0 &gt; boot_osflags</i>
# <i>echo -n '' &gt; boot_file</i>
# <i>echo -n 'BOOT' &gt; auto_action</i>
# <i>echo -n 'dkc100' &gt; bootdef_dev</i>
<comment>(Substitute dkc100 with whatever your boot device is)</comment>
</pre>

<p>
If you need to get into the SRM console again in the future (to recover 
your Gentoo install, play with some variables, or whatever), just hit 
CTRL+C to abort the automatic loading process.
</p>

<p>
If you're installing using a serial console, don't forget to include 
the serial console boot flag in <path>aboot.conf</path>.  See  
<path>/etc/aboot.conf.example</path> for some further information.
</p>

<p>
Aboot is now configured and ready to use. Continue with <uri
link="#reboot">Rebooting the System</uri>.
</p>

</body>
</section>
<section id="milo">
<title>Alternative: Using MILO</title>
<body>

<p>
Before continuing, you should decide on how to use MILO. In this
section, we will assume that you want to make a MILO boot floppy. If you
are going to boot from an MS-DOS partition on your hard disk, you should
amend the commands appropriately.
</p>

<p>
To install MILO, we use <c>emerge</c>.
</p>

<pre caption = "Installing MILO">
# <i>emerge --usepkg milo</i>
</pre>

<p>
After MILO has been installed, the MILO images should be in
<path>/opt/milo</path>. The commands below make a bootfloppy for use
with MILO. Remember to use the correct image for your Alpha-system.
</p>

<pre caption = "Installing MILO on a floppy">
<comment>(First insert a blank floppy)</comment>
# <i>fdformat /dev/fd0</i>
# <i>mformat a:</i>
# <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i>
# <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i>
<comment>(Only if you have a Ruffian:</comment>     
  # <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i>
<comment>)</comment>
# <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i>
</pre>

<p>
Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to
set environment variables in your ARCS Firmware to get MILO to start;
this is all explained in the <uri
link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples 
on common systems, and examples of the commands to use in interactive mode.
</p>

<p>
Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> 
is a <e>bad</e> idea.
</p>

<p>
Now continue with <uri link="#reboot">Rebooting the System</uri>.
</p>

</body>
</section>
<section id="reboot">
<title>Rebooting the System</title>
<subsection>
<body>

<p>
Exit the chrooted environment and unmount all mounted partitions. Then type in 
that one magical command you have been waiting for: <c>reboot</c>.
</p>

<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
# <i>exit</i>
cdimage ~# <i>cd</i>
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
cdimage ~# <i>reboot</i>
</pre>

<p>
Of course, don't forget to remove the bootable CD, otherwise the CD will be
booted again instead of your new Gentoo system.
</p>

<p>
Once rebooted in your Gentoo installation, finish up with <uri
link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
</p>

</body>
</subsection>
</section>

</sections>
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			<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6
7	neysx	1.15	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-bootloader.xml,v 1.14 2005/03/29 21:04:39 swift Exp $ -->
8	swift	1.1
9			<sections>
10	swift	1.9
11	neysx	1.15	<version>2.2</version>
12			<date>2006-01-19</date>
13	swift	1.9
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			Several bootloaders exist for Linux/Alpha. You must choose one of the supported
29			bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri>
30			and <uri link="#milo">MILO</uri>.
31			</p>
32
33			</body>
34			</subsection>
35			</section>
36			<section id="aboot">
37			<title>Default: Using aboot</title>
38			<body>
39
40			<p>
41			We first install aboot on our system. Of course we use <c>emerge</c> to
42			do so:
43			</p>
44
45			<pre caption = "Installing aboot">
46			# <i>emerge --usepkg aboot</i>
47			</pre>
48
49			<p>
50			The next step is to make our bootdisk bootable. This will start
51			<c>aboot</c> when you boot your system. We make our bootdisk bootable by
52			writing the <c>aboot</c> bootloader to the start of the disk.
53			</p>
54
55			<pre caption = "Making your bootdisk bootable">
56			# <i>swriteboot -f3 /dev/sda /boot/bootlx</i>
57			# <i>abootconf /dev/sda 2</i>
58			</pre>
59
60			<note>
61			If you use a different partitioning scheme than the one we use
62			throughout this chapter, you have to change the commands accordingly.
63			Please read the appropriate manual pages (<c>man 8 swriteboot</c> and
64	swift	1.14	<c>man 8 abootconf</c>). Also, if your root filesystem is ran using the JFS
65			filesystem, make sure it gets mounted read-only at first by adding <c>ro</c> as
66			a kernel option.
67	swift	1.1	</note>
68
69			<p>
70	vapier	1.5	Additionally, you can make Gentoo boot automatically by setting up the
71	vapier	1.7	aboot configuration file and some SRM variables. You can try setting
72			these variables from Linux, but it may be easier to do so from the SRM
73			console itself.
74	swift	1.1	</p>
75
76	vapier	1.5	<pre caption = "Automatically booting Gentoo">
77	swift	1.1	# <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' > /etc/aboot.conf</i>
78	vapier	1.6	# <i>cd /proc/srm_environment/named_variables</i>
79			# <i>echo -n 0 > boot_osflags</i>
80			# <i>echo -n '' > boot_file</i>
81	vapier	1.7	# <i>echo -n 'BOOT' > auto_action</i>
82	vapier	1.6	# <i>echo -n 'dkc100' > bootdef_dev</i>
83			<comment>(Substitute dkc100 with whatever your boot device is)</comment>
84	swift	1.1	</pre>
85
86			<p>
87	vapier	1.5	If you need to get into the SRM console again in the future (to recover
88			your Gentoo install, play with some variables, or whatever), just hit
89			CTRL+C to abort the automatic loading process.
90			</p>
91
92			<p>
93			If you're installing using a serial console, don't forget to include
94			the serial console boot flag in <path>aboot.conf</path>. See
95			<path>/etc/aboot.conf.example</path> for some further information.
96	swift	1.1	</p>
97
98			<p>
99			Aboot is now configured and ready to use. Continue with <uri
100	swift	1.3	link="#reboot">Rebooting the System</uri>.
101	swift	1.1	</p>
102
103			</body>
104			</section>
105			<section id="milo">
106			<title>Alternative: Using MILO</title>
107			<body>
108
109			<p>
110			Before continuing, you should decide on how to use MILO. In this
111			section, we will assume that you want to make a MILO boot floppy. If you
112			are going to boot from an MS-DOS partition on your hard disk, you should
113			amend the commands appropriately.
114			</p>
115
116			<p>
117			To install MILO, we use <c>emerge</c>.
118			</p>
119
120			<pre caption = "Installing MILO">
121			# <i>emerge --usepkg milo</i>
122			</pre>
123
124			<p>
125			After MILO has been installed, the MILO images should be in
126			<path>/opt/milo</path>. The commands below make a bootfloppy for use
127			with MILO. Remember to use the correct image for your Alpha-system.
128			</p>
129
130			<pre caption = "Installing MILO on a floppy">
131			<comment>(First insert a blank floppy)</comment>
132			# <i>fdformat /dev/fd0</i>
133			# <i>mformat a:</i>
134			# <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i>
135			# <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i>
136			<comment>(Only if you have a Ruffian:</comment>
137			# <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i>
138			<comment>)</comment>
139			# <i>echo -ne '\125\252' \| dd of=/dev/fd0 bs=1 seek=510 count=2</i>
140			</pre>
141
142			<p>
143			Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to
144			set environment variables in your ARCS Firmware to get MILO to start;
145			this is all explained in the <uri
146			link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples
147			on common systems, and examples of the commands to use in interactive mode.
148			</p>
149
150			<p>
151			Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri>
152			is a <e>bad</e> idea.
153			</p>
154
155			<p>
156	swift	1.3	Now continue with <uri link="#reboot">Rebooting the System</uri>.
157	swift	1.1	</p>
158
159			</body>
160			</section>
161	cam	1.4	<section id="reboot">
162	swift	1.3	<title>Rebooting the System</title>
163			<subsection>
164			<body>
165
166			<p>
167			Exit the chrooted environment and unmount all mounted partitions. Then type in
168			that one magical command you have been waiting for: <c>reboot</c>.
169			</p>
170
171			<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
172			# <i>exit</i>
173	swift	1.8	cdimage ~# <i>cd</i>
174	neysx	1.15	cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
175	swift	1.3	cdimage ~# <i>reboot</i>
176			</pre>
177
178			<p>
179			Of course, don't forget to remove the bootable CD, otherwise the CD will be
180			booted again instead of your new Gentoo system.
181			</p>
182
183			<p>
184			Once rebooted in your Gentoo installation, finish up with <uri
185			link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>.
186			</p>
187
188			</body>
189			</subsection>
190			</section>
191
192	swift	1.1	</sections>