Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* merge in documentation from Scott G. Akmentins-Taylor 

* add bits and pieces here and there
This commit is contained in:
pooka 2002-05-23 05:44:50 +00:00
parent fd401c6634
commit a9c4f01782
3 changed files with 214 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

66
distrib/notes/sgimips/hardware
View File

@ -1,12 +1,66 @@
.\" $NetBSD: hardware,v 1.1 2002/05/18 17:31:43 pooka Exp $
.\" $NetBSD: hardware,v 1.2 2002/05/23 05:44:50 pooka Exp $
.
.Nx*M
is aimed to run on MIPS-based computers manufactured by SGI.
.Ss2 Supported machines
.(bullet -compact
Indy
.(bullet -offset indent
.Tn SGI
IP22 R4000/R4400/R4600 \- Challenge S, Indigo 2 and Indy
.It
Indigo2
IP22 R5000 \- Indy
.bullet)
.
.Ss2 Unsupported machines
.(bullet -offset indent
IP19 R4000 - Challenge Onyx
.It
IP20 R4000 - Indigo
.It
IP21 R8000 - Power Challenge / Power Onyx
.It
IP25 R1000 - Power Challenge 10000 / Power Onyx 10000
.It
IP26 R8000 - Indigo 2 R8000
.It
IP27 R10000/R12000 - O200 / Origin 2000 / Onyx2
.It
IP28 R1000 - Indigo 2 R10000
.It
IP30 R1000/R12000 - Octane
.It
IP32 R5000 - O2 (Support exists but is not stable)
.It
IP32 R10000/R12000 - O2
.It
IP35 R12000A - Origin 3000 / Onyx 3000
.bullet)
.
.Ss2 Supported devices
.(bullet -offset indent
Serial ports
.(bullet -compact
On-board Zilog Z8530 Dual Uart
.bullet)
.It
Ethernet
.(bullet -compact
On-board SGI Seeq 80c03 ethernet controller
.Pq Em sq ,
.bullet)
.It
SCSI
.(bullet -compact
On-board
.Tn Western Digital
.Em wdsc
WD33C93 SCSI controller
.bullet)
.bullet)
.Ss2 Unsupported devices
.(bullet -offset indent
Graphics adapters
.It
Audio hardware
.It
Video hardware
.bullet)
There is some initial support for the SGI O2, but it is known to currently
have various problems.

144
distrib/notes/sgimips/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.1 2002/05/18 17:31:43 pooka Exp $
.\" $NetBSD: install,v 1.2 2002/05/23 05:44:50 pooka Exp $
.\"
.\" Copyright (c) 1999, 2000, 2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -32,9 +32,115 @@
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
The steps taken for installing
.Pp
To install or upgrade
.Nx ,
you need to first boot an installation
program and then interact with the screen-menu program
.Ic sysinst .
The installation program actually consists of the
.Nx
kernel plus
an in-memory file system of utility programs.
.Pp
The installation methods are:
.(enum
Installation from an existing
.Nx
or
.Tn IRIX
system by booting the
install kernel from an existing file system.
.if 0 \{\
.It
Copying a bootable diskimage onto the beginning of a disk and installing
onto that disk. See the
.Sx Diskless installation
section later in these INSTALL notes.
.\}
.It
Installation in a diskless environment. This means that you will install
your entire system onto a remotely shared disk.
.It
Booting the install kernel over the network and installing onto a local
disk. The beginning of the procedure is similar to diskless installation,
but you will eventually end up writing the system onto your local disk.
.if 0 \{\
.It
Using a helper machine with a SCSI controller to copy the bootable
diskimage onto the beginning of a disk, and moving the disk to the
target machine. See the
.Sx Install via diskimage
section later in these INSTALL notes.
.\}
.enum)
.Pp
You should familiarize yourself with the console PROM environment
and the hardware configuration. A good place to study PROM tricks
is the IRIX "prom" manual page.
Be sure you know how to print the configuration of your machine,
and how to boot from disk or network, as appropriate.
.Pp
To boot from disk, use:
.Pp
.(bullet
.Ic "All machine types:"
.Pp
.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 osloader boot"
.bullet)
.Pp
For all
drives (including all SCSI-2 drives), the kernel should correctly detect
the disk geometry.
.Pp
If you're installing
.Nx*M
are different for diskless and hard disk configurations.
for the first time it's a very
good idea to pre-plan partition sizes for the disks onto which you're
installing
.Nx .
Changing the size of partitions after you've
installed is difficult. If you do not have a spare bootable disk, it
may be simpler to re-install
.Nx
again from scratch.
.Pp
To be able to boot from local disk an
SGI Volume Header partition is required. This special partition is accessed
by the PROM to load the
.Nx*M
boot program. The partition should be about
2 MB in size, but can be reduced somewhat. The minimum size can approach
150k, but this doesn't leave room for upgrade boot programs.
.
.Ss2 Install via a bootable CD-ROM
.
The
.Nx*M
CD-ROM is not ISO-formatted. Since the older SGI PROMs
do not understand ISO/CD-9660 formats, the CD-ROM image is generated with an
SGI Volume Header and an FFS-formatted (BSD4.2) partition for the distribution.
Furthermore, since the filesystem is FFS, the CD cannot be mounted under IRIX.
.Pp
To install from a
.Nx*M
CD-ROM, follow the procedure above for
setting the PROM environment for SystemPartition, OSLoadPartition, OSLoader
and OSLoadFilename. The SCSI and DISK values used should be for your attached
CD-ROM drive, where
.Ar X
is the SCSI-ID of the CD-ROM.
.
Using the PROM command-line interface,
you can boot the CD-ROM installation kernel as follows:
.Pp
.(tag 12n -offset indent -compact
.It Ic ">> boot"
.tag)
.Pp
.Ss2 Installation for diskless configurations
This sections assumes you know how to configure DHCP, TFTP,
and NFS services on your server.
@ -45,13 +151,12 @@ kernel has a
.Dq .gz
suffix, you must first uncompress it using the
.Pa gunzip
program. You must also decide which kernel you need to boot. Because of
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.
.Pp
.Dl server# Ic cp netbsd-GENERIC /tftpboot/netbsd-sgimips
.Dl server# Ic cp netbsd-GENERIC_INDY /tftpboot/netbsd-sgimips-indy
.Pp
Note that your DHCP server must be configured to specify
this file as the boot file for the client.
@ -66,15 +171,34 @@ on the server.
.It
Load the kernel from the TFTP server:
.Pp
.Dl > setenv SystemPartition bootp():
.Dl > setenv netaddr your.ip.here.please
.Dl > boot
.Dl ">> setenv SystemPartition bootp():"
.Dl ">> setenv netaddr your.ip.here.please"
.Dl ">> boot"
.enum)
For more tricks with the bootprom, try reading the "prom" manual page
on found on IRIX.
.Pp
The installation of your diskless
.Nx*M
system is now complete! You may now skip ahead to any post-installation
instructions.
.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 vt100
for a serial console with a vt100-compatible terminal, or
.Ic xterm
or
.Ic xterms
for a
.Xr tip 1
or
.Xr cu 1
connection running in an
.Xr xterm 1 .
.Pp
The system will then start the
.Ic sysinst
program.
.so ../common/sysinst

22
distrib/notes/sgimips/prep
View File

@ -1,4 +1,4 @@
.\" $NetBSD: prep,v 1.1 2002/05/18 17:31:43 pooka Exp $
.\" $NetBSD: prep,v 1.2 2002/05/23 05:44:50 pooka Exp $
.
First and foremost, before beginning the installation process,
.Em make sure you have a reliable backup
@ -10,11 +10,29 @@ for the first time is most commonly done from the network. You must
set up DHCP, TFTP, and 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 can convert the standard ELF
an ECOFF version of the kernel. You will notice this from the following
message from PROM:
.Pp
.Dl Illegal f_magic number 0x7f45, expected MIPSELMAGIC or MIPSEBMAGIC.
.Pp
You can convert the standard ELF
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 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. They handle the port number as a signed entity, and
can thus not connect to ports >32767. You can work around this problem