Add sun3 stuff

This commit is contained in:
gwr 1999-05-19 05:49:06 +00:00
parent 85c2b5c458
commit 662828c4ce
4 changed files with 22 additions and 15 deletions

View File

@ -1,15 +1,15 @@
.\" $NetBSD: hardware,v 1.5 1999/01/13 07:30:09 ross Exp $
.\" $NetBSD: hardware,v 1.6 1999/05/19 05:49:06 gwr Exp $
.
NetBSD/sun3 \*V runs on most Sun3 machines, including:
.Bl -column -offset indent 3/260 3/280 3/160
. It 3/50 Ta 3/60 Ta 3/110
. It 3/75 Ta 3/150 Ta 3/160
. It 3/260 Ta 3/280 Ta 3/E
. It 3/80 Ta 3/470
.El
.Pp
NetBSD/sun3 \*V does not run on the Sun3/80 (sun3x class)
but that is presently handled as a separate distribution.
Use NetBSD/sun3x for Sun3/80 and Sun3/470 support.
Note that NetBSD/sun3 now includes support for "Sun3X" machines,
which used to be supported with a separate distribution.
.Pp
The minimal configuration requires 4M of RAM and about 80MB of disk
space. To install the entire system requires much more disk space
@ -34,7 +34,7 @@ and bulky to accommodate all people).
.Pp
Note that the sun3 installation procedure uses a `miniroot' image
which is placed into the swap area of the disk. The swap partition
must be at least as large as the miniroot image (8MB).
must be at least as large as the miniroot image (10MB).
.Pp
The following Sun3 hardware is supported:
.Bl -tag -width Em -offset indent
@ -49,6 +49,8 @@ On-board or VME Intel Ethernet
. br
Sun3/E SCSI/Ethernet board
. It Em SCSI: (Most SCSI disks, tapes, CD-ROMs, etc.)
On-board "esp" (Sun3/80 SCSI)
. br
On-board "si" (SCSI-3)
. br
VME "si" (SCSI-3) board
@ -62,6 +64,8 @@ Xylogics 753/7053
Sun keyboard and mouse
. It Em Miscellaneous:
Battery-backed real-time clock.
. br
On-board floppy controller (Sun3/80 floppy)
.El
.Pp
If it's not on this list, there is no support for it in this release.

View File

@ -1,4 +1,4 @@
.\" $NetBSD: prep,v 1.4 1999/01/13 07:30:09 ross Exp $
.\" $NetBSD: prep,v 1.5 1999/05/19 05:49:06 gwr Exp $
.
Sun3 machines usually need little or no preparation before installing
NetBSD, other than the usual, well advised precaution of
@ -21,6 +21,12 @@ It might be a good time to run the diagnostics on your Sun3. First,
attach a terminal to the "ttya" serial port, then set the "Diag/Norm"
switch to the Diagnostic position, and power-on the machine. The
Diag. switch setting forces console interaction to occur on ttya.
Note that the 3/80 has a "software" diag switch you can set at
the PROM monitor prompt. To turn on diag boot mode, do:
.Ic q 70b 12
To return to normal boot mode, do:
.Ic q 70b 6 .
.Pp
The console location (ttya, ttyb, or keyboard/display) is controlled
by address 0x1F in the EEPROM, which you can examine and change in
@ -31,5 +37,3 @@ just a '.' if you don't want to change it). Console values are:
.Dl 11: No tty b (1200-N-8-1)
.Dl 20: No Color option board on P4
.Pp
NetBSD will use the EEPROM setting to determine which device to
use as the console, so you should make sure it is correct.

View File

@ -1,6 +1,7 @@
.\" $NetBSD: whatis,v 1.5 1999/01/13 07:30:09 ross Exp $
.\" $NetBSD: whatis,v 1.6 1999/05/19 05:49:06 gwr Exp $
.
For the sun3,
.Nx \*V
brings support for the Sun3/E, and
significantly improved VM and context switch performance.
brings combined Sun3 and Sun3X support with the same
installation media.

View File

@ -1,4 +1,4 @@
.\" $NetBSD: xfer,v 1.5 1999/01/13 07:30:09 ross Exp $
.\" $NetBSD: xfer,v 1.6 1999/05/19 05:49:06 gwr Exp $
.
Installation is supported from several media types, including:
.Bl -bullet -compact -offset indent
@ -114,9 +114,7 @@ netbsd-rd kernel in the root area for your client (no other files
are needed in the client root) and /etc/bootparams on the server
should have an entry for your client and its root directory.
The client will need access to the miniroot image, which can be
provided using NFS or remote shell. If using NFS, miniroot.gz
must be expanded on the server, because there is no gzip program
in the RAMDISK image. The unzipped miniroot takes 8MB of space.
provided using NFS or remote shell.
.Pp
If you will be installing NetBSD on several clients, it may be useful
to know that you can use a single NFS root for all the clients as long