INSTALLATION NOTES for OpenBSD/alpha 5.0 What is OpenBSD? ---------------- OpenBSD is a fully functional, multi-platform UN*X-like Operating System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite. There are several operating systems in this family, but OpenBSD differentiates itself by putting security and correctness first. The OpenBSD team strives to achieve what is called a 'secure by default' status. This means that an OpenBSD user should feel safe that their newly installed machine will not be compromised. This 'secure by default' goal is achieved by taking a proactive stance on security. Since security flaws are essentially mistakes in design or implement- ation, the OpenBSD team puts as much importance on finding and fixing existing design flaws and implementation bugs as it does writing new code. This means that an OpenBSD system will not only be more secure, but it will be more stable. The source code for all critical system components has been checked for remote-access, local-access, denial- of-service, data destruction, and information-gathering problems. In addition to bug fixing, OpenBSD has integrated strong cryptography into the base system. A fully functional IPsec implementation is provided as well as support for common protocols such as SSL and SSH. Network filtering and monitoring tools such as packet filtering, NAT, and bridging are also standard, as well as several routing services, such as BGP and OSPF. For high performance demands, support for hardware cryptography has also been added to the base system. Because security is often seen as a tradeoff with usability, OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it. Because OpenBSD is from Canada, the export of Cryptography pieces (such as OpenSSH, IPsec, and Kerberos) to the world is not restricted. (NOTE: OpenBSD can not be re-exported from the US once it has entered the US. Because of this, take care NOT to get the distribution from an FTP server in the US if you are outside of Canada and the US.) A comprehensive list of the improvements brought by the 5.0 release is available on the web at http://www.OpenBSD.org/50.html. OpenBSD/alpha runs on a broad range of Alpha processor-based machines, including workstations manufactured by Digital (then Compaq, now HP), as well as OEM motherboards designed by Samsung and Alpha Processor, Inc. Sources of OpenBSD: ------------------- This is a list of currently known FTP and HTTP servers at the time of the 5.0 release. For a more recent list, please refer to http://www.OpenBSD.org/ftp.html Argentina: http://openbsd.org.ar/pub/OpenBSD (Buenos Aires) ftp://ftp.openbsd.org.ar/pub/OpenBSD (Buenos Aires) Australia: http://mirror.internode.on.net/pub/OpenBSD (Adelaide) ftp://mirror.internode.on.net/pub/OpenBSD (Adelaide) http://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane) ftp://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane) Austria: http://ftp5.eu.openbsd.org/ftp/pub/OpenBSD (Vienna) ftp://ftp5.eu.openbsd.org/pub/OpenBSD (Vienna) http://ftp.wu-wien.ac.at/pub/OpenBSD (Vienna) Bulgaria: http://mirror.telepoint.bg/OpenBSD (Sofia) ftp://mirror.telepoint.bg/OpenBSD (Sofia) Canada: http://ftp.OpenBSD.org/pub/OpenBSD (Alberta) ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta) Costa Rica: http://mirrors.ucr.ac.cr/OpenBSD ftp://mirrors.ucr.ac.cr/OpenBSD Denmark: http://ftp.openbsd.dk/pub/OpenBSD (Aalborg) ftp://ftp.openbsd.dk/pub/OpenBSD (Aalborg) Estonia: http://ftp.aso.ee/pub/OpenBSD (Tallinn) ftp://ftp.aso.ee/pub/OpenBSD (Tallinn) http://ftp.estpak.ee/pub/OpenBSD (Tallinn) ftp://ftp.estpak.ee/pub/OpenBSD (Tallinn) France: http://ftp.fr.openbsd.org/pub/OpenBSD (Paris) ftp://ftp.fr.openbsd.org/pub/OpenBSD (Paris) http://ftp.arcane-networks.fr/pub/OpenBSD (Paris) ftp://ftp.arcane-networks.fr/pub/OpenBSD (Paris) ftp://ftp.irisa.fr/pub/OpenBSD (Rennes) http://ftp2.fr.openbsd.org/pub/OpenBSD (Paris) ftp://ftp2.fr.openbsd.org/pub/OpenBSD (Paris) http://ftp.crans.org/pub/OpenBSD (Paris) Germany: http://openbsd.cs.fau.de/pub/OpenBSD (Erlangen) ftp://openbsd.cs.fau.de/pub/OpenBSD (Erlangen) http://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen) http://ftp.bytemine.net/pub/OpenBSD (Oldenburg) ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg) http://ftp.halifax.rwth-aachen.de/openbsd (Aachen) ftp://ftp.halifax.rwth-aachen.de/pub/OpenBSD (Aachen) Greece: http://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) ftp://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) Hungary: http://ftp.fsn.hu/pub/OpenBSD (Budapest) ftp://ftp.fsn.hu/pub/OpenBSD (Budapest) Ireland: http://ftp.heanet.ie/pub/OpenBSD (Dublin) ftp://ftp.heanet.ie/pub/OpenBSD (Dublin) Japan: http://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) http://www.ftp.ne.jp/OpenBSD (Saitama) ftp://ftp.kddilabs.jp/OpenBSD (Saitama) Korea: http://ftp.kaist.ac.kr/pub/OpenBSD (Daejeon) ftp://ftp.kaist.ac.kr/pub/OpenBSD (Daejeon) http://mirror.yongbok.net/OpenBSD (Seoul) ftp://mirror.yongbok.net/pub/OpenBSD (Seoul) The Netherlands: http://ftp.nluug.nl/pub/OpenBSD (Utrecht) ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht) http://ftp.bit.nl/pub/OpenBSD (Ede) ftp://ftp.bit.nl/pub/OpenBSD (Ede) http://ftp.z74.net/pub/OpenBSD (Amersfoort) ftp://ftp.z74.net/pub/OpenBSD (Amersfoort) Poland: http://piotrkosoft.net/pub/OpenBSD (Oswiecim) ftp://ftp.piotrkosoft.net/pub/OpenBSD (Oswiecim) Russia: http://mirror.corbina.net/pub/OpenBSD (Moscow) ftp://mirror.corbina.net/pub/OpenBSD (Moscow) Saudi Arabia: http://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh) ftp://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh) Slovenia: http://www.obsd.si/pub/OpenBSD (Ljubljana) ftp://ftp.obsd.si/pub/OpenBSD (Ljubljana) South Africa: http://mirror.is.co.za/mirror/ftp.openbsd.org (Johannesburg) ftp://ftp.is.co.za/mirror/ftp.openbsd.org (Johannesburg) Spain: http://ftp.udc.es/OpenBSD (A Coruna) ftp://ftp.udc.es/pub/OpenBSD (A Coruna) http://mirror.cdmon.com/pub/OpenBSD (Barcelona) ftp://mirror.cdmon.com/pub/OpenBSD (Barcelona) Sweden: http://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm) ftp://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm) http://ftp.netbsd.se/OpenBSD (Stockholm) Switzerland: http://mirror.switch.ch/ftp/pub/OpenBSD (Zurich) ftp://mirror.switch.ch/pub/OpenBSD (Zurich) http://ftp.ch.openbsd.org/pub/OpenBSD (Zurich) ftp://ftp.ch.openbsd.org/pub/OpenBSD (Zurich) Turkey: http://ftpopenbsd.ulak.net.tr ftp://ftp.ulak.net.tr/OpenBSD United Kingdom: http://www.mirrorservice.org/pub/OpenBSD (Kent) ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent) http://mirror.bytemark.co.uk/pub/OpenBSD (Manchester) ftp://mirror.bytemark.co.uk/pub/OpenBSD (Manchester) http://ftp.plig.net/pub/OpenBSD (London) ftp://ftp.plig.net/pub/OpenBSD (London) USA: http://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) http://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) http://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL) ftp://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL) http://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) ftp://mirrors.24-7-solutions.net/pub/OpenBSD (New York, NY) http://obsd.cec.mtu.edu/pub/OpenBSD (Houghton, Michigan) ftp://obsd.cec.mtu.edu/pub/OpenBSD (Houghton, Michigan) http://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY) ftp://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY) http://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY) ftp://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY) http://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois) ftp://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois) http://openbsd.mirrors.hoobly.com (Pittsburgh, PA) http://mirror.ece.vt.edu/pub/OpenBSD (Blacksburg, VA) http://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO) ftp://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO) Additionally, the file ftp://ftp.OpenBSD.org/pub/OpenBSD/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact . OpenBSD 5.0 Release Contents: ----------------------------- The OpenBSD 5.0 release is organized in the following way. In the .../5.0 directory, for each of the architectures having an OpenBSD 5.0 binary distribution, there is a sub-directory. The alpha-specific portion of the OpenBSD 5.0 release is found in the "alpha" subdirectory of the distribution. That subdirectory is laid out as follows: .../5.0/alpha/ INSTALL.alpha Installation notes; this file. SHA256 Output of the sum(1) program using the option -a sha256, usable for verification of the correctness of downloaded files. floppy50.fs The standard alpha boot and installation floppy; see below. This floppy image will boot on the following alpha models: - AlphaStation 200, 250, 255, 400 - AlphaServer 300 and 400 - AlphaStation 500, 600 - AlphaStation 600A, 1200 - AlphaServer 800, 1000, 1000A, 1200, 4000 and 4100 - AXPpci33 based machines, including ``Noname'', UDB, Multia - EB164 based machines, including PC164, 164SX, and 164LX - Personal Workstation (Miata) floppyB50.fs Another alpha boot and installation floppy; see below. This floppy image will boot on the following alpha models: - Alpha Processor, Inc. UP1000, UP1100, UP2000 and UP2000+ - XP900, XP1000, CS20, DS10, DS20, DS20L, ES40 and 264DP *.tgz alpha binary distribution sets; see below. bsd A stock GENERIC alpha kernel which will be installed on your system during the install. bsd.rd A compressed RAMDISK kernel; the embedded filesystem contains the installation tools. Used for simple installation from a pre-existing system. install50.iso The alpha boot and installation CD-ROM image, which contains the base and X sets, so that install or upgrade can be done without network connectivity. cd50.iso A miniroot filesystem image suitable to be used as a bootable CD-ROM image, but will require the base and X sets be found via another media or network; otherwise similar to the bsd.rd image above. Bootable installation/upgrade floppy images: The two floppy images can be copied to a floppy using rawrite.exe, ntrw.exe, or `dd', as described later in this document. Each floppy image is a bootable install floppy which can be used both to install and to upgrade OpenBSD to the current version. It is also useful for maintenance and disaster recovery. The OpenBSD/alpha binary distribution sets contain the binaries which comprise the OpenBSD 5.0 release for alpha systems. There are ten binary distribution sets. The binary distribution sets can be found in the "alpha" subdirectory of the OpenBSD 5.0 distribution tree, and are as follows: base50 The OpenBSD/alpha 5.0 base binary distribution. You MUST install this distribution set. It contains the base OpenBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. [ 61.3 MB gzipped, 199.0 MB uncompressed ] comp50 The OpenBSD/alpha Compiler tools. All of the tools relating to C, C++ and Objective-C are supported. This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 110.8 MB gzipped, 372.8 MB uncompressed ] etc50 This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand; see the section named Upgrading a previously-installed OpenBSD System" below.) [ 512.5 KB gzipped, 1.5 MB uncompressed ] game50 This set includes the games and their manual pages. [ 2.7 MB gzipped, 6.2 MB uncompressed ] man50 This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. [ 9.0 MB gzipped, 34.9 MB uncompressed ] xbase50 This set includes the base X distribution. This includes programs, headers and libraries. [ 17.6 MB gzipped, 61.2 MB uncompressed ] xetc50 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc50 for X. [ 72.9 KB gzipped, 275.8 KB uncompressed ] xfont50 This set includes all of the X fonts. [ 37.5 MB gzipped, 48.5 MB uncompressed ] xserv50 This set includes all of the X servers. [ 4.5 MB gzipped, 12.3 MB uncompressed ] xshare50 This set includes all text files equivalent between all architectures. [ 3.2 MB gzipped, 17.5 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/alpha 5.0 is expected to run on the following hardware. If you have hardware that is listed here and are unable to run OpenBSD, or if you are able to run OpenBSD on hardware not listed here, please send mail to with as much information as possible. Supported hardware: DS15, DS15A, DS25, ES45, TS15 and TS202C Supported devices: Built-in serial and parallel ports. Built-in Ethernet. Built-in SCSI. Built-in IDE controller. Most PCI devices (see below). Unsupported devices: Floppy drive. XP900, XP1000, CS20, DS10, DS20, DS20L, ES40, 264DP, and other EV6 machines using the Tsunami chipset (only one processor on multiprocessor models will be used) Supported devices: Built-in serial and parallel ports. Built-in DEC21143 Ethernet. Built-in ISP SCSI. Built-in IDE controller. Built-in USB should work, but has not been thoroughly tested. Most PCI devices (see below). Some ISA devices (see below). Unsupported devices: Floppy drive. ISA devices that require DMA operation. API UP1000, UP1100, UP2000, and UP2000+ and other EV6 machines using the Irongate chipset Supported devices: Built-in serial and parallel ports. Built-in DEC21040 Ethernet. Built-in IDE controller works, though there may be stability issues. Unsupported devices: Floppy drive. ISA devices that require DMA operation. Digital Personal Workstation (Miata) Supported devices: Built-in serial and parallel ports. Built-in DEC21043 Ethernet. Built-in ISP SCSI, when present (i.e. on ``au'' models). Built-in IDE controller. Most PCI devices (see below). Some ISA devices (see below). Unsupported devices: Floppy drive. Built-in audio. ISA devices that require DMA operation. EB164 based machines (including PC164, 164SX, 164LX, but NOT the 164UX) Supported devices: Built-in serial and parallel ports. Built-in PCIIDE controller, when present. PCI graphics card (TGA or VGA compatible). Most PCI devices (see below). Some ISA devices (see below). Unsupported devices: Floppy drive. ISA IDE controller on the EB164. ISA devices that require DMA operation. AlphaStation 600A and 1200 AlphaServer 800 (also known as Digital Server 3300 and 3305), 1000, 1000A AlphaServer 1200, 4000 and 4100 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 and EISA devices (see below). Unsupported devices: Floppy drive. Built-in audio. ISA and EISA devices that require DMA operation. AlphaServer 300 and 400, and 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. AlphaStation 500 and 600 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 and EISA devices (see below). Unsupported devices: Floppy drive. Built-in audio. ISA and EISA devices that require DMA operation. AXPpci based machines (including ``Noname'', UDB, Multia) Supported devices: Built-in serial and parallel ports. Built-in DEC21040 Ethernet. Built-in 53C810 SCSI (siop). Built-in IDE controller. (will not boot from IDE, though) PCI graphics card (TGA or VGA compatible). Most PCI devices (see below). Some ISA devices (see below). Unsupported devices: Floppy drive. ISA devices that require DMA operation. DEC 3000 models 300{,L,X,LX} Supported devices: Built-in serial ports. Built-in LANCE Ethernet. Built-in SCSI (53C94). TURBOchannel LANCE Ethernet cards (PMAD-A). TURBOchannel SCSI (53C94) (PMAZ-A). TURBOchannel DEFTA FDDI cards (PMAF-FA). Unsupported devices: Built-in ISDN/audio chip. Built-in framebuffer. Other TURBOchannel cards. DEC 3000 models 400,500,500X,600,700,800,900 Supported devices: Built-in serial ports. Built-in LANCE Ethernet. Built-in SCSI (53C94 or 53CF94-2). TURBOchannel LANCE Ethernet cards (PMAD-A). TURBOchannel SCSI (53C94) (PMAZ-A). TURBOchannel DEFTA FDDI cards (PMAF-FA). Unsupported devices: Built-in ISDN/audio chip. Built-in framebuffer (when applicable). Other TURBOchannel cards. At this time none of the following systems are supported: DECpc AXP150 (2000/300) ``Jensen'' systems (EISA-bus PC-like systems) AlphaServer 2000, 2100 and 2100A AlphaServer 8200, 8400, GS60 and GS140 AlphaServer ES47, ES80 and GS1280 AlphaServer GS80, GS160 and GS320 Alpha XL systems (no SRM) DEC 4000, 7000, and 10000 systems (FutureBus+ and XMIBus-based) EB64+ based systems Samsung 164BX and 164UX (no SRM) VME Alpha systems (AXPvme, ALPHAvme) Tadpole ALPHAbook Multiprocessor Alpha systems (though they will run fine using one processor only, if the model is listed as supported above) Supported Peripherals: PCI IDE Controllers (pciide) Acer Labs M5229 CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, and PCI0649 Contaq Microsystems/Cypress CY82C693 Any other PCI IDE-compliant controller should work, but are untested at this point SCSI Host Adapters Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880, AIC-7890, AIC-7891, AIC-7892, AIC-7895, AIC-7896, AIC-7897 and AIC-7899 based host adapters (ahc) [*] including the Adaptec cards AHA-274X[W,T] AHA-284X AHA-2910, AHA-2915 AHA-2920 AHA-2930[C,U2] AHA-2940[J,N,U,AU,UW,UW Dual,UW Pro,U2W,U2B] AHA-2950[U2W,U2B] AHA-3940[U,AU,UW,AUW,U2W] AHA-3950U2 AHA-3960 AHA-3985 AHA-4944UW AHA-19160B AHA-29160[B,N] AHA-39160 AdvanSys ABP940UW, ASB3940UW-00, ASB3940U2W-00 and ASB3950U160 PCI SCSI controllers. (adw) QLogic PCI SCSI controllers (isp) Symbios Logic (NCR) 53C8xx, 53C1010 and 53C1510D-based PCI SCSI host adapters (including generic/no name cards, old ASUS cards, the DTC-3130 series, Diamond Fireport series, etc.) (siop) AMD Am53c974 PCscsi-PCI host adapters including the Tekram DC-390 (pcscp) [*] RAID and Cache Controllers [*] 3ware Escalade 3W-5x00, 3W-6x00, 3W-7x00 DPT SmartCache and SmartRaid III/IV PCI/EISA adapters (dpt) ICP-Vortex GDT 6xxxR[DNPS] series (gdt) CD-ROM and DVD-ROM Drives [*] Most SCSI CD-ROM, CD-R, CD-RW, and DVD drives Most ATAPI CD-ROM, CD-R, CD-RW, and DVD drives Tape Drives [*] Most SCSI tape drives Most SCSI tape changers Serial Ports 8250/16450-based ports 16550-based ports Cyclades PCI Cyclom-{4, 8, 16}Y serial boards (cy) ST16660-base ports Ethernet Adapters 3Com 3c503 (ec) [*] 3Com 3c509, 3c579, and 3c59x (ep) [*] (disabling PnP on 3c509B is recommended) 3Com 3c9xx EtherLink XL adapters (xl), including: [*] 3Com 3c900/3c900B PCI adapters 3Com 3c905/3c905B/3c905C PCI adapters 3Com 3c980/3c980C server adapters 3Com 3cSOHO adapter 3Com 3c900B-FL and 3c900B-FL/FX fiber optic adapters 3Com 3c990 3XP Typhoon/Sidewinder PCI adapters (txp), including: [-] 3CR990-TX-95 3CR990-TX-97 3CR990-TX-SVR95 3CR990-TX-SVR97 Adaptec "Starfire" AIC-6915 based PCI adapters (sf), including: [*] Adaptec Single32 ANA-69011 Adaptec Single64 ANA-62011 and ANA-62020 Adaptec Duo64 ANA-62022 Adaptec Quartet64 ANA-62044 ADMtek AL981 ("Comet") and AN983 ("Centaur-P") based PCI adapters (dc), including: [*] Accton EN2242 MiniPCI Linksys LNE100TX v4.x Mototech ME316 ADMtek AN986-based USB adapters (aue), including: [*] Abocom UFE1000 Abocom DSB650TX Accton USB320-EC Accton SpeedStream Ethernet Admtek Pegasus, Pegasus II Billionton Systems USB100 Corega FEther USB-TX D-Link DSB-650, 650TX, 650TX-PNA Elecom LD-USB Elsa Microlink USB2Ethernet I/O Data USB ETTX Kingston KNU101TX Linksys USB100TX, USB100H1 and USB10TA Melco Inc. LUA-TX Siemens SpeedStream USB SmartBridges smartNIC 2 SMC 2202USB/ETH SMC 2206USB/ETH SOHOware NUB100 AMD PCnet-based PCI adapters (pcn), including: [*] BOCALANcard/PCI AT&T StarLAN 10, EN100, and StarLAN Fiber ASIX 88140A/88141-based PCI adapters (dc), including: [*] CNet Pro110B Alfa Inc. GFC2204 ASIX AX88172/AX88178/AX88772 USB Ethernet adapters (axe), including: [*] ATEN UC210T BAFO BF-320 Billionton Systems USB2AR Buffalo(MELCO) LUA-U2-KTX Corega FEther USB2-TX D-Link DUB-E100 Good Way GWUSB2E Hawking UF200 Intellinet USB 2.0 to Ethernet (rev A) IO-Data ETG-US2 JVC MP-PRX1 Level One USB-0200 Linksys USB200M Netgear FA120 Nintendo Wii USB Lan Ethernet Adapter RVL-015 OQO model 01+ Ethernet Sitecom LN-029 SMC 2209USB/ETH SnapPort USB 2.0 LAN Adapter ST Lab USB 2.0 Fast Ethernet Surecom EP-1427X-2 System TALKS SGC-X2UL TRENDnet TU2-ET100 Z-TEK ZK-R01-2 CATC USB-EL1210A-based USB adapters (cue), including: [*] CATC Netmate and Netmate II Belkin F5U011/F5U111 Davicom DM9601 based USB adapters, including: [*] Corega FEther USB-TXC HenTong WK-668 ShanTou ST268 Davicom DM9009, DM9100, DM9102, and DM9102A based PCI adapters (dc), including: [*] Jaton XpressNet DEC EtherWORKS III adapters, including: [-] DEC DE203, DE204, DE205 Digital DC21x4x-based PCI adapters (de), including: Older SMC PCI EtherPower 10, 10/100 (models 8432, 9332, and 9334) Older Linksys 10, 10/100 (newer models are supported by other drivers) Znyx ZX3xx Cogent EM100FX and EM440TX Digital PCI DE435, EISA DE425, DE450, DE500 Asante 21140A D-Link DFE-570TX Quad port Almost all other variants work. Digital DC2114x-based four port cards, (de) including: Adaptec ANA-6944A Cogent EM400 Compex 400TX Znyx ZX346 Intel i8255x-based (except the i82556) PCI adapters (fxp), including: Intel EtherExpress PRO/10+ Intel EtherExpress PRO/100, PRO/100B, and PRO/100+ Intel EtherExpress PRO/100+ "Management Adapter" Intel EtherExpress PRO/100 Dual Port Intel PRO/100 VE, PRO/100 VM, and PRO/100 S Intel 21145-based PCI adapters (dc) Kawasaki LSI KL5KUSB101B-based USB adapters (kue), including: [*] 3Com 3C19250 3Com 3c460 HomeConnect AboCom Systems URE450 Ethernet ADS Technologies USB-10BT Aox USB101 Asante USB to Ethernet ATen DSB-650C ATen UC10T Corega USB-T D-Link DSB-650C Entegra NET-USB-E45 I/O Data USB-ET/T Jaton USB XpressNet Kawasaki USB101 Kingston Ethernet Linksys USB10T Mobility Ethernet Netgear EA101 Peracom USB Portgear Ethernet Portsmith Express Ethernet Psion Dacom Gold Port Ethernet Shark Pocket Adapter Silicom U2E SMC 2102/2104USB Lite-On PNIC/PNIC-II-based adapters (dc), including: [*] Kingston KNE110TX Linksys LNE100TX Matrox Networks FastNIC 10/100 Netgear FA310TX Macronix 98713/98715/98725-based adapters (dc), including: [*] Accton EN1217 Addtron AEF-320TX/AEF-330TX CNet PRO120A/B Complex RL-100TX NDC Communications SOHOware SFA110A SVEC PN102-TX Fast Ethernet card National Semiconductor DP83815/DP83816-based PCI adapters (sis), including: [*] Netgear FA311 Netgear FA312 Netgear FA331 Novell NE1000, NE2000 (ISA and PCI variants thereof) (ne) [*] RealTek 8129/8139-based adapters (rl), including: [*] Accton MPX 5030/5038 Allied Telesyn AT2550 D-Link DFE530TX+ D-Link DFE538TX Encore ENL832-TX-RENT 10/100 M PCI Genius GF100TXR KTX-9130TX 10/100 Fast Ethernet Longshine LCS-8038TX-R NDC NE100TX-E Netgear FA311 v2 Netronix EA-1210 Net Ether 10/100 Nortel BayStack 21 OvisLink LEF-8129TX, LEF-8139TX SMC EZ Card 10/100 PCI 1211-TX RealTek RTL8150L based USB adapters, including: [*] Abocom RTL8151 BAFO BF-310 Billionton USBKR-100 Compex UE202-B GreenHouse GH-USB100B GreenHouse GH-USB100B with HomePNA Hawking Technology HUF11 Linksys USB100M Longshine LCS-8138TX Melco Inc. LUA-KTX Micronet SP128AR NetComm NP1010 Repotec RP-USB100-A SMC 2208USB/ETH TRENDnet TU-ET100C Zt USB10/100 Z-TEK ZK-R02 SiS 900 and SiS 7016-based PCI adapters (sis), including: [*] Mototech ME313 NetSurf NS-KFE30D SMC 9432 (EtherPower II) EPIC 10/100 [*] SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards (we) [*] Sundance ST201-based PCI adapters (ste), including: [*] D-Link DFE-550TX Texas Instruments ThunderLAN PCI adapters (tl), including: [*] Compaq Netelligent PCI Adapters Compaq NetFlex 3/P Compaq Deskpro integrated adapter Compaq Prosignia integrated adapter Olicom OC2135, OC2183, OC2325, OC2326 Racore 8165 and 8148 TI ThunderLAN adapters VIA Rhine/RhineII/Rhine III Ethernet adapters (vr), including: [*] Addtron AEF-360TX Hawking PN102TX D-Link DFE530TX Winbond W89C840F-based adapters (wb), including: [*] TRENDnet TE100-PCIE Compex RL100-ATX 10/100 Please be aware that many NE2000 adapters fail or perform very poorly. We do not recommend using them, but your mileage may vary. Gigabit Ethernet Adapters Alteon Tigon I/II-based adapters (ti), including: 3Com 3c985 and 3c985B Alteon ACEnic V (fiber and copper) Digital EtherWORKS 1000SX Farallon PN9000SX Netgear GA620 and GA620T SGI Tigon Broadcom BCM570x (a.k.a. Tigon3) based PCI adapters (bge), including: [-] 3Com 3c996-T 3Com 3c996-SX 3Com 3c996B-T HP ProLiant NC7770 PCI-X Gigabit NIC Netgear GA302T SysKonnect SK-9D21 SysKonnect SK-9D41 Intel i82540, i82541, i82542, i82543, i82544, i82545, i82546, i82547, i82571, i82572 and i82573 based adapters (em), including: [*] HP ProLiant NC310F PCI-X Gigabit NIC (SX Fiber) HP ProLiant NC340T PCI-X Gigabit NIC HP ProLiant NC360T PCI Express Dual Port Gigabit NIC HP ProLiant NC6132 Upgrade Module (SX Fiber) HP ProLiant NC6133 Upgrade Module (LX Fiber) HP ProLiant NC6134 PCI Gigabit NIC (SX Fiber) HP ProLiant NC6136 PCI Gigabit NIC (SX Fiber) HP ProLiant NC6170 PCI-X Gigabit NIC (SX Fiber) HP ProLiant NC7131 PCI Gigabit NIC HP ProLiant NC7132 Upgrade Module HP ProLiant NC7170 PCI-X Dual Port Gigabit NIC HP ProLiant NC7170LP PCI-X Dual Port Gigabit NIC Intel PRO/1000 Gigabit Server Adapter (SX Fiber) (PWLA8490) Intel PRO/1000F Gigabit Server Adapter (SX Fiber) (PWLA8490SX) Intel PRO/1000T Server Adapter (PWLA8490T) Intel PRO/1000XT Server Adapter (PWLA8490XT) Intel PRO/1000XS Server Adapter (SX Fiber) (PWLA8490XF) Intel PRO/1000T Desktop Adapter (PWLA8390T) Intel PRO/1000XTL Lo Profile PCI Server (PWLA8490XTL) Intel PRO/1000MT Desktop Adapter (PWLA8390MT) Intel PRO/1000MT Server Adapter (PWLA8490MT) Intel PRO/1000MT Dual Port Server Adapter (PWLA8492MT) Intel PRO/1000MF Server Adapter (SX Fiber) (PWLA8490MF) Intel PRO/1000MF Dual Port Server Adapter (SX Fiber) (PWLA8492MF) Intel PRO/1000MF Server Adapter (LX Fiber) (PWLA8490LX) Intel PRO/1000MT Quad PCI-X Adapter (PWLA8494MT) Intel PRO/1000GT Quad PCI-X Adapter (PWLA8494GT) Intel PRO/1000PT Desktop Adapter Intel PRO/1000PT Server Adapter Intel PRO/1000PT Dual Port Server Adapter Intel PRO/1000PT Quad Port Server Adapter Intel PRO/1000PF Server Adapter (SX Fiber) Intel PRO/1000PF Dual Port Server Adapter (SX Fiber) Realtek 8169/8169S/8110S based PCI adapters, including: Buffalo LGY-PCI-GT (8169S) Corega CG-LAPCIGT (8169S) D-Link DGE-528T (8169S) Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S) LevelOne GNC-0105T (8169S) Linksys EG1032v3 (8169S) Netgear GA311 (8169S) Netgear GA511 PC Card (8169) PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S) Surecom EP-320G-TX1 (8169S) US Robotics USR997902 (8169S) Xterasys XN-152 10/100/1000 NIC (8169) Sundance/Tamarack TC9021 based PCI adapters (stge), including: [-] D-Link DGE-550T (10/100/1000baseTX) Antares Microsystems Gigabit Ethernet board SysKonnect and Marvell based adapters (sk), including: SysKonnect SK-9821 (1000baseT) SysKonnect SK-9822 (dual 1000baseT) SysKonnect SK-9841 (1000baseLX) SysKonnect SK-9842 (dual 1000baseLX) SysKonnect SK-9843 (1000baseSX) SysKonnect SK-9844 (dual 1000baseSX) SysKonnect SK-9521 v2.0 (1000baseT 32-bit) SysKonnect SK-9821 v2.0 (1000baseT) SysKonnect SK-9843 v2.0 (1000baseSX) 3Com 3c940 (1000baseT) D-Link DGE-530T (1000baseT) Linksys EG1032v2 (1000baseT) Linksys EG1064v2 (1000baseT) SMC 9452TX (1000baseT) Wireless Ethernet Adapters ADMtek ADM8211 IEEE 802.11b PCI adapters Aironet Communications 4500/4800 IEEE 802.11FH/b PCI adapters Atheros IEEE 802.11a/b/g PCI adapters Atheros USB IEEE 802.11a/b/g USB adapters Conexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g PCI adapters Marvell Libertas IEEE 802.11b/g PCI adapters Ralink Technology IEEE 802.11a/b/g PCI adapters Ralink Technology IEEE 802.11a/b/g USB adapters TI ACX100/ACX111 IEEE 802.11a/b/g PCI adapters WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b PCI adapters WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b USB adapters Communications Controllers [*] Universal Serial Bus host controllers, including: USB Universal Host Controller (uhci) USB Open Host Controller (ohci) Universal Serial Bus (USB) Devices [*] USB Audio (uaudio) [-] USB Diamond MultiMedia Rio MP3 players (urio) [-] USB Ethernet adapters (aue, cue, kue), see above USB Generic Human Interface Devices (catch-all) (uhid) USB Handspring Visor (uvisor) [-] USB Hubs (uhub) USB Keyboards (ukbd) USB Mass Storage devices, i.e., USB floppy drives and USB memory stick controllers (umass) USB Mice (umouse) [-] USB Modems (umodem) [-] USB Printers (ulpt) [-] USB Scanners (uscanner) [-] USB-USB cables (upl) [-] FDDI Adapters [*] Digital DEFEA EISA FDDI adapters (fea) Digital DEFPA PCI FDDI adapters (fpa) WAN Adapters [*] Lan Media Corporation SSI (T1)/HSSI/DS1/DS3 WAN interfaces (lmc) Cryptography Accelerators [*] Hifn 7751/7811/7951/7955/7956-based boards (hifn), including: Soekris Engineering vpn1201, vpn1211, vpn1401, and vpn1411 GTGI PowerCrypt Encryption Accelerator NetSec 7751 Hifn 7751 and 9751 reference boards Invertex AEON Sound Devices [*] C-Media CMI8[37]38 (cmpci) Ensoniq AudioPCI (eap) ESS Solo-1 PCI AudioDrive (eso) Forte Media FM801 audio (fms) S3 SonicVibes (sv) SoundBlaster PCI128 (eap) VIA VT82C686A SouthBridge integrated AC'97 audio (auvia) Radio Receiver Devices [*] Brooktree 848/849/878/879-based TV tuner ATM Adapters [*] Efficient Networks EN-155 and Adaptec ANA-590x ATM interfaces (en) Miscellaneous Devices [*] Brooktree 8[47][89] based frame grabber and TV tuner cards, including: [G] Leadtek Winfast TV 2000 Hardware monitoring sensors, including: [-] Analog Devices AD7416, AD7417 and AD7418 (adc) Analog Devices ADM1021 (admtemp) Analog Devices ADM1024 (admlc) Analog Devices ADM1025 (admtm) Analog Devices ADM1030 (admtmp) Analog Devices ADM1031 (admtt) Analog Devices ADT7460 (adt) National Semiconductor LM75, LM77 (lmtemp) National Semiconductor LM78, LM78-J, LM79 (lm) National Semiconductor LM87 (lmenv) Maxim DS1624/DS1631/DS1721 (maxds) Maxim MAX6642/MAX6690 (maxtmp) Drivers for hardware marked with "[*]" are NOT included on the installation floppies, but are available in the CD-ROM installation kernel as well as the GENERIC kernel which will be installed. Drivers for hardware marked with "[-]" are NOT available on the installation floppies, or the CD-ROM installation kernel, but are available in the GENERIC kernel which will be installed. Console frame buffers and keyboards are only supported on systems explicitly mentioned above. On other systems, including all TURBOchannel-based machines, OpenBSD/alpha *must* be used with a serial console. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM (NOT supported if booting from floppy) FFS partitions Tape FTP HTTP If you can burn the bootable CD-ROM mini image, you can boot from it. Otherwise, you will need to create a bootable 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 distribution from the CD-ROM under DOS, you will find the bootable disks in the 5.0/alpha directory. Otherwise, you will have to download them from one of the OpenBSD FTP or HTTP mirror sites, using an FTP client or a web browser. 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 an ffs filesystem, not an MSDOS format diskette. Once you have installed rawrite.exe, just run it and specify the name of the bootable image, such as "floppy50.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, 2000, or XP 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 :" Note that, when installing, the boot floppy can be write-protected (i.e. read-only). Creating a bootable floppy disk using SunOS, Solaris 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 the sha1(1) command to verify the checksums of the images vs. the values in the SHA256 file on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. The command would likely be, under SunOS: dd if=floppy50.fs of=/dev/rfd0c bs=36b and, under Solaris: dd if=floppy50.fs of=/dev/rdiskette0 bs=36b unless the volume management daemon, vold(1M), is running, in which case the following command is preferable: dd if=floppy50.fs of=/vol/dev/rdiskette0 bs=36b If you are using another operating system, 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 correct block device, 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. Note that, when installing, the boot floppy can be write-protected (i.e. read-only). 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 should use the "dd" command to copy the file system image (floppy50.fs or floppyB50.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 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 you 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. The installation allows installing OpenBSD directly from FTP mirror sites over the internet, however you must consider the speed and reliability of your internet connection for this option. It may save much time and frustration to use ftp get/reget to transfer the distribution sets to a local server or disk and perform the installation from there, rather than directly from the internet. Creating an installation tape: While you won't be able to boot OpenBSD from a tape, you can use one to provide the installation sets. To do so, you need to make a tape that contains the distribution set files, each in "tar" format or in "gzipped tar format". First you will need to transfer the distribution sets to your local system, using ftp or by mounting the CD-ROM containing the release. Then you need to make a tape containing the files. If you're making the tape on a UN*X-like system, the easiest way to do so is make a shell script along the following lines, call it "/tmp/maketape". #! /bin/sh TAPE=${TAPE:-/dev/nrst0} mt -f ${TAPE} rewind for file in base etc comp game man xbase xetc xfont xserv xshare do dd if=${file}50.tgz of=${TAPE} obs=8k conv=osync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../5.0/alpha sh -x /tmp/maketape If you're using a system other than OpenBSD or SunOS, the tape name and other requirements may change. You can override the default device name (/dev/nrst0) with the TAPE environment variable. For example, under Solaris, you would probably run: TAPE=/dev/rmt/0n sh -x /tmp/maketape Note that, when installing, the tape can be write-protected (i.e. read-only). If you are upgrading OpenBSD, you also have the option of installing OpenBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base50" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- OpenBSD/alpha 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 with the SRM firmware. Switching your alpha to SRM console: AlphaServer class machines (except for models 300 and 400) and recent enough 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 Ctrl-B from serial console) - choose "CMOS Setup" from the menu - select "Advanced CMOS Setup" (F6 key, or Ctrl-F from serial console) - change the "Console Selection" setting to "OpenVMS console (SRM)" - confirm your changes with F10 (or Ctrl-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-ROM, which can be downloaded from ftp://ftp.hp.com/pub/alphaserver/firmware/v73.zip However, this CD-ROM image only supports AlphaServer DS10, DS20, DS20L, and ES40. Firmware update for other models can be picked individually via FTP from ftp://ftp.hp.com/pub/alphaserver/firmware/retired_platforms/ Please refer to http://h18002.www1.hp.com/alphaserver/firmware/index.html for more information. Note that, on most models, upgrading the firmware requires a jumper to be moved on the motherboards; refer to the firmware update instructions for details. AXPpci33 Motherboard specific notes: The 1994 version of the OEM guide has an incorrect pinout for the serial ports. The newer version used to be available at ftp://ftp.digital.com/pub/Digital/axppci/design_guide.ps.Z with a corrected pinout (as well as more information than the 1994 edition). Although ftp.digital.com does not exist anymore, a few copies of this document are scattered accross various ftp servers on the globe, such as ftp://ftp.uniroma2.it/Digital/support/axppci/design_guide.ps.Z or http://vt100.net/mirror/mds-199909/cd1/alpha/axpcidgc.pdf 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. 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 information to boot OpenBSD/alpha. To see a list of devices connected to your alpha, you can use the "show device" command. For booting, the devices you are interested in are "dva0" (the floppy drive) and "dka*" (the disk drives). You can set ROM variables by saying "set VARIABLE VALUE". Some variables you will want to set: auto_action Determines what happens when you turn the power on, halt, or restart your machine. Valid values are: "halt" the system will not autoboot, will restart when rebooted (shutdown -r), and will not restart when halted (shutdown -h). "boot" the system will autoboot on powerup, and when the system is halted (shutdown -h) or rebooted (shutdown -r). "restart" the system will autoboot on powerup, will restart when rebooted (shutdown -r), and will not restart when halted (shutdown -h). 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. Note that this variable does not exist in all versions of the SRM console, in which case you need to always boot manually and specify a kernel filename if it differs from "bsd". boot_osflags Flags to pass to the kernel (there is no need to prefix them with a `-' dash sign). To see a list of all variables on your machine, use the "show" command with no arguments. If there are too many of them, you might want to page with "show | more". 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 c dka0 will boot the "bsd" kernel with the "c" flag on dka0. However, some versions of the SRM console (mainly on DEC 3000 series) will only let you specify uppercase filenames. USB support on the XP1000: For some unknown reason, the USB interface found on the XP1000 (and possibly the XP900 and the XP1100) is not enabled unless a specific SRM environment variable is set. If you plan to use USB devices on these machines, enter set usb_enable on at the SRM prompt, followed by init before attempting to install OpenBSD. SRM console boot device restrictions: The SRM firmware on your system may or may not be able to boot from any disk controller you may install in your alpha. The built-in disk controllers on your alpha will always be supported, however on IDE-based machines, such as the EB164, 164SX and 164LX, as well as the low-end Personal Workstation (non-u models), you can plug in a SCSI controller, and boot from it if it is recognized. Recent SRM releases for these machines will be able to boot (or netboot) from the following controllers: QLogic PCI SCSI controllers Symbios Logic (NCR) 53C8xx (but not on PC164) Adaptec AHA-[23]9[34]x[U][W] cards Intel i8255x-based cards (EtherExpress PRO) The following controllers are known not to be supported as boot devices by the SRM: Adaptec AHA-[23]9[34]xU2 cards Depending on your specific model, your mileage may vary, though. OpenBSD/alpha console device restrictions: On systems with no framebuffer supported (currently all TURBOchannel-based machines), OpenBSD/alpha must be used with a serial console. Setting an Alpha system to use a serial console is system-specific. Although most models will default to serial console if no keyboard is connected on powerup, this behaviour can't be relied upon. The recommended procedure is: DEC 3000/[4-9]00 Flip the `S3' switch on the back of the machine (up for glass console, down for serial console). When configured to use a serial console, it is also necessary to set the ``server'' SRM environment variable to ``on'' for the system to autoboot on powerup despite the lack of a keyboard and mouse plugged in. DEC 3000/300 family machines Console is selected by the `W2' jumper block, to the edge of the logic board, near the memory banks. Setting the jumper cap on pins 1-2 selects glass console, and on pins 2-3 selects serial console. All other machines From the SRM console, enter either set console serial or set console graphics at the SRM prompt, then enter init or cycle power. Installing the OpenBSD System: ------------------------------ Installing OpenBSD is a relatively complex process, but if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. There are several ways to install OpenBSD onto a disk. The easiest way is to boot from the bootable CD-ROM mini image, then install from your favorite source. You can also use one of the OpenBSD installation floppies, if your machine has a floppy drive. Network booting is supported through means of dhcpd(8) and tftpd(8). Booting from Floppy Disk installation media: 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 than a minute. If some action doesn't eventually happen, or the spinning cursor has stopped and nothing further has happened, or the machine spontaneously reboots, then 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 to find the device ID of your CD-ROM drive (the device ID is 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 IDs are case insensitive). Insert the OpenBSD/alpha CD-ROM and enter boot DEVICE where DEVICE is the dka device name. 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 if possible. Booting from Network: In order to bootstrap via the network, you must provide a second system to act as a boot server. It is convenient if this is a second OpenBSD machine as the necessary services are already installed, although source code for such programs as dhcpd can be found in OpenBSD's source tree, and should be reasonably portable to other UN*X-like operating systems. More information on diskless booting can be found in the OpenBSD diskless(8) manual page. In this case, you will need to set up dhcpd on the server, which can serve bootp protocol requests. Start by editing the /etc/dhcpd.conf on the bootserver, and declare an information block. Here is an example: subnet 10.0.0.0 netmask 255.0.0.0 { host piper { always-reply-rfc1048 "true"; filename "netboot"; option root-path "/alpha"; hardware ethernet 00:02:56:00:73:31; fixed-address 10.42.42.42; } } Do not forget to enable dhcpd. You will also need to enable tftpd, for the alpha to download the "netboot" from the server in the /tftpboot directory. Next, you need to add an entry for your alpha in /etc/bootparams. For example: piper root=myserver:/alpha Enable rpc.bootparamd either by turning it on in /etc/rc.conf and rebooting, or by running it manually. Only uncompressed kernels are supported for booting in this release. This means you have to execute the following command on your boot server before installing a new kernel for your alpha to boot: # gzip -dc bsd.rd > /alpha/bsd This assumes you have path /alpha exported via NFS. Once loaded, netboot will mount /alpha over NFS and load the kernel from there. Installing using the Floppy, CD-ROM or Network procedure: You should now be ready to install OpenBSD. The following is a walk-through of the steps you will take while getting OpenBSD installed on your hard disk. The installation procedure is designed to gather as many information about your system setup as possible at the beginning, so that no human interaction is required as soon as the questions are over. The order of these questions might be quite disconcerting if you are used to other installation procedures, including older OpenBSD versions. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. Using Control-Z to suspend the process may be a better option, or at any prompt enter `!' to get a shell, from which 'exit' will return you back to that prompt (no refresh of the prompt will occur, though). Boot your machine from the installation media as described above. It will take a while to load the miniroot image, especially from a slow network connection or a CD-ROM, 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 media is bad, your diskless setup is incorrect, or you may have a hardware or configuration problem. Once the kernel has loaded, you will be presented with the OpenBSD kernel boot messages. You will want to read them to determine your disks name and geometry. Its name will be something like "sd0" for SCSI drives, or "wd0" for IDE drives. You will also need to know the device name to tell the install tools what disk to install on. If you cannot read the messages as they scroll by, do not worry -- you can get at this information later inside the install program. After the kernel is done initialization, you will be asked whether you wish to do an "(I)nstall" or an "(U)pgrade". Enter 'I' for a fresh install or 'U' to upgrade an existing installation. If you are connected with a serial console, you will next be asked for your terminal type. You should choose the terminal type from amongst those listed. (If your terminal type is xterm, just use vt220). The first question you will be asked is the system hostname. Reply with the name of the system, without any domain part. You will now be given an opportunity to configure the network. The network configuration you enter (if any) can then be used to do the install from another system using HTTP or FTP, and will also be the configuration used by the system after the installation is complete. The install program will give you a list of network interfaces you can configure. For each network interface you select to configure, you will be asked for: - the symbolic host name to use (except for the first interface setup, which will reuse the host name entered at the beginning of the installation). - the IPv4 settings: address and netmask. If the IP address should be obtained from a DHCP server, simply enter ``dhcp'' when asked for the address. - the IPv6 settings (address, prefix length, and default router). You may enter ``rtsol'' when asked for the address for the interface to configure automatically via router solicitation messages. After all interfaces have been configured, if there have been any IPv4 interfaces setup, you will be asked for the IPv4 default route. This step is skipped if you only have one IPv4 interface setup, and it is configured with DHCP. The install program will also ask you for your DNS domain name, and the domain name servers, unless this information has already been obtained from a DHCP server during interface setup. You will also be presented with an opportunity to do more manual configuration. If you accept, you will be dropped to a shell; when you are done, enter `exit' to return to the installation program. You will then be asked to enter the initial root password of the system, twice. Although the install program will only check that the two passwords match, you should make sure to use a strong password. As a minimum, the password should be at least eight characters long and a mixture of both lower and uppercase letters, numbers and punctuation characters. You will then be asked whether you want to start sshd(8) by default, as well as ntpd(8). If you choose to start ntpd(8), you will be asked for your ntp server; if you don't have any preferred ntp server, press enter to confirm the default setting of using the pool.ntp.org servers. You will next be asked whether you intend to run the X Window System on your machine. The install program needs to know this, to change a configuration setting controlling whether the X server will be able to access the xf86(4) driver; it is not necessary to answer `y' to this question if you only intend to run X client programs on a remote display. If you are installing using a serial console, and since by default, the OpenBSD/alpha installation will only start terminals on the primary display device, the installation program will ask you whether you want to also enable an additional terminal on that line, and will allow you to select the line speed. You will now be given the possibility to setup a user account on the forthcoming system. This user will be added to the `wheel' group. Enter the desired login name, or `n' if you do not want to add a user account at this point. Valid login names are sequences of digits and lowercase letters, and must start with a lowercase letter. If the login name matches this criteria, and doesn't conflict with any of the administrative user accounts (such as `root', `daemon' or `ftp'), you will be prompted with the users descriptive name, as well as its password, twice. As for the root password earlier, the install program will only check that the two passwords match, but you should make sure to use a strong password here as well. If you have chosen to setup a user account, and you had chosen to start sshd(8) on boot, you will be given the possibility to disable sshd(8) logins as root. You may now be given the opportunity to configure the time zone your system will be using (this depends on the installation media you are using). If the installation program skips this question, do not be alarmed, the time zone will be configured at the end of the installation. The installation program will now tell you which disks it can install on, and ask you which it should use. Reply with the name of your root disk. You will the be asked if you want to use DUID notation in /etc/fstab, instead of traditional device names. You are strongly advised to use DUIDs, as they allow you to move your disks to different controllers, or change their bus identifiers, without having to modify /etc/fstab every time your configuration changes. Next the disk label which defines the layout of the OpenBSD partitions must be set up. Each file system you want will require a separate partition. You will be proposed a default partition layout, trying to set up separate partitions, disk size permitting. You will be given the possibility to either accept the proposed layout, or edit it, or create your own custom layout. These last two choices will invoke the disklabel(8) interactive editor, allowing you to create your desired layout. Within the editor, you will probably start out with only the 'c' partition of fstype 'unused' that represents the whole disk. This partition can not be modified. You must create partition 'a' as a native OpenBSD partition, i.e. one with "4.2BSD" as the fstype, to hold the root file system. In addition to partition 'a' you should create partition 'b' with fstype "swap", and native OpenBSD partitions to hold separate file systems such as /usr, /tmp, /var, and /home. You will need to provide a mount point for all partitions you define. Partitions without mount points, or not of 4.2BSD fstype, will neither be formatted nor mounted during the installation. For quick help while in the interactive editor, enter '?'. The `z' command (which deletes all partitions and starts with a clean label), the `A' command (which performs the automatic partition layout) and the `n' command (to change mount points) are of particular interest. Although the partitions position and size are written in exact sector values, you do not need a calculator to create your partitions! Human-friendly units can be specified by adding `k', `m' or `g' after any numbers to have them converted to kilobytes, megabytes or gigabytes. Or you may specify a percentage of the disk size using `%' as the suffix. Enter 'M' to view the entire manual page (see the info on the ``-E'' flag). To exit the editor enter 'q'. After the layout has been saved, new filesystems will be created on all partitions with mount points. This will DESTROY ALL EXISTING DATA on those partitions. After configuring your root disk, the installer will return to the list of available disks to configure. You can choose the other disks to use with OpenBSD in any order, and will get to setup their layout similarly to the root disk above. However, for non-root disks, you will not be proposed a default partition layout. When all your disks are configured, simply hit return at the disk prompt. After these preparatory steps have been completed, you will be able to extract the distribution sets onto your system. There are several install methods supported: FTP, HTTP, CD-ROM, tape, or a local disk partition. To install via FTP or HTTP: To begin an FTP or HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based FTP or HTTP proxy (squid, CERN FTP, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing FTP or HTTP connections (assuming you have a proxy available to use). 2) The IP address (or hostname if you configured DNS servers earlier in the install) of an FTP or HTTP server carrying the OpenBSD 5.0 distribution. The installation program will try to fetch a list of such servers; depending on your network settings, this might fail. If the list could be fetched, it will be displayed, and you can choose an entry from the list (the first entries are expected to be the closest mirrors to your location). 3) The directory holding the distribution sets. The default value of pub/OpenBSD/5.0/alpha is almost always correct on FTP servers; for HTTP servers there is no standard location for this. 4) For FTP installs only, the login and password for the FTP account. You will only be asked for a password for non-anonymous FTP. Then refer to the section named "installation set selection" below. To install from CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be "cd0". If there is more than one partition on the CD-ROM, you will be asked which partition the distribution is to be loaded from. This is normally partition "a". You will also have to provide the relative path to the directory on the CD-ROM which holds the distribution, for the alpha this is "5.0/alpha". Then refer to the section named "installation set selection" below. To install from a local disk partition: When installing from a local disk partition, you will first have to identify which disk holds the distribution sets. This is normally "wdN" or "sdN", where N is a number. Next you will have to identify the partition within that disk that holds the distribution; this is a single letter between 'a' and 'p'. You will also have to identify the type of file system residing in the partition identified. Currently, you can only install from partitions that have been formatted as the Berkeley fast file system (ffs). You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. Then refer to the next section. Installation set selection: A list of available distribution sets found on the given location will be listed. You may individually select distribution sets to install, by entering their name, or wildcards (e.g. `*.tgz' or `base*|comp*', or `all' to select all the sets (which is what most users will want to do). You may also enter `abort' to deselect everything and restart the selection from scratch, or unselect sets by entering their name prefixed with `-' (e.g. `-x*'). It is also possible to enter an arbitrary filename and have it treated as a file set. When you are done selecting distribution sets, enter `done'. The files will begin to extract. To install from tape: Unlike all other installation methods, there is no way to know the names of the files on tape. Because of this, it is impossible to check that the files on tape match the machine architecture and release of OpenBSD/alpha. Moreover, since tape filenames are not known, the file checksums can not be verified. Use this installation method only if there is no better option. In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to specify how many files have to be skipped on the tape. This number is usually zero. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction of each file. After the files have been extracted, you will be given the choice to select a new location from which to install distribution sets. If there have been errors extracting the sets from the previous location, or if some sets have been missing, this allows you to select a better source. Also, if the installation program complains that the distribution sets you have been using do not match their recorded checksums, you might want to check your installation source (although this can happen between releases, if a snapshot is being updated on an FTP or HTTP server with newer files while you are installing). The last thing you might need to configure, if you did not get the chance to earlier, is the time zone your system will be using. For this work properly, it is expected that you have installed at least the "base50", "etc50", and "bsd" distribution sets. The installation program will then proceed to save the system configuration, create all the device nodes needed by the installed system, and will install bootblocks on the root disk. Finally, you will be asked whether you would like to install non-free firmware files (which can't be tightly integrated to the OpenBSD system) on first boot, by invoking fw_update(8) on the next boot. Congratulations, you have successfully installed OpenBSD 5.0. When you reboot into OpenBSD, you should log in as "root" at the login prompt. You should create yourself an account and protect it and the "root" account with good passwords. The install program leaves root an initial mail message. We recommend you read it, as it contains answers to basic questions you might have about OpenBSD, such as configuring your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more. To do this, run mail and then just enter "more 1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 5.0 distribution might need to be tailored for your site. We recommend you run: man afterboot which will tell you about a bunch of the files needing to be reviewed. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ Warning! Upgrades to OpenBSD 5.0 are currently only supported from the immediately previous release. The upgrade process will also work with older releases, but might not execute some migration tasks that would be necessary for a proper upgrade. The best solution, whenever possible, is to backup your data and reinstall from scratch. As a minimum, if the toolchain (the ``comp'' set) was installed, you should remove all files within /usr/include before attempting to upgrade. To upgrade OpenBSD 5.0 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from the CD-ROM or an installation floppy. When prompted, select the (U)pgrade option rather than the (I)nstall option at the prompt in the install process. You will be presented with a welcome message and asked if you really wish to upgrade. The upgrade script will ask you for the existing root partition, and will use the existing filesystems defined in /etc/fstab to install the new system in. It will also use your existing network parameters. From then, the upgrade procedure is very close to the installation procedure described earlier in this document. Note that the upgrade procedure will not let you pick neither the ``etc50.tgz'' nor the ``xetc50.tgz'' sets, so as to preserve your files in `/etc' which you are likely to have customized since a previous installation. However, it is strongly advised that you unpack the etc50.tgz and xetc50.tgz sets in a temporary directory and merge changes by hand, or with the help of the sysmerge(8) helper script, since all components of your system may not function correctly until your files in `/etc' are updated. Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. A few methods are provided. If you have an OpenBSD CD-ROM, the source code is provided. Otherwise, you can get the pieces over the Internet using anonymous CVS, CVSync or FTP. For more information, see http://www.OpenBSD.org/anoncvs.html http://www.OpenBSD.org/cvsync.html http://www.OpenBSD.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual pages distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropos(1), passwd(1), passwd(5) and afterboot(8). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Adding third party software; ``packages'' and ``ports'': -------------------------------------------------------- As complete as your OpenBSD system is, you may want to add any of several excellent third party software applications. There are several ways to do this. You can: 1) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. 2) Use the OpenBSD ``ports'' collection to automatically get any needed source file, apply any required patches, create the application, and install it for you. 3) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. If you purchased the OpenBSD CD-ROM set you already have several popular ``packages'', and the ``ports'' collection. Instructions for installing applications from the various sources using the different installation methods follow. You should also refer to the packages(7) manual page. Installing applications from the CD-ROM package collection: The OpenBSD CD-ROM ships with several applications pre-built for various hardware architectures. The number of applications vary according to available disk space. Check the directory 5.0/packages/alpha to see which packages are available for your hardware architecture. That directory will be on the same CD-ROM containing the OS installation files for your architecture. To install one or more of these packages you must: 1) become the superuser (root). 2) mount the appropriate CD-ROM. 3) use the ``pkg_add'' command to install the software. Example (in which we use su(1) to get superuser privileges, thus you have to be in group "wheel", see the manual page for su(1)). $ su Password: # mkdir -p /cdrom # mount /dev/cd0a /cdrom # pkg_add /cdrom/5.0/packages/alpha/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-21.3.tgz Installing applications from the ftp.OpenBSD.org package collection: All available packages for your architecture have been placed on ftp.OpenBSD.org in the directory pub/OpenBSD/5.0/packages/alpha/ You may want to peruse this to see what packages are available. The packages are also on the OpenBSD FTP mirror sites. See http://www.OpenBSD.org/ftp.html for a list of current FTP mirror sites. Installation of a package is very easy. 1) become the superuser (root) 2) use the ``pkg_add'' command to install the software ``pkg_add'' is smart enough to know how to download the software from the OpenBSD FTP server. Example: $ su Password: # pkg_add \ ftp://ftp.OpenBSD.org/pub/OpenBSD/5.0/packages/alpha/emacs-21.3.tgz Installing applications from the CD-ROM ports collection: The CD-ROM ``ports'' collection is a set of Makefiles, patches, and other files used to control the building and installation of an application from source files. Creating an application from sources can require a lot of disk space, sometimes 50 megabytes or more. The first step is to determine which of your disks has enough room. Once you've made this determination, read the file PORTS located on the CD-ROM which contains the ports tree. To build an application you must: 1) become the superuser (root) 2) have network access, or obtain the actual source files by some other means. 3) cd to the ports directory containing the port you wish to build. To build samba, for example, where you'd previously copied the ports files into the /usr/ports directory: cd /usr/ports/net/samba 4) make 5) make install 6) make clean Installing applications from the OpenBSD ports collection: See http://www.OpenBSD.org/faq/ports/ports.html for current instructions on obtaining and installing OpenBSD ports. You should also refer to the ports(7) manual page. Installing other applications: If an OpenBSD package or port does not exist for an application you're pretty much on your own. The first thing to do is ask if anyone is working on a port -- there may be one in progress. If no such port exists, you might want to look at the FreeBSD ports or NetBSD pkgsrc for inspiration. If you can't find an existing port, try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found in the OpenBSD Porter's Handbook at http://www.openbsd.org/faq/ports/ with more help coming from the mailing list, . Administrivia: -------------- There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are also two OpenBSD Usenet newsgroups, comp.unix.bsd.openbsd.announce for important announcements and comp.unix.bsd.openbsd.misc for general OpenBSD discussion. More information about the various OpenBSD mailing list and proper netiquette is available at http://www.OpenBSD.org/mail.html To report bugs, use the 'sendbug' command shipped with OpenBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: bugs@OpenBSD.org As a favor, please avoid mailing huge documents or files to the mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. For more information about reporting bugs, see http://www.OpenBSD.org/report.html