| 1 |
<!-- retain these comments for translator revision tracking --> |
<!-- retain these comments for translator revision tracking --> |
| 2 |
<!-- $Id: mips.xml 11648 2004-03-22 00:37:46Z joeyh $ --> |
<!-- original version: 22939 untranslated --> |
| 3 |
|
|
| 4 |
|
|
| 5 |
<sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title> |
<sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title> |
| 6 |
|
|
| 7 |
|
<sect3> |
| 8 |
|
<title>SGI Indys TFTP Booting</title> |
| 9 |
<para> |
<para> |
| 10 |
|
|
| 11 |
After entering the command monitor use |
After entering the command monitor use |
| 12 |
<informalexample><screen> |
<informalexample><screen> |
| 13 |
|
|
| 14 |
bootp(): root=/dev/ram0 |
bootp(): |
| 15 |
|
|
| 16 |
</screen></informalexample> |
</screen></informalexample> |
| 17 |
on SGI Indys to boot linux and to begin installation of the Debian |
on SGI Indys to boot linux and to begin installation of the Debian |
| 18 |
Software. In order to make this |
Software. In order to make this |
| 19 |
work you may have to unset the <envar>netaddr</envar> environment |
work you may have to unset the <envar>netaddr</envar> environment |
| 20 |
variable. Type |
variable. Type |
| 21 |
<informalexample><screen> |
<informalexample><screen> |
| 22 |
|
|
| 23 |
unsetenv netaddr |
unsetenv netaddr |
| 24 |
|
|
| 25 |
</screen></informalexample> |
</screen></informalexample> |
| 26 |
in the command monitor to do this. |
in the command monitor to do this. |
| 27 |
|
|
| 28 |
</para> |
</para> |
| 29 |
</sect2> |
</sect3> |
| 30 |
|
|
| 31 |
|
<sect3> |
| 32 |
|
<title>Broadcom BCM91250A TFTP Booting</title> |
| 33 |
|
<para> |
| 34 |
|
|
| 35 |
|
On the Broadcom BCM91250A evaluation board, 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 |
|
|
| 43 |
|
ifconfig eth0 -auto |
| 44 |
|
|
| 45 |
|
</screen></informalexample> |
| 46 |
|
|
| 47 |
|
Once you have obtained an IP address, you can load SiByl with the following |
| 48 |
|
command: |
| 49 |
|
|
| 50 |
|
<informalexample><screen> |
| 51 |
|
|
| 52 |
|
boot 192.168.1.1:/boot/sibyl |
| 53 |
|
|
| 54 |
|
</screen></informalexample> |
| 55 |
|
|
| 56 |
|
You need to substitute the IP address listed in this example with either |
| 57 |
|
the name or the IP address of your TFTP server. Once you issue this |
| 58 |
|
command, the installer will be loaded automatically. |
| 59 |
|
|
| 60 |
|
</para> |
| 61 |
|
</sect3> |
| 62 |
|
</sect2> |
| 63 |
|
|
| 64 |
<sect2 arch="mips"><title>Boot Parameters</title> |
<sect2 arch="mips"><title>Boot Parameters</title> |
| 65 |
|
|
| 66 |
|
<sect3> |
| 67 |
|
<title>SGI Indys TFTP Booting</title> |
| 68 |
<para> |
<para> |
| 69 |
|
|
| 70 |
On SGI Indys you can append boot parameters to the |
On SGI Indys you can append boot parameters to the |
| 75 |
Following the <command>bootp():</command> command you can give the |
Following the <command>bootp():</command> command you can give the |
| 76 |
path and name of the file to boot if you did not give an explicit name |
path and name of the file to boot if you did not give an explicit name |
| 77 |
via your bootp/dhcp server - Example: |
via your bootp/dhcp server - Example: |
| 78 |
<command>bootp():/boot/tftpboot.img</command> |
<informalexample><screen> |
| 79 |
|
|
| 80 |
|
bootp():/boot/tftpboot.img |
| 81 |
|
|
| 82 |
|
</screen></informalexample> |
| 83 |
|
</para><para> |
| 84 |
|
|
| 85 |
|
Further kernel parameters can be passed via <command>append</command>: |
| 86 |
|
<informalexample><screen> |
| 87 |
|
|
| 88 |
|
bootp(): append="root=/dev/sda1" |
| 89 |
|
|
| 90 |
|
</screen></informalexample> |
| 91 |
|
</para> |
| 92 |
|
</sect3> |
| 93 |
|
|
| 94 |
|
<sect3> |
| 95 |
|
<title>Broadcom BCM91250A TFTP Booting</title> |
| 96 |
|
<para> |
| 97 |
|
|
| 98 |
|
You cannot pass any boot parameters directly from the CFE prompt. Instead, |
| 99 |
|
you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP |
| 100 |
|
server and add your parameters to the <replaceable>extra_args</replaceable> |
| 101 |
|
variable. |
| 102 |
|
|
| 103 |
</para> |
</para> |
| 104 |
|
</sect3> |
| 105 |
|
|
| 106 |
</sect2> |
</sect2> |