diff options
| -rw-r--r-- | distrib/notes/alpha/install | 39 | ||||
| -rw-r--r-- | distrib/notes/alpha/prep | 48 | ||||
| -rw-r--r-- | distrib/notes/alpha/upgrade | 11 | ||||
| -rw-r--r-- | distrib/notes/alpha/xfer | 9 |
4 files changed, 61 insertions, 46 deletions
diff --git a/distrib/notes/alpha/install b/distrib/notes/alpha/install index ad282eb6871..6b4da58f568 100644 --- a/distrib/notes/alpha/install +++ b/distrib/notes/alpha/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.18 2002/03/30 22:52:57 miod Exp $ +dnl $OpenBSD: install,v 1.19 2002/04/07 22:13:01 miod Exp $ OpenBSDInstallPrelude dnl XXX document mopbooting from the SRM console. @@ -10,7 +10,8 @@ installation floppies, if your machine has a floppy drive. Booting from Floppy Disk installation media: - At the SRM console prompt, enter "boot dva0" and hit return. + At the SRM console prompt, enter + boot dva0 You should see info about the primary and secondary boot and then the kernel should start to load. It will take a while to load the kernel from the floppy, most likely more @@ -22,16 +23,17 @@ Booting from Floppy Disk installation media: Booting from CD-ROM installation media: - At the SRM console prompt, enter "show device" and hit return + At the SRM console prompt, enter + show device to find the device ID of your CD-ROM drive (the device ID is - in the second column and should start with DKA for a SCSI - CD-ROM drive). If your drive shows up with a drive number - with trailing zeros, you will want to ignore them (unless - it is DKA0). For example, if your CD-ROM drive is listed + usually in the second column (``bootdev'') and should start + with DKA for a SCSI CD-ROM drive). If your drive shows up with + a drive number with trailing zeros, you will want to ignore them + (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 - "boot -fi OSREV/MACHINE/bsd.rd DEVICE" + boot -fi OSREV/MACHINE/bsd.rd DEVICE where DEVICE is the dka device name. Note that the argument order is important here. You should see info about the primary and secondary boot @@ -50,32 +52,19 @@ OpenBSDInstallPart2 OpenBSDBootMsgs - If you boot from a floppy, you will probably see several - warnings. You should be warned that the kernel can't figure - out what device it booted from and that no swap space is - present. Do not be alarmed, these are completely normal. - The first warning occurs because while OpenBSD/MACHINE can - boot from the floppy drive, the kernel itself lacks a floppy - driver. - You will next be asked for your terminal type. If you are - installing from a non-serial console, the default of "sun" + installing from a non-serial console, the default of "vt220" is correct. If you are installing from a serial console you should choose the terminal type from amongst those listed. - (If your terminal type is xterm, just use vt100). + (If your terminal type is xterm, just use vt220). + OpenBSDInstallPart3({:- or "wd0" for IDE drives-:}) OpenBSDInstallPart4 OpenBSDInstallPart5(sd0) -OpenBSDInstallNet(linkflags)dnl - The flags usually carry the following - meaning: - - -link0 -link1 Use BNC (coaxial) port [default] - link0 -link1 Use AUI port - link0 link1 Use UTP (twisted pair) port +OpenBSDInstallNet OpenBSDInstallNet2({:-CD-ROM, -:},nofloppy) diff --git a/distrib/notes/alpha/prep b/distrib/notes/alpha/prep index 71e58d8437f..abe30959675 100644 --- a/distrib/notes/alpha/prep +++ b/distrib/notes/alpha/prep @@ -1,11 +1,31 @@ -dnl $OpenBSD: prep,v 1.12 2002/04/01 00:50:20 miod Exp $ +dnl $OpenBSD: prep,v 1.13 2002/04/07 22:13:01 miod Exp $ OpenBSD/MACHINE requires the SRM console. Some alphas come with -the ARC firmware instead (this is what Windows NT uses). It is -fairly simple to replace the ARC firmware with the SRM version. -You can get replacement firmware either from a firmware update -CD or via ftp from ftp://ftp.digital.com/pub/DEC/Alpha/firmware/. -Please refer to http://ftp.digital.com/pub/DEC/Alpha/firmware/readme.html -for more information. +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 +with the SRM firmware. + +Switching your MACHINE to SRM console: + Recent machines (such as the Miata and later models) have enough flash + rom space to carry both the AlphaBIOS and the SRM console. + To switch to SRM from AlphaBIOS, do the following: + - enter the AlphaBIOS setup upon startup + (F2 key, or ^B from serial console) + - choose "CMOS Setup" from the menu + - select "Advanced CMOS Setup" (F6 key, or ^F from serial console) + - change the "Console Selection" setting to "OpenVMS console (SRM)" + - confirm your changes with F10 (or ^U) twice, then enter. + - power-cycle your system for the changes to take effect. + + If you didn't find a "Console Selection" entry (for example on 164SX or + 164LX), your system can not hold both the AlphaBIOS and SRM console in + flash, and you will have to upgrade your firmware. + + You can get replacement firmware either from a firmware update CD or via + ftp from + ftp://ftp.digital.com/pub/DEC/Alpha/firmware/ + Please refer to + http://ftp.digital.com/pub/DEC/Alpha/firmware/readme.html + for more information. AXPpci33 Motherboard specific notes: The 1994 version of the OEM guide has an incorrect pinout @@ -37,15 +57,15 @@ Using the SRM console: empty, "bsd" will be loaded. boot_osflags Flags to pass to the kernel. IMPORTANT! For multiuser boot, this needs to be - set to "-a". - booted_osflags Don't try to set this one directly. It will - contain whatever flags the OS was last booted - with. - To set it indirectly, boot with the -flags - option; for example "b dka0 -flags a" will boot - multiuser from dka0 and set booted_osflags to "a". + set to "a". To see a list of all variables on your machine use the "show" command with no arguments. + + You can bypass the boot_file and boot_osflags values from the command + 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. dnl Change back when TC support is back diff --git a/distrib/notes/alpha/upgrade b/distrib/notes/alpha/upgrade index 5c8355ce7c8..0ab908b63f4 100644 --- a/distrib/notes/alpha/upgrade +++ b/distrib/notes/alpha/upgrade @@ -1,4 +1,7 @@ -Be warned that upgrades may not be well supported currently for the -MACHINE port. - -OpenBSDUpgrade({:- the CD-ROM or an installation floppy-:}) +dnl $OpenBSD: upgrade,v 1.6 2002/04/07 22:13:01 miod Exp $ +dnl uncomment once upgrade is available +dnl OpenBSDUpgrade({:- the CD-ROM or an installation floppy-:}) +Currently, upgrades to OpenBSD OSREV are not available from the installation +media. +You can however perform an upgrade manually, by entering a shell after +booting the installation media, and performing the necessary steps by hand. diff --git a/distrib/notes/alpha/xfer b/distrib/notes/alpha/xfer index 6dd55977d88..bfc07027b4f 100644 --- a/distrib/notes/alpha/xfer +++ b/distrib/notes/alpha/xfer @@ -1,7 +1,9 @@ +dnl $OpenBSD: xfer,v 1.23 2002/04/07 22:13:01 miod Exp $ Installation is supported from several media types, including: CD-ROM (NOT supported if booting from floppy) - FFS partitions +dnl uncomment once upgrade are available +dnl FFS partitions Tape FTP HTTP @@ -46,5 +48,6 @@ OpenBSDXferShortPrelude OpenBSDXferBareTape(xbase xfont xserv xshare) - -OpenBSDXferFFS +dnl uncomment once upgrade are available +dnl +dnl OpenBSDXferFFS |