diff options
| -rw-r--r-- | distrib/notes/alpha/contents | 17 | ||||
| -rw-r--r-- | distrib/notes/alpha/hardware | 28 | ||||
| -rw-r--r-- | distrib/notes/alpha/install | 74 | ||||
| -rw-r--r-- | distrib/notes/alpha/prep | 64 | ||||
| -rw-r--r-- | distrib/notes/alpha/whatis | 5 | ||||
| -rw-r--r-- | distrib/notes/alpha/xfer | 132 |
6 files changed, 169 insertions, 151 deletions
diff --git a/distrib/notes/alpha/contents b/distrib/notes/alpha/contents index 5c092854260..d6bca2ea419 100644 --- a/distrib/notes/alpha/contents +++ b/distrib/notes/alpha/contents @@ -1,13 +1,22 @@ TopPart OpenBSDfloppy - This floppy image has no support for 264-based - MACHINE computers (XP1000, DS10, DS20...). + This floppy image will boot on the following + MACHINE models: + - AlphaStation 200, 250, 255, 400 + - AlphaStation 500, 600 + - AXPpci33 based machines, including + ``Noname'', UDB, Multia + - EB164 based machines, including + PC164, 164SX and 164LX floppyB{:--:}OSrev.fs The MACHINE boot and installation floppy; see below. - This floppy image supports the 264-based MACHINE - computers, but no other models. + This floppy image will boot on the following + MACHINE models: + - Personal Workstation (Miata) + - Alpha Processor, Inc. UP1000 + - XP1000, 264DP, DS10, DS20 OpenBSDdistsets diff --git a/distrib/notes/alpha/hardware b/distrib/notes/alpha/hardware index f6864b89f03..f30afcbd597 100644 --- a/distrib/notes/alpha/hardware +++ b/distrib/notes/alpha/hardware @@ -5,8 +5,9 @@ here, please send mail to <alpha@openbsd.org> with as much information as possible. Supported hardware: - XP1000, DS10, 264DP, and other single processor EV6 machines using + XP1000, DS10, DS20, 264DP, and other single processor EV6 machines using the Tsunami chipset + (Only one processor on the DS20 will be used) Supported devices: Built-in serial and parallel ports. Built-in DEC21143 ethernet. @@ -53,23 +54,30 @@ Supported hardware: ISA IDE controller on the EB164. ISA devices that require DMA operation. Alphastation 500 and 600 - These systems should work, but we need to hear from people about - them. Supported devices: Built-in serial and parallel ports. Built-in DEC21040 ethernet. Built-in ISP SCSI. - Built-in IDE controller. PCI graphics card (TGA or VGA compatible). Most PCI devices (see below). Some ISA and EISA devices (see below). Unsupported devices: Floppy drive. Built-in audio. + ISA and EISA devices that require DMA operation. + Alphastation 200, 250, 255 and 400 + Supported devices: + Built-in serial and parallel ports. + Built-in DEC21040 ethernet. + Built-in ISP SCSI. + PCI graphics card (TGA or VGA compatible). + Most PCI devices (see below). + Some ISA devices (see below). + Unsupported devices: + Floppy drive. + Built-in audio. ISA devices that require DMA operation. AXPpci based machines (including ``Noname'', UDB, Multia) - These systems should work, but we need to hear from people about - them. Supported devices: Built-in serial and parallel ports. Built-in DEC21040 ethernet. @@ -108,7 +116,7 @@ Supported hardware: Built-in framebuffer. Other TurboChannel cards. At this time none of the following systems are supported: - DS20, API UP2000, UP2000+ (mostly because we don't have any + API UP2000, UP2000+ (mostly because we don't have any to test on.) DECpc AXP150 (2000/300) systems (EISA-bus PC-like systems) AlphaServer systems, other than models 400 and 500, which @@ -118,7 +126,7 @@ Supported hardware: based). EB64+ based systems. Samsung 164BX/UX. (No SRM) - Multiprocessor alpha systems. + Multiprocessor Alpha systems. VME Alpha systems. Supported Peripherals: @@ -342,6 +350,6 @@ Supported hardware: Console frame buffers and keyboards are only supported on systems -explicately mentioned above. On other systems, including all -TurboChannel-based machines, OpenBSD/Alpha *must* be used with a +explicitely mentioned above. On other systems, including all +TurboChannel-based machines, OpenBSD/MACHINE *must* be used with a serial console. diff --git a/distrib/notes/alpha/install b/distrib/notes/alpha/install index 901a42d880a..21601da45cf 100644 --- a/distrib/notes/alpha/install +++ b/distrib/notes/alpha/install @@ -1,41 +1,61 @@ OpenBSDInstallPrelude -OpenBSDInstallPart2 +dnl XXX document mopbooting from the SRM console. +dnl XXX check if recent SRM console still can netboot, and if so, if they +dnl XXX still use mop or a more recent protocol. +There are several ways to install OpenBSD onto a disk. The easiest way +is to boot from the OpenBSD CD-ROM. You can also use one of the OpenBSD +installation floppies, if your machine has a floppy drive. + +Booting from Floppy Disk installation media: - If you are using the floppy{:--:}OSrev.fs floppy, type "boot dva0" - and hit return when presented with the SRM console prompt. + At the SRM console prompt, enter "boot dva0" and hit return. 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 than a minute. If some action doesn't eventually happen, or the spinning cursor has stopped and nothing further has - happened, either your boot floppy is bad or you are having - hardware problems. Either you have a bad boot floppy (in - which case you should try another) or your alpha is not - currently supported by OpenBSD. - - If you are booting from the CD-ROM, type "show device" and - hit return when presented with the SRM console prompt. - You should see a list of devices; the SCSI devices will - start with "DKA". Find the SCSI device that is your CD-ROM - and enter "boot dka4 -fi OSREV/alpha/bsd", assuming that your - CD-ROM was listed as DKA4* (substitute the SCSI id of your - CD-ROM for the "4"). 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. + happened, or the machine spontaneously reboots, then either + either you have a bad boot floppy (in which case you should + try another) or your alpha is not currently supported by OpenBSD. + +Booting from CD-ROM installation media: + + At the SRM console prompt, enter "show device" and hit return + 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 + 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" + 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 + 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. + + +Installing using the Floppy or CD-ROM procedure: + +OpenBSDInstallPart2 + + Boot your machine from the installation media as described above. OpenBSDBootMsgs - While booting, 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/alpha can boot from the floppy - drive, the kernel itself lacks a floppy driver. When you reach - the prompt asking you for a shell name, just hit return. + 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" diff --git a/distrib/notes/alpha/prep b/distrib/notes/alpha/prep index 6cbdf2ed2f3..fb66f06c178 100644 --- a/distrib/notes/alpha/prep +++ b/distrib/notes/alpha/prep @@ -3,38 +3,18 @@ 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. -AXPPCI33 Motherboard notes: +AXPpci33 Motherboard specific notes: The 1994 version of the OEM guide has an incorrect pinout for the serial ports. The newer version from - ftp://ftp.digital.com/pub/Digital/axppci/design_guide.ps.Z + ftp://gatekeeper.dec.com/pub/DEC/axppci/design_guide.ps.Z has a corrected pinout (as well as more information than the 1994 edition). Note that there are two flavors of PC serial connectors. If you have the wrong kind, you won't get any output from the serial console. -Acquiring and updating firmware: - As of May, 1997, the latest firmware version available for - ftp is version 3.9. To update an alpha with an axppci33 - motherboard from ARC firmware to SRM one would ftp to - ftp.digital.com and download - /pub/DEC/Alpha/firmware/v3.9/decaxppci33/decaxppci33_v1_6.exe - then copy it to a FAT-formatted (ie: DOS) floppy with the name - FWUPDATE.EXE. Now that you have your new firmware on a floppy - you just need to insert it into your machine's floppy drive and - turn on the machine. To actually update the firmware you need to - choose the "Supplementary menu" from the ARC console and then - "Install new firmware". After fwupdate.exe is done loading from - the floppy, enter "update srm" at the prompt and hit return. - After the update is complete you may want to verify the update - (if this was not done automatically) by entering "verify srm" at - the prompt. Once this is done you can enter "exit" and cycle power - on your machine. When it reboots you should be in the SRM console. - - Note that the procedure for updating SRM firmware from an - existing version of the SRM console is different. Please see - the README files that come with the firmware update for details. - Using the SRM console: This is not intended to be an exhaustive guide on using the SRM firmware console. It should, however, give you enough @@ -66,7 +46,7 @@ Using the SRM console: On systems with no framebuffer supported, including all -TurboChannel-based machines, OpenBSD/Alpha *must* be used with a +TurboChannel-based machines, OpenBSD/MACHINE must be used with a serial console. Setting an Alpha system to use a serial console is system-specific. The procedure for most common hardware is: @@ -77,7 +57,7 @@ is system-specific. The procedure for most common hardware is: Boot the machine with the keyboard/mouse connector unplugged. - AlphaStations, AXPpci systems and most others: + Other machines running the SRM console on local display: Get to the SRM console prompt. Enter "set console serial", then enter "init" or cycle power. @@ -87,31 +67,11 @@ to use a serial console. Note that some MACHINE computers currently *require* a serial console and can't be used from a regular keyboard/display console, even though the motherboard has appropriate connectors. -The following MACHINE models fall in this category: - - TurboChannel MACHINE computers listed above - - Personal Workstation (Miata) - -If booting using the regular console aborts with ``not configured to use display -&& keyboard console'', then you need to use a serial console. If your machine -was not listed in the list above, please report this on alpha@openbsd.org. - - -Alpha-related URL's: - ftp://ftp.digital.com/pub/Digital/Alpha/ - Alpha related documents, software and firmware upgrades. - - http://www.digital.com/info/semiconductor/alpha.htm - Alpha processor and support chip information. - - http://www.brouhaha.com/~eric/computers/udb-man.ps.gz - The Multia Service manual, in postscript form. - - http://www.alphalinux.org - Alpha linux notes with a good introduction to Alpha chips/systems. +Currently, only the TurboChannel MACHINE computers (DEC 3000) require use +of a serial console. - http://www.redhat.com/support/mailing-lists/ - The linux axp-list mailing list is probably the best source of - alpha hardware related info, there's a searchable archive too. +If booting using the regular console aborts with ``not configured to use +display && keyboard console'', then you need to use a serial console. +If your machine was not listed in the list above, please report this on +<alpha@openbsd.org>. - http://www.netbsd.org/Ports/alpha/ - Pointers to documentation and supported systems. diff --git a/distrib/notes/alpha/whatis b/distrib/notes/alpha/whatis index b92fbaacf86..9377df1807e 100644 --- a/distrib/notes/alpha/whatis +++ b/distrib/notes/alpha/whatis @@ -1,6 +1,3 @@ -OpenBSD/alpha OSREV is a port to Alpha processor-based machines, +OpenBSD/MACHINE OSREV is a port to Alpha processor-based machines, such as some workstations manufactured by Digital (now Compaq), as well as OEM motherboards designed by Alpha Processor, Inc. - -This port is undergoing a lot of changes to improve stability and -hardware coverage, although this release should be pretty usable. diff --git a/distrib/notes/alpha/xfer b/distrib/notes/alpha/xfer index 244ca1a94ad..47dfebfdee1 100644 --- a/distrib/notes/alpha/xfer +++ b/distrib/notes/alpha/xfer @@ -9,74 +9,97 @@ Installation is supported from several media types, including: If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive) you can boot from it. Otherwise, you will need to create a bootable -disk. This may be a floppy or a hard disk (floppy is simplest). - -To boot from CD-ROM: - - At the SRM console 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). 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 - cdrom is listed as DKA600, you want to use dka6 (device - ID's are case insensitive). Insert the OpenBSD/alpha CD - and enter "boot -fi OSREV/alpha/bsd.rd DEVICE" where DEVICE is - the dka device. Note that the argument order is important - here. If this does not work, you'll have to create a boot - floppy or bootable hard disk; follow the directions below. - (A boot floppy image is included on the CD-ROM as - OSREV/{:--:}MACHINE/floppy{:--:}OSrev.fs.) - -If you have a floppy drive on your alpha: - - If you are using a UN*X-like system to write the floppy - image to disk, you should use the "dd" command to copy the - file system image (floppy{:--:}OSrev.fs) directly to the raw floppy - disk. It is suggested that you read the dd(1) manual page - or ask your system administrator to determine the correct - set of arguments to use; it will be slightly different from - system to system, and a comprehensive list of the possibilities - is beyond the scope of this document. - - If you are using a DOS PC to write the floppy image to - disk, you should use the "rawrite" utility, provided in - the "OSREV/tools" directory of the OpenBSD distribution. It - will write the file system image (floppy{:--:}OSrev.fs) to a disk. - You can boot it using "boot dva0". - - If you are using a NT to write the floppy image to - disk, you should use the "ntrw" utility, provided in - the "OSREV/tools" directory of the OpenBSD distribution, instead. - - Note that, when installing, the floppy can be write-protected (i.e. - read-only). - -If you don't have a floppy drive on your alpha: +floppy disk. + + +Creating a bootable floppy disk using DOS/Windows: + + First you need to get access to the OpenBSD Bootable floppy + images. If you can access the CD-ROM distribution under DOS + the bootable disks are in the OSREV/MACHINE directory, otherwise + you you will have to download them from one of the OpenBSD + ftp or http mirror sites, using ftp or a web-viewer. In either + case, take care to do "binary" transfers, since these are + images files and any DOS cr/lf translations or control/z EOF + interpretations will result in corrupted transfers. + + You will also need to go to the "tools" directory and grab a + copy of the rawrite.exe utility and its documentation. This + program is needed to correctly copy the bootable filesystem + image to the floppy, since it's an image of a unix partition + containing a ffs filesystem, not a MSDOS format diskette. + + Once you have installed rawrite.exe, just run it and specify the + name of the bootable image, such as "floppy.fs" and the name of + the floppy drive, such as "a:". Be sure to use good quality HD + (1.44MB) floppies, formatted on the system you're using. The + image copy and boot process is not especially tolerant of read + errors. + + Note that if you are using NT to write the images to disk, you + will need to use ntrw.exe instead. It is also available in the + "tools" directory. Grab it and run in with the correct + arguments like this "ntrw <image> <drive>:" + + Note that, when installing, the boot floppy can be write-protected + (i.e. read-only). + + +Creating a bootable floppy disk using SunOS or other Un*x-like system: + + First, you will need obtain a local copy of the bootable filesystem + image as described above. If possible use cksum or md5 to verify + the checksums of the images vs. the values in the CKSUM or MD5 + files on the mirror site. + + Next, use the dd(1) utility to copy the file to the floppy drive. + Under SunOS, the command would be: + + dd if=floppy{:--:}OSrev.fs of=/dev/rfd0c bs=36b + + If you are using something other than SunOS, you may have to adapt + this to conform to local naming conventions for the floppy and + options suitable for copying to a "raw" floppy image. The key + issue is that the device name used for the floppy *must* be one + that refers to the whole 2880 block image, not a partition or + compatibility mode, and the copy command needs to be compatible + with the requirement that writes to a raw device must be in + multiples of 512-byte blocks. The variations are endless and + beyond the scope of this document. + + If you're doing this on the system you intend to boot the floppy on, + copying the floppy back to a file and doing a compare or checksum + is a good way to verify that the floppy is readable and free of + read/write errors. + + +If you neither have a floppy drive nor a CD-ROM drive on your alpha: If you don't have a floppy drive you can copy the floppy image onto the hard disk you intend to install OpenBSD on. Doing so will overwrite the disk's old contents, however. You must use a UN*X-like system to write the floppy image - to the hard disk you will be using for OpenBSD/alpha. You + to the hard disk you will be using for OpenBSD/MACHINE. You should use the "dd" command to copy the file system image - (floppy{:--:}OSrev.fs) directly to the raw 'c' device (whole disk) of - the target hard disk. It is suggested that you read the - dd(1) manual page or ask your system administrator to - determine the correct set of arguments to use; it will be - slightly different from system to system, and a comprehensive - list of the possibilities is beyond the scope of this - document. + (floppy{:--:}OSrev.fs or floppyB{:--:}OSrev.fs) directly to the raw 'c' + device (whole disk) of the target hard disk. It is suggested + that you read the dd(1) manual page or ask your system + administrator to determine the correct set of arguments to use; + it will be slightly different from system to system, and a + comprehensive list of the possibilities is beyond the scope of + this document. Please note that this will put a floppy disklabel on your disk which will confuse the install script. To fix this - you need to answer "n" to the first question when booting - your disk and do "dd if=/dev/zero of=/dev/rsd0c count=20" - assuming your booted from sd0. After doing this you will + you need to ask for a shell (answer "s" to the first question) + when booting your disk and do "dd if=/dev/zero of=/dev/rsd0c + count=20" assuming your booted from sd0. After doing this you will not be able to boot that disk again unless you complete the install. You can now enter "install" and start the actual install process. + The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. Some methods require a bit of setup first that is explained below. @@ -116,6 +139,7 @@ following: an existing installation, go directly to the section on upgrading. + To install OpenBSD using a remote partition, mounted via NFS, you must do the following: |