| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id: sparc.xml,v 1.4 2004/03/11 14:50:07 stappers-guest Exp $ -->
|
| 3 |
|
| 4 |
<sect2 arch="sparc"><title>Booting from NFS</title>
|
| 5 |
<para>
|
| 6 |
|
| 7 |
To install the system via NFS, simply select
|
| 8 |
<userinput>NFS</userinput> for the location of the images and files
|
| 9 |
and follow the instructions provided. You will be prompted for the
|
| 10 |
<filename>server:/directory</filename> where the images are located.
|
| 11 |
|
| 12 |
</para>
|
| 13 |
</sect2>
|
| 14 |
|
| 15 |
|
| 16 |
<sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title>
|
| 17 |
|
| 18 |
&boot-installer-intro-net.xml;
|
| 19 |
|
| 20 |
<para>
|
| 21 |
|
| 22 |
On machines with OpenBoot, simply enter the boot monitor on the
|
| 23 |
machine which is being installed (see
|
| 24 |
<xref linkend="invoking-openboot"/>).
|
| 25 |
Use the command <userinput>boot net</userinput> to boot from a TFTP
|
| 26 |
and RARP server, or <userinput>boot net:dhcp</userinput> to boot from
|
| 27 |
a TFTP and DHCP server. Some older OpenBoot revisions require using
|
| 28 |
the device name, such as <userinput>boot le()</userinput>; these
|
| 29 |
probably don't support DHCP.
|
| 30 |
|
| 31 |
</para>
|
| 32 |
</sect2>
|
| 33 |
|
| 34 |
|
| 35 |
<sect2 arch="sparc"><title>Booting from a CD-ROM</title>
|
| 36 |
|
| 37 |
&boot-installer-intro-cd.xml;
|
| 38 |
|
| 39 |
<para>
|
| 40 |
|
| 41 |
Most OpenBoot versions support the <userinput>boot cdrom</userinput>
|
| 42 |
command which is simply an alias to boot from the SCSI device on ID 6
|
| 43 |
(or the secondary master for IDE based systems). You may have to use
|
| 44 |
the actual device name for older OpenBoot versions that don't support
|
| 45 |
this special command. Note that some problems have been reported on Sun4m
|
| 46 |
(e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM.
|
| 47 |
|
| 48 |
</para>
|
| 49 |
</sect2>
|
| 50 |
|
| 51 |
|
| 52 |
<sect2 arch="sparc">
|
| 53 |
<title>Booting from Floppies</title>
|
| 54 |
<para>
|
| 55 |
|
| 56 |
To boot from floppy on a Sparc, use
|
| 57 |
<informalexample><screen>
|
| 58 |
|
| 59 |
Stop-A -> OpenBoot: "boot floppy"
|
| 60 |
|
| 61 |
</screen></informalexample>
|
| 62 |
</para><para>
|
| 63 |
|
| 64 |
Be warned that the newer Sun4u (ultra) architecture does not support
|
| 65 |
floppy booting. A typical error message is <computeroutput>Bad magic
|
| 66 |
number in disk label - Can't open disk label package</computeroutput>.
|
| 67 |
Furthermore, a number of Sun4c models (such as the IPX) do not support
|
| 68 |
the compressed images found on the disks, so also are not supported.
|
| 69 |
|
| 70 |
</para><para>
|
| 71 |
|
| 72 |
Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from
|
| 73 |
booting (instead of not supporting booting at all). The appropriate
|
| 74 |
OBP update can be downloaded as product ID 106121 from
|
| 75 |
<ulink url="http://sunsolve.sun.com"></ulink>.
|
| 76 |
|
| 77 |
</para><para>
|
| 78 |
|
| 79 |
If you are booting from the floppy, and you seem messages such as
|
| 80 |
<informalexample><screen>
|
| 81 |
|
| 82 |
Fatal error: Cannot read partition
|
| 83 |
Illegal or malformed device name
|
| 84 |
|
| 85 |
</screen></informalexample>
|
| 86 |
then it is possible that floppy booting is simply not supported on
|
| 87 |
your machine.
|
| 88 |
|
| 89 |
</para>
|
| 90 |
</sect2>
|
| 91 |
|
| 92 |
<sect2 arch="sparc"><title>IDPROM Messages</title>
|
| 93 |
<para>
|
| 94 |
|
| 95 |
If you cannot boot because you get messages about a problem with
|
| 96 |
``IDPROM'', then it's possible that your NVRAM battery, which holds
|
| 97 |
configuration information for you firmware, has run out. See the
|
| 98 |
<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more
|
| 99 |
information.
|
| 100 |
|
| 101 |
</para>
|
| 102 |
</sect2>
|
Parent Directory
| 
Revision Log