Major overhaul. Cleaned up a lot of explanations, clarified instructions,
provided more detail when necessary and removed extraneous instructions. hardware: totally revamped to be more readable and include all known supported hardware, now matches htdocs/Ports/sparc/hardware.html install: new section on CD-ROM, netboot has instructions on setting up a NetBSD server, removed disklabel instructions (miniroot/sysboot's instructions are clear enough and have error-checking anyways) prep: reorganized, put in cleaner explanation of SCSI target remapping on OpenBOOT PROM 1 machines, put in instructions on how to figure out names ROM uses for SCSI device, put in info about 100BaseTX network cards upgrade: now points to ../common/upgrade
This commit is contained in:
parent
8f48358936
commit
b03b643f37
|
@ -1,27 +1,43 @@
|
|||
.\" $NetBSD: hardware,v 1.13 2000/10/10 12:55:22 lukem Exp $
|
||||
.\" $NetBSD: hardware,v 1.14 2000/10/21 04:49:26 mbw Exp $
|
||||
.
|
||||
.Ss2 Supported machines
|
||||
.(bullet -offset indent
|
||||
sun4c (e.g. the SS1, SS1+, SS2, IPC, ELC, IPX, and SLC)
|
||||
sun4 (4/100, 4/200, 4/300, and 4/400)
|
||||
.It
|
||||
sun4 (e.g. the 4/100, 4/200, and 4/300. Note that support
|
||||
for the 4/400 processor is incomplete)
|
||||
sun4c (SPARCstation/server 1, SPARCstation/server 1+,
|
||||
SPARCstation/server 2, IPC, ELC, IPX, and SLC)
|
||||
.It
|
||||
sun4m (e.g. Classic, LX, SS4, SS5, SS10, and SS20)
|
||||
sun4c clones (Aries Parrot II, Opus/5000, Opus/5250, FORCE Sparc CPU1e/4,
|
||||
FORCE Sparc CPU2e/4, and possibly more)
|
||||
.(bullet -compact
|
||||
NetBSD doesn't support the VME interface on the FORCE models)
|
||||
.bullet)
|
||||
.It
|
||||
sun4m (4/600, SPARC Classic, SPARC LX, SPARCstation 4,
|
||||
SPARCstation/server 5, SPARCstation/server 10, SPARCstation/server 20,
|
||||
Voyager, and JavaStation 1)
|
||||
.(bullet -compact
|
||||
All known mbus modules are supported
|
||||
.bullet)
|
||||
.It
|
||||
sun4m clones (Axil 245, Axil 311, Axil 320, Cycle C C Cycle 5-IP,
|
||||
DTKstation/Classic+, RDI PowerLite-85, RDI PowerLite-110, RDI BriteLite,
|
||||
Transtec SS5/170, Tatung microCOMPstation 5, TWS SuperCOMPstation-20S,
|
||||
Tadpole SPARCbook 3 series, and possibly more)
|
||||
.bullet)
|
||||
.
|
||||
.Ss2 Unsupported machines
|
||||
.Ss2 Machines not supported by NetBSD/\*M
|
||||
.(bullet -offset indent
|
||||
sun-4/400 (lacking support for the I/O cache, and has
|
||||
ethernet problems)
|
||||
.It
|
||||
sun4d (e.g. SPARCcenter 1000 and SPARCcenter 2000)
|
||||
.It
|
||||
sun4u and other UltraSPARC based machines.
|
||||
.Pp
|
||||
There is a separate sparc64 port for these machines.
|
||||
Refer to
|
||||
sun4u and other UltraSPARC based machines are supported by the
|
||||
.Nx
|
||||
sparc64 port. Refer to
|
||||
.Lk http://www.netbsd.org/Ports/sparc64/index.html
|
||||
.It
|
||||
Solbourne machines
|
||||
.It
|
||||
Other JavaStation models
|
||||
.bullet)
|
||||
.Pp
|
||||
The minimal configuration requires 4 MB of RAM and ~60 MB of disk space.
|
||||
|
@ -34,74 +50,134 @@ important than getting a faster CPU.
|
|||
.
|
||||
.Ss2 Supported devices
|
||||
.(bullet -offset indent
|
||||
sun4c/sun4m sbus video
|
||||
sun4c and sun4m video (sbus card, on-board, or optional)
|
||||
.(bullet -compact
|
||||
cgsix, cgthree, and bwtwo frame buffers
|
||||
bwtwo (1 bpp framebuffer, on-board and sbus card (MG1 and MG2))
|
||||
.It
|
||||
cgfourteen and tcx frame buffers (limited
|
||||
.Dq emulation
|
||||
mode)
|
||||
cgthree (8 bpp framebuffer, on-board and sbus card)
|
||||
.It
|
||||
cgsix (8 bpp accelerated framebuffer, on-board and sbus card (GX, GX+, TGX, and TGX+))
|
||||
.It
|
||||
cgfourteen (SX 24 bpp accelerated framebuffer, on-board SPARCstation 10SX and SPARCstation 20, requires optional 4 or 8 MB VSIMM, limited to cgthree emulation)
|
||||
.It
|
||||
tcx (S24 accelerated color framebuffer, on-board SPARCstation 4 (8 bpp) and
|
||||
optional on SPARCstation 5 (24 bpp), limited to cgthree emulation)
|
||||
.It
|
||||
pnozz (Weitek p9100 24 bpp accelerated framebuffer, on-board Tadpole SPARCbook 3GS and 3GX, limited to cgthree emulation)
|
||||
.bullet)
|
||||
.It
|
||||
sun4 video (not thoroughly tested?)
|
||||
sun4 video (VME card, on-board, or P4 (supported only on 4/100 and 4/300 series machines))
|
||||
.(bullet -compact
|
||||
P4 on-board bwtwo
|
||||
bwtwo (1 bpp framebuffer, on-board and P4)
|
||||
.It
|
||||
VME cgtwo card
|
||||
cgtwo (8 bpp framebuffer, VME card)
|
||||
.It
|
||||
cgfour (8 bpp framebuffer with overlay, P4)
|
||||
.It
|
||||
cgsix (LEGO 8 bpp accelerated framebuffer, P4)
|
||||
.It
|
||||
cgeight (24 bpp framebuffer with overlay, P4, not well tested)
|
||||
.bullet)
|
||||
.It
|
||||
Serial ports
|
||||
Network interfaces
|
||||
.(bullet -compact
|
||||
ttya and ttyb (can be used as console if needed)
|
||||
ie (10 Mbps Intel 82586 ethernet, on-board (4/100 and 4/200, may not be working properly on 4/400) and VME card)
|
||||
.It
|
||||
le (10 Mbps AMD 9790 Lance ethernet, on-board (4/300, sun4c, and sun4m) and sbus card)
|
||||
.It
|
||||
qec (one 100 Mbps be interface and four 10 Mbps Mace ethernet interfaces, sbus card)
|
||||
.It
|
||||
be (100 Mbps half-duplex "Big Mac" ethernet, sbus card)
|
||||
.It
|
||||
hme (100 Mbps full-duplex "Happy Meal" ethernet, sbus card, not well
|
||||
tested)
|
||||
.It
|
||||
qfe (quad 100 Mbps full-duplex "Happy Meal" ethernet (four ethernet interfaces), sbus card, not well tested)
|
||||
.It
|
||||
misc (various ethernet interfaces are found on multi-function sbus cards (e.g. along with SCSI), the ethernet interfaces work even if the other functions do not)
|
||||
.It
|
||||
en (Efficient Networks, Inc. ATM interface)
|
||||
.bullet)
|
||||
.It
|
||||
Ethernet
|
||||
SCSI interfaces
|
||||
.(bullet -compact
|
||||
On-board AMD Lance ethernet ("le0"),
|
||||
isp (10 MB/s (Fast) and 20 MB/s (Fast+Wide) Qlogic ISP 10x0 family)
|
||||
.It
|
||||
Sbus AMD Lance ethernet cards,
|
||||
esp (5 MB/s and 10 MB/s (Fast) NCR 53C9x SCSI controller, on-board (sun4c, sun4m, and 4/300) and sbus card)
|
||||
.It
|
||||
On-board Intel 82586 ethernet (ie0 on 4/100's and 4/200's),
|
||||
si (5 MB/s NCR 5380 SCSI controller, VME card (Interrupt driven and polled DMA))
|
||||
.It
|
||||
VME Intel 82586 ethernet cards
|
||||
sw (5 MB/s NCR 5380 SCSI controller, on-board 4/110 (polled DMA only))
|
||||
.It
|
||||
misc (SCSI functionality is sometimes found on multi-function sbus cards (e.g. along with ethernet), the SCSI isp and esp portions of those cards should work, even if the other functions do not)
|
||||
.(Note
|
||||
See
|
||||
.Lk http://saturn.tlug.org/suncdfaq/
|
||||
for information on bootable CD-ROMs
|
||||
.Note)
|
||||
.bullet)
|
||||
.It
|
||||
SCSI
|
||||
VME disk interfaces
|
||||
.(bullet -compact
|
||||
On-board "esp" SCSI controller (sun4c, sun4m and the 4/300),
|
||||
.It
|
||||
Sbus "esp" SCSI controller,
|
||||
.It
|
||||
Sun "SUN-3"/"si" VME SCSI controller (polled mode only, slow),
|
||||
.It
|
||||
Sun "SCSI Weird"/"sw" on-board controller (4/110 only, polled)
|
||||
.bullet)
|
||||
.It
|
||||
VME disks
|
||||
.(bullet -compact
|
||||
Xylogics 7053 VME/SMD disk controller ("xd"),
|
||||
.It
|
||||
Xylogics 450/451 VME disk controller ("xy")
|
||||
xd (Xylogics 7053 VME/SMD disk controller)
|
||||
.It
|
||||
xy (Xylogics 450/451 VME disk controller)
|
||||
.(Note
|
||||
VME/IPI disks are not supported
|
||||
.Note)
|
||||
.bullet)
|
||||
.It
|
||||
Sun floppy disk drive
|
||||
Floppy drives
|
||||
.(bullet -compact
|
||||
fd (floppy disk drive, on-board sun4c and sun4m)
|
||||
.It
|
||||
sd (SCSI floppy drive, acts as a SCSI drive to kernel, found with some SPARCBook 3 machines)
|
||||
.bullet)
|
||||
.It
|
||||
Serial interfaces
|
||||
.(bullet -compact
|
||||
on-board serial ports based on Zilog 8530 and Zilog 85C30 (can be used as console if needed)
|
||||
.bullet)
|
||||
.It
|
||||
Input devices
|
||||
.(bullet -compact
|
||||
Sun keyboard and mouse
|
||||
.It
|
||||
sun4c audio
|
||||
SPARCBook 3 keyboard and joystick
|
||||
.It
|
||||
sun4m audio on Sparcstation Classic
|
||||
Third-party keyboards, mice, and trackballs
|
||||
.bullet)
|
||||
.It
|
||||
Audio
|
||||
.(bullet -compact
|
||||
audioamd (AMD 7930-based 8000 Hz, 8 bit, mono, mu-law, on-board sun4c and
|
||||
SPARC Classic)
|
||||
.It
|
||||
audiocs (CS4231-based 44 KHz, 16 bit, stereo, PCM, on-board SPARCStation 5
|
||||
and optional on SPARCStation 4, does not support audio input)
|
||||
.bullet)
|
||||
.It
|
||||
Misc cards
|
||||
.(bullet -compact
|
||||
mtty/mbpp (Magma Serial/Parallel sbus card)
|
||||
.It
|
||||
xbox (Sun sbus expander device)
|
||||
.bullet)
|
||||
.bullet)
|
||||
.
|
||||
.Ss2 Unsupported devices
|
||||
.(bullet -offset indent
|
||||
Multi-processor sun4m machines
|
||||
Use of more than one processor in sun4m machines (it boots, but only uses one processor)
|
||||
.It
|
||||
audio drivers for sun4m machines (other than the Sparcstation Classic)
|
||||
DBRIe-based audio and ISDN on-board some sun4m machines (such as SS10,
|
||||
SS20, SPARC LX, and Tadpole SPARCbook)
|
||||
.It
|
||||
Interrupt driven SCSI driver for sun-4/100's and sun-4/200's
|
||||
sc (Sun SCSI VME card)
|
||||
.It
|
||||
bpp (bi-directional parallel port, on-board and sbus card)
|
||||
.It
|
||||
cgtwelve (a.k.a. GS, 24 bpp sbus framebuffer)
|
||||
.It
|
||||
leo (a.k.a. ZX and TZX, 24 bpp sbus framebuffer)
|
||||
.It
|
||||
nell (sbus-to-PCMCIA bridge)
|
||||
.bullet)
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: install,v 1.30 2000/10/20 12:26:41 pk Exp $
|
||||
.\" $NetBSD: install,v 1.31 2000/10/21 04:49:26 mbw Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
|
||||
.\" All rights reserved.
|
||||
|
@ -39,154 +39,194 @@ this document in hand it shouldn't be too much trouble.
|
|||
.Pp
|
||||
There are several ways to install
|
||||
.Nx
|
||||
onto a disk. The easiest way is to use the 'miniroot.fs' image copied to
|
||||
your local disk's swap partition.
|
||||
Alternatively, if your Sparcstation is hooked up in a network you
|
||||
can find a server and arrange for a diskless setup which is a
|
||||
convenient way to install on a machine whose disk does not currently
|
||||
hold a usable operating system (see the section `Installing
|
||||
.Nx
|
||||
by using a diskless setup' below). Also available is
|
||||
a two-disk bootable 1.44 MB floppy image set that can be used to boot into
|
||||
the miniroot environment.
|
||||
.
|
||||
.Ss2 Installing NetBSD by using the NetBSD miniroot
|
||||
.
|
||||
The miniroot is a self-contained
|
||||
.Nx
|
||||
filesystem holding all utilities
|
||||
necessary to install
|
||||
.Nx
|
||||
on a local disk. It is distributed as a plain
|
||||
file designed to be transferred to a raw disk partition from which it can
|
||||
be booted using the appropriate PROM command. Usually, the miniroot will
|
||||
be loaded into the swap partition of a disk. If needed, you can use any
|
||||
other unused partition, but remember that in the case of 'miniroot.fs'
|
||||
the partition will then not available during the installation process.
|
||||
onto your system. The easiest way is to use the `miniroot.fs' image copied to
|
||||
your local disk's swap partition or a scratch drive.
|
||||
If your sparc is hooked up in a network, you may configure another
|
||||
.Ux
|
||||
machine as a netboot server for your sparc. Alternatively, there is a pair of
|
||||
floppy images that will boot your system and run the installer.
|
||||
.Pp
|
||||
Loading the miniroot onto your raw partition is simple. On
|
||||
.Nx
|
||||
as well as SunOS you use a command like:
|
||||
.Dl # Ic dd if=miniroot.fs of=/dev/rsd0b bs=4k conv=sync
|
||||
(Here, `/dev/rsd0b' is assumed to be your swap partition.) There's a
|
||||
potential problem here if /dev/rsd0b is actually in use as a swap
|
||||
partition by your currently running system. If you don't have another
|
||||
disk or partition to spare, you can usually get away with running this
|
||||
command anyway after first booting into single-user mode to ensure a
|
||||
quiet system.
|
||||
For more information on the commands and variables available in
|
||||
the OpenBoot PROM (present in all sun4c and sun4m machines), go to
|
||||
.Lk http://docs.sun.com
|
||||
and search for ``openboot reference'' (without quotes).
|
||||
.Pp
|
||||
After transferring the miniroot to disk, bring the system down by:
|
||||
.Sx Installing NetBSD by placing a bootable filesystem on a partitioned hard drive
|
||||
.Pp
|
||||
.Sx Installing NetBSD by using a bootable CD-ROM
|
||||
.Pp
|
||||
.Sx Installing NetBSD by using the bootable floppies
|
||||
.Pp
|
||||
.Sx Installing NetBSD by using a netboot setup
|
||||
.
|
||||
.Ss2 Installing NetBSD by placing a bootable filesystem on a partitioned hard drive
|
||||
.
|
||||
.Pa installation/miniroot/miniroot.fs.gz
|
||||
is a compressed, self-contained
|
||||
.Nx
|
||||
filesystem holding all utilities necessary to install
|
||||
.Nx
|
||||
onto a disk attached to your system. It is distributed as a compressed plain
|
||||
file you will transfer to a raw disk partition. You will then boot
|
||||
this installer using the appropriate PROM command. The simplest case is
|
||||
where you place the `miniroot.fs' filesystem on the swap partition of
|
||||
your disk. Alternatively, you can place it on any
|
||||
other unused partition on any disk (such as a Zip disk). Be forewarned
|
||||
that you will not be able to install
|
||||
.Nx
|
||||
onto the partition that contains the `miniroot.fs' as this partition is
|
||||
needed during the install process.
|
||||
.Pp
|
||||
Loading the filesystem onto a raw partition is straightforward.
|
||||
First, download miniroot.fs to your system. Next, reboot in single-user
|
||||
mode (i.e. `boot -s') to ensure that your system will not be swapping.
|
||||
Finally, place the miniroot.fs on your partition of choice. On
|
||||
.Nx
|
||||
or SunOS the commands are:
|
||||
.Pp
|
||||
.Dl # Ic "gunzip miniroot.fs.gz"
|
||||
.Dl # Ic "dd if=miniroot.fs of=/dev/rsd0b bs=4k conv=sync"
|
||||
Here, `/dev/rsd0b' is assumed to be your swap partition. If you decide to
|
||||
place miniroot.fs on a non-swap partition, it will overwrite all of the
|
||||
contents of that partition, but you will not need to reboot into single-user
|
||||
mode to write it.
|
||||
.Pp
|
||||
After transferring the filesystem to disk, bring the system down by:
|
||||
.Dl # Ic halt
|
||||
.Pp
|
||||
Then boot the miniroot by typing the appropriate command at the PROM:
|
||||
.Dl \*> Ic "b sd(,,1)netbsd -s # for sun4 monitors
|
||||
.Dl ok Ic "boot sd(,,1)netbsd -s # for version 1 OpenBOOT ROMs
|
||||
.Dl ok Ic "boot disk:b netbsd -s # for version 2 OpenBOOT ROMs
|
||||
Then boot the installer by typing the appropriate
|
||||
command at the PROM prompt (this example is for the swap partition):
|
||||
.Dl \*> Ic b sd(,,1)netbsd -s Li # for sunmon
|
||||
.Dl ok Ic boot sd(,,1)netbsd -s Li # for OpenBOOT PROM 1
|
||||
.Dl ok Ic boot disk:b netbsd -s Li # for OpenBOOT PROM 2
|
||||
.Pp
|
||||
If you've loaded the miniroot onto some other disk than `sd0' adapt
|
||||
the boot specifier accordingly, e.g.:
|
||||
.Dl ok Ic boot disk1:b netbsd -s
|
||||
to boot from SCSI disk target 1 from a version 2 OpenBOOT ROM.
|
||||
If you have to use the old-style
|
||||
.Ic sd( Ns Ar c,u,p Ns Ic \&)
|
||||
syntax to boot from a
|
||||
SCSI disk, you can calculate the parameters as follows:
|
||||
.(tag xcc
|
||||
.It Ar c
|
||||
specifies the controller number
|
||||
.It Ar u
|
||||
the hexadecimal number obtained from evaluating
|
||||
the expression `(8 * TARGET) + LUN'
|
||||
.It Ar p
|
||||
the partition number from which to boot (0=`a', 1=`b', etc).
|
||||
.tag)
|
||||
.Pp
|
||||
The monitor boot command will cause the
|
||||
The monitor boot command will load the
|
||||
.Nx
|
||||
kernel contained in the
|
||||
miniroot image to be booted. After the initial probe messages you'll be
|
||||
filesystem image. After the initial probe messages you'll be
|
||||
asked to start the install or upgrade procedure. Proceed to the section
|
||||
.Sx Running the installation scripts.
|
||||
below.
|
||||
.
|
||||
.Ss2 Installing NetBSD by using the bootable floppy
|
||||
.Ss2 Installing NetBSD by using a bootable CD-ROM
|
||||
.
|
||||
If you wish to burn a CD-R containing a bootable NetBSD installation,
|
||||
then you can either burn the prepared disk image in
|
||||
.Pa installation/cdrom/netbsd-sparc.iso
|
||||
or create your own.
|
||||
If you wish to create your own, you should follow the directions on the
|
||||
.Nx
|
||||
Bootable CD-ROM HOW-TO at:
|
||||
.Lk http://www.netbsd.org/Documentation/bootcd.html#sparcimage
|
||||
.Pp
|
||||
Once you have downloaded
|
||||
.Pa netbsd-sparc.iso
|
||||
or created your own disk image, then you need to burn it to a CD-R.
|
||||
.Pp
|
||||
The CD-ROM attached to your sparc must support 512 byte sectors to be
|
||||
bootable.
|
||||
All Sun brand CD-ROMs will work, as well as many other manufacturers. See
|
||||
the Sun CD-ROM FAQ:
|
||||
.Lk http://saturn.tlug.org/suncdfaq/
|
||||
.Pp
|
||||
Sun sets their CD-ROM drives to SCSI ID 6. We recommend you do the same.
|
||||
.Pp
|
||||
Boot the installer by typing the appropriate command at the PROM prompt:
|
||||
.Dl \*> Ic b sd(,30,) Li # for sunmon
|
||||
.Dl ok Ic boot sd(,30,) Li # for OpenBOOT PROM 1
|
||||
.Dl ok Ic boot cdrom Li # for OpenBOOT PROM 2
|
||||
.Pp
|
||||
After the initial probe messages you'll be asked to start the
|
||||
install or upgrade procedure. Proceed to the section
|
||||
.Sx Running the installation scripts.
|
||||
below.
|
||||
.
|
||||
.Ss2 Installing NetBSD by using the bootable floppies
|
||||
.
|
||||
The
|
||||
.Nx
|
||||
install floppy works only on the sun4c and sun4m class.
|
||||
Making the install floppy is simple:
|
||||
install floppies only work on the sun4c and sun4m machines.
|
||||
Making the install floppies is fairly straightforward.
|
||||
.Pp
|
||||
Get two formatted floppy disks. If you have unformatted disks you can
|
||||
run the
|
||||
.Nx
|
||||
and SunOS use the same commands. First, get two 1.44 MB
|
||||
floppy disks and format them either using the
|
||||
.Xr fdformat 8
|
||||
program that comes with
|
||||
.Nx
|
||||
as well as SunOS. Use the following command:
|
||||
command or a PC.
|
||||
.Dl # Ic "fdformat"
|
||||
.Pp
|
||||
Make sure that the `fdformat' command completes successfully before proceeding
|
||||
to with the next step; on
|
||||
Be sure that the `fdformat' command completes successfully before proceeding;
|
||||
on
|
||||
.Nx
|
||||
, a string of all `V's, and on SunOS, a string of
|
||||
success is a string of all `V's, and on SunOS success is a string of
|
||||
all `.'s.
|
||||
Alternatively, you can use almost any PC to format your floppy disks.
|
||||
.Pp
|
||||
Next, transfer the floppy images onto the floppy disks:
|
||||
.Dl # Ic "insert the first disk"
|
||||
Next, transfer the two floppy images (
|
||||
.Pa installation/floppy/boot.fs.gz
|
||||
and
|
||||
.Pa installation/floppy/instfs.fs.gz
|
||||
) to the disks you just formatted.
|
||||
You can do this step from
|
||||
.Nx
|
||||
, SunOS, or a Windows machine using
|
||||
.Nm rawrite.exe
|
||||
(available in the NetBSD/i386 distribution).
|
||||
Insert the first floppy and run the following commands:
|
||||
.Dl # Ic "gunzip boot.fs.gz"
|
||||
.Dl # Ic "dd if=boot.fs of=/dev/rfd0a bs=36k"
|
||||
.Dl # Ic "eject floppy"
|
||||
Label this disk
|
||||
.Dq NetBSD bootfs .
|
||||
.Pp
|
||||
.Dl # Ic "insert the first disk"
|
||||
.Dl # Ic "dd if=instfs.tgz of=/dev/rfd0a bs=36k"
|
||||
Insert the second floppy and run the following commands:
|
||||
.Dl # Ic "gunzip instfs.fs.gz"
|
||||
.Dl # Ic "dd if=instfs.fs of=/dev/rfd0a bs=36k"
|
||||
.Dl # Ic "eject floppy"
|
||||
Label this disk
|
||||
.Dq NetBSD instfs .
|
||||
.Pp
|
||||
You can also accomplish this task on a Windows system by using the
|
||||
.Nm rawrite.exe
|
||||
command provided with the NetBSD/i386 install tools.
|
||||
Be sure to label your floppies so you can later identify them.
|
||||
.Pp
|
||||
Insert the disk labeled
|
||||
.Dq NetBSD bootfs
|
||||
into the floppy drive of the target system.
|
||||
From the OpenBOOT prompt, the following should boot the system from the floppy.
|
||||
.Dl ok Ic "boot fd(,,1) # Version 1 OpenBOOT ROMs
|
||||
.Dl ok Ic "boot /fd # or
|
||||
.Dl ok Ic "boot floppy # Version 2 OpenBOOT ROMs
|
||||
Insert the floppy labeled `boot.fs' into your sparc.
|
||||
From the OpenBOOT prompt, boot the floppy with the following command:
|
||||
.Dl ok Ic boot fd(,,1) # for OpenBOOT PROM 1
|
||||
.Dl ok Ic boot /fd # for OpenBoot PROM 1 (alternate)
|
||||
.Dl ok Ic boot floppy # for OpenBOOT PROM 2
|
||||
.Pp
|
||||
After the initial probe messages you'll be asked to insert the disk labeled
|
||||
.Dq NetBSD instfs
|
||||
into the drive. After the installation tools from the second disk have
|
||||
been loaded, you will be asked to start the install or upgrade procedure.
|
||||
Proceed to the section
|
||||
.Sx Running the installation scripts
|
||||
After the initial probe messages you'll be asked to insert the floppy
|
||||
labeled "NetBSD instfs". After the installation tools have been loaded
|
||||
from the `instfs' floppy, you'll be asked to start
|
||||
the install or upgrade procedure. Proceed to the section
|
||||
.Sx Running the installation scripts.
|
||||
below.
|
||||
.
|
||||
.Ss2 Installing NetBSD by using a diskless setup
|
||||
.Ss2 Installing NetBSD by using a netboot setup
|
||||
.
|
||||
First, you must setup a diskless client configuration on a server. If
|
||||
you are using a
|
||||
First, you must setup a netboot server to provide the services and files
|
||||
your client needs. If you are using a
|
||||
.Nx
|
||||
system as the boot-server, have a look at the
|
||||
system as the netboot server, have a look at the
|
||||
.Xr diskless 8
|
||||
manual page for guidelines on how to proceed with this.
|
||||
If the server runs another operating system, you'll have to consult
|
||||
documentation that came with it. (On SunOS systems, add_client(8) is a
|
||||
good start.)
|
||||
manual page for a more detailed guide on how to proceed with this.
|
||||
If the server runs another operating system, you should consult the
|
||||
.Nx
|
||||
Diskless HOW-TO, which will walk you through the steps necessary to
|
||||
configure a netboot server on a variety of platforms.
|
||||
.Lk http://www.netbsd.org/Documentation/network/netboot/
|
||||
.Pp
|
||||
Your Sparcstation expects to be able to download a second stage bootstrap
|
||||
program via TFTP after having acquired its IP address through RevARP when
|
||||
instructed to boot "over the net". It will look for a filename composed of
|
||||
This section will briefly describe what happens during a sparc
|
||||
netboot, and the next section will give a brief set of directions on how
|
||||
to set up your server. Your sparc initially broadcasts a RARP request, and
|
||||
expects a server
|
||||
to reply with your client's IP address. Next, it downloads a second stage
|
||||
bootstrap program via TFTP from the server
|
||||
that responded to the RARP request. It will look for a filename composed of
|
||||
the machine's IP address followed by the machine's architecture, separated
|
||||
by a period. For example, a sun4c machine which has been assigned IP
|
||||
address 130.115.144.11, will make an TFTP request for `8273900B.SUN4C'.
|
||||
Normally, this file is a symbolic link to an appropriate second-stage
|
||||
This file is a symbolic link to the second-stage
|
||||
boot program, which should be located in a place where the TFTP daemon
|
||||
can find it (remember, many TFTP daemons run in a chroot'ed environment).
|
||||
You can find the boot program in
|
||||
.Pp
|
||||
The boot program to use is
|
||||
.Pa installation/netboot/boot.net
|
||||
Alternatively, you can find
|
||||
the bootstrap program in
|
||||
.Pa /usr/mdec/boot.net
|
||||
in the
|
||||
.Nx*M
|
||||
|
@ -201,275 +241,149 @@ transformed in a way that makes it usable on all versions of Sparc PROMs.
|
|||
After the boot program has been loaded into memory and given control by
|
||||
the PROM, it starts locating the machine's remote root directory through
|
||||
the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast
|
||||
on the local net. The answer to this request (if it comes in) contains
|
||||
on the local net. The answer to this request should contain
|
||||
the client's name. This name is used in next step, a BOOTPARAM GETFILE
|
||||
request -- sent to the server that responded to the WHOAMI request --
|
||||
requesting the name and address of the machine that will serve the client's
|
||||
root directory, as well as the path of the client's root on that server.
|
||||
.Pp
|
||||
Finally, this information (if it comes in) is used to issue a REMOTE MOUNT
|
||||
Finally, this information is used to issue a REMOTE MOUNT
|
||||
request to the client's root filesystem server, asking for an NFS file
|
||||
handle corresponding to the root filesystem. If successful, the boot
|
||||
handle corresponding to the root filesystem. Once the NFS mount is complete, the boot
|
||||
program starts reading from the remote root filesystem in search of the
|
||||
kernel which is then read into memory.
|
||||
.Pp
|
||||
.
|
||||
.Ss2 Configuring your netboot server
|
||||
.
|
||||
Follow this section to configure a
|
||||
.Nx
|
||||
machine as your netboot server. We will use ``CC:CC:CC:CC:CC:CC'' as the
|
||||
MAC address (ethernet hardware address) of your netboot client machine
|
||||
that you wish to install
|
||||
.Nx
|
||||
on. We use ``192.168.1.10'' as the IP address of your client, and
|
||||
``client.test.net'' as the name. The server name is ``server.test.net'',
|
||||
and the path on the server to the NFS exported directory is
|
||||
.Pa /export/client/root
|
||||
although you may choose to use a different path. Create an
|
||||
.Pa /etc/ethers
|
||||
file with the following line:
|
||||
.Dl "CC:CC:CC:CC:CC:CC client"
|
||||
Add your client to the server's
|
||||
.Pa /etc/hosts
|
||||
file:
|
||||
.Dl "192.168.1.10 client"
|
||||
If rarpd is currently running, restart it (kill -HUP), otherwise start
|
||||
rarpd:
|
||||
.Dl # Ic "/usr/sbin/rarpd -a"
|
||||
Next, create
|
||||
.Pa /etc/bootparams
|
||||
with the following line:
|
||||
.Dl "client root=server:/export/client/root"
|
||||
If rpc.bootparamd is currently running, restart it (kill -HUP), otherwise
|
||||
start rpc.bootparamd:
|
||||
.Dl # Ic "/usr/sbin/rpc.bootparamd"
|
||||
Now, make sure the bootloader in
|
||||
.Pa /tftpboot
|
||||
is linked to, or a copy of,
|
||||
.Pa boot.net
|
||||
and is named appropriately for your client
|
||||
(in this case, it would be C0A8010A.SUN4C).
|
||||
.Dl # Ic "cp boot.net /tftpboot"
|
||||
.Dl # Ic "ln -s /tftpboot/boot.net /tftpboot/C0A8010A.SUN4C"
|
||||
Now, you should edit
|
||||
.Pa /etc/inetd.conf
|
||||
and make sure that the line starting with
|
||||
.Pa tftp
|
||||
is uncommented. You will need to kill -HUP the inetd process to enable
|
||||
tftp if this line was previously commented out. The next
|
||||
step is to set up NFS exports. Create the directory you are exporting for
|
||||
the netboot client:
|
||||
.Dl # Ic "mkdir -p /export/client/root"
|
||||
Put the following line in
|
||||
.Pa /etc/exports
|
||||
to enable NFS sharing:
|
||||
.Dl "/export/client/root -maproot=root client.test.net"
|
||||
If your server is currently running NFS services, you only need to kill
|
||||
-HUP the mountd process. Otherwise, you need to run:
|
||||
.Dl # Ic "/sbin/mountd"
|
||||
.Dl # Ic "/sbin/nfsd -tun 4"
|
||||
Now, you need to place the files your netboot client will need.
|
||||
As noted above in the section
|
||||
.Pa Preparing your System for NetBSD Installation
|
||||
you have several options when choosing a location to store the installation
|
||||
filesets. However, the easiest way is to put the
|
||||
.Pa *.tar.gz
|
||||
files you want
|
||||
to install into the root directory for your client on the server.
|
||||
.Pp
|
||||
.ie 0 \{\
|
||||
.\" section commented out because netbsd.ram.gz is no longer self-contained
|
||||
Next you must select whether to use the easier 'sysinst' or more flexible
|
||||
script based install.
|
||||
.
|
||||
.Ss2 Diskless sysinst installation
|
||||
.
|
||||
Follow this section and skip the next if you wish to use the easier 'sysinst'
|
||||
installation method.
|
||||
.Pp
|
||||
Copy the installation/bootfs/netbsd.ram.gz image into the exported
|
||||
root directory for your machine, then boot your workstation from the
|
||||
you have several options when choosing a location to store the
|
||||
distribution
|
||||
filesets. However, the easiest way is to put the distribution
|
||||
files into the exported directory for your client on the server.
|
||||
.Dl # Ic "mv *.tgz /export/client/root"
|
||||
Your client will need a kernel to boot (use
|
||||
.Pa binary/kernel/netbsd.GENERIC.gz
|
||||
).
|
||||
.Dl # Ic "gunzip netbsd.GENERIC.gz"
|
||||
.Dl # Ic "mv netbsd.GENERIC /export/client/root/netbsd"
|
||||
Your client will need installation tools (use
|
||||
.Pa installation/netboot/miniroot.tgz
|
||||
).
|
||||
.Dl # Ic "gunzip miniroot.tgz"
|
||||
.Dl # Ic "cd /export/client/root"
|
||||
.Dl # Ic "tar -xf miniroot.tar"
|
||||
Now, netboot your sparc from the
|
||||
server by entering the appropriate `boot' command at the monitor prompt.
|
||||
Depending on the PROM version in your machine, this command takes one of
|
||||
the following forms:
|
||||
.Dl "\*> b le()netbsd.ram.gz # for sun4 monitors
|
||||
.Dl "ok boot le()netbsd.ram.gz # for version 1 OpenBOOT ROMs
|
||||
.Dl "ok boot net netbsd.ram.gz # for version 2 OpenBOOT ROMs
|
||||
.Dl \*> Ic b le()netbsd Li # for sunmon
|
||||
.Dl ok Ic boot le()netbsd Li # for OpenBOOT PROM 1
|
||||
.Dl ok Ic boot net netbsd Li # for OpenBOOT PROM 2
|
||||
.Pp
|
||||
This will boot the
|
||||
.Nx
|
||||
kernel in single-user mode.
|
||||
.(Note
|
||||
The latter two examples assume you operate the OpenBOOT ROM in
|
||||
"new command mode". If your machine comes up and gives you a `\*>' prompt
|
||||
instead of `ok', type:
|
||||
.Dl "\*>n # enter native OpenBOOT mode
|
||||
.Dl "ok setenv sunmon-compat? false # make it permanent
|
||||
.Dl "ok
|
||||
.Note)
|
||||
.
|
||||
.\}
|
||||
.Ss2 Diskless script installation
|
||||
.
|
||||
.ie 0 \{\
|
||||
Follow this section and skip the previous if you wish to use the more
|
||||
flexible 'miniroot' script installation method.
|
||||
.Pp
|
||||
.\}
|
||||
Unpack `base.tar.gz', `etc.tar.gz', and 'kern.tgz' on the server in
|
||||
the root directory for your machine. If you elect to use a separately
|
||||
NFS-mounted filesystem for `/usr' with your diskless setup, make sure the
|
||||
"./usr" base files in base.tar.gz end up in the correct location. One way
|
||||
to do this is to temporarily use a loopback mount on the server, re-routing
|
||||
.Ar root Ns Pa /usr
|
||||
to your server's exported
|
||||
.Nx
|
||||
.Pa /usr
|
||||
directory. Also put 'install.*' and 'upgrade.sh' from the
|
||||
.Pa installation/netboot/
|
||||
directory into the root directory.
|
||||
.Pp
|
||||
A few configuration files need to be edited:
|
||||
.(tag indent
|
||||
.It Ar root Ns Pa /etc/hosts
|
||||
Add the IP addresses of both server and client.
|
||||
|
||||
.It Ar root Ns Pa /etc/myname
|
||||
This files contains the client's hostname; use the same
|
||||
name as in \*<root\*>/etc/hosts.
|
||||
|
||||
.It Ar root Ns Pa /etc/fstab
|
||||
Enter the entries for the remotely mounted filesystems.
|
||||
For example:
|
||||
.Dl server:/export/root/client / nfs rw 0 0
|
||||
.Dl server:/export/exec/sun4.netbsd /usr nfs rw 0 0
|
||||
.tag)
|
||||
.Pp
|
||||
Now you must populate the `/dev' directory for your client. If your server
|
||||
runs SunOS 4.x, you can simply change your working directory to
|
||||
.Ar root Ns Pa /dev
|
||||
and run the MAKEDEV script:
|
||||
.Ic sh MAKEDEV all .
|
||||
.Pp
|
||||
On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error
|
||||
messages about unknown user and groups. These errors are inconsequential
|
||||
for the purpose of installing
|
||||
.Nx .
|
||||
However, you may want to correct them
|
||||
if you plan to use the diskless setup regularly. In that case, you may re-run
|
||||
MAKEDEV on your
|
||||
.Nx
|
||||
machine once it has booted.
|
||||
.Pp
|
||||
If you to use the server setup for installation purposes only, then you
|
||||
may create a considerably smaller client filesystem by unpacking
|
||||
`instfs.tgz' (found in the `installation/bootfs' distribution directory)
|
||||
into your client's NFS root directory instead of using `base.tar.gz'
|
||||
and `etc.tar.gz'. You still need 'kern.tgz' to extract a kernel,
|
||||
since `instfs.tgz' does not contain one.
|
||||
.Pp
|
||||
Boot your workstation from the server by entering the appropriate `boot'
|
||||
command at the monitor prompt. Depending on the PROM version in your machine,
|
||||
this command takes one of the following forms:
|
||||
.Dl "\*> b le()netbsd -s # for sun4 monitors
|
||||
.Dl "ok boot le()netbsd -s # for version 1 OpenBOOT ROMs
|
||||
.Dl "ok boot net netbsd -s # for version 2 OpenBOOT ROMs
|
||||
.Pp
|
||||
This will boot the
|
||||
.Nx
|
||||
kernel in single-user mode.
|
||||
.(Note
|
||||
The latter two examples assume you operate the OpenBOOT ROM in
|
||||
"new command mode". If your machine comes up and gives you a `\*>' prompt
|
||||
instead of `ok', type:
|
||||
.Dl "\*>n # enter native OpenBOOT mode
|
||||
.Dl "ok setenv sunmon-compat? false # make it permanent
|
||||
.Dl "ok
|
||||
.Note)
|
||||
.Pp
|
||||
If you use a diskless setup with a separately NFS-mounted /usr filesystem,
|
||||
mount
|
||||
.Pa /usr
|
||||
by hand now:
|
||||
.Dl netbsd# Ic mount /usr
|
||||
.Pp
|
||||
.(Note
|
||||
the text editor provided nu the miniroot is
|
||||
.Xr vi 1 .
|
||||
.Note)
|
||||
When using
|
||||
.Xr disklabel 8
|
||||
to edit disklabels the -e switch will invoke the editor on the
|
||||
label. The -i switch will run an interactive session.
|
||||
.Pp
|
||||
At this point, it's worth checking the disk label and partition sizes on
|
||||
the disk you want to install
|
||||
.Nx
|
||||
onto.
|
||||
.Nx
|
||||
understands SunOS-style
|
||||
disklabels, so if your disk was previously used by SunOS there will be
|
||||
a usable label on it. Use `disklabel -e \*<disk\*>' or `disklabel -i
|
||||
\*<disk\*>' (where \*<disk\*> is the device name assigned by the
|
||||
.Nx
|
||||
kernel, e.g. `sd0') to view and modify the partition sizes. See
|
||||
the section
|
||||
.Sx Preparing your System for NetBSD Installation
|
||||
above for suggestions about disk partition sizes.
|
||||
.Pp
|
||||
If you are installing on a SCSI disk that does
|
||||
.Em not
|
||||
have a SunOS or
|
||||
.Nx
|
||||
label on it, you may still be able to use disklabel(8) but you'll
|
||||
have to create all partitions from scratch. If your disk is listed in
|
||||
`/etc/disktab', you may use the entry (which in most cases only defines
|
||||
a `c' partition to describe the whole disk) to put an initial label on
|
||||
the disk. Then proceed with `disklabel -e \*<disk\*>' or `disklabel -i
|
||||
\*<disk\*>' to create a partition layout that suits your needs.
|
||||
.(Note
|
||||
Because of the built-in compatibility with SunOS-style labels,
|
||||
.Em Always make sure all your partitions
|
||||
.Em start and end on cylinder boundaries.
|
||||
.Note)
|
||||
.Pp
|
||||
Here follows an example of what you'll see while in the dislabel editor.
|
||||
Do not touch any of the parameters except for the `label: ' entry and
|
||||
the actual partition size information at the bottom (the lines starting
|
||||
with `a:', `b:', ...).
|
||||
.Pp
|
||||
The size and offset fields are given in sector units. Be sure to make
|
||||
these numbers multiples of the of the number of sectors per cylinder:
|
||||
the kernel might be picky about these things, but aside from this you'll
|
||||
have the least chance of wasting disk space.
|
||||
Partitions on which you intend to have a mountable filesystem, should
|
||||
be given fstype `4.2BSD'. Remember, the `c' partition should describe
|
||||
the whole disk.
|
||||
The `(Cyl. x - y)' info that appears after the hash (`#') character is
|
||||
treated as a comment and need not be filled in when altering partitions.
|
||||
.(Note
|
||||
The line containing `8 partitions:' is best left alone,
|
||||
even if you define less then eight partitions. If this line displays
|
||||
a different number and the program complains about it (after you leave
|
||||
the editor), then try setting it to `8 partitions:'.
|
||||
.Note)
|
||||
.Ss2 Sample disklabel screen
|
||||
.(disp
|
||||
netbsd# disklabel sd2
|
||||
# /dev/rsd2c:
|
||||
type: SCSI
|
||||
disk: SCSI disk
|
||||
label: Hold Your Breath
|
||||
flags:
|
||||
bytes/sector: 512
|
||||
sectors/track: 64
|
||||
tracks/cylinder: 7
|
||||
sectors/cylinder: 448
|
||||
cylinders: 1429
|
||||
rpm: 3600
|
||||
interleave: 1
|
||||
trackskew: 0
|
||||
cylinderskew: 0
|
||||
headswitch: 0 # milliseconds
|
||||
track-to-track seek: 0 # milliseconds
|
||||
drivedata: 0
|
||||
|
||||
8 partitions:
|
||||
# size offset fstype [fsz bsz cpg]
|
||||
a: 50176 0 4.2BSD 0 0 0 # (Cyl. 0 - 111)
|
||||
b: 64512 50176 swap # (Cyl. 112 - 255)
|
||||
c: 640192 0 unknown # (Cyl. 0 - 1428)
|
||||
d: 525504 114688 4.2BSD 0 0 0 # (Cyl. 256 - 1428)
|
||||
.disp)
|
||||
.Pp
|
||||
If you are upgrading a
|
||||
.Nx
|
||||
installation, start the upgrade script:
|
||||
.Dl netbsd# Ic sh upgrade.sh
|
||||
else, start the installation script:
|
||||
.Dl netbsd# Ic sh install.sh
|
||||
After the initial probe messages you'll be asked to start the
|
||||
install or upgrade procedure. Proceed to the section
|
||||
.Sx Running the installation scripts.
|
||||
below.
|
||||
.
|
||||
.Ss2 Running the installation scripts
|
||||
.
|
||||
The installation system will do most of the work of transferring the
|
||||
system from the distribution sets onto your disk. You will frequently be
|
||||
asked for confirmation before the system proceeds with each phase of the
|
||||
installation process.
|
||||
If you booted your system using the `miniroot.fs' image or the CD-ROM image,
|
||||
you will be presented with a choice of two installation methods: a new
|
||||
full-screen `sysinst' program, or the traditional script-based `miniroot'
|
||||
program. The `sysinst' program is easier to use, but the `miniroot' program
|
||||
is more flexible. Both of these installation methods will follow the same
|
||||
set of procedures and will fully install
|
||||
.Nx
|
||||
on your sparc.
|
||||
.Pp
|
||||
Note: the
|
||||
.Ox
|
||||
miniroot also supports the use of the experimental
|
||||
full-screen installation program
|
||||
.Dq sysinst .
|
||||
To use sysinst instead of the default installtion script, follow the
|
||||
on-screen instruction that is displayed after the miniroot has started.
|
||||
You will frequently be asked for confirmation before the system proceeds
|
||||
with each phase of the installation process.
|
||||
.Pp
|
||||
Occasionally, you will have to provide a piece of information such as the
|
||||
name of the disk you want to install on or IP addresses and domain names
|
||||
name of the disk you want to install on, partitioning information,
|
||||
or IP addresses and domain names
|
||||
you want to assign. If your system has more than one disk, you may want
|
||||
to look at the output of the dmesg(8) command to see how your disks
|
||||
to look at the output of the
|
||||
.Xr dmesg 8
|
||||
command to see how your disks
|
||||
have been identified by the kernel.
|
||||
.(Note
|
||||
If you repartition a hard drive, be certain that every partition starts
|
||||
on a cylinder boundary for compatability with the sparc ROM.
|
||||
.Note)
|
||||
.Pp
|
||||
The installation script goes through the following phases:
|
||||
.(bullet -compact
|
||||
determination of the disk on to install
|
||||
determination of the disk on which to install
|
||||
.Nx
|
||||
.It
|
||||
checking of the partition information on the disk
|
||||
checking/creation of the partition information on the disk
|
||||
.It
|
||||
creating and mounting the
|
||||
.Nx
|
||||
filesystems
|
||||
.It
|
||||
setup of IP configuration
|
||||
setup of network configuration
|
||||
.It
|
||||
extraction of the distribution tar files
|
||||
.It
|
||||
installation of boot programs
|
||||
installation of bootstrap programs
|
||||
.bullet)
|
||||
.Pp
|
||||
Now try a reboot. Initially I'd suggest you "boot sd()netbsd -bs", then
|
||||
|
@ -477,18 +391,16 @@ try multiuser after that. If you boot single-user the
|
|||
.Nx
|
||||
incantation to make the root filesystem writable is
|
||||
.Dl netbsd# Ic mount -u /dev/sd0a /
|
||||
The Sun monitor might have been setup to instruct the boot program to load
|
||||
a file called "vmunix". On OpenBOOT ROM systems you can change it to load
|
||||
Your PROM might have been setup to instruct the boot program to load
|
||||
a file called "vmunix". On OpenBOOT PROM systems you can change it to load
|
||||
"netbsd" instead using the following commands:
|
||||
.Pp
|
||||
On version 1 OpenBOOT ROMs:
|
||||
.Dl \*>n
|
||||
On OpenBOOT PROM 1:
|
||||
.Dl ok Ic setenv boot-from sd(0,0,0)netbsd
|
||||
.Dl ok
|
||||
.Pp
|
||||
On version 2 OpenBOOT ROMs:
|
||||
On OpenBOOT PROM 2:
|
||||
.Dl ok Ic setenv boot-file netbsd
|
||||
.Dl ok Ic setenv boot-device /sbus/esp/sd@0,0
|
||||
.Dl ok Ic setenv boot-device disk:a
|
||||
.Pp
|
||||
.Em Congratulations ,
|
||||
you have successfully installed
|
||||
|
|
|
@ -1,54 +1,150 @@
|
|||
.\" $NetBSD: prep,v 1.9 2000/10/10 12:55:22 lukem Exp $
|
||||
.\" $NetBSD: prep,v 1.10 2000/10/21 04:49:26 mbw Exp $
|
||||
.
|
||||
Before you start you might need to consider your disk configuration
|
||||
to sort out a quirk in SCSI-ID to SD-UNIT mapping that exists on
|
||||
Sun Sparcstations.
|
||||
.Ss2 Configuring your ROM
|
||||
.
|
||||
Before you start, you should configure your ROM. There are three
|
||||
categories of ROM: ``sunmon'' (sometimes called Restricted Prompt,
|
||||
sun monitor, or old command mode), OpenBoot PROM 1, and OpenBoot PROM 2.
|
||||
The sun4 machines only have sunmon. Some of the early sun4c models
|
||||
default to sunmon but have OpenBoot PROM 1 (OBP1). The later sun4c
|
||||
models and all sun4m models have OBP2.
|
||||
.Pp
|
||||
Upon leaving the factory, SunOS and the OpenBOOT ROM map according to
|
||||
this table:
|
||||
.Bl -column -offset indent SCSI-ID SunOS\ SD-Unit
|
||||
.It Tn Em SCSI-ID Ta Tn Em SunOS\ SD-Unit
|
||||
.It \~\~\~0 Ta \~\~\~sd3
|
||||
.It \~\~\~1 Ta \~\~\~sd1
|
||||
.It \~\~\~2 Ta \~\~\~sd2
|
||||
.It \~\~\~3 Ta \~\~\~sd0
|
||||
.It \~\~\~4 Ta \~\~\~sd4
|
||||
.It \~\~\~5 Ta \~\~\~sd5
|
||||
.It \~\~\~6 Ta \~\~\~sd6
|
||||
First, you should set your system to always use the OpenBoot PROM
|
||||
(sometimes called ``new command mode'') if it defaults to sunmon. The
|
||||
.Nx
|
||||
kernel relies on some of the functionality provided by the OBP.
|
||||
If your machine gives you a `\*>' prompt instead of an `ok' prompt,
|
||||
type:
|
||||
.Pp
|
||||
.Dl \*> Ic n
|
||||
.Dl ok Ic setenv sunmon-compat? false
|
||||
.Dl ok
|
||||
.Pp
|
||||
Next, if you are using any security features of OBP, you should turn
|
||||
them off -- NetBSD can't deal well with this.
|
||||
.Dl ok Ic setenv security-mode none
|
||||
.Pp
|
||||
The OBP1 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 OBP1, based on its SCSI ID), and the name you
|
||||
reference within an operating system (set by the kernel, based on the SCSI
|
||||
target).
|
||||
.Pp
|
||||
Sun shipped these systems with the internal drive at SCSI ID 0.
|
||||
The default value of the OBP variable
|
||||
.Pa sd-targets
|
||||
is
|
||||
.Pa 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 ``boot scsi(0,0,0)'', OBP will boot from target 0
|
||||
(that is, SCSI ID 3). The
|
||||
SunOS kernel is hard-wired to map sd0 to SCSI target 3, and sd3
|
||||
to SCSI target 0. This means that SCSI ID 0 (target 3) is sd0, SCSI ID
|
||||
1 (target 1) is sd1,
|
||||
and so on. Essentially, SunOS reverses the OBP target remapping.
|
||||
.Bl -column -offset indent SCSI\ ID SCSI\ Target SunOS\ SD-Unit
|
||||
.It Em SCSI-ID Ta Em SCSI\ Target Ta Em SunOS\ SD-Unit
|
||||
.It \~\~\~0 Ta \~\~\~3 Ta \~\~\~sd0
|
||||
.It \~\~\~1 Ta \~\~\~1 Ta \~\~\~sd1
|
||||
.It \~\~\~2 Ta \~\~\~2 Ta \~\~\~sd2
|
||||
.It \~\~\~3 Ta \~\~\~0 Ta \~\~\~sd3
|
||||
.It \~\~\~4 Ta \~\~\~4 Ta \~\~\~st0
|
||||
.It \~\~\~5 Ta \~\~\~5 Ta \~\~\~st1
|
||||
.It \~\~\~6 Ta \~\~\~6 Ta \~\~\~cdrom
|
||||
.El
|
||||
.Pp
|
||||
Unlike SunOS and the OpenBOOT ROM, a generic NetBSD kernel numbers
|
||||
scsi drives sequentially as it finds them. The drive with the
|
||||
lowest scsi-id will be called sd0, the next one sd1, etc.
|
||||
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 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 sd1 and sd0 respectively. This can be a problem if you are not
|
||||
aware of it, particularly when creating an fstab.
|
||||
.Pp
|
||||
To ease the installation process, the default NetBSD kernel in the
|
||||
distribution is setup to match the Sun mapping above by hard-wiring
|
||||
scsi-id#3 to sd0 and scsi-id#0 to sd3. The remaining drives will be
|
||||
dynamically mapped to other sd* numbers.
|
||||
There are two approaches to fixing this problem: changing OBP1, and
|
||||
changing the
|
||||
.Nx
|
||||
kernel. To get OBP1 to number the SCSI targets the same as the SCSI
|
||||
IDs, you need to run this command:
|
||||
.Dl ok Ic setenv sd-targets 01234567
|
||||
This may, however, cause problems if you were to later attempt to use
|
||||
SunOS on this machine or if you reset the OBP variables.
|
||||
.Pp
|
||||
A truly generic NetBSD kernel is also provided as `/netbsd.GENERIC',
|
||||
which will do the standard NetBSD probe ordering. If your configuration
|
||||
differs from the default Sun setup, you can try to use this kernel to
|
||||
complete the installation.
|
||||
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 sd3 and target 3 (i.e. SCSI ID 0) as sd0.
|
||||
The GENERIC_SCSI3 kernel performs this target remapping, but the
|
||||
GENERIC and INSTALL kernels do not.
|
||||
.Pp
|
||||
.(Note
|
||||
This is also a concern when you start building your own customised kernels.
|
||||
.Note)
|
||||
.Pp
|
||||
Your OpenBOOT ROM may need some setup. make sure you boot from `new
|
||||
command mode'. If your machine comes up and gives you a `\*>' prompt
|
||||
instead of `ok', type:
|
||||
.Dl \*> Ic n
|
||||
.Dl ok Ic setenv sunmon-compat? false
|
||||
.Dl ok
|
||||
This is needed because the NetBSD kernel relies on functionality provided
|
||||
by OpenBOOT ROMs -- the ability to pass down Forth commands and have them
|
||||
executed in the ROM -- that appears to go away when the OpenBOOT ROM
|
||||
operates in `old monitor compatibility' mode.
|
||||
The machines with OBP2 (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 drives fixed at
|
||||
SCSI ID 3, so it may still be advantageous to use the GENERIC_SCSI3
|
||||
kernel to ensure that your internal drive shows up as sd0.
|
||||
.
|
||||
.Ss2 Determining how to access your SCSI disk from the ROM
|
||||
.
|
||||
sunmon and OBP1 use a strange
|
||||
.Ic sd( Ns Ar c,u,p Ns Ic \&)
|
||||
syntax to address SCSI devices. OBP2 uses a more intuitive
|
||||
syntax using device aliases.
|
||||
.Pp
|
||||
Also, you cannot use the security modes of the sparc OpenBOOT ROM.
|
||||
.Dl ok Ic setenv security-mode none
|
||||
To calculate the parameters for sunmon and OBP1:
|
||||
.(tag xcc
|
||||
.It Ar c
|
||||
specifies the SCSI controller number (first is 0, second is 1, ...)
|
||||
.It Ar u
|
||||
the hexadecimal number obtained from evaluating
|
||||
the expression `(8 * TARGET) + LUN'
|
||||
.It Ar p
|
||||
the partition number from which to boot (0=`a', 1=`b', etc).
|
||||
.tag)
|
||||
Therefore, to boot from the swap partition on the internal hard drive
|
||||
(first SCSI bus, target 0, lun 0, partition 1), one would use:
|
||||
.Dl ok Ic "boot sd(0,0,1)"
|
||||
To boot from a CD-ROM (first SCSI bus, target 6,
|
||||
lun 0, partition dynamically determined), one would use:
|
||||
.Dl ok Ic "boot sd(0,30,)"
|
||||
And, to boot from the fourth (`d', typically
|
||||
.Pa usr
|
||||
) partition on an external hard drive (first SCSI bus, target 2, lun 0,
|
||||
partition 3), one would use:
|
||||
.Dl ok Ic "boot sd(0,10,3)"
|
||||
.Pp
|
||||
Now, for OBP2, SCSI devices are specified by an OpenBOOT
|
||||
.Pa devalias
|
||||
which provides simple mnemonics for the full path to the device. Type
|
||||
.Pa devalias
|
||||
in OBP2 to get a list of all of the available aliases.
|
||||
Just the alias and partition are necessary when booting.
|
||||
.Pp
|
||||
Therefore, to boot from the swap partition on the internal hard drive
|
||||
(OBP2 assumes the internal hard drive is at target 3), one would use:
|
||||
.Dl ok Ic "boot disk:b"
|
||||
To boot from a CD-ROM (OBP2 assumes the CD-ROM is at target 6), one would use:
|
||||
.Dl ok Ic "boot cdrom"
|
||||
And, to boot from the fourth (`d', typically
|
||||
.Pa usr Ns
|
||||
) partition on an external hard drive (target 2, partition 3), one would use:
|
||||
.Dl ok Ic "boot disk2:d"
|
||||
.Pp
|
||||
The full device path specifier for OBP2 depends on how OBP2 recognizes
|
||||
your SCSI controller. Typically, one would use something like:
|
||||
.Pa /sbus/esp/sd@ Ns Ar t,p
|
||||
where t is the SCSI target and p is the partition number.
|
||||
.
|
||||
.Ss2 Deciding on partition sizes
|
||||
.
|
||||
If you're installing
|
||||
.Nx*M
|
||||
for the first time it's a good idea
|
||||
|
@ -60,14 +156,22 @@ a good initial size for the swap partition is twice the amount of physical
|
|||
memory in your machine (though, unlike SunOS 4.x, 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 `/usr'.
|
||||
.Pp
|
||||
.
|
||||
.Ss2 Configuration of network interfaces
|
||||
.
|
||||
Some network devices (i.e. the built-in `le' interface on sun4m machines)
|
||||
allow a choice between operating on a UTP or a AUI port. The `le' driver
|
||||
supports automatic detection of the port which is actually connected to
|
||||
the wire.
|
||||
the wire. Additionally, some of the Fast ethernet devices (such as `be',
|
||||
`hme', `qec', and `qfe') support selection of various speeds and options.
|
||||
The default is to attempt to automatically detect the speed.
|
||||
.Pp
|
||||
If automatic detection is not available or not working properly in your
|
||||
environment, you may have to specify the type connection using the
|
||||
`media' parameter of ifconfig(8). During installation, you'll get the
|
||||
opportunity to specify the appropriate medium. Use ``10base5/AUI''
|
||||
to select the AUI connector, or ``10baseT/UTP'' to select the UTP connector.
|
||||
opportunity to specify the appropriate medium. Use ``10base5'' or ``AUI''
|
||||
to select the AUI connector, or ``10baseT'' or ``UTP'' to select the UTP
|
||||
connector. Fast ethernet interfaces default to ``auto'', which
|
||||
usually does not detect properly and runs at ``10BaseT'' speed. The
|
||||
options are ``10baseT'', ``100baseTX'', and ``auto''. The hme and qfe
|
||||
interfaces also allow ``10baseT-FDX'' and ``100baseTX-FDX''.
|
||||
|
|
|
@ -1,46 +1,3 @@
|
|||
.\" $NetBSD: upgrade,v 1.10 2000/10/10 12:55:22 lukem Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
|
||||
.\" All rights reserved.
|
||||
.\"
|
||||
.\" Redistribution and use in source and binary forms, with or without
|
||||
.\" modification, are permitted provided that the following conditions
|
||||
.\" are met:
|
||||
.\" 1. Redistributions of source code must retain the above copyright
|
||||
.\" notice, this list of conditions and the following disclaimer.
|
||||
.\" 2. Redistributions in binary form must reproduce the above copyright
|
||||
.\" notice, this list of conditions and the following disclaimer in the
|
||||
.\" documentation and/or other materials provided with the distribution.
|
||||
.\" 3. All advertising materials mentioning features or use of this software
|
||||
.\" must display the following acknowledgement:
|
||||
.\" This product includes software developed by the NetBSD
|
||||
.\" Foundation, Inc. and its contributors.
|
||||
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
|
||||
.\" contributors may be used to endorse or promote products derived
|
||||
.\" from this software without specific prior written permission.
|
||||
.\"
|
||||
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
|
||||
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
|
||||
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
||||
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
|
||||
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
|
||||
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
|
||||
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
||||
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
|
||||
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $NetBSD: upgrade,v 1.11 2000/10/21 04:49:26 mbw Exp $
|
||||
.
|
||||
To upgrade to
|
||||
.Nx \*V
|
||||
from a previous version follow the instructions in the section
|
||||
.Sx Installing NetBSD ,
|
||||
but run the script
|
||||
.Pa upgrade.sh
|
||||
instead of
|
||||
.Pa install.sh .
|
||||
.Pp
|
||||
The upgrade script will use the existing disk partitions to install the
|
||||
new system in, and also preserves the files in
|
||||
.Pa /etc .
|
||||
.so ../common/upgrade
|
||||
|
|
Loading…
Reference in New Issue