OpenBSD/i386 2.1 runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems with 386-family processors, with or without math coprocessors. It does NOT support MCA systems, such as some IBM PS/2 systems. The minimal configuration is said to require 4M of RAM and 50M of disk space, though we do not know of anyone running with a system quite this minimal today. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (4M of RAM will actually allow you to run X and/or compile, but it won't be speedy. Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU.) Supported devices include: Floppy controllers. MFM, ESDI, IDE, and RLL hard disk controllers. SCSI host adapters: Adaptec AHA-154xA, -B, -C, and -CF Adaptec AHA-174x Adaptec AIC-6260 and AIC-6360 based boards, including 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 AHA-294x[W] cards and some onboard PCI designs using the AIC7870 chip. This driver does *not* currently work with non-PCI AIC-7xxx boards or the Adaptec 3940. Buslogic 54x (Adaptec AHA-154x clones; driver on kcadp floppy) BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series of BusLogic SCSI adapters) Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters Ultrastor 14f, 34f, and (possibly) 24f Seagate/Future Domain ISA SCSI adapter cards, including ST01/02 Future Domain TMC-885 Future Domain TMC-950 MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not all of the display adapters OpenBSD/i386 can work with are supported by X. See the XFree86 FAQ for more information.) Serial ports: 8250/16450-based ports 16550-based ports AST-style 4-port serial boards [*] BOCA 8-port serial cards [*] Cyclades Cyclom-{4, 8, 16}Y serial boards [*] IBM PC-RT 4-port serial boards [*] Parallel ports. Ethernet adapters: AMD LANCE and PCnet-based ISA Ethernet adapters [*], including: Novell NE1500T Novell NE2100 Kingston 21xx AMD PCnet-based PCI Ethernet adapters, including: BOCALANcard/PCI AT&T StarLAN 10, EN100, and StarLAN Fiber 3COM 3c501 3COM 3c503 3COM 3c505 [*] 3COM 3c507 3COM 3c509, 3c579, 3c589, 3c59x and 3c9xx Digital DC21x4x-based PCI Ethernet adapters, including: SMC EtherPower 10, 10/100 (PCI only!) Znyx ZX34X Cogent EM100 Digital DE450 Digital DE500 BICC Isolan [* and not recently tested] Intel EtherExpress 16 SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [X SEE BELOW] Novell NE1000, NE2000 Digital DEFPA PCI FDDI adapters Tape drives: Most SCSI tape drives QIC-02 and QIC-36 format (Archive- and Wangtek- compatible) tape drives [*] [+] CD-ROM drives: Mitsumi CD-ROM drives [*] [+] [Note: The Mitsumi driver device probe is known to cause trouble with several devices!] Most SCSI CD-ROM drives Mice: "Logitech"-style bus mice [*] [+] "Microsoft"-style bus mice [*] [+] "PS/2"-style mice [*] [+] Serial mice (no kernel support necessary) Sound Cards: SoundBlaster [*] [+] Gravis Ulrasound and Ultrasound Max [*] [+] [The following drivers are not extensively tested] Personal Sound System [*] [+] Windows Sound System [*] [+] ProAudio Spectrum [*] [+] Miscellaneous: Drivers for hardware marked with "[*]" are NOT included on the distribution floppies. Except as noted above, all other drivers are present on both kernel-copy disks. Also, at the present time, the distributed kernels support only one SCSI host adapter per machine. OpenBSD normally allows more, though, so if you have more than one, you can use all of them by compiling a custom kernel once OpenBSD is installed. Support for devices marked with "[+]" IS included in the "generic" kernels, although it is not in the kernel on the installation floppy. Hardware the we do NOT currently support, but get many questions about: Adaptec AIC-7770-based SCSI host adapters (including the Adaptec AHA-274x, AHA-284x families). NCR 5380-based SCSI host adapters. APM power management -- if your system supports it, turn it off! QIC-40 and QIC-80 tape drives. (Those are the tape drives that connect to the floppy disk controller.) WD-7000 SCSI host adapters. PCI-PCI bridges and cards which include them, such as the AHA-394x SCSI host adapter and some DC21x4x-based multi-Ethernet cards. Multiprocessor Pentium and Pentium Pro systems. (Though they should run fine using one processor only.) Intel EtherExpress 100 Fast Ethernet adapters. We are planning future support for many of these devices. To be detected by the distributed kernels, the devices must be configured as follows: 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] 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 AHA-174x SCSI host adapters (in enhanced mode) ahb0 any any any BT445, BT74x, or BT9xx SCSI host adapters bt0 0x330 any any Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters uha0 0x330 any any AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters aic0 0x340 11 6 Symbios Logic/NCR 53C8xx based PCI SCSI host adapters ncr0 any any any 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, 3c503, Novell NE1000, or NE2000 Ethernet boards ed0 0x280 2 iomem 0xd0000 ed1 0x250 2 iomem 0xd8000 ed2 0x300 10 iomem 0xcc000 [X SEE BELOW] 3COM 3c509, 3c579, 3c595 Ethernet boards (the 3c590 has problems) ep0 any any AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards ie0 0x360 7 iomem 0xd0000 PCNet-PCI based Ethernet boards; see above for partial list le0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] DC21x4x based Ethernet boards; see above for partial list de0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] SPECIAL CARE FOR SMC ULTRA ELITE -------------------------------- Note for SMC Elite Ultra ethernet card users: The Elite Ultra is very sensitive to how it's i/o port is treated. Mistreating it can cause a number of effects -- everything from the card not responding when the kernel probes, or the soft configuration being corrupted or wiped completely. By default, the kernel ships with device ed2 configured for the 'default' Elite Ultra locations, comprising of port 0x300, irq 10, and memory location 0xcc000. This matches a hard coded jumper on the board as well a common soft config setting. Unfortunately, the kernel's autconfiguration process (specifically, some of the devices it probes for) cause conflicts with the SMC Elite Ultra, and very often cause it to lose it's configuration and fail it's own probe. If thise happens, you must boot the computer into DOS, and run the EzSetup program available from SMC. The complete URL of which is ftp://ftp.smc.com/pub/nics/ethernet/elite_ultra/gez122.exe. This program will allow you to reconfigure and recover a card that has lost it's configuration with a minimum of hassle. In order to avoid blowing away the card, one *must* use the run-time kernel configuration system when booting the Install kernel. This is done by giving the -c flag to the initial boot request. Following the loading of the kernel, the user is presented with a UKC> prompt. At this prompt, as variety of commands may be issued, but the relevant one to getting the SMC Elite Ultra running is 'disable'. The wt0, el0, and ie1 devices all need to be disabled. This is done by typing 'disable' followed by the name of the device, i.e., 'disable wt0', and pressing return. If, for some reason, your Elite Ultra is not configured at the 'default' location the kernel is expecting it, you may also use the 'change' command in the UKC system to modify where the kernel will look for it. Typing 'change ed2' will allow you to modify those settings. Note that running the card at an i/o port of anything other then 0x300 at this point is not recommended, and is beyond the scope of this document-- by doing so you risk other device probes wreaking the havoc we are trying to avoid. When all three extra devices are disabled and any changes made, the 'quit' command will exit the UKC. The kernel should then boot, and find your Elite Ultra on device ed2.