diff --git a/website/content/en/releases/5.2R/todo.adoc b/website/content/en/releases/5.2R/todo.adoc index 3613e62abb..23c7ac07fd 100644 --- a/website/content/en/releases/5.2R/todo.adoc +++ b/website/content/en/releases/5.2R/todo.adoc @@ -1,508 +1,508 @@ FreeBSD 5.2 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2 Open Issues

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail re@FreeBSD.org.

Show stopper defects for 5.2-RELEASE

IssueStatusResponsibleDescription

Required features for 5.2-RELEASE

IssueStatusResponsibleDescription
Fine-grained network stack locking without Giant In progress Sam Leffler Significant parts of the network stack (especially IPv4 and IPv6) now have fine-grained locking of their data structures. However, it is not yet possible for the netisr threads to run without Giant, due to dependencies on sockets, routing, etc. A 5.2-RELEASE goal is to have the forwarding path in the network stack able to run without Giant, which should substantially improve performance of the stack, as well as other system components by reducing contention on Giant. For stability reasons, this will be disabled by default in 5.2.

Desired features for 5.2-RELEASE

IssueStatusResponsibleDescription
KAME Synchronization In progress Hajimu UMEMOTO The FreeBSD KAME IPv6 code is now substantially dated with respect to the KAME vendor source. The FreeBSD Project needs to take initiative in driving the merge of new bug fixes, features, et al.
Light-weight interrupt threads, context switches Not done -- Currently, there are two classes of interrupt handlers in 5.x: fast interrupt handlers which run entirely in interrupt context, and heavy-weight handlers which execute in a full-weight kernel interrupt thread. It is possible to optimize interrupt thread context management such that a light-weight context switch is performed to begin execution of the interrupt thread in the handler context, and only when a full-weight context is required (such as sleeping on a lock) is that cost required. This optimization should substantially improve interrupt latency. There are also additional kernel thread context switch optimizations that can be made to improve the performance of thread workers in the kernel, such as found in the network stack, crypto worker threads, and GEOM. Bosko Milekic has done substantial prototyping work, and should be coordinated with.
Run-time autoconfiguration of GBDE and related transforms Not done -- Currently, gbde must be manually configured at run-time each time an encrypted disk device is mounted. This prevents easy integration into /etc/fstab and easy automated deployment. Improved integration with the configuration, mounting, and boot process is required to make this feature more easily accessible.
gdb -k support for alpha Not done Mark Peek gdb -k doesn't work on alpha

Documentation items desired for 5.2

IssueStatusResponsibleDescription
Revise EAG Done Bruce A. Mah The Early Adopters Guide needs to be revised, hopefully for the last time, to reflect the state of 5.2.
Trim Hardware Notes In progress Bruce A. Mah Ongoing project to remove redundancy in documentation by removing lists of specific devices from the hardware notes and pointing readers to driver manpages.

Testing focuses for 5.2-RELEASE

- + - +
IssueStatusResponsibleDescription
PCM locking and performance issues Needs testing -- The PCM audio framework and device drivers have been locked and free of Giant for quite a while, but LOR problems persist along with reports of poor audio performance under load. These problems are believed to have been corrected, but more testing is desired.
ATA driver structural improvements, MPsafety Needs testingSøren SchmidtSøren Schmidt New ATA model has arrived, supporting fine-grained locking, and more. Much testing is needed to ensure no regressions.
GPT support for sysinstall Needs testing Marcel Moolenaar Sysinstall and libdisk has been overhauled to support the GPT partition scheme used on ia64.
Complete the APIC PCI interrupt routing support Needs testing John Baldwin Interrupt routing on ia32 has been completely re-written to support ACPI hints for PCI interrupt routing, along with ACPI hints for CPU enumeration. There have been reports of interrupt storms or a failure for interrupts to deliver, possibly a result of bad ACPI information. These problems need to be tracked down and resolved.
ATAng crashdump causes disk corruption Needs testingSøren Schmidt, Tor EggeSøren Schmidt, Tor Egge Performing a crashdump on an ATA device can result in a corrupted MBR record. Tor has a possible patch for this.
SMP users report acpi_cpu panic during shutdown Needs testing Nate Lawson The ACPI code registers eventhandlers that are not unregistered when ACPI shuts down during system shutdown. The result can be a panic during shutdown. Nate is circulating a patch that is believed to correct this problem.
random_harvest panic Needs testing Mark Murray There are reports of witness panics in random_harvest_internal() due to last minute changes in interrupt entropy harvesting code. Systems running with INVARIANTS will rapidly panic. Update: a workaround has been committed, but the original change must either be backed out or revised before we can cut the first beta.
Vinum data corruption and memory allocation problems Needs testing Greg Lehey In the last week, reports of two new (and possibly related) Vinum failures have come to light: a warning message of vinum: exiting with malloc table inconsistency at 0xc2053c00 from vinumio.c:755 has been experienced when Vinum auto-configuration fails. Also, even simple test cases for Vinum I/O appear to result in incorrect data being returned from disk, rendering Vinum unusable in several reproduceable configurations.
ACPI kernel module Needs testing John Baldwin The new i386 inpterrupt code should work whether the acpi driver is compiled into the kernel or loaded as a module. The loader should automatically load the module if it's not already compiled in.
Reported NFS failures Unknown   There have been a number of reports of NFS clients and server hangs. Unfortunately, these are difficult to reproduce, and have not yet been traced back to a particular change or reliable reproduction scenario.
Turnstile assertion failure Unknown John Baldwin panic: Assertion td->td_turnstile != NULL failed at ../../../kern/subr_turnstile.c:427 has been affecting several users on multiple platforms. This has hopefully been fixed now, but more testinig is needed.
fsync panic while installing with softupdates enabled Needs testing Doug White, Jeff Roberson There is a repeatable panic happening for many people while installing 5.2-RC1 when softupdates are enabled on the root partition. This was being triggered by sysinstall doing a forced unmount of devfs while node where still active. VFS has been fixed to deal with this better, and sysinstall has bee fixed to not do the forced unmount.

diff --git a/website/content/en/releases/5.3R/todo.adoc b/website/content/en/releases/5.3R/todo.adoc index 273a7c06b0..44822826b6 100644 --- a/website/content/en/releases/5.3R/todo.adoc +++ b/website/content/en/releases/5.3R/todo.adoc @@ -1,860 +1,860 @@ FreeBSD 5.3 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3 Open Issues

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 5.3. If you have any updates for this list, please e-mail re@FreeBSD.org.

Issues that require investigation

IssueStatusResponsibleDescription

Show stopper defects for 5.3-RELEASE

IssueStatusResponsibleDescription

Required features for 5.3-RELEASE

IssueStatusResponsibleDescription

Desired features and bugfixes for 5.3-RELEASE

IssueStatusResponsibleDescription
Reports of poor performance with the if_re driver (re ethernet interfaces) In progress John-Mark Gurney There have been reports that specific gigabit ethernet cards supported by the if_re driver are experiencing poor performance; a patch has been posted that corrects timer and interrupt problems with the driver, and is believed to correct the performace problems. The patch will be merged to 6.x and 5.x shortly.
GDB thread support In progress David Xu, Marcel Moolenaar With improved support for threading primitives, support is now required to ease debugging of threaded applications. Ideally, this support will work for both libthr and libkse threading models.
KSE support for sparc64 In progress Ken Smith Kernel bits implemented, userland not implemented.
truss support for ptrace -- -- Almost all process debugging tools have been updated to use non-procfs kernel primitives, with the exception of truss(1). As procfs is considered deprecated due to its inherent security risks, it is highly desirable to update truss to operate in - a post-procfs world. Dag-Erling Smørgrav had prototype patches; Robert Drehmel + a post-procfs world. Dag-Erling Smørgrav had prototype patches; Robert Drehmel is developing and testing patches now. Support for system call tracing has been added to ptrace().
FAST_IPSEC and KAME compatibility Not done -- FAST_IPSEC currently cannot be used directly with the KAME IPv6 implementation, requiring an additional level of IP tunnel indirection to protect IPv6 packets when using hardware crypto acceleration. This issue must be resolved so that the two services may more easily be used together. Among other things, this will require a careful review of the handling of mbuf header copying and m_tag support in the KAME IPv6 code.
rpc.lockd(8) stability -- -- A process cannot be interrupted while waiting on a lock. Fixing this requires that the RPC code be taught how to deal with lock cancellation and interruption events.
Revised kld build infrastructure Not done Peter Wemm Kernel modules are currently built independently from a kernel configuration, and independently from one another, resulting in substantially redundant compilation of objects, as well as the inability to easily manage compile-time options for kernel objects (such as MAC, PAE, etc) that may require conditional compilation in the kernel modules. In order to improve build performance and better support options of this sort, the KLD build infrastructure needs to be revamped. Peter Wemm has done some initial prototyping, and should be contacted before starting on this work.
Race conditions in truss Errata candidate Robert Drehmel Truss appears to contain a race condition during the start-up of debugging, which can result in truss failing to attach to the process before it exits. The symptom is that truss reports that it cannot open the procfs node supporting the process being debugged. A bug also appears to exist where in truss will hang if execve() returns ENOENT. A further race appears to exist in which truss will return "PIOCWAIT: Input/output error" occasionally on startup. The fix for this sufficiently changes process execution handling that we will defer the fix to post-5.0 and consider this errata.
filedesc LOR Not done -- The LOR reported in PR kern/55175 needs to be fixed. Filedesc locking needs to be heavily reviewed in general.
KSE support for alpha In progress Marcel Moolenaar Userland bits implemented, kernel bits not implemented.
CAM locking In progress Scott Long, Justin T. Gibbs For kernel API/ABI compatibility reasons, it would be desirable to have the CAM locking strategy determined and loosely implemented for 5.3.
syscons not working on Sparc64 Ultra-30 Not done -- When running syscons on an Ultra-30 with Creator-3D typing characters on the keyboard produces garbage. Problem reported by Kris Kennaway. Debugging difficult due to lack of this particular configuration among developers and problem isn't present on similar hardware (e.g. no problem on Ultra-60 w/Creator-3D).

Documentation items that must be resolved for 5.3

IssueStatusResponsibleDescription
i386 Floppy Installation Docs Done Gavin Atkinson, Bruce A. Mah The installation documentation doesn't take into account the new floppy images (with a full kernel split across multiple disks). This should be updated.
References:
docs/70485 (closed)
Finish hardware notes trimming Done Simon L. B. Nielsen, Christian Brueffer Finish removing mention of individual devices in the hardware notes and use auto-generated lists, based on driver manual pages, instead.
sound(4) related manual pages Done Simon L. B. Nielsen The snd(4) and pcm(4) drivers have been renamed but their manual pages are still outdated. sound(4) has to be added and pcm(4), csa(4), gusc(4), sbc(4), and uaudio(4) should be revised. Other manual pages which refer to pcm(4) (if any) should possibly be revised, too. In addition, supported cards list needs to be updated.
References:
Manpage for snd_solo on -doc@
[PATCH] sound(4) related manpages 5.3 TODO item on -doc@
src/share/man/man4/Makefile rev.1.279
Sound section in the Handbook Done Marc Fonvieille This section is outdated, some rewrites are needed for 5.3-RELEASE.
References:
doc/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml rev.1.94
FDP documentations related pcm(4) Not done -- With the snd(4) and pcm(4) drivers changes, documentations (FAQ) regarding the use of these drivers need an update.
Early Adopter's Guide Done Bruce A. Mah, Tom Rhodes Xin LI pointed out that FreeBSD 5.3-RELEASE is the first stable release on 5.X and it is (hopefully) not for early adopters. Early Adopter's Guide is still useful, but contains a bit old information. Some parts of this guide need a rewrite, and this document should be published as "4.X to 5.X Migration Guide", which focuses difference between 4.X and 5.X.
References:
Draft for review
discussion on -doc@ and -current@
Installation Notes Not done Tom Rhodes Some parts are outdated. doc/70485 has been committed, but more work is needed to reflect the realities. bmah@ pointed out that we should have "quick-start" installation guide for each platform instead of the current ones because they become too long and difficult to be maintained.
References:
doc/70485 (closed)
Xorg Done Ken Tom, Marc Fonvieille Update the X11 chapter of the Handbook for X.Org's X11 server.
References:
books/handbook/config/chapter.xml rev.1.147
rc.d scripts Done Tom Rhodes Ch.11.4 and 11.5 of the Handbook must be updated to mention the new rc.d scripts and some ports use /etc/rc.conf for their configuration.
References:
books/handbook/config/chapter.xml rev.1.170
books/handbook/config/chapter.xml rev.1.172
Handbook's kernel configuration chapter Done Ceri Davies Chapter 8 must be updated to match 5.3-RELEASE.
References:
docs/70674 (closed)
books/handbook/kernelconfig/chapter.xml rev.1.135
Handbook's IPsec section Not done -- Some parts of Section 14.10 are outdated and are not correct for 5.X systems.
References:
ipsec on -doc@
Problem with IPSEC in handbook on -doc@
Handbook's Vinum chapter Not done -- Vinum chapter needs to be revised for 5.X systems.

Testing focuses for 5.3-RELEASE

- + - +
IssueStatusResponsibleDescription
KSE as the default threads library Needs testing David Xu, Daniel Eischen KSE has matured to the point of being more stable and POSIX-compliant than the traditional libc_r. All Tier-1 platforms MUST have stable KSE support for 5.3 in order to support a consistent transition. Additionally, all ports that depend on the pthreads API must be modified to properly detect and support the default threading library.
Updated binutils for all platforms Needs testing David O'Brien Binutils needs updating in order to support new platforms, newer GDB versions, and Thread Local Storage.
gcc 3.3 floating point alignment regression Needs testing   The previous GCC 3.3 snapshot included regressions in alignment of floating point arguments, resulting in a substantial performance degradation. The recent GCC 3.4.2 import should fix this, but more testing is needed.
in6_pcbnotify() panic with TCP Done Robert Watson Jun Kuriyama has reported a failed locking assertion with IPv6 TCP notifications. This problem is believed to be corrected.
Per-platform Thread-Local Storage Needs testing Doug Rabson, Marcel Moolenaar To complete support for thread-local storage on FreeBSD, per-architecture changes must be made. Currently pending platforms are amd64, alpha, ia64, i386, sparc64, and powerpc.
SMP instability under load Needs testing Doug White, Alan L. Cox High load on SMP systems appears to result in a hard hang related to VM IPI. Doug White has prepared a candidate patch that appears to resolve this instability, which is currently in testing for merge to the CVS HEAD.
Fine-grained network stack locking without Giant Needs testing Robert Watson Significant parts of the network stack (especially IPv4, UNIX domain IPC, and sockets) now have fine-grained locking of their data structures. It's possible to run many common network subsystems and services without the Giant lock. However, a number of device drivers and less mainstream network subsystems are currently not MPSAFE. 5.3 betas have shipped with Giant-free networking by default, with some bug reports and fixes in later betas and release candidates. Please report any problems to the current@ mailing list.
kld support for amd64 Needs testing David O'Brien, Ian Dowse KLDs work when loaded from userland, but not from the loader. kldxref and loader support has been committed to HEAD and RELENG_5 and needs final testing.
ATA panics under sparc64 Needs testingSøren Schmidt, Scott LongSøren Schmidt, Scott Long Recent changes to the ATA driver trigger a bug on sparc64 that causes a panic on boot. This was caused by bugs in busdma that have been hopefully fixed.
ifconf() sleep warning Done Brooks Davis The ifconf() ioctl for listing network interfaces performs a copyout() while holding the global ifnet list mutex. This generates a witness warning in the event that copyout() generates a page fault, and risks more serious problems. This problem is believed to be corrected.
poll()/select() application wedge reports with debug.mpsafenet="1" Done Robert Watson There are reports of applications wedging in poll() and select() while running the network stack without the Giant lock. A recent sleepq change appears to have caused some of the observed problems to go away (others are difficult to test for due to recent SMP instability). This problem appears to be corrected.
if_em wedging under high pps Done Max Laier There have been several reports of if_em cards "wedging" under high packets-per-second load. This problem appears to have been corrected.
Panic on USB detach Needs testing Warner Losh, Scott Long A recent regression in the USB code is causing panics when a USB device detaches, especially USB hubs. A fix is in RELENG_5 now.
KAME IPSEC "ENOBUFS" problem with racoon and mbuma Done Robert Watson, Sam Leffler There are reports that racoon is unable to complete IKE negotiation due to a send to the pfkey socket returning ENOBUFS. This appears to be a result of an incorrect assumption about mbuf data size due to a change resulting from mbuma. This problem appears to have been corrected.
BIND9 import into 5-CURRENT DoneDoug Barton, Dag-Erling Smørgrav, Tom RhodesDoug Barton, Dag-Erling Smørgrav, Tom Rhodes BIND9 is now in RELENG_5 and HEAD. Testing is needed of basic functionality, migration from 8.x, and 3rd party packages in the ports tree.
Synaptics touchpad problems Needs testing Philip Paeps Synaptics updates to the psm(4) driver have resulted in poor interactivity for taps and button press events for some users. Support is now disabled by default but work will procede to fix the underlying problems.
Scheduler-related hangs involving threads Needs testing Scott Long, Julian Elischer Significant work has happened in the scheduler to fix stability problems. More testing for UP and SMP under heavily load is needed.
NFS over IPv6 problems Done Doug White Jun Kuriyama has reported problems with NFS over IPv6 not functioning correctly as of the improved NFS support for disconnection changes. Doug White has tracked down the source of the problem (EMSGSIZE being returned by IPv6 UDP send routine due to fragmentation), and is currently exploring possible fixes. This problem appears to have been corrected.
Reports of socket buffer corruption in tcp_output() Done Robert Watson There have been reports of occasional corruption of socket buffers. This may have been the result of missing socket buffer locking in tcp_output(), which has now been corrected in 6.x and 5.x; this problem is believed to be fixed.
Reports of hangs using i4b (isdn4bsd) Done Robert Watson There have been reports of system hangs while using ISDN with the i4b ISDN framework on SMP systems. These likely result from insufficient synchronization in the i4b implementation when runnning without the Giant lock over the network stack. The workaround until this is fixed is to re-assert the Giant lock over the stack when i4b is compiled into the kernel; this has been committed to 6.x and and 5.x. This problem appears to have been corrected.
Problems with multicast and setuid binaries/daemons Done Robert Watson, Christian S.J. Peron There have been reports that multicast socket options on raw sockets no longer work properly with daemons changing privilege or setuid binaries. These symptoms have been tracked down to bugs relating to permitting limited use of raw sockets in jail(). A patch correcting these problems has been merged to 6.x and 5.x. This problem appears to have been corrected.
Reports of sodealloc() panic under heavy load Done Robert Watson, Brian F. Feldman There have been reports of a so_count invariant violation in sofree(), which may relate to race conditions in sofree() against accept(), which were recently corrected in 6.x, and has been merged to 5.x. This problem appears to have been corrected.
Merge of Darwin msdosfs, other fixes Done -- Apple's Darwin operating system has fairly extensive improvements to msdosfs and other kernel services; these fixes must be reviewed and merged to the FreeBSD tree.
Reports of poor performance of the if_de driver (de ethernet interfaces) Done Robert Watson, John-Mark Gurney There have been reports that if_de ethernet cds behave poorly when running with debug.mpsafenet="1", even though the driver is marked to run all portions with the Giant lock. This suggests a race condition specific to this drive, which is currently being debugged. A patch has been committed to the 6.x and 5.x branches, and appears to correct the problem.
Threaded application get stuck in an unkillable state when touched by GDB Done David Xu Attaching GDB to a threaded process will leave the process in an unkillable state. Rebooting the machine is the only way to recover from this. This is easily triggered when a KDE app crashes and KDE automatically attaches GDB to it to extract a stack trace. A candidate fix is in 6-CURRENT. More testing and review is needed.
More truss problems Done Alfred Perlstein Truss appears to have another problem. It is repeatable by running "truss -f fsck -p /", suspending it with ^Z, and then killing truss. It will leave behind the fsck processes which will be unkillable.
Reports of TCP-related instability under extremely high load; possibly related to SACK Needs testing George V. Neville-Neil, Robert Watson, Scott Long There have been reports that, under extremely high load, the tcp_output() routine may appear to run for extended periods, resulting in the appearance of a hang for an extended period (up to 30 minutes), followed by recovery. A fix for SACK was developed and committed that hopefully corrects this problem.

diff --git a/website/content/en/releases/8.4R/announce.adoc b/website/content/en/releases/8.4R/announce.adoc index 0a27859e5c..ff7ebf706d 100644 --- a/website/content/en/releases/8.4R/announce.adoc +++ b/website/content/en/releases/8.4R/announce.adoc @@ -1,578 +1,578 @@ FreeBSD 8.4-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.4-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 8.4-RELEASE. This is the fifth release from the 8-STABLE branch which improves on the functionality of FreeBSD 8.3 and introduces some new features. Some of the highlights:

  • Gnome version 2.32.1, KDE version 4.10.1

  • Feature flags 5000 version of the ZFS filesystem.

  • Support for all shipping LSI storage controllers.

For a complete list of new features and known problems, please see the online release notes and errata list, available at:

For more information about FreeBSD release engineering activities, please see:

FreeBSD 8.4-RELEASE is now available for the amd64 and i386 architectures. Images for the pc98 architecture should be available within the next 24 hours.

FreeBSD 8.4 can be installed from bootable ISO images or over the network. Some architectures (currently amd64 and i386) also support installing from a USB memory stick. The required files can be downloaded via FTP as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

SHA256 and MD5 hashes for the release ISO and memory stick images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1:

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1:

This contains the base FreeBSD operating system and the English documentation package for CDROM-sized media. There are no other packages.

livefs:

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly:

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

memstick:

This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. The documentation packages are provided but no other packages.

As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:

# dd if=FreeBSD-8.4-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.4-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 8.4-based products is:

FTP

At the time of this announcement the following FTP sites have FreeBSD 8.4-RELEASE available.

However before trying these sites please check your regional mirror(s) first by going to:

  • ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

For instructions on installing FreeBSD or updating an existing machine to 8.4-RELEASE please see:

Support

The FreeBSD Security Team currently plans to support FreeBSD 8.4 until June 30, 2015. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 8.4 including The FreeBSD Foundation, Yahoo!, NetApp, Internet Systems Consortium, Sentex Communications, New York Internet, Juniper Networks, and iXsystems.

The release engineering team for 8.4-RELEASE includes:

- +
Josh Paetzel <jpaetzel@FreeBSD.org> Release Engineering, 8.4-RELEASE Release Engineer
Ken Smith <kensmith@FreeBSD.org> Release Engineering, Release Engineering Team Lead, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Marcus von Appen <mva@FreeBSD.org> Release Engineering
Glen Barber <gjb@FreeBSD.org> Release Engineering
Joel Dahl <joel@FreeBSD.org> Release Engineering
Steven Kreuzer <skreuzer@FreeBSD.org> Release Engineering
Xin Li <delphij@FreeBSD.org> Release Engineering
Craig Rodrigues <rodrigc@FreeBSD.org> Release Engineering
Gleb Smirnoff <glebius@FreeBSD.org> Release Engineering
Marius Strobl <marius@FreeBSD.org> Release Engineering
Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org> Package Building
Dag-Erling Smørgrav <des@FreeBSD.org>Dag-Erling Smørgrav <des@FreeBSD.org> Security Officer
Colin Percival <cperciva@FreeBSD.org> Security Officer Emeritus
Simon L. B. Nielsen <simon@FreeBSD.org> Security Officer Emeritus

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

SHA256 (FreeBSD-8.4-RELEASE-amd64-bootonly.iso) = c167d11721c2e505c062ccec4d0923fe18839d56c49e99e0646ab0de04294338
 SHA256 (FreeBSD-8.4-RELEASE-amd64-disc1.iso) = 2fb17d77d4eba34736eb98c142c56546dd73a4e7ac38895bb6c8517949282438
 SHA256 (FreeBSD-8.4-RELEASE-amd64-dvd1.iso) = 0a1acf77dee7fca7f71864e39804414ef53ad0540f2205bf0bfb954150f171f2
 SHA256 (FreeBSD-8.4-RELEASE-amd64-livefs.iso) = 6c0e004556e931da711d48bd530aaf45c056e4336b15acc00495cde128d8337a
 SHA256 (FreeBSD-8.4-RELEASE-amd64-memstick.img) = fe6686ce9f1c9afd3d1ee41d6c842d2173cfc8fed700fb76954fa2e2bef149cd
MD5 (FreeBSD-8.4-RELEASE-amd64-bootonly.iso) = 6d0cb38073c803d5f76cdbd89e0a6f24
 MD5 (FreeBSD-8.4-RELEASE-amd64-disc1.iso) = 642aba9299a30f06aca521abe0abb102
 MD5 (FreeBSD-8.4-RELEASE-amd64-dvd1.iso) = c8dfd45a0b4d6afca1aa79b7374682fe
 MD5 (FreeBSD-8.4-RELEASE-amd64-livefs.iso) = 72631f6b8a494390393db9f7c7a877bf
 MD5 (FreeBSD-8.4-RELEASE-amd64-memstick.img) = 36823c5c2613220ebc304d2508874cf6
SHA256 (FreeBSD-8.4-RELEASE-i386-bootonly.iso) = 8a92bea891f2e9bb3a4c8613c3e075c72491a5f3904219abea00eadf3c8d4258
 SHA256 (FreeBSD-8.4-RELEASE-i386-disc1.iso) = 73ecc5ba0c36e7682c4862e7351d385e2e07bc97a09f9dff326d3cc1ec690cf8
 SHA256 (FreeBSD-8.4-RELEASE-i386-dvd1.iso) = 28fcba3954f5014b67748f9870b7db9a95797a88e68956523f39dea8824fa694
 SHA256 (FreeBSD-8.4-RELEASE-i386-livefs.iso) = 7ed52fd38bc399603ff2f69013df54032f44fb431bcf1cfb4e30230cd37e323b
 SHA256 (FreeBSD-8.4-RELEASE-i386-memstick.img) = 071d889db802fc144c977023a94aece94dbe5a9e4019e85f7449128153110031
MD5 (FreeBSD-8.4-RELEASE-i386-bootonly.iso) = aca12a59ee988cccd19e4835ef8e6291
 MD5 (FreeBSD-8.4-RELEASE-i386-disc1.iso) = 051bfda6a9521ca950548b5449c8c5ce
 MD5 (FreeBSD-8.4-RELEASE-i386-dvd1.iso) = ca3ae875d0880e6b966f8eee2b13da40
 MD5 (FreeBSD-8.4-RELEASE-i386-livefs.iso) = 13ca52edd45284fb64133ceef804f890
 MD5 (FreeBSD-8.4-RELEASE-i386-memstick.img) = 52affc47ba90c9fa8df823a8c8c046e0
SHA256 (FreeBSD-8.4-RELEASE-pc98-bootonly.iso) = f88c46c223ce26146c4b82cb636fae33ff6903641ae95969f2e1e412f4ad9005
 SHA256 (FreeBSD-8.4-RELEASE-pc98-disc1.iso) = 6b7a564bdf9ba3f9370df52b78a85fdbb8eb480c9baeb07dfbc6a0374a86db91
 SHA256 (FreeBSD-8.4-RELEASE-pc98-livefs.iso) = 3d90e8f1aea96c4922be3aef8d2fd4ab54f07f2a30d0ae46eb29673b9db61065
MD5 (FreeBSD-8.4-RELEASE-pc98-bootonly.iso) = 8303bbf3b80a90e82fcee3e9280d297a
 MD5 (FreeBSD-8.4-RELEASE-pc98-disc1.iso) = a95bd4331afa524fc57ca9606893a814
 MD5 (FreeBSD-8.4-RELEASE-pc98-livefs.iso) = af6e0c5fee2ca6cf1f5b849fe4a2abb2

diff --git a/website/content/en/releases/8.4R/errata.adoc b/website/content/en/releases/8.4R/errata.adoc index c90c41ceae..63943ff2a0 100644 --- a/website/content/en/releases/8.4R/errata.adoc +++ b/website/content/en/releases/8.4R/errata.adoc @@ -1,158 +1,158 @@ FreeBSD 8.4-RELEASE Errata

FreeBSD 8.4-RELEASE Errata

The FreeBSD Project -

Copyright © 2015 The FreeBSD Documentation Project

FreeBSD is a registered trademark of +

Copyright © 2015 The FreeBSD Documentation Project

FreeBSD is a registered trademark of the FreeBSD Foundation.

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

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

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

Last modified on 2015-02-05 by gjb.
Abstract

This document lists errata items for FreeBSD 8.4-RELEASE, + “®” symbol.

Last modified on 2015-02-05 by gjb.
Abstract

This document lists errata items for FreeBSD 8.4-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.4-RELEASE will be maintained until the FreeBSD 8.4-RELEASE end of life.

Table of Contents
1. Introduction
2. Security Advisories
3. Errata Notices
4. Open Issues
5. Late-Breaking News and Corrections

1. Introduction

This errata document contains “late-breaking news” about FreeBSD 8.4-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.4-STABLE also contain up-to-date copies of this document (as of the time of the snapshot).

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

2. Security Advisories

Problems described in the following security advisories have been fixed in 8.4-RELEASE. For more information, consult the individual advisories available from http://security.FreeBSD.org/.

AdvisoryDateTopic
FreeBSD-SA-13:07.bind26 July 2013

Denial of Service vulnerability in named(8)

FreeBSD-SA-13:09.ip_multicast21 August 2013

Integer overflow in computing the size of a temporary buffer can result in a buffer which is too small for the requested operation

FreeBSD-SA-13:10.sctp21 August 2013

Fix a bug that could lead to kernel memory disclosure with SCTP state cookie

FreeBSD-SA-13:12.ifioctl10 September 2013

In IPv6 and NetATM, stop SIOCSIFADDR, SIOCSIFBRDADDR, SIOCSIFDSTADDR and SIOCSIFNETMASK at the socket layer rather than pass them on to the link layer without validation or credential checks

FreeBSD-SA-13:13.nullfs10 September 2013

Prevent cross-mount hardlinks between different nullfs mounts of the same underlying filesystem

FreeBSD-SA-14:01.bsnmpd14 January 2014

bsnmpd remote denial of service vulnerability

FreeBSD-SA-14:02.ntpd14 January 2014

ntpd distributed reflection Denial of Service vulnerability

FreeBSD-SA-14:04.bind14 January 2014

BIND remote denial of service vulnerability

FreeBSD-SA-14:05.nfsserver8 April 2014

NFS deadlock vulnerability

FreeBSD-SA-14:06.openssl8 April 2014

ECDSA Cache Side-channel Attack in OpenSSL

FreeBSD-SA-14:08.tcp30 April 2014

TCP reassembly vulnerability

FreeBSD-SA-14:11.sendmail5 June 2014

sendmail improper close-on-exec flag handling

FreeBSD-SA-14:12.ktrace5 June 2014

ktrace memory disclosure

FreeBSD-SA-14:14.openssl5 June 2014

OpenSSL multiple vulnerabilities

FreeBSD-SA-14:16.file5 June 2014

Multiple vulnerabilities in file(1) and libmagic(3)

FreeBSD-SA-14:17.kmem8 July 2014

kernel memory disclosure in control message and SCTP notifications

FreeBSD-SA-14:18.openssl9 September 2014

Multiple vulnerabilities in OpenSSL

FreeBSD-SA-14:19.tcp16 September 2014

Denial of Service in TCP packet processing

FreeBSD-SA-14:21.routed21 October 2014

routed(8) denial of service vulnerability

FreeBSD-SA-14:23.openssl21 October 2014

Multiple vulnerabilities in OpenSSL

FreeBSD-SA-14:25.setlogin4 November 2014

kernel stack disclosure in setlogin(2) and getlogin(2)

FreeBSD-SA-14:26.ftp4 November 2014

Remote command execution in ftp(1)

FreeBSD-SA-14:28.file10 December 2014

Multiple vulnerabilities in file(1) and libmagic(3)

FreeBSD-SA-14:29.bind10 December 2014

BIND remote denial of service vulnerability

FreeBSD-SA-14:31.ntp23 December 2014

Multiple vulnerabilities in NTP suite

FreeBSD-SA-15:01.ntp14 January 2015

Multiple vulnerabilities in OpenSSL

FreeBSD-SA-15:02.kmem27 January 2015

Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure vulnerability

FreeBSD-SA-15:03.sctp27 January 2015

Fix SCTP stream reset vulnerability

FreeBSD-SA-15:04.igmp25 February 2015

Integer overflow in IGMP protocol

FreeBSD-SA-15:05.igmp25 February 2015

Remote denial of service vulnerability

FreeBSD-SA-15:06.openssl19 March 2015

Multiple vulnerabilities

FreeBSD-SA-15:07.ntp7 April 2015

Multiple vulnerabilities

FreeBSD-SA-15:09.ipv67 April 2015

Router advertisement Denial of Service

FreeBSD-SA-15:10.openssl16 June 2015

Multiple vulnerabilities

FreeBSD-SA-15:11.bind7 July 2015

Resolver remote denial of service

FreeBSD-SA-15:13.tcp21 July 2015

resource exhaustion due to sessions stuck in LAST_ACK state.

FreeBSD-SA-15:15.tcp28 July 2015

resource exhaustion in TCP reassembly

FreeBSD-SA-15:16.openssh28 July 2015

Multiple vulnerabilities

FreeBSD-SA-15:17.bind28 July 2015

Remote denial of service vulnerability

3. Errata Notices

ErrataDateTopic
FreeBSD-EN-13:01.fxp28 June 2013

Fixed a problem where dhclient(8) would infinitely try to intialize fxp(4)

FreeBSD-EN-13:02.vtnet28 June 2013

Fixed a problem frames sent to additional MAC addresses are not forwarded to the vtnet(4) interface

FreeBSD-EN-13:04.freebsd-update26 October 2013

Multiple fixes

FreeBSD-EN-13:05.freebsd-update28 November 2013

Fix INDEX generation

FreeBSD-EN-14:01.random14 January 2014

Disable hardware RNGs by default

FreeBSD-EN-14:02.mmap14 January 2014

Fix incorrect coalescing of stack entry

FreeBSD-EN-14:03.pkg15 May 2014

Add pkg bootstrapping, configuration and public keys

FreeBSD-EN-14:04.kldxref15 May 2014

Improve build repeatability for kldxref(8)

FreeBSD-EN-14:06.exec3 June 2014

Fix triple-fault when executing from a threaded process

FreeBSD-EN-14:08.heimdal24 June 2014

Fix gss_pseudo_random() interoperability issue

FreeBSD-EN-14:09.jail8 July 2014

Fix jail fails to start if WITHOUT_INET/WITHOUT_INET6 is use

FreeBSD-EN-14:10.tzdata21 October 2014

Time zone data file update

FreeBSD-EN-14:12.zfs4 November 2014

Fix NFSv4 and ZFS cache consistency issue

FreeBSD-EN-14:13.freebsd-update23 December 2014

Fix directory deletion issue

FreeBSD-EN-15:02.openssl25 February 2015

OpenSSL update

FreeBSD-EN-15:03.freebsd-update25 February 2015

freebsd-update(8) updates libraries in suboptimal order

FreeBSD-EN-15:04.freebsd-update13 May 2015

freebsd-update(8) does not ensure the previous upgrade has completed

FreeBSD-EN-15:06.file9 June 2015

Multiple denial of service issues

FreeBSD-EN-15:08.sendmail30 June 2015 (revised)

Sendmail TLS/DH interoperability improvement

4. Open Issues

[20130613] The vtnet(4) network interface driver displays the following message upon configuration when using QEMU 1.4.1 and later:

vtnet0: error setting host MAC filter table

This message is harmless when the interface has only one MAC address. The patch for this issue is filed to a PR kern/178955.

[20130609] There is incompatibility in jail(8) configuration because the jail(8) utility and rc.d/jail script has been changed. More specifically, the following sysctl(8) variables cannot be used to set the default parameters for jails:

security.jail.mount_zfs_allowed
 security.jail.mount_procfs_allowed
 security.jail.mount_nullfs_allowed
 security.jail.mount_devfs_allowed
 security.jail.mount_allowed
 security.jail.chflags_allowed
 security.jail.allow_raw_sockets
 security.jail.sysvipc_allowed
 security.jail.socket_unixiproute_only
 security.jail.set_hostname_allowed

These could be set by manually using sysctl(8) utility, the sysctl.conf(5) file, or for some of them the following variables in rc.conf(5):

jail_set_hostname_allow="yes"
 jail_socket_unixiproute_only="yes"
 jail_sysvipc_allow="yes"

These parameters must now be specified in jail_parameters (or jail_jailname_parameters for per-jail configuration) in rc.conf(5). For example:

jail_parameters="allow.sysvipc allow.raw_sockets"

The valid keywords are the following. For more detail, see jail(8) manual page.

allow.set_hostname
 allow.sysvipc
 allow.raw_sockets
 allow.chflags
 allow.mount
 allow.mount.devfs
 allow.mount.nullfs
 allow.mount.procfs
 allow.mount.zfs
 allow.quotas
 allow.socket_af

[20130608] FreeBSD 8.4-RELEASE no longer supports FreeBSD CVS repository. Some documents mistakenly refer to RELENG_8_4_0_RELEASE as CVS tag for the release and RELENG_8_4 as CVS branch tag for the 8.4-RELEASE security branch. However, FreeBSD Project no longer supports FreeBSD CVS repository and 8.4-RELEASE has been released by using FreeBSD subversion repository instead. RELENG_8_4 corresponds to svn://svn.FreeBSD.org/base/releng/8.4, and RELENG_8_4_0_RELEASE corresponds to svn://svn.FreeBSD.org/base/release/8.4.0. Please note that FreeBSD source tree for 8.4-RELEASE and its security branch cannot be updated by using official CVSup servers.

[20130607] (removed about a bge(4) network interface driver issue because it was incorrect)

[20130606] The fxp(4) network interface driver may not work well with the dhclient(8) utility. More specifically, if the /etc/rc.conf has the following line:

ifconfig_fxp0="DHCP"

to activate a DHCP client to configure the network interface, the following notification messages are displayed and the dhclient(8) utility keeps trying to initialize the network interface forever.

kernel: fxp0: link state changed to UP
 kernel: fxp0: link state changed to DOWN

A patch to fix this issue will be released as an Errata Notice.

5. Late-Breaking News and Corrections

[20130606] As described in FreeBSD 8.4-RELEASE Release Notes, FreeBSD ZFS subsystem has been updated to support feature flags for ZFS pools. However, the default version number of a newly created ZFS pool is still 28.

This is because FreeBSD 9.0 and 9.1 do not support the feature flags. This means ZFS pools with feature flag support cannot be used on FreeBSD 9.0 and 9.1. An 8.X system with v28 ZFS pools can be upgraded to 9.X with no problem. Note that zfs(8) send and receive commands do not work between pools with different versions. Once a ZFS pool is upgraded from v28, there is no way to upgrade the system to FreeBSD 9.0 and 9.1. FreeBSD 9.2 and later will support ZFS pools with feature flags.

To create a ZFS pool with feature flag support, use the zpool(8) create command and then the zpool(8) upgrade command.

\ No newline at end of file diff --git a/website/content/en/releases/8.4R/hardware.adoc b/website/content/en/releases/8.4R/hardware.adoc index 676c0d2f19..efeab6dd00 100644 --- a/website/content/en/releases/8.4R/hardware.adoc +++ b/website/content/en/releases/8.4R/hardware.adoc @@ -1,10608 +1,10608 @@ FreeBSD 8.4-RELEASE Hardware Notes

FreeBSD 8.4-RELEASE Hardware Notes

The FreeBSD Documentation Project

Copyright © 2013 The FreeBSD Documentation Project

$FreeBSD: releng/8.4/release/doc/en_US.ISO8859-1/hardware/article.xml 251256 2013-06-02 15:47:22Z hrs $

FreeBSD is a registered trademark of the FreeBSD Foundation.

-

AMD, Am486, Am5X86, AMD Athlon, AMD Duron, AMD Opteron, AMD-K6, Athlon, Élan, Opteron, +

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

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

IBM, AIX, 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. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

Sun, Sun Microsystems, Java, Java Virtual Machine, JavaServer Pages, JDK, JRE, JSP, JVM, Netra, OpenJDK, 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.

+by the “™” or the “®” symbol.

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

1 Introduction

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

2 Supported Processors and System Boards

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

2.1 amd64

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

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

As of this writing, the following processors are supported:

  • AMD Athlon™64 (“Clawhammer”).

  • AMD Opteron™ (“Sledgehammer”).

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

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

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

  • All Intel Pentium® D processors

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

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

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

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

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

2.2 i386

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

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

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

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

FreeBSD will take advantage of SMT (Symmetric MultiThreading, also known as HyperThreading on Intel CPUs) on the supported CPUs. The GENERIC kernel which is installed by default will automatically detect the additional logical processors. The default FreeBSD scheduler recognizes processor topology on the system and selects logical and physical processors to obtain optimal performance. The smp(4) manual page has more details.

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

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

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

 hint.acpi.0.disabled="1"

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

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

2.3 ia64

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

Supported chipsets include:

  • HP zx1

  • Intel 460GX

  • Intel E8870

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

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

2.4 pc98

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

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

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

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

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

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

2.5 powerpc

The information for this paragraph has yet to be compiled.

2.6 sparc64

This section describes the systems currently known to be supported by FreeBSD on the Fujitsu SPARC64® and Sun UltraSPARC® platforms. 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.4-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:

  • Naturetech GENIALstation 777S

  • Sun Blade 100

  • Sun Blade 150

  • Sun Enterprise™ 150

  • Sun Enterprise 220R

  • Sun Enterprise 250

  • Sun Enterprise 420R

  • Sun Enterprise 450

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

  • Sun Fire V100

  • Sun Fire V120

  • Sun Netra™ t1 100/105

  • Sun Netra T1 AC200/DC200

  • Sun Netra t 1100

  • Sun Netra t 1120

  • Sun Netra t 1125

  • Sun Netra t 1400/1405

  • Sun Netra 120

  • Sun Netra X1

  • Sun SPARCengine® Ultra AX1105

  • Sun SPARCengine Ultra AXe

  • Sun SPARCengine Ultra AXi

  • Sun SPARCengine Ultra AXmp

  • Sun SPARCengine CP1500

  • Sun Ultra 1

  • Sun Ultra 1E

  • Sun Ultra 2

  • Sun Ultra 5

  • Sun Ultra 10

  • Sun Ultra 30

  • Sun Ultra 60

  • Sun Ultra 80

  • Sun Ultra 450

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

  • Sun Enterprise 3500

  • Sun Enterprise 4500

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

  • Sun Blade 1000

  • Sun Blade 1500

  • Sun Blade 2000

  • Sun Blade 2500

  • Sun Fire 280R

  • Sun Fire V210

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

  • Sun Fire V240

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

  • Sun Fire V250

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

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

  • Sun Fire V880

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

  • Netra 20/Netra T4

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

  • Sun Fire V125

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

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

  • Fujitsu PRIMEPOWER® 250

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

  • Fujitsu PRIMEPOWER 450

  • Fujitsu PRIMEPOWER 650

  • Fujitsu PRIMEPOWER 850

3 Supported Devices

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

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

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

3.1 Disk Controllers

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

[pc98] IDE/ATA controllers (wdc driver)

  • On-board IDE controller

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

  • Adaptec AAC-364

  • Adaptec RAID 2045

  • Adaptec RAID 2405

  • Adaptec RAID 2445

  • Adaptec RAID 2805

  • Adaptec RAID 3085

  • Adaptec RAID 31205

  • Adaptec RAID 31605

  • Adaptec RAID 5085

  • Adaptec RAID 51205

  • Adaptec RAID 51245

  • Adaptec RAID 51605

  • Adaptec RAID 51645

  • Adaptec RAID 52445

  • Adaptec RAID 5405

  • Adaptec RAID 5445

  • Adaptec RAID 5805

  • Adaptec SAS RAID 3405

  • Adaptec SAS RAID 3805

  • Adaptec SAS RAID 4000SAS

  • Adaptec SAS RAID 4005SAS

  • Adaptec SAS RAID 4800SAS

  • Adaptec SAS RAID 4805SAS

  • Adaptec SATA RAID 2020SA ZCR

  • Adaptec SATA RAID 2025SA ZCR

  • Adaptec SATA RAID 2026ZCR

  • Adaptec SATA RAID 2410SA

  • Adaptec SATA RAID 2420SA

  • Adaptec SATA RAID 2610SA

  • Adaptec SATA RAID 2620SA

  • Adaptec SATA RAID 2810SA

  • Adaptec SATA RAID 2820SA

  • Adaptec SATA RAID 21610SA

  • Adaptec SCSI RAID 2020ZCR

  • Adaptec SCSI RAID 2025ZCR

  • Adaptec SCSI RAID 2120S

  • Adaptec SCSI RAID 2130S

  • Adaptec SCSI RAID 2130SLP

  • Adaptec SCSI RAID 2230SLP

  • Adaptec SCSI RAID 2200S

  • Adaptec SCSI RAID 2240S

  • Adaptec SCSI RAID 3230S

  • Adaptec SCSI RAID 3240S

  • Adaptec SCSI RAID 5400S

  • Dell CERC SATA RAID 2

  • Dell PERC 2/Si

  • Dell PERC 2/QC

  • Dell PERC 3/Si

  • Dell PERC 3/Di

  • Dell PERC 320/DC

  • HP ML110 G2 (Adaptec SATA RAID 2610SA)

  • HP NetRAID 4M

  • IBM ServeRAID 8i

  • IBM ServeRAID 8k

  • IBM ServeRAID 8s

  • ICP RAID ICP5045BL

  • ICP RAID ICP5085BL

  • ICP RAID ICP5085SL

  • ICP RAID ICP5125BR

  • ICP RAID ICP5125SL

  • ICP RAID ICP5165BR

  • ICP RAID ICP5165SL

  • ICP RAID ICP5445SL

  • ICP RAID ICP5805BL

  • ICP RAID ICP5805SL

  • ICP ICP5085BR SAS RAID

  • ICP ICP9085LI SAS RAID

  • ICP ICP9047MA SATA RAID

  • ICP ICP9067MA SATA RAID

  • ICP ICP9087MA SATA RAID

  • ICP ICP9014RO SCSI RAID

  • ICP ICP9024RO SCSI RAID

  • Legend S220

  • Legend S230

  • Sun STK RAID REM

  • Sun STK RAID EM

  • SG-XPCIESAS-R-IN

  • SG-XPCIESAS-R-EX

  • AOC-USAS-S4i

  • AOC-USAS-S8i

  • AOC-USAS-S4iR

  • AOC-USAS-S8iR

  • AOC-USAS-S8i-LP

  • AOC-USAS-S8iR-LP

[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-1110ML

  • ARC-1120ML

  • ARC-1130ML

  • ARC-1160ML

  • ARC-1200

  • ARC-1201

  • ARC-1210

  • ARC-1212

  • ARC-1213

  • ARC-1214

  • ARC-1220

  • ARC-1222

  • ARC-1223

  • ARC-1224

  • ARC-1230

  • ARC-1231

  • ARC-1260

  • ARC-1261

  • ARC-1270

  • ARC-1280

  • ARC-1210ML

  • ARC-1220ML

  • ARC-1231ML

  • ARC-1261ML

  • ARC-1280ML

  • ARC-1380

  • ARC-1381

  • ARC-1680

  • ARC-1681

  • ARC-1880

  • ARC-1882

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

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

  • Adaptec SCSI RAID 2100S, 2110S

  • Adaptec ATA-100 RAID 2400A

  • Adaptec SCSI RAID 3200S, 3210S

  • Adaptec SCSI RAID 3400S, 3410S

  • Adaptec SmartRAID PM1554

  • Adaptec SmartRAID PM1564

  • Adaptec SmartRAID PM2554

  • Adaptec SmartRAID PM2564

  • Adaptec SmartRAID PM2664

  • Adaptec SmartRAID PM2754

  • Adaptec SmartRAID PM2865

  • Adaptec SmartRAID PM3754

  • Adaptec SmartRAID PM3755U2B / SmartRAID V Millennium

  • Adaptec SmartRAID PM3757

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

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

  • BusLogic BT-445C

  • BusLogic BT-445S

  • BusLogic BT-540CF

  • BusLogic BT-542B

  • BusLogic BT-542B

  • BusLogic BT-542D

  • BusLogic BT-545C

  • BusLogic BT-545S

  • BusLogic/BusTek BT-640

  • BusLogic BT-742A

  • BusLogic BT-742A

  • BusLogic BT-747C

  • BusLogic BT-747D

  • BusLogic BT-747S

  • BusLogic BT-757C

  • BusLogic BT-757CD

  • BusLogic BT-757D

  • BusLogic BT-757S

  • BusLogic BT-946C

  • BusLogic BT-948

  • BusLogic BT-956C

  • BusLogic BT-956CD

  • BusLogic BT-958

  • BusLogic BT-958D

  • Storage Dimensions SDC3211B / SDC3211F

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

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

  • Compaq Smart Array 5300

  • Compaq Smart Array 532

  • Compaq Smart Array 5i

  • HP Smart Array 5312

  • HP Smart Array 6i

  • HP Smart Array 641

  • HP Smart Array 642

  • HP Smart Array 6400

  • HP Smart Array 6400 EM

  • HP Smart Array E200

  • HP Smart Array E200i

  • HP Smart Array P212

  • HP Smart Array P220i

  • HP Smart Array P222

  • HP Smart Array P400

  • HP Smart Array P400i

  • HP Smart Array P410

  • HP Smart Array P410i

  • HP Smart Array P411

  • HP Smart Array P420

  • HP Smart Array P420i

  • HP Smart Array P421

  • HP Smart Array P600

  • HP Smart Array P721m

  • 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] Controllers supported by the esp(4) driver include:

  • MELCO IFC-DP (PC-98)

  • Sun ESP family

  • Sun FAS family

  • Tekram DC390

  • Tekram DC390T

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

  • HighPoint's RocketRAID 271x series

  • HighPoint's RocketRAID 272x series

  • HighPoint's RocketRAID 274x series

  • HighPoint's RocketRAID 276x series

  • HighPoint's RocketRAID 278x series

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

  • HighPoint RocketRAID 4522

  • HighPoint RocketRAID 4520

  • HighPoint RocketRAID 4322

  • HighPoint RocketRAID 4321

  • HighPoint RocketRAID 4320

  • HighPoint RocketRAID 4311

  • HighPoint RocketRAID 4310

  • HighPoint RocketRAID 4211

  • HighPoint RocketRAID 4210

  • HighPoint RocketRAID 3560

  • HighPoint RocketRAID 3540

  • HighPoint RocketRAID 3530

  • HighPoint RocketRAID 3522

  • HighPoint RocketRAID 3521

  • HighPoint RocketRAID 3520

  • HighPoint RocketRAID 3511

  • HighPoint RocketRAID 3510

  • HighPoint RocketRAID 3410

  • HighPoint RocketRAID 3320

  • HighPoint RocketRAID 3220

  • HighPoint RocketRAID 3122

  • HighPoint RocketRAID 3120

  • HighPoint RocketRAID 3020

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

  • HighPoint's RocketRAID 182x series

[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

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

Cards supported by the isp(4) driver include:

  • ISP1000

  • ISP1020

  • ISP1040

  • Qlogic 1240

  • Qlogic 1020

  • Qlogic 1040

  • Qlogic 1080

  • Qlogic 1280

  • Qlogic 12160

  • Qlogic 210X

  • Qlogic 220X

  • Qlogic 2300

  • Qlogic 2312

  • Qlogic 234X

  • Qlogic 2322

  • Qlogic 200

  • Qlogic 2422

  • Qlogic 2432

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

  • LSI MegaRAID SAS 1078

  • LSI MegaRAID SAS 8408E

  • LSI MegaRAID SAS 8480E

  • LSI MegaRAID SAS 9260

  • Dell PERC5

  • Dell PERC6

  • IBM ServeRAID M5015 SAS/SATA

  • IBM ServeRAID-MR10i

  • Intel RAID Controller SROMBSAS18E

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

  • Mylex DAC960P

  • Mylex DAC960PD / DEC KZPSC (Fast Wide)

  • Mylex DAC960PDU

  • Mylex DAC960PL

  • Mylex DAC960PJ

  • Mylex DAC960PG

  • Mylex DAC960PU / DEC PZPAC (Ultra Wide)

  • Mylex AcceleRAID 150 (DAC960PRL)

  • Mylex AcceleRAID 250 (DAC960PTL1)

  • Mylex eXtremeRAID 1100 (DAC1164P)

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

All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is always advisable to upgrade to the most recent firmware available for the controller.

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

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

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

  • Mylex AcceleRAID 160

  • Mylex AcceleRAID 170

  • Mylex AcceleRAID 352

  • Mylex eXtremeRAID 2000

  • Mylex eXtremeRAID 3000

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

The mps(4) driver supports the following controllers:

  • LSI Logic SAS2004 (4 Port SAS)

  • LSI Logic SAS2008 (8 Port SAS)

  • LSI Logic SAS2108 (8 Port SAS)

  • LSI Logic SAS2116 (16 Port SAS)

  • LSI Logic SAS2208 (8 Port SAS)

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

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

  • LSI Logic AS1064, LSI Logic AS1068

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

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

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

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

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

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

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

  • Dell PowerEdge 1750 thru 2850

  • IBM eServer xSeries 335

These systems also contain Integrated Raid Mirroring and Integrated Raid Mirroring Enhanced which this driver also supports.

The SAS controller chips are also present on many new AMD/Opteron based systems, like the Sun 4100. Note that this controller can drive both SAS and SATA drives or a mix of them at the same time. The Integrated Raid Mirroring available for these controllers is poorly supported at best.

The Fibre Channel controller chipset are supported by a broad variety of speeds and systems. The Apple Fibre Channel HBA is in fact the FC949ES card.

This driver also supports target mode for Fibre Channel cards. This support may be enabled by setting the desired role of the core via the LSI Logic firmware utility that establishes what roles the card can take on - no separate compilation is required.

The mvs(4) driver supports the following controllers:

Gen-I (SATA 1.5Gbps):

  • 88SX5040

  • 88SX5041

  • 88SX5080

  • 88SX5081

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

  • 88SX6040

  • 88SX6041 (including Adaptec 1420SA)

  • 88SX6080

  • 88SX6081

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

  • 88SX6042

  • 88SX7042 (including Adaptec 1430SA)

  • 88F5182 SoC

  • 88F6281 SoC

  • MV78100 SoC

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

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

  • 53C810

  • 53C810A

  • 53C815

  • 53C820

  • 53C825A

  • 53C860

  • 53C875

  • 53C875J

  • 53C885

  • 53C895

  • 53C895A

  • 53C896

  • 53C1510D

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

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

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

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

  • I-O DATA PCSC-DV

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

  • Macnica Miracle SCSI-II mPS110

  • Media Intelligent MSC-110, MSC-200

  • NEC PC-9801N-J03R

  • New Media Corporation BASICS SCSI

  • Qlogic Fast SCSI

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

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

  • Alpha-Data AD-PCS201

  • I-O DATA CBSC16

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

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

3.2 Ethernet Interfaces

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

  • ASUS EeePC 701

  • ASUS EeePC 900

Other hardware may or may not work with this driver.

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

  • ASUS M2N8-VMX

  • ASUS M2V

  • ASUS M3A

  • ASUS P2-M2A590G

  • ASUS P5B-E

  • ASUS P5B-MX/WIFI-AP

  • ASUS P5B-VMSE

  • ASUS P5K

  • ASUS P5KC

  • ASUS P5KPL-C

  • ASUS P5KPL-VM

  • ASUS P5K-SE

  • ASUS P5K-V

  • ASUS P5L-MX

  • ASUS P5DL2-VM

  • ASUS P5L-VM 1394

  • ASUS G2S

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

  • Atheros AR8113 PCI Express Fast Ethernet controller

  • Atheros AR8114 PCI Express Fast Ethernet controller

  • Atheros AR8121 PCI Express Gigabit Ethernet controller

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

  • Abocom UFE1000, DSB650TX_NA

  • Accton USB320-EC, SpeedStream

  • ADMtek AN986, AN8511

  • Billionton USB100, USB100LP, USB100EL, USBE100

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

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

  • Elecom LD-USBL/TX

  • Elsa Microlink USB2Ethernet

  • HP hn210e

  • I-O Data USB ETTX

  • Kingston KNU101TX

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

  • MELCO LUA-TX, LUA2-TX

  • Netgear FA101

  • Planex UE-200TX

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

  • Siemens Speedstream

  • SmartBridges smartNIC

  • SMC 2202USB

  • SOHOware NUB100

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

AX88172:

  • AboCom UF200

  • Acer Communications EP1427X2

  • ASIX AX88172

  • ATen UC210T

  • Billionton SnapPort

  • Billionton USB2AR

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

  • Corega USB2_TX

  • D-Link DUBE100

  • Goodway GWUSB2E

  • JVC MP_PRX1

  • LinkSys USB200M

  • Netgear FA120

  • Sitecom LN-029

  • System TALKS Inc. SGC-X2UL

AX88178:

  • ASIX AX88178

  • Belkin F5D5055

  • Logitec LAN-GTJ/U2A

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

  • Planex Communications GU1000T

  • Sitecom Europe LN-028

AX88772:

  • ASIX AX88772

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

  • D-Link DUBE100B1

  • Planex UE-200TX-G

  • Planex UE-200TX-G2

AX88772A:

  • ASIX AX88772A

  • Cisco-Linksys USB200Mv2

AX88772B:

  • ASIX AX88772B

AX88760:

  • ASIX AX88760

[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 MMF (Cassini Kuheen) (part no. 501-5524)

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

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

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

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

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

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

  • Sharp Zaurus PDA

  • Terayon TJ-715 DOCSIS Cable Modem

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

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

  • Belkin F5U011/F5U111

  • CATC Netmate

  • CATC Netmate II

  • SmartBridges SmartLink

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

  • Chelsio 10GBase-CX4

  • Chelsio 10GBase-LR

  • Chelsio 10GBase-SR

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

  • DEC/Intel 21143

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

  • ALi/ULi M5261 and M5263

  • ASIX Electronics AX88140A and AX88141

  • Conexant LANfinity RS7112 (miniPCI)

  • Davicom DM9009, DM9100, DM9102 and DM9102A

  • Lite-On 82c168 and 82c169 PNIC

  • Lite-On/Macronix 82c115 PNIC II

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

  • Xircom X3201 (cardbus only)

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

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

  • Abocom FE2500

  • Accton EN1217 (98715A)

  • Accton EN2242 MiniPCI

  • Adico AE310TX (98715A)

  • Alfa Inc GFC2204 (ASIX AX88140A)

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

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

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

  • CNet Pro110B (ASIX AX88140A)

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

  • Compex RL100-TX (98713 or 98713A)

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

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

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

  • Hawking CB102 CardBus

  • IBM EtherJet Cardbus Adapter

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

  • Jaton XpressNet (Davicom DM9102)

  • Kingston KNE100TX (21143, MII)

  • Kingston KNE110TX (PNIC 82c169)

  • LinkSys LNE100TX (PNIC 82c168, 82c169)

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

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

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

  • Melco LGY-PCI-TXL

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

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

  • NDC SOHOware SFA110A (98713A)

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

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

  • Netgear FA511

  • PlaneX FNW-3602-T (ADMtek AN985)

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

  • SVEC PN102-TX (98713)

  • Xircom Cardbus Realport

  • Xircom Cardbus Ethernet 10/100

  • Xircom Cardbus Ethernet II 10/100

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

  • Adaptec ANA-6944/TX

  • Cogent EM100FX and EM440TX

  • Corega FastEther PCI-TX

  • D-Link DFE-500TX

  • DEC DE435, DEC DE450, and DEC DE500

  • ELECOM LD-PCI2T, LD-PCITS

  • I-O DATA LA2/T-PCI

  • SMC Etherpower 8432, 9332 and 9334

  • ZNYX ZX3xx

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

  • 3Com 3c503 Etherlink II

  • AR-P500 Ethernet

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

  • Accton EN2212/EN2216/UE2216

  • Allied Telesis CentreCOM LA100-PCM_V2

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

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

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

  • AmbiCom 10BaseT card

  • 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 Ethernet/Modem

  • TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card

  • TDK DFL5610WS Ethernet/Modem PC Card

  • Telecom Device SuperSocket RE450T

  • Toshiba LANCT00A PC Card

  • VIA VT86C926

  • Winbond W89C940

  • Winbond W89C940F

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

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

  • Mitsubishi LAN Adapter B8895

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

  • Intel PRO/1000 CT Network Connection (82547)

  • Intel PRO/1000 F Server Adapter (82543)

  • Intel PRO/1000 Gigabit Server Adapter (82542)

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

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

  • Intel PRO/1000 MF Server Adapter (82545)

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

  • Intel PRO/1000 MT Desktop Adapter (82540)

  • Intel PRO/1000 MT Desktop Adapter (82541)

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

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

  • Intel PRO/1000 MT Server Adapter (82545)

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

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

  • Intel PRO/1000 PF Server Adapter (82572)

  • Intel PRO/1000 PT Desktop Adapter (82572)

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

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

  • Intel PRO/1000 PT Server Adapter (82572)

  • Intel PRO/1000 T Desktop Adapter (82544)

  • Intel PRO/1000 T Server Adapter (82543)

  • Intel PRO/1000 XF Server Adapter (82544)

  • Intel PRO/1000 XT Server Adapter (82544)

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

  • 3Com 3C1 CF

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

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

  • 3Com 3C529, 3C529-TP MCA

  • 3Com 3C562/3C563 PCMCIA

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

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

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

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

  • 3Com 3CCFEM556B, 3CCFEM556BI PCMCIA

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

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

  • 3Com OfficeConnect 3CXSH572BT, 3CCSH572BT PCMCIA

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

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

  • Intel EtherExpress Pro/10 ISA

  • Intel EtherExpress Pro/10+ ISA

  • Olicom OC2220 Ethernet PC Card

  • Olicom OC2232 Ethernet/Modem PC Card

  • Silicom Ethernet LAN PC Card

  • Silicom EtherSerial LAN PC Card

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

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

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

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

  • Eagle Tech NE200T

  • Eiger Labs EPX-10BT

  • Fujitsu FMV-J182, FMV-J182A

  • Fujitsu MB86960A, MB86965A

  • Fujitsu MBH10303, MBH10302 PC Card Ethernet

  • Fujitsu Towa LA501 Ethernet

  • HITACHI HT-4840-11 PC Card Ethernet

  • NextCom J Link NC5310

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

  • RATOC REX-9880/9881/9882/9883

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

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

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

Adapters supported by the fxp(4) driver include:

  • Intel EtherExpress PRO/10

  • Intel InBusiness 10/100

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

  • Intel PRO/100+ Management Adapter

  • Intel PRO/100 VE Desktop Adapter

  • Intel PRO/100 VM Network Connection

  • Intel PRO/100 M Desktop Adapter

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

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

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

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

  • Many on-board network interfaces on Intel motherboards

Chips supported by the gem(4) driver include:

  • Apple GMAC

  • Sun ERI 10/100 Mbps Ethernet

  • Sun GEM Gigabit Ethernet

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

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

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

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

Cards supported by the hme(4) driver include:

  • Sun PCI SunSwift Adapter

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

  • Sun PCI Sun100BaseT Adapter 2.0

  • Sun SBus Sun100BaseT 2.0

  • Sun PCI Quad FastEthernet Controller

  • Sun SBus Quad FastEthernet Controller

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

  • 3COM 3C507

  • AT&T EN100

  • AT&T Starlan 10

  • AT&T Starlan Fiber

  • Intel EtherExpress 16

  • RACAL Interlan NI5210

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

  • Intel Gigabit ET Dual Port Server Adapter (82576)

  • Intel Gigabit VT Quad Port Server Adapter (82575)

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

  • Intel PRO/10GbE LR Server Adapter

  • Intel PRO/10GbE SR Server Adapter

The ixgbe(4) driver supports the following cards:

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

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

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

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

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

  • JMicron JMC250 PCI Express Gigabit Ethernet controller

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

  • JMicron JMC260 PCI Express Fast Ethernet controller

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

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

  • 3Com 3c19250

  • 3Com 3c460 HomeConnect Ethernet USB Adapter

  • ADS Technologies USB-10BT

  • AOX USB101

  • ATen UC10T

  • Abocom URE 450

  • Corega USB-T

  • D-Link DSB-650C

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

  • I/O Data USB ETT

  • Kawasaki DU-H3E

  • LinkSys USB10T

  • Netgear EA101

  • Peracom USB Ethernet Adapter

  • Psion Gold Port USB Ethernet adapter

  • SMC 2102USB, 2104USB

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

  • SMC TigerCard 1000 (SMC9462SX)

  • D-Link DGE-500SX

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

  • D-Link 550SX Gigabit Ethernet

  • D-Link 560SX Gigabit Ethernet

  • D-Link 560T Gigabit Ethernet

  • Marvell Yukon 88E8021CU Gigabit Ethernet

  • Marvell Yukon 88E8021 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8022CU Gigabit Ethernet

  • Marvell Yukon 88E8022 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8061CU Gigabit Ethernet

  • Marvell Yukon 88E8061 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8062CU Gigabit Ethernet

  • Marvell Yukon 88E8062 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8035 Fast Ethernet

  • Marvell Yukon 88E8036 Fast Ethernet

  • Marvell Yukon 88E8038 Fast Ethernet

  • Marvell Yukon 88E8039 Fast Ethernet

  • Marvell Yukon 88E8040 Fast Ethernet

  • Marvell Yukon 88E8040T Fast Ethernet

  • Marvell Yukon 88E8042 Fast Ethernet

  • Marvell Yukon 88E8048 Fast Ethernet

  • Marvell Yukon 88E8050 Gigabit Ethernet

  • Marvell Yukon 88E8052 Gigabit Ethernet

  • Marvell Yukon 88E8053 Gigabit Ethernet

  • Marvell Yukon 88E8055 Gigabit Ethernet

  • Marvell Yukon 88E8056 Gigabit Ethernet

  • Marvell Yukon 88E8057 Gigabit Ethernet

  • Marvell Yukon 88E8058 Gigabit Ethernet

  • Marvell Yukon 88E8059 Gigabit Ethernet

  • Marvell Yukon 88E8070 Gigabit Ethernet

  • Marvell Yukon 88E8071 Gigabit Ethernet

  • Marvell Yukon 88E8072 Gigabit Ethernet

  • Marvell Yukon 88E8075 Gigabit Ethernet

  • SysKonnect SK-9Sxx Gigabit Ethernet

  • SysKonnect SK-9Exx Gigabit Ethernet

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

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

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

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

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

  • Myson MTD800 PCI Fast Ethernet chip

  • Myson MTD803 PCI Fast Ethernet chip

  • Myson MTD89X PCI Gigabit Ethernet chip

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

  • NVIDIA nForce MCP Networking Adapter

  • NVIDIA nForce MCP04 Networking Adapter

  • NVIDIA nForce 430 MCP12 Networking Adapter

  • NVIDIA nForce 430 MCP13 Networking Adapter

  • NVIDIA nForce MCP51 Networking Adapter

  • NVIDIA nForce MCP55 Networking Adapter

  • NVIDIA nForce MCP61 Networking Adapter

  • NVIDIA nForce MCP65 Networking Adapter

  • NVIDIA nForce MCP67 Networking Adapter

  • NVIDIA nForce MCP73 Networking Adapter

  • NVIDIA nForce MCP77 Networking Adapter

  • NVIDIA nForce MCP79 Networking Adapter

  • NVIDIA nForce2 MCP2 Networking Adapter

  • NVIDIA nForce2 400 MCP4 Networking Adapter

  • NVIDIA nForce2 400 MCP5 Networking Adapter

  • NVIDIA nForce3 MCP3 Networking Adapter

  • NVIDIA nForce3 250 MCP6 Networking Adapter

  • NVIDIA nForce3 MCP7 Networking Adapter

  • NVIDIA nForce4 CK804 MCP8 Networking Adapter

  • NVIDIA nForce4 CK804 MCP9 Networking Adapter

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

  • Addtron AEG320T

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

  • Asante FriendlyNet GigaNIX 1000TA and 1000TPC

  • D-Link DGE-500T

  • Linksys EG1032, revision 1

  • Netgear GA621

  • Netgear GA622T

  • SMC EZ Card 1000 (SMC9462TX)

  • Surecom Technology EP-320G-TX

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

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

  • nForce

  • nForce2

  • nForce3

  • nForce4

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

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

  • Emulex BladeEngine 2

  • Emulex BladeEngine 3

  • Emulex Lancer

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

  • AMD Am79C971 PCnet-FAST

  • AMD Am79C972 PCnet-FAST+

  • AMD Am79C973/Am79C975 PCnet-FAST III

  • AMD Am79C976 PCnet-PRO

  • AMD Am79C978 PCnet-Home

  • Allied-Telesis LA-PCI

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

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

  • Compaq Evo N1015v Integrated Ethernet (8139C+)

  • Corega CG-LAPCIGT Gigabit Ethernet (8169S)

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

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

  • LevelOne GNC-0105T (8169S)

  • LinkSys EG1032 (32-bit PCI)

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

  • USRobotics USR997902 Gigabit Ethernet (8169S)

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

Adapters supported by the rl(4) driver include:

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

  • Allied Telesyn AT2550

  • Allied Telesyn AT2500TX

  • Belkin F5D5000

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

  • Compaq HNE-300

  • CompUSA no-name 10/100 PCI Ethernet NIC

  • Corega FEther CB-TXD

  • Corega FEtherII CB-TXD

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

  • D-Link DFE-528TX

  • D-Link DFE-530TX+

  • D-Link DFE-538TX

  • D-Link DFE-690TXD

  • Edimax EP-4103DL CardBus

  • Encore ENL832-TX 10/100 M PCI

  • Farallon NetLINE 10/100 PCI

  • Genius GF100TXR

  • GigaFast Ethernet EE100-AXP

  • KTX-9130TX 10/100 Fast Ethernet

  • LevelOne FPC-0106TX

  • Longshine LCS-8038TX-R

  • NDC Communications NE100TX-E

  • Netronix Inc. EA-1210 NetEther 10/100

  • Nortel Networks 10/100BaseTX

  • OvisLink LEF-8129TX

  • OvisLink LEF-8139TX

  • Peppercon AG ROL-F

  • Planex FNW-3603-TX

  • Planex FNW-3800-TX

  • SMC EZ Card 10/100 PCI 1211-TX

  • SOHO (PRAGMATIC) UE-1211C

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

  • Buffalo (Melco Inc.) LUA-KTX

  • Green House GH-USB100B

  • LinkSys USB100M

  • Billionton 10/100 FastEthernet USBKR2

Adapters supported by the sf(4) driver include:

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

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

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

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

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

[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 VT6120, VT6122, VT6130 and VT6132 based Gigabit Ethernet adapters including:

  • VIA Networking LAN-on-motherboard Gigabit Ethernet

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

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

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

  • AOpen/Acer ALN-320

  • D-Link DFE520-TX

  • D-Link DFE530-TX

  • Hawking Technologies PN102TX

  • Soekris Engineering net5501

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

3.3 FDDI Interfaces

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

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

3.4 ATM Interfaces

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

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

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

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

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

3.5 Wireless Network Interfaces

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

[i386,pc98,amd64,sparc64] The ath(4) driver supports all Atheros Cardbus and PCI cards, except those that are based on the AR5005VL chipset.

The 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/PCIe/CardBus wireless adapters based on Ralink Technology chipsets, including:

  • A-Link WL54H

  • A-Link WL54PC

  • AirLink101 AWLC5025

  • AirLink101 AWLH5025

  • Amigo AWI-914W

  • Amigo AWI-922W

  • Amigo AWI-926W

  • AMIT WL531C

  • AMIT WL531P

  • AOpen AOI-831

  • ASUS WL-107G

  • ASUS WL-130g

  • Atlantis Land A02-PCI-W54

  • Atlantis Land A02-PCM-W54

  • Belkin F5D7000 v3

  • Belkin F5D7010 v2

  • Billionton MIWLGRL

  • Canyon CN-WF511

  • Canyon CN-WF513

  • CC&C WL-2102

  • CNet CWC-854

  • CNet CWP-854

  • Compex WL54G

  • Compex WLP54G

  • Conceptronic C54RC

  • Conceptronic C54Ri

  • Digitus DN-7001G-RA

  • Digitus DN-7006G-RA

  • E-Tech WGPC02

  • E-Tech WGPI02

  • Edimax EW-7108PCg

  • Edimax EW-7128g

  • Eminent EM3036

  • Eminent EM3037

  • Encore ENLWI-G-RLAM

  • Encore ENPWI-G-RLAM

  • Fiberline WL-400P

  • Fibreline WL-400X

  • Gigabyte GN-WI01GS

  • Gigabyte GN-WIKG

  • Gigabyte GN-WMKG

  • Gigabyte GN-WP01GS

  • Gigabyte GN-WPKG

  • Hawking HWC54GR

  • Hawking HWP54GR

  • iNexQ CR054g-009 (R03)

  • JAHT WN-4054P

  • JAHT WN-4054PCI

  • LevelOne WNC-0301 v2

  • LevelOne WPC-0301 v2

  • Linksys WMP54G v4

  • Micronet SP906GK

  • Micronet SP908GK V3

  • Minitar MN54GCB-R

  • Minitar MN54GPC-R

  • MSI CB54G2

  • MSI MP54G2

  • MSI PC54G2

  • OvisLink EVO-W54PCI

  • PheeNet HWL-PCIG/RA

  • Pro-Nets CB80211G

  • Pro-Nets PC80211G

  • Repotec RP-WB7108

  • Repotec RP-WP0854

  • SATech SN-54C

  • SATech SN-54P

  • Sitecom WL-112

  • Sitecom WL-115

  • SMC SMCWCB-GM

  • SMC SMCWPCI-GM

  • SparkLAN WL-685R

  • Surecom EP-9321-g

  • Surecom EP-9321-g1

  • Surecom EP-9428-g

  • Sweex LC500050

  • Sweex LC700030

  • TekComm NE-9321-g

  • TekComm NE-9428-g

  • Unex CR054g-R02

  • Unex MR054g-R02

  • Zinwell ZWX-G160

  • Zinwell ZWX-G360

  • Zinwell ZWX-G361

  • Zonet ZEW1500

  • Zonet ZEW1600

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

  • 3Com Aolynk WUB320g

  • Abocom WUG2700

  • Airlink101 AWLL5025

  • ASUS WL-167g ver 2

  • Belkin F5D7050 ver 3

  • Belkin F5D9050 ver 3

  • Buffalo WLI-U2-SG54HP

  • Buffalo WLI-U2-SG54HG

  • Buffalo WLI-U2-G54HP

  • Buffalo WLI-UC-G

  • CNet CWD-854 ver F

  • Conceptronic C54RU ver 2

  • Corega CG-WLUSB2GO

  • D-Link DWA-110

  • D-Link DWA-111

  • D-Link DWL-G122 rev C1

  • D-Link WUA-1340

  • Digitus DN-7003GR

  • Edimax EW-7318USG

  • Gigabyte GN-WB01GS

  • Gigabyte GN-WI05GS

  • Hawking HWUG1

  • Hawking HWU54DM

  • Hercules HWGUSB2-54-LB

  • Hercules HWGUSB2-54V2-AP

  • LevelOne WNC-0301USB v3

  • Linksys WUSB54G rev C

  • Linksys WUSB54GR

  • Planex GW-US54HP

  • Planex GW-US54Mini2

  • Planex GW-USMM

  • Senao NUB-3701

  • Sitecom WL-113 ver 2

  • Sitecom WL-172

  • Sweex LW053

  • TP-LINK TL-WN321G

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:

  • Belkin F5D7050E

  • Linksys WUSB54GCv2

  • Netgear WG111v2

  • Netgear WG111v3

  • Safehome WLG-1500SMA5

  • Shuttle XPC Accessory PN20

  • Sitecom WL168v1

  • Sitecom WL168v4

  • SureCom EP-9001-g(2A)

  • TRENDnet TEW-424UB V3.xR

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

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

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

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

  • 3COM 3CRUSB10075

  • Acer WLAN-G-US1

  • Airlink+ AWLL3025

  • Airlink 101 AWLL3026

  • AOpen 802.11g WL54

  • Asus A9T integrated wireless

  • Asus WL-159g

  • Belkin F5D7050 v.4000

  • Billion BiPAC 3011G

  • Buffalo WLI-U2-KG54L

  • CC&C WL-2203B

  • DrayTek Vigor 550

  • Edimax EW-7317UG

  • Edimax EW-7317LDG

  • Fiberline Networks WL-43OU

  • iNexQ UR055g

  • Linksys WUSBF54G

  • Longshine LCS-8131G3

  • MSI US54SE

  • MyTek MWU-201 USB adapter

  • Philips SNU5600

  • Planet WL-U356

  • Planex GW-US54GZ

  • Planex GW-US54GZL

  • Planex GW-US54Mini

  • Safecom SWMULZ-5400

  • Sagem XG 760A

  • Sagem XG 76NA

  • Sandberg Wireless G54 USB

  • Sitecom WL-113

  • SMC SMCWUSB-G

  • Sweex wireless USB 54 Mbps

  • Tekram/Siemens USB adapter

  • Telegent TG54USB

  • Trendnet TEW-424UB rev A

  • Trendnet TEW-429UB

  • TwinMOS G240

  • Unicorn WL-54G

  • US Robotics 5423

  • X-Micro XWL-11GUZX

  • Yakumo QuickWLAN USB

  • Zonet ZEW2501

  • ZyXEL ZyAIR G-220

3.6 Miscellaneous Networks

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

  • Cronyx Tau-PCI/32

  • Cronyx Tau-PCI/32-Lite

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

  • Cronyx Sigma-22, Sigma-24

  • Cronyx Sigma-100

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

  • Cronyx Sigma-500

  • Cronyx Sigma-703

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

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

  • Cronyx Tau-PCI

  • Cronyx Tau-PCI/R

  • Cronyx Tau-PCI-L

  • Cronyx Tau-PCI-L/R

  • Cronyx Tau-PCI-E1

  • Cronyx Tau-PCI-G703

  • Cronyx Tau-PCI-2E1

  • Cronyx Tau-PCI-4E1

  • Cronyx Tau-PCI-E3

  • Cronyx Tau-PCI-T3

  • Cronyx Tau-PCI-STS1

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

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

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

  • Cronyx Tau/E1 (fractional E1)

  • Cronyx Tau/G703 (unframed E1)

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

  • SMC90c26

  • SMC90c56

  • SMC90c66 in '56 compatibility mode.

3.7 Serial Interfaces

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

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

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

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

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

  • SAB82532: Siemens SAB 82532 based serial communications controllers.

  • Z8530: Zilog 8530 based serial communications controllers.

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

  • ARNET 8 port serial card using shared IRQ

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

[i386] Boca multi-port serial cards

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

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

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

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

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

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

[i386] STB 4 port card using shared IRQ

[i386] DigiBoard intelligent serial cards (digi driver)

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

  • [amd64, i386] Actiontech 56K PCI

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

  • [amd64, i386] Comtrol RocketPort 550

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

  • [ia64] Diva Serial (GSP) Multiport UART

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

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

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

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

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

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

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

  • [amd64, i386] Oxford Semiconductor OX16PCI954 PCI UART

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

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

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

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

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

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

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

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

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

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

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

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

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

  • PC-9801 on-board

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

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

  • COM2 (flags 0x01000000)

  • COM3 (flags 0x02000000)

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

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

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

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

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

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

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

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

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

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

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

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

3.8 Sound Devices

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

  • Analog Devices AD1816

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

  • Avance Logic ALS4000

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

  • ATI IXP 200

  • ATI IXP 300

  • ATI IXP 400

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

  • CS4231 on SBus based UltraSPARC

  • CS4231 on PCI/EBus based UltraSPARC

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

  • CMedia CMI8338A

  • CMedia CMI8338B

  • CMedia CMI8738

  • CMedia CMI8738B

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

  • Crystal Semiconductor CS4281

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

  • Crystal Semiconductor CS4280

  • Crystal Semiconductor CS4610

  • Crystal Semiconductor CS4611

  • Crystal Semiconductor CS4614

  • Crystal Semiconductor CS4615

  • Crystal Semiconductor CS4622

  • Crystal Semiconductor CS4624

  • Crystal Semiconductor CS4630

  • Genius Soundmaker 128 Value

  • Hercules Game Theatre XP

  • Turtle Beach Santa Cruz

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

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

  • Yamaha DS-1

  • Yamaha DS-1E

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

  • Creative SoundBlaster Live! (EMU10K1 Chipset)

  • Creative SoundBlaster Audigy (EMU10K2 Chipset)

  • Creative SoundBlaster Audigy 2 (EMU10K2 Chipset)

  • Creative SoundBlaster Audigy 2 (EMU10K3 Chipset)

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

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

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

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

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

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

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

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

  • All other Creative sound cards with -DAT chipsets.

  • All Creative X-Fi series sound cards.

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

  • M-Audio Audiophile 2496

  • M-Audio Delta Dio 2496

  • Terratec DMX 6fire

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

  • Audiotrak Prodigy 7.1

  • Audiotrak Prodigy 7.1 LT

  • Audiotrak Prodigy 7.1 XT

  • Audiotrak Prodigy HD2

  • ESI Juli@

  • M-Audio Audiophile 192

  • M-Audio Revolution 5.1

  • M-Audio Revolution 7.1

  • Terratec Aureon 5.1 Sky

  • Terratec Aureon 7.1 Space

  • Terratec Aureon 7.1 Universe

  • Terratec PHASE 22

  • Terratec PHASE 28

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

  • Creative CT5880-A

  • Creative CT5880-C

  • Creative CT5880-D

  • Creative CT5880-E

  • Creative SB AudioPCI CT4730

  • Ensoniq AudioPCI ES1370

  • Ensoniq AudioPCI ES1371-A

  • Ensoniq AudioPCI ES1371-B

  • Ensoniq AudioPCI ES1373-A

  • Ensoniq AudioPCI ES1373-B

  • Ensoniq AudioPCI ES1373-8

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

  • Ensoniq ESS ISA PnP/non-PnP

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

  • Forte Media FM801

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

  • Gravis UltraSound MAX

  • Gravis UltraSound PnP

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

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

[i386,amd64] The snd_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

3.9 Camera and Video Capture Devices

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

  • AOpen VA1000

  • AVerMedia AVerTV Studio

  • AVerMedia TF/FM-98

  • ATI TV Wonder VE

  • Hauppauge WinCast/TV

  • Hauppauge WinTV-Go-FM

  • Hauppauge WinTV-pci

  • Hauppauge WinTV-radio

  • Intel Smart Video Recorder III

  • KWORLD PCI TV Tuner

  • Miro PC TV

  • Pinnacle PCTV Pro

  • Pinnacle PCTV Rave

  • PixelView PlayTV PAK

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

  • SIGMA TV II

  • STB TV PCI Television Tuner

  • Super TV Tuner

  • TerraTec TValue

  • V-Stream XPERT TV-PVR 878

  • Video Highway XTreme

  • VideoLogic Captivator PCI

[i386] Connectix QuickCam

3.10 USB Devices

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

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

Note: [amd64, i386, ia64, pc98] USB Bluetooth adapters can be found in Bluetooth section.

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

  • AcerLabs M5237 (Aladdin-V)

  • AMD-756

  • OPTi 82C861 (FireLink)

  • NEC uPD 9210

  • CMD Tech 670 (USB0670)

  • CMD Tech 673 (USB0673)

  • NVIDIA nForce3

  • Sun PCIO-2 (RIO USB)

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

  • Intel 82371AB/EB (PIIX4)

  • Intel 82371SB (PIIX3)

  • VIA 83C572

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

[amd64, i386, ia64, pc98] Hubs

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

[amd64, i386, pc98] Miscellaneous

  • Assist Computer Systems PC Camera C-M1

  • ActiveWire I/O Board

  • Creative Technology Video Blaster WebCam Plus

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

  • Mirunet AlphaCam Plus

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

  • Diamond MultiMedia Rio 500

  • Diamond MultiMedia Rio 600

  • Diamond MultiMedia Rio 800

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

  • 3Com 5605

  • Curitel PC5740 Wireless Modem

  • Kyocera AH-K3001V Mobile Phone(WILLCOM)

  • Kyocera WX320K Mobile Phone(WILLCOM)

  • Metricom Ricochet GS USB wireless modem

  • Sierra MC5720 Wireless Modem

  • Yamaha Broadband Wireless Router RTW65b

  • ELSA MicroLink 56k USB modem

  • Sony Ericsson W810i phone

[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 devices and adapters:

  • ADLINK ND-6530 USB-Serial Adapter

  • Alcatel One Touch 535/735 Phone

  • Alcor AU9720 USB-RS232 Serial Adapter

  • AlDiga AL-11U Modem

  • Alltronix ACM003U00 Modem

  • Anchor Serial adapter

  • ATEN UC-232A

  • BAFO BF-800 and BF-810

  • Belkin F5U257

  • BenQ S81 Phone

  • Corega CG-USBRS232R Serial Adapter

  • Cressi Edy (Seiko) Diving Computer

  • ELECOM UC-SGT Serial Adapter

  • HAL Corporation Crossam2+USB IR commander

  • Hama USB RS-232 Serial Adapter

  • Hamlet exagerate XURS232

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

  • IOGEAR UC-232A

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

  • iTegno WM1080A GSM/GFPRS Modem

  • iTegno WM2080A CDMA Modem

  • Leadtek 9531 GPS

  • Micromax 610U Modem

  • Microsoft Palm 700WX

  • Mobile Action MA-620 Infrared Adapter

  • Motorola Cables

  • Nokia CA-42 Cable

  • OTI DKU-5 cable

  • Panasonic TY-TP50P6-S flat screen

  • PLX CA-42 Phone Cable

  • PLANEX USB-RS232 URS-03

  • Prolific Generic USB-Serial Adapters

  • Prolific Pharos USB-Serial Adapter

  • RATOC REX-USB60

  • Radio Shack USB Serial Cable

  • Sagem USB-Serial Adapter

  • Samsung I330 Phone Cradle

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

  • Sanwa KB-USB2 Multimeter cable

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

  • Sitecom USB-Serial Adapter

  • SMART Technologies USB-Serial Adapter

  • Sony QN3 Phone Cable

  • Sony Ericsson Datapilot

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

  • SOURCENEXT KeikaiDenwa 8 (with and without charger)

  • Speed Dragon USB-Serial Cable

  • Syntech CPT-8001C Barcode Scanner

  • TDK UHA6400 and UPA9664 USB-PHS Adapters

  • TRENDnet USB to Serial Converter (TU-S9)

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

  • UIC HCR331 Magnetic Stripe Card Reader

  • UIC MSR206 Magnetic Stripe Card Reader

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

  • YC-Cable USB-Serial Adapter

  • Zeagle N2iTion3 Diving Computer

The umct(4) driver supports the following adapters:

  • Belkin F5U109

  • Belkin F5U409

  • D-Link DU-H3SP USB BAY Hub

  • Magic Control Technology USB-232

  • Sitecom USB-232

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

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

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

  • FujiFilm Zip USB Drive ZDR100 USB A

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

  • Huawei Mobile (SD slot)

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

  • IBM 256MB USB Drive (MSYSTEM DiskOnKey2)

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

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

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

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

  • Iomega USB Zip 100/250 drive

  • Iomega Zip750 USB2.0 drive

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

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

  • LaCie P3 HardDrive USB 200GB

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

  • Logitec Mobile USB Memory LMC-256UD

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

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

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

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

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

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

  • MELCO USB2.0 MO Drive MO-CH640U2

  • Matshita CF-VFDU03 floppy drive

  • Merlin SM300 MP3/WMA Player (256Mb)

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

  • Motorola E398 Mobile Phone (TransFlash memory card)

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

  • PNY Attache Flash Drive

  • Panasonic ("Matshita FDD CF-VFDU03")

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

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

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

  • Panasonic floppy drive

  • Qware BeatZkey! Pro

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

  • SanDisk SDDR-31 (Compact Flash)

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

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

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

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

  • Time DPA20B MP3 Player (1Gb)

  • Trek Thumbdrive 8MB

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

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

Among the supported digital cameras are:

  • Asahi Optical (PENTAX) Optio 230 & 330

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

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

  • Aceeca Mez1000 RDA

  • Handspring Treo

  • Handspring Treo 600

  • Handspring Visor

  • Palm I705

  • Palm M125

  • Palm M130

  • Palm M500

  • Palm M505

  • Palm M515

  • Palm Tungsten T

  • Palm Tungsten Z

  • Palm Zire

  • Palm Zire 31

  • Sony Clie 4.0

  • Sony Clie 4.1

  • Sony Clie 5.0

  • Sony Clie PEG-S500C

  • Sony Clie NX60

  • Sony Clie S360

  • Sony Clie TJ37

3.11 IEEE 1394 (Firewire) Devices

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

  • Adaptec AHA-894x/AIC-5800

  • Apple Pangea

  • Apple UniNorth

  • Intel 82372FB

  • IOGEAR GUF320

  • Lucent / Agere FW322/323

  • NEC uPD72861

  • NEC uPD72870

  • NEC uPD72871/2

  • NEC uPD72873

  • NEC uPD72874

  • National Semiconductor CS4210

  • Ricoh R5C551

  • Ricoh R5C552

  • Sony CX3022

  • Sony i.LINK (CXD3222)

  • Sun PCIO-2 (RIO 1394)

  • Texas Instruments PCI4410A

  • Texas Instruments PCI4450

  • Texas Instruments PCI4451

  • Texas Instruments TSB12LV22

  • Texas Instruments TSB12LV23

  • Texas Instruments TSB12LV26

  • Texas Instruments TSB43AA22

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

  • Texas Instruments TSB43AB22/A

  • Texas Instruments TSB43AB23

  • Texas Instruments TSB82AA2

  • VIA Fire II (VT6306)

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

3.12 Bluetooth Devices

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

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

  • 3Com 3CREB96

  • AIPTEK BR0R02

  • EPoX BT-DG02

  • Mitsumi Bluetooth USB adapter

  • MSI MS-6967

  • TDK Bluetooth USB adapter

  • Broadcom Bluetooth USB adapter

3.13 Cryptographic Accelerators

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

  • Invertex AEON

  • Hifn 7751

  • PowerCrypt

  • XL-Crypt

  • NetSec 7751

  • Soekris Engineering vpn1201 and vpn1211

  • Soekris Engineering vpn1401 and vpn1411

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

  • SafeNet 1141

  • SafeNet 1741

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

  • Bluesteel 5501

  • Bluesteel 5601

  • Broadcom BCM5801

  • Broadcom BCM5802

  • Broadcom BCM5805

  • Broadcom BCM5820

  • Broadcom BCM5821

  • Broadcom BCM5822

  • Broadcom BCM5823

  • Broadcom BCM5825

3.14 Miscellaneous

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

  • MELCO IGM-PCM56K/IGM-PCM56KH

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

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

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

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

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

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

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

  • [pc98] Standard keyboards

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

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

  • [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 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/website/content/en/releases/8.4R/installation.adoc b/website/content/en/releases/8.4R/installation.adoc index a609189d45..8c1eb0a24e 100644 --- a/website/content/en/releases/8.4R/installation.adoc +++ b/website/content/en/releases/8.4R/installation.adoc @@ -1,168 +1,168 @@ FreeBSD 8.4-RELEASE Installation Instructions

FreeBSD 8.4-RELEASE Installation Instructions

The FreeBSD Project

Copyright © 2013 The FreeBSD Documentation Project

$FreeBSD: releng/8.4/release/doc/en_US.ISO8859-1/installation/article.xml 249128 2013-04-05 04:08:03Z 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. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

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

+by the “™” or the “®” symbol.

This article gives some brief instructions on installing FreeBSD 8.4-RELEASE and upgrading the systems running earlier releases.

1 Installing FreeBSD

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

2 Upgrading FreeBSD

2.1 Upgrading from Source

The procedure for doing a source code based update is described in http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/synching.html and http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook//makeworld.html.

The branch tag to use for updating the source is RELENG_8_4 for CVS. For SVN use releng/8.4.

2.2 Upgrading Using “FreeBSD Update”

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[01234]-RELEASE, 8.[0123]-RELEASE, 8.4-BETA1, or 8.4-RC[12] can upgrade as follows:

 # freebsd-update upgrade -r 8.4-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

 # freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

 # shutdown -r now

After rebooting, freebsd-update(8) needs to be run again to install the new userland components:

 # freebsd-update install

At this point, users of systems being upgraded from FreeBSD 7.4-RELEASE or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries.

After updating installed third-party applications (and again, only if freebsd-update(8) printed a message indicating that this was necessary), run freebsd-update(8) again so that it can delete the old (no longer used) system libraries:

 # freebsd-update install

Finally, reboot into 8.4-RELEASE

 # shutdown -r now

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/website/content/en/releases/8.4R/readme.adoc b/website/content/en/releases/8.4R/readme.adoc index db527552d7..f68a5b8325 100644 --- a/website/content/en/releases/8.4R/readme.adoc +++ b/website/content/en/releases/8.4R/readme.adoc @@ -1,411 +1,411 @@ FreeBSD 8.4-RELEASE README

FreeBSD 8.4-RELEASE README

The FreeBSD Project

Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 The FreeBSD Documentation Project

$FreeBSD: releng/8.4/release/doc/en_US.ISO8859-1/readme/article.xml 241718 2012-10-19 03:01:25Z gjb $

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. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

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

+by the “™” or the “®” symbol.

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

1 Introduction

This distribution is a release of FreeBSD 8.4-RELEASE, the latest point along the 8.4-STABLE branch.

1.1 About FreeBSD

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

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

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

1.2 Target Audience

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

2 Obtaining FreeBSD

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

2.1 CDROM and DVD

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

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

2.2 FTP

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

Lists of locations that mirror FreeBSD can be found in the FTP Sites section of the Handbook, 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 for more details on becoming an official mirror site. You can also find useful information for mirror sites at the Mirroring FreeBSD article.

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

3 Contacting the FreeBSD Project

3.1 Email and Mailing Lists

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

If you're tracking the 8.4-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.

3.2 Submitting Problem Reports

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

The preferred method to submit bug reports from a machine with Internet 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.

4 Further Reading

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

4.1 Release Documentation

A number of other files provide more specific information about this 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.4-RELEASE compared to the previous release (FreeBSD 8.3-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).

4.2 Manual Pages

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

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

4.3 Books and Articles

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

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

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

5 Acknowledgments

FreeBSD represents the cumulative work of many hundreds, if not thousands, of individuals from around the world who have worked countless hours to bring about this 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 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/website/content/en/releases/8.4R/relnotes-detailed.adoc b/website/content/en/releases/8.4R/relnotes-detailed.adoc index b60ecda268..91eed38ebe 100644 --- a/website/content/en/releases/8.4R/relnotes-detailed.adoc +++ b/website/content/en/releases/8.4R/relnotes-detailed.adoc @@ -1,2382 +1,2382 @@ FreeBSD 8.4-RELEASE Release Notes

FreeBSD 8.4-RELEASE Release Notes

The FreeBSD Project

Copyright © 2013 The FreeBSD Documentation Project

$FreeBSD: releng/8.4/release/doc/en_US.ISO8859-1/relnotes/article.xml 251258 2013-06-02 16:21:02Z hrs $

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. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

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

+by the “™” or the “®” symbol.

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

Table of Contents
1 Introduction
2 What's New
2.1 Security Advisories
2.2 Kernel Changes
2.2.1 Boot Loader Changes
2.2.2 Hardware Support
2.2.3 Network Protocols
2.2.4 Disks and Storage
2.2.5 File Systems
2.3 Userland Changes
2.3.1 /etc/rc.d Scripts
2.4 Contributed Software
2.5 Ports/Packages Collection Infrastructure
2.6 Release Engineering and Integration
3 Upgrading from previous releases of FreeBSD

1 Introduction

This document contains the release notes for FreeBSD 8.4-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.4-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.4-RELEASE can be found on the FreeBSD Web site.

2 What's New

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

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

2.1 Security Advisories

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-12:01.openssl 03 May 2012

OpenSSL multiple vulnerabilities
SA-12:02.crypt 30 May 2012

Incorrect crypt() hashing
SA-12:03.bind 12 June 2012

Incorrect handling of zero-length RDATA fields in named(8)
SA-12:04.sysret 12 June 2012

Privilege escalation when returning from kernel
SA-12:05.bind 06 August 2012

named(8) DNSSEC validation Denial of Service
SA-12:06.bind 22 November 2012

Multiple Denial of Service vulnerabilities with named(8)
SA-12:07.hostapd 22 November 2012

Insufficient message length validation for EAP-TLS messages
SA-12:08.linux 22 November 2012

Linux compatibility layer input validation error
SA-13:02.libc 19 February 2013

glob(3) related resource exhaustion
SA-13:03.openssl 02 April 2013

OpenSSL multiple vulnerabilities
SA-13:04.bind 02 April 2013

BIND remote denial of service
SA-13:05.nfsserver 29 April 2013

Insufficient input validation in the NFS server

2.2 Kernel Changes

A bug which could cause a kernel thread to have a wrong CPU affinity configuration has been fixed.[r232757]

loader(8) environment variables comconsole_port and comconsole_pcidev have been added. The former allows to set the base address of the serial console I/O port. The later takes the string of the format bus:device:function:[bar] as a value and uses the serial port attached as PCI device at the specified location for console. Both variants pass hw.uart.console variable to the uart(4) driver to properly hand-over the kernel console.[r245847]

A new loader(8) tunable hw.broken_txfifo has been added to enable workaround for old version of QEMU and Xen which have a buggy emulated UART.[r246626]

The F_DUPFD_CLOEXEC command for fcntl(2) has been implemented. This is standardized in IEEE Std 1003.1-2008 (POSIX, Single UNIX Specification Version 4). In addition to this, F_DUP2FD_CLOEXEC has been implemented in analogy with F_DUP2FD.[r239860, r239861]

The filemon(4) pseudo-device has been added. This allows a process to collect file operations data of its children.[r240707]

A bug in VIMAGE jail(8) which could make the network subsystem run on an wrong vnet context has been fixed.[r233584]

debug.kdb.break_to_debugger and debug.kdb.alt_break_to_debugger have been added as sysctl(8) variables and loader tunables. These are disabled by default and BREAK_TO_DEBUGGER and ALT_BREAK_TO_DEBUGGER kernel options now set them enabled. These changes allow GENERIC kernel to support break-to-debugger capability.[r235121]

The FreeBSD sched_ule(4) scheduler has been improved in CPU selection on systems which support SMT (Symmetric MultiThreading, also known as HyperThreading on Intel CPUs). It now prefers a logical CPU when the the other logical CPUs on the physical one are idle, and an idle CPU in an SMT CPU group always has lower priority. The CPU load calculation for load balancing has also been improved to consider highest and lowest CPU load in comparison to differentiate load in CPU groups. This change gives 10-15% performance improvement in SMT CPUs such as Core i7.[r241246]

The shm_map(9) and shm_unmap(9) functions have been added to allow in-kernel code to map portions of shared memory objects created by shm_open(2) into the kernel's address space.[r236684]

A new sysctl(8) variable kern.stop_scheduler_on_panic has been added. When set to 1, only one thread runs uninterruptedly after a system panic and the other CPUs are stopped. The default value is 0.[r235502]

The loader(8) tunables kern.maxtsiz, kern.dfldsiz, kern.maxdsiz, kern.dflssiz, kern.maxssiz, and kern.sgrowsiz are now writable sysctl(8) variables.[r240502]

A bug that changes to a mapped file with the mmap(2) system call were not flushed properly under certain circumstances has been fixed. If a process has an NFS-backed file and adds changes to it, normally the changes are written into the backing store automatically. However, the NFS client recognized the modified parts are written successfully even when the write operation was failed for some reason such as permission denied.[r233765, r234094, r236150]

2.2.1 Boot Loader Changes

[amd64, i386, pc98] A bug in FreeBSD boot block has been fixed. A pathname of the third stage loader (or kernel) in the boot.config(5) configuration file could not be recognized.[r233377, r234563]

A bug in loader(8) which could prevents a UFS1 filesystem on big endian platforms from booting.[r232963]

[sparc64] FreeBSD loader(8) now supports heap to show the heap usage.[r235998]

The gptboot boot block now reads the backup GPT header from the last LBA only when the primary GPT header and tables are invalid. This mitigates interoperability issues with some geom(4) providers like MIRROR which use the last LBA for the metadata.[r234694]

[sparc64] FreeBSD/sparc64 now supports booting from ZFS via the zfsboot boot block and zfsloader.[r236077]

A bug in the zfsboot boot block which could prevent -q option from working has been fixed.[r234680]

The zfsboot boot block and zfsloader support filesystems within a ZFS storage pool. In zfsloader, the ZFS device name format is now zfs:pool/fs and the fully qualified file path format is zfs:pool/fs:/path/to/file. The zfsboot boot block accepts the kernel/loader name in the format pool:fs:path/to/file or, as before, pool:path/to/file. In the latter case a default filesystem is used (the pool root or a filesystem with the bootfs property). The zfsboot boot block passes the GUIDs of the selected storage pool and dataset to zfsloader to be used as its defaults.[r237765]

2.2.2 Hardware Support

FreeBSD acpi(4) subsystem now uses MADT to match ACPI Processor objects to CPUs and ignores disabled cores while it is possible that MADT and DSDT/SSDTs may list CPUs in different orders. A new loader tunable debug.acpi.cpu_unordered has been added for buggy systems that do not have unique ACPI IDs for MADT and Processor objects. Setting it to 1 restores the old behavior.[r237823]

[amd64] A workaround for Erratum 721 for AMD Processor Family 10h and 12h has been implemented. Under a highly specific and detailed set of internal timing conditions, the processor may incorrectly update the stack pointer after a long series of push and/or near-call instructions, or a long series of pop and/or near-return instructions.[r233799]

[amd64] The extended FPU states for native 64-bit and 32-bit ABIs have been supported. AVX instructions are also enabled on capable CPUs.[r237009]

[amd64, i386, pc98] The atkbdc(4) driver now supports a keyboard controller which has PnP ID PNP0320. This can be found on machines which have Japanese PS/2 keyboard with 106/109 keys.[r233795]

[amd64, i386, pc98] The atkbdc(4) driver now supports Synaptics touchpad v7.5 and above.[r244982]

A bug in cpufreq(4) which could prevent CPU frequency tuning from working properly has been fixed.[r233369]

A bug in hwpmc(4) driver which could cause a deadlock in pmcstat(8) utility has been fixed.[r233825]

The pcf8563(4) driver for the NXP (Philips) PCF8563 RTC has been added.[r236079]

[amd64] The pci(4) driver now supports mapping between MSI (Message Signaled Interrupt) and HyperTransport interrupt messages on HyperTransport to PCI bus briges. This change improves handling of MSIs on AMD CPUs.[r234151]

The puc(4) driver now supports Sun 1040 PCI Quad Serial, Moxa PCIe CP102E/CP102EL/CP104EL-A/CP104JU/CP114EL/CP118EL-A/CP168EL-A multiport serial boards, Advantech PCI-1602 RS-485/RS-422 serial card, and Sunix SER5437A dual serial PCI Express card.[r236651, r238775, r243009, r248041]

[amd64, i386] The random(4) driver now supports VIA C3 Nehemiah random number generator on VIA Nano processors. PADLOCK kernel option has been replaced with PADLOCK_RNG in GENERIC kernel.[r240991]

[amd64, i386] The random(4) driver now supports RDRAND instruction on Intel on-chip Digital Random Number Generator (called Bull Mountain). RDRAND_RND kernel option has been added to GENERIC kernel.[r240994]

A new syscons(4) keyboard map for Danish ISO-8859-1 keyboard found on Apple MacBook has been added.[r242338]

A bug in the syscons(4) driver has been fixed. It could cause a button of a USB mouse to be pressed and never released after detaching.[r246787]

[amd64, i386] The uart(4) driver now supports Intel AMT Serial Port for Remote Keyboard and Text (KT) Redirection (Serial Over LAN) on Intel 4 Series Chipset family.[r233065]

The uart(4) driver now supports Wacom Tablet at FuS Lifebook T, multiport serial device IrDA devices with PnP ID PNP0502, PNP0510, and PNP0511, V.34 modems based on CIR1000 Cirrus Logic chip, and MosChip MCS9904 four serial ports controller.[r242883, r243357, r244140]

The uftdi(4) driver now supports BeagleBone and FT2232-based egnite Turtelizer 2 JTAG/RS232 Adapter.[r237189, r237381]

The uchcom(4) driver now supports CH341/CH340 USB-Serial Bridge.[r240570]

The ukbd(4) driver now supports Microsoft Natural Ergonomic Keyboard 4000. It had an issue that function keys were not recognized.[r239426]

The uplcom(4) driver now supports Motorola cable.[r239726]

The usb(4) driver now handles suspend events synchronously. This fixed problems of suspend and resume.[r232871]

The usb(4) driver now supports multi-TT mode operation, which can have one transaction translator for each downstream-facing port on a USB hub. This allows more bandwidth for isochronous FULL speed application connected through a High Speed USB HUB.[r235011]

The uslcom(4) driver now supports Silicon Laboratories CP2103/CP2104/CP2105 based USB serial adapter.[r239820, r239827]

[amd64, i386] The paravirtualized virtio(4) drivers have been added to GENERIC kernel. They include PCI fontend, net, block, balloon, and scsi drivers. The module files are virtio.ko, virtio_pci.ko, if_vtnet.ko, virtio_blk.ko, virtio_balloon.ko, and virtio_scsi.ko, respectively.[r239473, r247907, r247909]

The wbwd(4) driver, which supports the watchdog timer found in Winbond Super I/O chips, has been added.[r235947]

The xhci(4) USB driver now supports XHCI port routing on Intel 7 Series chipsets (Panther Point) and Intel 8 Series chipsets (Lynx Point). A new loader(8) tunable hw.usb.xhci.xhci_port_route has been added for routing bitmap for switching EHCI ports to XHCI controller.[r242985]

The xhci(4) USB driver now supports Etron EJ168 USB 3.0 Host Controllers.[r245736]

2.2.2.1 Multimedia Support

[i386] A bug in the snd_emu10kx(4) driver which could prevent it from working with PAE kernel option has been fixed.[r238674]

The snd_hda(4) driver has been updated. It now supports and provides HDMI, new volume control, automatic recording source selection, runtime reconfiguration, more than 4 PCM devices on a controller, multichannel recording, additional playback/record streams, higher bandwidth, and more informative device names.[r236750, r236753]

The snd_uaudio(4) driver now supports USB Audio v2.0.[r242983]

The snd_uaudio(4) driver now supports Intel 8 Series chipsets (Lynx Point).[r247121]

The snd_uaudio(4) driver now supports various Yamaha keyboards.[r244248]

The snd_uaudio(4) driver now supports buttons such as volume up/down.[r246788]

2.2.2.2 Network Interface Support

The age(4) network interface driver now supports jumbo frames.[r246725]

Link state change handling in the ale(4) network interface driver has been improved.[r234127]

The ale(4) network interface driver now supports flow control.[r234241]

A bug in the bce(4) network interface driver has been fixed. It could prevent jumbo frame configuration from working.[r235424]

A bug in bce(4) which could prevent IPMI (Intelligent Platform Management Interface) from working when the interface is down has been fixed.[r236217]

The bce(4) network interface driver now supports remote PHYs, which allow the controller to perform MDIO type accesses to a remote transceiver by using message pages defined through MRBE (MultiRate Backplane Ethernet). This is found on machines such as the Dell PowerEdge M610 Blade.[r235819]

A bug in the bge(4) network interface driver which could cause watchdog timeout on BCM5704 controller connected behind AMD 8131 PCI-X bridge has been fixed.[r233496]

The bge(4) driver now supports BCM5717/5718/5719/5720/5761/57766 controllers.[r243547, r245152]

A bug in if_ierrors counter in the bge(4) driver running on BCM5700, 5701, 5702, 5703, or 5704 controller has been fixed. It reported only the number of discarded packets.[r233499]

A bug in bge(4) which could make the device stop working has been fixed.[r236219]

[amd64, i386, pc98] The cas(4), gem(4), and hme(4) drivers have been added to GENERIC kernel.[r233744]

The cxgbe(4) network interface driver has been updated to firmware version 1.8.4.[r247670]

A bug in statistics counters in the em(4), lem(4), and igb(4) drivers has been fixed.[r241376]

The em(4) and lem(4) network interface drivers have been updated to version 7.3.7 and 2.3.9, respectively. It now supports Intel 82580 and I210/I217/I218 interfaces.[r247430]

The fxp(4) network interface driver has been improved. It does not cause unnecessary media change in controller reconfiguration such as promiscuous mode change which leads to an extra link reestablishment.[r233502]

The igb(4) network interface driver now attempts to attach as many CPUs as possible to each queue. If the number of CPUs are greater than or equal to the number of queues, all queues are bound to different CPUs.[r235616]

The ipheth(4) driver now supports Apple iPhone 5 tethering mode.[r242279]

The iwn(4) driver now supports Intel Centrino 6150 wireless N and WiMAX chipsets, and Intel Centrino Wireless-N 100/130 devices.[r233839, r235844]

The ixgbe(4) network interface driver has been updated to version 1.1.4.[r247501]

A bug in ixgbe(4) network interface driver has been fixed. It could cause packet loss in TCP communication when TSO (TCP Segmentation Offload) is enabled.[r235666]

The mxge(4) driver has been updated to firmware version 1.4.55 from Myricom.[r236416]

The oce(4) network interface driver has been updated to version 4.6.95.0.[r248062]

The ral(4) network interface driver now supports Ralink RT2800 and RT3000 chipsets.[r236008]

A bug in the re(4) and rl(4) network interface drivers which could cause a problem on RTL8139 family has been fixed.[r233490]

A bug in the re(4) network interface driver which could cause intermittent link up/down on RTL8169 controller has been fixed.[r233493]

The rl(4) network interface driver now supports D-Link DFE-520TX rev C1.[r245858]

WoL (Wake-on-LAN) support in the rl(4) driver is now disabled by default.[r233490]

The run(4) driver now supports Logitec LAN-W300NU2.[r232594]

The run(4) network interface driver now loads the firmware upon initialization, not attachment. This fixes an issue when the root filesystem is not available at the time of device detection.[r233461]

The run(4) driver has been updated to firmware version 0.236.[r234029]

The sf(4) network interface driver has been improved. System load fluctuation under high network load has been fixed.[r233487]

The tap(4) pseudo network interface driver now supports VIMAGE jail(8).[r237145]

The u3g(4) driver now supports Qualcomm Vertex Wireless 110L modem, Qualcomm 3G modem, Qualcomm Vertex VW110L modem, SIMCom SIM5218, and Huawei K4505, K3770, E3131, E392, E3131, K3765, K4505, and ETS2055 3G modems.[r232875, r235012, r243655]

The udav(4) network interface driver now supports JP1082 USB-LAN adapter.[r242984]

2.2.3 Network Protocols

Locking performance of the bpf(4) Berkeley Packet Filter has been improved.[r247732]

The if_bridge(4) pseudo network interface driver now supports multiple bridges in the same STP domain. It used the same MAC address as the bridge ID for all bridges on the system before.[r236056]

The if_bridge(4) now supports link state change notification and works with carp(4) protocol.[r236058]

The net.link.bridge sysctl(8) variables can now be set in loader(8) and/or loader.conf(5).[r236072]

The default number of the bridge forwarding cache entries of the if_bridge(4) pseudo network interface driver has been increased from 100 to 2000.[r233085]

The table argument in the ipfw(4) packet filter rule syntax now supports IP address, interface name, port number, and jail ID. The following syntax is valid:

 skipto tablearg ip from any to any via table(42) in

A new sysctl(8) variable net.inet.ip.fw.tables_max has been added to specify the maximum number of tables. The default value is 128.[r234637]

IP_RECVTOS socket option to receive for received UDP/IPv4 packets a cmsg of type IP_RECVTOS which contains the TOS byte has been implemented. This allows access to the ECN bits in a protocol on top of UDP.[r247944]

A bug in FreeBSD IPv6 stack has been fixed. It could cause a vlan(4) pseudo network interface to get the EUI64 part in an autoconfigured IPv6 address from an unrelated Ethernet interface on the system.[r233112]

FreeBSD IPv6 stack now supports multiple FIBs. One can use setfib(1) to select a different routing table for IPv6.[r232552]

A bug in reference counting of IPv6 interface routes has been fixed.[r236609, r236611, r236827]

FreeBSD IPv6 stack now handles fragment packets which are not actually fragments but have Fragment Header with both the Fragment Offset and the M bit set to 0 as a regular (non-fragment) packet. For more detail, see Internet Draft draft-gont-6man-ipv6-atomic-fragments.[r238495]

A bug which could cause a system panic in the multicast routing in kernel with VIMAGE kernel option has been fixed. This option is disabled in GENERIC kernel.[r233605]

The lagg(4) pseudo network driver now allows the configuration of which layers are used for the load balance hash calculation. It can be set in ifconfig lagghash option in a comma-separated list. The default value is lagghash l2,l3,l4. For more detail, see ifconfig(8) manual page.[r236057]

A bug in the lagg(4) pseudo network interface driver which could cause an unexpected removal of a member interface upon interface renaming has been fixed.[r238048]

The ng_netflow(4) netgraph(4) node and flowctl(8) utility now supports NetFlow version 9. A new export9 hook has been added for NetFlow v9 data. Note that data export can be done simultaneously in both version 5 and version 9.[r238619, r238620]

A bug in the ng_patch(4) netgraph(4) node which could cause a system panic has been fixed.[r234682]

FreeBSD routing table handling has been improved. It can now perform packet forwarding even while a user application is reading the whole routing table via sysctl(8).[r235056]

A loader tunable net.fibs now supports specifying the number of routing tables. The ROUTETABLES kernel option can still be used to set the default number of routing tables.[r235104]

FreeBSD SCTP stack now supports ng_iface(4) and stf(4) interfaces.[r233245, r233246]

FreeBSD SCTP stack now supports net.inet.udp.checksum sysctl(8) variable for SCTP over UDP over IPv4 encapsulation.[r234805]

SO_PROTOCOL and SO_PROTOTYPE socket option have been added. These are socket level options to get the protocol number found in Linux or Solaris. For more detail, see setsockopt(2) manual page.[r232819]

An issue in FreeBSD tcp(4) host cache has been fixed. It could cause extra ICMP message exchanges when an ICMP unreach is received but allocation of the corresponding TCP host cache fails.[r235053]

A sysctl(8) variable net.inet.tcp.rexmit_drop_options has been added to not drop options from the third retransmitted SYN. The default value is set to 1 for backward compatibility.[r247499]

2.2.4 Disks and Storage

The ahci(4) driver now supports Marvell 88SE9220/9230/9235 PCIe 2.0 x2 6Gbps SATA controllers.[r237114]

The arcmsr(4) driver has been updated to version 1.20.00.26 and now supports ARC-1214 and ARC-1224.[r244923, r247827]

A bug in the amr(4) driver which could cause data corruption has been fixed.[r236319]

The ata(4) driver now supports Intel 8 Series chipsets (Lynx Point).[r247099]

The ata(4) driver now creates symbolic links for backward compatibility when ATA_CAM kernel option is enabled. In a kernel with ATA_CAM, an ATA/SATA disk is recognized as a device node with a name ada0 instead of ad0. A symbolic link /dev/ad0 is automatically generated for /dev/ada0 to keep backward compatibility. This symbolic link generation can be controlled by a kern.cam.ada.legacy_aliases (enabled by default when ATA_CAM is set).[r234912]

The ata(4) driver now has loader(8) tunables to set initial SATA revision for the specific device. The tunable name is hint.ata.busnum.devdevnum.sata_rev for a device devnum on a bus busnum, or hint.ata.busnum.sata_rev for all devices on a bus busnum. The valid values are 1, 2, and 3, which correspond to 1.5 Gbps, 3 Gbps, and 6 Gbps.[r243124]

A new sysctl(8) kern.features.ata_cam has been added. This shows whether ATA_CAM kernel option is enabled or not. This option is disabled in GENERIC kernel.[r233714]

A new sysctl(8) variable kern.cam.pmp.hide_special has been added. This controls whether special PMP ports such as PMP (Port MultiPlier) configuration or SEMB (SATA Enclosure Management Bridge) will be exposed or hidden. The default value is 1 (hidden).[r236766]

The cam(4) driver now uses READ CAPACITY(16) SCSI command to get device information by default when possible. This enables to detect whether Logical Block Provisioning (also known as TRIM or UNMAP) in SBC-3 (SCSI Block Commands-3) Specification is supported on the device.[r232942, r236804]

The sysctl(8) variables kern.cam.da.da_send_ordered and kern.cam.ada.ada_send_ordered have been renamed with kern.cam.da.send_ordered and kern.cam.ada.send_ordered.[r247105]

Performance of the da(4) driver has been improved. It now handles subsequent BIO_DELETE requests handled as a single TRIM request.[r234914]

[amd64, i386] The hpt27xx(4) driver has been included in GENERIC kernel.[r245941]

The hptiop(4) driver has been updated to version 1.8 and now supports HighPoint RocketRAID 4500/4311/4310/4211/4210/3560/3530.[r239159, r242216]

The isci(4) driver now supports Intel C600 Serial Attached SCSI controllers with chip IDs from 0x1d6c to 0x1d6f.[r232554]

A bug in the isci(4) driver which could not correctly handle READ CAPACITY(16) SCSI command for an SATA device has been fixed.[r233789]

The isci(4) driver now supports SCSI UNMAP to ATA DSM translation.[r239735]

A bug in isci(4) driver which could prevent smartctl (sysutils/smartmontools in the Ports Collection) from working.[r236264]

The mfi(4) driver now supports LSI MegaRAID SAS cards named "Drake Skinny" and "ThunderBolt". This includes Dell PERC H810/H800/H710/H700 and Intel RAID Controller RS25DB080/RS25NB008.[r235625]

A bug which could make the mpt(4) driver attach LSI MegaRAID cards which should be handled by the mfi(4) driver has been fixed.[r232563]

The mfi(4) driver now supports loader(8) tunable hw.mfi.allow_cam_disk_passthrough to control raw disk attachment. The default value is 0 (disabled).[r243826]

The mps(4) driver has been updated to version 14.00.00.01-fbsd. This now supports Integrated RAID, WarpDrive controllers, WRITE12 and READ12 for direct I/O, SCSI protection information (EEDP), Transport Level Retries (TLR) for tape drives, and LSI's userland utility.[r237877]

[sparc64, powerpc] The mps(4) driver has been added to GENERIC kernel.[r237944, r238074]

The MULTIPATH geom(4) class has been updated. It now supports Active/Active mode, Active/Read mode as hybrid of Active/Active and Active/Passive, keeping a failed path without removing the geom provider, manual configuration without on-disk metadata, and add, remove, fail, restore, configure subcommands in the gmultipath(8) utility to manage the configured paths.[r234917]

The PART_LDM geom(4) class has been added. This partition scheme has support for Logical Disk Manager, which is also known as dynamic volumes in Microsoft Windows NT. Note that JBOD, RAID0, and RAID5 volumes are not supported yet.[r234407]

The RAID geom(4) class now supports the DDF metadata format, which is defined in the SNIA Common RAID Disk Data Format Specification v2.0. It can read non-degraded RAID4/5/5E/5EE/5R/6/MDF volumes. An -o option in graid(8) utility can be used to specify byte order for the DDF metadata.[r235875]

The RAID geom(4) class now partially supports Intel Rapid Recover Technology (Intel RRT). It is alike to RAID1, but with dedicating master and recovery disks and providing manual control over synchronization. It allows to use recovery disk as snapshot of the master disk from the time of the last sync.[r246170]

The RAID geom(4) class now supports sysctl(8) variables kern.geom.raid.enable and kern.geom.raid.format. kern.geom.raid.enable is to control on-disk metadata recognition in a systemwide basis. When it is set to 1, it is enabled (the default value is 1). kern.geom.raid.format are similar variables to control enable/disable of specific metadata or transformation modules. The valid keywords for format are raid0, raid1, raid1e, raid5, and concat.[r240554, r240556]

The RAID geom(4) class now supports BIO_DELETE requests.[r243679]

The tmpfs(5) filesystem is production ready, and no longer considered an experimental implementation.[r234512]

The tws(4) driver has been updated to version 10.80.00.005 from LSI.[r241763]

The umass(4) driver now supports Olympus FE-210 camera, LG UP3S MP3 player, Laser MP3-2GA13 MP3, and Garmin GPS devices.[r235086, r236654]

A bug in the xen(4) blkfront driver has been fixed. It could not attach on Citrix XenServer configurations that advertise the multi-page ring extension.[r233791]

2.2.5 File Systems

The linprocfs(5) filesystem now supports /proc/filesystems.[r247808]

Bugs in msdosfs(5) which could cause mounting a FAT32 filesystem to fail, create a broken directory entry in a FAT32 filesystem, and prevent sync and async mount option from working, have been fixed.[r246547, r246548, r246550]

Bugs in FreeBSD NFS subsystem has been fixed. They could cause stale name cache entries on an NFS client.[r233286]

A memory leak when a ZFS volume is exported via the FreeBSD NFS (newnfs) server has been fixed. Note that oldnfs is used as the default NFS implementation in GENERIC kernel.[r236147]

FreeBSD NFS subsystem now supports a timeout parameter on positive name cache entries on the NFS client side. nametimeo mount option has been added to specify the timeout. The default value is 60 seconds, and one can disable the positive name caching by setting it to 0.[r233327]

A workaround has been implemented in FreeBSD NFS subsystem to handle a reply to an NFS create RPC which do not include file attributes under certain circumstances. This improves interoperability between non-FreeBSD NFS servers and FreeBSD NFS clients.[r235417]

A bug in exports(5) handling in FreeBSD NFS subsystem has been fixed. It could cause an unintended security configuration when there are multiple export entries with different security flavors.[r241348]

Several bugs in nullfs(5) which could cause a system panic have been fixed.[r232665]

FreeBSD ZFS subsystem has been updated to support feature flags for ZFS pools (the SPA version is 5000). Asynchronous destroy of ZFS dataset, LZ4 compression, ZIO NOP-write optimization have been implemented as new features. loader(8) tunables vfs.zfs.sync_pass_deferred_free, vfs.zfs.sync_pass_dont_compress, vfs.zfs.sync_pass_rewrite, and vfs.zfs.nopwrite_enabled have been added.[r243717, r244088, r247310]

Note that this upgrade can cause interoperability issues when upgrading a FreeBSD 8.4 system to 9.0 or 9.1. This is because FreeBSD 9.0 and 9.1 support SPA version 28 and do not recognize version 5000. To mitigate this issue, the default SPA version for a newly created ZFS pool on FreeBSD 8.4 is set to version 28. To create a ZFS pool with version 5000, use zpool(8) upgrade command after the creation.

A bug in ZFS subsystem which could cause a system panic when importing a ZFS pool has been fixed.[r246578]

The sysctl(8) variable vfs.zfs.txg.timeout has been changed from read-only to writable.[r235507]

2.3 Userland Changes

The load average limit in the atrun(8) utility has been set based on the number of CPUs.[r242991]

The chkgrp(8) utility now supports a -q flag to disable printing of text when the group format is correct.[r244064]

The crontab(1) utility now waits for a second before updating the spool directory's mtime. It could happen that the modified crontab updated the mtime of the spool directory, and then crontab(1) utility updated the mtime again within a second. In this case, the crontab database is not updated properly.[r239877]

The cut(1) utility now supports a -w flag to specify whitespace as the delimiter.[r244305]

The default dot.cshrc file for csh(1) and tcsh(1) has been changed. For more detail, see /usr/share/skel/dot.cshrc.[r234979, r242642]

The daemon(8) utility now supports an -r flag to restart the program if it has been terminated.[r233762]

The devd(8) daemon now supports the ! character in regex matching in devd.conf(5). It inverts the logic of the matching.[r247768]

The devfs(5) mount now supports ruleset=number mount option and updating the existing mount by using -u flag in the mount(8) utility. This new option sets the specified ruleset number as the active ruleset of the new devfs mount and applies all its rules at mount time. If the specified ruleset doesn't exist, a new empty ruleset is created.[r233867]

The du(1) utility now supports a -g flag to display the results in gigabytes.[r247539]

The fetch(1) utility now supports percent-encoded strings in user and password component of a URL.[r235254]

The maximum number of HTTP redirections has been increased from 5 to 20 in the fetch(1) utility.[r242034]

The fetch(1) utility now supports HTTP status codes 305 (Use Proxy) and 308 (Permanent Redirect).[r242288, r242291]

A countermeasure against possible DoS (Denial of Service) attack described in CVE-2010-2632 in the ftpd(8) daemon has been implemented.[r246357]

A new environment variable PROFIL_USE_PID has been added to generate profiling data for the gprof(1) utility with a filename including the process ID.[r235084]

The ifconfig(8) now supports a state option for carp(4) protocol to set the state of a carp cluster. Valid state keywords are master and backup.[r243466]

A bug in the inetd(8) daemon which could cause wrong accounting for elapsed time has been fixed.[r236875]

The inetd(8) daemon now set the listen queue size to the value of kern.ipc.somaxconn instead of hardcoded value 64.[r246403]

The default ip6addrctl(8) address selection policy for IPv4 and IPv6 has been updated to one in RFC 6724.[r246599]

The kdump(1) utility now supports a -p pid option to accept either a process ID or a thread ID.[r237790]

The lastcomm(1) utility now supports a +format option to specify strftime(3) format for process start and exit times.[r235888]

The libedit library has been updated to a NetBSD snapshot as of 28 December, 2009.[r237739]

The libpmc library has been updated to support more PMCs (Performance Monitoring Counters) in Intel Core i7 and Xeon 5500 family based on Intel documentation as of October 2011. Specifically, DTLB_MISSES.PDE_MISS and DTLB_MISSES.LARGE_WALK_COMPLETED have been added.[r234045]

The libradius now supports the rad_bind_to(3) function.[r234555]

The libusb(3) library now supports a libusb_get_max_iso_packet_size(3) function.[r235017]

A bug in the the libutil library has been fixed. It could prevent configuration of priority class capability in /etc/login.conf (LOGIN_SETPRIORITY in setusercontext(3) function) from working when the password is not set.[r233153]

The make(1) utility has been updated to version 8201210080. It now supports -V ${VAR} variable expansion, and :tu and :tl variable modifiers.[r241368]

The mktemp(1) utility now uses tmp as the default prefix when -t is not specified.[r241422]

The mv(1) utility now supports a -h flag. This forces it to treat a symbolic link to a directory for the target as a symbolic instead of a directory.[r241321]

The pam_exec(8) module now supports return_prog_exit_status. When this option is enabled, the program exit status is used as the pam_exec(8) return code. It allows the program to tell why the step failed (user unknown, for example).[r234843]

A bug in pam_unix(8) module has been fixed. It could prevent passwordtime login capability in login.conf(5) from working.[r234741]

The pciconf(8) utility now supports a -e flag to display PCI error details in listing mode. When this is specified, the status of any error bits in the PCI status register and PCI-express device status register will be displayed. It also lists any errors indicated by version 1 of PCI-express Advanced Error Reporting (AER).[r237732]

A workaround has been implemented in the ppp(8) daemon to support some 3G modems which return a wrong signature in echo packets and make it impossible to use LQR and ECHO.[r242198]

The procstat(1) utility now displays osreldate in binary information for a process.[r233953]

The procstat(1) utility now displays superpage mapping flag in the process virtual memory mappings.[r238752]

The procstat(1) and fstat(1) utilities now shows pathname associated with a shared memory object.[r236699]

The ps(1) utility now supports cow keyword to show the number of copy-on-write faults in a process.[r236306]

The ps(1) utility now supports dsiz and ssiz keywords to show data and stack size respectively.[r241159]

The rarpd(8) daemon now supports vlan(4) interface and -P option to specify the PID file. When -a flag is specified, /var/run/rarpd.ifname.pid is used as the PID filename by default.[r245077]

A bug in the remquo(3) functions where the quotient did not always have the correct sign when the remainder was 0, and another bug that the remainder and quotient were both off by a bit in certain cases involving subnormal remainders, have been fixed. Note that these bugs affected all platforms except amd64 and i386.[r234534]

The rtld(1) dynamic linker has been improved in performance of TLS (Thread Local Storage) handling.[r233067]

The setbuf(1) utility and libstdbuf library have been added. This controls the default buffering behavior of standard stdio streams.[r235141]

The sh(1) program now allows underscore characters in the arithmetic expansion.[r234001]

The sockstat(1) utility now supports a -j jid option to specify the socket list to be limited to a specific jail(8) ID.[r237672]

A variable NO_FOO in src.conf(5) now overrides WITH_FOO.[r241969]

The syslogd(8) daemon now supports IPv6 destination address in syslog.conf(5).[r241472]

The systat(1) utility now accepts fractional number of seconds.[r243684]

The tcpdrop(8) utility now allows addresses and ports to be separated by a colon or period rather than a space to permit directly pasting the output of commands such as netstat and sockstat on the command line.[r247563]

The top(1) utility now displays ZFS ARC memory usage on hosts using ZFS.[r239751]

A bug in traceroute(8) utility which could result in not accepting any incoming packets has been fixed.[r235163]

The unzip(1) program now supports a -Z flag to enable zipinfo mode.[r234331]

The usbdump(8) utility now supports filtering USB devices and USB endpoints.[r235015]

The usbhidctl(1) utility now supports a -z flag for reading operation. It allows to not request current values from the device, but only receive changes.[r235881]

Performance of the zfs(8) list -t snapshot command has been dramatically improved.[r233862]

The zfs(8) get command now supports a -t datatype option.[r233862]

The zfs(8) jail and unjail commands now support a jail name as well as a jail ID.[r246750]

The zfs(8) send command now reports transmitted data size in bytes when -v flag is specified.[r235952]

Changing zfs(8) canmount property to on no longer causes remount of the ZFS dataset when a dataset is already mounted.[r237457]

2.3.1 /etc/rc.d Scripts

The rc.d scripts now display script filename running to standard error when SIGINFO is issued. This message was sent to standard output and could prevent redirection from working.[r232549]

The rc.d/jail script now supports a jail_parameters variable to specify extra parameters for each jail.[r242083]

The service(8) utility now supports a -R flag to restart all third party services in /usr/local/etc/rc.d.[r246609]

2.4 Contributed Software

AWK has been updated to 20121220.[r246374]

ISC BIND has been updated to version 9.8.4-P2.[r248807]

BZIP2 has been updated to version 1.0.6.[r247448]

TENEX C shell ( tcsh(1)) has been updated to version 6.18.01.[r232635]

LESS ( less(1)) has been updated to version v451.[r240160]

libexpat has been updated to version 2.1.0.[r247514]

netcat has been updated to a version as of OpenBSD 5.2.[r243819]

OpenSSH has been updated to version 6.1.[r247521]

OpenSSL has been updated to version 0.9.8y.[r248057]

sendmail has been updated to version 8.14.7.[r250167]

The timezone database has been updated to tzdata2012j release.[r243006]

XZ has been updated to version 5.0.4.[r245129]

2.5 Ports/Packages Collection Infrastructure

The pkg(8) command has been added. This is used as a bootstrap tool for ports-mgmt/pkg in the Ports Collection.[r239563]

The pkg_add(1) utility now supports PACKAGESUFFIX to specify extension in a package filename.[r240674]

The pkg_create(1) program now allows a relative pathname in the -p option.[r233686]

2.6 Release Engineering and Integration

The supported version of the KDE desktop environment (x11/kde4) has been updated from 4.7.4 to 4.10.1.

3 Upgrading from previous releases of FreeBSD

[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 kernel 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>.