--- title: "FreeBSD 7.2-RELEASE Hardware Notes" sidenav: download --- ++++

The FreeBSD Documentation Project

$FreeBSD: releng/7.2/release/doc/en_US.ISO8859-1/hardware/article.sgml 191519 2009-04-26 09:54:03Z blackend $

FreeBSD is a registered trademark of the FreeBSD Foundation.

AMD, Am486, Am5X86, AMD Athlon, AMD Duron, AMD Opteron, AMD-K6, Athlon, Élan, Opteron, and PCnet are trademarks of Advanced Micro Devices, Inc.

IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks of International Business Machines Corporation in the United States, other countries, or both.

Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc.

Sun, Sun Microsystems, Java, Java Virtual Machine, JavaServer Pages, JDK, JRE, JSP, JVM, Netra, Solaris, StarOffice, Sun Blade, Sun Enterprise, Sun Fire, SunOS, and Ultra are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol.


Table of Contents
1 Introduction
2 Supported Processors and System Boards
2.1 amd64
2.2 i386
2.3 ia64
2.4 pc98
2.5 powerpc
2.6 sparc64
3 Supported Devices
3.1 Disk Controllers
3.2 Ethernet Interfaces
3.3 Token Ring Interfaces
3.4 FDDI Interfaces
3.5 ATM Interfaces
3.6 Wireless Network Interfaces
3.7 Miscellaneous Networks
3.8 ISDN Interfaces
3.9 Serial Interfaces
3.10 Sound Devices
3.11 Camera and Video Capture Devices
3.12 USB Devices
3.13 IEEE 1394 (Firewire) Devices
3.14 Bluetooth Devices
3.15 Cryptographic Accelerators
3.16 Miscellaneous

1 Introduction

This document contains the hardware compatibility notes for FreeBSD 7.2-RELEASE. It lists the hardware platforms supported by FreeBSD, as well as the various types of hardware devices (storage controllers, network interfaces, and so on), along with known working instances of these devices.


2 Supported Processors and System Boards

This section provides some architecture-specific information about the specific processors and systems that are supported by each architecture.


2.1 amd64

Since mid-2003 FreeBSD/amd64 has supported the AMD64 (“Hammer”) and Intel® EM64T architecture, and is now one of the Tier-1 platforms (fully supported architecture), which are expected to be Production Quality with respects to all aspects of the FreeBSD operating system, including installation and development environments.

Note that there are two names for this architecture, AMD64 (AMD) and Intel EM64T (Extended Memory 64-bit Technology). 64-bit mode of the two architectures are almost compatible with each other, and FreeBSD/amd64 should support them both.

As of this writing, the following processors are supported:

Intel EM64T is an extended version of IA-32 (x86) and different from Intel IA-64 (Itanium) architecture, which FreeBSD/ia64 supports. Some Intel's old documentation refers to Intel EM64T as “64-bit extension technology” or “IA-32e”.

The largest tested memory configuration to date is 32GB. SMP support has been recently completed and is reasonably robust.

In many respects, FreeBSD/amd64 is similar to FreeBSD/i386, in terms of drivers supported. There may be some issues with 64-bit cleanliness in some (particularly older) drivers. Generally, drivers that already function correctly on other 64-bit platforms should work.

FreeBSD/amd64 is a very young platform on FreeBSD. While the core FreeBSD kernel and base system components are generally fairly robust, there are likely to still be rough edges, particularly with third party packages.


2.2 i386

FreeBSD/i386 runs on a wide variety of “IBM PC compatible” machines. Due to the wide range of hardware available for this architecture, it is impossible to exhaustively list all combinations of equipment supported by FreeBSD. Nevertheless, some general guidelines are presented here.

Almost all i386™-compatible processors with a floating point unit are supported. All Intel processors beginning with the 80486 are supported, including the 80486, Pentium, Pentium Pro, Pentium II, Pentium III, Pentium 4, and variants thereof, such as the Xeon and Celeron® processors. All i386-compatible AMD processors are also supported, including the Am486®, Am5x86®, K5, AMD-K6® (and variants), AMD Athlon (including Athlon-MP, Athlon-XP, Athlon-4, and Athlon Thunderbird), and AMD Duron™ processors. The AMD Élan SC520 embedded processor is supported. The Transmeta Crusoe is recognized and supported, as are i386-compatible processors from Cyrix and NexGen.

There is a wide variety of motherboards available for this architecture. Motherboards using the ISA, VLB, EISA, AGP, and PCI expansion busses are well-supported. There is some limited support for the MCA (“MicroChannel”) expansion bus used in the IBM PS/2 line of PCs.

Symmetric multi-processor (SMP) systems are generally supported by FreeBSD, although in some cases, BIOS or motherboard bugs may generate some problems. Perusal of the archives of the FreeBSD symmetric multiprocessing mailing list may yield some clues.

FreeBSD will take advantage of HyperThreading (HTT) support on Intel CPUs that support this feature. A kernel with the options SMP feature enabled will automatically detect the additional logical processors. The default FreeBSD scheduler treats the logical processors the same as additional physical processors; in other words, no attempt is made to optimize scheduling decisions given the shared resources between logical processors within the same CPU. Because this naive scheduling can result in suboptimal performance, under certain circumstances it may be useful to disable the logical processors with the the machdep.hlt_logical_cpus sysctl variable. It is also possible to halt any CPU in the idle loop with the machdep.hlt_cpus sysctl variable. The smp(4) manual page has more details.

FreeBSD will take advantage of Physical Address Extensions (PAE) support on CPUs that support this feature. A kernel with the PAE feature enabled will detect memory above 4 gigabytes and allow it to be used by the system. This feature places constraints on the device drivers and other features of FreeBSD which may be used; consult the pae(4) manpage for more details.

FreeBSD will generally run on i386-based laptops, albeit with varying levels of support for certain hardware features such as sound, graphics, power management, and PCCARD expansion slots. These features tend to vary in idiosyncratic ways between machines, and frequently require special-case support in FreeBSD to work around hardware bugs or other oddities. When in doubt, a search of the archives of the FreeBSD laptop computer mailing list may be useful.

Most modern laptops (as well as many desktops) use the Advanced Configuration and Power Management (ACPI) standard. FreeBSD supports ACPI via the ACPI Component Architecture reference implementation from Intel, as described in the acpi(4) manual page. The use of ACPI causes instabilities on some machines and it may be necessary to disable the ACPI driver, which is normally loaded via a kernel module. This may be accomplished by adding the following line to /boot/device.hints:

hint.acpi.0.disabled="1"

Users debugging ACPI-related problems may find it useful to disable portions of the ACPI functionality. The acpi(4) manual page has more information on how to do this via loader tunables.

ACPI depends on a Differentiated System Descriptor Table (DSDT) provided by each machine's BIOS. Some machines have bad or incomplete DSDTs, which prevents ACPI from functioning correctly. Replacement DSDTs for some machines can be found at the DSDT section of the ACPI4Linux project Web site. FreeBSD can use these DSDTs to override the DSDT provided by the BIOS; see the acpi(4) manual page for more information.


2.3 ia64

Currently supported processors are the Itanium® and the Itanium 2.

Supported chipsets include:

Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) configurations are supported.

Most devices that can be found in or are compatible with ia64 machines are fully supported. The notable exception is the VGA console. The FreeBSD support for VGA consoles is at this time too much based on PC hardware and not all ia64 machines have chipsets that provide sufficient PC legacy support. As such syscons(4) can not be enabled and the use of a serial console is required.


2.4 pc98

NEC PC-9801/9821 series with almost all i386-compatible processors, including 80486, Pentium, Pentium Pro, Pentium II, and variants. All i386-compatible processors by AMD, Cyrix, IBM, and IDT are also supported.

NEC FC-9801/9821 series, and NEC SV-98 series (both of them are compatible with PC-9801/9821 series) should be supported.

EPSON PC-386/486/586 series, which are compatible with NEC PC-9801 series are supported.

High-resolution mode is not supported. NEC PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in normal (PC-9801 compatible) mode only.

Although there are some multi-processor systems (such as Rs20/B20), SMP-related features of FreeBSD are not supported yet.

PC-9801/9821 standard bus (called C-Bus), PC-9801NOTE expansion bus (110pin), and PCI bus are supported. New Extend Standard Architecture (NESA) bus (used in PC-H98, SV-H98, and FC-H98 series) is not supported.


2.5 powerpc

The information for this paragraph has yet to be compiled.


2.6 sparc64

This section describes the systems currently known to be supported by FreeBSD on the UltraSPARC® platform. For background information on the various hardware designs see the Sun System Handbook.

SMP is supported on all systems with more than 1 processor.

When using the GENERIC kernel, FreeBSD/sparc64 systems not equipped with a framebuffer supported by the creator(4) (Sun™ Creator, Sun Creator3D and Sun Elite3D) or machfb(4) (Sun PGX and Sun PGX64 as well as the ATI Mach64 chips found onboard in for example Sun Blade™ 100, Sun Blade 150, Sun Ultra™ 5 and Sun Ultra 10) driver must use the serial console.

If you have a system that is not listed here, it may not have been tested with FreeBSD 7.2-RELEASE. We encourage you to try it and send a note to the FreeBSD SPARC porting mailing list with your results, including which devices work and which do not.

The following systems are fully supported by FreeBSD:

The following systems are partially supported by FreeBSD. In particular the fibre channel controllers in SBus-based systems are not supported. However, it is possible to use these with a SCSI controller supported by the esp(4) driver (Sun ESP SCSI, Sun FAS Fast-SCSI and Sun FAS366 Fast-Wide SCSI controllers).

Starting with 7.2-RELEASE, sparc64 systems based on UltraSPARC III and beyond are also supported by FreeBSD, which includes the following known working systems:

The following UltraSPARC IIIi systems are not tested but believed to be also supported by FreeBSD:


3 Supported Devices

This section describes the devices currently known to be supported by FreeBSD. Other configurations may also work, but simply have not been tested yet. Feedback, updates, and corrections to this list are encouraged.

Where possible, the drivers applicable to each device or class of devices is listed. If the driver in question has a manual page in the FreeBSD base distribution (most should), it is referenced here. Information on specific models of supported devices, controllers, etc. can be found in the manual pages.

Note: The device lists in this document are being generated automatically from FreeBSD manual pages. This means that some devices, which are supported by multiple drivers, may appear multiple times.


3.1 Disk Controllers

[amd64, i386, ia64, pc98, sparc64] IDE/ATA controllers ( ata(4) driver)

[pc98] IDE/ATA controllers (wdc driver)



[i386,ia64,amd64] Controllers supported by the aac(4) driver include:

[i386,pc98,amd64] The adv(4) driver supports the following SCSI controllers:

[i386,pc98,amd64] The adw(4) driver supports SCSI controllers including:

[i386] The aha(4) driver supports the following SCSI host adapters:

[i386] The ahb(4) driver supports the following SCSI host adapters:

The ahc(4) driver supports the following SCSI host adapter chips and SCSI controller cards:

[i386,sparc64,ia64,amd64] The ahd(4) driver supports the following:

[i386,pc98,amd64] The adapters supported by the aic(4) driver include:

[i386,pc98,amd64] Controllers supported by the amd(4) driver include:

Controllers supported by the amr(4) driver include:

[i386,amd64] The arcmsr(4) driver supports the following cards:

[i386] The adapters currently supported by the asr(4) driver include the following:

[i386,amd64] The bt(4) driver supports the following BusLogic MultiMaster “W”, “C”, “S”, and “A” series and compatible SCSI host adapters:

[i386,amd64] AMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also supported by the bt(4) driver.

[i386,ia64,amd64] Controllers supported by the ciss(4) driver include:

[pc98] The ct(4) driver supports the following adapters:

[i386,ia64,amd64] The dpt(4) driver provides support for the following RAID adapters:

Note: Booting from these controllers is supported. EISA adapters are not supported.

[sparc64] The esp(4) driver provides support for the Qlogic FAS216 and FAS408 SCSI controller chips found in a wide variety of systems and peripheral boards. This includes the Qlogic SCSI cards found in most Sun Ultra 1e and Ultra 2 machines. For Qlogic PCI SCSI host adapters, the isp(4) driver should be used in place of the esp(4) driver.

[i386,amd64] The hptiop(4) driver supports the following SAS and SATA RAID controllers:

[i386,amd64] The hptmv(4) driver supports the following ATA RAID controllers:

[i386,amd64] The hptrr(4) driver supports the following RAID controllers:

[i386] The following controllers are supported by the ida(4) driver:

[i386,ia64,amd64] Controllers supported by the iir(4) driver include:

[i386,ia64,amd64] The SRCU31 and SRCU31L can be updated via a firmware update available from Intel.

[i386,amd64] Controllers supported by the ips(4) driver include:

Cards supported by the isp(4) driver include:

[i386,ia64,amd64] The mfi(4) driver supports the following hardware:

[i386,ia64,amd64] Controllers supported by the mlx(4) driver include:

[i386,ia64,amd64] All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is always advisable to upgrade to the most recent firmware available for the controller. Compatible Mylex controllers not listed should work, but have not been verified.

Note: Booting from these controllers is supported. EISA adapters are not supported.

[i386,ia64,amd64] Controllers supported by the mly(4) driver include:

[i386,ia64,amd64] Compatible Mylex controllers not listed should work, but have not been verified.

The following controllers are supported by the mpt(4) driver:

The Ultra 320 SCSI controller chips supported by the mpt(4) driver can be found onboard on many systems including:

These systems also contain Integrated Raid Mirroring and Integrated Raid Mirroring Enhanced which this driver also supports. The SAS controller chips are also present on many new AMD/Opteron based systems, like the Sun 4100. Note that this controller can drive both SAS and SATA drives or a mix of them at the same time. The Integrated Raid Mirroring available for these controllers is poorly supported at best. The Fibre Channel controller chipset are supported by a broad variety of speeds and systems. The Apple Fibre Channel HBA is in fact the FC949ES card. This driver also supports target mode for Fibre Channel cards. This support may be enabled by setting the desired role of the core via the LSI Logic firmware utility that establishes what roles the card can take on - no separate compilation is required.

[i386,pc98,sparc64,amd64] The ncr(4) driver provides support for the following NCR/Symbios SCSI controller chips:

[i386,pc98,sparc64,amd64] The following add-on boards are known to be supported:

[i386,pc98] The following devices are currently supported by the ncv(4) driver:

[i386,pc98] Controllers supported by the nsp(4) driver include:

[i386] The pst(4) driver supports the Promise Supertrak SX6000 ATA hardware RAID controller.

[i386,pc98] Controllers supported by the stg(4) driver include:

[i386,pc98] Note that the Adaptec 2920C is supported by the ahc(4) driver.

The sym(4) driver provides support for the following Symbios/LSI Logic PCI SCSI controllers:

The SCSI controllers supported by sym(4) can be either embedded on a motherboard, or on one of the following add-on boards:

[i386,amd64] SCSI controllers supported by the trm(4) driver include:

[i386,amd64] For the Tekram DC-310/U and DC-390F/U/UW/U2B/U2W/U3W PCI SCSI host adapters, use the sym(4) driver.

[i386,amd64] The twa(4) driver supports the following SATA RAID controllers:

[i386,amd64] The twe(4) driver supports the following PATA/SATA RAID controllers:

[i386] The vpo(4) driver supports the following parallel to SCSI interfaces:

[i386] The wds(4) driver supports the WD7000 SCSI controller.

With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, 8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM drives. WORM devices that support CD-ROM commands are supported for read-only access by the CD-ROM drivers (such as cd(4)). WORM/CD-R/CD-RW writing support is provided by cdrecord(1), which is a part of the sysutils/cdrtools port in the Ports Collection.

The following CD-ROM type systems are supported at this time:



[i386] The following device is unmaintained:




3.2 Ethernet Interfaces

The ale(4) device driver provides support for the following Ethernet controllers:

[i386,pc98,ia64,amd64,powerpc] Adapters supported by the aue(4) driver include:

[i386,pc98,amd64,powerpc] The axe(4) driver supports ASIX Electronics AX88172/AX88178/AX88772 based USB Ethernet adapters including: AX88172:

[i386,pc98,amd64,powerpc] AX88178:

[i386,pc98,amd64,powerpc] AX88772:

[i386,amd64] The bce(4) driver provides support for various NICs based on the Broadcom NetXtreme II family of Gigabit Ethernet controllers, including the following:

[amd64, i386] Broadcom BCM4401 based Fast Ethernet adapters ( bfe(4) driver)

[i386,pc98,sparc64,ia64,amd64] The bge(4) driver provides support for various NICs based on the Broadcom BCM570x family of Gigabit Ethernet controller chips, including the following:

[i386,pc98,ia64,amd64,powerpc] The following devices are supported by the cdce(4) driver:

[amd64, i386] Crystal Semiconductor CS89x0-based NICs (cs(4) driver)

[i386,pc98,ia64,amd64,powerpc] The cue(4) driver supports CATC USB-EL1210A based USB Ethernet adapters including:

[i386,amd64] The cxgb(4) driver supports 10 Gigabit and 1 Gigabit Ethernet adapters based on the T3 and T3B chipset:

The dc(4) driver provides support for the following chipsets:

The following NICs are known to work with the dc(4) driver at this time:

[i386,pc98,ia64,amd64] Adapters supported by the de(4) driver include:

[i386,pc98] The ed(4) driver supports the following Ethernet NICs:

[i386,pc98] C-Bus, ISA, PCI and PC Card devices are supported.

The em(4) driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572, 82573, and 82574 controller chips:

[i386,pc98,amd64] The ep(4) driver supports Ethernet adapters based on the 3Com 3C5x9 Etherlink III Parallel Tasking chipset, including:

[i386,amd64] The ex(4) driver supports the following Ethernet adapters:

[i386,pc98,amd64] Controllers and cards supported by the fe(4) driver include:

Adapters supported by the fxp(4) driver include:

Chips supported by the gem(4) driver include:

The following add-on cards are known to work with the gem(4) driver at this time:

The hme(4) driver supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server models. Cards supported by the hme(4) driver include:

[i386] The ie(4) driver provides supports the following 8 and 16bit ISA Ethernet cards that are based on the Intel i82586 chip:

The igb(4) driver supports Gigabit Ethernet adapters based on the Intel 82575 and 82576 controller chips:

[i386,amd64] The ixgb(4) driver supports the following cards:

[i386,pc98,ia64,amd64,powerpc] The kue(4) driver supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:

[i386,pc98,amd64] Adapters supported by the lge(4) driver include:

[i386,amd64] The msk(4) driver provides support for various NICs based on the Marvell/SysKonnect Yukon II based Gigabit Ethernet controller chips, including:

[i386,amd64] The mxge(4) driver supports 10 Gigabit Ethernet adapters based on the Myricom LANai Z8E chips:

[i386,pc98] The my(4) driver provides support for various NICs based on the Myson chipset. Supported models include:

[i386,amd64] The nfe(4) driver supports the following NVIDIA MCP onboard adapters:

[i386,pc98,amd64] The nge(4) driver supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters including:

[i386,amd64] The nve(4) driver supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets:

[i386,amd64] The nxge(4) driver supports Neterion Xframe 10 Gigabit Ethernet adapters listed in http://www.neterion.com/how/pricing.html.

[i386,pc98,ia64,amd64] The pcn(4) driver supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:

The re(4) driver supports RealTek RTL8139C+, RTL8169, RTL816xS, RTL811xS, and RTL8101E based Fast Ethernet and Gigabit Ethernet adapters including:

Adapters supported by the rl(4) driver include:

[i386,pc98,amd64] The rue(4) driver supports RealTek RTL8150 based USB Ethernet adapters including:

Adapters supported by the sf(4) driver include:

[i386,pc98,ia64,amd64] The sis(4) driver supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and embedded controllers, as well as Fast Ethernet adapters based on the National Semiconductor DP83815 (MacPhyter) and DP83816 chips. Supported adapters include:

[i386,sparc64,pc98,amd64] Adapters supported by the sk(4) driver include:

[i386,amd64] The sn(4) driver supports SMC91Cxx based ISA and PCMCIA cards including:

[i386,amd64] The sn(4) driver supports the SMC 91C90, SMC 91C92, SMC 91C94, SMC 91C95, SMC 91C96, SMC91C100 and SMC 91C100FD chips from SMC. The Farallon EtherWave and EtherMac card came in two varieties. The ep(4) driver supports the 595 and 895 cards. These cards have the blue arrow on the front along with a 3Com logo. The Farallon 595a cards, which have a red arrow on the front, are also called EtherWave and EtherMac. They are supported by the sn(4) driver.

[pc98] The snc(4) driver supports the following cards:

[pc98] The snc(4) driver also includes support for the National Semiconductor NS46C46 as 64 * 16 bits Microwave Serial EEPROM.

[i386,pc98,amd64] The ste(4) driver supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded controllers including:

[i386,amd64,sparc64] The stge(4) driver provides support for various NICs based on the Sundance/Tamarack TC9021 based Gigabit Ethernet controller chips, including:

[i386,pc98,amd64,sparc64] The ti(4) driver supports Gigabit Ethernet adapters based on the Alteon Tigon I and II chips. The ti(4) driver has been tested with the following adapters:

[i386,pc98,amd64,sparc64] The following adapters should also be supported but have not yet been tested:

[i386,pc98,amd64] The tl(4) driver supports Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large number of Compaq PCI Ethernet adapters. Also supported are:

[i386,pc98,amd64] The tl(4) driver also supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq Deskpro desktop machines including:

[amd64, i386, pc98] SMC 83c17x (EPIC)-based Ethernet NICs (tx(4) driver)

[i386,pc98,ia64,amd64] The txp(4) driver supports the following cards:

[i386,pc98,amd64] The udav(4) driver supports the following adapters:

[i386,pc98,amd64] The vge(4) driver supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including:

[i386,pc98,amd64] The vr(4) driver supports VIA Technologies Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters including:

[i386,pc98,ia64,amd64] The vx(4) driver supports the following cards:

[i386,pc98,amd64] The wb(4) driver supports Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:

[i386,amd64] The xe(4) driver supports the following cards:

[i386,amd64] Other similar devices using the same hardware may also be supported.

The xl(4) driver supports the following hardware:

Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a built-in proprietary modem. Neither the xl(4) driver nor any other driver supports this modem.


3.3 Token Ring Interfaces

[i386] The oltr(4) driver supports the following ISA based Olicom Token Ring adapters:

[i386] The following PCI based adapters are supported:


3.4 FDDI Interfaces

[i386, pc98] DEC DEFPA PCI ( fpa(4) driver)

arch="i386">DEC DEFEA EISA ( fpa(4) driver)


3.5 ATM Interfaces

[i386, pc98] Midway-based ATM interfaces (en(4) driver)

[i386, pc98, sparc64] FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and fatm(4) drivers)

[i386, pc98] IDT NICStAR 77201/211-based ATM Adapters ( idt(4) driver)

[i386, pc98, sparc64] FORE Systems, Inc. HE155 and HE622 ATM interfaces ( hatm(4) driver)

[i386, pc98] IDT77252-based ATM cards ( patm(4) driver)


3.6 Wireless Network Interfaces

[amd64, i386, pc98] Cisco/Aironet 802.11b wireless adapters (an(4) driver)

[i386,pc98,amd64,sparc64] The ath(4) driver supports all Atheros Cardbus or PCI cards, except those that are based on the AR5005VL chipset. A list of cards that are supported can be found at http://customerproducts.atheros.com/customerproducts/default.asp.

[i386,pc98,amd64] Cards supported by the awi(4) driver include:

[i386,pc98,amd64] The original Xircom Netwave AirSurfer is supported by the cnw(4) driver.

[i386,pc98,amd64] Cards supported by the cnw(4) driver include:

[i386, amd64] Intel PRO/Wireless 2100 MiniPCI network adapter ( ipw(4) driver)

[i386, amd64] Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters ( iwi(4) driver)

[i386,amd64] The ral(4) driver supports PCI/CardBus wireless adapters based on the Ralink Technology RT2500, RT2501, and RT2600 chipsets, including:

[i386,amd64] An up to date list can be found at http://damien.bergamini.free.fr/ral/list.html.

[i386, pc98] Raytheon Raylink 2.4GHz wireless adapters ( ray(4) driver)

[i386,amd64] The rum(4) driver supports USB 2.0 and PCI Express Mini Card wireless adapters based on the Ralink RT2501USB and RT2601USB chipsets, including:

[i386,amd64] The ural(4) driver supports USB 2.0 wireless adapters based on the Ralink Technology RT2500USB chipset, including:

[i386,amd64] An up to date list can be found at http://ralink.rapla.net/.

[amd64, i386, pc98] Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24 chipsets (wi(4) driver)

[i386] NCR / AT&T / Lucent Technologies WaveLan T1-speed ISA/radio LAN cards (wl(4) driver)

[i386, amd64] Intel PRO/Wireless 3945ABG MiniPCI network adapters ( wpi(4) driver)

[i386,amd64] The following devices are known to be supported by the zyd(4) driver:


3.7 Miscellaneous Networks

[i386,pc98] The ce(4) driver supports the following models of Tau-PCI/32 WAN adapters:

[i386] The cx(4) driver supports the following cards:

[i386,pc98] The cp(4) driver supports the following models of Tau-PCI WAN adapters:

[i386] The ctau(4) driver supports the following cards:

[i386] Granch SBNI12 point-to-point communications adapters ( sbni(4) driver)

[i386] Granch SBNI16 SHDSL modems ( sbsh(4) driver)

[i386] The cm(4) driver supports the following card models:


3.8 ISDN Interfaces

[i386] AcerISDN P10 ISA PnP (experimental)

[i386] Asuscom ISDNlink 128K ISA

[i386] ASUSCOM P-IN100-ST-D (and other Winbond W6692-based cards)

[i386] AVM



[i386] Creatix



[i386] Compaq Microcom 610 ISDN (Compaq series PSB2222I) ISA PnP

[i386] Dr. Neuhaus Niccy Go@ and compatibles

[i386] Dynalink IS64PPH and IS64PPH+

[i386] Eicon Diehl DIVA 2.0 and 2.02

[i386] ELSA



[i386] ITK ix1 Micro ( < V.3, non-PnP version )

[i386] Sedlbauer Win Speed

[i386] Siemens I-Surf 2.0

[i386] TELEINT ISDN SPEED No.1 (experimental)

[i386] Teles



[i386] Traverse Technologies NETjet-S PCI

[i386] USRobotics Sportster ISDN TA intern

[i386] Winbond W6692 based PCI cards


3.9 Serial Interfaces

[amd64, i386] “PC standard” 8250, 16450, and 16550-based serial ports ( sio(4) driver)

The uart(4) driver supports the following classes of UARTs:

The scc(4) driver supports the following classes of SCCs:

[amd64, i386] AST 4 port serial card using shared IRQ

[i386] ARNET serial cards (ar(4) driver)



[i386] Boca multi-port serial cards



[i386] Comtrol Rocketport card (rp(4) driver)

[i386] Cyclades Cyclom-Y serial board (cy(4) driver)

[i386] STB 4 port card using shared IRQ

[i386] DigiBoard intelligent serial cards (digi driver)

[amd64, i386, ia64] PCI-Based multi-port serial boards ( puc(4) driver)



[i386] The rc(4) driver provides support for the SDL Communications RISCom/8 boards.

[i386] The sr(4) driver supports the following hardware:

[i386, amd64] Specialix SI/XIO/SX multiport serial cards, with both the older SIHOST2.x and the “enhanced” (transputer based, aka JET) host cards (ISA, EISA and PCI) are supported. Note that the newer SX+ PCI cards are not currently supported. (si(4) driver)

[pc98] Internel serial interfaces ( sio(4) driver)



[pc98] NEC PC-9861K, PC-9801-101 and Midori-Denshi MDC-926Rs ( sio(4) driver)



[pc98] NEC PC-9801-120 ( sio(4) driver)

Note: "flags 0x11000000" is necessary in kernel configuration.

[pc98] Microcore MC-16550, MC-16550II, MC-RS98 ( sio(4) driver)

Note: "flags 0x14000?01" is necessary in kernel configuration.

[pc98] Media Intelligent RSB-2000, RSB-3000 and AIWA B98-02 ( sio(4) driver)

Note: "flags 0x15000?01" is necessary in kernel configuration.

[pc98] Media Intelligent RSB-384 ( sio(4) driver)

Note: "flags 0x16000001" is necessary in kernel configuration.

[pc98] I-O DATA RSA-98III ( sio(4) driver)

Note: "flags 0x18000?01" is necessary in kernel configuration.

[pc98] Hayes ESP98 ( sio(4) driver)

Note: "options COM_ESP" and "flags 0x19000000" are necessary in kernel configuration.


3.10 Sound Devices

[i386,amd64] The snd_ad1816(4) driver supports the following sound cards:

[i386] The snd_als4000(4) driver supports the following sound cards:

[i386,amd64] The snd_atiixp(4) driver supports the following audio chipsets:

[sparc64] The snd_audiocs(4) driver supports the following audio devices:

[i386,amd64] The snd_cmi(4) driver supports the following sound cards:

[i386,amd64] The snd_cs4281(4) driver supports the following sound cards:

[i386,amd64] The snd_csa(4) driver supports the following sound cards:

[i386,amd64] Some onboard CS4610 chips are accompanied by the CS423x ISA codec instead of the CS4297 AC97 codec. Such configurations are not supported by the snd_csa(4) driver yet.

[i386,amd64] The snd_ds1(4) driver supports the following sound cards:

[i386,amd64] The snd_emu10k1(4) driver supports the following sound cards:

[i386,amd64] The snd_emu10kx(4) driver supports the following sound cards:

[i386,amd64] The snd_emu10kx(4) driver does support the following sound cards (although they have names similar to some supported ones):

[i386,amd64] The snd_envy24(4) driver supports the following audio devices:

[i386,amd64] The snd_envy24ht(4) driver supports the following audio devices:

[i386,sparc64,amd64] The snd_es137x(4) driver supports the following sound cards:

[i386,amd64] The snd_ess(4) driver supports the following sound cards:

[i386,amd64] The snd_fm801(4) driver supports audio devices based on the following chipset:

[i386,amd64] The snd_gusc(4) driver supports the following sound cards:

[i386,amd64] The snd_hda(4) driver supports many Intel HDA compatible audio chipsets including the following:

[i386,amd64] The following and many other codecs have been verified to work:

[i386,amd64] The snd_ich(4) driver supports the following audio devices:

[i386,amd64] The snd_maestro(4) driver supports the following PCI sound cards:

[i386,amd64] The snd_maestro3(4) driver supports the following audio devices:

[i386] The snd_mss(4) driver supports the following audio devices:

[i386,amd64] The snd_neomagic(4) driver supports the following audio devices:

[i386,amd64] The snd_sbc(4) driver supports the following sound cards:

[i386,amd64] The snd_solo(4) driver supports the following sound cards:

[i386,amd64] Note that older ESS ISA cards with ES18xx chipset are supported via snd_ess(4) and/or snd_sbc(4).

[i386,amd64] The snd_spicds(4) driver supports the following codecs:

[i386,amd64] The snd_t4dwave(4) driver supports the following audio devices:

[i386,amd64] The snd_via8233(4) driver supports the following audio chipsets:

[i386,amd64] The snd_via82c686(4) driver supports audio devices based on the following chipset:

[i386,amd64] The snd_vibes(4) driver supports audio devices based on the following chipset:

[pc98] NEC PC-9801-73, 86 and compatibles (nss driver)



[pc98] NEC X-MATE, CanBe, ValueStar internal (mss driver)

[pc98] Creative Technologies SoundBlaster(98) (sb(4) driver)

[pc98] I-O DATA CD-BOX (sb(4) driver)

[pc98] MPU-401 and compatible interfaces (mpu driver)




3.11 Camera and Video Capture Devices

[i386,pc98] The bktr(4) driver supports video capture cards based on the Brooktree Bt848/849/878/879 chips, as well as Pinnacle PCTV cards, including:

[i386] Connectix QuickCam


3.12 USB Devices

[amd64, i386, ia64, pc98] A range of USB peripherals are supported; devices known to work are listed in this section. Owing to the generic nature of most USB devices, with some exceptions any device of a given class will be supported, even if not explicitly listed here.

Note: USB Ethernet adapters can be found in the section listing Ethernet interfaces.

Note: USB Bluetooth adapters can be found in Bluetooth section.

[i386,pc98,ia64,amd64,powerpc] The ohci(4) driver supports all OHCI v1.0 compliant controllers including:

[i386,pc98,ia64,amd64,powerpc] The uhci(4) driver supports all UHCI v1.1 compliant controllers including:

[amd64, i386, ia64, pc98] USB 2.0 controllers using the EHCI interface ( ehci(4) driver)

[amd64, i386, ia64, pc98] Hubs

[amd64, i386, ia64, pc98] Keyboards ( ukbd(4) driver)

[amd64, i386, pc98] Miscellaneous



[i386,pc98,amd64,powerpc] The following devices are supported by the urio(4) driver:

[i386,pc98,amd64] Devices supported by the umodem(4) driver include:

[amd64, i386, ia64, pc98] Mice ( ums(4) driver)

[i386,pc98,amd64,powerpc] The ulpt(4) driver provides support for USB printers and parallel printer conversion cables, including the following:

[i386,pc98,amd64] The ubsa(4) driver supports the following adapters:

[i386,pc98,amd64] The supported 3G cards provide the necessary modem port for ppp, pppd, or mpd connections; other functions of these cards (diagnostic port, SIM toolkit port, WLAN) are not supported.

[i386,pc98,amd64] The ubser(4) driver provides support for the BWCT console management serial adapters.

[i386,pc98,amd64] The uftdi(4) driver supports the following adapters:

[i386,pc98,amd64] The uplcom(4) driver supports the following adapters:

The umct(4) driver supports the following adapters:

[i386,pc98,amd64,powerpc] Because there is no standard device class for USB scanners, this driver will only recognise devices whose USB IDs are explicitly listed in the table in the driver itself. The following devices are supported to date:

[i386,pc98,amd64,powerpc] The umass(4) driver supports USB Mass Storage devices, including:

[i386,pc98,amd64,powerpc] Among the supported digital cameras are:

[amd64, i386, pc98] Audio Devices ( uaudio(4) driver)

[i386,pc98,amd64] The uvisor(4) driver supports the following devices:


3.13 IEEE 1394 (Firewire) Devices

[i386,sparc64,ia64,amd64,powerpc] The fwohci(4) driver provides support for PCI/CardBus FireWire interface cards. The driver supports the following IEEE 1394 OHCI chipsets:

[amd64, i386, sparc64] Serial Bus Protocol 2 (SBP-2) storage devices ( sbp(4) driver)


3.14 Bluetooth Devices

[i386,pc98,amd64] The ng_bt3c(4) driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.

[i386,pc98,amd64] The ng_ubt(4) driver supports all Bluetooth USB devices that conform with the Bluetooth specification v1.1, including:


3.15 Cryptographic Accelerators

[i386,pc98,amd64] The hifn(4) driver supports various cards containing the Hifn 7751, 7951, 7811, 7955, and 7956 chipsets, such as:

[i386,pc98,amd64] The safe(4) driver supports cards containing any of the following chips:

[i386,pc98,amd64] The ubsec(4) driver supports cards containing any of the following chips:


3.16 Miscellaneous

[amd64, i386, pc98] FAX-Modem/PCCARD



[amd64, i386, pc98] Floppy drives ( fdc(4) driver)

[amd64, i386] VGA-compatible video cards ( vga(4) driver)

Note: Information regarding specific video cards and compatibility with Xorg can be found at http://www.x.org/.



[amd64, i386, ia64, pc98] Keyboards including:



[amd64, i386, ia64, pc98] Pointing devices including:

Note: moused(8) has more information on using pointing devices with FreeBSD. Information on using pointing devices with Xorg can be found at http://www.x.org/.



[amd64, i386] “PC standard” parallel ports ( ppc(4) driver)

[pc98] “PC-9821 standard” parallel ports ( ppc(4) driver)

[i386, amd64] PC-compatible joysticks ( joy(4) driver)

[pc98] Joystick port of SoundBlaster(98) ( joy(4) driver)

[i386, pc98] PHS Data Communication Card/PCCARD



[i386] Xilinx XC6200-based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (xrpu driver).

[pc98] Power Management Controller of NEC PC-98 Note (pmc driver)


This file, and other release-related documents, can be downloaded from ftp://ftp.FreeBSD.org/.

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.

For questions about this documentation, e-mail <doc@FreeBSD.org>.

++++