Browsing Occitan (post 1500) translation

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 -&gt; aboot
SRM -&gt; MILO
ARC -&gt; 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.

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;.

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 &mdash; 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>.

56.

Booting with TFTP

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>
&gt;&gt;&gt; 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>
&gt;&gt;&gt; set ewa0_protocols bootp
</screen></informalexample> Then check the medium type is correct: <informalexample><screen>
&gt;&gt;&gt; set ewa0_mode <replaceable>mode</replaceable>
</screen></informalexample> You can get a listing of valid modes with <userinput>&gt;&gt;&gt;set ewa0_mode</userinput>.

58.

Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>
&gt;&gt;&gt; boot ewa0 -flags ""
</screen></informalexample> This will boot using the default kernel parameters as included in the netboot image.

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:

60.

&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 console=ttyS0&quot;

61.

Booting from CD-ROM with the SRM Console

62.

The &debian; install CDs include several preconfigured boot options for VGA and serial consoles. Type <informalexample><screen>
&gt;&gt;&gt; boot xxxx -flags 0
</screen></informalexample> to boot using VGA console, where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. To use serial console on the first serial device, type <informalexample><screen>
&gt;&gt;&gt; boot xxxx -flags 1
</screen></informalexample> and for console on the second serial port, type