Source-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[src/netbsd-1-5]: src/distrib/notes/mvme68k Pullup 1.9 [scw]:
details: https://anonhg.NetBSD.org/src/rev/3f006fc51809
branches: netbsd-1-5
changeset: 490093:3f006fc51809
user: tv <tv%NetBSD.org@localhost>
date: Thu Nov 02 23:30:29 2000 +0000
description:
Pullup 1.9 [scw]:
These bring the mvme68k installation notes up to date WRT supported
hardware and diskspace requirements. Plus a few minor tweaks/corrections.
diffstat:
distrib/notes/mvme68k/prep | 47 +++++++++++++++++++++++++++++++++------------
1 files changed, 34 insertions(+), 13 deletions(-)
diffs (101 lines):
diff -r fa59b3306c4a -r 3f006fc51809 distrib/notes/mvme68k/prep
--- a/distrib/notes/mvme68k/prep Thu Nov 02 23:30:18 2000 +0000
+++ b/distrib/notes/mvme68k/prep Thu Nov 02 23:30:29 2000 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: prep,v 1.5.8.1 2000/11/01 03:48:21 tv Exp $
+.\" $NetBSD: prep,v 1.5.8.2 2000/11/02 23:30:29 tv Exp $
.
\*M machines usually need little or no preparation before installing
.Nx ,
@@ -6,7 +6,26 @@
.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 @@
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 @@
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 @@
.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
Home |
Main Index |
Thread Index |
Old Index