blob: faf39b310652d9e153c466ae33a776b760d751ad (
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
|
<!-- retain these comments for translator revision tracking -->
<!-- original version: 58021 untranslated -->
<sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title>
&boot-installer-intro-net.xml;
<para>
On machines with OpenBoot, simply enter the boot monitor on the
machine which is being installed (see
<xref linkend="invoking-openboot"/>).
Use the command <userinput>boot net</userinput> to boot from a TFTP
and RARP server, or try <userinput>boot net:bootp</userinput> or
<userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP
or DHCP server. You can pass extra boot parameters to &d-i; at the end
of the <userinput>boot</userinput> command.
</para>
</sect2>
<sect2 arch="sparc"><title>Booting from a CD-ROM</title>
&boot-installer-intro-cd.xml;
<para>
Most OpenBoot versions support the <userinput>boot cdrom</userinput>
command which is simply an alias to boot from the SCSI device on ID 6
(or the secondary master for IDE based systems).
</para>
</sect2>
<sect2 arch="sparc"><title>IDPROM Messages</title>
<para>
If you cannot boot because you get messages about a problem with
<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which
holds configuration information for you firmware, has run out. See the
<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more
information.
</para>
</sect2>
|
