summaryrefslogtreecommitdiff
path: root/ca/boot-installer/mips.xml
diff options
context:
space:
mode:
authorJoey Hess <joeyh@debian.org>2005-10-07 19:51:38 +0000
committerJoey Hess <joeyh@debian.org>2005-10-07 19:51:38 +0000
commit1ea73eea5ecc6a8ed901316049259aee737ee554 (patch)
tree03a077f0b1b1548f3c806bd1c5795964fba0fb52 /ca/boot-installer/mips.xml
downloadinstallation-guide-1ea73eea5ecc6a8ed901316049259aee737ee554.zip
move manual to top-level directory, split out of debian-installer package
Diffstat (limited to 'ca/boot-installer/mips.xml')
-rw-r--r--ca/boot-installer/mips.xml100
1 files changed, 100 insertions, 0 deletions
diff --git a/ca/boot-installer/mips.xml b/ca/boot-installer/mips.xml
new file mode 100644
index 000000000..f237aa957
--- /dev/null
+++ b/ca/boot-installer/mips.xml
@@ -0,0 +1,100 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 24663 untranslated -->
+
+
+ <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title>
+
+ <sect3>
+ <title>SGI Indys TFTP Booting</title>
+<para>
+
+After entering the command monitor use
+
+<informalexample><screen>
+bootp():
+</screen></informalexample>
+
+on SGI Indys to boot linux and to begin installation of the Debian
+Software. In order to make this
+work you may have to unset the <envar>netaddr</envar> environment
+variable. Type
+
+<informalexample><screen>
+unsetenv netaddr
+</screen></informalexample>
+
+in the command monitor to do this.
+
+</para>
+ </sect3>
+
+ <sect3>
+ <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>SGI Indys TFTP Booting</title>
+<para>
+
+On SGI Indys you can append boot parameters to the
+<command>bootp():</command> command in the command monitor.
+
+</para><para>
+
+Following the <command>bootp():</command> command you can give the
+path and name of the file to boot if you did not give an explicit name
+via your bootp/dhcp server. Example:
+
+<informalexample><screen>
+bootp():/boot/tftpboot.img
+</screen></informalexample>
+
+Further kernel parameters can be passed via <command>append</command>:
+
+<informalexample><screen>
+bootp(): append="root=/dev/sda1"
+</screen></informalexample>
+
+</para>
+ </sect3>
+
+ <sect3>
+ <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>