Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project
+ +$FreeBSD:
+release/8.0.0/release/doc/en_US.ISO8859-1/errata/article.sgml 145264 2005-04-19 09:42:25Z
+hrs $
+
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, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.
+ +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.
+++ +++This document lists errata items for FreeBSD 8.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 8.0-RELEASE will be maintained until the release of +FreeBSD 8.1-RELEASE.
+
This errata document contains “late-breaking news” about FreeBSD +8.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 8.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/.
+This file, and other release-related documents, can be +downloaded from http://www.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ + + diff --git a/en/releases/8.0R/hardware.html b/en/releases/8.0R/hardware.html new file mode 100644 index 0000000000..87163e6a4a --- /dev/null +++ b/en/releases/8.0R/hardware.html @@ -0,0 +1,10331 @@ + + + + +Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, +2008, 2009 The FreeBSD Documentation Project
+ +$FreeBSD:
+release/8.0.0/release/doc/en_US.ISO8859-1/hardware/article.sgml 197427 2009-09-23
+10:12:58Z marius $
+
FreeBSD is a registered trademark of the FreeBSD Foundation.
+ +AMD, Am486, Am5X86, AMD Athlon, AMD Duron, AMD Opteron, AMD-K6, Athlon, Élan, +Opteron, and PCnet are trademarks of Advanced Micro Devices, Inc.
+ +IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.
+ +Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.
+ +Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.
+ +Sun, Sun Microsystems, Java, Java Virtual Machine, JavaServer Pages, JDK, JRE, JSP, +JVM, Netra, Solaris, StarOffice, Sun Blade, Sun Enterprise, Sun Fire, SunOS, Ultra 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.
+This document contains the hardware compatibility notes for FreeBSD 8.0-RELEASE. It +lists the hardware platforms supported by FreeBSD, as well as the various types of +hardware devices (storage controllers, network interfaces, and so on), along with known +working instances of these devices.
+This section provides some architecture-specific information about the specific +processors and systems that are supported by each architecture.
+ +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”.
+ +The largest tested memory configuration to date is 64GB. SMP support has been recently +completed and is reasonably robust.
+ +In many respects, FreeBSD/amd64 is similar to FreeBSD/i386, in terms of drivers +supported. There may be some issues with 64-bit cleanliness in some (particularly older) +drivers. Generally, drivers that already function correctly on other 64-bit platforms +should work.
+ +FreeBSD/amd64 is a very young platform on FreeBSD. While the core FreeBSD kernel and +base system components are generally fairly robust, there are likely to still be rough +edges, particularly with third party packages.
+FreeBSD/i386 runs on a wide variety of “IBM PC compatible” machines. Due +to the wide range of hardware available for this architecture, it is impossible to +exhaustively list all combinations of equipment supported by FreeBSD. Nevertheless, some +general guidelines are presented here.
+ +Almost all i386™-compatible processors with a +floating point unit are supported. All Intel processors +beginning with the 80486 are supported, including the 80486, Pentium, Pentium Pro, Pentium II, Pentium III, Pentium 4, and variants thereof, such as the Xeon and Celeron® processors. +All i386-compatible AMD processors are also supported, +including the Am486®, Am5x86®, K5, AMD-K6® (and +variants), AMD Athlon (including Athlon-MP, +Athlon-XP, Athlon-4, and Athlon Thunderbird), and AMD Duron™ processors. The AMD Élan SC520 +embedded processor is supported. The Transmeta Crusoe is recognized and supported, as are +i386-compatible processors from Cyrix and NexGen.
+ +There is a wide variety of motherboards available for this architecture. Motherboards +using the ISA, VLB, EISA, AGP, and PCI expansion busses are well-supported. There is some +limited support for the MCA (“MicroChannel”) expansion bus used in the IBM +PS/2 line of PCs.
+ +Symmetric multi-processor (SMP) systems are generally supported by FreeBSD, although +in some cases, BIOS or motherboard bugs may generate some problems. Perusal of the +archives of the FreeBSD symmetric multiprocessing mailing list may yield some +clues.
+ +FreeBSD will take advantage of HyperThreading (HTT) support on Intel CPUs that support this feature. A kernel with the options SMP feature enabled will automatically detect the
+additional logical processors. The default FreeBSD scheduler treats the logical
+processors the same as additional physical processors; in other words, no attempt is made
+to optimize scheduling decisions given the shared resources between logical processors
+within the same CPU. Because this naive scheduling can result in suboptimal performance,
+under certain circumstances it may be useful to disable the logical processors with the
+the machdep.hlt_logical_cpus sysctl variable. It is also
+possible to halt any CPU in the idle loop with the machdep.hlt_cpus sysctl variable. The
+smp(4) manual
+page has more details.
FreeBSD will take advantage of Physical Address Extensions (PAE) support on CPUs that +support this feature. A kernel with the PAE feature enabled will +detect memory above 4 gigabytes and allow it to be used by the system. This feature +places constraints on the device drivers and other features of FreeBSD which may be used; +consult the +pae(4) manpage +for more details.
+ +FreeBSD will generally run on i386-based laptops, albeit with varying levels of +support for certain hardware features such as sound, graphics, power management, and +PCCARD expansion slots. These features tend to vary in idiosyncratic ways between +machines, and frequently require special-case support in FreeBSD to work around hardware +bugs or other oddities. When in doubt, a search of the archives of the FreeBSD +laptop computer mailing list may be useful.
+ +Most modern laptops (as well as many desktops) use the Advanced Configuration and +Power Management (ACPI) standard. FreeBSD supports ACPI via the ACPI Component +Architecture reference implementation from Intel, as +described in the +acpi(4) manual +page. The use of ACPI causes instabilities on some machines and it may be necessary to +disable the ACPI driver, which is normally loaded via a kernel module. This may be +accomplished by adding the following line to /boot/device.hints:
+ ++hint.acpi.0.disabled="1" ++ +
Users debugging ACPI-related problems may find it useful to disable portions of the +ACPI functionality. The +acpi(4) manual +page has more information on how to do this via loader tunables.
+ +ACPI depends on a Differentiated System Descriptor Table (DSDT) provided by each +machine's BIOS. Some machines have bad or incomplete DSDTs, which prevents ACPI from +functioning correctly. Replacement DSDTs for some machines can be found at the DSDT section of the +ACPI4Linux project Web site. +FreeBSD can use these DSDTs to override the DSDT provided by the BIOS; see the +acpi(4) manual +page for more information.
+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) can +not be enabled and the use of a serial console is required.
+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.
+This section describes the systems currently known to be supported by FreeBSD on the +UltraSPARC® platform. For background information on +the various hardware designs see the Sun System Handbook.
+ +SMP is supported on all systems with more than 1 processor.
+ +When using the GENERIC kernel, FreeBSD/sparc64 systems not +equipped with a framebuffer supported by the +creator(4) +(Sun™ Creator, Sun +Creator3D and Sun Elite3D) or +machfb(4) (Sun PGX and Sun PGX64 as well as +the ATI Mach64 chips found onboard in for example Sun Blade™ 100, Sun Blade 150, Sun Ultra™ 5 and Sun Ultra +10) driver must use the serial console.
+ +If you have a system that is not listed here, it may not have been tested with FreeBSD +8.0-RELEASE. We encourage you to try it and send a note to the FreeBSD +SPARC porting mailing list with your results, including which devices work and which +do not.
+ +The following systems are fully supported by FreeBSD:
+ +Sun Blade 100
+Sun Blade 150
+Sun Enterprise™ 100
+Sun Enterprise 220R
+Sun Enterprise 250
+Sun Enterprise 420R
+Sun Enterprise 450
+Sun Fire™ V100
+Sun Fire V120
+Netra™ t1 105
+Netra T1 AC200/DC200
+Netra t 1100
+Netra t 1120
+Netra t 1125
+Netra t 1400/1405
+Netra 120
+Netra X1
+SPARCEngine® Ultra AX1105
+SPARCEngine Ultra AXe
+SPARCEngine Ultra AXi
+SPARCEngine Ultra AXmp
+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 fibre +channel controllers in SBus-based systems are not supported. However, it is possible to +use these with a SCSI controller supported by the +esp(4) driver +(Sun ESP SCSI, Sun FAS +Fast-SCSI and Sun FAS366 Fast-Wide SCSI controllers).
+ +Sun Enterprise 3500
+Sun Enterprise 4500
+Starting with 7.2-RELEASE, sparc64 systems based on UltraSPARC III and beyond are also supported by FreeBSD, which +includes the following known working systems:
+ +Sun Blade 1000
+Sun Blade 1500
+Sun Blade 2000
+Sun Blade 2500
+Sun Fire 280R
+Sun Fire V210
+Sun Fire V250
+Sun Fire V440 (support for the on-board NICs first +appeared in 8.0-RELEASE)
+Sun Fire V880
+Netra 20/Netra T4
+The following UltraSPARC IIIi systems are not tested +but believed to be also supported by FreeBSD:
+ +Sun Fire V125
+Sun Fire V240
+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.
+
[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
+[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
+[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)
+[i386,pc98,amd64] Controllers supported by the +amd(4) driver +include:
+ +MELCO IFC-DP (PC-98)
+Tekram DC390
+Tekram DC390T
+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-1180
+ARC-1110ML
+ARC-1120ML
+ARC-1130ML
+ARC-1160ML
+ARC-1210
+ARC-1220
+ARC-1230
+ARC-1260
+ARC-1280
+ARC-1210ML
+ARC-1220ML
+ARC-1231ML
+ARC-1261ML
+ARC-1280ML
+[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
+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 P400
+HP Smart Array P400i
+HP Smart Array P410
+HP Smart Array P410i
+HP Smart Array P411
+HP Smart Array P600
+HP Smart Array P800
+HP Smart Array P812
+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] The +esp(4) driver +provides support for the Qlogic FAS216 and FAS408 SCSI controller chips found in a wide +variety of systems and peripheral boards. This includes the Qlogic SCSI cards found in +most Sun Ultra 1e and Ultra 2 machines.
+ +For Qlogic PCI SCSI host adapters, the isp(4) driver should be used in place of the +esp(4) +driver.
+ +[i386,amd64] The +hptiop(4) driver +supports the following SAS and SATA RAID controllers:
+ +HighPoint RocketRAID 4320
+HighPoint RocketRAID 3220
+HighPoint RocketRAID 3320
+HighPoint RocketRAID 3410
+HighPoint RocketRAID 3520
+HighPoint RocketRAID 3510
+HighPoint RocketRAID 3511
+HighPoint RocketRAID 3521
+HighPoint RocketRAID 3522
+HighPoint RocketRAID 3540
+HighPoint RocketRAID 3120
+HighPoint RocketRAID 3122
+HighPoint RocketRAID 3020
+[i386,amd64] The +hptmv(4) driver +supports the following ATA RAID controllers:
+ +HighPoint's RocketRAID 182x 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
+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 8408E
+LSI MegaRAID SAS 8480E
+LSI MegaRAID SAS 1078
+Dell PERC5
+Dell PERC6
+[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 +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 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.
+ +[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.
+ +[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] 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))
+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 +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 based USB Ethernet adapters +including:
+ +AX88172:
+ +AboCom UF200
+Acer Communications EP1427X2
+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:
+ +Belkin F5D5055
+Planex Communications GU1000T
+Sitecom Europe LN-028
+AX88772:
+ +Cisco-Linksys USB200Mv2
+D-Link DUBE100B1
+[i386,amd64] The +bce(4) driver +provides support for various NICs based on the Broadcom NetXtreme II family of Gigabit +Ethernet controllers, including the following:
+ +Broadcom NetXtreme II BCM5706 1000Base-SX
+Broadcom NetXtreme II BCM5706 1000Base-T
+Broadcom NetXtreme II BCM5708 1000Base-SX
+Broadcom NetXtreme II BCM5708 1000Base-T
+Broadcom NetXtreme II BCM5709 1000Base-SX
+Broadcom NetXtreme II BCM5709 1000Base-T
+Broadcom 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)
+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 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)
+[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 dc(4) driver provides +support for the following chipsets:
+ +DEC/Intel 21143
+ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II
+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
+Bay Networks NETGEAR FA410TXC Fast Ethernet
+Belkin F5D5020 PC Card Fast Ethernet
+Billionton LM5LT-10B Ethernet/Modem PC Card
+Bromax iPort 10/100 Ethernet PC Card
+Bromax iPort 10 Ethernet PC Card
+Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX PC 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 Etherenet/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)
+[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 JMC260 PCI Express Fast Ethernet 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 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 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 88E8058 Gigabit Ethernet
+Marvell Yukon 88E8070 Gigabit Ethernet
+Marvell Yukon 88E8071 Gigabit Ethernet
+Marvell Yukon 88E8072 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,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
+The re(4) driver supports +RealTek RTL8139C+, RTL8169, RTL816xS, RTL811xS, and RTL8101E 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-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
+[i386,pc98,ia64,amd64] The +sis(4) driver +supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and +embedded controllers, as well as Fast Ethernet adapters based on the National +Semiconductor DP83815 (MacPhyter) and DP83816 chips. Supported adapters include:
+ +@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
+[i386,sparc64,pc98,amd64] 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.
+ +[i386,pc98,amd64] 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
+[i386,amd64,sparc64] 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
+[i386,pc98,amd64] The +vge(4) driver +supports VIA Networking VT3119 and VT6122 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 DFE530-TX
+Hawking Technologies PN102TX
+Soekris Engineering net5501
+[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,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.
+[i386, pc98] DEC DEFPA PCI ( +fpa(4) +driver)
+ +[i386] DEC DEFEA EISA ( +fpa(4) +driver)
+[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)
+[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.
+ +A list of cards that are supported can be found at http://customerproducts.atheros.com/customerproducts/default.asp.
+ +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 1470
+Dell Truemobile 1400
+HP nx6125
+Linksys WPC54G Ver 3
+Linksys WPC54GS Ver 2
+TRENDnet TEW-401PCplus
+US Robotics 5411
+[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)
+ +[i386,amd64] The +ral(4) driver +supports PCI/CardBus wireless adapters based on the Ralink Technology RT2500, RT2501, and +RT2600 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
+An up to date list can be found at http://damien.bergamini.free.fr/ral/list.html.
+ +[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
+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
+The +uath(4) driver +should work with the following adapters:
+ +Li Compex WLU108AG
+Li Compex WLU108G
+Li D-Link DWL-G132
+Li IODATA WN-G54/US
+Li MELCO WLI-U2-KAMG54
+Li Netgear WG111T
+Li Netgear WG111U
+Li Netgear WPN111
+Li Olitec 000544
+Li PLANET WDL-U357
+Li Siemens Gigaset 108
+Li SMC SMCWUSBT-G
+Li SMC SMCWUSBT-G2
+Li SparkLAN WL-785A
+Li TP-Link TL-WN620G
+Li TRENDware International TEW-444UB
+Li TRENDware International TEW-504UB
+Li Unex Technology UR054ag
+Li 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:
+ +Netgear WG111v2
+Safehome WLG-1500SMA5
+Shuttle XPC Accessory PN20
+[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
+Trendnet TEW-429UB
+TwinMOS G240
+Unicorn WL-54G
+US Robotics 5423
+X-Micro XWL-11GUZX
+Yakumo QuickWLAN USB
+Zonet ZEW2501
+ZyXEL ZyAIR G-220
+[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.
+[i386] AcerISDN P10 ISA PnP (experimental)
+ +[i386] Asuscom ISDNlink 128K ISA
+ +[i386] ASUSCOM P-IN100-ST-D (and other Winbond W6692-based cards)
+ +[i386] AVM
+ +A1
+B1 ISA (tested with V2.0)
+B1 PCI (tested with V4.0)
+Fritz!Card classic
+Fritz!Card PnP
+Fritz!Card PCI
+Fritz!Card PCI, Version 2
+T1
+[i386] Creatix
+ +ISDN-S0
+ISDN-S0 P&P
+[i386] Compaq Microcom 610 ISDN (Compaq series PSB2222I) ISA PnP
+ +[i386] Dr. Neuhaus Niccy Go@ and compatibles
+ +[i386] Dynalink IS64PPH and IS64PPH+
+ +[i386] Eicon Diehl DIVA 2.0 and 2.02
+ +[i386] ELSA
+ +ELSA PCC-16
+QuickStep 1000pro ISA
+MicroLink ISDN/PCI
+QuickStep 1000pro PCI
+[i386] ITK ix1 Micro ( < V.3, non-PnP version )
+ +[i386] Sedlbauer Win Speed
+ +[i386] Siemens I-Surf 2.0
+ +[i386] TELEINT ISDN SPEED No.1 (experimental)
+ +[i386] Teles
+ +S0/8
+S0/16
+S0/16.3
+S0/16.3 PnP
+16.3c ISA PnP (experimental)
+Teles PCI-TJ
+[i386] Traverse Technologies NETjet-S PCI
+ +[i386] USRobotics Sportster ISDN TA intern
+ +[i386] Winbond W6692 based PCI cards
+[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.
+
[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 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 many Intel HDA compatible audio chipsets including the following:
+ +ATI SB450
+ATI SB600
+Intel 631x/632xESB
+Intel 82801F (ICH6)
+Intel 82801G (ICH7)
+Intel 82801H (ICH8)
+Intel 82801I (ICH9)
+Intel 82801J (ICH10)
+Intel US15W (SCH)
+nVidia MCP51
+nVidia MCP55
+nVidia MCP61A
+nVidia MCP61B
+nVidia MCP63
+nVidia MCP65A
+nVidia MCP65B
+nVidia MCP67A
+nVidia MCP67B
+nVidia MCP68
+nVidia MCP69
+SiS 966
+VIA VT8251/8237A
+The following and many other codecs have been verified to work:
+ +Analog Devices AD1981HD
+Analog Devices AD1983
+Analog Devices AD1984
+Analog Devices AD1986A
+Analog Devices AD1988
+Analog Devices AD1988B
+CMedia CMI9880
+Conexant CX20549 (Venice)
+Conexant CX20551 (Waikiki)
+Conexant CX20561 (Hermosa)
+Realtek ALC260
+Realtek ALC262
+Realtek ALC268
+Realtek ALC660
+Realtek ALC861
+Realtek ALC861VD
+Realtek ALC880
+Realtek ALC882
+Realtek ALC883
+Realtek ALC885
+Realtek ALC888
+Realtek ALC889
+Sigmatel STAC9205
+Sigmatel STAC9220
+Sigmatel STAC9220D / 9223D
+Sigmatel STAC9221
+Sigmatel STAC9221D
+Sigmatel STAC9227D
+Sigmatel STAC9227X
+Sigmatel STAC9228D
+Sigmatel STAC9228X
+Sigmatel STAC9229D
+Sigmatel STAC9229X
+Sigmatel STAC9230D
+Sigmatel STAC9230X
+Sigmatel STAC9271D
+Sigmatel STAC9872AK
+VIA VT1708
+VIA VT1708B
+VIA VT1709
+[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] 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
+[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
+[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
+[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 +uftdi(4) driver +supports the following adapters:
+ +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 adapters:
+ +ATEN UC-232A
+BAFO BF-800
+BAFO BF-810
+Belkin F5U257
+ELECOM UC-SGT
+HAL Corporation Crossam2+USB IR commander
+Hama USB RS-232 Serial Adapter
+Hamlet exagerate XURS232
+IOGEAR UC-232A
+I/O DATA USB-RSAQ
+I/O DATA USB-RSAQ2
+I/O DATA USB-RSAQ3
+Mobile Action MA-620 Infrared Adapter
+PLANEX USB-RS232 URS-03
+RATOC REX-USB60
+Radio Shack USB Serial Cable
+Sandberg USB to Serial Link (model number 133-08)
+SOURCENEXT KeikaiDenwa 8 (with and without charger)
+Sony Ericsson USB Cable (Susteen USB Data Cable)
+Willcom W-SIM DD PHS terminal.(WS002IN)
+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
+[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)
+[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
+[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
+[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:
+ +[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/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ + + diff --git a/en/releases/8.0R/readme.html b/en/releases/8.0R/readme.html new file mode 100644 index 0000000000..7fcb9653c6 --- /dev/null +++ b/en/releases/8.0R/readme.html @@ -0,0 +1,402 @@ + + + + +Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, +2008 The FreeBSD Documentation Project
+ +$FreeBSD:
+release/8.0.0/release/doc/en_US.ISO8859-1/readme/article.sgml 179456 2008-05-31 13:45:35Z
+hrs $
+
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, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.
+ +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.
++ ++ +
This distribution is a release of FreeBSD 8.0-RELEASE, the latest point along the +8.0-STABLE branch.
+ +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 20,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.
+This release of FreeBSD is suitable for all users. It has undergone a period of +testing and quality assurance checking to ensure the highest reliability and +dependability.
+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.
+ +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.
+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, or on the http://mirrorlist.FreeBSD.org/ +Web pages. Finding a close (in networking terms) mirror from which to download the +distribution is highly recommended.
+ +Additional mirror sites are always welcome. Contact <freebsd-admin@FreeBSD.org> 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.
+For any questions or general technical support issues, please send mail to the FreeBSD +general questions mailing list.
+ +If you're tracking the 8.0-STABLE development efforts, you must join the FreeBSD-CURRENT 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.
+
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 mail +connectivity is to use the +send-pr(1) +command. “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) +itself is a shell script that should be easy to move even onto a non-FreeBSD system. +Using this interface is highly preferred. If, for some reason, you are unable to use +send-pr(1) to +submit a bug report, you can try to send it to the FreeBSD +problem reports mailing list.
+ +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.
+There are many sources of information about FreeBSD; some are included with this +distribution, while others are available on-line or in print versions.
+ +A number of other files provide more specific information about this release +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 8.0-RELEASE compared to the previous release (FreeBSD +7.2-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 +sysinstall(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 +sysinstall(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 http://www.FreeBSD.org/releases/ (as well as any sites which keep +up-to-date mirrors of this location).
+
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).
+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.
+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 +release. 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 release simply would not have been possible.
+This file, and other release-related documents, can be +downloaded from http://www.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ + + diff --git a/en/releases/8.0R/relnotes-detailed.html b/en/releases/8.0R/relnotes-detailed.html new file mode 100644 index 0000000000..acb602989e --- /dev/null +++ b/en/releases/8.0R/relnotes-detailed.html @@ -0,0 +1,3113 @@ + + + + +Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, +2008, 2009 The FreeBSD Documentation Project
+ +$FreeBSD: stable/8/release/doc/en_US.ISO8859-1/relnotes/article.sgml
+196375 2009-08-19 03:58:12Z edwin $
+
FreeBSD is a registered trademark of the FreeBSD Foundation.
+ +IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.
+ +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, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.
+ +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.
+The release notes for FreeBSD 8.0-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 8-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.
+This document contains the release notes for FreeBSD 8.0-RELEASE. It describes +recently added, changed, or deleted features of FreeBSD. It also provides some notes on +upgrading from previous versions of FreeBSD.
+ +This distribution of FreeBSD 8.0-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the “Obtaining FreeBSD” appendix to the FreeBSD +Handbook.
+ +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 8.0-RELEASE can be found on the FreeBSD Web site.
+This section describes the most user-visible new or changed features in FreeBSD since +7.0-RELEASE, and changes shown in Release Notes for the previous releases are marked as +[7.1R] and [7.2R].
+ +Typical release note items document recent security advisories issued after +7.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.
+ +Problems described in the following security advisories have been fixed. For more +information, consult the individual advisories available from http://security.FreeBSD.org/.
+ +| Advisory | +Date | +Topic | +
|---|---|---|
| SA-08:05.openssh | +17 April 2008 | +
+ OpenSSH X11-forwarding privilege escalation + |
+
| SA-08:06.bind | +13 July 2008 | +
+ DNS cache poisoning + |
+
| SA-08:07.amd64 | +3 September 2008 | +
+ amd64 swapgs local privilege escalation + |
+
| SA-08:08.nmount | +3 September 2008 | +
+ +nmount(2) local +arbitrary code execution + |
+
| SA-08:09.icmp6 | +3 September 2008 | +
+ Remote kernel panics on IPv6 connections + |
+
| SA-08:10.nd6 | +1 October 2008 | +
+ IPv6 Neighbor Discovery Protocol routing vulnerability + |
+
| SA-08:11.arc4random | +24 November 2008 | +
+ +arc4random(9) +predictable sequence vulnerability + |
+
| SA-08:12.ftpd | +23 December 2008 | +
+ Cross-site request forgery in +ftpd(8) + |
+
| SA-08:13.protosw | +23 December 2008 | +
+ netgraph / bluetooth privilege escalation + |
+
| SA-09:01.lukemftpd | +07 January 2009 | +
+ Cross-site request forgery in +lukemftpd(8) + |
+
| SA-09:02.openssl | +07 January 2009 | +
+ OpenSSL incorrectly checks for malformed signatures + |
+
| SA-09:03.ntpd | +13 January 2009 | +
+ ntpd cryptographic signature bypass + |
+
| SA-09:04.bind | +13 January 2009 | +
+ BIND DNSSEC incorrect checks for malformed signatures + |
+
| SA-09:05.telnetd | +16 February 2009 | +
+ telnetd code execution vulnerability + |
+
| SA-09:06.ktimer | +23 March 2009 | +
+ Local privilege escalation + |
+
| SA-09:07.libc | +04 April 2009 | +
+ Information leak in db(3) + |
+
| SA-09:08.openssl | +22 April 2009 | +
+ Remotely exploitable crash in OpenSSL + |
+
| SA-09:09.pipe | +10 June 2009 | +
+ Local information disclosure via direct pipe writes + |
+
| SA-09:10.ipv6 | +10 June 2009 | +
+ Missing permission check on SIOCSIFINFO_IN6 ioctl + |
+
| SA-09:11.ntpd | +10 June 2009 | +
+ ntpd stack-based buffer-overflow vulnerability + |
+
| SA-09:12.bind | +29 July 2009 | +
+ BIND +named(8) dynamic +update message remote DoS + |
+
| SA-09:14.devfs | +2 Oct 2009 | +
+ Devfs / VFS NULL pointer race condition + |
+
The FreeBSD GENERIC kernel now includes Trusted BSD MAC +(Mandatory Access Control) support. No MAC policy module is loaded by default.
+ +[i386] A loader tunable hw.clflush_disable has been added
+to avoid panic (trap 9) at map_invalidate_cache_range()
+even if Intel CPU is used. This tunable can be set to -1
+(default), 0 and 1. The -1 is same as the current behavior, which automatically disable CLFLUSH on Intel CPUs without CPUID_SS
+(this should be occurred on Xen only). You can specify 1 when
+this panic happened on non-Intel CPUs (such as AMD's). Because disabling CLFLUSH can reduce performance, you can try with setting 0 on Intel CPUs without SS to use CLFLUSH feature.
The FreeBSD newbus subsystem is now MPSAFE.
+ +The +jail(8) +subsystem has been updated. Changes include:
+ +A new virtualization container named “vimage” has been implemented. This +is not enabled by default. To enable this, add the following kernel options to your +kernel configuration file and rebuild the kernel:
+ ++options VIMAGE ++ +
Note that an option SCTP in the GENERIC kernel is not compatible with the VIMAGE. This limitation will be fixed in the next release.
+ +The vimage is a jail with a virtualized instance of the FreeBSD network stack. It can +be created by using +jail(8) command +like this:
+ ++# jail -c vnet name=vnet1 host.hostname=vnet1.example.net path=/ persist ++ +
The vimage has own loopback interface and a separated network stack including the L3
+routing table. Network interfaces on the system can be moved by using
+ifconfig(8)
+vnet option between the different vimage jails and outside of
+them.
Furthermore, the +epair(4) +pseudo-interface driver has been added to help communication between vimage jails. It +emulates a pair of back-to-back connected Ethernet interfaces. For example, following +commands create the interface pair:
+ ++# ifconfig epair0 create +epair0a +# ifconfig epair0a +epair0a: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + ether 02:c0:64:00:07:0a +# ifconfig epair0b +epair0b: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + ether 02:c0:64:00:08:0b ++ +
The
+epair(4)
+pseudo-interfaces and any physical interfaces on the system can be moved between vimage
+jails by using
+ifconfig(8)
+vnet option. Even after one of an
+epair(4) pair is
+moved, the back-to-back connection still valid and can be used for inter-jail
+communication.
Note that the vimage is still considered as an experimental feature.
+A jail can have arbitrary named parameters similar to environmental variables and the +fixed jail parameters in the previous releases have been replaced with them. The jail +name can be used for identifying the jail in +jexec(8) and +killall(1).
+Multiple addresses of both IPv4 and IPv6 per jail has been supported. It is even +possible to have jails without an IP address at all, which basically gives one a chrooted +environment with restricted process view and no networking.
+SCTP ( +sctp(4)) with +IPv6 in jails has been implemented.
+Specific CPU binding by using +cpuset(1) has +been implemented. Note that the current implementation allows the superuser inside of the +jail to change the CPU bindings specified.
+A +jail(8) can +start with a specific route FIB now.
+A show jails subcommand in +ddb(8) has been +added.
+Compatibility support which permits 32-bit jail binaries to be used on 64-bit systems +to manage jails has been added.
+Note that both version numbers of jail and prison in the +jail(8) have +been updated for the new features.
+The +ksyms(4), kernel +symbol table interface driver has been added. It creates a character device /dev/ksyms and provides read-only access to a snapshot of the +kernel symbol table.
+ +[amd64, i386] The FreeBSD Linux emulation layer has been updated to version 2.6.16 and +the default Linux infrastructure port is emulators/linux_base-f10 (Fedora 10).
+ +[7.2R] The +ddb(8) kernel +debugger now supports a show mount subcommand.
+ +[7.2R] The FreeBSD DTrace subsystem now supports a probe for process execution.
+ +[7.2R] [amd64] The FreeBSD kernel virtual address space has been increased to 6GB. +This allows subsystems to use larger virtual memory space than before. For example, +zfs(8) adaptive +replacement cache (ARC) requires large kernel memory space to cache file system data, so +it benefits from the increased address space. Note that the ceiling on the kernel map +size is now 60% of the size rather than an absolute quantity.
+ +[7.2R] The +kld(4) now +supports installing 32-bit system calls to the FreeBSD syscall translation layer from +kernel modules.
+ +[7.2R] The +ktr(4) now +supports a new KTR tracepoint in the KTR_CALLOUT class to note +when a callout routine finishes executing.
+ +[7.2R] Types of variables used to track the amount of allocated System V shared memory +have been changed from int to size_t. +This makes it possible to use more than 2 GB of memory for shared memory segments on +64-bit architectures. Please note the new BUGS section in +shmctl(2) and +/usr/src/UPDATING for limitations of this temporary +solution.
+ +[7.2R] The +sysctl(3) leaf +nodes have a flag to tag themselves as MPSAFE now.
+ +[7.2R] The FreeBSD 32-bit system call translation layer now supports installing 32-bit +system calls for VFS_AIO.
+ +[7.2R] [amd64, i386] The FreeBSD virtual memory subsystem now supports fully
+transparent use of superpages for application memory;
+application memory pages are dynamically promoted to or demoted from superpages without
+any modification to application code. This change offers the benefit of large page sizes
+such as improved virtual memory efficiency and reduced TLB (translation lookaside buffer)
+misses without downsides like application changes and virtual memory inflexibility. This
+is disabled by default and can be enabled by setting a loader tunable vm.pmap.pg_ps_enabled to 1.
[7.1R] The +clock_gettime(2) +and the related system calls now support a clock ID CLOCK_THREAD_CPUTIME_ID, defined in POSIX.
+ +[7.1R] The +cpuset(2) system +call has been added. This is an API for thread to CPU binding and CPU resource grouping +and assignment.
+ +[7.1R] The DTrace, a comprehensive dynamic tracing framework and +dtrace(1) +userland utility have been imported from OpenSolaris. DTrace provides a powerful +infrastructure to permit administrators, developers, and service personnel to concisely +answer arbitrary questions about the behavior of the operating system and user +programs.
+ +[7.1R] The +ddb(4) kernel +debugger now has an output capture facility. Input and output from +ddb(4) can now +be captured to a memory buffer for later inspection using +sysctl(8) or a +textdump. The new capture command controls this feature.
+ +[7.1R] The +ddb(4) debugger +now supports a simple scripting facility, which supports a set of named scripts +consisting of a set of +ddb(4) commands. +These commands can be managed from within +ddb(4) or with +the use of the new +ddb(8) utility. +More details can be found in the +ddb(4) manual +page.
+ +[7.1R] The
+ddb(4) ex command now supports an /S mode which
+interprets and prints the value at the requested address as a symbol. For example, ex /S aio_swake prints the
+name of the function currently registered in via aio_swake hook.
[7.1R] The
+ddb(4) show conifhk command has been added. This lists hooks currently
+waiting for completion in run_interrupt_driven_config_hooks().
[7.1R] The +fcntl(2) system +call now supports F_DUP2FD command. This is equivalent to +dup(2), and +compatible with Sun Solaris and IBM AIX.
+ +[7.1R] The FreeBSD's
+linux(4) ABI
+support now implements sched_setaffinity() and sched_getaffinity() using real CPU affinity setting
+primitives.
[7.1R] The +procstat(1) +utility has been added. This is a process inspection utility which provides both some of +the missing functionality from +procfs(5) and +new functionality for monitoring and debugging specific processes.
+ +[7.1R] The client side functionality of +rpc.lockd(8) has +been implemented in FreeBSD kernel. This implementation provides the correct semantics +for +flock(2) style +locks which are used by the +lockf(1) command +line tool and the +pidfile(3) +library. It also implements recovery from server restarts and ensures that dirty cache +blocks are written to the server before obtaining locks (allowing multiple clients to use +file locking to safely share data). Also, a new kernel option options +NFSLOCKD has been added and enabled by default. If the kernel support is enabled, +rpc.lockd(8) +automatically detects and uses the functionality.
+ +[7.1R] The FreeBSD kernel now supports a new textdump format of kernel dumps. A +textdump provides higher-level information via mechanically generated/extracted debugging +output, rather than a simple memory dump. This facility can be used to generate brief +kernel bug reports that are rich in debugging information, but are not dependent on +kernel symbol tables or precisely synchronized source code. More information can be found +in the +textdump(4) +manual page.
+ +[7.1R] The
+wait4(2) system
+call now supports WNOWAIT flag to keep the process whose
+status is returned in a waitable state and WSTOPPED which is
+equivalent to WUNTRACED.
[7.1R] [amd64, i386, sparc64] The FreeBSD kernel now supports initial support of +binding interrupts to CPUs.
+ +[7.1R] [amd64, i386] The +sched_ule(4) +scheduler is now the default process scheduler in GENERIC +kernels.
+ +[7.1R] The sysctl variables kern.features.compat_freebsd[456] have been added. These are
+corresponding to the kernel options COMPAT_FREEBSD[456].
The boot0 boot loader now preserves volume ID at offset +0x1b8 used in other operating systems
+ +The
+boot0cfg(8)
+utility now supports a new -i option to set the volume
+ID.
[7.2R] The +boot(8) now +supports 4-byte volume ID that certain versions of Windows® put into the MBR and invoking PXE by pressing F6 +key on some supported BIOSes.
+ +[7.2R] [i386] The +boot(8) BTX +loader has been improved. This fixes several boot issues on recent machines reported for +7.1-RELEASE and before.
+ +[7.2R] The +loader(8) is now +able to obtain DHCP options from network boot via +kenv(2) +variables.
+ +[7.2R] A bug in the +loader(8) has +been fixed. Now the following line works as expected:
+ +
+loader_conf_files="foo bar ${variable}"
+
+
+[7.1R] [amd64, i386] The BTX kernel used by the boot loader has been changed to invoke +BIOS routines from real mode. This change makes it possible to boot FreeBSD from USB +devices.
+ +[7.1R] [amd64, i386] A new gptboot boot loader has been added to support booting from +a GPT labeled disk. A new boot command has been added to +gpt(8), which +makes a GPT disk bootable by writing the required bits of the boot loader, creating a new +boot partition if required.
+The FreeBSD now includes an experimental support for MIPS platform.
+ +The +acpi(4) +subsystem now supports System Resource Affinity Table (SRAT) used to describe affinity +relationships between CPUs and memory, ACPI 3.0 fields in the MADT including X2APIC +entries and UIDs for local SAPICs, and ACPI 3.0 flags in the FADT.
+ +[powerpc] The +cpufreq(4) now +supports PowerPC G5, along with a skeleton SMU driver in order to slew CPU voltage during +frequency changes.
+ +The sec(4) driver has been added to provide support for the integrated security engine +found in Freescale system-on-chip devices.
+ +The FreeBSD TTY layer has been replaced with a new one which has better support for +SMP and robust resource handling. A tty now has own mutex and it is expected to improve +scalability when compared to the old implementation based on Giant lock.
+ +[amd64, i386] The +uart(4) is now +the default driver for serial port devices in favor of the +sio(4) driver. +Note that the device nodes have been renamed with /dev/cuauN and /dev/ttyuN.
+ +The FreeBSD USB subsystem has been reimplemented to support modern devices and better +SMP scalability. The new implementation includes Giant-lock-free device drivers, Linux +compatibility layer, +usbconfig(8) +utility, full support for split transaction and isochronous transaction, and so on. +Device node names for USB devices are now in a the form of /dev/usb/bus.dev.iface.endpoint, and /dev/usbctl +is the master device node. The name /dev/ugen0.1 in the +previous releases has been renamed as /dev/ugen/0.1.0.0, for +example.
+ +[7.2R] [sparc64] The FreeBSD now supports Ultra SPARC III (Cheetah) processor +family.
+ +[7.2R] The
+acpi(4)
+subsystem now supports a
+sysctl(8)
+variable debug.batt.batt_sleep_ms. On some laptops with
+smart batteries, enabling battery monitoring software causes keystrokes from
+atkbd(4) to be
+lost. This sysctl variable adds a delay in millisecond to the status checking code as a
+workaround.
[7.2R] The +acpi_asus(4) +driver now supports Asus A8Sr notebooks.
+ +[7.2R] [powerpc] Support for the AltiVec, a floating point and integer SIMD +instruction set has been added.
+ +[7.2R] The +cpuctl(4) +driver, which provides a special device /dev/cpuctl as an +interface to the system CPU has been added. The +cpuctl(4) +functionality includes the ability to retrieve CPUID information, read/write machine +specific registers (MSR), and perform CPU firmware updates.
+ +[7.2R] The
+cpufreq(4)
+driver now supports an hw.est.msr_info loader tunable. When
+this is set to 1, it attempts to build a simple list containing
+just the high and low frequencies if it cannot obtain a frequency list from either ACPI
+or the static tables. This is disabled by default.
[7.2R] [amd64, i386] CPU frequency change notifiers are now disabled when the TSC is
+P-state invariant. Also, a new loader tunable kern.timecounter.invariant_tsc has been added to force this
+behavior by setting it to non-zero.
[7.2R] The +atkbd(4) driver +now disables the interrupt handler which is called from the keyboard callback function +when polled mode is enabled. This fixes the problem of duplicated/missing characters at +the mountroot prompt on multi CPU systems while +kbdmux(4) is +enabled.
+ +[7.2R] In the +pci(4) subsystem +INTx is now disabled when MSI/MSIX is enabled. This change fixes interrupt storm related +issues.
+ +[7.2R] [sparc64] The schizo(4) driver for Schizo Fireplane/Safari to PCI 2.1 and +Tomatillo JBus to PCI 2.2 bridges has been added.
+ +[7.2R] The +u3g(4) driver +for USB based 3G cards and dongles including Vodafone Mobile Connect Card 3G, Qualcomm +CDMA MSM, Huawei E220, Novatel U740, Sierra MC875U, and so on has been added. This +provides support for the multiple USB-to-serial interfaces exposed by many 3G USB/PC Card +modems, and the device is accessed through the +ucom(4) driver +which makes it behave like a +tty(4).
+ +[7.2R] The
+sched_ule(4)
+scheduler now supports a loader tunable machdep.hyperthreading_enabled as the
+sched_4bsd(4)
+does. Note that it cannot be modified at run-time.
[7.1R] The +cmx(4) driver, a +driver for Omnikey CardMan 4040 PCMCIA smartcard readers, has been added.
+ +[7.1R] [sparc64] The +kbdmux(4) driver +has been added. The +sunkbd(4) now +supports +atkbd(4) +emulation like +ukbd(4).
+ +[7.1R] The nvram(4) driver is now MPSAFE.
+ +[7.1R] An option of the +puc(4) driver +PUC_FASTINTR has been no longer supported.
+ +[7.1R] The +psm(4) driver +now attempts detection of Synaptics touchpad before IntelliMouse. Some touchpads will +pretend to be IntelliMouse causing the IntelliMouse probe to work and the Synaptics +detection never to be done.
+ +[7.1R] The +uslcom(4) +driver, a driver for Silicon Laboratories CP2101/CP2102-based USB serial adapters, has +been imported from OpenBSD.
+ +The FreeBSD audio subsystem has been improved. The changes include volume per channel, +high quality fixed-point band-limited SINC sampling rate converter, bit-perfect mode, +transparent/adaptive virtual channel, and exclusive stream. For more details, see +snd(4) manual +page.
+ +[7.2R] The +agp(4) driver +now supports Intel G4X series graphics chipsets.
+ +[7.2R] The DRM, a kernel module named Direct Rendering Manager that gives direct +hardware access to DRI clients, has been updated. Support for AMD/ATI r500, r600, r700, +and IGP based chips, XGI V3XE/V5/V8, and Intel i915 chipsets has been improved.
+ +[7.2R] A new loader tunable hw.drm.msi has been added to
+control if DRM uses MSI or not. This is set to 1 (enabled) by
+default.
[7.2R] The snd_au88x0(4) driver for Aureal Vortex 1/2/Advantage PCI has been removed +because this was broken for a long time.
+ +[7.2R] The +snd_hda(4) +driver has been updated. This changes include support for multiple codec per HDA bus, +multiple functional groups per codec, multiple audio devices per functional group, +digital (SPDIF/HDMI) audio input/output, suspend/resume, and part of multichannel +audio.
+ +[7.2R] Note that due to added HDMI audio and logical audio devices support, the
+updated driver often provides several PCM devices. This means that in some cases the
+system default audio device no longer corresponds to the users's habitual audio
+connectors. In such cases the default device can be specified in audio applications'
+setup or defined globally via hw.snd.default_unit sysctl, as
+described in the
+sound(4) manual
+page.
[7.1R] The +agp(4) driver +now supports Intel G33 and G45.
+ +[7.1R] [i386] The dpms(4) driver has been added to use the +VESA BIOS for DPMS during suspend and resume.
+ +[7.1R] The DRM kernel driver now supports i915 GME +devices.
+The +bwi(4) driver +has been added to provide support for Broadcom BCM43xx IEEE 802.11b/g wireless network +interfaces.
+ +[sparc64] The +cas(4) driver +has been added to provide support for Sun Cassini/Cassini+ and National Semiconductor +DP83065 Saturn Gigabit Ethernet devices.
+ +The +cxgbtool(8) now +supports an interactive mode for scripting of repeatedly performed tasks.
+ +The +fxp(4) driver +has been improved. Changes include:
+ +The multicast filter re-programming becomes robust.
+[7.2R] The checksum offload feature can be controlled by +ifconfig(8) +now.
+[7.2R] Rx checksum offload support for 82559 or later controllers has been added.
+[7.2R] TSO (TCP Segmentation Offload) support for 82550 and 82551 controllers has been +added.
+[7.2R] WoL (Wake on LAN) support for 82550, 82551, 82558, and 82559-based controllers +has been added. Note that ICH based controllers are treated as 82559, and 82557, earlier +revisions of 82558, and 82559ER have no WoL capability.
+[7.2R] VLAN hardware tag insertion/stripping support and Tx/Rx checksum offload for +VLAN frames support have been added. Note that the VLAN hardware assistance is available +only on 82550 or 82551-based controllers.
+The +miibus(4) driver +now supports Marvell 88E3016.
+ +The +msk(4) driver +now supports Yukon FE+ A0 including 88E8040, 88E8040T, 88E8048 and 88E8070.
+ +The +mwl(4) driver +has been added to provide support for Marvell 88W8363 IEEE 802.11n wireless network +devices.
+ +The +mxge(4) driver +now supports some newer revisions and 10GBASE-LRM and 10GBASE-Twinax media types. The +firmware version has been updated to 1.4.43.
+ +The +nge(4) driver +has been improved and now works on all platforms.
+ +The +uath(4) driver +for USB wireless LAN adapter based on Atheros AR5005UG and AR5005UX chipsets has been +added. The +uathload(8) +utility, a firmware loader for the Atheros USB wireless driver has also been added.
+ +The +urtw(4) driver +has been added to provide support for Realtek RTL8187B/L USB IEEE 802.11b/g wireless +network devices.
+ +The xl(4) driver now +supports TX checksum offload.
+ +[7.2R] The ae(4) driver now +supports WoL (Wake on LAN).
+ +[7.2R] [amd64, i386] The +ale(4) driver is +now included in the GENERIC kernel.
+ +[7.2R] The +ath_hal(4), +Atheros Hardware Access Layer, has been updated to the open source version.
+ +[7.2R] The +axe(4) driver +has been improved in performance by eliminating extra context switches and now supports +Apple USB Ethernet adapter.
+ +[7.2R] The +bce(4) driver's +firmware has been updated to the latest version (4.6.X).
+ +[7.2R] The ciphy(4) driver now supports Vitesse VSC8211 PHY.
+ +[7.2R] The +cxgb(4) driver +has been updated to firmware revision 4.7 and now supports hardware MAC statistics.
+ +[7.2R] A bug in the
+igb(4) driver,
+which prevents the loader tunable hw.igb.ave_latency from
+working, has been fixed.
[7.2R] The +ixgbe(4) driver +has been updated to version 1.7.4.
+ +[7.2R] The +jme(4) driver +now supports newer JMicron JMC250/JMC260 revisions.
+ +[7.2R] The
+msk(4) driver
+has been improved. An issue which makes it hang up in a certain condition has been fixed.
+Hardware MAC statistics support has been added and users can get the information via
+sysctl variables named dev.msk.N.stats.
[7.2R] The +nfe(4) driver +now supports hardware MAC statistics.
+ +[7.2R] The re(4) driver has been
+improved. It now detects the link status. A new loader tunable hw.re.prefer_iomap has been added, to disable memory register
+mapping. This tunable is 0 for all controllers except RTL8169SC
+family.
[7.2R] The rl(4) driver has been +improved. It now detects the link status and a bug which prevents it from working on +systems with more than 4GB memory has been fixed.
+ +[7.2R] A bug in +sis(4) on VLAN +tagged frame handling has been fixed.
+ +[7.2R] The
+txp(4) driver
+now works on all supported architectures. Support has been added for
+altq(4), WoL,
+checksum offload when VLAN enabled, and link state change handling has been improved, and
+new sysctl variables dev.txp.N.stats for MAC statistics have been added. New
+sysctl variables dev.txp.N.process_limit has been added, to control how
+many received frames should be served in Rx handler (set to 64 by default and valid
+ranges are 16 to 128 in unit of frames). The firmware has been updated to the latest
+version.
[7.1R] The ae(4) driver has been +added to provide support for the Attansic/Atheros L2 FastEthernet controllers.
+ +[7.1R] The +jme(4) driver +has been added to provide support for PCIe adapters based on JMicron JMC250 gigabit +Ethernet and JMC260 fast Ethernet controllers.
+ +[7.1R] The +age(4) driver +has been added to provide support for Attansic/Atheros L1 gigabit Ethernet +controller.
+ +[7.1R] The +malo(4) driver +has been added to provide support for Marvell Libertas 88W8335 based PCI network +adapters.
+ +[7.1R] The bm(4) driver has been added to provide support for Apple Big Mac (BMAC) +Ethernet controller, found on various Apple G3 models.
+ +[7.1R] The et(4) driver has been added to provide support for Agere ET1310 +10/100/Gigabit Ethernet controller.
+ +[7.1R] The +glxsb(4) driver +has been added to provide support for the Security Block in AMD Geode LX processors.
+ +[7.1R] The +ale(4) driver +has been added to provide support for Atheros AR8121/AR8113/AR8114 Gigabit/Fast Ethernet +controllers. This driver is not enabled in GENERIC kernels for +this release.
+ +[7.1R] The em(4) driver has been +split into two drivers with some common parts. The em(4) driver will +continue to support adapters up to the 82575, as well as new client/desktop adapters. A +new +igb(4) driver +will support new server adapters.
+ +[7.1R] The +hme(4) driver +has been improved.
+ +[7.1R] The +ixgbe(4) driver +has been updated to version 1.6.2 from Intel.
+ +[7.1R] A bug in some of the +miibus(4) +supported drivers that IEEE 802.3 auto-negotiation was performed in a wrong order, has +been fixed. Now it chooses the correct technologies supported by IEEE 802.3 in the order +described in Annex 28B.3.
+ +[7.1R] A workaround has been added for a bug in TCP/UDP hardware checksum offload of +the +msk(4) driver +for short frames. Note that for frames that requires hardware VLAN tag insertion, the +checksum offload workaround does not work due to changes of checksum offset in mbuf after +the VLAN tag. So disabling hardware checksum offload for the VLAN interface is needed in +such cases.
+ +[7.1R] The +ndis(4) NDIS +miniport driver wrapper has been improved.
+ +[7.1R] The sf(4) driver has been +improved and now supports checksum offloading.
+ +[7.1R] The +stge(4) driver +now supports WOL (Wake on LAN).
+ +[7.1R] The vr(4) driver has been +improved.
+ +[7.1R] [amd64, i386] The +wpi(4) driver +has been updated to include a number of stability fixes.
+The FreeBSD netisr framework has been reimplemented for parallel threading support. +This is a kernel network dispatch interface which allows device drivers (and other packet +sources) to direct packets to protocols for directly dispatched or deferred processing. +The new implementation supports up to one netisr thread per CPU, and several benchmarks +on SMP machines show substantial performance improvement over the old one.
+ +A bug in the +gif(4) that +EtherIP packets sent by combination of +if_bridge(4) and + +gif(4) have a +reversed version field has been fixed. If you need to communicate with older FreeBSD +releases via EtherIP, use new flags accept_rev_ethip_ver and send_rev_ethip_ver to control handling the reversed version field. +These can be set by +ifconfig(8) +utility to +gif(4) +interfaces. The EtherIP implementation found on FreeBSD 6.1, 6.2, 6.3, 7.0, 7.1, and 7.2 +had an interoperability issue because it sent the incorrect EtherIP packets and discarded +the correct ones. For more details, see +gif(4) manual +page.
+ +The IGMPv3 and SSM (Source-Specific Multicast) including IPv6 SSM and MLDv2 have been +added. Although the old KAME MLDv2 hooks has been replaced with the new implementation, +the related kernel programming interface is preserved.
+ +The multicast routing code has been improved and the IPv4 and IPv6 support has been +split.
+ +The FreeBSD now supports the upcoming Wireless Mesh standard, IEEE 802.11s. The +current implementation is based on the March 2009 D3.0 draft version.
+ +The wireless network support layer (net80211) now uses pseudo-interfaces named as wlanN instead of a device driver +name like em0 directly. The wlanN interface is created by +ifconfig(8) as +an instance of the parent interface and used for actual communication similar to +vlan(4), IEEE +802.1Q VLAN network interface. Note that multiple instances (to realize multiple BSSes +with a single AP device, for example) can be created if the parent interface supports it. +For more details, see +ifconfig(8) +manual page.
+ +The net80211 layer now supports TDMA for long distance point-to-point links using +ath(4) +devices.
+ +An infrastructure for caching flows as a means of accelerating L2 and L3 lookups has +been added. This is called “flow table” and enabled by default on amd64 and +i386 platforms. This also provides stateful load balancing when used with RADIX_MPATH
+ +The FreeBSD L2 address translation table has been reimplemented to reduce lock +contention on parallel processing and simplify the routing logic. The new implementation +has L2 address translation tables for both ARP (for IPv4) and NDP (for IPv6) which are +separated from the L3 routing tables, and supports flow table caches for both the routing +table and the L2 information. One of the user-visible changes is that a concept of cloned +route (a route generated by an entry with RTF_CLONING flag) is +deprecated. This means routing flags RTF_CLONING, RTF_WASCLONE, and RTF_LLINFO are +obsolete.
+ +The +ipsec(4) +subsystem now supports NAT-Traversal (RFC 3948). This is disabled by default. To enable +this add the following kernel option and rebuild the kernel:
+ ++device crypto +options IPSEC +options IPSEC_NAT_T ++ +
[7.2R] IPv4 source address selection for unbound sockets has been implemented as +follows:
+ +If we found a route, use the address corresponding to the outgoing interface.
+[7.2R] Otherwise we assume the foreign address is reachable on a directly connected +network and try to find a corresponding interface to take the source address from.
+[7.2R] As a last resort use the default jail address.
+[7.2R] This also changes the semantics of selecting the IP for processes within a +jail(8) as it +now uses the same logic as outside the +jail(8).
+ +[7.2R] The TCP MD5 Signature Option (RFC 2385) for IPv6 has been implemented in the +same way it has been implemented for IPv4.
+ +[7.2R] The +ng_netflow(4) +Netgraph node now includes support for generating egress netflow instead or in addition +to ingress. An NGM_NETFLOW_SETCONFIG control message has been +added to control the new functionality.
+ +[7.2R] The +tap(4) Ethernet +tunnel software network interface now supports a new TAPGIFNAME +character device ioctl. This is a convenient shortcut to obtain the network interface +name using a file descriptor to a character device.
+ +[7.2R] The +tap(4) now +supports SIOCSIFMTU ioctl to set a higher MTU than 1500 +(ETHERMTU). This allows +tap(4) devices +to be added to the same bridge (which requires all interface members to have the same +MTU) with an interface configured for jumbo frames.
+ +[7.2R] The domains list for handling the list of supported domains in the +unix(4) (UNIX +domain protocol family) subsystem is now MPSAFE.
+ +[7.1R] The +arp(8) utility +now supports reject and blackhole +keywords. In the entry marked as reject, traffic to the host +will be discarded and the sender will be notified the host is unreachable. In the entry +marked as blackhole, traffic is discarded but the sender is not +notified.
+ +[7.1R] The +bpf(4) now +supports an ioctl BIOCSETFNR. This is just like BIOCSETF but it does not drop all the packets buffered on the +descriptor and reset the statistics.
+ +[7.1R] The +if_bridge(4) now +allow to limit the number of source MACs that can be behind a bridge interface via ifmaxaddr parameter of +ifconfig(8).
+ +[7.1R] A bug in the +carp(4) +interface configuration which leads to a system panic has been fixed.
+ +[7.1R] The
+dummynet(4)
+subsystem now supports fast mode operation which allows certain
+packets to bypass the dummynet scheduler. This can achieve lower latency and lower
+overhead when the packet flow is under the pipe bandwidth, and eliminate recursion in the
+subsystem. The new sysctl variable net.inet.ip.dummynet.io_fast has been added to enable this
+feature.
[7.1R] The +enc(4) now +supports sysctl variables to control whether the firewalls or +bpf(4) will see +inner and outer headers or just inner or outer headers for incoming and outgoing IPsec +packets.
+ +[7.1R] The +gre(4) now +supports ioctls GRESKEY and GREGKEY +which allows set or get GRE key used for outgoing packets.
+ +[7.1R] A bug in the +ipsec(4) +subsystem that PMTU was broken in those cases when there was a route with a lower MTU +than the MTU of the outgoing interface, has been fixed.
+ +[7.1R] The netatm subsystem has been removed due to lacking of multiprocessor +support.
+ +[7.1R] The +ng_nat(4) now +supports redirect functionality in libalias. For more details, +see the manual page.
+ +[7.1R] The +ng_pptpgre(4) +now supports multiple hooks like +ng_l2tp(4), to +use one pair of pptpgre and ksocket nodes for all calls between two peers.
+ +[7.1R] The +resolver(3) now +allows underscore in domain names. Although this is a violation of RFC 1034 [STD 13], it +is accepted by certain name servers as well as other popular operating systems' resolver +library.
+ +[7.1R] A socket option TCP_CONGESTION for TCP socket has been +added. This is for setting and retrieving the congestion control algorithm. The name used +is to allow compatibility with Linux.
+ +[7.1R] The
+rwlock(9) has
+been used throughout the inpcbinfo and inpcb infrastructure, and protocols that depend on that
+infrastructure, including UDP, TCP, and IP raw sockets to reduce the lock
+contentions.
[7.1R] The FreeBSD now supports multiple routing tables. To enable this, the following +steps are needed:
+ +Add the following kernel configuration option and rebuild the kernel. The 2 is the number of FIB (Forward Information Base, synonym for a +routing table here). The maximum value is 16.
+ ++options ROUTETABLES=2 ++ +
The procedure for rebuilding the FreeBSD kernel is described in the FreeBSD Handbook.
+ +This number can be modified on boot time. To do so, add the following to /boot/loader.conf and reboot the system:
+ ++net.fibs=6 ++
Set a loader tunable net.my_fibnum if needed. This means
+the default number of routing tables. If not specified, 0 will
+be used.
Set a loader tunable net.add_addr_allfibs if needed. This
+enables to add routes to all FIBs for new interfaces by default. When this is set to 0, it will only allocate routes on interface changes for the FIB of
+the caller when adding a new set of addresses to an interface. Note that this tunable is
+set to 1 by default.
To select one of the FIBs, the new +setfib(1) +utility can be used. This set an associated FIB with the process. For example:
+ ++# setfib -3 ping target.example.com ++ +
The FIB #3 will be used for the +ping(8) +command.
+ +The FIB which the packet will be associated with will be determined in the following +rules:
+ +All packets which have a FIB associated with them will use the FIB. If not, FIB #0 +will be used.
+A packet received on an interface for forwarding uses FIB #0.
+A TCP listen socket associated with an FIB will generate accept sockets which are +associated with the same FIB.
+A packet generated in response to other packet uses the FIB associated with the packet +being responded to.
+A packet generated on tunnel interfaces such as +gif(4) and +tun(4) will be +encapsulated using the FIB of the process which set up the tunnel.
+Routing messages will be associated with the process's FIB.
+Also, the +ipfw(8) now +supports an action rule setfib. The following action:
+ ++setfib fibnum ++ +
will make the matched packet use the FIB specified in fibnum. The rule processing continues at the next +rule.
+The FreeBSD CAM SCSI subsystem ( +cam(4)) now +includes experimental support for ATA/SATA/AHCI-compliant devices. This is disabled by +default. To enable this, adding the following kernel options to your kernel configuration +file and rebuild the kernel:
+ ++device ahci +device siis ++ +
The current implementation supports AHCI-compliant controllers and SiliconImage +SiI3124/SiI3132/SiI3531 controllers. The device node of an ATA drive is ada and one of an ATAPI drive is cd.
+ +The FreeBSD iSCSI initiator implementation has been improved and supports IPv6.
+ +A userland utility +mftutil(8) for +the +mfi(4) devices +has been added. This includes basic features to monitor controller, array, and drive +status, change basic attributes, create/delete arrays and spares, and flush the +controller firmware. Note that this is a small utility, not a replacement of MegaCLI in +the Ports Collection which is supported officially and provides more functionality.
+ +A userland utility +mptutil(8) for +the +mpi(4) devices +has been added. This includes basic features to monitor controller, array, and drive +status, change basic attributes, and create/delete arrays and spares.
+ +The +siis(4) driver +has been added to provide support for SiliconImage SiI3124/3132/3531 SATA2 controllers. +It supports Serial ATA and ATAPI devices, port multipliers (including FIS-based +switching), hardware command queues (31 command per port) and Native Command Queuing.
+ +[7.2R] The +ata(4) driver +now supports Marvell PATA M88SX6121.
+ +[7.2R] The +ata(4) driver +now recognizes nForce MCP67 and MCP73 SATA controllers as AHCI.
+ +[7.2R] The +ataraid(4) +driver now includes preliminary support for DDF metadata found on Adaptec HostRAID +controllers. Note that spares and rebuilds are not supported yet.
+ +[7.2R] The
+cam(4) SCSI
+subsystem now supports a new sysctl variable kern.cam.cd.retry_count. This controls the number of retries for
+the CD media. When trying to read scratched or damaged CDs and DVDs, the default
+mechanism is sub-optimal, and programs like ddrescue do much
+better if you turn off the retries entirely since their algorithms do it by themselves.
+This value is set to 4 (for a total of 5 attempts) by default.
+Setting it to 0 turns off all retry attempts.
[7.2R] A bug in the +ciss(4) driver +which caused low “max device openings” count and led to poor performance has +been fixed.
+ +[7.2R] The +glabel(8) GEOM +class now supports a new UFS-based label called ufsid that can +be used to reference UFS-carrying devices by the unique file system ID. This file system +ID is automatically generated and detected when the +glabel(8) GEOM +class is enabled. An example of this new label is: /dev/ufsid/48e69c8b5c8e1b43. The benefit of using GEOM labels in +general is to avoid problems of device renaming when shifting drives or controllers.
+ +[7.2R] The +gjournal(8) GEOM +class now supports the root file system. Previously, an unclean shutdown would make it +impossible to mount the root file system at boot.
+ +[7.2R] The +gpart(8) utility +has been updated. The APM scheme now supports Tivo Series 1 partitions (read only), a new +EBR scheme to support Extended Boot Records has been added, the BSD scheme now support +bootcode, and bugs in the PC98 and VTOC8 schemes have been fixed.
+ +[7.2R] An issue in +gvinum(8) with +access permissions to underlying disks used by a gvinum plex has been fixed. If the plex +is a raid5 plex and is being written to, parity data might have to be read from the +underlying disks, requiring them to be opened for reading as well as writing.
+ +[7.2R] The +hptmv(4) driver +has been updated to version 1.16 from the vendor.
+ +[7.2R] The +mmc(4) and +mmcsd(4) drivers +now support MMC and SDHC cards, high speed timing, wide bus, and multiblock +transfers.
+ +[7.2R] [sparc64] The +mpt(4) driver is +now in the GENERIC kernel.
+ +[7.2R] The +sdhci(4) driver +has been added. This supports PCI devices with class 8 and subclass 5 according to the SD +Host Controller Specification.
+ +[7.2R] The
+sdhci(4) driver
+now supports kernel dumping and a sysctl variable hw.sdhci.debug for debug level.
[7.2R] The +twa(4) driver +now supports 64-bit DMA.
+ +[7.2R] The +mmc(4) +mmcsd(4), and +sdhci(4) driver +are now included as kernel modules.
+ +[7.1R] The +aac(4) driver +now supports 64-bit array support for RAIDs larger than 2TB and simultaneous opens of the +device for issuing commands to the controller.
+ +[7.1R] The
+ata(4) driver
+now supports a loader variable hw.ata.ata_dma_check_80pin.
+This can be used to disable the 80pin cable check on broken systems such as certain
+laptops and Soekris boards. The default value is 1.
[7.1R] A data corruption problem of the +ata(4) driver on +ServerWorks HT1000 chipsets has been fixed.
+ +[7.1R] The
+ciss(4) driver
+now supports a loader tunable hw.ciss.nop_message_heartbeat
+for NOP-message polling in ciss_periodic(). This can be
+used as a workaround for ADAPTER HEARTBEAT FAILED issue. The
+default value is 0 (disabled).
[7.1R] The geom_part GEOM class can be built as a kernel +module.
+ +[7.1R] The geom_linux_lvm GEOM class can be built as a +kernel module.
+ +[7.1R] The +hptrr(4) driver +has been updated to version 1.2 from Highpoint.
+ +[7.1R] A buffer overflow in the +iir(4) driver +has been fixed. This likely fixes a great number of weird problems that have been +reported with this driver.
+ +[7.1R] The +mpt(4) driver +now supports mpt_user personality.
+ +[7.1R] The +rr232x(4) driver +has been superseded by +hptrr(4) +driver.
+ +[7.1R] The +twa(4) driver +has been improved with regard to stability on machines with a plenty of memory and high +CPU load.
+The +gvinum(8) now +supports commands found in the old vinum implementation including attach, detach, start, stop, concat, mirror, stripe, and raid5.
+ +The +gvinum(8) now +supports grow command to make it easier for users to extend +plexes without having to understand all of the implementation internals.
+ +The FreeBSD NFS subsystem now supports RPCSEC_GSS +authentication on both the client and server. This replaces the RPC implementation of the +NFS client and server with the newer RPC implementation originally developed to support +the NFS Lock Manager. It supports both the new RPC implementation and the older legacy +implementation inherited from the original NFS codebase and the default is to use the new +one. To use RPCSEC_GSS on either client or server, you must +build a kernel which includes the KGSSAPI option and the +crypto(4) +device. For more details, see +gssd(8) manual +page.
+ +The FreeBSD NFS subsystem now includes a new, experimental implementation with support +for NFSv2, NFSv3, and NFSv4. This is not enabled by default. To enable this, add the +following kernel options to your kernel configuration file and rebuild the kernel:
+ ++options NFSCL # for NFS client +options NFSD # for NFS server ++ +
The fstype for +mount(8) program +is newnfs, and +mount_newnfs(8) +program has also been added. The old, unmaintained NFSv4 client based on an +implementation at University of Michigan was removed from the FreeBSD source tree.
+ +The FreeBSD NFS subsystem now uses TCP as the default transport.
+ +The shared vnode locking for pathname lookups in the
+VFS(9) subsystem
+has been improved. This is enabled by default. Setting a sysctl variable vfs.lookup_shared to 0 disables it. Note
+that the LOOKUP_SHARED kernel option equivalent to the sysctl
+variable has been removed.
The ZFS file system has been updated to version 13. The +changes include ZFS operations by a regular user, L2ARC, ZFS Intent Log on separated +disks (slog), sparse volumes, and so on.
+ +[7.2R] The semantics of +acl(3) extended +access control lists has been changed as follows:
+ +The inode modification time (mtime) is not updated when extended attributes are added, +modified, or removed.
+The inode access time (atime) is not updated when extended attributes are queried.
+[7.2R] The FreeBSD NFS file system now supports a sysctl variable vfs.nfs.prime_access_cache to determine whether or not nfs_getattr() will use an ACCESS RPC to prime the access cache
+instead of a simple GETATTR RPC. This is because on many NFS servers an ACCESS RPC is
+much more expensive to service than a GETATTR RPC for files in an NFSv3 mount. The sysctl
+variable is enabled by default to maintain the previous behavior.
[7.2R] The FreeBSD UDF file system now supports a fifo.
+ +[7.1R] The +fdescfs(5) is +now MPSAFE.
+ +[7.1R] The +gpart(8) now +supports BSD disklabels (option GEOM_PART_BSD) and VTOC8 +disklabels (option GEOM_PART_VTOC8).
+ +[7.1R] The +gvinum(8) now +accepts volume parameter when creating a plex.
+ +[7.1R] A pathname lookup bug of a UNIX domain socket in the unionfs(7) has been fixed.
+The GCC stack protection (also known as ProPolice) has been enabled in the FreeBSD +base system.
+ +A BSD-licensed ar(1) utility has +been added in favor of one in GNU binutils and it is now the +default utility for building the FreeBSD base system.
+ +The +awk(1) utility +now supports 64 files. The upper limit was 20 in the prior releases.
+ +The +bsnmpd(1) +program now supports OIDs for ZFS.
+ +The +camcontrol(8) +program now supports a new modularized ATA kernel module and various ATA commands.
+ +The +cat(1) and cp(1) now use a +larger buffer if the number of pages of the physical memory on the system is grater than +32k. This reduces a number of context switches.
+ +A new BSD-licensed +cpio(1) utility +has been added in favor of GNU cpio and it is now the default +utility in the FreeBSD base system.
+ +A script for the +crashinfo(8) +utility for simple analysis of crash dump has been added. It generates a text file +containing the output of several commands run against the core dump such as +kgdb(1) (stack +trace), ps(1), +netstat(1), +vmstat(8), +iostat(8), +dmesg(8), and +fstat(1).
+ +The df(1) utility's -h flag now supports displaying inode counts in a human-readable
+format when a flag -i is specified.
The df(1) utility now
+supports a -T flag to display file system type in each
+entry.
A bug in the +dhclient(8) that +can create a malformed /etc/resolv.conf has been fixed.
+ +The
+dhclient(8) now
+uses an -n flag when invoking
+route(8)
+command. This eliminates a long delay in the case that it gets a lease but DNS service is
+not working.
The +dhclient(8) +utility now uses 68 (bootpc) as the source port for unicast DHCPREQUEST packets instead of allowing the protocol stack to pick a +random source port. This fixes the behavior where +dhclient(8) +would never transition from RENEWING to BOUND without going through REBINDING in +some networks which has a tight policy on DHCP spoofing.
+ +The
+env(1) utility
+now supports a -u name
+option that completely unsets the given name instead of setting it to a null value.
The
+find(1) utility
+now supports a number of primaries found in GNU find including
+-ignore_readdir_race, -noignore_readdir_race, -noleaf, -gid, -uid, -wholename, -iwholename, -mount, -d, -lname, -ilname, -quit, -samefile, and -true.
The
+fsck(8) utility
+now supports a -r flag to free up excess unused inodes.
+Decreasing the number of preallocated inodes reduces the running time of future runs of
+fsck and frees up space that can allocated to files. This flag is ignored when running in
+preen mode.
The +freebsd-update(8) now supports backing up the old +kernel when installing a new kernel. The backup kernel will be written to /boot/kernel.old if the directory does not exist or the directory +was created by freebsd-update in a previous backup. Otherwise the +freebsd-update(8) will generate a new directory +name for use by the backup. This is enabled by default.
+ +The +gpt(8) program +has been removed in favor of +gpart(8).
+ +The +gzip(1) utility +now supports uncompressing files which are created by pack +found in some commercial UNIX-like systems.
+ +The +i2c(8) utility +for diagnostics of I2C has been added.
+ +The
+ifconfig(8) now
+supports vnet and -vnet option to
+allow moving interfaces between jails with vimage.
A BSD-licensed libdwarf library has been added for DTrace +clients.
+ +The libmsun library now supports acosl(), asinl(), atanl(), atan2l(), cargl(), csqrtl(), fmodl(), hypotl(), and remquol() functions.
The libproc library has been added for DTrace clients.
+ +The +mtest(8) utility +now supports IPv6.
+ +The
+mount(8) program
+now supports an -o mountprog=filename option to allow an alternative program to
+be used for mounting a file system. This is useful for non-
+nmount(2) based
+file systems such as FUSE.
The +nfscbd(8), +nfsuserd(8), +nfsdumpstate(8), +and +nfsrevoke(8) +utilities for the new NFSv4 subsystem has been added.
+ +The +pmcannotate(8) +utility has been added. This prints out sources of a tool (in C or assembly) with inlined +profiling informations retrieved by a prior +pmcstat(8) +analysis.
+ +The +route(8) utility +now supports show, weights, and sticky commands. For more details, see +route(8) manual +page.
+ +The
+rtld(1) now
+supports a new environment variable LD_ELF_HINTS_PATH for
+overriding the rtld hints file. This environment variable would be ignored if the process
+uses setuid and/or setgid. This feature gives a convenient way to use a custom set of
+shared library that is not in the default location.
The
+rtld(1) now
+supports the dynamic string token substitution in the rpath and soneeded pathes. The
+$ORIGIN, $OSNAME, $OSREL and $PLATFORM tokens are
+supported. Enabling the substitution requires DF_ORIGIN flag in
+DT_FLAGS or DF_1_ORIGIN if DF_FLAGS_1, that may be set with -z
+origin GNU ld flag. This translation is unconditionally
+disabled for setuid/setgid processes. The $ORIGIN
+translation relies on the AT_EXECPATH auxinfo supplied by the
+FreeBSD kernel.
The
+traceroute(8)
+and
+traceroute6(8)
+now support an -a flag to display AS number corresponding to
+the lookup IP address on each hop. It will query the number to WHOIS server specified in
+-A option. If no -A is specified,
+whois.radb.net will be used as the default value.
The
+tzsetup(8) now
+supports an -s flag to skip the question about adjusting the
+clock to UTC.
The +wake(8) utility, +a tool to send Wake on LAN frames to hosts on a local Ethernet network has been +added.
+ +The +ypserv(8) +program now supports shadow.byname and shadow.byuid maps.
+ +[7.2R] A bug in the +atacontrol(8) +utility, which prevents it from working when /usr is not +mounted or invoked from /rescue, has been fixed.
+ +[7.2R] The +btpand(8) daemon +from NetBSD has been added. This daemon provides support for Bluetooth Network Access +Point (NAP), Group Ad-hoc Network (GN) and Personal Area Network User (PANU) +profiles.
+ +[7.2R] The +cpucontrol(8) +utility has been added to control +cpuctl(4) +pseudo-device.
+ +[7.2R] The +ncal(1) utility +now supports multibyte characters.
+ +[7.2R] The +newfs(8) utility +now supports operations on a regular file.
+ +[7.2R] The
+config(8)
+utility now supports multiple makeoption lines.
[7.2R] The +csup(1) utility +now supports CVSMode to fetch a complete CVS repository. Note that the rsync transfer +mode is currently disabled.
+ +[7.2R] The +dirname(1) +utility now accepts multiple arguments in the same way that +basename(1) +does.
+ +[7.2R] The du(1) utility now
+supports an -l flag. When specified, the du(1) utility counts
+a file with multiple hard links as multiple different files.
[7.2R] The du(1) utility now
+supports an -A flag to display the apparent size instead of
+the disk usage. This can be helpful when operating on compressed volumes or sparse
+files.
[7.2R] The du(1) utility now
+supports a -B blocksize
+option to calculate block counts in blocks of blocksize bytes. This is different from the -k or -m options or setting BLOCKSIZE and gives an estimate of how much space the examined
+file hierarchy would require on a file system with the given blocksize. Unless in -A mode,
+blocksize is rounded up to the next multiple of
+512.
[7.2R] The
+dumpfs(8)
+utility now supports an -f flag, which causes it to list all
+free fragments in the file system by fragment (block) number. This new mode does the
+necessary arithmetic to generate absolute fragment numbers rather than the cg-relative
+numbers printed in the default mode.
[7.2R] If -f is passed once, contiguous fragment ranges
+are collapsed into an X-Y format as free block lists are currently printed in regular
+dumpfs output. If specified twice, all block numbers are printed individually, allowing
+both compact and more script-friendly representation.
[7.2R] The
+fetch(1) utility
+now supports an -i flag which supports the If-Modified-Since
+HTTP 1.1 request. If specified it will cause the file to be downloaded only if it is more
+recent than the mtime of the local file. Also, libfetch now
+accepts the mtime in the url structure and a flag to indicate when this behavior is
+desired.
[7.2R] The
+fsck(8) utility
+now supports a -C flag for check
+clean mode. This checks if the file system was dismounted cleanly first and then
+skip file system checks if true. Otherwise it does full checks.
[7.2R] The
+fsck(8) utility
+now supports a -D flag for damaged recovery mode, which will
+enable certain aggressive operations that can make
+fsck(8) to
+survive with file systems that has very serious data damage. This is a useful last resort
+when on disk data damage is very serious and causes
+fsck(8) to
+crash.
[7.2R] The +getaddrinfo(3) +function now supports SCTP.
+ +[7.2R] A bug was fixed in the
+ipfw(8) utility
+which displays extra messages for a NAT rule even when a -q
+flag is specified.
[7.2R] The ln(1) utility now
+supports a -w flag to check if the source file actually
+exists. When the flag is specified and the file does not exist, ln(1) will issue a
+warning message.
The ln(1) utility now
+allows creating hard links to symbolic links because the POSIX.1-2008 requires this
+behavior for -L and -P flag.
The
+lpr(1) utility
+now support an -m flag to send an email after the job is
+completed and a -t option to set the job title.
[7.2R] The
+make(1) utility
+now supports a -p flag to print the input graph only, without
+executing any commands. The output is the same as -d g1. When
+combined with -f /dev/null, only the built-in rules of make
+are displayed.
[7.2R] The
+make(1) utility
+now supports a -Q flag to cause file banners not to be
+generated in addition to the same effect of a -q flag when a
+-j option is specified.
[7.2R] The
+make(1) utility
+now supports the .MAKE.JOB.PREFIX variable. If -j and -v are specified, its output for
+each target is prefixed with a token --- target --- the first part of which can be controlled
+via the variable.
[7.2R] The
+make(1) utility
+now supports .MAKE.PID and .MAKE.PPID variable. These are set to process ID of the
+make(1) process
+and its parent process respectively.
[7.2R] The +makefs(8) +utility to create a file system image from a directory tree has been added.
+ +[7.2R] The
+mergemaster(8)
+utility now supports an -F option to automatically install
+files that differ only in their version control ID strings.
[7.2R] The
+mount(8) utility
+now supports an -o mountprog=/somewhere/mount_xxx option to force it to use the
+specified program to mount the file system instead of calling
+nmount(2)
+directly. This is useful when you want to use third party programs such as FUSE, for
+example.
[7.2R] The
+netstat(1)
+utility now reports
+unix(4) sockets'
+listen queue statistics when an -L flag is specified.
[7.2R] A bug in the +netstat(1) +utility has been fixed. It crashed with the following options in the previous +versions:
+ ++% netstat -m -N foo ++ +
[7.2R] A bug in the
+netstat(1)
+utility has been fixed. The -ss option now works in the icmp6
+section as expected.
[7.2R] The
+pciconf(8)
+utility now supports a -b flag, which lists any base address
+registers (BAR) that are assigned resources for each device.
[7.2R] The +powerd(8) +program has been improved. Changes include reasonable CPU load estimation on SMP systems +and a new mode named as hiadaptive for AC-powered systems. The +hiadaptive mode raises the CPU frequency twice as fast as adaptive, it drops the CPU frequency 4 times slower, prefers twice +lower CPU load and has an additional delay before leaving the highest frequency after the +period of maximum load.
+ +The +revoke(1) +utility has been added. This is a wrapper of +revoke(2) +syscall.
+ +[7.2R] The
+stat(1) utility
+now displays an octal representation of suid, sgid and sticky bits when the -x flag is specified.
[7.2R] The +strndup(3) +function has been added.
+ +The
+tftpd(8) program
+now supports a -W option. This is almost the same as a -w option but will generate unique named based on the submitted
+filename, a
+strftime(3)
+format string, and a two digit sequence number. The time format string can be set by an
+-F option.
[7.2R] The wc(1) utility now
+supports an -L flag to output the number of characters in the
+longest input line.
[7.2R] A bug in the +rpc.yppasswdd(8) +program, which causes it to leave a zombie process when a password or default shell is +changed, has been fixed.
+ +[7.1R] The
+adduser(8)
+utility now supports a -M option to set the mode of a new
+user's home directory.
[7.1R] The +atacontrol(8) +utility now supports a spindown command to set or report timeout +after which the device will be spun down.
+ +[7.1R] The
+chflags(1) now
+supports a -v flag for verbose output, a -f flag to ignore errors, and -h to
+allow setting flags on symbolic links with the same semantics as (for example)
+chmod(1).
[7.1R] The cp(1) now supports a
+-a flag, which is equivalent to -RpP flags.
[7.1R] A bug in the cp(1) utility which +prevents POSIX.1e ACL (see also +acl(3)) from +copying properly has been fixed.
+ +[7.1R] The
+cron(8) utility
+now supports -m flag which overrides the default mail
+recipient for cron mails unless explicitly provided by MAILTO=
+line in crontab file.
[7.1R] The +dhclient(8) now +supports more options described in +dhcp-options(5).
+ +[7.1R] The
+dhclient(8) now
+supports is_default_interface() function which determines
+if this interface is one with the default route.
[7.1R] A bug in the +dhclient(8) that +prevents removal of the default route from working has been fixed.
+ +[7.1R] The +environ(7), +environment array of strings now supports unsetting a variable by setting the first +character to NULL. This is required by third-party software such as Dovecot and Postfix.
+ +[7.1R] The
+fdisk(8) now
+supports a -q flag to not display any warnings.
[7.1R] The
+fetch(1) program
+and libfetch library now supports a NO_PROXY environment variable. This specifies comma- or
+whitespace-separated list of host names for which proxies should not be used. If a single
+asterisk is specified, the use of proxies is disabled.
[7.1R] The +ffsll(3) and +flsll(3) +functions have been added. These functions are the same as +ffs(3) and +fls(3) except +that they accept long long as the arguments.
+ +[7.1R] The
+fortune(6)
+program now supports FORTUNE_PATH environment variable to
+specify search path of the fortune files.
[7.1R] A bug in the
+fortune(6)
+program that prevents -e option with multiple files from
+working has been fixed.
[7.1R] The +freebsd-update.conf(5) now supports IDSIgnorePaths statement.
+ +[7.1R] The
+fwcontrol(8)
+utility now supports -f node option which specifies node as the root node on the next bus reset.
[7.1R] [sparc64] The
+gcc(1) now
+accepts -mcpu option properly; it was hardcoded as -mcpu=ultrasparc.
[7.1R] The +ifconfig(8) now +supports display of WPS IE (Wireless Provisioning Services Information Element).
+ +[7.1R] The +kgdb(1) now +supports an add-kld kld +command to locate a +kld(4) and load +its symbols.
+ +[7.1R] The +kgdb(1) now has +a shared library backend for kernel files that treats +kld(4) as shared +libraries and auto-loading symbols for +kld(4) on +startup.
+ +[7.1R] The +kgdb(1) now +supports a tid command and other kernel module related commands +even for a remote target.
+ +[7.1R] The +kvm_getcptime(3) +function to obtain the global CPU time statistics from the kernel has been added.
+ +[7.1R] The libalias library now supports PORT and EPRT FTP commands in +lowercase.
+ +[7.1R] The +man(1) now +includes a limited support of +bzip2(1)-compressed manual pages.
+ +[7.1R] The
+mdconfig(8) now
+supports a -v (verbose) flag to -l command. It shows size and backing store of all md(4) devices at one
+time.
[7.1R] The +memrchr(3) +function has been added. This behaves like +memchr(3) except +that it locates the last occurrence of the specified character in the string.
+ +[7.1R] The incorrect output grammar of +morse(6) program +has been fixed.
+ +[7.1R] The
+mountd(8)
+utility now supports -h bindip option which specifies IP addresses to bind
+to for TCP and UDP requests. This option may be specified multiple times. If no -h option is specified, INADDR_ANY will be
+used. Note that when specifying IP addresses with this option, it will automatically add
+127.0.0.1 and if IPv6 is enabled, ::1
+to the list.
[7.1R] The
+moused(8)
+utility now supports -L flag which changes the speed of
+scrolling and changes -U option behavior to only affect the
+scroll threshold.
[7.1R] The mv(1) now support +POSIX specification when moving a directory to an existing directory across devices.
+ +[7.1R] The
+periodic(8) now
+supports daily_status_mail_rejects_shorten configuration
+variable in
+periodic.conf(5). This allows the rejected mail
+reports to tally the rejects per blacklist without providing details about individual
+sender hosts. The default configuration keeps the reports in their original form.
[7.1R] The +ping6(8) now +uses exit status of 0 and 2 in the same +manner as +ping(8).
+ +[7.1R] The
+ping6(8) now
+supports an -o flag, which makes
+ping6(8) exit
+successfully after receiving one reply packet.
[7.1R] The
+ping6(8) now
+supports -r and -R flags, which
+are equivalent to
+ping(8)'s -a and -A flags, respectively.
[7.1R] The minimum allowed interval of +ping6(8) has +been decreased to 0.000001 from 0.01.
+ +[7.1R] The
+realpath(1)
+utility now supports a -q flag to suppress warnings; it now
+also accepts multiple paths on its command line.
[7.1R] The
+rfcomm_pppd(8)
+now supports a -D flag to register DUN (Dial-Up Networking)
+service in addition to the LAN (LAN Access Using PPP) service.
[7.1R] The +sdpd(8) now +supports a NAP, GN, and PANU profiles.
+ +[7.1R] The +setkey(8) +utility now accepts esp as a protocol name for the spdadd command.
+ +[7.1R] A bug in
+telnetd(8) that
+it attempts authentication even when -a off option is
+specified has been fixed.
[7.1R] The
+top(1) and
+vmstat(8) now
+support -P flag which displays per-CPU statistics.
[7.1R] The +uuid_enc_le(3), + +uuid_dec_le(3), + +uuid_enc_be(3), +and +uuid_dec_be(3) +functions have been added. These functions encode/decode a binary representation of a +UUID.
+ +[7.1R] The +watch(8) utility +now supports more than 10 +snp(4) devices +at a time.
+ +[7.1R] The
+ypserv(8) now
+supports a -P option to specify the port number on which it
+should listen.
[7.1R] The
+rc.conf(5) now
+supports dummynet_enable variable which allow
+dummynet(4)
+kernel module to be loaded when firewall_enable is YES.
[7.1R] The ntpd rc(8) script can work +with no configuration file /etc/ntp.conf now.
+ +[7.1R] The ppp rc(8) script now
+supports multiple instances. For more details, see description of ppp_profile variable in
+rc.conf(5).
[7.1R] The sysctl rc(8) script now +supports loading /etc/sysctl.conf.local in addition to /etc/sysctl.conf.
+ +[7.1R] The
+rc.conf(5) now
+supports configuration of interfaces and attached networks for firewall rule set by rc.firewall when firewall_type is simple or client. See firewall_client_net, firewall_simple_iif, firewall_simple_inet, firewall_simple_oif, and firewall_simple_onet.
ISC BIND has been updated to version 9.6.1rc1.
+ +The ACPI-CA has been updated to 20090521.
+ +The ee (easy editor) has been updated to 1.5.0. This +version is now licensed under a 2-clause BSD license, instead of the Artistic +license.
+ +The hostapd has been updated to version 0.6.8 + radius ACL +support.
+ +The less has been updated to version v436.
+ +The libarchive library has been updated to version +2.7.0.
+ +The libexpat library has been updated from version 1.95.5 to +version 2.0.1.
+ +The ncurses library has been updated to version +5.7-20081102.
+ +OpenBSM 1.1 from Trusted BSD Project has been merged.
+ +TCPDUMP has been updated to 4.0.0.
+ +The timezone database has been updated from to the tzdata2009f release.
+ +wpa_supplicant has been updated to version 0.6.8
+ +The ZFS file system has been updated from version 6 to +version 13.
+ +[7.1R] The am-utils has been updated from version 6.0.10p1 +to version 6.1.5.
+ +[7.1R] The awk has been updated from 1 May 2007 release to +the 23 October 2007 release.
+ +[7.1R] The bzip2 has been updated from version 1.0.4 to +version 1.0.5.
+ +[7.1R] The CVS has been updated to version 1.11.22.1.
+ +[7.1R] NTP has been updated to version 4.2.4p5.
+ +[7.1R] OpenPAM has been updated from the Figwort release to +the Hydrangea release.
+ +[7.1R] OpenSSH has been updated from version 4.5p1 to +version 5.1p1.
+ +[7.1R] The +resolver(3) +library has been updated to one of ISC BIND 9.4.3.
+ +[7.1R] sendmail has been updated from version 8.14.2 to +version 8.14.3.
+[7.2R] A bug in the
+pkg_create(1)
+utility, which prevents the -n flag from working has been
+fixed.
[7.2R] The FreeBSD Ports Collection now supports multiple
+make(1) jobs in
+some supported ports. This is automatically enabled when a port is marked as MAKE_JOBS_SAFE and improves CPU utilization at the build stage by
+passing an option -jX to
+the top level Makefile from the vendor. The number X is set to the number of CPUs by default, and can be set
+by users via a
+make(1) variable
+MAKE_JOBS_NUMBER. For more details, see ports/Mk/bsd.port.mk.
The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.26.3.
+ +The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.3.1.
+[amd64, i386] 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 or SMP +kernels distributed as a part of an official FreeBSD release. The +freebsd-update(8) utility requires that the host +being upgraded has Internet connectivity.
+ +An older form of binary upgrade is supported through the Upgrade option from the main +sysinstall(8) +menu on CDROM distribution media. This type of binary upgrade may be useful on non-i386, +non-amd64 machines or on systems with no 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, of course, only be attempted after backing +up all data and configuration +files.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ + + diff --git a/en/releases/8.0R/relnotes.sgml b/en/releases/8.0R/relnotes.sgml new file mode 100644 index 0000000000..240fa42c59 --- /dev/null +++ b/en/releases/8.0R/relnotes.sgml @@ -0,0 +1,125 @@ + + + + +]> + + &header; + +The highlights in the 8.0-RELEASE are the following:
+ +A new virtualization container named “vimage” + has been implemented. This is a jail with a virtualized + instance of the FreeBSD network stack and can be created by + using + jail(8) + command.
The FreeBSD netisr framework has been reimplemented for + parallel threading support. This is a kernel network dispatch + interface which allows device drivers (and other packet + sources) to direct packets to protocols for directly + dispatched or deferred processing. The new implementation + supports up to one netisr thread per CPU, and several + benchmarks on SMP machines show substantial performance + improvement over the old one.
The FreeBSD newbus subsystem is now MPSAFE.
The FreeBSD TTY layer has been replaced with a new one + which has better support for SMP and robust resource handling. A tty + now has own mutex and it is expected to improve scalability when + compared to the old implementation based on Giant lock.
[amd64, i386] The FreeBSD Linux emulation layer has been + updated to version 2.6.16 and the default Linux infrastructure + port is now emulators/linux_base-f10 + (Fedora 10).
The FreeBSD GENERIC kernel now + includes Trusted BSD MAC (Mandatory Access Control) support. No MAC + policy module is loaded by default.
The FreeBSD USB subsystem has been reimplemented to support + modern devices and better SMP scalability. The new implementation + includes Giant-lock-free device drivers, Linux compatibility layer, + usbconfig(8) utility, full + support for split transaction and isochronous transaction, and so + on.
The FreeBSD CAM SCSI subsystem ( + cam(4)) now includes + experimental support for ATA/SATA/AHCI-compliant + devices.
The shared vnode locking for pathname lookups in the + VFS(9) subsystem has + been improved.
The ZFS file system has been + updated to version 13. The changes include ZFS operations by a regular + user, L2ARC, ZFS Intent Log on separated disks (slog), sparse volumes, + and so on.
The FreeBSD NFS subsystem now supports RPCSEC_GSS authentication on both the client and + server.
The FreeBSD NFS subsystem now includes a new, experimental + implementation with support for NFSv2, NFSv3, and + NFSv4.
The wireless network support layer (net80211) now supports + multiple BSS instances on the supported network + devices.
The FreeBSD L2 address translation table has been + reimplemented to reduce lock contention on parallel processing + and simplify the routing logic.
The IGMPv3 and SSM (Source-Specific Multicast) including + IPv6 SSM and MLDv2 have been added.
The + ipsec(4) subsystem now + supports NAT-Traversal (RFC 3948).
The GCC stack protection (also known as ProPolice) has been + enabled in the FreeBSD base system.
The supported version of the GNOME desktop environment (x11/gnome2) has been updated to + 2.26.3.
The supported version of the KDE + desktop environment (x11/kde4) has been updated to 4.3.1.
For more details, please see the + Detailed Release Notes.
+ +A list of all platforms currently under development can be found + on the Supported + Platforms page.
+ + &footer; + +