1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 11648 untranslated -->
4
<sect2 arch="alpha" id="alpha-firmware">
5
<title>Alpha Console Firmware</title>
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
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.
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.
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
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
50
Conversely, SRM is <emphasis>incompatible</emphasis> with MS-DOS partition tables.
51
<footnote><para>Specifically, the bootsector format required by the Console
52
Subsystem Specification conflicts with the placement of the DOS
53
partition table.</para></footnote> Since Tru64 Unix uses the BSD disklabel format,
54
this is the ``native'' partition format for SRM installations.
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
67
The following table summarizes available and supported system
68
type/console combinations (see <xref linkend="alpha-cpus"/> for the
69
system type names). The word `ARC' below denotes any of the
70
ARC-compliant consoles.
74
<informaltable><tgroup cols="2">
77
<entry>System Type</entry>
78
<entry>Console Type Supported</entry>
85
<entry>ARC or SRM</entry>
88
<entry>ARC or SRM</entry>
91
<entry>SRM only</entry>
93
<entry>cabriolet</entry>
94
<entry>ARC or SRM</entry>
97
<entry>SRM only</entry>
100
<entry>ARC or SRM</entry>
103
<entry>ARC or SRM</entry>
106
<entry>ARC or SRM</entry>
109
<entry>ARC or SRM</entry>
111
<entry>jensen</entry>
112
<entry>SRM only</entry>
115
<entry>ARC or SRM</entry>
118
<entry>ARC or SRM</entry>
120
<entry>mikasa</entry>
121
<entry>ARC or SRM</entry>
123
<entry>mikasa-p</entry>
124
<entry>SRM only</entry>
126
<entry>nautilus</entry>
127
<entry>ARC only (see motherboard manual)</entry>
129
<entry>noname</entry>
130
<entry>ARC or SRM</entry>
132
<entry>noritake</entry>
133
<entry>SRM only</entry>
135
<entry>noritake-p</entry>
136
<entry>SRM only</entry>
139
<entry>ARC or SRM</entry>
141
<entry>rawhide</entry>
142
<entry>SRM only</entry>
144
<entry>ruffian</entry>
145
<entry>ARC only</entry>
148
<entry>SRM only</entry>
150
<entry>sable-g</entry>
151
<entry>SRM only</entry>
154
<entry>ARC or SRM</entry>
156
<entry>takara</entry>
157
<entry>ARC or SRM</entry>
160
<entry>ARC only</entry>
163
<entry>ARC or SRM</entry>
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>.
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;">MILO HOWTO</ulink>.
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>.
196
Thus, three scenarios are generally possible, depending on the
197
system's console firmware and whether or not <command>MILO</command> is
200
<informalexample><screen>
206
</screen></informalexample>
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.
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.
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 <command>arc</command>
232
reasons mentioned above, we recommend switching to SRM before
237
As on other architectures, you should install the newest available
238
revision of the firmware <footnote><para>Except on Jensen, where
239
Linux is not supported on firmware versions newer than 1.7 - see
240
<ulink url="&url-jensen-howto;"></ulink> for more
241
information</para></footnote> before installing &debian;. For
242
Alpha, firmware updates can be obtained from
243
<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>.
249
<sect2 arch="alpha"><title>Booting with TFTP</title>
252
In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput>
253
prefix, and will be listed in the output of the <userinput>show dev</userinput> command,
254
like this (edited slightly):
256
<informalexample><screen>
259
ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65
260
ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54
261
ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0
263
</screen></informalexample>
265
You first need to set the boot protocol:
266
<informalexample><screen>
268
>>> set ewa0_protocol bootp
270
</screen></informalexample>
272
Then check the medium type is correct:
274
<informalexample><screen>
276
>>> set ewa0_mode <replaceable>mode</replaceable>
278
</screen></informalexample>
280
You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>.
284
Then, to boot from the first Ethernet interface, you would type:
286
<informalexample><screen>
290
</screen></informalexample>
294
If you wish to use a serial console, you <emphasis>must</emphasis>
295
pass the <userinput>console=</userinput> parameter to the kernel.
296
This can be done using the <userinput>-flags</userinput> argument to
297
the SRM <userinput>boot</userinput> command. The serial ports are
298
named the same as their corresponding files in
299
<userinput>/dev</userinput>. For example, to boot from
300
<userinput>ewa0</userinput> and use a console on the first serial
301
port, you would type:
303
<informalexample><screen>
305
>>> boot ewa0 -flags console=ttyS0
307
</screen></informalexample>
312
<sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title>
317
<informalexample><screen>
319
>>> boot xxxx -flags 0
321
</screen></informalexample>
323
where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation.
329
<title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title>
332
To boot a CD-ROM from the ARC console, find your sub-architecture code
333
name (see <xref linkend="alpha-cpus"/>), then enter
334
<filename>\milo\linload.exe</filename> as the boot loader and
335
<filename>\milo\<replaceable>subarch</replaceable></filename> (where
336
<replaceable>subarch</replaceable> is the proper subarchitecture name)
337
as the OS Path in the `OS Selection Setup' menu. Ruffians make an
338
exception: You need to use <filename>\milo\ldmilo.exe</filename> as
346
<title>Booting from Floppies with the SRM Console</title>
349
At the SRM prompt (<prompt>>>></prompt>), issue the following
352
<informalexample><screen>
354
>>> boot dva0 -flags 0
356
</screen></informalexample>
358
possibly replacing <filename>dva0</filename> with the actual device
359
name. Usually, <filename>dva0</filename> is the floppy; type
361
<informalexample><screen>
363
>>> show dev
365
</screen></informalexample>
367
to see the list of devices (e.g., if you want to boot from a CD).
368
Note that if you are booting via MILO, <command>-flags</command> argument
369
is ignored, so you can just type <command>boot dva0</command>.
370
If everything works OK, you will eventually see the Linux kernel boot.
374
If you want to specify kernel parameters when booting via
375
<command>aboot</command>, use the following command:
376
<informalexample><screen>
378
>>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments"
380
</screen></informalexample>
381
(typed on one line), substituting, if necessary, the actual SRM boot
382
device name for <filename>dva0</filename>, the Linux boot device name for
383
<filename>fd0</filename>, and the desired kernel parameters for
384
<filename>arguments</filename>.
388
If you want to specify kernel parameters when booting via
389
<command>MILO</command>, you will have to interrupt bootstrap once you get
390
into MILO. See <xref linkend="booting-from-milo"/>.
396
<title>Booting from Floppies with the ARC or AlphaBIOS Console</title>
400
In the OS Selection menu, set <command>linload.exe</command> as the boot
401
loader, and <command>milo</command> as the OS Path. Bootstrap using the
408
<title>Booting from Floppies with the APB Boot Loader (UP1000)</title>
412
To boot on this platform, run <command>\apb\apb.exe</command> from the
413
`Utility/Run Maintenance Program' menu, and type
414
<informalexample><screen>
418
</screen></informalexample>
424
<sect2 arch="alpha" id="booting-from-milo"><title>Booting with MILO</title>
427
MILO contained on the bootstrap media is configured to proceed straight
428
to Linux automatically. Should you wish to intervene, all you need is to
429
press space during MILO countdown.
433
If you want to specify all the bits explicitly (for example, to supply
434
additional parameters), you can use a command like this:
436
<informalexample><screen>
438
MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->
440
</screen></informalexample>
444
If you are booting from something other than a floppy, substitute
445
<filename>fd0</filename> in the above example with the appropriate device name
446
in Linux notation. The <command>help</command> command would give you a brief
447
MILO command reference.