INSTALLATION NOTES for OpenBSD/i386 5.2 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.2 release is available on the web at http://www.OpenBSD.org/52.html. OpenBSD/i386 runs on standard PC computers and clones, based on Intel and compatible 80486 or better processors. Sources of OpenBSD: ------------------- This is a list of currently known FTP and HTTP servers at the time of the 5.2 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) http://ftp.iinet.net.au/pub/OpenBSD (Perth) ftp://ftp.iinet.net.au/pub/OpenBSD (Perth) http://mirror.as24220.net/pub/OpenBSD (Melbourne) ftp://mirror.as24220.net/pub/OpenBSD (Melbourne) Austria: http://ftp5.eu.openbsd.org/ftp/pub/OpenBSD (Vienna) ftp://ftp5.eu.openbsd.org/pub/OpenBSD (Vienna) http://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna) ftp://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna) Brazil: http://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo) ftp://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo) Bulgaria: http://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) 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) http://ftp2.fr.openbsd.org/pub/OpenBSD (Paris) ftp://ftp2.fr.openbsd.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) http://artfiles.org/openbsd (Hamburg) 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://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) Norway: http://baksmell.netrunner.nu/pub/OpenBSD (Trondheim) ftp://baksmell.netrunner.nu/pub/OpenBSD (Trondheim) Pakistan: http://stingray.cyber.net.pk/pub/OpenBSD (Karachi) ftp://stingray.cyber.net.pk/OpenBSD (Karachi) Poland: http://piotrkosoft.net/pub/OpenBSD (Oswiecim) ftp://ftp.piotrkosoft.net/pub/OpenBSD (Oswiecim) http://ftp.icm.edu.pl/pub/OpenBSD (Warszawa) ftp://ftp.icm.edu.pl/pub/OpenBSD (Warszawa) 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://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: 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/OpenBSD (Manchester) ftp://mirror.bytemark.co.uk/OpenBSD (Manchester) 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) 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) http://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) http://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL) ftp://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL) http://mirror.esc7.net/pub/OpenBSD (Dallas, TX) ftp://mirror.esc7.net/pub/OpenBSD (Dallas, TX) http://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO) ftp://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO) http://mirrors.nycbug.org/pub/OpenBSD (New York City, NY) ftp://mirrors.nycbug.org/pub/OpenBSD (New York City, NY) http://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID) ftp://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID) 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.2 Release Contents: ----------------------------- The OpenBSD 5.2 release is organized in the following way. In the .../5.2 directory, for each of the architectures having an OpenBSD 5.2 binary distribution, there is a sub-directory. The i386-specific portion of the OpenBSD 5.2 release is found in the "i386" subdirectory of the distribution. That subdirectory is laid out as follows: .../5.2/i386/ INSTALL.i386 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. floppy52.fs The standard i386 boot and installation floppy; see below. floppyB52.fs Another i386 boot and installation floppy; this one features all the drivers not available in floppy52.fs, such as SCSI, RAID, Gigabit Ethernet, and such; see below. floppyC52.fs Another i386 boot and installation floppy; this one features most of the cardbus and PCMCIA drivers; see below. pxeboot i386-specific second-stage PXE bootstrap (for network installs); see below. *.tgz i386 binary distribution sets; see below. bsd A stock GENERIC i386 kernel which will be installed on your system during the install. bsd.mp A stock GENERIC.MP i386 kernel, with support for multiprocessor machines, which can be used instead of the GENERIC kernel after the install. bsd.rd A compressed RAMDISK kernel; the embedded filesystem contains the installation tools. Used for simple installation from a pre-existing system. install52.iso The i386 boot and installation CD-ROM image, which contains the base and X sets, so that install or upgrade can be done without network connectivity. cd52.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. cdbr First-stage CD bootstrap (boot sector), which loads the cdboot second-stage bootstrap. This file is included in the cd52.iso image, and is provided as a convenience, but will rarely be needed. cdboot Second-stage CD bootstrap loader for non-emulation OpenBSD El Torito CD-ROMs. It processes boot.conf then loads the bsd.rd installation ramdisk kernel. This file is included in the cd52.iso image, and is provided as a convenience, but will rarely be needed. cdemu52.iso Another bootable CD-ROM image, for older systems where the BIOS only supports the ``large floppy emulation'' mode for bootable CD-ROMs, and which are therefore unable to boot cd52.iso. This image is provided as a convenience, but should rarely be needed. Additionally, you may be interested in .../5.2/tools/ miscellaneous i386 installation utilities like rawrite.exe, ntrw.exe, gzip.exe, and pfdisk.exe; see installation section, below. Bootable installation/upgrade floppy images: The three 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. In addition, the "tools/" directory contains some utilities that might be useful for the installation. The OpenBSD/i386 binary distribution sets contain the binaries which comprise the OpenBSD 5.2 release for i386 systems. There are ten binary distribution sets. The binary distribution sets can be found in the "i386" subdirectory of the OpenBSD 5.2 distribution tree, and are as follows: base52 The OpenBSD/i386 5.2 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. [ 52.6 MB gzipped, 159.0 MB uncompressed ] comp52 The OpenBSD/i386 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. [ 55.9 MB gzipped, 169.0 MB uncompressed ] etc52 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.6 KB gzipped, 1.5 MB uncompressed ] game52 This set includes the games and their manual pages. [ 2.5 MB gzipped, 5.7 MB uncompressed ] man52 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.2 MB gzipped, 35.7 MB uncompressed ] xbase52 This set includes the base X distribution. This includes programs, headers and libraries. [ 11.0 MB gzipped, 32.4 MB uncompressed ] xetc52 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc52 for X. [ 70.0 KB gzipped, 266.1 KB uncompressed ] xfont52 This set includes all of the X fonts. [ 37.5 MB gzipped, 48.5 MB uncompressed ] xserv52 This set includes all of the X servers. [ 22.5 MB gzipped, 54.8 MB uncompressed ] xshare52 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/i386 5.2 works across a broad range of standard PCs and clones, with a wide variety of processors and I/O bus architectures. It can be expected to install and run with minimal difficulties on most current products. The cases where problems may be encountered are typically older proprietary PCs, laptops, or specialized server boxes that rely on a custom BIOS to paper over implementation differences. OpenBSD/i386 5.2 supports most SMP (Symmetrical MultiProcessor) systems. To support SMP operation, a separate SMP kernel (bsd.mp) is included with the installation file sets. The minimal configuration to install the system is 24MB or 32MB of RAM and perhaps 200MB of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. Supported hardware include: Processors All CPU chips compatible with the Intel 80486 architecture: 80486 (SX/DX/DX2/DX4, an FPU is required) Intel Pentium/Pentium-MMX Intel Pentium Pro/II/III/Celeron/Xeon Intel Pentium IV AMD 6x86 AMD K5/K6/K6-2/K6-3 AMD Athlon/Duron Cyrix MediaGX/M1/M2 VIA Cyrix III Rise mP6 IDT WinChip NexGen 586 NS Geode GX1 Transmeta TMS3200, TMS5400, TMS5600 Everything that is a clone of the 486 or up should work fine. Buses All standard ISA, EISA, VLB, and PCI bus based machines, including among others: Intel 450GX/KX based machines Intel 450NX based machines ServerWorks chipset-based machines Both 16-bit PCMCIA Cards and newer 32-bit CardBus support Universal Serial Bus (USB) Inter IC (I2C) bus The MCA bus found in various older IBM PS/2 machines is not supported. Bus Interfaces Standard PCI-PCI bridges, including PCI expansion backplanes YENTA-compatible PCI-CardBus bridges Entropy Sources Interrupt latency collection from many devices Intel 82802 random number generator found on i810, i815, i820, i840, i850, and i860 based systems. Disk Controllers Floppy controllers. ISA MFM, ESDI, IDE, and RLL hard disk controllers. PCI IDE and Serial ATA Controllers Acard ATP850U, ATP860, ATP860-A, ATP865-A, ATP865-R Acer Labs M5229 Adaptec AAR-1210SA Advanced Micro Devices AMD-756, AMD-766, AMD-768, AMD-8111 ATI IXP 200, IXP 300, IXP 400, IXP 700 CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, PCI0649, PCI0680 Contaq Microsystems/Cypress CY82C693 HighPoint HPT366, HPT370, HPT372, HPT302, HPT371, HPT374 (RAID mode is not supported) Intel PIIX, PIIX3, and PIIX4 Intel 82801 (ICH/ICH0/ICH2/ICH3/ICH4/ICH4-M/ICH5/ICH5R/ ICH6/ICH6M/ICH6R/ICH7/ICH7M/ICH7R/ICH7M DH/ICH8/ICH8M/ ICH9/ICH9M) Intel 6300ESB/6321ESB ITE IT8211F/IT8212F (RAID mode is not supported) JMicron JMB361/JMB363/JMB365/JMB366/JMB368 National Semiconductor PC87415 National Semiconductor SCx200 (found on SC1100 SoC) NVIDIA nForce/nForce2/nForce2-400/nForce3/nForce3-250/nForce4/ MCP04/MCP51/MCP55/MCP61/MCP65/MCP67/MCP73/MCP77 Promise PDC20246, PDC20262, PDC20265, PDC20267, PDC20268, PDC20268R, PDC20269, PDC20271, PDC20275, PDC20276, PDC20277, PDC20318, PDC20319, PDC20371, PDC20375, PDC20376, PDC20377, PDC20378, PDC20379, PDC20571, PDC20575, PDC20579, PDC20775, PDC40518, PDC40718, PDC40719, PDC40779 ServerWorks OSB4, CSB5, CSB6 (including support for the third channel) Silicon Image SiI3112, SiI3512, SiI3114 Silicon Integrated System 180, 181, 5513 (5597/5598), 540, 550, 620, 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 661, 655, 658, 730, 733, 735, 740, 745, 746, 748, 750, 751, 752, 755, 760, 962, 963 VIA Technologies CX700, VT82C586/A/B, VT82C596A/B, VT82C686A/B, VT8231, VT8366, VT8233, VT8235, VT8237, VT8237A/S, VT8251, VT6410, VX700 SCSI Host Adapters Adaptec AHA-1540, AHA-154xA, AHA-154xB, AHA-1542C, AHA-1542CF, AHA-1542CP, AHA-1640 [B] [C] Adaptec AHA-174x [B] [C] Adaptec AIC-6260 and AIC-6360 based boards, including: [B] [C] the Adaptec AHA-152x and the SoundBlaster SCSI host adapter. (Note that you cannot boot from these boards if they do not have a boot ROM; only the AHA-152x and motherboards using this chip are likely to be bootable, consequently.) 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 [B] [C] 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 Adaptec AIC-7901, AIC-7901A, and AIC-7902 based host adapters [A] [C] including the Adaptec cards AHA-29320 AHA-39320 AdvanSys 'U', 'UW', 'U2W' and 'U160' PCI SCSI controllers including the ABP940U[AW], ASB3940U[AW]-00, ASB3940U2W-00 and ASB3950U160 [A] [B] [C] AMD Am53c974 PCscsi-PCI SCSI controllers, including: [A] [B] [C] Tekram DC-390 BusLogic BT-54x (Adaptec AHA-154x clones) [B] [C] BusLogic 445, 74x, 9xx (but not the new "FlashPoint" series of BusLogic SCSI adapters) [B] [C] Initio INIC-940 and INIC-950 based PCI SCSI host adapters, including: [A] [C] Initio INI-9090U Initio INI-9100U/UW Iwill 2935UW DTC Domex 3194U Plus LSI Fusion-MPT (Symbios Logic/NCR) [A] [C] 53C1020/53C1020A/53C1030/53C1030T/53C1035 FC909/FC919/919X/FC929/FC929X/FC949/FC949E/FC949X SAS1064/SAS1064E/SAS1068/SAS1068E QLogic PCI SCSI controllers [A] [C] Seagate/Future Domain ISA SCSI adapter cards, including: [B] [C] ST01/02 Future Domain TMC-885 Future Domain TMC-950 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.) [B] [C] Tekram DC-300B and DC-320E (Adaptec AHA-154x clones) [B] [C] Tekram DC-3x5U (DC-315U, DC-395U/UW/F) TRM-S1040 based PCI SCSI host adapters [A] [C] Ultrastor 14f, 24f, and 34f [A] [C] WD-7000 SCSI host adapters [A] [B] [C] RAID and Cache Controllers 3ware Escalade 3W-5x00, 3W-6x00, 3W-7x00 [A] [C] Adaptec FSA-based RAID controllers, including: [*] Adaptec AAC-2622, AAC-364, AAC-3642 Dell PERC 2/Si, PERC 2/QC, PERC 3/Si, PERC 3/Di, PERC 3/QC HP NetRAID-4M American Megatrends Inc. MegaRAID PCI controllers in "Mass Storage" mode, including: [A] [C] ACER MegaRAID ROMB-2E Apple Xserve G5 PCI Hardware RAID Card Dell CERC-PATA, PERC 2/DC, PERC 2/SC, PERC 3/DC, PERC 3/DCL PERC 3/QC, PERC 3/SC, PERC 4/DC, PERC 4/Di, PERC 4/SC, PERC 4e/DC, PERC 4e/Di, PERC 4e/SC, PERC 4e/Si FSC MegaRAID PCI Express ROMB Hewlett-Packard 438, 466, T[567] Intel RAID Controller SRCS16, SRCS28X, SRCU41L, SRCU42E, SRCU42X, SROMBU42E, SRCZCRX LSI Logic/AMI/Symbios MegaRAID, 523 SATA, i4 133 RAID, ATA 133-2 Elite 1400/1600/1650, Enterprise 1200/1300/1400/1500/1600, Express 100/200/300/500, Series 418, SCSI 320-0/320-0X, SCSI 320-1/320-1E/320-1LP/320-2/320-2E/320-2X/320-4X, SATA 150-4, SATA 150-6, SATA 300-4X, SATA 300-8ELP, SATA 300-8X, SATA 300-8XLP NEC MegaRAID PCI Express ROMB Compaq Smart ARRAY 2*, 3* and 4* adapters, including: [A] [C] Compaq Integrated Array Compaq IAES Compaq IDA, IDA-2 Compaq RAID LC2 Compaq Smart Array 221, 3100ES, 3200, 4200, 4250ES, 431 Compaq SMART, SMART-2/E, SMART-2/P, SMART-2DH, SMART-2SL Compaq/HP Smart ARRAY 5* and 6* adapters DPT SmartCache and SmartRaid III/IV PCI/EISA adapters [A] [C] Intel (and formerly ICP-Vortex) GDT series [A] [C] I2O (intelligent I/O) RAID controllers, including: [A] [C] Adaptec SCSI RAID (ASR-2100S, ASR-2110S, ASR-3200S, etc) American Megatrends Inc. MegaRAID controllers (in I2O mode) and probably other vendors' controllers supporting I2O, including Intel and Mylex (untested) LSI Logic & Dell MegaRAID SAS controllers Dell PERC 5/e, PERC 5/i, PERC 6/e, PERC 6/i Intel RAID Controller SRCSAS18E, SRCSAS144E LSI Logic MegaRAID SAS 8300XLP/8308ELP/8344ELP/8408E, MegaRAID SAS 8480E/8888ELP/8880EM2 CD-ROM and DVD-ROM Drives Mitsumi CD-ROM drives [*] [Note: The Mitsumi driver device probe is known to cause trouble with several devices!] Most SCSI CD-ROM, CD-R, CD-RW, DVD and DVD-RW drives Most ATAPI CD-ROM, CD-R, CD-RW, DVD and DVD-RW drives Tape Drives Most SCSI tape drives [C] Most SCSI tape changers [G] MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not all of the display adapters OpenBSD/i386 are supported by X. See the XFree86 FAQ for more information.) Serial Ports 8250/16450-based ports 16550-based ports ST16660-base ports AST-style 4-port serial boards [G] BOCA 8-port serial cards [*] Cyclades Cyclom-{4, 8, 16}Y serial boards [G] Cyclades-Z series multiport serial boards [G] IBM PC-RT 4-port serial boards [*] Addonics FlexPort 8S [*] Parallel Ports Any standard parallel port [G] Communication Controllers Universal Serial Bus host controllers, including: USB Universal Host Controller [A] [B] [C] USB Open Host Controller [A] [B] [C] PCI `universal' communication cards, providing serial and parallel ports, including: [G] AT&T/Lucent Venus Modem (found on IBM 33L4618 card, Actiontec 56K, and others) Avlab Low Profile PCI 4S Quartet (4 port serial) Avlab PCI 2S (2 port serial) Boca Research Turbo Serial 654 PCI (4 port serial) Boca Research Turbo Serial 658 PCI (8 port serial) Decision Computer Inc PCCOM PCI 2 Port (serial) Decision Computer Inc PCCOM PCI 4 Port (serial) Decision Computer Inc PCCOM PCI 8 Port (serial) Digi International Digi Neo 4 (4 port serial) Dolphin Peripherals 4014 (dual parallel) and 4035 (dual serial) Exsys EX-41098 (4 port serial) Koutech IOFLEX-2S (dual serial Kouwell Model-223 (2-port serial, 1 port parallel) Lava Computers 2SP-PCI (parallel port) Lava Computers 2SP-PCI and Quattro-PCI (dual serial) Lava Computers Octopus-550 Lava LavaPort-650 Moxa Technologies Co., Ltd. PCI I/O Card 4S (4 port serial) Moxa Technologies Co., Ltd. C104H/PCI (4 port serial) Moxa Technologies Co., Ltd. CP104/PCI (4 port serial) NEC PK-UG-X008 (serial) NEC PK-UG-X001 K56flex PCI (modem) NetMos 1P (1 port parallel) NetMos 2S1P (2 port serial and 1 port parallel) NetMos 4S (4 port serial) Oxford OX16PCI952 (2 port serial, 1 port parallel) Oxford OX16PCI954 (4 port serial, 1 port parallel) SIIG Cyber 2P1S (dual parallel, single serial) and 2S1P (dual serial, single parallel) SIIG Cyber 4S (quad serial) SIIG Cyber I/O (single parallel, single serial) SIIG Cyber Parallel, Parallel Dual, Serial, Serial Dual SIIG Cyber 8S PCI 16C850 SUNIX 400x (1 port parallel) SUNIX 401x (2 port parallel) SUNIX 402x (1 port serial) SUNIX 403x (2 port serial) SUNIX 405x (4 port serial) SUNIX 406x (8 port serial) SUNIX 407x (2 port serial and 1 port parallel) SUNIX 408x (2 port serial and 2 port parallel) SUNIX 409x (4 port serial and 2 port parallel) Syba Tech Ltd. PCI-4S2P-550-ECP (4 port serial, 2 port parallel) US Robotics 3CP5609 PCI (modem) VScom PCI 800 (8 port serial) VScom PCI 011H (1 port parallel) VScom PCI 100H (1 port serial) VScom PCI 110H (1 port serial and 1 port parallel) VScom PCI 200H (2 port serial) VScom PCI 210H (2 port serial and 1 port parallel) VScom PCI 400H (4 port serial) VScom PCI 410H (4 port serial and 1 port parallel) VScom PCI 800H (8 port serial) VScom PCI 100L (1 port serial) VScom PCI 200L (2 port serial) VScom PCI 210L (2 port serial and 1 port parallel) VScom PCI 400L (4 port serial) VScom PCI 800L (8 port serial) Ethernet Adapters 3Com 3c501 [A] [B] [C] 3Com 3c503 [B] [C] 3Com 3c505 [A] [B] [C] 3Com 3c507 [A] [B] [C] 3Com 3c509, 3c579, and 3c59x (disabling PnP on 3c509B is recommended) 3Com 3c515 [B] [C] 3Com 3c9xx Etherlink XL adapters, 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 3c555/3c556/3c556B MiniPCI adapters Dell on-board 3c920 Dell Precision on-board 3c905B Dell OptiPlex GX1 on-board 3c918 Dell Latitude laptop docking station embedded 3c905 NVIDIA nForce2 integrated 3Com 9201 (nForce2-ST, nForce2-GT) 3Com 3c990 3XP Typhoon/Sidewinder PCI adapters, including: [A] [B] [C] 3C990-TX-95 3C990-TX-97 3C990-TX-SVR95 3C990-TX-SVR97 Adaptec "Starfire" AIC-6915 based PCI adapters, including: [G] 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, including: Accton EN2242 MiniPCI Linksys LNE100TX v4.x Mototech ME316 ADMtek AN986-based USB adapters, including: [A] [B] [C] 3Com 3c460b Abocom UFE1000 Abocom DSB650TX Accton USB320-EC Accton SpeedStream Ethernet Admtek Pegasus, Pegasus II AEI USB Fast Ethernet Allied Telesyn AT-USB100 ATEN UC-110T Belkin F5D5050 Billionton Systems USB100, USB100E, USB100LP, USBE100 Corega FEther USB-TX, USB-TXS D-Link DSB-650, 650TX, 650TX-PNA ELCON Systemtechnik Goldpfeil P-LAN Elecom LD-USB/TX, LD-USBL/TX, LD-USB20 Elsa Microlink USB2Ethernet GIGABYTE GN-BR402W Hawking UF100 HP HN210E I/O Data USB ETTX Kingston KNU101TX Laneed LD-USBL/TX Linksys USB100TX, USB100H1, USB10T, USB10TA, USB10TX Melco Inc. LUA-TX, LUA2-TX Microsoft MN110 Mobility EasiDock Ethernet Netgear FA101 Omnidirectional Control Technology USB TO Ethernet Siemens SpeedStream USB SmartBridges smartNIC 2 SMC 2202USB/ETH SMC 2206USB/ETH SOHOware NUB100, NUB110 ASIX Electronics AX88172/AX88178/AX88772 USB Ethernet adapters, including: [A] [B] 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 Linksys USB1000 Logitec LAN-GTJ/U2 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 AMD LANCE and PCnet-based ISA Ethernet adapters, including: [B] [C] Novell NE1500T Novell NE2100 Kingston 21xx AMD PCnet-based PCI Ethernet adapters, including: [B] [C] BOCALANcard/PCI AT&T StarLAN 10, EN100, and StarLAN Fiber ASIX 88140A/88141 PCI Ethernet adapters, including: CNet Pro110B Alfa Inc. GFC2204 Broadcom BCM4401 [A] [B] CATC USB-EL1210A-based USB adapters, including: [A] [B] [C] Belkin F5U011/F5U111 CATC Netmate and Netmate II SmartBridges SmartLink Davicom DM9009, DM9100, DM9102, and DM9102A based PCI adapters, including: Jaton XpressNet Davicom DM9601 based USB adapters, including: [A] [B] [C] Corega FEther USB-TXC HenTong WK-668 ShanTou ST268 DEC EtherWORKS III adapters, including: [G] DEC DE203, DE204, DE205 Digital DC21x4x-based PCI Ethernet adapters, 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 Digital DC2114x-based four port cards, including: Adaptec ANA-6944A Cogent EM400 Compex 400TX CompuShack Goldline Quattro Phobos P430TX Znyx ZX346 Intel EtherExpress 16 [A] [B] [C] Intel EtherExpress PRO/10 ISA [A] [B] [C] Intel i8255x-based (except the i82556) PCI adapters, 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 Kawasaki LSI KL5KUSB101B-based USB adapters, including: [A] [B] [C] 3Com 3c19250 3Com 3c460 HomeConnect AboCom Systems URE450 Ethernet ADS Technologies USB-10T 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, including: Kingston KNE110TX Linksys LNE100TX Matrox Networks FastNIC 10/100 Netgear FA310TX Macronix 98713/713A/715/715A/725/727/732-based adapters, including: Accton EN1217 Addtron AEF-320TX/AEF-330TX CNet PRO120A/B Complex RL-100TX NDC Communications SOHOware SFA110A SVEC PN102-TX Fast Ethernet card Myson Technologies MTD803 3-in-1 Fast Ethernet adapters National Semiconductor DP83815/DP83816-based PCI adapters, including: [B] [C] Netgear FA311 Netgear FA312 Netgear FA331 Novell NE1000, NE2000 [B] [C] RealTek 8129, RealTek 8139 Ethernet adapters, including: Accton MPX 5030/5038 Allied Telesyn AT2550 D-Link DFE530TX+, 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: [A] [B] [C] 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 OQO model 01 (10/100) Ethernet Repotec RP-USB100-A SMC 2208USB/ETH TRENDnet TU-ET100C Z-TEK ZK-R02 Zt USB10/100 ZyXEL Prestige SiS 900 and SiS 7016-based PCI adapters, including: [B] [C] Mototech ME313 NetSurf NS-KFE30D SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards [B] [C] SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [B] [C] (See special notice later in this document) SMC 8416 EtherEZ PnP (with PnP mode off) [B] [C] SMC 9432 (EtherPower II) EPIC 10/100 [C] Sun Happy Meal PCI adapters, including: [G] Fast Ethernet Quad Fast Ethernet Sundance ST201-based PCI adapters, including: [G] D-Link DFE-550TX Texas Instruments ThunderLAN PCI adapters, including: [C] 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/RhineIII Ethernet adapters, including: [C] Addtron AEF-360TX Hawking PN102TX D-Link DFE530TX VMware VMXnet Virtual Interface Controller devices: [A] [B] [C] VMware ESX Server 2.x VMware GSX Server 2.5 and newer VMware Server 1.0 and newer VMware Workstation 4.5 and newer Winbond W89C840F Ethernet adapters, including: [A] [B] [C] TRENDnet TE100-PCIE Compex RL100-ATX 10/100baseTX Wireless Ethernet Adapters ADMtek ADM8211 IEEE 802.11b PCI/CardBus adapters [A] [B] [C] Aironet Communications 4500/4800 IEEE 802.11FH/b ISA PnP, PCI, and PCMCIA adapters [A] [B] [C] Atheros IEEE 802.11a/b/g CardBus adapters [A] [B] Atheros IEEE 802.11a/b/g PCI adapters [A] [B] Atheros USB IEEE 802.11a/b/g USB adapters [G] Atheros USB IEEE 802.11a/b/g/Draft-N USB adapters [G] Atmel AT76C50x IEEE 802.11b USB adapters [G] Broadcom AirForce IEEE 802.11b/g CardBus adapters [G] Broadcom AirForce IEEE 802.11b/g PCI adapters [G] Conexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g CardBus adapters [G] Conexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g PCI adapters [G] Conexant/Intersil PrismGT SoftMAC IEEE 802.11b/g USB adapters [A] [B] [C] Intel PRO/Wireless 2100 IEEE 802.11b PCI adapters [G] Intel PRO/Wireless 2200BG/2225BG/2915ABG 802.11a/b/g PCI adapters [G] Intel PRO/Wireless 3945ABG IEEE 802.11a/b/g PCI adapters [G] Intel Wireless WiFi Link 4965AGN IEEE 802.11a/b/g/Draft-N adapters [G] Marvell Libertas IEEE 802.11b/g PCI/CardBus adapters [G] Marvell Libertas IEEE 802.11b/g Compact Flash adapters (will be detected as PCMCIA adapters) [G] Ralink Technology IEEE 802.11a/b/g CardBus adapters [A] [B] Ralink Technology IEEE 802.11a/b/g PCI adapters [B] [C] Ralink Technology IEEE 802.11b/g USB adapters [A] [B] [C] Ralink Technology USB IEEE 802.11a/b/g USB adapters [A] [B] [C] Ralink Technology USB IEEE 802.11a/b/g/Draft-N USB adapters [A] [B] [C] Raytheon Raylink/WebGear Aviator IEEE 802.11FH PCMCIA adapters [A] [B] [C] Realtek RTL8180L IEEE 802.11b CardBus adapters [A] [B] [C] TI ACX100/ACX111 IEEE 802.11a/b/g PCI/CardBus adapters [G] WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b Compact Flash adapters (will be detected as PCMCIA adapters) [B] WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b PCI adapters [C] WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b PCMCIA adapters [B] WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b USB adapters [A] [B] ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g USB adapters [G] Gigabit Ethernet Adapters Agere/LSI ET1310 based adapters [A] [B] [C] Alteon Tigon I/II PCI Gigabit Ethernet boards, including: [A] [B] [C] 3Com 3c985 and 3c985B Alteon ACEnic V (fiber and copper) Digital EtherWORKS 1000SX Farallon PN9000SX Netgear GA620 and GA620T SGI Tigon Intel i82540, i82541, i82542, i82543, i82544, i82545, i82546, i82547, i82571, i82572 and i82573 based adapters, 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) Marvell Yukon-2 based adapters, including: [A] [B] [C] D-Link DGE-550SX D-Link DGE-560SX D-Link DGE-550T B1 D-Link DGE-560T SysKonnect SK-9E21 SysKonnect SK-9E22 SysKonnect SK-9E81 SysKonnect SK-9E82 SysKonnect SK-9E91 SysKonnect SK-9E92 SysKonnect SK-9S21 SysKonnect SK-9S22 SysKonnect SK-9S81 SysKonnect SK-9S82 SysKonnect SK-9S91 SysKonnect SK-9S92 SysKonnect SK-9E21D National Semiconductor DP83280 and DP83281 based PCI adapters, including: [A] [B] [C] Addtron AEG320T Asante FriendlyNet GigaNIX 1000TA and 1000TPC D-Link DGE-500T Linksys EG1032 and EG1064 Netgear GA622T SMC EZ Card 1000 Surecom Technology EP-320G-TX Level1 LXT1001 based adapters (untested), including: [*] SMC TigerCard 1000 D-Link DGE-500SX NVIDIA nForce MCP based adapters, including: nForce/nForce 2/nForce 3/CK804/MCP04/MCP51/MCP55/MCP61/ MCP65/MCP67/MCP73/MCP77/MCP79 Broadcom BCM570x (Tigon3) based PCI adapters, including: [A] [C] 3Com 3c996-T 3Com 3c996-SX 3Com 3c996B-T Dell PowerEdge 1750 integrated BCM5704C NIC Dell PowerEdge 2550 integrated BCM5700 NIC Dell PowerEdge 2650 integrated BCM5703 NIC HP ProLiant NC320T PCI-E Gigabit NIC HP ProLiant NC370F PCI-X Gigabit NIC HP ProLiant NC370T PCI-X Gigabit NIC HP ProLiant NC1020 PCI Gigabit NIC HP ProLiant NC6770 PCI-X Gigabit NIC HP ProLiant NC7760 embedded Gigabit NIC HP ProLiant NC7770 PCI-X Gigabit NIC HP ProLiant NC7771 PCI-X Gigabit NIC HP ProLiant NC7780 embedded PCI-X Gigabit NIC HP ProLiant NC7781 embedded PCI-X Gigabit NIC HP ProLiant NC7782 embedded PCI-X Gigabit NIC IBM ThinkPad T43/T43p integrated BCM5751M NIC IBM xSeries 235 integrated BCM5703X NIC IBM xSeries 305 integrated BCM5703X NIC Netgear GA302T SysKonnect SK-9D21 SysKonnect SK-9D41 Broadcom NetXtreme II based PCI-X/PCIe adapters, including: [A] [B] [C] Dell PowerEdge 1950 integrated BCM5708 Dell PowerEdge 2950 integrated BCM5708 Dell PowerEdge 2970 integrated BCM5708 HP NC370F PCI-X HP NC370T PCI-X HP NC373F PCI Express HP NC373i PCI Express HP NC380T PCI Express Dual Port IBM xSeries 3550 integrated BCM5708 IBM xSeries 3650 integrated BCM5708 Realtek 8139C+/8169/816xS/811xS/8101E based PCI adapters, including: Buffalo LGY-PCI-GT (8169S) Compaq Evo N1015v Integrated Ethernet (8139C+) Corega CG-LAPCIGT (8169S) D-Link DGE-528T (8169S) D-Link DGE-660TD (8196/8110SB) 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) TTTech MC322 (8139C+) Xterasys XN-152 10/100/1000 NIC (8169) Sundance/Tamarack TC9021 based PCI adapters, including: [G] D-Link DGE-550T (10/100/1000baseTX) Antares Microsystems Gigabit Ethernet board SysKonnect and Marvell based adapters, including: [B] [C] 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) VIA Networking VT6122 based PCI adapters, including: ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701) ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702) 10 Gigabit Ethernet Adapters Intel 82597EX based PCI-X adapters, including: Intel PRO/10GbE CX4 Server Adapter (PXLA8591CX4) Intel PRO/10GbE LR Server Adapter (PXLA8591LR) Intel PRO/10GbE SR Server Adapter (PXLA8591SR) Sun 10 Gigabit Ethernet PCI-X Adapter (X5544A-4) Neterion Xframe/Xframe II based adapters, including: Hitachi PCI-X 10 Gigabit Ethernet Adapter HP AB287A 10 Gigabit Ethernet Adapter IBM 10GbE SR Server Adapter IBM 10 Gb Ethernet-LR PCI-X 2.0 DDR Adapter IBM 10 Gb Ethernet-SR PCI-X 2.0 DDR Adapter Neterion/S2io Xframe Neterion Xframe II Neterion Xframe II Sun Fire Neterion Xframe E SGI 10 Gigabit Ethernet Network Adapter Tehuti Networks adapters, including: TN3017-S 10 GbE Single Port XAUI Server Controller TN3017-D 10 GbE Dual Port XAUI Server Controller TN7581-D 10 GbE Dual XFP Server Adapter TN7585-D 10 GbE Dual CX4 Low Profile Server Adapter TN7588-S 10 GbE Single 10GBASET Low Profile Server Adapter TN7588-D 10 GbE Dual 10GBASET Low Profile Server Adapter TN7589-S 10 GbE Single CX4 Low Profile Server Adapter ATM Adapters Efficient Networks EN-155 and Adaptec ANA-590X ATM interfaces [*] FDDI Adapters Digital DEFEA EISA and PCI FDDI adapters [G] Wan Adapters SBE (formerly Lan Media Corporation) SSI (T1)/HSSI/DS1/DS3 WAN interfaces [G] Sangoma Sangoma Technologies AFT T1/E1 WAN interfaces [G] Cryptography Accelerators Broadcom Bluesteelnet uBsec 5501, 5601, 5801, 5802, 5805, 5820, 5821, 5822, 5823 [G] Hifn 6500-based boards [G] Hifn 7751/7811/7951/7955/7956-based boards (hifn), including: [G] Soekris Engineering vpn1201, vpn1211, vpn1401, and vpn1411 GTGI PowerCrypt Encryption Accelerator NetSec 7751 Hifn 7751 and 9751 reference boards Invertex AEON SafeNet SafeXcel 1141/1741 [G] PC Cards (PCMCIA [B] and CardBus [B] [C]) ATA cards, including: ATA/IDE card drives ATA/IDE CD-ROM adapters CF/ATA flash cards and disk drives Ethernet adapters, including: 3Com EtherLink and EtherLink XL-based LAN PC cards, including: 3Com 3c556, 3c562 3Com 3c574TX, 3c[CX]FE574BT 3Com 3c589, 3c589[BCDE] 3Com 3c575TX, 3c[CX]FE575[BC]T CardBus 3Com 3c[CX]FEM656, 3c[CX]FEM656[BC] CardBus Intel/DEC 21443 "Tulip" clones, including: ADMtex AN985 Centaur-C CardBus IBM EtherJet 10/100 CardBus SMC EZ CardBus 10/100 Xircom X3201 CardBus adapters, including RealPort models Intel i8255x-based, including: Intel PRO/100 CardBus II NE2000-based, including: Accton EN2212, EN2216 Allied Telesis LA-PCM AmbiCom AMB8002T Arowana FE Belkin F5D5020 Billionton Systems LNT-10TN CNet NE2000 Compex Linkport ENET-B Corega PCC-T, PCC-TD, EtherII PCC-T, Corega FastEther PCC-T, FastEther PCC-TX Corega FastEther PCC-TXD, FastEther PCC-TXF D-Link DE-650, DE-660, DE-660+, DFE-670TXD Dayna CommuniCard E Digital DEPCM-XX Dual NE2000 Edimax NE2000 Genius ME 3000II SE Grey Cell GCS2000 Gold II GVC NIC-2000p, NP0335 Hawking PN650TX I-O DATA PCLA, PCLA/TE IC-Card Kingston KNE-PC2 Linksys PCMPC100, EC2T Combo, EthernetCard Linksys Combo EthernetCard, Trust Combo EthernetCard Linksys Etherfast 10/100 MACNICA ME1 for JEIDA Melco LPC3-TX National Semiconductor InfoMover NDC Instant-Link Netgear FA410TX, FA410TXC, FA411 Network Everywhere NP10T New Media LiveWire 10/100 Planet SmartCom 2000 Planex FNW-3600-T, FNW-3700-T Premax PE-200 RPTI EP-400, EP-401 Seiko Epson EN10B SMC EZCard, 8041 Socket Communications LP-CF, LP-E SVEC PN650TX, ComboCard, LANCard Synergy S21810 Tamarack NE2000 Telecom Device TCD-HPC100 Wisecom T210CT, iPort Xircom CFE-10 RealTek 81[23]9-based, including: Accton MPX5030 CardBus Corega FEther CB-TXD 10/100 Ethernet D-Link DFE-690TXD SMC 91Cxx-based, including: Megahertz XJEM1144, CC10BT SMC EtherEZ 8020BT Xircom, including: Xircom CreditCard CE2 PCMCIA controllers, including: Intel i82365 and compatibles SCSI host adapters, including: Adaptec SlimSCSI APA-14[56]0 Serial ports, including: Most modems, digital cellular modems, and serial cards should work Wireless Ethernet adapters: See above Universal Serial Bus (USB) Devices [A] [B] [C] USB Audio [G] USB Diamond Multimedia Rio MP3 players [G] USB Ethernet adapters, see above [G] USB Generic Human Interface Devices (catch-all) [G] USB Handspring Visor [G] USB Hubs USB Keyboards USB Mass Storage devices, i.e., USB floppy drives and USB memory stick controllers USB Mice [G] USB Modems [G] USB Printers [G] USB Scanners [G] USB-USB cables [G] USB Y@p phone [*] Pointing Devices [G] "Logitech"-style bus mice "Microsoft"-style bus mice "PS/2"-style mice Serial mice (uses serial port driver) Sound Devices [G] ALI M5461 AMD 768 and 8111 AC'97 AMD Geode LX series CS5536 integrated AC'97 ATI IXP series integrated AC'97 ATI SB450/SB600 C-Media CMI8[37]38 Cirrus Logic CrystalClear CS4280, CS4281 Ensoniq AudioPCI ESS Tech ES188[78], ES888 ESS Solo-1 PCI AudioDrive ESS Maestro 1, 2 and 2E and clones ESS Maestro 3 and Allegro 1 Forte Media FM801 audio Gravis Ultrasound and Ultrasound Max HD Audio compliant devices Intel i810/i820 and 440MX AC'97 Intel 82801FB/GB/HB audio NeoMagic 256AV/ZX NVIDIA nForce and nForce AC'97 NVIDIA MCP51/55/61/65 SiS 966/966L SiS 7012 AC'97 SoundBlaster ISA cards and 100% compatibles SoundBlaster PCI128 SoundBlaster Live! and PCI512 (EMU10k1) Trident 4DWAVE-DX/NX and clones (SiS 7018, ALi M5451) VIA Envy24 VIA VT82C686A, VT8233, VT8235, VT8237 SouthBridge integrated AC'97 audio VIA VT8237A/VT8251 Yamaha OPL3-SA3 Yamaha DS-XG Yamaha and Roland ISA/ISA PnP MIDI UART [The following drivers are not extensively tested:] Personal Sound System ProAudio Spectrum S3 SonicVibes Windows Sound System Radio Receiver Devices AIMS Lab Radiotrack FM radio AIMS Lab Radiotrack II FM radio Aztech/PackardBell FM radio Brooktree 848/849/878/879-based TV tuner D-Link DSB-R100 USB radio Forte Media FM801 audio SoundForte RadioLink SF16-FMR FM radio SoundForte RadioLink SF16-FMR2 FM radio Miscellaneous Devices APM power management (on non-ACPI systems) Brooktree 8[47][89] based frame grabber and TV tuner cards, including: [G] Animation Technologies FlyVideo AOpen VA1000 Askey/Dynalink Magic TView ATI TV-Wonder and Wonder/VE AverMedia cards Hauppauge Wincast TV and WinTV/PCI IMS TV Turbo Intel Smart Video Recorder III I/O DATA GV-BCTV2/PCI I/O DATA GV-BCTV3/PCI KISS TV/FM PCI Leadtek Winfast TV 2000 Leadtek Winfast TV 2000 XP Miro PC TV MMAC Osprey NEC PK-UG-X017 STB TV PCI Television Tuner Terratec TerraTVplus Video Highway XTreme VideoLogic Captivator PCI Zoltrix TV and Genie TV/FM Hardware monitoring sensors, including: [G] AMD K8 embedded temperature sensor Analog Devices AD7416, AD7417 and AD7418 Analog Devices ADM1021, ADM1023 and ADM1032 Analog Devices ADM1022 and ADM1028 Analog Devices ADM1024 Analog Devices ADM1025 Analog Devices ADM1026 Analog Devices ADM1027 Analog Devices ADM1030 Analog Devices ADM1031 Analog Devices ADM9240 Analog Devices ADT7460, ADT7465, ADT7475, ADT7476, ADT7477 Andigilog aSC7611 Andigilog aSC7621 Asus AS99127F Asus ASB100 Dallas Semiconductor 1775 Dallas Semiconductor 1780 Fintek F71805 Genesys Logic GL518SM Genesys Logic GL523SM Global Mixed-mode Technology G781 Intel Core embedded temperature sensor Intel Xeon embedded temperature sensor ITE IT8705F, IT8712F, IT8716F, IT8718F and IT8726F Maxim DS1617 Maxim DS1624, DS1631 and DS1721 Maxim MAX6642, MAX6657, MAX6658, MAX6659 and MAX6690 National Semiconductor LM75, LM77 National Semiconductor LM78, LM78-J, LM79 National Semiconductor LM81 and LM87 National Semiconductor LM85 and LM96000 National Semiconductor LM86, LM89, LM90, LM99 and LM99-1 National Semiconductor LM93 National Semiconductor PC87366 LPC Super I/O VLM and TMS Philips LM75A Philips NE1619 SMSC 47m192 SMSC EMC6D10x and SCH5017 SiS SiS950 Texas Instruments THMC50 ThinkPad Active Protection System accelerometer VIA VT1211 VIA VT82C686A, VT8231 Winbond W83627HF, W83627THF, W83627DHG, W83627EHF, W83637HF Winbond W83697HF, W83781D, W83782D, W83783S, W83791D, W83792D Winbond W83793G Winbond W83L784R, W83L785R and W83L785TS-L Hardware watchdog timer support, including: [G] AMD Elan SC520 System Controller ICS PCI-WDT500/501 watchdog timer Intel 6300ESB ICH National Semiconductor Geode SC1100 IAOC Quancom PWDOG1 VIA VT1211 General Purpose Input/Output (GPIO) devices, including: National Semiconductor PC87366 LPC Super I/O GPIO National Semiconductor Geode SC1100 PCI-ISA bridge GPIO AMD Elan SC520 System Controller PIO function Meinberg Funkuhren radio clocks, including: GPS170PCI 3.3V/5V 6-channel GPS receiver card PCI32 5V DCF77 time signal station receiver card PCI509 5V DCF77 time signal station receiver card PCI511 3.3V/5V DCF77 time signal station receiver card PEX511 PCI Express time signal station receiver card USB5131 USB attached DCF77 radio clock Many kinds of ISA Plug-and-Play cards Nearly all SB-style audio cards Nearly all joystick ports Nearly all Yamaha-style audio cards Many NE2000-style Ethernet cards Most serial port or modem cards NE2100 Ethernet cards Drivers for hardware marked with [G] are only included in the GENERIC kernels, but are NOT included on the various distribution floppies (including the CD-ROM boot image). Drivers for hardware marked with [A] are NOT included in floppy A. Drivers for hardware marked with [B] are NOT included in floppy B. Drivers for hardware marked with [C] are NOT included in floppy C. Support for devices marked with [*] is not included in the distribution media or in the GENERIC kernel, and will require you to compile a custom kernel to enable it. Hardware that we do NOT currently support, but get many questions about: The "Micro Channel" MCA bus used in many IBM PS/2 models NCR 5380-based and 53400-based SCSI host adapters QIC-40 and QIC-80 tape drives (these are the tape drives that connect to the floppy disk controller) Sony and Panasonic proprietary CD-ROM interfaces Parallel-port ZIP drives (SCSI and ATAPI ZIP drives work fine) Intel i82556 (EtherExpress PRO/100A) and i82596 (EtherExpress PRO/10 PCI) Ethernet adapters Hewlett-Packard PC-LAN+ (HP27xxx) Ethernet adapters Aureal Vortex sound cards Winmodems Infrared devices, such as commonly found on laptops Firewire Mylex and Intel RAID controllers PCMCIA: Memory cards Most multifunction cards We are planning future support for many of these devices. To be detected by the distributed kernels, some ISA devices must be configured with specific settings. Here's their list: Device Name Port IRQ DRQ Misc ------ ---- ---- --- --- ---- Serial ports com0 0x3f8 4 [8250/16450/16550/clones] com1 0x2f8 3 [8250/16450/16550/clones] com2 0x3e8 5 [8250/16450/16550/clones] ast0 0x1a0 5 [AST 4-port serial card] cy0 12 iomem 0xd4000 [Cyclom serial card] Parallel ports lpt0 0x378 7 [interrupt-driven or polling] lpt1 0x278 [polling only] lpt2 0x3bc [polling only] MFM/ESDI/IDE/RLL hard disk controllers wdc0 0x1f0 14 [supports two disks or atapi] wdc1 0x170 15 [supports two disks or atapi] Floppy controller fdc0 0x3f0 6 2 [supports two disks] AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters aha0 0x330 any any aha1 0x334 any any BT445, BT74x, or BT9xx SCSI host adapters bha0 0x330 any any bha1 0x334 any any Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters uha0 0x330 any any uha1 0x334 any any AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters aic0 0x340 11 any Seagate ST0[12], Future Domain TMC-8xx based SCSI controllers sea0 5 iomem 0xc8000 WD7000 and TMC-7000 SCSI host adapters wds0 0x350 15 6 wds1 0x358 11 5 SCSI disks sd0 first SCSI disk (by SCSI ID) sd1 second SCSI disk (by SCSI ID) sd2 third SCSI disk (by SCSI ID) sd3 fourth SCSI disk (by SCSI ID) SCSI tapes st0 first SCSI tape (by SCSI ID) st1 second SCSI tape (by SCSI ID) SCSI CD-ROMs cd0 first SCSI CD-ROM (by SCSI ID) cd1 second SCSI CD-ROM (by SCSI ID) SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards we0 0x280 9 iomem 0xd0000 we1 0x300 10 iomem 0xcc000 Novell NE1000, or NE2000 Ethernet boards ne0 0x240 9 iomem 0xd8000 ne1 0x300 10 ne2 0x280 9 3COM 3c501 Ethernet boards el0 0x300 9 3COM 3c503 Ethernet boards ec0 0x250 9 iomem 0xd8000 3COM 3c505/Etherlink+ Ethernet boards eg0 0x310 5 AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards ie0 0x360 7 iomem 0xd0000 EtherExpress boards ie1 0x300 10 IsoLan, NE2100, and DEPCA le0 0x360 15 6 Intel EtherExpress PRO/10 ex0 0x320 5 PCI Ethernet boards need to have an interrupt, either assigned in your PCI BIOS, or autoconfigured. Hardware not listed in the above table doesn't need any specific configuration. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM FFS partitions DOS (FAT) partitions EXT2 partitions (NOT supported if booting from floppy) Tape FTP HTTP If you can't (or don't want to) boot off a CD-ROM, you can use a floppy disk (1.44MB required). Failing that, if your computer supports PXE, you can prepare a server to start the install across the network, but you will still need the install sets available on one of the above media types. 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.2/i386 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 "floppy52.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=floppy52.fs of=/dev/rfd0c bs=36b and, under Solaris: dd if=floppy52.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=floppy52.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). Creating a PXE network bootable setup using OpenBSD or other Un*x-like system: In order to start the install via PXE, you will need to set up a DHCP server and a TFTP server. The details of how to do this vary considerably, depending on the network's host. You should refer to the relevant man pages or administrator's guide for the host system. The DHCP server should return "pxeboot" to i386 clients as the network boot program. Both pxeboot and the bsd.rd install kernel should be copied to the TFTP server's root directory. If you are using an OpenBSD server, you can use the supplied dhcpd and tftpd. A sample configuration for dhcpd is given in the pxeboot(8) man page. You can get it from the man52.tgz distribution set, or see the copy on the OpenBSD web page. You should also refer to dhcpd(8) and tftpd(8) for more information on configuring them. 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}52.tgz of=${TAPE} obs=8k conv=osync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../5.2/i386 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 "base52" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- NOTE: If you wish to install OpenBSD on your whole disk, i.e. you do not want DOS or any other operating system to reside on your hard disk, you can skip this section and go on to the section that describes installation, below. If you're upgrading your system from a previous release of OpenBSD, you should have proceeded directly to the section about upgrading; you need none of the information presented here. First and foremost, before beginning the installation process, MAKE SURE YOU HAVE A RELIABLE BACKUP of any data on your hard disk that you wish to keep. Repartitioning your hard disk is an excellent way to destroy important data. Second, if you are using a disk controller which supports disk geometry translation, be sure to use the same parameters for OpenBSD as for any other operating systems installed on the disk. If you do not, it will be much harder to make OpenBSD properly coexist with them. Most operating systems have utilities that print out the disk geometry they use; often "fdisk" (or its equivalent) will do this. Third (but related to the second point above), if you are using a hard disk with more cylinders than are supported by the other operating systems or the BIOS, you MUST be sure that all boot partitions start and end within the area supported by both the BIOS and the OS in question. The OpenBSD root partition must also reside completely within the BIOS supported part of the hard disk -- this could typically be 504MB, 2GB, 8GB or 128GB, depending upon the age of the machine and its BIOS. The rest of the OpenBSD partitions can be anywhere that hardware supports. Fourth, use the other operating system's "fdisk" program or partition editor to create at least one of the partitions to be used for that operating system. If that operating system is already set up to use the entire disk, you will have to back it up, remove and recreate a smaller partition for it, and then restore the data from that partition. You do not have to create an OpenBSD partition at this time; the OpenBSD install- ation will give you an opportunity to create the partition needed for OpenBSD. Finally, do whatever is necessary to restore order to the partition you took space away from. If it was a DOS partition, you probably will need to use "format" to create a new file system on it, and then restore your important files from your backups. Other operating systems will have different needs; most will need to reformat the partition, and if it was their "main" partition, will probably need to be reinstalled. Once you've backed all your data up, there is a tool called fips 2.0 that can shrink your FAT-based DOS/Windows partition to make room for OpenBSD. It is included in the i386 tools area of this distribution as a convenience. It is strongly advised that you read its documentation and understand the consequences of your actions before using it. In some cases, defragmenting your disk and running fips may be much faster than reinstalling your DOS partition from the backup. Windows 7 (and possibly Vista) can resize their own system partition, which is usually NTFS. In the control panel, search for "partition": this will lead you to the system administration tool. Then right click on the partition you wish to shrink. You may have to fiddle with the swap file, because it's unmoveable, and you might not be able to shrink the partition as much as you would wish. Your hard disk is now prepared to have OpenBSD installed on it, and you should proceed with the installation instructions. 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. If OpenBSD will be sharing the disk with DOS or another operating system, you should have already completed the section of these notes that instructed you on how to prepare your hard disk. You should know the size of the OpenBSD area of the disk and its offset from the beginning of the disk. You will need this information when setting up your OpenBSD partitions. If your BIOS uses translated geometry, you should use this geometry for the remainder of the install. This is only necessary if you are sharing the disk with other operating systems that use the translated geometry. There are several ways to install OpenBSD onto a disk. The easiest way, should your computer support it, is to boot off the OpenBSD CD-ROM, or off one of the bootable CD-ROM mini images. Otherwise, you can boot from a 3.5" 1.44MB floppy disk if your machine has a floppy drive. If your machine supports PXE network boots, you could try to configure a server for a network install. If your machine can boot from a USB device, having a USB key with a minimal install is another possibility. 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). If you are using CD-ROM or floppy media, ensure the disk is in the drive before starting. Reboot the computer to begin the install. You might have to play with your BIOS options to get the computer to boot from the correct installation media (floppy, CD, or network/PXE) rather than from the hard disk. If you are installing across the network with PXE, you will need to tell pxeboot to get the bsd.rd install kernel: boot> boot bsd.rd It can take a while to load the kernel from a floppy, slow speed CD-ROM drive, or across a network, 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. If trying another floppy disk doesn't help, try booting after disabling your CPU's internal and external caches (if any). If it still doesn't work, OpenBSD probably can't be run on your hardware. This can probably be considered a bug, so you might want to report it. If you do, please include as many details about your system configuration as you can. 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). If you are connected using a glass console, you will next be asked for your keyboard layout (the default being the US QWERTY layout). Depending on your keyboard type, not all international layouts may be supported; answering `?' (which, on QWERTY layouts, is the key to the left of the right `shift' key, shifted) will display a list of supported layouts. (If you do not need to change the keyboard layout, just press enter.) 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 answered `y' to this question, you will get asked whether you want to start xdm on boot. If you are installing using a serial console, and since by default, the OpenBSD/i386 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. Disks on OpenBSD/i386 are partitioned using the so-called ``MBR'' partitioning scheme. You will need to create one MBR partition, in which all the real OpenBSD partitions will be created. The installation program will ask you if you want to use the whole disk for OpenBSD. If you don't need to or don't intend to share the disk with other operating systems, answer `w' here. The installation program will then create a single MBR partition spanning the whole disk, dedicated to OpenBSD. Otherwise, fdisk(8) will be invoked to let you to edit your MBR partitioning. The current MBR partitions defined will be displayed and you will be allowed to modify them, add new partitions, and change which partition to boot from by default. Note that you should make the OpenBSD partition the active partition at least until the install has been completed. After your OpenBSD MBR partition has been setup, the real partition setup can follow. 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. If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'i', 'j' and so on. 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.2 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.2/i386 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 i386 this is "5.2/i386". 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 install from partitions that have been formatted as the Berkeley fast file system (ffs) or MS-DOS. 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/i386. 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 "base52", "etc52", 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. On multiprocessor systems, if the bsd.mp kernel has been installed, it will be renamed to `bsd', which is the default kernel the boot blocks look for. The single processor kernel, `bsd', will be available as `bsd.sp'. 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.2. 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.2 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.2 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.2 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from the CD-ROM or an installation floppy as you would do for a new installation. 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 ``etc52.tgz'' nor the ``xetc52.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 etc52.tgz and xetc52.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.2/packages/i386 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.2/packages/i386/ # # 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.2/packages/i386/ 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.2/packages/i386/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