NetBSD/i386 is the port of NetBSD to generic machines ("PC clones") with 32-bit x86-family processors. It runs on PCI-Express, PCI, and CardBus systems, as well as older hardware with PCMCIA, VL-bus, EISA, MCA, and ISA (AT-bus) interfaces, with or without math coprocessors.
NetBSD/i386 was the original port of NetBSD, and was initially released as NetBSD 0.8 in 1993.
Frank van der Linden is the current port maintainer of NetBSD/i386.
- NetBSD/i386 6.0 via FTP
- NetBSD/i386 6.0 INSTALL notes
- NetBSD/i386 6.0 pre-build binary packages from pkgsrc
- NetBSD/i386 6.0 changes
- NetBSD/i386 7.0 changes
The minimal configuration for a NetBSD/i386 system requires 4M of RAM and about 40M of disk space.
For a full installation (including source and X11), at least 8M of RAM and 200M of disk space are recommended.
Any i486 or better CPU should work - genuine Intel or a compatible such as Cyrix, AMD, or NexGen.
Devices (driver names in parenthesis) supported by NetBSD/i386 include:
- Machine-independent drivers for ISA devices
- Machine-independent drivers for PCI devices
- Machine-independent drivers for EISA devices
- Machine-independent drivers for PCMCIA devices
- Machine-independent drivers for Cardbus devices
- Machine-independent drivers for ATA devices
- Machine-independent drivers for SCSI and ATAPI devices.
- Machine-independent drivers for USB devices
- Machine-independent drivers for MII devices (IEEE 802.3 Media Independent Interface, typically used for physical media interfaces for FastEthernet controllers)
- Machine-independent drivers for MCA devices
- Standard PC floppy controllers (fdc) and drives (fd)
- Adaptec 284x VLbus SCSI host adapters (ahc)
- NCR 53C80 port-mapped and memory-mapped SCSI host adapters (nca)
- The PC speaker (pcppi and sysbeep)
- Logitech bus mouse (lms)
- Microsoft InPort mouse (mms)
- PS/2 mouse (pms)
- Joysticks on game ports (joy)
- MDA, CGA, VGA, SVGA and HGC Display Adapters (pccons or wscons).
- not all of the display adapters supported by NetBSD/i386 will work with X. See the XFree86 FAQ for more information.