summaryrefslogtreecommitdiff
path: root/en/boot-installer/arm.xml
blob: 6cd45e302e69f56ec92e91602cc8c414855dbe85 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->

  <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title>

&boot-installer-intro-net.xml;

  <sect3 arch="arm"><title>Booting from TFTP on Netwinder</title>

<para>

Netwinders have two network interfaces: A 10Mbps NE2000-compatible
card (which is generally referred to as </literal>eth0</literal>) and
a 100Mbps Tulip card.  There may be problems loading the image via TFTP
using the 100Mbps card so it is recommended that you use the 10Mbps
interfaced (the one labeled with <literal>10 Base-T</literal>).

</para><note><para>

You need NeTTrom 2.2.1 or later to boot the installation system, and
version 2.3.3 is recommended.  Unfortunately, firmware files are currently
not available for download because of license issues.  If this situation
changes, you may find new images at <ulink url="http//www.netwinder.org/"></ulink>.

</para></note><para>

When you boot your Netwinder you have to interrupt the boot process during the
countdown.  This allows you to set a number of firmware settings needed in
order to boot the installer.  First of all, start by loading the default
settings:

<informalexample><screen>
    NeTTrom command-&gt; load-defaults
</screen></informalexample>

Furthermore, you must configure the network, either with a static address:

<informalexample><screen>
    NeTTrom command-&gt; setenv netconfig_eth0 flash
    NeTTrom command-&gt; setenv eth0_ip 192.168.0.10/24
</screen></informalexample>

where 24 is the number of set bits in the netmask, or a dynamic address:

<informalexample><screen>
    NeTTrom command-&gt; setenv netconfig_eth0 dhcp
</screen></informalexample>

You may also need to configure the <userinput>route1</userinput>
settings if the TFTP
server is not on the local subnet.

Following these settings, you have to specify the TFTP server and the
location of the image.  You can then store your settings to flash.

<informalexample><screen>
    NeTTrom command-&gt; setenv kerntftpserver 192.168.0.1
    NeTTrom command-&gt; setenv kerntftpfile boot.img
    NeTTrom command-&gt; save-all
</screen></informalexample>

Now you have to tell the firmware that the TFTP image should be booted:

<informalexample><screen>
    NeTTrom command-&gt; setenv kernconfig tftp
    NeTTrom command-&gt; setenv rootdev /dev/ram
</screen></informalexample>

If you use a serial console to install your Netwinder, you need to add the
following setting:

<informalexample><screen>
    NeTTrom command-&gt; setenv cmdappend root=/dev/ram console=ttyS0,115200
</screen></informalexample>

Alternatively, for installations using a keyboard and monitor you have to
set:

<informalexample><screen>
    NeTTrom command-&gt; setenv cmdappend root=/dev/ram
</screen></informalexample>

You can use the <command>printenv</command> command to review your
environment settings.  After you have verified that the settings are
correct, you can load the image:

<informalexample><screen>
    NeTTrom command-&gt; boot
</screen></informalexample>

In case you run into any problems, a detailed HOWTO is <ulink
url="http://www.netwinder.org/howto/Firmware-HOWTO.html"></ulink> is
available.

</para>
  </sect3>

  <sect3 arch="arm"><title>Booting from TFTP on CATS</title>

<para>

On CATS machines, use <command>boot de0:</command> or similar at the
Cyclone prompt.

</para>
   </sect3>
  </sect2>



  <sect2 arch="arm"><title>Booting from CD-ROM</title>

&boot-installer-intro-cd.xml;

<para>

To boot a CD-ROM from the Cyclone console prompt, use the command
<command>boot cd0:cats.bin</command>

</para>
  </sect2>