summaryrefslogtreecommitdiff
path: root/distrib
diff options
context:
space:
mode:
authorMiod Vallat <miod@cvs.openbsd.org>2002-10-07 20:49:06 +0000
committerMiod Vallat <miod@cvs.openbsd.org>2002-10-07 20:49:06 +0000
commit0d976423350c2c6fb5a6df51f06c7f219b9d7f2d (patch)
tree1aadba55b3688f3a71fa818f13b9339bf7709909 /distrib
parent912e8b0b10c1262577e70d4c9b91b0f5e4bc0e72 (diff)
Add specific installation steps for DEC 3000 machines, and document a few
caveats from their v.1 SRM.
Diffstat (limited to 'distrib')
-rw-r--r--distrib/notes/alpha/install20
-rw-r--r--distrib/notes/alpha/prep11
2 files changed, 22 insertions, 9 deletions
diff --git a/distrib/notes/alpha/install b/distrib/notes/alpha/install
index 408b42da9bc..ee55e75d37c 100644
--- a/distrib/notes/alpha/install
+++ b/distrib/notes/alpha/install
@@ -1,4 +1,4 @@
-dnl $OpenBSD: install,v 1.20 2002/04/09 01:22:22 miod Exp $
+dnl $OpenBSD: install,v 1.21 2002/10/07 20:49:04 miod Exp $
OpenBSDInstallPrelude
dnl XXX document mopbooting from the SRM console.
@@ -32,16 +32,24 @@ Booting from CD-ROM installation media:
(unless it is DKA0). For example, if your CD-ROM drive is listed
as DKA600, you want to use dka6 (device ID's are case
insensitive).
- Insert the OpenBSD/MACHINE CD and enter
+
+ On all MACHINE computers but the TURBOchannel DEC 3000 series,
+ insert the OpenBSD/MACHINE CD and enter
boot -fi OSREV/MACHINE/bsd.rd DEVICE
- where DEVICE is the dka device name. Note that the argument
- order is important here.
+ where DEVICE is the dka device name.
+
+ On the DEC 3000 series, insert the OpenBSD/MACHINE CD and enter
+ boot -fi ALPHA DEVICE
+ where DEVICE is the dka device name.
+
+ Note that, in both cases, the argument order is important.
+
You should see info about the primary and secondary boot
and then the kernel should start to load. If the kernel
fails to load or the spinning cursor has stopped and nothing
further has happened, you either have a hardware problem or
- your alpha is not currently supported by OpenBSD; try booting
- from a floppy instead.
+ your MACHINE is not currently supported by OpenBSD; try booting
+ from a floppy instead if possible.
Installing using the Floppy or CD-ROM procedure:
diff --git a/distrib/notes/alpha/prep b/distrib/notes/alpha/prep
index c909a7b2939..0117951c5cc 100644
--- a/distrib/notes/alpha/prep
+++ b/distrib/notes/alpha/prep
@@ -1,4 +1,4 @@
-dnl $OpenBSD: prep,v 1.17 2002/06/30 16:36:55 miod Exp $
+dnl $OpenBSD: prep,v 1.18 2002/10/07 20:49:05 miod Exp $
OpenBSD/MACHINE requires the SRM console. Some alphas come with
the AlphaBIOS (also known as the ARC firmware on older machines) instead;
this is what Windows NT uses. It is fairly simple to replace the AlphaBIOS
@@ -54,7 +54,10 @@ Using the SRM console:
Most users will want to set this to "boot".
bootdef_dev Default boot device (or list of devices).
boot_file Name of the kernel to boot. If this variable is
- empty, "bsd" will be loaded.
+ empty, "bsd" will be loaded. Note that this
+ variable does not exist in all versions of the SRM
+ console, in which case you need to always specify a
+ kernel filename if it differs from "bsd".
boot_osflags Flags to pass to the kernel.
IMPORTANT! For multiuser boot, this needs to be
set to "a".
@@ -65,7 +68,9 @@ Using the SRM console:
prompt, with the -fi (to override boot_file) and -fl (to override
boot_osflags) options. For example,
boot -fi bsd -fl ac dka0
- will boot the "bsd" kernel with the "ac" flags on dka0.
+ will boot the "bsd" kernel with the "ac" flags on dka0. However, some
+ versions of the SRM console (mainly on DEC 3000 series) will only let
+ you specify uppercase filenames.
SRM console boot device restrictions: