Fix up sgimips install sections to more closely correspond to the current

state of reality: comment out O2 references since 1.6 won't support the
O2, add notes on installing via a net-booted kernel, disk partitioning
(disk must have IRIX volhdr, one-disk split NetBSD/IRIX install has not
been tested and may/may not work).  Also expand/add some examples.

XXX: Should add info on the "extra" kernel sets like the INSTALL_INDY,
etc. sets.
This commit is contained in:
rafal 2002-07-26 15:41:55 +00:00
parent 64ccdf4b88
commit a1489321a2
3 changed files with 104 additions and 35 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: sysinst,v 1.58 2002/07/22 15:13:41 lukem Exp $
.\" $NetBSD: sysinst,v 1.59 2002/07/26 15:41:55 rafal Exp $
.\"
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -677,8 +677,8 @@ command to boot from your hard drive.
.\}
.if \n[sgimips] \{\
Once the system reaches the PROM prompt, you will need to modify your
PROM environment settings for SystemPartition, OSLoadPartition, OSLoader
and OSLoadFilename and then boot the hard drive.
PROM environment settings for SystemPartition, OSLoadPartition, OSLoader,
OSLoadFilename and OSLoadOptions and then boot the hard drive.
.\}
.Nx
will now boot.
@ -1272,7 +1272,29 @@ if you are installing onto a drive that will be used with
(i.e. you selected
.Me "Re-install sets or install additional sets"
from the main menu).
.\}
.\} \" \n[macppc]
.if \n[sgimips] \{\
.(bullet
It is imprtant to note the disk on which
.Nx
is being installed on must already have an SGI volume header. Disks not
already formatted for
.Tn IRIX
can be prepared with the
.Tn IRIX
.Xr fx 1
disk formatting tool.
.It
Please also note that shared installs of
.Tn IRIX
and
.Nx
on the same drive have not been tested, and as such may cause problems
or may not work. It is
.Em strongly
recommended that all data is backed before attempting such installs.
.bullet)
.\} \" \n[sgimips]
.if !\n[atari]:\n[macppc]:\n[sgimips] \{\
.(bullet
Which portion of the disk to use.

View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.4 2002/07/11 04:52:51 scottr Exp $
.\" $NetBSD: install,v 1.5 2002/07/26 15:41:56 rafal Exp $
.\"
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -91,6 +91,7 @@ To boot from disk, use:
.Dl ">> setenv systempartition scsi(0)disk(X)rdisk(0)partition(8)"
.Dl ">> setenv osloadpartition scsi(0)disk(X)rdisk(0)partition(0)"
.Dl ">> setenv osloadfilename netbsd"
.Dl ">> setenv osloadoptions auto"
.Dl ">> setenv osloader boot"
.bullet)
.Pp
@ -146,7 +147,7 @@ you can boot the CD-ROM installation kernel as follows:
.tag)
.Pp
.Ss2 Installation for diskless configurations
This sections assumes you know how to configure DHCP, TFTP,
This section assumes you know how to configure DHCP, TFTP,
and NFS services on your server.
.Pp
.(enum
@ -157,12 +158,23 @@ suffix, you must first uncompress it using the
.Pa gunzip
program.
You must also decide which kernel you need to boot.
Because of differences in SGI hardware between different machines,
the kernel load addresses differ.
You will need GENERIC_INDY for the Indy and Indigo2,
while GENERIC should be enough for the O2.
.\" Because of differences in SGI hardware between different machines,
.\" the kernel load addresses differ.
.\" You will need GENERIC_INDY for the Indy and Indigo2,
.\" while GENERIC should be enough for the O2.
If your PROM can load ELF kernels directly (see the
.Sx Preparing Your System for NetBSD installation
section above), the GENERIC_INDY kernel will be sufficient.
Otherwise, you will need the ECOFF version of the GENERIC_INDY
kernel (
.Pa netbsd.ecoff-GENERIC_INDY ).
.Pp
.Dl server# Ic cp netbsd-GENERIC /tftpboot/netbsd-sgimips
.Dl server# Ic gunzip netbsd-GENERIC_INDY.gz
.Dl server# Ic cp netbsd-GENERIC_INDY /tftpboot/netbsd-sgimips
or
.Dl server# Ic gunzip netbsd.ecoff-GENERIC_INDY.gz
.Dl server# Ic cp netbsd.ecoff-GENERIC_INDY /tftpboot/netbsd-sgimips
.
.Pp
Note that your DHCP server must be configured to specify
this file as the boot file for the client.
@ -173,7 +185,7 @@ on the server.
.Dl server# Ic cd /export/client/mipseb
.Dl server# Ic gzcat .../base.tgz | tar xvpf -
.Dl server# Ic gzcat .../etc.tgz | tar xvpf -
.Dl [ repeat for all sets you wish to unpack ]
.Dl "[ repeat for all sets you wish to unpack ]"
.It
Load the kernel from the TFTP server:
.Pp
@ -186,13 +198,44 @@ The installation of your diskless
.Nx*M
system is now complete!
You may now skip ahead to any post-installation instructions.
.Pp
.Ss2 Installation to local disk from the network
This section is a subset of the above section, and also assumes that
you know how to configure DHCP and TFTP services on your server.
.Pp
.(enum
Place the install kernel into the TFTP server's download area.
Just as above, you need to place the correct bootable kernel into the
TFTP server's download area. However, instead of a GENERIC_INDY kernel,
you must use the correct INDY_INSTALL kernel. This kernel contains a
ramdisk with the installation tools and will allow you to proceed with
installation without further setup.
.Pp
If the kernel has a
.Dq .gz
suffix, you must first uncompress it using the
.Pa gunzip
program.
As above, you must choose either the ELF (netbsd-INDY_INSTALL) or ECOFF
(netbsd-INDY_INSTALL.ecoff) kernel.
.Pp
Note that your DHCP server must be configured to specify
this file as the boot file for the client.
.It
Load the kernel from the TFTP server:
.Pp
.Dl ">> setenv SystemPartition bootp():"
.Dl ">> setenv netaddr your.ip.here.please"
.Dl ">> boot"
.enum)
.Pp
.Ss2 Once you've booted the diskimage
.
Once you've booted the installation kernel you will need to
select your terminal type.
Use
.Ic iris-ansi
for an SGI graphics console (Not currently supported)
.\" .Ic iris-ansi
.\" for an SGI graphics console (Not currently supported),
.Ic vt100
for a serial console with a vt100-compatible terminal, or
.Ic xterm

View File

@ -1,4 +1,4 @@
.\" $NetBSD: prep,v 1.4 2002/07/15 12:48:01 rafal Exp $
.\" $NetBSD: prep,v 1.5 2002/07/26 15:41:56 rafal Exp $
.
First and foremost, before beginning the installation process,
.Em make sure you have a reliable backup
@ -9,10 +9,11 @@ Booting
for the first time is most commonly done from the network.
You must set up DHCP, TFTP, and possibly NFS for the installation
procedure to be successful.
Some SGI bootproms, such as the ones found on O2s, can read
ELF kernels directly from the network, others require that you boot
an ECOFF version of the kernel.
You will notice this from the following message from PROM:
Although newer SGI bootproms can read ELF kernels directly from the
network, others require that you boot an ECOFF version of the kernel.
Attempting to boot an ELF kernel on a system with a PROM that only
supports ECOFF binaries will result in the following message being
displayed by the PROM:
.Pp
.Dl Illegal f_magic number 0x7f45, expected MIPSELMAGIC or MIPSEBMAGIC.
.Pp
@ -21,19 +22,19 @@ format kernel into an ECOFF kernel using the
.Pa elf2ecoff
tool.
.Pp
Different SGI hardware will require the executable code in the loadable
image to start at a different address.
You must decide which image your system is capable of loading.
The current options are:
.(bullet
Indigo2, Indy, Challenge M, Challenge S
.It
O2
.bullet)
.Pp
Additionally there may be a third type in the future for 64bit machines.
From now on this document assumes you are familiar with selecting the
correct image for your system.
.\" Different SGI hardware will require the executable code in the loadable
.\" image to start at a different address.
.\" You must decide which image your system is capable of loading.
.\" The current options are:
.\" .(bullet
.\" Indigo2, Indy, Challenge M, Challenge S
.\" .It
.\" O2
.\" .bullet)
.\" .Pp
.\" Additionally there may be a third type in the future for 64bit machines.
.\" From now on this document assumes you are familiar with selecting the
.\" correct image for your system.
.Pp
Note that some older bootproms have an interesting bug in reading the
kernel via TFTP.
@ -46,7 +47,10 @@ to set
.Dq net.inet.ip.anonportmin
and
.Dq net.inet.ip.anonportmax
to more suitable values.
to more suitable values. For example:
.Pp
The O2 internal MACE Ethernet chip isn't supported yet, so to boot the O2
and mount nfsroot, you will need an external NIC in the PCI slot.
.Dl # Ic sysctl -w net.inet.ip.anonportmin=16384
.Dl # Ic sysctl -w net.inet.ip.anonportmax=32767
.Pp
.\" The O2 internal MACE Ethernet chip isn't supported yet, so to boot the O2
.\" and mount nfsroot, you will need an external NIC in the PCI slot.