From 8c1ef070bfb105c8579df77ba3d7e08c1d10d0d1 Mon Sep 17 00:00:00 2001 From: Glen Barber Date: Fri, 3 Oct 2014 01:31:26 +0000 Subject: [PATCH] Add the errata, hardware, readme, and relnotes pages for the 10.1-RELEASE, generated after branching releng/10.1. Approved by: re (implicit) Sponsored by: The FreeBSD Foundation --- .../htdocs/releases/10.1R/errata.html | 114 +++ .../htdocs/releases/10.1R/hardware.html | 345 ++++++++ .../htdocs/releases/10.1R/readme.html | 212 +++++ .../htdocs/releases/10.1R/relnotes.html | 738 ++++++++++++++++++ 4 files changed, 1409 insertions(+) create mode 100644 en_US.ISO8859-1/htdocs/releases/10.1R/errata.html create mode 100644 en_US.ISO8859-1/htdocs/releases/10.1R/hardware.html create mode 100644 en_US.ISO8859-1/htdocs/releases/10.1R/readme.html create mode 100644 en_US.ISO8859-1/htdocs/releases/10.1R/relnotes.html diff --git a/en_US.ISO8859-1/htdocs/releases/10.1R/errata.html b/en_US.ISO8859-1/htdocs/releases/10.1R/errata.html new file mode 100644 index 0000000000..deb536cfc8 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/10.1R/errata.html @@ -0,0 +1,114 @@ + +FreeBSD 10.0-RELEASE Errata

FreeBSD 10.0-RELEASE Errata

The FreeBSD Project

Copyright © 2014 The FreeBSD Documentation + Project

FreeBSD is a registered trademark of + the FreeBSD Foundation.

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, and + UltraSPARC are trademarks of SPARC International, Inc in the United + States and other countries. SPARC International, Inc owns all of the + SPARC trademarks and under licensing agreements allows the proper use + of these trademarks by its members.

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.

Last modified on 2014-09-16 by gjb.
Abstract

This document lists errata items for FreeBSD 10.0-RELEASE, + containing significant information discovered after the + release or too late in the release cycle to be otherwise + included in the release documentation. This information + includes security advisories, as well as news relating to the + software or documentation that could affect its operation or + usability. An up-to-date version of this document should + always be consulted before installing this version of + FreeBSD.

This errata document for FreeBSD 10.0-RELEASE will be + maintained until the release of FreeBSD 10.1-RELEASE.

Table of Contents
1. Introduction
2. Security Advisories
3. Open Issues
4. Late-Breaking News

1. Introduction

This errata document contains “late-breaking + news” about FreeBSD 10.0-RELEASE Before installing this + version, it is important to consult this document to learn about + any post-release discoveries or problems that may already have + been found and fixed.

Any version of this errata document actually distributed + with the release (for example, on a CDROM distribution) will be + out of date by definition, but other copies are kept updated on + the Internet and should be consulted as the “current + errata” for this release. These other copies of the + errata are located at http://www.FreeBSD.org/releases/, plus any + sites which keep up-to-date mirrors of this location.

Source and binary snapshots of FreeBSD 10.0-STABLE also + contain up-to-date copies of this document (as of the time of + the snapshot).

For a list of all FreeBSD CERT security advisories, see http://www.FreeBSD.org/security/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.

2. Security Advisories

AdvisoryDateTopic
SA-13:14.openssh19 November 2013

OpenSSH AES-GCM memory corruption + vulnerability

SA-14:01.bsnmpd14 January 2014

bsnmpd remote denial of service vulnerability

SA-14:02.ntpd14 January 2014

ntpd distributed reflection Denial of Service vulnerability

SA-14:03.openssl14 January 2014

OpenSSL multiple vulnerabilities

SA-14:04.bind14 January 2014

BIND remote denial of service vulnerability

SA-14:05.nfsserver8 April 2014

Deadlock in the NFS server

SA-14:06.openssl8 April 2014

OpenSSL multiple vulnerabilities

SA-14:07.devfs30 April 2014

Fix devfs rules not applied by default for + jails

SA-14:08.tcp30 April 2014

Fix TCP reassembly + vulnerability

SA-14:09.openssl30 April 2014

Fix OpenSSL use-after-free + vulnerability

SA-14:10.openssl15 May 2014

Fix OpenSSL NULL pointer deference + vulnerability

SA-14:11.sendmail3 June 2014

Fix sendmail improper close-on-exec flag + handling

SA-14:13.pam3 June 2014

Fix incorrect error handling in PAM policy + parser

SA-14:14.openssl5 June 2014

Multiple vulnerabilities

SA-14:15.iconv24 June 2014

NULL pointer dereference and out-of-bounds + array access

SA-14:16.file24 June 2014

Multiple vulnerabilities

SA-14:17.kmem8 July 2014

Kernel memory disclosure in control messages + and SCTP notifications

SA-14:18.openssl9 September 2014

Multiple vulnerabilities

SA-14:19.tcp16 September 2014

Denial of Service in TCP packet + processing.

3. Open Issues

  • FreeBSD/i386 10.0-RELEASE running as a guest + operating system on VirtualBox + can have a problem with disk I/O access. It depends on some + specific hardware configuration and does not depend on a + specific version of VirtualBox or + host operating system.

    It causes various errors and makes FreeBSD quite unstable. + Although the cause is still unclear, disabling unmapped I/O + works as a workaround. To disable it, choose + Escape to loader prompt in the boot menu + and enter the following lines from loader(8) prompt, + after an OK: 

    set vfs.unmapped_buf_allowed=0
+boot

    Note that the following line has to be added to + /boot/loader.conf after a boot. It + disables unmapped I/O at every boot: 

    vfs.unmapped_buf_allowed=0

    [2014-04-03 update] It has been reported that + instability may be present on virtual machines running + on other hypervisors, such as Xen or KVM.

  • A bug in Heimdal (an + implementation of Kerberos + authentication in FreeBSD base system) has been fixed. It + could cause an interoperability issue between + Heimdal and the other + implementations including MIT + Kerberos. However, due to this fix, + Heimdal and some applications + which depend on it in the previous FreeBSD releases do not work + with one in 10.0-RELEASE in certain cases. Errata Notice + for the supported releases to fix it will be + released.

  • A bug in killall(1) has been discovered. It + makes killall -INT to deliver + SIGTERM rather than the desired + SIGINT, and may cause blocking + behavior for scripts that uses it, as -I + means “interactive”. A workaround of this + would be to use -SIGINT instead. + This bug has been fixed on FreeBSD-CURRENT and will be fixed + in FreeBSD 10.0-STABLE.

  • The bxe(4) driver can cause packet corruption when + TSO (TCP Segmentation Offload) feature is enabled. This + feature is enabled by default and can be disabled by using a + -tso parameter of ifconfig(8). It can + be specified in rc.conf(5) like the following: 

    ifconfig_bxe0="DHCP -tso"

    This bug has been fixed on FreeBSD + 10.0-STABLE.

  • Due to a minor incompatibility with pkg(7) version + 1.2.x, bsdconfig(8) will duplicate + the list of available packages for installation. This is + due to the PACKAGESITE environment + variable being set for backwards compatibility with older + versions of pkg(7). This affects generation of the + available package list only, and does not affect the + behavior when processing packages for installation.

  • A regression in pw(8) does not remove a user from + groups not specified in the provided group list when the + -G flag is used. This is expected to be + corrected in FreeBSD-CURRENT and FreeBSD 10.0-STABLE.

  • ipfw(8) fwd action can send + packets to the correct interface with a wrong link-layer + address when the route is updated. This bug has been fixed + on FreeBSD-CURRENT and will be fixed in FreeBSD + 10.0-STABLE.

  • The mount_udf(8) utility has a bug which prevents + it from mounting any UDF file system. This has been fixed + in FreeBSD-CURRENT and FreeBSD 10.0-STABLE.

  • Updating LSI firmware on mps(4) controllers with + the sas2flash utility may cause + the system to hang, or may cause the system to panic. This + is fixed in the stable/10 branch with + revisions r262553 and + r262575, and will be included in + FreeBSD 10.1-RELEASE.

4. Late-Breaking News

No news.

This file, and other release-related documents, + can be downloaded from http://www.FreeBSD.org/snapshots/.

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

All users of FreeBSD 10.0-STABLE should + subscribe to the <stable@FreeBSD.org> + mailing list.

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

\ No newline at end of file diff --git a/en_US.ISO8859-1/htdocs/releases/10.1R/hardware.html b/en_US.ISO8859-1/htdocs/releases/10.1R/hardware.html new file mode 100644 index 0000000000..8c26b17ebb --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/10.1R/hardware.html @@ -0,0 +1,345 @@ + +FreeBSD 10.0-STABLE Hardware Notes

FreeBSD 10.0-STABLE Hardware Notes

The FreeBSD Documentation Project

Copyright © 2000-2014 The FreeBSD Documentation + Project

FreeBSD is a registered trademark of + the FreeBSD Foundation.

AMD, AMD Athlon, + AMD Opteron, Athlon, Élan, Opteron, and PCnet are + trademarks of Advanced Micro Devices, Inc.

Fujitsu, the Fujitsu logo, LifeBook, + Stylistic, PRIMEPOWER, PRIMEQUEST, PRIMECLUSTER, ETERNUS, TRIOLE, + ESPRIMO, BioMedCAChe, CAChe, CELLINJECTOR, isS, Materials Explorer, + SystemWalker, and Interstage are trademarks or registered trademarks + of Fujitsu Limited in the United States and other countries.

IBM, AIX, 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, and + UltraSPARC are trademarks of SPARC International, Inc in the United + States and other countries. SPARC International, Inc owns all of the + SPARC trademarks and under licensing agreements allows the proper use + of these trademarks by its members.

Sun, Sun Microsystems, Java, Java + Virtual Machine, JDK, JRE, JSP, JVM, Netra, OpenJDK, + Solaris, StarOffice, SunOS + and VirtualBox 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.

Last modified on 2014-08-26 by gjb.
Table of Contents
1. Introduction
2. Supported Processors and System Boards
3. Supported Devices

1. Introduction

This document contains the hardware compatibility notes for + FreeBSD 10.0-STABLE. 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:

  • AMD Athlon™64 (“Clawhammer”).

  • AMD Opteron™ (“Sledgehammer”).

  • All multi-core Intel® Xeon™ processors except + Sossaman have EM64T support.

  • The single-core Intel® Xeon™ processors + “Nocona”, “Irwindale”, + “Potomac”, and “Cranford” have + EM64T support.

  • All Intel® Core 2 (not Core Duo) and later + processors

  • All Intel® Pentium® D processors

  • Intel® Pentium® 4s and Celeron Ds using + the “Cedar Mill” core have EM64T + support.

  • Some Intel® Pentium® 4s and Celeron Ds using + the “Prescott” core have EM64T support. See + the Intel + Processor Spec Finder for the definitive answer + about EM64T support in Intel processors.

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”.

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

In many respects, FreeBSD/amd64 is similar to + FreeBSD/i386, in terms of drivers supported. Generally, + drivers that already function correctly on other 64-bit + platforms should work.

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 buses 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 SMT (Symmetric MultiThreading, + also known as HyperThreading on Intel® CPUs) on the supported + CPUs. The GENERIC kernel which is + installed by default will automatically detect the additional + logical processors. The default FreeBSD scheduler recognizes + processor topology on the system and selects logical and + physical processors to obtain optimal performance. + 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) manual page 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:

  • HP zx1

  • Intel® 460GX

  • Intel® E8870

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) cannot 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

All Apple PowerPC machines with built-in USB are + supported, as well a limited selection of non-Apple machines, + including KVM on POWER7

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

2.6. sparc64

This section describes the systems currently known to be + supported by FreeBSD on the Fujitsu SPARC64® and Sun + UltraSPARC® platforms.

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 10.0-STABLE. 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:

  • Naturetech GENIALstation 777S

  • Sun Blade™ 100

  • Sun Blade™ 150

  • Sun Enterprise™ 150

  • Sun Enterprise™ 220R

  • Sun Enterprise™ 250

  • Sun Enterprise™ 420R

  • Sun Enterprise™ 450

  • Sun Fire™ B100s (support for the on-board NICs first + appeared in 8.1-RELEASE)

  • Sun Fire™ V100

  • Sun Fire™ V120

  • Sun Netra™ t1 100/105

  • Sun Netra™ T1 AC200/DC200

  • Sun Netra™ t 1100

  • Sun Netra™ t 1120

  • Sun Netra™ t 1125

  • Sun Netra™ t 1400/1405

  • Sun Netra™ 120

  • Sun Netra™ X1

  • Sun SPARCEngine® Ultra AX1105

  • Sun SPARCEngine® Ultra AXe

  • Sun SPARCEngine® Ultra AXi

  • Sun SPARCEngine® Ultra AXmp

  • Sun SPARCEngine® CP1500

  • Sun Ultra™ 1

  • Sun Ultra™ 1E

  • Sun Ultra™ 2

  • Sun Ultra™ 5

  • Sun Ultra™ 10

  • Sun Ultra™ 30

  • Sun Ultra™ 60

  • Sun Ultra™ 80

  • Sun Ultra™ 450

The following systems are partially supported by FreeBSD. In + particular the fiber 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).

  • Sun Enterprise™ 3500

  • Sun Enterprise™ 4500

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

  • Sun Blade™ 1000

  • Sun Blade™ 1500

  • Sun Blade™ 2000

  • Sun Blade™ 2500

  • Sun Fire™ 280R

  • Sun Fire™ V210

  • Sun Fire™ V215 (support first appeared in 7.3-RELEASE + and 8.1-RELEASE)

  • Sun Fire™ V240

  • Sun Fire™ V245 (support first appeared in 7.3-RELEASE + and 8.1-RELEASE)

  • Sun Fire™ V250

  • Sun Fire™ V440 (support for the on-board NICs first + appeared in 7.3-RELEASE and 8.0-RELEASE)

  • Sun Fire™ V480 (501-6780 and 501-6790 centerplanes + only, for which support first appeared in 7.3-RELEASE and + 8.1-RELEASE, other centerplanes might work beginning with + 8.3-RELEASE and 9.0-RELEASE)

  • Sun Fire™ V880

  • Sun Fire™ V890 (support first appeared in 7.4-RELEASE + and 8.1-RELEASE, non-mixed UltraSPARC® IV/IV+ + CPU-configurations only)

  • Netra™ 20/Netra™ T4

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

  • Sun Fire™ V125

  • Sun Fire™ V490 (support first appeared in 7.4-RELEASE + and 8.1-RELEASE, non-mixed UltraSPARC® IV/IV+ + CPU-configurations only)

Starting with 7.4-RELEASE and 8.1-RELEASE, sparc64 + systems based on Fujitsu SPARC64® V are also supported by + FreeBSD, which includes the following known working + systems:

  • Fujitsu PRIMEPOWER® 250

The following Fujitsu PRIMEPOWER® systems are not tested + but also believed to be supported by FreeBSD:

  • Fujitsu PRIMEPOWER® 450

  • Fujitsu PRIMEPOWER® 650

  • Fujitsu PRIMEPOWER® 850

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)

  • On-board IDE controller

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

  • Adaptec AAC-364

  • Adaptec RAID 2045

  • Adaptec RAID 2405

  • Adaptec RAID 2445

  • Adaptec RAID 2805

  • Adaptec RAID 3085

  • Adaptec RAID 31205

  • Adaptec RAID 31605

  • Adaptec RAID 5085

  • Adaptec RAID 51205

  • Adaptec RAID 51245

  • Adaptec RAID 51605

  • Adaptec RAID 51645

  • Adaptec RAID 52445

  • Adaptec RAID 5405

  • Adaptec RAID 5445

  • Adaptec RAID 5805

  • Adaptec SAS RAID 3405

  • Adaptec SAS RAID 3805

  • Adaptec SAS RAID 4000SAS

  • Adaptec SAS RAID 4005SAS

  • Adaptec SAS RAID 4800SAS

  • Adaptec SAS RAID 4805SAS

  • Adaptec SATA RAID 2020SA ZCR

  • Adaptec SATA RAID 2025SA ZCR

  • Adaptec SATA RAID 2026ZCR

  • Adaptec SATA RAID 2410SA

  • Adaptec SATA RAID 2420SA

  • Adaptec SATA RAID 2610SA

  • Adaptec SATA RAID 2620SA

  • Adaptec SATA RAID 2810SA

  • Adaptec SATA RAID 2820SA

  • Adaptec SATA RAID 21610SA

  • Adaptec SCSI RAID 2020ZCR

  • Adaptec SCSI RAID 2025ZCR

  • Adaptec SCSI RAID 2120S

  • Adaptec SCSI RAID 2130S

  • Adaptec SCSI RAID 2130SLP

  • Adaptec SCSI RAID 2230SLP

  • Adaptec SCSI RAID 2200S

  • Adaptec SCSI RAID 2240S

  • Adaptec SCSI RAID 3230S

  • Adaptec SCSI RAID 3240S

  • Adaptec SCSI RAID 5400S

  • Dell CERC SATA RAID 2

  • Dell PERC 2/Si

  • Dell PERC 2/QC

  • Dell PERC 3/Si

  • Dell PERC 3/Di

  • Dell PERC 320/DC

  • HP ML110 G2 (Adaptec SATA RAID 2610SA)

  • HP NetRAID 4M

  • IBM ServeRAID 8i

  • IBM ServeRAID 8k

  • IBM ServeRAID 8s

  • ICP RAID ICP5045BL

  • ICP RAID ICP5085BL

  • ICP RAID ICP5085SL

  • ICP RAID ICP5125BR

  • ICP RAID ICP5125SL

  • ICP RAID ICP5165BR

  • ICP RAID ICP5165SL

  • ICP RAID ICP5445SL

  • ICP RAID ICP5805BL

  • ICP RAID ICP5805SL

  • ICP ICP5085BR SAS RAID

  • ICP ICP9085LI SAS RAID

  • ICP ICP9047MA SATA RAID

  • ICP ICP9067MA SATA RAID

  • ICP ICP9087MA SATA RAID

  • ICP ICP9014RO SCSI RAID

  • ICP ICP9024RO SCSI RAID

  • Legend S220

  • Legend S230

  • Sun STK RAID REM

  • Sun STK RAID EM

  • SG-XPCIESAS-R-IN

  • SG-XPCIESAS-R-EX

  • AOC-USAS-S4i

  • AOC-USAS-S8i

  • AOC-USAS-S4iR

  • AOC-USAS-S8iR

  • AOC-USAS-S8i-LP

  • AOC-USAS-S8iR-LP

Controllers supported by the aacraid(4) driver include:

  • Adaptec ASR-6405(T|E)

  • Adaptec ASR-6445

  • Adaptec ASR-6805(T|E|Q|TQ)

  • Adaptec ASR-7085

  • Adaptec ASR-7805(Q)

  • Adaptec ASR-70165

  • Adaptec ASR-71605(E|Q)

  • Adaptec ASR-71685

  • Adaptec ASR-72405

  • Adaptec Series 8 cards

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

  • AdvanSys ABP510/5150

  • AdvanSys ABP5140

  • AdvanSys ABP5142

  • AdvanSys ABP902/3902

  • AdvanSys ABP3905

  • AdvanSys ABP915

  • AdvanSys ABP920

  • AdvanSys ABP3922

  • AdvanSys ABP3925

  • AdvanSys ABP930, ABP930U, ABP930UA

  • AdvanSys ABP960, ABP960U

  • AdvanSys ABP542

  • AdvanSys ABP742

  • AdvanSys ABP842

  • AdvanSys ABP940

  • AdvanSys ABP940UA/3940UA

  • AdvanSys ABP940U

  • AdvanSys ABP3960UA

  • AdvanSys ABP970, ABP970U

  • AdvanSys ABP752

  • AdvanSys ABP852

  • AdvanSys ABP950

  • AdvanSys ABP980, ABP980U

  • AdvanSys ABP980UA/3980UA

  • MELCO IFC-USP (PC-98)

  • RATOC REX-PCI30 (PC-98)

  • @Nifty FNECHARD IFC-USUP-TX (PC-98)

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

  • AdvanSys ABP940UW/ABP3940UW

  • AdvanSys ABP950UW

  • AdvanSys ABP970UW

  • AdvanSys ABP3940U2W

  • AdvanSys ABP3950U2W

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

  • Adaptec AHA-154xB

  • Adaptec AHA-154xC

  • Adaptec AHA-154xCF

  • Adaptec AHA-154xCP

  • Adaptec AHA-1640

  • Adaptec AHA-174x in 154x emulation mode

  • DTC 3290 SCSI controller in 1542 emulation mode

  • Tekram SCSI controllers in 154x emulation mode

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

  • Adaptec AHA-1740

  • Adaptec AHA-1742

  • Adaptec AHA-1740A

  • Adaptec AHA-1742A

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

  • Adaptec AIC7770 host adapter chip

  • Adaptec AIC7850 host adapter chip

  • Adaptec AIC7860 host adapter chip

  • Adaptec AIC7870 host adapter chip

  • Adaptec AIC7880 host adapter chip

  • Adaptec AIC7890 host adapter chip

  • Adaptec AIC7891 host adapter chip

  • Adaptec AIC7892 host adapter chip

  • Adaptec AIC7895 host adapter chip

  • Adaptec AIC7896 host adapter chip

  • Adaptec AIC7897 host adapter chip

  • Adaptec AIC7899 host adapter chip

  • Adaptec 274X(W)

  • Adaptec 274X(T)

  • Adaptec 284X

  • Adaptec 2910

  • Adaptec 2915

  • Adaptec 2920C

  • Adaptec 2930C

  • Adaptec 2930U2

  • Adaptec 2940

  • Adaptec 2940J

  • Adaptec 2940N

  • Adaptec 2940U

  • Adaptec 2940AU

  • Adaptec 2940UW

  • Adaptec 2940UW Dual

  • Adaptec 2940UW Pro

  • Adaptec 2940U2W

  • Adaptec 2940U2B

  • Adaptec 2950U2W

  • Adaptec 2950U2B

  • Adaptec 19160B

  • Adaptec 29160B

  • Adaptec 29160N

  • Adaptec 3940

  • Adaptec 3940U

  • Adaptec 3940AU

  • Adaptec 3940UW

  • Adaptec 3940AUW

  • Adaptec 3940U2W

  • Adaptec 3950U2

  • Adaptec 3960

  • Adaptec 39160

  • Adaptec 3985

  • Adaptec 4944UW

  • NEC PC-9821Xt13 (PC-98)

  • NEC RvII26 (PC-98)

  • NEC PC-9821X-B02L/B09 (PC-98)

  • NEC SV-98/2-B03 (PC-98)

  • Many motherboards with on-board SCSI support

The ahci(4) driver supports AHCI compatible controllers having PCI class 1 (mass storage), subclass 6 (SATA) and programming interface 1 (AHCI).

Also, in cooperation with atamarvell and atajmicron drivers of ata(4), it supports AHCI part of legacy-PATA + AHCI-SATA combined controllers, such as JMicron JMB36x and Marvell 88SE61xx.

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

  • Adaptec AIC7901 host adapter chip

  • Adaptec AIC7901A host adapter chip

  • Adaptec AIC7902 host adapter chip

  • Adaptec 29320 host adapter

  • Adaptec 39320 host adapter

  • Many motherboards with on-board SCSI support

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

  • Adaptec AHA-1505 (ISA)

  • Adaptec AHA-1510A, AHA-1510B (ISA)

  • Adaptec AHA-1520A, AHA-1520B (ISA)

  • Adaptec AHA-1522A, AHA-1522B (ISA)

  • Adaptec AHA-1535 (ISA)

  • Creative Labs SoundBlaster SCSI host adapter (ISA)

  • Adaptec AHA-1460, AHA-1460B, AHA-1460C, AHA-1460D (PC Card)

  • Adaptec AHA-1030B, AHA-1030P (PC98)

  • NEC PC-9801-100 (PC98)

Controllers supported by the amr(4) driver include:

  • MegaRAID SATA 150-4

  • MegaRAID SATA 150-6

  • MegaRAID SATA 300-4X

  • MegaRAID SATA 300-8X

  • MegaRAID SCSI 320-1E

  • MegaRAID SCSI 320-2E

  • MegaRAID SCSI 320-4E

  • MegaRAID SCSI 320-0X

  • MegaRAID SCSI 320-2X

  • MegaRAID SCSI 320-4X

  • MegaRAID SCSI 320-0

  • MegaRAID SCSI 320-1

  • MegaRAID SCSI 320-2

  • MegaRAID SCSI 320-4

  • MegaRAID Series 418

  • MegaRAID i4 133 RAID

  • MegaRAID Elite 1500 (Series 467)

  • MegaRAID Elite 1600 (Series 493)

  • MegaRAID Elite 1650 (Series 4xx)

  • MegaRAID Enterprise 1200 (Series 428)

  • MegaRAID Enterprise 1300 (Series 434)

  • MegaRAID Enterprise 1400 (Series 438)

  • MegaRAID Enterprise 1500 (Series 467)

  • MegaRAID Enterprise 1600 (Series 471)

  • MegaRAID Express 100 (Series 466WS)

  • MegaRAID Express 200 (Series 466)

  • MegaRAID Express 300 (Series 490)

  • MegaRAID Express 500 (Series 475)

  • Dell PERC

  • Dell PERC 2/SC

  • Dell PERC 2/DC

  • Dell PERC 3/DCL

  • Dell PERC 3/QC

  • Dell PERC 4/DC

  • Dell PERC 4/IM

  • Dell PERC 4/SC

  • Dell PERC 4/Di

  • Dell PERC 4e/DC

  • Dell PERC 4e/Di

  • Dell PERC 4e/Si

  • Dell PERC 4ei

  • HP NetRAID-1/Si

  • HP NetRAID-3/Si (D4943A)

  • HP Embedded NetRAID

  • Intel RAID Controller SRCS16

  • Intel RAID Controller SRCU42X

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

  • ARC-1110

  • ARC-1120

  • ARC-1130

  • ARC-1160

  • ARC-1170

  • ARC-1110ML

  • ARC-1120ML

  • ARC-1130ML

  • ARC-1160ML

  • ARC-1200

  • ARC-1201

  • ARC-1210

  • ARC-1212

  • ARC-1213

  • ARC-1214

  • ARC-1220

  • ARC-1222

  • ARC-1223

  • ARC-1224

  • ARC-1230

  • ARC-1231

  • ARC-1260

  • ARC-1261

  • ARC-1270

  • ARC-1280

  • ARC-1210ML

  • ARC-1220ML

  • ARC-1231ML

  • ARC-1261ML

  • ARC-1280ML

  • ARC-1380

  • ARC-1381

  • ARC-1680

  • ARC-1681

  • ARC-1880

  • ARC-1882

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

  • Adaptec Zero-Channel SCSI RAID 2000S, 2005S, 2010S, 2015S

  • Adaptec SCSI RAID 2100S, 2110S

  • Adaptec ATA-100 RAID 2400A

  • Adaptec SCSI RAID 3200S, 3210S

  • Adaptec SCSI RAID 3400S, 3410S

  • Adaptec SmartRAID PM1554

  • Adaptec SmartRAID PM1564

  • Adaptec SmartRAID PM2554

  • Adaptec SmartRAID PM2564

  • Adaptec SmartRAID PM2664

  • Adaptec SmartRAID PM2754

  • Adaptec SmartRAID PM2865

  • Adaptec SmartRAID PM3754

  • Adaptec SmartRAID PM3755U2B / SmartRAID V Millennium

  • Adaptec SmartRAID PM3757

  • DEC KZPCC-AC (LVD 1-ch, 4MB or 16MB cache), DEC KZPCC-CE (LVD 3-ch, 64MB cache), DEC KZPCC-XC (LVD 1-ch, 16MB cache), DEC KZPCC-XE (LVD 3-ch, 64MB cache) -- rebadged SmartRAID V Millennium

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

  • BusLogic BT-445C

  • BusLogic BT-445S

  • BusLogic BT-540CF

  • BusLogic BT-542B

  • BusLogic BT-542B

  • BusLogic BT-542D

  • BusLogic BT-545C

  • BusLogic BT-545S

  • BusLogic/BusTek BT-640

  • BusLogic BT-742A

  • BusLogic BT-742A

  • BusLogic BT-747C

  • BusLogic BT-747D

  • BusLogic BT-747S

  • BusLogic BT-757C

  • BusLogic BT-757CD

  • BusLogic BT-757D

  • BusLogic BT-757S

  • BusLogic BT-946C

  • BusLogic BT-948

  • BusLogic BT-956C

  • BusLogic BT-956CD

  • BusLogic BT-958

  • BusLogic BT-958D

  • Storage Dimensions SDC3211B / SDC3211F

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:

  • Compaq Smart Array 5300 (simple mode only)

  • Compaq Smart Array 532

  • Compaq Smart Array 5i

  • HP Smart Array 5312

  • HP Smart Array 6i

  • HP Smart Array 641

  • HP Smart Array 642

  • HP Smart Array 6400

  • HP Smart Array 6400 EM

  • HP Smart Array E200

  • HP Smart Array E200i

  • HP Smart Array P212

  • HP Smart Array P220i

  • HP Smart Array P222

  • HP Smart Array P230i

  • HP Smart Array P400

  • HP Smart Array P400i

  • HP Smart Array P410

  • HP Smart Array P410i

  • HP Smart Array P411

  • HP Smart Array P420

  • HP Smart Array P420i

  • HP Smart Array P421

  • HP Smart Array P430

  • HP Smart Array P430i

  • HP Smart Array P431

  • HP Smart Array P530

  • HP Smart Array P531

  • HP Smart Array P600

  • HP Smart Array P721m

  • HP Smart Array P731m

  • HP Smart Array P800

  • HP Smart Array P812

  • HP Smart Array P830

  • HP Smart Array P830i

  • HP Modular Smart Array 20 (MSA20)

  • HP Modular Smart Array 500 (MSA500)

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

  • ELECOM bus-master SCSI adapters

  • I-O DATA SC-98II

  • ICM IF-2660, IF-2766, IF-2766ET, IF-2767 and IF-2769

  • Logitec LHA-N151 and LHA-20x series

  • Midori-Denshi MDC-554NA and MDC-926R

  • NEC PC-9801-55, 92 and compatibles

  • SMIT transfer type SCSI host adapters

  • TEXA HA-55BS2 and its later models

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

  • DPT Smart Cache Plus

  • Smart Cache II (PM2?2?, PM2022 [EISA], PM2024/PM2124 [PCI]) (Gen2)

  • Smart RAID II (PM3?2?, PM3021, PM3222)

  • Smart Cache III (PM2?3?)

  • Smart RAID III (PM3?3?, PM3332 [EISA], PM3334UW [PCI]) (Gen3)

  • Smart Cache IV (PM2?4?, PM2042 [EISA], PM2044/PM2144 [PCI]) (Gen4)

  • Smart RAID IV

Note:

[amd64, i386] Booting from these + controllers is supported. EISA adapters are not + supported.

[sparc64] Controllers supported by the esp(4) driver include:

  • MELCO IFC-DP (PC-98)

  • Sun ESP family

  • Sun FAS family

  • Tekram DC390

  • Tekram DC390T

[i386,amd64] The hpt27xx(4) driver supports the following SAS controllers:

  • HighPoint's RocketRAID 271x series

  • HighPoint's RocketRAID 272x series

  • HighPoint's RocketRAID 274x series

  • HighPoint's RocketRAID 276x series

  • HighPoint's RocketRAID 278x series

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

  • HighPoint RocketRAID 4522

  • HighPoint RocketRAID 4521

  • HighPoint RocketRAID 4520

  • HighPoint RocketRAID 4322

  • HighPoint RocketRAID 4321

  • HighPoint RocketRAID 4320

  • HighPoint RocketRAID 4311

  • HighPoint RocketRAID 4310

  • HighPoint RocketRAID 3640

  • HighPoint RocketRAID 3622

  • HighPoint RocketRAID 3620

The hptiop(4) driver also supports the following SAS and SATA RAID controllers that are already End-of-Life:

  • HighPoint RocketRAID 4211

  • HighPoint RocketRAID 4210

  • HighPoint RocketRAID 3560

  • HighPoint RocketRAID 3540

  • HighPoint RocketRAID 3530

  • HighPoint RocketRAID 3522

  • HighPoint RocketRAID 3521

  • HighPoint RocketRAID 3520

  • HighPoint RocketRAID 3511

  • HighPoint RocketRAID 3510

  • HighPoint RocketRAID 3410

  • HighPoint RocketRAID 3320

  • HighPoint RocketRAID 3220

  • HighPoint RocketRAID 3122

  • HighPoint RocketRAID 3120

  • HighPoint RocketRAID 3020

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

  • HighPoint's RocketRAID 182x series

The hptnr(4) driver supports the following SATA controllers:

  • HighPoint's DC7280 series

  • HighPoint's Rocket R750 series

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

  • RocketRAID 172x series

  • RocketRAID 174x series

  • RocketRAID 2210

  • RocketRAID 222x series

  • RocketRAID 2240

  • RocketRAID 230x series

  • RocketRAID 231x series

  • RocketRAID 232x series

  • RocketRAID 2340

  • RocketRAID 2522

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

  • Compaq SMART Array 221

  • Compaq Integrated SMART Array Controller

  • Compaq SMART Array 4200

  • Compaq SMART Array 4250ES

  • Compaq SMART 3200 Controller

  • Compaq SMART 3100ES Controller

  • Compaq SMART-2/DH Controller

  • Compaq SMART-2/SL Controller

  • Compaq SMART-2/P Controller

  • Compaq SMART-2/E Controller

  • Compaq SMART Controller

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

  • Intel RAID Controller SRCMR

  • Intel Server RAID Controller U3-l (SRCU31a)

  • Intel Server RAID Controller U3-1L (SRCU31La)

  • Intel Server RAID Controller U3-2 (SRCU32)

  • All past and future releases of Intel and ICP RAID Controllers.

  • Intel RAID Controller SRCU21 (discontinued)

  • Intel RAID Controller SRCU31 (older revision, not compatible)

  • Intel RAID Controller SRCU31L (older revision, not compatible)

The SRCU31 and SRCU31L can be updated via a firmware update available from Intel.

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

  • IBM ServeRAID 3H

  • ServeRAID 4L/4M/4H

  • ServeRAID Series 5

  • ServeRAID 6i/6M

  • ServeRAID 7t/7k/7M

Newer ServeRAID controllers are supported by the aac(4) or mfi(4) driver.

[i386,amd64] The isci(4) driver provides support for Intel C600 SAS controllers.

Cards supported by the isp(4) driver include:

  • ISP1000

  • ISP1020

  • ISP1040

  • Qlogic 1240

  • Qlogic 1020

  • Qlogic 1040

  • Qlogic 1080

  • Qlogic 1280

  • Qlogic 12160

  • Qlogic 210X

  • Qlogic 220X

  • Qlogic 2300

  • Qlogic 2312

  • Qlogic 234X

  • Qlogic 2322

  • Qlogic 200

  • Qlogic 2422

  • Qlogic 2432

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

  • LSI MegaRAID SAS 1078

  • LSI MegaRAID SAS 8408E

  • LSI MegaRAID SAS 8480E

  • LSI MegaRAID SAS 9240

  • LSI MegaRAID SAS 9260

  • Dell PERC5

  • Dell PERC6

  • IBM ServeRAID M1015 SAS/SATA

  • IBM ServeRAID M1115 SAS/SATA

  • IBM ServeRAID M5015 SAS/SATA

  • IBM ServeRAID M5110 SAS/SATA

  • IBM ServeRAID-MR10i

  • Intel RAID Controller SRCSAS18E

  • Intel RAID Controller SROMBSAS18E

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

  • Mylex DAC960P

  • Mylex DAC960PD / DEC KZPSC (Fast Wide)

  • Mylex DAC960PDU

  • Mylex DAC960PL

  • Mylex DAC960PJ

  • Mylex DAC960PG

  • Mylex DAC960PU / DEC PZPAC (Ultra Wide)

  • Mylex AcceleRAID 150 (DAC960PRL)

  • Mylex AcceleRAID 250 (DAC960PTL1)

  • Mylex eXtremeRAID 1100 (DAC1164P)

  • RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA (3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)

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:

[amd64, i386] Booting from these + controllers is supported. EISA adapters are not + supported.

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

  • Mylex AcceleRAID 160

  • Mylex AcceleRAID 170

  • Mylex AcceleRAID 352

  • Mylex eXtremeRAID 2000

  • Mylex eXtremeRAID 3000

Compatible Mylex controllers not listed should work, but have not been verified.

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

  • LSI SAS 3004 (4 Port SAS)

  • LSI SAS 3008 (8 Port SAS)

  • LSI SAS 3108 (8 Port SAS)

The mps(4) driver supports the following hardware:

  • LSI Logic SAS2004 (4 Port SAS)

  • LSI Logic SAS2008 (8 Port SAS)

  • LSI Logic SAS2108 (8 Port SAS)

  • LSI Logic SAS2116 (16 Port SAS)

  • LSI Logic SAS2208 (8 Port SAS)

  • LSI Logic SAS2308 (8 Port SAS)

  • LSI Logic SSS6200 Solid State Storage

  • Intel Integrated RAID Module RMS25JB040

  • Intel Integrated RAID Module RMS25JB080

  • Intel Integrated RAID Module RMS25KB040

  • Intel Integrated RAID Module RMS25KB080

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

  • LSI Logic 53c1030, LSI Logic LSI2x320-X (Single and Dual Ultra320 SCSI)

  • LSI Logic AS1064, LSI Logic AS1068

  • LSI Logic FC909 (1Gb/s Fibre Channel)

  • LSI Logic FC909A (Dual 1Gb/s Fibre Channel)

  • LSI Logic FC919, LSI Logic 7102XP-LC (Single 2Gb/s Fibre Channel)

  • LSI Logic FC929, LSI Logic FC929X, LSI Logic 7202XP-LC (Dual 2Gb/s Fibre Channel)

  • LSI Logic FC949X (Dual 4Gb/s Fibre Channel)

  • LSI Logic FC949E, LSI Logic FC949ES (Dual 4Gb/s Fibre Channel PCI-Express)

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

  • Dell PowerEdge 1750 thru 2850

  • IBM eServer xSeries 335

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.

The mrsas(4) driver supports the following hardware:

[ Thunderbolt 6Gb/s MR controller ]

  • LSI MegaRAID SAS 9265

  • LSI MegaRAID SAS 9266

  • LSI MegaRAID SAS 9267

  • LSI MegaRAID SAS 9270

  • LSI MegaRAID SAS 9271

  • LSI MegaRAID SAS 9272

  • LSI MegaRAID SAS 9285

  • LSI MegaRAID SAS 9286

  • DELL PERC H810

  • DELL PERC H710/P

[ Invader/Fury 12Gb/s MR controller ]

  • LSI MegaRAID SAS 9380

  • LSI MegaRAID SAS 9361

  • LSI MegaRAID SAS 9341

  • DELL PERC H830

  • DELL PERC H730/P

  • DELL PERC H330

The mvs(4) driver supports the following controllers:

Gen-I (SATA 1.5Gbps):

  • 88SX5040

  • 88SX5041

  • 88SX5080

  • 88SX5081

Gen-II (SATA 3Gbps, NCQ, PMP):

  • 88SX6040

  • 88SX6041 (including Adaptec 1420SA)

  • 88SX6080

  • 88SX6081

Gen-IIe (SATA 3Gbps, NCQ, PMP with FBS):

  • 88SX6042

  • 88SX7042 (including Adaptec 1430SA)

  • 88F5182 SoC

  • 88F6281 SoC

  • MV78100 SoC

Note, that this hardware supports command queueing and FIS-based switching only for ATA DMA commands. ATAPI and non-DMA ATA commands executed one by one for each port.

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

  • 53C810

  • 53C810A

  • 53C815

  • 53C820

  • 53C825A

  • 53C860

  • 53C875

  • 53C875J

  • 53C885

  • 53C895

  • 53C895A

  • 53C896

  • 53C1510D

The following add-on boards are known to be supported:

  • I-O DATA SC-98/PCI (PC-98)

  • I-O DATA SC-PCI (PC-98)

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

  • I-O DATA PCSC-DV

  • KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004, and UJDCD450

  • Macnica Miracle SCSI-II mPS110

  • Media Intelligent MSC-110, MSC-200

  • NEC PC-9801N-J03R

  • New Media Corporation BASICS SCSI

  • Qlogic Fast SCSI

  • RATOC REX-9530, REX-5572 (SCSI only)

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

  • Alpha-Data AD-PCS201

  • I-O DATA CBSC16

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

The siis(4) driver supports the following controller chips:

  • SiI3124 (PCI-X 133MHz/64bit, 4 ports)

  • SiI3131 (PCIe 1.0 x1, 1 port)

  • SiI3132 (PCIe 1.0 x1, 2 ports)

  • SiI3531 (PCIe 1.0 x1, 1 port)

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

  • Adaptec 2920/A

  • Future Domain SCSI2GO

  • Future Domain TMC-18XX/3260

  • IBM SCSI PCMCIA Card

  • ICM PSC-2401 SCSI

  • MELCO IFC-SC

  • RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A

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:

  • 53C810

  • 53C810A

  • 53C815

  • 53C825

  • 53C825A

  • 53C860

  • 53C875

  • 53C876

  • 53C895

  • 53C895A

  • 53C896

  • 53C897

  • 53C1000

  • 53C1000R

  • 53C1010-33

  • 53C1010-66

  • 53C1510D

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

  • ASUS SC-200, SC-896

  • Data Technology DTC3130 (all variants)

  • DawiControl DC2976UW

  • Diamond FirePort (all)

  • I-O DATA SC-UPCI (PC-98)

  • Logitec LHA-521UA (PC-98)

  • NCR cards (all)

  • Symbios cards (all)

  • Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and 390U3W

  • Tyan S1365

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

  • Tekram DC-315 PCI Ultra SCSI adapter without BIOS and internal SCSI connector

  • Tekram DC-315U PCI Ultra SCSI adapter without BIOS

  • Tekram DC-395F PCI Ultra-Wide SCSI adapter with flash BIOS and 68-pin external SCSI connector

  • Tekram DC-395U PCI Ultra SCSI adapter with flash BIOS

  • Tekram DC-395UW PCI Ultra-Wide SCSI adapter with flash BIOS

  • Tekram DC-395U2W PCI Ultra2-Wide SCSI adapter with flash BIOS

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:

  • AMCC's 3ware 9500S-4LP

  • AMCC's 3ware 9500S-8

  • AMCC's 3ware 9500S-8MI

  • AMCC's 3ware 9500S-12

  • AMCC's 3ware 9500S-12MI

  • AMCC's 3ware 9500SX-4LP

  • AMCC's 3ware 9500SX-8LP

  • AMCC's 3ware 9500SX-12

  • AMCC's 3ware 9500SX-12MI

  • AMCC's 3ware 9500SX-16ML

  • AMCC's 3ware 9550SX-4LP

  • AMCC's 3ware 9550SX-8LP

  • AMCC's 3ware 9550SX-12

  • AMCC's 3ware 9550SX-12MI

  • AMCC's 3ware 9550SX-16ML

  • AMCC's 3ware 9650SE-2LP

  • AMCC's 3ware 9650SE-4LPML

  • AMCC's 3ware 9650SE-8LPML

  • AMCC's 3ware 9650SE-12ML

  • AMCC's 3ware 9650SE-16ML

  • AMCC's 3ware 9650SE-24M8

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

  • AMCC's 3ware 5000 series

  • AMCC's 3ware 6000 series

  • AMCC's 3ware 7000-2

  • AMCC's 3ware 7006-2

  • AMCC's 3ware 7500-4LP

  • AMCC's 3ware 7500-8

  • AMCC's 3ware 7500-12

  • AMCC's 3ware 7506-4LP

  • AMCC's 3ware 7506-8

  • AMCC's 3ware 7506-12

  • AMCC's 3ware 8006-2LP

  • AMCC's 3ware 8500-4LP

  • AMCC's 3ware 8500-8

  • AMCC's 3ware 8500-12

  • AMCC's 3ware 8506-4LP

  • AMCC's 3ware 8506-8

  • AMCC's 3ware 8506-8MI

  • AMCC's 3ware 8506-12

  • AMCC's 3ware 8506-12MI

[i386,amd64] The tws(4) driver supports the following SATA/SAS RAID controller:

  • LSI's 3ware SAS 9750 series

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

  • Adaptec AIC-7110 Parallel to SCSI interface (built-in to Iomega ZIP drives)

  • Iomega Jaz Traveller interface

  • Iomega MatchMaker SCSI interface (built-in to Iomega ZIP+ drives)

[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:

  • SCSI interface (also includes ProAudio Spectrum and + SoundBlaster SCSI) (cd(4))

  • [i386] Sony proprietary interface (all models) + (scd(4))

  • ATAPI IDE interface (acd(4))

[i386] The following device is unmaintained:

  • Mitsumi proprietary CD-ROM interface (all models) + (mcd(4))

3.2. Ethernet Interfaces

The ae(4) driver supports Attansic/Atheros L2 PCIe FastEthernet controllers, and is known to support the following hardware:

  • ASUS EeePC 701

  • ASUS EeePC 900

Other hardware may or may not work with this driver.

The age(4) driver provides support for LOMs based on Attansic/Atheros L1 Gigabit Ethernet controller chips, including:

  • ASUS M2N8-VMX

  • ASUS M2V

  • ASUS M3A

  • ASUS P2-M2A590G

  • ASUS P5B-E

  • ASUS P5B-MX/WIFI-AP

  • ASUS P5B-VMSE

  • ASUS P5K

  • ASUS P5KC

  • ASUS P5KPL-C

  • ASUS P5KPL-VM

  • ASUS P5K-SE

  • ASUS P5K-V

  • ASUS P5L-MX

  • ASUS P5DL2-VM

  • ASUS P5L-VM 1394

  • ASUS G2S

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

  • Atheros AR8131 PCI Express Gigabit Ethernet controller

  • Atheros AR8132 PCI Express Fast Ethernet controller

  • Atheros AR8151 v1.0 PCI Express Gigabit Ethernet controller

  • Atheros AR8151 v2.0 PCI Express Gigabit Ethernet controller

  • Atheros AR8152 v1.1 PCI Express Fast Ethernet controller

  • Atheros AR8152 v2.0 PCI Express Fast Ethernet controller

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

  • Atheros AR8113 PCI Express Fast Ethernet controller

  • Atheros AR8114 PCI Express Fast Ethernet controller

  • Atheros AR8121 PCI Express Gigabit Ethernet controller

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

  • Abocom UFE1000, DSB650TX_NA

  • Accton USB320-EC, SpeedStream

  • ADMtek AN986, AN8511

  • Billionton USB100, USB100LP, USB100EL, USBE100

  • Corega Ether FEther USB-T, FEther USB-TX, FEther USB-TXS

  • D-Link DSB-650, DSB-650TX, DSB-650TX-PNA

  • Elecom LD-USBL/TX

  • Elsa Microlink USB2Ethernet

  • HP hn210e

  • I-O Data USB ETTX

  • Kingston KNU101TX

  • LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, USB100TX, USB100H1

  • MELCO LUA-TX, LUA2-TX

  • Netgear FA101

  • Planex UE-200TX

  • Sandberg USB to Network Link (model number 133-06)

  • Siemens Speedstream

  • SmartBridges smartNIC

  • SMC 2202USB

  • SOHOware NUB100

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

AX88172:

  • AboCom UF200

  • Acer Communications EP1427X2

  • ASIX AX88172

  • ATen UC210T

  • Billionton SnapPort

  • Billionton USB2AR

  • Buffalo (Melco Inc.) LUA-U2-KTX

  • Corega USB2_TX

  • D-Link DUBE100

  • Goodway GWUSB2E

  • JVC MP_PRX1

  • LinkSys USB200M

  • Netgear FA120

  • Sitecom LN-029

  • System TALKS Inc. SGC-X2UL

AX88178:

  • ASIX AX88178

  • Belkin F5D5055

  • Logitec LAN-GTJ/U2A

  • Buffalo (Melco Inc.) LUA3-U2-AGT

  • Planex Communications GU1000T

  • Sitecom Europe LN-028

AX88772:

  • ASIX AX88772

  • Buffalo (Melco Inc.) LUA3-U2-ATX

  • D-Link DUBE100B1

  • Planex UE-200TX-G

  • Planex UE-200TX-G2

AX88772A:

  • ASIX AX88772A

  • Cisco-Linksys USB200Mv2

AX88772B:

  • ASIX AX88772B

  • Lenovo USB 2.0 Ethernet

AX88760:

  • ASIX AX88760

ASIX Electronics AX88178A/AX88179 USB Gigabit Ethernet + adapters (axge(4) driver)

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

  • QLogic NetXtreme II BCM5706 1000Base-SX

  • QLogic NetXtreme II BCM5706 1000Base-T

  • QLogic NetXtreme II BCM5708 1000Base-SX

  • QLogic NetXtreme II BCM5708 1000Base-T

  • QLogic NetXtreme II BCM5709 1000Base-SX

  • QLogic NetXtreme II BCM5709 1000Base-T

  • QLogic NetXtreme II BCM5716 1000Base-T

  • Dell PowerEdge 1950 integrated BCM5708 NIC

  • Dell PowerEdge 2950 integrated BCM5708 NIC

  • Dell PowerEdge R710 integrated BCM5709 NIC

  • HP NC370F Multifunction Gigabit Server Adapter

  • HP NC370T Multifunction Gigabit Server Adapter

  • HP NC370i Multifunction Gigabit Server Adapter

  • HP NC371i Multifunction Gigabit Server Adapter

  • HP NC373F PCIe Multifunc Giga Server Adapter

  • HP NC373T PCIe Multifunction Gig Server Adapter

  • HP NC373i Multifunction Gigabit Server Adapter

  • HP NC373m Multifunction Gigabit Server Adapter

  • HP NC374m PCIe Multifunction Adapter

  • HP NC380T PCIe DP Multifunc Gig Server Adapter

  • HP NC382T PCIe DP Multifunction Gigabit Server Adapter

  • HP NC382i DP Multifunction Gigabit Server Adapter

  • HP NC382m DP 1GbE Multifunction BL-c Adapter

[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:

  • 3Com 3c996-SX (1000baseSX)

  • 3Com 3c996-T (10/100/1000baseTX)

  • Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX)

  • Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX)

  • Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX)

  • Dell PowerEdge R200 integrated BCM5750 NIC (10/100/1000baseTX)

  • Dell PowerEdge R300 integrated BCM5722 NIC (10/100/1000baseTX)

  • IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX)

  • HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX)

  • HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX)

  • HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX)

  • HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseTX)

  • HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX)

  • Netgear GA302T (10/100/1000baseTX)

  • SysKonnect SK-9D21 (10/100/1000baseTX)

  • SysKonnect SK-9D41 (1000baseSX)

[i386,amd64] The bxe(4) driver provides support for various NICs based on the QLogic NetXtreme II family of 10Gb Ethernet controller chips, including the following:

  • QLogic NetXtreme II BCM57710 10Gb

  • QLogic NetXtreme II BCM57711 10Gb

  • QLogic NetXtreme II BCM57711E 10Gb

  • QLogic NetXtreme II BCM57712 10Gb

  • QLogic NetXtreme II BCM57712-MF 10Gb

  • QLogic NetXtreme II BCM57800 10Gb

  • QLogic NetXtreme II BCM57800-MF 10Gb

  • QLogic NetXtreme II BCM57810 10Gb

  • QLogic NetXtreme II BCM57810-MF 10Gb

  • QLogic NetXtreme II BCM57840 10Gb / 20Gb

  • QLogic NetXtreme II BCM57840-MF 10Gb

The chips supported by the cas(4) driver are:

  • National Semiconductor DP83065 Saturn Gigabit Ethernet

  • Sun Cassini Gigabit Ethernet

  • Sun Cassini+ Gigabit Ethernet

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

  • Sun GigaSwift Ethernet 1.0 MMF (Cassini Kuheen) (part no. 501-5524)

  • Sun GigaSwift Ethernet 1.0 UTP (Cassini) (part no. 501-5902)

  • Sun GigaSwift Ethernet UTP (GCS) (part no. 501-6719)

  • Sun Quad GigaSwift Ethernet UTP (QGE) (part no. 501-6522)

  • Sun Quad GigaSwift Ethernet PCI-X (QGE-X) (part no. 501-6738)

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

  • Prolific PL-2501 Host-to-Host Bridge Controller

  • Sharp Zaurus PDA

  • Terayon TJ-715 DOCSIS Cable Modem

[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:

  • Belkin F5U011/F5U111

  • CATC Netmate

  • CATC Netmate II

  • SmartBridges SmartLink

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

  • Chelsio 10GBase-CX4

  • Chelsio 10GBase-LR

  • Chelsio 10GBase-SR

The cxgbe(4) driver supports 40Gb, 10Gb and 1Gb Ethernet adapters based on the T5 ASIC (ports will be named cxl):

  • Chelsio T580-CR

  • Chelsio T580-LP-CR

  • Chelsio T580-LP-SO-CR

  • Chelsio T560-CR

  • Chelsio T540-CR

  • Chelsio T540-LP-CR

  • Chelsio T522-CR

  • Chelsio T520-LL-CR

  • Chelsio T520-CR

  • Chelsio T520-SO

  • Chelsio T520-BT

  • Chelsio T504-BT

The cxgbe(4) driver supports 10Gb and 1Gb Ethernet adapters based on the T4 ASIC:

  • Chelsio T420-CR

  • Chelsio T422-CR

  • Chelsio T440-CR

  • Chelsio T420-BCH

  • Chelsio T440-BCH

  • Chelsio T440-CH

  • Chelsio T420-SO

  • Chelsio T420-CX

  • Chelsio T420-BT

  • Chelsio T404-BT

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

  • DEC/Intel 21143

  • ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II

  • ALi/ULi M5261 and M5263

  • ASIX Electronics AX88140A and AX88141

  • Conexant LANfinity RS7112 (miniPCI)

  • Davicom DM9009, DM9100, DM9102 and DM9102A

  • Lite-On 82c168 and 82c169 PNIC

  • Lite-On/Macronix 82c115 PNIC II

  • Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732

  • Xircom X3201 (cardbus only)

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

  • 3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)

  • Abocom FE2500

  • Accton EN1217 (98715A)

  • Accton EN2242 MiniPCI

  • Adico AE310TX (98715A)

  • Alfa Inc GFC2204 (ASIX AX88140A)

  • Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, non-MII)

  • Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, MII)

  • Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)

  • CNet Pro110B (ASIX AX88140A)

  • CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)

  • Compex RL100-TX (98713 or 98713A)

  • D-Link DFE-570TX (21143, MII, quad port)

  • Digital DE500-BA 10/100 (21143, non-MII)

  • ELECOM Laneed LD-CBL/TXA (ADMtek AN985)

  • Hawking CB102 CardBus

  • IBM EtherJet Cardbus Adapter

  • Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)

  • Jaton XpressNet (Davicom DM9102)

  • Kingston KNE100TX (21143, MII)

  • Kingston KNE110TX (PNIC 82c169)

  • LinkSys LNE100TX (PNIC 82c168, 82c169)

  • LinkSys LNE100TX v2.0 (PNIC II 82c115)

  • LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)

  • Matrox FastNIC 10/100 (PNIC 82c168, 82c169)

  • Melco LGY-PCI-TXL

  • Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)

  • Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)

  • NDC SOHOware SFA110A (98713A)

  • NDC SOHOware SFA110A Rev B4 (98715AEC-C)

  • NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)

  • Netgear FA511

  • PlaneX FNW-3602-T (ADMtek AN985)

  • SMC EZ Card 10/100 1233A-TX (ADMtek AN985)

  • SVEC PN102-TX (98713)

  • Xircom Cardbus Realport

  • Xircom Cardbus Ethernet 10/100

  • Xircom Cardbus Ethernet II 10/100

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

  • Adaptec ANA-6944/TX

  • Cogent EM100FX and EM440TX

  • Corega FastEther PCI-TX

  • D-Link DFE-500TX

  • DEC DE435, DEC DE450, and DEC DE500

  • ELECOM LD-PCI2T, LD-PCITS

  • I-O DATA LA2/T-PCI

  • SMC Etherpower 8432, 9332 and 9334

  • ZNYX ZX3xx

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

  • 3Com 3c503 Etherlink II

  • AR-P500 Ethernet

  • Accton EN1644 (old model), EN1646 (old model), EN2203 (old model) (110pin) (flags 0xd00000)

  • Accton EN2212/EN2216/UE2216

  • Allied Telesis CentreCOM LA100-PCM_V2

  • Allied Telesis LA-98 (flags 0x000000) (PC-98)

  • Allied Telesis SIC-98, SIC-98NOTE (110pin), SIU-98 (flags 0x600000) (PC-98)

  • Allied Telesis SIU-98-D (flags 0x610000) (PC-98)

  • AmbiCom 10BaseT card (8002, 8002T, 8010 and 8610)

  • Bay Networks NETGEAR FA410TXC Fast Ethernet

  • Belkin F5D5020 PC Card Fast Ethernet

  • Billionton LM5LT-10B Ethernet/Modem PC Card

  • Billionton LNT-10TB, LNT-10TN Ethernet PC Card

  • Bromax iPort 10/100 Ethernet PC Card

  • Bromax iPort 10 Ethernet PC Card

  • Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX, LPC-CTX PC Card

  • Buffalo LPC-CF-CLT CF Card

  • CNet BC40 adapter

  • Compex Net-A adapter

  • Compex RL2000

  • Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) (flags 0xa00000) (PC-98)

  • Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P (flags 0x300000) (PC-98)

  • Corega Ether98-T (flags 0x000000) (PC-98)

  • Corega Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD PCC-T/Fether II TXD

  • Corega LAPCCTXD (TC5299J)

  • CyQ've ELA-010

  • DEC EtherWorks DE305

  • Danpex EN-6200P2

  • D-Link DE-298, DE-298P (flags 0x500000) (PC-98)

  • D-Link DE-660, DE-660+

  • D-Link IC-CARD/IC-CARD+ Ethernet

  • ELECOM LD-98P (flags 0x500000) (PC-98)

  • ELECOM LD-BDN, LD-NW801G (flags 0x200000) (PC-98)

  • ELECOM Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A)

  • Hawking PN652TX PC Card (AX88790)

  • HP PC Lan+ 27247B and 27252A

  • IBM Creditcard Ethernet I/II

  • ICM AD-ET2-T, DT-ET-25, DT-ET-T5, IF-2766ET, IF-2771ET, NB-ET-T (110pin) (flags 0x500000) (PC-98)

  • I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 (flags 0x900000) (PC-98)

  • I-O DATA ET2/T-PCI

  • I-O DATA PCLATE

  • Kansai KLA-98C/T (flags 0x900000) (PC-98)

  • Kingston KNE-PC2, CIO10T, KNE-PCM/x Ethernet

  • KTI ET32P2 PCI

  • Linksys EC2T/PCMPC100/PCM100, PCMLM56

  • Linksys EtherFast 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 V2)

  • Logitec LAN-98T (flags 0xb00000) (PC-98)

  • MACNICA Ethernet ME1 for JEIDA

  • MACNICA ME98 (flags 0x900000) (PC-98)

  • MACNICA NE2098 (flags 0x400000) (PC-98)

  • MELCO EGY-98 (flags 0x300000) (PC-98)

  • MELCO LGH-98, LGY-98, LGY-98-N (110pin), IND-SP, IND-SS (flags 0x400000) (PC-98)

  • MELCO LGY-PCI-TR

  • MELCO LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX

  • NDC Ethernet Instant-Link

  • NEC PC-9801-77, PC-9801-78 (flags 0x910000) (PC-98)

  • NEC PC-9801-107, PC-9801-108 (flags 0x800000) (PC-98)

  • National Semiconductor InfoMover NE4100

  • NetGear FA-410TX

  • NetVin NV5000SC

  • Network Everywhere Ethernet 10BaseT PC Card

  • Networld 98X3 (flags 0xd00000) (PC-98)

  • Networld EC-98X, EP-98X (flags 0xd10000) (PC-98)

  • New Media LANSurfer 10+56 Ethernet/Modem

  • New Media LANSurfer

  • Novell NE1000/NE2000/NE2100

  • PLANEX ENW-8300-T

  • PLANEX EN-2298-C (flags 0x200000) (PC-98)

  • PLANEX EN-2298P-T, EN-2298-T (flags 0x500000) (PC-98)

  • PLANEX FNW-3600-T

  • Psion 10/100 LANGLOBAL Combine iT

  • RealTek 8019

  • RealTek 8029

  • Relia Combo-L/M-56k PC Card

  • SMC Elite 16 WD8013

  • SMC Elite Ultra

  • SMC EtherEZ98 (flags 0x000000) (PC-98)

  • SMC WD8003E/WD8003EBT/WD8003S/WD8003SBT/WD8003W/WD8013EBT/WD8013W and clones

  • SMC EZCard PC Card, 8040-TX, 8041-TX (AX88x90), 8041-TX V.2 (TC5299J)

  • Socket LP-E, ES-1000 Ethernet/Serial, LP-E CF, LP-FE CF

  • Surecom EtherPerfect EP-427

  • Surecom NE-34

  • TDK 3000/3400/5670 Fast Ethernet/Modem

  • TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card

  • TDK DFL5610WS Ethernet/Modem PC Card

  • Telecom Device SuperSocket RE450T

  • Toshiba LANCT00A PC Card

  • VIA VT86C926

  • Winbond W89C940

  • Winbond W89C940F

C-Bus, ISA, PCI and PC Card devices are supported.

The ed(4) driver does not support the following Ethernet NICs:

  • Mitsubishi LAN Adapter B8895

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:

  • Intel PRO/1000 CT Network Connection (82547)

  • Intel PRO/1000 F Server Adapter (82543)

  • Intel PRO/1000 Gigabit Server Adapter (82542)

  • Intel PRO/1000 GT Desktop Adapter (82541PI)

  • Intel PRO/1000 MF Dual Port Server Adapter (82546)

  • Intel PRO/1000 MF Server Adapter (82545)

  • Intel PRO/1000 MF Server Adapter (LX) (82545)

  • Intel PRO/1000 MT Desktop Adapter (82540)

  • Intel PRO/1000 MT Desktop Adapter (82541)

  • Intel PRO/1000 MT Dual Port Server Adapter (82546)

  • Intel PRO/1000 MT Quad Port Server Adapter (82546EB)

  • Intel PRO/1000 MT Server Adapter (82545)

  • Intel PRO/1000 PF Dual Port Server Adapter (82571)

  • Intel PRO/1000 PF Quad Port Server Adapter (82571)

  • Intel PRO/1000 PF Server Adapter (82572)

  • Intel PRO/1000 PT Desktop Adapter (82572)

  • Intel PRO/1000 PT Dual Port Server Adapter (82571)

  • Intel PRO/1000 PT Quad Port Server Adapter (82571)

  • Intel PRO/1000 PT Server Adapter (82572)

  • Intel PRO/1000 T Desktop Adapter (82544)

  • Intel PRO/1000 T Server Adapter (82543)

  • Intel PRO/1000 XF Server Adapter (82544)

  • Intel PRO/1000 XT Server Adapter (82544)

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

  • 3Com 3C1 CF

  • 3Com 3C509-TP, 3C509-BNC, 3C509-Combo, 3C509-TPO, 3C509-TPC ISA

  • 3Com 3C509B-TP, 3C509B-BNC, 3C509B-Combo, 3C509B-TPO, 3C509B-TPC ISA

  • 3Com 3C529, 3C529-TP MCA

  • 3Com 3C562/3C563 PCMCIA

  • 3Com 3C569B-J-TPO, 3C569B-J-COMBO CBUS

  • 3Com 3C574, 3C574TX, 3C574-TX, 3CCFE574BT, 3CXFE574BT, 3C3FE574BT PCMCIA

  • 3Com 3C579-TP, 3C579-BNC EISA

  • 3Com 3C589, 3C589B, 3C589C, 3C589D, 3CXE589DT PCMCIA

  • 3Com 3CCFEM556B, 3CCFEM556BI PCMCIA

  • 3Com 3CXE589EC, 3CCE589EC, 3CXE589ET, 3CCE589ET PCMCIA

  • 3Com Megahertz 3CCEM556, 3CXEM556, 3CCEM556B, 3CXEM556B, 3C3FEM556C PCMCIA

  • 3Com OfficeConnect 3CXSH572BT, 3CCSH572BT PCMCIA

  • Farallon EtherWave and EtherMac PC Card (P/n 595/895 with BLUE arrow)

Agere ET1310 Gigabit Ethernet adapters + (et(4) driver)

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

  • Intel EtherExpress Pro/10 ISA

  • Intel EtherExpress Pro/10+ ISA

  • Olicom OC2220 Ethernet PC Card

  • Olicom OC2232 Ethernet/Modem PC Card

  • Silicom Ethernet LAN PC Card

  • Silicom EtherSerial LAN PC Card

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

  • Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin)

  • CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard)

  • CONTEC C-NET(PC)C PC Card Ethernet

  • Eagle Tech NE200T

  • Eiger Labs EPX-10BT

  • Fujitsu FMV-J182, FMV-J182A

  • Fujitsu MB86960A, MB86965A

  • Fujitsu MBH10303, MBH10302 PC Card Ethernet

  • Fujitsu Towa LA501 Ethernet

  • HITACHI HT-4840-11 PC Card Ethernet

  • NextCom J Link NC5310

  • RATOC REX-5588, REX-9822, REX-4886, and REX-R280

  • RATOC REX-9880/9881/9882/9883

  • TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin)

  • TDK LAK-CD011, LAK-CD021, LAK-CD021A, LAK-CD021BX

  • Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE N98(PC86132) (110-pin)

Adapters supported by the fxp(4) driver include:

  • Intel EtherExpress PRO/10

  • Intel InBusiness 10/100

  • Intel PRO/100B / EtherExpressPRO/100 B PCI Adapter

  • Intel PRO/100+ Management Adapter

  • Intel PRO/100 VE Desktop Adapter

  • Intel PRO/100 VM Network Connection

  • Intel PRO/100 M Desktop Adapter

  • Intel PRO/100 S Desktop, Server and Dual-Port Server Adapters

  • Contec C-NET(PI)-100TX (PC-98)

  • NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)

  • NEC PC-9821X-B06 (PC-98)

  • Many on-board network interfaces on Intel motherboards

Chips supported by the gem(4) driver include:

  • Apple GMAC

  • Sun ERI 10/100 Mbps Ethernet

  • Sun GEM Gigabit Ethernet

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

  • Sun Gigabit Ethernet PCI 2.0/3.0 (GBE/P) (part no. 501-4373)

  • Sun Gigabit Ethernet SBus 2.0/3.0 (GBE/S) (part no. 501-4375)

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:

  • Sun PCI SunSwift Adapter

  • Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)

  • Sun PCI Sun100BaseT Adapter 2.0

  • Sun SBus Sun100BaseT 2.0

  • Sun PCI Quad FastEthernet Controller

  • Sun SBus Quad FastEthernet Controller

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

  • 3COM 3C507

  • AT&T EN100

  • AT&T Starlan 10

  • AT&T Starlan Fiber

  • Intel EtherExpress 16

  • RACAL Interlan NI5210

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

  • Intel Gigabit ET Dual Port Server Adapter (82576)

  • Intel Gigabit VT Quad Port Server Adapter (82575)

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

  • Intel PRO/10GbE LR Server Adapter

  • Intel PRO/10GbE SR Server Adapter

The ixgbe(4) driver supports the following cards:

  • Intel(R) 10 Gigabit XF SR/AF Dual Port Server Adapter

  • Intel(R) 10 Gigabit XF SR/LR Server Adapter

  • Intel(R) 82598EB 10 Gigabit AF Network Connection

  • Intel(R) 82598EB 10 Gigabit AT CX4 Network Connection

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

  • JMicron JMC250 PCI Express Gigabit Ethernet controller

  • JMicron JMC251 PCI Express Gigabit Ethernet with Card Read Host controller

  • JMicron JMC260 PCI Express Fast Ethernet controller

  • JMicron JMC261 PCI Express Gigabit Ethernet with Card Read Host controller

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

  • 3Com 3c19250

  • 3Com 3c460 HomeConnect Ethernet USB Adapter

  • ADS Technologies USB-10BT

  • AOX USB101

  • ATen UC10T

  • Abocom URE 450

  • Corega USB-T

  • D-Link DSB-650C

  • Entrega NET-USB-E45, NET-HUB-3U1E

  • I/O Data USB ETT

  • Kawasaki DU-H3E

  • LinkSys USB10T

  • Netgear EA101

  • Peracom USB Ethernet Adapter

  • Psion Gold Port USB Ethernet adapter

  • SMC 2102USB, 2104USB

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

  • SMC TigerCard 1000 (SMC9462SX)

  • D-Link DGE-500SX

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

  • D-Link 550SX Gigabit Ethernet

  • D-Link 560SX Gigabit Ethernet

  • D-Link 560T Gigabit Ethernet

  • Marvell Yukon 88E8021CU Gigabit Ethernet

  • Marvell Yukon 88E8021 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8022CU Gigabit Ethernet

  • Marvell Yukon 88E8022 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8061CU Gigabit Ethernet

  • Marvell Yukon 88E8061 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8062CU Gigabit Ethernet

  • Marvell Yukon 88E8062 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8035 Fast Ethernet

  • Marvell Yukon 88E8036 Fast Ethernet

  • Marvell Yukon 88E8038 Fast Ethernet

  • Marvell Yukon 88E8039 Fast Ethernet

  • Marvell Yukon 88E8040 Fast Ethernet

  • Marvell Yukon 88E8040T Fast Ethernet

  • Marvell Yukon 88E8042 Fast Ethernet

  • Marvell Yukon 88E8048 Fast Ethernet

  • Marvell Yukon 88E8050 Gigabit Ethernet

  • Marvell Yukon 88E8052 Gigabit Ethernet

  • Marvell Yukon 88E8053 Gigabit Ethernet

  • Marvell Yukon 88E8055 Gigabit Ethernet

  • Marvell Yukon 88E8056 Gigabit Ethernet

  • Marvell Yukon 88E8057 Gigabit Ethernet

  • Marvell Yukon 88E8058 Gigabit Ethernet

  • Marvell Yukon 88E8059 Gigabit Ethernet

  • Marvell Yukon 88E8070 Gigabit Ethernet

  • Marvell Yukon 88E8071 Gigabit Ethernet

  • Marvell Yukon 88E8072 Gigabit Ethernet

  • Marvell Yukon 88E8075 Gigabit Ethernet

  • SysKonnect SK-9Sxx Gigabit Ethernet

  • SysKonnect SK-9Exx Gigabit Ethernet

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

  • Myricom 10GBase-CX4 (10G-PCIE-8A-C, 10G-PCIE-8AL-C)

  • Myricom 10GBase-R (10G-PCIE-8A-R, 10G-PCIE-8AL-R)

  • Myricom 10G XAUI over ribbon fiber (10G-PCIE-8A-Q, 10G-PCIE-8AL-Q)

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

  • Myson MTD800 PCI Fast Ethernet chip

  • Myson MTD803 PCI Fast Ethernet chip

  • Myson MTD89X PCI Gigabit Ethernet chip

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

  • NVIDIA nForce MCP Networking Adapter

  • NVIDIA nForce MCP04 Networking Adapter

  • NVIDIA nForce 430 MCP12 Networking Adapter

  • NVIDIA nForce 430 MCP13 Networking Adapter

  • NVIDIA nForce MCP51 Networking Adapter

  • NVIDIA nForce MCP55 Networking Adapter

  • NVIDIA nForce MCP61 Networking Adapter

  • NVIDIA nForce MCP65 Networking Adapter

  • NVIDIA nForce MCP67 Networking Adapter

  • NVIDIA nForce MCP73 Networking Adapter

  • NVIDIA nForce MCP77 Networking Adapter

  • NVIDIA nForce MCP79 Networking Adapter

  • NVIDIA nForce2 MCP2 Networking Adapter

  • NVIDIA nForce2 400 MCP4 Networking Adapter

  • NVIDIA nForce2 400 MCP5 Networking Adapter

  • NVIDIA nForce3 MCP3 Networking Adapter

  • NVIDIA nForce3 250 MCP6 Networking Adapter

  • NVIDIA nForce3 MCP7 Networking Adapter

  • NVIDIA nForce4 CK804 MCP8 Networking Adapter

  • NVIDIA nForce4 CK804 MCP9 Networking Adapter

The nge(4) driver supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters including:

  • Addtron AEG320T

  • Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI)

  • Asante FriendlyNet GigaNIX 1000TA and 1000TPC

  • D-Link DGE-500T

  • Linksys EG1032, revision 1

  • Netgear GA621

  • Netgear GA622T

  • SMC EZ Card 1000 (SMC9462TX)

  • Surecom Technology EP-320G-TX

  • Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI)

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

  • nForce

  • nForce2

  • nForce3

  • nForce4

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

[i386,amd64] The oce(4) driver supports the following network adapters:

  • Emulex BladeEngine 2

  • Emulex BladeEngine 3

  • Emulex Lancer

[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:

  • AMD Am79C971 PCnet-FAST

  • AMD Am79C972 PCnet-FAST+

  • AMD Am79C973/Am79C975 PCnet-FAST III

  • AMD Am79C976 PCnet-PRO

  • AMD Am79C978 PCnet-Home

  • Allied-Telesis LA-PCI

[amd64] The qlxgb(4) driver supports 10 Gigabit Ethernet & CNA Adapter based on the following chipsets:

  • QLogic 3200 series

  • QLogic 8200 series

[amd64] The qlxgbe(4) driver supports 10 Gigabit Ethernet & CNA Adapter based on the following chipsets:

  • QLogic 8300 series

[amd64] The qlxge(4) driver supports 10 Gigabit Ethernet & CNA Adapter based on the following chipsets:

  • QLogic 8100 series

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

  • Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)

  • Compaq Evo N1015v Integrated Ethernet (8139C+)

  • Corega CG-LAPCIGT Gigabit Ethernet (8169S)

  • D-Link DGE-528(T) Gigabit Ethernet (8169S)

  • Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

  • LevelOne GNC-0105T (8169S)

  • LinkSys EG1032 (32-bit PCI)

  • PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)

  • USRobotics USR997902 Gigabit Ethernet (8169S)

  • Xterasys XN-152 10/100/1000 NIC (8169)

Adapters supported by the rl(4) driver include:

  • Accton “Cheetah” EN1207D (MPX 5030/5038; RealTek 8139 clone)

  • Allied Telesyn AT2550

  • Allied Telesyn AT2500TX

  • Belkin F5D5000

  • BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)

  • Compaq HNE-300

  • CompUSA no-name 10/100 PCI Ethernet NIC

  • Corega FEther CB-TXD

  • Corega FEtherII CB-TXD

  • D-Link DFE-520TX (rev. C1)

  • D-Link DFE-528TX

  • D-Link DFE-530TX+

  • D-Link DFE-538TX

  • D-Link DFE-690TXD

  • Edimax EP-4103DL CardBus

  • Encore ENL832-TX 10/100 M PCI

  • Farallon NetLINE 10/100 PCI

  • Genius GF100TXR

  • GigaFast Ethernet EE100-AXP

  • KTX-9130TX 10/100 Fast Ethernet

  • LevelOne FPC-0106TX

  • Longshine LCS-8038TX-R

  • NDC Communications NE100TX-E

  • Netronix Inc. EA-1210 NetEther 10/100

  • Nortel Networks 10/100BaseTX

  • OvisLink LEF-8129TX

  • OvisLink LEF-8139TX

  • Peppercon AG ROL-F

  • Planex FNW-3603-TX

  • Planex FNW-3800-TX

  • SMC EZ Card 10/100 PCI 1211-TX

  • SOHO (PRAGMATIC) UE-1211C

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

  • Buffalo (Melco Inc.) LUA-KTX

  • Green House GH-USB100B

  • LinkSys USB100M

  • Billionton 10/100 FastEthernet USBKR2

Adapters supported by the sf(4) driver include:

  • ANA-62011 64-bit single port 10/100baseTX adapter

  • ANA-62022 64-bit dual port 10/100baseTX adapter

  • ANA-62044 64-bit quad port 10/100baseTX adapter

  • ANA-69011 32-bit single port 10/100baseTX adapter

  • ANA-62020 64-bit single port 100baseFX adapter

The sfxge(4) driver supports all 10Gb Ethernet adapters based on Solarflare SFC9000 family controllers.

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

  • SiS190 Fast Ethernet controller

  • SiS191 Fast/Gigabit Ethernet controller

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:

  • @Nifty FNECHARD IFC USUP-TX

  • MELCO LGY-PCI-TXC

  • Netgear FA311-TX (DP83815)

  • Netgear FA312-TX (DP83815)

  • SiS 630, 635, and 735 motherboard chipsets

  • Soekris Engineering net45xx, net48xx, lan1621, and lan1641

Adapters supported by the sk(4) driver include:

  • 3Com 3C940 single port, 1000baseT adapter

  • 3Com 3C2000-T single port, 1000baseT adapter

  • Belkin F5D5005 single port, 1000baseT adapter

  • D-Link DGE-530T single port, 1000baseT adapter

  • Linksys (revision 2) single port, 1000baseT adapter

  • SK-9521 SK-NET GE-T single port, 1000baseT adapter

  • SK-9821 SK-NET GE-T single port, 1000baseT adapter

  • SK-9822 SK-NET GE-T dual port, 1000baseT adapter

  • SK-9841 SK-NET GE-LX single port, single mode fiber adapter

  • SK-9842 SK-NET GE-LX dual port, single mode fiber adapter

  • SK-9843 SK-NET GE-SX single port, multimode fiber adapter

  • SK-9844 SK-NET GE-SX dual port, multimode fiber adapter

  • SMC 9452TX single port, 1000baseT adapter

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

  • 3Com Megahertz X-Jack Ethernet PC Card XJ10BT, XJ10BC

  • 3Com Megahertz XJEM and CCEM series: CCEM3288C, CCEM3288T, CCEM3336, CEM3336C, CCEM3336T, XJEM1144C, XJEM1144T, XJEM3288C, XJEM3288T, XJEM3336

  • Farallon EtherMac PC Card 595a

  • Motorola Mariner Ethernet/Modem PC Card

  • Ositech Seven of Diamonds Ethernet PC Card

  • Ositech Jack of Hearts Ethernet/Modem PC Card

  • Psion Gold Card Netglobal Ethernet PC Card

  • Psion Gold Card Netglobal 10/100 Fast Ethernet PC Card

  • Psion Gold Card Netglobal 56k+10Mb Ethernet PC Card

  • SMC EZEther PC Card (8020BT)

  • SMC EZEther PC Card (8020T)

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:

  • National Semiconductor DP83934AVQB

  • NEC PC-9801-83

  • NEC PC-9801-84

  • NEC PC-9801-103

  • NEC PC-9801-104

  • NEC PC-9801N-15

  • NEC PC-9801N-25

  • NEC PC-9801N-J02 PCMCIA

  • NEC PC-9801N-J02R PCMCIA

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

The ste(4) driver supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded controllers including:

  • D-Link DFE-530TXS

  • D-Link DFE-550TX

  • D-Link DFE-580TX

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

  • Antares Microsystems Gigabit Ethernet

  • ASUS NX1101 Gigabit Ethernet

  • D-Link DL-4000 Gigabit Ethernet

  • IC Plus IP1000A Gigabit Ethernet

  • Sundance ST-2021 Gigabit Ethernet

  • Sundance ST-2023 Gigabit Ethernet

  • Sundance TC9021 Gigabit Ethernet

  • Tamarack TC9021 Gigabit Ethernet

[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:

  • 3Com 3c985-SX Gigabit Ethernet adapter (Tigon 1)

  • 3Com 3c985B-SX Gigabit Ethernet adapter (Tigon 2)

  • Alteon AceNIC V Gigabit Ethernet adapter (1000baseSX)

  • Alteon AceNIC V Gigabit Ethernet adapter (1000baseT)

  • Digital EtherWORKS 1000SX PCI Gigabit adapter

  • Netgear GA620 Gigabit Ethernet adapter (1000baseSX)

  • Netgear GA620T Gigabit Ethernet adapter (1000baseT)

The following adapters should also be supported but have not yet been tested:

  • Asante GigaNIX1000T Gigabit Ethernet adapter

  • Asante PCI 1000BASE-SX Gigabit Ethernet adapter

  • Farallon PN9000SX Gigabit Ethernet adapter

  • NEC Gigabit Ethernet

  • Silicon Graphics PCI Gigabit Ethernet adapter

[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:

  • Olicom OC-2135/2138 10/100 TX UTP adapter

  • Olicom OC-2325/OC-2326 10/100 TX UTP adapter

  • Racore 8148 10baseT/100baseTX/100baseFX adapter

  • Racore 8165 10/100baseTX adapter

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

  • Compaq Netelligent 10

  • Compaq Netelligent 10 T PCI UTP/Coax

  • Compaq Netelligent 10/100

  • Compaq Netelligent 10/100 Dual-Port

  • Compaq Netelligent 10/100 Proliant

  • Compaq Netelligent 10/100 TX Embedded UTP

  • Compaq Netelligent 10/100 TX UTP

  • Compaq NetFlex 3P

  • Compaq NetFlex 3P Integrated

  • Compaq NetFlex 3P w/BNC

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

The txp(4) driver supports the following cards:

  • 3Com 3CR990-TX-95

  • 3Com 3CR990-TX-97

  • 3Com 3cR990B-TXM

  • 3Com 3CR990SVR95

  • 3Com 3CR990SVR97

  • 3Com 3cR990B-SRV

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

  • Corega FEther USB-TXC

  • ShanTou ST268 USB NIC

The vge(4) driver supports VIA Networking VT6120, VT6122, VT6130 and VT6132 based Gigabit Ethernet adapters including:

  • VIA Networking LAN-on-motherboard Gigabit Ethernet

  • ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701)

  • ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702)

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

  • AOpen/Acer ALN-320

  • D-Link DFE520-TX

  • D-Link DFE530-TX

  • Hawking Technologies PN102TX

  • Soekris Engineering net5501

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

  • DM&P Vortex86 RDC R6040 Fast Ethernet controller

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

  • 3Com 3c590 EtherLink III PCI

  • 3Com 3c592 EtherLink III EISA

  • 3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode

  • 3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode

[i386,amd64] The vxge(4) driver supports Neterion X3100 10 Gigabit Ethernet adapters listed in http://www.neterion.com.

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

  • Trendware TE100-PCIE

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

  • Xircom CreditCard Ethernet (PS-CE2-10)

  • Xircom CreditCard Ethernet + Modem 28 (PS-CEM-28)

  • Xircom CreditCard Ethernet + Modem 33 (CEM33)

  • Xircom CreditCard 10/100 (CE3, CE3B)

  • Xircom CreditCard Ethernet 10/100 + Modem 56 (CEM56)

  • Xircom RealPort Ethernet 10 (RE10)

  • Xircom RealPort Ethernet 10/100 (RE100)

  • Xircom RealPort Ethernet 10/100 + Modem 56 (REM56, REM56G)

  • Accton Fast EtherCard-16 (EN2226)

  • Compaq Microcom CPQ550 Ethernet/Modem PC Card

  • Compaq Netelligent 10/100 PC Card (CPQ-10/100)

  • Intel EtherExpress Pro/100 PC Card Mobile Adapter 16 (Pro/100 M16A)

  • Intel EtherExpress Pro/100 LAN/Modem PC Card Adapter (Pro/100 M16B)

Other similar devices using the same hardware may also be supported.

The xl(4) driver supports the following hardware:

  • 3Com 3c900-TPO

  • 3Com 3c900-COMBO

  • 3Com 3c905-TX

  • 3Com 3c905-T4

  • 3Com 3c900B-TPO

  • 3Com 3c900B-TPC

  • 3Com 3c900B-FL

  • 3Com 3c900B-COMBO

  • 3Com 3c905B-T4

  • 3Com 3c905B-TX

  • 3Com 3c905B-FX

  • 3Com 3c905B-COMBO

  • 3Com 3c905C-TX

  • 3Com 3c980, 3c980B, and 3c980C server adapters

  • 3Com 3cSOHO100-TX OfficeConnect adapters

  • 3Com 3c450 HomeConnect adapters

  • 3Com 3c555, 3c556 and 3c556B mini-PCI adapters

  • 3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, 3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters

  • 3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded adapters

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 FreeBSD driver supports this modem.

3.3. FDDI Interfaces

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

[i386] DEC DEFEA EISA (fpa(4) driver)

3.4. 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.5. 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 and PCI cards, except those that are based on the AR5005VL chipset.

The following cards are among those supported by the ath_hal(4) module:

  • Aztech WL830PC

  • D-Link DWL-A650

  • D-Link DWL-AB650

  • D-Link DWL-A520

  • D-Link DWL-AG520

  • D-Link DWL-AG650

  • D-Link DWL-G520B

  • D-Link DWL-G650B

  • Elecom LD-WL54AG

  • Elecom LD-WL54

  • Fujitsu E5454

  • Fujitsu FMV-JW481

  • Fujitsu E5454

  • HP NC4000

  • I/O Data WN-AB

  • I/O Data WN-AG

  • I/O Data WN-A54

  • Linksys WMP55AG

  • Linksys WPC51AB

  • Linksys WPC55AG

  • NEC PA-WL/54AG

  • Netgear WAG311

  • Netgear WAB501

  • Netgear WAG511

  • Netgear WG311 (aka WG311v1)

  • Netgear WG311v2

  • Netgear WG311T

  • Netgear WG511T

  • Orinoco 8480

  • Orinoco 8470WD

  • Proxim Skyline 4030

  • Proxim Skyline 4032

  • Samsung SWL-5200N

  • SMC SMC2735W

  • Sony PCWA-C700

  • Sony PCWA-C300S

  • Sony PCWA-C500

  • 3Com 3CRPAG175

  • TP-LINK TL-WDN4800

The bwi(4) driver supports Broadcom BCM43xx based wireless devices, including:

  • Apple Airport Extreme

  • Apple Airport Extreme

  • ASUS WL-138g

  • Buffalo WLI-CB-G54S

  • Buffalo WLI-PCI-G54S

  • Compaq R4035 onboard

  • Dell Wireless 1390

  • Dell Wireless 1470

  • Dell Truemobile 1300 r2

  • Dell Truemobile 1400

  • HP nx6125

  • Linksys WPC54G Ver 3

  • Linksys WPC54GS Ver 2

  • TRENDnet TEW-401PCplus

  • US Robotics 5411

The bwi(4) driver uses the older v3 version of Broadcom's firmware. While this older firmware does support most BCM43xx parts, the bwn(4) driver works better for the newer chips it supports. You must use the bwi(4) driver if you are using older Broadcom chipsets (BCM4301, BCM4303 and BCM4306 rev 2). The v4 version of the firmware that bwn(4) uses does not support these chips.

The bwn(4) driver supports Broadcom BCM43xx based wireless devices, including:

  • Apple Airport Extreme

  • ASUS WL-138g

  • Buffalo WLI-CB-G54S

  • Dell Wireless 1390

  • Dell Wireless 1470

  • Dell Truemobile 1400

  • HP Compaq 6715b

  • HP nx6125

  • Linksys WPC54G Ver 3

  • Linksys WPC54GS Ver 2

  • US Robotics 5411

Users of older Broadcom chipsets (BCM4301, BCM4303 and BCM4306 rev 2) must use bwi(4) because the v4 version of the firmware does not support these chips. The newer firmware is too big to fit into these old chips.

[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] Intel Wireless WiFi Link + 4965AGN IEEE 802.11n PCI network adapters + (iwn(4) driver)

[i386, amd64] Marvell Libertas IEEE + 802.11b/g PCI network adapters (malo(4) driver)

Marvell 88W8363 IEEE 802.11n wireless network + adapters (mwl(4) driver)

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

  • A-Link WL54H

  • A-Link WL54PC

  • AirLink101 AWLC5025

  • AirLink101 AWLH5025

  • Amigo AWI-914W

  • Amigo AWI-922W

  • Amigo AWI-926W

  • AMIT WL531C

  • AMIT WL531P

  • AOpen AOI-831

  • ASUS WL-107G

  • ASUS WL-130g

  • Atlantis Land A02-PCI-W54

  • Atlantis Land A02-PCM-W54

  • Belkin F5D7000 v3

  • Belkin F5D7010 v2

  • Billionton MIWLGRL

  • Canyon CN-WF511

  • Canyon CN-WF513

  • CC&C WL-2102

  • CNet CWC-854

  • CNet CWP-854

  • Compex WL54G

  • Compex WLP54G

  • Conceptronic C54RC

  • Conceptronic C54Ri

  • Digitus DN-7001G-RA

  • Digitus DN-7006G-RA

  • E-Tech WGPC02

  • E-Tech WGPI02

  • Edimax EW-7108PCg

  • Edimax EW-7128g

  • Eminent EM3036

  • Eminent EM3037

  • Encore ENLWI-G-RLAM

  • Encore ENPWI-G-RLAM

  • Fiberline WL-400P

  • Fibreline WL-400X

  • Gigabyte GN-WI01GS

  • Gigabyte GN-WIKG

  • Gigabyte GN-WMKG

  • Gigabyte GN-WP01GS

  • Gigabyte GN-WPKG

  • Hawking HWC54GR

  • Hawking HWP54GR

  • iNexQ CR054g-009 (R03)

  • JAHT WN-4054P

  • JAHT WN-4054PCI

  • LevelOne WNC-0301 v2

  • LevelOne WPC-0301 v2

  • Linksys WMP54G v4

  • Micronet SP906GK

  • Micronet SP908GK V3

  • Minitar MN54GCB-R

  • Minitar MN54GPC-R

  • MSI CB54G2

  • MSI MP54G2

  • MSI PC54G2

  • OvisLink EVO-W54PCI

  • PheeNet HWL-PCIG/RA

  • Pro-Nets CB80211G

  • Pro-Nets PC80211G

  • Repotec RP-WB7108

  • Repotec RP-WP0854

  • SATech SN-54C

  • SATech SN-54P

  • Sitecom WL-112

  • Sitecom WL-115

  • SMC SMCWCB-GM

  • SMC SMCWPCI-GM

  • SparkLAN WL-685R

  • Surecom EP-9321-g

  • Surecom EP-9321-g1

  • Surecom EP-9428-g

  • Sweex LC500050

  • Sweex LC700030

  • TekComm NE-9321-g

  • TekComm NE-9428-g

  • Unex CR054g-R02

  • Unex MR054g-R02

  • Zinwell ZWX-G160

  • Zinwell ZWX-G360

  • Zinwell ZWX-G361

  • Zonet ZEW1500

  • Zonet ZEW1600

[i386,amd64] The rsu(4) driver provices support for Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network adapters, including:

  • ASUS USB-N10

  • Belkin F7D1101 v1

  • D-Link DWA-131 A1

  • EDUP EP-MS150N(W)

  • Hercules HWGUn-54

  • Hercules HWNUm-300

  • Planex GW-USNano

  • Sitecom WL-349 v1

  • Sitecom WL-353

  • Sweex LW154

  • TRENDnet TEW-648UB

  • TRENDnet TEW-649UB

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

  • 3Com Aolynk WUB320g

  • Abocom WUG2700

  • Airlink101 AWLL5025

  • ASUS WL-167g ver 2

  • Belkin F5D7050 ver 3

  • Belkin F5D9050 ver 3

  • Buffalo WLI-U2-SG54HP

  • Buffalo WLI-U2-SG54HG

  • Buffalo WLI-U2-G54HP

  • Buffalo WLI-UC-G

  • CNet CWD-854 ver F

  • Conceptronic C54RU ver 2

  • Corega CG-WLUSB2GO

  • D-Link DWA-110

  • D-Link DWA-111

  • D-Link DWL-G122 rev C1

  • D-Link WUA-1340

  • Digitus DN-7003GR

  • Edimax EW-7318USG

  • Gigabyte GN-WB01GS

  • Gigabyte GN-WI05GS

  • Hawking HWUG1

  • Hawking HWU54DM

  • Hercules HWGUSB2-54-LB

  • Hercules HWGUSB2-54V2-AP

  • LevelOne WNC-0301USB v3

  • Linksys WUSB54G rev C

  • Linksys WUSB54GR

  • Planex GW-US54HP

  • Planex GW-US54Mini2

  • Planex GW-USMM

  • Senao NUB-3701

  • Sitecom WL-113 ver 2

  • Sitecom WL-172

  • Sweex LW053

  • TP-LINK TL-WN321G

[i386,amd64] The run(4) driver supports the following wireless adapters:

  • Airlink101 AWLL6090

  • ASUS USB-N11

  • ASUS USB-N13 ver. A1

  • ASUS USB-N66

  • ASUS WL-160N

  • Belkin F5D8051 ver 3000

  • Belkin F5D8053

  • Belkin F5D8055

  • Belkin F6D4050 ver 1

  • Belkin F9L1103

  • Buffalo WLI-UC-AG300N

  • Buffalo WLI-UC-G300N

  • Buffalo WLI-UC-G301N

  • Buffalo WLI-UC-GN

  • Buffalo WLI-UC-GNM

  • Buffalo WLI-UC-GNM2

  • Corega CG-WLUSB2GNL

  • Corega CG-WLUSB2GNR

  • Corega CG-WLUSB300AGN

  • Corega CG-WLUSB300GNM

  • D-Link DWA-130 rev B1

  • D-Link DWA-140 rev B1, B2, B3, D1

  • D-Link DWA-160 rev B2

  • D-Link DWA-162

  • DrayTek Vigor N61

  • Edimax EW-7711UAn

  • Edimax EW-7711UTn

  • Edimax EW-7717Un

  • Edimax EW-7718Un

  • Edimax EW-7733UnD

  • Gigabyte GN-WB30N

  • Gigabyte GN-WB31N

  • Gigabyte GN-WB32L

  • Hawking HWDN1

  • Hawking HWUN1

  • Hawking HWUN2

  • Hercules HWNU-300

  • Linksys WUSB54GC v3

  • Linksys WUSB600N

  • Logitec LAN-W150N/U2

  • Mvix Nubbin MS-811N

  • Planex GW-USMicroN

  • Planex GW-US300MiniS

  • Sitecom WL-182

  • Sitecom WL-188

  • Sitecom WL-301

  • Sitecom WL-302

  • Sitecom WL-315

  • SMC SMCWUSBS-N2

  • Sweex LW303

  • Sweex LW313

  • TP-LINK TL-WDN3200

  • TP-LINK TL-WN727N v3

  • Unex DNUR-81

  • Unex DNUR-82

  • ZyXEL NWD2705

  • ZyXEL NWD210N

  • ZyXEL NWD270N

The uath(4) driver should work with the following adapters:

  • Compex WLU108AG

  • Compex WLU108G

  • D-Link DWL-G132

  • IODATA WN-G54/US

  • MELCO WLI-U2-KAMG54

  • Netgear WG111T

  • Netgear WG111U

  • Netgear WPN111

  • Olitec 000544

  • PLANET WDL-U357

  • Siemens Gigaset 108

  • SMC SMCWUSBT-G

  • SMC SMCWUSBT-G2

  • SparkLAN WL-785A

  • TP-Link TL-WN620G

  • TRENDware International TEW-444UB

  • TRENDware International TEW-504UB

  • Unex Technology UR054ag

  • ZyXEL XtremeMIMO M-202

An up to date list can be found at http://customerproducts.atheros.com/customerproducts/default.asp.

The upgt(4) driver supports USB 2.0 Conexant/Intersil PrismGT series wireless adapters based on the GW3887 chipset, among them:

  • Belkin F5D7050 (version 1000)

  • Cohiba Proto Board

  • D-Link DWL-G120 Cohiba

  • FSC Connect2Air E-5400 USB D1700

  • Gigaset USB Adapter 54

  • Inventel UR045G

  • SMC EZ ConnectG SMC2862W-G

  • Sagem XG703A

  • Spinnaker DUT

  • Spinnaker Proto Board

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

  • AMIT WL532U

  • ASUS WL-167g

  • Belkin F5D7050 v2000

  • Buffalo WLI-U2-KG54-AI

  • CNet CWD-854

  • Compex WLU54G 2A1100

  • Conceptronic C54RU

  • D-Link DWL-G122 b1

  • Dynalink WLG25USB

  • E-Tech WGUS02

  • Gigabyte GN-WBKG

  • Hercules HWGUSB2-54

  • KCORP LifeStyle KLS-685

  • Linksys WUSB54G v4

  • Linksys WUSB54GP v4

  • MSI MS-6861

  • MSI MS-6865

  • MSI MS-6869

  • NovaTech NV-902

  • OvisLink Evo-W54USB

  • SerComm UB801R

  • SparkLAN WL-685R

  • Surecom EP-9001-g

  • Sweex LC100060

  • Tonze UW-6200C

  • Zinwell ZWX-G261

  • Zonet ZEW2500P

An up to date list can be found at http://ralink.rapla.net/.

The urtw(4) driver supports Realtek RTL8187B/L based wireless network devices, including:

  • Belkin F5D7050E

  • Linksys WUSB54GCv2

  • Netgear WG111v2

  • Netgear WG111v3

  • Safehome WLG-1500SMA5

  • Shuttle XPC Accessory PN20

  • Sitecom WL168v1

  • Sitecom WL168v4

  • SureCom EP-9001-g(2A)

  • TRENDnet TEW-424UB V3.xR

The urtwn(4) driver supports Realtek RTL8188CU/RTL8188EU/RTL8192CU based USB IEEE 802.11b/g/n wireless network adapters, including:

  • ASUS USB-N10 NANO

  • Belkin F7D1102 Surf Wireless Micro

  • D-Link DWA-125 rev D1

  • D-Link DWA-131

  • Edimax EW-7811Un

  • Netgear WNA1000M

  • Realtek RTL8192CU

  • Realtek RTL8188CUS

  • TP-LINK TL-WN723N v3

  • TP-LINK TL-WN725N v2

[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:

  • 3COM 3CRUSB10075

  • Acer WLAN-G-US1

  • Airlink+ AWLL3025

  • Airlink 101 AWLL3026

  • AOpen 802.11g WL54

  • Asus A9T integrated wireless

  • Asus WL-159g

  • Belkin F5D7050 v.4000

  • Billion BiPAC 3011G

  • Buffalo WLI-U2-KG54L

  • CC&C WL-2203B

  • DrayTek Vigor 550

  • Edimax EW-7317UG

  • Edimax EW-7317LDG

  • Fiberline Networks WL-43OU

  • iNexQ UR055g

  • Linksys WUSBF54G

  • Longshine LCS-8131G3

  • MSI US54SE

  • MyTek MWU-201 USB adapter

  • Philips SNU5600

  • Planet WL-U356

  • Planex GW-US54GZ

  • Planex GW-US54GZL

  • Planex GW-US54Mini

  • Safecom SWMULZ-5400

  • Sagem XG 760A

  • Sagem XG 76NA

  • Sandberg Wireless G54 USB

  • Sitecom WL-113

  • SMC SMCWUSB-G

  • Sweex wireless USB 54 Mbps

  • Tekram/Siemens USB adapter

  • Telegent TG54USB

  • Trendnet TEW-424UB rev A

  • Trendnet TEW-429UB

  • TwinMOS G240

  • Unicorn WL-54G

  • US Robotics 5423

  • X-Micro XWL-11GUZX

  • Yakumo QuickWLAN USB

  • Zonet ZEW2501

  • ZyXEL ZyAIR G-202

  • ZyXEL ZyAIR G-220

3.6. Miscellaneous Networks

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

  • Cronyx Tau-PCI/32

  • Cronyx Tau-PCI/32-Lite

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

  • Cronyx Sigma-22, Sigma-24

  • Cronyx Sigma-100

  • Cronyx Sigma-400, Sigma-401, Sigma-404, Sigma-410, Sigma-440

  • Cronyx Sigma-500

  • Cronyx Sigma-703

  • Cronyx Sigma-800, Sigma-801, Sigma-810, Sigma-840

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

  • Cronyx Tau-PCI

  • Cronyx Tau-PCI/R

  • Cronyx Tau-PCI-L

  • Cronyx Tau-PCI-L/R

  • Cronyx Tau-PCI-E1

  • Cronyx Tau-PCI-G703

  • Cronyx Tau-PCI-2E1

  • Cronyx Tau-PCI-4E1

  • Cronyx Tau-PCI-E3

  • Cronyx Tau-PCI-T3

  • Cronyx Tau-PCI-STS1

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

  • Cronyx Tau (RS-232/V.35)

  • Cronyx Tau/R (RS-530/RS-449)

  • Cronyx Tau/E1 (fractional E1)

  • Cronyx Tau/G703 (unframed E1)

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

  • SMC90c26

  • SMC90c56

  • SMC90c66 in '56 compatibility mode.

3.7. 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:

  • NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 UARTs.

  • SCC: serial communications controllers supported by the scc(4) device driver.

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

  • SAB82532: Siemens SAB 82532 based serial communications controllers.

  • Z8530: Zilog 8530 based serial communications controllers.

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

  • ARNET 8 port serial card using shared IRQ

  • ARNET (now Digiboard) Sync 570/i high-speed + serial

[i386] Boca multi-port serial cards

  • Boca BB1004 4-Port serial card (Modems + not supported)

  • Boca IOAT66 6-Port serial card (Modems + supported)

  • Boca BB1008 8-Port serial card (Modems + not supported)

  • Boca BB2016 16-Port serial card (Modems + supported)

[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)

  • [amd64, i386] Actiontech 56K PCI

  • [amd64, i386] Avlab Technology, PCI IO + 2S and PCI IO 4S

  • [amd64, i386] Comtrol RocketPort + 550

  • [amd64, i386] Decision Computers PCCOM + 4-port serial and dual port RS232/422/485

  • [ia64] Diva Serial (GSP) Multiport UART

  • [amd64, i386] Dolphin Peripherals + 4025/4035/4036

  • [amd64, i386] IC Book Labs Dreadnought + 16x Lite and Pro

  • [amd64, i386] Lava Computers + 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550

  • [amd64, i386] Middle Digital, Weasle + serial port

  • [amd64, i386] Moxa Industio CP-114, + Smartio C104H-PCI and C168H/PCI

  • [amd64, i386] NEC PK-UG-X001 and + PK-UG-X008

  • [amd64, i386] Netmos NM9835 + PCI-2S-550

  • [amd64, i386] Oxford Semiconductor + OX16PCI954 PCI UART

  • [amd64, i386] Syba Tech SD-LAB + PCI-4S2P-550-ECP

  • [amd64, i386] SIIG Cyber I/O PCI + 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber 2P1S PCI + 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber 2S1P PCI + 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber 4S PCI + 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber Serial (Single + and Dual) PCI 16C550/16C650/16C850

  • [amd64, i386] Syba Tech + Ltd. PCI-4S2P-550-ECP

  • [amd64, i386] Titan PCI-200H and + PCI-800H

  • [amd64, i386] US Robotics (3Com) 3CP5609 + modem

  • [amd64, i386] VScom PCI-400 and + PCI-800

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

[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)

  • PC-9801 on-board

  • PC-9821 2'nd CCU (flags 0x12000000)

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

  • COM2 (flags 0x01000000)

  • COM3 (flags 0x02000000)

[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.8. Sound Devices

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

  • Analog Devices AD1816

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

  • Avance Logic ALS4000

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

  • ATI IXP 200

  • ATI IXP 300

  • ATI IXP 400

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

  • CS4231 on SBus based UltraSPARC

  • CS4231 on PCI/EBus based UltraSPARC

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

  • CMedia CMI8338A

  • CMedia CMI8338B

  • CMedia CMI8738

  • CMedia CMI8738B

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

  • Crystal Semiconductor CS4281

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

  • Crystal Semiconductor CS4280

  • Crystal Semiconductor CS4610

  • Crystal Semiconductor CS4611

  • Crystal Semiconductor CS4614

  • Crystal Semiconductor CS4615

  • Crystal Semiconductor CS4622

  • Crystal Semiconductor CS4624

  • Crystal Semiconductor CS4630

  • Genius Soundmaker 128 Value

  • Hercules Game Theatre XP

  • Turtle Beach Santa Cruz

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:

  • Yamaha DS-1

  • Yamaha DS-1E

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

  • Creative SoundBlaster Live! (EMU10K1 Chipset)

  • Creative SoundBlaster Audigy (EMU10K2 Chipset)

  • Creative SoundBlaster Audigy 2 (EMU10K2 Chipset)

  • Creative SoundBlaster Audigy 2 (EMU10K3 Chipset)

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

  • Creative Sound Blaster Live! (EMU10K1 Chipset). Both PCM and MIDI interfaces are available.

  • Creative Sound Blaster Audigy (CA0100 and CA0101 Chipset). PCM and two MIDI interfaces available.

  • Creative Sound Blaster Audigy 2 and Creative Sound Blaster Audigy 4 (CA0102 Chipset). PCM support is limited to 48kHz/16 bit stereo (192kHz/24 bit part of this chipset is not supported).

  • Creative Sound Blaster Audigy 2 Value (CA0108 Chipset). PCM support is limited to 48kHz/16 bit stereo (192kHz/24 bit part of this chipset is not supported). There is no MIDI support for this card.

The snd_emu10kx(4) driver does not support the following sound cards (although they have names similar to some supported ones):

  • Creative Sound Blaster Live! 24-Bit, identified by FreeBSD as

  • Creative Sound Blaster Audigy LS / ES, identified by FreeBSD as

  • All other Creative sound cards with -DAT chipsets.

  • All Creative X-Fi series sound cards.

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

  • M-Audio Audiophile 2496

  • M-Audio Delta Dio 2496

  • Terratec DMX 6fire

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

  • Audiotrak Prodigy 7.1

  • Audiotrak Prodigy 7.1 LT

  • Audiotrak Prodigy 7.1 XT

  • Audiotrak Prodigy HD2

  • ESI Juli@

  • M-Audio Audiophile 192

  • M-Audio Revolution 5.1

  • M-Audio Revolution 7.1

  • Terratec Aureon 5.1 Sky

  • Terratec Aureon 7.1 Space

  • Terratec Aureon 7.1 Universe

  • Terratec PHASE 22

  • Terratec PHASE 28

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

  • Creative CT5880-A

  • Creative CT5880-C

  • Creative CT5880-D

  • Creative CT5880-E

  • Creative SB AudioPCI CT4730

  • Ensoniq AudioPCI ES1370

  • Ensoniq AudioPCI ES1371-A

  • Ensoniq AudioPCI ES1371-B

  • Ensoniq AudioPCI ES1373-A

  • Ensoniq AudioPCI ES1373-B

  • Ensoniq AudioPCI ES1373-8

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

  • Ensoniq ESS ISA PnP/non-PnP

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

  • Forte Media FM801

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

  • Gravis UltraSound MAX

  • Gravis UltraSound PnP

[i386,amd64] The snd_hda(4) driver supports controllers having PCI class 4 (multimedia) and subclass 3 (HDA), compatible with Intel HDA specification.

The snd_hda(4) driver supports more than two hundred different controllers and CODECs. There is no sense to list all of them here, as in most cases specific CODEC configuration and wiring are more important then type of the CODEC itself.

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

  • RME HDSPe AIO

  • RME HDSPe RayDAT

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

  • AMD 768

  • AMD 8111

  • Intel 443MX

  • Intel ICH

  • Intel ICH revision 1

  • Intel ICH2

  • Intel ICH3

  • Intel ICH4

  • Intel ICH5

  • Intel ICH6

  • Intel ICH7

  • NVIDIA nForce

  • NVIDIA nForce2

  • NVIDIA nForce2 400

  • NVIDIA nForce3

  • NVIDIA nForce3 250

  • NVIDIA nForce4

  • SiS 7012

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

  • ESS Technology Maestro-1

  • ESS Technology Maestro-2

  • ESS Technology Maestro-2E

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

  • ESS Technology Allegro-1

  • ESS Technology Maestro3

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

  • AD1845

  • AD1848

  • Aztech 2320

  • CMedia CMI8330

  • Crystal Semiconductor CS4231

  • Crystal Semiconductor CS4232

  • Crystal Semiconductor CS4234

  • Crystal Semiconductor CS4235

  • Crystal Semiconductor CS4236

  • Crystal Semiconductor CS4237

  • ENSONIQ SoundscapeVIVO ENS4081

  • NeoMagic 256AV (non-AC97)

  • OPTi 924

  • OPTi 925

  • OPTi 930

  • OPTi 931

  • OPTi 933

  • Yamaha OPL-SA2

  • Yamaha OPL-SA3

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

  • NeoMagic 256AV

  • NeoMagic 256ZX

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

  • Avance Asound 110

  • Avance Logic ALS100+

  • Avance Logic ALS120

  • Creative SB16

  • Creative SB32

  • Creative AWE64

  • Creative AWE64 Gold

  • Creative ViBRA16C

  • Creative ViBRA16X

  • ESS ES1681

  • ESS ES1688

  • ESS ES1868

  • ESS ES1869

  • ESS ES1878

  • ESS ES1879

  • ESS ES1888

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

  • ESS Solo-1 (ES1938 Chipset)

  • ESS Solo-1E (ES1946 Chipset)

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:

  • AK4358

  • AK4381

  • AK4396

  • AK4524

  • AK4528

  • WM8770

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

  • Acer Labs M5451

  • SIS 7018

  • Trident 4DWave DX

  • Trident 4DWave NX

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

  • VIA VT8233

  • VIA VT8233A

  • VIA VT8233C

  • VIA VT8235

  • VIA VT8237

  • VIA VT8251

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

  • VIA 82C686A

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

  • S3 SonicVibes

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

  • NEC A-MATE internal sound

  • Q-Vision WaveStar, WaveMaster

[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)

  • Q-Vision WaveStar

3.9. 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:

  • AOpen VA1000

  • AVerMedia AVerTV Studio

  • AVerMedia TF/FM-98

  • ATI TV Wonder VE

  • Hauppauge WinCast/TV

  • Hauppauge WinTV-Go-FM

  • Hauppauge WinTV-pci

  • Hauppauge WinTV-radio

  • Intel Smart Video Recorder III

  • KWORLD PCI TV Tuner

  • Miro PC TV

  • Pinnacle PCTV Pro

  • Pinnacle PCTV Rave

  • PixelView PlayTV PAK

  • PixelView PlayTV Pro (rev 4C, 9D)

  • SIGMA TV II

  • STB TV PCI Television Tuner

  • Super TV Tuner

  • TerraTec TValue

  • V-Stream XPERT TV-PVR 878

  • Video Highway XTreme

  • VideoLogic Captivator PCI

[i386] Connectix QuickCam

3.10. 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:

[amd64, i386, ia64, pc98] + USB Ethernet adapters can be found in the section listing + Ethernet + interfaces.

Note:

[amd64, i386, ia64, pc98] + 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:

  • AcerLabs M5237 (Aladdin-V)

  • AMD-756

  • OPTi 82C861 (FireLink)

  • NEC uPD 9210

  • CMD Tech 670 (USB0670)

  • CMD Tech 673 (USB0673)

  • NVIDIA nForce3

  • Sun PCIO-2 (RIO USB)

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

  • Intel 82371AB/EB (PIIX4)

  • Intel 82371SB (PIIX3)

  • VIA 83C572

[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

  • Assist Computer Systems PC Camera C-M1

  • ActiveWire I/O Board

  • Creative Technology Video Blaster WebCam Plus

  • D-Link DSB-R100 USB Radio (ufm(4) driver)

  • Mirunet AlphaCam Plus

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

  • Diamond MultiMedia Rio 500

  • Diamond MultiMedia Rio 600

  • Diamond MultiMedia Rio 800

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

  • 3Com 5605

  • Curitel PC5740 Wireless Modem

  • Kyocera AH-K3001V Mobile Phone(WILLCOM)

  • Kyocera WX320K Mobile Phone(WILLCOM)

  • Metricom Ricochet GS USB wireless modem

  • Sierra MC5720 Wireless Modem

  • Yamaha Broadband Wireless Router RTW65b

  • ELSA MicroLink 56k USB modem

  • Sony Ericsson W810i phone

  • Sonim XP5300 Force

[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:

  • ATen parallel printer adapter

  • Belkin F5U002 parallel printer adapter

  • Canon BJ F850, S600

  • Canon LBP-1310, 350

  • Entrega USB-to-parallel printer adapter

  • Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)

  • Oki Data MICROLINE ML660PS

  • Seiko Epson PM-900C, 880C, 820C, 730C

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

  • AnyData ADU-500A EV-DO modem

  • AnyData ADU-E100A (no EV-DO mode support)

  • Belkin F5U103

  • Belkin F5U120

  • e-Tek Labs Kwik232

  • GoHubs GoCOM232

  • Peracom single port serial adapter

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

[i386,pc98,amd64] The

  • B&B Electronics USB->RS422/485 adapter

  • Elexol USB MOD1 and USB MOD3

  • HP USB-Serial adapter shipped with some HP laptops

  • Inland UAS111

  • QVS USC-1000

  • Buffalo PC-OP-RS / Kurouto-shikou KURO-RS universal remote

  • Prologix GPIB-USB Controller

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

  • ADLINK ND-6530 USB-Serial Adapter

  • Alcatel One Touch 535/735 Phone

  • Alcor AU9720 USB-RS232 Serial Adapter

  • AlDiga AL-11U Modem

  • Alltronix ACM003U00 Modem

  • Anchor Serial adapter

  • ATEN UC-232A

  • BAFO BF-800 and BF-810

  • Belkin F5U257

  • BenQ S81 Phone

  • Corega CG-USBRS232R Serial Adapter

  • Cressi Edy (Seiko) Diving Computer

  • ELECOM UC-SGT Serial Adapter

  • HAL Corporation Crossam2+USB IR commander

  • Hama USB RS-232 Serial Adapter

  • Hamlet exagerate XURS232

  • HP LD220 Point-Of-Sale (POS) Display

  • IOGEAR UC-232A

  • I/O DATA USB-RSAQ, USB-RSAQ2, USB-RSAQ3 and USB-RSAQ5

  • iTegno WM1080A GSM/GFPRS Modem

  • iTegno WM2080A CDMA Modem

  • Leadtek 9531 GPS

  • Micromax 610U Modem

  • Microsoft Palm 700WX

  • Mobile Action MA-620 Infrared Adapter

  • Motorola Cables

  • Nokia CA-42 Cable

  • OTI DKU-5 cable

  • Panasonic TY-TP50P6-S flat screen

  • PLX CA-42 Phone Cable

  • PLANEX USB-RS232 URS-03

  • Prolific Generic USB-Serial Adapters

  • Prolific Pharos USB-Serial Adapter

  • RATOC REX-USB60

  • Radio Shack USB Serial Cable

  • Sagem USB-Serial Adapter

  • Samsung I330 Phone Cradle

  • Sandberg USB to Serial Link (model number 133-08)

  • Sanwa KB-USB2 Multimeter cable

  • Siemens/BenQ EF81, SX1, X65 and X75 Mobile Phones

  • Sitecom USB-Serial Adapter

  • SMART Technologies USB-Serial Adapter

  • Sony QN3 Phone Cable

  • Sony Ericsson Datapilot

  • Sony Ericsson DCU-10 and DCU-11 (Susteen) USB Cables

  • SOURCENEXT KeikaiDenwa 8 (with and without charger)

  • Speed Dragon USB-Serial Cable

  • Syntech CPT-8001C Barcode Scanner

  • TDK UHA6400 and UPA9664 USB-PHS Adapters

  • TRENDnet USB to Serial Converter (TU-S9)

  • Tripp-Lite U209-000-R USB-Serial Adapter

  • UIC HCR331 Magnetic Stripe Card Reader

  • UIC MSR206 Magnetic Stripe Card Reader

  • Willcom W-SIM DD PHS terminal.(WS002IN)

  • YC-Cable USB-Serial Adapter

  • Zeagle N2iTion3 Diving Computer

The umct(4) driver supports the following adapters:

  • Belkin F5U109

  • Belkin F5U409

  • D-Link DU-H3SP USB BAY Hub

  • Magic Control Technology USB-232

  • Sitecom USB-232

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

  • ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M

  • Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20

  • FujiFilm Zip USB Drive ZDR100 USB A

  • GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M

  • Huawei Mobile (SD slot)

  • IBM 32MB USB Memory Key (P/N 22P5296)

  • IBM 256MB USB Drive (MSYSTEM DiskOnKey2)

  • IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)

  • I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM only)

  • I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)

  • I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI

  • Iomega USB Zip 100/250 drive

  • Iomega Zip750 USB2.0 drive

  • Keian USB1.1/2.0 3.5-inch HDD Case KU350A

  • Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0

  • LaCie P3 HardDrive USB 200GB

  • Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive

  • Logitec Mobile USB Memory LMC-256UD

  • Logitec USB1.1/2.0 HDD Unit SHD-E60U2

  • Logitec USB Double-Speed Floppy Drive LFD-31U2

  • Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)

  • MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M

  • MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm

  • MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2

  • MELCO USB2.0 MO Drive MO-CH640U2

  • Matshita CF-VFDU03 floppy drive

  • Merlin SM300 MP3/WMA Player (256Mb)

  • Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable

  • Motorola E398 Mobile Phone (TransFlash memory card)

  • NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U

  • PNY Attache Flash Drive

  • Panasonic ("Matshita FDD CF-VFDU03")

  • Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW

  • Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW)

  • Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)

  • Panasonic floppy drive

  • Qware BeatZkey! Pro

  • RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B

  • SanDisk SDDR-31 (Compact Flash)

  • SanDisk SDDR-75 (only Compact Flash port works)

  • Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick)

  • Sony Portable CD-R/RW Drive CRX10U (CDROM only)

  • TEAC Portable USB CD-ROM Unit CD-110PU/210PU

  • Time DPA20B MP3 Player (1Gb)

  • Trek Thumbdrive 8MB

  • VAIO floppy drive (includes Y-E Data Flashbuster-U)

  • Y-E Data floppy drive (720/1.44/2.88Mb)

Among the supported digital cameras are:

  • Asahi Optical (PENTAX) Optio 230 & 330

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

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

  • Aceeca Mez1000 RDA

  • Handspring Treo

  • Handspring Treo 600

  • Handspring Visor

  • Palm I705

  • Palm M125

  • Palm M130

  • Palm M500

  • Palm M505

  • Palm M515

  • Palm Tungsten T

  • Palm Tungsten Z

  • Palm Zire

  • Palm Zire 31

  • Sony Clie 4.0

  • Sony Clie 4.1

  • Sony Clie 5.0

  • Sony Clie PEG-S500C

  • Sony Clie NX60

  • Sony Clie S360

  • Sony Clie TJ37

3.11. 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:

  • Adaptec AHA-894x/AIC-5800

  • Apple Pangea

  • Apple UniNorth

  • Intel 82372FB

  • IOGEAR GUF320

  • Lucent / Agere FW322/323

  • NEC uPD72861

  • NEC uPD72870

  • NEC uPD72871/2

  • NEC uPD72873

  • NEC uPD72874

  • National Semiconductor CS4210

  • Ricoh R5C551

  • Ricoh R5C552

  • Sony CX3022

  • Sony i.LINK (CXD3222)

  • Sun PCIO-2 (RIO 1394)

  • Texas Instruments PCI4410A

  • Texas Instruments PCI4450

  • Texas Instruments PCI4451

  • Texas Instruments TSB12LV22

  • Texas Instruments TSB12LV23

  • Texas Instruments TSB12LV26

  • Texas Instruments TSB43AA22

  • Texas Instruments TSB43AB21/A/AI/A-EP

  • Texas Instruments TSB43AB22/A

  • Texas Instruments TSB43AB23

  • Texas Instruments TSB82AA2

  • VIA Fire II (VT6306)

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

3.12. 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:

  • 3Com 3CREB96

  • AIPTEK BR0R02

  • EPoX BT-DG02

  • Mitsumi Bluetooth USB adapter

  • MSI MS-6967

  • TDK Bluetooth USB adapter

  • Broadcom Bluetooth USB adapter

3.13. Cryptographic Accelerators

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

  • Invertex AEON

  • Hifn 7751

  • PowerCrypt

  • XL-Crypt

  • NetSec 7751

  • Soekris Engineering vpn1201 and vpn1211

  • Soekris Engineering vpn1401 and vpn1411

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

  • SafeNet 1141

  • SafeNet 1741

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

  • Bluesteel 5501

  • Bluesteel 5601

  • Broadcom BCM5801

  • Broadcom BCM5802

  • Broadcom BCM5805

  • Broadcom BCM5820

  • Broadcom BCM5821

  • Broadcom BCM5822

  • Broadcom BCM5823

  • Broadcom BCM5825

3.14. Miscellaneous

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

  • MELCO IGM-PCM56K/IGM-PCM56KH

  • Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD + terminal)

[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:

  • [i386] AT-style keyboards (atkbd(4) + driver)

  • [amd64, i386] PS/2 keyboards + (atkbd(4) driver)

  • [pc98] Standard keyboards

  • [amd64, i386, ia64, pc98] + USB keyboards (ukbd(4) driver)

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

  • The atp(4) driver provides support for the following Product IDs:

    • PowerBooks, iBooks (IDs: 0x020e, 0x020f, 0x0210, 0x0214, 0x0215, 0x0216)

    • Core Duo MacBook & MacBook Pro (IDs: 0x0217, 0x0218, 0x0219)

    • Core2 Duo MacBook & MacBook Pro (IDs: 0x021a, 0x021b, 0x021c)

    • Core2 Duo MacBook3,1 (IDs: 0x0229, 0x022a, 0x022b)

    • 12 inch PowerBook and iBook (IDs: 0x030a, 0x030b)

    • 15 inch PowerBook (IDs: 0x020e, 0x020f, 0x0215)

    • 17 inch PowerBook (ID: 0x020d)

    • Almost all recent Macbook-Pros and Airs (IDs: 0x0223, 0x0223, 0x0224, 0x0224, 0x0225, 0x0225, 0x0230, 0x0230, 0x0231, 0x0231, 0x0232, 0x0232, 0x0236, 0x0236, 0x0237, 0x0237, 0x0238, 0x0238, 0x023f, 0x023f, 0x0240, 0x0241, 0x0242, 0x0243, 0x0244, 0x0245, 0x0246, 0x0247, 0x0249, 0x024a, 0x024b, 0x024c, 0x024d, 0x024e, 0x0252, 0x0252, 0x0253, 0x0253, 0x0254, 0x0254, 0x0259, 0x025a, 0x025b, 0x0262, 0x0262, 0x0263, 0x0264, 0x0290, 0x0291, 0x0292)

    To discover the product\-id of a touchpad, search for 'Trackpad' in the output of lshal(1) and look up the property

  • [amd64, i386, pc98] Bus mice and + compatible devices (mse(4) driver)

  • [amd64, i386] PS/2 mice and compatible + devices, including many laptop pointing devices + (psm(4) driver)

  • Serial mice and compatible devices

  • [amd64, i386, ia64, pc98] + USB mice (ums(4) driver)

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

  • NTT DoCoMo P-in Comp@ct

  • Panasonic KX-PH405

  • SII MC-P200

[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 http://www.FreeBSD.org/snapshots/.

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

All users of FreeBSD 10.0-STABLE should + subscribe to the <stable@FreeBSD.org> + mailing list.

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

\ No newline at end of file diff --git a/en_US.ISO8859-1/htdocs/releases/10.1R/readme.html b/en_US.ISO8859-1/htdocs/releases/10.1R/readme.html new file mode 100644 index 0000000000..646fb7eea6 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/10.1R/readme.html @@ -0,0 +1,212 @@ + +FreeBSD 10.0-STABLE README

FreeBSD 10.0-STABLE README

The FreeBSD Project

Copyright © 2000-2014 The FreeBSD Documentation + Project

FreeBSD is a registered trademark of + the FreeBSD Foundation.

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.

Motif, OSF/1, and UNIX are + registered trademarks and IT DialTone and The Open Group are + trademarks of The Open Group in the United States and other + countries.

SPARC, SPARC64, and + UltraSPARC are trademarks of SPARC International, Inc in the United + States and other countries. SPARC International, Inc owns all of the + SPARC trademarks and under licensing agreements allows the proper use + of these trademarks by its members.

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.

Last modified on 2014-08-26 by gjb.
Abstract

This document gives a brief introduction to FreeBSD + 10.0-STABLE. It includes some information on how to + obtain FreeBSD, a listing of various ways to contact the FreeBSD + Project, and pointers to some other sources of + information.

Table of Contents
1. Introduction
2. Obtaining FreeBSD
3. Contacting the FreeBSD Project
4. Further Reading
5. Acknowledgments

1. Introduction

This distribution is a snapshot of FreeBSD + 10.0-STABLE, the latest point along the 10.0-STABLE + branch.

1.1. About FreeBSD

FreeBSD is an operating system based on 4.4 BSD Lite for + AMD64 and Intel EM64T based PC hardware (amd64), Intel, + AMD, Cyrix or NexGen “x86” based PC hardware + (i386), Intel Itanium Processor based computers + (ia64), NEC PC-9801/9821 series PCs and compatibles + (pc98), and UltraSPARC® machines (sparc64). + Versions for the ARM® (arm), MIPS® (mips), and + PowerPC® (powerpc) architectures are currently under + development as well. FreeBSD works with a wide variety of + peripherals and configurations and can be used for everything + from software development to games to Internet Service + Provision.

This release of FreeBSD contains everything you need to run + such a system, including full source code for the kernel and + all utilities in the base distribution. With the source + distribution installed, you can literally recompile the entire + system from scratch with one command, making it ideal for + students, researchers, or users who simply want to see how it + all works.

A large collection of third-party ported software (the + “Ports Collection”) is also provided to make it + easy to obtain and install all your favorite traditional + UNIX® utilities for FreeBSD. Each “port” consists + of a set of scripts to retrieve, configure, build, and install + a piece of software, with a single command. Over + 24,000 ports, from editors to programming languages to + graphical applications, make FreeBSD a powerful and comprehensive + operating environment that extends far beyond what's provided + by many commercial versions of UNIX®. Most ports are also + available as pre-compiled “packages”, which can + be quickly installed from the installation program.

1.2. Target Audience

This snapshot is aimed + primarily at early adopters and various other users who want + to get involved with the ongoing development of FreeBSD. While + the FreeBSD development team tries its best to ensure that each + snapshot works as advertised, 10.0-STABLE is very + much a work-in-progress.

The basic requirements for using + this snapshot are technical proficiency with FreeBSD and an + understanding of the ongoing development process of FreeBSD + 10.0-STABLE (as discussed on the FreeBSD-STABLE mailing list).

For those more interested in doing + business with FreeBSD than in experimenting with new FreeBSD + technology, formal releases (such as 10.0-RELEASE) + are frequently more appropriate. Releases undergo a period of + testing and quality assurance checking to ensure high + reliability and dependability.

2. Obtaining FreeBSD

FreeBSD may be obtained in a variety of ways. This section + focuses on those ways that are primarily useful for obtaining a + complete FreeBSD distribution, rather than updating an existing + installation.

2.1. CDROM and DVD

FreeBSD -RELEASE distributions may be ordered on CDROM or DVD + from several publishers. This is frequently the most + convenient way to obtain FreeBSD for new installations, as it + provides a convenient way to quickly reinstall the system if + necessary. Some distributions include some of the optional, + precompiled “packages” from the FreeBSD Ports + Collection, or other extra material.

A list of the CDROM and DVD publishers known to the + project are listed in the “Obtaining + FreeBSD” appendix to the Handbook.

2.2. FTP

You can use FTP to retrieve FreeBSD and any or all of its + optional packages from ftp://ftp.FreeBSD.org/, + which is the official FreeBSD release site, or any of its + “mirrors”.

Lists of locations that mirror FreeBSD can be found in the + FTP + Sites section of the Handbook. + Finding a close (in networking terms) mirror from which to + download the distribution is highly recommended.

Additional mirror sites are always welcome. Contact + for more details on + becoming an official mirror site. You can also find useful + information for mirror sites at the Mirroring FreeBSD + article.

Mirrors generally contain the ISO images generally used to + create a CDROM of a FreeBSD release. They usually also contain + floppy disk images (for applicable platforms), as well as the + files necessary to do an installation over the network. + Finally mirrors sites usually contain a set of packages for + the most current release.

3. Contacting the FreeBSD Project

3.1. Email and Mailing Lists

For any questions or general technical support issues, + please send mail to the FreeBSD general questions mailing list.

If tracking the 10.0-STABLE development efforts, you + must join the FreeBSD-STABLE mailing list, in order to + keep abreast of recent developments and changes that may + affect the way you use and maintain the system.

Being a largely-volunteer effort, the FreeBSD Project is + always happy to have extra hands willing to help—there + are already far more desired enhancements than there is time + to implement them. To contact the developers on technical + matters, or with offers of help, please send mail to the + FreeBSD technical discussions mailing list.

Please note that these mailing lists can experience + significant amounts of traffic. If you + have slow or expensive mail access, or are only interested in + keeping up with major FreeBSD events, you may find it + preferable to subscribe instead to the FreeBSD announcements mailing list.

All of the mailing lists can be freely joined by anyone + wishing to do so. Visit the FreeBSD Mailman Info + Page. This will give you more information on joining + the various lists, accessing archives, etc. There are + a number of mailing lists targeted at special interest groups + not mentioned here; more information can be obtained either + from the Mailman pages or the mailing + lists section of the FreeBSD Web site.

Important:

Do not send email to the lists + asking to be subscribed. Use the Mailman interface + instead.

3.2. Submitting Problem Reports

Suggestions, bug reports and contributions of code are + always valued—please do not hesitate to report any + problems you may find. Bug reports with attached fixes are of + course even more welcome.

The preferred method to submit bug reports from a machine + with Internet connectivity is to use the + Bugzilla bug tracker. + “Problem Reports” (PRs) submitted in this way + will be filed and their progress tracked; the FreeBSD developers + will do their best to respond to all reported bugs as soon as + possible. A list of all + active PRs is available on the FreeBSD Web site; this + list is useful to see what potential problems other users have + encountered.

Note that send-pr(1) is deprecated.

For more information, “Writing + FreeBSD Problem Reports”, available on the FreeBSD + Web site, has a number of helpful hints on writing and + submitting effective problem reports.

4. Further Reading

There are many sources of information about FreeBSD; some are + included with this distribution, while others are available + on-line or in print versions.

4.1. Release Documentation

A number of other files provide more specific information + about this snapshot distribution. These files are + provided in various formats. Most distributions will include + both ASCII text (.TXT) and HTML + (.HTM) renditions. Some distributions + may also include other formats such as Portable Document + Format (.PDF).

  • README.TXT: This file, which + gives some general information about FreeBSD as well as + some cursory notes about obtaining a + distribution.

  • RELNOTES.TXT: The release + notes, showing what's new and different in FreeBSD + 10.0-STABLE compared to the previous release (FreeBSD + 10.0-RELEASE).

  • HARDWARE.TXT: The hardware + compatibility list, showing devices with which FreeBSD has + been tested and is known to work.

  • ERRATA.TXT: Release errata. + Late-breaking, post-release information can be found in + this file, which is principally applicable to releases + (as opposed to snapshots). It is important to consult + this file before installing a release of FreeBSD, as it + contains the latest information on problems which have + been found and fixed since the release was + created.

On platforms that support bsdinstall(8) (currently + amd64, i386, ia64, pc98, and + sparc64), these documents are generally available via + the Documentation menu during installation. Once the system + is installed, you can revisit this menu by re-running the + bsdinstall(8) utility.

Note:

It is extremely important to read the errata for any + given release before installing it, to learn about any + “late-breaking news” or post-release problems. + The errata file accompanying each release (most likely right + next to this file) is already out of date by definition, but + other copies are kept updated on the Internet and should be + consulted as the “current errata” for this + release. These other copies of the errata are located at + ../../../../releases/ + (as well as any sites which keep up-to-date mirrors of this + location).

4.2. Manual Pages

As with almost all UNIX® like operating systems, FreeBSD + comes with a set of on-line manual pages, accessed through the + man(1) command or through the hypertext + manual pages gateway on the FreeBSD Web site. In + general, the manual pages provide information on the different + commands and APIs available to the FreeBSD user.

In some cases, manual pages are written to give + information on particular topics. Notable examples of such + manual pages are tuning(7) (a guide to performance + tuning), security(7) (an introduction to FreeBSD security), + and style(9) (a style guide to kernel coding).

4.3. Books and Articles

Two highly-useful collections of FreeBSD-related information, + maintained by the FreeBSD Project, are the FreeBSD Handbook and FreeBSD + FAQ (Frequently Asked Questions document). On-line versions + of the Handbook and FAQ are always + available from the FreeBSD Documentation + page or its mirrors. If you install the + doc distribution set, you can use a Web + browser to read the Handbook and FAQ locally. In particular, + note that the Handbook contains a step-by-step guide to + installing FreeBSD.

A number of on-line books and articles, also maintained by + the FreeBSD Project, cover more-specialized, FreeBSD-related topics. + This material spans a wide range of topics, from effective use + of the mailing lists, to dual-booting FreeBSD with other + operating systems, to guidelines for new committers. Like the + Handbook and FAQ, these documents are available from the FreeBSD + Documentation Page or in the doc + distribution set.

A listing of other books and documents about FreeBSD can be + found in the bibliography + of the FreeBSD Handbook. Because of FreeBSD's strong UNIX® + heritage, many other articles and books written for UNIX® + systems are applicable as well, some of which are also listed + in the bibliography.

5. Acknowledgments

FreeBSD represents the cumulative work of many hundreds, if not + thousands, of individuals from around the world who have worked + countless hours to bring about this snapshot. For + a complete list of FreeBSD developers and contributors, please see + “Contributors + to FreeBSD” on the FreeBSD Web site or any of its + mirrors.

Special thanks also go to the many thousands of FreeBSD users + and testers all over the world, without whom this snapshot + simply would not have been possible.

This file, and other release-related documents, + can be downloaded from http://www.FreeBSD.org/snapshots/.

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

All users of FreeBSD 10.0-STABLE should + subscribe to the <stable@FreeBSD.org> + mailing list.

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

\ No newline at end of file diff --git a/en_US.ISO8859-1/htdocs/releases/10.1R/relnotes.html b/en_US.ISO8859-1/htdocs/releases/10.1R/relnotes.html new file mode 100644 index 0000000000..1631d6372e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/10.1R/relnotes.html @@ -0,0 +1,738 @@ + +FreeBSD 10.0-STABLE Release Notes

FreeBSD 10.0-STABLE Release Notes

The FreeBSD Project

Copyright © 2000-2014 The FreeBSD Documentation + Project

FreeBSD is a registered trademark of + the FreeBSD Foundation.

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

IEEE, POSIX, and 802 are registered + trademarks of Institute of Electrical and Electronics Engineers, + Inc. in the United States.

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, and + UltraSPARC are trademarks of SPARC International, Inc in the United + States and other countries. SPARC International, Inc owns all of the + SPARC trademarks and under licensing agreements allows the proper use + of these trademarks by its members.

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.

Last modified on 2014-09-25 by gjb.
Abstract

The release notes for FreeBSD 10.0-STABLE contain + a summary of the changes made to the FreeBSD base system on the + 10.0-STABLE development line. This document lists + applicable security advisories that were issued since the last + release, as well as significant changes to the FreeBSD kernel and + userland. Some brief remarks on upgrading are also + presented.

Table of Contents
1. Introduction
2. What's New
3. Upgrading from Previous Releases of FreeBSD

1. Introduction

This document contains the release notes for FreeBSD + 10.0-STABLE. It describes recently added, changed, or + deleted features of FreeBSD. It also provides some notes on + upgrading from previous versions of FreeBSD.

The snapshot distribution to + which these release notes apply represents a point along the + 10.0-STABLE development branch between 10.0-RELEASE and + the future 10.1-RELEASE. Information regarding pre-built, + binary snapshot distributions along this branch can be + found at http://www.FreeBSD.org/snapshots/.

All users are encouraged to consult the release errata + before installing FreeBSD. The errata document is updated with + “late-breaking” information discovered late in the + release cycle or after the release. Typically, it contains + information on known bugs, security advisories, and corrections + to documentation. An up-to-date copy of the errata for FreeBSD + 10.0-STABLE can be found on the FreeBSD Web site.

2. What's New

This section describes the most user-visible new or changed + features in FreeBSD since 10.0-RELEASE.

Typical release note items document recent security + advisories issued after 10.0-RELEASE, new drivers or hardware + support, new commands or options, major bug fixes, or + contributed software upgrades. They may also list changes to + major ports/packages or release engineering practices. Clearly + the release notes cannot list every single change made to FreeBSD + between releases; this document focuses primarily on security + advisories, user-visible changes, and major architectural + improvements.

2.1. Security Advisories

 

2.2. Kernel Changes

A new sysctl(8), + kern.panic_reboot_wait_time, has been + added, which allows controlling how long the system will wait + after panic(9) before rebooting. [r260431]

The vt(4) driver has been merged + from FreeBSD-CURRENT. To enable vt(4), enter + set kern.vty=vt at the loader(8) + prompt during boot, or add kern.vty=vt to + loader.conf(5) and reboot the system. [r262861]

Support for hwpmc(4) has been added + for PowerPC® 970 class processors. [r263122]

Support for ADT7460 and ADT7467 fan + controllers found in newer PowerBooks™ and + iBooks™ has been added to the iicbus(4) + driver. [r263197]

A panic triggered by removing + a urtwn(4) device has been fixed. [r263256]

A potential deadlock in the usb(4) + stack triggered by detaching USB devices that create character + devices has been fixed. [r263799]

Support for AMD® Family 16h sensor + devices has been added to amdtemp(4). [r263869]

The uslcom(4) driver has been + updated to support 26 new devices. [r265610]

A kernel bug that inhibited proper + functionality of the dev.cpu.0.freq + sysctl(8) on Intel® processors with Turbo + Boost™ enabled has been fixed. [r266165]

The uart(4) driver has been + updated to include support for the Intel® Lynx Point + KT AMT serial port. [r266436]

The radeonkms(4) + driver has been updated to include 32-bit ioctl(2) + support, allowing 32-bit applications to run on a 64-bit + system. [r266594]

A bug that would prevent + a jail(8) from setting the correct IPv4 source address + with some operations that required + security.jail.allow_raw_sockets has been + fixed. [r266718]

The hwpmc(4) driver has been + updated to support core events from the Atom™ + Silvermont architecture. [r266911]

The oce(4) driver has been updated + with vendor-supplied fixes for big endian support, and 20GB/s + and 25GB/s link speeds. [r268046]

The FreeBSD virtual memory subsystem + has been updated to implement “fast path” for + the page fault handler. [r270630]

The asmc(4) driver has been updated + to support the Apple® Mac Mini 3,1. [r271069]

The FreeBSD/powerpc64 default kernel + configuration, GENERIC64, has been + updated to enable the vt(4) console driver for the + Sony® Playstation 3™ platform. [r271111]

The + FreeBSD/powerpc ofwfb driver, used to + provide a graphics console when the vt(4) console driver + is used, has been modified to work with the x11-drivers/xf86-video-scfb + port. [r271116] + (Sponsored by + The FreeBSD Foundation)

Note:

If using an ATI graphics card with + the vt(4) driver, the x11-servers/xorg-server package + must be updated to version 1.12.4_8 or newer.

Several + performance enchancements to the vt(4) driver have been + merged from FreeBSD-CURRENT. [r271128] + (Sponsored by + The FreeBSD Foundation)

The default stack size + (KSTACK_PAGES) has been increased from + 4 to 8 for the + powerpc64 architecture. [r271153]

The FreeBSD/powerpc ATI driver + has been updated to support enabling and disabling the + Radeon 9700 backlight, found in the + Apple® PowerBook™ G4. [r271205]

Hardware context support has been + added to the drm/i915 driver, adding + support for Mesa 9.2 and + later. [r271816]

2.2.1. Virtualization Support

Support for Microsoft® Hyper-V + has been added to FreeBSD/i386 as loadable modules, however + not available in the GENERIC kernel + configuration. [r259450]

The bhyve(4) hypervisor now + supports soft power-off functionality via the ACPI S5 + state. [r261090]

Support for FreeBSD/i386 guests has been + added to bhyve(4). [r267399]

Support for virtualized + XSAVE has been added to bhyve(4), + allowing guest operating systems to use + XSAVE and + XSAVE-enabled features, such as + AVX. [r267427]

The bhyve(4) hypervisor now + supports booting from a zfs(8) filesystem. [r268932]

A new driver, virtio_random(4), + has been added, which allows FreeBSD virtual machines to + harvest entropy from the hypervisor. [r268933]

The bhyve(4) hypervisor has been + synced with the version in FreeBSD-CURRENT. [r270159]

A number of enhancements have been added, and several + bug fixes, including:

  • Post-mortem debugging has been added when + a guest virtual machine exits with an + “EPT Misconfiguration” + error.

  • The hypervisor virtio(4) API + has been expanded from 32- to 64-bit.

  • Support for identifying capabilities of the virtual + CPU has been added.

  • Support for emulating legacy x86 task + switching has been added.

  • Support to list the VT-x features in base kernel + dmesg(8) has been added.

  • Support for extended PCI configuration space + has been added.

2.2.2. ARM Support

The WANDBOARD + kernel configuration file has been added. [r259355]

Boot devices may now be specified by + setting a u-boot environment variable. If a boot device is + not specified, the probe mechanism will be used. To specify + the boot device, set the + loaderdev=device + u-boot environment variable. [r265067]

The nexus(4) driver + has been updated to include “Flattened Device + Tree” support, replacing the fdtbus(4) driver + in most cases. [r266000]

The gpioiic(4) and + gpioled(4) have been merged from FreeBSD-CURRENT. [r266105]

Support for hardware floating point was added to the + kernel, and enabled by default in the configuration files + for all platforms that contain the required hardware.

C++ exception handling now + works with GCC.

Support for SMP was added to the + kernel, and enabled by default in the configuration files + for all platforms that contain multi-core CPUs.

Support was added for:

  • CHROMEBOOK (Samsung Exynos 5250)

  • COLIBRI (Freescale Vybrid)

  • COSMIC (Freescale Vybrid)

  • IMX53-QSB (Freescale i.MX53)

  • QUARTZ (Freescale Vybrid)

  • RADXA (Rockchip rk30xx)

  • WANDBOARD (Freescale i.MX6)

An I2C driver was added for + the RaspberryPi.

Drivers have been added to support TI + platforms, such as BEAGLEBONE and PANDABOARD:

  • PRUSS (Programmable Realtime Unit Subsystem)

  • MBOX (Mailbox hardware)

  • SDHCI (new faster driver for + MMC/SD + storage)

  • PPS (Pulse Per Second input on a + GPIO/timer pin)

  • PWM (Pulse Width Modulation output)

  • ADC (Analog to Digital converter)

2.2.3. Boot Loader Changes

A kernel selection menu has been added + to loader(8). If the “beastie menu” is + enabled, the kernel to boot may be selected from the kernel + selection menu. Additional kernels may be listed in + loader.conf(5) as a comma- or space-separated list. By + default, kernel and + kernel.old are listed. [r262701]

The + sys/boot/ sources + have been rearranged, moving libstand(3) to a directory + indicating the library is built as 32-bit. [r271130] + (Sponsored by + The FreeBSD Foundation)

The + libstand(3) library has been updated to produce + a 64-bit shared library for the FreeBSD/amd64 and + FreeBSD/powerpc64 architectures. [r271135] + (Sponsored by + The FreeBSD Foundation)

Initial support for UEFI + boot has been added. [r271135] + (Sponsored by + The FreeBSD Foundation)

Three + new files are installed to /boot, supporting + UEFI boot: [r271136] + (Sponsored by + The FreeBSD Foundation)

  • boot1.efi: The + UEFI first stage bootstrap + file.

  • boot1.efifat: + A FAT filesystem image containing + an EFI system partition.

  • loader.efi: The third stage + bootstrap file.

Serial console and null console + support has been added to the UEFI boot + loader. [r271880]

Support has been added to cache + geli(8) passphrases during system boot. When a system + is configured with multiple GEOM_ELI + providers all using the same passphrase, the passphrase that + is cached after the first entry is used for the subsequent + GEOM_ELI provider. If the passphrase in + the cache is incorrect, then a prompt for the passphrase for + the next provider is displayed. [r272006]

2.2.4. Hardware Support

 

2.2.4.1. Multimedia Support

 

2.2.4.2. Network Interface Support

Support for Ralink RT5370 and + RT5372 chipsets has been added to the run(4) + driver. [r259453]

Firmware for the run(4) driver + has been updated to version 0.33. [r260120]

Support for the Ralink RT3593 + chipset has been added to the run(4) driver. [r261868]

The nve(4) driver is now + deprecated, and the nfe(4) driver should be used + instead. [r261972]

Support for the axge(4) driver + has been added. This driver supports the ASIX AX88178A + and AX88179 USB ethernet adapters. The AX88178A supports + USB 2.0, and the AX88179 supports USB 2.0 and 3.0. [r262137]

The urndis(4) driver has been + imported from OpenBSD. [r262363]

Support for multiple + transmitter/receiver queues has been added to the + vmx(4) driver. [r264866]

Note:

The FreeBSD guest operating system must have + MSIX enabled as a prerequisite for + multiple queues.

Support for the ASUS USB-N10 Nano + wireless card has been added to the urtwn(4) + driver. [r265345]

Transmission checksum offloading has + been disabled for the RTL8168C and RTL8168CP chipsets in + the re(4) driver for TCP and UDP frames. This is + due to a report of UDP datagrams with IP options + generating corrupt frames. [r266212]

Preliminary support has been added + to the urtwn(4) driver for the Realtek RTL8188EUS and + RTL8188ETV chipsets. [r266578]

A bug in the fast receiver buffer + recycle path has been fixed in the cxgbe(4) + driver. [r267694]

The bundled cxgbe(4) firmware for + T4 and T5 cards has been updated to version + 1.11.27.0. [r267849] + (Contributed / provided by + Chelsio)

The em(4) driver has been + updated to version 7.4.2. [r269196]

The ixgbe(4) tunables have been + renamed to match their sysctl(8) counterparts: [r269975]

Old NameNew Name
hw.ixgbe.enable_aimhw.ix.enable_aim
hw.ixgbe.max_interrupt_ratehw.ix.max_interrupt_rate
hw.ixgbe.rx_process_limithw.ix.rx_process_limit
hw.ixgbe.tx_process_limithw.ix.tx_process_limit
hw.ixgbe.enable_msixhw.ix.enable_msix
hw.ixgbe.num_queueshw.ix.num_queues
hw.ixgbe.txdhw.ix.txd
hw.ixgbe.rxdhw.ix.rxd
hw.ixgbe.unsupported_sfphw.ix.unsupported_sfp

Be sure to update loader.conf(5) if using the + old tunables before upgrading to + FreeBSD 10.0-STABLE.

The if_nf10bmac(4) driver has + been merged from FreeBSD-CURRENT to support the NetFPGA-10G + Embedded CPU Ethernet Core. [r270061]

The cxgbe(4) driver has been + updated to support netmap(4) for the T5 10G/40G + cards. [r270297]

The vtnet(4) driver has been + updated to support netmap(4). [r270509]

The urtwn(4) driver has been + updated to support the ASUS USB-AC51 wireless card. [r270514]

The Intel® XL710 ethernet + controller driver, ixlv(4), has been + merged from FreeBSD-CURRENT. [r270631]

2.2.5. Network Protocols

Support for the UDP-Lite protocol + (RFC 3828) has been added to the IPv4 and IPv6 + stacks. [r265946]

A bug in sctp(4) that would allow + two listening sockets bound to the same port has been + fixed. [r267771]

Kernel RPC code, which + is a base of NFS server took multiple optimizations, that + significantly improved its performance and + SMP scalability. + (Sponsored by + iXsystems)

The + iSCSI initiator has been updated to + support redirection handling when an + iSCSI device is configured with multiple + IP addresses across different network + interfaces. Previously, clients connecting to + such iSCSI devices could require + additional client-side configuration. [r269065] + (Sponsored by + The FreeBSD Foundation)

A new + sysctl(8), + kern.iscsi.fail_on_disconnection, has + been added, which allows iSCSI clients to + remove the attached disk device when the connection to the + target is dropped, where previously I/O would stop until the + connection is restored. [r265523] + (Sponsored by + The FreeBSD Foundation)

The + iSCSI transmit code has been optimized + to coalesce PDUs and avoid lock + contention. [r265524] + (Sponsored by + The FreeBSD Foundation)

Several performance optimizations have been + made to the iSCSI subsystem, including + deferring wakeup until enough data has been received to + read or write a file, reducing CPU usage + and throughput performance with large I/O workloads. [r265524] + (Sponsored by + iXsystems)

Support for hostname- and IP-based access + restriction has been added to the iSCSI + ctld(8) daemon. [r263720] + (Sponsored by + The FreeBSD Foundation)

The ctld(8) daemon has been updated + to allow overriding the “default” + portal-group configuration. [r263725] + (Sponsored by + The FreeBSD Foundation)

The ctld(8) daemon now includes a new + auth-group, “default”, + defaulting to deny, which is possible + to override. [r263726] + (Sponsored by + The FreeBSD Foundation)

2.2.6. Disks and Storage

The + geom(4) subsystem has been updated to support I/O + direct dispatch. When safety requirements are met, it + enables avoiding passing I/O requests to GEOM + g_up/g_down thread, + executing them directly in the caller context, avoiding + CPU bottlenecks in + g_up/g_down threads, + plus avoid several context switches per I/O. [r260385] + (Sponsored by + iXsystems)

The + geom(4) RAID driver has been + updated to support unmapped I/O. [r260385] + (Sponsored by + iXsystems)

The + cam(4) subsystem has been updated to support + finer-grained locking, direct dispatch and multi-queue, + which combined with geom(4) direct dispatch, reduces + lock congestion and improves SMP + scalability of the SCSI/ATA stack. [r260387] + (Sponsored by + iXsystems)

The geom(8) + GEOM_MULTIPATH class has been updated to + support automatic live partition resizing. [r260478]

The virtio_blk(4) driver has been + updated to support unmapped I/O. [r260857]

The virtio_scsi(4) driver has + been updated to support unmapped I/O. [r260858]

Support for LUN-based CD changers has + been removed from the cd(4) driver. [r264522]

Support for + BIO_DELETE has been added to zfs(8) + zvol volumes. [r264732]

Support for 9th generation HP host bus + adapter cards has been added to ciss(4). [r264734]

The + mpr(4) device has been added, + providing support for LSI Fusion-MPT 3 12Gb SCSI/SATA + controllers. [r265388] + (Sponsored by + LSI)

A new zvol property + volmode and sysctl(8) + vfs.zfs.vol.mode has been added to allow + switching zvol between three different + ways of exposing it to a user: geom, + dev and none. [r265678]

The + mrsas(4) driver has been added, providing support for + LSI MegaRAID SAS controllers. The mfi(4) driver will + attach to the controller, by default. To enable + mrsas(4) add hw.mfi.mrsas_enable=1 + to /boot/loader.conf, which turns off + mfi(4) device probing. [r265922] + (Sponsored by + LSI)

Note:

At this time, the mfiutil(8) utility and the FreeBSD + version of MegaCLI and + StorCli do not work with + mrsas(4).

Fixed accounting of + BIO_FLUSH operation in geom(8) + GEOM_DISK class [r266608]

The gstat(8) utility now has an + -o option, to display + “other” operations, such as + BIO_FLUSH. [r266610]

The mfi(4) driver has been + updated to include support for unmapped I/O. [r267084]

The hpt27xx(4) driver has been + updated with various vendor-supplied bug fixes. [r267457]

Support for unmapped I/O has been + added to the xen(4) blkfront + driver. [r270130] + (Sponsored by + Citrix Systems R&D)

The + geom(8) label class is now aware of + resized partitions. This corrects an issue where + geom resize would resize the partition, + but the label provider in /dev/gptid/ would not be + resized. [r259328] + (Sponsored by + The FreeBSD Foundation)

The gmirror(8) + utility now has a resize command, making + it easier to resize the size of a mirror when all of its + components have been replaced. [r260502]

Support for MegaRAID Fury cards has + been added to the mfi(4) driver. [r262967]

The aacraid(4) driver has been + updated to version 3.2.5. [r263024]

The GEOM_VINUM + option is now able to be built both directly into the kernel + or as a kldload(8) loadable module. [r265536]

The geom(8) + GEOM_PART class has been updated to + support automatic partition resizing. Changes to the + partition size are not saved to disk until + gpart commit is run, and prior to saving, + can be reverted with gpart undo. [r265912]

The geom_uncompress(4) module is + built by default which, similar to geom_uzip(4), + provides support for compressed, read-only disk + images. [r266220]

Support for the + disklabel64 partitioning scheme has been + added to gpart(8). [r268091]

A new sysctl(8) and + loader(8) tunable, + kern.geom.part.mbr.enforce_chs has been + added to the geom(8) MBR partition + class. When set to a non-zero value, + GEOM_PART_MBR will automatically + recalculate the user-specified offset and size for alignment + with the disk geometry. [r270552]

Many improvements to + the CAM Target Layer (CTL): + (Sponsored by + iXsystems)

  • Support for UNMAP, WRITE + SAME, COMPARE AND WRITE, + XCOPY and some other SCSI commands + was added to support VMWare VAAI and Microsoft ODX + storage acceleration.

  • The + READ/WRITE size + limitations were removed by supporting multiple + data moves per command. [r265642]

  • Finer-grained per-LUN locking and + multiple worker threads for better + SMP scapability. [r268556]

  • Memory consumption reduced by + several times by disabling some never used + functionality. [r269297]

  • The maximum number of + SCSI ports increased from 32 to + 128. [r269298]

  • Improved zvol + integration for better performance. [r269429]

The hptnr(4) driver has been + updated to version 1.0.1. [r270810] + (Contributed / provided by + HighPoint)

The mrsas(4) driver has been + added to the GENERIC kernel + configuration on amd64 and i386 + architectures. [r271234]

2.2.7. File Systems

The + vfs.zfs.zio.use_uma sysctl(8) has + been re-enabled. On multi-CPU machines with enough RAM, + this can easily double zfs(8) performance or reduce CPU + usage in half. It was originally disabled due to memory and + KVA exhaustion problem reports, which + should be resolved due to several changes in the VM + subsystem. [r260338]

A new flag, -R, + has been added to the fsck_ffs(8) utility. When used, + fsck_ffs(8) will restart itself when too many critical + errors have been detected. [r260178] + (Contributed / provided by + Netflix)

The zfs(8) filesystem has been + updated to implement “bookmarks”. See + zfs(8) for further details. [r263407]

The zfs(8) filesystem has been + updated to allow tuning the minimum “ashift” + value when creating new top-level virtual devices (vdevs). + To set the minimum ashift value, for example when creating + a zpool(8) on “Advanced Format” drives, + set the vfs.zfs.min_auto_ashift + sysctl(8) accordingly. [r266122]

The libzfs thread + pool API has been imported from + OpenSolaris, and adapted for FreeBSD. This change allows + parallel disk scanning, which can reduce zpool(8) + overall import time in some workloads. [r266612]

The restore(8) utility has been + updated to prevent assertion failures when restoring + a UFS filesystem dump to + a ZFS filesystem by writing restored + files in block sizes that are a multiple of 1024. [r269651]

Two sysctl(8)s have been added + to the zfs(8) filesystem: [r269774]

  • + vfs.zfs.mg_fragmentation_threshold: The + percentage of the metaslab group size that should be + considered eligible for allocation, unless all metaslab + groups within the metaslab class have also crossed this + threshold.

  • + vfs.zfs.metaslab.fragmentation_threshold: The + maximum percentage of metaslab fragmentation level to + keep their active state

The default zfs(8) + ARC hash table size has been increased, + and a new loader(8) tunable, + vfs.zfs.arc_average_blocksize, has been + added. Previously, the hash table could be too small, which + would lead to long hash chains and limit performance for + cached reads. The + vfs.zfs.arc_average_blocksize tunable + allows overriding the default block size. The previous + default was 65536, and default of the new loader(8) + tunable is 8192. [r269846]

The Fast File System + (FFS) has been updated to support + multi-threaded soft updates. Previously, soft updates were + handled by a single thread, and as of this change, now have + one thread per FFS mountpoint. [r270157]

The + new filesystem automount facility, autofs(5), has been + merged from FreeBSD-CURRENT. The new autofs(5) facility + is similar to that found in other UNIX®-like operating + systems, such as OS X™ and Solaris™. The + autofs(5) facility uses a Sun™-compatible + auto_master(5) configuration file, and is administered + with the automount(8) userland utility, and the + automountd(8) and autounmountd(8) daemons. [r270892] + (Sponsored by + The FreeBSD Foundation)

2.3. Userland Changes

A new flag is added to camcontrol(8), + -b, which outputs the existing buses and + their parents. [r260177] + (Sponsored by + Netflix)

The newsyslog(8) utility has been + updated to rotate files based on the actual file size instead + of the blocks on disk. This matches the behavior documented + in newsyslog.conf(5). [r262075]

The location of the rctl(8) + configuration file can now be overridden in rc.conf(5). + To use a non-default location, set + rctl_rules in rc.conf(5) to the + location of the file. [r262384]

The ATF test + suite has been updated to version 0.20. The test suite is + disabled by default in FreeBSD 10.1, and can be enabled by + adding WITH_TESTS=yes to + src.conf(5). [r262855]

The libucl library + (Unified Configuration Library) has been merged from + FreeBSD-CURRENT. [r263019]

The pkg(7) bootstrapping utility + has been synced with the version in FreeBSD-CURRENT. [r263020]

The zfs(8) userland utility has + been updated to include aliases for + snapshot, which allows use of zfs + list -t snap and zfs + snap. [r263403]

The zfs(8) userland utility has + been updated to include a new flag to zfs + list, -p, which when specified, + prints the output in a parsable format. [r263405]

The Blowfish password format + implementation has been updated. Support for $2b$ has + been added, allowing use of passwords greater than 256 + characters long. [r263783]

The iconv(3) library has been + updated to match NetBSD, providing several bug fixes. [r264497]

The date(1) utility has been + updated to include a new flag, -R, which + prints the date and time output as specified in RFC + 2822. [r265265]

The bc(1) utility has been updated + to version 1.1, in sync with the version in OpenBSD. [r265533]

The pmcstat(8) utility has been + updated to include a new flag, -a, which + when specified, produces a full stack track on the sampled + points. [r265604] + (Contributed / provided by + Netflix)

The netstat(8) and route(8) + utilities have been updated to include a shorthand equivalent + to the -f inet and -f + inet6 address specifiers, -4 + and -6, respectively. [r265701]

The crypt(3) library now defaults + to SHA512 for password hashing. [r265879]

The gvinum(8) utility has been + updated to allow forceful configuration reset with the + -f flag. Additionally, a bug that would + prevent -f from properly creating + a gvinum(8) configuration has been fixed. [r266014]

The login.conf(5) file now takes + precedence over the shell-specific environment files. In + particular, the PATH, + BLOCKSIZE variables are commented from + /usr/share/skel/dot.profile, and the + path, BLOCKSIZE, and + umask variables have been commented from + /usr/share/skel/dot.cshrc. [r266029]

The binmiscctl(8) userland utility + and related image activator features have been merged from + FreeBSD-CURRENT. [r266272]

The ps(1) utility has been + updated to include the -J flag, used to + filter output by matching jail(8) IDs and names. + Additionally, argument 0 can be used to + -J to only list processes running on the + host system. [r266279]

The top(1) utility has been updated + to filter by jail(8) ID or name, in followup to the + ps(1) change in r265229. [r266280]

The gstat(8) utility has been + updated to include a new flag, -o. When + set, gstat(8) will display statistics for operations + such as BIO_FLUSH. [r266610]

The fetch(3) library has been + updated to look for root SSL certificates + in /usr/local/etc/ssl/ + before /etc/ssl/. [r266632]

The clang(1)/llvm suite has been + updated to version 3.4.1. [r266715]

The Blowfish password format + has been changed to $2b$ by default. [r266816]

The amount of data collected for + hwpmc(4) has been updated to work with modern processors + and larger amounts of available memory. [r266888]

The pmcstat(8) utility has been + updated to include a new flag, -l, which + ends event collection after the specified number of + seconds. [r266890]

The mergemaster(8) utility has + been updated to avoid printing + “/var/tmp/temproot + disappeared” if there is nothing to compare. [r266953]

The FreeBSD installer, bsdinstall(8), + has been updated to include optional + geli(8)-encrypted or gmirror(8)-mirrored swap + devices when installing onto a full zfs(8) filesystem. + Additionally, the parent zfs(8) dataset is now configured + with lz4 compression enabled. [r267056]

The default newsyslog.conf(5) now + includes files in the + /etc/newsyslog.conf.d/ and + /usr/local/etc/newsyslog.conf.d/ + directories by default for newsyslog(8). [r267113]

The realpath(1) utility has been + updated to return ENOTDIR on paths + components “.” and “..” that are + not directories, such as /dev/null/. or /dev/null/... [r267161]

A new flag, “onifconsole” + has been added to /etc/ttys. This allows + the system to provide a login prompt via serial console if the + device is an active kernel console, otherwise it is equivalent + to off. [r267236]

Support for legacy + PCI devices has been removed from + bhyve(8). [r267341]

The bhyve(8) userland utility + has been updated to include SMBIOS support. A new flag has + been added, -U, which allows specifying the + UUID of the guest in the System Information structure. [r267450]

The FreeBSD Project has migrated + from the GNATS bug tracking system + to Bugzilla. The send-pr(1) + utility used for submitting problem reports has been replaced + with a stub shell script that instructs to use the Bugzilla + web interface. [r267734]

The patch(1) utility has been + updated to include a --dry-run flag, which + is equivalent to --check and + -C. [r267747]

A bug in bsdgrep(1) that would + prevent patterns from being matched under certain conditions + has been fixed. [r267878]

The procstat(1) utility has been + updated to include two new flags, -r and + -H. When -r is + specified, procstat(1) will print current resource usage + about the process(es). When -H is + specified, procstat(1) will print information about + threads rather than the process(es). [r267979]

Note:

The -H flag is currently only used + with -r to display resource usage for + individual threads, rather than the entire process.

The sed(1) utility has been + updated to include a new flag, -u, which + enables unbuffered output when specified. [r268019]

The mkimg(1) utility has been + merged from FreeBSD-CURRENT. [r268161]

The camcontrol(8) has been + updated to include a new persist command, + which allows issuing SCSI PERSISTENT RESERVE + IN and SCSI PERSISTENT RESERVE + OUT. [r268700] + (Sponsored by + Spectra Logic)

The gstat(8) utility has been + updated to include a new flag, -p, which + displays only physical providers when specified. [r268791]

The kldstat(8) utility has been + updated to allow -q to be specified when + also specifying -n + module.ko. [r268903]

The mkimg(1) utility has been + updated to include support for both fixed- and + dynamically-allocated images for the VHD + and VMDK formats. [r269177]

The random(4) entropy collection + script, /usr/libexec/save-entropy, no + longer runs within jail(8) environments. [r269220]

The bhyve(8) wrapper script, + /usr/share/examples/bhyve/vmrun.sh, + has been synced with FreeBSD-CURRENT. [r269397]

This update includes:

  • A new flag, -e, has been added, + which is used to set loader(8) environment + variables.

  • A new flag, -C, has been added, + which is used to specify the guest console device.

  • A new flag, -H, has been added, + which is used to pass the host path to + bhyveload(8).

  • Support for multiple disk and tap(4) devices + has been added.

  • The -I flag has been + removed.

The nfsd(8) server update to 4.1, + adding support for RFC5661, has merged from + FreeBSD-CURRENT. [r269398]

[ia64] The serial terminals + ttyu0 and ttyu1 have + been updated to onifconsole by default in + ttys(5), which either can be the serial console, + depending on the platform. [r269432]

The ping6(8) utility has been + updated to reset itimer when the maximum + number of packets to send have been reached. This prevents + ping6(8) from exiting when the interval in set to a small + value and a low number of packets to send has been + specified. [r269800]

The jail(8) utility has been + updated to support extra ifconfig(8) arguments for the + ip4.addr and ip6.addr + parameters. This change allows carp(4) interfaces to + be used within the jail(8). [r269805]

Support for generating and compiling + USDT DTrace + probes has been improved. DTrace + USDT files are now handled similar to + lex(1) and yacc(1) files, meaning support for + handling D files as part of the + build process is built into the SRCS + make(1) environment variable. [r269946]

The iscsictl(8) utility has been + updated to include a new flag, -M, which + allows modifying the iSCSI session + parameters without requiring the session to be removed and + added back. [r269968]

The mount_nfs(8) utility has been + updated to support specifying the NFS version as + a key=value pair + argument to the -o flag. For example, to + specify NFS version 4, the syntax to use is + -o vers=4. [r270043]

The devd(8) client socket type + has been changed to SOCK_SEQPACKET, + providing sequential packet support. [r270242] + (Sponsored by + Spectra Logic)

Support for the “account” + facility has been added to the pam_group(8) + module. [r270401]

The pathchk(1) utility has been + updated to ensure bytes greater than or equal to 128 are + considered non-portable. [r270890]

The + zdb(8) utility is now included in the set of applications + installed in the /rescue environment, making it + possible to examine zfs(8) filesystems when /usr is unavailable. [r270997] + (Contributed / provided by + FreeNAS)

Several libc improvements have been + merged from illumos™ and Apple®, providing better + internationalization support and POSIX® compliance.

Support for adding empty partitions has + been added to the mkimg(1) utility. [r271967]

2.3.1. /etc/rc.d Scripts

The network.subr + rc(8) script has been updated to loosen the requirement + of listing network aliases in numeric order. Previously, + a network alias of + _alias2 + would not be created if + _alias1 was + not defined. [r264438]

The service(8) utility has been + updated to check that the rc.d(8) directory exists + before traversing the directory. [r268098]

A regression introduced in + FreeBSD 10.0-RELEASE that would prevent proper IPv6 + allocation via the jail(8) rc(8) startup script + has been fixed. [r259141]

The rc(8) restriction requiring + mdconfig(8) devices defined in rc.conf(5) to be + listed sequentially has been removed. [r264438]

The sshd(8) rc.d(8) startup + script now generates ED25519 sshd(8) + host keys if keys do not already exist when + ssh_keygen_alg() is invoked. [r262566]

Support for vt(4) keyboard maps + has been added to the syscons + rc.d(8) startup script. [r271095]

Support for subdirectories within + /etc/rc.conf.d/service/ + has been added the rc.d(8). This allows creating + separate configuration files for services such as + netif, for example, where each network + interface can have a separate configuration file. [r271260]

2.4. Contributed Software

The xz(1) utility has been updated + to a post-5.0.5 snapshot. [r263285]

OpenSSH has + been updated to version 6.6p1. [r264377]

The nc(1) utility has been updated + to match the version in OpenBSD 5.5. [r264911]

Sendmail + has been updated to 8.14.9. [r266692]

The file(1) utility and + libmagic(3) library have been updated to 5.19. [r268515]

The byacc(1) parser has been + updated to version 20140422. [r268899]

The lldb(1) debugging library has + been updated to the r202189 snapshot. [r269024] + (Sponsored by + DARPA, AFRL)

The unbound(8) caching resolver and + ldns have been updated to version + 1.4.22. [r269257]

OpenSSL has + been updated to version 1.0.1i. [r269686]

The “lite” version of + Subversion included in the + FreeBSD base system and its dependencies have been + updated: [r269847]

  • apr has been + updated to version 1.5.1.

  • apr-util has been + updated to version 1.5.3.

  • serf has been + updated to version 1.3.7.

  • svnlite has been + updated to version 1.8.10.

The nvi(1) editor has been + update to version 2.1.2-c80f493b038. [r270026]

The fparseln(3) library has + been updated to version 1.7. [r270031]

The lukemftpd + FTP server has been removed from the + FreeBSD base system. [r270415]

The timezone database has been updated + to version tzdata2014f. [r270817]

OpenPAM has + been updated to Ourouparia (20140912). [r271947]

2.5. Ports/Packages Collection Infrastructure

 

2.6. Release Engineering and Integration

The services.mkdb(8) utility has + been updated to include endianness awareness, allowing the + services.db database to be created as + part of the release build, regardless of native- or + cross-built releases. [r263028]

The + release/ scripts have + been updated to produce UEFI-capable and + BIOS-capable CD-ROM ISOs as well as memory + stick images for the FreeBSD/amd64 architecture. [r271470] + (Sponsored by + The FreeBSD Foundation)

The + release/scripts/pkg-stage.sh script has + been updated to include a symlink to the on-disc version of + pkg(8) in the packages/ structure on the + DVD installer. This allows the pkg(7) bootstrap utility + to properly locate the Latest/pkg.txz + file on the DVD when REPOS_DIR is set to + /dist/packages/repos, + eliminating the need for a network connection or explicitly + providing the path to the version included on the DVD + installation medium. [r271943] + (Sponsored by + The FreeBSD Foundation)

2.7. Documentation

 

3. Upgrading from Previous Releases of FreeBSD

[amd64,i386] Binary upgrades between RELEASE versions + (and snapshots of the various security branches) are supported + using the freebsd-update(8) utility. The binary upgrade + procedure will update unmodified userland utilities, as well as + unmodified GENERIC kernel distributed as + a part of an official FreeBSD release. The freebsd-update(8) + utility requires that the host being upgraded have Internet + connectivity.

Source-based upgrades (those based on recompiling the FreeBSD + base system from source code) from previous versions are + supported, according to the instructions in + /usr/src/UPDATING.

Important:

Upgrading FreeBSD should only be attempted after + backing up all data and configuration + files.

This file, and other release-related documents, + can be downloaded from http://www.FreeBSD.org/snapshots/.

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

All users of FreeBSD 10.0-STABLE should + subscribe to the <stable@FreeBSD.org> + mailing list.

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

\ No newline at end of file