INSTALLATION NOTES for OpenBSD/i386 3.7 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. To integrate more smoothly in other environments, OpenBSD 3.7 also provides, on some platforms, several binary emulation subsystems (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris, and Ultrix compatibility), aiming at making the emulation as accurate as possible so that it is transparent to the user. 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 3.7 release is available on the web at http://www.OpenBSD.org/37.html. OpenBSD/i386 runs on standard PC computers and clones, based on Intel i386 and compatible processors. Sources of OpenBSD: ------------------- This is a list of currently known FTP servers at the time of the 3.7 release. For a more recent list, please refer to http://www.OpenBSD.org/ftp.html Main server in Canada: ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta) Argentina: ftp://ftp.openbsd.md5.com.ar/pub/OpenBSD (Buenos Aires) Australia: ftp://mirror.aarnet.edu.au/pub/OpenBSD (Canberra, .au only) ftp://ftp.it.net.au/mirrors/OpenBSD (Perth) ftp://ftp.planetmirror.com/pub/OpenBSD (Sydney) ftp://mirror.pacific.net.au/OpenBSD (Sydney) ftp://openbsd.wiretapped.net/pub/OpenBSD (Sydney) Austria: ftp://gd.tuwien.ac.at/opsys/OpenBSD (Vienna) ftp://playboy.wu-wien.ac.at/pub/OpenBSD (Vienna) Belgium: ftp://ftp.scarlet.be/pub/openbsd ftp://ftp.belnet.be/packages/openbsd (Brussels) ftp://openbsd.rug.ac.be/pub/OpenBSD (Ghent) Brazil: ftp://ftp.openbsd.org.br/pub/OpenBSD (Curitiba) ftp://ftp.das.ufsc.br/pub/OpenBSD (Santa Catarina) Bulgaria: ftp://ftp.bg.openbsd.org/pub/OpenBSD (Plovdiv) Canada: ftp://ftp.ca.openbsd.org/pub/OpenBSD (Edmonton) China: ftp://ftp.shellhung.org/pub/OpenBSD (Hong Kong) Czech Republic: ftp://ftp.openbsd.cz/pub/OpenBSD (Prague) Denmark: ftp://sunsite.dk/mirrors/openbsd (Aalborg) Finland: ftp://ftp.fi.debian.org/pub/OpenBSD ftp://ftp.jyu.fi/pub/OpenBSD (Jyvaskyla) France: ftp://ftp.ac-creteil.fr/OpenBSD ftp://ftp.bsdfr.org/pub/OpenBSD (Paris) ftp://ftp.club-internet.fr/pub/OpenBSD (Paris) ftp://ftp.fr.openbsd.org/pub/OpenBSD (Paris) Germany: ftp://ftp.de.openbsd.org/unix/OpenBSD (Berlin) ftp://ftp.tu-clausthal.de/pub/OpenBSD (Clausthal) ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD (Duesseldorf) ftp://openbsd.informatik.uni-erlangen.de/pub/OpenBSD (Erlangen) ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen) ftp://pandemonium.tiscali.de/pub/OpenBSD (Frankfurt) ftp://openbsd.bay13.net/pub/OpenBSD (Hamburg) ftp://ftp.leo.org/pub/OpenBSD (Muenchen) ftp://ftp.uni-stuttgart.de/pub/OpenBSD (Stuttgart) ftp://ftp.fh-wolfenbuettel.de/pub/os/openbsd (Wolfenbuettel) Greece: ftp://filoktitis.noc.uoa.gr/pub/OpenBSD (Athens) ftp://ftp.physics.auth.gr/pub/mirrors/OpenBSD/OpenBSD (Thessaloniki) ftp://ftp.duth.gr/pub/OpenBSD (Thrace) Hungary: ftp://ftp.fsn.hu/pub/OpenBSD Ireland: ftp://ftp.esat.net/pub/OpenBSD (Dublin) Italy: ftp://ftp.openbsd.it/pub/Unix/OpenBSD (Napoli) ftp://na.mirror.garr.it/mirrors/OpenBSD (Napoli) Japan: ftp://ftp.netlab.is.tsukuba.ac.jp/pub/os/OpenBSD (Ibaraki) ftp://ftp.iij.ad.jp/pub/OpenBSD (Tokyo) ftp://ftp.jp.openbsd.org/pub/OpenBSD (Tokyo) ftp://ftp.kddlabs.co.jp/OpenBSD (Tokyo) Latvia: ftp://ftp.bsd.lv/pub/OpenBSD Lithuania: ftp://ftp.openbsd.lt/pub/OpenBSD The Netherlands: ftp://ftp.nl.uu.net/pub/OpenBSD (Amsterdam) ftp://ftp.calyx.nl/pub/OpenBSD (Amsterdam) ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht) Norway: ftp://ftp.inet.no/pub/OpenBSD (Oslo) ftp://ftp.uninett.no/pub/OpenBSD (Oslo) Poland: ftp://sunsite.icm.edu.pl/pub/OpenBSD ftp://ftp.man.szczecin.pl/pub/BSD/OpenBSD Portugal: ftp://ftp.fmed.uc.pt/pub/OpenBSD Romania: ftp://ftp.physics.uvt.ro/pub/OpenBSD (Timisoara) Russia: ftp://ftp.chg.ru/pub/OpenBSD (Chernogolovka-Moscow) ftp://ftp.gamma.ru/pub/OpenBSD (Moscow) ftp://ftp.radio-msu.net/pub/OpenBSD (Moscow) Saudi Arabia: ftp://ftp.isu.net.sa/pub/mirrors/ftp.openbsd.org/pub/OpenBSD Spain: ftp://ftp.rediris.es/mirror/OpenBSD (Madrid) Sweden: ftp://ftp.stacken.kth.se/pub/OpenBSD (Stockholm) ftp://ftp.sunet.se/pub/OpenBSD (Uppsala) Switzerland: ftp://ftp.solnet.ch/mirror/OpenBSD ftp://ftp.dragonbsd.swiss-anime.ch/pub/OpenBSD (Bern) ftp://sunsite.cnlab-switch.ch/pub/OpenBSD (Zurich) Taiwan: ftp://openbsd.csie.nctu.edu.tw/pub/OpenBSD ftp://openbsd.nsysu.edu.tw/pub/OpenBSD ftp://ftp.tku.edu.tw/pub/OpenBSD (TamSui) Turkey: ftp://ftp.linux.org.tr/pub/OpenBSD Ukraine: ftp://ftp.openbsd.org.ua/pub/OpenBSD (Kiev) United Kingdom: ftp://ftp.plig.org/pub/OpenBSD (London) USA: ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) ftp.lug.udel.edu/pub/OpenBSD (Newark, DE) ftp://reflection.ncsa.uiuc.edu/pub/OpenBSD (Champaign, IL) ftp://mirror.sg.depaul.edu/pub/OpenBSD (Chicago, IL) ftp://rt.fm/pub/OpenBSD (Lake in the Hills, IL) ftp://ftp.groupbsd.org/pub/OpenBSD (Hillsborough, NC) ftp://ftp.cse.buffalo.edu/pub/OpenBSD (Buffalo, NY) ftp://ftp.crimelabs.net/pub/OpenBSD (New York, NY) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://carroll.cac.psu.edu/pub/OpenBSD (State College, PA) ftp://mirrors.rcn.net/pub/OpenBSD (Fairfax, VA) ftp://openbsd.secsup.org/pub/openbsd (Fairfax, VA) ftp://ftp.tux.org/bsd/openbsd (Springfield, VA) ftp://mirror.cs.wisc.edu/pub/mirrors/OpenBSD (Madison, WI) 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 3.7 Release Contents: ----------------------------- The OpenBSD 3.7 release is organized in the following way. In the .../3.7 directory, for each of the architectures having an OpenBSD 3.7 binary distribution, there is a sub-directory. The i386-specific portion of the OpenBSD 3.7 release is found in the "i386" subdirectory of the distribution. That subdirectory is laid out as follows: .../3.7/i386/ INSTALL.i386 Installation notes; this file. CKSUM, MD5 Output of the cksum(1) and md5(1) programs, usable for verification of the correctness of downloaded files. floppy37.fs The standard i386 boot and installation floppy; see below. floppyB37.fs Another i386 boot and installation floppy; this one features all the drivers not available in floppy37.fs, such as SCSI, RAID, Gigabit Ethernet, and such; see below. floppyC37.fs Another i386 boot and installation floppy; this one features most of the cardbus and PCMCIA drivers; see below. cdrom37.fs The i386 boot and installation 2.88MB floppy image that contains almost all OpenBSD drivers; 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. cd37.iso A miniroot filesystem image suitable to be used as a bootable CD-ROM image; otherwise similar to the bsd.rd image above. cdemu37.iso Another bootable CD-ROM image, for older systems which BIOS only support the ``large floppy emulation'' mode for bootable CD-ROM, and as such are unable to boot cd37.iso; this image is provided for convenience purposes, but should never be needed. Additionally, you may be interested in .../3.7/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 3.7 release for i386 systems. There are eleven binary distribution sets. The binary distribution sets can be found in the "i386" subdirectory of the OpenBSD 3.7 distribution tree, and are as follows: base37 The OpenBSD/i386 3.7 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. [ 30.6 MB gzipped, 88.0 MB uncompressed ] comp37 The OpenBSD/i386 Compiler tools. All of the tools relating to C, C++, and fortran 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. [ 17.8 MB gzipped, 57.8 MB uncompressed ] etc37 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.) [ 1.6 MB gzipped, 6.2 MB uncompressed ] game37 This set includes the games and their manual pages. [ 2.4 MB gzipped, 5.7 MB uncompressed ] man37 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. [ 6.6 MB gzipped, 23.6 MB uncompressed ] misc37 This set includes the system dictionaries (which are rather large), and the typesettable document set. [ 2.1 MB gzipped, 7.0 MB uncompressed ] xbase37 This set includes the base X distribution. This includes programs, headers and libraries. [ 9.8 MB gzipped, 27.7 MB uncompressed ] xetc37 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc37 for X. [ 0.4 MB gzipped, 2.2 MB uncompressed ] xfont37 This set includes all of the X fonts. [ 30.9 MB gzipped, 34.3 MB uncompressed ] xserv37 This set includes all of the X servers. [ 15.0 MB gzipped, 39.3 MB uncompressed ] xshare37 This set includes all text files equivalent between all architectures. [ 1.8 MB gzipped, 9.5 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/i386 3.7 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 3.7 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 12MB or 16MB of RAM and perhaps 100MB of disk space. A custom kernel might be able to run with only 8MB. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (16MB of RAM will actually allow you to run X and/or compile but it won't be speedy. Note that until you have around 32MB of RAM, getting more RAM is more important than getting a faster CPU.) Supported hardware include: Processors All CPU chips compatible with the Intel 80386 (i386) architecture: 386/486 (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 386 or up should work fine. The only CPU that is known to work poorly (due to flawed motherboard designs) is the Cyrix 386DLC. Buses All standard ISA, EISA, VLB, and PCI bus based machines, including: Intel 450GX/KX based machines Intel 450NX based machines ServerWorks chipset-based machines (We just had to mention those last three, since they are the hardest to support) 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 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 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/ICH6R) Intel 6300ESB ITE IT8212F (RAID mode is not supported) National Semiconductor PC87415 National Semiconductor SCx200 (found on SC1100 SoC) NVIDIA nForce/nForce2/nForce2-400/nForce3/nForce3-250 (SATA controllers are not supported) Promise PDC20246, PDC20262, PDC20265, PDC20267, PDC20268, PDC20268R, PDC20269, PDC20271, PDC20275, PDC20276, PDC20277, PDC20376 (RAID mode is not supported) ServerWorks OSB4, CSB5, CSB6 (including support for the third channel) Silicon Image SiI3112, SiI3512, SiI3114 Silicon Integrated System 5513 (5597/5598), 540, 550, 620, 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735, 740, 745, 746, 748, 750, 751, 752, 755, 962, 963 VIA Technologies VT82C586/A/B, VT82C596A/B, VT82C686A/B, VT8231, VT8366, VT8233, VT8235, VT8237 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) (mpt) [A] [C] 53C1030 (Dual channel Ultra320 SCSI) 53C1020 (Single channel Ultra320 SCSI) FC909 (1Gb/s Fibre Channel) FC909A (Dual 1Gb/s Fibre Channel) FC919 (2Gb/s Fibre Channel) FC929 (Dual 2Gb/s Fibre Channel) 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 [A] [C] Adaptec FSA-based RAID controllers, including: [A] [B] [C] 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] AMI MegaRAID Dell PERC 4Si and 4Di HP NetRAID 438, 466 and T[567] LSI/Symbios 523 SATA Compaq Smart ARRAY PCI/EISA 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 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) 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] QIC-02 and QIC-36 format (Archive- and Wangtek- compatible) tape drives [*] 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 XR16850-based ports (only in the pccom driver) 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] Dolphin Peripherals 4014 (dual parallel) and 4035 (dual serial) 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 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) AT&T/Lucent Venus Modem (found on IBM 33L4618 card, Actiontec 56K, and others) US Robotics 3CP5609 PCI (modem) Lava Computers 2SP-PCI (parallel port) Lava Computers 2SP-PCI and Quattro-PCI (dual serial) NEC PK-UG-X008 (serial) NEC PK-UG-X001 K56flex PCI (modem) Koutech IOFLEX-2S (dual serial) Syba Tech Ltd. PCI-4S2P-550-ECP (4 port serial, 2 port parallel) Moxa Technologies Co., Ltd. PCI I/O Card 4S (4 port serial) Moxa Technologies Co., Ltd. C104H/PCI (4 port serial) NetMos 2S1P (2 port serial and 1 port parallel) Boca Research Turbo Serial 654 PCI (4 port serial) Boca Research Turbo Serial 658 PCI (8 port serial) 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) 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] 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 SMC EZ Connect USB SOHOware NUB100 ASIX Electronics AX88172 USB Ethernet adapters, including: [A] [B] ATEN UC210T Billionton Systems USB2AR Buffalo(MELCO) LUA-U2-KTX Corega FEther USB2-TX D-Link DUB-E100 Hawking UF200 Intellinet USB 2.0 to Ethernet (rev A) JVC MP-PRX1 LinkSys USB200M Netgear FA120 Sitecom LN-029 SnapPort USB 2.0 LAN Adapter ST Lab USB 2.0 Fast Ethernet Surecom EP-1427X-2 System TALKS SGC-X2UL TRENDnet TU2-ET100 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] CATC Netmate and Netmate II Belkin F5U011/F5U111 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 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 10/100 M PCI Genius GF100TXR KTX-9130TX 10/100 Fast Ethernet Longshine LCS-8038TX-R NDC NE100TX-E 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 GreenHouse GH-USB100B GreenHouse GH-USB100B with HomePNA Linksys USB100M Longshine LCS-8138TX Melco Inc. LUA-KTX Micronet SP128AR OQO model 01 Ethernet SMC 2208USB/ETH TrendNet TU-ET100C Zt USB10/100 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 Winbond W89C840F Ethernet adapters, including: [A] [B] [C] Trendware TE100-PCIE Compex RL100-ATX 10/100baseTX Wireless Ethernet Adapters ADMtek ADM8211 based IEEE 802.11b CardBus adapters [A] [B] [C] 3Com OfficeConnect 3CRSHPW796 Blitz NetWave Point D-Link DWL-650 Rev. L1 TrendNet TEW-221PC CardBus ADMtek ADM8211 based IEEE 802.11b PCI adapters [A] [B] [C] Belkin F5D6001 v2 D-Link DWL-520 Rev. C1 LanReady WP2000 Xterasys XN2511B Aironet 4500/4800 IEEE 802.11FH/b ISA PnP, PCMCIA and PCI [A] [B] [C] Atheros AR521x based CardBus IEEE 802.11a/b/g adapters [A] [B] 3Com 3CRPAG175 Aztech WL830PC D-Link DWL-A650 D-Link DWL-AB650 D-Link DWL-AG650 D-Link DWL-G650B Elecom LD-WL54AG Elecom LD-WL54 Fujitsu E5454 Fujitsu FMV-JW481 Fujitsu E5454 I/O Data WN-AB I/O Data WN-AG I/O Data WN-A54 Linksys WPC51AB Linksys WPC55AG NEC PA-WL/54AG Netgear WAB501 Netgear WAG511 Netgear WG511T Orinoco 8480 Orinoco 8470WD Proxim Skyline 4030 Samsung SWL-5200N SMC SMC2735W Sony PCWA-C700 Sony PCWA-C300S Sony PCWA-C500 Atheros AR521x based PCI IEEE 802.11a/b/g adapters [A] [B] D-Link DWL-A520 D-Link DWL-AG520 D-Link DWL-G520 HP NC4000 Linksys WMP55AG Netgear WAG311 Netgear WG311 Proxim Skyline 4032 Senao NL-5354MP Atmel AT76C50x based USB IEEE 802.11b adapters [G] 3Com 3CRSHEW696 AboCom BWU613 Accton 2664W Acer Peripherals AWL300 Acer Peripherals AWL400 Actiontec 802UAT1 Addtron AWU120 Aincomm AWU2000B Askey Computer Voyager 1010 Askey Computer WLL013 (Intersil Radio) Askey Computer WLL013 (RFMD Radio) Belkin F5D6050 Bluetake BW002 Compaq iPAQ h54xx/h55xx Internal WLAN Conceptronic C11U Conceptronic WL210 Corega WLAN USB Stick 11 Dick Smith Electronics CHUSB 611G Dick Smith Electronics WL200U Dick Smith Electronics WL240U Dick Smith Electronics XH1153 D-Link DWL-120 rev E Geowave GW-US11S Gigabyte GN-WLBM101 Gigaset WLAN Hewlett-Packard HN210W Intel AP310 AnyPoint II I/O DATA USB WN-B11 Lexar 2662W-AR Linksys WUSB11 Linksys WUSB11 v2.8 MSI WLAN Netgear MA101 Netgear MA101 rev B OQO model 01 builtin wireless Ovislink AirLive WL-1120USB OvisLink AirLive WL-1130USB Planex Communications GW-US11S Samsung SWL2100W Siemens WLL013 SMC 2662W-AR SMC 2662W-V4 Tekram U-300C Z-Com M4Y-750 Intel PRO/Wireless 2100 IEEE 802.11b adapters [G] Intel PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11a/b/g adapters [G] Intersil PRISM-2-3 based IEEE 802.11b Compact Flash adapters (will be detected as PCMCIA adapters) [A] [B] Buffalo AirStation D-Link DCF-660W ELSA XI800 Linksys WCF12 Netgear MA701 Intersil PRISM 2-3, Lucent Hermes and Symbol Spectrum 24 based PCMCIA IEEE 802.11b adapters [A] [B] 3Com AirConnect 3CRWE737A ACTIONTEC HWC01170 Addtron AWP-100 Agere Orinoco ARtem Onair BUFFALO AirStation Cabletron RoamAbout Compaq Agency NC5004 Contec FLEXLAN/FX-DS110-PCC Corega PCC-11 Corega PCCA-11 Corega PCCB-11 Corega CGWLPCIA11 D-Link DWL-650 revisions A1-J3 ELSA XI300 ELSA XI325 ELSA XI325H EMTAC A2424i Ericsson Wireless LAN CARD C11 Gemtek WL-311 Hawking Technology WE110P I-O DATA WN-B11/PCM Intel PRO/Wireless 2011 Intersil Prism II Linksys Instant Wireless WPC11 Linksys Instant Wireless WPC11 2.5 Linksys Instant Wireless WPC11 3.0 Lucent WaveLAN NANOSPEED ROOT-RZ2000 NEC CMZ-RT-WP Netgear MA401 Netgear MA401RA Nokia C020 Wireless LAN Nokia C110/C111 Wireless LAN NTT-ME 11Mbps Wireless LAN Planex GW-NS11H Wireless LAN Proxim Harmony Proxim RangeLAN-DS Samsung MagicLAN SWL-2000N SMC 2632 EZ Connect Symbol Spectrum24 TDK LAK-CD011WL US Robotics 2410 US Robotics 2445 Intersil PRISM 2-3 and Symbol Spectrum24 based PCI IEEE 802.11b adapters [A] [B] 3Com AirConnect 3CRWE777A Belkin F5D6000 PCI (a rebadged WL11000P) Corega CGWLPCIA11 Eumitcom WL11000P D-Link DWL-520 revisions A and B Global Sun Technology GL24110P (untested) Global Sun Technology GL24110P02 Intersil Mini-PCI LinkSys WDT11 (a rebadged GL24110P02) NDC/Sohoware NCP130 Netgear MA301 Netgear MA311 US Robotics 2415 (rebadged WL11000P) Nortel E-mobility 211818-A Symbol LA4123 Intersil PRISM 2.5/3 based USB IEEE 802.11b adapters [A] [B] Acer Warplink USB-400 Actiontec HWU01170 AirVast WM168b Ambit WLAN Apacer Wireless Steno MB112 ASUS WL-140 Compaq W100 Corega WLUSB-11 Corega WLUSB-11 Key D-Link DWL-120 (rev F) D-Link DWL-122 I-O DATA WN-B11/USB Intel PRO/Wireless 2011B Intersil Prism 2X JVC MP-XP7250 Linksys WUSB11 v3.0 Linksys WUSB12 Melco WLI-USB-KB11 Melco WLI-USB-KS11G Melco WLI-USB-S11 Microsoft MN510 Netgear MA111 (version 1) Pheenet WL-503IA Planex GW-US11H Siemens SpeedStream SS1022 Sitecom WL-022 Syntax USB-400 US Robotics 1120 Z-Com XI-725/726 Z-Com XI-735 ZyXEL ZyAIR B-200 Ralink RT2500 based CardBus IEEE 802.11b/g adapters [A] [B] A-Link WL54PC Amigo AWI-914W AMIT WL531C ASUS WL-107G Atlantis Land A02-PCM-W54 Belkin F5D7010 v2 Canyon CN-WF513 CC&C WL-2102 CNet CWC-854 Compex WL54G Conceptronic C54RC Digitus DN-7001G-RA E-Tech WGPC02 Edimax EW-7108PCg Eminent EM3036 Encore ENPWI-G-RLAM Fibreline WL-400X Gigabyte GN-WMKG Hawking HWC54GR JAHT WN-4054P MSI CB54G2 Pro-Nets CB80211G Repotec RP-WB7108 SATech SN-54C Sitecom WL-112 SparkLAN WL-685R Surecom EP-9428-g Surecom EP-9428-g Sweex LC500050 TekComm NE-9428-g Unex MR054g-R02 Zinwell ZWX-G160 Zonet ZEW1500 Ralink RT2500 based PCI IEEE 802.11b/g adapters [A] [B] A-Link WL54H Amigo AWI-922W mini-PCI Amigo AWI-926W AMIT WL531P AOpen AOI-831 ASUS WL-130g ASUS WIFI-G-AAY Atlantis Land A02-PCI-W54 Belkin F5D7000 v3 Billionton MIWLGRL mini-PCI Canyon CN-WF511 CNet CWP-854 Compex WLP54G Conceptronic C54Ri Digitus DN-7006G-RA E-Tech WGPI02 Edimax EW-7128g Eminent EM3037 Encore ENLWI-G-RLAM Fiberline WL-400P Gigabyte GN-WIKG mini-PCI Gigabyte GN-WPKG Hawking HWP54GR iNexQ CR054g-009 (R03) JAHT WN-4054PCI LevelOne WNC-0301 v2 Linksys WMP54G v4 Micronet SP906GK Minitar MN54GPC-R MSI MP54G2 mini-PCI MSI PC54G2 OvisLink EVO-W54PCI PheeNet HWL-PCIG/RA Pro-Nets PC80211G Repotec RP-WP0854 SATech SN-54P Sitecom WL-115 Surecom EP-9321-g Surecom EP-9321-g1 Sweex LC700030 TekComm NE-9321-g Unex CR054g-R02 Zinwell ZWX-G360 mini-PCI Zinwell ZWX-G361 Zonet ZEW1600 Ralink RT2500 based USB 2.0 IEEE 802.11b/g adapters [A] [B] AMIT WL532U ASUS WL-167g Buffalo WLI-U2-KG54-AI CNet CWD-854 Compex WLU54G Conceptronic C54RU D-Link DWL-G122 (b1) E-Tech WGUS02 Gigabyte GN-WBKG Linksys WUSB54G v4 Linksys WUSB54GP v4 MSI MS-6861 MSI MS-6865 MSI MS-6869 Repotec RP-WU0402 Surecom EP-9001-g Zinwell ZWX-G261 Raytheon Raylink PCMCIA IEEE 802.11 FH adapters [A] [B] [C] Realtek RTL8180L based CardBus IEEE 802.11b adapters [A] [B] Belkin F5D6020 V3 Corega CG-WLCB11V3 D-Link DWL-610 Level-One WPC-0101 Linksys WPC11 v4 Netgear MA521 Ovislink AirLive WL-1120PCM Planet WL-3553 TrendNET TEW-266PC VCTnet PC-11B1 Gigabit Ethernet Adapters 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 and i82547 based adapters, including: 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) 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 Broadcom BCM570x (Tigon3) based PCI adapters, including: [A] [B] [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 NC7760 embedded Gigabit NIC HP ProLiant NC7770 PCI-X Gigabit NIC HP ProLiant NC7781 embedded PCI-X Gigabit NIC IBM xSeries 235 integrated BCM5703X NIC IBM xSeries 305 integrated BCM5703X NIC Netgear GA302T SysKonnect SK-9D21 SysKonnect SK-9D41 Realtek 8169/8169S/8110S based PCI adapters, including: Buffalo LGY-PCI-GT (8169S) Corega CG-LAPCIGT (8169S) Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S) PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S) 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) 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] AMD 768 and 8111 AC'97 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 Intel i810/i820 and 440MX AC'97 NeoMagic 256AV/ZX nVidia nForce and nForce AC'97 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 VT82C686A, VT8233, VT8235, VT8237 SouthBridge integrated AC'97 audio 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, 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 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] National Semiconductor LM75, LM77, LM78, LM78-J, LM79 National Semiconductor PC87366 LPC Super I/O VLM and TMS Winbond W83697HF, W83627HF, W83627THF, W83781D, W83782D VIA VT82C686A, VT8231 ITE IT8705F, IT8712F SiS SiS950 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 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 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 pccom0 0x3f8 4 [8250/16450/16550/clones] pccom1 0x2f8 3 [8250/16450/16550/clones] pccom2 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. Special care for PCI BIOS: As with all BIOS implementations and subsystems this one has bugs too. Sometimes specifications are unclear about interfaces and/or data validation. These all cause our driver for PCI BIOS to misbehave in more or less fatal ways, such as panics on pcibios0 configuration or PCI device attachments, or unconfigured PCI devices due to IRQ and/or I/O address misconfiguration. Fast workaround Boot by giving the -c flag to the initial boot request. Following the loading of the kernel, the user is presented with a UKC> Then type the following commands: UKC> change bios0 165 bios0 at mainbus0 bus -1 flags 0x0 change [n] y bus [-1] ? flags [0] ? 3 165 bios0 changed 165 bios0 at mainbus0 bus -1 flags 0x3 UKC> quit This will disable the pcibios0 attachment. Sometimes, especially when hangs occur on particular PCI device attachments, moving PCI cards into a different slot helps. Fixing for good Try to gather dmesg output from the failing configuration, for example by using a serial console (see boot(8)), and send it to along with descriptions of your hardware setup. Alternatively, dig in the code and fix problems. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM FFS partitions (for upgrades only) DOS (FAT) partitions (for upgrades only) EXT2 partitions (for upgrades only) 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 3.7/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 "floppy37.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 cksum(1) or md5(1) commands to verify the checksums of the images vs. the values in the CKSUM or MD5 files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. The command would likely be, under SunOS: dd if=floppy37.fs of=/dev/rfd0c bs=36b and, under Solaris: dd if=floppy37.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=floppy37.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 man37.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 misc xbase xetc xfont xserv xshare do dd if=${file}37.tgz of=${TAPE} obs=8k conv=sync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../3.7/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 "base37" 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 DOS or the other operating systems installed on your disk. If you do not, it will be much harder to make OpenBSD properly coexist with them. Utilities exist which will print out the disk geometry which DOS sees; some versions of DOS "fdisk" also do this. If you have an "EIDE" hard disk, DOS and OpenBSD probably won't see the same geometry, and you must be careful to find out the DOS geometry and tell OpenBSD about it during the installation. Third (but related to the second point above), if you are using a hard disk with more sectors than DOS or your controller's BIOS supports without some kind of software translation utility or other kludge, you MUST BE SURE that all partitions which you want to boot from must start and end below cylinder 1024 by the BIOS's idea of the disk, and that all DOS partitions MUST EXIST ENTIRELY BELOW cylinder 1024, or you will either not be able to boot OpenBSD, not be able to boot DOS, or you may experience data loss or filesystem corruption. Be sure you aren't using geometry translation that you don't know about, but that the DOS "fdisk" program does! The OpenBSD root partition must also reside completely within the BIOS supported part of the hard disk -- this would typically be 504MB, 2GB, 8GB or 128GB, depending upon the age of the machine and its BIOS. 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. 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. Before you begin, you should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The OpenBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) 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. 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. 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 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 disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you will need your disk's geometry when creating OpenBSD partitions. 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. You will next be asked for your terminal type. You should just hit return to select the default (vt220). After entering the terminal type 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. You will be presented with a welcome message and asked if you really wish to install (or upgrade). Assuming you answered yes, the install program will then tell you which disks of that type it can install on, and ask you which it should use. The name of the disk is typically "sd0" for SCSI drives. Reply with the name of your disk. Next you will have to edit or create a disk label for the disk OpenBSD is being installed on. If there are any existing partitions defined (for any operating system), and a disk label is not found, you will first be given an opportunity to run fdisk and create an OpenBSD partition. If fdisk is being invoked on your behalf, it will start by displaying the current partitions defined and then allow you to modify this information, add new partitions, and change which partition to boot from by default. If you make a mistake, you will be allowed to repeat this procedure as necessary to correct this. Note that you should make OpenBSD be the active partition at least until the install has been completed. Next the disk label which defines the layout of the OpenBSD file systems must be set up. The installation script will invoke an interactive editor allowing you to do this. Note that partition 'c' inside this disk label should ALWAYS reflect the entire disk, including any non-OpenBSD portions. If you are labeling a new disk, you will probably start out with an 'a' partition that spans the disk. In this case you should delete 'a' before adding new partitions. The root file system should be in partition 'a', and swap is usually in partition 'b'. If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'h', 'i' and so on. It is recommended that you create separate partitions for /usr, /tmp, and /var, and if you have room for it, one for /home. In doing this, remember to skip 'c', leaving it as type "unused". For help in the disk label editor, enter '?' or 'M' to view the manual page (see the info on the ``-E'' flag). Note that all OpenBSD partitions in the disk label must have an offset that makes it start within the OpenBSD part of the disk, and a size that keeps it inside of that portion of the disk. This is within the bounds of the 'c' partition if the disk is not being shared with other operating systems, and within the OpenBSD fdisk partition if the disk is being shared. The swap partition (usually 'b') should have a type of "swap", all other native OpenBSD partitions should have a type of "4.2BSD". Block and fragment sizes are usually 8192 and 1024 bytes, but can also be 4096 and 512 or even 16384 and 2048 bytes. The install program will now label your disk and ask which file systems should be created on which partitions. It will auto- matically select the 'a' partition to be the root file system. Next it will ask for which disk and partition you want a file system created on. This will be the same as the disk name (e.g. "wd0") with the letter identifying the partition (e.g. "d") appended (e.g. "wd0d"). Then it will ask where this partition is to be mounted, e.g. /usr. This process will be repeated until you enter "done". At this point you will be asked to confirm that the file system information you have entered is correct, and given an opportunity to change the file system table. Next it will create the new file systems as specified, OVERWRITING ANY EXISTING DATA. This is the point of no return. After all your file systems have been created, the install program will give you 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. If you select to configure the network, the install program will ask you for the name of your system and the DNS domain name to use. Note that the host name should be without the domain part, and that the domain name should NOT include the host name part. Next the system will give you a list of network interfaces you can configure. For each network interface you select to configure, it will ask for the IP address to use, the symbolic host name to use, the netmask to use, and any interface-specific flags to set. The interface-specific flags are usually used to determine which media the network card is to use. Typically no media flags are required as autodetection normally works, but you will be prompted with a list of the acceptable media flags, and asked if you want to provide any. In doubt, do not enter any media flags; or you can refer to the manual page for your interface for the appropriate flags. After all network interfaces have been configured, the install pro- gram will ask for a default route and IP address of the primary name server to use. You will also be presented with an opportunity to edit the host table. At this point you will be allowed to edit the file system table that will be used for the remainder of the installation and that will be used by the finished system, following which the new file systems will be mounted to complete the installation. 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, tape, CD-ROM, or a local disk partition. Note that installation from floppies is not currently supported. To install via FTP: To begin an FTP install you will need the following pieces of information. Don't be daunted by this list; the defaults are sufficient for most people. 1) Proxy server URL if you are using a URL-based FTP 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 (assuming you have a proxy available to use). 2) Do you need to use active mode FTP? By default, ftp will attempt to use passive mode and fall back to an active connection if the server does not support passive mode. You only need to enable this option if you are connecting to a buggy FTP daemon that implements passive FTP incorrectly. Note that you will not be asked about active FTP if you are using a proxy. 3) The IP address (or hostname if you enabled DNS earlier in the install) of an FTP server carrying the OpenBSD 3.7 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 4) The FTP directory holding the distribution sets. The default value of pub/OpenBSD/3.7/i386 is almost always correct. 5) The login and password for the FTP account. You will only be asked for a password for non-anonymous FTP. For instructions on how to complete the installation via FTP, see the section named "Common URL installations" below. To install via HTTP: To begin an HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based 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 HTTP connections (assuming you have a proxy available to use). 2) The IP address (or hostname if you enabled DNS earlier in the install) of an HTTP server carrying the OpenBSD 3.7 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 3) The directory holding the distribution sets. There is no standard location for this; You should use the directory specified along with the server in the list of official HTTP mirror sites that you received in step 3. For instructions on how to complete the installation via HTTP, see the section named "Common URL installations" below. To install from tape: 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 provide the file number of the set that is to be extracted. Note that the file number starts at 1, which is the first file written to the tape. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction. 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". Next you will be asked which partition on the CD-ROM the distribution is to be loaded from. This is normally partition "a". Next you will have to identify the file system type that has been used to create the distribution on the CD-ROM, this can be either FFS or ISO CD9660. The OpenBSD CD-ROM distribution uses the CD9660 format. 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 "3.7/i386". For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" 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 0 through 9. 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 '/'. For instructions on how to complete the installation from a local disk partition, see the next section. Common file system installations: The following instructions are common to installations from mounted disk partitions and CD-ROMs. A list of available distribution sets will be listed. You may individually select distribution sets to install or enter `all' to install all of the sets (which is what most users will want to do). You may also enter `list' to get a file list or `done' when you are done selecting distribution sets. You may also use wildcards in place of a file name, e.g. `*.tgz' or even `base*|comp*'. It is also possible to enter an arbitrary filename and have it treated as a file set. Once you have selected the file sets you want to install and entered `done' you will be prompted to verify that you really do want to extract file sets. Assuming you acquiesce, the files will begin to extract. If not, you will be given the option of installing sets via one of the other install methods. Common URL installations: Once you have entered the required information, the install program will fetch a file list and present a list of all the distribution sets that were found in the specified directory. (If no valid sets were found, you will be notified and given the option of unpacking any gzipped tar files found or getting a file list if none were found.) At this point you may individually select distribution sets to install or enter `all' to install all of the sets (which is what most users will want to do). You may also enter `list' to get a file list or `done' when you are done selecting distribution sets. You may also use wildcards in place of a file name, e.g. `*.tgz' or even `base*|comp*'. It is also possible to enter an arbitrary filename and have it treated as a file set. Once you have selected the file sets you want to install and entered `done' you will be prompted to verify that you really do want to download and install the files. Assuming you acquiesce, the files will begin to download and unpack. If not, you will be given the option of installing sets via one of the other install methods. When all the selected distribution sets has been extracted, you will be allowed to select which time zone your system will be using, all the device nodes needed by the installed system will be created for you, and the file systems will be unmounted. For this to work properly, it is expected that you have installed at least the "base37", "etc37", and "bsd" distribution sets. Congratulations, you have successfully installed OpenBSD 3.7. 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. You should have got a mail from the install program we recommend you to read, it contains answers to basic questions you might have about OpenBSD (like setting up your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more). This you can do by running 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 3.7 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 3.7 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. To upgrade OpenBSD 3.7 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. 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 the ``etc37.tgz'' set, 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 etc37.tgz set in a temporary directory and merge changes by hand, 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, CTM, CVSync or FTP. For more information, see http://www.OpenBSD.org/anoncvs.html http://www.OpenBSD.org/ctm.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) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. 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) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. 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 3.7/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/3.7/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/3.7/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/3.7/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/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 tinker with the FreeBSD ports or NetBSD pkgsrc. It is also quite possible that the FreeBSD binary packages, if they exist, will work for you. Note that you will need to enable FreeBSD binaries emulation with sysctl(8) and set up a complete emulation environment. Refer to the compat_freebsd(8) manual page for more information about this. 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 at http://www.OpenBSD.org/porting.html 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. 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 Use of 'sendbug' is encouraged, however, because bugs reported with it are entered into the OpenBSD bugs database, and thus can't slip through the cracks. 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