From 541a1c68fa258f332f18f770d9119db6bb2dd897 Mon Sep 17 00:00:00 2001 From: Hiroki Sato Date: Thu, 17 Jan 2008 16:13:58 +0000 Subject: [PATCH] Add 6.3 release documentation. Note that they are not hooked up to the build yet. --- en/releases/6.3R/Makefile | 31 +- en/releases/6.3R/docbook.css | 161 + en/releases/6.3R/errata.html | 116 + en/releases/6.3R/hardware-alpha.html | 5784 ++++++++++++++ en/releases/6.3R/hardware-amd64.html | 6670 ++++++++++++++++ en/releases/6.3R/hardware-i386.html | 8159 ++++++++++++++++++++ en/releases/6.3R/hardware-ia64.html | 2999 +++++++ en/releases/6.3R/hardware-pc98.html | 4846 ++++++++++++ en/releases/6.3R/hardware-sparc64.html | 2105 +++++ en/releases/6.3R/hardware.sgml | 32 + en/releases/6.3R/installation-alpha.html | 1195 +++ en/releases/6.3R/installation-amd64.html | 1403 ++++ en/releases/6.3R/installation-i386.html | 1626 ++++ en/releases/6.3R/installation-ia64.html | 895 +++ en/releases/6.3R/installation-pc98.html | 1018 +++ en/releases/6.3R/installation-sparc64.html | 950 +++ en/releases/6.3R/installation.sgml | 32 + en/releases/6.3R/readme.html | 415 + en/releases/6.3R/relnotes-alpha.html | 608 ++ en/releases/6.3R/relnotes-amd64.html | 623 ++ en/releases/6.3R/relnotes-i386.html | 622 ++ en/releases/6.3R/relnotes-ia64.html | 608 ++ en/releases/6.3R/relnotes-pc98.html | 608 ++ en/releases/6.3R/relnotes-sparc64.html | 608 ++ en/releases/6.3R/relnotes.sgml | 32 + 25 files changed, 42143 insertions(+), 3 deletions(-) create mode 100644 en/releases/6.3R/docbook.css create mode 100644 en/releases/6.3R/errata.html create mode 100644 en/releases/6.3R/hardware-alpha.html create mode 100644 en/releases/6.3R/hardware-amd64.html create mode 100644 en/releases/6.3R/hardware-i386.html create mode 100644 en/releases/6.3R/hardware-ia64.html create mode 100644 en/releases/6.3R/hardware-pc98.html create mode 100644 en/releases/6.3R/hardware-sparc64.html create mode 100644 en/releases/6.3R/hardware.sgml create mode 100644 en/releases/6.3R/installation-alpha.html create mode 100644 en/releases/6.3R/installation-amd64.html create mode 100644 en/releases/6.3R/installation-i386.html create mode 100644 en/releases/6.3R/installation-ia64.html create mode 100644 en/releases/6.3R/installation-pc98.html create mode 100644 en/releases/6.3R/installation-sparc64.html create mode 100644 en/releases/6.3R/installation.sgml create mode 100644 en/releases/6.3R/readme.html create mode 100644 en/releases/6.3R/relnotes-alpha.html create mode 100644 en/releases/6.3R/relnotes-amd64.html create mode 100644 en/releases/6.3R/relnotes-i386.html create mode 100644 en/releases/6.3R/relnotes-ia64.html create mode 100644 en/releases/6.3R/relnotes-pc98.html create mode 100644 en/releases/6.3R/relnotes-sparc64.html create mode 100644 en/releases/6.3R/relnotes.sgml diff --git a/en/releases/6.3R/Makefile b/en/releases/6.3R/Makefile index a284b0bcfe..eadec6a9f1 100644 --- a/en/releases/6.3R/Makefile +++ b/en/releases/6.3R/Makefile @@ -1,4 +1,4 @@ -# $FreeBSD$ +# $FreeBSD: www/en/releases/6.3R/Makefile,v 1.1 2007/11/25 05:26:46 kensmith Exp $ .if exists(../Makefile.conf) .include "../Makefile.conf" @@ -7,13 +7,38 @@ .include "../Makefile.inc" .endif -DOCS= schedule.sgml +#DOCS= announce.sgml +#DOCS+= relnotes.sgml +#DOCS+= hardware.sgml +#DOCS+= installation.sgml +DOCS+= schedule.sgml #FETCHFILE= http://people.freebsd.org/~pho/stress/log/news.rss #FETCHCMD= /usr/bin/fetch #CLEANFILES+= news.rss stress.html -#DATA+= docbook.css +DATA+= errata.html +DATA+= hardware-alpha.html +DATA+= hardware-amd64.html +DATA+= hardware-ia64.html +DATA+= hardware-i386.html +DATA+= hardware-pc98.html +DATA+= hardware-sparc64.html +DATA+= installation-alpha.html +DATA+= installation-amd64.html +DATA+= installation-ia64.html +DATA+= installation-i386.html +DATA+= installation-pc98.html +DATA+= installation-sparc64.html +DATA+= readme.html +DATA+= relnotes-alpha.html +DATA+= relnotes-amd64.html +DATA+= relnotes-ia64.html +DATA+= relnotes-i386.html +DATA+= relnotes-pc98.html +DATA+= relnotes-sparc64.html + +DATA+= docbook.css #news.rss: # ${FETCHCMD} ${FETCHFILE} diff --git a/en/releases/6.3R/docbook.css b/en/releases/6.3R/docbook.css new file mode 100644 index 0000000000..f0ac619ebe --- /dev/null +++ b/en/releases/6.3R/docbook.css @@ -0,0 +1,161 @@ +/* + * Copyright (c) 2003 The FreeBSD Documentation Project + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * + * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + * $FreeBSD$ + */ + +BODY ADDRESS { + line-height: 1.3; + margin: .6em 0; +} + +BODY BLOCKQUOTE { + margin-top: .75em; + line-height: 1.5; + margin-bottom: .75em; +} + +HTML BODY { + margin: 1em 8% 1em 10%; + line-height: 1.2; +} + +.LEGALNOTICE { + font-size: small; + font-variant: small-caps; +} + +BODY DIV { + margin: 0; +} + +DL { + margin: .8em 0; + line-height: 1.2; +} + +BODY FORM { + margin: .6em 0; +} + +H1, H2, H3, H4, H5, H6, +DIV.EXAMPLE P B, +.QUESTION, +DIV.TABLE P B, +DIV.PROCEDURE P B { + color: #990000; +} + +BODY H1 { + margin: .8em 0 0 -4%; + line-height: 1.3; +} + +BODY H2 { + margin: .8em 0 0 -4%; + line-height: 1.3; +} + +BODY H3 { + margin: .8em 0 0 -3%; + line-height: 1.3; +} + +BODY H4 { + margin: .8em 0 0 -3%; + line-height: 1.3; +} + +BODY H5 { + margin: .8em 0 0 -2%; + line-height: 1.3; +} + +BODY H6 { + margin: .8em 0 0 -1%; + line-height: 1.3; +} + +BODY HR { + margin: .6em +} + +BODY IMG.NAVHEADER { + margin: 0 0 0 -4%; +} + +OL { + margin: 0 0 0 5%; + line-height: 1.2; +} + +BODY P { + margin: .6em 0; + line-height: 1.2; +} + +BODY PRE { + margin: .75em 0; + line-height: 1.0; + color: #461b7e; +} + +BODY TD { + line-height: 1.2 +} + +BODY TH { + line-height: 1.2; +} + +UL, BODY DIR, BODY MENU { + margin: 0 0 0 5%; + line-height: 1.2; +} + +HTML { + margin: 0; + padding: 0; +} + + +.FILENAME { + color: #007a00; +} + +BODY H1, BODY H2, BODY H3, BODY H4, BODY H5, BODY H6 { + margin-left: 0 +} + +.GUIMENU, .GUIMENUITEM, .GUISUBMENU, +.GUILABEL, .INTERFACE, .GUIBUTTON, +.SHORTCUT, .SHORTCUT .KEYCAP { + background-color: #F0F0F0; +} + +.ACCEL { + background-color: #F0F0F0; + text-decoration: underline; +} diff --git a/en/releases/6.3R/errata.html b/en/releases/6.3R/errata.html new file mode 100644 index 0000000000..f2c4632988 --- /dev/null +++ b/en/releases/6.3R/errata.html @@ -0,0 +1,116 @@ + + + + +FreeBSD 6.3-RELEASE Errata + + + + + +
+
+

FreeBSD 6.3-RELEASE Errata

+ +

The FreeBSD Project

+ +

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

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v +1.73.2.50.2.1 2007/11/25 17:41:31 bmah Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+
+ +
+
+ +
+
+

This document lists errata items for FreeBSD 6.3-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 6.3-RELEASE will be maintained until the release of +FreeBSD 6.4-RELEASE.

+
+
+ +
+
+

1 Introduction

+ +

This errata document contains “late-breaking news” about FreeBSD +6.3-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 6.3-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://security.FreeBSD.org/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.

+
+ +
+
+

2 Late-Breaking News and +Corrections

+
+ +
+
+

3 Security Advisories

+
+ +
+
+

4 Known Problems and +Solutions

+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/hardware-alpha.html b/en/releases/6.3R/hardware-alpha.html new file mode 100644 index 0000000000..08fbea6b00 --- /dev/null +++ b/en/releases/6.3R/hardware-alpha.html @@ -0,0 +1,5784 @@ + + + + +FreeBSD/alpha 6.3-RELEASE Hardware Notes + + + + + +
+
+

FreeBSD/alpha 6.3-RELEASE Hardware +Notes

+ +

The FreeBSD Documentation Project

+ +

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

+ +
+
+ +
+
+
Table of Contents
+ +
1 Introduction
+ +
2 Supported processors and motherboards
+ +
+
+
2.1 Overview
+ +
2.2 In general, what do you need to run FreeBSD on an +Alpha?
+ +
2.3 System-specific information
+ +
+
+
2.3.1 AXPpci33 (“NoName”)
+ +
2.3.2 Personal Workstation (“Miata”)
+ +
2.3.3 Evaluation Board 64 family
+ +
2.3.4 Evaluation Board 164 (“EB164, PC164, PC164LX, +PC164SX”) family
+ +
2.3.5 AlphaStation 200 (“Mustang”) and 400 +(“Avanti”) series
+ +
2.3.6 AlphaStation 500 and 600 (“Alcor” & +“Maverick” for EV5, “Bret” for EV56)
+ +
2.3.7 AlphaServer 1000 (“Mikasa”), 1000A +(“Noritake”) and 800(“Corelle”)
+ +
2.3.8 DS10/VS10/XP900 (“Webbrick”) / XP1000 +(“Monet”) / DS10L (“Slate”)
+ +
2.3.9 DS20/DS20E (“Goldrush”)
+ +
2.3.10 AlphaPC 264DP / UP2000
+ +
2.3.11 AlphaServer 2000 (“DemiSable”), 2100 +(“Sable”), 2100A (“Lynx”)
+ +
2.3.12 AlphaServer 4x00 (“Rawhide”)
+ +
2.3.13 AlphaServer 1200 (“Tincup”) and AlphaStation +1200 (“DaVinci”)
+ +
2.3.14 Alpha Processor Inc. UP1000
+ +
2.3.15 Alpha Processor Inc. UP1100
+ +
2.3.16 Alpha Processor Inc. CS20, Compaq DS20L
+ +
2.3.17 Compaq AlphaServer ES40 (“Clipper”)
+
+
+ +
2.4 Supported Hardware Overview
+ +
2.5 Further reading
+ +
2.6 Acknowledgments
+
+
+ +
3 Supported Devices
+ +
+
+
3.1 Disk Controllers
+ +
3.2 Ethernet Interfaces
+ +
3.3 Token Ring Interfaces
+ +
3.4 FDDI Interfaces
+ +
3.5 ATM Interfaces
+ +
3.6 Wireless Network Interfaces
+ +
3.7 Miscellaneous Networks
+ +
3.8 ISDN Interfaces
+ +
3.9 Serial Interfaces
+ +
3.10 Sound Devices
+ +
3.11 Camera and Video Capture Devices
+ +
3.12 USB Devices
+ +
3.13 IEEE 1394 (Firewire) Devices
+ +
3.14 Bluetooth Devices
+ +
3.15 Cryptographic Accelerators
+ +
3.16 Miscellaneous
+
+
+
+
+ +
+

1 Introduction

+ +

This document contains the hardware compatibility notes for FreeBSD 6.3-RELEASE on the +Alpha/AXP hardware platform (also referred to as FreeBSD/alpha 6.3-RELEASE). It lists +devices known to work on this platform, as well as some notes on boot-time kernel +customization that may be useful when attempting to configure support for new +devices.

+ +
+
+

Note: This document includes information specific to the Alpha/AXP hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.

+
+
+
+ +
+
+

2 Supported processors and +motherboards

+ +Maintained by Wilko Bulte. + +

Additions, corrections and constructive criticism are invited. In particular, +information on system quirks is more than welcome.

+ +
+
+

2.1 Overview

+ +

This document tries to provide a starting point for those who want to run FreeBSD on +an Alpha-based machine. It is aimed at providing background information on the various +hardware designs. It is not a replacement for the systems manuals.

+ +

The information is structured as follows:

+ +
    +
  • +

    general hardware requirements to run FreeBSD on alpha;

    +
    • + +
  • +

    system specific information for each of the systems/boards supported by FreeBSD;

    +
    • + +
  • +

    information on expansion boards for FreeBSD, including things that differ from what is +in the generic supported hardware list.

    +
    • +
+ +
+
+

Note: You will see references to DEC, Digital Equipment Corporation and Compaq +used more or less interchangeably. Now that Compaq has acquired Digital Equipment it +would be more correct to refer to Compaq only. To be completely politically correct given +that Hewlett Packard in turn has acquired Compaq I probably should be using HP +everywhere. Given the fact that you will see the mix of names everywhere, I don't +bother.

+
+
+ +
+
+

Note: SRM commands will be in UPPER CASE. Lower +case input is also acceptable to SRM. Upper case is used for clarity.

+
+
+
+ +
+
+

2.2 In general, what do you need to run +FreeBSD on an Alpha?

+ +

Obviously you will need an Alpha machine that FreeBSD knows about. Alpha machines are +NOT like PCs. There are considerable differences between the various core logic chip sets +and mainboard designs. This means that a kernel needs to know the intimate details of a +particular machine before it can run on it. Throwing some odd GENERIC kernel at unknown hardware is almost guaranteed to fail +miserably.

+ +

For a machine even to be considered for FreeBSD use please make sure it has the SRM +console firmware installed. Or at least make sure that SRM console firmware is available +for the particular machine type. If FreeBSD does not currently support your machine type, +there is a good chance that this will change at some point in time, assuming SRM is +available. All bets are off when SRM console firmware is not available.

+ +

Machines with the ARC or AlphaBIOS console firmware were intended for WindowsNT. Some +have SRM console firmware available in the system ROMs which you only have to select (via +an ARC or AlphaBIOS menu). In other cases you will have to re-flash the ROMs with SRM +code. Check on http://ftp.digital.com/pub/DEC/Alpha/firmware to see what is available for +your particular system. In any case: no SRM means no FreeBSD (or NetBSD, OpenBSD, Tru64 Unix or OpenVMS for +that matter). With the demise of WindowsNT/alpha a lot of former NT boxes are sold on the +second hand market. They have little or no trade-in value when they are NT-only from the +console firmware perspective. So, be suspicious if the price appears too good.

+ +

In case you have problems making your selection of SRM 'stick', in other words if the +system falls back to AlphaBIOS after you selected the SRM console, it is time to check if +the battery of your CMOS clock/parameter RAM is empty. If so, a replacement battery most +likely fixes the issue.

+ +

Known non-SRM machines are:

+ +
    +
  • +

    Digital XL series

    +
    • + +
  • +

    Digital XLT series

    +
    • + +
  • +

    Samsung PC164UX (“Ruffian”)

    +
    • + +
  • +

    Samsung 164B

    +
    • +
+ +

Machines that have SRM but are not supported by FreeBSD are:

+ +
    +
  • +

    DECpc 150 (“Jensen”)

    +
    • + +
  • +

    DEC 2000/300 (“Jensen”)

    +
    • + +
  • +

    DEC 2000/500 (“Culzean”)

    +
    • + +
  • +

    AXPvme series (“Medulla”)

    +
    • +
+ +

To complicate things a bit further: Digital used to have so called +“white-box” Alpha machines destined as NT-only and “blue-box” +Alpha machines destined for OpenVMS and Digital Unix. These names are based on the color +of the cabinets, “FrostWhite” and “TopGunBlue” respectively. +Although you could put the SRM console firmware on a whitebox, OpenVMS and Digital Unix +will refuse to boot on them. FreeBSD in post-4.0-RELEASE will run on both the white and +the blue-box variants. Before someone asks: the white ones had a rather different (read: +cheaper) Digital price tag.

+ +

As part of the SRM you will get the so called OSF/1 PAL code (OSF/1 being the initial +name of Digital's UNIX offering on Alpha). The PAL code can be thought of as a software +abstraction layer between the hardware and the operating system. It uses normal CPU +instruction plus a handful of privileged instructions specific for PAL use. PAL is not +microcode. The ARC console firmware contains a different PAL code, geared towards WinNT +and in no way suitable for use by FreeBSD (or more generic: Unix or OpenVMS). Before +someone asks: Linux/alpha brings its own PAL code, allowing it to boot on ARC and +AlphaBIOS. There are various reasons why this is not a very good idea in the eyes of the +*BSD folks. I don't want to go into details here. If you are interested in the gory +details search the FreeBSD and NetBSD web sites.

+ +

There is another pitfall ahead: you will need a disk adapter that the SRM console +firmware recognizes in order to be able to boot from a disk. What is acceptable to SRM as +a boot adapter is unfortunately highly system and SRM version dependent. For older PCI +based machines it means you will need either a NCR/Symbios 53C810 based adapter, or a +Qlogic 1020/1040 based adapter. Some machines come with a SCSI chip embedded on the +mainboard. Newer machine designs and SRM versions will be able to work with more modern +SCSI chips/adapters. Check out the machine specific info below. Please note that the rest +of this discussion only refers to Symbios chips, this is meant to include the older chips +that still have NCR stamped on them. Symbios bought NCR sometime.

+ +

The problem might bite those who have machines that started their lives as WindowsNT +boxes. The ARC or AlphaBIOS knows about other adapter types that it can boot from than the SRM. For +example you can boot from an Adaptec 2940UW with ARC/AlphaBios but (generally) not with +SRM. Some newer machine types have introduced Adaptec boot support. Please consult the +machine specific section for details.

+ +

Most adapters that cannot be booted from work fine for data-only disks. The +differences between SRM and ARC could also get you pre-packaged IDE CDROMs and hard +drives in some (former WindowsNT) systems. SRM versions exist (depends on the machine +type) that can boot from IDE disks and CDROMs. Check the machine specific section for +details.

+ +

In order to be bootable the root partition (partition a) must be at offset 0 of the +disk drive. This means you have to use the installer's partitioning menu and start with +assigning partition a at offset 0 to the root partition. Subsequently layout the rest of +the partitions to your liking. If you do not adhere to this rule the install will proceed +just fine, but the system will not be bootable from the freshly installed disk. Note that +fdisk is not used on FreeBSD running on Alpha, disks are directly labeled using +disklabel.

+ +

If you don't have/want a local disk drive you can boot via the Ethernet. This assumes +an Ethernet adapter/chip that is recognized by the SRM console. Generally speaking this +boils down to either a 21040 or 21142 or 21143 based Ethernet interface. Older machines +or SRM versions may not recognize the 21142 / 21143 Fast Ethernet chips, you are then +limited to using 10Mbit Ethernet for net booting those machines. Non-DEC cards based on +said chips will generally (but are not guaranteed to) work. Note that Intel took over the +21x4x chips when it bought Digital Semiconductor. So you might see an Intel logo on them +these days. Recent machine designs have SRM support for Intel 8255x Ethernet chips.

+ +

Alpha machines can be run with SRM on a graphics console or on a serial console. ARC +can also be run on a serial consoles if need be. VT100 emulation with 8 bit controls +should at least allow you to switch from ARC/AlphaBIOS to SRM mode without having to +install a graphics card first.

+ +

If you want to run your Alpha machine without a monitor/graphics card just don't +connect a keyboard/mouse to the machine. Instead hook up a serial terminal[emulator] to +serial port #1. The SRM will talk 9600N81 to you. This can also be really practical for +debugging purposes. Beware: some/most (?) SRMs will also present you with a console +prompt at serial port #2. The booting kernel, however, will display the boot messages on +serial port #1 and will also put the console there. This can be extremely confusing.

+ +

Most PCI based Alphas can use ordinary PC-type VGA cards. The SRM contains enough +smarts to make that work. It does not, however, mean that each and every PCI VGA card out +on the street will work in an Alpha machine. Things like S3 Trio64, Mach64, and Matrox +Millennium generally work. Old ET4000 based ISA cards have also worked for me. But ask +around first before buying.

+ +

Most PCI devices from the PC-world will also work in FreeBSD PCI-based machines. Check +the /sys/alpha/conf/GENERIC file for the latest word on this. +Check the appropriate machine type's discussion in case you want to use PCI cards that +have PCI bridge chips on them. In some cases you might encounter problems with PCI cards +not handling PCI parity correctly. This can lead to panics. PCI parity checking can be +disabled using the following SRM command:

+ +
+>>> SET PCI_PARITY OFF
+
+ +

This is not a FreeBSD problem, all operating systems running on Alpha hardware will +need this workaround.

+ +

If your system (also) contains EISA expansion slots you will need to run the EISA +Configuration Utility (ECU) after you have installed EISA cards or after you have +upgraded your console firmware.

+ +

For Alpha CPUs you will find multiple generations. The original Alpha design is the +21064. It was produced in a chip process called MOS4, chips made in this process are +nicknamed EV4. Newer CPUs are 21164, 21264 etc. You will see designations like EV4S, +EV45, EV5, EV56, EV6, EV67, EV68. The EVs with double digit numbers are slightly improved +versions. For example EV45 has an improved FPU and 16 kByte on-chip separate I & D +caches compared to the EV4 on which it is based. Rule of thumb: the higher the digit +immediately following “EV” the more desirable (read: faster / more modern). +Spending money on anything less than an EV5 is not recommended. Hardware available for +free is a different matter of course.

+ +

For memory you want at least 32 Mbytes. I have had FreeBSD run on a 16 Mbyte system +years ago but you will not enjoy that. Kernel build times halved when I went to 32 +Mbytes. Note that the SRM console steals 2Mbyte from the total system memory (and keeps +it). For more serious work 128 Mbytes or more are recommended. Although Alpha machines +typically can accommodate large to very large physical memory sizes, FreeBSD is limited +to 1 or 2 Gbytes (dependent on the core chipset) of RAM. This restriction is due to the +current implementation of the VM system.

+ +

While on the subject of memory: pay close attention to the type of memory your machine +uses. There are very different memory configurations and requirements for the various +machines.

+ +

Final word: I expect the above to sound a bit daunting to the first-time Alpha user. +Don't be daunted too much. And do feel free to ask questions if something is not clear +after reading this document.

+
+ +
+
+

2.3 System-specific information

+ +

Below is an overview of the hardware that FreeBSD runs on. This list will definitely +grow, a look in /sys/alpha/conf/GENERIC can be +enlightening.

+ +

Alpha machines are often best known by their project code name. Where known these are +listed below in parentheses.

+ +
+
+

2.3.1 AXPpci33 +(“NoName”)

+ +

The NoName is a baby-AT mainboard based on the 21066 LCA (Low Cost Alpha) processor. +NoName was originally designed for OEM-use. The LCA chip includes almost all of the logic +to drive a PCI bus and the memory subsystem. All of this makes for a low-priced +design.

+ +

Due to the limited memory interface the system is not particularly fast in case of +cache misses. As long as you stay inside the on-chip cache the CPU is comparable to a +21064 (first generation Alpha). These boards should be very cheap to obtain these days. +It is a full-fledged 64 bit CPU, just don't expect miracles as far as speed goes.

+ +

Features:

+ +
    +
  • +

    21066 Alpha CPU at 166 MHz or 21066A CPU at 233MHz. 21068 CPUs are also possible, but +are even slower.

    +
    • + +
  • +

    on-board Bcache / L2 cache: 0, 256k or 1 Mbyte (uses DIL chips)

    +
    • + +
  • +

    PS/2 mouse & keyboard port OR 5pin DIN keyboard (2 mainboard models)

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      bus width: 64 bits

      +
      • + +
    • +

      PS/2 style 72 pin 36 bit Fast Page Mode SIMMs

      +
      • + +
    • +

      70ns or better

      +
      • + +
    • +

      installed in pairs of 2

      +
      • + +
    • +

      4 SIMM sockets

      +
      • + +
    • +

      uses ECC

      +
      • +
    +
    • + +
  • +

    512kB Flash ROM for the console code.

    +
    • + +
  • +

    2 16550A serial ports

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    floppy interface

    +
    • + +
  • +

    1 embedded IDE interface

    +
    • + +
  • +

    expansion:

    + +
      +
    • +

      3 32 bit PCI slots (1 shared with ISA)

      +
      • + +
    • +

      5 ISA slots (1 shared with PCI)

      +
      • +
    +
    • + +
  • +

    embedded Fast SCSI using a Symbios 53C810 chip

    +
    • +
+ +

NoNames can either have SRM or +ARC console firmware in their Flash ROM. The Flash ROM is not big enough to hold both ARC +and SRM at the same time and allow software selection of alternate console code. But you +only need SRM anyway.

+ +

Cache for the NoNames are 15 or 20 ns DIL chips. For a 256 kByte cache you want to +check your junked 486 mainboard. Chips for a 1 Mbyte cache are a rarer breed +unfortunately. Getting at least a 256kByte cache is recommended performance wise. +Cache-less they are really slow.

+ +

The NoName mainboard has a PC/AT-standard power connector. It also has a power +connector for 3.3 Volts. No need to rush out to get a new power supply. The 3.3 Volts is +only needed in case you run 3.3 Volts PCI expansion boards. These are quite rare.

+ +

The IDE interface is supported by FreeBSD and requires a line in the kernel +configuration file as follows:

+ +
+device ata
+
+ +

The ATA interface uses irq 14.

+ +

The SRM console unfortunately cannot +boot from IDE disks. This means you will have to use a SCSI disk as the boot +device.

+ +

The NoName is somewhat stubborn when it comes to serial consoles. It needs

+ +
+>>> SET CONSOLE SERIAL
+
+ +

before it goes for a serial console. Pulling the keyboard from the machine is not +sufficient, like it is on most other Alpha models. Going back to a graphical console +needs

+ +
+>>> SET CONSOLE GRAPHICS
+
+ +

at the serial console.

+ +

There have been reports that you sometimes need to press Control-Alt-Del to capture +the SRM's attention. I have never seen this myself, but it is worth trying if you are +greeted by a blank screen after powerup.

+ +

Make sure you use true 36 bit SIMMs, and only FPM (Fast Page Mode) DRAM. EDO DRAM or +SIMMs with fake parity will not +work. The board uses the 4 extra bits for ECC. 33 bit FPM SIMMs will for the +same reason not work.

+ +

Given the choice, get the PS/2-variant mainboard. Apart from giving you a mouse port +as bonus it is directly supported by Tru64 Unix in case you ever want or need to run it. +The “DIN-plug”-variant should work OK for FreeBSD.

+ +

The OEM +manual is recommended reading.

+ +

The kernel configuration file for a NoName kernel must contain:

+ +
+options    DEC_AXPPCI_33           
+cpu EV4
+
+
+ +
+
+

2.3.2 Personal Workstation +(“Miata”)

+ +

The Miata is a small tower machine intended to be put under a desk. There are multiple +Miata variants. The original Miata is the MX5 model. Because it suffers from a number of +hardware design flaws a redesign was done, yielding the MiataGL. Unfortunately the +variants are not easily distinguishable at first sight from the outside of the case. An +easy check is to see if the back of the machine sports two USB connectors. If yes, it is +a MiataGL. MX5 models tend to be more common in the used system market place.

+ +

System designations look like “Personal Workstation 433a”. Personal +Workstation, being a bit of a mouthful, is often abbreviated to PWS. This means it has a +433 MHz CPU, and started life as a WinNT workstation (the trailing “a”). +Systems designated from day 1 to run Tru64 Unix or OpenVMS will sport +“433au”. WinNT-Miatas are likely to come pre-configured with an IDE CDROM +drive. So, in general systems are named like PWS[433,500,600]a[u].

+ +

There was also a Miata model with a special CPU cooling system by Kryotech. The +Kryotech has a special cooling system and is housed in a different enclosure.

+ +

Features:

+ +
    +
  • +

    21164A EV56 Alpha CPU at 433, 500 or 600MHz

    +
    • + +
  • +

    21174 core logic (“Pyxis”) chip

    +
    • + +
  • +

    on-board Bcache / L3 cache: 0, 2 or 4 Mbytes (uses a cache module)

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      bus width: 128 bits wide, ECC protected

      +
      • + +
    • +

      unbuffered 72 bit wide SDRAMs DIMMs, installed in pairs of 2

      +
      • + +
    • +

      6 DIMM sockets

      +
      • + +
    • +

      maximum memory 1.5 GBytes

      +
      • +
    +
    • + +
  • +

    on-board Fast Ethernet:

    + +
      +
    • +

      MX5 uses a 21142 or 21143 Ethernet chip, dependent on the version of the PCI riser +card

      +
      • + +
    • +

      MiataGL has a 21143 chip

      +
      • + +
    • +

      the bulkhead can be 10/100 Mbit UTP, or 10 Mbit UTP/BNC

      +
      • +
    +
    • + +
  • +

    2 on-board [E]IDE disk interfaces, based on the CMD646 (MX5) or the Cypress 82C693 +(MiataGL)

    +
    • + +
  • +

    1 Ultra-Wide SCSI Qlogic 1040 [MiataGL only]

    +
    • + +
  • +

    2 64-bit PCI slots

    +
    • + +
  • +

    3 32-bit PCI slots (behind a DEC PCI-PCI bridge chip)

    +
    • + +
  • +

    3 ISA slots (physically shared with the 32 bit PCI slots, via an Intel 82378IB PCI to +ISA bridge chip)

    +
    • + +
  • +

    2 16550A serial port

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    PS/2 keyboard & mouse port

    +
    • + +
  • +

    USB interface [MiataGL only]

    +
    • + +
  • +

    embedded sound based on an ESS1888 chip

    +
    • +
+ +

The Miata logic is divided into two printed circuit boards. The lower board in the +bottom of the machine has the PCI and ISA slots and things like the sound chip etc. The +top board has the CPU, the Pyxis chip, memory etc. Note that MX5 and the MiataGL use a +different PCI riser board. This means that you cannot just upgrade to a MiataGL CPU board +(with the newer Pyxis chip) but that you will also need a different riser board. +Apparently an MX5 riser with a MiataGL CPU board will work but it is definitely not a +supported or tested configuration. Everything else (cabinet, wiring, etc.) is identical +for MX5 and MiataGL.

+ +

MX5 has problems with DMA via the 2 64-bit PCI slots when this DMA crosses a page +boundary. The 32 bit slots don't have this problem because the PCI-PCI bridge chip does +not allow the offending transfers. The SRM code knows about the problem and refuses to +start the system if there is a PCI card in one of the 64bit slots that it does not know +about. Cards that are “known good” to the SRM are allowed to be used in the +64bit slots.

+ +

If you want to fool the SRM you can type set +pci_device_override at the SRM prompt. Just don't complain if your data +mysteriously gets mangled.

+ +

The complete command is:

+ +
+>>> SET PCI_DEVICE_OVERRIDE <vendor_id><device_id>
+
+ +

For example:

+ +
+>>> SET PCI_DEVICE_OVERRIDE 88c15333
+
+ +

The most radical approach is to use:

+ +
+>>> SET PCI_DEVICE_OVERRIDE -1
+
+ +

This disables PCI ID checking altogether, so that you can install any PCI card without +its ID getting checked. For this to work you need a reasonable current SRM version.

+ +
+
+

Important: Do this on your own risk..

+
+
+ +

The FreeBSD kernel reports it when it sees a buggy Pyxis chip:

+ +
+Sep 16 18:39:43 miata /kernel: cia0: Pyxis, pass 1
+Sep 16 18:39:43 miata /kernel: cia0: extended capabilities: 1<BWEN>
+Sep 16 18:39:43 miata /kernel: cia0: WARNING: Pyxis pass 1 DMA bug; no bets...
+
+ +

A MiataGL probes as:

+ +
+Jan  3 12:22:32 miata /kernel: cia0: Pyxis, pass 1
+Jan  3 12:22:32 miata /kernel: cia0: extended capabilities: 1<BWEN>
+Jan  3 12:22:32 miata /kernel: pcib0: <2117x PCI host bus adapter> on cia0
+
+ +

MiataGL does not have the DMA problems of the MX5. PCI cards that make the MX5 SRM +choke when installed in the 64bit slots are accepted without problems by the MiataGL +SRM.

+ +

The latest mainboard revisions of MX5 contain a hardware workaround for the bug. The +SRM does not know about the ECO and will complain about unknown cards as before. So does +the FreeBSD kernel by the way.

+ +

The Miata SRM can boot from IDE CDROM drives. IDE hard disk boot is known to work for +both MiataGL and MX5 disks, so you can root FreeBSD from an IDE disk. Speeds on MX5 are +around 14 Mbytes/sec assuming a suitable drive. Miata's CMD646 chip will support up to +WDMA2 mode as the chip is too buggy for use with UDMA.

+ +

Miata MX5s generally use Qlogic 1040 based SCSI adapters. These are bootable by the +SRM console. Note that Adaptec cards are not bootable by the Miata SRM console.

+ +

The MiataGL has a faster PCI-PCI bridge chip on the PCI riser card than some of the +MX5 riser card versions. Some of the MX5 risers have the same chip as the MiataGL. All in all there is a lot of +variation.

+ +

Not all VGA cards will work behind the PCI-PCI bridge. This manifests itself as no +video at all. Workaround is to put the VGA card “before” the bridge, in one +of the 64 bit PCI slots. Graphics performance using a 64 bit slot is generally +substantially better.

+ +

Both MX5 and MiataGL have an on-board sound chip, an ESS1888. It emulates a +SoundBlaster and can be enabled by putting

+ +
+device pcm
+device  sbc
+
+ +

in your kernel configuration file:

+ +

in case your Miata has the optional cache board installed make sure it is firmly +seated. A slightly loose cache has been observed to cause weird crashes (not surprising +obviously, but maybe not so obvious when troubleshooting). The cache module is identical +between MX5 and MiataGL.

+ +

Installing a 2Mb cache module achieves, apart from a 10-15% speed increase (based on +buildworld elapsed time), a decrease for PCI DMA read bandwidth from 64bit PCI cards. A +benchmark on a 64-bit Myrinet card resulted in a decrease from 149 Mbytes/sec to 115 +Mbytes/sec. Something to keep in mind when doing really high speed things with 64 bit PCI +adapters.

+ +

Although the hardware allows you to install up to 1.5Gbyte of memory, FreeBSD is +limited to 1Gbyte because the DMA code does not correctly handle memory above 1Gbyte.

+ +

Moving to a faster CPU is quite simple, swap out the CPU chip and set the clock +multiplier dipswitch to the speed of the new CPU.

+ +

If you experience SRM errors like

+ +
+ERROR: scancode 0xa3 not supported on PCXAL
+
+ +

after halting FreeBSD you should update your SRM firmware to V7.2-1 or later. This SRM +version is first available on the Firmware Update CD V5.7, or on http://www.compaq.com/ This SRM problem +is fixed on both Miata MX5 and Miata GL.

+ +

USB is supported by FreeBSD 4.1 and later.

+ +

Disconnect the power cord before dismantling the machine, the soft-power switch keeps +part of the logic powered even when +the machine is switched off.

+ +

The kernel configuration file for a Miata kernel must contain:

+ +
+options    DEC_ST550               
+cpu EV5
+
+
+ +
+
+

2.3.3 Evaluation Board 64 family

+ +

In its attempts to popularize the Alpha CPU DEC produced a number of so called +Evaluation Boards. Members of this family are EB64, EB64+, AlphaPC64 (codename +“Cabriolet”). A non-DEC member of this family is the Aspen Alpine. The EB64 +family of evaluation boards has the following feature set:

+ +
    +
  • +

    21064 or 21064A CPU, 150 to 275 MHz

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      memory buswidth: 128 bit

      +
      • + +
    • +

      PS/2 style 72 pin 33 bit Fast Page Mode SIMMs

      +
      • + +
    • +

      70ns or better

      +
      • + +
    • +

      installed in sets of 4

      +
      • + +
    • +

      8 SIMM sockets

      +
      • + +
    • +

      uses parity memory

      +
      • +
    +
    • + +
  • +

    Bcache / L2 cache: 0, 512 kByte, 1 Mbyte or 2 Mbytes

    +
    • + +
  • +

    21072 (“APECS”) chip set

    +
    • + +
  • +

    Intel 82378ZB PCI to ISA bridge chip (“Saturn”)

    +
    • + +
  • +

    dual 16550A serial ports

    +
    • + +
  • +

    parallel printer port

    +
    • + +
  • +

    Symbios 53C810 Fast-SCSI (not on AlphaPC64)

    +
    • + +
  • +

    IDE interface (only on AlphaPC64)

    +
    • + +
  • +

    embedded 10 Mbit Ethernet (not on AlphaPC64)

    +
    • + +
  • +

    2 PCI slots (4 slots on AlphaPC64)

    +
    • + +
  • +

    3 ISA slots

    +
    • +
+ +

Aspen Alpine is slightly different, but is close enough to the EB64+ to run an EB64+ +SRM EPROM (mine did..). The Aspen Alpine does not have an embedded Ethernet, has 3 +instead of 2 PCI slots. It comes with 2 Mbytes of cache already soldered onto the +mainboard. It has jumpers to select the use of 60, 70 or 80ns SIMM speeds.

+ +

36 bits SIMMs work fine, 3 bits simply remain unused. Note the systems use Fast Page +Mode memory, not EDO memory.

+ +

The EB64+ SRM console code is housed in an UV-erasable EPROM. No easy flash SRM +upgrades for the EB64+ The latest SRM version available for EB64+ is quite ancient +anyway.

+ +

The EB64+ SRM can boot both 53C810 and Qlogic1040 SCSI adapters. Pitfall for the +Qlogic is that the firmware that is down-loaded by the SRM onto the Qlogic chip is very +old. There are no updates for the EB64+ SRM available. So you are stuck with old Qlogic +bits too. I have had quite some problems when I wanted to use Ultra-SCSI drives on the +Alpine with Qlogic. The FreeBSD kernel can be compiled to include a much newer Qlogic +firmware revision. This is not the default because it adds hundreds of kBytes worth of +bloat to the kernel. In FreeBSD 4.1 and later the isp firmware is contained in a kernel +loadable module. All of this might mean that you need to use a non-Qlogic adapter to boot +from.

+ +

AlphaPC64 boards generally come with ARC console firmware. SRM console code can be +loaded from floppy into the Flash ROM.

+ +

The IDE interface of the AlphaPC64 is not bootable from the SRM console. Enabling it +requires the following line in the kernel configuration file:

+ +
+device ata
+
+ +

The ATA interface uses irq 14.

+ +

Note that the boards require a power supply that supplies 3.3 Volts for the CPU.

+ +

For the EB64 family machines the kernel config file must contain:

+ +
+options    DEC_EB64PLUS            
+cpu EV4
+
+
+ +
+
+

2.3.4 Evaluation Board 164 (“EB164, +PC164, PC164LX, PC164SX”) family

+ +

EB164 is a newer design evaluation board, based on the 21164A CPU. This design has +been used to “spin off” multiple variations, some of which are used by OEM +manufacturers/assembly shops. Samsung did its own PC164LX which has only 32 bit PCI, +whereas the Digital variant has 64 bit PCI.

+ +
    +
  • +

    21164A, multiple speed variants [EB164, PC164, PC164LX]

    +
    • + +
  • +

    21164PC [only on PC164SX]

    +
    • + +
  • +

    21171 (Alcor) chip set [EB164]

    + +

    21172 (Alcor2) chip set [PC164]

    + +

    21174 (Pyxis) chip [164LX, 164SX]

    +
    • + +
  • +

    Bcache / L3 cache: EB164 uses special cache-SIMMs

    +
    • + +
  • +

    memory bus: 128 bit / 256 bit

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      PS/2 style SIMMs in sets of 4 or 8

      +
      • + +
    • +

      36 bit, Fast Page Mode, uses ECC, [EB164 / PC164]

      +
      • + +
    • +

      SDRAM DIMMs in sets of 2, non-ECC or ECC can be used [PC164SX]

      +
      • + +
    • +

      SDRAM DIMMs in sets of 2, uses ECC [PC164LX]

      +
      • +
    +
    • + +
  • +

    2 16550A serial ports

    +
    • + +
  • +

    PS/2 style keyboard & mouse

    +
    • + +
  • +

    floppy controller

    +
    • + +
  • +

    parallel port

    +
    • + +
  • +

    32 bits PCI

    +
    • + +
  • +

    64 bits PCI [some models]

    +
    • + +
  • +

    ISA slots via an Intel 82378ZB PCI to ISA bridge chip

    +
    • +
+ +

Using 8 SIMMs for a 256bit wide memory can yield interesting speedups over a 4 +SIMM/128bit wide memory. Obviously all 8 SIMMs must be of the same type to make this +work. The system must be explicitly setup to use the 8 SIMM memory arrangement. You must +have 8 SIMMs, 4 SIMMs distributed over 2 banks will not work. For the AlphaPC164 you can +have a maximum of 1Gbyte of RAM, using 8 128Mbyte SIMMs. The manual indicates the maximum +is 512 Mbyte.

+ +

The SRM can boot from Qlogic 10xx boards or the Symbios 53C810[A]. Newer Symbios 810 +revisions like the Symbios 810AE are not recognized by the SRM on PC164. PC164 SRM does +not appear to recognize a Symbios 53C895 based host adapter (tested with a Tekram +DC-390U2W). On the other hand some no-name Symbios 53C985 board has been reported to +work. Cards like the Tekram DC-390F (Symbios875 based) have been confirmed to work fine +on the PC164. Symbios 53C896 has been confirmed to not work.

+ +

Symbios 53C825[a] will also work as boot adapter. Diamond FirePort, although based on +Symbios chips, is not bootable by the PC164SX SRM. PC164SX is reported to boot fine with +Symbios825, Symbios875, Symbios895 and Symbios876 based cards. In addition, Adaptec 2940U +and 2940UW are reported to work for booting (verified on SRM V5.7-1). Adaptec 2930U2 and +2940U2[W] do not work.

+ +

164LX and 164SX with SRM firmware version 5.8 or later can boot from Adaptec +2940-series adapters. A test with an Adaptec 3940UW showed that that one is not supported +however. 164SX SRM recognises Intel 8255x Ethernet cards which show up as eia. Using such +a NIC allows network booting.

+ +

In summary: this family of machines is “blessed” with a challenging +compatibility as far as SCSI adapters go.

+ +

On 164SX you can have a maximum of 1 Gbyte of RAM. 4 regular (PC100 or PC133) 256MB +DIMMs are reported to work just fine. Whether 512MB DIMMs will also work is currently +unknown. You can use ECC or non-ECC DIMMs. The non-ECC ones are the same as commonly +found in PCs. Unfortunately the 164SX is quite picky on which DIMMs it likes, so be +prepared to test and experiment.

+ +

PCI bridge chips are sometimes not appreciated by the 164SX, they cause SRM errors and +kernel panics in those cases. This seems to depend on the fact if the card is recognised, +and therefore correctly initialised, by the SRM console. The 164SX' onboard IDE interface +is quite slow, a Promise card gives a 3-4 times speed improvement.

+ +

On PC164 the SRM sometimes seems to lose its variable settings. “For PC164, +current superstition says that, to avoid losing settings, you want to first downgrade to +SRM 4.x and then upgrade to 5.x.” One sample error that was observed was:

+ +
+ERROR: ISA table corrupt!
+
+ +

A sequence of a downgrade to SRM4.9, an

+ +
+>>> ISACFG -INIT
+
+ +

followed by

+ +
+>>> INIT
+
+ +

made the problem go away. Some PC164 owners report they have never seen the +problem.

+ +

On PC164SX the AlphaBIOS allows you a selection to select SRM to be used as console on +the next power up. This selection does not appear to have any effect. In other words, you +will get the AlphaBIOS regardless of what you select. The fix is to reflash the console +ROM with the SRM code for PC164SX. This will overwrite the AlphaBIOS and will get you the +SRM console you desire. The SRM code can be found on the Compaq Web site.

+ +

164LX can either have the SRM console code or the AlphaBIOS code in its flash ROM +because the flash ROM is too small to hold both at the same time.

+ +

PC164 can boot from IDE disks assuming your SRM version is recent enough.

+ +

EB164 needs a power supply that supplies 3.3 Volts. PC164 does not implement the PS_ON +signal that ATX power supplies need to switch on. A simple switch pulling this signal to +ground allows you to run a standard ATX power supply.

+ +

For the EB164 class machines the kernel config file must contain:

+ +
+options         DEC_EB164
+cpu             EV5
+
+
+ +
+
+

2.3.5 AlphaStation 200 +(“Mustang”) and 400 (“Avanti”) series

+ +

The Digital AlphaStation 200 and 400 series systems are early low end PCI based +workstations. The 200 and 250 series are desktop boxes, the 400 series is a desk-side +mini-tower.

+ +

Features:

+ +
    +
  • +

    21064 or 21064A CPU at speeds of 100 up to 333 MHz

    +
    • + +
  • +

    DECchip 21071-AA core logic chip set

    +
    • + +
  • +

    Bcache / L2 cache: 512 Kbytes (200 and 400 series) or 2048KBytes (250 series)

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      64 bit bus width

      +
      • + +
    • +

      8 to 384 MBytes of RAM

      +
      • + +
    • +

      70 ns or better Fast Page DRAM

      +
      • + +
    • +

      in three pairs (200 and 400 series)

      +
      • + +
    • +

      in two quads, so banks of four. (250 series)

      +
      • + +
    • +

      the memory subsystem uses parity

      +
      • +
    +
    • + +
  • +

    PS/2 keyboard and mouse port

    +
    • + +
  • +

    two 16550 serial ports

    +
    • + +
  • +

    parallel port

    +
    • + +
  • +

    floppy disk interface

    +
    • + +
  • +

    32 bit PCI expansion slots (3 for the AS400-series, 2 for the AS200 & +250-series)

    +
    • + +
  • +

    ISA expansion slots (4 for the AS400-series, 2 for the AS200 & 250-series) (some +ISA/PCI slots are physically shared)

    +
    • + +
  • +

    embedded 21040-based Ethernet (200 & 250 series)

    +
    • + +
  • +

    embedded Symbios 53c810 Fast SCSI-2 chip

    +
    • + +
  • +

    Intel 82378IB (“Saturn”) PCI-ISA bridge chip

    +
    • + +
  • +

    graphics is embedded TGA or PCI VGA (model dependent)

    +
    • + +
  • +

    16 bit sound (on 200 & 250 series)

    +
    • +
+ +

The systems use parity memory SIMMs, but these do not need 36 bit wide SIMMs. 33 bit +wide SIMMs are sufficient, 36 bit SIMMs are acceptable too. EDO or 32 bit SIMMs will not +work. 4, 8, 16, 32 and 64 Mbyte SIMMs are supported.

+ +

The AS200 & AS250 sound hardware is reported to work OK assuming you have the +following line in your kernel config file:

+ +
+device pcm
+
+ +

The sound device uses port 0x530, IRQ 10 and drq 0. You also need to specify flags +0x10011 in the device.hints file.

+ +

AlphaStation 200 & 250 series have an automatic SCSI terminator. This means that +as soon as you plug a cable onto the external SCSI connector the internal terminator of +the system is disabled. It also means that you should not leave unterminated cables +plugged into the machine.

+ +

AlphaStation 400 series have an SRM variable that controls termination. In case you +have external SCSI devices connected you must set this SRM variable using

+ +
+>>> SET CONTROL_SCSI_TERM EXTERNAL.
+
+ +

If only internal SCSI devices are present use:

+ +
+>>> SET CONTROL_SCSI_TERM INTERNAL
+
+ +

For the AlphaStation-[24][05]00 machines the kernel config file must contain:

+ +
+options    DEC_2100_A50
+cpu EV4
+
+
+ +
+
+

2.3.6 AlphaStation 500 and 600 +(“Alcor” & “Maverick” for EV5, “Bret” for +EV56)

+ +

AS500 and 600 were the high-end EV5 / PCI based workstations. EV6 based machines have +in the meantime taken their place as front runners. AS500 is a desktop in a dark blue +case (TopGun blue), AS600 is a sturdy desk-side box. AS600 has a nice LCD panel to +observe the early stages of SRM startup.

+ +

Features:

+ +
    +
  • +

    21164 EV5 CPU at 266, 300, 333, 366, 400, 433, 466, or 500 MHz (AS500) or at 266, 300 +or 333 MHz (AS600)

    +
    • + +
  • +

    21171 (Alcor) or 21172 (Alcor2) core logic chip set

    +
    • + +
  • +

    Cache:

    + +
      +
    • +

      2 or 4 Mb L3 / Bcache (AS600 at 266 MHz)

      +
      • + +
    • +

      4 Mb L3 / Bcache (AS600 at 300 MHz)

      +
      • + +
    • +

      2 or 8 Mb L3 / Bcache (8 Mb on 500 MHz version only)

      +
      • + +
    • +

      2 to 16 Mb L3 / Bcache (AS600; 3 cache-SIMM slots)

      +
      • +
    +
    • + +
  • +

    memory buswidth: 256 bits

    +
    • + +
  • +

    AS500 memory:

    + +
      +
    • +

      industry standard 72 bit wide buffered Fast Page Mode DIMMs

      +
      • + +
    • +

      8 DIMM slots

      +
      • + +
    • +

      installed in sets of 4

      +
      • + +
    • +

      maximum memory is 1 GB (512 Mb max on 333 MHz CPUs)

      +
      • + +
    • +

      uses ECC

      +
      • +
    +
    • + +
  • +

    AS600 memory:

    + +
      +
    • +

      industry standard 36 bit Fast Page Mode SIMMs

      +
      • + +
    • +

      32 SIMM slots

      +
      • + +
    • +

      installed in sets of 8

      +
      • + +
    • +

      maximum memory is 1 GB

      +
      • + +
    • +

      uses ECC

      +
      • +
    +
    • + +
  • +

    Qlogic 1020 based wide SCSI bus (1 bus/chip for AS500, 2 buses/chip for AS600)

    +
    • + +
  • +

    21040 based 10 Mbit Ethernet adapter, both Thinwire and UTP connectors

    +
    • + +
  • +

    expansion:

    + +
      +
    • +

      AS500:

      + +
        +
      • +

        3 32-bit PCI slots

        +
        • + +
      • +

        1 64-bit PCI slot

        +
        • +
      +
      • + +
    • +

      AS600:

      + +
        +
      • +

        2 32-bit PCI slot

        +
        • + +
      • +

        3 64-bit PCI slots

        +
        • + +
      • +

        1 PCI/EISA physically shared slot

        +
        • + +
      • +

        3 EISA slots

        +
        • + +
      • +

        1 PCI and 1 EISA slot are occupied by default

        +
        • +
      +
      • +
    +
    • + +
  • +

    21050 PCI-to-PCI bridge chip

    +
    • + +
  • +

    Intel 82375EB PCI-EISA bridge (AS600 only)

    +
    • + +
  • +

    2 16550A serial ports

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    16 bit audio Windows Sound System, in a dedicated slot (AS500) in EISA slot (AS600, +this is an ISA card)

    +
    • + +
  • +

    PS/2 keyboard and mouse port

    +
    • +
+ +

Early machines had Fast SCSI interfaces, later ones are Ultra SCSI capable. AS500 +shares its single SCSI bus with internal and external devices. For a Fast SCSI bus you +are limited to 1.8 meters bus length external to the box. The AS500 Qlogic ISP1020A chip +can be set to run in Ultra mode by setting a SRM variable. FreeBSD however follows the +Qlogic chip errata and limits the bus speed to Fast.

+ +

Beware of ancient SRM versions on AS500. When you see weird SCSI speeds being reported +by FreeBSD like

+ +
+cd0 at isp0 bus 0 target 4 lun 0
+cd0: <DEC RRD45   DEC 0436> Removable CD-ROM SCSI-2 device
+cd0: 250.000MB/s transfers (250.000MHz, offset 12)
+
+ +

it is time to do a SRM console firmware upgrade.

+ +

AS600 has one Qlogic SCSI chip dedicated to the internal devices whereas the other +Qlogic SCSI chip is dedicated to external SCSI devices. Keep the card, which apart from +the two SCSI interfaces also houses the Ethernet chip by the way in the DEC-recommended, +topmost, 32bit PCI slot. You get machine checks if you plug it into one of the 64 bit +slots.

+ +

In AS500 DIMMs are installed in sets of 4, in “physically interleaved” +layout. So, a bank of 4 DIMMs is not 4 physically adjacent DIMMs. Note that the DIMMs are +not SDRAM DIMMs.

+ +

In AS600 the memory SIMMs are placed onto two memory daughter cards. SIMMs are +installed in sets of 8. Both memory daughter cards must be populated identically.

+ +

Note that both AS500 and AS600 are EISA machines. This means you have to run the EISA +Configuration Utility (ECU) from floppy after adding EISA cards or to change things like +the configuration settings of the onboard I/O. For AS500 which does not have a physical +EISA slot the ECU is used to configure the onboard sound interface etc.

+ +

AS500 onboard sound can be used by adding a line like

+ +
+device pcm
+
+ +

to the kernel configuration file.

+ +

Using the ECU I configured my AS500 to use IRQ 10, port 0x530, drq 0. Corresponding +entries along with flags 0x10011 must go into the device.hints +file. Note that the flags value is rather non-standard.

+ +

AS600 has a peculiarity for its PCI slots. AS600 (or rather the PCI expansion card +containing the SCSI adapters) does not allow I/O port mapping, therefore all devices +behind it must use memory mapping. If you have problems getting the Qlogic SCSI adapters +to work, add the following option to /boot/loader.rc:

+ +
+set isp_mem_map=0xff
+
+ +

This may need to be typed at the boot loader prompt before booting the installation +kernel.

+ +

For the AlphaStation-[56]00 machines the kernel config file must contain:

+ +
+options    DEC_KN20AA 
+cpu EV5
+
+
+ +
+
+

2.3.7 AlphaServer 1000 +(“Mikasa”), 1000A (“Noritake”) and +800(“Corelle”)

+ +

The AlphaServer 1000 and 800 range of machines are intended as departmental servers. +They come in quite some variations in packaging and mainboard/cpu. Generally speaking +there are 21064 (EV4) CPU based machines and 21164 (EV5) based ones. The CPU is on a +daughter card, and the type of CPU (EV4 or EV5) must match the mainboard in use.

+ +

AlphaServer 800 has a much smaller mini tower case, it lacks the StorageWorks SCSI +hot-plug chassis. Instead, it has a disk cage that allows up to 4 fullheight 3.5" SCA +SCSI disks to be installed. The carriers used to mount the disks are specific to the +AlphaServer 800. The main difference between AS1000 and AS1000A is that AS1000A has 7 PCI +slots whereas AS1000 only has 3 PCI slots and has EISA slots instead.

+ +

The AlphaServer 800 system has a smart power controller. This means that parts of the +system remain powered when it is switched off (like an ATX-style PC power supply). Before +servicing the machine remove the power cord.

+ +

The smart power controller is called the RMC. When enabled, typing EscapeEscapeRMC on serial port 1 will bring you +to the RMC prompt. RMC allows you to powerup or powerdown, reset the machine, monitor and +set temperature trip levels etc. RMC has its own builtin help.

+ +

AlphaServer 800 with an EV5/400 MHz CPU was later re-branded to become a +“DIGITAL Server 3300[R]”, AlphaServer 800 with an EV5/500 MHz CPU was later +re-branded to become a “DIGITAL Server 3305[R]”.

+ +

Features:

+ +
    +
  • +

    21064 EV4[5] CPU at 200, 233 or 266 MHz 21164 EV5[6] CPU at 300, 333 or 400 MHz (or +500 MHz, for AS800 only)

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      buswidth: 128 bit with ECC

      +
      • + +
    • +

      AS1000[A]:

      + +
        +
      • +

        72pin 36 bit Fast Page Mode SIMMs, 70ns or better

        +
        • + +
      • +

        16 (EV5 machines) or 20 (EV4 machines) SIMM slots

        +
        • + +
      • +

        max memory is 1 GB

        +
        • + +
      • +

        uses ECC

        +
        • +
      +
      • + +
    • +

      AS800: Uses 60ns 3.3 Volts EDO DIMMs. 8 DIMM sockets are provided.

      +
      • +
    +
    • + +
  • +

    embedded VGA (on some mainboard models)

    +
    • + +
  • +

    3 PCI, 2 EISA, 1 64-bit PCI/EISA combo (AS800)

    +
    • + +
  • +

    7 PCI, 2 EISA (AS1000A)

    +
    • + +
  • +

    2 PCI, 1 EISA/PCI, 7 EISA (AS1000)

    +
    • + +
  • +

    embedded SCSI based on Symbios 810 [AS1000] or Qlogic 1020 [AS1000A]

    +
    • +
+ +

AS1000 based machines come in multiple enclosure types. Floor standing, rack-mount, +with or without StorageWorks SCSI chassis etc. The electronics are the same.

+ +

AS1000-systems: All EV4 based machines use standard PS/2 style 36 bit 72pin SIMMs in +sets of 5. The fifth SIMM is used for ECC. All EV5 based machines use standard PS/2 style +36 bit 72pin SIMMs in sets of 4. The ECC is done based on the 4 extra bits per SIMM (4 +bits out of 36). The EV5 mainboards have 16 SIMM slots, the EV4 mainboards have 20 +slots.

+ +

AS800 machines use DIMMs in sets of 4. DIMM installation must start in slots marked +bank 0. A bank is four physically adjacent slots. The biggest size DIMMs must be +installed in bank 0 in case 2 banks of different DIMM sizes are used. Max memory size is +2GB. Note that it uses buffered EDO DIMMs.

+ +

The AS1000/800 are somewhat stubborn when it comes to serial consoles. They need

+ +
+>>> SET CONSOLE SERIAL
+
+ +

before they go for a serial console. Pulling the keyboard from the machine is not +sufficient, like it is on most other Alpha models. Going back to a graphical console +needs

+ +
+>>> SET CONSOLE GRAPHICS
+
+ +

at the serial console.

+ +

For AS800 you want to check if your Ultra-Wide SCSI is indeed in Ultra mode. This can +be done using the EEROMCFG.EXE utility that is on the Console +Firmware Upgrade CDROM.

+ +

For the AlphaServer1000/1000A/800 machines the kernel config file must contain:

+ +
+options    DEC_1000A
+cpu EV4     # depends on the CPU model installed
+cpu EV5     # depends on the CPU model installed
+
+
+ +
+
+

2.3.8 DS10/VS10/XP900 +(“Webbrick”) / XP1000 (“Monet”) / DS10L +(“Slate”)

+ +

Webbrick and Monet are high performance workstations/servers based on the EV6 CPU and +the Tsunami chipset. Tsunami is also used in much higher-end systems and as such has +plenty of performance to offer. DS10, VS10 and XP900 are different names for essentially +the same system. The differences are the software and options that are supported. DS10L +is a DS10 based machine in a 1U high rackmount enclosure. DS10L is intended for ISPs and +for HPTC clusters (e.g. Beowulf)

+ +
+
+
2.3.8.1 “Webbrick / +Slate”
+ +
    +
  • +

    21264 EV6 CPU at 466 MHz

    +
    • + +
  • +

    L2 / Bcache: 2MB, ECC protected

    +
    • + +
  • +

    memory bus: 128 bit via crossbar, 1.3GB/sec memory bandwidth

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      industry standard 200 pin 83 MHz buffered ECC SDRAM DIMMs

      +
      • + +
    • +

      4 DIMM slots for DS10; 2GB max memory

      +
      • + +
    • +

      2 DIMM slots for DS10L; 1GB max memory

      +
      • + +
    • +

      DIMMs are installed in pairs of 2

      +
      • +
    +
    • + +
  • +

    21271 Core Logic chipset (“Tsunami”)

    +
    • + +
  • +

    2 on-board 21143 Fast Ethernet controllers

    +
    • + +
  • +

    AcerLabs M5237 (Aladdin-V) USB controller (disabled)

    +
    • + +
  • +

    AcerLabs M1533 PCI-ISA bridge

    +
    • + +
  • +

    AcerLabs Aladdin ATA-33 controller

    +
    • + +
  • +

    embedded dual EIDE

    +
    • + +
  • +

    expansion: 3 64-bit PCI slots and 1 32-bit PCI slot. DS10L has a single 64bit PCI +slot

    +
    • + +
  • +

    2 16550A serial ports

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    2 USB

    +
    • + +
  • +

    PS/2 keyboard & mouse port

    +
    • +
+ +

The system has a smart power controller. This means that parts of the system remain +powered when it is switched off (like an ATX-style PC power supply). Before servicing the +machine remove the power cord.

+ +

The smart power controller is called the RMC. When enabled, typing EscapeEscapeRMC on serial port 1 will bring you +to the RMC prompt. RMC allows you to powerup or powerdown, reset the machine, monitor and +set temperature trip levels etc. RMC has its own builtin help.

+ +

Webbrick is shipped in a desktop-style case similar to the older 21164 +“Maverick” workstations but this case offers much better access to the +components. If you intend to build a farm you can rackmount them in a 19-inch rack; they +are 3U high. Slate is 1U high but has only one PCI slot.

+ +

DS10 has 4 DIMM slots. DIMMs are installed as pairs. Please note that DIMM pairs are +not installed in adjacent DIMM sockets but rather physically interleaved. DIMM sizes of +32, 64, 128, 256 and 512 Mbytes are supported.

+ +

When 2 pairs of identical-sized DIMMs are installed DS10 will use memory interleaving +for increased performance. DS10L, which has only 2 DIMM slots cannot do interleaving.

+ +

Starting with SRM firmware version 5.9 you can boot from Adaptec 2940-series adapters +in addition to the usual set of Qlogic and Symbios/NCR adapters. KZPEA aka Adaptec 39160 +gives you dual channel LVD U160 SCSI which is bootable from SRM.

+ +

The base model comes with a FUJITSU 9.5GB ATA disk as its boot device. FreeBSD works +just fine using EIDE disks on Webbrick. DS10 has 2 IDE interfaces on the mainboard. +Machines destined for Tru64 Unix or VMS are standard equipped with Qlogic-driven +Ultra-SCSI disks

+ +

On the PCI bus 32 and 64 bit cards are supported, in 3.3V and 5V variants.

+ +

The USB ports are not supported and are disabled by the SRM console in all recent SRM +versions.

+ +

The kernel config file must contain:

+ +
+options    DEC_ST6600    
+cpu EV5
+
+ +
+
+

Note: Contrary to expectation there is no cpu EV6 +defined for inclusion in the kernel config file. The cpu EV5 is +mandatory to keep +config(8) +happy.

+
+
+
+ +
+
+
2.3.8.2 “Monet”
+ +
    +
  • +

    21264 EV6 at 500 MHz 21264 EV67 at 500 or 667 MHz (XP1000G, codenamed Brisbane) CPU is +mounted on a daughter-card which is field-upgradable

    +
    • + +
  • +

    L2 / Bcache: 4MB, ECC protected

    +
    • + +
  • +

    memory bus: 256 bit

    +
    • + +
  • +

    memory: 128 or 256 Mbytes 100 MHz (PC100) 168 pin JEDEC standard, registered ECC SDRAM +DIMMs

    +
    • + +
  • +

    21271 core logic chip set (“Tsunami”)

    +
    • + +
  • +

    1 on-board 21143 Ethernet controller

    +
    • + +
  • +

    Cypress 82C693 USB controller

    +
    • + +
  • +

    Cypress 82C693 PCI-ISA bridge

    +
    • + +
  • +

    Cypress 82C693 controller

    +
    • + +
  • +

    expansion: 2 independent PCI buses, driven by high-speed I/O channels called +“hoses”:

    + +
      +
    • +

      hose 0: (the upper 3 slots) 2 64-bit PCI slots 1 32-bit PCI slot

      +
      • + +
    • +

      hose 1: (the bottom 2 slots) 2 32-bit PCI slots (behind a 21154 PCI-PCI bridge)

      +
      • + +
    • +

      2 of the 64-bit PCI slots are for full-length cards

      +
      • + +
    • +

      all of the 32-bit PCI slots are for short cards

      +
      • + +
    • +

      1 of the 32-bit PCI slots is physically shared with an ISA slot

      +
      • + +
    • +

      all PCI slots run at 33MHz

      +
      • +
    +
    • + +
  • +

    1 Ultra-Wide SCSI port based on a Qlogic 1040 chip

    +
    • + +
  • +

    2 16550A serial port

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    PS/2 keyboard & mouse port

    +
    • + +
  • +

    embedded 16-bit ESS ES1888 sound chip

    +
    • + +
  • +

    2 USB ports

    +
    • + +
  • +

    graphics options: ELSA Gloria Synergy or DEC/Compaq PowerStorm 3D accelerator +cards

    +
    • +
+ +

Monet is housed in a mini-tower like enclosure quite similar to the Miata box.

+ +

The on-board Qlogic UW-SCSI chip supports up to 4 internal devices. There is no +external connector for the on-board SCSI.

+ +

For 500 MHz CPUs 83 MHz DIMMs will do. Compaq specifies PC100 DIMMs for all CPU +speeds. DIMMs are installed in sets of 4, starting with the DIMM slots marked +“0” Memory capacity is max 4 GB. DIMMs are installed “physically +interleaved”, note the markings of the slots. Memory bandwidth of Monet is twice +that of Webbrick. The DIMMs live on the CPU daughter-card. Note that the system uses ECC +RAM so you need DIMMs with 72 bits (not the generic PC-class 64 bit DIMMs)

+ +

The EIDE interface is usable / SRM bootable so FreeBSD can be rooted on an EIDE disk. +Although the Cypress chip has potential for 2 EIDE channels Monet uses only one of +them.

+ +

The USB interface is supported by FreeBSD.If you experience problems trying to use the +USB interface please check if the SRM variable usb_enable is +set to on. You can change this by performing:

+ +
+>>> SET USB_ENABLE ON
+
+ +
+
+

Important: Don"t try to use Symbios-chip based SCSI adapters in the PCI +slots connected to hose 1. There is a not-yet-found FreeBSD bug that prevents this from +working correctly.

+
+
+ +
+
+

Important: Not all VGA cards will work behind the PCI-PCI bridge (so in slots 4 +and 5). Only cards that implement VGA-legacy addressing correctly will work. Workaround +is to put the VGA card “before” the bridge.

+
+
+ +

The sound chip is not currently supported with FreeBSD.

+ +

The kernel config file must contain:

+ +
+options    DEC_ST6600    
+cpu EV5
+
+ +
+
+

Note: Contrary to expectation there is no cpu EV6 +defined for inclusion in the kernel config file. The cpu EV5 is +mandatory to keep +config(8) +happy.

+
+
+
+
+ +
+
+

2.3.9 DS20/DS20E +(“Goldrush”)

+ +

Features:

+ +
    +
  • +

    21264 EV6 CPU at 500, 667 or 833 MHz

    +
    • + +
  • +

    dual CPU capable machine

    +
    • + +
  • +

    L2 / Bcache: 4 Mbytes per CPU (500 MHz)

    + +

    L2 / Bcache: 8 Mbytes per CPU (667 and 833 MHz)

    +
    • + +
  • +

    memory bus: dual 256 bit wide with crossbar switch

    +
    • + +
  • +

    memory:

    + +
      +
    • +

      SDRAM DIMMs

      +
      • + +
    • +

      installed in sets of 4

      +
      • + +
    • +

      16 DIMM slots, max. 4GB

      +
      • + +
    • +

      uses ECC

      +
      • +
    +
    • + +
  • +

    21271 core logic chip set (“Tsunami”)

    +
    • + +
  • +

    embedded Adaptec AIC-7895 Wide Ultra SCSI

    +
    • + +
  • +

    expansion:

    + +
      +
    • +

      2 independent PCI buses, driven by high-speed I/O channels called +“hoses”

      +
      • + +
    • +

      6 64-bit PCI slots, 3 per hose

      +
      • + +
    • +

      1 ISA slot

      +
      • +
    +
    • +
+ +

DS20 needs

+ +
+>>> SET CONSOLE SERIAL
+
+ +

before it goes for a serial console. Pulling the keyboard from the machine is not +sufficient. Going back to a graphical console needs

+ +
+>>> SET CONSOLE GRAPHICS
+
+ +

at the serial console. Confusing is the fact that you will get SRM console output on +the graphics console with the console set to serial, but when FreeBSD boots it honors the +CONSOLE variable setting and all the boot messages as well as +the login prompt will go to the serial port.

+ +

The DS20 is housed in a fat cube-like enclosure. The enclosure also contains a +StorageWorks SCSI hot-swap shelf for a maximum of seven 3.5" SCSI devices. The DS20E +is in a sleeker case, and lacks the StorageWorks shelf. It can either be rackmounted or +floorstanding.

+ +

The system has a smart power controller. This means that parts of the system remain +powered when it is switched off (like an ATX-style PC power supply). Before servicing the +machine remove all power cord(s).

+ +

The smart power controller is called the RMC. When enabled, typing EscapeEscapeRMC on serial port 1 will bring you +to the RMC prompt. RMC allows you to powerup or powerdown, reset the machine, monitor and +set temperature trip levels etc. RMC has its own builtin help.

+ +

The embedded Adaptec SCSI on the DS20 is disabled and is therefore not usable under +FreeBSD. On the DS20E with recent SRM console code you can use them with FreeBSD.

+ +

Starting with SRM firmware version 5.9 you can boot from Adaptec 2940-series adapters +in addition to the usual set of Qlogic and Symbios/NCR adapters. This unfortunately does +not include the embedded Adaptec SCSI chips. You can use a KZPEA aka Adaptec 39160 for +dual channel LVD U160 SCSI, which is bootable from SRM. For a single channel LVD Ultra2 +SCSI adapter you can use a LSI Logic / Symbios Sym8952u card.

+ +

If you are using banks of DIMMs of different sizes the biggest DIMMs should be +installed in the DIMM slots marked 0 on the mainboard. The DIMM +slots should be filled “in order” so after bank 0 install in bank 1 and so +on.

+ +

Don't try to use Symbios-chip based SCSI adapters in the PCI slots connected to hose +1. There is a not-yet-found FreeBSD bug that prevents this from working correctly. DS20 +ships by default with a Symbios on hose 1 so you have to move this card before you can +install/boot FreeBSD on it.

+ +

The kernel config file must contain:

+ +
+options    DEC_ST6600    
+cpu EV5
+
+ +
+
+

Note: Contrary to expectation there is no cpu EV6 +defined for inclusion in the kernel config file. The cpu EV5 is +mandatory to keep +config(8) +happy.

+
+
+
+ +
+
+

2.3.10 AlphaPC 264DP / UP2000

+ +

UP2000 was built by Alpha Processor Inc.

+ +

Features:

+ +
    +
  • +

    21264 EV6 CPU at 670 or 750 MHz

    +
    • + +
  • +

    dual CPU capable

    +
    • + +
  • +

    L2 / Bcache: 4 Mbytes per CPU

    +
    • + +
  • +

    memory bus: 256 bit

    +
    • + +
  • +

    memory: SDRAM DIMMs installed in sets of 4, uses ECC, 16 DIMM slots, max. 4GB

    +
    • + +
  • +

    21272 core logic chip set (“Tsunami”)

    +
    • + +
  • +

    2 embedded Adaptec AIC7890/91 Wide Ultra2 SCSI chips

    +
    • + +
  • +

    2 embedded IDE based on Cypress 82C693 chips

    +
    • + +
  • +

    embedded USB via Cypress 82C693

    +
    • + +
  • +

    expansion:

    + +
      +
    • +

      2 independent PCI buses, driven by high-speed I/O channels called +“hoses”

      +
      • + +
    • +

      6 64-bit PCI slots, 3 per hose

      +
      • + +
    • +

      1 ISA slot

      +
      • +
    +
    • +
+ +

Currently a maximum of 2GB memory is supported by FreeBSD.

+ +

The on-board Adaptec SCSI HBAs are bootable on UP2000.

+ +

Busmaster DMA is supported on the first IDE interface only. The system can boot from +it's IDE hard drives and cdrom drives.

+ +

The kernel config file must contain:

+ +
+options    DEC_ST6600    
+cpu EV5
+
+ +
+
+

Note: Contrary to expectation there is no cpu EV6 +defined for inclusion in the kernel config file. The cpu EV5 is +mandatory to keep +config(8) +happy.

+
+
+
+ +
+
+

2.3.11 AlphaServer 2000 +(“DemiSable”), 2100 (“Sable”), 2100A +(“Lynx”)

+ +

The AlphaServer 2[01]00 machines are intended as departmental servers. This is medium +iron. They are multi-CPU machines, up to 2 CPUs (AS2000) or 4 CPUs (2100[A]) can be +installed. Both floor-standing and 19" rackmount boxes exist. Rackmount variations +have different numbers of I/O expansion slots, different max number of CPUs and different +maximum memory size. Some of the boxes come with an integral StorageWorks shelf to house +hot-swap SCSI disks. There was an upgrade program available to convert your Sable machine +into a Lynx by swapping the I/O backplane (the C-bus backplane remains). CPU upgrades +were available as well.

+ +
    +
  • +

    21064 EV4[5] CPU[s] at 200, 233, 275 MHz or 21164 EV5[6] CPU[s]s at 250, 300, 375, 400 +MHz

    +
    • + +
  • +

    cache: varies in size with the CPU model; 1, 4 or 8Mbyte per CPU

    +
    • + +
  • +

    embedded floppy controller driving a 2.88 Mbytes drive

    +
    • + +
  • +

    embedded 10Mbit 21040 Ethernet [AS2100 only]

    +
    • + +
  • +

    2 serial ports

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    PS/2 style keyboard & mouse port

    +
    • +
+ +

The CPUs spec-ed as 200 MHz are in reality running at 190 MHz. Maximum number of CPUs +is 4. All CPUs must be of the same type/speed.

+ +

If any of the processors are ever marked as failed, they will remain marked as failed +even after they have been replaced (or reseated) until you issue the command

+ +
+>>> CLEAR_ERROR ALL
+
+ +

on the SRM console and power-cycle the machine. This may be true for other modules (IO +and memory) as well, but it has not been verified.

+ +

The machines use dedicated memory boards. These boards live on a 128 bit C-bus shared +with the CPU boards. DemiSable supports up to 1GB, Sable up to 2GB. One of the memory bus +slots can either hold a CPU or a memory card. A 4 CPU machine can have a maximum of 2 +memory boards.

+ +

Some memory board models house SIMMs. These are called SIMM carriers. There are also +memory modules that have soldered-on memory chips instead of SIMMs. These are called +“flat memory modules”.

+ +

SIMM boards are used in sets of eight 72-pin 36 bit FPM memory of 70ns or faster. SIMM +types supported are 1M x36 bit (4 Mbyte), 2M x36bit (8 Mbyte) and 4M x36 bit (16 Mbyte). +Each memory board can house 4 banks of SIMMs. SIMM sizes can not be mixed on a single +memory board. The first memory module must be filled with SIMMs before starting to fill +the next memory module. Note that the spacing between the slots is not that big, so make +sure your SIMMs fit physically (before buying them..)

+ +

Both Lynx and Sable are somewhat stubborn when it comes to serial consoles. They +need

+ +
+>>> SET CONSOLE SERIAL
+
+ +

before they go for a serial console. Pulling the keyboard from the machine is not +sufficient, like it is on many other Alpha models. Going back to a graphical console +needs

+ +
+>>> SET CONSOLE GRAPHICS
+
+ +

at the serial console. On Lynx keep the VGA card in one of the primary PCI slots. EISA +VGA cards are not slot sensitive.

+ +

The machines are equipped with a small OCP (Operator Control Panel) LCD screen. On +this screen the self-test messages are displayed during system initialization. You can +put your own little text there by using the SRM:

+ +
+>>> SET OCP_TEXT "FreeBSD"
+     
+
+ +

The SRM

+ +
+>>> SHOW FRU
+
+ +

command produces an overview of your configuration with module serial numbers, +hardware revisions and error log counts.

+ +

Both Sable, DemiSable and Lynx have Symbios 810 based Fast SCSI on-board. Check if it +is set to Fast SCSI speed by

+ +
+>>> SHOW PKA0_FAST
+
+ +

When set to 1 it is negotiating for Fast speeds.

+ +
+>>> SET PKA0_FAST 1
+
+ +

enables Fast SCSI speeds.

+ +

AS2100[A] come equipped with a StorageWorks 7 slot SCSI cage. A second cage can be +added inside the cabinet. AS2000 has a single 7 slot SCSI cage, which cannot be expanded +with an additional one. Note that the slot locations in these cages map differently to +SCSI IDs compared to the standard StorageWorks shelves. Slot IDs from top to bottom are +0, 4, 1, 5, 2, 6, 3 when using a single bus configuration.

+ +

The cage can also be set to provide two independent SCSI buses. This is used for +embedded RAID controllers like the KZPSC (Mylex DAC960). Slot ID assignments for split +bus are, from top to bottom: 0A, 0B, 1A, 1B, 2A, 2B, 3A, 3B. Where A and B signify a SCSI +bus. In a single bus configuration the terminator module on the back of the SCSI cage is +on the TOP. The jumper module is on the BOTTOM. For split bus operation these two modules +are reversed. The terminator can be distinguished from the jumper by noting the chips on +the terminator. The jumper does not have any active components on it.

+ +

DemiSable has 7 EISA slots and 3 PCI slots. Sable has 8 EISA and 3 PCI slots. Lynx, +being newer, has 8 PCI and 3 EISA slots. The Lynx PCI slots are grouped in sets of 4. The +4 PCI slots closest to the CPU/memory slots are the primary slots, so logically before +the PCI bridge chip. Note that contrary to expectation the primary PCI slots are the +highest numbered ones (PCI4 - PCI7).

+ +

Make sure you run the EISA Configuration Utility (from floppy) when adding/change +expansion cards in EISA slots or after upgrading your console firmware. This is done by +inserting the ECU floppy and typing

+ +
+>>> RUNECU
+
+ +
+
+

Note: EISA slots are currently unsupported, but the Compaq Qvision EISA VGA +adapter is treated as an ISA device. It therefore works OK as a console.

+
+
+ +

A special Extended I/O module for use on the C-bus was planned-for. If they ever saw +daylight is unknown. In any case FreeBSD has never been verified with an ExtIO +module.

+ +

The machines can be equipped with redundant power supplies. Note that the enclosure is +equipped with interlock switches that switch off power when the enclosure is opened. The +system's cooling fans are speed controlled. When the machine has more than 2 CPUs and +more than 1 memory board dual power supplies are mandatory.

+ +

The kernel config file must contain:

+ +
+options    DEC_2100_A500
+cpu EV4 #dependent on CPU model installed
+cpu EV5 #dependent on CPU model installed
+
+
+ +
+
+

2.3.12 AlphaServer 4x00 +(“Rawhide”)

+ +

The AlphaServer 4x00 machines are intended as small enterprise servers. Expect a +30" high pedestal cabinet or alternatively the same system box in a 19" rack. +Rawhides are multi-CPU machines, up to 4 CPUs can be in a single machine. Basic disk +storage is housed in one or two StorageWorks shelves at the bottom of the pedestal. The +Rawhides intended for the NT market are designated DIGITAL Server 7300 (5/400 CPU), +DIGITAL Server 7305 (5/533 CPU). A trailing R on the part-number means a rackmount +variant.

+ +

Features:

+ +
    +
  • +

    21164 EV5 CPUs at 266, 300, 333 MHz or 21164A EV56 CPUs at 400, 466, 533, 600 Mhz

    +
    • + +
  • +

    cache: 4 Mbytes per CPU. EV5 300 MHz was also available cache-less. 8 Mbytes for EV56 +600Mhz

    +
    • + +
  • +

    memory bus: 128 bit with ECC

    +
    • + +
  • +

    embedded floppy controller

    +
    • + +
  • +

    2 serial ports

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    PS/2 style keyboard & mouse port

    +
    • +
+ +

Rawhide can be equipped with a variety of CPU modules. CPU modules exist in versions +with and without external cache. In all cases the CPU modules installed always must be of +the same speed. A mix of NT-only and full-blown Tru64/VMS CPUs works fine. It will +however result in the system reporting itself to the operating system as a Digital Server +730x (so the NT-only variant). FreeBSD does not care, but such a system will not allow +Tru64 or VMS to run.

+ +

Rawhide uses a maximum of 8 RAM modules. These modules are used in pairs and supply 72 +bits to the bus (this includes ECC bits). Memory can be EDO RAM or synchronous DRAM. A +fully populated AS4100 has 4 pairs of memory modules. The AS4000 model is limited to 2 +pairs of memory modules. Given the choice use SDRAM for best performance. The highest +capacity memory boards must be in the memory slots marked MEM0L and MEM0H. A mix of +memory board sizes is allowed. A mix of EDO and SDRAM works as well (assuming you don't +try to mix EDO and SDRAM in a single module pair). A mix of EDO and SDRAM results in the +entire memory subsystem running at +the slower EDO timing.

+ +

Rawhide has an embedded Symbios 810 chip that gives you a narrow fast-SCSI bus. +Generally only the SCSI CDROM is driven by this interface.

+ +

Rawhides are available with a 8 64-bit PCI / 3 EISA slot expansion backplanes (called +“Saddle” modules). There are 2 separate PCI buses, PCI0 and PCI1. PCI0 has 1 +dedicated PCI slot and (shared) 3 PCI/EISA slots. PCI0 also has a PCI/EISA bridge that +drives things like the serial and parallel ports, keyboard/mouse etc. PCI1 has 4 PCI +slots and a Symbios 810 SCSI chip. VGA console cards must be installed in a slot +connected to PCI0.

+ +

The current FreeBSD implementation has problems in handling PCI bridges. There is +currently a limited fix in place which allows for single level, single device PCI +bridges. The fix allows the use of the Digital supplied Qlogic SCSI card which sits +behind a 21054 PCI bridge chip.

+ +
+
+

Note: EISA slots are currently unsupported, but the Compaq Qvision EISA VGA +adapter is treated as an ISA device. It therefore works as a console. In case you use +EISA options in your machine you must run the EISA Configuration Utility (ECU) from +floppy. Do yourself a favor and use the Tru64/OpenVMS ECU, and not the WindowsNT ECU.

+
+
+ +

Rawhide employs an I2C based power controller system. If you want to be sure all power +is removed from the system remove all mains cables from the system.

+ +

Rawhide comes with RCM functionality, which means you can power it on/off remotely, +reset it etc. See also the description for the RMC in the DS10 section of this document. +RCM versus RMC is not a typo, the various documentation I consulted used both acronyms +interchangeably. Note that if you want remote power on/off to function you need to +connect a small DC adapter to the machine in order to have the RCM logic powered. You +need to supply 9-12V DC to the small inlet located next to the keyboard connector.

+ +

The kernel config file must contain:

+ +
+options    DEC_KN300
+cpu EV5
+
+
+ +
+
+

2.3.13 AlphaServer 1200 +(“Tincup”) and AlphaStation 1200 (“DaVinci”)

+ +

The AlphaServer 1200 machine is the successor to the AlphaServer 1000A. It uses the +same enclosure the 1000A uses, but the logic is based on the AlphaServer 4000 design. +These are multi-CPU machines, up to 2 CPUs can be in a single machine. Basic disk storage +is housed in a StorageWorks shelves The AS1200 intended for the NT market were designated +DIGITAL Server 5300 (5/400 CPU) and DIGITAL Server 5305 (5/533 CPU).

+ +

Features:

+ +
    +
  • +

    21164A EV56 CPUs at 400 or 533 Mhz

    +
    • + +
  • +

    cache: 4 Mbytes per CPU

    +
    • + +
  • +

    memory bus: 128 bit with ECC, DIMM memory on two memory daughter boards

    +
    • + +
  • +

    embedded floppy controller

    +
    • + +
  • +

    2 serial ports

    +
    • + +
  • +

    1 parallel port

    +
    • + +
  • +

    PS/2 style keyboard & mouse port

    +
    • +
+ +

AS1200 uses 2 memory daughter cards. On each of these cards are 8 DIMM slots. DIMMs +must be installed in pairs. The maximum memory size is 4 GBytes. Slots must be filled in +order and slot 0 must contain the largest size DIMM if different sized DIMMs are used. +AS1200 employs fixed starting addresses for DIMMs, each DIMM pair starts at a 512 Mbyte +boundary. This means that if DIMMs smaller than 256 Mbyte are used the system's physical +memory map will contain “holes”. Supported DIMM sizes are 64 Mbytes and 256 +Mbytes. The DIMMs are 72 bit SDRAM based, as the system employs ECC.

+ +
+
+

Note: FreeBSD currently supports up to 2GBytes

+
+
+ +

AS1200 has an embedded Symbios 810 drive Fast SCSI bus.

+ +

Tincup has 5 64-bit PCI slots, one 1 32-bit PCI slot and one EISA slot (which is +physically shared with one of the 64-bit PCI slots). There are 2 separate PCI buses, PCI0 +and PCI1. PCI0 has the 32-bit PCI slot and the 2 top-most 64-bit PCI slots. PCI0 also has +an Intel 82375EB PCI/EISA bridge that drives things like the serial and parallel ports, +keyboard/mouse etc. PCI1 has 4 64-bit PCI slots and a Symbios 810 SCSI chip. VGA console +cards must be installed in a slot connected to PCI0.

+ +

The system employs an I2C based power controller system. If you want to be sure all +power is removed from the system remove the mains cables from the system. Tincup uses +dual power supplies in load-sharing mode and not as a redundancy pair.

+ +

The kernel config file must contain:

+ +
+options    DEC_KN300
+cpu EV5
+
+
+ +
+
+

2.3.14 Alpha Processor Inc. +UP1000

+ +

The UP1000 is an ATX mainboard based on the 21264a CPU which itself lives in a Slot B +module. It is normally housed in an ATX tower enclosure.

+ +

Features:

+ +
    +
  • +

    21264a Alpha CPU at 600 or 700 MHz in a Slot B module (includes cooling fans)

    +
    • + +
  • +

    memory bus: 128 bits to the L2 cache, 64 bits from Slot B to the AMD-751

    +
    • + +
  • +

    on-board Bcache / L2 cache: 2MB (600Mhz) or 4MB (700Mhz)

    +
    • + +
  • +

    AMD AMD-751 (“Irongate”) system controller chip

    +
    • + +
  • +

    Acer Labs M1543C PCI-ISA bridge controller / super-IO chip

    +
    • + +
  • +

    PS/2 mouse & keyboard port

    +
    • + +
  • +

    memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 DIMM slots DIMM sizes supported are +64, 128 or 256 Mb in size

    +
    • + +
  • +

    2 16550A serial port

    +
    • + +
  • +

    1 ECP/EPP parallel port

    +
    • + +
  • +

    floppy interface

    +
    • + +
  • +

    2 embedded Ultra DMA33 IDE interface

    +
    • + +
  • +

    2 USB ports

    +
    • + +
  • +

    expansion:

    + +
      +
    • +

      4 32 bit PCI slots

      +
      • + +
    • +

      2 ISA slots

      +
      • + +
    • +

      1 AGP slot

      +
      • +
    +
    • +
+ +

Slot B is a box-like enclosure that houses a daughter-board for the CPU and cache. It +has 2 small fans for cooling. Loud fans..

+ +

The machine needs ECC capable DIMMs, so 72 bit ones. This does not appear to be +documented in the UP1000 docs. The system accesses the serial EEPROM on the DIMMs via the +SM bus. Note that if only a single DIMM is used it must be installed in slot 2. This is a bit counter-intuitive.

+ +

The UP1000 needs a 400Watt ATX power supply according to the manufacturer. This might +be a bit overly conservative/pessimistic judging from the power consumption of the board +& cpu. But as always you will have to take your expansion cards and peripherals into +account. The M1543C chip contains power management functionality & temperature +monitoring (via I2C / SM bus).

+ +

Chances are that your UP1000 comes by default with AlphaBios only. The SRM console +firmware is available from the Alpha Processor Inc. web site. It is currently available +in a beta version which was successfully used during the port of FreeBSD to the +UP1000.

+ +

The embedded Ultra DMA EIDE ports are bootable by the SRM console.

+ +

UP1000 SRM can boot off an Adaptec 294x adapter. Under high I/O load conditions +machine lockups have been observed using the Adaptec 294x. A Symbios 875 based card works +just fine, using the sym driver. Most likely other cards based on the Symbios chips that +the sym driver supports will work as well.

+ +

The USB interfaces are disabled by the SRM console and have not (yet) been tested with +FreeBSD.

+ +

For the UP1000 the kernel config file must contain:

+ +
+options    API_UP1000  # UP1000, UP1100 (Nautilus)
+cpu EV5
+
+
+ +
+
+

2.3.15 Alpha Processor Inc. +UP1100

+ +

The UP1100 is an ATX mainboard based on the 21264a CPU running at 600 MHz. It is +normally housed in an ATX tower enclosure.

+ +

Features:

+ +
    +
  • +

    21264a Alpha EV6 CPU at 600 or 700 MHz

    +
    • + +
  • +

    memory bus: 100MHz 64-bit (PC-100 SDRAM), 800 MB/s memory bandwidth

    +
    • + +
  • +

    on-board Bcache / L2 cache: 2Mb

    +
    • + +
  • +

    AMD AMD-751 (“Irongate”) system controller chip

    +
    • + +
  • +

    Acer Labs M1535D PCI-ISA bridge controller / super-IO chip

    +
    • + +
  • +

    PS/2 mouse & keyboard port

    +
    • + +
  • +

    memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 DIMM slots DIMM sizes supported are +64, 128 or 256 Mb in size

    +
    • + +
  • +

    2 16550A serial port

    +
    • + +
  • +

    1 ECP/EPP parallel port

    +
    • + +
  • +

    floppy interface

    +
    • + +
  • +

    2 embedded Ultra DMA66 IDE interface

    +
    • + +
  • +

    2 USB port

    +
    • + +
  • +

    expansion: 3 32 bit PCI slots and 1 AGP2x slot

    +
    • +
+ +

SRM console code comes standard with the UP1100. The SRM lives in 2Mbytes of flash +ROM.

+ +

The machine needs ECC capable DIMMs, so 72 bit ones. This does not appear to be +documented in the UP1100 docs. The system accesses the serial EEPROM on the DIMMs via the +SM bus. Note that if only a single DIMM is used it must be installed in slot 2. This is a bit counter-intuitive.

+ +

The UP1100 needs a 400Watt ATX power supply according to the manufacturer. This might +be a bit overly conservative/pessimistic judging from the power consumption of the board +& cpu. But as always you will have to take your expansion cards and peripherals into +account. The M1535D chip contains power management functionality & temperature +monitoring (via I2C / SM bus using a LM75 thermal sensor).

+ +

The UP1100 has an on-board 21143 10/100Mbit Ethernet interface.

+ +

The UP1100 is equipped with a SoundBlaster compatible audio interface. Whether it +works with FreeBSD is as of yet unknown.

+ +

The embedded Ultra DMA EIDE ports are bootable by the SRM console.

+ +

The UP1100 has 3 USB ports, 2 going external and one connected to the AGP port.

+ +

For the UP1100 the kernel config file must contain:

+ +
+options    API_UP1000  # UP1000, UP1100 (Nautilus)
+cpu EV5
+
+ +

Contrary to expectation there is no cpu EV6 defined for +inclusion in the kernel config file. The cpu EV5 is mandatory to +keep +config(8) +happy.

+
+ +
+
+

2.3.16 Alpha Processor Inc. CS20, Compaq +DS20L

+ +

The CS20 is a 19", 1U high rackmount server based on the 21264[ab] CPU. It can +have a maximum of 2 CPUs. Compaq sells the CS20 rebranded as the AlphaServer DS20L. DS20L +has 833MHz CPUs.

+ +

Features:

+ +
    +
  • +

    21264a Alpha CPU at 667 MHz or 21264b 833 MHz (max. 2 CPUs)

    +
    • + +
  • +

    memory bus: 100MHz 256-bit wide

    +
    • + +
  • +

    21271 Core Logic chipset (“Tsunami”)

    +
    • + +
  • +

    Acer Labs M1533 PCI-ISA bridge controller / super-IO chip

    +
    • + +
  • +

    PS/2 mouse & keyboard port

    +
    • + +
  • +

    memory: 168-pin PC100 PLL buffered/registered SDRAM DIMMS, 8 DIMM slots, uses ECC +memory, min 256 Mbytes / max 2 GBytes of memory

    +
    • + +
  • +

    2 16550A serial port

    +
    • + +
  • +

    1 ECP/EPP parallel port

    +
    • + +
  • +

    ALI M1543C Ultra DMA66 IDE interface

    +
    • + +
  • +

    embedded dual Intel 82559 10/100Mbit Ethernet

    +
    • + +
  • +

    embedded Symbios 53C1000 Ultra160 SCSI controller

    +
    • + +
  • +

    expansion: 2 64 bit PCI slots (2/3 length)

    +
    • +
+ +

SRM console code comes standard with the CS20. The SRM lives in 2Mbytes of flash +ROM.

+ +

The CS20 needs ECC capable DIMMs. Note that it uses buffered DIMMs.

+ +

The CS20 has an I2C based internal monitoring system for things like temperature, +fans, voltages etc. The I2C also supports “wake on LAN”.

+ +

Each PCI slot is connected to its own independent PCI bus on the Tsunami.

+ +

The embedded Ultra DMA EIDE ports are bootable by the SRM console.

+ +

The CS20 has an embedded slim-line IDE CD drive. There is a front-accessible bay for a +1" high 3.5" SCSI hard-disk drive with SCA connector.

+ +

Note that there is no floppy disk drive (or a connector to add one).

+ +

The kernel config file must contain:

+ +
+options    DEC_ST6600
+cpu EV5
+
+ +

Contrary to expectation there is no cpu EV6 defined for +inclusion in the kernel config file. The cpu EV5 is mandatory to +keep +config(8) +happy.

+
+ +
+
+

2.3.17 Compaq AlphaServer ES40 +(“Clipper”)

+ +

The ES40 is a SMP system that can have 1 - 4 21264 Alpha CPUs. With the maximum +configuration of 32GB of memory these systems are often deployed as heavy database +servers and are also found in HPTC compute farm environments.

+ +

Features:

+ +
    +
  • +

    21264 Alpha CPU at 500 (EV6), 667 (EV67) or 833 MHz (EV68) (max. 4 CPUs)

    +
    • + +
  • +

    memory bus: 256-bit wide

    +
    • + +
  • +

    21272 Core Logic chipset

    +
    • + +
  • +

    PS/2 mouse & keyboard port

    +
    • + +
  • +

    memory: 200-pin JEDEC standard SDRAM DIMMS, max 32 GBytes of memory

    +
    • + +
  • +

    2 16550A serial port

    +
    • + +
  • +

    1 ECP/EPP parallel port

    +
    • + +
  • +

    ALI M1543C Ultra DMA66 IDE interface

    +
    • + +
  • +

    expansion: 2 64 bit PCI buses

    +
    • +
+ +

SRM console code comes standard with the ES40.

+ +

ES40 comes with an ATA CDROM drive, but uses SCSI harddisks. The usual Symbios & +Qlogic adapters are bootable, as is the KZPEA aka Adaptec 39160 dual channel LVD U160 +adapter.

+ +

Memory is divided in 4 memory arrays which each contain a set of 4 SDRAM DIMMs. Each +DIMM is 72 bit wide and of the 100MHz speed variant. An array can contain 2 sets, so 8 +DIMMs max per array. The DIMMs live on Memory Mother Boards (MMBs). There are 2 MMB +models, with 4 and 8 DIMM sockets respectively. Each MMB provides half of the 256 bit +memory bus width to the CPUs. Given the myriad options for the memory configuration it is +advisable to check the system documentation for the optimum memory configuration.

+ +

Dependent on the model variation the ES40 has 6 or 10 64 bit PCI slots. This is +basically just means the same backplane with less connectors mounted.

+ +

ES40 has the same RMC remote power control as DS10 and DS20. See the description of +the RMC in the DS10 section of this document. Most variations of ES40 have multiple power +supplies, allowing for N+1 redundancy. When installing CPU cards you must unplug all +power cords, the CPU cards receive standby power from the power supplies. Maximum memory +configurations need more than the default number of powersupplies.

+ +

The kernel config file must contain:

+ +
+options   DEC_ST6600
+cpu     EV5
+
+ +

Contrary to expectation there is no cpu EV6 defined for +inclusion in the kernel config file. The cpu EV5 is mandatory to +keep +config(8) +happy.

+
+
+ +
+
+

2.4 Supported Hardware Overview

+ +

A word of caution: the installed base for FreeBSD is not nearly as large as for +FreeBSD/Intel. This means that the enormous variation of PCI/ISA expansion cards out +there has much less chance of having been tested on alpha than on Intel. This is not to +imply they are doomed to fail, just that the chance of running into something never +tested before is much higher. GENERIC contains things that are +known to work on Alpha only.

+ +

The PCI and ISA expansion busses are fully supported. Turbo Channel is not in GENERIC and has limited support (see the relevant machine model +info). The MCA bus is not supported. The EISA bus is not supported for use with EISA +expansion cards as the EISA support code is lacking. ISA cards in EISA slots are reported +to work. The Compaq Qvision EISA VGA card is driven in ISA mode and works OK as a +console.

+ +

1.44 Mbyte and 1.2 Mbyte floppy drives are supported. 2.88 Mbyte drives sometimes +found in Alpha machines are supported up to 1.44Mbyte.

+ +

ATA and ATAPI (IDE) devices are supported via the +ata(4) driver +framework. As most people run their Alphas with SCSI disks it is not as well tested as +SCSI. Be aware of boot-ability restrictions for IDE disks. See the machine specific +information.

+ +

There is full SCSI support via the CAM layer for Adaptec 2940x (AIC7xxx chip-based), +Qlogic family and Symbios. Those of you interested in U160 SCSI might want to take a look +at an Adaptec 39160 dual channel LVD U160 adapter. Compaq calls this a KZPEA adapter. +Recent Alpha models have SRM versions that can boot from them. In general be aware of the +machine-specific boot-ability issues for the various adapter models. Where known they are +listed in the individual machine descriptions.

+ +

The Qlogic QL2x00 FibreChannel host adapters are fully supported.

+ +

If you want to boot your Alpha over the Ethernet you will obviously need an Ethernet +card that the SRM console recognizes. This generally means you need a board with an 21x4x +Ethernet chip as that is what Digital used. These chips are driven by the FreeBSD de(4) (older driver) +or dc(4) (newer driver). +Some new SRM versions are known to recognize the Intel 8255x Ethernet chips as driven by +the FreeBSD +fxp(4) driver. +But beware: the +fxp(4) driver is +reported not to work correctly with FreeBSD/alpha (although it works excellently on +FreeBSD/x86).

+ +

In general the SRM console emulates a VGA-compatibility mode on PCI VGA cards. This +is, however, not guaranteed to work by Compaq/DEC for each and every card type out there. +When the SRM thinks the VGA is acceptable FreeBSD will be able to use it. The console +driver works just like on a FreeBSD/intel machine. Please note that VESA modes are not +supported on Alpha, so that leaves you with 80x25 consoles.

+ +

In some Alpha machines you will find video adapters based on TGA chips. TGA support in +FreeBSD is not as robust as it should be. In case of problems it is advisable to try +either a serial console or a plain VGA card.

+ +

The “PC standard” serial ports found on most Alphas are supported.

+ +

ISDN (i4b) is not supported on FreeBSD/alpha.

+
+ +
+
+

2.5 Further reading

+ +

An interesting overview of the history of the Alpha CPU can be found at http://www.alasir.com/alpha/alpha_history.html.

+
+ +
+
+

2.6 Acknowledgments

+ +

In compiling this file I used multiple information sources, but the NetBSD Web site proved to be an +invaluable source of information. If it wasn't for NetBSD/alpha there probably would not +be a FreeBSD/alpha in the first place.

+ +

People who kindly helped me create this section:

+ +
    +
  • +

    Andrew Gallatin

    +
    • + +
  • +

    Chuck Robey

    +
    • + +
  • +

    Matthew Jacob

    +
    • + +
  • +

    Michael Smith

    +
    • + +
  • +

    David O'Brien

    +
    • + +
  • +

    Christian Weisgerber

    +
    • + +
  • +

    Kazutaka YOKOTA

    +
    • + +
  • +

    Nick Maniscalco

    +
    • + +
  • +

    Eric Schnoebelen

    +
    • + +
  • +

    Peter van Dijk

    +
    • + +
  • +

    Peter Jeremy

    +
    • + +
  • +

    Dolf de Waal

    +
    • + +
  • +

    Wim Lemmers, ex-Compaq

    +
    • + +
  • +

    Wouter Brackman, Compaq

    +
    • + +
  • +

    Lodewijk van den Berg, Compaq

    +
    • +
+
+
+ +
+
+

3 Supported Devices

+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.17 +2007/09/13 16:25:43 brueffer Exp $ + +

This section describes the devices currently known to be supported by with FreeBSD on +the Alpha/AXP platform. 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

+ +

IDE/ATA controllers ( +ata(4) +driver)

+ +

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 2920

    +
    • + +
  • +

    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

    +
    • +
+ +

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

    +
    • +
+ +
+
+

Booting from these controllers is not supported due to SRM limitations.

+
+
+ +

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

    +
    • +
+ +

The +mfi(4) driver +supports the following hardware:

+ +
    +
  • +

    LSI MegaRAID SAS 8408E

    +
    • + +
  • +

    LSI MegaRAID SAS 8480E

    +
    • + +
  • +

    Dell PERC5/i

    +
    • +
+ +

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.

+ +
+
+

Booting from these controllers is not supported due to SRM limitations. DAC960 +controllers sold by Digital/Compaq for Alpha systems as part of the StorageWorks family, +e.g. KZPSC or KZPAC are bootable from SRM. Note that these cards used 2.x firmware. SRM +bootability of newer firmware is unknown.

+
+
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    LSI Logic AS1064, LSI Logic AS1068

    +
    • + +
  • +

    LSI Logic FC909 (1Gb/s Fibre Channel)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Dell PowerEdge 1750 thru 2850

    +
    • + +
  • +

    IBM eServer xSeries 335

    +
    • +
+ +

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

+ +

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)

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    ATAPI IDE interface ( +acd(4))

    +
    • +
+ +
+
+
+ +
+
+

3.2 Ethernet Interfaces

+ +

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

+ +
    +
  • +

    DEC/Intel 21143

    +
    • + +
  • +

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

    +
    • + +
  • +

    ASIX Electronics AX88140A and AX88141

    +
    • + +
  • +

    Conexant LANfinity RS7112 (miniPCI)

    +
    • + +
  • +

    Davicom DM9009, DM9100, DM9102 and DM9102A

    +
    • + +
  • +

    Lite-On 82c168 and 82c169 PNIC

    +
    • + +
  • +

    Lite-On/Macronix 82c115 PNIC II

    +
    • + +
  • +

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

    +
    • + +
  • +

    Xircom X3201 (cardbus only)

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Abocom FE2500

    +
    • + +
  • +

    Accton EN1217 (98715A)

    +
    • + +
  • +

    Accton EN2242 MiniPCI

    +
    • + +
  • +

    Adico AE310TX (98715A)

    +
    • + +
  • +

    Alfa Inc GFC2204 (ASIX AX88140A)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Built in DE500-BA on DEC Alpha workstations (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

    +
    • +
+ +

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

    +
    • +
+ +

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 and 82573 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 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)

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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 (32-bit PCI) and EG1064 (64-bit PCI)

    +
    • + +
  • +

    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)

    +
    • +
+ +

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

+ +
    +
  • +

    AMD Am79C971 PCnet-FAST

    +
    • + +
  • +

    AMD Am79C972 PCnet-FAST+

    +
    • + +
  • +

    AMD Am79C973/Am79C975 PCnet-FAST III

    +
    • + +
  • +

    AMD Am79C976 PCnet-PRO

    +
    • + +
  • +

    AMD Am79C978 PCnet-Home

    +
    • + +
  • +

    Allied-Telesis LA-PCI

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Compaq Evo N1015v Integrated Ethernet (8139C+)

    +
    • + +
  • +

    Corega CG-LAPCIGT Gigabit Ethernet (8169S)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

    +
    • + +
  • +

    LevelOne GNC-0105T (8169S)

    +
    • + +
  • +

    LinkSys EG1032 (32-bit PCI)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

Adapters supported by the rl(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

    Allied Telesyn AT2550

    +
    • + +
  • +

    Allied Telesyn AT2500TX

    +
    • + +
  • +

    Belkin F5D5000

    +
    • + +
  • +

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

    +
    • + +
  • +

    Compaq HNE-300

    +
    • + +
  • +

    CompUSA no-name 10/100 PCI Ethernet NIC

    +
    • + +
  • +

    Corega FEther CB-TXD

    +
    • + +
  • +

    Corega FEtherII CB-TXD

    +
    • + +
  • +

    D-Link DFE-528TX

    +
    • + +
  • +

    D-Link DFE-530TX+

    +
    • + +
  • +

    D-Link DFE-538TX

    +
    • + +
  • +

    D-Link DFE-690TXD

    +
    • + +
  • +

    Edimax EP-4103DL CardBus

    +
    • + +
  • +

    Encore ENL832-TX 10/100 M PCI

    +
    • + +
  • +

    Farallon NetLINE 10/100 PCI

    +
    • + +
  • +

    Genius GF100TXR

    +
    • + +
  • +

    GigaFast Ethernet EE100-AXP

    +
    • + +
  • +

    KTX-9130TX 10/100 Fast Ethernet

    +
    • + +
  • +

    LevelOne FPC-0106TX

    +
    • + +
  • +

    Longshine LCS-8038TX-R

    +
    • + +
  • +

    NDC Communications NE100TX-E

    +
    • + +
  • +

    Netronix Inc. EA-1210 NetEther 10/100

    +
    • + +
  • +

    Nortel Networks 10/100BaseTX

    +
    • + +
  • +

    OvisLink LEF-8129TX

    +
    • + +
  • +

    OvisLink LEF-8139TX

    +
    • + +
  • +

    Peppercon AG ROL-F

    +
    • + +
  • +

    Planex FNW-3603-TX

    +
    • + +
  • +

    Planex FNW-3800-TX

    +
    • + +
  • +

    SMC EZ Card 10/100 PCI 1211-TX

    +
    • + +
  • +

    SOHO (PRAGMATIC) UE-1211C

    +
    • +
+ +

Adapters supported by the sf(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    ANA-62020 64-bit single port 100baseFX adapter

    +
    • +
+ +

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

+ +
    +
  • +

    @Nifty FNECHARD IFC USUP-TX

    +
    • + +
  • +

    MELCO LGY-PCI-TXC

    +
    • + +
  • +

    Netgear FA311-TX (DP83815)

    +
    • + +
  • +

    Netgear FA312-TX (DP83815)

    +
    • + +
  • +

    SiS 630, 635, and 735 motherboard chipsets

    +
    • + +
  • +

    Soekris Engineering net45xx, net48xx, lan1621, and lan1641

    +
    • +
+ +

Adapters supported by the sk(4) driver +include:

+ +
    +
  • +

    3Com 3C940 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Belkin F5D5005 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Linksys EG1032 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

    +
    • +
+ +

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

+ +
    +
  • +

    D-Link DFE-530TXS

    +
    • + +
  • +

    D-Link DFE-550TX

    +
    • + +
  • +

    D-Link DFE-580TX

    +
    • +
+ +

The 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

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

    AOpen/Acer ALN-320

    +
    • + +
  • +

    D-Link DFE530-TX

    +
    • + +
  • +

    Hawking Technologies PN102TX

    +
    • +
+ +

The wb(4) driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:

+ +
    +
  • +

    Trendware TE100-PCIE

    +
    • +
+ +

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

+
+ +
+
+

3.3 Token Ring Interfaces

+
+ +
+
+

3.4 FDDI Interfaces

+ +

DEC DEFPA PCI ( +fpa(4) +driver)

+
+ +
+
+

3.5 ATM Interfaces

+
+ +
+
+

3.6 Wireless Network Interfaces

+ +

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

+ +

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

+
+ +
+
+

3.7 Miscellaneous +Networks

+
+ +
+
+

3.8 ISDN Interfaces

+
+ +
+
+

3.9 Serial Interfaces

+ +

“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

    +
    • + +
  • +

    SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.

    +
    • + +
  • +

    Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.

    +
    • +
+ +

AST 4 port serial card using shared IRQ

+ +

Comtrol Rocketport card (rp(4) driver)

+
+ +
+
+

3.10 Sound Devices

+ +

The +snd_maestro(4) +driver supports the following PCI sound cards:

+ +
    +
  • +

    ESS Technology Maestro-1

    +
    • + +
  • +

    ESS Technology Maestro-2

    +
    • + +
  • +

    ESS Technology Maestro-2E

    +
    • +
+ +

The +snd_maestro3(4) +driver supports the following audio devices:

+ +
    +
  • +

    ESS Technology Allegro-1

    +
    • + +
  • +

    ESS Technology Maestro3

    +
    • +
+ +

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

    +
    • +
+
+ +
+
+

3.11 Camera and Video Capture +Devices

+
+ +
+
+

3.12 USB Devices

+ +

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

+ +
+
+

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

+
+
+ +
+
+

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

+
+
+ +

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)

    +
    • +
+ +

The +uhci(4) driver +supports all UHCI v1.1 compliant controllers including:

+ +
    +
  • +

    Intel 82371AB/EB (PIIX4)

    +
    • + +
  • +

    Intel 82371SB (PIIX3)

    +
    • + +
  • +

    VIA 83C572

    +
    • +
+ +

Hubs

+ +

Keyboards ( +ukbd(4) +driver)

+ +

Mice ( +ums(4) +driver)

+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    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

    +
    • +
+
+ +
+
+

3.13 IEEE 1394 (Firewire) +Devices

+
+ +
+
+

3.14 Bluetooth Devices

+
+ +
+
+

3.15 Cryptographic +Accelerators

+
+ +
+
+

3.16 Miscellaneous

+ +

Floppy drives ( +fdc(4) +driver)

+ +

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

+
+
+ +
+
+

Keyboards including:

+ + + +
+
+

Pointing devices including:

+ +
    +
  • +

    PS/2 mice and compatible devices, including many laptop pointing devices ( +psm(4) +driver)

    +
    • + +
  • +

    Serial mice and compatible devices

    +
    • + +
  • +

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

+
+
+ +
+
+

“PC standard” parallel ports ( +ppc(4) +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/en/releases/6.3R/hardware-amd64.html b/en/releases/6.3R/hardware-amd64.html new file mode 100644 index 0000000000..b2934702bd --- /dev/null +++ b/en/releases/6.3R/hardware-amd64.html @@ -0,0 +1,6670 @@ + + + + +FreeBSD/amd64 6.3-RELEASE Hardware Notes + + + + + +
+
+

FreeBSD/amd64 6.3-RELEASE Hardware +Notes

+ +

The FreeBSD Documentation Project

+ +

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

+ +
+
+ +
+
+
Table of Contents
+ +
1 Introduction
+ +
2 Supported Processors and Motherboards
+ +
3 Supported Devices
+ +
+
+
3.1 Disk Controllers
+ +
3.2 Ethernet Interfaces
+ +
3.3 Token Ring Interfaces
+ +
3.4 FDDI Interfaces
+ +
3.5 ATM Interfaces
+ +
3.6 Wireless Network Interfaces
+ +
3.7 Miscellaneous Networks
+ +
3.8 ISDN Interfaces
+ +
3.9 Serial Interfaces
+ +
3.10 Sound Devices
+ +
3.11 Camera and Video Capture Devices
+ +
3.12 USB Devices
+ +
3.13 IEEE 1394 (Firewire) Devices
+ +
3.14 Bluetooth Devices
+ +
3.15 Cryptographic Accelerators
+ +
3.16 Miscellaneous
+
+
+
+
+ +
+

1 Introduction

+ +

This document contains the hardware compatibility notes for FreeBSD 6.3-RELEASE on the +AMD64 hardware platform (also referred to as FreeBSD/amd64 6.3-RELEASE). It lists devices +known to work on this platform, as well as some notes on boot-time kernel customization +that may be useful when attempting to configure support for new devices.

+ +
+
+

Note: This document includes information specific to the AMD64 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.

+
+
+
+ +
+
+

2 Supported Processors and +Motherboards

+ +

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 Athlon64 (“Clawhammer”).

    +
    • + +
  • +

    AMD Opteron (“Sledgehammer”).

    +
    • + +
  • +

    Intel 64-bit Xeon (“Nacona”). This processor is fabricated on 90nm process +technology, and operates with 2.80 to 3.60 GHz (FSB 800MHz) and Intel E7520/E7525/E7320 +chipsets.

    +
    • + +
  • +

    Intel Pentium 4 Processor supporting Intel EM64T (“Prescott”). This is +fabricated on 90nm process technology, uses FC-LGA775 package, and operates with +3.20F/3.40F/3.60F GHz and Intel 925X Express chipsets. The corresponding S-Spec numbers +are SL7L9, SL7L8, SL7LA, SL7NZ, SL7PZ, and SL7PX. Note that processors marked as 5xx +numbers do not support EM64T.

    +
    • +
+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+

3 Supported Devices

+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.17 +2007/09/13 16:25:43 brueffer Exp $ + +

This section describes the devices currently known to be supported by with FreeBSD on +the AMD64 platform. 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

+ +

IDE/ATA controllers ( +ata(4) +driver)

+ +

Controllers supported by the +aac(4) driver +include:

+ +
    +
  • +

    Adaptec AAC-364

    +
    • + +
  • +

    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

    +
    • +
+ +

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)

    +
    • +
+ +

The +adw(4) driver +supports SCSI controllers including:

+ +
    +
  • +

    AdvanSys ABP940UW/ABP3940UW

    +
    • + +
  • +

    AdvanSys ABP950UW

    +
    • + +
  • +

    AdvanSys ABP970UW

    +
    • + +
  • +

    AdvanSys ABP3940U2W

    +
    • + +
  • +

    AdvanSys ABP3950U2W

    +
    • +
+ +

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 2920

    +
    • + +
  • +

    Adaptec 2930C

    +
    • + +
  • +

    Adaptec 2930U2

    +
    • + +
  • +

    Adaptec 2940

    +
    • + +
  • +

    Adaptec 2940J

    +
    • + +
  • +

    Adaptec 2940N

    +
    • + +
  • +

    Adaptec 2940U

    +
    • + +
  • +

    Adaptec 2940AU

    +
    • + +
  • +

    Adaptec 2940UW

    +
    • + +
  • +

    Adaptec 2940UW Dual

    +
    • + +
  • +

    Adaptec 2940UW Pro

    +
    • + +
  • +

    Adaptec 2940U2W

    +
    • + +
  • +

    Adaptec 2940U2B

    +
    • + +
  • +

    Adaptec 2950U2W

    +
    • + +
  • +

    Adaptec 2950U2B

    +
    • + +
  • +

    Adaptec 19160B

    +
    • + +
  • +

    Adaptec 29160B

    +
    • + +
  • +

    Adaptec 29160N

    +
    • + +
  • +

    Adaptec 3940

    +
    • + +
  • +

    Adaptec 3940U

    +
    • + +
  • +

    Adaptec 3940AU

    +
    • + +
  • +

    Adaptec 3940UW

    +
    • + +
  • +

    Adaptec 3940AUW

    +
    • + +
  • +

    Adaptec 3940U2W

    +
    • + +
  • +

    Adaptec 3950U2

    +
    • + +
  • +

    Adaptec 3960

    +
    • + +
  • +

    Adaptec 39160

    +
    • + +
  • +

    Adaptec 3985

    +
    • + +
  • +

    Adaptec 4944UW

    +
    • + +
  • +

    NEC PC-9821Xt13 (PC-98)

    +
    • + +
  • +

    NEC RvII26 (PC-98)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Many motherboards with on-board SCSI support

    +
    • +
+ +

The +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

    +
    • +
+ +

The adapters supported by the +aic(4) driver +include:

+ +
    +
  • +

    Adaptec AHA-1505 (ISA)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Adaptec AHA-1535 (ISA)

    +
    • + +
  • +

    Creative Labs SoundBlaster SCSI host adapter (ISA)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    NEC PC-9801-100 (PC98)

    +
    • +
+ +

Controllers supported by the +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

    +
    • +
+ +
+
+

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

+
+
+ +

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-1210

    +
    • + +
  • +

    ARC-1220

    +
    • + +
  • +

    ARC-1230

    +
    • + +
  • +

    ARC-1260

    +
    • + +
  • +

    ARC-1280

    +
    • + +
  • +

    ARC-1210ML

    +
    • + +
  • +

    ARC-1220ML

    +
    • + +
  • +

    ARC-1231ML

    +
    • + +
  • +

    ARC-1261ML

    +
    • + +
  • +

    ARC-1280ML

    +
    • +
+ +

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.

+ +

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 P400

    +
    • + +
  • +

    HP Smart Array P400i

    +
    • + +
  • +

    HP Smart Array P600

    +
    • + +
  • +

    HP Smart Array P800

    +
    • + +
  • +

    HP Modular Smart Array 20 (MSA20)

    +
    • + +
  • +

    HP Modular Smart Array 500 (MSA500)

    +
    • +
+ +

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

    +
    • +
+ +

The +hptmv(4) driver +supports the following ATA RAID controllers:

+ +
    +
  • +

    HighPoint's RocketRAID 182x series

    +
    • +
+ +

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.

+ +

Controllers supported by the +ips(4) driver +include:

+ +
    +
  • +

    IBM ServeRAID 3H

    +
    • + +
  • +

    ServeRAID 4L/4M/4H

    +
    • + +
  • +

    ServeRAID Series 5

    +
    • + +
  • +

    ServeRAID 6i/6M

    +
    • + +
  • +

    ServeRAID 7t/7k/7M

    +
    • +
+ +

Cards supported by the +isp(4) driver +include:

+ +
    +
  • +

    ISP1000

    +
    • + +
  • +

    ISP1020

    +
    • + +
  • +

    ISP1040

    +
    • + +
  • +

    Qlogic 1240

    +
    • + +
  • +

    Qlogic 1020

    +
    • + +
  • +

    Qlogic 1040

    +
    • + +
  • +

    Qlogic 1080

    +
    • + +
  • +

    Qlogic 1280

    +
    • + +
  • +

    Qlogic 12160

    +
    • + +
  • +

    Qlogic 210X

    +
    • + +
  • +

    Qlogic 220X

    +
    • + +
  • +

    Qlogic 2300

    +
    • + +
  • +

    Qlogic 2312

    +
    • + +
  • +

    Qlogic 234X

    +
    • + +
  • +

    Qlogic 2322

    +
    • + +
  • +

    Qlogic 200

    +
    • + +
  • +

    Qlogic 2422

    +
    • + +
  • +

    Qlogic 2432

    +
    • +
+ +

The +mfi(4) driver +supports the following hardware:

+ +
    +
  • +

    LSI MegaRAID SAS 8408E

    +
    • + +
  • +

    LSI MegaRAID SAS 8480E

    +
    • + +
  • +

    Dell PERC5/i

    +
    • +
+ +

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: Booting from these controllers is supported. EISA adapters are not +supported.

+
+
+ +

Controllers supported by the +mly(4) driver +include:

+ +
    +
  • +

    Mylex AcceleRAID 160

    +
    • + +
  • +

    Mylex AcceleRAID 170

    +
    • + +
  • +

    Mylex AcceleRAID 352

    +
    • + +
  • +

    Mylex eXtremeRAID 2000

    +
    • + +
  • +

    Mylex eXtremeRAID 3000

    +
    • +
+ +

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

+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    LSI Logic AS1064, LSI Logic AS1068

    +
    • + +
  • +

    LSI Logic FC909 (1Gb/s Fibre Channel)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Dell PowerEdge 1750 thru 2850

    +
    • + +
  • +

    IBM eServer xSeries 335

    +
    • +
+ +

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

+ +

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)

    +
    • +
+ +

The +rr232x(4) driver +supports the following hardware:

+ +
    +
  • +

    HighPoint RocketRAID 2320

    +
    • + +
  • +

    HighPoint RocketRAID 2322

    +
    • +
+ +

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

    +
    • +
+ +

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.

+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    ATAPI IDE interface ( +acd(4))

    +
    • +
+ +
+
+
+ +
+
+

3.2 Ethernet Interfaces

+ +

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

    +
    • +
+ +

The +axe(4) driver +supports ASIX Electronics AX88172 based USB Ethernet adapters including:

+ +
    +
  • +

    Buffalo (Melco Inc.) LUA-U2-KTX

    +
    • + +
  • +

    D-Link DUB-E100, revision A

    +
    • + +
  • +

    LinkSys USB200M

    +
    • + +
  • +

    Netgear FA120

    +
    • + +
  • +

    Sitecom LN-029

    +
    • + +
  • +

    System TALKS Inc. SGC-X2UL

    +
    • +
+ +

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

+ +
    +
  • +

    HP NC370T Multifunction Gigabit Server Adapter

    +
    • + +
  • +

    HP NC370i Multifunction Gigabit Server Adapter

    +
    • +
+ +

Broadcom BCM4401 based Fast Ethernet adapters ( +bfe(4) +driver)

+ +

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)

    +
    • + +
  • +

    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 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 +cue(4) driver +supports CATC USB-EL1210A based USB Ethernet adapters including:

+ +
    +
  • +

    Belkin F5U011/F5U111

    +
    • + +
  • +

    CATC Netmate

    +
    • + +
  • +

    CATC Netmate II

    +
    • + +
  • +

    SmartBridges SmartLink

    +
    • +
+ +

Crystal Semiconductor CS89x0-based NICs (cs(4) driver)

+ +

The +cxgb(4) driver +supports 10 Gigabit Ethernet adapters based on the T3 and T3B chipset:

+ +
    +
  • +

    Chelsio 10GBase-CX4

    +
    • + +
  • +

    Chelsio 10GBase-LR

    +
    • + +
  • +

    Chelsio 10GBase-SR

    +
    • +
+ +

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

+ +
    +
  • +

    DEC/Intel 21143

    +
    • + +
  • +

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

    +
    • + +
  • +

    ASIX Electronics AX88140A and AX88141

    +
    • + +
  • +

    Conexant LANfinity RS7112 (miniPCI)

    +
    • + +
  • +

    Davicom DM9009, DM9100, DM9102 and DM9102A

    +
    • + +
  • +

    Lite-On 82c168 and 82c169 PNIC

    +
    • + +
  • +

    Lite-On/Macronix 82c115 PNIC II

    +
    • + +
  • +

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

    +
    • + +
  • +

    Xircom X3201 (cardbus only)

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Abocom FE2500

    +
    • + +
  • +

    Accton EN1217 (98715A)

    +
    • + +
  • +

    Accton EN2242 MiniPCI

    +
    • + +
  • +

    Adico AE310TX (98715A)

    +
    • + +
  • +

    Alfa Inc GFC2204 (ASIX AX88140A)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Built in DE500-BA on DEC Alpha workstations (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

    +
    • +
+ +

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

    +
    • +
+ +

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 and 82573 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 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)

    +
    • +
+ +

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)

    +
    • +
+ +

The ex(4) driver supports +the following Ethernet adapters:

+ +
    +
  • +

    Intel EtherExpress Pro/10

    +
    • + +
  • +

    Intel EtherExpress Pro/10+

    +
    • + +
  • +

    The Olicom OC2220

    +
    • +
+ +

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 PCMCIA Ethernet

    +
    • + +
  • +

    Eagle Tech NE200T

    +
    • + +
  • +

    Eiger Labs EPX-10BT

    +
    • + +
  • +

    Fujitsu FMV-J182, FMV-J182A

    +
    • + +
  • +

    Fujitsu MB86960A, MB86965A

    +
    • + +
  • +

    Fujitsu MBH10303, MBH10302 Ethernet PCMCIA

    +
    • + +
  • +

    Fujitsu Towa LA501 Ethernet

    +
    • + +
  • +

    HITACHI HT-4840-11

    +
    • + +
  • +

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

    +
    • +
+ +

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

    +
    • +
+ +

The +ixgb(4) driver +supports the following cards:

+ +
    +
  • +

    Intel PRO/10GbE LR Server Adapter

    +
    • + +
  • +

    Intel PRO/10GbE SR Server Adapter

    +
    • +
+ +

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

    +
    • +
+ +

Adapters supported by the +lge(4) driver +include:

+ +
    +
  • +

    SMC TigerCard 1000 (SMC9462SX)

    +
    • + +
  • +

    D-Link DGE-500SX

    +
    • +
+ +

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

+ +
    +
  • +

    D-Link 550SX Gigabit Ethernet

    +
    • + +
  • +

    D-Link 560T Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8021CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8021 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8022CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8022 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8061CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8061 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8062CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8062 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8035 Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8036 Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8038 Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8039 Gigabit 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

    +
    • + +
  • +

    SysKonnect SK-9Sxx Gigabit Ethernet

    +
    • + +
  • +

    SysKonnect SK-9Exx Gigabit Ethernet

    +
    • +
+ +

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)

    +
    • +
+ +

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 (32-bit PCI) and EG1064 (64-bit PCI)

    +
    • + +
  • +

    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)

    +
    • +
+ +

The +nve(4) driver +supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets:

+ +
    +
  • +

    nForce

    +
    • + +
  • +

    nForce2

    +
    • + +
  • +

    nForce3

    +
    • + +
  • +

    nForce4

    +
    • +
+ +

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

+ +
    +
  • +

    AMD Am79C971 PCnet-FAST

    +
    • + +
  • +

    AMD Am79C972 PCnet-FAST+

    +
    • + +
  • +

    AMD Am79C973/Am79C975 PCnet-FAST III

    +
    • + +
  • +

    AMD Am79C976 PCnet-PRO

    +
    • + +
  • +

    AMD Am79C978 PCnet-Home

    +
    • + +
  • +

    Allied-Telesis LA-PCI

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Compaq Evo N1015v Integrated Ethernet (8139C+)

    +
    • + +
  • +

    Corega CG-LAPCIGT Gigabit Ethernet (8169S)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

    +
    • + +
  • +

    LevelOne GNC-0105T (8169S)

    +
    • + +
  • +

    LinkSys EG1032 (32-bit PCI)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

Adapters supported by the rl(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

    Allied Telesyn AT2550

    +
    • + +
  • +

    Allied Telesyn AT2500TX

    +
    • + +
  • +

    Belkin F5D5000

    +
    • + +
  • +

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

    +
    • + +
  • +

    Compaq HNE-300

    +
    • + +
  • +

    CompUSA no-name 10/100 PCI Ethernet NIC

    +
    • + +
  • +

    Corega FEther CB-TXD

    +
    • + +
  • +

    Corega FEtherII CB-TXD

    +
    • + +
  • +

    D-Link DFE-528TX

    +
    • + +
  • +

    D-Link DFE-530TX+

    +
    • + +
  • +

    D-Link DFE-538TX

    +
    • + +
  • +

    D-Link DFE-690TXD

    +
    • + +
  • +

    Edimax EP-4103DL CardBus

    +
    • + +
  • +

    Encore ENL832-TX 10/100 M PCI

    +
    • + +
  • +

    Farallon NetLINE 10/100 PCI

    +
    • + +
  • +

    Genius GF100TXR

    +
    • + +
  • +

    GigaFast Ethernet EE100-AXP

    +
    • + +
  • +

    KTX-9130TX 10/100 Fast Ethernet

    +
    • + +
  • +

    LevelOne FPC-0106TX

    +
    • + +
  • +

    Longshine LCS-8038TX-R

    +
    • + +
  • +

    NDC Communications NE100TX-E

    +
    • + +
  • +

    Netronix Inc. EA-1210 NetEther 10/100

    +
    • + +
  • +

    Nortel Networks 10/100BaseTX

    +
    • + +
  • +

    OvisLink LEF-8129TX

    +
    • + +
  • +

    OvisLink LEF-8139TX

    +
    • + +
  • +

    Peppercon AG ROL-F

    +
    • + +
  • +

    Planex FNW-3603-TX

    +
    • + +
  • +

    Planex FNW-3800-TX

    +
    • + +
  • +

    SMC EZ Card 10/100 PCI 1211-TX

    +
    • + +
  • +

    SOHO (PRAGMATIC) UE-1211C

    +
    • +
+ +

The +rue(4) driver +supports RealTek RTL8150 based USB Ethernet adapters including:

+ +
    +
  • +

    Buffalo (Melco Inc.) LUA-KTX

    +
    • + +
  • +

    Green House GH-USB100B

    +
    • + +
  • +

    LinkSys USB100M

    +
    • + +
  • +

    Billionton 10/100 FastEthernet USBKR2

    +
    • +
+ +

Adapters supported by the sf(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    ANA-62020 64-bit single port 100baseFX adapter

    +
    • +
+ +

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

+ +
    +
  • +

    @Nifty FNECHARD IFC USUP-TX

    +
    • + +
  • +

    MELCO LGY-PCI-TXC

    +
    • + +
  • +

    Netgear FA311-TX (DP83815)

    +
    • + +
  • +

    Netgear FA312-TX (DP83815)

    +
    • + +
  • +

    SiS 630, 635, and 735 motherboard chipsets

    +
    • + +
  • +

    Soekris Engineering net45xx, net48xx, lan1621, and lan1641

    +
    • +
+ +

Adapters supported by the sk(4) driver +include:

+ +
    +
  • +

    3Com 3C940 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Belkin F5D5005 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Linksys EG1032 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

    +
    • +
+ +

The sn(4) driver supports +SMC91Cxx based ISA and PCMCIA cards including:

+ +
    +
  • +

    3Com Megahertz X-Jack Ethernet PC-Card XJ10BT

    +
    • + +
  • +

    3Com Megahertz X-Jack Ethernet PC-Card XJ10BC

    +
    • + +
  • +

    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.

+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

    D-Link DFE-530TXS

    +
    • + +
  • +

    D-Link DFE-550TX

    +
    • + +
  • +

    D-Link DFE-580TX

    +
    • +
+ +

The 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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

The +udav(4) driver +supports the following adapters:

+ +
    +
  • +

    Corega FEther USB-TXC

    +
    • +
+ +

The +vge(4) driver +supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including:

+ +
    +
  • +

    VIA Networking LAN-on-motherboard Gigabit Ethernet

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    AOpen/Acer ALN-320

    +
    • + +
  • +

    D-Link DFE530-TX

    +
    • + +
  • +

    Hawking Technologies PN102TX

    +
    • +
+ +

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

    +
    • +
+ +

The wb(4) driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:

+ +
    +
  • +

    Trendware TE100-PCIE

    +
    • +
+ +

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

+
+ +
+
+

3.3 Token Ring Interfaces

+
+ +
+
+

3.4 FDDI Interfaces

+
+ +
+
+

3.5 ATM Interfaces

+
+ +
+
+

3.6 Wireless Network Interfaces

+ +

Cisco/Aironet 802.11b wireless adapters (an(4) driver)

+ +

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

+ +

Cards supported by the +awi(4) driver +include:

+ +
    +
  • +

    BayStack 650

    +
    • + +
  • +

    BayStack 660

    +
    • + +
  • +

    Icom SL-200

    +
    • + +
  • +

    Melco WLI-PCM

    +
    • + +
  • +

    NEL SSMagic

    +
    • + +
  • +

    Netwave AirSurfer Plus

    +
    • + +
  • +

    Netwave AirSurfer Pro

    +
    • + +
  • +

    Nokia C020 WLAN

    +
    • + +
  • +

    Farallon SkyLINE

    +
    • +
+ +

The original Xircom Netwave AirSurfer is supported by the cnw(4) driver.

+ +

Cards supported by the +cnw(4) driver +include:

+ +
    +
  • +

    Xircom CreditCard Netwave

    +
    • + +
  • +

    NetWave AirSurfer

    +
    • +
+ +

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

+ +

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

+ +
    +
  • +

    A-Link WL54H

    +
    • + +
  • +

    A-Link WL54PC

    +
    • + +
  • +

    AirLink101 AWLC5025

    +
    • + +
  • +

    AirLink101 AWLH5025

    +
    • + +
  • +

    Amigo AWI-914W

    +
    • + +
  • +

    Amigo AWI-922W

    +
    • + +
  • +

    Amigo AWI-926W

    +
    • + +
  • +

    AMIT WL531C

    +
    • + +
  • +

    AMIT WL531P

    +
    • + +
  • +

    AOpen AOI-831

    +
    • + +
  • +

    ASUS WL-107G

    +
    • + +
  • +

    ASUS WL-130g

    +
    • + +
  • +

    Atlantis Land A02-PCI-W54

    +
    • + +
  • +

    Atlantis Land A02-PCM-W54

    +
    • + +
  • +

    Belkin F5D7000 v3

    +
    • + +
  • +

    Belkin F5D7010 v2

    +
    • + +
  • +

    Billionton MIWLGRL

    +
    • + +
  • +

    Canyon CN-WF511

    +
    • + +
  • +

    Canyon CN-WF513

    +
    • + +
  • +

    CC&C WL-2102

    +
    • + +
  • +

    CNet CWC-854

    +
    • + +
  • +

    CNet CWP-854

    +
    • + +
  • +

    Compex WL54G

    +
    • + +
  • +

    Compex WLP54G

    +
    • + +
  • +

    Conceptronic C54RC

    +
    • + +
  • +

    Conceptronic C54Ri

    +
    • + +
  • +

    Digitus DN-7001G-RA

    +
    • + +
  • +

    Digitus DN-7006G-RA

    +
    • + +
  • +

    E-Tech WGPC02

    +
    • + +
  • +

    E-Tech WGPI02

    +
    • + +
  • +

    Edimax EW-7108PCg

    +
    • + +
  • +

    Edimax EW-7128g

    +
    • + +
  • +

    Eminent EM3036

    +
    • + +
  • +

    Eminent EM3037

    +
    • + +
  • +

    Encore ENLWI-G-RLAM

    +
    • + +
  • +

    Encore ENPWI-G-RLAM

    +
    • + +
  • +

    Fiberline WL-400P

    +
    • + +
  • +

    Fibreline WL-400X

    +
    • + +
  • +

    Gigabyte GN-WI01GS

    +
    • + +
  • +

    Gigabyte GN-WIKG

    +
    • + +
  • +

    Gigabyte GN-WMKG

    +
    • + +
  • +

    Gigabyte GN-WP01GS

    +
    • + +
  • +

    Gigabyte GN-WPKG

    +
    • + +
  • +

    Hawking HWC54GR

    +
    • + +
  • +

    Hawking HWP54GR

    +
    • + +
  • +

    iNexQ CR054g-009 (R03)

    +
    • + +
  • +

    JAHT WN-4054P

    +
    • + +
  • +

    JAHT WN-4054PCI

    +
    • + +
  • +

    LevelOne WNC-0301 v2

    +
    • + +
  • +

    LevelOne WPC-0301 v2

    +
    • + +
  • +

    Linksys WMP54G v4

    +
    • + +
  • +

    Micronet SP906GK

    +
    • + +
  • +

    Micronet SP908GK V3

    +
    • + +
  • +

    Minitar MN54GCB-R

    +
    • + +
  • +

    Minitar MN54GPC-R

    +
    • + +
  • +

    MSI CB54G2

    +
    • + +
  • +

    MSI MP54G2

    +
    • + +
  • +

    MSI PC54G2

    +
    • + +
  • +

    OvisLink EVO-W54PCI

    +
    • + +
  • +

    PheeNet HWL-PCIG/RA

    +
    • + +
  • +

    Pro-Nets CB80211G

    +
    • + +
  • +

    Pro-Nets PC80211G

    +
    • + +
  • +

    Repotec RP-WB7108

    +
    • + +
  • +

    Repotec RP-WP0854

    +
    • + +
  • +

    SATech SN-54C

    +
    • + +
  • +

    SATech SN-54P

    +
    • + +
  • +

    Sitecom WL-112

    +
    • + +
  • +

    Sitecom WL-115

    +
    • + +
  • +

    SMC SMCWCB-GM

    +
    • + +
  • +

    SMC SMCWPCI-GM

    +
    • + +
  • +

    SparkLAN WL-685R

    +
    • + +
  • +

    Surecom EP-9321-g

    +
    • + +
  • +

    Surecom EP-9321-g1

    +
    • + +
  • +

    Surecom EP-9428-g

    +
    • + +
  • +

    Sweex LC500050

    +
    • + +
  • +

    Sweex LC700030

    +
    • + +
  • +

    TekComm NE-9321-g

    +
    • + +
  • +

    TekComm NE-9428-g

    +
    • + +
  • +

    Unex CR054g-R02

    +
    • + +
  • +

    Unex MR054g-R02

    +
    • + +
  • +

    Zinwell ZWX-G160

    +
    • + +
  • +

    Zinwell ZWX-G360

    +
    • + +
  • +

    Zinwell ZWX-G361

    +
    • + +
  • +

    Zonet ZEW1500

    +
    • + +
  • +

    Zonet ZEW1600

    +
    • +
+ +

An up to date list can be found at http://damien.bergamini.free.fr/ral/list.html.

+ +

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

+ +

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)

+
+ +
+
+

3.7 Miscellaneous +Networks

+
+ +
+
+

3.8 ISDN Interfaces

+
+ +
+
+

3.9 Serial Interfaces

+ +

“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

    +
    • + +
  • +

    SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.

    +
    • + +
  • +

    Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.

    +
    • +
+ +

AST 4 port serial card using shared IRQ

+ +

PCI-Based multi-port serial boards ( +puc(4) +driver)

+ +
    +
  • +

    Actiontech 56K PCI

    +
    • + +
  • +

    Avlab Technology, PCI IO 2S and PCI IO 4S

    +
    • + +
  • +

    Comtrol RocketPort 550

    +
    • + +
  • +

    Decision Computers PCCOM 4-port serial and dual port RS232/422/485

    +
    • + +
  • +

    Dolphin Peripherals 4025/4035/4036

    +
    • + +
  • +

    IC Book Labs Dreadnought 16x Lite and Pro

    +
    • + +
  • +

    Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550

    +
    • + +
  • +

    Middle Digital, Weasle serial port

    +
    • + +
  • +

    Moxa Industio CP-114, Smartio C104H-PCI and C168H/PCI

    +
    • + +
  • +

    NEC PK-UG-X001 and PK-UG-X008

    +
    • + +
  • +

    Netmos NM9835 PCI-2S-550

    +
    • + +
  • +

    Oxford Semiconductor OX16PCI954 PCI UART

    +
    • + +
  • +

    Syba Tech SD-LAB PCI-4S2P-550-ECP

    +
    • + +
  • +

    SIIG Cyber I/O PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber 2P1S PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber 2S1P PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber 4S PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber Serial (Single and Dual) PCI 16C550/16C650/16C850

    +
    • + +
  • +

    Syba Tech Ltd. PCI-4S2P-550-ECP

    +
    • + +
  • +

    Titan PCI-200H and PCI-800H

    +
    • + +
  • +

    US Robotics (3Com) 3CP5609 modem

    +
    • + +
  • +

    VScom PCI-400 and PCI-800

    +
    • +
+ +
+
+

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)

+
+ +
+
+

3.10 Sound Devices

+ +

The +snd_ad1816(4) +driver supports the following sound cards:

+ +
    +
  • +

    Analog Devices AD1816

    +
    • +
+ +

The +snd_atiixp(4) +driver supports the following audio chipsets:

+ +
    +
  • +

    ATI IXP 200

    +
    • + +
  • +

    ATI IXP 300

    +
    • + +
  • +

    ATI IXP 400

    +
    • +
+ +

The +snd_cmi(4) +driver supports the following sound cards:

+ +
    +
  • +

    CMedia CMI8338A

    +
    • + +
  • +

    CMedia CMI8338B

    +
    • + +
  • +

    CMedia CMI8738

    +
    • + +
  • +

    CMedia CMI8738B

    +
    • +
+ +

The +snd_cs4281(4) +driver supports the following sound cards:

+ +
    +
  • +

    Crystal Semiconductor CS4281

    +
    • +
+ +

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.

+ +

The +snd_ds1(4) +driver supports the following sound cards:

+ +
    +
  • +

    Yamaha DS-1

    +
    • + +
  • +

    Yamaha DS-1E

    +
    • +
+ +

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)

    +
    • +
+ +

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

    +
    • +
+ +

The +snd_ess(4) +driver supports the following sound cards:

+ +
    +
  • +

    Ensoniq ESS ISA PnP/non-PnP

    +
    • +
+ +

The +snd_fm801(4) +driver supports audio devices based on the following chipset:

+ +
    +
  • +

    Forte Media FM801

    +
    • +
+ +

The +snd_gusc(4) +driver supports the following sound cards:

+ +
    +
  • +

    Gravis UltraSound MAX

    +
    • + +
  • +

    Gravis UltraSound PnP

    +
    • +
+ +

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

    +
    • +
+ +

The +snd_maestro(4) +driver supports the following PCI sound cards:

+ +
    +
  • +

    ESS Technology Maestro-1

    +
    • + +
  • +

    ESS Technology Maestro-2

    +
    • + +
  • +

    ESS Technology Maestro-2E

    +
    • +
+ +

The +snd_maestro3(4) +driver supports the following audio devices:

+ +
    +
  • +

    ESS Technology Allegro-1

    +
    • + +
  • +

    ESS Technology Maestro3

    +
    • +
+ +

The +snd_neomagic(4) +driver supports the following audio devices:

+ +
    +
  • +

    NeoMagic 256AV

    +
    • + +
  • +

    NeoMagic 256ZX

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +

The +snd_t4dwave(4) +driver supports the following audio devices:

+ +
    +
  • +

    Acer Labs M5451

    +
    • + +
  • +

    SIS 7018

    +
    • + +
  • +

    Trident 4DWave DX

    +
    • + +
  • +

    Trident 4DWave NX

    +
    • +
+ +

The +snd_via82c686(4) +driver supports audio devices based on the following chipset:

+ +
    +
  • +

    VIA 82C686A

    +
    • +
+ +

The +snd_vibes(4) +driver supports audio devices based on the following chipset:

+ +
    +
  • +

    S3 SonicVibes

    +
    • +
+
+ +
+
+

3.11 Camera and Video Capture +Devices

+
+ +
+
+

3.12 USB Devices

+ +

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

+ +
+
+

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

+
+
+ +
+
+

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

+
+
+ +

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)

    +
    • +
+ +

The +uhci(4) driver +supports all UHCI v1.1 compliant controllers including:

+ +
    +
  • +

    Intel 82371AB/EB (PIIX4)

    +
    • + +
  • +

    Intel 82371SB (PIIX3)

    +
    • + +
  • +

    VIA 83C572

    +
    • +
+ +

USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)

+ +

Hubs

+ +

Keyboards ( +ukbd(4) +driver)

+ +

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

    +
    • +
+ +
+
+

The following devices are supported by the +urio(4) +driver:

+ +
    +
  • +

    Diamond MultiMedia Rio 500

    +
    • + +
  • +

    Diamond MultiMedia Rio 600

    +
    • + +
  • +

    Diamond MultiMedia Rio 800

    +
    • +
+ +

Devices supported by the +umodem(4) driver +include:

+ +
    +
  • +

    3Com 5605

    +
    • + +
  • +

    Curitel PC5740 Wireless Modem

    +
    • + +
  • +

    Metricom Ricochet GS USB wireless modem

    +
    • + +
  • +

    Sierra MC5720 Wireless Modem

    +
    • + +
  • +

    Yamaha Broadband Wireless Router RTW65b

    +
    • + +
  • +

    ELSA MicroLink 56k USB modem

    +
    • +
+ +

Mice ( +ums(4) +driver)

+ +

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

    +
    • +
+ +

The +ubsa(4) driver +supports the following adapters:

+ +
    +
  • +

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

    +
    • + +
  • +

    Belkin F5U103

    +
    • + +
  • +

    Belkin F5U120

    +
    • + +
  • +

    e-Tek Labs Kwik232

    +
    • + +
  • +

    GoHubs GoCOM232

    +
    • + +
  • +

    Huawei Technologies Mobile card (3G)

    +
    • + +
  • +

    Novatel Wireless Merlin U740 (only basic modem port supported)

    +
    • + +
  • +

    Option Globetrotter 3G (aka Vodafone Mobile Connect Card 3G)

    +
    • + +
  • +

    Option Globetrotter 3G Quad

    +
    • + +
  • +

    Option Globetrotter 3G Fusion (no WLAN support, only basic 3G modem port)

    +
    • + +
  • +

    Option Globetrotter 3G Fusion Quad (no WLAN support)

    +
    • + +
  • +

    Peracom single port serial adapter

    +
    • +
+ +

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

+ +

The +ubser(4) driver +provides support for the BWCT console management serial adapters.

+ +

The +uftdi(4) driver +supports the following adapters:

+ +
    +
  • +

    B&B Electronics USB->RS422/485 adapter

    +
    • + +
  • +

    HP USB-Serial adapter shipped with some HP laptops

    +
    • + +
  • +

    Inland UAS111

    +
    • + +
  • +

    QVS USC-1000

    +
    • +
+ +

The +uplcom(4) driver +supports the following adapters:

+ +
    +
  • +

    ATEN UC-232A

    +
    • + +
  • +

    BAFO BF-800

    +
    • + +
  • +

    BAFO BF-810

    +
    • + +
  • +

    ELECOM UC-SGT

    +
    • + +
  • +

    HAL Corporation Crossam2+USB IR commander

    +
    • + +
  • +

    Hama USB RS-232 Serial Adapter

    +
    • + +
  • +

    IOGEAR UC-232A

    +
    • + +
  • +

    I/O DATA USB-RSAQ

    +
    • + +
  • +

    I/O DATA USB-RSAQ2

    +
    • + +
  • +

    I/O DATA USB-RSAQ3

    +
    • + +
  • +

    PLANEX USB-RS232 URS-03

    +
    • + +
  • +

    RATOC REX-USB60

    +
    • + +
  • +

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

    +
    • + +
  • +

    SOURCENEXT KeikaiDenwa 8 (with and without charger)

    +
    • + +
  • +

    Sony Ericsson USB Cable (Susteen USB Data Cable)

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Acer Acerscan: 320U, 620U, 640U, 640BT, 1240U, C310U;

    +
    • + +
  • +

    AGFA SnapScan: 1212U, 1236U, e20, e25, e26, e40, e50, e52, SnapScan Touch;

    +
    • + +
  • +

    Avision 1200U

    +
    • + +
  • +

    Canon CanoScan: D660U, N656U, N676U, N1220U, LIDE 20, LIDE 25, LIDE 30;

    +
    • + +
  • +

    Epson Perfection: 610, 636U / 636Photo, 640U, 1200U / 1200Photo, 1240U / 1240Photo, +1250, 1260, 1270, 1600, 1640SU, 1650, 1660, 1670, 2480, 3200, 3500, 3590, 4200, 4990;

    +
    • + +
  • +

    Epson: GT-8400UF, GT-9300UF, GT-9700F;

    +
    • + +
  • +

    Epson Stylus: Photo RX425, CX3650, DX-5000, DX-5050, DX-6000, DX-6050 (and possibly +more in the CX-5000 and DX-3800..DX-7000 family);

    +
    • + +
  • +

    Hewlett Packard: Photosmart S20

    +
    • + +
  • +

    Hewlett Packard Scanjet: 2200C, 3300C, 3400CSE, 4100C, 4200C, 4300C, 5200C, 5300C, +5400C, 6200C, 6300C, 8200C, 8250C, 8290C;

    +
    • + +
  • +

    KYE ColorPage Vivid-Pro

    +
    • + +
  • +

    Microtek Phantom: 336CX, C6;

    +
    • + +
  • +

    Microtek ScanMaker: V6UL V6USL, X6U;

    +
    • + +
  • +

    Minolta 5400

    +
    • + +
  • +

    Mustek: 600 CU, 1200 CU, 1200 UB, 1200 USB;

    +
    • + +
  • +

    Mustek BearPaw: 1200F, 1200TA;

    +
    • + +
  • +

    NatSemi BearPaw 1200

    +
    • + +
  • +

    Nikon CoolScan LS40 ED

    +
    • + +
  • +

    Primax 6200

    +
    • + +
  • +

    Primax Colorado: 1200u, 600u, USB 19200, USB 9600;

    +
    • + +
  • +

    Primax: G2-200, G2-300, G2-600, G2600, G2E-300, G2E-3002, G2E-600, G2E600, G2X-300, +G600, ReadyScan 636i;

    +
    • + +
  • +

    Ultima 1200 UB Plus

    +
    • + +
  • +

    UMAX Astra: 1220U, 1236U, 2000U, 2100U, 2200U, 3400;

    +
    • + +
  • +

    Visioneer OneTouch: 3000, 5300, 7600, 6100, 6200, 8100, 8600;

    +
    • +
+ +

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

    +
    • + +
  • +

    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

    +
    • +
+ +

Audio Devices ( +uaudio(4) +driver)

+ +

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.13 IEEE 1394 (Firewire) +Devices

+ +

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 (CXD1947)

    +
    • + +
  • +

    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)

    +
    • +
+ +

Serial Bus Protocol 2 (SBP-2) storage devices ( +sbp(4) +driver)

+
+ +
+
+

3.14 Bluetooth Devices

+ +

The +ng_bt3c(4) +driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.

+ +

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

    +
    • +
+
+ +
+
+

3.15 Cryptographic +Accelerators

+ +

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

    +
    • +
+ +

The +safe(4) driver +supports cards containing any of the following chips:

+ +
    +
  • +

    SafeNet 1141

    +
    • + +
  • +

    SafeNet 1741

    +
    • +
+ +

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

    +
    • +
+
+ +
+
+

3.16 Miscellaneous

+ +

FAX-Modem/PCCARD

+ +
    +
  • +

    MELCO IGM-PCM56K/IGM-PCM56KH

    +
    • + +
  • +

    Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)

    +
    • +
+ +
+
+

Floppy drives ( +fdc(4) +driver)

+ +

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

+
+
+ +
+
+

Keyboards including:

+ + + +
+
+

Pointing devices including:

+ +
    +
  • +

    Bus mice and compatible devices ( +mse(4) +driver)

    +
    • + +
  • +

    PS/2 mice and compatible devices, including many laptop pointing devices ( +psm(4) +driver)

    +
    • + +
  • +

    Serial mice and compatible devices

    +
    • + +
  • +

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

+
+
+ +
+
+

“PC standard” parallel ports ( +ppc(4) +driver)

+ +

PC-compatible joysticks ( +joy(4) +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/en/releases/6.3R/hardware-i386.html b/en/releases/6.3R/hardware-i386.html new file mode 100644 index 0000000000..d38d8374f8 --- /dev/null +++ b/en/releases/6.3R/hardware-i386.html @@ -0,0 +1,8159 @@ + + + + +FreeBSD/i386 6.3-RELEASE Hardware Notes + + + + + +
+
+

FreeBSD/i386 6.3-RELEASE Hardware +Notes

+ +

The FreeBSD Documentation Project

+ +

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

+ +
+
+ +
+
+
Table of Contents
+ +
1 Introduction
+ +
2 Supported Processors and Motherboards
+ +
3 Supported Devices
+ +
+
+
3.1 Disk Controllers
+ +
3.2 Ethernet Interfaces
+ +
3.3 Token Ring Interfaces
+ +
3.4 FDDI Interfaces
+ +
3.5 ATM Interfaces
+ +
3.6 Wireless Network Interfaces
+ +
3.7 Miscellaneous Networks
+ +
3.8 ISDN Interfaces
+ +
3.9 Serial Interfaces
+ +
3.10 Sound Devices
+ +
3.11 Camera and Video Capture Devices
+ +
3.12 USB Devices
+ +
3.13 IEEE 1394 (Firewire) Devices
+ +
3.14 Bluetooth Devices
+ +
3.15 Cryptographic Accelerators
+ +
3.16 Miscellaneous
+
+
+
+
+ +
+

1 Introduction

+ +

This document contains the hardware compatibility notes for FreeBSD 6.3-RELEASE on the +i386 hardware platform (also referred to as FreeBSD/i386 6.3-RELEASE). It lists devices +known to work on this platform, as well as some notes on boot-time kernel customization +that may be useful when attempting to configure support for new devices.

+ +
+
+

Note: This document includes information specific to the i386 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.

+
+
+
+ +
+
+

2 Supported Processors and +Motherboards

+ +

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, K6 (and variants), Athlon (including Athlon-MP, Athlon-XP, +Athlon-4, and Athlon Thunderbird), and Duron processors. The AMD Élan SC520 +embedded processor is supported. The Transmeta Crusoe is recognized and supported, as are +i386-compatible processors from Cyrix and NexGen.

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +
+hint.acpi.0.disabled="1"
+
+ +

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

+ +

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

+
+ +
+
+

3 Supported Devices

+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.17 +2007/09/13 16:25:43 brueffer Exp $ + +

This section describes the devices currently known to be supported by with FreeBSD on +the i386 platform. 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

+ +

IDE/ATA controllers ( +ata(4) +driver)

+ +

Controllers supported by the +aac(4) driver +include:

+ +
    +
  • +

    Adaptec AAC-364

    +
    • + +
  • +

    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

    +
    • +
+ +

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)

    +
    • +
+ +

The +adw(4) driver +supports SCSI controllers including:

+ +
    +
  • +

    AdvanSys ABP940UW/ABP3940UW

    +
    • + +
  • +

    AdvanSys ABP950UW

    +
    • + +
  • +

    AdvanSys ABP970UW

    +
    • + +
  • +

    AdvanSys ABP3940U2W

    +
    • + +
  • +

    AdvanSys ABP3950U2W

    +
    • +
+ +

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

    +
    • +
+ +

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 2920

    +
    • + +
  • +

    Adaptec 2930C

    +
    • + +
  • +

    Adaptec 2930U2

    +
    • + +
  • +

    Adaptec 2940

    +
    • + +
  • +

    Adaptec 2940J

    +
    • + +
  • +

    Adaptec 2940N

    +
    • + +
  • +

    Adaptec 2940U

    +
    • + +
  • +

    Adaptec 2940AU

    +
    • + +
  • +

    Adaptec 2940UW

    +
    • + +
  • +

    Adaptec 2940UW Dual

    +
    • + +
  • +

    Adaptec 2940UW Pro

    +
    • + +
  • +

    Adaptec 2940U2W

    +
    • + +
  • +

    Adaptec 2940U2B

    +
    • + +
  • +

    Adaptec 2950U2W

    +
    • + +
  • +

    Adaptec 2950U2B

    +
    • + +
  • +

    Adaptec 19160B

    +
    • + +
  • +

    Adaptec 29160B

    +
    • + +
  • +

    Adaptec 29160N

    +
    • + +
  • +

    Adaptec 3940

    +
    • + +
  • +

    Adaptec 3940U

    +
    • + +
  • +

    Adaptec 3940AU

    +
    • + +
  • +

    Adaptec 3940UW

    +
    • + +
  • +

    Adaptec 3940AUW

    +
    • + +
  • +

    Adaptec 3940U2W

    +
    • + +
  • +

    Adaptec 3950U2

    +
    • + +
  • +

    Adaptec 3960

    +
    • + +
  • +

    Adaptec 39160

    +
    • + +
  • +

    Adaptec 3985

    +
    • + +
  • +

    Adaptec 4944UW

    +
    • + +
  • +

    NEC PC-9821Xt13 (PC-98)

    +
    • + +
  • +

    NEC RvII26 (PC-98)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Many motherboards with on-board SCSI support

    +
    • +
+ +

The +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

    +
    • +
+ +

The adapters supported by the +aic(4) driver +include:

+ +
    +
  • +

    Adaptec AHA-1505 (ISA)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Adaptec AHA-1535 (ISA)

    +
    • + +
  • +

    Creative Labs SoundBlaster SCSI host adapter (ISA)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    NEC PC-9801-100 (PC98)

    +
    • +
+ +

Controllers supported by the +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

    +
    • +
+ +
+
+

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

+
+
+ +

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-1210

    +
    • + +
  • +

    ARC-1220

    +
    • + +
  • +

    ARC-1230

    +
    • + +
  • +

    ARC-1260

    +
    • + +
  • +

    ARC-1280

    +
    • + +
  • +

    ARC-1210ML

    +
    • + +
  • +

    ARC-1220ML

    +
    • + +
  • +

    ARC-1231ML

    +
    • + +
  • +

    ARC-1261ML

    +
    • + +
  • +

    ARC-1280ML

    +
    • +
+ +

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

    +
    • +
+ +

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.

+ +

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 P400

    +
    • + +
  • +

    HP Smart Array P400i

    +
    • + +
  • +

    HP Smart Array P600

    +
    • + +
  • +

    HP Smart Array P800

    +
    • + +
  • +

    HP Modular Smart Array 20 (MSA20)

    +
    • + +
  • +

    HP Modular Smart Array 500 (MSA500)

    +
    • +
+ +

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

    +
    • +
+ +

The +hptmv(4) driver +supports the following ATA RAID controllers:

+ +
    +
  • +

    HighPoint's RocketRAID 182x series

    +
    • +
+ +

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

    +
    • +
+ +

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.

+ +

Controllers supported by the +ips(4) driver +include:

+ +
    +
  • +

    IBM ServeRAID 3H

    +
    • + +
  • +

    ServeRAID 4L/4M/4H

    +
    • + +
  • +

    ServeRAID Series 5

    +
    • + +
  • +

    ServeRAID 6i/6M

    +
    • + +
  • +

    ServeRAID 7t/7k/7M

    +
    • +
+ +

Cards supported by the +isp(4) driver +include:

+ +
    +
  • +

    ISP1000

    +
    • + +
  • +

    ISP1020

    +
    • + +
  • +

    ISP1040

    +
    • + +
  • +

    Qlogic 1240

    +
    • + +
  • +

    Qlogic 1020

    +
    • + +
  • +

    Qlogic 1040

    +
    • + +
  • +

    Qlogic 1080

    +
    • + +
  • +

    Qlogic 1280

    +
    • + +
  • +

    Qlogic 12160

    +
    • + +
  • +

    Qlogic 210X

    +
    • + +
  • +

    Qlogic 220X

    +
    • + +
  • +

    Qlogic 2300

    +
    • + +
  • +

    Qlogic 2312

    +
    • + +
  • +

    Qlogic 234X

    +
    • + +
  • +

    Qlogic 2322

    +
    • + +
  • +

    Qlogic 200

    +
    • + +
  • +

    Qlogic 2422

    +
    • + +
  • +

    Qlogic 2432

    +
    • +
+ +

The +mfi(4) driver +supports the following hardware:

+ +
    +
  • +

    LSI MegaRAID SAS 8408E

    +
    • + +
  • +

    LSI MegaRAID SAS 8480E

    +
    • + +
  • +

    Dell PERC5/i

    +
    • +
+ +

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: Booting from these controllers is supported. EISA adapters are not +supported.

+
+
+ +

Controllers supported by the +mly(4) driver +include:

+ +
    +
  • +

    Mylex AcceleRAID 160

    +
    • + +
  • +

    Mylex AcceleRAID 170

    +
    • + +
  • +

    Mylex AcceleRAID 352

    +
    • + +
  • +

    Mylex eXtremeRAID 2000

    +
    • + +
  • +

    Mylex eXtremeRAID 3000

    +
    • +
+ +

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

+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    LSI Logic AS1064, LSI Logic AS1068

    +
    • + +
  • +

    LSI Logic FC909 (1Gb/s Fibre Channel)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Dell PowerEdge 1750 thru 2850

    +
    • + +
  • +

    IBM eServer xSeries 335

    +
    • +
+ +

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

+ +

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)

    +
    • +
+ +

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)

    +
    • +
+ +

Controllers supported by the +nsp(4) driver +include:

+ +
    +
  • +

    Alpha-Data AD-PCS201

    +
    • + +
  • +

    I-O DATA CBSC16

    +
    • +
+ +

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

+ +

The +rr232x(4) driver +supports the following hardware:

+ +
    +
  • +

    HighPoint RocketRAID 2320

    +
    • + +
  • +

    HighPoint RocketRAID 2322

    +
    • +
+ +

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

    +
    • +
+ +

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.

+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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)

    +
    • +
+ +

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

    +
    • + +
  • +

    Sony proprietary interface (all models) ( +scd(4))

    +
    • + +
  • +

    ATAPI IDE interface ( +acd(4))

    +
    • +
+ +
+
+

The following device is unmaintained:

+ +
    +
  • +

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

    +
    • +
+ +
+
+
+ +
+
+

3.2 Ethernet Interfaces

+ +

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

    +
    • +
+ +

The +axe(4) driver +supports ASIX Electronics AX88172 based USB Ethernet adapters including:

+ +
    +
  • +

    Buffalo (Melco Inc.) LUA-U2-KTX

    +
    • + +
  • +

    D-Link DUB-E100, revision A

    +
    • + +
  • +

    LinkSys USB200M

    +
    • + +
  • +

    Netgear FA120

    +
    • + +
  • +

    Sitecom LN-029

    +
    • + +
  • +

    System TALKS Inc. SGC-X2UL

    +
    • +
+ +

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

+ +
    +
  • +

    HP NC370T Multifunction Gigabit Server Adapter

    +
    • + +
  • +

    HP NC370i Multifunction Gigabit Server Adapter

    +
    • +
+ +

Broadcom BCM4401 based Fast Ethernet adapters ( +bfe(4) +driver)

+ +

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)

    +
    • + +
  • +

    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 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 +cue(4) driver +supports CATC USB-EL1210A based USB Ethernet adapters including:

+ +
    +
  • +

    Belkin F5U011/F5U111

    +
    • + +
  • +

    CATC Netmate

    +
    • + +
  • +

    CATC Netmate II

    +
    • + +
  • +

    SmartBridges SmartLink

    +
    • +
+ +

Crystal Semiconductor CS89x0-based NICs (cs(4) driver)

+ +

The +cxgb(4) driver +supports 10 Gigabit Ethernet adapters based on the T3 and T3B chipset:

+ +
    +
  • +

    Chelsio 10GBase-CX4

    +
    • + +
  • +

    Chelsio 10GBase-LR

    +
    • + +
  • +

    Chelsio 10GBase-SR

    +
    • +
+ +

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

+ +
    +
  • +

    DEC/Intel 21143

    +
    • + +
  • +

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

    +
    • + +
  • +

    ASIX Electronics AX88140A and AX88141

    +
    • + +
  • +

    Conexant LANfinity RS7112 (miniPCI)

    +
    • + +
  • +

    Davicom DM9009, DM9100, DM9102 and DM9102A

    +
    • + +
  • +

    Lite-On 82c168 and 82c169 PNIC

    +
    • + +
  • +

    Lite-On/Macronix 82c115 PNIC II

    +
    • + +
  • +

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

    +
    • + +
  • +

    Xircom X3201 (cardbus only)

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Abocom FE2500

    +
    • + +
  • +

    Accton EN1217 (98715A)

    +
    • + +
  • +

    Accton EN2242 MiniPCI

    +
    • + +
  • +

    Adico AE310TX (98715A)

    +
    • + +
  • +

    Alfa Inc GFC2204 (ASIX AX88140A)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Built in DE500-BA on DEC Alpha workstations (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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    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

    +
    • + +
  • +

    CyQ've ELA-010

    +
    • + +
  • +

    DEC EtherWorks DE305

    +
    • + +
  • +

    Danpex EN-6200P2

    +
    • + +
  • +

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

    +
    • + +
  • +

    D-Link DE-650/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)

    +
    • + +
  • +

    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

    +
    • + +
  • +

    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 5000

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Surecom EtherPerfect EP-427

    +
    • + +
  • +

    Surecom NE-34

    +
    • + +
  • +

    TDK 3000/3400/5670 Fast Etherenet/Modem

    +
    • + +
  • +

    TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card

    +
    • + +
  • +

    TDK DFL5610WS Ethernet/Modem PC Card

    +
    • + +
  • +

    Telecom Device SuperSocket RE450T

    +
    • + +
  • +

    VIA VT86C926

    +
    • + +
  • +

    Winbond W89C940

    +
    • +
+ +

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

+ +

The el(4) driver supports +the 3Com 3c501 8bit ISA Ethernet card.

+ +

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 and 82573 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 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)

    +
    • +
+ +

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)

    +
    • +
+ +

The ex(4) driver supports +the following Ethernet adapters:

+ +
    +
  • +

    Intel EtherExpress Pro/10

    +
    • + +
  • +

    Intel EtherExpress Pro/10+

    +
    • + +
  • +

    The Olicom OC2220

    +
    • +
+ +

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 PCMCIA Ethernet

    +
    • + +
  • +

    Eagle Tech NE200T

    +
    • + +
  • +

    Eiger Labs EPX-10BT

    +
    • + +
  • +

    Fujitsu FMV-J182, FMV-J182A

    +
    • + +
  • +

    Fujitsu MB86960A, MB86965A

    +
    • + +
  • +

    Fujitsu MBH10303, MBH10302 Ethernet PCMCIA

    +
    • + +
  • +

    Fujitsu Towa LA501 Ethernet

    +
    • + +
  • +

    HITACHI HT-4840-11

    +
    • + +
  • +

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

    +
    • +
+ +

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

    +
    • +
+ +

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 +ixgb(4) driver +supports the following cards:

+ +
    +
  • +

    Intel PRO/10GbE LR Server Adapter

    +
    • + +
  • +

    Intel PRO/10GbE SR Server Adapter

    +
    • +
+ +

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

    +
    • +
+ +

Adapters supported by the +lge(4) driver +include:

+ +
    +
  • +

    SMC TigerCard 1000 (SMC9462SX)

    +
    • + +
  • +

    D-Link DGE-500SX

    +
    • +
+ +

The +lnc(4) driver +supports the following adapters:

+ +
    +
  • +

    Diamond HomeFree

    +
    • + +
  • +

    Hewlett Packard Vectra 486/66XM

    +
    • + +
  • +

    Hewlett Packard Vectra XU

    +
    • + +
  • +

    Isolan AT 4141-0 (16 bit)

    +
    • + +
  • +

    Isolan BICC

    +
    • + +
  • +

    Isolink 4110 (8 bit)

    +
    • + +
  • +

    Novell NE2100

    +
    • + +
  • +

    Novell NE32-VL

    +
    • +
+ +

Also supported are adapters working with the pcn(4) driver. The +lnc(4) driver +runs these in compatibility mode, thus the pcn(4) driver should be preferred.

+ +

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

+ +
    +
  • +

    D-Link 550SX Gigabit Ethernet

    +
    • + +
  • +

    D-Link 560T Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8021CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8021 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8022CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8022 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8061CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8061 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8062CU Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8062 SX/LX Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8035 Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8036 Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8038 Gigabit Ethernet

    +
    • + +
  • +

    Marvell Yukon 88E8039 Gigabit 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

    +
    • + +
  • +

    SysKonnect SK-9Sxx Gigabit Ethernet

    +
    • + +
  • +

    SysKonnect SK-9Exx Gigabit Ethernet

    +
    • +
+ +

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)

    +
    • +
+ +

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

    +
    • +
+ +

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 (32-bit PCI) and EG1064 (64-bit PCI)

    +
    • + +
  • +

    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)

    +
    • +
+ +

The +nve(4) driver +supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets:

+ +
    +
  • +

    nForce

    +
    • + +
  • +

    nForce2

    +
    • + +
  • +

    nForce3

    +
    • + +
  • +

    nForce4

    +
    • +
+ +

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

+ +
    +
  • +

    AMD Am79C971 PCnet-FAST

    +
    • + +
  • +

    AMD Am79C972 PCnet-FAST+

    +
    • + +
  • +

    AMD Am79C973/Am79C975 PCnet-FAST III

    +
    • + +
  • +

    AMD Am79C976 PCnet-PRO

    +
    • + +
  • +

    AMD Am79C978 PCnet-Home

    +
    • + +
  • +

    Allied-Telesis LA-PCI

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Compaq Evo N1015v Integrated Ethernet (8139C+)

    +
    • + +
  • +

    Corega CG-LAPCIGT Gigabit Ethernet (8169S)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

    +
    • + +
  • +

    LevelOne GNC-0105T (8169S)

    +
    • + +
  • +

    LinkSys EG1032 (32-bit PCI)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

Adapters supported by the rl(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

    Allied Telesyn AT2550

    +
    • + +
  • +

    Allied Telesyn AT2500TX

    +
    • + +
  • +

    Belkin F5D5000

    +
    • + +
  • +

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

    +
    • + +
  • +

    Compaq HNE-300

    +
    • + +
  • +

    CompUSA no-name 10/100 PCI Ethernet NIC

    +
    • + +
  • +

    Corega FEther CB-TXD

    +
    • + +
  • +

    Corega FEtherII CB-TXD

    +
    • + +
  • +

    D-Link DFE-528TX

    +
    • + +
  • +

    D-Link DFE-530TX+

    +
    • + +
  • +

    D-Link DFE-538TX

    +
    • + +
  • +

    D-Link DFE-690TXD

    +
    • + +
  • +

    Edimax EP-4103DL CardBus

    +
    • + +
  • +

    Encore ENL832-TX 10/100 M PCI

    +
    • + +
  • +

    Farallon NetLINE 10/100 PCI

    +
    • + +
  • +

    Genius GF100TXR

    +
    • + +
  • +

    GigaFast Ethernet EE100-AXP

    +
    • + +
  • +

    KTX-9130TX 10/100 Fast Ethernet

    +
    • + +
  • +

    LevelOne FPC-0106TX

    +
    • + +
  • +

    Longshine LCS-8038TX-R

    +
    • + +
  • +

    NDC Communications NE100TX-E

    +
    • + +
  • +

    Netronix Inc. EA-1210 NetEther 10/100

    +
    • + +
  • +

    Nortel Networks 10/100BaseTX

    +
    • + +
  • +

    OvisLink LEF-8129TX

    +
    • + +
  • +

    OvisLink LEF-8139TX

    +
    • + +
  • +

    Peppercon AG ROL-F

    +
    • + +
  • +

    Planex FNW-3603-TX

    +
    • + +
  • +

    Planex FNW-3800-TX

    +
    • + +
  • +

    SMC EZ Card 10/100 PCI 1211-TX

    +
    • + +
  • +

    SOHO (PRAGMATIC) UE-1211C

    +
    • +
+ +

The +rue(4) driver +supports RealTek RTL8150 based USB Ethernet adapters including:

+ +
    +
  • +

    Buffalo (Melco Inc.) LUA-KTX

    +
    • + +
  • +

    Green House GH-USB100B

    +
    • + +
  • +

    LinkSys USB100M

    +
    • + +
  • +

    Billionton 10/100 FastEthernet USBKR2

    +
    • +
+ +

Adapters supported by the sf(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    ANA-62020 64-bit single port 100baseFX adapter

    +
    • +
+ +

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

+ +
    +
  • +

    @Nifty FNECHARD IFC USUP-TX

    +
    • + +
  • +

    MELCO LGY-PCI-TXC

    +
    • + +
  • +

    Netgear FA311-TX (DP83815)

    +
    • + +
  • +

    Netgear FA312-TX (DP83815)

    +
    • + +
  • +

    SiS 630, 635, and 735 motherboard chipsets

    +
    • + +
  • +

    Soekris Engineering net45xx, net48xx, lan1621, and lan1641

    +
    • +
+ +

Adapters supported by the sk(4) driver +include:

+ +
    +
  • +

    3Com 3C940 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Belkin F5D5005 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Linksys EG1032 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

    +
    • +
+ +

The sn(4) driver supports +SMC91Cxx based ISA and PCMCIA cards including:

+ +
    +
  • +

    3Com Megahertz X-Jack Ethernet PC-Card XJ10BT

    +
    • + +
  • +

    3Com Megahertz X-Jack Ethernet PC-Card XJ10BC

    +
    • + +
  • +

    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.

+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

    D-Link DFE-530TXS

    +
    • + +
  • +

    D-Link DFE-550TX

    +
    • + +
  • +

    D-Link DFE-580TX

    +
    • +
+ +

The 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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

The +udav(4) driver +supports the following adapters:

+ +
    +
  • +

    Corega FEther USB-TXC

    +
    • +
+ +

The +vge(4) driver +supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including:

+ +
    +
  • +

    VIA Networking LAN-on-motherboard Gigabit Ethernet

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    AOpen/Acer ALN-320

    +
    • + +
  • +

    D-Link DFE530-TX

    +
    • + +
  • +

    Hawking Technologies PN102TX

    +
    • +
+ +

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

    +
    • +
+ +

The wb(4) driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:

+ +
    +
  • +

    Trendware TE100-PCIE

    +
    • +
+ +

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

+
+ +
+
+

3.3 Token Ring Interfaces

+ +

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

+ +
    +
  • +

    Olicom OC-3115

    +
    • + +
  • +

    Olicom ISA 16/4 Adapter (OC-3117)

    +
    • + +
  • +

    Olicom ISA 16/4 Adapter (OC-3118)

    +
    • +
+ +

The following PCI based adapters are supported:

+ +
    +
  • +

    Olicom PCI 16/4 Adapter (OC-3136)

    +
    • + +
  • +

    Olicom PCI/II 16/4 Adapter (OC-3137)

    +
    • + +
  • +

    Olicom PCI 16/4 Adapter (OC-3139)

    +
    • + +
  • +

    Olicom RapidFire 3140 16/4 PCI Adapter (OC-3140)

    +
    • + +
  • +

    Olicom RapidFire 3141 Fiber Adapter (OC-3141)

    +
    • + +
  • +

    Olicom RapidFire 3540 100/16/4 Adapter (OC-3540)

    +
    • +
+
+ +
+
+

3.4 FDDI Interfaces

+ +

DEC DEFPA PCI ( +fpa(4) +driver)

+ +

DEC DEFEA EISA ( +fpa(4) +driver)

+
+ +
+
+

3.5 ATM Interfaces

+ +

Midway-based ATM interfaces (en(4) driver)

+ +

FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and +fatm(4) +drivers)

+ +

IDT NICStAR 77201/211-based ATM Adapters ( +idt(4) +driver)

+ +

FORE Systems, Inc. HE155 and HE622 ATM interfaces ( +hatm(4) +driver)

+ +

IDT77252-based ATM cards ( +patm(4) +driver)

+
+ +
+
+

3.6 Wireless Network Interfaces

+ +

Cisco/Aironet 802.11b wireless adapters (an(4) driver)

+ +

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

+ +

Cards supported by the +awi(4) driver +include:

+ +
    +
  • +

    BayStack 650

    +
    • + +
  • +

    BayStack 660

    +
    • + +
  • +

    Icom SL-200

    +
    • + +
  • +

    Melco WLI-PCM

    +
    • + +
  • +

    NEL SSMagic

    +
    • + +
  • +

    Netwave AirSurfer Plus

    +
    • + +
  • +

    Netwave AirSurfer Pro

    +
    • + +
  • +

    Nokia C020 WLAN

    +
    • + +
  • +

    Farallon SkyLINE

    +
    • +
+ +

The original Xircom Netwave AirSurfer is supported by the cnw(4) driver.

+ +

Cards supported by the +cnw(4) driver +include:

+ +
    +
  • +

    Xircom CreditCard Netwave

    +
    • + +
  • +

    NetWave AirSurfer

    +
    • +
+ +

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

+ +

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

+ +
    +
  • +

    A-Link WL54H

    +
    • + +
  • +

    A-Link WL54PC

    +
    • + +
  • +

    AirLink101 AWLC5025

    +
    • + +
  • +

    AirLink101 AWLH5025

    +
    • + +
  • +

    Amigo AWI-914W

    +
    • + +
  • +

    Amigo AWI-922W

    +
    • + +
  • +

    Amigo AWI-926W

    +
    • + +
  • +

    AMIT WL531C

    +
    • + +
  • +

    AMIT WL531P

    +
    • + +
  • +

    AOpen AOI-831

    +
    • + +
  • +

    ASUS WL-107G

    +
    • + +
  • +

    ASUS WL-130g

    +
    • + +
  • +

    Atlantis Land A02-PCI-W54

    +
    • + +
  • +

    Atlantis Land A02-PCM-W54

    +
    • + +
  • +

    Belkin F5D7000 v3

    +
    • + +
  • +

    Belkin F5D7010 v2

    +
    • + +
  • +

    Billionton MIWLGRL

    +
    • + +
  • +

    Canyon CN-WF511

    +
    • + +
  • +

    Canyon CN-WF513

    +
    • + +
  • +

    CC&C WL-2102

    +
    • + +
  • +

    CNet CWC-854

    +
    • + +
  • +

    CNet CWP-854

    +
    • + +
  • +

    Compex WL54G

    +
    • + +
  • +

    Compex WLP54G

    +
    • + +
  • +

    Conceptronic C54RC

    +
    • + +
  • +

    Conceptronic C54Ri

    +
    • + +
  • +

    Digitus DN-7001G-RA

    +
    • + +
  • +

    Digitus DN-7006G-RA

    +
    • + +
  • +

    E-Tech WGPC02

    +
    • + +
  • +

    E-Tech WGPI02

    +
    • + +
  • +

    Edimax EW-7108PCg

    +
    • + +
  • +

    Edimax EW-7128g

    +
    • + +
  • +

    Eminent EM3036

    +
    • + +
  • +

    Eminent EM3037

    +
    • + +
  • +

    Encore ENLWI-G-RLAM

    +
    • + +
  • +

    Encore ENPWI-G-RLAM

    +
    • + +
  • +

    Fiberline WL-400P

    +
    • + +
  • +

    Fibreline WL-400X

    +
    • + +
  • +

    Gigabyte GN-WI01GS

    +
    • + +
  • +

    Gigabyte GN-WIKG

    +
    • + +
  • +

    Gigabyte GN-WMKG

    +
    • + +
  • +

    Gigabyte GN-WP01GS

    +
    • + +
  • +

    Gigabyte GN-WPKG

    +
    • + +
  • +

    Hawking HWC54GR

    +
    • + +
  • +

    Hawking HWP54GR

    +
    • + +
  • +

    iNexQ CR054g-009 (R03)

    +
    • + +
  • +

    JAHT WN-4054P

    +
    • + +
  • +

    JAHT WN-4054PCI

    +
    • + +
  • +

    LevelOne WNC-0301 v2

    +
    • + +
  • +

    LevelOne WPC-0301 v2

    +
    • + +
  • +

    Linksys WMP54G v4

    +
    • + +
  • +

    Micronet SP906GK

    +
    • + +
  • +

    Micronet SP908GK V3

    +
    • + +
  • +

    Minitar MN54GCB-R

    +
    • + +
  • +

    Minitar MN54GPC-R

    +
    • + +
  • +

    MSI CB54G2

    +
    • + +
  • +

    MSI MP54G2

    +
    • + +
  • +

    MSI PC54G2

    +
    • + +
  • +

    OvisLink EVO-W54PCI

    +
    • + +
  • +

    PheeNet HWL-PCIG/RA

    +
    • + +
  • +

    Pro-Nets CB80211G

    +
    • + +
  • +

    Pro-Nets PC80211G

    +
    • + +
  • +

    Repotec RP-WB7108

    +
    • + +
  • +

    Repotec RP-WP0854

    +
    • + +
  • +

    SATech SN-54C

    +
    • + +
  • +

    SATech SN-54P

    +
    • + +
  • +

    Sitecom WL-112

    +
    • + +
  • +

    Sitecom WL-115

    +
    • + +
  • +

    SMC SMCWCB-GM

    +
    • + +
  • +

    SMC SMCWPCI-GM

    +
    • + +
  • +

    SparkLAN WL-685R

    +
    • + +
  • +

    Surecom EP-9321-g

    +
    • + +
  • +

    Surecom EP-9321-g1

    +
    • + +
  • +

    Surecom EP-9428-g

    +
    • + +
  • +

    Sweex LC500050

    +
    • + +
  • +

    Sweex LC700030

    +
    • + +
  • +

    TekComm NE-9321-g

    +
    • + +
  • +

    TekComm NE-9428-g

    +
    • + +
  • +

    Unex CR054g-R02

    +
    • + +
  • +

    Unex MR054g-R02

    +
    • + +
  • +

    Zinwell ZWX-G160

    +
    • + +
  • +

    Zinwell ZWX-G360

    +
    • + +
  • +

    Zinwell ZWX-G361

    +
    • + +
  • +

    Zonet ZEW1500

    +
    • + +
  • +

    Zonet ZEW1600

    +
    • +
+ +

An up to date list can be found at http://damien.bergamini.free.fr/ral/list.html.

+ +

Raytheon Raylink 2.4GHz wireless adapters ( +ray(4) +driver)

+ +

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

+ +

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)

+ +

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

+
+ +
+
+

3.7 Miscellaneous +Networks

+ +

The ce(4) driver supports +the following models of Tau-PCI/32 WAN adapters:

+ +
    +
  • +

    Cronyx Tau-PCI/32

    +
    • + +
  • +

    Cronyx Tau-PCI/32-Lite

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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)

    +
    • +
+ +

Granch SBNI12 point-to-point communications adapters ( +sbni(4) +driver)

+ +

Granch SBNI16 SHDSL modems ( +sbsh(4) +driver)

+ +

The cm(4) driver supports +the following card models:

+ +
    +
  • +

    SMC90c26

    +
    • + +
  • +

    SMC90c56

    +
    • + +
  • +

    SMC90c66 in '56 compatibility mode.

    +
    • +
+
+ +
+
+

3.8 ISDN Interfaces

+ +

AcerISDN P10 ISA PnP (experimental)

+ +

Asuscom ISDNlink 128K ISA

+ +

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

+ +

AVM

+ +
    +
  • +

    A1

    +
    • + +
  • +

    B1 ISA (tested with V2.0)

    +
    • + +
  • +

    B1 PCI (tested with V4.0)

    +
    • + +
  • +

    Fritz!Card classic

    +
    • + +
  • +

    Fritz!Card PnP

    +
    • + +
  • +

    Fritz!Card PCI

    +
    • + +
  • +

    Fritz!Card PCI, Version 2

    +
    • + +
  • +

    T1

    +
    • +
+ +
+
+

Creatix

+ +
    +
  • +

    ISDN-S0

    +
    • + +
  • +

    ISDN-S0 P&P

    +
    • +
+ +
+
+

Compaq Microcom 610 ISDN (Compaq series PSB2222I) ISA PnP

+ +

Dr. Neuhaus Niccy Go@ and compatibles

+ +

Dynalink IS64PPH and IS64PPH+

+ +

Eicon Diehl DIVA 2.0 and 2.02

+ +

ELSA

+ +
    +
  • +

    ELSA PCC-16

    +
    • + +
  • +

    QuickStep 1000pro ISA

    +
    • + +
  • +

    MicroLink ISDN/PCI

    +
    • + +
  • +

    QuickStep 1000pro PCI

    +
    • +
+ +
+
+

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

+ +

Sedlbauer Win Speed

+ +

Siemens I-Surf 2.0

+ +

TELEINT ISDN SPEED No.1 (experimental)

+ +

Teles

+ +
    +
  • +

    S0/8

    +
    • + +
  • +

    S0/16

    +
    • + +
  • +

    S0/16.3

    +
    • + +
  • +

    S0/16.3 PnP

    +
    • + +
  • +

    16.3c ISA PnP (experimental)

    +
    • + +
  • +

    Teles PCI-TJ

    +
    • +
+ +
+
+

Traverse Technologies NETjet-S PCI

+ +

USRobotics Sportster ISDN TA intern

+ +

Winbond W6692 based PCI cards

+
+ +
+
+

3.9 Serial Interfaces

+ +

“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

    +
    • + +
  • +

    SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.

    +
    • + +
  • +

    Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.

    +
    • +
+ +

AST 4 port serial card using shared IRQ

+ +

ARNET serial cards (ar(4) driver)

+ +
    +
  • +

    ARNET 8 port serial card using shared IRQ

    +
    • + +
  • +

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

    +
    • +
+ +
+
+

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)

    +
    • +
+ +
+
+

Comtrol Rocketport card (rp(4) driver)

+ +

Cyclades Cyclom-Y serial board (cy(4) driver)

+ +

STB 4 port card using shared IRQ

+ +

DigiBoard intelligent serial cards (digi driver)

+ +

PCI-Based multi-port serial boards ( +puc(4) +driver)

+ +
    +
  • +

    Actiontech 56K PCI

    +
    • + +
  • +

    Avlab Technology, PCI IO 2S and PCI IO 4S

    +
    • + +
  • +

    Comtrol RocketPort 550

    +
    • + +
  • +

    Decision Computers PCCOM 4-port serial and dual port RS232/422/485

    +
    • + +
  • +

    Dolphin Peripherals 4025/4035/4036

    +
    • + +
  • +

    IC Book Labs Dreadnought 16x Lite and Pro

    +
    • + +
  • +

    Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550

    +
    • + +
  • +

    Middle Digital, Weasle serial port

    +
    • + +
  • +

    Moxa Industio CP-114, Smartio C104H-PCI and C168H/PCI

    +
    • + +
  • +

    NEC PK-UG-X001 and PK-UG-X008

    +
    • + +
  • +

    Netmos NM9835 PCI-2S-550

    +
    • + +
  • +

    Oxford Semiconductor OX16PCI954 PCI UART

    +
    • + +
  • +

    Syba Tech SD-LAB PCI-4S2P-550-ECP

    +
    • + +
  • +

    SIIG Cyber I/O PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber 2P1S PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber 2S1P PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber 4S PCI 16C550/16C650/16C850

    +
    • + +
  • +

    SIIG Cyber Serial (Single and Dual) PCI 16C550/16C650/16C850

    +
    • + +
  • +

    Syba Tech Ltd. PCI-4S2P-550-ECP

    +
    • + +
  • +

    Titan PCI-200H and PCI-800H

    +
    • + +
  • +

    US Robotics (3Com) 3CP5609 modem

    +
    • + +
  • +

    VScom PCI-400 and PCI-800

    +
    • +
+ +
+
+

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

+ +

The sr(4) driver supports +the following hardware:

+ +
    +
  • +

    SDL Communications RISCom/N2 ISA

    +
    • + +
  • +

    SDL Communications N2pci

    +
    • + +
  • +

    SDL Communications WANic 400/405 PCI

    +
    • +
+ +

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)

+
+ +
+
+

3.10 Sound Devices

+ +

The +snd_ad1816(4) +driver supports the following sound cards:

+ +
    +
  • +

    Analog Devices AD1816

    +
    • +
+ +

The +snd_als4000(4) +driver supports the following sound cards:

+ +
    +
  • +

    Avance Logic ALS4000

    +
    • +
+ +

The +snd_atiixp(4) +driver supports the following audio chipsets:

+ +
    +
  • +

    ATI IXP 200

    +
    • + +
  • +

    ATI IXP 300

    +
    • + +
  • +

    ATI IXP 400

    +
    • +
+ +

The +snd_cmi(4) +driver supports the following sound cards:

+ +
    +
  • +

    CMedia CMI8338A

    +
    • + +
  • +

    CMedia CMI8338B

    +
    • + +
  • +

    CMedia CMI8738

    +
    • + +
  • +

    CMedia CMI8738B

    +
    • +
+ +

The +snd_cs4281(4) +driver supports the following sound cards:

+ +
    +
  • +

    Crystal Semiconductor CS4281

    +
    • +
+ +

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.

+ +

The +snd_ds1(4) +driver supports the following sound cards:

+ +
    +
  • +

    Yamaha DS-1

    +
    • + +
  • +

    Yamaha DS-1E

    +
    • +
+ +

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)

    +
    • +
+ +

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

    +
    • +
+ +

The +snd_ess(4) +driver supports the following sound cards:

+ +
    +
  • +

    Ensoniq ESS ISA PnP/non-PnP

    +
    • +
+ +

The +snd_fm801(4) +driver supports audio devices based on the following chipset:

+ +
    +
  • +

    Forte Media FM801

    +
    • +
+ +

The +snd_gusc(4) +driver supports the following sound cards:

+ +
    +
  • +

    Gravis UltraSound MAX

    +
    • + +
  • +

    Gravis UltraSound PnP

    +
    • +
+ +

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

    +
    • +
+ +

The +snd_maestro(4) +driver supports the following PCI sound cards:

+ +
    +
  • +

    ESS Technology Maestro-1

    +
    • + +
  • +

    ESS Technology Maestro-2

    +
    • + +
  • +

    ESS Technology Maestro-2E

    +
    • +
+ +

The +snd_maestro3(4) +driver supports the following audio devices:

+ +
    +
  • +

    ESS Technology Allegro-1

    +
    • + +
  • +

    ESS Technology Maestro3

    +
    • +
+ +

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

    +
    • +
+ +

The +snd_neomagic(4) +driver supports the following audio devices:

+ +
    +
  • +

    NeoMagic 256AV

    +
    • + +
  • +

    NeoMagic 256ZX

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +

The +snd_t4dwave(4) +driver supports the following audio devices:

+ +
    +
  • +

    Acer Labs M5451

    +
    • + +
  • +

    SIS 7018

    +
    • + +
  • +

    Trident 4DWave DX

    +
    • + +
  • +

    Trident 4DWave NX

    +
    • +
+ +

The +snd_via8233(4) +driver supports the following audio chipsets:

+ +
    +
  • +

    VIA VT8233

    +
    • + +
  • +

    VIA VT8233A

    +
    • + +
  • +

    VIA VT8233C

    +
    • + +
  • +

    VIA VT8235

    +
    • + +
  • +

    VIA VT8237

    +
    • + +
  • +

    VIA VT8251

    +
    • +
+ +

The +snd_via82c686(4) +driver supports audio devices based on the following chipset:

+ +
    +
  • +

    VIA 82C686A

    +
    • +
+ +

The +snd_vibes(4) +driver supports audio devices based on the following chipset:

+ +
    +
  • +

    S3 SonicVibes

    +
    • +
+
+ +
+
+

3.11 Camera and Video Capture +Devices

+ +

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

    +
    • +
+ +

Connectix QuickCam

+
+ +
+
+

3.12 USB Devices

+ +

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

+ +
+
+

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

+
+
+ +
+
+

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

+
+
+ +

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)

    +
    • +
+ +

The +uhci(4) driver +supports all UHCI v1.1 compliant controllers including:

+ +
    +
  • +

    Intel 82371AB/EB (PIIX4)

    +
    • + +
  • +

    Intel 82371SB (PIIX3)

    +
    • + +
  • +

    VIA 83C572

    +
    • +
+ +

USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)

+ +

Hubs

+ +

Keyboards ( +ukbd(4) +driver)

+ +

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

    +
    • +
+ +
+
+

The following devices are supported by the +urio(4) +driver:

+ +
    +
  • +

    Diamond MultiMedia Rio 500

    +
    • + +
  • +

    Diamond MultiMedia Rio 600

    +
    • + +
  • +

    Diamond MultiMedia Rio 800

    +
    • +
+ +

Devices supported by the +umodem(4) driver +include:

+ +
    +
  • +

    3Com 5605

    +
    • + +
  • +

    Curitel PC5740 Wireless Modem

    +
    • + +
  • +

    Metricom Ricochet GS USB wireless modem

    +
    • + +
  • +

    Sierra MC5720 Wireless Modem

    +
    • + +
  • +

    Yamaha Broadband Wireless Router RTW65b

    +
    • + +
  • +

    ELSA MicroLink 56k USB modem

    +
    • +
+ +

Mice ( +ums(4) +driver)

+ +

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

    +
    • +
+ +

The +ubsa(4) driver +supports the following adapters:

+ +
    +
  • +

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

    +
    • + +
  • +

    Belkin F5U103

    +
    • + +
  • +

    Belkin F5U120

    +
    • + +
  • +

    e-Tek Labs Kwik232

    +
    • + +
  • +

    GoHubs GoCOM232

    +
    • + +
  • +

    Huawei Technologies Mobile card (3G)

    +
    • + +
  • +

    Novatel Wireless Merlin U740 (only basic modem port supported)

    +
    • + +
  • +

    Option Globetrotter 3G (aka Vodafone Mobile Connect Card 3G)

    +
    • + +
  • +

    Option Globetrotter 3G Quad

    +
    • + +
  • +

    Option Globetrotter 3G Fusion (no WLAN support, only basic 3G modem port)

    +
    • + +
  • +

    Option Globetrotter 3G Fusion Quad (no WLAN support)

    +
    • + +
  • +

    Peracom single port serial adapter

    +
    • +
+ +

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

+ +

The +ubser(4) driver +provides support for the BWCT console management serial adapters.

+ +

The +uftdi(4) driver +supports the following adapters:

+ +
    +
  • +

    B&B Electronics USB->RS422/485 adapter

    +
    • + +
  • +

    HP USB-Serial adapter shipped with some HP laptops

    +
    • + +
  • +

    Inland UAS111

    +
    • + +
  • +

    QVS USC-1000

    +
    • +
+ +

The +uplcom(4) driver +supports the following adapters:

+ +
    +
  • +

    ATEN UC-232A

    +
    • + +
  • +

    BAFO BF-800

    +
    • + +
  • +

    BAFO BF-810

    +
    • + +
  • +

    ELECOM UC-SGT

    +
    • + +
  • +

    HAL Corporation Crossam2+USB IR commander

    +
    • + +
  • +

    Hama USB RS-232 Serial Adapter

    +
    • + +
  • +

    IOGEAR UC-232A

    +
    • + +
  • +

    I/O DATA USB-RSAQ

    +
    • + +
  • +

    I/O DATA USB-RSAQ2

    +
    • + +
  • +

    I/O DATA USB-RSAQ3

    +
    • + +
  • +

    PLANEX USB-RS232 URS-03

    +
    • + +
  • +

    RATOC REX-USB60

    +
    • + +
  • +

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

    +
    • + +
  • +

    SOURCENEXT KeikaiDenwa 8 (with and without charger)

    +
    • + +
  • +

    Sony Ericsson USB Cable (Susteen USB Data Cable)

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Acer Acerscan: 320U, 620U, 640U, 640BT, 1240U, C310U;

    +
    • + +
  • +

    AGFA SnapScan: 1212U, 1236U, e20, e25, e26, e40, e50, e52, SnapScan Touch;

    +
    • + +
  • +

    Avision 1200U

    +
    • + +
  • +

    Canon CanoScan: D660U, N656U, N676U, N1220U, LIDE 20, LIDE 25, LIDE 30;

    +
    • + +
  • +

    Epson Perfection: 610, 636U / 636Photo, 640U, 1200U / 1200Photo, 1240U / 1240Photo, +1250, 1260, 1270, 1600, 1640SU, 1650, 1660, 1670, 2480, 3200, 3500, 3590, 4200, 4990;

    +
    • + +
  • +

    Epson: GT-8400UF, GT-9300UF, GT-9700F;

    +
    • + +
  • +

    Epson Stylus: Photo RX425, CX3650, DX-5000, DX-5050, DX-6000, DX-6050 (and possibly +more in the CX-5000 and DX-3800..DX-7000 family);

    +
    • + +
  • +

    Hewlett Packard: Photosmart S20

    +
    • + +
  • +

    Hewlett Packard Scanjet: 2200C, 3300C, 3400CSE, 4100C, 4200C, 4300C, 5200C, 5300C, +5400C, 6200C, 6300C, 8200C, 8250C, 8290C;

    +
    • + +
  • +

    KYE ColorPage Vivid-Pro

    +
    • + +
  • +

    Microtek Phantom: 336CX, C6;

    +
    • + +
  • +

    Microtek ScanMaker: V6UL V6USL, X6U;

    +
    • + +
  • +

    Minolta 5400

    +
    • + +
  • +

    Mustek: 600 CU, 1200 CU, 1200 UB, 1200 USB;

    +
    • + +
  • +

    Mustek BearPaw: 1200F, 1200TA;

    +
    • + +
  • +

    NatSemi BearPaw 1200

    +
    • + +
  • +

    Nikon CoolScan LS40 ED

    +
    • + +
  • +

    Primax 6200

    +
    • + +
  • +

    Primax Colorado: 1200u, 600u, USB 19200, USB 9600;

    +
    • + +
  • +

    Primax: G2-200, G2-300, G2-600, G2600, G2E-300, G2E-3002, G2E-600, G2E600, G2X-300, +G600, ReadyScan 636i;

    +
    • + +
  • +

    Ultima 1200 UB Plus

    +
    • + +
  • +

    UMAX Astra: 1220U, 1236U, 2000U, 2100U, 2200U, 3400;

    +
    • + +
  • +

    Visioneer OneTouch: 3000, 5300, 7600, 6100, 6200, 8100, 8600;

    +
    • +
+ +

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

    +
    • + +
  • +

    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

    +
    • +
+ +

Audio Devices ( +uaudio(4) +driver)

+ +

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.13 IEEE 1394 (Firewire) +Devices

+ +

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 (CXD1947)

    +
    • + +
  • +

    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)

    +
    • +
+ +

Serial Bus Protocol 2 (SBP-2) storage devices ( +sbp(4) +driver)

+
+ +
+
+

3.14 Bluetooth Devices

+ +

The +ng_bt3c(4) +driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.

+ +

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

    +
    • +
+
+ +
+
+

3.15 Cryptographic +Accelerators

+ +

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

    +
    • +
+ +

The +safe(4) driver +supports cards containing any of the following chips:

+ +
    +
  • +

    SafeNet 1141

    +
    • + +
  • +

    SafeNet 1741

    +
    • +
+ +

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

    +
    • +
+
+ +
+
+

3.16 Miscellaneous

+ +

FAX-Modem/PCCARD

+ +
    +
  • +

    MELCO IGM-PCM56K/IGM-PCM56KH

    +
    • + +
  • +

    Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)

    +
    • +
+ +
+
+

Floppy drives ( +fdc(4) +driver)

+ +

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

+
+
+ +
+
+

Keyboards including:

+ + + +
+
+

Pointing devices including:

+ +
    +
  • +

    Bus mice and compatible devices ( +mse(4) +driver)

    +
    • + +
  • +

    PS/2 mice and compatible devices, including many laptop pointing devices ( +psm(4) +driver)

    +
    • + +
  • +

    Serial mice and compatible devices

    +
    • + +
  • +

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

+
+
+ +
+
+

“PC standard” parallel ports ( +ppc(4) +driver)

+ +

PC-compatible joysticks ( +joy(4) +driver)

+ +

PHS Data Communication Card/PCCARD

+ +
    +
  • +

    NTT DoCoMo P-in Comp@ct

    +
    • + +
  • +

    Panasonic KX-PH405

    +
    • + +
  • +

    SII MC-P200

    +
    • +
+ +
+
+

Xilinx XC6200-based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (xrpu 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/en/releases/6.3R/hardware-ia64.html b/en/releases/6.3R/hardware-ia64.html new file mode 100644 index 0000000000..4a50bd273a --- /dev/null +++ b/en/releases/6.3R/hardware-ia64.html @@ -0,0 +1,2999 @@ + + + + +FreeBSD/ia64 6.3-RELEASE Hardware Notes + + + + + +
+
+

FreeBSD/ia64 6.3-RELEASE Hardware +Notes

+ +

The FreeBSD Documentation Project

+ +

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

+ +
+
+ +
+
+
Table of Contents
+ +
1 Introduction
+ +
2 Supported Processors and Motherboards
+ +
+
+
2.1 Supported Devices Overview
+
+
+ +
3 Supported Devices
+ +
+
+
3.1 Disk Controllers
+ +
3.2 Ethernet Interfaces
+ +
3.3 Token Ring Interfaces
+ +
3.4 FDDI Interfaces
+ +
3.5 ATM Interfaces
+ +
3.6 Wireless Network Interfaces
+ +
3.7 Miscellaneous Networks
+ +
3.8 ISDN Interfaces
+ +
3.9 Serial Interfaces
+ +
3.10 Sound Devices
+ +
3.11 Camera and Video Capture Devices
+ +
3.12 USB Devices
+ +
3.13 IEEE 1394 (Firewire) Devices
+ +
3.14 Bluetooth Devices
+ +
3.15 Cryptographic Accelerators
+ +
3.16 Miscellaneous
+
+
+
+
+ +
+
+

This is a preliminary document. It is incomplete, and in need of additional content. +Please send additional information on IA-64 processors, motherboards, and various devices +working on FreeBSD to the FreeBSD IA64 +porting mailing list.

+
+
+ +
+
+

1 Introduction

+ +

This document contains the hardware compatibility notes for FreeBSD 6.3-RELEASE on the +IA-64 hardware platform (also referred to as FreeBSD/ia64 6.3-RELEASE). It lists devices +known to work on this platform, as well as some notes on boot-time kernel customization +that may be useful when attempting to configure support for new devices.

+ +
+
+

Note: This document includes information specific to the IA-64 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.

+
+
+ +

More information on FreeBSD/ia64 is contained on the FreeBSD/ia64 +Project page.

+
+ +
+
+

2 Supported Processors and +Motherboards

+ +

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.

+ +
+
+

2.1 Supported Devices Overview

+ +

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.

+
+
+ +
+
+

3 Supported Devices

+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.17 +2007/09/13 16:25:43 brueffer Exp $ + +

This section describes the devices currently known to be supported by with FreeBSD on +the IA-64 platform. 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

+ +

IDE/ATA controllers ( +ata(4) +driver)

+ +

Controllers supported by the +aac(4) driver +include:

+ +
    +
  • +

    Adaptec AAC-364

    +
    • + +
  • +

    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

    +
    • +
+ +

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 2920

    +
    • + +
  • +

    Adaptec 2930C

    +
    • + +
  • +

    Adaptec 2930U2

    +
    • + +
  • +

    Adaptec 2940

    +
    • + +
  • +

    Adaptec 2940J

    +
    • + +
  • +

    Adaptec 2940N

    +
    • + +
  • +

    Adaptec 2940U

    +
    • + +
  • +

    Adaptec 2940AU

    +
    • + +
  • +

    Adaptec 2940UW

    +
    • + +
  • +

    Adaptec 2940UW Dual

    +
    • + +
  • +

    Adaptec 2940UW Pro

    +
    • + +
  • +

    Adaptec 2940U2W

    +
    • + +
  • +

    Adaptec 2940U2B

    +
    • + +
  • +

    Adaptec 2950U2W

    +
    • + +
  • +

    Adaptec 2950U2B

    +
    • + +
  • +

    Adaptec 19160B

    +
    • + +
  • +

    Adaptec 29160B

    +
    • + +
  • +

    Adaptec 29160N

    +
    • + +
  • +

    Adaptec 3940

    +
    • + +
  • +

    Adaptec 3940U

    +
    • + +
  • +

    Adaptec 3940AU

    +
    • + +
  • +

    Adaptec 3940UW

    +
    • + +
  • +

    Adaptec 3940AUW

    +
    • + +
  • +

    Adaptec 3940U2W

    +
    • + +
  • +

    Adaptec 3950U2

    +
    • + +
  • +

    Adaptec 3960

    +
    • + +
  • +

    Adaptec 39160

    +
    • + +
  • +

    Adaptec 3985

    +
    • + +
  • +

    Adaptec 4944UW

    +
    • + +
  • +

    NEC PC-9821Xt13 (PC-98)

    +
    • + +
  • +

    NEC RvII26 (PC-98)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Many motherboards with on-board SCSI support

    +
    • +
+ +

The +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

    +
    • +
+ +

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

    +
    • +
+ +

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 P400

    +
    • + +
  • +

    HP Smart Array P400i

    +
    • + +
  • +

    HP Smart Array P600

    +
    • + +
  • +

    HP Smart Array P800

    +
    • + +
  • +

    HP Modular Smart Array 20 (MSA20)

    +
    • + +
  • +

    HP Modular Smart Array 500 (MSA500)

    +
    • +
+ +

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

    +
    • +
+ +

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.

+ +

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

    +
    • +
+ +

The +mfi(4) driver +supports the following hardware:

+ +
    +
  • +

    LSI MegaRAID SAS 8408E

    +
    • + +
  • +

    LSI MegaRAID SAS 8480E

    +
    • + +
  • +

    Dell PERC5/i

    +
    • +
+ +

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.

+ +

Controllers supported by the +mly(4) driver +include:

+ +
    +
  • +

    Mylex AcceleRAID 160

    +
    • + +
  • +

    Mylex AcceleRAID 170

    +
    • + +
  • +

    Mylex AcceleRAID 352

    +
    • + +
  • +

    Mylex eXtremeRAID 2000

    +
    • + +
  • +

    Mylex eXtremeRAID 3000

    +
    • +
+ +

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

+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    LSI Logic AS1064, LSI Logic AS1068

    +
    • + +
  • +

    LSI Logic FC909 (1Gb/s Fibre Channel)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Dell PowerEdge 1750 thru 2850

    +
    • + +
  • +

    IBM eServer xSeries 335

    +
    • +
+ +

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

+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    ATAPI IDE interface ( +acd(4))

    +
    • +
+ +
+
+
+ +
+
+

3.2 Ethernet Interfaces

+ +

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

    +
    • +
+ +

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)

    +
    • + +
  • +

    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 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 +cue(4) driver +supports CATC USB-EL1210A based USB Ethernet adapters including:

+ +
    +
  • +

    Belkin F5U011/F5U111

    +
    • + +
  • +

    CATC Netmate

    +
    • + +
  • +

    CATC Netmate II

    +
    • + +
  • +

    SmartBridges SmartLink

    +
    • +
+ +

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

+ +
    +
  • +

    DEC/Intel 21143

    +
    • + +
  • +

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

    +
    • + +
  • +

    ASIX Electronics AX88140A and AX88141

    +
    • + +
  • +

    Conexant LANfinity RS7112 (miniPCI)

    +
    • + +
  • +

    Davicom DM9009, DM9100, DM9102 and DM9102A

    +
    • + +
  • +

    Lite-On 82c168 and 82c169 PNIC

    +
    • + +
  • +

    Lite-On/Macronix 82c115 PNIC II

    +
    • + +
  • +

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

    +
    • + +
  • +

    Xircom X3201 (cardbus only)

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Abocom FE2500

    +
    • + +
  • +

    Accton EN1217 (98715A)

    +
    • + +
  • +

    Accton EN2242 MiniPCI

    +
    • + +
  • +

    Adico AE310TX (98715A)

    +
    • + +
  • +

    Alfa Inc GFC2204 (ASIX AX88140A)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Built in DE500-BA on DEC Alpha workstations (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

    +
    • +
+ +

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

    +
    • +
+ +

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 and 82573 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 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)

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

    AMD Am79C971 PCnet-FAST

    +
    • + +
  • +

    AMD Am79C972 PCnet-FAST+

    +
    • + +
  • +

    AMD Am79C973/Am79C975 PCnet-FAST III

    +
    • + +
  • +

    AMD Am79C976 PCnet-PRO

    +
    • + +
  • +

    AMD Am79C978 PCnet-Home

    +
    • + +
  • +

    Allied-Telesis LA-PCI

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Compaq Evo N1015v Integrated Ethernet (8139C+)

    +
    • + +
  • +

    Corega CG-LAPCIGT Gigabit Ethernet (8169S)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

    +
    • + +
  • +

    LevelOne GNC-0105T (8169S)

    +
    • + +
  • +

    LinkSys EG1032 (32-bit PCI)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

Adapters supported by the rl(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

    Allied Telesyn AT2550

    +
    • + +
  • +

    Allied Telesyn AT2500TX

    +
    • + +
  • +

    Belkin F5D5000

    +
    • + +
  • +

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

    +
    • + +
  • +

    Compaq HNE-300

    +
    • + +
  • +

    CompUSA no-name 10/100 PCI Ethernet NIC

    +
    • + +
  • +

    Corega FEther CB-TXD

    +
    • + +
  • +

    Corega FEtherII CB-TXD

    +
    • + +
  • +

    D-Link DFE-528TX

    +
    • + +
  • +

    D-Link DFE-530TX+

    +
    • + +
  • +

    D-Link DFE-538TX

    +
    • + +
  • +

    D-Link DFE-690TXD

    +
    • + +
  • +

    Edimax EP-4103DL CardBus

    +
    • + +
  • +

    Encore ENL832-TX 10/100 M PCI

    +
    • + +
  • +

    Farallon NetLINE 10/100 PCI

    +
    • + +
  • +

    Genius GF100TXR

    +
    • + +
  • +

    GigaFast Ethernet EE100-AXP

    +
    • + +
  • +

    KTX-9130TX 10/100 Fast Ethernet

    +
    • + +
  • +

    LevelOne FPC-0106TX

    +
    • + +
  • +

    Longshine LCS-8038TX-R

    +
    • + +
  • +

    NDC Communications NE100TX-E

    +
    • + +
  • +

    Netronix Inc. EA-1210 NetEther 10/100

    +
    • + +
  • +

    Nortel Networks 10/100BaseTX

    +
    • + +
  • +

    OvisLink LEF-8129TX

    +
    • + +
  • +

    OvisLink LEF-8139TX

    +
    • + +
  • +

    Peppercon AG ROL-F

    +
    • + +
  • +

    Planex FNW-3603-TX

    +
    • + +
  • +

    Planex FNW-3800-TX

    +
    • + +
  • +

    SMC EZ Card 10/100 PCI 1211-TX

    +
    • + +
  • +

    SOHO (PRAGMATIC) UE-1211C

    +
    • +
+ +

Adapters supported by the sf(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    ANA-62020 64-bit single port 100baseFX adapter

    +
    • +
+ +

The +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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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

+
+ +
+
+

3.3 Token Ring Interfaces

+
+ +
+
+

3.4 FDDI Interfaces

+
+ +
+
+

3.5 ATM Interfaces

+
+ +
+
+

3.6 Wireless Network Interfaces

+ +

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

+
+ +
+
+

3.7 Miscellaneous +Networks

+
+ +
+
+

3.8 ISDN Interfaces

+
+ +
+
+

3.9 Serial Interfaces

+ +

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

    +
    • + +
  • +

    SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.

    +
    • + +
  • +

    Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.

    +
    • +
+ +

PCI-Based multi-port serial boards ( +puc(4) +driver)

+ +
    +
  • +

    Diva Serial (GSP) Multiport UART

    +
    • +
+ +
+
+
+ +
+
+

3.10 Sound Devices

+
+ +
+
+

3.11 Camera and Video Capture +Devices

+
+ +
+
+

3.12 USB Devices

+ +

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

+ +
+
+

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

+
+
+ +
+
+

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

+
+
+ +

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)

    +
    • +
+ +

The +uhci(4) driver +supports all UHCI v1.1 compliant controllers including:

+ +
    +
  • +

    Intel 82371AB/EB (PIIX4)

    +
    • + +
  • +

    Intel 82371SB (PIIX3)

    +
    • + +
  • +

    VIA 83C572

    +
    • +
+ +

USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)

+ +

Hubs

+ +

Keyboards ( +ukbd(4) +driver)

+ +

Mice ( +ums(4) +driver)

+ +

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

    +
    • +
+
+ +
+
+

3.13 IEEE 1394 (Firewire) +Devices

+ +

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 (CXD1947)

    +
    • + +
  • +

    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)

    +
    • +
+
+ +
+
+

3.14 Bluetooth Devices

+
+ +
+
+

3.15 Cryptographic +Accelerators

+
+ +
+
+

3.16 Miscellaneous

+ +

Keyboards including:

+ + + +
+
+

Pointing devices including:

+ +
    +
  • +

    Serial mice and compatible devices

    +
    • + +
  • +

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

+
+
+ +
+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/hardware-pc98.html b/en/releases/6.3R/hardware-pc98.html new file mode 100644 index 0000000000..d88711037a --- /dev/null +++ b/en/releases/6.3R/hardware-pc98.html @@ -0,0 +1,4846 @@ + + + + +FreeBSD/pc98 6.3-RELEASE Hardware Notes + + + + + +
+
+

FreeBSD/pc98 6.3-RELEASE Hardware +Notes

+ +

The FreeBSD Documentation Project

+ +

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

+ +
+
+ +
+
+
Table of Contents
+ +
1 Introduction
+ +
2 Supported Systems
+ +
3 Supported Devices
+ +
+
+
3.1 Disk Controllers
+ +
3.2 Ethernet Interfaces
+ +
3.3 Token Ring Interfaces
+ +
3.4 FDDI Interfaces
+ +
3.5 ATM Interfaces
+ +
3.6 Wireless Network Interfaces
+ +
3.7 Miscellaneous Networks
+ +
3.8 ISDN Interfaces
+ +
3.9 Serial Interfaces
+ +
3.10 Sound Devices
+ +
3.11 Camera and Video Capture Devices
+ +
3.12 USB Devices
+ +
3.13 IEEE 1394 (Firewire) Devices
+ +
3.14 Bluetooth Devices
+ +
3.15 Cryptographic Accelerators
+ +
3.16 Miscellaneous
+
+
+
+
+ +
+

1 Introduction

+ +

This document contains the hardware compatibility notes for FreeBSD 6.3-RELEASE on the +NEC PC-98x1 hardware platform (also referred to as FreeBSD/pc98 6.3-RELEASE). It lists +devices known to work on this platform, as well as some notes on boot-time kernel +customization that may be useful when attempting to configure support for new +devices.

+ +
+
+

Note: This document includes information specific to the NEC PC-98x1 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.

+
+
+
+ +
+
+

2 Supported Systems

+ +

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.

+
+ +
+
+

3 Supported Devices

+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.17 +2007/09/13 16:25:43 brueffer Exp $ + +

This section describes the devices currently known to be supported by with FreeBSD on +the NEC PC-98x1 platform. 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

+ +

IDE/ATA controllers ( +ata(4) +driver)

+ +

IDE/ATA controllers (wdc driver)

+ +
    +
  • +

    On-board IDE controller

    +
    • +
+ +
+
+

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)

    +
    • +
+ +

The +adw(4) driver +supports SCSI controllers including:

+ +
    +
  • +

    AdvanSys ABP940UW/ABP3940UW

    +
    • + +
  • +

    AdvanSys ABP950UW

    +
    • + +
  • +

    AdvanSys ABP970UW

    +
    • + +
  • +

    AdvanSys ABP3940U2W

    +
    • + +
  • +

    AdvanSys ABP3950U2W

    +
    • +
+ +

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 2920

    +
    • + +
  • +

    Adaptec 2930C

    +
    • + +
  • +

    Adaptec 2930U2

    +
    • + +
  • +

    Adaptec 2940

    +
    • + +
  • +

    Adaptec 2940J

    +
    • + +
  • +

    Adaptec 2940N

    +
    • + +
  • +

    Adaptec 2940U

    +
    • + +
  • +

    Adaptec 2940AU

    +
    • + +
  • +

    Adaptec 2940UW

    +
    • + +
  • +

    Adaptec 2940UW Dual

    +
    • + +
  • +

    Adaptec 2940UW Pro

    +
    • + +
  • +

    Adaptec 2940U2W

    +
    • + +
  • +

    Adaptec 2940U2B

    +
    • + +
  • +

    Adaptec 2950U2W

    +
    • + +
  • +

    Adaptec 2950U2B

    +
    • + +
  • +

    Adaptec 19160B

    +
    • + +
  • +

    Adaptec 29160B

    +
    • + +
  • +

    Adaptec 29160N

    +
    • + +
  • +

    Adaptec 3940

    +
    • + +
  • +

    Adaptec 3940U

    +
    • + +
  • +

    Adaptec 3940AU

    +
    • + +
  • +

    Adaptec 3940UW

    +
    • + +
  • +

    Adaptec 3940AUW

    +
    • + +
  • +

    Adaptec 3940U2W

    +
    • + +
  • +

    Adaptec 3950U2

    +
    • + +
  • +

    Adaptec 3960

    +
    • + +
  • +

    Adaptec 39160

    +
    • + +
  • +

    Adaptec 3985

    +
    • + +
  • +

    Adaptec 4944UW

    +
    • + +
  • +

    NEC PC-9821Xt13 (PC-98)

    +
    • + +
  • +

    NEC RvII26 (PC-98)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Many motherboards with on-board SCSI support

    +
    • +
+ +

The adapters supported by the +aic(4) driver +include:

+ +
    +
  • +

    Adaptec AHA-1505 (ISA)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Adaptec AHA-1535 (ISA)

    +
    • + +
  • +

    Creative Labs SoundBlaster SCSI host adapter (ISA)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    NEC PC-9801-100 (PC98)

    +
    • +
+ +

Controllers supported by the +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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    LSI Logic AS1064, LSI Logic AS1068

    +
    • + +
  • +

    LSI Logic FC909 (1Gb/s Fibre Channel)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Dell PowerEdge 1750 thru 2850

    +
    • + +
  • +

    IBM eServer xSeries 335

    +
    • +
+ +

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

+ +

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)

    +
    • +
+ +

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)

    +
    • +
+ +

Controllers supported by the +nsp(4) driver +include:

+ +
    +
  • +

    Alpha-Data AD-PCS201

    +
    • + +
  • +

    I-O DATA CBSC16

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    ATAPI IDE interface ( +acd(4))

    +
    • +
+ +
+
+
+ +
+
+

3.2 Ethernet Interfaces

+ +

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

    +
    • +
+ +

The +axe(4) driver +supports ASIX Electronics AX88172 based USB Ethernet adapters including:

+ +
    +
  • +

    Buffalo (Melco Inc.) LUA-U2-KTX

    +
    • + +
  • +

    D-Link DUB-E100, revision A

    +
    • + +
  • +

    LinkSys USB200M

    +
    • + +
  • +

    Netgear FA120

    +
    • + +
  • +

    Sitecom LN-029

    +
    • + +
  • +

    System TALKS Inc. SGC-X2UL

    +
    • +
+ +

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)

    +
    • + +
  • +

    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 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 +cue(4) driver +supports CATC USB-EL1210A based USB Ethernet adapters including:

+ +
    +
  • +

    Belkin F5U011/F5U111

    +
    • + +
  • +

    CATC Netmate

    +
    • + +
  • +

    CATC Netmate II

    +
    • + +
  • +

    SmartBridges SmartLink

    +
    • +
+ +

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

+ +
    +
  • +

    DEC/Intel 21143

    +
    • + +
  • +

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

    +
    • + +
  • +

    ASIX Electronics AX88140A and AX88141

    +
    • + +
  • +

    Conexant LANfinity RS7112 (miniPCI)

    +
    • + +
  • +

    Davicom DM9009, DM9100, DM9102 and DM9102A

    +
    • + +
  • +

    Lite-On 82c168 and 82c169 PNIC

    +
    • + +
  • +

    Lite-On/Macronix 82c115 PNIC II

    +
    • + +
  • +

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

    +
    • + +
  • +

    Xircom X3201 (cardbus only)

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Abocom FE2500

    +
    • + +
  • +

    Accton EN1217 (98715A)

    +
    • + +
  • +

    Accton EN2242 MiniPCI

    +
    • + +
  • +

    Adico AE310TX (98715A)

    +
    • + +
  • +

    Alfa Inc GFC2204 (ASIX AX88140A)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Built in DE500-BA on DEC Alpha workstations (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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    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

    +
    • + +
  • +

    CyQ've ELA-010

    +
    • + +
  • +

    DEC EtherWorks DE305

    +
    • + +
  • +

    Danpex EN-6200P2

    +
    • + +
  • +

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

    +
    • + +
  • +

    D-Link DE-650/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)

    +
    • + +
  • +

    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

    +
    • + +
  • +

    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 5000

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Surecom EtherPerfect EP-427

    +
    • + +
  • +

    Surecom NE-34

    +
    • + +
  • +

    TDK 3000/3400/5670 Fast Etherenet/Modem

    +
    • + +
  • +

    TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card

    +
    • + +
  • +

    TDK DFL5610WS Ethernet/Modem PC Card

    +
    • + +
  • +

    Telecom Device SuperSocket RE450T

    +
    • + +
  • +

    VIA VT86C926

    +
    • + +
  • +

    Winbond W89C940

    +
    • +
+ +

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

+ +

The em(4) driver supports +Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, +82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 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 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)

    +
    • +
+ +

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)

    +
    • +
+ +

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 PCMCIA Ethernet

    +
    • + +
  • +

    Eagle Tech NE200T

    +
    • + +
  • +

    Eiger Labs EPX-10BT

    +
    • + +
  • +

    Fujitsu FMV-J182, FMV-J182A

    +
    • + +
  • +

    Fujitsu MB86960A, MB86965A

    +
    • + +
  • +

    Fujitsu MBH10303, MBH10302 Ethernet PCMCIA

    +
    • + +
  • +

    Fujitsu Towa LA501 Ethernet

    +
    • + +
  • +

    HITACHI HT-4840-11

    +
    • + +
  • +

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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

Adapters supported by the +lge(4) driver +include:

+ +
    +
  • +

    SMC TigerCard 1000 (SMC9462SX)

    +
    • + +
  • +

    D-Link DGE-500SX

    +
    • +
+ +

The +lnc(4) driver +supports the following adapters:

+ +
    +
  • +

    Diamond HomeFree

    +
    • + +
  • +

    Hewlett Packard Vectra 486/66XM

    +
    • + +
  • +

    Hewlett Packard Vectra XU

    +
    • + +
  • +

    Isolan AT 4141-0 (16 bit)

    +
    • + +
  • +

    Isolan BICC

    +
    • + +
  • +

    Isolink 4110 (8 bit)

    +
    • + +
  • +

    Novell NE2100

    +
    • + +
  • +

    Novell NE32-VL

    +
    • +
+ +

Also supported are adapters working with the pcn(4) driver. The +lnc(4) driver +runs these in compatibility mode, thus the pcn(4) driver should be preferred.

+ +

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

    +
    • +
+ +

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 (32-bit PCI) and EG1064 (64-bit PCI)

    +
    • + +
  • +

    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)

    +
    • +
+ +

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

+ +
    +
  • +

    AMD Am79C971 PCnet-FAST

    +
    • + +
  • +

    AMD Am79C972 PCnet-FAST+

    +
    • + +
  • +

    AMD Am79C973/Am79C975 PCnet-FAST III

    +
    • + +
  • +

    AMD Am79C976 PCnet-PRO

    +
    • + +
  • +

    AMD Am79C978 PCnet-Home

    +
    • + +
  • +

    Allied-Telesis LA-PCI

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Compaq Evo N1015v Integrated Ethernet (8139C+)

    +
    • + +
  • +

    Corega CG-LAPCIGT Gigabit Ethernet (8169S)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

    +
    • + +
  • +

    LevelOne GNC-0105T (8169S)

    +
    • + +
  • +

    LinkSys EG1032 (32-bit PCI)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

Adapters supported by the rl(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

    Allied Telesyn AT2550

    +
    • + +
  • +

    Allied Telesyn AT2500TX

    +
    • + +
  • +

    Belkin F5D5000

    +
    • + +
  • +

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

    +
    • + +
  • +

    Compaq HNE-300

    +
    • + +
  • +

    CompUSA no-name 10/100 PCI Ethernet NIC

    +
    • + +
  • +

    Corega FEther CB-TXD

    +
    • + +
  • +

    Corega FEtherII CB-TXD

    +
    • + +
  • +

    D-Link DFE-528TX

    +
    • + +
  • +

    D-Link DFE-530TX+

    +
    • + +
  • +

    D-Link DFE-538TX

    +
    • + +
  • +

    D-Link DFE-690TXD

    +
    • + +
  • +

    Edimax EP-4103DL CardBus

    +
    • + +
  • +

    Encore ENL832-TX 10/100 M PCI

    +
    • + +
  • +

    Farallon NetLINE 10/100 PCI

    +
    • + +
  • +

    Genius GF100TXR

    +
    • + +
  • +

    GigaFast Ethernet EE100-AXP

    +
    • + +
  • +

    KTX-9130TX 10/100 Fast Ethernet

    +
    • + +
  • +

    LevelOne FPC-0106TX

    +
    • + +
  • +

    Longshine LCS-8038TX-R

    +
    • + +
  • +

    NDC Communications NE100TX-E

    +
    • + +
  • +

    Netronix Inc. EA-1210 NetEther 10/100

    +
    • + +
  • +

    Nortel Networks 10/100BaseTX

    +
    • + +
  • +

    OvisLink LEF-8129TX

    +
    • + +
  • +

    OvisLink LEF-8139TX

    +
    • + +
  • +

    Peppercon AG ROL-F

    +
    • + +
  • +

    Planex FNW-3603-TX

    +
    • + +
  • +

    Planex FNW-3800-TX

    +
    • + +
  • +

    SMC EZ Card 10/100 PCI 1211-TX

    +
    • + +
  • +

    SOHO (PRAGMATIC) UE-1211C

    +
    • +
+ +

The +rue(4) driver +supports RealTek RTL8150 based USB Ethernet adapters including:

+ +
    +
  • +

    Buffalo (Melco Inc.) LUA-KTX

    +
    • + +
  • +

    Green House GH-USB100B

    +
    • + +
  • +

    LinkSys USB100M

    +
    • + +
  • +

    Billionton 10/100 FastEthernet USBKR2

    +
    • +
+ +

Adapters supported by the sf(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    ANA-62020 64-bit single port 100baseFX adapter

    +
    • +
+ +

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

+ +
    +
  • +

    @Nifty FNECHARD IFC USUP-TX

    +
    • + +
  • +

    MELCO LGY-PCI-TXC

    +
    • + +
  • +

    Netgear FA311-TX (DP83815)

    +
    • + +
  • +

    Netgear FA312-TX (DP83815)

    +
    • + +
  • +

    SiS 630, 635, and 735 motherboard chipsets

    +
    • + +
  • +

    Soekris Engineering net45xx, net48xx, lan1621, and lan1641

    +
    • +
+ +

Adapters supported by the sk(4) driver +include:

+ +
    +
  • +

    3Com 3C940 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Belkin F5D5005 single port, 1000baseT adapter

    +
    • + +
  • +

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

    +
    • + +
  • +

    Linksys EG1032 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

    +
    • +
+ +

The +snc(4) driver +supports the following cards:

+ +
    +
  • +

    National Semiconductor DP83934AVQB

    +
    • + +
  • +

    NEC PC-9801-83

    +
    • + +
  • +

    NEC PC-9801-84

    +
    • + +
  • +

    NEC PC-9801-103

    +
    • + +
  • +

    NEC PC-9801-104

    +
    • + +
  • +

    NEC PC-9801N-15

    +
    • + +
  • +

    NEC PC-9801N-25

    +
    • + +
  • +

    NEC PC-9801N-J02 PCMCIA

    +
    • + +
  • +

    NEC PC-9801N-J02R PCMCIA

    +
    • +
+ +

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

+ +

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

+ +
    +
  • +

    D-Link DFE-530TXS

    +
    • + +
  • +

    D-Link DFE-550TX

    +
    • + +
  • +

    D-Link DFE-580TX

    +
    • +
+ +

The 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

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • +
+ +

The +udav(4) driver +supports the following adapters:

+ +
    +
  • +

    Corega FEther USB-TXC

    +
    • +
+ +

The +vge(4) driver +supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including:

+ +
    +
  • +

    VIA Networking LAN-on-motherboard Gigabit Ethernet

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    AOpen/Acer ALN-320

    +
    • + +
  • +

    D-Link DFE530-TX

    +
    • + +
  • +

    Hawking Technologies PN102TX

    +
    • +
+ +

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

    +
    • +
+ +

The wb(4) driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:

+ +
    +
  • +

    Trendware TE100-PCIE

    +
    • +
+ +

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

+
+ +
+
+

3.3 Token Ring Interfaces

+
+ +
+
+

3.4 FDDI Interfaces

+ +

DEC DEFPA PCI ( +fpa(4) +driver)

+
+ +
+
+

3.5 ATM Interfaces

+ +

Midway-based ATM interfaces (en(4) driver)

+ +

FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and +fatm(4) +drivers)

+ +

IDT NICStAR 77201/211-based ATM Adapters ( +idt(4) +driver)

+ +

FORE Systems, Inc. HE155 and HE622 ATM interfaces ( +hatm(4) +driver)

+ +

IDT77252-based ATM cards ( +patm(4) +driver)

+
+ +
+
+

3.6 Wireless Network Interfaces

+ +

Cisco/Aironet 802.11b wireless adapters (an(4) driver)

+ +

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

+ +

Cards supported by the +awi(4) driver +include:

+ +
    +
  • +

    BayStack 650

    +
    • + +
  • +

    BayStack 660

    +
    • + +
  • +

    Icom SL-200

    +
    • + +
  • +

    Melco WLI-PCM

    +
    • + +
  • +

    NEL SSMagic

    +
    • + +
  • +

    Netwave AirSurfer Plus

    +
    • + +
  • +

    Netwave AirSurfer Pro

    +
    • + +
  • +

    Nokia C020 WLAN

    +
    • + +
  • +

    Farallon SkyLINE

    +
    • +
+ +

The original Xircom Netwave AirSurfer is supported by the cnw(4) driver.

+ +

Cards supported by the +cnw(4) driver +include:

+ +
    +
  • +

    Xircom CreditCard Netwave

    +
    • + +
  • +

    NetWave AirSurfer

    +
    • +
+ +

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

+ +

Raytheon Raylink 2.4GHz wireless adapters ( +ray(4) +driver)

+ +

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)

+
+ +
+
+

3.7 Miscellaneous +Networks

+ +

The ce(4) driver supports +the following models of Tau-PCI/32 WAN adapters:

+ +
    +
  • +

    Cronyx Tau-PCI/32

    +
    • + +
  • +

    Cronyx Tau-PCI/32-Lite

    +
    • +
+ +

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

    +
    • +
+
+ +
+
+

3.8 ISDN Interfaces

+
+ +
+
+

3.9 Serial Interfaces

+ +

Internel serial interfaces ( +sio(4) +driver)

+ +
    +
  • +

    PC-9801 on-board

    +
    • + +
  • +

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

    +
    • +
+ +
+
+

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

+ +
    +
  • +

    COM2 (flags 0x01000000)

    +
    • + +
  • +

    COM3 (flags 0x02000000)

    +
    • +
+ +
+
+

NEC PC-9801-120 ( +sio(4) +driver)

+ +
+
+

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

+
+
+ +

Microcore MC-16550, MC-16550II, MC-RS98 ( +sio(4) +driver)

+ +
+
+

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

+
+
+ +

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

+ +
+
+

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

+
+
+ +

Media Intelligent RSB-384 ( +sio(4) +driver)

+ +
+
+

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

+
+
+ +

I-O DATA RSA-98III ( +sio(4) +driver)

+ +
+
+

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

+
+
+ +

Hayes ESP98 ( +sio(4) +driver)

+ +
+
+

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

+
+
+
+ +
+
+

3.10 Sound Devices

+ +

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

+ +
    +
  • +

    NEC A-MATE internal sound

    +
    • + +
  • +

    Q-Vision WaveStar, WaveMaster

    +
    • +
+ +
+
+

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

+ +

Creative Technologies SoundBlaster(98) (sb(4) driver)

+ +

I-O DATA CD-BOX (sb(4) driver)

+ +

MPU-401 and compatible interfaces (mpu driver)

+ +
    +
  • +

    Q-Vision WaveStar

    +
    • +
+ +
+
+
+ +
+
+

3.11 Camera and Video Capture +Devices

+ +

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

    +
    • +
+
+ +
+
+

3.12 USB Devices

+ +

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

+ +
+
+

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

+
+
+ +
+
+

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

+
+
+ +

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)

    +
    • +
+ +

The +uhci(4) driver +supports all UHCI v1.1 compliant controllers including:

+ +
    +
  • +

    Intel 82371AB/EB (PIIX4)

    +
    • + +
  • +

    Intel 82371SB (PIIX3)

    +
    • + +
  • +

    VIA 83C572

    +
    • +
+ +

USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)

+ +

Hubs

+ +

Keyboards ( +ukbd(4) +driver)

+ +

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

    +
    • +
+ +
+
+

The following devices are supported by the +urio(4) +driver:

+ +
    +
  • +

    Diamond MultiMedia Rio 500

    +
    • + +
  • +

    Diamond MultiMedia Rio 600

    +
    • + +
  • +

    Diamond MultiMedia Rio 800

    +
    • +
+ +

Devices supported by the +umodem(4) driver +include:

+ +
    +
  • +

    3Com 5605

    +
    • + +
  • +

    Curitel PC5740 Wireless Modem

    +
    • + +
  • +

    Metricom Ricochet GS USB wireless modem

    +
    • + +
  • +

    Sierra MC5720 Wireless Modem

    +
    • + +
  • +

    Yamaha Broadband Wireless Router RTW65b

    +
    • + +
  • +

    ELSA MicroLink 56k USB modem

    +
    • +
+ +

Mice ( +ums(4) +driver)

+ +

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

    +
    • +
+ +

The +ubsa(4) driver +supports the following adapters:

+ +
    +
  • +

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

    +
    • + +
  • +

    Belkin F5U103

    +
    • + +
  • +

    Belkin F5U120

    +
    • + +
  • +

    e-Tek Labs Kwik232

    +
    • + +
  • +

    GoHubs GoCOM232

    +
    • + +
  • +

    Huawei Technologies Mobile card (3G)

    +
    • + +
  • +

    Novatel Wireless Merlin U740 (only basic modem port supported)

    +
    • + +
  • +

    Option Globetrotter 3G (aka Vodafone Mobile Connect Card 3G)

    +
    • + +
  • +

    Option Globetrotter 3G Quad

    +
    • + +
  • +

    Option Globetrotter 3G Fusion (no WLAN support, only basic 3G modem port)

    +
    • + +
  • +

    Option Globetrotter 3G Fusion Quad (no WLAN support)

    +
    • + +
  • +

    Peracom single port serial adapter

    +
    • +
+ +

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

+ +

The +ubser(4) driver +provides support for the BWCT console management serial adapters.

+ +

The +uftdi(4) driver +supports the following adapters:

+ +
    +
  • +

    B&B Electronics USB->RS422/485 adapter

    +
    • + +
  • +

    HP USB-Serial adapter shipped with some HP laptops

    +
    • + +
  • +

    Inland UAS111

    +
    • + +
  • +

    QVS USC-1000

    +
    • +
+ +

The +uplcom(4) driver +supports the following adapters:

+ +
    +
  • +

    ATEN UC-232A

    +
    • + +
  • +

    BAFO BF-800

    +
    • + +
  • +

    BAFO BF-810

    +
    • + +
  • +

    ELECOM UC-SGT

    +
    • + +
  • +

    HAL Corporation Crossam2+USB IR commander

    +
    • + +
  • +

    Hama USB RS-232 Serial Adapter

    +
    • + +
  • +

    IOGEAR UC-232A

    +
    • + +
  • +

    I/O DATA USB-RSAQ

    +
    • + +
  • +

    I/O DATA USB-RSAQ2

    +
    • + +
  • +

    I/O DATA USB-RSAQ3

    +
    • + +
  • +

    PLANEX USB-RS232 URS-03

    +
    • + +
  • +

    RATOC REX-USB60

    +
    • + +
  • +

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

    +
    • + +
  • +

    SOURCENEXT KeikaiDenwa 8 (with and without charger)

    +
    • + +
  • +

    Sony Ericsson USB Cable (Susteen USB Data Cable)

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Acer Acerscan: 320U, 620U, 640U, 640BT, 1240U, C310U;

    +
    • + +
  • +

    AGFA SnapScan: 1212U, 1236U, e20, e25, e26, e40, e50, e52, SnapScan Touch;

    +
    • + +
  • +

    Avision 1200U

    +
    • + +
  • +

    Canon CanoScan: D660U, N656U, N676U, N1220U, LIDE 20, LIDE 25, LIDE 30;

    +
    • + +
  • +

    Epson Perfection: 610, 636U / 636Photo, 640U, 1200U / 1200Photo, 1240U / 1240Photo, +1250, 1260, 1270, 1600, 1640SU, 1650, 1660, 1670, 2480, 3200, 3500, 3590, 4200, 4990;

    +
    • + +
  • +

    Epson: GT-8400UF, GT-9300UF, GT-9700F;

    +
    • + +
  • +

    Epson Stylus: Photo RX425, CX3650, DX-5000, DX-5050, DX-6000, DX-6050 (and possibly +more in the CX-5000 and DX-3800..DX-7000 family);

    +
    • + +
  • +

    Hewlett Packard: Photosmart S20

    +
    • + +
  • +

    Hewlett Packard Scanjet: 2200C, 3300C, 3400CSE, 4100C, 4200C, 4300C, 5200C, 5300C, +5400C, 6200C, 6300C, 8200C, 8250C, 8290C;

    +
    • + +
  • +

    KYE ColorPage Vivid-Pro

    +
    • + +
  • +

    Microtek Phantom: 336CX, C6;

    +
    • + +
  • +

    Microtek ScanMaker: V6UL V6USL, X6U;

    +
    • + +
  • +

    Minolta 5400

    +
    • + +
  • +

    Mustek: 600 CU, 1200 CU, 1200 UB, 1200 USB;

    +
    • + +
  • +

    Mustek BearPaw: 1200F, 1200TA;

    +
    • + +
  • +

    NatSemi BearPaw 1200

    +
    • + +
  • +

    Nikon CoolScan LS40 ED

    +
    • + +
  • +

    Primax 6200

    +
    • + +
  • +

    Primax Colorado: 1200u, 600u, USB 19200, USB 9600;

    +
    • + +
  • +

    Primax: G2-200, G2-300, G2-600, G2600, G2E-300, G2E-3002, G2E-600, G2E600, G2X-300, +G600, ReadyScan 636i;

    +
    • + +
  • +

    Ultima 1200 UB Plus

    +
    • + +
  • +

    UMAX Astra: 1220U, 1236U, 2000U, 2100U, 2200U, 3400;

    +
    • + +
  • +

    Visioneer OneTouch: 3000, 5300, 7600, 6100, 6200, 8100, 8600;

    +
    • +
+ +

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

    +
    • + +
  • +

    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

    +
    • +
+ +

Audio Devices ( +uaudio(4) +driver)

+ +

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.13 IEEE 1394 (Firewire) +Devices

+
+ +
+
+

3.14 Bluetooth Devices

+ +

The +ng_bt3c(4) +driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.

+ +

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

    +
    • +
+
+ +
+
+

3.15 Cryptographic +Accelerators

+ +

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

    +
    • +
+ +

The +safe(4) driver +supports cards containing any of the following chips:

+ +
    +
  • +

    SafeNet 1141

    +
    • + +
  • +

    SafeNet 1741

    +
    • +
+ +

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

    +
    • +
+
+ +
+
+

3.16 Miscellaneous

+ +

FAX-Modem/PCCARD

+ +
    +
  • +

    MELCO IGM-PCM56K/IGM-PCM56KH

    +
    • + +
  • +

    Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)

    +
    • +
+ +
+
+

Floppy drives ( +fdc(4) +driver)

+ +

Keyboards including:

+ +
    +
  • +

    Standard keyboards

    +
    • + +
  • +

    USB keyboards ( +ukbd(4) +driver)

    +
    • +
+ +
+
+

Pointing devices including:

+ +
    +
  • +

    Bus mice and compatible devices ( +mse(4) +driver)

    +
    • + +
  • +

    Serial mice and compatible devices

    +
    • + +
  • +

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

+
+
+ +
+
+

“PC-9821 standard” parallel ports ( +ppc(4) +driver)

+ +

Joystick port of SoundBlaster(98) ( +joy(4) +driver)

+ +

PHS Data Communication Card/PCCARD

+ +
    +
  • +

    NTT DoCoMo P-in Comp@ct

    +
    • + +
  • +

    Panasonic KX-PH405

    +
    • + +
  • +

    SII MC-P200

    +
    • +
+ +
+
+

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/en/releases/6.3R/hardware-sparc64.html b/en/releases/6.3R/hardware-sparc64.html new file mode 100644 index 0000000000..8778bb7bc1 --- /dev/null +++ b/en/releases/6.3R/hardware-sparc64.html @@ -0,0 +1,2105 @@ + + + + +FreeBSD/sparc64 6.3-RELEASE Hardware Notes + + + + + +
+
+

FreeBSD/sparc64 6.3-RELEASE Hardware +Notes

+ +

The FreeBSD Documentation Project

+ +

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

+ +
+
+ +
+
+
Table of Contents
+ +
1 Introduction
+ +
2 Supported Systems
+ +
+
+
2.1 Fully Supported Systems
+ +
2.2 Partially Supported Systems
+ +
2.3 Unsupported Systems
+
+
+ +
3 Supported Devices
+ +
+
+
3.1 Disk Controllers
+ +
3.2 Ethernet Interfaces
+ +
3.3 Token Ring Interfaces
+ +
3.4 FDDI Interfaces
+ +
3.5 ATM Interfaces
+ +
3.6 Wireless Network Interfaces
+ +
3.7 Miscellaneous Networks
+ +
3.8 ISDN Interfaces
+ +
3.9 Serial Interfaces
+ +
3.10 Sound Devices
+ +
3.11 Camera and Video Capture Devices
+ +
3.12 USB Devices
+ +
3.13 IEEE 1394 (Firewire) Devices
+ +
3.14 Bluetooth Devices
+ +
3.15 Cryptographic Accelerators
+ +
3.16 Miscellaneous
+
+
+
+
+ +
+

1 Introduction

+ +

This document contains the hardware compatibility notes for FreeBSD 6.3-RELEASE on the +UltraSPARC hardware platform (also referred to as FreeBSD/sparc64 6.3-RELEASE). It lists +devices known to work on this platform, as well as some notes on boot-time kernel +customization that may be useful when attempting to configure support for new +devices.

+ +
+
+

Note: This document includes information specific to the UltraSPARC hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.

+
+
+
+ +
+
+

2 Supported Systems

+ +

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

+ +

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

+ +

If you have a system that is not listed here, it may not have been tested with FreeBSD +6.3-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.

+ +
+
+

2.1 Fully Supported Systems

+ +

The following systems are fully supported by FreeBSD.

+ +
    +
  • +

    Blade 100

    +
    • + +
  • +

    Blade 150

    +
    • + +
  • +

    Enterprise 220R

    +
    • + +
  • +

    Enterprise 250

    +
    • + +
  • +

    Enterprise 420R

    +
    • + +
  • +

    Enterprise 450

    +
    • + +
  • +

    Fire V100

    +
    • + +
  • +

    Fire V120

    +
    • + +
  • +

    Netra t1 105

    +
    • + +
  • +

    Netra T1 AC200/DC200

    +
    • + +
  • +

    Netra t 1100

    +
    • + +
  • +

    Netra t 1120

    +
    • + +
  • +

    Netra t 1125

    +
    • + +
  • +

    Netra t 1400/1405

    +
    • + +
  • +

    Netra 120

    +
    • + +
  • +

    Netra X1

    +
    • + +
  • +

    SPARCEngine Ultra AXi

    +
    • + +
  • +

    SPARCEngine Ultra AXmp

    +
    • + +
  • +

    Ultra 1

    +
    • + +
  • +

    Ultra 1E

    +
    • + +
  • +

    Ultra 2

    +
    • + +
  • +

    Ultra 5

    +
    • + +
  • +

    Ultra 10

    +
    • + +
  • +

    Ultra 30

    +
    • + +
  • +

    Ultra 60

    +
    • + +
  • +

    Ultra 80

    +
    • +
+
+ +
+
+

2.2 Partially Supported Systems

+ +

The following systems are partially supported by FreeBSD. In particular the onboard +scsi controller in sbus systems is not supported.

+ +
    +
  • +

    Enterprise 3500

    +
    • + +
  • +

    Enterprise 4500

    +
    • +
+
+ +
+
+

2.3 Unsupported Systems

+ +

The following systems are not supported by FreeBSD. This may be due to lack of +processor support (UltraSPARC III), due to a quirk in the system design that makes +FreeBSD unstable, or due to lack of support for sufficient onboard devices to make +FreeBSD generally useful.

+ +
    +
  • +

    All systems containing UltraSPARC III processor(s).

    +
    • +
+
+
+ +
+
+

3 Supported Devices

+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.17 +2007/09/13 16:25:43 brueffer Exp $ + +

This section describes the devices currently known to be supported by with FreeBSD on +the UltraSPARC platform. 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

+ +

IDE/ATA controllers ( +ata(4) +driver)

+ +

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 2920

    +
    • + +
  • +

    Adaptec 2930C

    +
    • + +
  • +

    Adaptec 2930U2

    +
    • + +
  • +

    Adaptec 2940

    +
    • + +
  • +

    Adaptec 2940J

    +
    • + +
  • +

    Adaptec 2940N

    +
    • + +
  • +

    Adaptec 2940U

    +
    • + +
  • +

    Adaptec 2940AU

    +
    • + +
  • +

    Adaptec 2940UW

    +
    • + +
  • +

    Adaptec 2940UW Dual

    +
    • + +
  • +

    Adaptec 2940UW Pro

    +
    • + +
  • +

    Adaptec 2940U2W

    +
    • + +
  • +

    Adaptec 2940U2B

    +
    • + +
  • +

    Adaptec 2950U2W

    +
    • + +
  • +

    Adaptec 2950U2B

    +
    • + +
  • +

    Adaptec 19160B

    +
    • + +
  • +

    Adaptec 29160B

    +
    • + +
  • +

    Adaptec 29160N

    +
    • + +
  • +

    Adaptec 3940

    +
    • + +
  • +

    Adaptec 3940U

    +
    • + +
  • +

    Adaptec 3940AU

    +
    • + +
  • +

    Adaptec 3940UW

    +
    • + +
  • +

    Adaptec 3940AUW

    +
    • + +
  • +

    Adaptec 3940U2W

    +
    • + +
  • +

    Adaptec 3950U2

    +
    • + +
  • +

    Adaptec 3960

    +
    • + +
  • +

    Adaptec 39160

    +
    • + +
  • +

    Adaptec 3985

    +
    • + +
  • +

    Adaptec 4944UW

    +
    • + +
  • +

    NEC PC-9821Xt13 (PC-98)

    +
    • + +
  • +

    NEC RvII26 (PC-98)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

    Many motherboards with on-board SCSI support

    +
    • +
+ +

The +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

    +
    • +
+ +

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

    +
    • +
+ +

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

+ +

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

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    LSI Logic AS1064, LSI Logic AS1068

    +
    • + +
  • +

    LSI Logic FC909 (1Gb/s Fibre Channel)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

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

+ +
    +
  • +

    Dell PowerEdge 1750 thru 2850

    +
    • + +
  • +

    IBM eServer xSeries 335

    +
    • +
+ +

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

+ +

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)

    +
    • +
+ +

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

    +
    • +
+ +

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

    +
    • + +
  • +

    ATAPI IDE interface ( +acd(4))

    +
    • +
+ +
+
+
+ +
+
+

3.2 Ethernet Interfaces

+ +

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

+ +
    +
  • +

    DEC/Intel 21143

    +
    • + +
  • +

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

    +
    • + +
  • +

    ASIX Electronics AX88140A and AX88141

    +
    • + +
  • +

    Conexant LANfinity RS7112 (miniPCI)

    +
    • + +
  • +

    Davicom DM9009, DM9100, DM9102 and DM9102A

    +
    • + +
  • +

    Lite-On 82c168 and 82c169 PNIC

    +
    • + +
  • +

    Lite-On/Macronix 82c115 PNIC II

    +
    • + +
  • +

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

    +
    • + +
  • +

    Xircom X3201 (cardbus only)

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Abocom FE2500

    +
    • + +
  • +

    Accton EN1217 (98715A)

    +
    • + +
  • +

    Accton EN2242 MiniPCI

    +
    • + +
  • +

    Adico AE310TX (98715A)

    +
    • + +
  • +

    Alfa Inc GFC2204 (ASIX AX88140A)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Built in DE500-BA on DEC Alpha workstations (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

    +
    • +
+ +

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 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 +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

    +
    • +
+ +

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

+ +
    +
  • +

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

    +
    • + +
  • +

    Compaq Evo N1015v Integrated Ethernet (8139C+)

    +
    • + +
  • +

    Corega CG-LAPCIGT Gigabit Ethernet (8169S)

    +
    • + +
  • +

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

    +
    • + +
  • +

    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

    +
    • + +
  • +

    LevelOne GNC-0105T (8169S)

    +
    • + +
  • +

    LinkSys EG1032 (32-bit PCI)

    +
    • + +
  • +

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

    +
    • + +
  • +

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

    +
    • +
+ +

Adapters supported by the rl(4) driver +include:

+ +
    +
  • +

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

    +
    • + +
  • +

    Allied Telesyn AT2550

    +
    • + +
  • +

    Allied Telesyn AT2500TX

    +
    • + +
  • +

    Belkin F5D5000

    +
    • + +
  • +

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

    +
    • + +
  • +

    Compaq HNE-300

    +
    • + +
  • +

    CompUSA no-name 10/100 PCI Ethernet NIC

    +
    • + +
  • +

    Corega FEther CB-TXD

    +
    • + +
  • +

    Corega FEtherII CB-TXD

    +
    • + +
  • +

    D-Link DFE-528TX

    +
    • + +
  • +

    D-Link DFE-530TX+

    +
    • + +
  • +

    D-Link DFE-538TX

    +
    • + +
  • +

    D-Link DFE-690TXD

    +
    • + +
  • +

    Edimax EP-4103DL CardBus

    +
    • + +
  • +

    Encore ENL832-TX 10/100 M PCI

    +
    • + +
  • +

    Farallon NetLINE 10/100 PCI

    +
    • + +
  • +

    Genius GF100TXR

    +
    • + +
  • +

    GigaFast Ethernet EE100-AXP

    +
    • + +
  • +

    KTX-9130TX 10/100 Fast Ethernet

    +
    • + +
  • +

    LevelOne FPC-0106TX

    +
    • + +
  • +

    Longshine LCS-8038TX-R

    +
    • + +
  • +

    NDC Communications NE100TX-E

    +
    • + +
  • +

    Netronix Inc. EA-1210 NetEther 10/100

    +
    • + +
  • +

    Nortel Networks 10/100BaseTX

    +
    • + +
  • +

    OvisLink LEF-8129TX

    +
    • + +
  • +

    OvisLink LEF-8139TX

    +
    • + +
  • +

    Peppercon AG ROL-F

    +
    • + +
  • +

    Planex FNW-3603-TX

    +
    • + +
  • +

    Planex FNW-3800-TX

    +
    • + +
  • +

    SMC EZ Card 10/100 PCI 1211-TX

    +
    • + +
  • +

    SOHO (PRAGMATIC) UE-1211C

    +
    • +
+ +

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

    +
    • +
+ +

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

+
+ +
+
+

3.3 Token Ring Interfaces

+
+ +
+
+

3.4 FDDI Interfaces

+
+ +
+
+

3.5 ATM Interfaces

+ +

FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and +fatm(4) +drivers)

+ +

FORE Systems, Inc. HE155 and HE622 ATM interfaces ( +hatm(4) +driver)

+
+ +
+
+

3.6 Wireless Network Interfaces

+ +

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

+ +

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

+
+ +
+
+

3.7 Miscellaneous +Networks

+
+ +
+
+

3.8 ISDN Interfaces

+
+ +
+
+

3.9 Serial Interfaces

+ +

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

    +
    • + +
  • +

    SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.

    +
    • + +
  • +

    Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.

    +
    • +
+
+ +
+
+

3.10 Sound Devices

+ +

The +snd_audiocs(4) +driver supports the following audio devices:

+ +
    +
  • +

    CS4231 on SBus based UltraSPARC

    +
    • + +
  • +

    CS4231 on PCI/EBus based UltraSPARC

    +
    • +
+ +

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

    +
    • +
+
+ +
+
+

3.11 Camera and Video Capture +Devices

+
+ +
+
+

3.12 USB Devices

+ +

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

    +
    • +
+
+ +
+
+

3.13 IEEE 1394 (Firewire) +Devices

+ +

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 (CXD1947)

    +
    • + +
  • +

    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)

    +
    • +
+ +

Serial Bus Protocol 2 (SBP-2) storage devices ( +sbp(4) +driver)

+
+ +
+
+

3.14 Bluetooth Devices

+
+ +
+
+

3.15 Cryptographic +Accelerators

+
+ +
+
+

3.16 Miscellaneous

+ +

OpenFirmware console (ofwcons 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/en/releases/6.3R/hardware.sgml b/en/releases/6.3R/hardware.sgml new file mode 100644 index 0000000000..7ff69254ac --- /dev/null +++ b/en/releases/6.3R/hardware.sgml @@ -0,0 +1,32 @@ + + + + +]> + + &header; +

The hardware notes for FreeBSD are customized for different + platforms, as many devices are only supported on (or are + only relevant for) + specific processors or architectures.

+ +

Hardware notes for FreeBSD 6.3-RELEASE are available for the following + platforms:

+ + + +

A list of all platforms currently under development can be found + on the Supported + Platforms page.

+ + &footer; + + diff --git a/en/releases/6.3R/installation-alpha.html b/en/releases/6.3R/installation-alpha.html new file mode 100644 index 0000000000..b9dc61e2f1 --- /dev/null +++ b/en/releases/6.3R/installation-alpha.html @@ -0,0 +1,1195 @@ + + + + +FreeBSD/alpha 6.3-RELEASE Installation Instructions + + + + + +
+
+

FreeBSD/alpha 6.3-RELEASE Installation +Instructions

+ +

The FreeBSD Project

+ +

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

+ +
+
+ +
+
+

This article gives some brief instructions on installing FreeBSD/alpha 6.3-RELEASE, +with particular emphasis given to obtaining a FreeBSD distribution. Some notes on +troubleshooting and frequently-asked questions are also given.

+
+
+ +
+
+

1 Installing FreeBSD

+ +

This section documents the process of installing a new distribution of FreeBSD. These +instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE +distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.

+ +

If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

+ +
+
+

1.1 Getting +Started

+ +

Probably the most important pre-installation step that can be taken is that of reading +the various instruction documents provided with FreeBSD. A roadmap of documents +pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this +file; most of these documents, such as the release notes and the hardware compatibility +list, are also accessible in the Documentation menu of the installer.

+ +

Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

+ +

This collection of documents may seem daunting, but the time spent reading them will +likely be saved many times over. Being familiar with what resources are available can +also be helpful in the event of problems during installation.

+ +

The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You +should also read an updated copy of ERRATA.TXT before +installing, since this will alert you to any problems which have reported in the interim +for your particular release.

+ +
+
+

Important: While FreeBSD does its best to safeguard against accidental loss of +data, it's still more than possible to wipe +out your entire disk with this installation if you make a mistake. Please do +not proceed to the final FreeBSD installation menu unless you've adequately backed up any +important data first.

+
+
+
+ +
+
+

1.2 Hardware Requirements

+ +

FreeBSD for the Alpha/AXP supports the platforms described in HARDWARE.TXT.

+ +

You will need a dedicated disk for FreeBSD/alpha. It is not possible to share a disk +with another operating system at this time. This disk will need to be attached to a SCSI +controller which is supported by the SRM firmware or an IDE disk assuming the SRM in your +machine supports booting from IDE disks.

+ +

Your root filesystem MUST be the first partition (partition a) on the disk to be bootable.

+ +

You will need the SRM console firmware for your platform. In some cases, it is +possible to switch between AlphaBIOS (or ARC) firmware and SRM. In others it will be +necessary to download new firmware from the vendor's Web site.

+ +

If you are not familiar with configuring hardware for FreeBSD, you should be sure to +read the HARDWARE.TXT file; it contains important information +on what hardware is supported by FreeBSD.

+
+ +
+
+

1.3 Floppy Disk Image +Instructions

+ +

Depending on how you choose to install FreeBSD, you may need to create a set of floppy +disks (usually four) to begin the installation process. This section briefly describes +how to create these disks, either from a CDROM installation or from the Internet. Note +that in the common case of installing FreeBSD from CDROM, on a machine that supports +bootable CDROMs, the steps outlined in this section will not be needed and can be +skipped.

+ +

For most CDROM or network installations, all you need to copy onto actual floppies +from the floppies/ directory are the boot.flp and kernX.flp images (for 1.44MB floppies).

+ +

Getting these images over the network is easy. Simply fetch the release/floppies/boot.flp, and +all of the release/floppies/kernX.flp files from +ftp://ftp.FreeBSD.org/ or one of the +many mirrors listed at FTP Sites section of the Handbook, or on the http://mirrorlist.FreeBSD.org/ +Web pages.

+ +

Get several blank, freshly formatted floppies and image copy boot.flp onto one and the kernX.flp files onto the others. These images are not DOS files. You cannot simply copy +them to a DOS or UFS floppy as regular files, you need to “image” copy them +to the floppy with fdimage.exe under DOS (see the tools directory on your CDROM or FreeBSD FTP mirror) or the dd(1) command in +UNIX.

+ +

For example, to create the kernel floppy image from DOS, you'd do something like +this:

+ +
+C> fdimage boot.flp a:
+
+ +

Assuming that you'd copied fdimage.exe and boot.flp into a directory somewhere. You would do the same for the +kernX.flp files, of +course.

+ +

If you're creating the boot floppy from a UNIX machine, you may find that:

+ +
+# dd if=floppies/boot.flp of=/dev/rfd0
+
+ +

or

+ +
+# dd if=floppies/boot.flp of=/dev/fd0
+
+ +

or

+ +
+# dd if=floppies/boot.flp of=/dev/floppy
+
+ +

work well, depending on your hardware and operating system environment (different +versions of UNIX have different names for the floppy drive).

+
+ +
+
+

1.4 Installing +FreeBSD from CDROM or the Internet

+ +

The easiest type of installation is from CDROM. If you have a supported CDROM drive +and a FreeBSD installation CDROM, you can boot FreeBSD directly from the CDROM. Insert +the CDROM into the drive and type the following command to start the installation +(substituting the name of the appropriate CDROM drive if necessary):

+ +
+>>>boot dka0
+
+ +

Alternatively you can boot the installation from floppy disk. You should start the +installation by building a set of FreeBSD boot floppies from the floppies/boot.flp and floppies/kernX.flp files using the instructions found in Section 1.3. From the SRM console prompt (>>>), just insert the boot.flp +floppy and type the following command to start the installation:

+ +
+>>>boot dva0
+
+ +

Insert the other floppies when prompted and you will end up at the first screen of the +install program.

+
+ +
+
+

1.5 Detail on various installation +types

+ +

Once you've gotten yourself to the initial installation screen somehow, you should be +able to follow the various menu prompts and go from there. If you've never used the +FreeBSD installation before, you are also encouraged to read some of the documentation in +the Documentation submenu as well as the general “Usage” instructions on the +first menu.

+ +
+
+

Note: If you get stuck at a screen, press the F1 key for +online documentation relevant to that specific section.

+
+
+ +

If you've never installed FreeBSD before, or even if you have, the +“Standard” installation mode is the most recommended since it makes sure that +you'll visit all the various important checklist items along the way. If you're much more +comfortable with the FreeBSD installation process and know exactly what you want to do, use the “Express” or +“Custom” installation options. If you're upgrading an existing system, use +the “Upgrade” option.

+ +

The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS +and UFS partitions as installation media; further tips on installing from each type of +media are listed below.

+ +

Once the install procedure has finished, you will be able to start FreeBSD/alpha by +typing something like this to the SRM prompt:

+ +
+>>>boot dkc0
+
+ +

This instructs the firmware to boot the specified disk. To find the SRM names of disks +in your machine, use the show device command:

+ +
+>>>show device
+dka0.0.0.4.0               DKA0           TOSHIBA CD-ROM XM-57  3476
+dkc0.0.0.1009.0            DKC0                       RZ1BB-BS  0658
+dkc100.1.0.1009.0          DKC100             SEAGATE ST34501W  0015
+dva0.0.0.0.1               DVA0
+ewa0.0.0.3.0               EWA0              00-00-F8-75-6D-01
+pkc0.7.0.1009.0            PKC0                  SCSI Bus ID 7  5.27
+pqa0.0.0.4.0               PQA0                       PCI EIDE
+pqb0.0.1.4.0               PQB0                       PCI EIDE
+
+ +

This example is from a Digital Personal Workstation 433au and shows three disks +attached to the machine. The first is a CDROM called dka0 and +the other two are disks and are called dkc0 and dkc100 respectively.

+ +

You can specify which kernel file to load and what boot options to use with the -file and -flags options, for +example:

+ +
+>>> boot -file kernel.old -flags s
+
+ +

To make FreeBSD/alpha boot automatically, use these commands:

+ +
+>>> set boot_osflags a
+>>> set bootdef_dev dkc0
+>>> set auto_action BOOT
+
+ +
+
+

1.5.1 Installing from a Network +CDROM

+ +

If you simply wish to install from a local CDROM drive then see Section 1.4. If you don't have a CDROM drive on your +system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to +which you have network connectivity, there are also several ways of going about it:

+ +
    +
  • +

    If you would be able to FTP install FreeBSD directly from the CDROM drive in some +FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add +the following line to the password file (using the +vipw(8) +command):

    + +
    +ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
    + +

    On the machine on which you are running the install, go to the Options menu and set +Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp +sites menu.

    + +
    +
    +

    Warning: This may allow anyone on the local network (or Internet) to make +“anonymous FTP” connections to this machine, which may not be desirable.

    +
    +
    +
    • + +
  • +

    If you would rather use NFS to export the CDROM directly to the machine(s) you'll be +installing from, you need to first add an entry to the /etc/exports file (on the machine with the CDROM drive). The +example below allows the machine ziggy.foo.com to mount the CDROM +directly via NFS during installation:

    + +
    +/cdrom          -ro             ziggy.foo.com
+
    + +

    The machine with the CDROM must also be configured as an NFS server, of course, and if +you're not sure how to do that then an NFS installation is probably not the best choice +for you unless you're willing to read up on +rc.conf(5) and +configure things appropriately. Assuming that this part goes smoothly, you should be able +to enter: cdrom-host:/cdrom +as the path for an NFS installation when the target machine is installed, e.g. wiggy:/cdrom.

    +
    • +
+
+ +
+
+

1.5.2 Installing from Floppies

+ +

If you must install from floppy disks, either due to unsupported hardware or just +because you enjoy doing things the hard way, you must first prepare some floppies for the +install.

+ +

First, make your boot floppies as described in Section +1.3.

+ +

Second, peruse Section 2 and pay special attention to the +“Distribution Format” section since it describes which files you're going to +need to put onto floppy and which you can safely skip.

+ +

Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files +in the bin (binary distribution) directory. If you're preparing +these floppies under DOS, then these floppies must be formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File +Manager format command.

+ +
+
+

Important: Frequently, floppy disks come “factory preformatted”. +While convenient, many problems reported by users in the past have resulted from the use +of improperly formatted media. Re-format them yourself, just to make sure.

+
+
+ +

If you're creating the floppies from another FreeBSD machine, a format is still not a +bad idea though you don't need to put a DOS filesystem on each floppy. You can use the +disklabel(8) and + +newfs(8) +commands to put a UFS filesystem on a floppy, as the following sequence of commands +illustrates:

+ +
+# fdformat -f 1440 fd0
+# disklabel -w fd0 floppy3
+# newfs -i 65536 /dev/fd0
+
+ +

After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto +them. The distribution files are sized so that a floppy disk will hold a single file. +Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +
+
+

Important: The bin.inf file also needs to go on the +first floppy of the bin set since it is read by the +installation program in order to figure out how many additional pieces to look for when +fetching and concatenating the distribution. When putting distributions onto floppies, +the distname.inf file must occupy the first floppy of each distribution set.

+
+
+ +

Once you come to the Media screen of the install, select “Floppy” and +you'll be prompted for the rest.

+
+ +
+
+

1.5.4 Installing from QIC/SCSI +Tape

+ +

When installing from tape, the installation program expects the files to be simply +tar'ed onto it, so after fetching all of the files for the distributions you're +interested in, simply use +tar(1) to get +them onto the tape with a command something like this:

+ +
+# cd /where/you/have/your/dists
+# tar cvf /dev/sa0 dist1 .. dist2
+
+ +

When you go to do the installation, you should also make sure that you leave enough +room in some temporary directory (which you'll be allowed to choose) to accommodate the +full contents of the tape you've +created. Due to the non-random access nature of tapes, this method of installation +requires quite a bit of temporary storage. You should expect to require as much temporary +storage as you have stuff written on tape.

+ +
+
+

Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. +The installation “probe” may otherwise fail to find it.

+
+
+ +

Now create a boot floppy as described in Section 1.3 and +proceed with the installation.

+
+ +
+
+

1.5.5 Installing over a Network using FTP +or NFS

+ +

After making the boot floppies as described in the first section, you can load the +rest of the installation over a network using one of 3 types of connections: serial port, +parallel port, or Ethernet.

+ +
+
+
1.5.5.1 Serial Port
+ +

SLIP support is rather primitive, and is limited primarily to hard-wired links, such +as a serial cable running between two computers. The link must be hard-wired because the +SLIP installation doesn't currently offer a dialing capability. If you need to dial out +with a modem or otherwise dialog with the link before connecting to it, then the PPP +utility should be used instead.

+ +

If you're using PPP, make sure that you have your Internet Service Provider's IP +address and DNS information handy as you'll need to know it fairly early in the +installation process. You may also need to know your own IP address, though PPP supports +dynamic address negotiation and may be able to pick up this information directly from +your ISP if they support it.

+ +

You will also need to know how to use the various “AT commands” for +dialing out with your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator.

+
+ +
+
+
1.5.5.2 Parallel Port
+ +

If a hard-wired connection to another FreeBSD or Linux machine is available, you might +also consider installing over a “laplink” style parallel port cable. The data +rate over the parallel port is much higher than what is typically possible over a serial +line (up to 50k/sec), thus resulting in a quicker installation. It's not typically +necessary to use “real” IP addresses when using a point-to-point parallel +cable in this way and you can generally just use RFC 1918 style addresses for the ends of +the link (e.g. 10.0.0.1, 10.0.0.2, +etc).

+ +
+
+

Important: If you use a Linux machine rather than a FreeBSD machine as your +PLIP peer, you will also have to specify link0 in the TCP/IP +setup screen's “extra options for ifconfig” field in order to be compatible +with Linux's slightly different PLIP protocol.

+
+
+
+ +
+
+
1.5.5.3 Ethernet
+ +

FreeBSD supports most common Ethernet cards; a table of supported cards is provided as +part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the +Documentation menu on the boot floppy or the top level directory of the CDROM). If you +are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in +before the laptop is powered on. +FreeBSD does not, unfortunately, currently support “hot insertion” of PCMCIA +cards during installation.

+ +

You will also need to know your IP address on the network, the netmask value for your subnet and the name of your machine. Your +system administrator can tell you which values are appropriate to your particular network +setup. If you will be referring to other hosts by name rather than IP address, you'll +also need a name server and possibly the address of a gateway (if you're using PPP, it's +your provider's IP address) to use in talking to it. If you want to install by FTP via an +HTTP proxy (see below), you will also need the proxy's address.

+ +

If you do not know the answers to these questions then you should really probably talk +to your system administrator first +before trying this type of installation. Using a randomly chosen IP address or netmask on +a live network is almost guaranteed not to work, and will probably result in a lecture +from said system administrator.

+ +

Once you have a network connection of some sort working, the installation can continue +over NFS or FTP.

+
+ +
+
+
1.5.5.4 NFS installation tips
+ +

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution +files you want onto a server somewhere and then point the NFS media selection at it.

+ +

If this server supports only “privileged port” access (this is generally +the default for Sun and Linux workstations), you may need to set this option in the +Options menu before installation can proceed.

+ +

If you have a poor quality Ethernet card which suffers from very slow transfer rates, +you may also wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server must also support “subdir +mounts”, e.g. if your FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr +or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled by the +-alldirs option. Other NFS servers may have different +conventions. If you are getting Permission Denied messages from +the server then it's likely that you don't have this properly enabled.

+
+ +
+
+
1.5.5.5 FTP Installation tips
+ +

FTP installation may be done from any mirror site containing a reasonably up-to-date +version of FreeBSD. A full menu of reasonable choices for almost any location in the +world is provided in the FTP site menu during installation.

+ +

If you are installing from some other FTP site not listed in this menu, or you are +having troubles getting your name server configured properly, you can also specify your +own URL by selecting the “URL” choice in that menu. A URL can contain a +hostname or an IP address, so something like the following would work in the absence of a +name server:

+ +
+ftp://216.66.64.162/pub/FreeBSD/releases/alpha/4.2-RELEASE
+
+ +

There are three FTP installation modes you can use:

+ +
    +
  • +

    FTP: This method uses the standard “Active” mode for transfers, in which +the server initiates a connection to the client. This will not work through most +firewalls but will often work best with older FTP servers that do not support passive +mode. If your connection hangs with passive mode, try this one.

    +
    • + +
  • +

    FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening +connections to the client. This option is best for users to pass through firewalls that +do not allow incoming connections on random port addresses.

    +
    • + +
  • +

    FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy +for all FTP operations. The proxy will translate the requests and send them to the FTP +server. This allows the user to pass through firewalls that do not allow FTP at all, but +offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP +server.

    + +

    In the rare case that you have an FTP proxy that does not go through HTTP, you can +specify the URL as something like:

    + +
    +ftp://foo.bar.com:port/pub/FreeBSD
+
    + +

    In the URL above, port is the port number of the +proxy FTP server.

    +
    • +
+
+
+ +
+
+

1.5.6 Tips for Serial Console +Users

+ +

If you'd like to install FreeBSD on a machine using just a serial port (e.g. you don't +have or wish to use a VGA card), please follow these steps:

+ +
+
    +
  1. +

    Connect some sort of ANSI (vt100) compatible terminal or terminal emulation program to +the COM1 port of the PC you are installing FreeBSD onto.

    +
    2. + +
  2. +

    Unplug the keyboard (yes, that's correct!) and then try to boot from floppy or the +installation CDROM, depending on the type of installation media you have, with the +keyboard unplugged.

    +
    3. + +
  3. +

    If you don't get any output on your serial console, plug the keyboard in again. If you +are booting from the CDROM, proceed to step 5 as soon as you hear +the beep.

    +
    4. + +
  4. +

    If booting from floppies, when access to the disk stops, insert the first of the kernX.flp disks and press Enter. When access to this disk finishes, insert the next kernX.flp disk and press Enter, and repeat until all kernX.flp disks have been inserted. When disk activity +finishes, reinsert the boot.flp floppy disk and press Enter.

    +
    5. + +
  5. +

    Once a beep is heard, hit the number 6, then enter

    + +
    +boot -h
+
    + +

    and you should now definitely be seeing everything on the serial port. If that still +doesn't work, check your serial cabling as well as the settings on your terminal +emulation program or actual terminal device. It should be set for 9600 baud, 8 bits, no +parity.

    +
    6. +
+
+
+
+ +
+
+

1.6 Question and Answer Section for +Alpha/AXP Architecture Users

+ +
+
+
1.6.1. Can I boot from the ARC or Alpha BIOS Console?
+ +
1.6.2. Help! I have no space! Do I need to delete everything +first?
+ +
1.6.3. Can I mount my Compaq Tru64 or VMS extended +partitions?
+ +
1.6.4. What about support for Compaq Tru64 (OSF/1) +binaries?
+ +
1.6.5. What about support for Linux binaries?
+ +
1.6.6. What about support for NT Alpha binaries?
+
+ +
+
+

1.6.1. Can I boot from the ARC or Alpha BIOS +Console?

+
+ +
+

No. FreeBSD, like Compaq Tru64 and VMS, will only boot from the SRM +console.

+
+
+ +
+
+

1.6.2. Help! I have no space! Do I need to +delete everything first?

+
+ +
+

Unfortunately, yes.

+
+
+ +
+
+

1.6.3. Can I mount my Compaq Tru64 or VMS +extended partitions?

+
+ +
+

No, not at this time.

+
+
+ +
+
+

1.6.4. What about support for Compaq Tru64 +(OSF/1) binaries?

+
+ +
+

FreeBSD can run Tru64 applications very well using the emulators/osf1_base port/package.

+
+
+ +
+
+

1.6.5. What about support for Linux +binaries?

+
+ +
+

FreeBSD can run AlphaLinux binaries with the assistance of the emulators/linux_base port/package.

+
+
+ +
+
+

1.6.6. What about support for NT Alpha +binaries?

+
+ +
+

FreeBSD is not able to run NT applications natively, although it has the +ability to mount NT partitions.

+
+
+
+
+
+ +
+
+

2 Distribution Format

+ +

A typical FreeBSD distribution directory looks something like this (exact details may +vary depending on version, architecture, and other factors):

+ +
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    base            compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+
+ +

These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see Section 4 for how to use this).

+ +

The floppies directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.

+ +

If you're trying to do some other type of installation or are merely curious about how +a distribution is organized, what follows is a more thorough description of some of these +items in more detail:

+ +
    +
  1. +

    The *.TXT and *.HTM files contain +documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should +be read before starting an installation. The *.TXT files are +plain text, while the *.HTM files are HTML files that can be +read by almost any Web browser. Some distributions may contain documentation in other +formats as well, such as PDF or PostScript.

    +
    2. + +
  2. +

    docbook.css is a Cascading Style Sheet (CSS) file used by +some Web browsers for formatting the HTML documentation.

    +
    3. + +
  3. +

    The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the +primary distribution components of FreeBSD itself and are split into smaller files for +easy packing onto floppies (should that be necessary).

    +
    4. + +
  4. +

    The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories +contain distributions for compatibility with older releases and are distributed as single +gzip'd tar files - they can be installed during release time or later by running their +install.sh scripts.

    +
    5. + +
  5. +

    The floppies/ subdirectory contains the floppy installation +images; further information on using them can be found in Section +1.3.

    +
    6. + +
  6. +

    The packages and ports directories +contain the FreeBSD Packages and Ports Collections. Packages may be installed from the +packages directory by running the command:

    + +
    +# sysinstall configPackages
+
    + +

    Packages can also be installed by feeding individual filenames in packages/ to the +pkg_add(1) +command.

    + +

    The Ports Collection may be installed like any other distribution and requires about +190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or +locally from /usr/share/doc/handbook if you've installed the +doc distribution.

    +
    7. + +
  7. +

    Last of all, the tools directory contains various DOS tools +for discovering disk geometries, installing boot managers and the like. It is purely +optional and provided only for user convenience.

    +
    8. +
+ +

A typical distribution directory (for example, the info +distribution) looks like this internally:

+ +
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+
+ +

The CHECKSUM.MD5 file contains MD5 signatures for each file, +should data corruption be suspected, and is purely for reference. It is not used by the +actual installation and does not need to be copied with the rest of the distribution +files. The info.a* files are split, gzip'd tar files, the +contents of which can be viewed by doing:

+ +
+# cat info.a* | tar tvzf -
+
+ +

During installation, they are automatically concatenated and extracted by the +installation procedure.

+ +

The info.inf file is also necessary since it is read by the +installation program in order to figure out how many pieces to look for when fetching and +concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

+ +

The info.mtree file is another non-essential file which is +provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be +later used with the +mtree(8) program +to verify the installation permissions and checksums against any possible modifications +to the file. When used with the base distribution, this can be +an excellent way of detecting trojan horse attacks on your system.

+ +

Finally, the install.sh file is for use by those who want to +install the distribution after installation time. To install the info distribution from +CDROM after a system was installed, for example, you'd do:

+ +
+# cd /cdrom/info
+# sh install.sh
+
+
+ +
+
+

3 Upgrading FreeBSD

+ +

These instructions describe a procedure for doing a binary upgrade from an older +version of FreeBSD.

+ +
+
+

Warning: While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do +not accept the final confirmation request unless you have adequately backed up any +important data files.

+
+
+ +
+
+

Important: These notes assume that you are using the version of +sysinstall(8) +supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched +version of +sysinstall(8) is +almost guaranteed to cause problems and has been known to leave systems in an unusable +state. The most commonly made mistake in this regard is the use of an old copy of +sysinstall(8) +from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.

+
+
+ +
+
+

Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).

+ +

These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.3-STABLE snapshots.

+
+
+ +
+
+

3.1 Introduction

+ +

The upgrade procedure replaces distributions selected by the user with those +corresponding to the new FreeBSD release. It preserves standard system configuration +data, as well as user data, installed packages and other software.

+ +

Administrators contemplating an upgrade are encouraged to study this section in its +entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or +loss of data.

+ +
+
+

3.1.1 Upgrade Overview

+ +

Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.

+ +

System configuration is preserved by retaining and restoring the previous version of +the following files:

+ +

Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

+ +

The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.

+ +

During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.

+
+
+ +
+
+

3.2 Procedure

+ +

This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.

+ +
+
+

3.2.1 Backup

+ +

User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.

+
+ +
+
+

3.2.2 Mount Filesystems

+ +

The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” +for any filesystems, as this will cause data loss.

+
+ +
+
+

3.2.3 Select Distributions

+ +

When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.

+
+ +
+
+

3.2.4 After Installation

+ +

Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.

+
+
+ +
+
+

3.3 Upgrading from Source Code

+ +

Those interested in an upgrade method that allows more flexibility and sophistication +should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves +rebuilding all of FreeBSD from source code. It requires reliable network connectivity, +extra disk space, and time, but has advantages for networks and other more complex +installations. This is roughly the same procedure as is used for track the -STABLE or +-CURRENT development branches.

+ +

/usr/src/UPDATING contains important information on updating +a FreeBSD system from source code. It lists various issues resulting from changes in +FreeBSD that may affect an upgrade.

+
+
+ +
+
+

4 Troubleshooting

+ +
+

4.1 Repairing an Existing FreeBSD +Installation

+ +

FreeBSD features a “fixit” option in the top menu of the +sysinstall(8) +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.

+ +

Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main +sysinstall(8) +menu. Then select the “CDROM/DVD” option from the fixit menu.

+ +

Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the boot.flp and kernX.flp disks required for +installation, create the fixit.flp floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main +sysinstall(8) +menu. At that point, choose the “fixit” item from the main +sysinstall(8) +menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

+ +

The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.

+ +

In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM +version of fixit, these same programs can be found in /stand or +/mnt2/rescue (as well as the rest of the programs from the live +filesystem, which can be found under /mnt).

+
+ +
+
+

4.2 Common Installation Problems for +Alpha/AXP Architecture Users

+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/installation-amd64.html b/en/releases/6.3R/installation-amd64.html new file mode 100644 index 0000000000..2b4ed3359c --- /dev/null +++ b/en/releases/6.3R/installation-amd64.html @@ -0,0 +1,1403 @@ + + + + +FreeBSD/amd64 6.3-RELEASE Installation Instructions + + + + + +
+
+

FreeBSD/amd64 6.3-RELEASE Installation +Instructions

+ +

The FreeBSD Project

+ +

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

+ +
+
+ +
+
+

This article gives some brief instructions on installing FreeBSD/amd64 6.3-RELEASE, +with particular emphasis given to obtaining a FreeBSD distribution. Some notes on +troubleshooting and frequently-asked questions are also given.

+
+
+ +
+
+

1 Installing FreeBSD

+ +

This section documents the process of installing a new distribution of FreeBSD. These +instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE +distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.

+ +

If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

+ +
+
+

1.1 Getting +Started

+ +

Probably the most important pre-installation step that can be taken is that of reading +the various instruction documents provided with FreeBSD. A roadmap of documents +pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this +file; most of these documents, such as the release notes and the hardware compatibility +list, are also accessible in the Documentation menu of the installer.

+ +

Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

+ +

This collection of documents may seem daunting, but the time spent reading them will +likely be saved many times over. Being familiar with what resources are available can +also be helpful in the event of problems during installation.

+ +

The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You +should also read an updated copy of ERRATA.TXT before +installing, since this will alert you to any problems which have reported in the interim +for your particular release.

+ +
+
+

Important: While FreeBSD does its best to safeguard against accidental loss of +data, it's still more than possible to wipe +out your entire disk with this installation if you make a mistake. Please do +not proceed to the final FreeBSD installation menu unless you've adequately backed up any +important data first.

+
+
+
+ +
+
+

1.2 Hardware Requirements

+ +

FreeBSD for the AMD64 requires an Athlon64, Athlon64-FX, Opteron or better processor +to run.

+ +

If you have an machine based on an nVidia nForce3 Pro-150, you MUST use the BIOS setup +to disable the IO APIC. If you do not have an option to do this, you will likely have to +disable ACPI instead. There are bugs in the Pro-150 chipset that we have not found a +workaround for yet.

+ +

If you are not familiar with configuring hardware for FreeBSD, you should be sure to +read the HARDWARE.TXT file; it contains important information +on what hardware is supported by FreeBSD.

+
+ +
+
+

1.3 Floppy Disk Image +Instructions

+ +

Floppy disk based install is not supported on FreeBSD/amd64.

+
+ +
+
+

1.4 Installing +FreeBSD from CDROM or the Internet

+ +

The easiest type of installation is from CDROM. If you have a supported CDROM drive +and a FreeBSD installation CDROM, there are 2 ways of starting the installation from +it:

+ +
    +
  • +

    If your system supports the “CDBOOT” standard for bootable CDROM media and +you have booting from CD enabled, simply put the FreeBSD installation CD in your CDROM +drive and boot the system to begin installation.

    +
    • + +
  • +

    Build a set of FreeBSD boot floppies from the floppies/ +directory in every FreeBSD distribution. Read Section 1.3 for +more information on creating the bootable floppies under different operating systems. +Then you simply boot from the first floppy and you should soon be in the FreeBSD +installation.

    +
    • +
+ +
+
+
+ +
+
+

1.5 Detail on various installation +types

+ +

Once you've gotten yourself to the initial installation screen somehow, you should be +able to follow the various menu prompts and go from there. If you've never used the +FreeBSD installation before, you are also encouraged to read some of the documentation in +the Documentation submenu as well as the general “Usage” instructions on the +first menu.

+ +
+
+

Note: If you get stuck at a screen, press the F1 key for +online documentation relevant to that specific section.

+
+
+ +

If you've never installed FreeBSD before, or even if you have, the +“Standard” installation mode is the most recommended since it makes sure that +you'll visit all the various important checklist items along the way. If you're much more +comfortable with the FreeBSD installation process and know exactly what you want to do, use the “Express” or +“Custom” installation options. If you're upgrading an existing system, use +the “Upgrade” option.

+ +

The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS +and UFS partitions as installation media; further tips on installing from each type of +media are listed below.

+ +
+
+

1.5.1 Installing from a Network +CDROM

+ +

If you simply wish to install from a local CDROM drive then see Section 1.4. If you don't have a CDROM drive on your +system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to +which you have network connectivity, there are also several ways of going about it:

+ +
    +
  • +

    If you would be able to FTP install FreeBSD directly from the CDROM drive in some +FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add +the following line to the password file (using the +vipw(8) +command):

    + +
    +ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
    + +

    On the machine on which you are running the install, go to the Options menu and set +Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp +sites menu.

    + +
    +
    +

    Warning: This may allow anyone on the local network (or Internet) to make +“anonymous FTP” connections to this machine, which may not be desirable.

    +
    +
    +
    • + +
  • +

    If you would rather use NFS to export the CDROM directly to the machine(s) you'll be +installing from, you need to first add an entry to the /etc/exports file (on the machine with the CDROM drive). The +example below allows the machine ziggy.foo.com to mount the CDROM +directly via NFS during installation:

    + +
    +/cdrom          -ro             ziggy.foo.com
+
    + +

    The machine with the CDROM must also be configured as an NFS server, of course, and if +you're not sure how to do that then an NFS installation is probably not the best choice +for you unless you're willing to read up on +rc.conf(5) and +configure things appropriately. Assuming that this part goes smoothly, you should be able +to enter: cdrom-host:/cdrom +as the path for an NFS installation when the target machine is installed, e.g. wiggy:/cdrom.

    +
    • +
+
+ +
+
+

1.5.2 Installing from Floppies

+ +

If you must install from floppy disks, either due to unsupported hardware or just +because you enjoy doing things the hard way, you must first prepare some floppies for the +install.

+ +

First, make your boot floppies as described in Section +1.3.

+ +

Second, peruse Section 2 and pay special attention to the +“Distribution Format” section since it describes which files you're going to +need to put onto floppy and which you can safely skip.

+ +

Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files +in the bin (binary distribution) directory. If you're preparing +these floppies under DOS, then these floppies must be formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File +Manager format command.

+ +
+
+

Important: Frequently, floppy disks come “factory preformatted”. +While convenient, many problems reported by users in the past have resulted from the use +of improperly formatted media. Re-format them yourself, just to make sure.

+
+
+ +

If you're creating the floppies from another FreeBSD machine, a format is still not a +bad idea though you don't need to put a DOS filesystem on each floppy. You can use the +disklabel(8) and + +newfs(8) +commands to put a UFS filesystem on a floppy, as the following sequence of commands +illustrates:

+ +
+# fdformat -f 1440 fd0
+# disklabel -w fd0 floppy3
+# newfs -i 65536 /dev/fd0
+
+ +

After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto +them. The distribution files are sized so that a floppy disk will hold a single file. +Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +
+
+

Important: The bin.inf file also needs to go on the +first floppy of the bin set since it is read by the +installation program in order to figure out how many additional pieces to look for when +fetching and concatenating the distribution. When putting distributions onto floppies, +the distname.inf file must occupy the first floppy of each distribution set.

+
+
+ +

Once you come to the Media screen of the install, select “Floppy” and +you'll be prompted for the rest.

+
+ +
+
+

1.5.3 Installing from a DOS +partition

+ +

To prepare for installation from an MS-DOS partition you should simply copy the files +from the distribution into a directory called FREEBSD on the +Primary DOS partition (C:). For example, to do a minimal +installation of FreeBSD from DOS using files copied from the CDROM, you might do +something like this:

+ +
+C:\> MD C:\FREEBSD
+C:\> XCOPY /S E:\BASE C:\FREEBSD\BASE
+
+ +

Assuming that E: was where your CD was mounted.

+ +

For as many distributions as you wish to install from DOS (and you have free space +for), install each one in a directory under C:\FREEBSD - the +BIN dist is only the minimal requirement.

+ +

Once you've copied the directories, you can simply launch the installation from +floppies as normal and select “DOS” as your media type when the time +comes.

+
+ +
+
+

1.5.4 Installing from QIC/SCSI +Tape

+ +

When installing from tape, the installation program expects the files to be simply +tar'ed onto it, so after fetching all of the files for the distributions you're +interested in, simply use +tar(1) to get +them onto the tape with a command something like this:

+ +
+# cd /where/you/have/your/dists
+# tar cvf /dev/sa0 dist1 .. dist2
+
+ +

When you go to do the installation, you should also make sure that you leave enough +room in some temporary directory (which you'll be allowed to choose) to accommodate the +full contents of the tape you've +created. Due to the non-random access nature of tapes, this method of installation +requires quite a bit of temporary storage. You should expect to require as much temporary +storage as you have stuff written on tape.

+ +
+
+

Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. +The installation “probe” may otherwise fail to find it.

+
+
+ +

Now create a boot floppy as described in Section 1.3 and +proceed with the installation.

+
+ +
+
+

1.5.5 Installing over a Network using FTP +or NFS

+ +

After making the boot floppies as described in the first section, you can load the +rest of the installation over a network using one of 3 types of connections: serial port, +parallel port, or Ethernet.

+ +
+
+
1.5.5.1 Serial Port
+ +

SLIP support is rather primitive, and is limited primarily to hard-wired links, such +as a serial cable running between two computers. The link must be hard-wired because the +SLIP installation doesn't currently offer a dialing capability. If you need to dial out +with a modem or otherwise dialog with the link before connecting to it, then the PPP +utility should be used instead.

+ +

If you're using PPP, make sure that you have your Internet Service Provider's IP +address and DNS information handy as you'll need to know it fairly early in the +installation process. You may also need to know your own IP address, though PPP supports +dynamic address negotiation and may be able to pick up this information directly from +your ISP if they support it.

+ +

You will also need to know how to use the various “AT commands” for +dialing out with your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator.

+
+ +
+
+
1.5.5.2 Parallel Port
+ +

If a hard-wired connection to another FreeBSD or Linux machine is available, you might +also consider installing over a “laplink” style parallel port cable. The data +rate over the parallel port is much higher than what is typically possible over a serial +line (up to 50k/sec), thus resulting in a quicker installation. It's not typically +necessary to use “real” IP addresses when using a point-to-point parallel +cable in this way and you can generally just use RFC 1918 style addresses for the ends of +the link (e.g. 10.0.0.1, 10.0.0.2, +etc).

+ +
+
+

Important: If you use a Linux machine rather than a FreeBSD machine as your +PLIP peer, you will also have to specify link0 in the TCP/IP +setup screen's “extra options for ifconfig” field in order to be compatible +with Linux's slightly different PLIP protocol.

+
+
+
+ +
+
+
1.5.5.3 Ethernet
+ +

FreeBSD supports most common Ethernet cards; a table of supported cards is provided as +part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the +Documentation menu on the boot floppy or the top level directory of the CDROM). If you +are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in +before the laptop is powered on. +FreeBSD does not, unfortunately, currently support “hot insertion” of PCMCIA +cards during installation.

+ +

You will also need to know your IP address on the network, the netmask value for your subnet and the name of your machine. Your +system administrator can tell you which values are appropriate to your particular network +setup. If you will be referring to other hosts by name rather than IP address, you'll +also need a name server and possibly the address of a gateway (if you're using PPP, it's +your provider's IP address) to use in talking to it. If you want to install by FTP via an +HTTP proxy (see below), you will also need the proxy's address.

+ +

If you do not know the answers to these questions then you should really probably talk +to your system administrator first +before trying this type of installation. Using a randomly chosen IP address or netmask on +a live network is almost guaranteed not to work, and will probably result in a lecture +from said system administrator.

+ +

Once you have a network connection of some sort working, the installation can continue +over NFS or FTP.

+
+ +
+
+
1.5.5.4 NFS installation tips
+ +

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution +files you want onto a server somewhere and then point the NFS media selection at it.

+ +

If this server supports only “privileged port” access (this is generally +the default for Sun and Linux workstations), you may need to set this option in the +Options menu before installation can proceed.

+ +

If you have a poor quality Ethernet card which suffers from very slow transfer rates, +you may also wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server must also support “subdir +mounts”, e.g. if your FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr +or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled by the +-alldirs option. Other NFS servers may have different +conventions. If you are getting Permission Denied messages from +the server then it's likely that you don't have this properly enabled.

+
+ +
+
+
1.5.5.5 FTP Installation tips
+ +

FTP installation may be done from any mirror site containing a reasonably up-to-date +version of FreeBSD. A full menu of reasonable choices for almost any location in the +world is provided in the FTP site menu during installation.

+ +

If you are installing from some other FTP site not listed in this menu, or you are +having troubles getting your name server configured properly, you can also specify your +own URL by selecting the “URL” choice in that menu. A URL can contain a +hostname or an IP address, so something like the following would work in the absence of a +name server:

+ +
+ftp://216.66.64.162/pub/FreeBSD/releases/amd64/4.2-RELEASE
+
+ +

There are three FTP installation modes you can use:

+ +
    +
  • +

    FTP: This method uses the standard “Active” mode for transfers, in which +the server initiates a connection to the client. This will not work through most +firewalls but will often work best with older FTP servers that do not support passive +mode. If your connection hangs with passive mode, try this one.

    +
    • + +
  • +

    FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening +connections to the client. This option is best for users to pass through firewalls that +do not allow incoming connections on random port addresses.

    +
    • + +
  • +

    FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy +for all FTP operations. The proxy will translate the requests and send them to the FTP +server. This allows the user to pass through firewalls that do not allow FTP at all, but +offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP +server.

    + +

    In the rare case that you have an FTP proxy that does not go through HTTP, you can +specify the URL as something like:

    + +
    +ftp://foo.bar.com:port/pub/FreeBSD
+
    + +

    In the URL above, port is the port number of the +proxy FTP server.

    +
    • +
+
+
+ +
+
+

1.5.6 Tips for Serial Console +Users

+ +

If you'd like to install FreeBSD on a machine using just a serial port (e.g. you don't +have or wish to use a VGA card), please follow these steps:

+ +
+
    +
  1. +

    Connect some sort of ANSI (vt100) compatible terminal or terminal emulation program to +the COM1 port of the PC you are installing FreeBSD onto.

    +
    2. + +
  2. +

    Unplug the keyboard (yes, that's correct!) and then try to boot from floppy or the +installation CDROM, depending on the type of installation media you have, with the +keyboard unplugged.

    +
    3. + +
  3. +

    If you don't get any output on your serial console, plug the keyboard in again. If you +are booting from the CDROM, proceed to step 5 as soon as you hear +the beep.

    +
    4. + +
  4. +

    If booting from floppies, when access to the disk stops, insert the first of the kernX.flp disks and press Enter. When access to this disk finishes, insert the next kernX.flp disk and press Enter, and repeat until all kernX.flp disks have been inserted. When disk activity +finishes, reinsert the boot.flp floppy disk and press Enter.

    +
    5. + +
  5. +

    Once a beep is heard, hit the number 6, then enter

    + +
    +boot -h
+
    + +

    and you should now definitely be seeing everything on the serial port. If that still +doesn't work, check your serial cabling as well as the settings on your terminal +emulation program or actual terminal device. It should be set for 9600 baud, 8 bits, no +parity.

    +
    6. +
+
+
+
+ +
+
+

1.6 Question and Answer Section for AMD64 +Architecture Users

+ +
+
+
1.6.1. Help! I have no space! Do I need to delete everything +first?
+ +
1.6.2. Can I use compressed DOS filesystems from FreeBSD?
+ +
1.6.3. Can I mount my DOS extended partitions?
+ +
1.6.4. Can I run DOS binaries under FreeBSD?
+ +
1.6.5. Can I run Microsoft® Windows® +applications under FreeBSD?
+ +
1.6.6. Can I run other Operating Systems under FreeBSD?
+
+ +
+
+

1.6.1. Help! I have no space! Do I need to +delete everything first?

+
+ +
+

If your machine is already running DOS and has little or no free space +available for FreeBSD's installation, there are several alternatives for resizing +existing partitions so that you can install FreeBSD.

+ +

The FIPS utility, provided in the tools/ subdirectory on the FreeBSD CDROM or on the various FreeBSD +ftp sites, can resize an existing FAT partition. It allows you to split an existing DOS +partition into two pieces, preserving the original partition and allowing you to install +onto the second free piece. You first “defrag” your DOS partition, using the +DOS 6.xx DEFRAG utility or the Norton +Disk Tools, then run FIPS. It will prompt you for the rest of the information it +needs. Afterwards, you can reboot and install FreeBSD on the new partition. Also note +that FIPS will create the second partition as a “clone” of the first, so +you'll actually see that you now have two DOS Primary partitions where you formerly had +one. Don't be alarmed! You can simply delete the extra DOS Primary partition (making sure +it's the right one by examining its size).

+ +

For systems with NTFS partitions, a different tool, such as ntfsresize or the commercially-available Partition Magic, is required. ntfsresize, as well as the GParted +graphical interface for partition resizing, is available on a number of Live CD Linux +distributions, such as SystemRescueCD.

+ +

Problems have been reported resizing Microsoft Vista partitions. Having a Vista +installation CDROM handy when attempting such an operation is recommended. As with all +such disk maintenance tasks, a current set of backups is also strongly advised.

+
+
+ +
+
+

1.6.2. Can I use compressed DOS filesystems +from FreeBSD?

+
+ +
+

No. If you are using a utility such as Stacker(tm) +or DoubleSpace(tm), FreeBSD will only be able to use whatever +portion of the filesystem you leave uncompressed. The rest of the filesystem will show up +as one large file (the stacked/dblspaced file!). Do not remove that file as you will probably regret it +greatly!

+ +

It is probably better to create another uncompressed DOS extended partition and use +this for communications between DOS and FreeBSD if such is your desire.

+
+
+ +
+
+

1.6.3. Can I mount my DOS extended +partitions?

+
+ +
+

Yes. DOS extended partitions are mapped in at the end of the other +“slices” in FreeBSD, e.g. your D: drive might be +/dev/da0s5, your E: drive /dev/da0s6, and so on. This example assumes, of course, that your +extended partition is on SCSI drive 0. For IDE drives, substitute ad for da appropriately. You otherwise +mount extended partitions exactly like you would mount any other DOS drive, e.g.:

+ +
+# mount -t msdos /dev/da0s5 /dos_d
+
+
+
+ +
+
+

1.6.4. Can I run DOS binaries under +FreeBSD?

+
+ +
+

Ongoing work with BSDI's +doscmd(1) +utility will suffice in many cases, though it still has some rough edges. The emulators/doscmd port/package can be found in the FreeBSD Ports +Collection. If you're interested in working on this, please send mail to the FreeBSD-emulation mailing list and indicate that you're interested in +joining this ongoing effort!

+ +

The emulators/pcemu port/package in the FreeBSD Ports Collection +which emulates an 8088 and enough BIOS services to run DOS text mode applications. It +requires the X Window System (XFree86) to operate.

+
+
+ +
+
+

1.6.5. Can I run Microsoft® Windows® +applications under FreeBSD?

+
+ +
+

There are several ports/packages in the FreeBSD Ports Collection which can +enable the use of many Windows applications. The emulators/wine port/package provides a compatibility layer on +top of FreeBSD which allow many Windows applications to be +run within X Windows (XFree86).

+
+
+ +
+
+

1.6.6. Can I run other Operating Systems +under FreeBSD?

+
+ +
+

Again, there are several ports/packages in the FreeBSD Ports Collection which +simulate "virtual machines" and allow other operating systems to run on top of FreeBSD. +The emulators/bochs port/package allows Microsoft Windows, Linux and +even other copies of FreeBSD to be run within a window on the FreeBSD desktop. The emulators/vmware2 and emulators/vmware3 ports/packages allow the commercial VMware +virtual machine software to be run on FreeBSD.

+
+
+
+
+
+ +
+
+

2 Distribution Format

+ +

A typical FreeBSD distribution directory looks something like this (exact details may +vary depending on version, architecture, and other factors):

+ +
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    base            compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+
+ +

These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see Section 4 for how to use this).

+ +

The floppies directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.

+ +

If you're trying to do some other type of installation or are merely curious about how +a distribution is organized, what follows is a more thorough description of some of these +items in more detail:

+ +
    +
  1. +

    The *.TXT and *.HTM files contain +documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should +be read before starting an installation. The *.TXT files are +plain text, while the *.HTM files are HTML files that can be +read by almost any Web browser. Some distributions may contain documentation in other +formats as well, such as PDF or PostScript.

    +
    2. + +
  2. +

    docbook.css is a Cascading Style Sheet (CSS) file used by +some Web browsers for formatting the HTML documentation.

    +
    3. + +
  3. +

    The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the +primary distribution components of FreeBSD itself and are split into smaller files for +easy packing onto floppies (should that be necessary).

    +
    4. + +
  4. +

    The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories +contain distributions for compatibility with older releases and are distributed as single +gzip'd tar files - they can be installed during release time or later by running their +install.sh scripts.

    +
    5. + +
  5. +

    The floppies/ subdirectory contains the floppy installation +images; further information on using them can be found in Section +1.3.

    +
    6. + +
  6. +

    The packages and ports directories +contain the FreeBSD Packages and Ports Collections. Packages may be installed from the +packages directory by running the command:

    + +
    +# sysinstall configPackages
+
    + +

    Packages can also be installed by feeding individual filenames in packages/ to the +pkg_add(1) +command.

    + +

    The Ports Collection may be installed like any other distribution and requires about +190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or +locally from /usr/share/doc/handbook if you've installed the +doc distribution.

    +
    7. + +
  7. +

    Last of all, the tools directory contains various DOS tools +for discovering disk geometries, installing boot managers and the like. It is purely +optional and provided only for user convenience.

    +
    8. +
+ +

A typical distribution directory (for example, the info +distribution) looks like this internally:

+ +
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+
+ +

The CHECKSUM.MD5 file contains MD5 signatures for each file, +should data corruption be suspected, and is purely for reference. It is not used by the +actual installation and does not need to be copied with the rest of the distribution +files. The info.a* files are split, gzip'd tar files, the +contents of which can be viewed by doing:

+ +
+# cat info.a* | tar tvzf -
+
+ +

During installation, they are automatically concatenated and extracted by the +installation procedure.

+ +

The info.inf file is also necessary since it is read by the +installation program in order to figure out how many pieces to look for when fetching and +concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

+ +

The info.mtree file is another non-essential file which is +provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be +later used with the +mtree(8) program +to verify the installation permissions and checksums against any possible modifications +to the file. When used with the base distribution, this can be +an excellent way of detecting trojan horse attacks on your system.

+ +

Finally, the install.sh file is for use by those who want to +install the distribution after installation time. To install the info distribution from +CDROM after a system was installed, for example, you'd do:

+ +
+# cd /cdrom/info
+# sh install.sh
+
+
+ +
+
+

3 Upgrading FreeBSD

+ +

These instructions describe a procedure for doing a binary upgrade from an older +version of FreeBSD.

+ +
+
+

Warning: While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do +not accept the final confirmation request unless you have adequately backed up any +important data files.

+
+
+ +
+
+

Important: These notes assume that you are using the version of +sysinstall(8) +supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched +version of +sysinstall(8) is +almost guaranteed to cause problems and has been known to leave systems in an unusable +state. The most commonly made mistake in this regard is the use of an old copy of +sysinstall(8) +from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.

+
+
+ +
+
+

Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).

+ +

These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.3-STABLE snapshots.

+
+
+ +
+
+

3.1 Introduction

+ +

The upgrade procedure replaces distributions selected by the user with those +corresponding to the new FreeBSD release. It preserves standard system configuration +data, as well as user data, installed packages and other software.

+ +

Administrators contemplating an upgrade are encouraged to study this section in its +entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or +loss of data.

+ +
+
+

3.1.1 Upgrade Overview

+ +

Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.

+ +

System configuration is preserved by retaining and restoring the previous version of +the following files:

+ +

Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

+ +

The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.

+ +

During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.

+
+
+ +
+
+

3.2 Procedure

+ +

This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.

+ +
+
+

3.2.1 Backup

+ +

User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.

+
+ +
+
+

3.2.2 Mount Filesystems

+ +

The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” +for any filesystems, as this will cause data loss.

+
+ +
+
+

3.2.3 Select Distributions

+ +

When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.

+
+ +
+
+

3.2.4 After Installation

+ +

Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.

+
+
+ +
+
+

3.3 Upgrading from Source Code

+ +

Those interested in an upgrade method that allows more flexibility and sophistication +should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves +rebuilding all of FreeBSD from source code. It requires reliable network connectivity, +extra disk space, and time, but has advantages for networks and other more complex +installations. This is roughly the same procedure as is used for track the -STABLE or +-CURRENT development branches.

+ +

/usr/src/UPDATING contains important information on updating +a FreeBSD system from source code. It lists various issues resulting from changes in +FreeBSD that may affect an upgrade.

+
+
+ +
+
+

4 Troubleshooting

+ +
+

4.1 Repairing an Existing FreeBSD +Installation

+ +

FreeBSD features a “fixit” option in the top menu of the +sysinstall(8) +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.

+ +

Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main +sysinstall(8) +menu. Then select the “CDROM/DVD” option from the fixit menu.

+ +

Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the boot.flp and kernX.flp disks required for +installation, create the fixit.flp floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main +sysinstall(8) +menu. At that point, choose the “fixit” item from the main +sysinstall(8) +menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

+ +

The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.

+ +

In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM +version of fixit, these same programs can be found in /stand or +/mnt2/rescue (as well as the rest of the programs from the live +filesystem, which can be found under /mnt).

+
+ +
+
+

4.2 Common Installation Problems for AMD64 +Architecture Users

+ +
+
+
4.2.1. My system hangs while probing hardware during boot, or it +behaves strangely during install, or the floppy drive isn't probed.
+ +
4.2.2. My system uses the nVidia nForce3 Pro-150 chipset and I get +hangs at the end of boot or suddenly starts losing interrupts.
+ +
4.2.4. I go to boot from the hard disk for the first time after +installing FreeBSD, the kernel loads and probes my hardware, but stops with messages +like:
+ +
4.2.5. I go to boot from the hard disk for the first time after +installing FreeBSD, but the Boot Manager prompt just prints F? +at the boot menu each time but the boot won't go any further.
+ +
4.2.7. The system finds my ed(4) network card, but I keep getting device timeout +errors.
+ +
4.2.12. I have this CMD640 IDE controller that is said to be +broken.
+ +
4.2.15. I have an IBM EtherJet PCI card, it is detected by the +fxp(4) driver +correctly, but the lights on the card don't come on and it doesn't connect to the +network.
+ +
4.2.17. When I install onto a drive managed by a Mylex PCI RAID +controller, the system fails to boot (eg. with a read error +message).
+
+ +
+
+

4.2.1. My system hangs while probing +hardware during boot, or it behaves strangely during install, or the floppy drive isn't +probed.

+
+ +
+

FreeBSD 5.0 and above makes extensive use of the system ACPI service on the +i386, amd64 and ia64 platforms to aid in system configuration if it's detected during +boot. Unfortunately, some bugs still exist in both the ACPI driver and within system +motherboards and BIOS. The use of ACPI can be disabled by setting the +“hint.acpi.0.disabled” hint in the third stage boot loader:

+ +
+set hint.acpi.0.disabled="1"
+
+ +

This is reset each time the system is booted, so it is necessary to add hint.acpi.0.disabled="1" to the file /boot/loader.conf. More information about the boot loader can be +found in the FreeBSD Handbook.

+
+
+ +
+
+

4.2.2. My system uses the nVidia nForce3 +Pro-150 chipset and I get hangs at the end of boot or suddenly starts losing +interrupts.

+
+ +
+

There are problems with the apic on this chipset and/or the bios on every +machine that we had seen at the time of release. While disabling ACPI as above will work, +a less drastic option may be to set the “hint.apic.0.disabled” hint instead. +If you have the option in the bios, try disabling the APIC support. Unfortunately some +machines lack this option.

+
+
+ +
+
+

4.2.4. I go to boot from the hard disk for +the first time after installing FreeBSD, the kernel loads and probes my hardware, but +stops with messages like:

+ +
+changing root device to ad1s1a panic: cannot mount root
+
+ +

What is wrong? What can I do?

+ +

What is this bios_drive:interface(unit,partition)kernel_name +thing that is displayed with the boot help?

+
+ +
+

There is a longstanding problem in the case where the boot disk is not the +first disk in the system. The BIOS uses a different numbering scheme to FreeBSD, and +working out which numbers correspond to which is difficult to get right.

+ +

In the case where the boot disk is not the first disk in the system, FreeBSD can need +some help finding it. There are two common situations here, and in both of these cases, +you need to tell FreeBSD where the root filesystem is. You do this by specifying the BIOS +disk number, the disk type and the FreeBSD disk number for that type.

+ +

The first situation is where you have two IDE disks, each configured as the master on +their respective IDE busses, and wish to boot FreeBSD from the second disk. The BIOS sees +these as disk 0 and disk 1, while FreeBSD sees them as ad0 +and ad2.

+ +

FreeBSD is on BIOS disk 1, of type ad and the FreeBSD disk +number is 2, so you would say:

+ +
+1:ad(2,a)kernel
+
+ +

Note that if you have a slave on the primary bus, the above is not necessary (and is +effectively wrong).

+ +

The second situation involves booting from a SCSI disk when you have one or more IDE +disks in the system. In this case, the FreeBSD disk number is lower than the BIOS disk +number. If you have two IDE disks as well as the SCSI disk, the SCSI disk is BIOS disk 2, +type da and FreeBSD disk number 0, so you would say:

+ +
+2:da(0,a)kernel
+
+ +

To tell FreeBSD that you want to boot from BIOS disk 2, which is the first SCSI disk +in the system. If you only had one IDE disk, you would use '1:' instead.

+ +

Once you have determined the correct values to use, you can put the command exactly as +you would have typed it in the /boot.config file using a +standard text editor. Unless instructed otherwise, FreeBSD will use the contents of this +file as the default response to the boot: prompt.

+
+
+ +
+
+

4.2.5. I go to boot from the hard disk for +the first time after installing FreeBSD, but the Boot Manager prompt just prints F? at the boot menu each time but the boot won't go any further.

+
+ +
+

The hard disk geometry was set incorrectly in the Partition editor when you +installed FreeBSD. Go back into the partition editor and specify the actual geometry of +your hard disk. You must reinstall FreeBSD again from the beginning with the correct +geometry.

+ +

If you are failing entirely in figuring out the correct geometry for your machine, +here's a tip: Install a small DOS partition at the beginning of the disk and install +FreeBSD after that. The install program will see the DOS partition and try to infer the +correct geometry from it, which usually works.

+ +

The following tip is no longer recommended, but is left here for reference:

+ + +
+

If you are setting up a truly dedicated FreeBSD server or workstation where you don't +care for (future) compatibility with DOS, Linux or another operating system, you've also +got the option to use the entire disk (`A' in the partition editor), selecting the +non-standard option where FreeBSD occupies the entire disk from the very first to the +very last sector. This will leave all geometry considerations aside, but is somewhat +limiting unless you're never going to run anything other than FreeBSD on a disk.

+
+
+
+ +
+
+

4.2.7. The system finds my ed(4) network card, but I +keep getting device timeout errors.

+
+ +
+

Your card is probably on a different IRQ from what is specified in the /boot/device.hints file. The ed driver does not use the `soft' +configuration by default (values entered using EZSETUP in DOS), but it will use the +software configuration if you specify -1 in the hints for the +interface.

+ +

Either move the jumper on the card to a hard configuration setting (altering the +kernel settings if necessary), or specify the IRQ as -1 by +setting the hint “hint.ed.0.irq="-1"” This will tell the kernel to use the +soft configuration.

+ +

Another possibility is that your card is at IRQ 9, which is shared by IRQ 2 and +frequently a cause of problems (especially when you have a VGA card using IRQ 2!). You +should not use IRQ 2 or 9 if at all possible.

+
+
+ +
+
+

4.2.12. I have this CMD640 IDE controller +that is said to be broken.

+
+ +
+

FreeBSD does not support this controller.

+
+
+ +
+
+

4.2.15. I have an IBM EtherJet PCI card, +it is detected by the fxp(4) driver correctly, but the lights on the card +don't come on and it doesn't connect to the network.

+
+ +
+

We don't understand why this happens. Neither do IBM (we asked them). The card +is a standard Intel EtherExpress Pro/100 with an IBM label on it, and these cards +normally work just fine. You may see these symptoms only in some IBM Netfinity servers. +The only solution is to install a different Ethernet adapter.

+
+
+ +
+
+

4.2.17. When I install onto a drive +managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a read error message).

+
+ +
+

There is a bug in the Mylex driver which results in it ignoring the +“8GB” geometry mode setting in the BIOS. Use the 2GB mode instead.

+
+
+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/installation-i386.html b/en/releases/6.3R/installation-i386.html new file mode 100644 index 0000000000..14c1dba9f2 --- /dev/null +++ b/en/releases/6.3R/installation-i386.html @@ -0,0 +1,1626 @@ + + + + +FreeBSD/i386 6.3-RELEASE Installation Instructions + + + + + +
+
+

FreeBSD/i386 6.3-RELEASE Installation +Instructions

+ +

The FreeBSD Project

+ +

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

+ +
+
+ +
+
+

This article gives some brief instructions on installing FreeBSD/i386 6.3-RELEASE, +with particular emphasis given to obtaining a FreeBSD distribution. Some notes on +troubleshooting and frequently-asked questions are also given.

+
+
+ +
+
+

1 Installing FreeBSD

+ +

This section documents the process of installing a new distribution of FreeBSD. These +instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE +distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.

+ +

If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

+ +
+
+

1.1 Getting +Started

+ +

Probably the most important pre-installation step that can be taken is that of reading +the various instruction documents provided with FreeBSD. A roadmap of documents +pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this +file; most of these documents, such as the release notes and the hardware compatibility +list, are also accessible in the Documentation menu of the installer.

+ +

Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

+ +

This collection of documents may seem daunting, but the time spent reading them will +likely be saved many times over. Being familiar with what resources are available can +also be helpful in the event of problems during installation.

+ +

The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You +should also read an updated copy of ERRATA.TXT before +installing, since this will alert you to any problems which have reported in the interim +for your particular release.

+ +
+
+

Important: While FreeBSD does its best to safeguard against accidental loss of +data, it's still more than possible to wipe +out your entire disk with this installation if you make a mistake. Please do +not proceed to the final FreeBSD installation menu unless you've adequately backed up any +important data first.

+
+
+
+ +
+
+

1.2 Hardware Requirements

+ +

FreeBSD for the i386 requires a 486 or better processor and at least 24 MB of +RAM. You will need at least 150MB of free hard drive space for the most minimal +installation. See below for ways of shrinking existing DOS partitions in order to install +FreeBSD.

+ +

If you are not familiar with configuring hardware for FreeBSD, you should be sure to +read the HARDWARE.TXT file; it contains important information +on what hardware is supported by FreeBSD.

+
+ +
+
+

1.3 Floppy Disk Image +Instructions

+ +

Depending on how you choose to install FreeBSD, you may need to create a set of floppy +disks (usually four) to begin the installation process. This section briefly describes +how to create these disks, either from a CDROM installation or from the Internet. Note +that in the common case of installing FreeBSD from CDROM, on a machine that supports +bootable CDROMs, the steps outlined in this section will not be needed and can be +skipped.

+ +

For most CDROM or network installations, all you need to copy onto actual floppies +from the floppies/ directory are the boot.flp and kernX.flp images (for 1.44MB floppies).

+ +

Getting these images over the network is easy. Simply fetch the release/floppies/boot.flp, and +all of the release/floppies/kernX.flp files from +ftp://ftp.FreeBSD.org/ or one of the +many mirrors listed at FTP Sites section of the Handbook, or on the http://mirrorlist.FreeBSD.org/ +Web pages.

+ +

Get several blank, freshly formatted floppies and image copy boot.flp onto one and the kernX.flp files onto the others. These images are not DOS files. You cannot simply copy +them to a DOS or UFS floppy as regular files, you need to “image” copy them +to the floppy with fdimage.exe under DOS (see the tools directory on your CDROM or FreeBSD FTP mirror) or the dd(1) command in +UNIX.

+ +

For example, to create the kernel floppy image from DOS, you'd do something like +this:

+ +
+C> fdimage boot.flp a:
+
+ +

Assuming that you'd copied fdimage.exe and boot.flp into a directory somewhere. You would do the same for the +kernX.flp files, of +course.

+ +

If you're creating the boot floppy from a UNIX machine, you may find that:

+ +
+# dd if=floppies/boot.flp of=/dev/rfd0
+
+ +

or

+ +
+# dd if=floppies/boot.flp of=/dev/fd0
+
+ +

or

+ +
+# dd if=floppies/boot.flp of=/dev/floppy
+
+ +

work well, depending on your hardware and operating system environment (different +versions of UNIX have different names for the floppy drive).

+
+ +
+
+

1.4 Installing +FreeBSD from CDROM or the Internet

+ +

The easiest type of installation is from CDROM. If you have a supported CDROM drive +and a FreeBSD installation CDROM, there are 2 ways of starting the installation from +it:

+ +
    +
  • +

    If your system supports the “CDBOOT” standard for bootable CDROM media and +you have booting from CD enabled, simply put the FreeBSD installation CD in your CDROM +drive and boot the system to begin installation.

    +
    • + +
  • +

    Build a set of FreeBSD boot floppies from the floppies/ +directory in every FreeBSD distribution. Read Section 1.3 for +more information on creating the bootable floppies under different operating systems. +Then you simply boot from the first floppy and you should soon be in the FreeBSD +installation.

    +
    • +
+ +
+
+

If you don't have a CDROM (or your computer does not support booting from CDROM) and +would like to simply install over the net using PPP, SLIP or a dedicated connection, you +should start the installation by building a set of FreeBSD boot floppies from the files +floppies/boot.flp and floppies/kernX.flp using the instructions found in Section 1.3. Restart your computer using the boot.flp disk; when prompted, insert the other disks as required. +Then, please go to Section 1.5.5 for additional tips on installing +via FTP or NFS.

+
+ +
+
+

1.5 Detail on various installation +types

+ +

Once you've gotten yourself to the initial installation screen somehow, you should be +able to follow the various menu prompts and go from there. If you've never used the +FreeBSD installation before, you are also encouraged to read some of the documentation in +the Documentation submenu as well as the general “Usage” instructions on the +first menu.

+ +
+
+

Note: If you get stuck at a screen, press the F1 key for +online documentation relevant to that specific section.

+
+
+ +

If you've never installed FreeBSD before, or even if you have, the +“Standard” installation mode is the most recommended since it makes sure that +you'll visit all the various important checklist items along the way. If you're much more +comfortable with the FreeBSD installation process and know exactly what you want to do, use the “Express” or +“Custom” installation options. If you're upgrading an existing system, use +the “Upgrade” option.

+ +

The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS +and UFS partitions as installation media; further tips on installing from each type of +media are listed below.

+ +
+
+

1.5.1 Installing from a Network +CDROM

+ +

If you simply wish to install from a local CDROM drive then see Section 1.4. If you don't have a CDROM drive on your +system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to +which you have network connectivity, there are also several ways of going about it:

+ +
    +
  • +

    If you would be able to FTP install FreeBSD directly from the CDROM drive in some +FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add +the following line to the password file (using the +vipw(8) +command):

    + +
    +ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
    + +

    On the machine on which you are running the install, go to the Options menu and set +Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp +sites menu.

    + +
    +
    +

    Warning: This may allow anyone on the local network (or Internet) to make +“anonymous FTP” connections to this machine, which may not be desirable.

    +
    +
    +
    • + +
  • +

    If you would rather use NFS to export the CDROM directly to the machine(s) you'll be +installing from, you need to first add an entry to the /etc/exports file (on the machine with the CDROM drive). The +example below allows the machine ziggy.foo.com to mount the CDROM +directly via NFS during installation:

    + +
    +/cdrom          -ro             ziggy.foo.com
+
    + +

    The machine with the CDROM must also be configured as an NFS server, of course, and if +you're not sure how to do that then an NFS installation is probably not the best choice +for you unless you're willing to read up on +rc.conf(5) and +configure things appropriately. Assuming that this part goes smoothly, you should be able +to enter: cdrom-host:/cdrom +as the path for an NFS installation when the target machine is installed, e.g. wiggy:/cdrom.

    +
    • +
+
+ +
+
+

1.5.2 Installing from Floppies

+ +

If you must install from floppy disks, either due to unsupported hardware or just +because you enjoy doing things the hard way, you must first prepare some floppies for the +install.

+ +

First, make your boot floppies as described in Section +1.3.

+ +

Second, peruse Section 2 and pay special attention to the +“Distribution Format” section since it describes which files you're going to +need to put onto floppy and which you can safely skip.

+ +

Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files +in the bin (binary distribution) directory. If you're preparing +these floppies under DOS, then these floppies must be formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File +Manager format command.

+ +
+
+

Important: Frequently, floppy disks come “factory preformatted”. +While convenient, many problems reported by users in the past have resulted from the use +of improperly formatted media. Re-format them yourself, just to make sure.

+
+
+ +

If you're creating the floppies from another FreeBSD machine, a format is still not a +bad idea though you don't need to put a DOS filesystem on each floppy. You can use the +disklabel(8) and + +newfs(8) +commands to put a UFS filesystem on a floppy, as the following sequence of commands +illustrates:

+ +
+# fdformat -f 1440 fd0
+# disklabel -w fd0 floppy3
+# newfs -i 65536 /dev/fd0
+
+ +

After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto +them. The distribution files are sized so that a floppy disk will hold a single file. +Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +
+
+

Important: The bin.inf file also needs to go on the +first floppy of the bin set since it is read by the +installation program in order to figure out how many additional pieces to look for when +fetching and concatenating the distribution. When putting distributions onto floppies, +the distname.inf file must occupy the first floppy of each distribution set.

+
+
+ +

Once you come to the Media screen of the install, select “Floppy” and +you'll be prompted for the rest.

+
+ +
+
+

1.5.3 Installing from a DOS +partition

+ +

To prepare for installation from an MS-DOS partition you should simply copy the files +from the distribution into a directory called FREEBSD on the +Primary DOS partition (C:). For example, to do a minimal +installation of FreeBSD from DOS using files copied from the CDROM, you might do +something like this:

+ +
+C:\> MD C:\FREEBSD
+C:\> XCOPY /S E:\BASE C:\FREEBSD\BASE
+
+ +

Assuming that E: was where your CD was mounted.

+ +

For as many distributions as you wish to install from DOS (and you have free space +for), install each one in a directory under C:\FREEBSD - the +BIN dist is only the minimal requirement.

+ +

Once you've copied the directories, you can simply launch the installation from +floppies as normal and select “DOS” as your media type when the time +comes.

+
+ +
+
+

1.5.4 Installing from QIC/SCSI +Tape

+ +

When installing from tape, the installation program expects the files to be simply +tar'ed onto it, so after fetching all of the files for the distributions you're +interested in, simply use +tar(1) to get +them onto the tape with a command something like this:

+ +
+# cd /where/you/have/your/dists
+# tar cvf /dev/sa0 dist1 .. dist2
+
+ +

When you go to do the installation, you should also make sure that you leave enough +room in some temporary directory (which you'll be allowed to choose) to accommodate the +full contents of the tape you've +created. Due to the non-random access nature of tapes, this method of installation +requires quite a bit of temporary storage. You should expect to require as much temporary +storage as you have stuff written on tape.

+ +
+
+

Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. +The installation “probe” may otherwise fail to find it.

+
+
+ +

Now create a boot floppy as described in Section 1.3 and +proceed with the installation.

+
+ +
+
+

1.5.5 Installing over a Network using FTP +or NFS

+ +

After making the boot floppies as described in the first section, you can load the +rest of the installation over a network using one of 3 types of connections: serial port, +parallel port, or Ethernet.

+ +
+
+
1.5.5.1 Serial Port
+ +

SLIP support is rather primitive, and is limited primarily to hard-wired links, such +as a serial cable running between two computers. The link must be hard-wired because the +SLIP installation doesn't currently offer a dialing capability. If you need to dial out +with a modem or otherwise dialog with the link before connecting to it, then the PPP +utility should be used instead.

+ +

If you're using PPP, make sure that you have your Internet Service Provider's IP +address and DNS information handy as you'll need to know it fairly early in the +installation process. You may also need to know your own IP address, though PPP supports +dynamic address negotiation and may be able to pick up this information directly from +your ISP if they support it.

+ +

You will also need to know how to use the various “AT commands” for +dialing out with your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator.

+
+ +
+
+
1.5.5.2 Parallel Port
+ +

If a hard-wired connection to another FreeBSD or Linux machine is available, you might +also consider installing over a “laplink” style parallel port cable. The data +rate over the parallel port is much higher than what is typically possible over a serial +line (up to 50k/sec), thus resulting in a quicker installation. It's not typically +necessary to use “real” IP addresses when using a point-to-point parallel +cable in this way and you can generally just use RFC 1918 style addresses for the ends of +the link (e.g. 10.0.0.1, 10.0.0.2, +etc).

+ +
+
+

Important: If you use a Linux machine rather than a FreeBSD machine as your +PLIP peer, you will also have to specify link0 in the TCP/IP +setup screen's “extra options for ifconfig” field in order to be compatible +with Linux's slightly different PLIP protocol.

+
+
+
+ +
+
+
1.5.5.3 Ethernet
+ +

FreeBSD supports most common Ethernet cards; a table of supported cards is provided as +part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the +Documentation menu on the boot floppy or the top level directory of the CDROM). If you +are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in +before the laptop is powered on. +FreeBSD does not, unfortunately, currently support “hot insertion” of PCMCIA +cards during installation.

+ +

You will also need to know your IP address on the network, the netmask value for your subnet and the name of your machine. Your +system administrator can tell you which values are appropriate to your particular network +setup. If you will be referring to other hosts by name rather than IP address, you'll +also need a name server and possibly the address of a gateway (if you're using PPP, it's +your provider's IP address) to use in talking to it. If you want to install by FTP via an +HTTP proxy (see below), you will also need the proxy's address.

+ +

If you do not know the answers to these questions then you should really probably talk +to your system administrator first +before trying this type of installation. Using a randomly chosen IP address or netmask on +a live network is almost guaranteed not to work, and will probably result in a lecture +from said system administrator.

+ +

Once you have a network connection of some sort working, the installation can continue +over NFS or FTP.

+
+ +
+
+
1.5.5.4 NFS installation tips
+ +

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution +files you want onto a server somewhere and then point the NFS media selection at it.

+ +

If this server supports only “privileged port” access (this is generally +the default for Sun and Linux workstations), you may need to set this option in the +Options menu before installation can proceed.

+ +

If you have a poor quality Ethernet card which suffers from very slow transfer rates, +you may also wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server must also support “subdir +mounts”, e.g. if your FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr +or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled by the +-alldirs option. Other NFS servers may have different +conventions. If you are getting Permission Denied messages from +the server then it's likely that you don't have this properly enabled.

+
+ +
+
+
1.5.5.5 FTP Installation tips
+ +

FTP installation may be done from any mirror site containing a reasonably up-to-date +version of FreeBSD. A full menu of reasonable choices for almost any location in the +world is provided in the FTP site menu during installation.

+ +

If you are installing from some other FTP site not listed in this menu, or you are +having troubles getting your name server configured properly, you can also specify your +own URL by selecting the “URL” choice in that menu. A URL can contain a +hostname or an IP address, so something like the following would work in the absence of a +name server:

+ +
+ftp://216.66.64.162/pub/FreeBSD/releases/i386/4.2-RELEASE
+
+ +

There are three FTP installation modes you can use:

+ +
    +
  • +

    FTP: This method uses the standard “Active” mode for transfers, in which +the server initiates a connection to the client. This will not work through most +firewalls but will often work best with older FTP servers that do not support passive +mode. If your connection hangs with passive mode, try this one.

    +
    • + +
  • +

    FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening +connections to the client. This option is best for users to pass through firewalls that +do not allow incoming connections on random port addresses.

    +
    • + +
  • +

    FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy +for all FTP operations. The proxy will translate the requests and send them to the FTP +server. This allows the user to pass through firewalls that do not allow FTP at all, but +offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP +server.

    + +

    In the rare case that you have an FTP proxy that does not go through HTTP, you can +specify the URL as something like:

    + +
    +ftp://foo.bar.com:port/pub/FreeBSD
+
    + +

    In the URL above, port is the port number of the +proxy FTP server.

    +
    • +
+
+
+ +
+
+

1.5.6 Tips for Serial Console +Users

+ +

If you'd like to install FreeBSD on a machine using just a serial port (e.g. you don't +have or wish to use a VGA card), please follow these steps:

+ +
+
    +
  1. +

    Connect some sort of ANSI (vt100) compatible terminal or terminal emulation program to +the COM1 port of the PC you are installing FreeBSD onto.

    +
    2. + +
  2. +

    Unplug the keyboard (yes, that's correct!) and then try to boot from floppy or the +installation CDROM, depending on the type of installation media you have, with the +keyboard unplugged.

    +
    3. + +
  3. +

    If you don't get any output on your serial console, plug the keyboard in again. If you +are booting from the CDROM, proceed to step 5 as soon as you hear +the beep.

    +
    4. + +
  4. +

    If booting from floppies, when access to the disk stops, insert the first of the kernX.flp disks and press Enter. When access to this disk finishes, insert the next kernX.flp disk and press Enter, and repeat until all kernX.flp disks have been inserted. When disk activity +finishes, reinsert the boot.flp floppy disk and press Enter.

    +
    5. + +
  5. +

    Once a beep is heard, hit the number 6, then enter

    + +
    +boot -h
+
    + +

    and you should now definitely be seeing everything on the serial port. If that still +doesn't work, check your serial cabling as well as the settings on your terminal +emulation program or actual terminal device. It should be set for 9600 baud, 8 bits, no +parity.

    +
    6. +
+
+
+
+ +
+
+

1.6 Question and Answer Section for i386 +Architecture Users

+ +
+
+
1.6.1. Help! I have no space! Do I need to delete everything +first?
+ +
1.6.2. Can I use compressed DOS filesystems from FreeBSD?
+ +
1.6.3. Can I mount my DOS extended partitions?
+ +
1.6.4. Can I run DOS binaries under FreeBSD?
+ +
1.6.5. Can I run Microsoft® Windows® +applications under FreeBSD?
+ +
1.6.6. Can I run other Operating Systems under FreeBSD?
+
+ +
+
+

1.6.1. Help! I have no space! Do I need to +delete everything first?

+
+ +
+

If your machine is already running DOS and has little or no free space +available for FreeBSD's installation, there are several alternatives for resizing +existing partitions so that you can install FreeBSD.

+ +

The FIPS utility, provided in the tools/ subdirectory on the FreeBSD CDROM or on the various FreeBSD +ftp sites, can resize an existing FAT partition. It allows you to split an existing DOS +partition into two pieces, preserving the original partition and allowing you to install +onto the second free piece. You first “defrag” your DOS partition, using the +DOS 6.xx DEFRAG utility or the Norton +Disk Tools, then run FIPS. It will prompt you for the rest of the information it +needs. Afterwards, you can reboot and install FreeBSD on the new partition. Also note +that FIPS will create the second partition as a “clone” of the first, so +you'll actually see that you now have two DOS Primary partitions where you formerly had +one. Don't be alarmed! You can simply delete the extra DOS Primary partition (making sure +it's the right one by examining its size).

+ +

For systems with NTFS partitions, a different tool, such as ntfsresize or the commercially-available Partition Magic, is required. ntfsresize, as well as the GParted +graphical interface for partition resizing, is available on a number of Live CD Linux +distributions, such as SystemRescueCD.

+ +

Problems have been reported resizing Microsoft Vista partitions. Having a Vista +installation CDROM handy when attempting such an operation is recommended. As with all +such disk maintenance tasks, a current set of backups is also strongly advised.

+
+
+ +
+
+

1.6.2. Can I use compressed DOS filesystems +from FreeBSD?

+
+ +
+

No. If you are using a utility such as Stacker(tm) +or DoubleSpace(tm), FreeBSD will only be able to use whatever +portion of the filesystem you leave uncompressed. The rest of the filesystem will show up +as one large file (the stacked/dblspaced file!). Do not remove that file as you will probably regret it +greatly!

+ +

It is probably better to create another uncompressed DOS extended partition and use +this for communications between DOS and FreeBSD if such is your desire.

+
+
+ +
+
+

1.6.3. Can I mount my DOS extended +partitions?

+
+ +
+

Yes. DOS extended partitions are mapped in at the end of the other +“slices” in FreeBSD, e.g. your D: drive might be +/dev/da0s5, your E: drive /dev/da0s6, and so on. This example assumes, of course, that your +extended partition is on SCSI drive 0. For IDE drives, substitute ad for da appropriately. You otherwise +mount extended partitions exactly like you would mount any other DOS drive, e.g.:

+ +
+# mount -t msdos /dev/da0s5 /dos_d
+
+
+
+ +
+
+

1.6.4. Can I run DOS binaries under +FreeBSD?

+
+ +
+

Ongoing work with BSDI's +doscmd(1) +utility will suffice in many cases, though it still has some rough edges. The emulators/doscmd port/package can be found in the FreeBSD Ports +Collection. If you're interested in working on this, please send mail to the FreeBSD-emulation mailing list and indicate that you're interested in +joining this ongoing effort!

+ +

The emulators/pcemu port/package in the FreeBSD Ports Collection +which emulates an 8088 and enough BIOS services to run DOS text mode applications. It +requires the X Window System (XFree86) to operate.

+
+
+ +
+
+

1.6.5. Can I run Microsoft® Windows® +applications under FreeBSD?

+
+ +
+

There are several ports/packages in the FreeBSD Ports Collection which can +enable the use of many Windows applications. The emulators/wine port/package provides a compatibility layer on +top of FreeBSD which allow many Windows applications to be +run within X Windows (XFree86).

+
+
+ +
+
+

1.6.6. Can I run other Operating Systems +under FreeBSD?

+
+ +
+

Again, there are several ports/packages in the FreeBSD Ports Collection which +simulate "virtual machines" and allow other operating systems to run on top of FreeBSD. +The emulators/bochs port/package allows Microsoft Windows, Linux and +even other copies of FreeBSD to be run within a window on the FreeBSD desktop. The emulators/vmware2 and emulators/vmware3 ports/packages allow the commercial VMware +virtual machine software to be run on FreeBSD.

+
+
+
+
+
+ +
+
+

2 Distribution Format

+ +

A typical FreeBSD distribution directory looks something like this (exact details may +vary depending on version, architecture, and other factors):

+ +
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    base            compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+
+ +

These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see Section 4 for how to use this).

+ +

The floppies directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.

+ +

If you're trying to do some other type of installation or are merely curious about how +a distribution is organized, what follows is a more thorough description of some of these +items in more detail:

+ +
    +
  1. +

    The *.TXT and *.HTM files contain +documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should +be read before starting an installation. The *.TXT files are +plain text, while the *.HTM files are HTML files that can be +read by almost any Web browser. Some distributions may contain documentation in other +formats as well, such as PDF or PostScript.

    +
    2. + +
  2. +

    docbook.css is a Cascading Style Sheet (CSS) file used by +some Web browsers for formatting the HTML documentation.

    +
    3. + +
  3. +

    The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the +primary distribution components of FreeBSD itself and are split into smaller files for +easy packing onto floppies (should that be necessary).

    +
    4. + +
  4. +

    The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories +contain distributions for compatibility with older releases and are distributed as single +gzip'd tar files - they can be installed during release time or later by running their +install.sh scripts.

    +
    5. + +
  5. +

    The floppies/ subdirectory contains the floppy installation +images; further information on using them can be found in Section +1.3.

    +
    6. + +
  6. +

    The packages and ports directories +contain the FreeBSD Packages and Ports Collections. Packages may be installed from the +packages directory by running the command:

    + +
    +# sysinstall configPackages
+
    + +

    Packages can also be installed by feeding individual filenames in packages/ to the +pkg_add(1) +command.

    + +

    The Ports Collection may be installed like any other distribution and requires about +190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or +locally from /usr/share/doc/handbook if you've installed the +doc distribution.

    +
    7. + +
  7. +

    Last of all, the tools directory contains various DOS tools +for discovering disk geometries, installing boot managers and the like. It is purely +optional and provided only for user convenience.

    +
    8. +
+ +

A typical distribution directory (for example, the info +distribution) looks like this internally:

+ +
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+
+ +

The CHECKSUM.MD5 file contains MD5 signatures for each file, +should data corruption be suspected, and is purely for reference. It is not used by the +actual installation and does not need to be copied with the rest of the distribution +files. The info.a* files are split, gzip'd tar files, the +contents of which can be viewed by doing:

+ +
+# cat info.a* | tar tvzf -
+
+ +

During installation, they are automatically concatenated and extracted by the +installation procedure.

+ +

The info.inf file is also necessary since it is read by the +installation program in order to figure out how many pieces to look for when fetching and +concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

+ +

The info.mtree file is another non-essential file which is +provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be +later used with the +mtree(8) program +to verify the installation permissions and checksums against any possible modifications +to the file. When used with the base distribution, this can be +an excellent way of detecting trojan horse attacks on your system.

+ +

Finally, the install.sh file is for use by those who want to +install the distribution after installation time. To install the info distribution from +CDROM after a system was installed, for example, you'd do:

+ +
+# cd /cdrom/info
+# sh install.sh
+
+
+ +
+
+

3 Upgrading FreeBSD

+ +

These instructions describe a procedure for doing a binary upgrade from an older +version of FreeBSD.

+ +
+
+

Warning: While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do +not accept the final confirmation request unless you have adequately backed up any +important data files.

+
+
+ +
+
+

Important: These notes assume that you are using the version of +sysinstall(8) +supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched +version of +sysinstall(8) is +almost guaranteed to cause problems and has been known to leave systems in an unusable +state. The most commonly made mistake in this regard is the use of an old copy of +sysinstall(8) +from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.

+
+
+ +
+
+

Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).

+ +

These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.3-STABLE snapshots.

+
+
+ +
+
+

3.1 Introduction

+ +

The upgrade procedure replaces distributions selected by the user with those +corresponding to the new FreeBSD release. It preserves standard system configuration +data, as well as user data, installed packages and other software.

+ +

Administrators contemplating an upgrade are encouraged to study this section in its +entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or +loss of data.

+ +
+
+

3.1.1 Upgrade Overview

+ +

Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.

+ +

System configuration is preserved by retaining and restoring the previous version of +the following files:

+ +

Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

+ +

The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.

+ +

During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.

+
+
+ +
+
+

3.2 Procedure

+ +

This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.

+ +
+
+

3.2.1 Backup

+ +

User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.

+
+ +
+
+

3.2.2 Mount Filesystems

+ +

The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” +for any filesystems, as this will cause data loss.

+
+ +
+
+

3.2.3 Select Distributions

+ +

When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.

+
+ +
+
+

3.2.4 After Installation

+ +

Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.

+
+
+ +
+
+

3.3 Upgrading from Source Code

+ +

Those interested in an upgrade method that allows more flexibility and sophistication +should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves +rebuilding all of FreeBSD from source code. It requires reliable network connectivity, +extra disk space, and time, but has advantages for networks and other more complex +installations. This is roughly the same procedure as is used for track the -STABLE or +-CURRENT development branches.

+ +

/usr/src/UPDATING contains important information on updating +a FreeBSD system from source code. It lists various issues resulting from changes in +FreeBSD that may affect an upgrade.

+
+
+ +
+
+

4 Troubleshooting

+ +
+

4.1 Repairing an Existing FreeBSD +Installation

+ +

FreeBSD features a “fixit” option in the top menu of the +sysinstall(8) +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.

+ +

Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main +sysinstall(8) +menu. Then select the “CDROM/DVD” option from the fixit menu.

+ +

Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the boot.flp and kernX.flp disks required for +installation, create the fixit.flp floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main +sysinstall(8) +menu. At that point, choose the “fixit” item from the main +sysinstall(8) +menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

+ +

The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.

+ +

In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM +version of fixit, these same programs can be found in /stand or +/mnt2/rescue (as well as the rest of the programs from the live +filesystem, which can be found under /mnt).

+
+ +
+
+

4.2 Common Installation Problems for i386 +Architecture Users

+ +
+
+
4.2.1. My system hangs while probing hardware during boot, or it +behaves strangely during install, or the floppy drive isn't probed.
+ +
4.2.3. My legacy ISA device used to be recognized in previous +versions of FreeBSD, but now it's not. What happened?
+ +
4.2.4. I go to boot from the hard disk for the first time after +installing FreeBSD, the kernel loads and probes my hardware, but stops with messages +like:
+ +
4.2.5. I go to boot from the hard disk for the first time after +installing FreeBSD, but the Boot Manager prompt just prints F? +at the boot menu each time but the boot won't go any further.
+ +
4.2.6. The mcd(4) driver keeps thinking that it has found a +device and this stops my Intel EtherExpress card from working.
+ +
4.2.7. The system finds my ed(4) network card, but I keep getting device timeout +errors.
+ +
4.2.8. I booted the install floppy on my IBM ThinkPad (tm) laptop, +and the keyboard is all messed up.
+ +
4.2.9. My system can not find my Intel EtherExpress 16 +card.
+ +
4.2.10. When installing on an EISA HP Netserver, my on-board +AIC-7xxx SCSI controller isn't detected.
+ +
4.2.11. I have a Panasonic AL-N1 or Rios Chandler Pentium machine +and I find that the system hangs before ever getting into the installation now.
+ +
4.2.12. I have this CMD640 IDE controller that is said to be +broken.
+ +
4.2.13. On a Compaq Aero notebook, I get the message “No +floppy devices found! Please check ...” when trying to install from +floppy.
+ +
4.2.14. When installing on a Dell Poweredge XE, Dell proprietary +RAID controller DSA (Dell SCSI Array) isn't recognized.
+ +
4.2.15. I have an IBM EtherJet PCI card, it is detected by the +fxp(4) driver +correctly, but the lights on the card don't come on and it doesn't connect to the +network.
+ +
4.2.16. When I configure the network during installation on an +IBM Netfinity 3500, the system freezes.
+ +
4.2.17. When I install onto a drive managed by a Mylex PCI RAID +controller, the system fails to boot (eg. with a read error +message).
+
+ +
+
+

4.2.1. My system hangs while probing +hardware during boot, or it behaves strangely during install, or the floppy drive isn't +probed.

+
+ +
+

FreeBSD 5.0 and above makes extensive use of the system ACPI service on the +i386, amd64 and ia64 platforms to aid in system configuration if it's detected during +boot. Unfortunately, some bugs still exist in both the ACPI driver and within system +motherboards and BIOS. The use of ACPI can be disabled by setting the +“hint.acpi.0.disabled” hint in the third stage boot loader:

+ +
+set hint.acpi.0.disabled="1"
+
+ +

This is reset each time the system is booted, so it is necessary to add hint.acpi.0.disabled="1" to the file /boot/loader.conf. More information about the boot loader can be +found in the FreeBSD Handbook.

+
+
+ +
+
+

4.2.3. My legacy ISA device used to be +recognized in previous versions of FreeBSD, but now it's not. What happened?

+
+ +
+

Some device drivers, like matcd, were removed over time due to lack of +maintainership or other reasons. Others still exist but are disabled because of their +intrusive hardware probe routines. The following ISA device drivers fall into this +category and can re-enabled from the third stage boot loader: aha, ahv, aic, bt, ed, cs, +sn, ie, fe, le, and lnc. To do this, stop the loader during it's 10 second countdown and +enter the following at the prompt:

+ +
+unset hint.foo.0.disabled
+
+ +

where foo is the name of the driver to re-enable. +This can be set permanently by editing the file /boot/device.hints and removing the appropriate +“disabled” entry.

+
+
+ +
+
+

4.2.4. I go to boot from the hard disk for +the first time after installing FreeBSD, the kernel loads and probes my hardware, but +stops with messages like:

+ +
+changing root device to ad1s1a panic: cannot mount root
+
+ +

What is wrong? What can I do?

+ +

What is this bios_drive:interface(unit,partition)kernel_name +thing that is displayed with the boot help?

+
+ +
+

There is a longstanding problem in the case where the boot disk is not the +first disk in the system. The BIOS uses a different numbering scheme to FreeBSD, and +working out which numbers correspond to which is difficult to get right.

+ +

In the case where the boot disk is not the first disk in the system, FreeBSD can need +some help finding it. There are two common situations here, and in both of these cases, +you need to tell FreeBSD where the root filesystem is. You do this by specifying the BIOS +disk number, the disk type and the FreeBSD disk number for that type.

+ +

The first situation is where you have two IDE disks, each configured as the master on +their respective IDE busses, and wish to boot FreeBSD from the second disk. The BIOS sees +these as disk 0 and disk 1, while FreeBSD sees them as ad0 +and ad2.

+ +

FreeBSD is on BIOS disk 1, of type ad and the FreeBSD disk +number is 2, so you would say:

+ +
+1:ad(2,a)kernel
+
+ +

Note that if you have a slave on the primary bus, the above is not necessary (and is +effectively wrong).

+ +

The second situation involves booting from a SCSI disk when you have one or more IDE +disks in the system. In this case, the FreeBSD disk number is lower than the BIOS disk +number. If you have two IDE disks as well as the SCSI disk, the SCSI disk is BIOS disk 2, +type da and FreeBSD disk number 0, so you would say:

+ +
+2:da(0,a)kernel
+
+ +

To tell FreeBSD that you want to boot from BIOS disk 2, which is the first SCSI disk +in the system. If you only had one IDE disk, you would use '1:' instead.

+ +

Once you have determined the correct values to use, you can put the command exactly as +you would have typed it in the /boot.config file using a +standard text editor. Unless instructed otherwise, FreeBSD will use the contents of this +file as the default response to the boot: prompt.

+
+
+ +
+
+

4.2.5. I go to boot from the hard disk for +the first time after installing FreeBSD, but the Boot Manager prompt just prints F? at the boot menu each time but the boot won't go any further.

+
+ +
+

The hard disk geometry was set incorrectly in the Partition editor when you +installed FreeBSD. Go back into the partition editor and specify the actual geometry of +your hard disk. You must reinstall FreeBSD again from the beginning with the correct +geometry.

+ +

If you are failing entirely in figuring out the correct geometry for your machine, +here's a tip: Install a small DOS partition at the beginning of the disk and install +FreeBSD after that. The install program will see the DOS partition and try to infer the +correct geometry from it, which usually works.

+ +

The following tip is no longer recommended, but is left here for reference:

+ + +
+

If you are setting up a truly dedicated FreeBSD server or workstation where you don't +care for (future) compatibility with DOS, Linux or another operating system, you've also +got the option to use the entire disk (`A' in the partition editor), selecting the +non-standard option where FreeBSD occupies the entire disk from the very first to the +very last sector. This will leave all geometry considerations aside, but is somewhat +limiting unless you're never going to run anything other than FreeBSD on a disk.

+
+
+
+ +
+
+

4.2.6. The mcd(4) driver keeps thinking that it has found a +device and this stops my Intel EtherExpress card from working.

+
+ +
+

Set the hints “hint.mcd.0.disabled="1"” and +“hint.mcd.1.disabled="1"” in the third stage boot loader to disable the +probing of the mcd0 and mcd1 +devices. Generally speaking, you should only leave the devices that you will be using +enabled in your kernel.

+
+
+ +
+
+

4.2.7. The system finds my ed(4) network card, but I +keep getting device timeout errors.

+
+ +
+

Your card is probably on a different IRQ from what is specified in the /boot/device.hints file. The ed driver does not use the `soft' +configuration by default (values entered using EZSETUP in DOS), but it will use the +software configuration if you specify -1 in the hints for the +interface.

+ +

Either move the jumper on the card to a hard configuration setting (altering the +kernel settings if necessary), or specify the IRQ as -1 by +setting the hint “hint.ed.0.irq="-1"” This will tell the kernel to use the +soft configuration.

+ +

Another possibility is that your card is at IRQ 9, which is shared by IRQ 2 and +frequently a cause of problems (especially when you have a VGA card using IRQ 2!). You +should not use IRQ 2 or 9 if at all possible.

+
+
+ +
+
+

4.2.8. I booted the install floppy on my IBM +ThinkPad (tm) laptop, and the keyboard is all messed up.

+
+ +
+

Older IBM laptops use a non-standard keyboard controller, so you must tell the +keyboard driver (atkbd0) to go into a special mode which works on the ThinkPads. Set the +hint “hint.atkbd.0.flags="4"” and it should work fine.

+
+
+ +
+
+

4.2.9. My system can not find my Intel +EtherExpress 16 card.

+
+ +
+

You must set your Intel EtherExpress 16 card to be memory mapped at address +0xD0000, and set the amount of mapped memory to 32K using the Intel supplied softset.exe program.

+
+
+ +
+
+

4.2.10. When installing on an EISA HP +Netserver, my on-board AIC-7xxx SCSI controller isn't detected.

+
+ +
+

This is a known problem, and will hopefully be fixed in the future. In order to +get your system installed at all, set the hint “hw.eisa_slots="12"” in the +third stage loader.

+
+
+ +
+
+

4.2.11. I have a Panasonic AL-N1 or Rios +Chandler Pentium machine and I find that the system hangs before ever getting into the +installation now.

+
+ +
+

Your machine doesn't like the new i586_copyout and i586_copyin code for some reason. To disable this, set the hint +“hint.npx.0.flags="1"”

+
+
+ +
+
+

4.2.12. I have this CMD640 IDE controller +that is said to be broken.

+
+ +
+

FreeBSD does not support this controller.

+
+
+ +
+
+

4.2.13. On a Compaq Aero notebook, I get +the message “No floppy devices found! Please check ...” when trying to +install from floppy.

+
+ +
+

With Compaq being always a little different from other systems, they do not +announce their floppy drive in the CMOS RAM of an Aero notebook. Therefore, the floppy +disk driver assumes there is no drive configured. Set the hint +“hint.fdc.0.flags="1"” This pretends the existence of the first floppy drive +(as a 1.44 MB drive) to the driver without asking the CMOS at all.

+
+
+ +
+
+

4.2.14. When installing on a Dell +Poweredge XE, Dell proprietary RAID controller DSA (Dell SCSI Array) isn't +recognized.

+
+ +
+

Configure the DSA to use AHA-1540 emulation using EISA configuration utility. +After that FreeBSD detects the DSA as an Adaptec AHA-1540 SCSI controller, with irq 11 +and port 340. Under emulation mode system will use DSA RAID disks, but you cannot use +DSA-specific features such as watching RAID health.

+
+
+ +
+
+

4.2.15. I have an IBM EtherJet PCI card, +it is detected by the fxp(4) driver correctly, but the lights on the card +don't come on and it doesn't connect to the network.

+
+ +
+

We don't understand why this happens. Neither do IBM (we asked them). The card +is a standard Intel EtherExpress Pro/100 with an IBM label on it, and these cards +normally work just fine. You may see these symptoms only in some IBM Netfinity servers. +The only solution is to install a different Ethernet adapter.

+
+
+ +
+
+

4.2.16. When I configure the network +during installation on an IBM Netfinity 3500, the system freezes.

+
+ +
+

There is a problem with the onboard Ethernet in the Netfinity 3500 which we +have not been able to identify at this time. It may be related to the SMP features of the +system being misconfigured. You will have to install another Ethernet adapter and avoid +attempting to configure the onboard adapter at any time.

+
+
+ +
+
+

4.2.17. When I install onto a drive +managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a read error message).

+
+ +
+

There is a bug in the Mylex driver which results in it ignoring the +“8GB” geometry mode setting in the BIOS. Use the 2GB mode instead.

+
+
+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/installation-ia64.html b/en/releases/6.3R/installation-ia64.html new file mode 100644 index 0000000000..f205bd4484 --- /dev/null +++ b/en/releases/6.3R/installation-ia64.html @@ -0,0 +1,895 @@ + + + + +FreeBSD/ia64 6.3-RELEASE Installation Instructions + + + + + +
+
+

FreeBSD/ia64 6.3-RELEASE Installation +Instructions

+ +

The FreeBSD Project

+ +

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

+ +
+
+ +
+
+

This article gives some brief instructions on installing FreeBSD/ia64 6.3-RELEASE, +with particular emphasis given to obtaining a FreeBSD distribution. Some notes on +troubleshooting and frequently-asked questions are also given.

+
+
+ +
+
+

1 Installing FreeBSD

+ +

This section documents the process of installing a new distribution of FreeBSD. These +instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE +distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.

+ +

If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

+ +
+
+

1.1 Getting +Started

+ +

Probably the most important pre-installation step that can be taken is that of reading +the various instruction documents provided with FreeBSD. A roadmap of documents +pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this +file; most of these documents, such as the release notes and the hardware compatibility +list, are also accessible in the Documentation menu of the installer.

+ +

Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

+ +

This collection of documents may seem daunting, but the time spent reading them will +likely be saved many times over. Being familiar with what resources are available can +also be helpful in the event of problems during installation.

+ +

The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You +should also read an updated copy of ERRATA.TXT before +installing, since this will alert you to any problems which have reported in the interim +for your particular release.

+ +
+
+

Important: While FreeBSD does its best to safeguard against accidental loss of +data, it's still more than possible to wipe +out your entire disk with this installation if you make a mistake. Please do +not proceed to the final FreeBSD installation menu unless you've adequately backed up any +important data first.

+
+
+
+ +
+
+

1.2 Hardware Requirements

+ +

If you are not familiar with configuring hardware for FreeBSD, you should be sure to +read the HARDWARE.TXT file; it contains important information +on what hardware is supported by FreeBSD.

+
+ +
+
+

1.3 Floppy Disk Image +Instructions

+
+ +
+
+

1.4 Installing +FreeBSD from CDROM or the Internet

+
+ +
+
+

1.5 Detail on various installation +types

+ +

Once you've gotten yourself to the initial installation screen somehow, you should be +able to follow the various menu prompts and go from there. If you've never used the +FreeBSD installation before, you are also encouraged to read some of the documentation in +the Documentation submenu as well as the general “Usage” instructions on the +first menu.

+ +
+
+

Note: If you get stuck at a screen, press the F1 key for +online documentation relevant to that specific section.

+
+
+ +

If you've never installed FreeBSD before, or even if you have, the +“Standard” installation mode is the most recommended since it makes sure that +you'll visit all the various important checklist items along the way. If you're much more +comfortable with the FreeBSD installation process and know exactly what you want to do, use the “Express” or +“Custom” installation options. If you're upgrading an existing system, use +the “Upgrade” option.

+ +

The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS +and UFS partitions as installation media; further tips on installing from each type of +media are listed below.

+ +
+
+

1.5.1 Installing from a Network +CDROM

+ +

If you simply wish to install from a local CDROM drive then see Section 1.4. If you don't have a CDROM drive on your +system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to +which you have network connectivity, there are also several ways of going about it:

+ +
    +
  • +

    If you would be able to FTP install FreeBSD directly from the CDROM drive in some +FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add +the following line to the password file (using the +vipw(8) +command):

    + +
    +ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
    + +

    On the machine on which you are running the install, go to the Options menu and set +Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp +sites menu.

    + +
    +
    +

    Warning: This may allow anyone on the local network (or Internet) to make +“anonymous FTP” connections to this machine, which may not be desirable.

    +
    +
    +
    • + +
  • +

    If you would rather use NFS to export the CDROM directly to the machine(s) you'll be +installing from, you need to first add an entry to the /etc/exports file (on the machine with the CDROM drive). The +example below allows the machine ziggy.foo.com to mount the CDROM +directly via NFS during installation:

    + +
    +/cdrom          -ro             ziggy.foo.com
+
    + +

    The machine with the CDROM must also be configured as an NFS server, of course, and if +you're not sure how to do that then an NFS installation is probably not the best choice +for you unless you're willing to read up on +rc.conf(5) and +configure things appropriately. Assuming that this part goes smoothly, you should be able +to enter: cdrom-host:/cdrom +as the path for an NFS installation when the target machine is installed, e.g. wiggy:/cdrom.

    +
    • +
+
+ +
+
+

1.5.2 Installing from Floppies

+ +

If you must install from floppy disks, either due to unsupported hardware or just +because you enjoy doing things the hard way, you must first prepare some floppies for the +install.

+ +

First, make your boot floppies as described in Section +1.3.

+ +

Second, peruse Section 2 and pay special attention to the +“Distribution Format” section since it describes which files you're going to +need to put onto floppy and which you can safely skip.

+ +

Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files +in the bin (binary distribution) directory. If you're preparing +these floppies under DOS, then these floppies must be formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File +Manager format command.

+ +
+
+

Important: Frequently, floppy disks come “factory preformatted”. +While convenient, many problems reported by users in the past have resulted from the use +of improperly formatted media. Re-format them yourself, just to make sure.

+
+
+ +

If you're creating the floppies from another FreeBSD machine, a format is still not a +bad idea though you don't need to put a DOS filesystem on each floppy. You can use the +disklabel(8) and + +newfs(8) +commands to put a UFS filesystem on a floppy, as the following sequence of commands +illustrates:

+ +
+# fdformat -f 1440 fd0
+# disklabel -w fd0 floppy3
+# newfs -i 65536 /dev/fd0
+
+ +

After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto +them. The distribution files are sized so that a floppy disk will hold a single file. +Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +
+
+

Important: The bin.inf file also needs to go on the +first floppy of the bin set since it is read by the +installation program in order to figure out how many additional pieces to look for when +fetching and concatenating the distribution. When putting distributions onto floppies, +the distname.inf file must occupy the first floppy of each distribution set.

+
+
+ +

Once you come to the Media screen of the install, select “Floppy” and +you'll be prompted for the rest.

+
+ +
+
+

1.5.4 Installing from QIC/SCSI +Tape

+ +

When installing from tape, the installation program expects the files to be simply +tar'ed onto it, so after fetching all of the files for the distributions you're +interested in, simply use +tar(1) to get +them onto the tape with a command something like this:

+ +
+# cd /where/you/have/your/dists
+# tar cvf /dev/sa0 dist1 .. dist2
+
+ +

When you go to do the installation, you should also make sure that you leave enough +room in some temporary directory (which you'll be allowed to choose) to accommodate the +full contents of the tape you've +created. Due to the non-random access nature of tapes, this method of installation +requires quite a bit of temporary storage. You should expect to require as much temporary +storage as you have stuff written on tape.

+ +
+
+

Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. +The installation “probe” may otherwise fail to find it.

+
+
+ +

Now create a boot floppy as described in Section 1.3 and +proceed with the installation.

+
+ +
+
+

1.5.5 Installing over a Network using FTP +or NFS

+ +

After making the boot floppies as described in the first section, you can load the +rest of the installation over a network using one of 3 types of connections: serial port, +parallel port, or Ethernet.

+ +
+
+
1.5.5.1 Serial Port
+ +

SLIP support is rather primitive, and is limited primarily to hard-wired links, such +as a serial cable running between two computers. The link must be hard-wired because the +SLIP installation doesn't currently offer a dialing capability. If you need to dial out +with a modem or otherwise dialog with the link before connecting to it, then the PPP +utility should be used instead.

+ +

If you're using PPP, make sure that you have your Internet Service Provider's IP +address and DNS information handy as you'll need to know it fairly early in the +installation process. You may also need to know your own IP address, though PPP supports +dynamic address negotiation and may be able to pick up this information directly from +your ISP if they support it.

+ +

You will also need to know how to use the various “AT commands” for +dialing out with your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator.

+
+ +
+
+
1.5.5.2 Parallel Port
+ +

If a hard-wired connection to another FreeBSD or Linux machine is available, you might +also consider installing over a “laplink” style parallel port cable. The data +rate over the parallel port is much higher than what is typically possible over a serial +line (up to 50k/sec), thus resulting in a quicker installation. It's not typically +necessary to use “real” IP addresses when using a point-to-point parallel +cable in this way and you can generally just use RFC 1918 style addresses for the ends of +the link (e.g. 10.0.0.1, 10.0.0.2, +etc).

+ +
+
+

Important: If you use a Linux machine rather than a FreeBSD machine as your +PLIP peer, you will also have to specify link0 in the TCP/IP +setup screen's “extra options for ifconfig” field in order to be compatible +with Linux's slightly different PLIP protocol.

+
+
+
+ +
+
+
1.5.5.3 Ethernet
+ +

FreeBSD supports most common Ethernet cards; a table of supported cards is provided as +part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the +Documentation menu on the boot floppy or the top level directory of the CDROM). If you +are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in +before the laptop is powered on. +FreeBSD does not, unfortunately, currently support “hot insertion” of PCMCIA +cards during installation.

+ +

You will also need to know your IP address on the network, the netmask value for your subnet and the name of your machine. Your +system administrator can tell you which values are appropriate to your particular network +setup. If you will be referring to other hosts by name rather than IP address, you'll +also need a name server and possibly the address of a gateway (if you're using PPP, it's +your provider's IP address) to use in talking to it. If you want to install by FTP via an +HTTP proxy (see below), you will also need the proxy's address.

+ +

If you do not know the answers to these questions then you should really probably talk +to your system administrator first +before trying this type of installation. Using a randomly chosen IP address or netmask on +a live network is almost guaranteed not to work, and will probably result in a lecture +from said system administrator.

+ +

Once you have a network connection of some sort working, the installation can continue +over NFS or FTP.

+
+ +
+
+
1.5.5.4 NFS installation tips
+ +

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution +files you want onto a server somewhere and then point the NFS media selection at it.

+ +

If this server supports only “privileged port” access (this is generally +the default for Sun and Linux workstations), you may need to set this option in the +Options menu before installation can proceed.

+ +

If you have a poor quality Ethernet card which suffers from very slow transfer rates, +you may also wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server must also support “subdir +mounts”, e.g. if your FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr +or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled by the +-alldirs option. Other NFS servers may have different +conventions. If you are getting Permission Denied messages from +the server then it's likely that you don't have this properly enabled.

+
+ +
+
+
1.5.5.5 FTP Installation tips
+ +

FTP installation may be done from any mirror site containing a reasonably up-to-date +version of FreeBSD. A full menu of reasonable choices for almost any location in the +world is provided in the FTP site menu during installation.

+ +

If you are installing from some other FTP site not listed in this menu, or you are +having troubles getting your name server configured properly, you can also specify your +own URL by selecting the “URL” choice in that menu. A URL can contain a +hostname or an IP address, so something like the following would work in the absence of a +name server:

+ +
+ftp://216.66.64.162/pub/FreeBSD/releases/ia64/4.2-RELEASE
+
+ +

There are three FTP installation modes you can use:

+ +
    +
  • +

    FTP: This method uses the standard “Active” mode for transfers, in which +the server initiates a connection to the client. This will not work through most +firewalls but will often work best with older FTP servers that do not support passive +mode. If your connection hangs with passive mode, try this one.

    +
    • + +
  • +

    FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening +connections to the client. This option is best for users to pass through firewalls that +do not allow incoming connections on random port addresses.

    +
    • + +
  • +

    FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy +for all FTP operations. The proxy will translate the requests and send them to the FTP +server. This allows the user to pass through firewalls that do not allow FTP at all, but +offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP +server.

    + +

    In the rare case that you have an FTP proxy that does not go through HTTP, you can +specify the URL as something like:

    + +
    +ftp://foo.bar.com:port/pub/FreeBSD
+
    + +

    In the URL above, port is the port number of the +proxy FTP server.

    +
    • +
+
+
+
+ +
+
+

1.6 Question and Answer Section for IA-64 +Architecture Users

+
+
+ +
+
+

2 Distribution Format

+ +

A typical FreeBSD distribution directory looks something like this (exact details may +vary depending on version, architecture, and other factors):

+ +
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    base            compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+
+ +

These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see Section 4 for how to use this).

+ +

The floppies directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.

+ +

If you're trying to do some other type of installation or are merely curious about how +a distribution is organized, what follows is a more thorough description of some of these +items in more detail:

+ +
    +
  1. +

    The *.TXT and *.HTM files contain +documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should +be read before starting an installation. The *.TXT files are +plain text, while the *.HTM files are HTML files that can be +read by almost any Web browser. Some distributions may contain documentation in other +formats as well, such as PDF or PostScript.

    +
    2. + +
  2. +

    docbook.css is a Cascading Style Sheet (CSS) file used by +some Web browsers for formatting the HTML documentation.

    +
    3. + +
  3. +

    The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the +primary distribution components of FreeBSD itself and are split into smaller files for +easy packing onto floppies (should that be necessary).

    +
    4. + +
  4. +

    The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories +contain distributions for compatibility with older releases and are distributed as single +gzip'd tar files - they can be installed during release time or later by running their +install.sh scripts.

    +
    5. + +
  5. +

    The floppies/ subdirectory contains the floppy installation +images; further information on using them can be found in Section +1.3.

    +
    6. + +
  6. +

    The packages and ports directories +contain the FreeBSD Packages and Ports Collections. Packages may be installed from the +packages directory by running the command:

    + +
    +# sysinstall configPackages
+
    + +

    Packages can also be installed by feeding individual filenames in packages/ to the +pkg_add(1) +command.

    + +

    The Ports Collection may be installed like any other distribution and requires about +190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or +locally from /usr/share/doc/handbook if you've installed the +doc distribution.

    +
    7. + +
  7. +

    Last of all, the tools directory contains various DOS tools +for discovering disk geometries, installing boot managers and the like. It is purely +optional and provided only for user convenience.

    +
    8. +
+ +

A typical distribution directory (for example, the info +distribution) looks like this internally:

+ +
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+
+ +

The CHECKSUM.MD5 file contains MD5 signatures for each file, +should data corruption be suspected, and is purely for reference. It is not used by the +actual installation and does not need to be copied with the rest of the distribution +files. The info.a* files are split, gzip'd tar files, the +contents of which can be viewed by doing:

+ +
+# cat info.a* | tar tvzf -
+
+ +

During installation, they are automatically concatenated and extracted by the +installation procedure.

+ +

The info.inf file is also necessary since it is read by the +installation program in order to figure out how many pieces to look for when fetching and +concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

+ +

The info.mtree file is another non-essential file which is +provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be +later used with the +mtree(8) program +to verify the installation permissions and checksums against any possible modifications +to the file. When used with the base distribution, this can be +an excellent way of detecting trojan horse attacks on your system.

+ +

Finally, the install.sh file is for use by those who want to +install the distribution after installation time. To install the info distribution from +CDROM after a system was installed, for example, you'd do:

+ +
+# cd /cdrom/info
+# sh install.sh
+
+
+ +
+
+

3 Upgrading FreeBSD

+ +

These instructions describe a procedure for doing a binary upgrade from an older +version of FreeBSD.

+ +
+
+

Warning: While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do +not accept the final confirmation request unless you have adequately backed up any +important data files.

+
+
+ +
+
+

Important: These notes assume that you are using the version of +sysinstall(8) +supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched +version of +sysinstall(8) is +almost guaranteed to cause problems and has been known to leave systems in an unusable +state. The most commonly made mistake in this regard is the use of an old copy of +sysinstall(8) +from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.

+
+
+ +
+
+

Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).

+ +

These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.3-STABLE snapshots.

+
+
+ +
+
+

3.1 Introduction

+ +

The upgrade procedure replaces distributions selected by the user with those +corresponding to the new FreeBSD release. It preserves standard system configuration +data, as well as user data, installed packages and other software.

+ +

Administrators contemplating an upgrade are encouraged to study this section in its +entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or +loss of data.

+ +
+
+

3.1.1 Upgrade Overview

+ +

Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.

+ +

System configuration is preserved by retaining and restoring the previous version of +the following files:

+ +

Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

+ +

The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.

+ +

During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.

+
+
+ +
+
+

3.2 Procedure

+ +

This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.

+ +
+
+

3.2.1 Backup

+ +

User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.

+
+ +
+
+

3.2.2 Mount Filesystems

+ +

The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” +for any filesystems, as this will cause data loss.

+
+ +
+
+

3.2.3 Select Distributions

+ +

When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.

+
+ +
+
+

3.2.4 After Installation

+ +

Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.

+
+
+ +
+
+

3.3 Upgrading from Source Code

+ +

Those interested in an upgrade method that allows more flexibility and sophistication +should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves +rebuilding all of FreeBSD from source code. It requires reliable network connectivity, +extra disk space, and time, but has advantages for networks and other more complex +installations. This is roughly the same procedure as is used for track the -STABLE or +-CURRENT development branches.

+ +

/usr/src/UPDATING contains important information on updating +a FreeBSD system from source code. It lists various issues resulting from changes in +FreeBSD that may affect an upgrade.

+
+
+ +
+
+

4 Troubleshooting

+ +
+

4.1 Repairing an Existing FreeBSD +Installation

+ +

FreeBSD features a “fixit” option in the top menu of the +sysinstall(8) +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.

+ +

Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main +sysinstall(8) +menu. Then select the “CDROM/DVD” option from the fixit menu.

+ +

Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the boot.flp and kernX.flp disks required for +installation, create the fixit.flp floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main +sysinstall(8) +menu. At that point, choose the “fixit” item from the main +sysinstall(8) +menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

+ +

The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.

+ +

In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM +version of fixit, these same programs can be found in /stand or +/mnt2/rescue (as well as the rest of the programs from the live +filesystem, which can be found under /mnt).

+
+ +
+
+

4.2 Common Installation Problems for IA-64 +Architecture Users

+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/installation-pc98.html b/en/releases/6.3R/installation-pc98.html new file mode 100644 index 0000000000..d02df6e78a --- /dev/null +++ b/en/releases/6.3R/installation-pc98.html @@ -0,0 +1,1018 @@ + + + + +FreeBSD/pc98 6.3-RELEASE Installation Instructions + + + + + +
+
+

FreeBSD/pc98 6.3-RELEASE Installation +Instructions

+ +

The FreeBSD Project

+ +

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

+ +
+
+ +
+
+

This article gives some brief instructions on installing FreeBSD/pc98 6.3-RELEASE, +with particular emphasis given to obtaining a FreeBSD distribution. Some notes on +troubleshooting and frequently-asked questions are also given.

+
+
+ +
+
+

1 Installing FreeBSD

+ +

This section documents the process of installing a new distribution of FreeBSD. These +instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE +distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.

+ +

If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

+ +
+
+

1.1 Getting +Started

+ +

Probably the most important pre-installation step that can be taken is that of reading +the various instruction documents provided with FreeBSD. A roadmap of documents +pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this +file; most of these documents, such as the release notes and the hardware compatibility +list, are also accessible in the Documentation menu of the installer.

+ +

Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

+ +

This collection of documents may seem daunting, but the time spent reading them will +likely be saved many times over. Being familiar with what resources are available can +also be helpful in the event of problems during installation.

+ +

The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You +should also read an updated copy of ERRATA.TXT before +installing, since this will alert you to any problems which have reported in the interim +for your particular release.

+ +
+
+

Important: While FreeBSD does its best to safeguard against accidental loss of +data, it's still more than possible to wipe +out your entire disk with this installation if you make a mistake. Please do +not proceed to the final FreeBSD installation menu unless you've adequately backed up any +important data first.

+
+
+
+ +
+
+

1.2 Hardware Requirements

+ +

FreeBSD for the NEC PC-98x1 requires a 486 or better processor and at least 24 MB +of RAM. You will need at least 150MB of free hard drive space for the most minimal +installation. See below for ways of shrinking existing DOS partitions in order to install +FreeBSD.

+ +

If you are not familiar with configuring hardware for FreeBSD, you should be sure to +read the HARDWARE.TXT file; it contains important information +on what hardware is supported by FreeBSD.

+
+ +
+
+

1.3 Floppy Disk Image +Instructions

+ +

Depending on how you choose to install FreeBSD, you may need to create a set of floppy +disks (usually four) to begin the installation process. This section briefly describes +how to create these disks, either from a CDROM installation or from the Internet. Note +that in the common case of installing FreeBSD from CDROM, on a machine that supports +bootable CDROMs, the steps outlined in this section will not be needed and can be +skipped.

+ +

For a normal CDROM or network installation, all you need to copy onto actual floppies +from the floppies/ directory are the boot.flp and kernX.flp images (for 1.44MB floppies) or boot-small.flp and kern-small.flp images +(for 1.2MB floppies).

+ +

Getting these images over the network is easy. Simply fetch the release/floppies/boot.flp, and +all of the release/floppies/kernX.flp files from +ftp://ftp.FreeBSD.org/ or one of the +many mirrors listed at FTP Sites section of the Handbook, or on the http://mirrorlist.FreeBSD.org/ +Web pages.

+ +

Get several blank, freshly formatted floppies and image copy boot.flp onto one and the kernX.flp files onto the others. These images are not DOS files. You cannot simply copy +them to a DOS or UFS floppy as regular files, you need to “image” copy them +to the floppy with rawrite.exe under DOS (see the tools directory on your CDROM or FreeBSD FTP mirror) or the dd(1) command in +UNIX.

+ +

For example, to create the kernel floppy image from DOS, you'd do something like +this:

+ +
+A> rawrite
+
+ +

Assuming that you'd copied rawrite.exe and boot.flp into a directory somewhere. You would do the same for the +kernX.flp files, of +course.

+ +

If you're creating the boot floppy from a UNIX machine, you may find that:

+ +
+# dd if=floppies/boot.flp of=/dev/rfd0.1440
+
+ +

or

+ +
+# dd if=floppies/boot-small.flp of=/dev/rfd0.1200
+
+ +

work well, depending on your hardware and operating system environment (different +versions of UNIX have different names for the floppy drive).

+
+ +
+
+

1.4 Installing +FreeBSD from CDROM or the Internet

+ +

The easiest type of installation is from CDROM. If you have a supported CDROM drive +and a FreeBSD installation CDROM, there is a next way of starting the installation from +it:

+ +
    +
  • +

    Build a set of FreeBSD boot floppies from the floppies/ +directory in every FreeBSD distribution. Read Section 1.3 for +more information on creating the bootable floppies under different operating systems. +Then you simply boot from the first floppy and you should soon be in the FreeBSD +installation.

    +
    • +
+ +
+
+

If you don't have a CDROM and would like to simply install over the net using PPP, +SLIP or a dedicated connection, you should start the installation by building a set of +FreeBSD boot floppies from the files floppies/boot.flp and floppies/kernX.flp using the +instructions found in Section 1.3. Restart your computer using +the boot.flp disk; when prompted, insert the other disks as +required. Then, please go to Section 1.5.5 for additional tips on +installing via FTP or NFS.

+
+ +
+
+

1.5 Detail on various installation +types

+ +

Once you've gotten yourself to the initial installation screen somehow, you should be +able to follow the various menu prompts and go from there. If you've never used the +FreeBSD installation before, you are also encouraged to read some of the documentation in +the Documentation submenu as well as the general “Usage” instructions on the +first menu.

+ +
+
+

Note: If you get stuck at a screen, press the F1 key for +online documentation relevant to that specific section.

+
+
+ +

If you've never installed FreeBSD before, or even if you have, the +“Standard” installation mode is the most recommended since it makes sure that +you'll visit all the various important checklist items along the way. If you're much more +comfortable with the FreeBSD installation process and know exactly what you want to do, use the “Express” or +“Custom” installation options. If you're upgrading an existing system, use +the “Upgrade” option.

+ +

The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS +and UFS partitions as installation media; further tips on installing from each type of +media are listed below.

+ +
+
+

1.5.1 Installing from a Network +CDROM

+ +

If you simply wish to install from a local CDROM drive then see Section 1.4. If you don't have a CDROM drive on your +system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to +which you have network connectivity, there are also several ways of going about it:

+ +
    +
  • +

    If you would be able to FTP install FreeBSD directly from the CDROM drive in some +FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add +the following line to the password file (using the +vipw(8) +command):

    + +
    +ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
    + +

    On the machine on which you are running the install, go to the Options menu and set +Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp +sites menu.

    + +
    +
    +

    Warning: This may allow anyone on the local network (or Internet) to make +“anonymous FTP” connections to this machine, which may not be desirable.

    +
    +
    +
    • + +
  • +

    If you would rather use NFS to export the CDROM directly to the machine(s) you'll be +installing from, you need to first add an entry to the /etc/exports file (on the machine with the CDROM drive). The +example below allows the machine ziggy.foo.com to mount the CDROM +directly via NFS during installation:

    + +
    +/cdrom          -ro             ziggy.foo.com
+
    + +

    The machine with the CDROM must also be configured as an NFS server, of course, and if +you're not sure how to do that then an NFS installation is probably not the best choice +for you unless you're willing to read up on +rc.conf(5) and +configure things appropriately. Assuming that this part goes smoothly, you should be able +to enter: cdrom-host:/cdrom +as the path for an NFS installation when the target machine is installed, e.g. wiggy:/cdrom.

    +
    • +
+
+ +
+
+

1.5.2 Installing from Floppies

+ +

If you must install from floppy disks, either due to unsupported hardware or just +because you enjoy doing things the hard way, you must first prepare some floppies for the +install.

+ +

First, make your boot floppies as described in Section +1.3.

+ +

Second, peruse Section 2 and pay special attention to the +“Distribution Format” section since it describes which files you're going to +need to put onto floppy and which you can safely skip.

+ +

Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files +in the bin (binary distribution) directory. If you're preparing +these floppies under DOS, then these floppies must be formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File +Manager format command.

+ +
+
+

Important: Frequently, floppy disks come “factory preformatted”. +While convenient, many problems reported by users in the past have resulted from the use +of improperly formatted media. Re-format them yourself, just to make sure.

+
+
+ +

If you're creating the floppies from another FreeBSD machine, a format is still not a +bad idea though you don't need to put a DOS filesystem on each floppy. You can use the +disklabel(8) and + +newfs(8) +commands to put a UFS filesystem on a floppy, as the following sequence of commands +illustrates:

+ +
+# fdformat -f 1440 fd0
+# disklabel -w fd0 floppy3
+# newfs -i 65536 /dev/fd0
+
+ +

After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto +them. The distribution files are sized so that a floppy disk will hold a single file. +Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +
+
+

Important: The bin.inf file also needs to go on the +first floppy of the bin set since it is read by the +installation program in order to figure out how many additional pieces to look for when +fetching and concatenating the distribution. When putting distributions onto floppies, +the distname.inf file must occupy the first floppy of each distribution set.

+
+
+ +

Once you come to the Media screen of the install, select “Floppy” and +you'll be prompted for the rest.

+
+ +
+
+

1.5.3 Installing from a DOS +partition

+ +

To prepare for installation from an MS-DOS partition you should simply copy the files +from the distribution into a directory called FREEBSD on the +Primary DOS partition (A:). For example, to do a minimal +installation of FreeBSD from DOS using files copied from the CDROM, you might do +something like this:

+ +
+A:\> MD A:\FREEBSD
+A:\> XCOPY /S E:\BASE A:\FREEBSD\BASE
+
+ +

Assuming that E: was where your CD was mounted.

+ +

For as many distributions as you wish to install from DOS (and you have free space +for), install each one in a directory under A:\FREEBSD - the +BIN dist is only the minimal requirement.

+ +

Once you've copied the directories, you can simply launch the installation from +floppies as normal and select “DOS” as your media type when the time +comes.

+
+ +
+
+

1.5.4 Installing from QIC/SCSI +Tape

+ +

When installing from tape, the installation program expects the files to be simply +tar'ed onto it, so after fetching all of the files for the distributions you're +interested in, simply use +tar(1) to get +them onto the tape with a command something like this:

+ +
+# cd /where/you/have/your/dists
+# tar cvf /dev/sa0 dist1 .. dist2
+
+ +

When you go to do the installation, you should also make sure that you leave enough +room in some temporary directory (which you'll be allowed to choose) to accommodate the +full contents of the tape you've +created. Due to the non-random access nature of tapes, this method of installation +requires quite a bit of temporary storage. You should expect to require as much temporary +storage as you have stuff written on tape.

+ +
+
+

Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. +The installation “probe” may otherwise fail to find it.

+
+
+ +

Now create a boot floppy as described in Section 1.3 and +proceed with the installation.

+
+ +
+
+

1.5.5 Installing over a Network using FTP +or NFS

+ +

After making the boot floppies as described in the first section, you can load the +rest of the installation over a network using one of 3 types of connections: serial port, +parallel port, or Ethernet.

+ +
+
+
1.5.5.1 Serial Port
+ +

SLIP support is rather primitive, and is limited primarily to hard-wired links, such +as a serial cable running between two computers. The link must be hard-wired because the +SLIP installation doesn't currently offer a dialing capability. If you need to dial out +with a modem or otherwise dialog with the link before connecting to it, then the PPP +utility should be used instead.

+ +

If you're using PPP, make sure that you have your Internet Service Provider's IP +address and DNS information handy as you'll need to know it fairly early in the +installation process. You may also need to know your own IP address, though PPP supports +dynamic address negotiation and may be able to pick up this information directly from +your ISP if they support it.

+ +

You will also need to know how to use the various “AT commands” for +dialing out with your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator.

+
+ +
+
+
1.5.5.2 Parallel Port
+ +

If a hard-wired connection to another FreeBSD or Linux machine is available, you might +also consider installing over a “laplink” style parallel port cable. The data +rate over the parallel port is much higher than what is typically possible over a serial +line (up to 50k/sec), thus resulting in a quicker installation. It's not typically +necessary to use “real” IP addresses when using a point-to-point parallel +cable in this way and you can generally just use RFC 1918 style addresses for the ends of +the link (e.g. 10.0.0.1, 10.0.0.2, +etc).

+ +
+
+

Important: If you use a Linux machine rather than a FreeBSD machine as your +PLIP peer, you will also have to specify link0 in the TCP/IP +setup screen's “extra options for ifconfig” field in order to be compatible +with Linux's slightly different PLIP protocol.

+
+
+
+ +
+
+
1.5.5.3 Ethernet
+ +

FreeBSD supports most common Ethernet cards; a table of supported cards is provided as +part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the +Documentation menu on the boot floppy or the top level directory of the CDROM). If you +are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in +before the laptop is powered on. +FreeBSD does not, unfortunately, currently support “hot insertion” of PCMCIA +cards during installation.

+ +

You will also need to know your IP address on the network, the netmask value for your subnet and the name of your machine. Your +system administrator can tell you which values are appropriate to your particular network +setup. If you will be referring to other hosts by name rather than IP address, you'll +also need a name server and possibly the address of a gateway (if you're using PPP, it's +your provider's IP address) to use in talking to it. If you want to install by FTP via an +HTTP proxy (see below), you will also need the proxy's address.

+ +

If you do not know the answers to these questions then you should really probably talk +to your system administrator first +before trying this type of installation. Using a randomly chosen IP address or netmask on +a live network is almost guaranteed not to work, and will probably result in a lecture +from said system administrator.

+ +

Once you have a network connection of some sort working, the installation can continue +over NFS or FTP.

+
+ +
+
+
1.5.5.4 NFS installation tips
+ +

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution +files you want onto a server somewhere and then point the NFS media selection at it.

+ +

If this server supports only “privileged port” access (this is generally +the default for Sun and Linux workstations), you may need to set this option in the +Options menu before installation can proceed.

+ +

If you have a poor quality Ethernet card which suffers from very slow transfer rates, +you may also wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server must also support “subdir +mounts”, e.g. if your FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr +or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled by the +-alldirs option. Other NFS servers may have different +conventions. If you are getting Permission Denied messages from +the server then it's likely that you don't have this properly enabled.

+
+ +
+
+
1.5.5.5 FTP Installation tips
+ +

FTP installation may be done from any mirror site containing a reasonably up-to-date +version of FreeBSD. A full menu of reasonable choices for almost any location in the +world is provided in the FTP site menu during installation.

+ +

If you are installing from some other FTP site not listed in this menu, or you are +having troubles getting your name server configured properly, you can also specify your +own URL by selecting the “URL” choice in that menu. A URL can contain a +hostname or an IP address, so something like the following would work in the absence of a +name server:

+ +
+ftp://216.66.64.162/pub/FreeBSD/releases/pc98/4.2-RELEASE
+
+ +

There are three FTP installation modes you can use:

+ +
    +
  • +

    FTP: This method uses the standard “Active” mode for transfers, in which +the server initiates a connection to the client. This will not work through most +firewalls but will often work best with older FTP servers that do not support passive +mode. If your connection hangs with passive mode, try this one.

    +
    • + +
  • +

    FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening +connections to the client. This option is best for users to pass through firewalls that +do not allow incoming connections on random port addresses.

    +
    • + +
  • +

    FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy +for all FTP operations. The proxy will translate the requests and send them to the FTP +server. This allows the user to pass through firewalls that do not allow FTP at all, but +offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP +server.

    + +

    In the rare case that you have an FTP proxy that does not go through HTTP, you can +specify the URL as something like:

    + +
    +ftp://foo.bar.com:port/pub/FreeBSD
+
    + +

    In the URL above, port is the port number of the +proxy FTP server.

    +
    • +
+
+
+
+ +
+
+

1.6 Question and Answer Section for NEC +PC-98x1 Architecture Users

+
+
+ +
+
+

2 Distribution Format

+ +

A typical FreeBSD distribution directory looks something like this (exact details may +vary depending on version, architecture, and other factors):

+ +
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    base            compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+
+ +

These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see Section 4 for how to use this).

+ +

The floppies directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.

+ +

If you're trying to do some other type of installation or are merely curious about how +a distribution is organized, what follows is a more thorough description of some of these +items in more detail:

+ +
    +
  1. +

    The *.TXT and *.HTM files contain +documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should +be read before starting an installation. The *.TXT files are +plain text, while the *.HTM files are HTML files that can be +read by almost any Web browser. Some distributions may contain documentation in other +formats as well, such as PDF or PostScript.

    +
    2. + +
  2. +

    docbook.css is a Cascading Style Sheet (CSS) file used by +some Web browsers for formatting the HTML documentation.

    +
    3. + +
  3. +

    The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the +primary distribution components of FreeBSD itself and are split into smaller files for +easy packing onto floppies (should that be necessary).

    +
    4. + +
  4. +

    The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories +contain distributions for compatibility with older releases and are distributed as single +gzip'd tar files - they can be installed during release time or later by running their +install.sh scripts.

    +
    5. + +
  5. +

    The floppies/ subdirectory contains the floppy installation +images; further information on using them can be found in Section +1.3.

    +
    6. + +
  6. +

    The packages and ports directories +contain the FreeBSD Packages and Ports Collections. Packages may be installed from the +packages directory by running the command:

    + +
    +# sysinstall configPackages
+
    + +

    Packages can also be installed by feeding individual filenames in packages/ to the +pkg_add(1) +command.

    + +

    The Ports Collection may be installed like any other distribution and requires about +190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or +locally from /usr/share/doc/handbook if you've installed the +doc distribution.

    +
    7. + +
  7. +

    Last of all, the tools directory contains various DOS tools +for discovering disk geometries, installing boot managers and the like. It is purely +optional and provided only for user convenience.

    +
    8. +
+ +

A typical distribution directory (for example, the info +distribution) looks like this internally:

+ +
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+
+ +

The CHECKSUM.MD5 file contains MD5 signatures for each file, +should data corruption be suspected, and is purely for reference. It is not used by the +actual installation and does not need to be copied with the rest of the distribution +files. The info.a* files are split, gzip'd tar files, the +contents of which can be viewed by doing:

+ +
+# cat info.a* | tar tvzf -
+
+ +

During installation, they are automatically concatenated and extracted by the +installation procedure.

+ +

The info.inf file is also necessary since it is read by the +installation program in order to figure out how many pieces to look for when fetching and +concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

+ +

The info.mtree file is another non-essential file which is +provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be +later used with the +mtree(8) program +to verify the installation permissions and checksums against any possible modifications +to the file. When used with the base distribution, this can be +an excellent way of detecting trojan horse attacks on your system.

+ +

Finally, the install.sh file is for use by those who want to +install the distribution after installation time. To install the info distribution from +CDROM after a system was installed, for example, you'd do:

+ +
+# cd /cdrom/info
+# sh install.sh
+
+
+ +
+
+

3 Upgrading FreeBSD

+ +

These instructions describe a procedure for doing a binary upgrade from an older +version of FreeBSD.

+ +
+
+

Warning: While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do +not accept the final confirmation request unless you have adequately backed up any +important data files.

+
+
+ +
+
+

Important: These notes assume that you are using the version of +sysinstall(8) +supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched +version of +sysinstall(8) is +almost guaranteed to cause problems and has been known to leave systems in an unusable +state. The most commonly made mistake in this regard is the use of an old copy of +sysinstall(8) +from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.

+
+
+ +
+
+

Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).

+ +

These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.3-STABLE snapshots.

+
+
+ +
+
+

3.1 Introduction

+ +

The upgrade procedure replaces distributions selected by the user with those +corresponding to the new FreeBSD release. It preserves standard system configuration +data, as well as user data, installed packages and other software.

+ +

Administrators contemplating an upgrade are encouraged to study this section in its +entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or +loss of data.

+ +
+
+

3.1.1 Upgrade Overview

+ +

Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.

+ +

System configuration is preserved by retaining and restoring the previous version of +the following files:

+ +

Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

+ +

The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.

+ +

During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.

+
+
+ +
+
+

3.2 Procedure

+ +

This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.

+ +
+
+

3.2.1 Backup

+ +

User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.

+
+ +
+
+

3.2.2 Mount Filesystems

+ +

The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” +for any filesystems, as this will cause data loss.

+
+ +
+
+

3.2.3 Select Distributions

+ +

When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.

+
+ +
+
+

3.2.4 After Installation

+ +

Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.

+
+
+ +
+
+

3.3 Upgrading from Source Code

+ +

Those interested in an upgrade method that allows more flexibility and sophistication +should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves +rebuilding all of FreeBSD from source code. It requires reliable network connectivity, +extra disk space, and time, but has advantages for networks and other more complex +installations. This is roughly the same procedure as is used for track the -STABLE or +-CURRENT development branches.

+ +

/usr/src/UPDATING contains important information on updating +a FreeBSD system from source code. It lists various issues resulting from changes in +FreeBSD that may affect an upgrade.

+
+
+ +
+
+

4 Troubleshooting

+ +
+

4.1 Repairing an Existing FreeBSD +Installation

+ +

FreeBSD features a “fixit” option in the top menu of the +sysinstall(8) +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.

+ +

Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main +sysinstall(8) +menu. Then select the “CDROM/DVD” option from the fixit menu.

+ +

Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the boot.flp and kernX.flp disks required for +installation, create the fixit.flp floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main +sysinstall(8) +menu. At that point, choose the “fixit” item from the main +sysinstall(8) +menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

+ +

The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.

+ +

In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM +version of fixit, these same programs can be found in /stand or +/mnt2/rescue (as well as the rest of the programs from the live +filesystem, which can be found under /mnt).

+
+ +
+
+

4.2 Common Installation Problems for NEC +PC-98x1 Architecture Users

+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/installation-sparc64.html b/en/releases/6.3R/installation-sparc64.html new file mode 100644 index 0000000000..4459950913 --- /dev/null +++ b/en/releases/6.3R/installation-sparc64.html @@ -0,0 +1,950 @@ + + + + +FreeBSD/sparc64 6.3-RELEASE Installation Instructions + + + + + +
+
+

FreeBSD/sparc64 6.3-RELEASE Installation +Instructions

+ +

The FreeBSD Project

+ +

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

+ +
+
+ +
+
+

This article gives some brief instructions on installing FreeBSD/sparc64 6.3-RELEASE, +with particular emphasis given to obtaining a FreeBSD distribution. Some notes on +troubleshooting and frequently-asked questions are also given.

+
+
+ +
+
+

1 Installing FreeBSD

+ +

This section documents the process of installing a new distribution of FreeBSD. These +instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE +distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.

+ +

If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

+ +
+
+

1.1 Getting +Started

+ +

Probably the most important pre-installation step that can be taken is that of reading +the various instruction documents provided with FreeBSD. A roadmap of documents +pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this +file; most of these documents, such as the release notes and the hardware compatibility +list, are also accessible in the Documentation menu of the installer.

+ +

Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

+ +

This collection of documents may seem daunting, but the time spent reading them will +likely be saved many times over. Being familiar with what resources are available can +also be helpful in the event of problems during installation.

+ +

The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You +should also read an updated copy of ERRATA.TXT before +installing, since this will alert you to any problems which have reported in the interim +for your particular release.

+ +
+
+

Important: While FreeBSD does its best to safeguard against accidental loss of +data, it's still more than possible to wipe +out your entire disk with this installation if you make a mistake. Please do +not proceed to the final FreeBSD installation menu unless you've adequately backed up any +important data first.

+
+
+
+ +
+
+

1.2 Hardware Requirements

+ +

FreeBSD for the UltraSPARC supports the platforms described in HARDWARE.TXT.

+ +

You will need a dedicated disk for FreeBSD/sparc64. It is not possible to share a disk +with another operating system at this time.

+ +

If you are not familiar with configuring hardware for FreeBSD, you should be sure to +read the HARDWARE.TXT file; it contains important information +on what hardware is supported by FreeBSD.

+
+ +
+
+

1.3 Floppy Disk Image +Instructions

+ +

Floppy disk based install is not supported on FreeBSD/sparc64.

+
+ +
+
+

1.4 Installing +FreeBSD from CDROM or the Internet

+ +

Most sparc64 systems are set up to boot automatically from disk. To install FreeBSD, +you need to boot over the network or from a CDROM, which requires you to break into the +PROM (OpenFirmware).

+ +

To do this, reboot the system, and wait until the boot message appears. It depends on +the model, but should look about like:

+ +
+Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
+Copyright 1998-2001 Sun Microsystems, Inc.  All rights reserved.
+OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
+Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.
+
+ +

If your system proceeds to boot from disk at this point, you need to press L1+A or Stop+A on the keyboard, or send a BREAK over the +serial console (using for example ~# in +tip(1) or cu(1)) to get to the +PROM prompt. It looks like this:

+ +
+ok         (1)
+ok {0}     (2)
+
+ +
+
+
(1)
+ +
This is the prompt used on systems with just one CPU.
+ +
(2)
+ +
This is the prompt used on SMP systems, the digit indicates the number of the active +CPU.
+
+
+ +

At this point, place the CDROM into your drive, and from the PROM prompt, type boot cdrom.

+
+ +
+
+

1.5 Detail on various installation +types

+ +

Once you've gotten yourself to the initial installation screen somehow, you should be +able to follow the various menu prompts and go from there. If you've never used the +FreeBSD installation before, you are also encouraged to read some of the documentation in +the Documentation submenu as well as the general “Usage” instructions on the +first menu.

+ +
+
+

Note: If you get stuck at a screen, press the F1 key for +online documentation relevant to that specific section.

+
+
+ +

If you've never installed FreeBSD before, or even if you have, the +“Standard” installation mode is the most recommended since it makes sure that +you'll visit all the various important checklist items along the way. If you're much more +comfortable with the FreeBSD installation process and know exactly what you want to do, use the “Express” or +“Custom” installation options. If you're upgrading an existing system, use +the “Upgrade” option.

+ +

The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS +and UFS partitions as installation media; further tips on installing from each type of +media are listed below.

+ +
+
+

1.5.1 Installing from a Network +CDROM

+ +

If you simply wish to install from a local CDROM drive then see Section 1.4. If you don't have a CDROM drive on your +system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to +which you have network connectivity, there are also several ways of going about it:

+ +
    +
  • +

    If you would be able to FTP install FreeBSD directly from the CDROM drive in some +FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add +the following line to the password file (using the +vipw(8) +command):

    + +
    +ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
    + +

    On the machine on which you are running the install, go to the Options menu and set +Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp +sites menu.

    + +
    +
    +

    Warning: This may allow anyone on the local network (or Internet) to make +“anonymous FTP” connections to this machine, which may not be desirable.

    +
    +
    +
    • + +
  • +

    If you would rather use NFS to export the CDROM directly to the machine(s) you'll be +installing from, you need to first add an entry to the /etc/exports file (on the machine with the CDROM drive). The +example below allows the machine ziggy.foo.com to mount the CDROM +directly via NFS during installation:

    + +
    +/cdrom          -ro             ziggy.foo.com
+
    + +

    The machine with the CDROM must also be configured as an NFS server, of course, and if +you're not sure how to do that then an NFS installation is probably not the best choice +for you unless you're willing to read up on +rc.conf(5) and +configure things appropriately. Assuming that this part goes smoothly, you should be able +to enter: cdrom-host:/cdrom +as the path for an NFS installation when the target machine is installed, e.g. wiggy:/cdrom.

    +
    • +
+
+ +
+
+

1.5.2 Installing from Floppies

+ +

If you must install from floppy disks, either due to unsupported hardware or just +because you enjoy doing things the hard way, you must first prepare some floppies for the +install.

+ +

First, make your boot floppies as described in Section +1.3.

+ +

Second, peruse Section 2 and pay special attention to the +“Distribution Format” section since it describes which files you're going to +need to put onto floppy and which you can safely skip.

+ +

Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files +in the bin (binary distribution) directory. If you're preparing +these floppies under DOS, then these floppies must be formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File +Manager format command.

+ +
+
+

Important: Frequently, floppy disks come “factory preformatted”. +While convenient, many problems reported by users in the past have resulted from the use +of improperly formatted media. Re-format them yourself, just to make sure.

+
+
+ +

If you're creating the floppies from another FreeBSD machine, a format is still not a +bad idea though you don't need to put a DOS filesystem on each floppy. You can use the +disklabel(8) and + +newfs(8) +commands to put a UFS filesystem on a floppy, as the following sequence of commands +illustrates:

+ +
+# fdformat -f 1440 fd0
+# disklabel -w fd0 floppy3
+# newfs -i 65536 /dev/fd0
+
+ +

After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto +them. The distribution files are sized so that a floppy disk will hold a single file. +Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +
+
+

Important: The bin.inf file also needs to go on the +first floppy of the bin set since it is read by the +installation program in order to figure out how many additional pieces to look for when +fetching and concatenating the distribution. When putting distributions onto floppies, +the distname.inf file must occupy the first floppy of each distribution set.

+
+
+ +

Once you come to the Media screen of the install, select “Floppy” and +you'll be prompted for the rest.

+
+ +
+
+

1.5.4 Installing from QIC/SCSI +Tape

+ +

When installing from tape, the installation program expects the files to be simply +tar'ed onto it, so after fetching all of the files for the distributions you're +interested in, simply use +tar(1) to get +them onto the tape with a command something like this:

+ +
+# cd /where/you/have/your/dists
+# tar cvf /dev/sa0 dist1 .. dist2
+
+ +

When you go to do the installation, you should also make sure that you leave enough +room in some temporary directory (which you'll be allowed to choose) to accommodate the +full contents of the tape you've +created. Due to the non-random access nature of tapes, this method of installation +requires quite a bit of temporary storage. You should expect to require as much temporary +storage as you have stuff written on tape.

+ +
+
+

Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. +The installation “probe” may otherwise fail to find it.

+
+
+ +

Now create a boot floppy as described in Section 1.3 and +proceed with the installation.

+
+ +
+
+

1.5.5 Installing over a Network using FTP +or NFS

+ +

After making the boot floppies as described in the first section, you can load the +rest of the installation over a network using one of 3 types of connections: serial port, +parallel port, or Ethernet.

+ +
+
+
1.5.5.1 Serial Port
+ +

SLIP support is rather primitive, and is limited primarily to hard-wired links, such +as a serial cable running between two computers. The link must be hard-wired because the +SLIP installation doesn't currently offer a dialing capability. If you need to dial out +with a modem or otherwise dialog with the link before connecting to it, then the PPP +utility should be used instead.

+ +

If you're using PPP, make sure that you have your Internet Service Provider's IP +address and DNS information handy as you'll need to know it fairly early in the +installation process. You may also need to know your own IP address, though PPP supports +dynamic address negotiation and may be able to pick up this information directly from +your ISP if they support it.

+ +

You will also need to know how to use the various “AT commands” for +dialing out with your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator.

+
+ +
+
+
1.5.5.2 Parallel Port
+ +

If a hard-wired connection to another FreeBSD or Linux machine is available, you might +also consider installing over a “laplink” style parallel port cable. The data +rate over the parallel port is much higher than what is typically possible over a serial +line (up to 50k/sec), thus resulting in a quicker installation. It's not typically +necessary to use “real” IP addresses when using a point-to-point parallel +cable in this way and you can generally just use RFC 1918 style addresses for the ends of +the link (e.g. 10.0.0.1, 10.0.0.2, +etc).

+ +
+
+

Important: If you use a Linux machine rather than a FreeBSD machine as your +PLIP peer, you will also have to specify link0 in the TCP/IP +setup screen's “extra options for ifconfig” field in order to be compatible +with Linux's slightly different PLIP protocol.

+
+
+
+ +
+
+
1.5.5.3 Ethernet
+ +

FreeBSD supports most common Ethernet cards; a table of supported cards is provided as +part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the +Documentation menu on the boot floppy or the top level directory of the CDROM). If you +are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in +before the laptop is powered on. +FreeBSD does not, unfortunately, currently support “hot insertion” of PCMCIA +cards during installation.

+ +

You will also need to know your IP address on the network, the netmask value for your subnet and the name of your machine. Your +system administrator can tell you which values are appropriate to your particular network +setup. If you will be referring to other hosts by name rather than IP address, you'll +also need a name server and possibly the address of a gateway (if you're using PPP, it's +your provider's IP address) to use in talking to it. If you want to install by FTP via an +HTTP proxy (see below), you will also need the proxy's address.

+ +

If you do not know the answers to these questions then you should really probably talk +to your system administrator first +before trying this type of installation. Using a randomly chosen IP address or netmask on +a live network is almost guaranteed not to work, and will probably result in a lecture +from said system administrator.

+ +

Once you have a network connection of some sort working, the installation can continue +over NFS or FTP.

+
+ +
+
+
1.5.5.4 NFS installation tips
+ +

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution +files you want onto a server somewhere and then point the NFS media selection at it.

+ +

If this server supports only “privileged port” access (this is generally +the default for Sun and Linux workstations), you may need to set this option in the +Options menu before installation can proceed.

+ +

If you have a poor quality Ethernet card which suffers from very slow transfer rates, +you may also wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server must also support “subdir +mounts”, e.g. if your FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr +or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled by the +-alldirs option. Other NFS servers may have different +conventions. If you are getting Permission Denied messages from +the server then it's likely that you don't have this properly enabled.

+
+ +
+
+
1.5.5.5 FTP Installation tips
+ +

FTP installation may be done from any mirror site containing a reasonably up-to-date +version of FreeBSD. A full menu of reasonable choices for almost any location in the +world is provided in the FTP site menu during installation.

+ +

If you are installing from some other FTP site not listed in this menu, or you are +having troubles getting your name server configured properly, you can also specify your +own URL by selecting the “URL” choice in that menu. A URL can contain a +hostname or an IP address, so something like the following would work in the absence of a +name server:

+ +
+ftp://216.66.64.162/pub/FreeBSD/releases/sparc64/4.2-RELEASE
+
+ +

There are three FTP installation modes you can use:

+ +
    +
  • +

    FTP: This method uses the standard “Active” mode for transfers, in which +the server initiates a connection to the client. This will not work through most +firewalls but will often work best with older FTP servers that do not support passive +mode. If your connection hangs with passive mode, try this one.

    +
    • + +
  • +

    FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening +connections to the client. This option is best for users to pass through firewalls that +do not allow incoming connections on random port addresses.

    +
    • + +
  • +

    FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy +for all FTP operations. The proxy will translate the requests and send them to the FTP +server. This allows the user to pass through firewalls that do not allow FTP at all, but +offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP +server.

    + +

    In the rare case that you have an FTP proxy that does not go through HTTP, you can +specify the URL as something like:

    + +
    +ftp://foo.bar.com:port/pub/FreeBSD
+
    + +

    In the URL above, port is the port number of the +proxy FTP server.

    +
    • +
+
+
+
+ +
+
+

1.6 Question and Answer Section for +UltraSPARC Architecture Users

+
+
+ +
+
+

2 Distribution Format

+ +

A typical FreeBSD distribution directory looks something like this (exact details may +vary depending on version, architecture, and other factors):

+ +
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    base            compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+
+ +

These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see Section 4 for how to use this).

+ +

The floppies directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.

+ +

If you're trying to do some other type of installation or are merely curious about how +a distribution is organized, what follows is a more thorough description of some of these +items in more detail:

+ +
    +
  1. +

    The *.TXT and *.HTM files contain +documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should +be read before starting an installation. The *.TXT files are +plain text, while the *.HTM files are HTML files that can be +read by almost any Web browser. Some distributions may contain documentation in other +formats as well, such as PDF or PostScript.

    +
    2. + +
  2. +

    docbook.css is a Cascading Style Sheet (CSS) file used by +some Web browsers for formatting the HTML documentation.

    +
    3. + +
  3. +

    The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the +primary distribution components of FreeBSD itself and are split into smaller files for +easy packing onto floppies (should that be necessary).

    +
    4. + +
  4. +

    The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories +contain distributions for compatibility with older releases and are distributed as single +gzip'd tar files - they can be installed during release time or later by running their +install.sh scripts.

    +
    5. + +
  5. +

    The floppies/ subdirectory contains the floppy installation +images; further information on using them can be found in Section +1.3.

    +
    6. + +
  6. +

    The packages and ports directories +contain the FreeBSD Packages and Ports Collections. Packages may be installed from the +packages directory by running the command:

    + +
    +# sysinstall configPackages
+
    + +

    Packages can also be installed by feeding individual filenames in packages/ to the +pkg_add(1) +command.

    + +

    The Ports Collection may be installed like any other distribution and requires about +190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or +locally from /usr/share/doc/handbook if you've installed the +doc distribution.

    +
    7. + +
  7. +

    Last of all, the tools directory contains various DOS tools +for discovering disk geometries, installing boot managers and the like. It is purely +optional and provided only for user convenience.

    +
    8. +
+ +

A typical distribution directory (for example, the info +distribution) looks like this internally:

+ +
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+
+ +

The CHECKSUM.MD5 file contains MD5 signatures for each file, +should data corruption be suspected, and is purely for reference. It is not used by the +actual installation and does not need to be copied with the rest of the distribution +files. The info.a* files are split, gzip'd tar files, the +contents of which can be viewed by doing:

+ +
+# cat info.a* | tar tvzf -
+
+ +

During installation, they are automatically concatenated and extracted by the +installation procedure.

+ +

The info.inf file is also necessary since it is read by the +installation program in order to figure out how many pieces to look for when fetching and +concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

+ +

The info.mtree file is another non-essential file which is +provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be +later used with the +mtree(8) program +to verify the installation permissions and checksums against any possible modifications +to the file. When used with the base distribution, this can be +an excellent way of detecting trojan horse attacks on your system.

+ +

Finally, the install.sh file is for use by those who want to +install the distribution after installation time. To install the info distribution from +CDROM after a system was installed, for example, you'd do:

+ +
+# cd /cdrom/info
+# sh install.sh
+
+
+ +
+
+

3 Upgrading FreeBSD

+ +

These instructions describe a procedure for doing a binary upgrade from an older +version of FreeBSD.

+ +
+
+

Warning: While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do +not accept the final confirmation request unless you have adequately backed up any +important data files.

+
+
+ +
+
+

Important: These notes assume that you are using the version of +sysinstall(8) +supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched +version of +sysinstall(8) is +almost guaranteed to cause problems and has been known to leave systems in an unusable +state. The most commonly made mistake in this regard is the use of an old copy of +sysinstall(8) +from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.

+
+
+ +
+
+

Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).

+ +

These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.3-STABLE snapshots.

+
+
+ +
+
+

3.1 Introduction

+ +

The upgrade procedure replaces distributions selected by the user with those +corresponding to the new FreeBSD release. It preserves standard system configuration +data, as well as user data, installed packages and other software.

+ +

Administrators contemplating an upgrade are encouraged to study this section in its +entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or +loss of data.

+ +
+
+

3.1.1 Upgrade Overview

+ +

Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.

+ +

System configuration is preserved by retaining and restoring the previous version of +the following files:

+ +

Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

+ +

The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.

+ +

During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.

+
+
+ +
+
+

3.2 Procedure

+ +

This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.

+ +
+
+

3.2.1 Backup

+ +

User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.

+
+ +
+
+

3.2.2 Mount Filesystems

+ +

The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” +for any filesystems, as this will cause data loss.

+
+ +
+
+

3.2.3 Select Distributions

+ +

When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.

+
+ +
+
+

3.2.4 After Installation

+ +

Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.

+
+
+ +
+
+

3.3 Upgrading from Source Code

+ +

Those interested in an upgrade method that allows more flexibility and sophistication +should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves +rebuilding all of FreeBSD from source code. It requires reliable network connectivity, +extra disk space, and time, but has advantages for networks and other more complex +installations. This is roughly the same procedure as is used for track the -STABLE or +-CURRENT development branches.

+ +

/usr/src/UPDATING contains important information on updating +a FreeBSD system from source code. It lists various issues resulting from changes in +FreeBSD that may affect an upgrade.

+
+
+ +
+
+

4 Troubleshooting

+ +
+

4.1 Repairing an Existing FreeBSD +Installation

+ +

FreeBSD features a “fixit” option in the top menu of the +sysinstall(8) +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.

+ +

Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main +sysinstall(8) +menu. Then select the “CDROM/DVD” option from the fixit menu.

+ +

Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the boot.flp and kernX.flp disks required for +installation, create the fixit.flp floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main +sysinstall(8) +menu. At that point, choose the “fixit” item from the main +sysinstall(8) +menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

+ +

The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.

+ +

In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM +version of fixit, these same programs can be found in /stand or +/mnt2/rescue (as well as the rest of the programs from the live +filesystem, which can be found under /mnt).

+
+ +
+
+

4.2 Common Installation Problems for +UltraSPARC Architecture Users

+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/installation.sgml b/en/releases/6.3R/installation.sgml new file mode 100644 index 0000000000..90c930e787 --- /dev/null +++ b/en/releases/6.3R/installation.sgml @@ -0,0 +1,32 @@ + + + + +]> + + &header; + +

The installation notes for FreeBSD are customized for different + platforms, as the procedures for installing FreeBSD are highly + dependent on the hardware platform.

+ +

Installation notes for FreeBSD 6.3-RELEASE are available for + the following platforms:

+ + + +

A list of all platforms currently under development can be found + on the Supported + Platforms page.

+ + &footer; + + diff --git a/en/releases/6.3R/readme.html b/en/releases/6.3R/readme.html new file mode 100644 index 0000000000..5d8dba683d --- /dev/null +++ b/en/releases/6.3R/readme.html @@ -0,0 +1,415 @@ + + + + +FreeBSD 6.3-RELEASE README + + + + + +
+
+

FreeBSD 6.3-RELEASE README

+ +

The FreeBSD Project

+ +

Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.37 +2005/04/19 09:43:53 hrs Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+ +
+
+

This document gives a brief introduction to FreeBSD 6.3-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 6.3-RELEASE, the latest point along the +6.3-STABLE branch.

+ +
+
+

1.1 About FreeBSD

+ +

FreeBSD is an operating system based on 4.4 BSD Lite for DEC/Compaq/HP Alpha/AXP +computers (alpha), 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 PowerPC® (powerpc), and MIPS® (mips) 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 17,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.

+ +

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 floppy disk images necessary to begin an installation, +as well as the distribution files needed for the install process itself. Many mirrors +also contain the ISO images necessary to create a CDROM of a FreeBSD 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 6.3-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 PostScript (.PS) or 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 6.3-RELEASE compared to the previous release (FreeBSD +6.2-RELEASE).

    +
    • + +
  • +

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

    +
    • + +
  • +

    INSTALL.TXT: Installation instructions for installing +FreeBSD from its distribution media.

    +
    • + +
  • +

    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.

    +
    • +
+ +
+
+

Note: Several of these documents (in particular, RELNOTES.TXT, HARDWARE.TXT, and INSTALL.TXT) contain information that is specific to a particular +hardware architecture. For example, the alpha release notes contain information not +applicable to the i386™, and vice versa. The +architecture for which each document applies will be listed in that document's title.

+
+
+ +
+
+

On platforms that support +sysinstall(8) +(currently alpha, 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.

+ +

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/en/releases/6.3R/relnotes-alpha.html b/en/releases/6.3R/relnotes-alpha.html new file mode 100644 index 0000000000..f74617bc96 --- /dev/null +++ b/en/releases/6.3R/relnotes-alpha.html @@ -0,0 +1,608 @@ + + + + +FreeBSD/alpha 6.3-RELEASE Release Notes + + + + + +
+
+

FreeBSD/alpha 6.3-RELEASE Release +Notes

+ +

The FreeBSD Project

+ +

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

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+

The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.3-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
+ +
2.7 Documentation
+
+
+ +
3 Upgrading from previous releases of FreeBSD
+
+
+ +
+

1 Introduction

+ +

This document contains the release notes for FreeBSD 6.3-RELEASE on the Alpha/AXP +hardware platform. 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 6.3-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 6.3-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 +6.2-RELEASE.

+ +

Typical release note items document recent security advisories issued after +6.2-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

+ +

Two remote denials of service in BIND (one involving DNSSEC and one involving +recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

+ +

Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to +0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

+ +

Problems with +libarchive(3) +and +tar(1) handling +corrupted +tar(5) archive +files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

+ +

A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has +been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

+ +

An flaw that could lead to the disclosure of previously-generated +random(4) data +has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

+ +

Information disclosure issues found in +openpty(3) and + +ptsname(3) have +been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

+ +

A programming error in +inet_network(3) +Internet address manipulation function that could lead to overwriting a region of memory +with user defined data has been corrected. Information regarding this issue can be found +in security advisory FreeBSD-SA-08:02.libc.

+
+ +
+
+

2.2 Kernel Changes

+ +

+acpi(4) now has +support for the HPET time counter.

+ +

Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts +(MSI-X) has been added to the kernel's PCI support code.

+ +
+
+

2.2.1 Boot Loader Changes

+
+ +
+
+

2.2.2 Hardware Support

+ +

An +acpi_dock(4) +driver has been added to provide support for controlling laptop docking station functions +via ACPI.

+ +
+
+
2.2.2.1 Multimedia Support
+ +

The +snd_envy24(4) +driver has been added to support the Envy24 series of audio chips.

+ +

The +snd_envy24ht(4) +driver has been added to support the VIA Envy24HT series of audio chips.

+ +

The +snd_hda(4) +driver has been added. It supports devices that conform to revision 1.0 of the Intel High +Definition Audio specification.

+ +

The +snd_spicds(4) +driver has been added to support I2S SPI audio codec chips.

+
+ +
+
+
2.2.2.2 Network Interface Support
+ +

The +ath(4) driver +has been updated to HAL version 0.9.20.3.

+ +

The +axe(4) driver +now supports +altq(4).

+ +

The +cxgb(4) driver +has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio +T3 and T3B chipsets.

+ +

The +edsc(4) driver, +which provides Ethernet discard network interfaces, has been added.

+ +

The em(4) driver has been +updated to version 6.7.2 from Intel.

+ +

The +msk(4) driver +has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II +Gigabit Ethernet controller.

+ +

The +vge(4) driver +now supports +altq(4).

+ +

The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and +half-channel support for 802.11a.

+
+
+ +
+
+

2.2.3 Network Protocols

+ +

The +if_bridge(4) +driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

+ +

The +lagg(4) driver, +ported from OpenBSD and NetBSD, has been added to support a variety of protocols and +algorithms for link aggregation, failover, and fault tolerance.

+ +

A new +ng_deflate(4) +NetGraph node type has been added. It implements Deflate PPP compression.

+ +

The +ng_ppp(4) +Netgraph node is now MPSAFE.

+ +

A new +ng_pred1(4) +NetGraph node type has been added to implement Predictor-1 PPP compression.

+ +

A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over +gif(4) tunnels +has been fixed.

+ +

The net.link.tap.up_on_open sysctl variable has been +added to the +tap(4) driver. +If enabled, new tap devices will marked up upon creation.

+
+ +
+
+

2.2.4 Disks and Storage

+ +

The +mpt(4) driver +has been updated to support various new features such as RAID volume and RAID member +state/settings reporting, periodic volume re-synchronization status reporting, and sysctl +variables for volume re-synchronization rate, volume member write cache status, and +volume transaction queue depth.

+ +

The +mpt(4) driver +now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

+ +

The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG +passthrough device API, has been added. It is intended to allow programs running under +Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by +Linux.

+ +

The +twa(4) driver +has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's +3ware 9650 series of SATA controllers.

+
+ +
+
+

2.2.5 File Systems

+ +

The unionfs file system has been re-implemented. This version solves many crashing and +locking issues compared to the previous implementation. It also adds new +“transparent” and “masquerade” modes for automatically creating +files in the upper file system layer of unions. More information can be found in the +mount_unionfs(8) +manual page.

+
+
+ +
+
+

2.3 Userland Changes

+ +

The +camcontrol(8) +utility now supports a readcap command to display the size of +devices.

+ +

A bug in +freebsd-update(8), which caused it not to update +SMP kernels correctly, has been fixed.

+ +

The +fdisk(8) program +now supports a -p flag to print the slice table in fdisk +configuration format.

+ +

The +freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different +versions of FreeBSD.

+ +

The +ftpd(8) utility +now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The +RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the +ftpd(8) manual +page.

+ +

The +ipfwpcap(8) +utility has been added; it captures packets on a +divert(4) socket +and writes them as +pcap(3) (also +known as +tcpdump(1)) +format data to a file or pipe.

+ +

The +rpc.lockd(8) and + +rpc.statd(8) +programs now accept -p options to indicate which port they +should bind to.

+ +

The pw(8) program now +supports a -M option to set the permissions of a user's newly +created home directory.

+ +

The +top(1) program +now supports a -j flag to display the +jail(8) ID for +each process.

+ +

The +touch(1) utility +now supports a -A flag that allows the access and +modification times of a file be adjusted by a specified value.

+ +

The +wpa_passphrase(8) utility has been added. It +generates a 256-bit pre-shared WPA key from an ASCII passphrase.

+ +
+
+

2.3.1 /etc/rc.d Scripts

+ +

The sendmail script can be instructed not to rebuild the +aliases database if it is missing or older than the aliases file. If desired, set the new +rc.conf option sendmail_rebuild_aliases to "NO" to turn off +that functionality.

+ +

The /etc/rc.d/nfslocking script has been deprecated and will +be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd +scripts.

+
+
+ +
+
+

2.4 Contributed Software

+ +

awk has been updated from the 24 April 2005 release to the +1 May 2007 release.

+ +

BIND has been updated from 9.3.3 to 9.3.4-p1.

+ +

BZIP2 has been updated from 1.0.3 to 1.0.4.

+ +

GNU Diffutils has been updated from 2.7 to 2.8.7.

+ +

The GNU version of gzip has been replaced with a modified +version of gzip ported from NetBSD.

+ +

IPFilter has been updated from 4.1.13 to 4.1.28.

+ +

less has been updated from v381 to v416.

+ +

ncurses has been updated from 5.2-20020615 to 5.6-20061217. +ncurses now also has wide character support.

+ +

netcat has been updated from the version in a 4 February +2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

+ +

GNU Readline library has been updated from 5.0 to 5.2 patch +2.

+ +

sendmail has been updated from 8.13.8 to 8.14.2.

+ +

The timezone database has been updated from the tzdata2006g +release to the tzdata2007k release.

+ +

TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to +1.0.

+
+ +
+
+

2.5 Ports/Packages Collection +Infrastructure

+
+ +
+
+

2.6 Release Engineering and +Integration

+ +

The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

+ +

The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

+ +

The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

+ +

The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default +value of LOCALBASE.

+
+ +
+
+

2.7 Documentation

+
+
+ +
+
+

3 Upgrading from previous releases of +FreeBSD

+ +

Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

+ +
+
+

Important: Upgrading FreeBSD should, of course, only be attempted after backing +up all data and configuration +files.

+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/relnotes-amd64.html b/en/releases/6.3R/relnotes-amd64.html new file mode 100644 index 0000000000..ade208e277 --- /dev/null +++ b/en/releases/6.3R/relnotes-amd64.html @@ -0,0 +1,623 @@ + + + + +FreeBSD/amd64 6.3-RELEASE Release Notes + + + + + +
+
+

FreeBSD/amd64 6.3-RELEASE Release +Notes

+ +

The FreeBSD Project

+ +

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

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+

The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.3-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
+ +
2.7 Documentation
+
+
+ +
3 Upgrading from previous releases of FreeBSD
+
+
+ +
+

1 Introduction

+ +

This document contains the release notes for FreeBSD 6.3-RELEASE on the AMD64 hardware +platform. 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 6.3-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 6.3-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 +6.2-RELEASE.

+ +

Typical release note items document recent security advisories issued after +6.2-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

+ +

Two remote denials of service in BIND (one involving DNSSEC and one involving +recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

+ +

Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to +0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

+ +

Problems with +libarchive(3) +and +tar(1) handling +corrupted +tar(5) archive +files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

+ +

A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has +been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

+ +

An flaw that could lead to the disclosure of previously-generated +random(4) data +has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

+ +

Information disclosure issues found in +openpty(3) and + +ptsname(3) have +been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

+ +

A programming error in +inet_network(3) +Internet address manipulation function that could lead to overwriting a region of memory +with user defined data has been corrected. Information regarding this issue can be found +in security advisory FreeBSD-SA-08:02.libc.

+
+ +
+
+

2.2 Kernel Changes

+ +

+acpi(4) now has +support for the HPET time counter.

+ +

Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts +(MSI-X) has been added to the kernel's PCI support code.

+ +
+
+

2.2.1 Boot Loader Changes

+
+ +
+
+

2.2.2 Hardware Support

+ +

An +acpi_dock(4) +driver has been added to provide support for controlling laptop docking station functions +via ACPI.

+ +

The +coretemp(4) +driver has been added to provide temperature readings on Intel® Core™ +processors.

+ +
+
+
2.2.2.1 Multimedia Support
+ +

The +snd_envy24(4) +driver has been added to support the Envy24 series of audio chips.

+ +

The +snd_envy24ht(4) +driver has been added to support the VIA Envy24HT series of audio chips.

+ +

The +snd_hda(4) +driver has been added. It supports devices that conform to revision 1.0 of the Intel High +Definition Audio specification.

+ +

The +snd_spicds(4) +driver has been added to support I2S SPI audio codec chips.

+
+ +
+
+
2.2.2.2 Network Interface Support
+ +

The +ath(4) driver +has been updated to HAL version 0.9.20.3.

+ +

The +axe(4) driver +now supports +altq(4).

+ +

The +cxgb(4) driver +has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio +T3 and T3B chipsets.

+ +

The +edsc(4) driver, +which provides Ethernet discard network interfaces, has been added.

+ +

The em(4) driver has been +updated to version 6.7.2 from Intel.

+ +

The +msk(4) driver +has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II +Gigabit Ethernet controller.

+ +

The +mxge(4) driver, +which supports Myricom Myri10GE 10 Gigabit Ethernet adapters, has been added. For more +details, see +mxge(4).

+ +

The +vge(4) driver +now supports +altq(4).

+ +

The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and +half-channel support for 802.11a.

+
+
+ +
+
+

2.2.3 Network Protocols

+ +

The +if_bridge(4) +driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

+ +

The +lagg(4) driver, +ported from OpenBSD and NetBSD, has been added to support a variety of protocols and +algorithms for link aggregation, failover, and fault tolerance.

+ +

A new +ng_deflate(4) +NetGraph node type has been added. It implements Deflate PPP compression.

+ +

The +ng_ppp(4) +Netgraph node is now MPSAFE.

+ +

A new +ng_pred1(4) +NetGraph node type has been added to implement Predictor-1 PPP compression.

+ +

A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over +gif(4) tunnels +has been fixed.

+ +

The net.link.tap.up_on_open sysctl variable has been +added to the +tap(4) driver. +If enabled, new tap devices will marked up upon creation.

+
+ +
+
+

2.2.4 Disks and Storage

+ +

The +mpt(4) driver +has been updated to support various new features such as RAID volume and RAID member +state/settings reporting, periodic volume re-synchronization status reporting, and sysctl +variables for volume re-synchronization rate, volume member write cache status, and +volume transaction queue depth.

+ +

The +mpt(4) driver +now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

+ +

The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG +passthrough device API, has been added. It is intended to allow programs running under +Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by +Linux.

+ +

The +twa(4) driver +has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's +3ware 9650 series of SATA controllers.

+
+ +
+
+

2.2.5 File Systems

+ +

The unionfs file system has been re-implemented. This version solves many crashing and +locking issues compared to the previous implementation. It also adds new +“transparent” and “masquerade” modes for automatically creating +files in the upper file system layer of unions. More information can be found in the +mount_unionfs(8) +manual page.

+
+
+ +
+
+

2.3 Userland Changes

+ +

The +camcontrol(8) +utility now supports a readcap command to display the size of +devices.

+ +

A bug in +freebsd-update(8), which caused it not to update +SMP kernels correctly, has been fixed.

+ +

The +fdisk(8) program +now supports a -p flag to print the slice table in fdisk +configuration format.

+ +

The +freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different +versions of FreeBSD.

+ +

The +ftpd(8) utility +now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The +RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the +ftpd(8) manual +page.

+ +

The +ipfwpcap(8) +utility has been added; it captures packets on a +divert(4) socket +and writes them as +pcap(3) (also +known as +tcpdump(1)) +format data to a file or pipe.

+ +

The +rpc.lockd(8) and + +rpc.statd(8) +programs now accept -p options to indicate which port they +should bind to.

+ +

The pw(8) program now +supports a -M option to set the permissions of a user's newly +created home directory.

+ +

The +top(1) program +now supports a -j flag to display the +jail(8) ID for +each process.

+ +

The +touch(1) utility +now supports a -A flag that allows the access and +modification times of a file be adjusted by a specified value.

+ +

The +wpa_passphrase(8) utility has been added. It +generates a 256-bit pre-shared WPA key from an ASCII passphrase.

+ +
+
+

2.3.1 /etc/rc.d Scripts

+ +

The sendmail script can be instructed not to rebuild the +aliases database if it is missing or older than the aliases file. If desired, set the new +rc.conf option sendmail_rebuild_aliases to "NO" to turn off +that functionality.

+ +

The /etc/rc.d/nfslocking script has been deprecated and will +be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd +scripts.

+
+
+ +
+
+

2.4 Contributed Software

+ +

awk has been updated from the 24 April 2005 release to the +1 May 2007 release.

+ +

BIND has been updated from 9.3.3 to 9.3.4-p1.

+ +

BZIP2 has been updated from 1.0.3 to 1.0.4.

+ +

GNU Diffutils has been updated from 2.7 to 2.8.7.

+ +

The GNU version of gzip has been replaced with a modified +version of gzip ported from NetBSD.

+ +

IPFilter has been updated from 4.1.13 to 4.1.28.

+ +

less has been updated from v381 to v416.

+ +

ncurses has been updated from 5.2-20020615 to 5.6-20061217. +ncurses now also has wide character support.

+ +

netcat has been updated from the version in a 4 February +2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

+ +

GNU Readline library has been updated from 5.0 to 5.2 patch +2.

+ +

sendmail has been updated from 8.13.8 to 8.14.2.

+ +

The timezone database has been updated from the tzdata2006g +release to the tzdata2007k release.

+ +

TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to +1.0.

+
+ +
+
+

2.5 Ports/Packages Collection +Infrastructure

+
+ +
+
+

2.6 Release Engineering and +Integration

+ +

The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

+ +

The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

+ +

The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

+ +

The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default +value of LOCALBASE.

+
+ +
+
+

2.7 Documentation

+
+
+ +
+
+

3 Upgrading from previous releases of +FreeBSD

+ +

Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

+ +
+
+

Important: Upgrading FreeBSD should, of course, only be attempted after backing +up all data and configuration +files.

+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/relnotes-i386.html b/en/releases/6.3R/relnotes-i386.html new file mode 100644 index 0000000000..b2252e0ab7 --- /dev/null +++ b/en/releases/6.3R/relnotes-i386.html @@ -0,0 +1,622 @@ + + + + +FreeBSD/i386 6.3-RELEASE Release Notes + + + + + +
+
+

FreeBSD/i386 6.3-RELEASE Release +Notes

+ +

The FreeBSD Project

+ +

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

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+

The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.3-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
+ +
2.7 Documentation
+
+
+ +
3 Upgrading from previous releases of FreeBSD
+
+
+ +
+

1 Introduction

+ +

This document contains the release notes for FreeBSD 6.3-RELEASE on the i386 hardware +platform. 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 6.3-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 6.3-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 +6.2-RELEASE.

+ +

Typical release note items document recent security advisories issued after +6.2-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

+ +

Two remote denials of service in BIND (one involving DNSSEC and one involving +recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

+ +

Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to +0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

+ +

Problems with +libarchive(3) +and +tar(1) handling +corrupted +tar(5) archive +files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

+ +

A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has +been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

+ +

An flaw that could lead to the disclosure of previously-generated +random(4) data +has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

+ +

Information disclosure issues found in +openpty(3) and + +ptsname(3) have +been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

+ +

A programming error in +inet_network(3) +Internet address manipulation function that could lead to overwriting a region of memory +with user defined data has been corrected. Information regarding this issue can be found +in security advisory FreeBSD-SA-08:02.libc.

+
+ +
+
+

2.2 Kernel Changes

+ +

+acpi(4) now has +support for the HPET time counter.

+ +

Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts +(MSI-X) has been added to the kernel's PCI support code.

+ +
+
+

2.2.1 Boot Loader Changes

+
+ +
+
+

2.2.2 Hardware Support

+ +

An +acpi_dock(4) +driver has been added to provide support for controlling laptop docking station functions +via ACPI.

+ +

The +coretemp(4) +driver has been added to provide temperature readings on Intel® Core™ +processors.

+ +
+
+
2.2.2.1 Multimedia Support
+ +

The +snd_envy24(4) +driver has been added to support the Envy24 series of audio chips.

+ +

The +snd_envy24ht(4) +driver has been added to support the VIA Envy24HT series of audio chips.

+ +

The +snd_hda(4) +driver has been added. It supports devices that conform to revision 1.0 of the Intel High +Definition Audio specification.

+ +

The +snd_spicds(4) +driver has been added to support I2S SPI audio codec chips.

+
+ +
+
+
2.2.2.2 Network Interface Support
+ +

The +ath(4) driver +has been updated to HAL version 0.9.20.3.

+ +

The +axe(4) driver +now supports +altq(4).

+ +

The +cxgb(4) driver +has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio +T3 and T3B chipsets.

+ +

The +edsc(4) driver, +which provides Ethernet discard network interfaces, has been added.

+ +

The em(4) driver has been +updated to version 6.7.2 from Intel.

+ +

The +msk(4) driver +has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II +Gigabit Ethernet controller.

+ +

The +mxge(4) driver, +which supports Myricom Myri10GE 10 Gigabit Ethernet adapters, has been added. For more +details, see +mxge(4).

+ +

The +vge(4) driver +now supports +altq(4).

+ +

The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and +half-channel support for 802.11a.

+
+
+ +
+
+

2.2.3 Network Protocols

+ +

The +if_bridge(4) +driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

+ +

The +lagg(4) driver, +ported from OpenBSD and NetBSD, has been added to support a variety of protocols and +algorithms for link aggregation, failover, and fault tolerance.

+ +

A new +ng_deflate(4) +NetGraph node type has been added. It implements Deflate PPP compression.

+ +

The +ng_ppp(4) +Netgraph node is now MPSAFE.

+ +

A new +ng_pred1(4) +NetGraph node type has been added to implement Predictor-1 PPP compression.

+ +

A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over +gif(4) tunnels +has been fixed.

+ +

The net.link.tap.up_on_open sysctl variable has been +added to the +tap(4) driver. +If enabled, new tap devices will marked up upon creation.

+
+ +
+
+

2.2.4 Disks and Storage

+ +

The +mpt(4) driver +has been updated to support various new features such as RAID volume and RAID member +state/settings reporting, periodic volume re-synchronization status reporting, and sysctl +variables for volume re-synchronization rate, volume member write cache status, and +volume transaction queue depth.

+ +

The +mpt(4) driver +now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

+ +

The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG +passthrough device API, has been added. It is intended to allow programs running under +Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by +Linux.

+ +

The +twa(4) driver +has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's +3ware 9650 series of SATA controllers.

+
+ +
+
+

2.2.5 File Systems

+ +

The unionfs file system has been re-implemented. This version solves many crashing and +locking issues compared to the previous implementation. It also adds new +“transparent” and “masquerade” modes for automatically creating +files in the upper file system layer of unions. More information can be found in the +mount_unionfs(8) +manual page.

+
+
+ +
+
+

2.3 Userland Changes

+ +

The +camcontrol(8) +utility now supports a readcap command to display the size of +devices.

+ +

A bug in +freebsd-update(8), which caused it not to update +SMP kernels correctly, has been fixed.

+ +

The +fdisk(8) program +now supports a -p flag to print the slice table in fdisk +configuration format.

+ +

The +freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different +versions of FreeBSD.

+ +

The +ftpd(8) utility +now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The +RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the +ftpd(8) manual +page.

+ +

The +ipfwpcap(8) +utility has been added; it captures packets on a +divert(4) socket +and writes them as +pcap(3) (also +known as +tcpdump(1)) +format data to a file or pipe.

+ +

The +rpc.lockd(8) and + +rpc.statd(8) +programs now accept -p options to indicate which port they +should bind to.

+ +

The pw(8) program now +supports a -M option to set the permissions of a user's newly +created home directory.

+ +

The +top(1) program +now supports a -j flag to display the +jail(8) ID for +each process.

+ +

The +touch(1) utility +now supports a -A flag that allows the access and +modification times of a file be adjusted by a specified value.

+ +

The +wpa_passphrase(8) utility has been added. It +generates a 256-bit pre-shared WPA key from an ASCII passphrase.

+ +
+
+

2.3.1 /etc/rc.d Scripts

+ +

The sendmail script can be instructed not to rebuild the +aliases database if it is missing or older than the aliases file. If desired, set the new +rc.conf option sendmail_rebuild_aliases to "NO" to turn off +that functionality.

+ +

The /etc/rc.d/nfslocking script has been deprecated and will +be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd +scripts.

+
+
+ +
+
+

2.4 Contributed Software

+ +

awk has been updated from the 24 April 2005 release to the +1 May 2007 release.

+ +

BIND has been updated from 9.3.3 to 9.3.4-p1.

+ +

BZIP2 has been updated from 1.0.3 to 1.0.4.

+ +

GNU Diffutils has been updated from 2.7 to 2.8.7.

+ +

The GNU version of gzip has been replaced with a modified +version of gzip ported from NetBSD.

+ +

IPFilter has been updated from 4.1.13 to 4.1.28.

+ +

less has been updated from v381 to v416.

+ +

ncurses has been updated from 5.2-20020615 to 5.6-20061217. +ncurses now also has wide character support.

+ +

netcat has been updated from the version in a 4 February +2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

+ +

GNU Readline library has been updated from 5.0 to 5.2 patch +2.

+ +

sendmail has been updated from 8.13.8 to 8.14.2.

+ +

The timezone database has been updated from the tzdata2006g +release to the tzdata2007k release.

+ +

TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to +1.0.

+
+ +
+
+

2.5 Ports/Packages Collection +Infrastructure

+
+ +
+
+

2.6 Release Engineering and +Integration

+ +

The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

+ +

The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

+ +

The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

+ +

The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default +value of LOCALBASE.

+
+ +
+
+

2.7 Documentation

+
+
+ +
+
+

3 Upgrading from previous releases of +FreeBSD

+ +

Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

+ +
+
+

Important: Upgrading FreeBSD should, of course, only be attempted after backing +up all data and configuration +files.

+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/relnotes-ia64.html b/en/releases/6.3R/relnotes-ia64.html new file mode 100644 index 0000000000..4fd4e51a04 --- /dev/null +++ b/en/releases/6.3R/relnotes-ia64.html @@ -0,0 +1,608 @@ + + + + +FreeBSD/ia64 6.3-RELEASE Release Notes + + + + + +
+
+

FreeBSD/ia64 6.3-RELEASE Release +Notes

+ +

The FreeBSD Project

+ +

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

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+

The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.3-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
+ +
2.7 Documentation
+
+
+ +
3 Upgrading from previous releases of FreeBSD
+
+
+ +
+

1 Introduction

+ +

This document contains the release notes for FreeBSD 6.3-RELEASE on the IA-64 hardware +platform. 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 6.3-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 6.3-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 +6.2-RELEASE.

+ +

Typical release note items document recent security advisories issued after +6.2-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

+ +

Two remote denials of service in BIND (one involving DNSSEC and one involving +recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

+ +

Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to +0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

+ +

Problems with +libarchive(3) +and +tar(1) handling +corrupted +tar(5) archive +files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

+ +

A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has +been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

+ +

An flaw that could lead to the disclosure of previously-generated +random(4) data +has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

+ +

Information disclosure issues found in +openpty(3) and + +ptsname(3) have +been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

+ +

A programming error in +inet_network(3) +Internet address manipulation function that could lead to overwriting a region of memory +with user defined data has been corrected. Information regarding this issue can be found +in security advisory FreeBSD-SA-08:02.libc.

+
+ +
+
+

2.2 Kernel Changes

+ +

+acpi(4) now has +support for the HPET time counter.

+ +

Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts +(MSI-X) has been added to the kernel's PCI support code.

+ +
+
+

2.2.1 Boot Loader Changes

+
+ +
+
+

2.2.2 Hardware Support

+ +

An +acpi_dock(4) +driver has been added to provide support for controlling laptop docking station functions +via ACPI.

+ +
+
+
2.2.2.1 Multimedia Support
+ +

The +snd_envy24(4) +driver has been added to support the Envy24 series of audio chips.

+ +

The +snd_envy24ht(4) +driver has been added to support the VIA Envy24HT series of audio chips.

+ +

The +snd_hda(4) +driver has been added. It supports devices that conform to revision 1.0 of the Intel High +Definition Audio specification.

+ +

The +snd_spicds(4) +driver has been added to support I2S SPI audio codec chips.

+
+ +
+
+
2.2.2.2 Network Interface Support
+ +

The +ath(4) driver +has been updated to HAL version 0.9.20.3.

+ +

The +axe(4) driver +now supports +altq(4).

+ +

The +cxgb(4) driver +has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio +T3 and T3B chipsets.

+ +

The +edsc(4) driver, +which provides Ethernet discard network interfaces, has been added.

+ +

The em(4) driver has been +updated to version 6.7.2 from Intel.

+ +

The +msk(4) driver +has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II +Gigabit Ethernet controller.

+ +

The +vge(4) driver +now supports +altq(4).

+ +

The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and +half-channel support for 802.11a.

+
+
+ +
+
+

2.2.3 Network Protocols

+ +

The +if_bridge(4) +driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

+ +

The +lagg(4) driver, +ported from OpenBSD and NetBSD, has been added to support a variety of protocols and +algorithms for link aggregation, failover, and fault tolerance.

+ +

A new +ng_deflate(4) +NetGraph node type has been added. It implements Deflate PPP compression.

+ +

The +ng_ppp(4) +Netgraph node is now MPSAFE.

+ +

A new +ng_pred1(4) +NetGraph node type has been added to implement Predictor-1 PPP compression.

+ +

A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over +gif(4) tunnels +has been fixed.

+ +

The net.link.tap.up_on_open sysctl variable has been +added to the +tap(4) driver. +If enabled, new tap devices will marked up upon creation.

+
+ +
+
+

2.2.4 Disks and Storage

+ +

The +mpt(4) driver +has been updated to support various new features such as RAID volume and RAID member +state/settings reporting, periodic volume re-synchronization status reporting, and sysctl +variables for volume re-synchronization rate, volume member write cache status, and +volume transaction queue depth.

+ +

The +mpt(4) driver +now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

+ +

The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG +passthrough device API, has been added. It is intended to allow programs running under +Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by +Linux.

+ +

The +twa(4) driver +has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's +3ware 9650 series of SATA controllers.

+
+ +
+
+

2.2.5 File Systems

+ +

The unionfs file system has been re-implemented. This version solves many crashing and +locking issues compared to the previous implementation. It also adds new +“transparent” and “masquerade” modes for automatically creating +files in the upper file system layer of unions. More information can be found in the +mount_unionfs(8) +manual page.

+
+
+ +
+
+

2.3 Userland Changes

+ +

The +camcontrol(8) +utility now supports a readcap command to display the size of +devices.

+ +

A bug in +freebsd-update(8), which caused it not to update +SMP kernels correctly, has been fixed.

+ +

The +fdisk(8) program +now supports a -p flag to print the slice table in fdisk +configuration format.

+ +

The +freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different +versions of FreeBSD.

+ +

The +ftpd(8) utility +now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The +RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the +ftpd(8) manual +page.

+ +

The +ipfwpcap(8) +utility has been added; it captures packets on a +divert(4) socket +and writes them as +pcap(3) (also +known as +tcpdump(1)) +format data to a file or pipe.

+ +

The +rpc.lockd(8) and + +rpc.statd(8) +programs now accept -p options to indicate which port they +should bind to.

+ +

The pw(8) program now +supports a -M option to set the permissions of a user's newly +created home directory.

+ +

The +top(1) program +now supports a -j flag to display the +jail(8) ID for +each process.

+ +

The +touch(1) utility +now supports a -A flag that allows the access and +modification times of a file be adjusted by a specified value.

+ +

The +wpa_passphrase(8) utility has been added. It +generates a 256-bit pre-shared WPA key from an ASCII passphrase.

+ +
+
+

2.3.1 /etc/rc.d Scripts

+ +

The sendmail script can be instructed not to rebuild the +aliases database if it is missing or older than the aliases file. If desired, set the new +rc.conf option sendmail_rebuild_aliases to "NO" to turn off +that functionality.

+ +

The /etc/rc.d/nfslocking script has been deprecated and will +be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd +scripts.

+
+
+ +
+
+

2.4 Contributed Software

+ +

awk has been updated from the 24 April 2005 release to the +1 May 2007 release.

+ +

BIND has been updated from 9.3.3 to 9.3.4-p1.

+ +

BZIP2 has been updated from 1.0.3 to 1.0.4.

+ +

GNU Diffutils has been updated from 2.7 to 2.8.7.

+ +

The GNU version of gzip has been replaced with a modified +version of gzip ported from NetBSD.

+ +

IPFilter has been updated from 4.1.13 to 4.1.28.

+ +

less has been updated from v381 to v416.

+ +

ncurses has been updated from 5.2-20020615 to 5.6-20061217. +ncurses now also has wide character support.

+ +

netcat has been updated from the version in a 4 February +2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

+ +

GNU Readline library has been updated from 5.0 to 5.2 patch +2.

+ +

sendmail has been updated from 8.13.8 to 8.14.2.

+ +

The timezone database has been updated from the tzdata2006g +release to the tzdata2007k release.

+ +

TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to +1.0.

+
+ +
+
+

2.5 Ports/Packages Collection +Infrastructure

+
+ +
+
+

2.6 Release Engineering and +Integration

+ +

The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

+ +

The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

+ +

The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

+ +

The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default +value of LOCALBASE.

+
+ +
+
+

2.7 Documentation

+
+
+ +
+
+

3 Upgrading from previous releases of +FreeBSD

+ +

Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

+ +
+
+

Important: Upgrading FreeBSD should, of course, only be attempted after backing +up all data and configuration +files.

+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/relnotes-pc98.html b/en/releases/6.3R/relnotes-pc98.html new file mode 100644 index 0000000000..3011915342 --- /dev/null +++ b/en/releases/6.3R/relnotes-pc98.html @@ -0,0 +1,608 @@ + + + + +FreeBSD/pc98 6.3-RELEASE Release Notes + + + + + +
+
+

FreeBSD/pc98 6.3-RELEASE Release +Notes

+ +

The FreeBSD Project

+ +

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

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+

The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.3-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
+ +
2.7 Documentation
+
+
+ +
3 Upgrading from previous releases of FreeBSD
+
+
+ +
+

1 Introduction

+ +

This document contains the release notes for FreeBSD 6.3-RELEASE on the NEC PC-98x1 +hardware platform. 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 6.3-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 6.3-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 +6.2-RELEASE.

+ +

Typical release note items document recent security advisories issued after +6.2-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

+ +

Two remote denials of service in BIND (one involving DNSSEC and one involving +recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

+ +

Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to +0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

+ +

Problems with +libarchive(3) +and +tar(1) handling +corrupted +tar(5) archive +files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

+ +

A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has +been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

+ +

An flaw that could lead to the disclosure of previously-generated +random(4) data +has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

+ +

Information disclosure issues found in +openpty(3) and + +ptsname(3) have +been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

+ +

A programming error in +inet_network(3) +Internet address manipulation function that could lead to overwriting a region of memory +with user defined data has been corrected. Information regarding this issue can be found +in security advisory FreeBSD-SA-08:02.libc.

+
+ +
+
+

2.2 Kernel Changes

+ +

+acpi(4) now has +support for the HPET time counter.

+ +

Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts +(MSI-X) has been added to the kernel's PCI support code.

+ +
+
+

2.2.1 Boot Loader Changes

+
+ +
+
+

2.2.2 Hardware Support

+ +

An +acpi_dock(4) +driver has been added to provide support for controlling laptop docking station functions +via ACPI.

+ +
+
+
2.2.2.1 Multimedia Support
+ +

The +snd_envy24(4) +driver has been added to support the Envy24 series of audio chips.

+ +

The +snd_envy24ht(4) +driver has been added to support the VIA Envy24HT series of audio chips.

+ +

The +snd_hda(4) +driver has been added. It supports devices that conform to revision 1.0 of the Intel High +Definition Audio specification.

+ +

The +snd_spicds(4) +driver has been added to support I2S SPI audio codec chips.

+
+ +
+
+
2.2.2.2 Network Interface Support
+ +

The +ath(4) driver +has been updated to HAL version 0.9.20.3.

+ +

The +axe(4) driver +now supports +altq(4).

+ +

The +cxgb(4) driver +has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio +T3 and T3B chipsets.

+ +

The +edsc(4) driver, +which provides Ethernet discard network interfaces, has been added.

+ +

The em(4) driver has been +updated to version 6.7.2 from Intel.

+ +

The +msk(4) driver +has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II +Gigabit Ethernet controller.

+ +

The +vge(4) driver +now supports +altq(4).

+ +

The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and +half-channel support for 802.11a.

+
+
+ +
+
+

2.2.3 Network Protocols

+ +

The +if_bridge(4) +driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

+ +

The +lagg(4) driver, +ported from OpenBSD and NetBSD, has been added to support a variety of protocols and +algorithms for link aggregation, failover, and fault tolerance.

+ +

A new +ng_deflate(4) +NetGraph node type has been added. It implements Deflate PPP compression.

+ +

The +ng_ppp(4) +Netgraph node is now MPSAFE.

+ +

A new +ng_pred1(4) +NetGraph node type has been added to implement Predictor-1 PPP compression.

+ +

A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over +gif(4) tunnels +has been fixed.

+ +

The net.link.tap.up_on_open sysctl variable has been +added to the +tap(4) driver. +If enabled, new tap devices will marked up upon creation.

+
+ +
+
+

2.2.4 Disks and Storage

+ +

The +mpt(4) driver +has been updated to support various new features such as RAID volume and RAID member +state/settings reporting, periodic volume re-synchronization status reporting, and sysctl +variables for volume re-synchronization rate, volume member write cache status, and +volume transaction queue depth.

+ +

The +mpt(4) driver +now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

+ +

The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG +passthrough device API, has been added. It is intended to allow programs running under +Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by +Linux.

+ +

The +twa(4) driver +has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's +3ware 9650 series of SATA controllers.

+
+ +
+
+

2.2.5 File Systems

+ +

The unionfs file system has been re-implemented. This version solves many crashing and +locking issues compared to the previous implementation. It also adds new +“transparent” and “masquerade” modes for automatically creating +files in the upper file system layer of unions. More information can be found in the +mount_unionfs(8) +manual page.

+
+
+ +
+
+

2.3 Userland Changes

+ +

The +camcontrol(8) +utility now supports a readcap command to display the size of +devices.

+ +

A bug in +freebsd-update(8), which caused it not to update +SMP kernels correctly, has been fixed.

+ +

The +fdisk(8) program +now supports a -p flag to print the slice table in fdisk +configuration format.

+ +

The +freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different +versions of FreeBSD.

+ +

The +ftpd(8) utility +now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The +RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the +ftpd(8) manual +page.

+ +

The +ipfwpcap(8) +utility has been added; it captures packets on a +divert(4) socket +and writes them as +pcap(3) (also +known as +tcpdump(1)) +format data to a file or pipe.

+ +

The +rpc.lockd(8) and + +rpc.statd(8) +programs now accept -p options to indicate which port they +should bind to.

+ +

The pw(8) program now +supports a -M option to set the permissions of a user's newly +created home directory.

+ +

The +top(1) program +now supports a -j flag to display the +jail(8) ID for +each process.

+ +

The +touch(1) utility +now supports a -A flag that allows the access and +modification times of a file be adjusted by a specified value.

+ +

The +wpa_passphrase(8) utility has been added. It +generates a 256-bit pre-shared WPA key from an ASCII passphrase.

+ +
+
+

2.3.1 /etc/rc.d Scripts

+ +

The sendmail script can be instructed not to rebuild the +aliases database if it is missing or older than the aliases file. If desired, set the new +rc.conf option sendmail_rebuild_aliases to "NO" to turn off +that functionality.

+ +

The /etc/rc.d/nfslocking script has been deprecated and will +be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd +scripts.

+
+
+ +
+
+

2.4 Contributed Software

+ +

awk has been updated from the 24 April 2005 release to the +1 May 2007 release.

+ +

BIND has been updated from 9.3.3 to 9.3.4-p1.

+ +

BZIP2 has been updated from 1.0.3 to 1.0.4.

+ +

GNU Diffutils has been updated from 2.7 to 2.8.7.

+ +

The GNU version of gzip has been replaced with a modified +version of gzip ported from NetBSD.

+ +

IPFilter has been updated from 4.1.13 to 4.1.28.

+ +

less has been updated from v381 to v416.

+ +

ncurses has been updated from 5.2-20020615 to 5.6-20061217. +ncurses now also has wide character support.

+ +

netcat has been updated from the version in a 4 February +2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

+ +

GNU Readline library has been updated from 5.0 to 5.2 patch +2.

+ +

sendmail has been updated from 8.13.8 to 8.14.2.

+ +

The timezone database has been updated from the tzdata2006g +release to the tzdata2007k release.

+ +

TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to +1.0.

+
+ +
+
+

2.5 Ports/Packages Collection +Infrastructure

+
+ +
+
+

2.6 Release Engineering and +Integration

+ +

The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

+ +

The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

+ +

The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

+ +

The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default +value of LOCALBASE.

+
+ +
+
+

2.7 Documentation

+
+
+ +
+
+

3 Upgrading from previous releases of +FreeBSD

+ +

Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

+ +
+
+

Important: Upgrading FreeBSD should, of course, only be attempted after backing +up all data and configuration +files.

+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/relnotes-sparc64.html b/en/releases/6.3R/relnotes-sparc64.html new file mode 100644 index 0000000000..cab834d675 --- /dev/null +++ b/en/releases/6.3R/relnotes-sparc64.html @@ -0,0 +1,608 @@ + + + + +FreeBSD/sparc64 6.3-RELEASE Release Notes + + + + + +
+
+

FreeBSD/sparc64 6.3-RELEASE Release +Notes

+ +

The FreeBSD Project

+ +

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

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
+

+ +
+

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+
+ +
+
+

The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.3-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
+ +
2.7 Documentation
+
+
+ +
3 Upgrading from previous releases of FreeBSD
+
+
+ +
+

1 Introduction

+ +

This document contains the release notes for FreeBSD 6.3-RELEASE on the UltraSPARC +hardware platform. 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 6.3-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 6.3-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 +6.2-RELEASE.

+ +

Typical release note items document recent security advisories issued after +6.2-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

+ +

Two remote denials of service in BIND (one involving DNSSEC and one involving +recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

+ +

Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to +0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

+ +

Problems with +libarchive(3) +and +tar(1) handling +corrupted +tar(5) archive +files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

+ +

A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has +been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

+ +

An flaw that could lead to the disclosure of previously-generated +random(4) data +has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

+ +

Information disclosure issues found in +openpty(3) and + +ptsname(3) have +been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

+ +

A programming error in +inet_network(3) +Internet address manipulation function that could lead to overwriting a region of memory +with user defined data has been corrected. Information regarding this issue can be found +in security advisory FreeBSD-SA-08:02.libc.

+
+ +
+
+

2.2 Kernel Changes

+ +

+acpi(4) now has +support for the HPET time counter.

+ +

Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts +(MSI-X) has been added to the kernel's PCI support code.

+ +
+
+

2.2.1 Boot Loader Changes

+
+ +
+
+

2.2.2 Hardware Support

+ +

An +acpi_dock(4) +driver has been added to provide support for controlling laptop docking station functions +via ACPI.

+ +
+
+
2.2.2.1 Multimedia Support
+ +

The +snd_envy24(4) +driver has been added to support the Envy24 series of audio chips.

+ +

The +snd_envy24ht(4) +driver has been added to support the VIA Envy24HT series of audio chips.

+ +

The +snd_hda(4) +driver has been added. It supports devices that conform to revision 1.0 of the Intel High +Definition Audio specification.

+ +

The +snd_spicds(4) +driver has been added to support I2S SPI audio codec chips.

+
+ +
+
+
2.2.2.2 Network Interface Support
+ +

The +ath(4) driver +has been updated to HAL version 0.9.20.3.

+ +

The +axe(4) driver +now supports +altq(4).

+ +

The +cxgb(4) driver +has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio +T3 and T3B chipsets.

+ +

The +edsc(4) driver, +which provides Ethernet discard network interfaces, has been added.

+ +

The em(4) driver has been +updated to version 6.7.2 from Intel.

+ +

The +msk(4) driver +has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II +Gigabit Ethernet controller.

+ +

The +vge(4) driver +now supports +altq(4).

+ +

The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and +half-channel support for 802.11a.

+
+
+ +
+
+

2.2.3 Network Protocols

+ +

The +if_bridge(4) +driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

+ +

The +lagg(4) driver, +ported from OpenBSD and NetBSD, has been added to support a variety of protocols and +algorithms for link aggregation, failover, and fault tolerance.

+ +

A new +ng_deflate(4) +NetGraph node type has been added. It implements Deflate PPP compression.

+ +

The +ng_ppp(4) +Netgraph node is now MPSAFE.

+ +

A new +ng_pred1(4) +NetGraph node type has been added to implement Predictor-1 PPP compression.

+ +

A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over +gif(4) tunnels +has been fixed.

+ +

The net.link.tap.up_on_open sysctl variable has been +added to the +tap(4) driver. +If enabled, new tap devices will marked up upon creation.

+
+ +
+
+

2.2.4 Disks and Storage

+ +

The +mpt(4) driver +has been updated to support various new features such as RAID volume and RAID member +state/settings reporting, periodic volume re-synchronization status reporting, and sysctl +variables for volume re-synchronization rate, volume member write cache status, and +volume transaction queue depth.

+ +

The +mpt(4) driver +now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

+ +

The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG +passthrough device API, has been added. It is intended to allow programs running under +Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by +Linux.

+ +

The +twa(4) driver +has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's +3ware 9650 series of SATA controllers.

+
+ +
+
+

2.2.5 File Systems

+ +

The unionfs file system has been re-implemented. This version solves many crashing and +locking issues compared to the previous implementation. It also adds new +“transparent” and “masquerade” modes for automatically creating +files in the upper file system layer of unions. More information can be found in the +mount_unionfs(8) +manual page.

+
+
+ +
+
+

2.3 Userland Changes

+ +

The +camcontrol(8) +utility now supports a readcap command to display the size of +devices.

+ +

A bug in +freebsd-update(8), which caused it not to update +SMP kernels correctly, has been fixed.

+ +

The +fdisk(8) program +now supports a -p flag to print the slice table in fdisk +configuration format.

+ +

The +freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different +versions of FreeBSD.

+ +

The +ftpd(8) utility +now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The +RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the +ftpd(8) manual +page.

+ +

The +ipfwpcap(8) +utility has been added; it captures packets on a +divert(4) socket +and writes them as +pcap(3) (also +known as +tcpdump(1)) +format data to a file or pipe.

+ +

The +rpc.lockd(8) and + +rpc.statd(8) +programs now accept -p options to indicate which port they +should bind to.

+ +

The pw(8) program now +supports a -M option to set the permissions of a user's newly +created home directory.

+ +

The +top(1) program +now supports a -j flag to display the +jail(8) ID for +each process.

+ +

The +touch(1) utility +now supports a -A flag that allows the access and +modification times of a file be adjusted by a specified value.

+ +

The +wpa_passphrase(8) utility has been added. It +generates a 256-bit pre-shared WPA key from an ASCII passphrase.

+ +
+
+

2.3.1 /etc/rc.d Scripts

+ +

The sendmail script can be instructed not to rebuild the +aliases database if it is missing or older than the aliases file. If desired, set the new +rc.conf option sendmail_rebuild_aliases to "NO" to turn off +that functionality.

+ +

The /etc/rc.d/nfslocking script has been deprecated and will +be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd +scripts.

+
+
+ +
+
+

2.4 Contributed Software

+ +

awk has been updated from the 24 April 2005 release to the +1 May 2007 release.

+ +

BIND has been updated from 9.3.3 to 9.3.4-p1.

+ +

BZIP2 has been updated from 1.0.3 to 1.0.4.

+ +

GNU Diffutils has been updated from 2.7 to 2.8.7.

+ +

The GNU version of gzip has been replaced with a modified +version of gzip ported from NetBSD.

+ +

IPFilter has been updated from 4.1.13 to 4.1.28.

+ +

less has been updated from v381 to v416.

+ +

ncurses has been updated from 5.2-20020615 to 5.6-20061217. +ncurses now also has wide character support.

+ +

netcat has been updated from the version in a 4 February +2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

+ +

GNU Readline library has been updated from 5.0 to 5.2 patch +2.

+ +

sendmail has been updated from 8.13.8 to 8.14.2.

+ +

The timezone database has been updated from the tzdata2006g +release to the tzdata2007k release.

+ +

TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to +1.0.

+
+ +
+
+

2.5 Ports/Packages Collection +Infrastructure

+
+ +
+
+

2.6 Release Engineering and +Integration

+ +

The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

+ +

The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

+ +

The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

+ +

The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default +value of LOCALBASE.

+
+ +
+
+

2.7 Documentation

+
+
+ +
+
+

3 Upgrading from previous releases of +FreeBSD

+ +

Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

+ +
+
+

Important: Upgrading FreeBSD should, of course, only be attempted after backing +up all data and configuration +files.

+
+
+
+
+ +
+

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

+ +

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

+ +

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

+ + + diff --git a/en/releases/6.3R/relnotes.sgml b/en/releases/6.3R/relnotes.sgml new file mode 100644 index 0000000000..ec8c869869 --- /dev/null +++ b/en/releases/6.3R/relnotes.sgml @@ -0,0 +1,32 @@ + + + + +]> + + &header; + +

The release notes for FreeBSD are customized for different + platforms, as some of the changes made to FreeBSD apply only to + specific processor architectures.

+ +

Release notes for FreeBSD 6.3-RELEASE are available for the following + platforms:

+ + + +

A list of all platforms currently under development can be found + on the Supported + Platforms page.

+ + &footer; + +