diff options
author | Martin Michlmayr <tbm@cyrius.com> | 2006-03-07 19:53:29 +0000 |
---|---|---|
committer | Martin Michlmayr <tbm@cyrius.com> | 2006-03-07 19:53:29 +0000 |
commit | 1dc0b1992fa67229f3aeb117e1e0df172330388a (patch) | |
tree | 1d22f3c28999f32dd85845ed6f387dfc87bb36d5 /en | |
parent | a3dcdfbb98f3c147dbae9b47b7339a9ccfa1606e (diff) | |
download | installation-guide-1dc0b1992fa67229f3aeb117e1e0df172330388a.zip |
Describe how to boot a Cobalt machine.
Diffstat (limited to 'en')
-rw-r--r-- | en/boot-installer/boot-installer.xml | 4 | ||||
-rw-r--r-- | en/boot-installer/mipsel.xml | 94 | ||||
-rw-r--r-- | en/hardware/supported/mipsel.xml | 10 |
3 files changed, 97 insertions, 11 deletions
diff --git a/en/boot-installer/boot-installer.xml b/en/boot-installer/boot-installer.xml index b064e9b04..a1845a192 100644 --- a/en/boot-installer/boot-installer.xml +++ b/en/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> @@ -19,7 +19,7 @@ &boot-installer-ia64.xml; &boot-installer-m68k.xml; &boot-installer-mips.xml; -<!-- &boot-installer-mipsel.xml; --> +&boot-installer-mipsel.xml; &boot-installer-s390.xml; &boot-installer-powerpc.xml; &boot-installer-sparc.xml; diff --git a/en/boot-installer/mipsel.xml b/en/boot-installer/mipsel.xml index a9fd14ed6..e3d185938 100644 --- a/en/boot-installer/mipsel.xml +++ b/en/boot-installer/mipsel.xml @@ -1,12 +1,96 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect2 arch="mipsel"> - <title></title> + <sect2 arch="mipsel" id="boot-tftp"><title>Booting with TFTP</title> + + <sect3> + <title>Cobalt TFTP Booting</title> <para> -<!-- Placeholder document; please write and include in - boot-installer.xml and build/templates/docstruct.ent --> +Strictly speaking, Cobalt does not ue TFTP but NFS to boot. You need to +install an NFS server and put the installer files in +<filename>/nfsroot</filename>. When you boot your Cobalt, you have to +press the left and the right cursor buttons at the same time and the +machine will boot via the network from NFS. It will then display several +options on the display. There are the following two installation methods: + +<itemizedlist> +<listitem><para> + +Via SSH (default): In this case, the installer will configure the network +via DHCP and start an SSH server. It will then display a random password +and other login information (such as the IP address) on the Cobalt LCD. +When you connect to the machine with an SSH client you can start with +the installation. + +</para></listitem> +<listitem><para> + +Via serial console: Using a null modem cable, you can connect to the serial +port of your Cobalt machine (using 115200 bps) and perform the installation +this way. This option is not available on Qube 2700 (Qube1) machines since +they have no serial port. + +</para></listitem> +</itemizedlist> </para> - </sect2> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot +loader via TFTP which will then load and start the Debian installer. In +most cases, you will first obtain an IP address via DHCP but it is also +possible to configure a static address. In order to use DHCP, you can +enter the following command on the CFE prompt: + +<informalexample><screen> +ifconfig eth0 -auto +</screen></informalexample> + +Once you have obtained an IP address, you can load SiByl with the following +command: + +<informalexample><screen> +boot 192.168.1.1:/boot/sibyl +</screen></informalexample> + +You need to substitute the IP address listed in this example with either +the name or the IP address of your TFTP server. Once you issue this +command, the installer will be loaded automatically. + +</para> +</sect3> + </sect2> + + <sect2 arch="mips"><title>Boot Parameters</title> + + <sect3> + <title>Cobalt TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly. Instead, you have to edit +the <filename>/nfsroot/default.colo</filename> file on the NFS server and +add your parameters to the <replaceable>args</replaceable> variable. + +</para> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP +server and add your parameters to the <replaceable>extra_args</replaceable> +variable. + +</para> + </sect3> + + </sect2> diff --git a/en/hardware/supported/mipsel.xml b/en/hardware/supported/mipsel.xml index aa06c45ce..981a1a820 100644 --- a/en/hardware/supported/mipsel.xml +++ b/en/hardware/supported/mipsel.xml @@ -15,8 +15,8 @@ DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> -Cobalt Microserver: only MIPS based Cobalt machines are covered here. -This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway +Cobalt Microserver: only MIPS based Cobalt machines are covered here. This +included the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> @@ -97,8 +97,10 @@ The Debian installation system works on the following machines: </para><para> -All Cobalt machines are supported which have a serial console (which is -needed for the installation). +All Cobalt machines are supported. In the past, only machines with a +serial console were supported (that is, all machines except for the Qube +2700, aka Qube1). However, installations are now also possible through +SSH. </para><para> |