Bring these up to date WRT reality. In particular, the disk-space
requirements were somewhat insufficient, and MVME162 was nowhere to be seen.
This commit is contained in:
scw
parent
3cae956077
commit
5e24af1bd0
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: contents,v 1.27 2000/10/29 13:13:07 simonb Exp $
|
||||
.\" $NetBSD: contents,v 1.28 2000/11/01 10:58:30 scw Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
|
||||
.\" All rights reserved.
|
||||
@ -81,6 +81,15 @@ A version of
|
||||
.Li INSTALL
|
||||
intended to run on machines with less than 8 MB.
|
||||
.\}
|
||||
.
|
||||
.if r_mvme68k \{\
|
||||
. It Pa netbsd.VME147.gz
|
||||
A kernel for MVME147 boards.
|
||||
. It Pa netbsd.VME162.gz
|
||||
A kernel for MVME162-LX boards.
|
||||
. It Pa netbsd.VME167.gz
|
||||
A kernel for MVME167 boards.
|
||||
.\}
|
||||
. tag)
|
||||
. It Pa sets/
|
||||
\*M binary distribution sets;
|
||||
@ -90,8 +99,10 @@ see below.
|
||||
.
|
||||
. (tag instkernel/ -compact
|
||||
.
|
||||
.if !r_mvme68k \{\
|
||||
. It Pa floppy/
|
||||
\*M boot and installation floppies; see below.
|
||||
.\}
|
||||
.
|
||||
.if r_alpha \{\
|
||||
. It Pa diskimage/
|
||||
@ -122,6 +133,7 @@ this image.
|
||||
\*M miniroot file system image; see below.
|
||||
.\}
|
||||
.
|
||||
.if !r_mvme68k \{\
|
||||
. It Pa misc/
|
||||
.
|
||||
.if r_alpha \{\
|
||||
@ -142,12 +154,13 @@ Statically-linked versions of
|
||||
Miscellaneous \*M installation utilities; see
|
||||
installation section, below.
|
||||
\}
|
||||
.\}
|
||||
.
|
||||
.if r_mvme68k \{\
|
||||
. It Pa netboot/
|
||||
Two programs needed to boot \*M kernels over the network.
|
||||
Two programs needed to boot \*M kernels over the network; see below.
|
||||
. It Pa tapeimage/
|
||||
Tape boot programs, and a RAMDISK kernel.
|
||||
Tape boot programs, and a RAMDISK kernel; see below.
|
||||
.\}
|
||||
.
|
||||
.if \n[sparc]:\n[sparc64] \{\
|
||||
@ -249,63 +262,6 @@ for more details.)
|
||||
.\}
|
||||
.
|
||||
.
|
||||
.if r_mvme68k \{\
|
||||
.Pp
|
||||
The
|
||||
.Nx*M
|
||||
install distribution contains files that can be
|
||||
used to install
|
||||
.Nx
|
||||
onto completely
|
||||
.Sq bare
|
||||
MVME147 and MVME167
|
||||
boards. The files
|
||||
in the
|
||||
.Pa mvme68k/installation
|
||||
directories are described below.
|
||||
.(tag netbsd-rd.gz
|
||||
.It Pa miniroot.gz
|
||||
A gzipped copy of the miniroot file system.
|
||||
This image is to be un-gzipped and copied
|
||||
into the swap area of a disk.
|
||||
.It Pa netbsd-rd.gz
|
||||
A gzipped copy of the
|
||||
.Li RAMDISK
|
||||
kernel for installing the miniroot file system.
|
||||
.It Pa stboot
|
||||
A tape boot-block, in the form required to
|
||||
allow 1x7-Bug to boot from tape. This is the
|
||||
first segment of a boot tape.
|
||||
.It Pa bootst
|
||||
A copy of the tape boot program, used
|
||||
as the second segment of a boot tape.
|
||||
.It Pa sboot
|
||||
A copy of the MVME147 serial boot program. This is
|
||||
necessary if you don't have a tape drive,
|
||||
but you
|
||||
.Em do
|
||||
have another system which can
|
||||
act as a boot and NFS server. This is also
|
||||
useful if you are installing a diskless
|
||||
.Nx
|
||||
system on an MVME147 board.
|
||||
.It Pa netboot
|
||||
A copy of the network boot program. Used
|
||||
in conjunction with sboot on the MVME147 to get your system
|
||||
booted over a network. The MVME167 can boot this file
|
||||
directly using 167Bug's builtin TFTP client.
|
||||
.tag)
|
||||
.Pp
|
||||
These files can be used to make a boot tape suitable for installing
|
||||
.Nx*M .
|
||||
These files can also be used to configure an NFS server
|
||||
to support installation
|
||||
.Sq "over the network" . See the section
|
||||
.Sx Getting the NetBSD System onto Useful Media
|
||||
for instructions on either method.
|
||||
.\}
|
||||
.
|
||||
.
|
||||
.Ss2 Binary distribution sets
|
||||
The
|
||||
.Nx
|
||||
@ -989,6 +945,70 @@ the sources for these utilities are in the
|
||||
.Pa src No subdirectory.
|
||||
.\}
|
||||
.
|
||||
.if r_mvme68k \{\
|
||||
.Pp
|
||||
The following are included in the
|
||||
.Pa mvme68k/installation No directory:
|
||||
.
|
||||
.(tag miniroot/
|
||||
.It Pa miniroot/
|
||||
. (tag miniroot.gz
|
||||
. It Pa miniroot.gz
|
||||
A copy of the miniroot file system.
|
||||
This filesystem image is copied into the swap partition of the disk which
|
||||
you intend to boot
|
||||
.Nx
|
||||
from. Normally, this step will be performed manually from the ramdisk boot
|
||||
environment.
|
||||
. tag)
|
||||
.tag)
|
||||
.
|
||||
.(tag miniroot/
|
||||
.It Pa netboot/
|
||||
. (tag sboot
|
||||
. It Pa sboot
|
||||
An MVME147 bootstrap program in Motorola S-Record format. This is
|
||||
required when you wish to boot an MVME147 over the network since
|
||||
the ROM has no built-in network support. Instructions for getting
|
||||
this program into memory are discussed later.
|
||||
. tag)
|
||||
. (tag netboot
|
||||
. It Pa netboot
|
||||
A standalone 2nd stage bootstrap program loaded over the network
|
||||
via TFTP. This is responsible for fetching and starting the
|
||||
.Nx
|
||||
\*M
|
||||
kernel from an NFS server.
|
||||
. tag)
|
||||
.tag)
|
||||
.
|
||||
.(tag tapeimage/
|
||||
.It Pa tapeimage/
|
||||
. (tag stboot
|
||||
. It Pa stboot
|
||||
This file contains a boot sector for Motorola MVME boards. It must
|
||||
be the first file written to a tape in order to make the tape bootable.
|
||||
. tag)
|
||||
. (tag bootst
|
||||
. It Pa bootst
|
||||
This file contains a bootstrap program which knows how to load the
|
||||
.Nx
|
||||
\*M
|
||||
ramdisk image from tape. This must be the second file written to the tape.
|
||||
. tag)
|
||||
. (tag netbsd-rd.gz
|
||||
. It Pa netbsd-rd.gz
|
||||
This is the
|
||||
.Nx
|
||||
\*M
|
||||
ramdisk image. It contains a GENERIC kernel and a built in RAMDISK
|
||||
with just enough tools to partition a disk, dump the miniroot kernel
|
||||
to it and make the disk bootable. This must be the third file written
|
||||
to the tape.
|
||||
. tag)
|
||||
.tag)
|
||||
.\}
|
||||
.
|
||||
.
|
||||
.if r_pc532 \{\
|
||||
.Pp
|
||||
|
||||
@ -1,23 +1,35 @@
|
||||
.\" $NetBSD: hardware,v 1.6 2000/10/29 14:08:08 lukem Exp $
|
||||
.\" $NetBSD: hardware,v 1.7 2000/11/01 10:58:29 scw Exp $
|
||||
.
|
||||
.Nx*M
|
||||
\*V runs on Motorola
|
||||
.Tn MVME147 No and MVME167 No Single Board Computers.
|
||||
.Tn MVME147
|
||||
,
|
||||
.Tn MVME162-LX
|
||||
and
|
||||
.Tn MVME167
|
||||
Single Board Computers.
|
||||
.Pp
|
||||
The minimal configuration requires 4 MB of RAM and ~100 MB of disk space.
|
||||
The minimal configuration requires 8 MB of RAM and ~200 MB of disk space.
|
||||
To install the entire system requires much more disk space (approx.
|
||||
200 MB additional space is necessary for full sources. Double that if you
|
||||
600 MB additional space is necessary for full sources. Double that if you
|
||||
want to recompile it all!). To run X (clients only) or compile the system,
|
||||
more RAM is recommended. Good performance requires 8 MB of RAM, or 16 MB
|
||||
more RAM is recommended. Good performance requires 16 MB of RAM, or 32 MB
|
||||
when running the X Window System.
|
||||
.Pp
|
||||
Note that you can install
|
||||
.Nx
|
||||
\*V
|
||||
on a system with only 4 MB of onboard RAM, but you will need to use a
|
||||
VMEbus RAM card with at least another 4 MB to augment the onboard
|
||||
memory in order to actually install the system.
|
||||
.Pp
|
||||
Here is a table of recommended HD partition sizes for a full install:
|
||||
.Bl -column -offset indent Partition Suggested Needed
|
||||
.It Partition Ta Suggested Ta Needed
|
||||
.It /\ (root) Ta "20 MB" Ta "12 MB"
|
||||
.It /usr Ta "100 MB" Ta "80 MB"
|
||||
.It /var Ta "20 MB" Ta "5 MB"
|
||||
.It swap Ta Em "2-3 *RAM" Ta 6 MB
|
||||
.It /\ (root) Ta "32 MB" Ta "26 MB"
|
||||
.It /usr Ta "200 MB" Ta "150 MB"
|
||||
.It /var Ta "32 MB" Ta "6 MB"
|
||||
.It swap Ta Em "2-3 *RAM" Ta 16 MB
|
||||
.El
|
||||
.(item -offset indent
|
||||
Anything else is up to you!
|
||||
@ -28,7 +40,7 @@ Note that the
|
||||
installation procedure uses a
|
||||
.Em miniroot
|
||||
image which is placed into the swap area of the disk. The swap partition
|
||||
must be large enough to hold this miniroot image (\*> 6 MB).
|
||||
must be large enough to hold this miniroot image (\*> 7.5 MB).
|
||||
.
|
||||
.Ss2 Supported VME147 hardware
|
||||
.(bullet -offset indent
|
||||
@ -57,7 +69,7 @@ SCSI
|
||||
.(bullet -compact
|
||||
Most SCSI disks, tapes, CD-ROMs, etc
|
||||
.It
|
||||
On-board wd33c93 SCSI bus interface chip (async only for now)
|
||||
On-board wd33c93 SCSI bus interface chip (async only)
|
||||
.bullet)
|
||||
.It
|
||||
Miscellaneous:
|
||||
@ -65,6 +77,43 @@ Miscellaneous:
|
||||
Battery-backed real-time clock
|
||||
.It
|
||||
VMEbus RAM cards
|
||||
.It
|
||||
Any VMEbus interface cards with Machine Independent drivers
|
||||
.bullet)
|
||||
.bullet)
|
||||
.
|
||||
.Ss2 Supported VME162-LX hardware
|
||||
.(bullet -offset indent
|
||||
Serial ports (RS232)
|
||||
.(bullet -compact
|
||||
built-in console
|
||||
.It
|
||||
ttyZ1
|
||||
.It
|
||||
ttyZ2
|
||||
.It
|
||||
ttyZ3
|
||||
.bullet)
|
||||
.It
|
||||
Network interfaces:
|
||||
.(bullet -compact
|
||||
On-board Intel Ethernet (ie)
|
||||
.bullet)
|
||||
.It
|
||||
SCSI
|
||||
.(bullet -compact
|
||||
Most SCSI disks, tapes, CD-ROMs, etc
|
||||
.It
|
||||
On-board ncr53c710 SCSI I/O processor chip
|
||||
.bullet)
|
||||
.It
|
||||
Miscellaneous:
|
||||
.(bullet -compact
|
||||
Battery-backed real-time clock
|
||||
.It
|
||||
VMEbus RAM cards
|
||||
.It
|
||||
Any VMEbus interface cards with Machine Independent drivers
|
||||
.bullet)
|
||||
.bullet)
|
||||
.
|
||||
@ -88,7 +137,7 @@ On-board centronics style printer port
|
||||
.It
|
||||
Network interfaces:
|
||||
.(bullet -compact
|
||||
On-board Lance Ethernet (ie)
|
||||
On-board Intel Ethernet (ie)
|
||||
.bullet)
|
||||
.It
|
||||
SCSI
|
||||
@ -101,6 +150,10 @@ On-board ncr53c710 SCSI I/O Processor chip
|
||||
Miscellaneous:
|
||||
.(bullet -compact
|
||||
Battery-backed real-time clock
|
||||
.It
|
||||
VMEbus RAM cards
|
||||
.It
|
||||
Any VMEbus interface cards with Machine Independent drivers
|
||||
.bullet)
|
||||
.bullet)
|
||||
.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: install,v 1.10 2000/10/29 14:08:08 lukem Exp $
|
||||
.\" $NetBSD: install,v 1.11 2000/11/01 10:58:29 scw Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
|
||||
.\" All rights reserved.
|
||||
@ -57,11 +57,11 @@ Create the
|
||||
\*V boot tape as described in the section
|
||||
entitled
|
||||
.Sx "Preparing a boot tape" .
|
||||
Then, with the tape in the drive, type the following at the 1x7Bug prompt:
|
||||
Then, with the tape in the drive, type the following at the Bug prompt:
|
||||
.Pp
|
||||
.Dl 147-Bug\*> Ic "bo 5"
|
||||
.Pp
|
||||
.Dl 167-Bug\*> Ic "bo 0,50"
|
||||
.Dl 16x-Bug\*> Ic "bo 0,50"
|
||||
.Pp
|
||||
As mentioned earlier, this assumes your tape is jumpered for SCSI-ID 5.
|
||||
.Pp
|
||||
@ -73,13 +73,15 @@ SCSI disks detected by
|
||||
.Nx .
|
||||
They are of the form:
|
||||
.(disp
|
||||
sd0 at scsibus0 targ 0 lun 0: \*<CDC, 94161-9, 2506\*> SCSI1 0/direct fixed
|
||||
sd0: 148 MB, 967 cyl, 9 head, 35 sec, 512 bytes/sect x 304605 sectors
|
||||
sd0 at scsibus0 targ 0 lun 0: \*<Maker, Disk, Foo\*> SCSI1 0/direct fixed
|
||||
sd0: 800 MB, 800 cyl, 16 head, 128 sec, 512 bytes/sect x 1638400 sectors
|
||||
.disp)
|
||||
.Pp
|
||||
The information of most interest is the number of sectors; here it's
|
||||
304605. You will need this number when you come to create a disklabel
|
||||
for that drive.
|
||||
The information of most interest is the number of sectors; for the ficticious
|
||||
disk above, it's 1638400. You will need this number when you come to create
|
||||
a disklabel for that drive.
|
||||
.Pp
|
||||
Here is an example of an MVME147 system booting from tape:
|
||||
.(disp
|
||||
RAM address from VMEbus = $00000000
|
||||
|
||||
@ -89,15 +91,16 @@ Loading: Operating System
|
||||
Volume: NBSD
|
||||
|
||||
IPL loaded at: $003F0000
|
||||
\*>\*> BSD MVME147 tapeboot [$Revision: 1.10 $]
|
||||
\*>\*> BSD MVME147 tapeboot [$Revision: 1.11 $]
|
||||
578616+422344+55540+[46032+51284]=0x11a6e4
|
||||
Start @ 0x8000 ...
|
||||
Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved.
|
||||
Copyright (c) 1996, 1997, 1998, 1999, 2000
|
||||
The NetBSD Foundation, Inc. All rights reserved.
|
||||
Copyright (c) 1982, 1986, 1989, 1991, 1993
|
||||
The Regents of the University of California. All rights reserved.
|
||||
|
||||
NetBSD 1.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997
|
||||
steve@soapy.mctavish.demon.co.uk:/usr/src/sys/arch/mvme68k/compile/RAMDISK
|
||||
NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000
|
||||
steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK
|
||||
Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU
|
||||
real mem = 7237632
|
||||
avail mem = 6381568
|
||||
@ -112,7 +115,8 @@ clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM
|
||||
.Pp
|
||||
.(Note
|
||||
The exact text of the messages will vary depending on which
|
||||
MVME147 or MVME167 variant you're using.
|
||||
\*M
|
||||
variant you're using.
|
||||
.Note)
|
||||
.Pp
|
||||
Finally, you will see the following "welcome" message:
|
||||
@ -251,7 +255,7 @@ at the edlabel prompt, then enter the letter corresponding to the first
|
||||
.Dl edlabel/modify\*> Ic a
|
||||
.Dl a (root) 0 (0/00/00) 0 (0/00/00) unused
|
||||
.Dl start as \*<blkno\*> or \*<cyls/trks/sects\*> : Ic 0
|
||||
.Dl length as \*<nblks\*> or \*<cyls/trks/sects\*> : Ic 38000
|
||||
.Dl length as \*<nblks\*> or \*<cyls/trks/sects\*> : Ic 65536
|
||||
.Dl type: Ic 4.2BSD
|
||||
.Dl edlabel/modify\*>
|
||||
.Pp
|
||||
@ -263,8 +267,8 @@ it's probably easiest to use block
|
||||
notation. The above example creates partition
|
||||
.Sq Li a ,
|
||||
starting at block zero
|
||||
and with a size of 38000 blocks. Note that the usual size of a block is
|
||||
512 bytes, so this creates a 19 MB partition.
|
||||
and with a size of 65536 blocks. Note that the usual size of a block is
|
||||
512 bytes, so this creates a 32 MB partition.
|
||||
.Pp
|
||||
The
|
||||
.Li type
|
||||
@ -280,7 +284,7 @@ installation!
|
||||
.Pp
|
||||
.Dl edlabel/modify\*> Ic b
|
||||
.Dl b (swap) 0 (0/00/00) 0 (0/00/00) unused
|
||||
.Dl start as \*<blkno\*> or \*<cyls/trks/sects\*> : Ic 38000
|
||||
.Dl start as \*<blkno\*> or \*<cyls/trks/sects\*> : Ic 65536
|
||||
.Dl length as \*<nblks\*> or \*<cyls/trks/sects\*> : Ic 32768
|
||||
.Dl type: Ic swap
|
||||
.Dl edlabel/modify\*>
|
||||
@ -289,10 +293,10 @@ Here, we specify a value for
|
||||
.Li start
|
||||
such that the swap partition follows immediately after partition
|
||||
.Sq Li a ,
|
||||
i.e. 38000. The length of the swap
|
||||
i.e. 65536. The length of the swap
|
||||
partition should be a multiple of the amount of RAM you have in your
|
||||
system. Here, we've chosen 32768, or 16 MB. The next available block on the
|
||||
drive is thus 38000 + 32768. We will use this to create partition
|
||||
drive is thus 65536 + 32768. We will use this to create partition
|
||||
.Sq Li d
|
||||
for our
|
||||
.Pa /usr
|
||||
@ -301,20 +305,24 @@ than 8 MB of RAM, you'll be better off with a 32 or 64 MB swap partition.)
|
||||
.Pp
|
||||
.Dl edlabel/modify\*> Ic d
|
||||
.Dl d (user) 0 (0/00/00) 0 (0/00/00) unused
|
||||
.Dl start as \*<blkno\*> or \*<cyls/trks/sects\*> : Ic 70768
|
||||
.Dl length as \*<nblks\*> or \*<cyls/trks/sects\*> : Ic 233837
|
||||
.Dl start as \*<blkno\*> or \*<cyls/trks/sects\*> : Ic 98304
|
||||
.Dl length as \*<nblks\*> or \*<cyls/trks/sects\*> : Ic 1540096
|
||||
.Dl type: Ic 4.2BSD
|
||||
.Dl edlabel/modify\*> Ic q
|
||||
.Dl edlabel\*>
|
||||
.Pp
|
||||
As you can see, we've chosen to assign the remainder of the disk to
|
||||
.Pa /usr .
|
||||
Since there are 304605 sectors on the example disk (did you remember to
|
||||
Since there are 1638400 sectors on the example disk (did you remember to
|
||||
note down the number of sectors on your disk during boot?), and partition
|
||||
.Sy d
|
||||
starts at sector 70768, a simple bit of arithmetic (304605 - 70768)
|
||||
starts at sector 98304, a simple bit of arithmetic (1638400 - 98304)
|
||||
gives
|
||||
.Sy d No a size of 233837.
|
||||
.Sy d No a size of 1540096.
|
||||
.Pp
|
||||
Note that the above partition sizes are just guidelines. If your disk is
|
||||
large enough, you should resize the partitions appropriately and
|
||||
perhaps also create a /var partition as well.
|
||||
.Pp
|
||||
You now need to write this new disklabel, together with the partition
|
||||
details you've just entered, to disk. You might also try the
|
||||
@ -330,16 +338,16 @@ to view the partitions. Once written, you can quit back to ssh using
|
||||
type_name: SCSI disk
|
||||
pack_name: fictitious
|
||||
bytes/sector: 512
|
||||
sectors/track: 35
|
||||
tracks/cylinder: 9
|
||||
cylinders: 967
|
||||
sectors/cylinder: 315
|
||||
sectors/track: 128
|
||||
tracks/cylinder: 16
|
||||
cylinders: 800
|
||||
sectors/cylinder: 2048
|
||||
partition start (c/t/s) nblks (c/t/s) type
|
||||
|
||||
a (root) 0 (0/00/00) 38000 (120/05/25)* 4.2BSD
|
||||
b (swap) 38000 (120/05/25)* 32768 (104/00/08)* swap
|
||||
c (disk) 0 (0/00/00) 304605 (967/00/00) unused
|
||||
d (user) 70768 (224/05/33)* 233837 (742/03/02)* 4.2BSD
|
||||
a (root) 0 (0/00/00) 65536 (32/00/00) 4.2BSD
|
||||
b (swap) 65536 (32/00/00) 32768 (48/00/00) swap
|
||||
c (disk) 0 (0/00/00) 1638400 (800/00/00) unused
|
||||
d (user) 98304 (48/00/00) 1540096 (752/00/00) 4.2BSD
|
||||
.disp)
|
||||
.Pp
|
||||
.Dl edlabel\*> Ic w
|
||||
@ -369,7 +377,6 @@ You can now shutdown the system.
|
||||
.Dl ssh: Ic halt
|
||||
.Dl signal 15
|
||||
.Dl ssh: syncing disks... done
|
||||
.Dl unmounting /mnt (/dev/sd1b)...
|
||||
.Dl unmounting / (root_device)...
|
||||
.Dl halted
|
||||
.Pp
|
||||
@ -379,7 +386,7 @@ You can now shutdown the system.
|
||||
.Dl Cold/Warm Reset flag [C,W] = C?
|
||||
.Dl Execute Soft Reset [Y,N] N? Ic y
|
||||
.Pp
|
||||
Resetting the MVME167 board is very similar.
|
||||
Resetting the MVME162-LX and MVME167 boards are very similar.
|
||||
You should now reboot from that just installed miniroot. See the section
|
||||
entitled
|
||||
.Sx "Booting the miniroot"
|
||||
@ -462,33 +469,35 @@ Download was a success!
|
||||
.Pp
|
||||
See below for the next step in booting MVME147.
|
||||
.Pp
|
||||
The MVME167 is able to download netboot directly using TFTP.
|
||||
The MVME162-LX and MVME167 boards are able to download netboot
|
||||
directly using TFTP.
|
||||
To enable this, you must first configure the networking parameters
|
||||
on the board as described in the section entitled "Preparing your System
|
||||
for
|
||||
.Nx
|
||||
Installation. On a properly configured MVME167, all you need
|
||||
Installation. On a properly configured MVME162-LX or MVME167, all you need
|
||||
to type is:
|
||||
.Pp
|
||||
.Dl 167-Bug\*> Ic nbo
|
||||
.Dl 16x-Bug\*> Ic nbo
|
||||
.Pp
|
||||
For both boards, the boot messages are very similar:
|
||||
For all board types, the boot messages are very similar:
|
||||
.Pp
|
||||
.(disp
|
||||
Start @ 0x8000 ...
|
||||
\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.10 $]
|
||||
\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.11 $]
|
||||
device: le0 attached to 08:00:3e:20:cb:87
|
||||
boot: client IP address: 192.168.1.4
|
||||
boot: client name: soapy
|
||||
root addr=192.168.1.1 path=/export/soapy
|
||||
578616+422344+55540+[46032+51284]=0x11a6e4
|
||||
Start @ 0x8000 ...
|
||||
Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved.
|
||||
Copyright (c) 1996, 1997, 1998, 1999, 2000
|
||||
The NetBSD Foundation, Inc. All rights reserved.
|
||||
Copyright (c) 1982, 1986, 1989, 1991, 1993
|
||||
The Regents of the University of California. All rights reserved.
|
||||
The Regents of the University of California. All rights reserved.
|
||||
|
||||
NetBSD 1.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997
|
||||
steve@soapy.mctavish.demon.co.uk:/usr/src/sys/arch/mvme68k/compile/RAMDISK
|
||||
NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000
|
||||
steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK
|
||||
Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU
|
||||
real mem = 7237632
|
||||
avail mem = 6381568
|
||||
@ -525,7 +534,7 @@ The command:
|
||||
.Pp
|
||||
.Dl ssh: Ic "ifconfig ie0 inet 192.168.1.4 up"
|
||||
.Pp
|
||||
will bring up the MVME167 network interface
|
||||
will bring up the MVME162-LX or MVME167 network interface
|
||||
.Li ie0
|
||||
with that address.
|
||||
The next
|
||||
@ -587,9 +596,9 @@ SCSI-ID 0, then the 147Bug boot command is:
|
||||
.Pp
|
||||
.Dl 147-Bug\*> Ic "bo 0,,b:"
|
||||
.Pp
|
||||
The corresponding 167Bug boot command is:
|
||||
The corresponding 162Bug or 167Bug boot command is:
|
||||
.Pp
|
||||
.Dl 167-Bug\*> Ic "bo 0,,,b:"
|
||||
.Dl 16x-Bug\*> Ic "bo 0,,,b:"
|
||||
.Pp
|
||||
The command line parameters above are:
|
||||
.Pp
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: prep,v 1.8 2000/10/29 14:08:08 lukem Exp $
|
||||
.\" $NetBSD: prep,v 1.9 2000/11/01 10:58:29 scw Exp $
|
||||
.
|
||||
\*M machines usually need little or no preparation before installing
|
||||
.Nx ,
|
||||
@ -6,7 +6,26 @@ other than the usual, well advised precaution of
|
||||
.Em backing up all data
|
||||
on any attached storage devices.
|
||||
.Pp
|
||||
The following instructions should make your machine
|
||||
The exception to the above is that
|
||||
.Tn MVME162-LX
|
||||
and
|
||||
.Tn MVME167
|
||||
boards require a jumper to be removed before
|
||||
.Nx
|
||||
can be installed.
|
||||
On
|
||||
.Tn MVME162-LX
|
||||
pins 1-2 of jumper J11
|
||||
.Em must
|
||||
be removed.
|
||||
On
|
||||
.Tn MVME167
|
||||
pins 1-2 of jumper J1
|
||||
.Em must
|
||||
be removed.
|
||||
.Pp
|
||||
Once you've made any necessary jumper changes,
|
||||
the following instructions should make your machine
|
||||
.Dq NetBSD Ready .
|
||||
.Pp
|
||||
Power-up your MVME147 board. You should have the
|
||||
@ -19,7 +38,8 @@ Onboard RAM start = $00000000, stop = $007FFFFF
|
||||
147-Bug\*>
|
||||
.disp)
|
||||
.Pp
|
||||
Or, if you have an MVME167 board:
|
||||
Or, if you have an MVME162-LX or MVME167 board (the following boot
|
||||
message is from MVME167; MVME162-LX is similar):
|
||||
.(disp
|
||||
MVME167 Debugger/Diagnostics Release Version 2.3 - 02/25/94
|
||||
COLD Start
|
||||
@ -35,16 +55,16 @@ Make sure the RAM size looks ok (if you've got an 8 MB MVME147 or a
|
||||
32 MB MVME167 you should
|
||||
have the same value as we do). Also make sure the clock is ticking:
|
||||
.Pp
|
||||
.Dl 1x7-Bug\*> Ns Ic time
|
||||
.Dl 1xx-Bug\*> Ns Ic time
|
||||
.Dl Sunday 12/21/31 16:25:14
|
||||
.Dl 1x7-Bug\*> Ns Ic time
|
||||
.Dl 1xx-Bug\*> Ns Ic time
|
||||
.Dl Sunday 12/21/31 16:25:15
|
||||
.Dl 1x7-Bug\*>
|
||||
.Dl 1xx-Bug\*>
|
||||
.Pp
|
||||
Note that
|
||||
.Nx
|
||||
bases its year at 1968, and adds the year offset in
|
||||
the MVME1x7's real-time clock to get the current year. So the
|
||||
the system's real-time clock to get the current year. So the
|
||||
.Li 31
|
||||
here
|
||||
equates to 1999. You may have to adjust your clock using the
|
||||
@ -64,25 +84,26 @@ doesn't get set correctly by the 147Bug PROM.
|
||||
.Pp
|
||||
Also make sure that your board's ethernet address is initialised to
|
||||
the correct value. You'll find the address on a label on the inside of
|
||||
the MVME147's front panel, and on the VMEbus P2 connector of the MVME167.
|
||||
the MVME147's front panel, and on the VMEbus P2 connector of the MVME162-LX
|
||||
and MVME167.
|
||||
On the MVME147, enter the last five digits of the address
|
||||
using the
|
||||
.Ic lsad
|
||||
command. On the MVME167, you should use the
|
||||
command. On the MVME162-LX and MVME167, you should use the
|
||||
.Ic cnfg
|
||||
command.
|
||||
.Pp
|
||||
To install successfully to a local SCSI disk, you need to ensure that
|
||||
1x7Bug is aware of what targets are connected to the SCSI bus. This
|
||||
the system is aware of what targets are connected to the SCSI bus. This
|
||||
can be done by issueing the following command:
|
||||
.Pp
|
||||
.Dl 1x7-Bug\*> Ic iot;t
|
||||
.Dl 1xx-Bug\*> Ic iot;t
|
||||
.Pp
|
||||
At this point, 1x7Bug will scan for any attached SCSI devices. After
|
||||
At this point, Bug will scan for any attached SCSI devices. After
|
||||
a short delay, a list of SCSI devices will be displayed. 147Bug will
|
||||
ask if LUNs should be assigned from SCSI ids, to which you should
|
||||
answer Y. You should also answer Y when asked if the information is
|
||||
to be saved to NVRAM. 167Bug does not prompt for this information.
|
||||
to be saved to NVRAM. 16xBug does not prompt for this information.
|
||||
.Pp
|
||||
The following installation instructions will assume that your target
|
||||
SCSI disk drive appears at SCSI-ID 0. If you have a tape drive, the
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: xfer,v 1.7 2000/10/29 14:08:08 lukem Exp $
|
||||
.\" $NetBSD: xfer,v 1.8 2000/11/01 10:58:29 scw Exp $
|
||||
.
|
||||
Installation is supported from several media types, including:
|
||||
.(bullet
|
||||
@ -107,10 +107,15 @@ where the TFTP daemon can find it (remember, many TFTP daemons run in
|
||||
a chroot'ed environment). The netboot program may be found in the
|
||||
install directory of this distribution.
|
||||
.Pp
|
||||
The MVME167 boot ROM has code builtin to boot over ethernet from a
|
||||
The
|
||||
.Tn MVME162-LX
|
||||
and
|
||||
.Tn MVME167
|
||||
boot ROMs have code builtin to boot over ethernet from a
|
||||
TFTP server. You should configure it to download the same
|
||||
.Pa netboot
|
||||
program as is used for MVME147.
|
||||
program as is used for
|
||||
.Tn MVME147 .
|
||||
.Pp
|
||||
The netboot program will query a bootparamd server to find the NFS
|
||||
server address and path name for its root, and then load a kernel from
|
||||
@ -129,7 +134,7 @@ in the client's root directory before trying to netboot the client.
|
||||
The client will need access to the miniroot image, which can be
|
||||
provided using NFS or remote shell. If using NFS, miniroot.gz should be
|
||||
expanded on the server, because doing so from the RAMDISK shell is not
|
||||
so easy. The unzipped miniroot takes about 6 MB of space.
|
||||
so easy. The unzipped miniroot takes about 7.5 MB of space.
|
||||
.Pp
|
||||
If you will be installing
|
||||
.Nx
|
||||
|
||||
Loading…
Reference in New Issue
Block a user