ca/boot-installer/alpha.xml

<!-- retain these comments for translator revision tracking -->
<!-- $Id: alpha.xml,v 1.1 2003/10/22 14:43:55 toff Exp $ -->

 <sect2 arch="alpha" id="alpha-firmware">
 <title>Alpha Console Firmware</title>
<para>

Console firmware is stored in a flash ROM and started when an Alpha
system is powered up or reset.  There are two different console
specifications used on Alpha systems, and hence two classes of console
firmware available:

</para>

<itemizedlist>
<listitem><para>

  <emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem
  specification, which provides an operating environment for OpenVMS, Tru64
  UNIX, and Linux operating systems.

</para></listitem>
<listitem><para>

  <emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the
  Advanced RISC Computing (ARC) specification, which provides an operating
  environment for Windows NT.

</para></listitem>
</itemizedlist>

<para>

From the user's perspective, the most important difference between SRM
and ARC is that the choice of console constrains the possible
disk-partitioning scheme for the hard disk which you wish to boot off
of.

</para><para>

ARC requires that you use an MS-DOS partition table (as created by
<command>cfdisk</command>) for the boot disk.  Therefore MS-DOS partition
tables are the ``native'' partition format when booting from ARC.  In
fact, since AlphaBIOS contains a disk partitioning utility, you may
prefer to partition your disks from the firmware menus before
installing Linux.

</para><para>

Conversely, SRM is <emphasis>incompatible</emphasis> with MS-DOS partition tables.
<footnote>Specifically, the bootsector format required by the Console
Subsystem Specification conflicts with the placement of the DOS
partition table.</footnote> Since Tru64 Unix uses the BSD disklabel format,
this is the ``native'' partition format for SRM installations.

</para><para>

Because GNU/Linux is the only operating system on Alpha that can be
booted from both console types, the choice will also depend on what
other operating systems you wish to run on the same machine.  All
other Unix-like operating systems (Tru64 Unix, FreeBSD, OpenBSD, and
NetBSD) and OpenVMS can only boot from SRM, whereas Windows NT can
only boot from ARC.

</para><para>

The following table summarizes available and supported system
type/console combinations (see <xref linkend="supported-cpus"></xref> for the
system type names).  The word `ARC' below denotes any of the
ARC-compliant consoles.

</para><para>

<informaltable><tgroup cols="2">
<thead>
<row>
  <entry>System Type</entry>
  <entry>Console Type Supported</entry>
</row>
</thead>

<tbody>
<row>
  <entry>alcor</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>avanti</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>book1</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>cabriolet</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>dp264</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>eb164</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>eb64p</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>eb66</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>eb66p</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>jensen</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>lx164</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>miata</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>mikasa</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>mikasa-p</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>nautilus</entry>
  <entry>ARC only (see motherboard manual)</entry>
</row><row>
  <entry>noname</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>noritake</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>noritake-p</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>pc164</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>rawhide</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>ruffian</entry>
  <entry>ARC only</entry>
</row><row>
  <entry>sable</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>sable-g</entry>
  <entry>SRM only</entry>
</row><row>
  <entry>sx164</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>takara</entry>
  <entry>ARC or SRM</entry>
</row><row>
  <entry>xl</entry>
  <entry>ARC only</entry>
</row><row>
  <entry>xlt</entry>
  <entry>ARC or SRM</entry>
</row>

</tbody>
</tgroup>
</informaltable>

</para><para>

Generally, none of these consoles can boot Linux directly, so the
assistance of an intermediary bootloader is required.  There are two
mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>.

</para><para>

<command>MILO</command> is itself a console, which replaces ARC or SRM in
memory.  <command>MILO</command> can be booted from both ARC and SRM and is
the only way to bootstrap Linux from the ARC console.
<command>MILO</command> is platform-specific (a different <command>MILO</command>
is needed for each system type) and exist only for those systems, for
which ARC support is shown in the table above.  See also the
(unfortunately outdated) 
<ulink url="&url-milo-howto;"> name="MILO HOWTO"</ulink>.

</para><para>

<command>aboot</command> is a small, platform-independent bootloader, which
runs from SRM only.  See the (also unfortunately outdated) <ulink
url="&url-srm-howto;">SRM HOWTO</ulink> for more information on
<command>aboot</command>.

</para><para>

Thus, three scenarios are generally possible, depending on the
system's console firmware and whether or not <command>MILO</command> is
available:

<informalexample><screen>

SRM -> aboot
SRM -> MILO
ARC -> MILO

</screen></informalexample>

</para><para>

The UP1000 motherboard (subarchitecture name `nautilus') from Alpha
Processor, Inc. is different from all the others, in that it uses an
API-specific bootloader that runs under AlphaBIOS firmware.

</para><para>

Because <command>MILO</command> is not available for any of the Alpha
systems currently in production (as of February 2000), and because it
is no longer necessary to buy an OpenVMS or Tru64 Unix license to have
SRM firmware on your older Alpha, it is recommended that you use SRM and
<command>aboot</command> on new installations of GNU/Linux, unless you wish
to dual-boot with Windows NT.

</para><para>

The majority of AlphaServers and all current server and workstation
products contain both SRM and AlphaBIOS in their firmware.  For
"half-flash" machines such as the various evaluation boards, it is
possible to switch from one version to another by reflashing the
firmware.  Also, once SRM is installed, it is possible to run
ARC/AlphaBIOS from a floppy disk (using the `arc' command).  For the
reasons mentioned above, we recommend switching to SRM before
installing &debian;.

</para><para>

As on other architectures, you should install the newest available
revision of the firmware <footnote>Except on Jensen, where Linux is
not supported on firmware versions newer than 1.7 - see <ulink
url="&url-jensen-howto;"></ulink>> for more information</footnote> before
installing &debian;.  For Alpha, firmware updates can be obtained from
<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>.

</para>
 </sect2>


  <sect2 arch="alpha"><title>Booting with TFTP</title>
<para>

In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput>
prefix, and will be listed in the output of the <userinput>show dev</userinput> command,
like this (edited slightly):
<informalexample><screen>

>>>show dev
ewa0.0.0.9.0               EWA0              08-00-2B-86-98-65
ewb0.0.0.11.0              EWB0              08-00-2B-86-98-54
ewc0.0.0.2002.0            EWC0              00-06-2B-01-32-B0

</screen></informalexample>

<para>

You first need to set the boot protocol:
<informalexample><screen>

>>> set ewa0_protocol bootp

</screen></informalexample>
Then check the medium type is correct:
<informalexample><screen>

>>> set ewa0_mode <replaceable>mode</replaceable>

</screen></informalexample>
You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>.

<para>

Then, to boot from the first Ethernet interface, you would type:
<informalexample><screen>

>>>boot ewa0

</screen></informalexample>

<para>

If you wish to use a serial console, you <emphasis>must</emphasis> pass the
<userinput>console=</userinput> parameter to the kernel.  This can be done using the
<userinput>-flags</userinput> argument to the SRM <userinput>boot</userinput> command.  The serial
ports are named the same as their corresponding files in
<userinput>/dev</userinput>.  For example, to boot from <userinput>ewa0</userinput> and use a
console on the first serial port, you would type:
<informalexample><screen>

>>>boot ewa0 -flags console=ttyS0

</screen></informalexample>

  </para>
  </sect2>

  <sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title>
<para>

Type
<informalexample><screen>

&gt;&gt;&gt; boot xxxx -flags 0

</screen></informalexample>
where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation.

</para>
  </sect2>

  <sect2><title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title>

<para>

To boot a CD-ROM from the ARC console, find your sub-architecture code
name (see <xref linkend="supported-cpus"></xref>), then enter
<filename>\milo\linload.exe</filename> as the boot loader and
<filename>\milo\<replaceable>subarch</replaceable></filename> (where
<replaceable>subarch</replaceable> is the proper subarchitecture name)
as the OS Path in the `OS Selection Setup' menu. Ruffians make an
exception: You need to use <filename>\milo\ldmilo.exe</filename> as
boot loader.

</para>
  </sect2>


  <sect2><title>Booting from Floppies with the SRM Console</title>
<para>

At the SRM prompt (<command>&gt;&gt;&gt;</command>), issue the following
command:
        <informalexample><screen>

&gt;&gt;&gt; boot dva0 -flags 0
        
</screen></informalexample>
possibly replacing <filename>dva0</filename> with the actual device
name.  Usually, <filename>dva0</filename> is the floppy; type
        <informalexample><screen>

&gt;&gt;&gt; show dev
        
</screen></informalexample>
to see the list of devices (e.g., if you want to boot from a CD).
Note that if you are booting via MILO, <command>-flags</command> argument
is ignored, so you can just type <command>boot dva0</command>.

<para>

If everything works OK, you will eventually see the Linux kernel boot.

<para>

If you want to specify kernel parameters when booting via
<command>aboot</command>, use the following command:
        <informalexample><screen>

&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments"
        
</screen></informalexample>
(typed on one line), substituting, if necessary, the actual SRM boot
device name for <filename>dva0</filename>, the Linux boot device name for
<filename>fd0</filename>, and the desired kernel parameters for
<filename>arguments</filename>.

<para>

If you want to specify kernel parameters when booting via
<command>MILO</command>, you will have to interrupt bootstrap once you get
into MILO.  See <xref linkend="booting-from-milo"></xref>.

  <sect2><title>Booting from floppies with the ARC or AlphaBIOS Console</title>

<para>

In the OS Selection menu, set <command>linload.exe</command> as the boot
loader, and <command>milo</command> as the OS Path.  Bootstrap using the
newly created entry.

  <sect2><title>Booting from floppies with the APB boot loader (UP1000)</title>

<para>

To boot on this platform, run <command>\apb\apb.exe</command> from the
`Utility/Run Maintenance Program' menu, and type
      <informalexample><screen>

boot debian_install
      
</screen></informalexample>
 at the APB prompt.

</para>
  </sect2>

 <sect2 arch="alpha" id="booting-from-milo"><title>Booting with MILO</title>
<para>

MILO contained on the bootstrap media is configured to proceed straight
to Linux automatically.  Should you wish to intervene, all you need is to
press space during MILO countdown.

</para><para>

If you want to specify all the bits explicitly (for example, to supply
additional parameters), you can use a command like this:

<informalexample><screen>

MILO&gt; boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->
        
</screen></informalexample>

</para><para>

If you are booting from something other than a floppy, substitute
<filename>fd0</filename> in the above example with the appropriate device name
in Linux notation.  The <command>help</command> command would give you a brief
MILO command reference.

</para>
 </sect2>

  <sect2 arch="alpha"><title>Alpha Boot Parameters</title>
<para>

Depending on the console firmware from which you will be bootstrapping,
different methods apply for passing parameters to the kernel.  These
methods will be described below, separately for each bootstrap procedure.

</para>
</sect2>
1	toff	5236	<!-- retain these comments for translator revision tracking -->
2			<!-- $Id: alpha.xml,v 1.1 2003/10/22 14:43:55 toff Exp $ -->
3
4			<sect2 arch="alpha" id="alpha-firmware">
5			<title>Alpha Console Firmware</title>
6			<para>
7
8			Console firmware is stored in a flash ROM and started when an Alpha
9			system is powered up or reset. There are two different console
10			specifications used on Alpha systems, and hence two classes of console
11			firmware available:
12
13			</para>
14
15			<itemizedlist>
16			<listitem><para>
17
18			<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem
19			specification, which provides an operating environment for OpenVMS, Tru64
20			UNIX, and Linux operating systems.
21
22			</para></listitem>
23			<listitem><para>
24
25			<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the
26			Advanced RISC Computing (ARC) specification, which provides an operating
27			environment for Windows NT.
28
29			</para></listitem>
30			</itemizedlist>
31
32			<para>
33
34			From the user's perspective, the most important difference between SRM
35			and ARC is that the choice of console constrains the possible
36			disk-partitioning scheme for the hard disk which you wish to boot off
37			of.
38
39			</para><para>
40
41			ARC requires that you use an MS-DOS partition table (as created by
42			<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition
43			tables are the ``native'' partition format when booting from ARC. In
44			fact, since AlphaBIOS contains a disk partitioning utility, you may
45			prefer to partition your disks from the firmware menus before
46			installing Linux.
47
48			</para><para>
49
50			Conversely, SRM is <emphasis>incompatible</emphasis> with MS-DOS partition tables.
51			<footnote>Specifically, the bootsector format required by the Console
52			Subsystem Specification conflicts with the placement of the DOS
53			partition table.</footnote> Since Tru64 Unix uses the BSD disklabel format,
54			this is the ``native'' partition format for SRM installations.
55
56			</para><para>
57
58			Because GNU/Linux is the only operating system on Alpha that can be
59			booted from both console types, the choice will also depend on what
60			other operating systems you wish to run on the same machine. All
61			other Unix-like operating systems (Tru64 Unix, FreeBSD, OpenBSD, and
62			NetBSD) and OpenVMS can only boot from SRM, whereas Windows NT can
63			only boot from ARC.
64
65			</para><para>
66
67			The following table summarizes available and supported system
68			type/console combinations (see <xref linkend="supported-cpus"></xref> for the
69			system type names). The word `ARC' below denotes any of the
70			ARC-compliant consoles.
71
72			</para><para>
73
74			<informaltable><tgroup cols="2">
75			<thead>
76			<row>
77			<entry>System Type</entry>
78			<entry>Console Type Supported</entry>
79			</row>
80			</thead>
81
82			<tbody>
83			<row>
84			<entry>alcor</entry>
85			<entry>ARC or SRM</entry>
86			</row><row>
87			<entry>avanti</entry>
88			<entry>ARC or SRM</entry>
89			</row><row>
90			<entry>book1</entry>
91			<entry>SRM only</entry>
92			</row><row>
93			<entry>cabriolet</entry>
94			<entry>ARC or SRM</entry>
95			</row><row>
96			<entry>dp264</entry>
97			<entry>SRM only</entry>
98			</row><row>
99			<entry>eb164</entry>
100			<entry>ARC or SRM</entry>
101			</row><row>
102			<entry>eb64p</entry>
103			<entry>ARC or SRM</entry>
104			</row><row>
105			<entry>eb66</entry>
106			<entry>ARC or SRM</entry>
107			</row><row>
108			<entry>eb66p</entry>
109			<entry>ARC or SRM</entry>
110			</row><row>
111			<entry>jensen</entry>
112			<entry>SRM only</entry>
113			</row><row>
114			<entry>lx164</entry>
115			<entry>ARC or SRM</entry>
116			</row><row>
117			<entry>miata</entry>
118			<entry>ARC or SRM</entry>
119			</row><row>
120			<entry>mikasa</entry>
121			<entry>ARC or SRM</entry>
122			</row><row>
123			<entry>mikasa-p</entry>
124			<entry>SRM only</entry>
125			</row><row>
126			<entry>nautilus</entry>
127			<entry>ARC only (see motherboard manual)</entry>
128			</row><row>
129			<entry>noname</entry>
130			<entry>ARC or SRM</entry>
131			</row><row>
132			<entry>noritake</entry>
133			<entry>SRM only</entry>
134			</row><row>
135			<entry>noritake-p</entry>
136			<entry>SRM only</entry>
137			</row><row>
138			<entry>pc164</entry>
139			<entry>ARC or SRM</entry>
140			</row><row>
141			<entry>rawhide</entry>
142			<entry>SRM only</entry>
143			</row><row>
144			<entry>ruffian</entry>
145			<entry>ARC only</entry>
146			</row><row>
147			<entry>sable</entry>
148			<entry>SRM only</entry>
149			</row><row>
150			<entry>sable-g</entry>
151			<entry>SRM only</entry>
152			</row><row>
153			<entry>sx164</entry>
154			<entry>ARC or SRM</entry>
155			</row><row>
156			<entry>takara</entry>
157			<entry>ARC or SRM</entry>
158			</row><row>
159			<entry>xl</entry>
160			<entry>ARC only</entry>
161			</row><row>
162			<entry>xlt</entry>
163			<entry>ARC or SRM</entry>
164			</row>
165
166			</tbody>
167			</tgroup>
168			</informaltable>
169
170			</para><para>
171
172			Generally, none of these consoles can boot Linux directly, so the
173			assistance of an intermediary bootloader is required. There are two
174			mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>.
175
176			</para><para>
177
178			<command>MILO</command> is itself a console, which replaces ARC or SRM in
179			memory. <command>MILO</command> can be booted from both ARC and SRM and is
180			the only way to bootstrap Linux from the ARC console.
181			<command>MILO</command> is platform-specific (a different <command>MILO</command>
182			is needed for each system type) and exist only for those systems, for
183			which ARC support is shown in the table above. See also the
184			(unfortunately outdated)
185			<ulink url="&url-milo-howto;"> name="MILO HOWTO"</ulink>.
186
187			</para><para>
188
189			<command>aboot</command> is a small, platform-independent bootloader, which
190			runs from SRM only. See the (also unfortunately outdated) <ulink
191			url="&url-srm-howto;">SRM HOWTO</ulink> for more information on
192			<command>aboot</command>.
193
194			</para><para>
195
196			Thus, three scenarios are generally possible, depending on the
197			system's console firmware and whether or not <command>MILO</command> is
198			available:
199
200			<informalexample><screen>
201
202			SRM -> aboot
203			SRM -> MILO
204			ARC -> MILO
205
206			</screen></informalexample>
207
208			</para><para>
209
210			The UP1000 motherboard (subarchitecture name `nautilus') from Alpha
211			Processor, Inc. is different from all the others, in that it uses an
212			API-specific bootloader that runs under AlphaBIOS firmware.
213
214			</para><para>
215
216			Because <command>MILO</command> is not available for any of the Alpha
217			systems currently in production (as of February 2000), and because it
218			is no longer necessary to buy an OpenVMS or Tru64 Unix license to have
219			SRM firmware on your older Alpha, it is recommended that you use SRM and
220			<command>aboot</command> on new installations of GNU/Linux, unless you wish
221			to dual-boot with Windows NT.
222
223			</para><para>
224
225			The majority of AlphaServers and all current server and workstation
226			products contain both SRM and AlphaBIOS in their firmware. For
227			"half-flash" machines such as the various evaluation boards, it is
228			possible to switch from one version to another by reflashing the
229			firmware. Also, once SRM is installed, it is possible to run
230			ARC/AlphaBIOS from a floppy disk (using the `arc' command). For the
231			reasons mentioned above, we recommend switching to SRM before
232			installing &debian;.
233
234			</para><para>
235
236			As on other architectures, you should install the newest available
237			revision of the firmware <footnote>Except on Jensen, where Linux is
238			not supported on firmware versions newer than 1.7 - see <ulink
239			url="&url-jensen-howto;"></ulink>> for more information</footnote> before
240			installing &debian;. For Alpha, firmware updates can be obtained from
241			<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>.
242
243			</para>
244			</sect2>
245
246
247			<sect2 arch="alpha"><title>Booting with TFTP</title>
248			<para>
249
250			In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput>
251			prefix, and will be listed in the output of the <userinput>show dev</userinput> command,
252			like this (edited slightly):
253			<informalexample><screen>
254
255			>>>show dev
256			ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65
257			ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54
258			ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0
259
260			</screen></informalexample>
261
262			<para>
263
264			You first need to set the boot protocol:
265			<informalexample><screen>
266
267			>>> set ewa0_protocol bootp
268
269			</screen></informalexample>
270			Then check the medium type is correct:
271			<informalexample><screen>
272
273			>>> set ewa0_mode <replaceable>mode</replaceable>
274
275			</screen></informalexample>
276			You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>.
277
278			<para>
279
280			Then, to boot from the first Ethernet interface, you would type:
281			<informalexample><screen>
282
283			>>>boot ewa0
284
285			</screen></informalexample>
286
287			<para>
288
289			If you wish to use a serial console, you <emphasis>must</emphasis> pass the
290			<userinput>console=</userinput> parameter to the kernel. This can be done using the
291			<userinput>-flags</userinput> argument to the SRM <userinput>boot</userinput> command. The serial
292			ports are named the same as their corresponding files in
293			<userinput>/dev</userinput>. For example, to boot from <userinput>ewa0</userinput> and use a
294			console on the first serial port, you would type:
295			<informalexample><screen>
296
297			>>>boot ewa0 -flags console=ttyS0
298
299			</screen></informalexample>
300
301			</para>
302			</sect2>
303
304			<sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title>
305			<para>
306
307			Type
308			<informalexample><screen>
309
310			>>> boot xxxx -flags 0
311
312			</screen></informalexample>
313			where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation.
314
315			</para>
316			</sect2>
317
318			<sect2><title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title>
319
320			<para>
321
322			To boot a CD-ROM from the ARC console, find your sub-architecture code
323			name (see <xref linkend="supported-cpus"></xref>), then enter
324			<filename>\milo\linload.exe</filename> as the boot loader and
325			<filename>\milo\<replaceable>subarch</replaceable></filename> (where
326			<replaceable>subarch</replaceable> is the proper subarchitecture name)
327			as the OS Path in the `OS Selection Setup' menu. Ruffians make an
328			exception: You need to use <filename>\milo\ldmilo.exe</filename> as
329			boot loader.
330
331			</para>
332			</sect2>
333
334
335			<sect2><title>Booting from Floppies with the SRM Console</title>
336			<para>
337
338			At the SRM prompt (<command>>>></command>), issue the following
339			command:
340			<informalexample><screen>
341
342			>>> boot dva0 -flags 0
343
344			</screen></informalexample>
345			possibly replacing <filename>dva0</filename> with the actual device
346			name. Usually, <filename>dva0</filename> is the floppy; type
347			<informalexample><screen>
348
349			>>> show dev
350
351			</screen></informalexample>
352			to see the list of devices (e.g., if you want to boot from a CD).
353			Note that if you are booting via MILO, <command>-flags</command> argument
354			is ignored, so you can just type <command>boot dva0</command>.
355
356			<para>
357
358			If everything works OK, you will eventually see the Linux kernel boot.
359
360			<para>
361
362			If you want to specify kernel parameters when booting via
363			<command>aboot</command>, use the following command:
364			<informalexample><screen>
365
366			>>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments"
367
368			</screen></informalexample>
369			(typed on one line), substituting, if necessary, the actual SRM boot
370			device name for <filename>dva0</filename>, the Linux boot device name for
371			<filename>fd0</filename>, and the desired kernel parameters for
372			<filename>arguments</filename>.
373
374			<para>
375
376			If you want to specify kernel parameters when booting via
377			<command>MILO</command>, you will have to interrupt bootstrap once you get
378			into MILO. See <xref linkend="booting-from-milo"></xref>.
379
380			<sect2><title>Booting from floppies with the ARC or AlphaBIOS Console</title>
381
382			<para>
383
384			In the OS Selection menu, set <command>linload.exe</command> as the boot
385			loader, and <command>milo</command> as the OS Path. Bootstrap using the
386			newly created entry.
387
388			<sect2><title>Booting from floppies with the APB boot loader (UP1000)</title>
389
390			<para>
391
392			To boot on this platform, run <command>\apb\apb.exe</command> from the
393			`Utility/Run Maintenance Program' menu, and type
394			<informalexample><screen>
395
396			boot debian_install
397
398			</screen></informalexample>
399			at the APB prompt.
400
401			</para>
402			</sect2>
403
404			<sect2 arch="alpha" id="booting-from-milo"><title>Booting with MILO</title>
405			<para>
406
407			MILO contained on the bootstrap media is configured to proceed straight
408			to Linux automatically. Should you wish to intervene, all you need is to
409			press space during MILO countdown.
410
411			</para><para>
412
413			If you want to specify all the bits explicitly (for example, to supply
414			additional parameters), you can use a command like this:
415
416			<informalexample><screen>
417
418			MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->
419
420			</screen></informalexample>
421
422			</para><para>
423
424			If you are booting from something other than a floppy, substitute
425			<filename>fd0</filename> in the above example with the appropriate device name
426			in Linux notation. The <command>help</command> command would give you a brief
427			MILO command reference.
428
429			</para>
430			</sect2>
431
432			<sect2 arch="alpha"><title>Alpha Boot Parameters</title>
433			<para>
434
435			Depending on the console firmware from which you will be bootstrapping,
436			different methods apply for passing parameters to the kernel. These
437			methods will be described below, separately for each bootstrap procedure.
438
439			</para>
440			</sect2>