summaryrefslogtreecommitdiff
path: root/distrib/notes
diff options
context:
space:
mode:
Diffstat (limited to 'distrib/notes')
-rw-r--r--distrib/notes/luna88k/contents6
-rw-r--r--distrib/notes/luna88k/install69
-rw-r--r--distrib/notes/luna88k/prep77
-rw-r--r--distrib/notes/luna88k/upgrade6
-rw-r--r--distrib/notes/luna88k/xfer5
5 files changed, 107 insertions, 56 deletions
diff --git a/distrib/notes/luna88k/contents b/distrib/notes/luna88k/contents
index 9ebc2d4a286..9ba100ab8cc 100644
--- a/distrib/notes/luna88k/contents
+++ b/distrib/notes/luna88k/contents
@@ -1,12 +1,16 @@
-dnl $OpenBSD: contents,v 1.11 2013/07/26 20:07:29 miod Exp $
+dnl $OpenBSD: contents,v 1.12 2013/10/30 22:06:36 miod Exp $
TopPart
OpenBSDdistsets
OpenBSDbsd
+OpenBSDbsdmp
+
OpenBSDrd
+ boot The OpenBSD/MACHINE boot block.
+
These files can be used to make a bootable tape suitable for installation.
They can also be used to configure an NFS server to support installation
over the network. See the section "Getting the OpenBSD system onto Useful
diff --git a/distrib/notes/luna88k/install b/distrib/notes/luna88k/install
index bb6aa53b353..0f7fdaf20f2 100644
--- a/distrib/notes/luna88k/install
+++ b/distrib/notes/luna88k/install
@@ -1,4 +1,4 @@
-dnl $OpenBSD: install,v 1.9 2010/03/16 17:23:09 miod Exp $
+dnl $OpenBSD: install,v 1.10 2013/10/30 22:06:36 miod Exp $
OpenBSDInstallPrelude
There are several ways to install OpenBSD onto a disk. The easiest way
@@ -22,44 +22,55 @@ using the shutdown(8) and/or halt(8) commands, which will eventually go
back to the PROM prompt. Remember that the leftmost switch from the front
panel DIP switch #1 must be down to access the PROM prompt.
-Booting from an installation tape:
-
- The internal tape drive is usually configured as SCSI ID #4. At the
- prompt, enter
-
- b st(0,0,0)
-
- to boot the first file from the tape. If your tape drive uses a
- different SCSI ID, replace the middle number with the appropriate number
- from the following table:
+dnl Not until the bootblock can boot from tape.
+dnl Booting from an installation tape:
+dnl
+dnl The internal tape drive is usually configured as SCSI ID #4. At the
+dnl prompt, enter
+dnl
+dnl b st(0,0,0)
+dnl
+dnl to boot the first file from the tape. If your tape drive uses a
+dnl different SCSI ID, replace the middle number with the appropriate number
+dnl from the following table:
+dnl
+dnl tape drive SCSI ID: 0 1 2 3 4 5 6
+dnl middle number for st(): 4 3 2 1 0 6 5
+dnl
+dnl If the tape drive is connected to the external SCSI controller, add 10 to
+dnl the middle number. For example, to boot from a tape drive with ID #5
+dnl connected to the external controller, enter:
+dnl
+dnl b st(0,16,0)
+dnl
+Booting from an existing partition:
- tape drive SCSI ID: 0 1 2 3 4 5 6
- middle number for st(): 4 3 2 1 0 6 5
+ Copy the OpenBSD/MACHINE boot loader on one of the first 8 partitions
+ (a-h). Copy the installation kernel (bsd.rd) to the same partition.
- If the tape drive is connected to the external SCSI controller, add 10 to
- the middle number. For example, to boot from a tape drive with ID #5
- connected to the external controller, enter:
+ At the PROM prompt, enter
- b st(0,16,0)
+ b sd(n,p) boot
-Booting from an existing partition:
+ to boot the OpenBSD bootloader from the specified disk and partition.
+ Replace 'p' with the partition number (usually 0, for the 'a' partition),
+ and 'n' with the appropriate number from the following table:
- At the prompt, enter
+ disk drive SCSI ID: 0 1 2 3 4 5 6
+ value of 'n': 6 5 4 3 2 1 0
- b sd(0,n,p) bsd.rd
+ On LUNA88K-2 systems, if the disk drive is connected to the external SCSI
+ controller, add 10 to this number. For example, to boot from a disk drive
+ with ID #0 connected to the external controller, enter:
- to boot bsd.rd from the specified disk and partition. Replace 'p' with
- the partition number (usually 0, for the 'a' partition), and 'n' with
- the appropriate number from the following table:
+ b sd(10,0)boot
- disk drive SCSI ID: 0 1 2 3 4 5 6
- value of 'n': 6 5 4 3 2 1 0
+ Once the OpenBSD bootloader starts, press any key to stop the countdown
+ if the ``boot>'' prompt does not appear.
- If the disk drive is connected to the external SCSI controller, add 10 to
- this number. For example, to boot from a disk drive with ID #0 connected
- to the external controller, enter:
+ Then, boot the installation kernel from the same partition:
- b sd(0,16,0) bsd.rd
+ b sd(n,p)bsd.rd
Installing the system:
diff --git a/distrib/notes/luna88k/prep b/distrib/notes/luna88k/prep
index e50837a2f52..dc8f5a004c0 100644
--- a/distrib/notes/luna88k/prep
+++ b/distrib/notes/luna88k/prep
@@ -1,32 +1,65 @@
-dnl $OpenBSD: prep,v 1.4 2005/03/31 13:59:46 aoyama Exp $
+dnl $OpenBSD: prep,v 1.5 2013/10/30 22:06:36 miod Exp $
+dnl Need to provide a short monitor description. Start from
+dnl http://www.nk-home.net/~aoyama/luna88k/monitor.txt
+dnl and also document NVRAM?
Luna-88K do not require any specific preparation prior to the OpenBSD
installation. However, you might want to get familiar with the PROM
interface, in order to be able to boot the installation media and, later,
specify the correct boot parameters.
-The first set of DIP switches in the front panel (DIP SW1) is used to
-select the machine behaviour upon powerup, as well as the preferred
-console device.
+Setting up the boot device and filename:
-The meaning of these switches will depend upon your particular machine.
-On the Luna-88k, the 'down' position is 'on', and the 'up' position is
-'off', while the Luna-88k2 uses the opposite convention (i.e. 'up' is 'on'
-and 'down' is 'off').
+ Boot device and filename information is stored by the PROM into
+ the machine's non-volatile memory.
-If the leftmost switch in SW1, #1, is in the 'off' position, the system will
-auto-boot from the boot device saved in NVRAM. Otherwise, the boot process
-will stop at the PROM prompt.
+ LUNA88K systems can only boot from SCSI devices. The boot device type
+ (either ``sd'' for a disk or ``st'' for a tape) is specified by the
+ ``boot_device'' variable. The SCSI id of the boot device is specified
+ by the ``boot_unit'' NVRAM variable, and the boot partition on said
+ device is specified by the ``boot_partition'' variable. The
+ ``boot_filename'' variable stores the name of the file to boot, and
+ defaults to ``vmunix''. To boot OpenBSD, this variable should be
+ changed to ``boot'', as in:
+ 0> nvram boot_filename boot
-The second switch in SW1, #2, selects the console device. When in the 'on'
-position, it selects the serial console port as the console; otherwise,
-the graphics display and keyboard are used as the console.
+ The ``boot_unit'' value is an encoding of the device SCSI identifier.
+ If the boot device is an SCSI disk (``sd''), the value of ``boot_unit''
+ should be (6 - ID). On LUNA88K-2 systems, if the boot device is connected
+ to the external SCSI connector, 10 should be added to the value of
+ ``boot_unit''. Thus booting off an external SCSI disk of ID #0 would
+ be 16 on a LUNA88K-2, and 6 on a LUNA88K.
+
+Setting up the boot behaviour:
+
+ Unlike other platforms, boot behaviour is controlled by the front panel
+ DIP switches only.
+
+ The first set of DIP switches in the front panel (DIP SW1) is used to
+ select the machine behaviour upon powerup, as well as the preferred
+ console device.
+
+ The meaning of these switches will depend upon your particular machine.
+ On the LUNA88K, the 'down' position is 'on', and the 'up' position is
+ 'off', while the LUNA88K-2 uses the opposite convention (i.e. 'up' is
+ 'on' and 'down' is 'off').
+
+ If the leftmost switch in SW1, #1, is in the 'off' position, the system
+ will auto-boot from the boot device saved in NVRAM (using the
+ ``boot_device'', ``boot_unit'' and ``boot_filename'' variables). Otherwise,
+ the boot process will stop at the PROM prompt.
+
+Setting up serial console:
+
+ The second switch in SW1, #2, selects the console device. When in the 'on'
+ position, it selects the serial console port as the console; otherwise,
+ the graphics display and keyboard are used as the console.
+
+ While the LUNA88K-2 uses ``standard'' DB9 serial ports, the earlier
+ LUNA88K have a specific connector, HiRose QM10-14R(L)-PR. Wiring
+ information for this connector can be found at the following URL:
+ http://www.kk.iij4u.or.jp/~taokamur/luna68k/serial.jpg
+ A suitable cable connector for this port would be either HiRose
+ QM30-14PA-EP with a QM14-CS cover (with lock), or QM30-14P-EP with a
+ QM14-CY cover (without lock).
-While the Luna-88K2 uses ``standard'' serial ports, the earlier Luna-88K
-have a specific connector. Wiring information for this connector can be
-found at the following URL:
- http://www.kk.iij4u.or.jp/~taokamur/luna68k/serial.jpg
-dnl
-dnl Need to provide a short monitor description. Start from
-dnl http://www.nk-home.net/~aoyama/luna/monitor.txt
-dnl and also document NVRAM?
diff --git a/distrib/notes/luna88k/upgrade b/distrib/notes/luna88k/upgrade
index 93c606d1534..65777053f0c 100644
--- a/distrib/notes/luna88k/upgrade
+++ b/distrib/notes/luna88k/upgrade
@@ -1,2 +1,4 @@
-dnl $OpenBSD: upgrade,v 1.2 2005/03/31 13:59:46 aoyama Exp $
-OpenBSDUpgrade({:-an installation tape, or a bsd.rd file on the root file system-:})
+dnl $OpenBSD: upgrade,v 1.3 2013/10/30 22:06:36 miod Exp $
+dnl Not until tape boot works again
+dnl OpenBSDUpgrade({:-an installation tape, or a bsd.rd file on the root file system-:})
+OpenBSDUpgrade({:-bsd.rd on the root file system-:})
diff --git a/distrib/notes/luna88k/xfer b/distrib/notes/luna88k/xfer
index 032480ced95..bc7a75f4f06 100644
--- a/distrib/notes/luna88k/xfer
+++ b/distrib/notes/luna88k/xfer
@@ -1,4 +1,4 @@
-dnl $OpenBSD: xfer,v 1.5 2010/03/16 17:23:09 miod Exp $
+dnl $OpenBSD: xfer,v 1.6 2013/10/30 22:06:36 miod Exp $
Installation is supported from several media types, including:
CD-ROM
@@ -10,8 +10,9 @@ Installation is supported from several media types, including:
OpenBSDXferPrelude
+dnl Not until tape boot works again
dnl OpenBSDXferBootTape(xbase xetc xfont xshare,bsd.rd obs=8k conv=osync)
-OpenBSDXferBootTape(,bsd.rd obs=8k conv=osync)
+OpenBSDXferBareTape(xbase xetc xfont xshare)
OpenBSDXferNFS