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

hardware: fix a couple of typos

Browse Source 
add ross sparc 20 clone
        a little more info on sw device

prep:   mention that can't boot if root partition is past first 2 GB of disk
        refine wording of section on scsi id mappings

install: add a little more info to the tape booting section
This commit is contained in:
mbw 2000-11-01 20:56:06 +00:00
parent a6a1220287
commit 2ccdefdb53
3 changed files with 100 additions and 58 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
distrib/notes/sparc/hardware
View File

@ -1,4 +1,4 @@
.\" $NetBSD: hardware,v 1.15 2000/10/29 14:08:09 lukem Exp $
.\" $NetBSD: hardware,v 1.16 2000/11/01 20:56:06 mbw Exp $
.
.Ss2 Supported machines
.(bullet -offset indent
@ -89,6 +89,8 @@ RDI PowerLite-110
.It
RDI BriteLite
.It
Ross sparc 20
.It
Transtec SS5/170
.It
Tatung microCOMPstation 5
@ -183,7 +185,7 @@ VME card
P4
.It
.Em cgsix ;
LEO 8 bpp accelerated framebuffer.
LEGO 8 bpp accelerated framebuffer.
P4
.It
.Em cgeight ;
@ -235,7 +237,7 @@ functions do not
SCSI interfaces
.(bullet -compact
.Em esp ;
5 MB/s and 10 MB/s (Fast) NCR 53C9x SCSI controller,
5 MB/s and 10 MB/s (Fast) NCR 53C9x SCSI controller.
On-board (sun4c, sun4m, and 4/300) and Sbus card
.It
.Em isp ;
@ -247,8 +249,9 @@ Sbus card
VME card (Interrupt driven and polled DMA)
.It
.Em sw ;
5 MB/s NCR 5380
.Dq "SCSI Weird"
controller
controller.
Onboard 4/110 (polled DMA only)
.It
misc: SCSI functionality is sometimes found on multi-function Sbus cards
@ -329,20 +332,20 @@ Sun Sbus expander device
Use of more than one processor in sun4m machines (it boots, but only uses
one processor)
.It
DBRIe-based audio and ISDN on-board some sun4m machines (such as SS10,
DBRIe-based audio and ISDN. On-board some sun4m machines (such as SS10,
SS20, SPARC LX, and Tadpole SPARCbook)
.It
.Em sc ;
Sun SCSI VME card
Sun SCSI. VME card
.It
.Em bpp ;
Bi-directional parallel port, on-board and Sbus card
Bi-directional parallel port. On-board and Sbus card
.It
.Em cgtwelve ;
I.e. GS, 24 bpp Sbus framebuffer
I.e. GS, 24 bpp. Sbus framebuffer
.It
.Em leo ;
I.e. ZX and TZX, 24 bpp Sbus framebuffer
I.e. ZX and TZX, 24 bpp. Sbus framebuffer
.It
.Em nell ;
Sbus-to-PCMCIA bridge

16
distrib/notes/sparc/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.33 2000/11/01 00:23:51 pk Exp $
.\" $NetBSD: install,v 1.34 2000/11/01 20:56:06 mbw Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -425,9 +425,13 @@ below.
.
.Ss2 Installing NetBSD by using a bootable tape
.
Sun sets their tape drives to SCSI ID 4. We recommend you do the same.
.Pp
Get the tape images
.Pq Pa installation/tape/tapefile1.gz No and Pa installation/tape/tapefile2
and transfer them to a tape using the following commands:
and transfer them to a tape. Make sure you use the
.Sq no rewind scsi tape
device. Run the following commands:
.Pp
.Dl # Ic "gunzip tapefile1.gz"
.Dl # Ic "mt -f /dev/nrst0 rew"
@ -446,12 +450,14 @@ Be sure to mark the location of these files on the tape; you'll need them
during the installation procedure.
.Pp
Insert the tape into your Sparc's tapestation.
From the OpenBoot prompt, boot the from the tape with the following command:
Boot the installer by typing the appropriate command at the PROM prompt:
.Pp
.(tag OpenBoot\ PROM\ 2\ (alternate) -offset indent -compact
.It sun4 PROM
.It sunmon
.Li > Ic "b st()"
.It OpenBoot PROM
.It OpenBoot PROM 1
.Li ok Ic "boot st()"
.It OpenBoot PROM 2
.Li ok Ic "boot tape"
.tag)
.Pp

121
distrib/notes/sparc/prep
View File

@ -1,4 +1,4 @@
.\" $NetBSD: prep,v 1.12 2000/10/29 14:08:10 lukem Exp $
.\" $NetBSD: prep,v 1.13 2000/11/01 20:56:06 mbw Exp $
.
.Ss2 Configuring your PROM
.
@ -50,38 +50,38 @@ turn them off - NetBSD can't deal well with this.
The OpenBoot PROM 1 machines (SPARCstation/server 1, SPARCstation/server 1+,
IPC, and SLC) have an odd SCSI quirk you should be aware of.
There are three SCSI addressing schemes used by your
system: SCSI ID (set by physical jumpers on the device),
SCSI target (set by OpenBoot PROM 1, based on its SCSI ID), and the name you
reference within an operating system (set by the kernel, based on the SCSI
target).
system: SCSI target ID (set by physical jumpers on the device), PROM
.Sq unit
number (set by OpenBoot PROM 1, based on its SCSI target ID), and the name
you reference within an operating system (set by the kernel, based on the PROM
.Sq unit
number).
.Pp
Sun shipped these systems with the internal drive at SCSI ID 0.
The default value of the OpenBoot PROM variable
Sun shipped these systems with the internal drives set to SCSI target IDs
3 and 1. The default value of the OpenBoot PROM variable
.Sq Li sd-targets
is
.Sq Li 31204567.
The means that the device at SCSI ID 3 is
at SCSI target 0, and the SCSI device at ID 0 is at target 3.
When you type
This variable maps how the OpenBoot PROM 1 assigns
.Sq unit
numbers based on the SCSI target ID.
Thus the device at SCSI target ID 3 is considered
.Sq unit
0, and the SCSI device at target ID 0 is
.Sq unit
3. When you type
.Dq Ic boot scsi(0,0,0) ,
the OpenBoot PROM will boot from target 0 (that is, SCSI ID 3).
The
the OpenBoot PROM will boot from
.Sq unit
0 (which is SCSI target ID 3, the internal hard drive). The
.Tn SunOS
kernel is hard-wired to map
.Li sd0
to SCSI target 3, and
.Li sd3
to SCSI target 0.
This means that SCSI ID 0 (target 3) is
.Li sd0 ,
SCSI ID 1 (target 1) is
.Li sd1 ,
and so on.
Essentially,
.Tn SunOS
reverses the OpenBoot PROM target remapping.
.Bl -column -offset indent SCSI\ ID SCSI\ Target SunOS\ name
.It Em SCSI\ ID Ta Em SCSI\ Target Ta Em SunOS\ name
.Bl -column -offset indent PROM\ Unit# SCSI\ Target SunOS\ name
.It Em PROM\ Unit# Ta Em SCSI\ Target Ta Em SunOS\ name
.It \~\~\~0 Ta \~\~\~3 Ta \~\~\~sd0
.It \~\~\~1 Ta \~\~\~1 Ta \~\~\~sd1
.It \~\~\~2 Ta \~\~\~2 Ta \~\~\~sd2
@ -91,28 +91,41 @@ reverses the OpenBoot PROM target remapping.
.It \~\~\~6 Ta \~\~\~6 Ta \~\~\~cdrom
.El
.Pp
The
Unfortunately, the
.Nx
kernel is not hard-wired in this manner and names the disks in the order
that the targets are probed (01234567). If you only have one disk, it is
always
kernel believes the
.Sq unit
values returned by the OpenBoot PROM really are the SCSI target IDs. The
.Nx*M
.Li GENERIC
kernel does not by default wire things down as does
.Tn SunOS .
It names the disks in the order
that the targets (actually the PROM
.Sq unit
numbers) are probed (01234567). If you only have one disk, it is always
.Li sd0
irregardless of its SCSI ID or target, and there are no
problems. If you have two disks, one at
SCSI ID 2 (target 2) and SCSI ID 3 (target 0), then they are recognized
as
regardless of its SCSI target ID or its PROM
.Sq unit
number, and there are no problems. If you have two disks, one at
SCSI ID 2 (
.Sq unit
2) and SCSI ID 3 (
.Sq unit
0), then they are recognized as
.Li sd1
and
.Li sd0
respectively. This can be a problem if you are not
aware of it, particularly when creating an fstab.
.Pp
There are two approaches to fixing this problem: changing OpenBoot PROM 1,
and changing the
There are two approaches to fixing this problem: changing the
mapping that OpenBoot PROM 1 does, and changing the
.Nx
kernel.
To get OpenBoot PROM 1 to number the SCSI targets the same as the SCSI
IDs, you need to run this command:
To get OpenBoot PROM 1 to number the SCSI
.Sq unit
numbers the same as the SCSI target IDs, you need to run this command:
.Pp
.Dl ok Ic "setenv sd-targets 01234567"
.Pp
@ -122,10 +135,13 @@ on this machine or if you reset the OpenBoot PROM variables.
.Pp
The other approach is to use a
.Nx
kernel that reverses this odd target mapping by treating target 0
(i.e. SCSI ID 3) as
kernel that reverses this odd target mapping by treating
.Sq unit
0 (i.e. SCSI target ID 3) as
.Li sd3
and target 3 (i.e. SCSI ID 0) as
and
.Sq unit
3 (i.e. SCSI target ID 0) as
.Li sd0 .
The
.Li GENERIC_SCSI3
@ -139,9 +155,19 @@ kernels do not.
This is also a concern when you start building your own customised kernels.
.Note)
.Pp
The sun4 models and the machines with OpenBoot PROM 2 (SPARCstation/server 2,
ELC, IPX, and all sun4m models) do not have this target mapping problem.
You should be aware, however, that some models have their internal hard
The machines with OpenBoot PROM 2 (SPARCstation/server 2,
ELC, IPX, and all sun4m models) do not have this mapping problem.
You should be aware, however, that the OpenBoot PROM
.Ic devalias
entries are similarly reversed. That is,
.Li disk0
is the hard drive at SCSI ID 3, and
.Li disk3
is the hard drive at SCSI ID 3. But don't worry, since
it is only a device alias the
.Nx
kernel finds your SCSI device at the correct target ID.
Some models have their internal hard
drives fixed at SCSI ID 3, so it may still be advantageous to use the
.Li GENERIC_SCSI3
kernel to ensure that your internal drive shows up as
@ -185,14 +211,16 @@ lun 0, partition dynamically determined), one would use:
.Pp
.Dl ok Ic "boot sd(0,30,)"
.Pp
And, to boot from the fourth partition (
And, to boot from a kernel named
.Li netbsd-GENERIC
on the fourth partition (
.Sq Li d ,
often the
.Pa /usr
partition) on an external hard drive (first SCSI bus, target 2, lun 0,
partition 3), one would use:
.Pp
.Dl ok Ic "boot sd(0,10,3)"
.Dl ok Ic "boot sd(0,10,3)netbsd-GENERIC"
.Pp
Now, for OpenBoot PROM 2, SCSI devices are specified by an OpenBOOT
.Ic devalias
@ -212,13 +240,15 @@ one would use:
.Pp
.Dl ok Ic "boot cdrom"
.Pp
And, to boot from the fourth partition (
And, to boot from a kernel named
.Li netbsd-GENERIC
on the fourth partition (
.Sq Li d ,
often the
.Pa /usr
partition) on an external hard drive (target 2, partition 3), one would use:
.Pp
.Dl ok Ic "boot disk2:d"
.Dl ok Ic "boot disk2:d netbsd-GENERIC"
.Pp
The full device path specifier for OpenBoot PROM 2 depends on how OpenBoot
PROM 2 recognizes
@ -245,6 +275,9 @@ there are no restrictions on the size of the swap partition that would render
part of your memory unusable). A full binary installation takes about 60 MB
in
.Pa /usr .
Pp
Most sparc systems have trouble booting if the root partition extends
beyond the first 2 GB of your disk.
.
.Ss2 Configuration of network interfaces
.