|
|
50.
|
|
|
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>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:233
|
|
|
51.
|
|
|
<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;">MILO HOWTO</ulink>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:239
|
|
|
52.
|
|
|
<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>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:249
|
|
|
53.
|
|
|
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> 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. |
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:256
|
|
|
54.
|
|
|
The majority of AlphaServers and all current server and workstation products contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</quote> 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 <command>arc</command> command). For the reasons mentioned above, we recommend switching to SRM before installing &debian;.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:271
|
|
|
55.
|
|
|
As on other architectures, you should install the newest available revision of the firmware<footnote> <para> 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. </para> </footnote> before installing &debian;. For Alpha, firmware updates can be obtained from <ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:282
|
|
|
57.
|
|
|
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> You first need to set the boot protocol: <informalexample><screen>
>>> set ewa0_protocols 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>. |
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:302
|
|
|
58.
|
|
|
Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>
>>> boot ewa0 -flags ""
</screen></informalexample> This will boot using the default kernel parameters as included in the netboot image. |
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:320
|
|
|
59.
|
|
|
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>. Also, when specifying additional kernel parameters, you must repeat certain default options that are needed by the &d-i; images. For example, to boot from <userinput>ewa0</userinput> and use a console on the first serial port, you would type:
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:329
|
|
|
60.
|
|
|
>>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"
|
|
|
Tag: screen
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:341
|
