| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id$ -->
|
| 3 |
|
| 4 |
|
| 5 |
<sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title>
|
| 6 |
|
| 7 |
<sect3>
|
| 8 |
<title>SGI TFTP Booting</title>
|
| 9 |
<para>
|
| 10 |
|
| 11 |
After entering the command monitor use
|
| 12 |
|
| 13 |
<informalexample><screen>
|
| 14 |
bootp():
|
| 15 |
</screen></informalexample>
|
| 16 |
|
| 17 |
on SGI machines to boot linux and to begin installation of the Debian
|
| 18 |
Software. In order to make this
|
| 19 |
work you may have to unset the <envar>netaddr</envar> environment
|
| 20 |
variable. Type
|
| 21 |
|
| 22 |
<informalexample><screen>
|
| 23 |
unsetenv netaddr
|
| 24 |
</screen></informalexample>
|
| 25 |
|
| 26 |
in the command monitor to do this.
|
| 27 |
|
| 28 |
</para>
|
| 29 |
</sect3>
|
| 30 |
|
| 31 |
<sect3>
|
| 32 |
<title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
|
| 33 |
<para>
|
| 34 |
|
| 35 |
On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot
|
| 36 |
loader via TFTP which will then load and start the Debian installer. In
|
| 37 |
most cases, you will first obtain an IP address via DHCP but it is also
|
| 38 |
possible to configure a static address. In order to use DHCP, you can
|
| 39 |
enter the following command on the CFE prompt:
|
| 40 |
|
| 41 |
<informalexample><screen>
|
| 42 |
ifconfig eth0 -auto
|
| 43 |
</screen></informalexample>
|
| 44 |
|
| 45 |
Once you have obtained an IP address, you can load SiByl with the following
|
| 46 |
command:
|
| 47 |
|
| 48 |
<informalexample><screen>
|
| 49 |
boot 192.168.1.1:/boot/sibyl
|
| 50 |
</screen></informalexample>
|
| 51 |
|
| 52 |
You need to substitute the IP address listed in this example with either
|
| 53 |
the name or the IP address of your TFTP server. Once you issue this
|
| 54 |
command, the installer will be loaded automatically.
|
| 55 |
|
| 56 |
</para>
|
| 57 |
</sect3>
|
| 58 |
</sect2>
|
| 59 |
|
| 60 |
<sect2 arch="mips"><title>Boot Parameters</title>
|
| 61 |
|
| 62 |
<sect3>
|
| 63 |
<title>SGI TFTP Booting</title>
|
| 64 |
<para>
|
| 65 |
|
| 66 |
On SGI machines you can append boot parameters to the
|
| 67 |
<command>bootp():</command> command in the command monitor.
|
| 68 |
|
| 69 |
</para><para>
|
| 70 |
|
| 71 |
Following the <command>bootp():</command> command you can give the
|
| 72 |
path and name of the file to boot if you did not give an explicit name
|
| 73 |
via your bootp/dhcp server. Example:
|
| 74 |
|
| 75 |
<informalexample><screen>
|
| 76 |
bootp():/boot/tftpboot.img
|
| 77 |
</screen></informalexample>
|
| 78 |
|
| 79 |
Further kernel parameters can be passed via <command>append</command>:
|
| 80 |
|
| 81 |
<informalexample><screen>
|
| 82 |
bootp(): append="root=/dev/sda1"
|
| 83 |
</screen></informalexample>
|
| 84 |
|
| 85 |
</para>
|
| 86 |
</sect3>
|
| 87 |
|
| 88 |
<sect3>
|
| 89 |
<title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
|
| 90 |
<para>
|
| 91 |
|
| 92 |
You cannot pass any boot parameters directly from the CFE prompt. Instead,
|
| 93 |
you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP
|
| 94 |
server and add your parameters to the <replaceable>extra_args</replaceable>
|
| 95 |
variable.
|
| 96 |
|
| 97 |
</para>
|
| 98 |
</sect3>
|
| 99 |
|
| 100 |
</sect2>
|
Parent Directory
| 
Revision Log