diff --git a/en/releases/4.9R/docbook.css b/en/releases/4.9R/docbook.css
new file mode 100644
index 0000000000..ea4167cfc0
--- /dev/null
+++ b/en/releases/4.9R/docbook.css
@@ -0,0 +1,165 @@
+/*
+ * Copyright (c) 2001, 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: doc/share/misc/docbook.css,v 1.6 2003/07/10 15:25:35 blackend Exp $
+ */
+
+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;
+} 
+
+.PROGRAMLISTING, .SCREEN {
+	margin-left: 3ex;
+}
diff --git a/en/releases/4.9R/errata.html b/en/releases/4.9R/errata.html
new file mode 100644
index 0000000000..b1a8548801
--- /dev/null
+++ b/en/releases/4.9R/errata.html
@@ -0,0 +1,98 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD 4.9-RELEASE Errata</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD 4.9-RELEASE Errata</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v
+1.1.2.113 2003/10/06 04:21:21 bmah Exp $<br />
+</p>
+
+<hr />
+</div>
+
+<blockquote class="ABSTRACT">
+<div class="ABSTRACT"><a id="AEN12" name="AEN12"></a>
+<p>This document lists errata items for FreeBSD 4.9-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.</p>
+
+<p>This errata document for FreeBSD 4.9-RELEASE will be maintained until the release of
+FreeBSD 4.10-RELEASE.</p>
+</div>
+</blockquote>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN15" name="AEN15">1 Introduction</a></h2>
+
+<p>This errata document contains ``late-breaking news'' about FreeBSD 4.9-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.</p>
+
+<p>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 <a
+href="http://www.FreeBSD.org/releases/"
+target="_top">http://www.FreeBSD.org/releases/</a>, plus any sites which keep up-to-date
+mirrors of this location.</p>
+
+<p>Source and binary snapshots of FreeBSD 4-STABLE also contain up-to-date copies of this
+document (as of the time of the snapshot).</p>
+
+<p>For a list of all FreeBSD CERT security advisories, see <a
+href="http://www.FreeBSD.org/security/"
+target="_top">http://www.FreeBSD.org/security/</a> or <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"
+target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/</a>.</p>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN26" name="AEN26">2 Security Advisories</a></h2>
+
+<p>No active security advisories.</p>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN29" name="AEN29">3 Late-Breaking News</a></h2>
+
+<p>No news.</p>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+
diff --git a/en/releases/4.9R/hardware-alpha.html b/en/releases/4.9R/hardware-alpha.html
new file mode 100644
index 0000000000..6704ac9b48
--- /dev/null
+++ b/en/releases/4.9R/hardware-alpha.html
@@ -0,0 +1,5352 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD/alpha 4.9-RELEASE Hardware Notes</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD/alpha 4.9-RELEASE Hardware
+Notes</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<hr />
+</div>
+
+<div class="TOC">
+<dl>
+<dt><b>Table of Contents</b></dt>
+
+<dt>1 <a href="#AEN11">Introduction</a></dt>
+
+<dt>2 <a href="#AEN16">Supported processors and motherboards</a></dt>
+
+<dd>
+<dl>
+<dt>2.1 <a href="#AEN25">Overview</a></dt>
+
+<dt>2.2 <a href="#AEN44">In general, what do you need to run FreeBSD on an
+Alpha?</a></dt>
+
+<dt>2.3 <a href="#AEN105">System-specific information</a></dt>
+
+<dd>
+<dl>
+<dt>2.3.1 <a href="#AEN110">AXPpci33 (``NoName'')</a></dt>
+
+<dt>2.3.2 <a href="#AEN184">Universal Desktop Box (UDB or ``Multia'')</a></dt>
+
+<dt>2.3.3 <a href="#AEN270">Personal Workstation (``Miata'')</a></dt>
+
+<dt>2.3.4 <a href="#AEN380">DEC3000 family (the ``Bird'' machines)</a></dt>
+
+<dt>2.3.5 <a href="#AEN551">Evaluation Board 64 family</a></dt>
+
+<dt>2.3.6 <a href="#AEN605">Evaluation Board 164 (``EB164, PC164, PC164LX, PC164SX'')
+family</a></dt>
+
+<dt>2.3.7 <a href="#AEN672">AlphaStation 200 (``Mustang'') and 400 (``Avanti'')
+series</a></dt>
+
+<dt>2.3.8 <a href="#AEN737">AlphaStation 500 and 600 (``Alcor'' &#38; ``Maverick'' for
+EV5, ``Bret'' for EV56)</a></dt>
+
+<dt>2.3.9 <a href="#AEN848">AlphaServer 1000 (``Mikasa''), 1000A (``Noritake'') and
+800(``Corelle'')</a></dt>
+
+<dt>2.3.10 <a href="#AEN904">DS10/VS10/XP900 (``Webbrick'') / XP1000 (``Monet'') / DS10L
+(``Slate'')</a></dt>
+
+<dt>2.3.11 <a href="#AEN1055">DS20/DS20E (``Goldrush'')</a></dt>
+
+<dt>2.3.12 <a href="#AEN1124">AlphaPC 264DP / UP2000</a></dt>
+
+<dt>2.3.13 <a href="#AEN1170">AlphaServer 2000 (``DemiSable''), 2100 (``Sable''), 2100A
+(``Lynx'')</a></dt>
+
+<dt>2.3.14 <a href="#AEN1241">AlphaServer 4x00 (``Rawhide'')</a></dt>
+
+<dt>2.3.15 <a href="#AEN1274">AlphaServer 1200 (``Tincup'') and AlphaStation 1200
+(``DaVinci'')</a></dt>
+
+<dt>2.3.16 <a href="#AEN1304">AlphaServer 8200 and 8400 (``TurboLaser'')</a></dt>
+
+<dt>2.3.17 <a href="#AEN1347">Alpha Processor Inc. UP1000</a></dt>
+
+<dt>2.3.18 <a href="#AEN1396">Alpha Processor Inc. UP1100</a></dt>
+
+<dt>2.3.19 <a href="#AEN1444">Alpha Processor Inc. CS20, Compaq DS20L</a></dt>
+
+<dt>2.3.20 <a href="#AEN1491">Compaq AlphaServer ES40 (``Clipper'')</a></dt>
+</dl>
+</dd>
+
+<dt>2.4 <a href="#AEN1528">Supported Hardware Overview</a></dt>
+
+<dt>2.5 <a href="#AEN1560">Acknowledgments</a></dt>
+</dl>
+</dd>
+
+<dt>3 <a href="#AEN1601">Supported Devices</a></dt>
+
+<dd>
+<dl>
+<dt>3.1 <a href="#AEN1607">Disk Controllers</a></dt>
+
+<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt>
+
+<dt>3.3 <a href="#AEN2916">FDDI Interfaces</a></dt>
+
+<dt>3.4 <a href="#AEN2926">ATM Interfaces</a></dt>
+
+<dt>3.5 <a href="#AEN2968">Wireless Network Interfaces</a></dt>
+
+<dt>3.6 <a href="#AEN3096">Miscellaneous Networks</a></dt>
+
+<dt>3.7 <a href="#AEN3113">ISDN Interfaces</a></dt>
+
+<dt>3.8 <a href="#AEN3177">Multi-port Serial Interfaces</a></dt>
+
+<dt>3.9 <a href="#AEN3309">Audio Devices</a></dt>
+
+<dt>3.10 <a href="#AEN3412">Camera and Video Capture Devices</a></dt>
+
+<dt>3.11 <a href="#USB">USB Devices</a></dt>
+
+<dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt>
+
+<dt>3.13 <a href="#AEN3673">Cryptographic Accelerators</a></dt>
+
+<dt>3.14 <a href="#AEN3698">Miscellaneous</a></dt>
+</dl>
+</dd>
+</dl>
+</div>
+
+<div class="SECT1">
+<h2 class="SECT1"><a id="AEN11" name="AEN11">1 Introduction</a></h2>
+
+<p>This document contains the hardware compatability notes for FreeBSD 4.9-RELEASE on the
+Alpha/AXP hardware platform (also referred to as FreeBSD/alpha 4.9-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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> This document includes information specific to the Alpha/AXP hardware
+platform. Versions of the hardware compatability notes for other architectures will
+differ in some details.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN16" name="AEN16">2 Supported processors and
+motherboards</a></h2>
+
+<i class="AUTHORGROUP"><span class="CONTRIB">Maintained by</span> Wilko Bulte.</i> 
+
+<p>Additions, corrections and constructive criticism are invited. In particular,
+information on system quirks is more than welcome.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN25" name="AEN25">2.1 Overview</a></h3>
+
+<p>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.</p>
+
+<p>The information is structured as follows:</p>
+
+<ul>
+<li>
+<p>general hardware requirements to run FreeBSD on alpha;</p>
+</li>
+
+<li>
+<p>system specific information for each of the systems/boards supported by FreeBSD;</p>
+</li>
+
+<li>
+<p>information on expansion boards for FreeBSD, including things that differ from what is
+in the generic supported hardware list.</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> 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.</p>
+</blockquote>
+</div>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> SRM commands will be in <kbd class="USERINPUT">UPPER CASE</kbd>. Lower
+case input is also acceptable to SRM. Upper case is used for clarity.</p>
+</blockquote>
+</div>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Compaq has put information on the Web for Linux developers that is also
+very useful for FreeBSD users. Please check at <a
+href="http://www.support.compaq.com/alpha-tools/" target="_top">Linux Alpha Power
+tools</a>.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN44" name="AEN44">2.2 In general, what do you need to run
+FreeBSD on an Alpha?</a></h3>
+
+<p>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 <tt
+class="FILENAME">GENERIC</tt> kernel at unknown hardware is almost guaranteed to fail
+miserably.</p>
+
+<p>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.</p>
+
+<p>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 <span class="emphasis"><i
+class="EMPHASIS">no</i></span> 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.</p>
+
+<p>Known non-SRM machines are:</p>
+
+<ul>
+<li>
+<p>Digital XL series</p>
+</li>
+
+<li>
+<p>Digital XLT series</p>
+</li>
+
+<li>
+<p>Samsung PC164UX (``Ruffian'')</p>
+</li>
+
+<li>
+<p>Samsung 164B</p>
+</li>
+</ul>
+
+<p>Machines that have SRM but are not supported by FreeBSD are:</p>
+
+<ul>
+<li>
+<p>DECpc 150 (``Jensen'')</p>
+</li>
+
+<li>
+<p>DEC 2000/300 (``Jensen'')</p>
+</li>
+
+<li>
+<p>DEC 2000/500 (``Culzean'')</p>
+</li>
+
+<li>
+<p>AXPvme series (``Medulla'')</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>The problem might bite those who have machines that started their lives as WindowsNT
+boxes. The ARC or AlphaBIOS knows about <span class="emphasis"><i
+class="EMPHASIS">other</i></span> 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.</p>
+
+<p>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.</p>
+
+<p>FreeBSD 4.0 and later can be booted from the distribution CDROM. Earlier versions
+needed booting from a 2 disk floppy set.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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. <span class="emphasis"><i
+class="EMPHASIS">This can be extremely confusing.</i></span></p>
+
+<p>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.</p>
+
+<p>Most PCI devices from the PC-world will also work in FreeBSD PCI-based machines. Check
+the <tt class="FILENAME">/sys/alpha/conf/GENERIC</tt> 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:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SET PCI_PARITY OFF</kbd>
+</pre>
+
+<p>This is not a FreeBSD problem, all operating systems running on Alpha hardware will
+need this workaround.</p>
+
+<p>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.</p>
+
+<p>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 &amp; 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).</p>
+
+<p>For memory you want at least 32 Mbytes. I have had FreeBSD run on a 16 Mbyte system
+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 64 Mbytes or more are recommended.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN105" name="AEN105">2.3 System-specific information</a></h3>
+
+<p>Below is an overview of the hardware that FreeBSD runs on. This list will definitely
+grow, a look in <tt class="FILENAME">/sys/alpha/conf/GENERIC</tt> can be
+enlightening.</p>
+
+<p>Alpha machines are often best known by their project code name. Where known these are
+listed below in parentheses.</p>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN110" name="AEN110">2.3.1 AXPpci33 (``NoName'')</a></h4>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21066 Alpha CPU at 166 MHz or 21066A CPU at 233MHz. 21068 CPUs are also possible, but
+are even slower.</p>
+</li>
+
+<li>
+<p>on-board Bcache / L2 cache: 0, 256k or 1 Mbyte (uses DIL chips)</p>
+</li>
+
+<li>
+<p>PS/2 mouse &#38; keyboard port OR 5pin DIN keyboard (2 mainboard models)</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>bus width: 64 bits</p>
+</li>
+
+<li>
+<p>PS/2 style 72 pin 36 bit Fast Page Mode SIMMs</p>
+</li>
+
+<li>
+<p>70ns or better</p>
+</li>
+
+<li>
+<p>installed in pairs of 2</p>
+</li>
+
+<li>
+<p>4 SIMM sockets</p>
+</li>
+
+<li>
+<p>uses ECC</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>512kB Flash ROM for the console code.</p>
+</li>
+
+<li>
+<p>2 16550A serial ports</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>floppy interface</p>
+</li>
+
+<li>
+<p>1 embedded IDE interface</p>
+</li>
+
+<li>
+<p>expansion:</p>
+
+<ul>
+<li>
+<p>3 32 bit PCI slots (1 shared with ISA)</p>
+</li>
+
+<li>
+<p>5 ISA slots (1 shared with PCI)</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>embedded Fast SCSI using a Symbios 53C810 chip</p>
+</li>
+</ul>
+
+<p>NoNames can either have SRM <span class="emphasis"><i class="EMPHASIS">or</i></span>
+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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>The IDE interface is supported by FreeBSD and requires a line in the kernel
+configuration file as follows:</p>
+
+<pre class="PROGRAMLISTING">
+device ata0 at isa? port IO_WD1 irq 14
+</pre>
+
+<p>The SRM console unfortunately <span class="emphasis"><i class="EMPHASIS">cannot
+boot</i></span> from IDE disks. This means you will have to use a SCSI disk as the boot
+device.</p>
+
+<p>The NoName is somewhat stubborn when it comes to serial consoles. It needs</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt; <kbd class="USERINPUT">SET CONSOLE SERIAL</kbd>
+</pre>
+
+<p>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</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt; <kbd class="USERINPUT">SET CONSOLE GRAPHICS</kbd>
+</pre>
+
+<p>at the serial console.</p>
+
+<p>There have been reports that you sometimes need to press <b
+class="KEYCAP">Control</b>-<b class="KEYCAP">Alt</b>-<b class="KEYCAP">Del</b> 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.</p>
+
+<p>Make sure you use true 36 bit SIMMs, and only FPM (Fast Page Mode) DRAM. EDO DRAM or
+SIMMs with fake parity <span class="emphasis"><i class="EMPHASIS">will not
+work</i></span>. The board uses the 4 extra bits for ECC. 33 bit FPM SIMMs will for the
+same reason not work.</p>
+
+<p>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.</p>
+
+<p>The <a href="ftp://ftp.digital.com/pub/DEC/axppci/design_guide.ps" target="_top">OEM
+manual</a> is recommended reading.</p>
+
+<p>The kernel configuration file for a NoName kernel must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_AXPPCI_33           
+cpu EV4
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN184" name="AEN184">2.3.2 Universal Desktop Box (UDB or
+``Multia'')</a></h4>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Multia can be either Intel or Alpha CPU based. We assume Alpha based ones
+here for obvious reasons.</p>
+</blockquote>
+</div>
+
+<p>Multia is a small desktop box intended as a sort of personal workstation. They come in
+a considerable number of variations, check closely what you get.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21066 Alpha CPU at 166 MHz or 21066A CPU at 233MHz</p>
+</li>
+
+<li>
+<p>on-board Bcache / L2 cache: COAST-like 256 kByte cache module; 233MHz models have
+512kByte of cache; 166MHz models have soldered-on 256kB caches</p>
+</li>
+
+<li>
+<p>PS/2 mouse &#38; keyboard port</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>bus width: 64 bits</p>
+</li>
+
+<li>
+<p>PS/2 style 72 pin 36 bit Fast Page Mode SIMMs</p>
+</li>
+
+<li>
+<p>70ns or better</p>
+</li>
+
+<li>
+<p>SIMMs are installed in pairs of 2</p>
+</li>
+
+<li>
+<p>4 SIMM sockets</p>
+</li>
+
+<li>
+<p>uses ECC</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>2 16550A serial ports</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>floppy interface</p>
+</li>
+
+<li>
+<p>Intel 82378ZB PCI to ISA bridge</p>
+</li>
+
+<li>
+<p>1 embedded 21040 based 10Mbit Ethernet, AUI and 10base2 connector</p>
+</li>
+
+<li>
+<p>expansion:</p>
+
+<ul>
+<li>
+<p>1 32 bit PCI slot</p>
+</li>
+
+<li>
+<p>2 PCMCIA slots</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>on-board Crystal CS4231 or AD1848 sound chip</p>
+</li>
+
+<li>
+<p>embedded Fast SCSI, using a Symbios 53C810[A] chip on the PCI riser card</p>
+</li>
+</ul>
+
+<p>Multia has enough Flash ROM to store both SRM and ARC code at the same time and allow
+software selection of one of them.</p>
+
+<p>The embeded TGA video adapter is <span class="emphasis"><i
+class="EMPHASIS">not</i></span> currently usable as a FreeBSD console. You will need to
+use a serial console.</p>
+
+<p>Multia has only one 32 bit PCI slot for expansion, and it is only suitable for a small
+form factor PCI card. By sacrificing the PCI slot space you can mount a 3.5&quot; hard
+disk drive. Mounting stuff may have come with your Multia. Adding a 3.5&quot; disk is
+<span class="emphasis"><i class="EMPHASIS">not</i></span> a recommended upgrade due to
+the limited power rating of the power supply and the extremely marginal cooling of the
+system box.</p>
+
+<p>Multia also has 2 PCMCIA expansion slots. These are currently not supported by
+FreeBSD.</p>
+
+<p>The CPU might or might not be socketed, check this before considering CPU upgrade
+hacks. The low-end Multias have a soldered-in CPU.</p>
+
+<p>Multia has 2 serial ports but routes both of them to the outside world on a single 25
+pin sub-D connector. The Multia FAQ explains how to build your own Y-cable to allow both
+ports to be used.</p>
+
+<p>Although the Multia SRM supports booting from floppy this can be problematic.
+Typically the errors look like:</p>
+
+<pre class="SCREEN">
+*** Soft Error - Error #10 - FDC: Data overrun or underrun
+</pre>
+
+<p>This is not a FreeBSD problem, it is a SRM problem. The best available workaround to
+install FreeBSD is to boot from a SCSI CDROM.</p>
+
+<p>There have been reports that you sometimes need to press <b
+class="KEYCAP">Control</b>-<b class="KEYCAP">Alt</b>-<b class="KEYCAP">Del</b> to capture
+the SRM's attention. I have never seen this myself, but it is worth trying when you are
+greeted by a blank screen after powerup.</p>
+
+<p>Sound works fine using <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a> driver
+and a line in the kernel configuration file as follows for the Crystal CS4231 chip:</p>
+
+<pre class="PROGRAMLISTING">
+device pcm0 at isa? port 0x530  irq 9 drq 3 flags 0x15
+</pre>
+
+<p>I have not yet been successful in getting my Multia with the AD1848 to play any
+sound.</p>
+
+<p>While verifying playback I was reminded of the lack of CPU power of the 166MHz CPU.
+MP3 only plays acceptable using 22kHz down-sampling.</p>
+
+<p>Multias are somewhat notorious for dying of heat strokes. The very compact box does
+not really allow access to cooling air. Please use the Multia on its vertical stand,
+don't put it horizontally (``pizza style''). Replacing the fan with something which
+pushes around more air is really recommended. You can also cut one of the wires to the
+fan speed sensor. Once cut, the fan runs at a (loud) full speed. Beware of PCI cards with
+high power consumption. If your system has died you might want to check the
+Multia-Heat-Death pages at the <a href="http://www.netbsd.org/" target="_top">NetBSD Web
+site</a> for help in reviving it.</p>
+
+<p>The Intel 82378ZB PCI to ISA bridge enables the use of an IDE disk. This requires a
+line in the kernel configuration file as follows:</p>
+
+<pre class="PROGRAMLISTING">
+device ata0 at isa? port IO_WD1 irq 14
+</pre>
+
+<p>The IDE connector pin spacing is thought for 2.5&quot; laptop disks. A 3.5&quot; IDE
+disk would not fit in the case anyway. At least not without sacrificing your only PCI
+slot. The SRM console unfortunately does not know how to boot from IDE disks. You will
+need to use a SCSI disk as the boot disk.</p>
+
+<p>In case you want to change the internal hard drive: the internal flat cable running
+from the PCI riser board to the <span class="emphasis"><i
+class="EMPHASIS">2.5&quot;</i></span> hard drive has a finer pitch than the standard SCSI
+flat cables. Otherwise it would not fit on the 2.5&quot; drives. There are also riser
+cards that have a standard-pitch SCSI cable attached to it, which will fit an ordinary
+SCSI disk.</p>
+
+<p>Again, I recommend against trying to cram a replacement hard disk inside. Use the
+external SCSI connector and put your disk in an external enclosure. Multias run hot
+enough as-is. In most cases you will have the external high density 50-pin SCSI connector
+but some Multia models came without disk and may lack the connector. Something to check
+before buying one.</p>
+
+<p>The kernel configuration file for a Multia kernel must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_AXPPCI_33
+cpu EV4
+</pre>
+
+<p>Recommended reading on Multia can be found at <a
+href="http://www.netbsd.org/Ports/alpha/multiafaq.html"
+target="_top">http://www.netbsd.org/Ports/alpha/multiafaq.html</a> or <a
+href="http://www.brouhaha.com/~eric/computers/udb.html"
+target="_top">http://www.brouhaha.com/~eric/computers/udb.html</a>.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN270" name="AEN270">2.3.3 Personal Workstation
+(``Miata'')</a></h4>
+
+<p>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.</p>
+
+<p>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].</p>
+
+<p>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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21164A EV56 Alpha CPU at 433, 500 or 600MHz</p>
+</li>
+
+<li>
+<p>21174 core logic (``Pyxis'') chip</p>
+</li>
+
+<li>
+<p>on-board Bcache / L3 cache: 0, 2 or 4 Mbytes (uses a cache module)</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>bus width: 128 bits wide, ECC protected</p>
+</li>
+
+<li>
+<p>unbuffered 72 bit wide SDRAMs DIMMs, installed in pairs of 2</p>
+</li>
+
+<li>
+<p>6 DIMM sockets</p>
+</li>
+
+<li>
+<p>maximum memory 1.5 GBytes</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>on-board Fast Ethernet:</p>
+
+<ul>
+<li>
+<p>MX5 uses a 21142 or 21143 Ethernet chip, dependent on the version of the PCI riser
+card</p>
+</li>
+
+<li>
+<p>MiataGL has a 21143 chip</p>
+</li>
+
+<li>
+<p>the bulkhead can be 10/100 Mbit UTP, or 10 Mbit UTP/BNC</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>2 on-board [E]IDE disk interfaces, based on the CMD646 (MX5) or the Cypress 82C693
+(MiataGL)</p>
+</li>
+
+<li>
+<p>1 Ultra-Wide SCSI Qlogic 1040 [MiataGL only]</p>
+</li>
+
+<li>
+<p>2 64-bit PCI slots</p>
+</li>
+
+<li>
+<p>3 32-bit PCI slots (behind a DEC PCI-PCI bridge chip)</p>
+</li>
+
+<li>
+<p>3 ISA slots (physically shared with the 32 bit PCI slots, via an Intel 82378IB PCI to
+ISA bridge chip)</p>
+</li>
+
+<li>
+<p>2 16550A serial port</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>PS/2 keyboard &#38; mouse port</p>
+</li>
+
+<li>
+<p>USB interface [MiataGL only]</p>
+</li>
+
+<li>
+<p>embedded sound based on an ESS1888 chip</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>If you want to fool the SRM you can type <kbd class="USERINPUT">set
+pci_device_override</kbd> at the SRM prompt. Just don't complain if your data
+mysteriously gets mangled.</p>
+
+<p>The complete command is:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">SET PCI_DEVICE_OVERRIDE <var
+class="REPLACEABLE">&lt;vendor_id&gt;</var><var
+class="REPLACEABLE">&lt;device_id&gt;</var></kbd>
+</pre>
+
+<p>For example:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">SET PCI_DEVICE_OVERRIDE 88c15333</kbd>
+</pre>
+
+<p>The most radical approach is to use:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">SET PCI_DEVICE_OVERRIDE -1</kbd>
+</pre>
+
+<p>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.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> Do this on your own risk..</p>
+</blockquote>
+</div>
+
+<p>The FreeBSD kernel reports it when it sees a buggy Pyxis chip:</p>
+
+<pre class="SCREEN">
+Sep 16 18:39:43 miata /kernel: cia0: Pyxis, pass 1
+Sep 16 18:39:43 miata /kernel: cia0: extended capabilities: 1&lt;BWEN&gt;
+Sep 16 18:39:43 miata /kernel: cia0: WARNING: Pyxis pass 1 DMA bug; no bets...
+</pre>
+
+<p>A MiataGL probes as:</p>
+
+<pre class="SCREEN">
+Jan  3 12:22:32 miata /kernel: cia0: Pyxis, pass 1
+Jan  3 12:22:32 miata /kernel: cia0: extended capabilities: 1&lt;BWEN&gt;
+Jan  3 12:22:32 miata /kernel: pcib0: &lt;2117x PCI host bus adapter&gt; on cia0
+</pre>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>Miata MX5s generally use Qlogic 1040 based SCSI adapters. These are bootable by the
+SRM console. Note that Adaptec cards are <span class="emphasis"><i
+class="EMPHASIS">not</i></span> bootable by the Miata SRM console.</p>
+
+<p>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 <span class="emphasis"><i
+class="EMPHASIS">same</i></span> chip as the MiataGL. All in all there is a lot of
+variation.</p>
+
+<p>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.</p>
+
+<p>Both MX5 and MiataGL have an on-board sound chip, an ESS1888. It emulates a
+SoundBlaster and can be enabled by putting</p>
+
+<pre class="PROGRAMLISTING">
+device pcm0
+device  sbc0
+</pre>
+
+<p>in your kernel configuration file:</p>
+
+<p>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.</p>
+
+<p>Installing a 2Mb cache module achieves, apart from a 10-15% speed increase (based on
+buildworld elapsed time), a <span class="emphasis"><i
+class="EMPHASIS">decrease</i></span> 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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>If you experience SRM errors like</p>
+
+<pre class="SCREEN">
+ERROR: scancode 0xa3 not supported on PCXAL
+</pre>
+
+<p>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 <a
+href="http://www.compaq.com/" target="_top">http://www.compaq.com/</a> This SRM problem
+is fixed on both Miata MX5 and Miata GL.</p>
+
+<p>USB is supported by FreeBSD 4.1 and later.</p>
+
+<p>Disconnect the power cord before dismantling the machine, the soft-power switch keeps
+part of the logic powered <span class="emphasis"><i class="EMPHASIS">even</i></span> when
+the machine is switched off.</p>
+
+<p>The kernel configuration file for a Miata kernel must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_ST550               
+cpu EV5
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN380" name="AEN380">2.3.4 DEC3000 family (the ``Bird''
+machines)</a></h4>
+
+<p>The DEC3000 series were among the first Alpha machines ever produced. They are based
+on an I/O bus called the TurboChannel (TC) bus. These machines are built like tanks
+(watch your back).</p>
+
+<p>DEC3000 can be subdivided in DEC3000/500-class and DEC3000/300-class. The
+DEC3000/500-class is the early high-end workstation/server Alpha family. Servers use
+serial consoles, workstations have graphics tubes. DEC3000/300-class is the lower-cost
+workstation class.</p>
+
+<p>DEC3000/500-class are quite fast (considering their age) thanks to the good memory
+design. DEC3000/300 is crippled compared to DEC3000/500 because of its much narrower
+memory bus.</p>
+
+<p>They are called ``Birds'' because their internal DEC code names were bird names:</p>
+
+<div class="INFORMALTABLE"><a id="AEN388" name="AEN388"></a>
+<table border="1" class="CALSTABLE">
+<col width="1*" />
+<col width="1*" />
+<col width="2*" />
+<tbody>
+<tr>
+<td>DEC3000/400</td>
+<td>Sandpiper</td>
+<td>133MHz CPU, desktop</td>
+</tr>
+
+<tr>
+<td>DEC3000/500</td>
+<td>Flamingo</td>
+<td>150MHz CPU, floor standing</td>
+</tr>
+
+<tr>
+<td>DEC3000/500X</td>
+<td>Hot Pink</td>
+<td>200MHz CPU, floor standing</td>
+</tr>
+
+<tr>
+<td>DEC3000/600</td>
+<td>Sandpiper+</td>
+<td>175MHz CPU, desktop</td>
+</tr>
+
+<tr>
+<td>DEC3000/700</td>
+<td>Sandpiper45</td>
+<td>225MHz CPU, floor standing</td>
+</tr>
+
+<tr>
+<td>DEC3000/800</td>
+<td>Flamingo Ultra</td>
+<td>200MHz CPU, floor standing</td>
+</tr>
+
+<tr>
+<td>DEC3000/900</td>
+<td>Flamingo45</td>
+<td>275MHz CPU, floor standing</td>
+</tr>
+
+<tr>
+<td>DEC3000/300</td>
+<td>Pelican</td>
+<td>150MHz CPU, desktop, 2 TC slots</td>
+</tr>
+
+<tr>
+<td>DEC3000/300X</td>
+<td>Pelican+</td>
+<td>175MHz CPU, desktop, 2 TC slots</td>
+</tr>
+
+<tr>
+<td>DEC3000/300LX</td>
+<td>Pelican+</td>
+<td>125MHz CPU, desktop, 2 TC slots</td>
+</tr>
+
+<tr>
+<td>DEC3000/300L</td>
+<td>&nbsp;</td>
+<td>100MHz CPU, desktop, no TC slots</td>
+</tr>
+</tbody>
+</table>
+</div>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21064 CPU (100 to 200 MHz) or 21064A CPU (225 to 275 MHz)</p>
+</li>
+
+<li>
+<p>memory DEC3000/500 class:</p>
+
+<ul>
+<li>
+<p>bus width: 256 bit, with ECC</p>
+</li>
+
+<li>
+<p>proprietary 100pin SIMMs</p>
+</li>
+
+<li>
+<p>installed in sets of 8</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>memory DEC3000/300 class:</p>
+
+<ul>
+<li>
+<p>bus width: 64 bit, with ECC</p>
+</li>
+
+<li>
+<p>PS/2 style 72pin 36 bit FPM SIMMs 70ns or better</p>
+</li>
+
+<li>
+<p>used in pairs of 2</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>Bcache / L2 cache: varying sizes, 512 kB to 2 Mbyte</p>
+</li>
+
+<li>
+<p>built-in 10Mbit Ethernet based on a Lance 7990 chip, AUI and UTP</p>
+</li>
+
+<li>
+<p>one or two SCSI buses based on a NCR53C94 or a NCR53CF94-2 chip</p>
+</li>
+
+<li>
+<p>2 serial ports based on Zilog 8530 (one usable as a serial console)</p>
+</li>
+
+<li>
+<p>embedded ISDN interface</p>
+</li>
+
+<li>
+<p>on-board 8 bit sound</p>
+</li>
+
+<li>
+<p>8 bit graphics on-board or via a TC card (depending on model)</p>
+</li>
+</ul>
+
+<p>Currently DEC3000 machines can only be used diskless on FreeBSD. The reason for this
+is that the SCSI drivers needed for the TC SCSI adapters were not brought into CAM that
+the recent FreeBSD versions use. TC option cards for single (PMAZ-A) or dual fast SCSI
+(PMAZC-AA) are also available. These cards currently have no drivers on FreeBSD
+either.</p>
+
+<p>DEC3000/300 has 5 MBytes/sec SCSI on-board. This bus is used for both internal and
+external devices. DEC3000/500 has 2 SCSI buses. One is for internal devices only, the
+other one is for external devices only.</p>
+
+<p>Floppy devices found in the DEC3000s are attached to the SCSI bus (via a bridge card).
+This makes it possible to boot from them using the same device names as ordinary SCSI
+hard-disks, for example:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">BOOT DKA300</kbd>
+</pre>
+
+<p>The 3000/300 series has a half-speed TurboChannel compared to the other 3000 machines.
+Some TC expansion cards have troubles with the half-speed bus. Caveat emptor.</p>
+
+<p>The embedded ISDN interface is not supported on FreeBSD.</p>
+
+<p>DEC3000/300-class uses standard 36 bit, 72 pin Fast Page Mode SIMMs. EDO SIMMs, 32 or
+33 bit SIMMs all will not work in Pelicans. For 32Mbyte SIMMs to work on the
+DEC3000/300-class the presence detect bits/pins of the SIMM must correspond to what the
+machine expects. If they don't, the SIMM is ``seen'' as a 8 Mbyte SIMM. 8 Mbyte and 32
+Mbyte SIMMs can be mixed, as long as the pairs themselves are identical.</p>
+
+<p>When you find yourself in need of fixing 32Mbyte SIMMs that lack correct presence bits
+the following info might be of use:</p>
+
+<p>There are four presence detection bits on PS/2 SIMMs. Two of the bits indicate the
+access time. The other two indicate the memory size.</p>
+
+<p>At one end of the SIMM there are two rows of four solder pads. One row is connected to
+Vss (GND) and the other is connected to pins 67 (PRD1), 68 (PRD2), 69 (PRD3), 70
+(PRD4).</p>
+
+<p>If you bridge a pair of pads with a small resistor or a drop of solder you ground that
+particular bit.</p>
+
+<div class="INFORMALTABLE"><a id="AEN488" name="AEN488"></a>
+<table border="1" class="CALSTABLE">
+<col width="1*" />
+<col width="1*" />
+<col width="2*" />
+<thead>
+<tr>
+<th>PRD1</th>
+<th>PRD2</th>
+<th>Memory Size</th>
+</tr>
+</thead>
+
+<tbody>
+<tr>
+<td>GND</td>
+<td>GND</td>
+<td>4 or 64 Mbyte</td>
+</tr>
+
+<tr>
+<td>Open</td>
+<td>GND</td>
+<td>2 or 32 Mbyte</td>
+</tr>
+
+<tr>
+<td>GND</td>
+<td>Open</td>
+<td>1 or 16 Mbyte</td>
+</tr>
+
+<tr>
+<td>Open</td>
+<td>Open</td>
+<td>8 Mbyte</td>
+</tr>
+</tbody>
+</table>
+</div>
+
+<div class="INFORMALTABLE"><a id="AEN515" name="AEN515"></a>
+<table border="1" class="CALSTABLE">
+<col width="1*" />
+<col width="1*" />
+<col width="2*" />
+<thead>
+<tr>
+<th>PRD3</th>
+<th>PRD4</th>
+<th>Access Time</th>
+</tr>
+</thead>
+
+<tbody>
+<tr>
+<td>GND</td>
+<td>GND</td>
+<td>50 or 100 nsec</td>
+</tr>
+
+<tr>
+<td>Open</td>
+<td>GND</td>
+<td>80 nsec</td>
+</tr>
+
+<tr>
+<td>GND</td>
+<td>Open</td>
+<td>70 nsec</td>
+</tr>
+
+<tr>
+<td>Open</td>
+<td>Open</td>
+<td>60 nsec</td>
+</tr>
+</tbody>
+</table>
+</div>
+
+<p>DEC3000/500-class can use 2, 4, 8, 16 and 32 Mbyte 100pin SIMMs. Note that the maximum
+memory size varies from system to system, desktop machines have sacrificed box size for
+less memory SIMM sockets. Given enough sockets and enough SIMMs you can get to 512 Mbytes
+maximum. This is one of the main differences between floor standing and desktop machines,
+the latter have far less SIMM sockets.</p>
+
+<p>The sound hardware is not supported on any of the Birds.</p>
+
+<p>There is no X-Windows version available for the TC machines. DEC3000/300 needs a
+serial console. DEC3000/500-class might work with a graphical console. I ran mine with a
+serial console so I cannot verify this.</p>
+
+<p>Birds can be obtained from surplus sales etc. As they are not PCI based they are no
+longer actively maintained. TC expansion boards can be difficult to obtain these days and
+support for them is not too good unless you write/debug the code yourself. Programming
+information for TC boards is hard to find. Birds are recommended only if a. you can get
+them cheap and b. if you prepared to work on the code to support them better.</p>
+
+<p>For the DEC3000/[4-9]00 series machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_3000_500           
+cpu EV4
+</pre>
+
+<p>For the DEC3000/300 (``Pelican'') machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_3000_300            
+cpu EV4
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN551" name="AEN551">2.3.5 Evaluation Board 64 family</a></h4>
+
+<p>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:</p>
+
+<ul>
+<li>
+<p>21064 or 21064A CPU, 150 to 275 MHz</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>memory buswidth: 128 bit</p>
+</li>
+
+<li>
+<p>PS/2 style 72 pin 33 bit Fast Page Mode SIMMs</p>
+</li>
+
+<li>
+<p>70ns or better</p>
+</li>
+
+<li>
+<p>installed in sets of 4</p>
+</li>
+
+<li>
+<p>8 SIMM sockets</p>
+</li>
+
+<li>
+<p>uses parity memory</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>Bcache / L2 cache: 0, 512 kByte, 1 Mbyte or 2 Mbytes</p>
+</li>
+
+<li>
+<p>21072 (``APECS'') chip set</p>
+</li>
+
+<li>
+<p>Intel 82378ZB PCI to ISA bridge chip (``Saturn'')</p>
+</li>
+
+<li>
+<p>dual 16550A serial ports</p>
+</li>
+
+<li>
+<p>parallel printer port</p>
+</li>
+
+<li>
+<p>Symbios 53C810 Fast-SCSI (not on AlphaPC64)</p>
+</li>
+
+<li>
+<p>IDE interface (only on AlphaPC64)</p>
+</li>
+
+<li>
+<p>embedded 10 Mbit Ethernet (not on AlphaPC64)</p>
+</li>
+
+<li>
+<p>2 PCI slots (4 slots on AlphaPC64)</p>
+</li>
+
+<li>
+<p>3 ISA slots</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>36 bits SIMMs work fine, 3 bits simply remain unused. Note the systems use Fast Page
+Mode memory, not EDO memory.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>AlphaPC64 boards generally come with ARC console firmware. SRM console code can be
+loaded from floppy into the Flash ROM.</p>
+
+<p>The IDE interface of the AlphaPC64 is not bootable from the SRM console. Enabling it
+requires the following line in the kernel configuration file:</p>
+
+<pre class="PROGRAMLISTING">
+device ata0 at isa? port IO_WD1 irq 14
+</pre>
+
+<p>Note that the boards require a power supply that supplies 3.3 Volts for the CPU.</p>
+
+<p>For the EB64 family machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_EB64PLUS            
+cpu EV4
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN605" name="AEN605">2.3.6 Evaluation Board 164 (``EB164,
+PC164, PC164LX, PC164SX'') family</a></h4>
+
+<p>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.</p>
+
+<ul>
+<li>
+<p>21164A, multiple speed variants [EB164, PC164, PC164LX]</p>
+</li>
+
+<li>
+<p>21164PC [only on PC164SX]</p>
+</li>
+
+<li>
+<p>21171 (Alcor) chip set [EB164]</p>
+
+<p>21172 (Alcor2) chip set [PC164]</p>
+
+<p>21174 (Pyxis) chip [164LX, 164SX]</p>
+</li>
+
+<li>
+<p>Bcache / L3 cache: EB164 uses special cache-SIMMs</p>
+</li>
+
+<li>
+<p>memory bus: 128 bit / 256 bit</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>PS/2 style SIMMs in sets of 4 or 8</p>
+</li>
+
+<li>
+<p>36 bit, Fast Page Mode, uses ECC, [EB164 / PC164]</p>
+</li>
+
+<li>
+<p>SDRAM DIMMs in sets of 2, uses ECC [PC164SX / PC164LX]</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>2 16550A serial ports</p>
+</li>
+
+<li>
+<p>PS/2 style keyboard &#38; mouse</p>
+</li>
+
+<li>
+<p>floppy controller</p>
+</li>
+
+<li>
+<p>parallel port</p>
+</li>
+
+<li>
+<p>32 bits PCI</p>
+</li>
+
+<li>
+<p>64 bits PCI [some models]</p>
+</li>
+
+<li>
+<p>ISA slots via an Intel 82378ZB PCI to ISA bridge chip</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>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. Unfortunately this seems to be dependent on the actual version of the
+chip/board.</p>
+
+<p>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.</p>
+
+<p>164LX and 164SX with SRM firmware version 5.8 or later can boot from Adaptec
+2940-series adapters.</p>
+
+<p>In summary: this family of machines is ``blessed'' with a challenging compatibility as
+far as SCSI adapters go.</p>
+
+<p>On 164SX you can have a maximum of 1 Gbyte of RAM. 4 regular 256MB PC133 ECC DIMMs are
+reported to work just fine. Whether 512MB DIMMs will also work is currently unknown.</p>
+
+<p>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.</p>
+
+<p>On PC164 the SRM sometimes seems to loose 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:</p>
+
+<pre class="SCREEN">
+ERROR: ISA table corrupt!
+</pre>
+
+<p>A sequence of a downgrade to SRM4.9, an</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">ISACFG -INIT</kbd>
+</pre>
+
+<p>followed by</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">INIT</kbd>
+</pre>
+
+<p>made the problem go away. Some PC164 owners report they have never seen the
+problem.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>PC164 can boot from IDE disks assuming your SRM version is recent enough.</p>
+
+<p>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.</p>
+
+<p>For the EB164 class machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options         DEC_EB164
+cpu             EV5
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN672" name="AEN672">2.3.7 AlphaStation 200 (``Mustang'') and
+400 (``Avanti'') series</a></h4>
+
+<p>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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21064 or 21064A CPU at speeds of 166 up to 333 MHz</p>
+</li>
+
+<li>
+<p>DECchip 21071-AA core logic chip set</p>
+</li>
+
+<li>
+<p>Bcache / L2 cache: 512 Kbytes (200 and 400 series) or 2048KBytes (250 series)</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>64 bit bus width</p>
+</li>
+
+<li>
+<p>8 to 384 MBytes of RAM</p>
+</li>
+
+<li>
+<p>70 ns or better Fast Page DRAM</p>
+</li>
+
+<li>
+<p>in three pairs (200 and 400 series)</p>
+</li>
+
+<li>
+<p>in two quads, so banks of four. (250 series)</p>
+</li>
+
+<li>
+<p>the memory subsystem uses parity</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>PS/2 keyboard and mouse port</p>
+</li>
+
+<li>
+<p>two 16550 serial ports</p>
+</li>
+
+<li>
+<p>parallel port</p>
+</li>
+
+<li>
+<p>floppy disk interface</p>
+</li>
+
+<li>
+<p>32 bit PCI expansion slots (3 for the AS400-series, 2 for the AS200 &#38;
+250-series)</p>
+</li>
+
+<li>
+<p>ISA expansion slots (4 for the AS400-series, 2 for the AS200 &#38; 250-series) (some
+ISA/PCI slots are physically shared)</p>
+</li>
+
+<li>
+<p>embedded 21040-based Ethernet (200 &#38; 250 series)</p>
+</li>
+
+<li>
+<p>embedded Symbios 53c810 Fast SCSI-2 chip</p>
+</li>
+
+<li>
+<p>Intel 82378IB (``Saturn'') PCI-ISA bridge chip</p>
+</li>
+
+<li>
+<p>graphics is embedded TGA or PCI VGA (model dependent)</p>
+</li>
+
+<li>
+<p>16 bit sound (on 200 &#38; 250 series)</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>The AS200 &#38; AS250 sound hardware is reported to work OK assuming you have the
+following line in your kernel config file:</p>
+
+<pre class="PROGRAMLISTING">
+device pcm0 at isa? port 0x530 irq 10 drq 0 flags 0x10011
+</pre>
+
+<p>AlphaStation 200 &#38; 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.</p>
+
+<p>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</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">SET CONTROL_SCSI_TERM EXTERNAL</kbd>.
+</pre>
+
+<p>If only internal SCSI devices are present use:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">SET CONTROL_SCSI_TERM INTERNAL</kbd>
+</pre>
+
+<p>For the AlphaStation-[24][05]00 machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_2100_A50
+cpu EV4
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN737" name="AEN737">2.3.8 AlphaStation 500 and 600 (``Alcor''
+&#38; ``Maverick'' for EV5, ``Bret'' for EV56)</a></h4>
+
+<p>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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21164 EV5 CPU at 266, 300, 333, 366, 400, 433, 466, or 500 MHz (AS500) or at 266, 300
+or 333 MHz (AS600)</p>
+</li>
+
+<li>
+<p>21171 (Alcor) or 21172 (Alcor2) core logic chip set</p>
+</li>
+
+<li>
+<p>Cache:</p>
+
+<ul>
+<li>
+<p>2 or 4 Mb L3 / Bcache (AS600 at 266 MHz)</p>
+</li>
+
+<li>
+<p>4 Mb L3 / Bcache (AS600 at 300 MHz)</p>
+</li>
+
+<li>
+<p>2 or 8 Mb L3 / Bcache (8 Mb on 500 MHz version only)</p>
+</li>
+
+<li>
+<p>2 to 16 Mb L3 / Bcache (AS600; 3 cache-SIMM slots)</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>memory buswidth: 256 bits</p>
+</li>
+
+<li>
+<p>AS500 memory:</p>
+
+<ul>
+<li>
+<p>industry standard 72 bit wide buffered Fast Page Mode DIMMs</p>
+</li>
+
+<li>
+<p>8 DIMM slots</p>
+</li>
+
+<li>
+<p>installed in sets of 4</p>
+</li>
+
+<li>
+<p>maximum memory is 1 GB (512 Mb max on 333 MHz CPUs)</p>
+</li>
+
+<li>
+<p>uses ECC</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>AS600 memory:</p>
+
+<ul>
+<li>
+<p>industry standard 36 bit Fast Page Mode SIMMs</p>
+</li>
+
+<li>
+<p>32 SIMM slots</p>
+</li>
+
+<li>
+<p>installed in sets of 8</p>
+</li>
+
+<li>
+<p>maximum memory is 1 GB</p>
+</li>
+
+<li>
+<p>uses ECC</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>Qlogic 1020 based wide SCSI bus (1 bus/chip for AS500, 2 buses/chip for AS600)</p>
+</li>
+
+<li>
+<p>21040 based 10 Mbit Ethernet adapter, both Thinwire and UTP connectors</p>
+</li>
+
+<li>
+<p>expansion:</p>
+
+<ul>
+<li>
+<p>AS500:</p>
+
+<ul>
+<li>
+<p>3 32-bit PCI slots</p>
+</li>
+
+<li>
+<p>1 64-bit PCI slot</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>AS600:</p>
+
+<ul>
+<li>
+<p>2 32-bit PCI slot</p>
+</li>
+
+<li>
+<p>3 64-bit PCI slots</p>
+</li>
+
+<li>
+<p>1 PCI/EISA physically shared slot</p>
+</li>
+
+<li>
+<p>3 EISA slots</p>
+</li>
+
+<li>
+<p>1 PCI and 1 EISA slot are occupied by default</p>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+
+<li>
+<p>21050 PCI-to-PCI bridge chip</p>
+</li>
+
+<li>
+<p>Intel 82375EB PCI-EISA bridge (AS600 only)</p>
+</li>
+
+<li>
+<p>2 16550A serial ports</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>16 bit audio Windows Sound System, in a dedicated slot (AS500) in EISA slot (AS600,
+this is an ISA card)</p>
+</li>
+
+<li>
+<p>PS/2 keyboard and mouse port</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>Beware of ancient SRM versions on AS500. When you see weird SCSI speeds being reported
+by FreeBSD like</p>
+
+<pre class="PROGRAMLISTING">
+cd0 at isp0 bus 0 target 4 lun 0
+cd0: &lt;DEC RRD45   DEC 0436&gt; Removable CD-ROM SCSI-2 device
+cd0: 250.000MB/s transfers (250.000MHz, offset 12)
+</pre>
+
+<p>it is time to do a SRM console firmware upgrade.</p>
+
+<p>AS600 has one Qlogic SCSI chip dedicated to the internal devices whereas the other
+Qlogic SCSI chip is dedicated to external SCSI devices.</p>
+
+<p>In AS500 DIMMs are installed in sets of 4, in ``physically interleaved'' layout. So, a
+bank of 4 DIMMs is <span class="emphasis"><i class="EMPHASIS">not</i></span> 4 physically
+adjacent DIMMs. Note that the DIMMs are <span class="emphasis"><i
+class="EMPHASIS">not</i></span> SDRAM DIMMs.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>AS500 onboard sound can be used by adding a line like</p>
+
+<pre class="PROGRAMLISTING">
+device pcm0 at isa? port? irq 10 drq 0 flags 0x10011
+</pre>
+
+<p>to the kernel configuration file.</p>
+
+<p>Using the ECU I configured my AS500 to use IRQ 10, port 0x530, and drq 0. Note the
+uncommon flags in the kernel configuration.</p>
+
+<p>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 <tt class="FILENAME">/boot/loader.rc</tt>:</p>
+
+<pre class="PROGRAMLISTING">
+set isp_mem_map=0xff
+</pre>
+
+<p>This may need to be typed at the boot loader prompt before booting the installation
+kernel.</p>
+
+<p>For the AlphaStation-[56]00 machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_KN20AA 
+cpu EV5
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN848" name="AEN848">2.3.9 AlphaServer 1000 (``Mikasa''), 1000A
+(``Noritake'') and 800(``Corelle'')</a></h4>
+
+<p>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.</p>
+
+<p>AlphaServer 800 has a much smaller mini tower case, it lacks the StorageWorks SCSI
+hot-plug chassis. 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.</p>
+
+<p>AS800 with an EV5/400 MHz CPU was later re-branded to become a ``DIGITAL Server
+3300[R]'', AS800 with an EV5/500 MHz CPU was later re-branded to become a ``DIGITAL
+Server 3305[R]''.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>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)</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>buswidth: 128 bit with ECC</p>
+</li>
+
+<li>
+<p>AS1000[A]:</p>
+
+<ul>
+<li>
+<p>72pin 36 bit Fast Page Mode SIMMs, 70ns or better</p>
+</li>
+
+<li>
+<p>16 (EV5 machines) or 20 (EV4 machines) SIMM slots</p>
+</li>
+
+<li>
+<p>max memory is 1 GB</p>
+</li>
+
+<li>
+<p>uses ECC</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>AS800: Uses 60ns 3.3 Volts EDO DIMMs</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>embedded VGA (on some mainboard models)</p>
+</li>
+
+<li>
+<p>3 PCI, 2 EISA, 1 64-bit PCI/EISA combo (AS800)</p>
+</li>
+
+<li>
+<p>7 PCI, 2 EISA (AS1000A)</p>
+</li>
+
+<li>
+<p>2 PCI, 1 EISA/PCI, 7 EISA (AS1000)</p>
+</li>
+
+<li>
+<p>embedded SCSI based on Symbios 810 [AS1000] or Qlogic 1020 [AS1000A]</p>
+</li>
+</ul>
+
+<p>AS1000 based machines come in multiple enclosure types. Floor standing, rack-mount,
+with or without StorageWorks SCSI chassis etc. The electronics are the same.</p>
+
+<p>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.</p>
+
+<p>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 these are EDO DIMMs.</p>
+
+<p>The AS1000/800 are somewhat stubborn when it comes to serial consoles. They need</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt; <kbd class="USERINPUT">SET CONSOLE SERIAL</kbd>
+</pre>
+
+<p>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</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt; <kbd class="USERINPUT">SET CONSOLE GRAPHICS</kbd>
+</pre>
+
+<p>at the serial console.</p>
+
+<p>For AS800 you want to check if your Ultra-Wide SCSI is indeed in Ultra mode. This can
+be done using the <tt class="FILENAME">EEROMCFG.EXE</tt> utility that is on the Console
+Firmware Upgrade CDROM.</p>
+
+<p>For the AlphaServer1000/1000A/800 machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_1000A
+cpu EV4     # depends on the CPU model installed
+cpu EV5     # depends on the CPU model installed
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN904" name="AEN904">2.3.10 DS10/VS10/XP900 (``Webbrick'') /
+XP1000 (``Monet'') / DS10L (``Slate'')</a></h4>
+
+<p>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)</p>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN910" name="AEN910">2.3.10.1 ``Webbrick / Slate''</a></h5>
+
+<ul>
+<li>
+<p>21264 EV6 CPU at 466 MHz</p>
+</li>
+
+<li>
+<p>L2 / Bcache: 2MB, ECC protected</p>
+</li>
+
+<li>
+<p>memory bus: 128 bit via crossbar, 1.3GB/sec memory bandwidth</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>industry standard 200 pin 83 MHz buffered ECC SDRAM DIMMs</p>
+</li>
+
+<li>
+<p>4 DIMM slots for DS10; 2GB max memory</p>
+</li>
+
+<li>
+<p>2 DIMM slots for DS10L; 1GB max memory</p>
+</li>
+
+<li>
+<p>DIMMs are installed in pairs of 2</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>21271 Core Logic chipset (``Tsunami'')</p>
+</li>
+
+<li>
+<p>2 on-board 21143 Fast Ethernet controllers</p>
+</li>
+
+<li>
+<p>AcerLabs M5237 (Aladdin-V) USB controller (disabled)</p>
+</li>
+
+<li>
+<p>AcerLabs M1533 PCI-ISA bridge</p>
+</li>
+
+<li>
+<p>AcerLabs Aladdin ATA-33 controller</p>
+</li>
+
+<li>
+<p>embedded dual EIDE</p>
+</li>
+
+<li>
+<p>expansion: 3 64-bit PCI slots and 1 32-bit PCI slot. DS10L has a single 64bit PCI
+slot</p>
+</li>
+
+<li>
+<p>2 16550A serial ports</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>2 USB</p>
+</li>
+
+<li>
+<p>PS/2 keyboard &#38; mouse port</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>The smart power controller is called the RMC. When enabled, typing <b
+class="KEYCAP">Escape</b><b class="KEYCAP">Escape</b>RMC 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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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</p>
+
+<p>On the PCI bus 32 and 64 bit cards are supported, in 3.3V and 5V variants.</p>
+
+<p>The USB ports are not supported and are disabled by the SRM console in all recent SRM
+versions.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_ST6600    
+cpu EV5
+</pre>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Contrary to expectation there is no <var class="LITERAL">cpu EV6</var>
+defined for inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var>
+is mandatory to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN975" name="AEN975">2.3.10.2 ``Monet''</a></h5>
+
+<ul>
+<li>
+<p>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</p>
+</li>
+
+<li>
+<p>L2 / Bcache: 4MB, ECC protected</p>
+</li>
+
+<li>
+<p>memory bus: 256 bit</p>
+</li>
+
+<li>
+<p>memory: 128 or 256 Mbytes 100 MHz (PC100) 168 pin JEDEC standard, registered ECC SDRAM
+DIMMs</p>
+</li>
+
+<li>
+<p>21271 core logic chip set (``Tsunami'')</p>
+</li>
+
+<li>
+<p>1 on-board 21143 Ethernet controller</p>
+</li>
+
+<li>
+<p>Cypress 82C693 USB controller</p>
+</li>
+
+<li>
+<p>Cypress 82C693 PCI-ISA bridge</p>
+</li>
+
+<li>
+<p>Cypress 82C693 controller</p>
+</li>
+
+<li>
+<p>expansion: 2 independent PCI buses, driven by high-speed I/O channels called
+``hoses'':</p>
+
+<ul>
+<li>
+<p>hose 0: (the upper 3 slots) 2 64-bit PCI slots 1 32-bit PCI slot</p>
+</li>
+
+<li>
+<p>hose 1: (the bottom 2 slots) 2 32-bit PCI slots (behind a 21154 PCI-PCI bridge)</p>
+</li>
+
+<li>
+<p>2 of the 64-bit PCI slots are for full-length cards</p>
+</li>
+
+<li>
+<p>all of the 32-bit PCI slots are for short cards</p>
+</li>
+
+<li>
+<p>1 of the 32-bit PCI slots is physically shared with an ISA slot</p>
+</li>
+
+<li>
+<p>all PCI slots run at 33MHz</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>1 Ultra-Wide SCSI port based on a Qlogic 1040 chip</p>
+</li>
+
+<li>
+<p>2 16550A serial port</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>PS/2 keyboard &#38; mouse port</p>
+</li>
+
+<li>
+<p>embedded 16-bit ESS ES1888 sound chip</p>
+</li>
+
+<li>
+<p>2 USB ports</p>
+</li>
+
+<li>
+<p>graphics options: ELSA Gloria Synergy or DEC/Compaq PowerStorm 3D accelerator
+cards</p>
+</li>
+</ul>
+
+<p>Monet is housed in a mini-tower like enclosure quite similar to the Miata box.</p>
+
+<p>The on-board Qlogic UW-SCSI chip supports up to 4 internal devices. There is no
+external connector for the on-board SCSI.</p>
+
+<p>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)</p>
+
+<p>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.</p>
+
+<p>The USB interface is supported by FreeBSD.If you experience problems trying to use the
+USB interface please check if the SRM variable <var class="VARNAME">usb_enable</var> is
+set to <var class="LITERAL">on</var>. You can change this by performing:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SET USB_ENABLE ON</kbd>
+</pre>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> Don&quot;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.</p>
+</blockquote>
+</div>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> 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.</p>
+</blockquote>
+</div>
+
+<p>The sound chip is not currently supported with FreeBSD.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_ST6600    
+cpu EV5
+</pre>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Contrary to expectation there is no <var class="LITERAL">cpu EV6</var>
+defined for inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var>
+is mandatory to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</blockquote>
+</div>
+</div>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1055" name="AEN1055">2.3.11 DS20/DS20E
+(``Goldrush'')</a></h4>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21264 EV6 CPU at 500 or 670 MHz</p>
+</li>
+
+<li>
+<p>dual CPU capable machine</p>
+</li>
+
+<li>
+<p>L2 / Bcache: 4 Mbytes per CPU</p>
+</li>
+
+<li>
+<p>memory bus: dual 256 bit wide with crossbar switch</p>
+</li>
+
+<li>
+<p>memory:</p>
+
+<ul>
+<li>
+<p>SDRAM DIMMs</p>
+</li>
+
+<li>
+<p>installed in sets of 4</p>
+</li>
+
+<li>
+<p>16 DIMM slots, max. 4GB</p>
+</li>
+
+<li>
+<p>uses ECC</p>
+</li>
+</ul>
+</li>
+
+<li>
+<p>21271 core logic chip set (``Tsunami'')</p>
+</li>
+
+<li>
+<p>embedded Adaptec ? Wide Ultra SCSI</p>
+</li>
+
+<li>
+<p>expansion:</p>
+
+<ul>
+<li>
+<p>2 independent PCI buses, driven by high-speed I/O channels called ``hoses''</p>
+</li>
+
+<li>
+<p>6 64-bit PCI slots, 3 per hose</p>
+</li>
+
+<li>
+<p>1 ISA slot</p>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>DS20 needs</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SET CONSOLE SERIAL</kbd>
+</pre>
+
+<p>before it goes for a serial console. Pulling the keyboard from the machine is not
+sufficient. Going back to a graphical console needs</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">SET CONSOLE GRAPHICS</kbd>
+</pre>
+
+<p>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
+<var class="LITERAL">CONSOLE</var> variable setting and all the boot messages as well as
+the login prompt will go to the serial port.</p>
+
+<p>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&quot; SCSI devices. The DS20E
+is in a sleeker case, and lacks the StorageWorks shelf.</p>
+
+<p>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(s).</p>
+
+<p>The smart power controller is called the RMC. When enabled, typing <b
+class="KEYCAP">Escape</b><b class="KEYCAP">Escape</b>RMC 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.</p>
+
+<p>The embedded Adaptec SCSI chip on the DS20 is disabled and is therefore not usable
+under FreeBSD.</p>
+
+<p>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.</p>
+
+<p>If you are using banks of DIMMs of different sizes the biggest DIMMs should be
+installed in the DIMM slots marked <var class="LITERAL">0</var> on the mainboard. The
+DIMM slots should be filled ``in order'' so after bank 0 install in bank 1 and so on.</p>
+
+<p>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.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_ST6600    
+cpu EV5
+</pre>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Contrary to expectation there is no <var class="LITERAL">cpu EV6</var>
+defined for inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var>
+is mandatory to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1124" name="AEN1124">2.3.12 AlphaPC 264DP / UP2000</a></h4>
+
+<p>UP2000 was built by Alpha Processor Inc.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21264 EV6 CPU at 670 or 750 MHz</p>
+</li>
+
+<li>
+<p>dual CPU capable</p>
+</li>
+
+<li>
+<p>L2 / Bcache: 4 Mbytes per CPU</p>
+</li>
+
+<li>
+<p>memory bus: 256 bit</p>
+</li>
+
+<li>
+<p>memory: SDRAM DIMMs installed in sets of 4, uses ECC, 16 DIMM slots, max. 4GB</p>
+</li>
+
+<li>
+<p>21272 core logic chip set (``Tsunami'')</p>
+</li>
+
+<li>
+<p>2 embedded Adaptec AIC7890/91 Wide Ultra2 SCSI chips</p>
+</li>
+
+<li>
+<p>2 embedded IDE based on Cypress 82C693 chips</p>
+</li>
+
+<li>
+<p>embedded USB via Cypress 82C693</p>
+</li>
+
+<li>
+<p>expansion:</p>
+
+<ul>
+<li>
+<p>2 independent PCI buses, driven by high-speed I/O channels called ``hoses''</p>
+</li>
+
+<li>
+<p>6 64-bit PCI slots, 3 per hose</p>
+</li>
+
+<li>
+<p>1 ISA slot</p>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>Currently a maximum of 2GB memory is supported by FreeBSD.</p>
+
+<p>The on-board Adaptec SCSI HBAs are bootable on UP2000.</p>
+
+<p>Busmaster DMA is supported on the first IDE interface only. The system can boot from
+it's IDE hard drives and cdrom drives.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_ST6600    
+cpu EV5
+</pre>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Contrary to expectation there is no <var class="LITERAL">cpu EV6</var>
+defined for inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var>
+is mandatory to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1170" name="AEN1170">2.3.13 AlphaServer 2000 (``DemiSable''),
+2100 (``Sable''), 2100A (``Lynx'')</a></h4>
+
+<p>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&quot; 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.</p>
+
+<ul>
+<li>
+<p>21064 EV4[5] CPU[s] at 200, 233, 275 MHz or 21164 EV5[6] CPU[s]s at 250, 300, 375, 400
+MHz</p>
+</li>
+
+<li>
+<p>cache: varies in size with the CPU model; 1, 4 or 8Mbyte per CPU</p>
+</li>
+
+<li>
+<p>embedded floppy controller driving a 2.88 Mbytes drive</p>
+</li>
+
+<li>
+<p>embedded 10Mbit 21040 Ethernet [AS2100 only]</p>
+</li>
+
+<li>
+<p>2 serial ports</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>PS/2 style keyboard &#38; mouse port</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>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</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">CLEAR_ERROR ALL</kbd>
+</pre>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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''.</p>
+
+<p>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..)</p>
+
+<p>Both Lynx and Sable are somewhat stubborn when it comes to serial consoles. They
+need</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SET CONSOLE SERIAL</kbd>
+</pre>
+
+<p>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</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">SET CONSOLE GRAPHICS</kbd>
+</pre>
+
+<p>at the serial console. On Lynx keep the VGA card in one of the primary PCI slots. EISA
+VGA cards are not slot sensitive.</p>
+
+<p>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:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SET OCP_TEXT "FreeBSD"
+     </kbd>
+</pre>
+
+<p>The SRM</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SHOW FRU</kbd>
+</pre>
+
+<p>command produces an overview of your configuration with module serial numbers,
+hardware revisions and error log counts.</p>
+
+<p>Both Sable, DemiSable and Lynx have Symbios 810 based Fast SCSI on-board. Check if it
+is set to Fast SCSI speed by</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SHOW PKA0_FAST</kbd>
+</pre>
+
+<p>When set to 1 it is negotiating for Fast speeds.</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">SET PKA0_FAST 1</kbd>
+</pre>
+
+<p>enables Fast SCSI speeds.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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).</p>
+
+<p>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</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">RUNECU</kbd>
+</pre>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> 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.</p>
+</blockquote>
+</div>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_2100_A500
+cpu EV4 #dependent on CPU model installed
+cpu EV5 #dependent on CPU model installed
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1241" name="AEN1241">2.3.14 AlphaServer 4x00
+(``Rawhide'')</a></h4>
+
+<p>The AlphaServer 4x00 machines are intended as small enterprise servers. Expect a
+30&quot; high pedestal cabinet or alternatively the same system box in a 19&quot; 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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21164 EV5 CPUs at 266, 300, 333 MHz or 21164A EV56 CPUs at 400, 466, 533, 600 Mhz</p>
+</li>
+
+<li>
+<p>cache: 4 Mbytes per CPU. EV5 300 MHz was also available cache-less. 8 Mbytes for EV56
+600Mhz</p>
+</li>
+
+<li>
+<p>memory bus: 128 bit with ECC</p>
+</li>
+
+<li>
+<p>embedded floppy controller</p>
+</li>
+
+<li>
+<p>2 serial ports</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>PS/2 style keyboard &#38; mouse port</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<p>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
+<span class="emphasis"><i class="EMPHASIS">entire</i></span> memory subsystem running at
+the slower EDO timing.</p>
+
+<p>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.</p>
+
+<p>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
+an Symbios 810 SCSI chip. VGA console cards must be installed in a slot connected to
+PCI0.</p>
+
+<p>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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> 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.</p>
+</blockquote>
+</div>
+
+<p>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.</p>
+
+<p>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
+interchangably. 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.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_KN300
+cpu EV5
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1274" name="AEN1274">2.3.15 AlphaServer 1200 (``Tincup'') and
+AlphaStation 1200 (``DaVinci'')</a></h4>
+
+<p>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).</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21164A EV56 CPUs at 400 or 533 Mhz</p>
+</li>
+
+<li>
+<p>cache: 4 Mbytes per CPU</p>
+</li>
+
+<li>
+<p>memory bus: 128 bit with ECC, DIMM memory on two memory daughter boards</p>
+</li>
+
+<li>
+<p>embedded floppy controller</p>
+</li>
+
+<li>
+<p>2 serial ports</p>
+</li>
+
+<li>
+<p>1 parallel port</p>
+</li>
+
+<li>
+<p>PS/2 style keyboard &#38; mouse port</p>
+</li>
+</ul>
+
+<p>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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> FreeBSD currently supports up to 2GBytes</p>
+</blockquote>
+</div>
+
+<p>AS1200 has an embedded Symbios 810 drive Fast SCSI bus.</p>
+
+<p>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 an Symbios 810 SCSI chip. VGA console
+cards must be installed in a slot connected to PCI0.</p>
+
+<p>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.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_KN300
+cpu EV5
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1304" name="AEN1304">2.3.16 AlphaServer 8200 and 8400
+(``TurboLaser'')</a></h4>
+
+<p>The AlphaServer 8200 and 8400 machines are enterprise servers. Expect a tall 19&quot;
+cabinet (8200) or fat (8400) 19&quot; rack. This is big iron, not a hobbyist system.
+TurboLasers are multi-CPU machines, up to 12 CPUs can be in a single machine. The
+TurboLaser System Bus (TLSB) allows 9 nodes on the AS8400 and 5 nodes on the AS8200. TLSB
+is 256 bit data, 40 bit address allowing 2.1 GBytes/sec. Nodes on the TLSB can be CPUs,
+memory or I/O. A maximum of 3 I/O ports are supported on a TLSB.</p>
+
+<p>Basic disk storage is housed in a StorageWorks shelf. AS8400 uses 3 phase power,
+AS8200 uses single phase power.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21164 EV5/EV56 CPUs at up to 467 MHz or 21264 EV67 CPUs at up to 625 MHz</p>
+</li>
+
+<li>
+<p>one or two CPUs per CPU module</p>
+</li>
+
+<li>
+<p>cache: 4Mbytes B-cache per CPU</p>
+</li>
+
+<li>
+<p>memory bus: 256 bit with ECC</p>
+</li>
+
+<li>
+<p>memory: big memory modules that plug into the TLSB, which in turn hold special SIMM
+modules. Memory modules come in varying sizes, up to 4 GBytes a piece. Uses ECC (8 bits
+per 64 bits of data) 7 memory modules max for AS8400, 3 modules max for AS8200. Maximum
+memory is 28 GBytes.</p>
+</li>
+
+<li>
+<p>expansion: 3 system ``I/O ports'' that allow up to 12 I/O channels each I/O channel
+can connect to XMI, Futurebus+ or PCI boxes</p>
+</li>
+</ul>
+
+<p>FreeBSD supports (and has been tested with) up to 2 GBytes of memory on TurboLaser.
+There is a trade-off to be made between TLSB slots occupied by memory modules and TLSB
+slots occupied by CPU modules. For example you can have 28GBytes of memory but only 2
+CPUs (1 module) at the same time.</p>
+
+<p>Only PCI expansion is supported on FreeBSD. XMI or Futurebus+ (which are AS8400 only)
+are both unsupported.</p>
+
+<p>The I/O port modules are designated KFTIA or KFTHA. The I/O port modules supply so
+called ``hoses'' that connect to up to 4 (KFTHA) PCI buses or 1 PCI bus (KFTIA). KFTIA
+has embedded dual 10baseT Ethernet, single FDDI, 3 SCSI Fast Wide Differential SCSI buses
+and a single Fast Wide Single Ended SCSI bus. The FWSE SCSI is intended for the
+CDROM.</p>
+
+<p>KFTHA can drive via each of its 4 hoses a DWLPA or DWLPB box. The DWLPx house a 12
+slots 32 bit PCI backplane. Physically the 12 slots are 3 4-slot buses but to the
+software it appears as a single 12 slots PCI bus. A fully expanded AS8x00 can have 3 (I/O
+ports) times 4 (hoses) times 12 (PCI slots/DWLPx) = 144 PCI slots. The maximum bandwidth
+per KFTHA is 500 Mbytes/second. DWLPA can also house 8 EISA cards, 2 slots are PCI-only,
+2 slots are EISA only. Of the 12 slots 2 are always occupied by an I/O and connector
+module. DWLPB are the prefered I/O boxes.</p>
+
+<p>For best performance distribute high bandwidth (FibreChannel, Gigabit Ethernet) over
+multiple hoses and/or multiple KFTHA/KFTIA.</p>
+
+<p>Currently PCI expansion cards containing PCI bridges are not usable with FreeBSD.
+Don't use them at this time.</p>
+
+<p>The single ended narrow SCSI bus on the KFTIA will turn up as the <span
+class="emphasis"><i class="EMPHASIS">fourth</i></span> SCSI bus. The 3 fast-wide
+differential SCSI buses of the KFTIA precede it.</p>
+
+<p>AS8x00 are generally run with serial consoles. Some newer machines might have a
+graphical console of some sorts but FreeBSD has only been tested on a serial console.</p>
+
+<p>For serial console usage either change <tt class="FILENAME">/etc/ttys</tt> to
+have:</p>
+
+<pre class="PROGRAMLISTING">
+console "/usr/libexec/getty std.9600"   unknown   on secure
+</pre>
+
+<p>as the console entry, or add</p>
+
+<pre class="PROGRAMLISTING">
+zs0     "/usr/libexec/getty std.9600"   unknown   on secure
+</pre>
+
+<p>For the AlphaServer 8x00 machines the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_KN8AE   # Alpha 8200/8400 (Turbolaser)
+cpu EV5
+</pre>
+
+<p>Contrary to expectation there is no <var class="LITERAL">cpu EV6</var> defined for
+inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var> is mandatory
+to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1347" name="AEN1347">2.3.17 Alpha Processor Inc.
+UP1000</a></h4>
+
+<p>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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21264a Alpha CPU at 600 or 700 MHz in a Slot B module (includes cooling fans)</p>
+</li>
+
+<li>
+<p>memory bus: 128 bits to the L2 cache, 64 bits from Slot B to the AMD-751</p>
+</li>
+
+<li>
+<p>on-board Bcache / L2 cache: 2MB (600Mhz) or 4MB (700Mhz)</p>
+</li>
+
+<li>
+<p>AMD AMD-751 (``Irongate'') system controller chip</p>
+</li>
+
+<li>
+<p>Acer Labs M1543C PCI-ISA bridge controller / super-IO chip</p>
+</li>
+
+<li>
+<p>PS/2 mouse &#38; keyboard port</p>
+</li>
+
+<li>
+<p>memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 DIMM slots DIMM sizes supported are
+64, 128 or 256 Mb in size</p>
+</li>
+
+<li>
+<p>2 16550A serial port</p>
+</li>
+
+<li>
+<p>1 ECP/EPP parallel port</p>
+</li>
+
+<li>
+<p>floppy interface</p>
+</li>
+
+<li>
+<p>2 embedded Ultra DMA33 IDE interface</p>
+</li>
+
+<li>
+<p>2 USB ports</p>
+</li>
+
+<li>
+<p>expansion:</p>
+
+<ul>
+<li>
+<p>4 32 bit PCI slots</p>
+</li>
+
+<li>
+<p>2 ISA slots</p>
+</li>
+
+<li>
+<p>1 AGP slot</p>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>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..</p>
+
+<p>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 <span
+class="emphasis"><i class="EMPHASIS">2</i></span>. This is a bit counter-intuitive.</p>
+
+<p>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
+&#38; cpu. But as always you will have to take your expansion cards and peripherals into
+account. The M1543C chip contains power management functionality &#38; temperature
+monitoring (via I2C / SM bus).</p>
+
+<p>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.</p>
+
+<p>The embedded Ultra DMA EIDE ports are bootable by the SRM console.</p>
+
+<p>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.</p>
+
+<p>The USB interfaces are disabled by the SRM console and have not (yet) been tested with
+FreeBSD.</p>
+
+<p>For the UP1000 the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    API_UP1000  # UP1000, UP1100 (Nautilus)
+cpu EV5
+</pre>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1396" name="AEN1396">2.3.18 Alpha Processor Inc.
+UP1100</a></h4>
+
+<p>The UP1100 is an ATX mainboard based on the 21264a CPU running at 600 MHz. It is
+normally housed in an ATX tower enclosure.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21264a Alpha EV6 CPU at 600 or 700 MHz</p>
+</li>
+
+<li>
+<p>memory bus: 100MHz 64-bit (PC-100 SDRAM), 800 MB/s memory bandwidth</p>
+</li>
+
+<li>
+<p>on-board Bcache / L2 cache: 2Mb</p>
+</li>
+
+<li>
+<p>AMD AMD-751 (``Irongate'') system controller chip</p>
+</li>
+
+<li>
+<p>Acer Labs M1535D PCI-ISA bridge controller / super-IO chip</p>
+</li>
+
+<li>
+<p>PS/2 mouse &#38; keyboard port</p>
+</li>
+
+<li>
+<p>memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 DIMM slots DIMM sizes supported are
+64, 128 or 256 Mb in size</p>
+</li>
+
+<li>
+<p>2 16550A serial port</p>
+</li>
+
+<li>
+<p>1 ECP/EPP parallel port</p>
+</li>
+
+<li>
+<p>floppy interface</p>
+</li>
+
+<li>
+<p>2 embedded Ultra DMA66 IDE interface</p>
+</li>
+
+<li>
+<p>2 USB port</p>
+</li>
+
+<li>
+<p>expansion: 3 32 bit PCI slots and 1 AGP2x slot</p>
+</li>
+</ul>
+
+<p>SRM console code comes standard with the UP1100. The SRM lives in 2Mbytes of flash
+ROM.</p>
+
+<p>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 <span
+class="emphasis"><i class="EMPHASIS">2</i></span>. This is a bit counter-intuitive.</p>
+
+<p>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
+&#38; cpu. But as always you will have to take your expansion cards and peripherals into
+account. The M1535D chip contains power management functionality &#38; temperature
+monitoring (via I2C / SM bus using a LM75 thermal sensor).</p>
+
+<p>The UP1100 has an on-board 21143 10/100Mbit Ethernet interface.</p>
+
+<p>The UP1100 is equipped with a SoundBlaster compatible audio interface. Whether it
+works with FreeBSD is as of yet unknown.</p>
+
+<p>The embedded Ultra DMA EIDE ports are bootable by the SRM console.</p>
+
+<p>The UP1100 has 3 USB ports, 2 going external and one connected to the AGP port.</p>
+
+<p>For the UP1100 the kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    API_UP1000  # UP1000, UP1100 (Nautilus)
+cpu EV5
+</pre>
+
+<p>Contrary to expectation there is no <var class="LITERAL">cpu EV6</var> defined for
+inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var> is mandatory
+to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1444" name="AEN1444">2.3.19 Alpha Processor Inc. CS20, Compaq
+DS20L</a></h4>
+
+<p>The CS20 is a 19&quot;, 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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21264a Alpha CPU at 667 MHz or 21264b 833 MHz (max. 2 CPUs)</p>
+</li>
+
+<li>
+<p>memory bus: 100MHz 256-bit wide</p>
+</li>
+
+<li>
+<p>21271 Core Logic chipset (``Tsunami'')</p>
+</li>
+
+<li>
+<p>Acer Labs M1533 PCI-ISA bridge controller / super-IO chip</p>
+</li>
+
+<li>
+<p>PS/2 mouse &#38; keyboard port</p>
+</li>
+
+<li>
+<p>memory: 168-pin PC100 PLL buffered/registered SDRAM DIMMS, 8 DIMM slots, uses ECC
+memory, min 256 Mbytes / max 2 GBytes of memory</p>
+</li>
+
+<li>
+<p>2 16550A serial port</p>
+</li>
+
+<li>
+<p>1 ECP/EPP parallel port</p>
+</li>
+
+<li>
+<p>ALI M1543C Ultra DMA66 IDE interface</p>
+</li>
+
+<li>
+<p>embedded dual Intel 82559 10/100Mbit Ethernet</p>
+</li>
+
+<li>
+<p>embedded Symbios 53C1000 Ultra160 SCSI controller</p>
+</li>
+
+<li>
+<p>expansion: 2 64 bit PCI slots (2/3 length)</p>
+</li>
+</ul>
+
+<p>SRM console code comes standard with the CS20. The SRM lives in 2Mbytes of flash
+ROM.</p>
+
+<p>The CS20 needs ECC capable DIMMs. Note that it uses <span class="emphasis"><i
+class="EMPHASIS">buffered</i></span> DIMMs.</p>
+
+<p>The CS20 has an I2C based internal monitoring system for things like temperature,
+fans, voltages etc. The I2C also supports ``wake on LAN''.</p>
+
+<p>Each PCI slot is connected to its own independent PCI bus on the Tsunami.</p>
+
+<p>The embedded Ultra DMA EIDE ports are bootable by the SRM console.</p>
+
+<p>The CS20 has an embedded slim-line IDE CD drive. There is a front-accessible bay for a
+1&quot; high 3.5&quot; SCSI hard-disk drive with SCA connector.</p>
+
+<p>Note that there is no floppy disk drive (or a connector to add one).</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options    DEC_ST6600
+cpu EV5
+</pre>
+
+<p>Contrary to expectation there is no <var class="LITERAL">cpu EV6</var> defined for
+inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var> is mandatory
+to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN1491" name="AEN1491">2.3.20 Compaq AlphaServer ES40
+(``Clipper'')</a></h4>
+
+<p>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.</p>
+
+<p>Features:</p>
+
+<ul>
+<li>
+<p>21264 Alpha CPU at 500 (EV6), 667 (EV67) or 833 MHz (EV68) (max. 4 CPUs)</p>
+</li>
+
+<li>
+<p>memory bus: 256-bit wide</p>
+</li>
+
+<li>
+<p>21272 Core Logic chipset</p>
+</li>
+
+<li>
+<p>PS/2 mouse &#38; keyboard port</p>
+</li>
+
+<li>
+<p>memory: 200-pin JEDEC standard SDRAM DIMMS, max 32 GBytes of memory</p>
+</li>
+
+<li>
+<p>2 16550A serial port</p>
+</li>
+
+<li>
+<p>1 ECP/EPP parallel port</p>
+</li>
+
+<li>
+<p>ALI M1543C Ultra DMA66 IDE interface</p>
+</li>
+
+<li>
+<p>expansion: 2 64 bit PCI buses</p>
+</li>
+</ul>
+
+<p>SRM console code comes standard with the ES40.</p>
+
+<p>ES40 comes with an ATA CDROM drive, but uses SCSI harddisks. The usual Symbios &#38;
+Qlogic adapters are bootable, as is the KZPEA aka Adaptec 39160 dual channel LVD U160
+adapter.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>The kernel config file must contain:</p>
+
+<pre class="PROGRAMLISTING">
+options   DEC_ST6600
+cpu     EV5
+</pre>
+
+<p>Contrary to expectation there is no <var class="LITERAL">cpu EV6</var> defined for
+inclusion in the kernel config file. The <var class="LITERAL">cpu EV5</var> is mandatory
+to keep <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=config&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a>
+happy.</p>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1528" name="AEN1528">2.4 Supported Hardware Overview</a></h3>
+
+<p>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. <tt class="FILENAME">GENERIC</tt> contains things that are
+known to work on Alpha only.</p>
+
+<p>The PCI and ISA expansion busses are fully supported. Turbo Channel is not in <tt
+class="FILENAME">GENERIC</tt> 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.</p>
+
+<p>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.</p>
+
+<p>ATA and ATAPI (IDE) devices are supported via the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> 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.</p>
+
+<p>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.</p>
+
+<p>The Qlogic QL2x00 FibreChannel host adapters are fully supported.</p>
+
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=de&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a> (older
+driver) or <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> (newer
+driver). Some new SRM versions are known to recognize the Intel 8255x Ethernet chips as
+driven by the FreeBSD <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver.
+But beware: the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver is
+reported not to work correctly with FreeBSD (although it works excellently on
+FreeBSD/x86).</p>
+
+<p>DEC DEFPA PCI FDDI network adapters are supported on alpha.</p>
+
+<p>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.</p>
+
+<p>In some Alpha machines you will find video adapters based on TGA chips. The plain TGA
+adapter does not emulate VGA and is therefore not usable for a FreeBSD console. TGA2
+cards have a basic VGA compatibility mode and work fine as FreeBSD consoles.</p>
+
+<p>The ``PC standard'' serial ports found on most Alphas are supported. For TurboChannel
+machines the serial ports are also supported.</p>
+
+<p>ISDN (i4b) is not supported on FreeBSD/alpha.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1560" name="AEN1560">2.5 Acknowledgments</a></h3>
+
+<p>In compiling this file I used multiple information sources, but <a
+href="http://www.netbsd.org/" target="_top">the NetBSD Web site</a> 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.</p>
+
+<p>People who kindly helped me create this section:</p>
+
+<ul>
+<li>
+<p>Andrew Gallatin <code class="EMAIL">&#60;<a
+href="mailto:gallatin@FreeBSD.org">gallatin@FreeBSD.org</a>&#62;</code></p>
+</li>
+
+<li>
+<p>Chuck Robey <code class="EMAIL">&#60;<a
+href="mailto:chuckr@FreeBSD.org">chuckr@FreeBSD.org</a>&#62;</code></p>
+</li>
+
+<li>
+<p>Matthew Jacob <code class="EMAIL">&#60;<a
+href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&#62;</code></p>
+</li>
+
+<li>
+<p>Michael Smith <code class="EMAIL">&#60;<a
+href="mailto:msmith@FreeBSD.org">msmith@FreeBSD.org</a>&#62;</code></p>
+</li>
+
+<li>
+<p>David O'Brien <code class="EMAIL">&#60;<a
+href="mailto:obrien@FreeBSD.org">obrien@FreeBSD.org</a>&#62;</code></p>
+</li>
+
+<li>
+<p>Christian Weisgerber</p>
+</li>
+
+<li>
+<p>Kazutaka YOKOTA</p>
+</li>
+
+<li>
+<p>Nick Maniscalco</p>
+</li>
+
+<li>
+<p>Eric Schnoebelen</p>
+</li>
+
+<li>
+<p>Peter van Dijk</p>
+</li>
+
+<li>
+<p>Peter Jeremy</p>
+</li>
+
+<li>
+<p>Dolf de Waal</p>
+</li>
+
+<li>
+<p>Wim Lemmers, ex-Compaq</p>
+</li>
+
+<li>
+<p>Wouter Brackman, Compaq</p>
+</li>
+
+<li>
+<p>Lodewijk van den Berg, Compaq</p>
+</li>
+</ul>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN1601" name="AEN1601">3 Supported Devices</a></h2>
+
+$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.13.2.90 2003/10/01
+20:36:57 simon Exp $
+
+<p>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.</p>
+
+<p>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.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1607" name="AEN1607">3.1 Disk Controllers</a></h3>
+
+<p>IDE/ATA controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Acerlabs Aladdin</p>
+</li>
+
+<li>
+<p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p>
+</li>
+
+<li>
+<p>Cenatek Rocket Drive</p>
+</li>
+
+<li>
+<p>CMD 646, 648 ATA66, and 649 ATA100</p>
+</li>
+
+<li>
+<p>Cypress 82C693</p>
+</li>
+
+<li>
+<p>Cyrix 5530 ATA33</p>
+</li>
+
+<li>
+<p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 ATA133, HPT374 ATA133</p>
+</li>
+
+<li>
+<p>Intel PIIX, PIIX3, PIIX4</p>
+</li>
+
+<li>
+<p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 ATA100</p>
+</li>
+
+<li>
+<p>nVidia nForce ATA100</p>
+</li>
+
+<li>
+<p>Promise ATA100 OEM chip (pdc20265)</p>
+</li>
+
+<li>
+<p>Promise ATA133 OEM chip (pdc20269)</p>
+</li>
+
+<li>
+<p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000</p>
+</li>
+
+<li>
+<p>Promise Ultra-33, -66, -100, -133 TX2/TX2000</p>
+</li>
+
+<li>
+<p>ServerWorks ROSB4 ATA33</p>
+</li>
+
+<li>
+<p>ServerWorks CSB5 ATA66/ATA100</p>
+</li>
+
+<li>
+<p>Sil 0680 UDMA6</p>
+</li>
+
+<li>
+<p>SiS 530, 540, 620</p>
+</li>
+
+<li>
+<p>SiS 630, 633, 635, 645, 730, 733, 735, 740, 745, 750</p>
+</li>
+
+<li>
+<p>SiS 5591 ATA100</p>
+</li>
+
+<li>
+<p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100</p>
+</li>
+
+<li>
+<p>VIA 8233, 8235 ATA133</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Adaptec SCSI Controllers</p>
+
+<ul>
+<li>
+<p>Adaptec 19160/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x series PCI
+SCSI controllers, including Narrow/Wide/Twin/Ultra/Ultra2 variants (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec AIC7770, AIC7850, AIC7860, AIC7870, AIC7880, and AIC789x on-board SCSI
+controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a>
+driver)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>AMI MegaRAID Express and Enterprise family RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>MegaRAID Series 418</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1200 (Series 428)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1300 (Series 434)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1400 (Series 438)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1500 (Series 467)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1600 (Series 471)</p>
+</li>
+
+<li>
+<p>MegaRAID Elite 1500 (Series 467)</p>
+</li>
+
+<li>
+<p>MegaRAID Elite 1600 (Series 493)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 100 (Series 466WS)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 200 (Series 466)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 300 (Series 490)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 500 (Series 475)</p>
+</li>
+
+<li>
+<p>Dell PERC</p>
+</li>
+
+<li>
+<p>Dell PERC 2/SC</p>
+</li>
+
+<li>
+<p>Dell PERC 2/DC</p>
+</li>
+
+<li>
+<p>Dell PERC 3/DCL</p>
+</li>
+
+<li>
+<p>Dell PERC 4/Di</p>
+</li>
+
+<li>
+<p>HP NetRaid-1si</p>
+</li>
+
+<li>
+<p>HP NetRaid-3si</p>
+</li>
+
+<li>
+<p>HP Embedded NetRaid</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p>Booting from these controllers is not supported due to SRM limitations.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mlx</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>DAC960P</p>
+</li>
+
+<li>
+<p>DAC960PD</p>
+</li>
+
+<li>
+<p>DAC960PDU</p>
+</li>
+
+<li>
+<p>DAC960PL</p>
+</li>
+
+<li>
+<p>DAC960PJ</p>
+</li>
+
+<li>
+<p>DAC960PG</p>
+</li>
+
+<li>
+<p>AcceleRAID 150</p>
+</li>
+
+<li>
+<p>AcceleRAID 250</p>
+</li>
+
+<li>
+<p>eXtremeRAID 1100</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p>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.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C825, 53C825a, 53C860, 53C875,
+53C875a, 53C876, 53C885, 53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000,
+53C1000R PCI SCSI controllers, either embedded on motherboard or on add-on boards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>ASUS SC-200, SC-896</p>
+</li>
+
+<li>
+<p>Data Technology DTC3130 (all variants)</p>
+</li>
+
+<li>
+<p>DawiControl DC2976UW</p>
+</li>
+
+<li>
+<p>Diamond FirePort (all)</p>
+</li>
+
+<li>
+<p>NCR cards (all)</p>
+</li>
+
+<li>
+<p>Symbios cards (all)</p>
+</li>
+
+<li>
+<p>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and 390U3W</p>
+</li>
+
+<li>
+<p>Tyan S1365</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Qlogic controllers and variants (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Qlogic 1020, 1040 SCSI and Ultra SCSI host adapters</p>
+</li>
+
+<li>
+<p>Qlogic 1240 dual Ultra SCSI controllers</p>
+</li>
+
+<li>
+<p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD controllers</p>
+</li>
+
+<li>
+<p>Qlogic 12160 Ultra3 LVD controllers</p>
+</li>
+
+<li>
+<p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI controllers</p>
+</li>
+
+<li>
+<p>Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre Channel SCSI controllers</p>
+</li>
+
+<li>
+<p>Performance Technology SBS440 ISP1000 variants</p>
+</li>
+
+<li>
+<p>Performance Technology SBS450 ISP1040 variants</p>
+</li>
+
+<li>
+<p>Performance Technology SBS470 ISP2100 variants</p>
+</li>
+
+<li>
+<p>Antares Microsystems P-0033 ISP2100 variants</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>LSI Logic Fusion/MP architecture Fiber Channel controllers (mpt driver)</p>
+
+<ul>
+<li>
+<p>LSI FC909, FC929</p>
+</li>
+
+<li>
+<p>LSI 53c1020, 53c1030</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cd</span>(4)</span></a>).
+WORM/CD-R/CD-RW writing support is provided by <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&amp;sektion=1&amp;manpath=FreeBSD+Ports">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cdrecord</span>(1)</span></a>,
+which is a part of the <a
+href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr"><tt
+class="FILENAME">sysutils/cdrtools</tt></a> port in the Ports Collection.</p>
+
+<p>The following CD-ROM type systems are supported at this time:</p>
+
+<ul>
+<li>
+<p>SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cd</span>(4)</span></a>)</p>
+</li>
+
+<li>
+<p>ATAPI IDE interface (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=acd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acd</span>(4)</span></a>)</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 Ethernet Interfaces</a></h3>
+
+<p>Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast
+Ethernet controller chip (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sf</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>ANA-62011 64-bit single port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-62022 64-bit dual port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-62044 64-bit quad port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-69011 32-bit single port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-62020 64-bit single port 100baseFX adapter</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>AMD PCnet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcn</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>AMD PCnet/PCI (79c970 &#38; 53c974 or 79c974)</p>
+</li>
+
+<li>
+<p>AMD PCnet/FAST</p>
+</li>
+
+<li>
+<p>Isolan AT 4141-0 (16 bit)</p>
+</li>
+
+<li>
+<p>Isolink 4110 (8 bit)</p>
+</li>
+
+<li>
+<p>PCnet/FAST+</p>
+</li>
+
+<li>
+<p>PCnet/FAST III</p>
+</li>
+
+<li>
+<p>PCnet/PRO</p>
+</li>
+
+<li>
+<p>PCnet/Home</p>
+</li>
+
+<li>
+<p>HomePNA</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>National Semiconductor DS8390-based Ethernet NICs, including Novell NE2000 and clones
+(<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3C503 Etherlink II (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>NetVin 5000</p>
+</li>
+
+<li>
+<p>Novell NE1000, NE2000, and NE2100</p>
+</li>
+
+<li>
+<p>RealTek 8029</p>
+</li>
+
+<li>
+<p>SMC Elite 16 WD8013 Ethernet interface</p>
+</li>
+
+<li>
+<p>SMC Elite Ultra</p>
+</li>
+
+<li>
+<p>SMC WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT and
+clones</p>
+</li>
+
+<li>
+<p>Surecom NE-34</p>
+</li>
+
+<li>
+<p>VIA VT86C926</p>
+</li>
+
+<li>
+<p>Winbond W89C940</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>RealTek 8129/8139 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek 8139 clone)</p>
+</li>
+
+<li>
+<p>Allied Telesyn AT2550</p>
+</li>
+
+<li>
+<p>Allied Telesyn AT2500TX</p>
+</li>
+
+<li>
+<p>D-Link DFE-530TX+, DFE-538TX</p>
+</li>
+
+<li>
+<p>Farallon NetLINE 10/100 PCI</p>
+</li>
+
+<li>
+<p>Genius GF100TXR (RTL8139)</p>
+</li>
+
+<li>
+<p>KTX-9130TX 10/100 Fast Ethernet</p>
+</li>
+
+<li>
+<p>NDC Communications NE100TX-E</p>
+</li>
+
+<li>
+<p>Netronix Inc. EA-1210 NetEther 10/100</p>
+</li>
+
+<li>
+<p>OvisLink LEF-8129TX</p>
+</li>
+
+<li>
+<p>OvisLink LEF-8139TX</p>
+</li>
+
+<li>
+<p>SMC EZ Card 10/100 PCI 1211-TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Lite-On 82c168/82c169 PNIC Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Kingston KNE110TX</p>
+</li>
+
+<li>
+<p>LinkSys EtherFast LNE100TX</p>
+</li>
+
+<li>
+<p>Matrox FastNIC 10/100</p>
+</li>
+
+<li>
+<p>NetGear FA310-TX Rev. D1</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Accton EN1217 (98715A)</p>
+</li>
+
+<li>
+<p>Adico AE310TX (98715A)</p>
+</li>
+
+<li>
+<p>Compex RL100-TX (98713 or 98713A)</p>
+</li>
+
+<li>
+<p>CNet Pro120A (98713 or 98713A)</p>
+</li>
+
+<li>
+<p>CNet Pro120B (98715)</p>
+</li>
+
+<li>
+<p>NDC Communications SFA100A (98713A)</p>
+</li>
+
+<li>
+<p>SVEC PN102TX (98713)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>LinkSys EtherFast LNE100TX Version 2</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Winbond W89C840F Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wb</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Trendware TE100-PCIE</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine II'', and VT6105/VT6105M
+``Rhine III'' Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vr</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>AOpen/Acer ALN-320</p>
+</li>
+
+<li>
+<p>D-Link DFE-530TX</p>
+</li>
+
+<li>
+<p>Hawking Technologies PN102TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>SiS 630, 635 and 735 motherboard chipsets</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>National Semiconductor DP83815 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>NetGear FA311-TX</p>
+</li>
+
+<li>
+<p>NetGear FA312-TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Sundance Technologies ST201 PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ste</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>D-Link DFE-550TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>SysKonnect SK-984x PCI Gigabit Ethernet cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>SK-9821 1000baseT copper, single port</p>
+</li>
+
+<li>
+<p>SK-9822 1000baseT copper, dual port</p>
+</li>
+
+<li>
+<p>SK-9841 1000baseLX single mode fiber, single port</p>
+</li>
+
+<li>
+<p>SK-9842 1000baseLX single mode fiber, dual port</p>
+</li>
+
+<li>
+<p>SK-9843 1000baseSX multimode fiber, single port</p>
+</li>
+
+<li>
+<p>SK-9844 1000baseSX multimode fiber, dual port</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Texas Instruments ThunderLAN PCI NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Compaq Netelligent 10, 10/100, 10/100 Dual-Port</p>
+</li>
+
+<li>
+<p>Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP</p>
+</li>
+
+<li>
+<p>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</p>
+</li>
+
+<li>
+<p>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP</p>
+</li>
+
+<li>
+<p>Racore 8165 10/100baseTX</p>
+</li>
+
+<li>
+<p>Racore 8148 10baseT/100baseTX/100baseFX multi-personality</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<p>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>LinkSys EtherFast LNE100TX v4.0/4.1</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ASIX Electronics AX88140A PCI NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Alfa Inc. GFC2204</p>
+</li>
+
+<li>
+<p>CNet Pro110B</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 based NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=de&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Asante</p>
+</li>
+
+<li>
+<p>Cogent EM100FX and EM440TX</p>
+</li>
+
+<li>
+<p>DEC DE425, DE435, DE450, and DE500</p>
+</li>
+
+<li>
+<p>SMC Etherpower 8432T, 9332, and 9334</p>
+</li>
+
+<li>
+<p>ZYNX ZX 3xx</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>DEC/Intel 21143 based Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>DEC DE500</p>
+</li>
+
+<li>
+<p>Compaq Presario 7900 series built-in Ethernet</p>
+</li>
+
+<li>
+<p>D-Link DFE-570TX</p>
+</li>
+
+<li>
+<p>Kingston KNE100TX</p>
+</li>
+
+<li>
+<p>LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Davicom DM9009, DM9100 and DM9102 PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Jaton Corporation XpressNet</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Intel 82557- or 82559-based Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p>
+</li>
+
+<li>
+<p>Intel InBusiness 10/100 PCI Network Adapter</p>
+</li>
+
+<li>
+<p>Intel PRO/100+ Management Adapter</p>
+</li>
+
+<li>
+<p>Intel Pro/100 VE Desktop Adapter</p>
+</li>
+
+<li>
+<p>Intel Pro/100 M Desktop Adapter</p>
+</li>
+
+<li>
+<p>Intel Pro/100 S Desktop, Server and Dual-Port Server Adapters</p>
+</li>
+
+<li>
+<p>On-board Ethernet NICs on many Intel motherboards.</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>3Com Etherlink XL-based NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3C900/905/905B/905C PCI</p>
+</li>
+
+<li>
+<p>3C556/556B MiniPCI</p>
+</li>
+
+<li>
+<p>3C450-TX HomeConnect adapter</p>
+</li>
+
+<li>
+<p>3c980/3c980B Fast Etherlink XL server adapter</p>
+</li>
+
+<li>
+<p>3cSOHO100-TX OfficeConnect adapter</p>
+</li>
+
+<li>
+<p>Dell Optiplex GX1 on-board 3C918</p>
+</li>
+
+<li>
+<p>Dell On-board 3C920</p>
+</li>
+
+<li>
+<p>Dell Precision on-board 3C905B</p>
+</li>
+
+<li>
+<p>Dell Latitude laptop docking station embedded 3C905-TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Ethernet and Fast Ethernet NICs based on the 3Com 3XP Typhoon/Sidewinder (3CR990)
+chipset (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">txp</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3Com 3CR990-TX-95</p>
+</li>
+
+<li>
+<p>3Com 3CR990-TX-97</p>
+</li>
+
+<li>
+<p>3Com 3CR990B-SRV</p>
+</li>
+
+<li>
+<p>3Com 3CR990B-TXM</p>
+</li>
+
+<li>
+<p>3Com 3CR990SVR95</p>
+</li>
+
+<li>
+<p>3Com 3CR990SVR97</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Gigabit Ethernet NICs based on the Intel 82542 and 82543 controller chips (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wx</span>(4)</span></a>, <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=gx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gx</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=em&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> drivers),
+plus NICs supported by the Intel 82540EM, 82544, 82545EM, and 82546EB controller chips
+(<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=em&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver
+only)</p>
+
+<ul>
+<li>
+<p>Intel PRO/1000 Gigabit Ethernet</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wx</span>(4)</span></a> driver is
+deprecated.</p>
+</blockquote>
+</div>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=em&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver is
+officially supported by Intel, but is only supported on the i386.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN2916" name="AEN2916">3.3 FDDI Interfaces</a></h3>
+
+<p>DEC DEFPA PCI (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fpa</span>(4)</span></a>
+driver)</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN2926" name="AEN2926">3.4 ATM Interfaces</a></h3>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN2968" name="AEN2968">3.5 Wireless Network Interfaces</a></h3>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN3096" name="AEN3096">3.6 Miscellaneous Networks</a></h3>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN3113" name="AEN3113">3.7 ISDN Interfaces</a></h3>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN3177" name="AEN3177">3.8 Multi-port Serial
+Interfaces</a></h3>
+
+<p>AST 4 port serial card using shared IRQ</p>
+
+<p>Comtrol Rocketport card (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rp</span>(4)</span></a>
+driver)</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN3309" name="AEN3309">3.9 Audio Devices</a></h3>
+
+<p>ESS</p>
+
+<ul>
+<li>
+<p>ES1868, ES1869, ES1879 and ES1888 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbc</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Maestro-1, Maestro-2, and Maestro-2E</p>
+</li>
+
+<li>
+<p>Maestro-3/Allegro</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The Maestro-3/Allegro cannot be compiled into the FreeBSD kernel due to
+licensing restrictions. To use this driver, add the following line to <tt
+class="FILENAME">/boot/loader.conf</tt>:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">snd_maestro3_load="YES"</kbd>
+</pre>
+</blockquote>
+</div>
+</li>
+</ul>
+
+<br />
+<br />
+<p>MSS/WSS Compatible DSPs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a>
+driver)</p>
+
+<p>Creative Technologies SoundBlaster series (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>SoundBlaster</p>
+</li>
+
+<li>
+<p>SoundBlaster Pro</p>
+</li>
+
+<li>
+<p>SoundBlaster AWE-32</p>
+</li>
+
+<li>
+<p>SoundBlaster AWE-64</p>
+</li>
+
+<li>
+<p>SoundBlaster AWE-64 GOLD</p>
+</li>
+
+<li>
+<p>SoundBlaster ViBRA-16</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN3412" name="AEN3412">3.10 Camera and Video Capture
+Devices</a></h3>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="USB" name="USB">3.11 USB Devices</a></h3>
+
+<p>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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> USB Ethernet adapters can be found in the section listing <a
+href="#ETHERNET">Ethernet interfaces</a>.</p>
+</blockquote>
+</div>
+
+<p>Host Controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>ALi Aladdin-V</p>
+</li>
+
+<li>
+<p>AMD-756</p>
+</li>
+
+<li>
+<p>Belkin USB 2.0 High Speed Host Controller</p>
+</li>
+
+<li>
+<p>CMD Tech 670 &#38; 673</p>
+</li>
+
+<li>
+<p>Intel 82371SB (PIIX3)</p>
+</li>
+
+<li>
+<p>Intel 82371AB and EB (PIIX4)</p>
+</li>
+
+<li>
+<p>Intel 82801AA (ICH)</p>
+</li>
+
+<li>
+<p>Intel 82801AB (ICH0)</p>
+</li>
+
+<li>
+<p>Intel 82801BA/BAM (ICH2)</p>
+</li>
+
+<li>
+<p>Intel 82443MX</p>
+</li>
+
+<li>
+<p>NEC uPD 9210</p>
+</li>
+
+<li>
+<p>OPTi 82C861 (FireLink)</p>
+</li>
+
+<li>
+<p>SiS 5571</p>
+</li>
+
+<li>
+<p>VIA 83C572 USB</p>
+</li>
+
+<li>
+<p>UHCI or OHCI compliant motherboard chipsets (no exceptions known)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Hubs</p>
+
+<ul>
+<li>
+<p>Andromeda hub</p>
+</li>
+
+<li>
+<p>MacAlly self powered hub (4 ports)</p>
+</li>
+
+<li>
+<p>NEC hub</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Keyboards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Apple iMac keyboard</p>
+</li>
+
+<li>
+<p>BTC BTC7935 keyboard with PS/2 mouse port</p>
+</li>
+
+<li>
+<p>Cherry G81-3504 keyboard</p>
+</li>
+
+<li>
+<p>Logitech M2452 keyboard</p>
+</li>
+
+<li>
+<p>MacAlly iKey keyboard</p>
+</li>
+
+<li>
+<p>Microsoft keyboard</p>
+</li>
+
+<li>
+<p>Sun Microsystems Type 6 USB keyboard</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Mice (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Agiler Mouse 29UO</p>
+</li>
+
+<li>
+<p>Apple iMac Mouse</p>
+</li>
+
+<li>
+<p>Belkin Mouse</p>
+</li>
+
+<li>
+<p>Chic mouse</p>
+</li>
+
+<li>
+<p>Cypress mouse</p>
+</li>
+
+<li>
+<p>Genius Niche mouse</p>
+</li>
+
+<li>
+<p>Kensington Mouse-in-a-Box</p>
+</li>
+
+<li>
+<p>Logitech wheel mouse (3 buttons)</p>
+</li>
+
+<li>
+<p>Logitech PS/2 / USB mouse (3 buttons)</p>
+</li>
+
+<li>
+<p>MacAlly mouse (3 buttons)</p>
+</li>
+
+<li>
+<p>Microsoft IntelliMouse (3 buttons)</p>
+</li>
+
+<li>
+<p>Sun Microsystems Type 6 USB Mouse</p>
+</li>
+
+<li>
+<p>Trust Ami Mouse (3 buttons)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Printers and parallel printer conversion cables (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ulpt</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>ATen parallel printer adapter</p>
+</li>
+
+<li>
+<p>Belkin F5U002 parallel printer adapter</p>
+</li>
+
+<li>
+<p>Entrega USB-to-parallel printer adapter</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Storage (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umass</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Matshita CF-VFDU03 floppy drive</p>
+</li>
+
+<li>
+<p>Microtech USB-SCSI-HD 50 USB to SCSI cable</p>
+</li>
+
+<li>
+<p>Panasonic floppy drive</p>
+</li>
+
+<li>
+<p>Y-E Data floppy drive (720/1.44/2.88Mb)</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 IEEE 1394 (Firewire)
+Devices</a></h3>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN3673" name="AEN3673">3.13 Cryptographic Accelerators</a></h3>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN3698" name="AEN3698">3.14 Miscellaneous</a></h3>
+
+<p>Floppy drives (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fdc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fdc</span>(4)</span></a>
+driver)</p>
+
+<p>VGA-compatible video cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vga&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vga</span>(4)</span></a>
+driver)</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Information regarding specific video cards and compatibility with <b
+class="APPLICATION">XFree86</b> can be found at <a href="http://www.xfree86.org/"
+target="_top">http://www.xfree86.org/</a>.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>Keyboards including:</p>
+
+<ul>
+<li>
+<p>AT-style keyboards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>PS/2 keyboards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>USB keyboards (specific instances are listed in the section describing <a
+href="#USB">USB devices</a>)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Pointing devices including:</p>
+
+<ul>
+<li>
+<p>PS/2 mice and compatible devices (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">psm</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Serial mice and compatible devices</p>
+</li>
+
+<li>
+<p>USB mice (specific instances are listed in the section describing <a href="#USB">USB
+devices</a>)</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> has
+more information on using pointing devices with FreeBSD. Information on using pointing
+devices with <b class="APPLICATION">XFree86</b> can be found at <a
+href="http://www.xfree86.org/" target="_top">http://www.xfree86.org/</a>.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>``PC standard'' parallel ports (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppc</span>(4)</span></a>
+driver)</p>
+
+<p>``PC standard'' 8250, 16450, and 16550-based serial ports (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a>
+driver)</p>
+</div>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+
diff --git a/en/releases/4.9R/hardware-i386.html b/en/releases/4.9R/hardware-i386.html
new file mode 100644
index 0000000000..3ef17b95b9
--- /dev/null
+++ b/en/releases/4.9R/hardware-i386.html
@@ -0,0 +1,4292 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD/i386 4.9-RELEASE Hardware Notes</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD/i386 4.9-RELEASE Hardware
+Notes</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<hr />
+</div>
+
+<div class="TOC">
+<dl>
+<dt><b>Table of Contents</b></dt>
+
+<dt>1 <a href="#AEN11">Introduction</a></dt>
+
+<dt>2 <a href="#AEN16">Supported Processors and Motherboards</a></dt>
+
+<dt>3 <a href="#AEN27">Supported Devices</a></dt>
+
+<dd>
+<dl>
+<dt>3.1 <a href="#AEN33">Disk Controllers</a></dt>
+
+<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt>
+
+<dt>3.3 <a href="#AEN1342">FDDI Interfaces</a></dt>
+
+<dt>3.4 <a href="#AEN1352">ATM Interfaces</a></dt>
+
+<dt>3.5 <a href="#AEN1394">Wireless Network Interfaces</a></dt>
+
+<dt>3.6 <a href="#AEN1522">Miscellaneous Networks</a></dt>
+
+<dt>3.7 <a href="#AEN1539">ISDN Interfaces</a></dt>
+
+<dt>3.8 <a href="#AEN1603">Multi-port Serial Interfaces</a></dt>
+
+<dt>3.9 <a href="#AEN1735">Audio Devices</a></dt>
+
+<dt>3.10 <a href="#AEN1838">Camera and Video Capture Devices</a></dt>
+
+<dt>3.11 <a href="#USB">USB Devices</a></dt>
+
+<dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt>
+
+<dt>3.13 <a href="#AEN2099">Cryptographic Accelerators</a></dt>
+
+<dt>3.14 <a href="#AEN2124">Miscellaneous</a></dt>
+</dl>
+</dd>
+</dl>
+</div>
+
+<div class="SECT1">
+<h2 class="SECT1"><a id="AEN11" name="AEN11">1 Introduction</a></h2>
+
+<p>This document contains the hardware compatability notes for FreeBSD 4.9-RELEASE on the
+i386 hardware platform (also referred to as FreeBSD/i386 4.9-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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> This document includes information specific to the i386 hardware
+platform. Versions of the hardware compatability notes for other architectures will
+differ in some details.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN16" name="AEN16">2 Supported Processors and
+Motherboards</a></h2>
+
+<p>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.</p>
+
+<p>Almost all i386-compatible processors are supported. All Intel processors beginning
+with the 80386 are supported, including the 80386, 80486, Pentium, Pentium Pro, Pentium
+II, Pentium III, Pentium 4, and variants thereof, such as the Xeon and Celeron
+processors. (While technically supported, the use of the 80386SX is specifically not
+recommended.) 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 &Eacute;lan SC520 embedded processor
+is supported. The Transmeta Crusoe is recognized and supported, as are i386-compatible
+processors from Cyrix and NexGen.</p>
+
+<p>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.</p>
+
+<p>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 <a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-smp"
+target="_top">FreeBSD symmetric multiprocessing mailing list</a> may yield some
+clues.</p>
+
+<p>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 <a
+href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-mobile" target="_top">FreeBSD
+laptop computer mailing list</a> may be useful.</p>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN27" name="AEN27">3 Supported Devices</a></h2>
+
+$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.13.2.90 2003/10/01
+20:36:57 simon Exp $
+
+<p>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.</p>
+
+<p>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.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN33" name="AEN33">3.1 Disk Controllers</a></h3>
+
+<p>IDE/ATA controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Acerlabs Aladdin</p>
+</li>
+
+<li>
+<p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p>
+</li>
+
+<li>
+<p>Cenatek Rocket Drive</p>
+</li>
+
+<li>
+<p>CMD 646, 648 ATA66, and 649 ATA100</p>
+</li>
+
+<li>
+<p>Cypress 82C693</p>
+</li>
+
+<li>
+<p>Cyrix 5530 ATA33</p>
+</li>
+
+<li>
+<p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 ATA133, HPT374 ATA133</p>
+</li>
+
+<li>
+<p>Intel PIIX, PIIX3, PIIX4</p>
+</li>
+
+<li>
+<p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 ATA100</p>
+</li>
+
+<li>
+<p>nVidia nForce ATA100</p>
+</li>
+
+<li>
+<p>Promise ATA100 OEM chip (pdc20265)</p>
+</li>
+
+<li>
+<p>Promise ATA133 OEM chip (pdc20269)</p>
+</li>
+
+<li>
+<p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000</p>
+</li>
+
+<li>
+<p>Promise Ultra-33, -66, -100, -133 TX2/TX2000</p>
+</li>
+
+<li>
+<p>ServerWorks ROSB4 ATA33</p>
+</li>
+
+<li>
+<p>ServerWorks CSB5 ATA66/ATA100</p>
+</li>
+
+<li>
+<p>Sil 0680 UDMA6</p>
+</li>
+
+<li>
+<p>SiS 530, 540, 620</p>
+</li>
+
+<li>
+<p>SiS 630, 633, 635, 645, 730, 733, 735, 740, 745, 750</p>
+</li>
+
+<li>
+<p>SiS 5591 ATA100</p>
+</li>
+
+<li>
+<p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100</p>
+</li>
+
+<li>
+<p>VIA 8233, 8235 ATA133</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Adaptec SCSI Controllers</p>
+
+<ul>
+<li>
+<p>Adaptec 1535 ISA SCSI controllers</p>
+</li>
+
+<li>
+<p>Adaptec 154x series ISA SCSI controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aha</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec 164x series MCA SCSI controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aha</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec 174x series EISA SCSI controller in standard and enhanced mode (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aha</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahb&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahb</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec 274x series EISA SCSI controllers, including narrow and wide variants (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec 284x series VLB SCSI controllers, including narrow and wide variants (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec 19160/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x series PCI
+SCSI controllers, including Narrow/Wide/Twin/Ultra/Ultra2 variants (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec AIC7770, AIC7850, AIC7860, AIC7870, AIC7880, and AIC789x on-board SCSI
+controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec 1510 series ISA SCSI controllers (not for bootable devices)</p>
+</li>
+
+<li>
+<p>Adaptec 152x series ISA SCSI controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aha</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and
+SoundBlaster SCSI cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=aic&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aic</span>(4)</span></a>
+driver)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Ultra-320 SCSI controllers based on the Adaptec AIC7901, AIC7901A, and AIC7902
+Ultra320 controller chips (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahd</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Adaptec 29320, 29320A, 29320B, 29320LP</p>
+</li>
+
+<li>
+<p>Adaptec 39320, 39320D</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Adaptec 2100S/32x0S/34x0S SCSI RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">asr</span>(4)</span></a>
+driver)</p>
+
+<p>Adaptec 2000S/2005S Zero-Channel RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">asr</span>(4)</span></a>
+driver)</p>
+
+<p>Adaptec 2400A ATA-100 RAID controller (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">asr</span>(4)</span></a>
+driver)</p>
+
+<p>Adaptec FSA family RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aac</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Adaptec AAC-2622</p>
+</li>
+
+<li>
+<p>Adaptec AAC-364</p>
+</li>
+
+<li>
+<p>Adaptec SCSI RAID 5400S</p>
+</li>
+
+<li>
+<p>Dell PERC 2/QC</p>
+</li>
+
+<li>
+<p>Dell PERC 2/Si</p>
+</li>
+
+<li>
+<p>Dell PERC 3/Di</p>
+</li>
+
+<li>
+<p>Dell PERC 3/QC</p>
+</li>
+
+<li>
+<p>Dell PERC 3/Si</p>
+</li>
+
+<li>
+<p>HP NetRAID-4M</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>AdvanSys SCSI controllers (all models, <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=adv&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adv</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=adw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adw</span>(4)</span></a>
+drivers)</p>
+
+<p>BusLogic MultiMaster ``W'' Series Host Adapters (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a>
+driver):</p>
+
+<ul>
+<li>
+<p>BT-948</p>
+</li>
+
+<li>
+<p>BT-958</p>
+</li>
+
+<li>
+<p>BT-958D</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>BusLogic MultiMaster ``C'' Series Host Adapters (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a>
+driver):</p>
+
+<ul>
+<li>
+<p>BT-946C</p>
+</li>
+
+<li>
+<p>BT-956C</p>
+</li>
+
+<li>
+<p>BT-956CD</p>
+</li>
+
+<li>
+<p>BT-445C</p>
+</li>
+
+<li>
+<p>BT-747C</p>
+</li>
+
+<li>
+<p>BT-757C</p>
+</li>
+
+<li>
+<p>BT-757CD</p>
+</li>
+
+<li>
+<p>BT-545C</p>
+</li>
+
+<li>
+<p>BT-540CF</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>BusLogic MultiMaster ``S'' Series Host Adapters (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a>
+driver):</p>
+
+<ul>
+<li>
+<p>BT-445S</p>
+</li>
+
+<li>
+<p>BT-747S</p>
+</li>
+
+<li>
+<p>BT-747D</p>
+</li>
+
+<li>
+<p>BT-757S</p>
+</li>
+
+<li>
+<p>BT-757D</p>
+</li>
+
+<li>
+<p>BT-545S</p>
+</li>
+
+<li>
+<p>BT-542D</p>
+</li>
+
+<li>
+<p>BT-742A</p>
+</li>
+
+<li>
+<p>BT-542B</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>BusLogic MultiMaster ``A'' Series Host Adapters (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a>
+driver):</p>
+
+<ul>
+<li>
+<p>BT-742A</p>
+</li>
+
+<li>
+<p>BT-542B</p>
+</li>
+</ul>
+
+<br />
+<br />
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> BusLogic/Mylex ``Flashpoint'' adapters are not yet supported.</p>
+</blockquote>
+</div>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> AMI FastDisk controllers that are true BusLogic MultiMaster clones are
+also supported.</p>
+</blockquote>
+</div>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F
+Microchannel (MCA) bus adapters are also supported.</p>
+</blockquote>
+</div>
+
+<p>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV
+SCSI/RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dpt&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dpt</span>(4)</span></a>
+driver)</p>
+
+<p>DPT SmartRAID V and VI SCSI RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">asr</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>PM1554</p>
+</li>
+
+<li>
+<p>PM2554</p>
+</li>
+
+<li>
+<p>PM2654</p>
+</li>
+
+<li>
+<p>PM2865</p>
+</li>
+
+<li>
+<p>PM2754</p>
+</li>
+
+<li>
+<p>PM3755</p>
+</li>
+
+<li>
+<p>PM3757</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>AMI MegaRAID Express and Enterprise family RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>MegaRAID Series 418</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1200 (Series 428)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1300 (Series 434)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1400 (Series 438)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1500 (Series 467)</p>
+</li>
+
+<li>
+<p>MegaRAID Enterprise 1600 (Series 471)</p>
+</li>
+
+<li>
+<p>MegaRAID Elite 1500 (Series 467)</p>
+</li>
+
+<li>
+<p>MegaRAID Elite 1600 (Series 493)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 100 (Series 466WS)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 200 (Series 466)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 300 (Series 490)</p>
+</li>
+
+<li>
+<p>MegaRAID Express 500 (Series 475)</p>
+</li>
+
+<li>
+<p>Dell PERC</p>
+</li>
+
+<li>
+<p>Dell PERC 2/SC</p>
+</li>
+
+<li>
+<p>Dell PERC 2/DC</p>
+</li>
+
+<li>
+<p>Dell PERC 3/DCL</p>
+</li>
+
+<li>
+<p>Dell PERC 4/Di</p>
+</li>
+
+<li>
+<p>HP NetRaid-1si</p>
+</li>
+
+<li>
+<p>HP NetRaid-3si</p>
+</li>
+
+<li>
+<p>HP Embedded NetRaid</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Booting from these controllers is supported. EISA adapters are not
+supported.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mlx</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>DAC960P</p>
+</li>
+
+<li>
+<p>DAC960PD</p>
+</li>
+
+<li>
+<p>DAC960PDU</p>
+</li>
+
+<li>
+<p>DAC960PL</p>
+</li>
+
+<li>
+<p>DAC960PJ</p>
+</li>
+
+<li>
+<p>DAC960PG</p>
+</li>
+
+<li>
+<p>AcceleRAID 150</p>
+</li>
+
+<li>
+<p>AcceleRAID 250</p>
+</li>
+
+<li>
+<p>eXtremeRAID 1100</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Booting from these controllers is supported. EISA adapters are not
+supported.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>Mylex PCI to SCSI RAID controllers with 6.x firmware (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mly</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>AcceleRAID 160</p>
+</li>
+
+<li>
+<p>AcceleRAID 170</p>
+</li>
+
+<li>
+<p>AcceleRAID 352</p>
+</li>
+
+<li>
+<p>eXtremeRAID 2000</p>
+</li>
+
+<li>
+<p>eXtremeRAID 3000</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Compatible Mylex controllers not listed should work, but have not been
+verified.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>3ware Escalade ATA RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=twe&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twe</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>5000 series</p>
+</li>
+
+<li>
+<p>6000 series</p>
+</li>
+
+<li>
+<p>7000 series</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C825, 53C825a, 53C860, 53C875,
+53C875a, 53C876, 53C885, 53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000,
+53C1000R PCI SCSI controllers, either embedded on motherboard or on add-on boards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>ASUS SC-200, SC-896</p>
+</li>
+
+<li>
+<p>Data Technology DTC3130 (all variants)</p>
+</li>
+
+<li>
+<p>DawiControl DC2976UW</p>
+</li>
+
+<li>
+<p>Diamond FirePort (all)</p>
+</li>
+
+<li>
+<p>NCR cards (all)</p>
+</li>
+
+<li>
+<p>Symbios cards (all)</p>
+</li>
+
+<li>
+<p>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and 390U3W</p>
+</li>
+
+<li>
+<p>Tyan S1365</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>NCR 53C500 based PC-Card SCSI host adapters (ncv driver)</p>
+
+<ul>
+<li>
+<p>IO DATA PCSC-DV</p>
+</li>
+
+<li>
+<p>KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004</p>
+</li>
+
+<li>
+<p>Macnica Miracle SCSI-II mPS110</p>
+</li>
+
+<li>
+<p>Media Intelligent MSC-110, MSC-200</p>
+</li>
+
+<li>
+<p>NEC PC-9801N-J03R</p>
+</li>
+
+<li>
+<p>New Media Corporation BASICS SCSI</p>
+</li>
+
+<li>
+<p>Qlogic Fast SCSI</p>
+</li>
+
+<li>
+<p>RATOC REX-9530, REX-5572 (as SCSI only)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters (stg driver)</p>
+
+<ul>
+<li>
+<p>Future Domain SCSI2GO</p>
+</li>
+
+<li>
+<p>IBM SCSI PCMCIA Card</p>
+</li>
+
+<li>
+<p>ICM PSC-2401 SCSI</p>
+</li>
+
+<li>
+<p>Melco IFC-SC</p>
+</li>
+
+<li>
+<p>RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Qlogic controllers and variants (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Qlogic 1020, 1040 SCSI and Ultra SCSI host adapters</p>
+</li>
+
+<li>
+<p>Qlogic 1240 dual Ultra SCSI controllers</p>
+</li>
+
+<li>
+<p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD controllers</p>
+</li>
+
+<li>
+<p>Qlogic 12160 Ultra3 LVD controllers</p>
+</li>
+
+<li>
+<p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI controllers</p>
+</li>
+
+<li>
+<p>Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre Channel SCSI controllers</p>
+</li>
+
+<li>
+<p>Performance Technology SBS440 ISP1000 variants</p>
+</li>
+
+<li>
+<p>Performance Technology SBS450 ISP1040 variants</p>
+</li>
+
+<li>
+<p>Performance Technology SBS470 ISP2100 variants</p>
+</li>
+
+<li>
+<p>Antares Microsystems P-0033 ISP2100 variants</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>DTC 3290 EISA SCSI controller in 1542 emulation mode.</p>
+
+<p>Tekram DC390 and DC390T controllers, maybe other cards based on the AMD 53c974 as well
+(<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amd</span>(4)</span></a>
+driver)</p>
+
+<p>Workbit Ninja SCSI-3 based PC-Card SCSI host adapters (nsp driver)</p>
+
+<ul>
+<li>
+<p>Alpha-Data AD-PCS201</p>
+</li>
+
+<li>
+<p>IO DATA CBSC16</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Parallel to SCSI interfaces (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vpo&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vpo</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>AIC 7110 SCSI controller (built-in to Iomega ZIP drive)</p>
+</li>
+
+<li>
+<p>Iomega Jaz Traveller interface</p>
+</li>
+
+<li>
+<p>Iomega MatchMaker SCSI interface (built-in to Iomega ZIP+ drive)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Compaq Intelligent Drive Array Controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ida&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ida</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Compaq SMART Array 221</p>
+</li>
+
+<li>
+<p>Compaq Integrated SMART Array Controller</p>
+</li>
+
+<li>
+<p>Compaq SMART Array 4200, 4250ES Controllers</p>
+</li>
+
+<li>
+<p>Compaq SMART Array 3200, 3100ES Controller</p>
+</li>
+
+<li>
+<p>Compaq SMART-2/DH, SMART-2/SL, SMART-2/P, SMART-2E, and SMART Controllers</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>SCSI adapters utilizing the Command Interface for SCSI-3 Support (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ciss&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ciss</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Compaq Smart Array 5* series (5300, 5i, 532)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Intel Integrated RAID Controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">iir</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Intel RAID Controller SRCMR</p>
+</li>
+
+<li>
+<p>ICP Vortex SCSI RAID controllers (all Wide/Ultra160, 32-bit/64-bit PCI models)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Promise SuperTrak ATA RAID controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pst&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pst</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Promise SuperTrak SX6000 ATA RAID controller</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>LSI Logic Fusion/MP architecture Fiber Channel controllers (mpt driver)</p>
+
+<ul>
+<li>
+<p>LSI FC909, FC929</p>
+</li>
+
+<li>
+<p>LSI 53c1020, 53c1030</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>PCI SCSI host adapters using the Tekram TRM-S1040 SCSI chipset (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=trm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">trm</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Tekram DC395U/UW/F</p>
+</li>
+
+<li>
+<p>Tekram DC315U</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cd</span>(4)</span></a>).
+WORM/CD-R/CD-RW writing support is provided by <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&amp;sektion=1&amp;manpath=FreeBSD+Ports">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cdrecord</span>(1)</span></a>,
+which is a part of the <a
+href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr"><tt
+class="FILENAME">sysutils/cdrtools</tt></a> port in the Ports Collection.</p>
+
+<p>The following CD-ROM type systems are supported at this time:</p>
+
+<ul>
+<li>
+<p>SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cd</span>(4)</span></a>)</p>
+</li>
+
+<li>
+<p>Sony proprietary interface (all models) (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=scd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">scd</span>(4)</span></a>)</p>
+</li>
+
+<li>
+<p>ATAPI IDE interface (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=acd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acd</span>(4)</span></a>)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>The following drivers were supported under the old SCSI subsystem, but are not yet
+supported under the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cam&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cam</span>(4)</span></a> SCSI
+subsystem:</p>
+
+<ul>
+<li>
+<p>NCR5380/NCR53400 (``ProAudio Spectrum'') SCSI controller</p>
+</li>
+
+<li>
+<p>UltraStor 14F, 24F and 34F SCSI controllers.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> There is work-in-progress to port the UltraStor driver to the new CAM
+SCSI framework, but no estimates on when or if it will be completed.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+</li>
+
+<li>
+<p>Seagate ST01/02 SCSI controllers</p>
+</li>
+
+<li>
+<p>Future Domain 8xx/950 series SCSI controllers</p>
+</li>
+
+<li>
+<p>WD7000 SCSI controller</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>The following device is unmaintained:</p>
+
+<ul>
+<li>
+<p>Mitsumi proprietary CD-ROM interface (all models) (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mcd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mcd</span>(4)</span></a>)</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 Ethernet Interfaces</a></h3>
+
+<p>Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast
+Ethernet controller chip (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sf</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>ANA-62011 64-bit single port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-62022 64-bit dual port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-62044 64-bit quad port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-69011 32-bit single port 10/100baseTX adapter</p>
+</li>
+
+<li>
+<p>ANA-62020 64-bit single port 100baseFX adapter</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Allied-Telesis AT1700 and RE2000 cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fe</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>CONTEC C-NET(PC)C PCMCIA Ethernet</p>
+</li>
+
+<li>
+<p>Fujitsu MBH10303, MBH10302 Ethernet PCMCIA</p>
+</li>
+
+<li>
+<p>Fujitsu Towa LA501 Ethernet</p>
+</li>
+
+<li>
+<p>Fujitsu FMV-J182, FMV-J182A</p>
+</li>
+
+<li>
+<p>RATOC REX-5588, REX-9822, REX-4886, and REX-R280</p>
+</li>
+
+<li>
+<p>Eiger Labs EPX-10BT</p>
+</li>
+
+<li>
+<p>HITACHI HT-4840-11</p>
+</li>
+
+<li>
+<p>NextCom J Link NC5310</p>
+</li>
+
+<li>
+<p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets
+(<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ti</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3Com 3c985-SX (Tigon 1 and 2)</p>
+</li>
+
+<li>
+<p>Alteon AceNIC (Tigon 1 and 2)</p>
+</li>
+
+<li>
+<p>Alteon AceNIC 1000baseT (Tigon 2)</p>
+</li>
+
+<li>
+<p>Asante PCI 1000BASE-SX Gigabit Ethernet Adapter</p>
+</li>
+
+<li>
+<p>Asante GigaNIX1000T Gigabit Ethernet Adapter</p>
+</li>
+
+<li>
+<p>DEC/Compaq EtherWORKS 1000</p>
+</li>
+
+<li>
+<p>Farallon PN9000SX</p>
+</li>
+
+<li>
+<p>NEC Gigabit Ethernet</p>
+</li>
+
+<li>
+<p>Netgear GA620 (Tigon 2)</p>
+</li>
+
+<li>
+<p>Netgear GA620T (Tigon 2, 1000baseT)</p>
+</li>
+
+<li>
+<p>Silicon Graphics Gigabit Ethernet</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>AMD PCnet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcn</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>AMD PCnet/PCI (79c970 &#38; 53c974 or 79c974)</p>
+</li>
+
+<li>
+<p>AMD PCnet/FAST</p>
+</li>
+
+<li>
+<p>Isolan AT 4141-0 (16 bit)</p>
+</li>
+
+<li>
+<p>Isolink 4110 (8 bit)</p>
+</li>
+
+<li>
+<p>PCnet/FAST+</p>
+</li>
+
+<li>
+<p>PCnet/FAST III</p>
+</li>
+
+<li>
+<p>PCnet/PRO</p>
+</li>
+
+<li>
+<p>PCnet/Home</p>
+</li>
+
+<li>
+<p>HomePNA</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>SMC 83c17x (EPIC)-based Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=tx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tx</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>SMC EtherPower II 9432 series</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>National Semiconductor DS8390-based Ethernet NICs, including Novell NE2000 and clones
+(<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3C503 Etherlink II (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>DEC Etherworks DE305</p>
+</li>
+
+<li>
+<p>Hewlett-Packard PC Lan+ 27247B and 27252A</p>
+</li>
+
+<li>
+<p>NetVin 5000</p>
+</li>
+
+<li>
+<p>Novell NE1000, NE2000, and NE2100</p>
+</li>
+
+<li>
+<p>RealTek 8029</p>
+</li>
+
+<li>
+<p>SMC Elite 16 WD8013 Ethernet interface</p>
+</li>
+
+<li>
+<p>SMC Elite Ultra</p>
+</li>
+
+<li>
+<p>SMC WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT and
+clones</p>
+</li>
+
+<li>
+<p>Surecom NE-34</p>
+</li>
+
+<li>
+<p>VIA VT86C926</p>
+</li>
+
+<li>
+<p>Winbond W89C940</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>NE2000 compatible PC-Card (PCMCIA) Ethernet and FastEthernet cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>AR-P500 Ethernet</p>
+</li>
+
+<li>
+<p>Accton EN2212/EN2216/UE2216</p>
+</li>
+
+<li>
+<p>Allied Telesis CentreCOM LA100-PCM_V2</p>
+</li>
+
+<li>
+<p>AmbiCom 10BaseT card</p>
+</li>
+
+<li>
+<p>BayNetworks NETGEAR FA410TXC Fast Ethernet</p>
+</li>
+
+<li>
+<p>CNet BC40 adapter</p>
+</li>
+
+<li>
+<p>COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD</p>
+</li>
+
+<li>
+<p>Compex Net-A adapter</p>
+</li>
+
+<li>
+<p>CyQ've ELA-010</p>
+</li>
+
+<li>
+<p>D-Link DE-650/660</p>
+</li>
+
+<li>
+<p>Danpex EN-6200P2</p>
+</li>
+
+<li>
+<p>Elecom Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A), MACNICA
+Ethernet ME1 for JEIDA</p>
+</li>
+
+<li>
+<p>IO DATA PCLATE</p>
+</li>
+
+<li>
+<p>IBM Creditcard Ethernet I/II</p>
+</li>
+
+<li>
+<p>IC-CARD Ethernet/IC-CARD+ Ethernet</p>
+</li>
+
+<li>
+<p>Kingston KNE-PC2, KNE-PCM/x Ethernet</p>
+</li>
+
+<li>
+<p>Linksys EC2T/PCMPC100/PCM100, PCMLM56, EtherFast 10/100 PC Card, Combo PCMCIA Ethernet
+Card (PCMPC100 V2)</p>
+</li>
+
+<li>
+<p>Melco LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX</p>
+</li>
+
+<li>
+<p>NDC Ethernet Instant-Link</p>
+</li>
+
+<li>
+<p>National Semiconductor InfoMover NE4100</p>
+</li>
+
+<li>
+<p>NetGear FA-410TX</p>
+</li>
+
+<li>
+<p>Network Everywhere Ethernet 10BaseT PC Card</p>
+</li>
+
+<li>
+<p>Planex FNW-3600-T</p>
+</li>
+
+<li>
+<p>Socket LP-E</p>
+</li>
+
+<li>
+<p>Surecom EtherPerfect EP-427</p>
+</li>
+
+<li>
+<p>TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card</p>
+</li>
+
+<li>
+<p>Telecom Device SuperSocket RE450T</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>RealTek RTL 8002 Pocket Ethernet (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rdp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rdp</span>(4)</span></a>
+driver)</p>
+
+<p>RealTek 8129/8139 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek 8139 clone)</p>
+</li>
+
+<li>
+<p>Allied Telesyn AT2550</p>
+</li>
+
+<li>
+<p>Allied Telesyn AT2500TX</p>
+</li>
+
+<li>
+<p>D-Link DFE-530TX+, DFE-538TX</p>
+</li>
+
+<li>
+<p>Farallon NetLINE 10/100 PCI</p>
+</li>
+
+<li>
+<p>Genius GF100TXR (RTL8139)</p>
+</li>
+
+<li>
+<p>KTX-9130TX 10/100 Fast Ethernet</p>
+</li>
+
+<li>
+<p>NDC Communications NE100TX-E</p>
+</li>
+
+<li>
+<p>Netronix Inc. EA-1210 NetEther 10/100</p>
+</li>
+
+<li>
+<p>OvisLink LEF-8129TX</p>
+</li>
+
+<li>
+<p>OvisLink LEF-8139TX</p>
+</li>
+
+<li>
+<p>SMC EZ Card 10/100 PCI 1211-TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Lite-On 82c168/82c169 PNIC Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Kingston KNE110TX</p>
+</li>
+
+<li>
+<p>LinkSys EtherFast LNE100TX</p>
+</li>
+
+<li>
+<p>Matrox FastNIC 10/100</p>
+</li>
+
+<li>
+<p>NetGear FA310-TX Rev. D1</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Accton EN1217 (98715A)</p>
+</li>
+
+<li>
+<p>Adico AE310TX (98715A)</p>
+</li>
+
+<li>
+<p>Compex RL100-TX (98713 or 98713A)</p>
+</li>
+
+<li>
+<p>CNet Pro120A (98713 or 98713A)</p>
+</li>
+
+<li>
+<p>CNet Pro120B (98715)</p>
+</li>
+
+<li>
+<p>NDC Communications SFA100A (98713A)</p>
+</li>
+
+<li>
+<p>SVEC PN102TX (98713)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>LinkSys EtherFast LNE100TX Version 2</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Winbond W89C840F Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wb</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Trendware TE100-PCIE</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine II'', and VT6105/VT6105M
+``Rhine III'' Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vr</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>AOpen/Acer ALN-320</p>
+</li>
+
+<li>
+<p>D-Link DFE-530TX</p>
+</li>
+
+<li>
+<p>Hawking Technologies PN102TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>SiS 630, 635 and 735 motherboard chipsets</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>National Semiconductor DP83815 Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>NetGear FA311-TX</p>
+</li>
+
+<li>
+<p>NetGear FA312-TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=nge&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nge</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Addtron AEG320T</p>
+</li>
+
+<li>
+<p>Asante FriendlyNet GigaNIC 1000TA and 1000TPC</p>
+</li>
+
+<li>
+<p>D-Link DGE-500T</p>
+</li>
+
+<li>
+<p>LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit PCI)</p>
+</li>
+
+<li>
+<p>Netgear GA621 and GA622T</p>
+</li>
+
+<li>
+<p>SMC EZ Card 1000 (SMC9462TX)</p>
+</li>
+
+<li>
+<p>Surecom Technology EP-320G-TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Sundance Technologies ST201 PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ste</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>D-Link DFE-550TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>SysKonnect SK-984x PCI Gigabit Ethernet cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>SK-9821 1000baseT copper, single port</p>
+</li>
+
+<li>
+<p>SK-9822 1000baseT copper, dual port</p>
+</li>
+
+<li>
+<p>SK-9841 1000baseLX single mode fiber, single port</p>
+</li>
+
+<li>
+<p>SK-9842 1000baseLX single mode fiber, dual port</p>
+</li>
+
+<li>
+<p>SK-9843 1000baseSX multimode fiber, single port</p>
+</li>
+
+<li>
+<p>SK-9844 1000baseSX multimode fiber, dual port</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Texas Instruments ThunderLAN PCI NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Compaq Netelligent 10, 10/100, 10/100 Dual-Port</p>
+</li>
+
+<li>
+<p>Compaq Netelligent 10/100 Proliant</p>
+</li>
+
+<li>
+<p>Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP</p>
+</li>
+
+<li>
+<p>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</p>
+</li>
+
+<li>
+<p>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP</p>
+</li>
+
+<li>
+<p>Racore 8165 10/100baseTX</p>
+</li>
+
+<li>
+<p>Racore 8148 10baseT/100baseTX/100baseFX multi-personality</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<p>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>LinkSys EtherFast LNE100TX v4.0/4.1</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ADMtek Inc. AN986-based USB Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=aue&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aue</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Abocom UFE1000, DSB650TX_NA</p>
+</li>
+
+<li>
+<p>Accton USB320-EC, SpeedStream</p>
+</li>
+
+<li>
+<p>ADMtek AN986, AN8511</p>
+</li>
+
+<li>
+<p>Billionton USB100, USB100LP, USB100EL, USBE100</p>
+</li>
+
+<li>
+<p>Corega Ether FEther USB-TX, FEther USB-TXS</p>
+</li>
+
+<li>
+<p>D-Link DSB-650, DSB-650TX, DSB-650TX-PNA</p>
+</li>
+
+<li>
+<p>Elsa Microlink USB2Ethernet</p>
+</li>
+
+<li>
+<p>I/O Data USB ETTX</p>
+</li>
+
+<li>
+<p>Kingston KNU101TX</p>
+</li>
+
+<li>
+<p>LinkSys USB10T, USB10TA, USB10TX, USB100TX, USB100H1</p>
+</li>
+
+<li>
+<p>Melco Inc. LUA-TX, LUA2-TX</p>
+</li>
+
+<li>
+<p>Siemens Speedstream</p>
+</li>
+
+<li>
+<p>SmartBridges smartNIC</p>
+</li>
+
+<li>
+<p>SMC 2202USB</p>
+</li>
+
+<li>
+<p>SOHOware NUB100</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>CATC USB-EL1210A-based USB Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cue&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cue</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Belkin F5U011, F5U111</p>
+</li>
+
+<li>
+<p>CATC Netmate, Netmate II</p>
+</li>
+
+<li>
+<p>SmartBridges SmartLink</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=kue&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kue</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3Com 3c19250</p>
+</li>
+
+<li>
+<p>AOX USB101</p>
+</li>
+
+<li>
+<p>ADS Technologies USB-10BT</p>
+</li>
+
+<li>
+<p>ATen UC10T</p>
+</li>
+
+<li>
+<p>Corega USB-T</p>
+</li>
+
+<li>
+<p>D-Link DSB-650C</p>
+</li>
+
+<li>
+<p>Entrega NET-USB-E45</p>
+</li>
+
+<li>
+<p>Kawasaki DU-H3E</p>
+</li>
+
+<li>
+<p>LinkSys USB10T</p>
+</li>
+
+<li>
+<p>Netgear EA101</p>
+</li>
+
+<li>
+<p>Peracom USB Ethernet Adapter</p>
+</li>
+
+<li>
+<p>SMC 2102USB, 2104USB</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>RealTek RTL8150-based USB Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rue</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>GREEN HOUSE GH-USB100B</p>
+</li>
+
+<li>
+<p>MELCO LUA-KTX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ASIX Electronics AX88140A PCI NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Alfa Inc. GFC2204</p>
+</li>
+
+<li>
+<p>CNet Pro110B</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>DEC EtherWORKS II and III NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=le&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">le</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>DE200, DE201, DE202, DE422</p>
+</li>
+
+<li>
+<p>DE203, DE204, DE205</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 based NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=de&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Asante</p>
+</li>
+
+<li>
+<p>Cogent EM100FX and EM440TX</p>
+</li>
+
+<li>
+<p>DEC DE425, DE435, DE450, and DE500</p>
+</li>
+
+<li>
+<p>SMC Etherpower 8432T, 9332, and 9334</p>
+</li>
+
+<li>
+<p>ZYNX ZX 3xx</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>DEC/Intel 21143 based Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>DEC DE500</p>
+</li>
+
+<li>
+<p>Compaq Presario 7900 series built-in Ethernet</p>
+</li>
+
+<li>
+<p>D-Link DFE-570TX</p>
+</li>
+
+<li>
+<p>Kingston KNE100TX</p>
+</li>
+
+<li>
+<p>LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Davicom DM9009, DM9100 and DM9102 PCI Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Jaton Corporation XpressNet</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Conexant LANfinity RS7112 (MiniPCI) (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
+driver)</p>
+
+<p>Fujitsu MB86960A/MB86965A based Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fe</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>CONTEC C-NET(PC)C Ethernet</p>
+</li>
+
+<li>
+<p>Eiger Labs EPX-10BT</p>
+</li>
+
+<li>
+<p>Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 Ethernet PCMCIA</p>
+</li>
+
+<li>
+<p>Fujitsu Towa LA501 Ethernet</p>
+</li>
+
+<li>
+<p>HITACHI HT-4840-11</p>
+</li>
+
+<li>
+<p>NextCom J Link NC5310</p>
+</li>
+
+<li>
+<p>RATOC REX-5588, REX-9822, REX-4886, REX-R280</p>
+</li>
+
+<li>
+<p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Intel 82557- or 82559-based Fast Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p>
+</li>
+
+<li>
+<p>Intel InBusiness 10/100 PCI Network Adapter</p>
+</li>
+
+<li>
+<p>Intel PRO/100+ Management Adapter</p>
+</li>
+
+<li>
+<p>Intel Pro/100 VE Desktop Adapter</p>
+</li>
+
+<li>
+<p>Intel Pro/100 M Desktop Adapter</p>
+</li>
+
+<li>
+<p>Intel Pro/100 S Desktop, Server and Dual-Port Server Adapters</p>
+</li>
+
+<li>
+<p>On-board Ethernet NICs on many Intel motherboards.</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Intel 82595-based Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ex&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ex</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Intel EtherExpress Pro/10 and Pro/10+ Ethernet</p>
+</li>
+
+<li>
+<p>Olicom OC2220</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Intel 82586-based Ethernet NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ie&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ie</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3Com 3C507 Etherlink 16/TP</p>
+</li>
+
+<li>
+<p>AT&amp;T Starlan 10 and Starlan Fiber</p>
+</li>
+
+<li>
+<p>EN100</p>
+</li>
+
+<li>
+<p>Intel EtherExpress 16</p>
+</li>
+
+<li>
+<p>RACAL Interlan NI5210</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>3Com 3C5x9 Etherlink III NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ep</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3C509</p>
+</li>
+
+<li>
+<p>3C529 MCA</p>
+</li>
+
+<li>
+<p>3C579 EISA</p>
+</li>
+
+<li>
+<p>3CXE589EC, 3CXE589ET PCMCIA</p>
+</li>
+
+<li>
+<p>3C589/589B/589C/589D/589E/574TX/574B PC-card/PCMCIA</p>
+</li>
+
+<li>
+<p>Megahertz 3CCFEM556BI, 3CXEM556, 3CCFEM556B</p>
+</li>
+
+<li>
+<p>OfficeConnect 3CXSH572BT</p>
+</li>
+
+<li>
+<p>Farallon EtherMac</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>3Com 3C501 8-bit ISA Ethernet NIC (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=el&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">el</span>(4)</span></a>
+driver)</p>
+
+<p>3Com Etherlink XL-based NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3C900/905/905B/905C PCI</p>
+</li>
+
+<li>
+<p>3C556/556B MiniPCI</p>
+</li>
+
+<li>
+<p>3C450-TX HomeConnect adapter</p>
+</li>
+
+<li>
+<p>3c980/3c980B Fast Etherlink XL server adapter</p>
+</li>
+
+<li>
+<p>3cSOHO100-TX OfficeConnect adapter</p>
+</li>
+
+<li>
+<p>Dell Optiplex GX1 on-board 3C918</p>
+</li>
+
+<li>
+<p>Dell On-board 3C920</p>
+</li>
+
+<li>
+<p>Dell Precision on-board 3C905B</p>
+</li>
+
+<li>
+<p>Dell Latitude laptop docking station embedded 3C905-TX</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>3Com 3C59X series NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vx</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3C590 Etherlink III (PCI)</p>
+</li>
+
+<li>
+<p>3C595 Fast Etherlink III (PCI)</p>
+</li>
+
+<li>
+<p>3C592/3C597 (EISA)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Crystal Semiconductor CS89x0-based NICs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cs&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cs</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>IBM Etherjet ISA</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Megahertz X-Jack Ethernet PC-Card CC-10BT (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sn</span>(4)</span></a>
+driver)</p>
+
+<p>Xircom CreditCard adapters (16 bit) and workalikes (xe driver)</p>
+
+<ul>
+<li>
+<p>Accton EN2226/Fast EtherCard (16-bit version)</p>
+</li>
+
+<li>
+<p>Compaq Netelligent 10/100 PC Card</p>
+</li>
+
+<li>
+<p>Intel EtherExpress PRO/100 Mobile Adapter (16-bit version)</p>
+</li>
+
+<li>
+<p>Xircom 10/100 Network PC Card adapter</p>
+</li>
+
+<li>
+<p>Xircom Realport card + modem(Ethernet part)</p>
+</li>
+
+<li>
+<p>Xircom CreditCard Ethernet 10/100</p>
+</li>
+
+<li>
+<p>Xircom CreditCard 10Base-T ``CreditCard Ethernet Adapter IIps'' (PS-CE2-10)</p>
+</li>
+
+<li>
+<p>Xircom CreditCard Ethernet 10/100 + modem (Ethernet part)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>National Semiconductor DP8393X (SONIC) Ethernet cards (snc driver)</p>
+
+<ul>
+<li>
+<p>NEC PC-9801-83, -84, -103, and -104</p>
+</li>
+
+<li>
+<p>NEC PC-9801N-25 and -J02R</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Gigabit Ethernet cards based on the Level 1 LXT1001 NetCellerator controller (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>D-Link DGE-500SX</p>
+</li>
+
+<li>
+<p>SMC TigerCard 1000 (SMC9462SX)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Ethernet and Fast Ethernet NICs based on the 3Com 3XP Typhoon/Sidewinder (3CR990)
+chipset (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">txp</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3Com 3CR990-TX-95</p>
+</li>
+
+<li>
+<p>3Com 3CR990-TX-97</p>
+</li>
+
+<li>
+<p>3Com 3CR990B-SRV</p>
+</li>
+
+<li>
+<p>3Com 3CR990B-TXM</p>
+</li>
+
+<li>
+<p>3Com 3CR990SVR95</p>
+</li>
+
+<li>
+<p>3Com 3CR990SVR97</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Gigabit Ethernet NICs based on the Broadcom BCM570x (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>3Com 3c996-SX, 3c996-T</p>
+</li>
+
+<li>
+<p>Netgear GA302T</p>
+</li>
+
+<li>
+<p>SysKonnect SK-9D21 and 9D41</p>
+</li>
+
+<li>
+<p>Built-in Gigabit Ethernet NICs on DELL PowerEdge 2550 servers</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Gigabit Ethernet NICs based on the Intel 82542 and 82543 controller chips (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wx</span>(4)</span></a>, <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=gx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gx</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=em&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> drivers),
+plus NICs supported by the Intel 82540EM, 82544, 82545EM, and 82546EB controller chips
+(<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=em&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver
+only)</p>
+
+<ul>
+<li>
+<p>Intel PRO/1000 Gigabit Ethernet</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wx&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wx</span>(4)</span></a> driver is
+deprecated.</p>
+</blockquote>
+</div>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=em&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver is
+officially supported by Intel, but is only supported on the i386.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>Myson Ethernet NICs (my driver)</p>
+
+<ul>
+<li>
+<p>Myson MTD80X Based Fast Ethernet Card</p>
+</li>
+
+<li>
+<p>Myson MTD89X Based Gigabit Ethernet Card</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1342" name="AEN1342">3.3 FDDI Interfaces</a></h3>
+
+<p>DEC DEFPA PCI (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fpa</span>(4)</span></a>
+driver)</p>
+
+<p>DEC DEFEA EISA (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fpa</span>(4)</span></a>
+driver)</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1352" name="AEN1352">3.4 ATM Interfaces</a></h3>
+
+<p>Efficient Networks, Inc. ENI-155p ATM PCI Adapters (hea driver)</p>
+
+<p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa driver)</p>
+
+<p>The ATM support in FreeBSD supports the following signaling protocols:</p>
+
+<ul>
+<li>
+<p>The ATM Forum UNI 3.1 signaling protocol</p>
+</li>
+
+<li>
+<p>The ATM Forum UNI 3.0 signaling protocol</p>
+</li>
+
+<li>
+<p>The ATM Forum ILMI address registration</p>
+</li>
+
+<li>
+<p>FORE Systems' proprietary SPANS signaling protocol</p>
+</li>
+
+<li>
+<p>Permanent Virtual Channels (PVCs)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Support for the IETF ``Classical IP and ARP over ATM'' model is provided, compliant
+with the following RFCs and Internet Drafts:</p>
+
+<ul>
+<li>
+<p>RFC 1483, ``Multiprotocol Encapsulation over ATM Adaptation Layer 5''</p>
+</li>
+
+<li>
+<p>RFC 1577, ``Classical IP and ARP over ATM''</p>
+</li>
+
+<li>
+<p>RFC 1626, ``Default IP MTU for use over ATM AAL5''</p>
+</li>
+
+<li>
+<p>RFC 1755, ``ATM Signaling Support for IP over ATM''</p>
+</li>
+
+<li>
+<p>RFC 2225, ``Classical IP and ARP over ATM''</p>
+</li>
+
+<li>
+<p>RFC 2334, ``Server Cache Synchronization Protocol (SCSP)''</p>
+</li>
+
+<li>
+<p>Internet Draft <tt class="FILENAME">draft-ietf-ion-scsp-atmarp-00.txt</tt>, ``A
+Distributed ATMARP Service Using SCSP''</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Support for an ATM sockets interface is also provided.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1394" name="AEN1394">3.5 Wireless Network Interfaces</a></h3>
+
+<p>NCR / AT&amp;T / Lucent Technologies WaveLan T1-speed ISA/radio LAN cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wl</span>(4)</span></a>
+driver)</p>
+
+<p>Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and
+turbo speed (6Mbps) wireless network adapters and workalikes (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wi</span>(4)</span></a>
+driver)</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The ISA versions of these adapters are actually PCMCIA cards combined
+with an ISA to PCMCIA bridge card, so both kinds of devices work with the same
+driver.</p>
+</blockquote>
+</div>
+
+<ul>
+<li>
+<p>3COM 3crwe737A AirConnect Wireless LAN PC Card</p>
+</li>
+
+<li>
+<p>Accton airDirect WN3301</p>
+</li>
+
+<li>
+<p>Addtron AWA100</p>
+</li>
+
+<li>
+<p>Adtec ADLINK340APC</p>
+</li>
+
+<li>
+<p>Airway 802.11 Adapter</p>
+</li>
+
+<li>
+<p>Avaya Wireless PC Card</p>
+</li>
+
+<li>
+<p>Blue Concentric Circle CF Wireless LAN Model WL-379F</p>
+</li>
+
+<li>
+<p>BreezeNET PC-DS.11</p>
+</li>
+
+<li>
+<p>Buffalo WLI-CF-S11G</p>
+</li>
+
+<li>
+<p>Cabletron RoamAbout 802.11 DS</p>
+</li>
+
+<li>
+<p>Compaq WL100, WL110</p>
+</li>
+
+<li>
+<p>Corega KK Wireless LAN PCC-11, PCCA-11, PCCB-11</p>
+</li>
+
+<li>
+<p>D-Link DWL-650</p>
+</li>
+
+<li>
+<p>Dell TrueMobile 1150 Series</p>
+</li>
+
+<li>
+<p>ELECOM Air@Hawk/LD-WL11/PCC</p>
+</li>
+
+<li>
+<p>ELSA AirLancer MC-11</p>
+</li>
+
+<li>
+<p>Farallon Skyline 11Mbps Wireless</p>
+</li>
+
+<li>
+<p>ICOM SL-1100</p>
+</li>
+
+<li>
+<p>IBM High Rate Wireless LAN PC Card</p>
+</li>
+
+<li>
+<p>Intel PRO/Wireless 2011 LAN PC Card</p>
+</li>
+
+<li>
+<p>IO Data WN-B11/PCM</p>
+</li>
+
+<li>
+<p>Laneed Wireless card</p>
+</li>
+
+<li>
+<p>Linksys Instant Wireless WPC11</p>
+</li>
+
+<li>
+<p>Lucent WaveLAN/IEEE 802.11</p>
+</li>
+
+<li>
+<p>Melco Airconnect WLI-PCM-S11, WLI-PCM-L11</p>
+</li>
+
+<li>
+<p>NCR WaveLAN/IEEE 802.11</p>
+</li>
+
+<li>
+<p>NEC Wireless Card CMZ-RT-WP</p>
+</li>
+
+<li>
+<p>NEC Aterm WL11C (PC-WL/11C)</p>
+</li>
+
+<li>
+<p>NEC PK-WL001</p>
+</li>
+
+<li>
+<p>Netgear MA401</p>
+</li>
+
+<li>
+<p>PLANEX GeoWave/GW-NS110</p>
+</li>
+
+<li>
+<p>Proxim Harmony, RangeLAN-DS</p>
+</li>
+
+<li>
+<p>SMC 2632W, 2602W</p>
+</li>
+
+<li>
+<p>Sony PCWA-C100</p>
+</li>
+
+<li>
+<p>TDK LAK-CD011WL</p>
+</li>
+
+<li>
+<p>Toshiba Wireless LAN Card</p>
+</li>
+
+<li>
+<p>US Robotics Wireless Card 2410</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Aironet 802.11 wireless adapters (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=an&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">an</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Aironet 4500/4800 series (PCMCIA, PCI, and ISA adapters are all supported)</p>
+</li>
+
+<li>
+<p>Cisco Systems Aironet 340 and 350 series (PCMCIA, PCI, and ISA adapters are all
+supported)</p>
+</li>
+
+<li>
+<p>Xircom Wireless Ethernet adapter (rebadged Aironet)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Raytheon Raylink 2.4GHz wireless adapters (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ray&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ray</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Webgear Aviator</p>
+</li>
+
+<li>
+<p>Webgear Aviator Pro</p>
+</li>
+
+<li>
+<p>Raytheon Raylink PC Card</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>AMD Am79C930 and Harris (Intersil) based 802.11 cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=awi&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">awi</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>BayStack 650 and 660</p>
+</li>
+
+<li>
+<p>Farallon SkyLINE Wireless</p>
+</li>
+
+<li>
+<p>Icom SL-200</p>
+</li>
+
+<li>
+<p>Melco WLI-PCM</p>
+</li>
+
+<li>
+<p>NEL SSMagic</p>
+</li>
+
+<li>
+<p>Netwave AirSurfer Plus and AirSurfer Pro</p>
+</li>
+
+<li>
+<p>ZoomAir 4000</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1522" name="AEN1522">3.6 Miscellaneous Networks</a></h3>
+
+<p>Granch SBNI12 point-to-point communications adapters (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbni&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbni</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>SBNI12-XX and SBNI12D-XX ISA and PCI</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Granch SBNI16 SHDSL modems (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbsh&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbsh</span>(4)</span></a>
+driver)</p>
+
+<p>SMC COM90cx6 ARCNET network adapters (cm driver)</p>
+
+<ul>
+<li>
+<p>SMC 90c26, 90c56, and 90c66 in 90c56 compatability mode</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1539" name="AEN1539">3.7 ISDN Interfaces</a></h3>
+
+<p>AcerISDN P10 ISA PnP (experimental)</p>
+
+<p>Asuscom ISDNlink 128K ISA</p>
+
+<p>ASUSCOM P-IN100-ST-D (and other Winbond W6692-based cards)</p>
+
+<p>AVM</p>
+
+<ul>
+<li>
+<p>A1</p>
+</li>
+
+<li>
+<p>B1 ISA (tested with V2.0)</p>
+</li>
+
+<li>
+<p>B1 PCI (tested with V4.0)</p>
+</li>
+
+<li>
+<p>Fritz!Card classic</p>
+</li>
+
+<li>
+<p>Fritz!Card PnP</p>
+</li>
+
+<li>
+<p>Fritz!Card PCI</p>
+</li>
+
+<li>
+<p>Fritz!Card PCI, Version 2</p>
+</li>
+
+<li>
+<p>T1</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Creatix</p>
+
+<ul>
+<li>
+<p>ISDN-S0</p>
+</li>
+
+<li>
+<p>ISDN-S0 P&amp;P</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Compaq Microcom 610 ISDN (Compaq series PSB2222I) ISA PnP</p>
+
+<p>Dr. Neuhaus Niccy Go@ and compatibles</p>
+
+<p>Dynalink IS64PPH and IS64PPH+</p>
+
+<p>Eicon Diehl DIVA 2.0 and 2.02</p>
+
+<p>ELSA</p>
+
+<ul>
+<li>
+<p>ELSA PCC-16</p>
+</li>
+
+<li>
+<p>QuickStep 1000pro ISA</p>
+</li>
+
+<li>
+<p>MicroLink ISDN/PCI</p>
+</li>
+
+<li>
+<p>QuickStep 1000pro PCI</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ITK ix1 Micro ( &lt; V.3, non-PnP version )</p>
+
+<p>Sedlbauer Win Speed</p>
+
+<p>Siemens I-Surf 2.0</p>
+
+<p>TELEINT ISDN SPEED No.1 (experimental)</p>
+
+<p>Teles</p>
+
+<ul>
+<li>
+<p>S0/8</p>
+</li>
+
+<li>
+<p>S0/16</p>
+</li>
+
+<li>
+<p>S0/16.3</p>
+</li>
+
+<li>
+<p>S0/16.3 PnP</p>
+</li>
+
+<li>
+<p>16.3c ISA PnP (experimental)</p>
+</li>
+
+<li>
+<p>Teles PCI-TJ</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Traverse Technologies NETjet-S PCI</p>
+
+<p>USRobotics Sportster ISDN TA intern</p>
+
+<p>Winbond W6692 based PCI cards</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1603" name="AEN1603">3.8 Multi-port Serial
+Interfaces</a></h3>
+
+<p>AST 4 port serial card using shared IRQ</p>
+
+<p>ARNET serial cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ar&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ar</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>ARNET 8 port serial card using shared IRQ</p>
+</li>
+
+<li>
+<p>ARNET (now Digiboard) Sync 570/i high-speed serial</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Boca multi-port serial cards</p>
+
+<ul>
+<li>
+<p>Boca BB1004 4-Port serial card (Modems <span class="emphasis"><i
+class="EMPHASIS">not</i></span> supported)</p>
+</li>
+
+<li>
+<p>Boca IOAT66 6-Port serial card (Modems supported)</p>
+</li>
+
+<li>
+<p>Boca BB1008 8-Port serial card (Modems <span class="emphasis"><i
+class="EMPHASIS">not</i></span> supported)</p>
+</li>
+
+<li>
+<p>Boca BB2016 16-Port serial card (Modems supported)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Comtrol Rocketport card (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rp</span>(4)</span></a>
+driver)</p>
+
+<p>Cyclades Cyclom-Y serial board (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=cy&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cy</span>(4)</span></a>
+driver)</p>
+
+<p>STB 4 port card using shared IRQ</p>
+
+<p>DigiBoard intelligent serial cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dgb&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dgb</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>DigiBoard PC/Xe series</p>
+</li>
+
+<li>
+<p>DigiBoard PC/Xi series</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>PCI-Based multi-port serial boards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=puc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">puc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Actiontech 56K PCI</p>
+</li>
+
+<li>
+<p>Avlab Technology, PCI IO 2S and PCI IO 4S</p>
+</li>
+
+<li>
+<p>Comtrol RocketPort 550</p>
+</li>
+
+<li>
+<p>Decision Computers PCCOM 4-port serial and dual port RS232/422/485</p>
+</li>
+
+<li>
+<p>Dolphin Peripherals 4025/4035/4036</p>
+</li>
+
+<li>
+<p>IC Book Labs Dreadnought 16x Lite and Pro</p>
+</li>
+
+<li>
+<p>Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550</p>
+</li>
+
+<li>
+<p>Middle Digital, Weasle serial port</p>
+</li>
+
+<li>
+<p>Moxa Industio CP-114 and C168H/PCI</p>
+</li>
+
+<li>
+<p>NEC PK-UG-X001 and PK-UG-X008</p>
+</li>
+
+<li>
+<p>Netmos NM9835 PCI-2S-550</p>
+</li>
+
+<li>
+<p>Oxford Semiconductor OX16PCI954 PCI UART</p>
+</li>
+
+<li>
+<p>Syba Tech SD-LAB PCI-4S2P-550-ECP</p>
+</li>
+
+<li>
+<p>SIIG Cyber I/O PCI 16C550/16C650/16C850</p>
+</li>
+
+<li>
+<p>SIIG Cyber 2P1S PCI 16C550/16C650/16C850</p>
+</li>
+
+<li>
+<p>SIIG Cyber 2S1P PCI 16C550/16C650/16C850</p>
+</li>
+
+<li>
+<p>SIIG Cyber 4S PCI 16C550/16C650/16C850</p>
+</li>
+
+<li>
+<p>SIIG Cyber Serial (Single and Dual) PCI 16C550/16C650/16C850</p>
+</li>
+
+<li>
+<p>Syba Tech Ltd. PCI-4S2P-550-ECP</p>
+</li>
+
+<li>
+<p>Titan PCI-200H and PCI-800H</p>
+</li>
+
+<li>
+<p>US Robotics (3Com) 3CP5609 modem</p>
+</li>
+
+<li>
+<p>VScom PCI-400 and PCI-800</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>SDL Communication serial boards</p>
+
+<ul>
+<li>
+<p>SDL Communications Riscom/8 Serial Board (rc driver)</p>
+</li>
+
+<li>
+<p>SDL Communications RISCom/N2 and N2pci high-speed sync serial boards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sr</span>(4)</span></a>
+driver)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Stallion Technologies multiport serial boards</p>
+
+<ul>
+<li>
+<p>EasyIO (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=stl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">stl</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>EasyConnection 8/32 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=stl&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">stl</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>EasyConnection 8/64 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=stli&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">stli</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>ONboard 4/16 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=stli&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">stli</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Brumby (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=stli&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">stli</span>(4)</span></a>
+driver)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Specialix SI/XIO/SX multiport serial cards, with both the older SIHOST2.x and the new
+``enhanced'' (transputer based, aka JET) host cards (ISA, EISA and PCI are supported) (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=si&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">si</span>(4)</span></a>
+driver)</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1735" name="AEN1735">3.9 Audio Devices</a></h3>
+
+<p>Advance (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Asound 100 and 110</p>
+</li>
+
+<li>
+<p>Logic ALS120 and ALS4000</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>CMedia sound chips</p>
+
+<ul>
+<li>
+<p>CMI8338/CMI8738</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Crystal Semiconductor (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=csa&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">csa</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>CS461x/462x Audio Accelerator</p>
+</li>
+
+<li>
+<p>CS428x Audio Controller</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ENSONIQ (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>AudioPCI ES1370/1371</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ESS</p>
+
+<ul>
+<li>
+<p>ES1868, ES1869, ES1879 and ES1888 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbc</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Maestro-1, Maestro-2, and Maestro-2E</p>
+</li>
+
+<li>
+<p>Maestro-3/Allegro</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The Maestro-3/Allegro cannot be compiled into the FreeBSD kernel due to
+licensing restrictions. To use this driver, add the following line to <tt
+class="FILENAME">/boot/loader.conf</tt>:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">snd_maestro3_load="YES"</kbd>
+</pre>
+</blockquote>
+</div>
+</li>
+</ul>
+
+<br />
+<br />
+<p>ForteMedia fm801</p>
+
+<p>Gravis (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=gusc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gusc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>UltraSound MAX</p>
+</li>
+
+<li>
+<p>UltraSound PnP</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Intel 443MX, 810, 815, and 815E integrated sound devices (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a>
+driver)</p>
+
+<p>MSS/WSS Compatible DSPs (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a>
+driver)</p>
+
+<p>NeoMagic 256AV/ZX (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a>
+driver)</p>
+
+<p>OPTi 931/82C931 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a>
+driver)</p>
+
+<p>S3 Sonicvibes</p>
+
+<p>Creative Technologies SoundBlaster series (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbc</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>SoundBlaster</p>
+</li>
+
+<li>
+<p>SoundBlaster Pro</p>
+</li>
+
+<li>
+<p>SoundBlaster AWE-32</p>
+</li>
+
+<li>
+<p>SoundBlaster AWE-64</p>
+</li>
+
+<li>
+<p>SoundBlaster AWE-64 GOLD</p>
+</li>
+
+<li>
+<p>SoundBlaster ViBRA-16</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Creative Technologies Sound Blaster Live! series (emu10k1 driver)</p>
+
+<p>Trident 4DWave DX/NX (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a>
+driver)</p>
+
+<p>VIA Technologies VT82C686A</p>
+
+<p>Yamaha</p>
+
+<ul>
+<li>
+<p>DS1</p>
+</li>
+
+<li>
+<p>DS1e</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN1838" name="AEN1838">3.10 Camera and Video Capture
+Devices</a></h3>
+
+<p>Brooktree Bt848/849/878/879-based frame grabbers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bktr&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bktr</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>AverMedia cards</p>
+</li>
+
+<li>
+<p>Hauppauge Wincast TV and WinTV boards (PCI)</p>
+</li>
+
+<li>
+<p>Intel Smart Video Recorder III</p>
+</li>
+
+<li>
+<p>Miro PC TV</p>
+</li>
+
+<li>
+<p>STB TV PCI</p>
+</li>
+
+<li>
+<p>Video Highway XTreme</p>
+</li>
+
+<li>
+<p>VideoLogic Captivator PCI</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Connectix QuickCam</p>
+
+<p>Cortex1 frame grabber (ctx driver)</p>
+
+<p>Creative Labs Video Spigot frame grabber (spigot driver)</p>
+
+<p>Matrox Meteor Video frame grabber (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=meteor&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">meteor</span>(4)</span></a>
+driver)</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="USB" name="USB">3.11 USB Devices</a></h3>
+
+<p>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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> USB Ethernet adapters can be found in the section listing <a
+href="#ETHERNET">Ethernet interfaces</a>.</p>
+</blockquote>
+</div>
+
+<p>Host Controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a>
+drivers)</p>
+
+<ul>
+<li>
+<p>ALi Aladdin-V</p>
+</li>
+
+<li>
+<p>AMD-756</p>
+</li>
+
+<li>
+<p>Belkin USB 2.0 High Speed Host Controller</p>
+</li>
+
+<li>
+<p>CMD Tech 670 &#38; 673</p>
+</li>
+
+<li>
+<p>Intel 82371SB (PIIX3)</p>
+</li>
+
+<li>
+<p>Intel 82371AB and EB (PIIX4)</p>
+</li>
+
+<li>
+<p>Intel 82801AA (ICH)</p>
+</li>
+
+<li>
+<p>Intel 82801AB (ICH0)</p>
+</li>
+
+<li>
+<p>Intel 82801BA/BAM (ICH2)</p>
+</li>
+
+<li>
+<p>Intel 82443MX</p>
+</li>
+
+<li>
+<p>NEC uPD 9210</p>
+</li>
+
+<li>
+<p>OPTi 82C861 (FireLink)</p>
+</li>
+
+<li>
+<p>SiS 5571</p>
+</li>
+
+<li>
+<p>VIA 83C572 USB</p>
+</li>
+
+<li>
+<p>UHCI or OHCI compliant motherboard chipsets (no exceptions known)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>USB host controllers (PCI)</p>
+
+<ul>
+<li>
+<p>ADS Electronics PCI plug-in card (2 ports)</p>
+</li>
+
+<li>
+<p>Entrega PCI plug-in card (4 ports)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Hubs</p>
+
+<ul>
+<li>
+<p>Andromeda hub</p>
+</li>
+
+<li>
+<p>MacAlly self powered hub (4 ports)</p>
+</li>
+
+<li>
+<p>NEC hub</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Keyboards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Apple iMac keyboard</p>
+</li>
+
+<li>
+<p>BTC BTC7935 keyboard with PS/2 mouse port</p>
+</li>
+
+<li>
+<p>Cherry G81-3504 keyboard</p>
+</li>
+
+<li>
+<p>Logitech M2452 keyboard</p>
+</li>
+
+<li>
+<p>MacAlly iKey keyboard</p>
+</li>
+
+<li>
+<p>Microsoft keyboard</p>
+</li>
+
+<li>
+<p>Sun Microsystems Type 6 USB keyboard</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Miscellaneous</p>
+
+<ul>
+<li>
+<p>ActiveWire I/O Board</p>
+</li>
+
+<li>
+<p>Diamond Rio 500, 600, and 800 MP3 players (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=urio&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">urio</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>D-Link DSB-R100 USB Radio (ufm driver)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Modems (umodem driver)</p>
+
+<ul>
+<li>
+<p>3Com 5605</p>
+</li>
+
+<li>
+<p>Metricom Ricochet GS USB wireless modem</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Mice (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Agiler Mouse 29UO</p>
+</li>
+
+<li>
+<p>Apple iMac Mouse</p>
+</li>
+
+<li>
+<p>Belkin Mouse</p>
+</li>
+
+<li>
+<p>Chic mouse</p>
+</li>
+
+<li>
+<p>Cypress mouse</p>
+</li>
+
+<li>
+<p>Genius Niche mouse</p>
+</li>
+
+<li>
+<p>Kensington Mouse-in-a-Box</p>
+</li>
+
+<li>
+<p>Logitech wheel mouse (3 buttons)</p>
+</li>
+
+<li>
+<p>Logitech PS/2 / USB mouse (3 buttons)</p>
+</li>
+
+<li>
+<p>MacAlly mouse (3 buttons)</p>
+</li>
+
+<li>
+<p>Microsoft IntelliMouse (3 buttons)</p>
+</li>
+
+<li>
+<p>Sun Microsystems Type 6 USB Mouse</p>
+</li>
+
+<li>
+<p>Trust Ami Mouse (3 buttons)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Printers and parallel printer conversion cables (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ulpt</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>ATen parallel printer adapter</p>
+</li>
+
+<li>
+<p>Belkin F5U002 parallel printer adapter</p>
+</li>
+
+<li>
+<p>Entrega USB-to-parallel printer adapter</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Serial devices</p>
+
+<ul>
+<li>
+<p>Belkin F5U103 and F5U120 (ubsa driver)</p>
+</li>
+
+<li>
+<p>e-Tek Labs Kwik232 (ubsa driver)</p>
+</li>
+
+<li>
+<p>GoHubs GoCOM232 (ubsa driver)</p>
+</li>
+
+<li>
+<p>HP USB-Serial adapter (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uftdi</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Inland UAS111 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uftdi</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Peracom single port serial adapter (ubsa driver)</p>
+</li>
+
+<li>
+<p>Prolific PL-2303 serial adapter (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uplcom&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uplcom</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>QVS USC-1000 (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uftdi</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>SUNTAC Slipper U VS-10U (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uvscom&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uvscom</span>(4)</span></a>
+driver)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Scanners (through <b class="APPLICATION">SANE</b>) (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uscanner&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uscanner</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Perfection 636U</p>
+</li>
+
+<li>
+<p>HP ScanJet 4100C, 5200C, 6300C</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Storage (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umass</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Iomega USB Zip 100Mb (primitive support still)</p>
+</li>
+
+<li>
+<p>Matshita CF-VFDU03 floppy drive</p>
+</li>
+
+<li>
+<p>Microtech USB-SCSI-HD 50 USB to SCSI cable</p>
+</li>
+
+<li>
+<p>Panasonic floppy drive</p>
+</li>
+
+<li>
+<p>Y-E Data floppy drive (720/1.44/2.88Mb)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Handspring Visor and other PalmOS devices (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uvisor&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uvisor</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Handspring Visor</p>
+</li>
+
+<li>
+<p>Palm M125, M500, M505</p>
+</li>
+
+<li>
+<p>Sony Clie 4.0 and 4.1</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 IEEE 1394 (Firewire)
+Devices</a></h3>
+
+<p>Host Controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fwohci</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Ricoh R5C552 chipset</p>
+</li>
+
+<li>
+<p>Sony CX3022 chipset</p>
+</li>
+
+<li>
+<p>TI TSB12LV22, LV23, 26 and TSB43AA22 chipsets</p>
+</li>
+
+<li>
+<p>uPD72861 chipset</p>
+</li>
+
+<li>
+<p>VIA VT6306 chipset</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Storage (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbp&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbp</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Apple iPod</p>
+</li>
+
+<li>
+<p>Apple Macintosh G4 (target mode)</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN2099" name="AEN2099">3.13 Cryptographic Accelerators</a></h3>
+
+<p>Accelerators based on the Hifn 7751, 7811, or 7951 chipsets (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=hifn&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hifn</span>(4)</span></a>
+driver)</p>
+
+<ul>
+<li>
+<p>Invertex AEON</p>
+</li>
+
+<li>
+<p>Hifn 7751 reference board</p>
+</li>
+
+<li>
+<p>Global Technologies Group PowerCrypt and XL-Crypt</p>
+</li>
+
+<li>
+<p>NetSec 7751</p>
+</li>
+
+<li>
+<p>Soekris Engineering vpn1201 and vpn1211</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Accelerators based on the Bluesteel 5501 or 5601 chipsets (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsec</span>(4)</span></a>
+driver)</p>
+
+<p>Accelerators based on the Broadcom BCM5801, BCM5802, BCM5805, BCM5820, BCM 5821,
+BCM5822 chipsets (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsec</span>(4)</span></a>
+driver)</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN2124" name="AEN2124">3.14 Miscellaneous</a></h3>
+
+<p>FAX-Modem/PCCARD</p>
+
+<ul>
+<li>
+<p>Melco IGM-PCM56K/IGM-PCM56KH</p>
+</li>
+
+<li>
+<p>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Floppy drives (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=fdc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fdc</span>(4)</span></a>
+driver)</p>
+
+<p>Genius and Mustek hand scanners</p>
+
+<p>GPB and Transputer drivers</p>
+
+<p>VGA-compatible video cards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vga&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vga</span>(4)</span></a>
+driver)</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Information regarding specific video cards and compatibility with <b
+class="APPLICATION">XFree86</b> can be found at <a href="http://www.xfree86.org/"
+target="_top">http://www.xfree86.org/</a>.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>Keyboards including:</p>
+
+<ul>
+<li>
+<p>AT-style keyboards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>PS/2 keyboards (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>USB keyboards (specific instances are listed in the section describing <a
+href="#USB">USB devices</a>)</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Loran-C receiver (Dave Mills experimental hardware, loran driver).</p>
+
+<p>Pointing devices including:</p>
+
+<ul>
+<li>
+<p>Bus mice and compatible devices (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mse&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mse</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>PS/2 mice and compatible devices (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">psm</span>(4)</span></a>
+driver)</p>
+</li>
+
+<li>
+<p>Serial mice and compatible devices</p>
+</li>
+
+<li>
+<p>USB mice (specific instances are listed in the section describing <a href="#USB">USB
+devices</a>)</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> has
+more information on using pointing devices with FreeBSD. Information on using pointing
+devices with <b class="APPLICATION">XFree86</b> can be found at <a
+href="http://www.xfree86.org/" target="_top">http://www.xfree86.org/</a>.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>``PC standard'' parallel ports (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppc</span>(4)</span></a>
+driver)</p>
+
+<p>PC-compatible joysticks (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=joy&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">joy</span>(4)</span></a>
+driver)</p>
+
+<p>PHS Data Communication Card/PCCARD</p>
+
+<ul>
+<li>
+<p>NTT DoCoMo P-in Comp@ct</p>
+</li>
+
+<li>
+<p>Panasonic KX-PH405</p>
+</li>
+
+<li>
+<p>SII MC-P200</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>``PC standard'' 8250, 16450, and 16550-based serial ports (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a>
+driver)</p>
+
+<p>X-10 power controllers (<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=tw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tw</span>(4)</span></a>
+driver)</p>
+
+<p>Xilinx XC6200-based reconfigurable hardware cards compatible with the HOT1 from <a
+href="http://www.vcc.com/" target="_top">Virtual Computers</a> (xrpu driver).</p>
+</div>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+
diff --git a/en/releases/4.9R/installation-alpha.html b/en/releases/4.9R/installation-alpha.html
new file mode 100644
index 0000000000..fded85605d
--- /dev/null
+++ b/en/releases/4.9R/installation-alpha.html
@@ -0,0 +1,1711 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD/alpha 4.9-RELEASE Installation Instructions</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD/alpha 4.9-RELEASE Installation
+Instructions</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<hr />
+</div>
+
+<blockquote class="ABSTRACT">
+<div class="ABSTRACT"><a id="AEN11" name="AEN11"></a>
+<p>This article gives some brief instructions on installing FreeBSD/alpha 4.9-RELEASE,
+with particular emphasis given to obtaining a FreeBSD distribution. Some notes on
+troubleshooting and frequently-asked questions are also given.</p>
+</div>
+</blockquote>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN13" name="AEN13">1 Installing FreeBSD</a></h2>
+
+<p>This section documents the process of installing a new distribution of FreeBSD. These
+instructions pay particular emphasis to the process of obtaining the FreeBSD 4.9-RELEASE
+distribution and to beginning the installation procedure. The <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"
+target="_top">``Installing FreeBSD''</a> chapter of the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a> provides more in-depth information about the installation program itself,
+including a guided walkthrough with screenshots.</p>
+
+<p>If you are upgrading from a previous release of FreeBSD, please see <a
+href="#UPGRADING">Section 3</a> for instructions on upgrading.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="GETTING-STARTED" name="GETTING-STARTED">1.1 Getting
+Started</a></h3>
+
+<p>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 <tt
+class="FILENAME">README.TXT</tt>, which can usually be found in the same location as this
+file; most of these documents, such as the release notes and the hardware compatability
+list, are also accessible in the Documentation menu of the installer.</p>
+
+<p>Note that on-line versions of the FreeBSD <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/" target="_top">FAQ</a> and <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
+target="_top">Handbook</a> are also available from the <a href="http://www.FreeBSD.org/"
+target="_top">FreeBSD Project Web site</a>, if you have an Internet connection.</p>
+
+<p>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.</p>
+
+<p>The best laid plans sometimes go awry, so if you run into trouble take a look at <a
+href="#TROUBLE">Section 4</a>, which contains valuable troubleshooting information. You
+should also read an updated copy of <tt class="FILENAME">ERRATA.TXT</tt> before
+installing, since this will alert you to any problems which have reported in the interim
+for your particular release.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> While FreeBSD does its best to safeguard against accidental loss of
+data, it's still more than possible to <span class="emphasis"><i class="EMPHASIS">wipe
+out your entire disk</i></span> 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.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware Requirements</a></h3>
+
+<p>FreeBSD for the Alpha/AXP supports the platforms described in <tt
+class="FILENAME">HARDWARE.TXT</tt>.</p>
+
+<p>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.</p>
+
+<p>Your root filesystem MUST be the first partition (partition <var
+class="LITERAL">a</var>) on the disk to be bootable.</p>
+
+<p>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.</p>
+
+<p>If you are not familiar with configuring hardware for FreeBSD, you should be sure to
+read the <tt class="FILENAME">HARDWARE.TXT</tt> file; it contains important information
+on what hardware is supported by FreeBSD.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 Floppy Disk Image
+Instructions</a></h3>
+
+<p>Depending on how you choose to install FreeBSD, you may need to create a set of floppy
+disks (usually two) 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.</p>
+
+<p>For a normal CDROM or network installation, all you need to copy onto actual floppies
+from the <tt class="FILENAME">floppies/</tt> directory are the <tt
+class="FILENAME">kern.flp</tt> and <tt class="FILENAME">mfsroot.flp</tt> images (for
+1.44MB floppies).</p>
+
+<p>Getting these images over the network is easy. Simply fetch the <var
+class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/kern.flp</tt> and <var
+class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/mfsroot.flp</tt> files
+from <a href="ftp://ftp.FreeBSD.org/" target="_top">ftp://ftp.FreeBSD.org/</a> or one of
+the many mirrors listed at <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"
+target="_top">FTP Sites</a> section of the Handbook, or on the <a
+href="http://www.freebsdmirrors.org/" target="_top">http://www.freebsdmirrors.org/</a>
+Web pages.</p>
+
+<p>Get two blank, freshly formatted floppies and image copy <tt
+class="FILENAME">kern.flp</tt> onto one and <tt class="FILENAME">mfsroot.flp</tt> onto
+the other. These images are <span class="emphasis"><i class="EMPHASIS">not</i></span> 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 <tt class="FILENAME">fdimage.exe</tt> under DOS
+(see the <tt class="FILENAME">tools</tt> directory on your CDROM or FreeBSD FTP mirror)
+or the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dd&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dd</span>(1)</span></a> command in
+UNIX.</p>
+
+<p>For example, to create the kernel floppy image from DOS, you'd do something like
+this:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">C&#62;</samp> <kbd class="USERINPUT">fdimage kern.flp a:</kbd>
+</pre>
+
+<p>Assuming that you'd copied <tt class="FILENAME">fdimage.exe</tt> and <tt
+class="FILENAME">kern.flp</tt> into a directory somewhere. You would do the same for <tt
+class="FILENAME">mfsroot.flp</tt>, of course.</p>
+
+<p>If you're creating the boot floppy from a UNIX machine, you may find that:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">dd if=floppies/kern.flp of=/dev/rfd0</kbd>
+</pre>
+
+<p>or</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">dd if=floppies/kern.flp of=/dev/floppy</kbd>
+</pre>
+
+<p>work well, depending on your hardware and operating system environment (different
+versions of UNIX have different names for the floppy drive).</p>
+
+<p>If you're on an alpha machine that can network-boot its floppy images or you have a
+2.88MB or LS-120 floppy capable of taking a 2.88MB image on an x86 machine, you may wish
+to use the single (but twice as large) <tt class="FILENAME">boot.flp</tt> image. It
+contains the contents of <tt class="FILENAME">kern.flp</tt> and <tt
+class="FILENAME">mfsroot.flp</tt> on a single floppy. This file should also be used as
+the boot file for those mastering ``El Torito'' bootable CD images. See the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mkisofs&amp;sektion=8&amp;manpath=FreeBSD+Ports">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mkisofs</span>(8)</span></a>
+command for more information.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="START-INSTALLATION" name="START-INSTALLATION">1.4 Installing
+FreeBSD from CDROM or the Internet</a></h3>
+
+<p>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):</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt;<kbd class="USERINPUT">boot dka0</kbd>
+</pre>
+
+<p>Alternatively you can boot the installation from floppy disk. You should start the
+installation by building a set of FreeBSD boot floppies from the files <tt
+class="FILENAME">floppies/kern.flp</tt> and <tt
+class="FILENAME">floppies/mfsroot.flp</tt> using the instructions found in <a
+href="#FLOPPIES">Section 1.3</a>. From the SRM console prompt (<var
+class="LITERAL">&gt;&gt;&gt;</var>), just insert the <tt class="FILENAME">kern.flp</tt>
+floppy and type the following command to start the installation:</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt;<kbd class="USERINPUT">boot dva0</kbd>
+</pre>
+
+<p>Insert the <tt class="FILENAME">mfsroot.flp</tt> floppy when prompted and you will end
+up at the first screen of the install program.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN132" name="AEN132">1.5 Detail on various installation
+types</a></h3>
+
+<p>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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> If you get stuck at a screen, press the <b class="KEYCAP">F1</b> key for
+online documentation relevant to that specific section.</p>
+</blockquote>
+</div>
+
+<p>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 <span class="emphasis"><i
+class="EMPHASIS">exactly</i></span> what you want to do, use the ``Express'' or
+``Custom'' installation options. If you're upgrading an existing system, use the
+``Upgrade'' option.</p>
+
+<p>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.</p>
+
+<p>Once the install procedure has finished, you will be able to start FreeBSD/alpha by
+typing something like this to the SRM prompt:</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt;<kbd class="USERINPUT">boot dkc0</kbd>
+</pre>
+
+<p>This instructs the firmware to boot the specified disk. To find the SRM names of disks
+in your machine, use the <var class="LITERAL">show device</var> command:</p>
+
+<pre class="SCREEN">
+&gt;&gt;&gt;<kbd class="USERINPUT">show device</kbd>
+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
+</pre>
+
+<p>This example is from a Digital Personal Workstation 433au and shows three disks
+attached to the machine. The first is a CDROM called <tt class="DEVICENAME">dka0</tt> and
+the other two are disks and are called <tt class="DEVICENAME">dkc0</tt> and <tt
+class="DEVICENAME">dkc100</tt> repectively.</p>
+
+<p>You can specify which kernel file to load and what boot options to use with the <var
+class="OPTION">-file</var> and <var class="OPTION">-flags</var> options, for example:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">boot -file kernel.old -flags s</kbd>
+</pre>
+
+<p>To make FreeBSD/alpha boot automatically, use these commands:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd class="USERINPUT">set boot_osflags a</kbd>
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">set bootdef_dev dkc0</kbd>
+<samp class="PROMPT">&gt;&gt;&gt;</samp> <kbd
+class="USERINPUT">set auto_action BOOT</kbd>
+</pre>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN171" name="AEN171">1.5.1 Installing from a Network
+CDROM</a></h4>
+
+<p>If you simply wish to install from a local CDROM drive then see <a
+href="#START-INSTALLATION">Section 1.4</a>. 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:</p>
+
+<ul>
+<li>
+<p>If you would be able to FTP install FreeBSD directly from the CDROM drive in some
+FreeBSD machine, it's quite easy: You simply add the following line to the password file
+(using the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vipw</span>(8)</span></a>
+command):</p>
+
+<pre class="SCREEN">
+ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+</pre>
+
+<p>On the machine on which you are running the install, go to the Options menu and set
+Release Name to <var class="LITERAL">any</var>. You may then choose a Media type of <var
+class="LITERAL">FTP</var> and type in <tt class="FILENAME">ftp://<var
+class="REPLACEABLE">machine</var></tt> after picking ``URL'' in the ftp sites menu.</p>
+
+<div class="WARNING">
+<blockquote class="WARNING">
+<p><b>Warning:</b> This may allow anyone on the local network (or Internet) to make
+``anonymous FTP'' connections to this machine, which may not be desirable.</p>
+</blockquote>
+</div>
+</li>
+
+<li>
+<p>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 <tt
+class="FILENAME">/etc/exports</tt> file (on the machine with the CDROM drive). The
+example below allows the machine <tt class="HOSTID">ziggy.foo.com</tt> to mount the CDROM
+directly via NFS during installation:</p>
+
+<pre class="SCREEN">
+/cdrom          -ro             ziggy.foo.com
+</pre>
+
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.conf&amp;sektion=5&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rc.conf</span>(5)</span></a> and
+configure things appropriately. Assuming that this part goes smoothly, you should be able
+to enter: <tt class="FILENAME"><var class="REPLACEABLE">cdrom-host</var>:/cdrom</tt> as
+the path for an NFS installation when the target machine is installed, e.g. <tt
+class="FILENAME">wiggy:/cdrom</tt>.</p>
+</li>
+</ul>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN203" name="AEN203">1.5.2 Installing from Floppies</a></h4>
+
+<p>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.</p>
+
+<p>First, make your boot floppies as described in <a href="#FLOPPIES">Section
+1.3</a>.</p>
+
+<p>Second, peruse <a href="#LAYOUT">Section 2</a> 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.</p>
+
+<p>Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files
+in the <tt class="FILENAME">bin</tt> (binary distribution) directory. If you're preparing
+these floppies under DOS, then these floppies <span class="emphasis"><i
+class="EMPHASIS">must</i></span> be formatted using the MS-DOS <tt
+class="FILENAME">FORMAT</tt> command. If you're using Windows, use the Windows File
+Manager format command.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> 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.</p>
+</blockquote>
+</div>
+
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and
+<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>
+commands to put a UFS filesystem on a floppy, as the following sequence of commands
+illustrates:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">fdformat -f 1440 fd0.1440</kbd>
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">disklabel -w -r fd0.1440 floppy3</kbd>
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</kbd>
+</pre>
+
+<p>After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto
+them. The distribution files are split into chunks conveniently sized so that 5 of them
+will fit on a conventional 1.44MB floppy. Go through all your floppies, packing as many
+files as will fit on each one, until you've got all the distributions you want packed up
+in this fashion. Each distribution should go into its own subdirectory on the floppy,
+e.g.: <tt class="FILENAME">a:\bin\bin.inf</tt>, <tt class="FILENAME">a:\bin\bin.aa</tt>,
+<tt class="FILENAME">a:\bin\bin.ab</tt>, ...</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> The <tt class="FILENAME">bin.inf</tt> file also needs to go on the
+first floppy of the <tt class="FILENAME">bin</tt> 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 <tt class="FILENAME">distname.inf</tt> file <span class="emphasis"><i
+class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set. This
+is also covered in <tt class="FILENAME">README.TXT</tt>.</p>
+</blockquote>
+</div>
+
+<p>Once you come to the Media screen of the install, select ``Floppy'' and you'll be
+prompted for the rest.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN262" name="AEN262">1.5.4 Installing from QIC/SCSI
+Tape</a></h4>
+
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(1)</span></a> to get
+them onto the tape with a command something like this:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd <var
+class="REPLACEABLE">/where/you/have/your/dists</var></kbd>
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/rsa0 <var
+class="REPLACEABLE">dist1</var> .. <var class="REPLACEABLE">dist2</var></kbd>
+</pre>
+
+<p>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
+<span class="emphasis"><i class="EMPHASIS">full</i></span> 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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> When going to do the installation, the tape must be in the drive <span
+class="emphasis"><i class="EMPHASIS">before</i></span> booting from the boot floppies.
+The installation ``probe'' may otherwise fail to find it.</p>
+</blockquote>
+</div>
+
+<p>Now create a boot floppy as described in <a href="#FLOPPIES">Section 1.3</a> and
+proceed with the installation.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 Installing over a Network using FTP
+or NFS</a></h4>
+
+<p>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.</p>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN287" name="AEN287">1.5.5.1 Serial Port</a></h5>
+
+<p>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 I recommend
+that the PPP utility be used instead.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN293" name="AEN293">1.5.5.2 Parallel Port</a></h5>
+
+<p>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. <tt
+class="HOSTID">10.0.0.1</tt>, <tt class="HOSTID">10.0.0.2</tt>, etc).</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> If you use a Linux machine rather than a FreeBSD machine as your
+PLIP peer, you will also have to specify <var class="OPTION">link0</var> in the TCP/IP
+setup screen's ``extra options for ifconfig'' field in order to be compatible with
+Linux's slightly different PLIP protocol.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN304" name="AEN304">1.5.5.3 Ethernet</a></h5>
+
+<p>FreeBSD supports many common Ethernet cards; a table of supported cards is provided as
+part of the FreeBSD Hardware Notes (see <tt class="FILENAME">HARDWARE.TXT</tt> 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
+<span class="emphasis"><i class="EMPHASIS">before</i></span> the laptop is powered on.
+FreeBSD does not, unfortunately, currently support ``hot insertion'' of PCMCIA cards
+during installation.</p>
+
+<p>You will also need to know your IP address on the network, the <var
+class="OPTION">netmask</var> 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.</p>
+
+<p>If you do not know the answers to these questions then you should really probably talk
+to your system administrator <span class="emphasis"><i class="EMPHASIS">first</i></span>
+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.</p>
+
+<p>Once you have a network connection of some sort working, the installation can continue
+over NFS or FTP.</p>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN315" name="AEN315">1.5.5.4 NFS installation tips</a></h5>
+
+<p>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.</p>
+
+<p>If this server supports only ``privileged port'' access (this is generally the default
+for Sun and Linux workstations), you will need to set this option in the Options menu
+before installation can proceed.</p>
+
+<p>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.</p>
+
+<p>In order for NFS installation to work, the server must also support ``subdir mounts'',
+e.g. if your FreeBSD distribution directory lives on <tt
+class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, then <tt
+class="HOSTID">wiggy</tt> will have to allow the direct mounting of <tt
+class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not just <tt class="FILENAME">/usr</tt>
+or <tt class="FILENAME">/usr/archive/stuff</tt>.</p>
+
+<p>In FreeBSD's <tt class="FILENAME">/etc/exports</tt> file this is controlled by the
+<var class="OPTION">-alldirs</var> option. Other NFS servers may have different
+conventions. If you are getting <var class="LITERAL">Permission Denied</var> messages
+from the server then it's likely that you don't have this properly enabled.</p>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN332" name="AEN332">1.5.5.5 FTP Installation tips</a></h5>
+
+<p>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.</p>
+
+<p>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:</p>
+
+<pre class="SCREEN">
+ftp://216.66.64.162/pub/FreeBSD/releases/alpha/4.2-RELEASE
+</pre>
+
+<p>There are three FTP installation modes you can use:</p>
+
+<ul>
+<li>
+<p>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.</p>
+</li>
+
+<li>
+<p>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.</p>
+</li>
+
+<li>
+<p>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.</p>
+
+<p>In the rare case that you have an FTP proxy that does not go through HTTP, you can
+specify the URL as something like:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">ftp://foo.bar.com:<var
+class="REPLACEABLE">port</var>/pub/FreeBSD</kbd>
+</pre>
+
+<p>In the URL above, <var class="REPLACEABLE">port</var> is the port number of the proxy
+FTP server.</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN353" name="AEN353">1.5.6 Tips for Serial Console
+Users</a></h4>
+
+<p>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:</p>
+
+<div class="PROCEDURE">
+<ol type="1">
+<li>
+<p>Connect some sort of ANSI (vt100) compatible terminal or terminal emulation program to
+the <tt class="DEVICENAME">COM1</tt> port of the PC you are installing FreeBSD onto.</p>
+</li>
+
+<li>
+<p>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.</p>
+</li>
+
+<li>
+<p>If you don't get any output on your serial console, plug the keyboard in again and
+wait for some beeps. If you are booting from the CDROM, proceed to <a
+href="#HITSPACE">step 5</a> as soon as you hear the beep.</p>
+</li>
+
+<li>
+<p>For a floppy boot, the first beep means to remove the <tt
+class="FILENAME">kern.flp</tt> floppy and insert the <tt
+class="FILENAME">mfsroot.flp</tt> floppy, after which you should press <b
+class="KEYCAP">Enter</b> and wait for another beep.</p>
+</li>
+
+<li><a id="HITSPACE" name="HITSPACE"></a>
+<p>Hit the space bar, then enter</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">boot -h</kbd>
+</pre>
+
+<p>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.</p>
+</li>
+</ol>
+</div>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN375" name="AEN375">1.6 Question and Answer Section for
+Alpha/AXP Architecture Users</a></h3>
+
+<div class="QANDASET">
+<dl>
+<dt>1.6.1. <a href="#Q1.6.1.">Can I boot from the ARC or Alpha BIOS Console?</a></dt>
+
+<dt>1.6.2. <a href="#Q1.6.2.">Help! I have no space! Do I need to delete everything
+first?</a></dt>
+
+<dt>1.6.3. <a href="#Q1.6.3.">Can I mount my Compaq Tru64 or VMS extended
+partitions?</a></dt>
+
+<dt>1.6.4. <a href="#Q1.6.4.">What about support for Compaq Tru64 (OSF/1)
+binaries?</a></dt>
+
+<dt>1.6.5. <a href="#Q1.6.5.">What about support for Linux binaries?</a></dt>
+
+<dt>1.6.6. <a href="#Q1.6.6.">What about support for NT Alpha binaries?</a></dt>
+</dl>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.1." name="Q1.6.1."></a><b>1.6.1.</b> Can I boot from the ARC or Alpha BIOS
+Console?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>No. FreeBSD, like Compaq Tru64 and VMS, will only boot from the SRM
+console.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.2." name="Q1.6.2."></a><b>1.6.2.</b> Help! I have no space! Do I need to
+delete everything first?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Unfortunately, yes.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.3." name="Q1.6.3."></a><b>1.6.3.</b> Can I mount my Compaq Tru64 or VMS
+extended partitions?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>No, not at this time.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.4." name="Q1.6.4."></a><b>1.6.4.</b> What about support for Compaq Tru64
+(OSF/1) binaries?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>FreeBSD can run Tru64 applications very well using the <a
+href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/osf1_base/pkg-descr"><tt
+class="FILENAME">emulators/osf1_base</tt></a> port/package.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.5." name="Q1.6.5."></a><b>1.6.5.</b> What about support for Linux
+binaries?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>FreeBSD can run AlphaLinux binaries with the assistance of the <a
+href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/linux_base/pkg-descr"><tt
+class="FILENAME">emulators/linux_base</tt></a> port/package.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.6." name="Q1.6.6."></a><b>1.6.6.</b> What about support for NT Alpha
+binaries?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>FreeBSD is not able to run NT applications natively, although it has the
+ability to mount NT partitions.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 Distribution Format</a></h2>
+
+<p>A typical FreeBSD distribution directory looks something like this:</p>
+
+<pre class="SCREEN">
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    bin             compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+</pre>
+
+<p>If you want to do a CDROM, FTP or NFS installation from this distribution directory,
+all you need to do is make the 1.44MB boot floppies from the floppies directory (see <a
+href="#FLOPPIES">Section 1.3</a> for instructions on how to do this), boot them and
+follow the instructions. 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.</p>
+
+<p>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:</p>
+
+<ol type="1">
+<li>
+<p>The <tt class="FILENAME">*.TXT</tt> and <tt class="FILENAME">*.HTM</tt> files contain
+documentation (for example, this document is contained in both <tt
+class="FILENAME">INSTALL.TXT</tt> and <tt class="FILENAME">INSTALL.HTM</tt>) and should
+be read before starting an installation. The <tt class="FILENAME">*.TXT</tt> files are
+plain text, while the <tt class="FILENAME">*.HTM</tt> 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.</p>
+</li>
+
+<li>
+<p><tt class="FILENAME">docbook.css</tt> is a Cascading Style Sheet (CSS) file used by
+some Web browsers for formatting the HTML documentation.</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">bin</tt>, <tt class="FILENAME">catpages</tt>, <tt
+class="FILENAME">crypto</tt>, <tt class="FILENAME">dict</tt>, <tt
+class="FILENAME">doc</tt>, <tt class="FILENAME">games</tt>, <tt
+class="FILENAME">info</tt>, <tt class="FILENAME">manpages</tt>, <tt
+class="FILENAME">proflibs</tt>, and <tt class="FILENAME">src</tt> directories contain the
+primary distribution components of FreeBSD itself and are split into smaller files for
+easy packing onto floppies (should that be necessary).</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">compat1x</tt>, <tt class="FILENAME">compat20</tt>, <tt
+class="FILENAME">compat21</tt>, <tt class="FILENAME">compat22</tt>, <tt
+class="FILENAME">compat3x</tt>, and <tt class="FILENAME">compat4x</tt> 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
+<tt class="FILENAME">install.sh</tt> scripts.</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">floppies/</tt> subdirectory contains the floppy installation
+images; further information on using them can be found in <a href="#FLOPPIES">Section
+1.3</a>.</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">packages</tt> and <tt class="FILENAME">ports</tt> directories
+contain the FreeBSD Packages and Ports Collections. Packages may be installed from the
+packages directory by running the command:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp><kbd
+class="USERINPUT">/stand/sysinstall configPackages</kbd>
+</pre>
+
+<p>Packages can also be installed by feeding individual filenames in <tt
+class="FILENAME">packages</tt>/ to the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>
+command.</p>
+
+<p>The Ports Collection may be installed like any other distribution and requires about
+100MB unpacked. More information on the ports collection may be obtained from <a
+href="http://www.FreeBSD.org/ports/" target="_top">http://www.FreeBSD.org/ports/</a> or
+locally from <tt class="FILENAME">/usr/share/doc/handbook</tt> if you've installed the
+<tt class="FILENAME">doc</tt> distribution.</p>
+</li>
+
+<li>
+<p>Last of all, the <tt class="FILENAME">tools</tt> 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.</p>
+</li>
+</ol>
+
+<br />
+<br />
+<p>A typical distribution directory (for example, the <tt class="FILENAME">info</tt>
+distribution) looks like this internally:</p>
+
+<pre class="SCREEN">
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+</pre>
+
+<p>The <tt class="FILENAME">CHECKSUM.MD5</tt> 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 <tt class="FILENAME">info.a*</tt> files are split, gzip'd tar files, the
+contents of which can be viewed by doing:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cat info.a* | tar tvzf -</kbd>
+</pre>
+
+<p>During installation, they are automatically concatenated and extracted by the
+installation procedure.</p>
+
+<p>The <tt class="FILENAME">info.inf</tt> 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 <tt
+class="FILENAME">.inf</tt> file <span class="emphasis"><i
+class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set!</p>
+
+<p>The <tt class="FILENAME">info.mtree</tt> file is another non-essential file which is
+provided for user reference. It contains the MD5 signatures of the <span
+class="emphasis"><i class="EMPHASIS">unpacked</i></span> distribution files and can be
+later used with the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mtree</span>(8)</span></a> program
+to verify the installation permissions and checksums against any possible modifications
+to the file. When used with the <tt class="FILENAME">bin</tt> distribution, this can be
+an excellent way of detecting trojan horse attacks on your system.</p>
+
+<p>Finally, the <tt class="FILENAME">install.sh</tt> 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:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /cdrom/info</kbd>
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">sh install.sh</kbd>
+</pre>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 Upgrading FreeBSD</a></h2>
+
+<p>These instructions describe a procedure for doing a binary upgrade from an older
+version of FreeBSD.</p>
+
+<div class="WARNING">
+<blockquote class="WARNING">
+<p><b>Warning:</b> While the FreeBSD upgrade procedure does its best to safeguard against
+accidental loss of data, it is still more than possible to <span class="emphasis"><i
+class="EMPHASIS">wipe out your entire disk</i></span> with this installation! Please do
+not accept the final confirmation request unless you have adequately backed up any
+important data files.</p>
+</blockquote>
+</div>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> These notes assume that you are using the version of <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched
+version of <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> 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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+from an existing installation to upgrade to a newer version of FreeBSD. This is <span
+class="emphasis"><i class="EMPHASIS">not</i></span> recommended.</p>
+</blockquote>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN571" name="AEN571">3.1 Introduction</a></h3>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN575" name="AEN575">3.1.1 Upgrade Overview</a></h4>
+
+<p>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.</p>
+
+<p>System configuration is preserved by retaining and restoring the previous version of
+the following files:</p>
+
+<p><tt class="FILENAME">Xaccel.ini</tt>, <tt class="FILENAME">XF86Config</tt>, <tt
+class="FILENAME">adduser.conf</tt>, <tt class="FILENAME">aliases</tt>, <tt
+class="FILENAME">aliases.db</tt>, <tt class="FILENAME">amd.map</tt>, <tt
+class="FILENAME">crontab</tt>, <tt class="FILENAME">csh.cshrc</tt>, <tt
+class="FILENAME">csh.login</tt>, <tt class="FILENAME">csh.logout</tt>, <tt
+class="FILENAME">cvsupfile</tt>, <tt class="FILENAME">dhclient.conf</tt>, <tt
+class="FILENAME">disktab</tt>, <tt class="FILENAME">dm.conf</tt>, <tt
+class="FILENAME">dumpdates</tt>, <tt class="FILENAME">exports</tt>, <tt
+class="FILENAME">fbtab</tt>, <tt class="FILENAME">fstab</tt>, <tt
+class="FILENAME">ftpusers</tt>, <tt class="FILENAME">gettytab</tt>, <tt
+class="FILENAME">gnats</tt>, <tt class="FILENAME">group</tt>, <tt
+class="FILENAME">hosts</tt>, <tt class="FILENAME">host.conf</tt>, <tt
+class="FILENAME">hosts.allow</tt>, <tt class="FILENAME">hosts.equiv</tt>, <tt
+class="FILENAME">hosts.lpd</tt>, <tt class="FILENAME">inetd.conf</tt>, <tt
+class="FILENAME">kerberosIV</tt>, <tt class="FILENAME">localtime</tt>, <tt
+class="FILENAME">login.access</tt>, <tt class="FILENAME">login.conf</tt>, <tt
+class="FILENAME">mail</tt>, <tt class="FILENAME">mail.rc</tt>, <tt
+class="FILENAME">make.conf</tt>, <tt class="FILENAME">manpath.config</tt>, <tt
+class="FILENAME">master.passwd</tt>, <tt class="FILENAME">modems</tt>, <tt
+class="FILENAME">motd</tt>, <tt class="FILENAME">namedb</tt>, <tt
+class="FILENAME">networks</tt>, <tt class="FILENAME">newsyslog.conf</tt>, <tt
+class="FILENAME">nsmb.conf</tt>, <tt class="FILENAME">pam.conf</tt>, <tt
+class="FILENAME">passwd</tt>, <tt class="FILENAME">periodic</tt>, <tt
+class="FILENAME">ppp</tt>, <tt class="FILENAME">printcap</tt>, <tt
+class="FILENAME">profile</tt>, <tt class="FILENAME">pwd.db</tt>, <tt
+class="FILENAME">rc.conf</tt>, <tt class="FILENAME">rc.conf.local</tt>, <tt
+class="FILENAME">rc.firewall</tt>, <tt class="FILENAME">rc.local</tt>, <tt
+class="FILENAME">remote</tt>, <tt class="FILENAME">resolv.conf</tt>, <tt
+class="FILENAME">rmt</tt>, <tt class="FILENAME">sendmail.cf</tt>, <tt
+class="FILENAME">sendmail.cw</tt>, <tt class="FILENAME">services</tt>, <tt
+class="FILENAME">shells</tt>, <tt class="FILENAME">skeykeys</tt>, <tt
+class="FILENAME">spwd.db</tt>, <tt class="FILENAME">ssh</tt>, <tt
+class="FILENAME">syslog.conf</tt>, <tt class="FILENAME">ttys</tt>, <tt
+class="FILENAME">uucp</tt></p>
+
+<p>The versions of these files which correspond to the new version are moved to <tt
+class="FILENAME">/etc/upgrade/</tt>. 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.</p>
+
+<p>During the upgrade procedure, the administrator is prompted for a location into which
+all files from <tt class="FILENAME">/etc/</tt> are saved. In the event that local
+modifications have been made to other files, they may be subsequently retrieved from this
+location.</p>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN651" name="AEN651">3.2 Procedure</a></h3>
+
+<p>This section details the upgrade procedure. Particular attention is given to items
+which substantially differ from a normal installation.</p>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN654" name="AEN654">3.2.1 Backup</a></h4>
+
+<p>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.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN657" name="AEN657">3.2.2 Mount Filesystems</a></h4>
+
+<p>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. <span
+class="emphasis"><i class="EMPHASIS">Do not</i></span>set the ``newfs flag'' for any
+filesystems, as this will cause data loss.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN662" name="AEN662">3.2.3 Select Distributions</a></h4>
+
+<p>When selecting distributions, there are no constraints on which must be selected. As a
+general rule, the <var class="LITERAL">bin</var> distribution should be selected for an
+update, and the <var class="LITERAL">man</var> distribution if manpages are already
+installed. Other distributions may be selected beyond those originally installed if the
+administrator wishes to add additional functionality.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 After Installation</a></h4>
+
+<p>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 <tt
+class="FILENAME">/etc/rc.conf</tt> and <tt class="FILENAME">/etc/fstab</tt> files should
+be checked.</p>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN672" name="AEN672">3.3 Upgrading from Source Code</a></h3>
+
+<p>Those interested in an upgrade method that allows more flexibility and sophistication
+should take a look at <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html"
+target="_top">The Cutting Edge</a> 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.</p>
+
+<p><tt class="FILENAME">/usr/src/UPDATING</tt> 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.</p>
+
+<p></p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 Troubleshooting</a></h2>
+
+<div class="SECT2">
+<h3 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 Repairing an Existing FreeBSD
+Installation</a></h3>
+
+<p>FreeBSD features a ``Fixit'' option in the top menu of the boot floppy. To use it, you
+will also need either a <tt class="FILENAME">fixit.flp</tt> image floppy, generated in
+the same fashion as the boot floppy, or the ``live filesystem'' CDROM; typically the
+second CDROM in a multi-disc FreeBSD distribution.</p>
+
+<p>To invoke fixit, simply boot the <tt class="FILENAME">kern.flp</tt> floppy, choose the
+``Fixit'' item and insert the fixit floppy or CDROM when asked. You will then be placed
+into a shell with a wide variety of commands available (in the <tt
+class="FILENAME">/stand</tt> and <tt class="FILENAME">/mnt2/stand</tt> directories) for
+checking, repairing and examining file systems and their contents. Some UNIX
+administration experience <span class="emphasis"><i class="EMPHASIS">is</i></span>
+required to use the fixit option.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN693" name="AEN693">4.2 Common Installation Problems,
+Q&amp;A</a></h3>
+
+<div class="QANDASET">
+<dl>
+<dt>4.2.1. <a href="#Q4.2.1.">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:</a></dt>
+
+<dt>4.2.2. <a href="#Q4.2.2.">I go to boot from the hard disk for the first time after
+installing FreeBSD, but the Boot Manager prompt just prints <var class="LITERAL">F?</var>
+at the boot menu each time but the boot won't go any further.</a></dt>
+</dl>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.2.1." name="Q4.2.1."></a><b>4.2.1.</b> 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:</p>
+
+<pre class="SCREEN">
+changing root device to wd1s1a panic: cannot mount root
+</pre>
+
+<p>What is wrong? What can I do?</p>
+
+<p>What is this <var
+class="LITERAL">bios_drive:interface(unit,partition)kernel_name</var> thing that is
+displayed with the boot help?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+
+<p>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.</p>
+
+<p>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 <tt class="DEVICENAME">wd0</tt>
+and <tt class="DEVICENAME">wd2</tt>.</p>
+
+<p>FreeBSD is on BIOS disk 1, of type <var class="LITERAL">wd</var> and the FreeBSD disk
+number is 2, so you would say:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">1:wd(2,a)kernel</kbd>
+</pre>
+
+<p>Note that if you have a slave on the primary bus, the above is not necessary (and is
+effectively wrong).</p>
+
+<p>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 <var class="LITERAL">da</var> and FreeBSD disk number 0, so you would say:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">2:da(0,a)kernel</kbd>
+</pre>
+
+<p>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.</p>
+
+<p>Once you have determined the correct values to use, you can put the command exactly as
+you would have typed it in the <tt class="FILENAME">/boot.config</tt> file using a
+standard text editor. Unless instructed otherwise, FreeBSD will use the contents of this
+file as the default response to the <var class="LITERAL">boot:</var> prompt.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.2.2." name="Q4.2.2."></a><b>4.2.2.</b> I go to boot from the hard disk for
+the first time after installing FreeBSD, but the Boot Manager prompt just prints <var
+class="LITERAL">F?</var> at the boot menu each time but the boot won't go any
+further.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+
+<p>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.</p>
+
+<p>The following tip is no longer recommended, but is left here for reference:</p>
+
+<a id="AEN730" name="AEN730"></a>
+<blockquote class="BLOCKQUOTE">
+<p>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.</p>
+</blockquote>
+</div>
+</div>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN732" name="AEN732">4.3 Known Hardware Problems,
+Q&amp;A</a></h3>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Please send hardware tips for this section to Jordan K. Hubbard <code
+class="EMAIL">&#60;<a href="mailto:jkh@FreeBSD.org">jkh@FreeBSD.org</a>&#62;</code>.</p>
+</blockquote>
+</div>
+
+<div class="QANDASET">
+<dl>
+<dt>4.3.1. <a href="#Q4.3.1.">The <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">mcd</span>(4)</span> driver keeps thinking that it has found a
+device and this stops my Intel EtherExpress card from working.</a></dt>
+
+<dt>4.3.2. <a href="#Q4.3.2.">FreeBSD claims to support the 3Com PCMCIA card, but my card
+isn't recognized when it's plugged into my laptop.</a></dt>
+
+<dt>4.3.3. <a href="#Q4.3.3.">FreeBSD finds my PCMCIA network card, but no packets appear
+to be sent even though it claims to be working.</a></dt>
+
+<dt>4.3.4. <a href="#Q4.3.4.">The system finds my <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">ed</span>(4)</span> network card, but I keep getting device timeout
+errors.</a></dt>
+
+<dt>4.3.5. <a href="#Q4.3.5.">I booted the install floppy on my IBM ThinkPad (tm) laptop,
+and the keyboard is all messed up.</a></dt>
+
+<dt>4.3.6. <a href="#Q4.3.6.">When I try to boot the install floppy, I see the following
+message and nothing seems to be happening. I cannot enter anything from the keyboard
+either.</a></dt>
+
+<dt>4.3.7. <a href="#Q4.3.7.">I have a Matsushita/Panasonic CR-522, a
+Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is not recognized even when the
+correct I/O port is set.</a></dt>
+
+<dt>4.3.8. <a href="#Q4.3.8.">I'm trying to install from a tape drive but all I get is
+something like this on the screen:</a></dt>
+
+<dt>4.3.9. <a href="#Q4.3.9.">I've installed FreeBSD onto my system, but it hangs when
+booting from the hard drive with the message:</a></dt>
+
+<dt>4.3.10. <a href="#Q4.3.10.">My system can not find my Intel EtherExpress 16
+card.</a></dt>
+
+<dt>4.3.11. <a href="#Q4.3.11.">When installing on an EISA HP Netserver, my on-board
+AIC-7xxx SCSI controller isn't detected.</a></dt>
+
+<dt>4.3.12. <a href="#Q4.3.12.">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.</a></dt>
+
+<dt>4.3.13. <a href="#Q4.3.13.">I have this CMD640 IDE controller that is said to be
+broken.</a></dt>
+
+<dt>4.3.14. <a href="#Q4.3.14.">On a Compaq Aero notebook, I get the message ``No floppy
+devices found! Please check ...'' when trying to install from floppy.</a></dt>
+
+<dt>4.3.15. <a href="#Q4.3.15.">When I go to boot my Intel AL440LX (``Atlanta'') -based
+system from the hard disk the first time, it stops with a <var class="LITERAL">Read
+Error</var> message.</a></dt>
+
+<dt>4.3.16. <a href="#Q4.3.16.">When installing on an Dell Poweredge XE, Dell proprietary
+RAID controller DSA (Dell SCSI Array) isn't recognized.</a></dt>
+
+<dt>4.3.17. <a href="#Q4.3.17.">My Ethernet adapter is detected as an AMD PCnet-FAST (or
+similar) but it doesn't work. (Eg. onboard Ethernet on IBM Netfinity 5xxx or
+7xxx)</a></dt>
+
+<dt>4.3.18. <a href="#Q4.3.18.">I have an IBM EtherJet PCI card, it is detected by the
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span> driver
+correctly, but the lights on the card don't come on and it doesn't connect to the
+network.</a></dt>
+
+<dt>4.3.19. <a href="#Q4.3.19.">When I configure the network during installation on an
+IBM Netfinity 3500, the system freezes.</a></dt>
+
+<dt>4.3.20. <a href="#Q4.3.20.">When I install onto a drive managed by a Mylex PCI RAID
+controller, the system fails to boot (eg. with a <var class="LITERAL">read error</var>
+message).</a></dt>
+</dl>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.1." name="Q4.3.1."></a><b>4.3.1.</b> The <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">mcd</span>(4)</span> driver keeps thinking that it has found a
+device and this stops my Intel EtherExpress card from working.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Use the UserConfig utility (see <tt class="FILENAME">HARDWARE.TXT</tt>) and
+disable the probing of the <tt class="DEVICENAME">mcd0</tt> and <tt
+class="DEVICENAME">mcd1</tt> devices. Generally speaking, you should only leave the
+devices that you will be using enabled in your kernel.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.2." name="Q4.3.2."></a><b>4.3.2.</b> FreeBSD claims to support the 3Com
+PCMCIA card, but my card isn't recognized when it's plugged into my laptop.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>There are a couple of possible problems. First of all, FreeBSD does not support
+multi-function cards, so if you have a combo Ethernet/modem card (such as the 3C562), it
+won't work. The default driver for the 3C589 card was written just like all of the other
+drivers in FreeBSD, and depend on the card's own configuration data stored in NVRAM to
+work. You must correctly configure FreeBSD's driver to match the IRQ, port, and IOMEM
+stored in NVRAM.</p>
+
+<p>Unfortunately, the only program capable of reading them is the 3COM supplied DOS
+program. This program must be run on a absolutely clean system (no other drivers must be
+running), and the program will whine about CARD-Services not being found, but it will
+continue. This is necessary to read the NVRAM values. You want to know the IRQ, port, and
+IOMEM values (the latter is called the CIS tuple by 3COM). The first two can be set in
+the program, the third is un-settable, and can only be read. Once you have these values,
+set them in UserConfig and your card will be recognized.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.3." name="Q4.3.3."></a><b>4.3.3.</b> FreeBSD finds my PCMCIA network card,
+but no packets appear to be sent even though it claims to be working.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Many PCMCIA cards have the ability to use either the 10-Base2 (BNC) or 10-BaseT
+connectors for connecting to the network. The driver is unable to ``auto-select'' the
+correct connector, so you must tell it which connector to use. In order to switch between
+the two connectors, the link flags must be set. Depending on the model of the card, <var
+class="OPTION">-link0 link1</var> or <var class="OPTION">-link0 -link1</var> will choose
+the correct network connector. You can set these in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> by
+using the <var class="LITERAL">Extra options to ifconfig:</var> field in the network
+setup screen.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.4." name="Q4.3.4."></a><b>4.3.4.</b> The system finds my <span
+class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span> network card, but I
+keep getting device timeout errors.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Your card is probably on a different IRQ from what is specified in the kernel
+configuration. 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
+<var class="LITERAL">?</var> in the IRQ field of your kernel config file.</p>
+
+<p>Either move the jumper on the card to a hard configuration setting (altering the
+kernel settings if necessary), or specify the IRQ as <var class="LITERAL">-1</var> in
+UserConfig or <var class="LITERAL">?</var> in your kernel config file. This will tell the
+kernel to use the soft configuration.</p>
+
+<p>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.5." name="Q4.3.5."></a><b>4.3.5.</b> I booted the install floppy on my IBM
+ThinkPad (tm) laptop, and the keyboard is all messed up.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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. Change
+the atkbd0 'Flags' to 0x4 in UserConfig and it should work fine. (Look in the Input Menu
+for 'Keyboard'.)</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.6." name="Q4.3.6."></a><b>4.3.6.</b> When I try to boot the install
+floppy, I see the following message and nothing seems to be happening. I cannot enter
+anything from the keyboard either.</p>
+
+<pre class="SCREEN">
+Keyboard: no
+</pre>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Due to lack of space, full support for old XT/AT (84-key) keyboards is no
+longer available in the bootblocks. Some notebook computers may also have this type of
+keyboard. If you are still using this kind of hardware, you will see the above message
+appears when you boot from the CD-ROM or an install floppy.</p>
+
+<p>As soon as you see this message, hit the space bar, and you will see the prompt:</p>
+
+<pre class="SCREEN">
+&#62;&#62; FreeBSD/i386 BOOT
+Default: x:xx(x,x)/boot/loader 
+boot:
+</pre>
+
+<p>Then enter <kbd class="USERINPUT">-Dh</kbd>, and things should proceed normally.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.7." name="Q4.3.7."></a><b>4.3.7.</b> I have a Matsushita/Panasonic CR-522,
+a Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is not recognized even when
+the correct I/O port is set.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>These CD-ROM drives are currently not supported by FreeBSD. The command sets
+for these drives are not compatible with the double-speed CR-562 and CR-563 drives.</p>
+
+<p>The single-speed CR-522 and CR-523 drives can be identified by their use of a
+CD-caddy.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.8." name="Q4.3.8."></a><b>4.3.8.</b> I'm trying to install from a tape
+drive but all I get is something like this on the screen:</p>
+
+<pre class="SCREEN">
+sa0(aha0:1:0) NOT READY csi 40,0,0,0
+</pre>
+</div>
+
+<div class="ANSWER">
+<p><b></b>There's a limitation in the current <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+that the tape <span class="emphasis"><i class="EMPHASIS">must</i></span> be in the drive
+while <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> is
+started or it won't be detected. Try again with the tape in the drive the whole time.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.9." name="Q4.3.9."></a><b>4.3.9.</b> I've installed FreeBSD onto my
+system, but it hangs when booting from the hard drive with the message:</p>
+
+<pre class="SCREEN">
+Changing root to /dev/da0a
+</pre>
+</div>
+
+<div class="ANSWER">
+<p><b></b>his problem may occur in a system with a 3com 3c509 Ethernet adapter. The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ep</span>(4)</span></a> device
+driver appears to be sensitive to probes for other devices that also use address 0x300.
+Boot your FreeBSD system by power cycling the machine (turn off and on). At the <var
+class="LITERAL">Boot:</var> prompt specify the <var class="OPTION">-c</var>. This will
+invoke UserConfig (see <a href="#REPAIRING">Section 4.1</a> above). Use the <var
+class="LITERAL">disable</var> command to disable the device probes for all devices at
+address 0x300 except the ep0 driver. On exit, your machine should successfully boot
+FreeBSD.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.10." name="Q4.3.10."></a><b>4.3.10.</b> My system can not find my Intel
+EtherExpress 16 card.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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 <tt
+class="FILENAME">softset.exe</tt> program.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.11." name="Q4.3.11."></a><b>4.3.11.</b> When installing on an EISA HP
+Netserver, my on-board AIC-7xxx SCSI controller isn't detected.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>This is a known problem, and will hopefully be fixed in the future. In order to
+get your system installed at all, boot with the <var class="OPTION">-c</var> option into
+UserConfig, but <span class="emphasis"><i class="EMPHASIS">don't</i></span> use the
+pretty visual mode but the plain old CLI mode. Type:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">eisa 12</kbd>
+<kbd class="USERINPUT">quit</kbd>
+</pre>
+
+<p>at the prompt. (Instead of `quit', you might also type `visual', and continue the rest
+of the configuration session in visual mode.) While it's recommended to compile a custom
+kernel, dset now also understands to save this value.</p>
+
+<p>Refer to the FAQ topic 3.16 for an explanation of the problem, and for how to
+continue. Remember that you can find the FAQ on your local system in /usr/share/doc/FAQ,
+provided you have installed the `doc' distribution.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.12." name="Q4.3.12."></a><b>4.3.12.</b> 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.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Your machine doesn't like the new <var class="LITERAL">i586_copyout</var> and
+<var class="LITERAL">i586_copyin</var> code for some reason. To disable this, boot the
+installation boot floppy and when it comes to the very first menu (the choice to drop
+into kernel UserConfig mode or not) choose the command-line interface (``expert mode'')
+version and type the following at it:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">flags npx0 1</kbd>
+</pre>
+
+<p>Then proceed normally to boot. This will be saved into your kernel, so you only need
+to do it once.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.13." name="Q4.3.13."></a><b>4.3.13.</b> I have this CMD640 IDE controller
+that is said to be broken.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Yes, it is. FreeBSD does not support this controller except through the legacy
+wdc driver.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.14." name="Q4.3.14."></a><b>4.3.14.</b> On a Compaq Aero notebook, I get
+the message ``No floppy devices found! Please check ...'' when trying to install from
+floppy.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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. Go to the UserConfig screen, and set
+the Flags value of the fdc0 device to 0x1. This pretends the existence of the first
+floppy drive (as a 1.44 MB drive) to the driver without asking the CMOS at all.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.15." name="Q4.3.15."></a><b>4.3.15.</b> When I go to boot my Intel AL440LX
+(``Atlanta'') -based system from the hard disk the first time, it stops with a <var
+class="LITERAL">Read Error</var> message.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>There appears to be a bug in the BIOS on at least some of these boards, this
+bug results in the FreeBSD bootloader thinking that it is booting from a floppy disk.
+This is only a problem if you are not using the BootEasy boot manager. Slice the disk in
+``compatible''mode and install BootEasy during the FreeBSD installation to avoid the bug,
+or upgrade the BIOS (see Intel's website for details).</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.16." name="Q4.3.16."></a><b>4.3.16.</b> When installing on an Dell
+Poweredge XE, Dell proprietary RAID controller DSA (Dell SCSI Array) isn't
+recognized.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.17." name="Q4.3.17."></a><b>4.3.17.</b> My Ethernet adapter is detected as
+an AMD PCnet-FAST (or similar) but it doesn't work. (Eg. onboard Ethernet on IBM
+Netfinity 5xxx or 7xxx)</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver is
+currently faulty, and will often not work correctly with the PCnet-FAST and PCnet-FAST+.
+You need to install a different Ethernet adapter.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.18." name="Q4.3.18."></a><b>4.3.18.</b> I have an IBM EtherJet PCI card,
+it is detected by the <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">fxp</span>(4)</span> driver correctly, but the lights on the card
+don't come on and it doesn't connect to the network.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.19." name="Q4.3.19."></a><b>4.3.19.</b> When I configure the network
+during installation on an IBM Netfinity 3500, the system freezes.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.20." name="Q4.3.20."></a><b>4.3.20.</b> When I install onto a drive
+managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a <var
+class="LITERAL">read error</var> message).</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+
diff --git a/en/releases/4.9R/installation-i386.html b/en/releases/4.9R/installation-i386.html
new file mode 100644
index 0000000000..345a5b5bd8
--- /dev/null
+++ b/en/releases/4.9R/installation-i386.html
@@ -0,0 +1,1706 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD/i386 4.9-RELEASE Installation Instructions</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD/i386 4.9-RELEASE Installation
+Instructions</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<hr />
+</div>
+
+<blockquote class="ABSTRACT">
+<div class="ABSTRACT"><a id="AEN11" name="AEN11"></a>
+<p>This article gives some brief instructions on installing FreeBSD/i386 4.9-RELEASE,
+with particular emphasis given to obtaining a FreeBSD distribution. Some notes on
+troubleshooting and frequently-asked questions are also given.</p>
+</div>
+</blockquote>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN13" name="AEN13">1 Installing FreeBSD</a></h2>
+
+<p>This section documents the process of installing a new distribution of FreeBSD. These
+instructions pay particular emphasis to the process of obtaining the FreeBSD 4.9-RELEASE
+distribution and to beginning the installation procedure. The <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"
+target="_top">``Installing FreeBSD''</a> chapter of the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a> provides more in-depth information about the installation program itself,
+including a guided walkthrough with screenshots.</p>
+
+<p>If you are upgrading from a previous release of FreeBSD, please see <a
+href="#UPGRADING">Section 3</a> for instructions on upgrading.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="GETTING-STARTED" name="GETTING-STARTED">1.1 Getting
+Started</a></h3>
+
+<p>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 <tt
+class="FILENAME">README.TXT</tt>, which can usually be found in the same location as this
+file; most of these documents, such as the release notes and the hardware compatability
+list, are also accessible in the Documentation menu of the installer.</p>
+
+<p>Note that on-line versions of the FreeBSD <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/" target="_top">FAQ</a> and <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
+target="_top">Handbook</a> are also available from the <a href="http://www.FreeBSD.org/"
+target="_top">FreeBSD Project Web site</a>, if you have an Internet connection.</p>
+
+<p>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.</p>
+
+<p>The best laid plans sometimes go awry, so if you run into trouble take a look at <a
+href="#TROUBLE">Section 4</a>, which contains valuable troubleshooting information. You
+should also read an updated copy of <tt class="FILENAME">ERRATA.TXT</tt> before
+installing, since this will alert you to any problems which have reported in the interim
+for your particular release.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> While FreeBSD does its best to safeguard against accidental loss of
+data, it's still more than possible to <span class="emphasis"><i class="EMPHASIS">wipe
+out your entire disk</i></span> 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.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware Requirements</a></h3>
+
+<p>FreeBSD for the i386 requires an 80386 or better processor. The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+installation program requires 16MB of RAM; after installation, FreeBSD itself can be run
+in 4-8MB of RAM with a pared-down kernel. You will need at least 100MB of free hard drive
+space for the most minimal installation; a more realistic minimum is on the order of
+250-350MB. See below for ways of shrinking existing DOS partitions in order to install
+FreeBSD.</p>
+
+<p>If you are not familiar with configuring hardware for FreeBSD, you should be sure to
+read the <tt class="FILENAME">HARDWARE.TXT</tt> file; it contains important information
+on what hardware is supported by FreeBSD.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 Floppy Disk Image
+Instructions</a></h3>
+
+<p>Depending on how you choose to install FreeBSD, you may need to create a set of floppy
+disks (usually two) 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.</p>
+
+<p>For a normal CDROM or network installation, all you need to copy onto actual floppies
+from the <tt class="FILENAME">floppies/</tt> directory are the <tt
+class="FILENAME">kern.flp</tt> and <tt class="FILENAME">mfsroot.flp</tt> images (for
+1.44MB floppies).</p>
+
+<p>Getting these images over the network is easy. Simply fetch the <var
+class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/kern.flp</tt> and <var
+class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/mfsroot.flp</tt> files
+from <a href="ftp://ftp.FreeBSD.org/" target="_top">ftp://ftp.FreeBSD.org/</a> or one of
+the many mirrors listed at <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"
+target="_top">FTP Sites</a> section of the Handbook, or on the <a
+href="http://www.freebsdmirrors.org/" target="_top">http://www.freebsdmirrors.org/</a>
+Web pages.</p>
+
+<p>Get two blank, freshly formatted floppies and image copy <tt
+class="FILENAME">kern.flp</tt> onto one and <tt class="FILENAME">mfsroot.flp</tt> onto
+the other. These images are <span class="emphasis"><i class="EMPHASIS">not</i></span> 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 <tt class="FILENAME">fdimage.exe</tt> under DOS
+(see the <tt class="FILENAME">tools</tt> directory on your CDROM or FreeBSD FTP mirror)
+or the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dd&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dd</span>(1)</span></a> command in
+UNIX.</p>
+
+<p>For example, to create the kernel floppy image from DOS, you'd do something like
+this:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">C&#62;</samp> <kbd class="USERINPUT">fdimage kern.flp a:</kbd>
+</pre>
+
+<p>Assuming that you'd copied <tt class="FILENAME">fdimage.exe</tt> and <tt
+class="FILENAME">kern.flp</tt> into a directory somewhere. You would do the same for <tt
+class="FILENAME">mfsroot.flp</tt>, of course.</p>
+
+<p>If you're creating the boot floppy from a UNIX machine, you may find that:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">dd if=floppies/kern.flp of=/dev/rfd0</kbd>
+</pre>
+
+<p>or</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">dd if=floppies/kern.flp of=/dev/floppy</kbd>
+</pre>
+
+<p>work well, depending on your hardware and operating system environment (different
+versions of UNIX have different names for the floppy drive).</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="START-INSTALLATION" name="START-INSTALLATION">1.4 Installing
+FreeBSD from CDROM or the Internet</a></h3>
+
+<p>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:</p>
+
+<ul>
+<li>
+<p>If your system supports bootable CDROM media (usually an option which can be
+selectively enabled in the controller's setup menu or in the PC BIOS for some systems)
+and you have it enabled, FreeBSD supports the ``El Torrito'' bootable CD standard. Simply
+put the installation CD in your CDROM drive and boot the system to begin
+installation.</p>
+</li>
+
+<li>
+<p>Build a set of FreeBSD boot floppies from the <tt class="FILENAME">floppies/</tt>
+directory in every FreeBSD distribution. Either simply use the <tt
+class="FILENAME">makeflp.bat</tt> script from DOS or read <a href="#FLOPPIES">Section
+1.3</a> 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.</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>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
+<tt class="FILENAME">floppies/kern.flp</tt> and <tt
+class="FILENAME">floppies/mfsroot.flp</tt> using the instructions found in <a
+href="#FLOPPIES">Section 1.3</a>. Restart your computer using the <tt
+class="FILENAME">kern.flp</tt> disk; when prompted, insert the <tt
+class="FILENAME">mfsroot.flp</tt> disk. Then, please go to <a href="#FTPNFS">Section
+1.5.5</a> for additional tips on installing via FTP or NFS.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN132" name="AEN132">1.5 Detail on various installation
+types</a></h3>
+
+<p>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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> If you get stuck at a screen, press the <b class="KEYCAP">F1</b> key for
+online documentation relevant to that specific section.</p>
+</blockquote>
+</div>
+
+<p>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 <span class="emphasis"><i
+class="EMPHASIS">exactly</i></span> what you want to do, use the ``Express'' or
+``Custom'' installation options. If you're upgrading an existing system, use the
+``Upgrade'' option.</p>
+
+<p>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.</p>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN171" name="AEN171">1.5.1 Installing from a Network
+CDROM</a></h4>
+
+<p>If you simply wish to install from a local CDROM drive then see <a
+href="#START-INSTALLATION">Section 1.4</a>. 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:</p>
+
+<ul>
+<li>
+<p>If you would be able to FTP install FreeBSD directly from the CDROM drive in some
+FreeBSD machine, it's quite easy: You simply add the following line to the password file
+(using the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vipw</span>(8)</span></a>
+command):</p>
+
+<pre class="SCREEN">
+ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+</pre>
+
+<p>On the machine on which you are running the install, go to the Options menu and set
+Release Name to <var class="LITERAL">any</var>. You may then choose a Media type of <var
+class="LITERAL">FTP</var> and type in <tt class="FILENAME">ftp://<var
+class="REPLACEABLE">machine</var></tt> after picking ``URL'' in the ftp sites menu.</p>
+
+<div class="WARNING">
+<blockquote class="WARNING">
+<p><b>Warning:</b> This may allow anyone on the local network (or Internet) to make
+``anonymous FTP'' connections to this machine, which may not be desirable.</p>
+</blockquote>
+</div>
+</li>
+
+<li>
+<p>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 <tt
+class="FILENAME">/etc/exports</tt> file (on the machine with the CDROM drive). The
+example below allows the machine <tt class="HOSTID">ziggy.foo.com</tt> to mount the CDROM
+directly via NFS during installation:</p>
+
+<pre class="SCREEN">
+/cdrom          -ro             ziggy.foo.com
+</pre>
+
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.conf&amp;sektion=5&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rc.conf</span>(5)</span></a> and
+configure things appropriately. Assuming that this part goes smoothly, you should be able
+to enter: <tt class="FILENAME"><var class="REPLACEABLE">cdrom-host</var>:/cdrom</tt> as
+the path for an NFS installation when the target machine is installed, e.g. <tt
+class="FILENAME">wiggy:/cdrom</tt>.</p>
+</li>
+</ul>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN203" name="AEN203">1.5.2 Installing from Floppies</a></h4>
+
+<p>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.</p>
+
+<p>First, make your boot floppies as described in <a href="#FLOPPIES">Section
+1.3</a>.</p>
+
+<p>Second, peruse <a href="#LAYOUT">Section 2</a> 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.</p>
+
+<p>Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files
+in the <tt class="FILENAME">bin</tt> (binary distribution) directory. If you're preparing
+these floppies under DOS, then these floppies <span class="emphasis"><i
+class="EMPHASIS">must</i></span> be formatted using the MS-DOS <tt
+class="FILENAME">FORMAT</tt> command. If you're using Windows, use the Windows File
+Manager format command.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> 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.</p>
+</blockquote>
+</div>
+
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and
+<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>
+commands to put a UFS filesystem on a floppy, as the following sequence of commands
+illustrates:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">fdformat -f 1440 fd0.1440</kbd>
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">disklabel -w -r fd0.1440 floppy3</kbd>
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</kbd>
+</pre>
+
+<p>After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto
+them. The distribution files are split into chunks conveniently sized so that 5 of them
+will fit on a conventional 1.44MB floppy. Go through all your floppies, packing as many
+files as will fit on each one, until you've got all the distributions you want packed up
+in this fashion. Each distribution should go into its own subdirectory on the floppy,
+e.g.: <tt class="FILENAME">a:\bin\bin.inf</tt>, <tt class="FILENAME">a:\bin\bin.aa</tt>,
+<tt class="FILENAME">a:\bin\bin.ab</tt>, ...</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> The <tt class="FILENAME">bin.inf</tt> file also needs to go on the
+first floppy of the <tt class="FILENAME">bin</tt> 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 <tt class="FILENAME">distname.inf</tt> file <span class="emphasis"><i
+class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set. This
+is also covered in <tt class="FILENAME">README.TXT</tt>.</p>
+</blockquote>
+</div>
+
+<p>Once you come to the Media screen of the install, select ``Floppy'' and you'll be
+prompted for the rest.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN245" name="AEN245">1.5.3 Installing from a DOS
+partition</a></h4>
+
+<p>To prepare for installation from an MS-DOS partition you should simply copy the files
+from the distribution into a directory called <tt class="FILENAME">FREEBSD</tt> on the
+Primary DOS partition (<tt class="DEVICENAME">C:</tt>). For example, to do a minimal
+installation of FreeBSD from DOS using files copied from the CDROM, you might do
+something like this:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">C:\&#62;</samp> <kbd class="USERINPUT">MD C:\FREEBSD</kbd>
+<samp class="PROMPT">C:\&#62;</samp> <kbd
+class="USERINPUT">XCOPY /S E:\BIN C:\FREEBSD\BIN</kbd>
+</pre>
+
+<p>Assuming that <tt class="DEVICENAME">E:</tt> was where your CD was mounted.</p>
+
+<p>For as many distributions as you wish to install from DOS (and you have free space
+for), install each one in a directory under <tt class="FILENAME">C:\FREEBSD</tt> - the
+<tt class="FILENAME">BIN</tt> dist is only the minimal requirement.</p>
+
+<p>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.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN262" name="AEN262">1.5.4 Installing from QIC/SCSI
+Tape</a></h4>
+
+<p>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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(1)</span></a> to get
+them onto the tape with a command something like this:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd <var
+class="REPLACEABLE">/where/you/have/your/dists</var></kbd>
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/rsa0 <var
+class="REPLACEABLE">dist1</var> .. <var class="REPLACEABLE">dist2</var></kbd>
+</pre>
+
+<p>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
+<span class="emphasis"><i class="EMPHASIS">full</i></span> 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.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> When going to do the installation, the tape must be in the drive <span
+class="emphasis"><i class="EMPHASIS">before</i></span> booting from the boot floppies.
+The installation ``probe'' may otherwise fail to find it.</p>
+</blockquote>
+</div>
+
+<p>Now create a boot floppy as described in <a href="#FLOPPIES">Section 1.3</a> and
+proceed with the installation.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 Installing over a Network using FTP
+or NFS</a></h4>
+
+<p>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.</p>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN287" name="AEN287">1.5.5.1 Serial Port</a></h5>
+
+<p>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 I recommend
+that the PPP utility be used instead.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN293" name="AEN293">1.5.5.2 Parallel Port</a></h5>
+
+<p>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. <tt
+class="HOSTID">10.0.0.1</tt>, <tt class="HOSTID">10.0.0.2</tt>, etc).</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> If you use a Linux machine rather than a FreeBSD machine as your
+PLIP peer, you will also have to specify <var class="OPTION">link0</var> in the TCP/IP
+setup screen's ``extra options for ifconfig'' field in order to be compatible with
+Linux's slightly different PLIP protocol.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN304" name="AEN304">1.5.5.3 Ethernet</a></h5>
+
+<p>FreeBSD supports many common Ethernet cards; a table of supported cards is provided as
+part of the FreeBSD Hardware Notes (see <tt class="FILENAME">HARDWARE.TXT</tt> 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
+<span class="emphasis"><i class="EMPHASIS">before</i></span> the laptop is powered on.
+FreeBSD does not, unfortunately, currently support ``hot insertion'' of PCMCIA cards
+during installation.</p>
+
+<p>You will also need to know your IP address on the network, the <var
+class="OPTION">netmask</var> 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.</p>
+
+<p>If you do not know the answers to these questions then you should really probably talk
+to your system administrator <span class="emphasis"><i class="EMPHASIS">first</i></span>
+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.</p>
+
+<p>Once you have a network connection of some sort working, the installation can continue
+over NFS or FTP.</p>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN315" name="AEN315">1.5.5.4 NFS installation tips</a></h5>
+
+<p>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.</p>
+
+<p>If this server supports only ``privileged port'' access (this is generally the default
+for Sun and Linux workstations), you will need to set this option in the Options menu
+before installation can proceed.</p>
+
+<p>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.</p>
+
+<p>In order for NFS installation to work, the server must also support ``subdir mounts'',
+e.g. if your FreeBSD distribution directory lives on <tt
+class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, then <tt
+class="HOSTID">wiggy</tt> will have to allow the direct mounting of <tt
+class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not just <tt class="FILENAME">/usr</tt>
+or <tt class="FILENAME">/usr/archive/stuff</tt>.</p>
+
+<p>In FreeBSD's <tt class="FILENAME">/etc/exports</tt> file this is controlled by the
+<var class="OPTION">-alldirs</var> option. Other NFS servers may have different
+conventions. If you are getting <var class="LITERAL">Permission Denied</var> messages
+from the server then it's likely that you don't have this properly enabled.</p>
+</div>
+
+<div class="SECT4">
+<hr />
+<h5 class="SECT4"><a id="AEN332" name="AEN332">1.5.5.5 FTP Installation tips</a></h5>
+
+<p>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.</p>
+
+<p>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:</p>
+
+<pre class="SCREEN">
+ftp://216.66.64.162/pub/FreeBSD/releases/i386/4.2-RELEASE
+</pre>
+
+<p>There are three FTP installation modes you can use:</p>
+
+<ul>
+<li>
+<p>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.</p>
+</li>
+
+<li>
+<p>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.</p>
+</li>
+
+<li>
+<p>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.</p>
+
+<p>In the rare case that you have an FTP proxy that does not go through HTTP, you can
+specify the URL as something like:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">ftp://foo.bar.com:<var
+class="REPLACEABLE">port</var>/pub/FreeBSD</kbd>
+</pre>
+
+<p>In the URL above, <var class="REPLACEABLE">port</var> is the port number of the proxy
+FTP server.</p>
+</li>
+</ul>
+
+<br />
+<br />
+</div>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN353" name="AEN353">1.5.6 Tips for Serial Console
+Users</a></h4>
+
+<p>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:</p>
+
+<div class="PROCEDURE">
+<ol type="1">
+<li>
+<p>Connect some sort of ANSI (vt100) compatible terminal or terminal emulation program to
+the <tt class="DEVICENAME">COM1</tt> port of the PC you are installing FreeBSD onto.</p>
+</li>
+
+<li>
+<p>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.</p>
+</li>
+
+<li>
+<p>If you don't get any output on your serial console, plug the keyboard in again and
+wait for some beeps. If you are booting from the CDROM, proceed to <a
+href="#HITSPACE">step 5</a> as soon as you hear the beep.</p>
+</li>
+
+<li>
+<p>For a floppy boot, the first beep means to remove the <tt
+class="FILENAME">kern.flp</tt> floppy and insert the <tt
+class="FILENAME">mfsroot.flp</tt> floppy, after which you should press <b
+class="KEYCAP">Enter</b> and wait for another beep.</p>
+</li>
+
+<li><a id="HITSPACE" name="HITSPACE"></a>
+<p>Hit the space bar, then enter</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">boot -h</kbd>
+</pre>
+
+<p>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.</p>
+</li>
+</ol>
+</div>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN375" name="AEN375">1.6 Question and Answer Section for i386
+Architecture Users</a></h3>
+
+<div class="QANDASET">
+<dl>
+<dt>1.6.1. <a href="#Q1.6.1.">Help! I have no space! Do I need to delete everything
+first?</a></dt>
+
+<dt>1.6.2. <a href="#Q1.6.2.">Can I use compressed DOS filesystems from FreeBSD?</a></dt>
+
+<dt>1.6.3. <a href="#Q1.6.3.">Can I mount my DOS extended partitions?</a></dt>
+
+<dt>1.6.4. <a href="#Q1.6.4.">Can I run DOS binaries under FreeBSD?</a></dt>
+</dl>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.1." name="Q1.6.1."></a><b>1.6.1.</b> Help! I have no space! Do I need to
+delete everything first?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>If your machine is already running DOS and has little or no free space
+available for FreeBSD's installation, all is not lost! You may find the <b
+class="APPLICATION">FIPS</b> utility, provided in the <tt class="FILENAME">tools/</tt>
+subdirectory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to be quite
+useful.</p>
+
+<p><b class="APPLICATION">FIPS</b> 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 <tt
+class="FILENAME">DEFRAG</tt> utility or the <b class="APPLICATION">Norton Disk Tools</b>,
+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).</p>
+
+<p><b class="APPLICATION">FIPS</b> does NOT currently work with NTFS style partitions. To
+split up such a partition, you will need a commercial product such as <b
+class="APPLICATION">Partition Magic</b>. Sorry, but this is just the breaks if you've got
+a Windows partition hogging your whole disk and you don't want to reinstall from
+scratch.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.2." name="Q1.6.2."></a><b>1.6.2.</b> Can I use compressed DOS filesystems
+from FreeBSD?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>No. If you are using a utility such as <b class="APPLICATION">Stacker</b>(tm)
+or <b class="APPLICATION">DoubleSpace</b>(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!). <span class="emphasis"><i
+class="EMPHASIS">Do not remove that file</i></span> as you will probably regret it
+greatly!</p>
+
+<p>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.3." name="Q1.6.3."></a><b>1.6.3.</b> Can I mount my DOS extended
+partitions?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Yes. DOS extended partitions are mapped in at the end of the other ``slices''
+in FreeBSD, e.g. your <tt class="DEVICENAME">D:</tt> drive might be <tt
+class="FILENAME">/dev/da0s5</tt>, your <tt class="DEVICENAME">E:</tt> drive <tt
+class="FILENAME">/dev/da0s6</tt>, and so on. This example assumes, of course, that your
+extended partition is on SCSI drive 0. For IDE drives, substitute <var
+class="LITERAL">ad</var> for <var class="LITERAL">da</var> appropriately. You otherwise
+mount extended partitions exactly like you would mount any other DOS drive, e.g.:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd
+class="USERINPUT">mount -t msdos /dev/da0s5 /dos_d</kbd>
+</pre>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q1.6.4." name="Q1.6.4."></a><b>1.6.4.</b> Can I run DOS binaries under
+FreeBSD?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Ongoing work with BSDI's <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=doscmd&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">doscmd</span>(1)</span></a>
+utility will suffice in many cases, though it still has some rough edges. If you're
+interested in working on this, please send mail to the <a
+href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-emulation"
+target="_top">FreeBSD-emulation mailing list</a> and indicate that you're interested in
+joining this ongoing effort!</p>
+
+<p>The <a href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/pcemu/pkg-descr"><tt
+class="FILENAME">emulators/pcemu</tt></a> 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.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 Distribution Format</a></h2>
+
+<p>A typical FreeBSD distribution directory looks something like this:</p>
+
+<pre class="SCREEN">
+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    bin             compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+</pre>
+
+<p>If you want to do a CDROM, FTP or NFS installation from this distribution directory,
+all you need to do is make the 1.44MB boot floppies from the floppies directory (see <a
+href="#FLOPPIES">Section 1.3</a> for instructions on how to do this), boot them and
+follow the instructions. 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.</p>
+
+<p>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:</p>
+
+<ol type="1">
+<li>
+<p>The <tt class="FILENAME">*.TXT</tt> and <tt class="FILENAME">*.HTM</tt> files contain
+documentation (for example, this document is contained in both <tt
+class="FILENAME">INSTALL.TXT</tt> and <tt class="FILENAME">INSTALL.HTM</tt>) and should
+be read before starting an installation. The <tt class="FILENAME">*.TXT</tt> files are
+plain text, while the <tt class="FILENAME">*.HTM</tt> 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.</p>
+</li>
+
+<li>
+<p><tt class="FILENAME">docbook.css</tt> is a Cascading Style Sheet (CSS) file used by
+some Web browsers for formatting the HTML documentation.</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">bin</tt>, <tt class="FILENAME">catpages</tt>, <tt
+class="FILENAME">crypto</tt>, <tt class="FILENAME">dict</tt>, <tt
+class="FILENAME">doc</tt>, <tt class="FILENAME">games</tt>, <tt
+class="FILENAME">info</tt>, <tt class="FILENAME">manpages</tt>, <tt
+class="FILENAME">proflibs</tt>, and <tt class="FILENAME">src</tt> directories contain the
+primary distribution components of FreeBSD itself and are split into smaller files for
+easy packing onto floppies (should that be necessary).</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">compat1x</tt>, <tt class="FILENAME">compat20</tt>, <tt
+class="FILENAME">compat21</tt>, <tt class="FILENAME">compat22</tt>, <tt
+class="FILENAME">compat3x</tt>, and <tt class="FILENAME">compat4x</tt> 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
+<tt class="FILENAME">install.sh</tt> scripts.</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">floppies/</tt> subdirectory contains the floppy installation
+images; further information on using them can be found in <a href="#FLOPPIES">Section
+1.3</a>.</p>
+</li>
+
+<li>
+<p>The <tt class="FILENAME">packages</tt> and <tt class="FILENAME">ports</tt> directories
+contain the FreeBSD Packages and Ports Collections. Packages may be installed from the
+packages directory by running the command:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp><kbd
+class="USERINPUT">/stand/sysinstall configPackages</kbd>
+</pre>
+
+<p>Packages can also be installed by feeding individual filenames in <tt
+class="FILENAME">packages</tt>/ to the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>
+command.</p>
+
+<p>The Ports Collection may be installed like any other distribution and requires about
+100MB unpacked. More information on the ports collection may be obtained from <a
+href="http://www.FreeBSD.org/ports/" target="_top">http://www.FreeBSD.org/ports/</a> or
+locally from <tt class="FILENAME">/usr/share/doc/handbook</tt> if you've installed the
+<tt class="FILENAME">doc</tt> distribution.</p>
+</li>
+
+<li>
+<p>Last of all, the <tt class="FILENAME">tools</tt> 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.</p>
+</li>
+</ol>
+
+<br />
+<br />
+<p>A typical distribution directory (for example, the <tt class="FILENAME">info</tt>
+distribution) looks like this internally:</p>
+
+<pre class="SCREEN">
+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+</pre>
+
+<p>The <tt class="FILENAME">CHECKSUM.MD5</tt> 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 <tt class="FILENAME">info.a*</tt> files are split, gzip'd tar files, the
+contents of which can be viewed by doing:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cat info.a* | tar tvzf -</kbd>
+</pre>
+
+<p>During installation, they are automatically concatenated and extracted by the
+installation procedure.</p>
+
+<p>The <tt class="FILENAME">info.inf</tt> 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 <tt
+class="FILENAME">.inf</tt> file <span class="emphasis"><i
+class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set!</p>
+
+<p>The <tt class="FILENAME">info.mtree</tt> file is another non-essential file which is
+provided for user reference. It contains the MD5 signatures of the <span
+class="emphasis"><i class="EMPHASIS">unpacked</i></span> distribution files and can be
+later used with the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mtree</span>(8)</span></a> program
+to verify the installation permissions and checksums against any possible modifications
+to the file. When used with the <tt class="FILENAME">bin</tt> distribution, this can be
+an excellent way of detecting trojan horse attacks on your system.</p>
+
+<p>Finally, the <tt class="FILENAME">install.sh</tt> 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:</p>
+
+<pre class="SCREEN">
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /cdrom/info</kbd>
+<samp class="PROMPT">#</samp> <kbd class="USERINPUT">sh install.sh</kbd>
+</pre>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 Upgrading FreeBSD</a></h2>
+
+<p>These instructions describe a procedure for doing a binary upgrade from an older
+version of FreeBSD.</p>
+
+<div class="WARNING">
+<blockquote class="WARNING">
+<p><b>Warning:</b> While the FreeBSD upgrade procedure does its best to safeguard against
+accidental loss of data, it is still more than possible to <span class="emphasis"><i
+class="EMPHASIS">wipe out your entire disk</i></span> with this installation! Please do
+not accept the final confirmation request unless you have adequately backed up any
+important data files.</p>
+</blockquote>
+</div>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> These notes assume that you are using the version of <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched
+version of <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> 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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+from an existing installation to upgrade to a newer version of FreeBSD. This is <span
+class="emphasis"><i class="EMPHASIS">not</i></span> recommended.</p>
+</blockquote>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN571" name="AEN571">3.1 Introduction</a></h3>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN575" name="AEN575">3.1.1 Upgrade Overview</a></h4>
+
+<p>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.</p>
+
+<p>System configuration is preserved by retaining and restoring the previous version of
+the following files:</p>
+
+<p><tt class="FILENAME">Xaccel.ini</tt>, <tt class="FILENAME">XF86Config</tt>, <tt
+class="FILENAME">adduser.conf</tt>, <tt class="FILENAME">aliases</tt>, <tt
+class="FILENAME">aliases.db</tt>, <tt class="FILENAME">amd.map</tt>, <tt
+class="FILENAME">crontab</tt>, <tt class="FILENAME">csh.cshrc</tt>, <tt
+class="FILENAME">csh.login</tt>, <tt class="FILENAME">csh.logout</tt>, <tt
+class="FILENAME">cvsupfile</tt>, <tt class="FILENAME">dhclient.conf</tt>, <tt
+class="FILENAME">disktab</tt>, <tt class="FILENAME">dm.conf</tt>, <tt
+class="FILENAME">dumpdates</tt>, <tt class="FILENAME">exports</tt>, <tt
+class="FILENAME">fbtab</tt>, <tt class="FILENAME">fstab</tt>, <tt
+class="FILENAME">ftpusers</tt>, <tt class="FILENAME">gettytab</tt>, <tt
+class="FILENAME">gnats</tt>, <tt class="FILENAME">group</tt>, <tt
+class="FILENAME">hosts</tt>, <tt class="FILENAME">host.conf</tt>, <tt
+class="FILENAME">hosts.allow</tt>, <tt class="FILENAME">hosts.equiv</tt>, <tt
+class="FILENAME">hosts.lpd</tt>, <tt class="FILENAME">inetd.conf</tt>, <tt
+class="FILENAME">kerberosIV</tt>, <tt class="FILENAME">localtime</tt>, <tt
+class="FILENAME">login.access</tt>, <tt class="FILENAME">login.conf</tt>, <tt
+class="FILENAME">mail</tt>, <tt class="FILENAME">mail.rc</tt>, <tt
+class="FILENAME">make.conf</tt>, <tt class="FILENAME">manpath.config</tt>, <tt
+class="FILENAME">master.passwd</tt>, <tt class="FILENAME">modems</tt>, <tt
+class="FILENAME">motd</tt>, <tt class="FILENAME">namedb</tt>, <tt
+class="FILENAME">networks</tt>, <tt class="FILENAME">newsyslog.conf</tt>, <tt
+class="FILENAME">nsmb.conf</tt>, <tt class="FILENAME">pam.conf</tt>, <tt
+class="FILENAME">passwd</tt>, <tt class="FILENAME">periodic</tt>, <tt
+class="FILENAME">ppp</tt>, <tt class="FILENAME">printcap</tt>, <tt
+class="FILENAME">profile</tt>, <tt class="FILENAME">pwd.db</tt>, <tt
+class="FILENAME">rc.conf</tt>, <tt class="FILENAME">rc.conf.local</tt>, <tt
+class="FILENAME">rc.firewall</tt>, <tt class="FILENAME">rc.local</tt>, <tt
+class="FILENAME">remote</tt>, <tt class="FILENAME">resolv.conf</tt>, <tt
+class="FILENAME">rmt</tt>, <tt class="FILENAME">sendmail.cf</tt>, <tt
+class="FILENAME">sendmail.cw</tt>, <tt class="FILENAME">services</tt>, <tt
+class="FILENAME">shells</tt>, <tt class="FILENAME">skeykeys</tt>, <tt
+class="FILENAME">spwd.db</tt>, <tt class="FILENAME">ssh</tt>, <tt
+class="FILENAME">syslog.conf</tt>, <tt class="FILENAME">ttys</tt>, <tt
+class="FILENAME">uucp</tt></p>
+
+<p>The versions of these files which correspond to the new version are moved to <tt
+class="FILENAME">/etc/upgrade/</tt>. 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.</p>
+
+<p>During the upgrade procedure, the administrator is prompted for a location into which
+all files from <tt class="FILENAME">/etc/</tt> are saved. In the event that local
+modifications have been made to other files, they may be subsequently retrieved from this
+location.</p>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN651" name="AEN651">3.2 Procedure</a></h3>
+
+<p>This section details the upgrade procedure. Particular attention is given to items
+which substantially differ from a normal installation.</p>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN654" name="AEN654">3.2.1 Backup</a></h4>
+
+<p>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.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN657" name="AEN657">3.2.2 Mount Filesystems</a></h4>
+
+<p>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. <span
+class="emphasis"><i class="EMPHASIS">Do not</i></span>set the ``newfs flag'' for any
+filesystems, as this will cause data loss.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="AEN662" name="AEN662">3.2.3 Select Distributions</a></h4>
+
+<p>When selecting distributions, there are no constraints on which must be selected. As a
+general rule, the <var class="LITERAL">bin</var> distribution should be selected for an
+update, and the <var class="LITERAL">man</var> distribution if manpages are already
+installed. Other distributions may be selected beyond those originally installed if the
+administrator wishes to add additional functionality.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 After Installation</a></h4>
+
+<p>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 <tt
+class="FILENAME">/etc/rc.conf</tt> and <tt class="FILENAME">/etc/fstab</tt> files should
+be checked.</p>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN672" name="AEN672">3.3 Upgrading from Source Code</a></h3>
+
+<p>Those interested in an upgrade method that allows more flexibility and sophistication
+should take a look at <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html"
+target="_top">The Cutting Edge</a> 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.</p>
+
+<p><tt class="FILENAME">/usr/src/UPDATING</tt> 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.</p>
+
+<p></p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 Troubleshooting</a></h2>
+
+<div class="SECT2">
+<h3 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 Repairing an Existing FreeBSD
+Installation</a></h3>
+
+<p>FreeBSD features a ``Fixit'' option in the top menu of the boot floppy. To use it, you
+will also need either a <tt class="FILENAME">fixit.flp</tt> image floppy, generated in
+the same fashion as the boot floppy, or the ``live filesystem'' CDROM; typically the
+second CDROM in a multi-disc FreeBSD distribution.</p>
+
+<p>To invoke fixit, simply boot the <tt class="FILENAME">kern.flp</tt> floppy, choose the
+``Fixit'' item and insert the fixit floppy or CDROM when asked. You will then be placed
+into a shell with a wide variety of commands available (in the <tt
+class="FILENAME">/stand</tt> and <tt class="FILENAME">/mnt2/stand</tt> directories) for
+checking, repairing and examining file systems and their contents. Some UNIX
+administration experience <span class="emphasis"><i class="EMPHASIS">is</i></span>
+required to use the fixit option.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN693" name="AEN693">4.2 Common Installation Problems,
+Q&amp;A</a></h3>
+
+<div class="QANDASET">
+<dl>
+<dt>4.2.1. <a href="#Q4.2.1.">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:</a></dt>
+
+<dt>4.2.2. <a href="#Q4.2.2.">I go to boot from the hard disk for the first time after
+installing FreeBSD, but the Boot Manager prompt just prints <var class="LITERAL">F?</var>
+at the boot menu each time but the boot won't go any further.</a></dt>
+</dl>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.2.1." name="Q4.2.1."></a><b>4.2.1.</b> 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:</p>
+
+<pre class="SCREEN">
+changing root device to wd1s1a panic: cannot mount root
+</pre>
+
+<p>What is wrong? What can I do?</p>
+
+<p>What is this <var
+class="LITERAL">bios_drive:interface(unit,partition)kernel_name</var> thing that is
+displayed with the boot help?</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+
+<p>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.</p>
+
+<p>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 <tt class="DEVICENAME">wd0</tt>
+and <tt class="DEVICENAME">wd2</tt>.</p>
+
+<p>FreeBSD is on BIOS disk 1, of type <var class="LITERAL">wd</var> and the FreeBSD disk
+number is 2, so you would say:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">1:wd(2,a)kernel</kbd>
+</pre>
+
+<p>Note that if you have a slave on the primary bus, the above is not necessary (and is
+effectively wrong).</p>
+
+<p>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 <var class="LITERAL">da</var> and FreeBSD disk number 0, so you would say:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">2:da(0,a)kernel</kbd>
+</pre>
+
+<p>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.</p>
+
+<p>Once you have determined the correct values to use, you can put the command exactly as
+you would have typed it in the <tt class="FILENAME">/boot.config</tt> file using a
+standard text editor. Unless instructed otherwise, FreeBSD will use the contents of this
+file as the default response to the <var class="LITERAL">boot:</var> prompt.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.2.2." name="Q4.2.2."></a><b>4.2.2.</b> I go to boot from the hard disk for
+the first time after installing FreeBSD, but the Boot Manager prompt just prints <var
+class="LITERAL">F?</var> at the boot menu each time but the boot won't go any
+further.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+
+<p>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.</p>
+
+<p>The following tip is no longer recommended, but is left here for reference:</p>
+
+<a id="AEN730" name="AEN730"></a>
+<blockquote class="BLOCKQUOTE">
+<p>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.</p>
+</blockquote>
+</div>
+</div>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN732" name="AEN732">4.3 Known Hardware Problems,
+Q&amp;A</a></h3>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Please send hardware tips for this section to Jordan K. Hubbard <code
+class="EMAIL">&#60;<a href="mailto:jkh@FreeBSD.org">jkh@FreeBSD.org</a>&#62;</code>.</p>
+</blockquote>
+</div>
+
+<div class="QANDASET">
+<dl>
+<dt>4.3.1. <a href="#Q4.3.1.">The <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">mcd</span>(4)</span> driver keeps thinking that it has found a
+device and this stops my Intel EtherExpress card from working.</a></dt>
+
+<dt>4.3.2. <a href="#Q4.3.2.">FreeBSD claims to support the 3Com PCMCIA card, but my card
+isn't recognized when it's plugged into my laptop.</a></dt>
+
+<dt>4.3.3. <a href="#Q4.3.3.">FreeBSD finds my PCMCIA network card, but no packets appear
+to be sent even though it claims to be working.</a></dt>
+
+<dt>4.3.4. <a href="#Q4.3.4.">The system finds my <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">ed</span>(4)</span> network card, but I keep getting device timeout
+errors.</a></dt>
+
+<dt>4.3.5. <a href="#Q4.3.5.">I booted the install floppy on my IBM ThinkPad (tm) laptop,
+and the keyboard is all messed up.</a></dt>
+
+<dt>4.3.6. <a href="#Q4.3.6.">When I try to boot the install floppy, I see the following
+message and nothing seems to be happening. I cannot enter anything from the keyboard
+either.</a></dt>
+
+<dt>4.3.7. <a href="#Q4.3.7.">I have a Matsushita/Panasonic CR-522, a
+Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is not recognized even when the
+correct I/O port is set.</a></dt>
+
+<dt>4.3.8. <a href="#Q4.3.8.">I'm trying to install from a tape drive but all I get is
+something like this on the screen:</a></dt>
+
+<dt>4.3.9. <a href="#Q4.3.9.">I've installed FreeBSD onto my system, but it hangs when
+booting from the hard drive with the message:</a></dt>
+
+<dt>4.3.10. <a href="#Q4.3.10.">My system can not find my Intel EtherExpress 16
+card.</a></dt>
+
+<dt>4.3.11. <a href="#Q4.3.11.">When installing on an EISA HP Netserver, my on-board
+AIC-7xxx SCSI controller isn't detected.</a></dt>
+
+<dt>4.3.12. <a href="#Q4.3.12.">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.</a></dt>
+
+<dt>4.3.13. <a href="#Q4.3.13.">I have this CMD640 IDE controller that is said to be
+broken.</a></dt>
+
+<dt>4.3.14. <a href="#Q4.3.14.">On a Compaq Aero notebook, I get the message ``No floppy
+devices found! Please check ...'' when trying to install from floppy.</a></dt>
+
+<dt>4.3.15. <a href="#Q4.3.15.">When I go to boot my Intel AL440LX (``Atlanta'') -based
+system from the hard disk the first time, it stops with a <var class="LITERAL">Read
+Error</var> message.</a></dt>
+
+<dt>4.3.16. <a href="#Q4.3.16.">When installing on an Dell Poweredge XE, Dell proprietary
+RAID controller DSA (Dell SCSI Array) isn't recognized.</a></dt>
+
+<dt>4.3.17. <a href="#Q4.3.17.">My Ethernet adapter is detected as an AMD PCnet-FAST (or
+similar) but it doesn't work. (Eg. onboard Ethernet on IBM Netfinity 5xxx or
+7xxx)</a></dt>
+
+<dt>4.3.18. <a href="#Q4.3.18.">I have an IBM EtherJet PCI card, it is detected by the
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span> driver
+correctly, but the lights on the card don't come on and it doesn't connect to the
+network.</a></dt>
+
+<dt>4.3.19. <a href="#Q4.3.19.">When I configure the network during installation on an
+IBM Netfinity 3500, the system freezes.</a></dt>
+
+<dt>4.3.20. <a href="#Q4.3.20.">When I install onto a drive managed by a Mylex PCI RAID
+controller, the system fails to boot (eg. with a <var class="LITERAL">read error</var>
+message).</a></dt>
+</dl>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.1." name="Q4.3.1."></a><b>4.3.1.</b> The <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">mcd</span>(4)</span> driver keeps thinking that it has found a
+device and this stops my Intel EtherExpress card from working.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Use the UserConfig utility (see <tt class="FILENAME">HARDWARE.TXT</tt>) and
+disable the probing of the <tt class="DEVICENAME">mcd0</tt> and <tt
+class="DEVICENAME">mcd1</tt> devices. Generally speaking, you should only leave the
+devices that you will be using enabled in your kernel.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.2." name="Q4.3.2."></a><b>4.3.2.</b> FreeBSD claims to support the 3Com
+PCMCIA card, but my card isn't recognized when it's plugged into my laptop.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>There are a couple of possible problems. First of all, FreeBSD does not support
+multi-function cards, so if you have a combo Ethernet/modem card (such as the 3C562), it
+won't work. The default driver for the 3C589 card was written just like all of the other
+drivers in FreeBSD, and depend on the card's own configuration data stored in NVRAM to
+work. You must correctly configure FreeBSD's driver to match the IRQ, port, and IOMEM
+stored in NVRAM.</p>
+
+<p>Unfortunately, the only program capable of reading them is the 3COM supplied DOS
+program. This program must be run on a absolutely clean system (no other drivers must be
+running), and the program will whine about CARD-Services not being found, but it will
+continue. This is necessary to read the NVRAM values. You want to know the IRQ, port, and
+IOMEM values (the latter is called the CIS tuple by 3COM). The first two can be set in
+the program, the third is un-settable, and can only be read. Once you have these values,
+set them in UserConfig and your card will be recognized.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.3." name="Q4.3.3."></a><b>4.3.3.</b> FreeBSD finds my PCMCIA network card,
+but no packets appear to be sent even though it claims to be working.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Many PCMCIA cards have the ability to use either the 10-Base2 (BNC) or 10-BaseT
+connectors for connecting to the network. The driver is unable to ``auto-select'' the
+correct connector, so you must tell it which connector to use. In order to switch between
+the two connectors, the link flags must be set. Depending on the model of the card, <var
+class="OPTION">-link0 link1</var> or <var class="OPTION">-link0 -link1</var> will choose
+the correct network connector. You can set these in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> by
+using the <var class="LITERAL">Extra options to ifconfig:</var> field in the network
+setup screen.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.4." name="Q4.3.4."></a><b>4.3.4.</b> The system finds my <span
+class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span> network card, but I
+keep getting device timeout errors.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Your card is probably on a different IRQ from what is specified in the kernel
+configuration. 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
+<var class="LITERAL">?</var> in the IRQ field of your kernel config file.</p>
+
+<p>Either move the jumper on the card to a hard configuration setting (altering the
+kernel settings if necessary), or specify the IRQ as <var class="LITERAL">-1</var> in
+UserConfig or <var class="LITERAL">?</var> in your kernel config file. This will tell the
+kernel to use the soft configuration.</p>
+
+<p>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.5." name="Q4.3.5."></a><b>4.3.5.</b> I booted the install floppy on my IBM
+ThinkPad (tm) laptop, and the keyboard is all messed up.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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. Change
+the atkbd0 'Flags' to 0x4 in UserConfig and it should work fine. (Look in the Input Menu
+for 'Keyboard'.)</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.6." name="Q4.3.6."></a><b>4.3.6.</b> When I try to boot the install
+floppy, I see the following message and nothing seems to be happening. I cannot enter
+anything from the keyboard either.</p>
+
+<pre class="SCREEN">
+Keyboard: no
+</pre>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Due to lack of space, full support for old XT/AT (84-key) keyboards is no
+longer available in the bootblocks. Some notebook computers may also have this type of
+keyboard. If you are still using this kind of hardware, you will see the above message
+appears when you boot from the CD-ROM or an install floppy.</p>
+
+<p>As soon as you see this message, hit the space bar, and you will see the prompt:</p>
+
+<pre class="SCREEN">
+&#62;&#62; FreeBSD/i386 BOOT
+Default: x:xx(x,x)/boot/loader 
+boot:
+</pre>
+
+<p>Then enter <kbd class="USERINPUT">-Dh</kbd>, and things should proceed normally.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.7." name="Q4.3.7."></a><b>4.3.7.</b> I have a Matsushita/Panasonic CR-522,
+a Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is not recognized even when
+the correct I/O port is set.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>These CD-ROM drives are currently not supported by FreeBSD. The command sets
+for these drives are not compatible with the double-speed CR-562 and CR-563 drives.</p>
+
+<p>The single-speed CR-522 and CR-523 drives can be identified by their use of a
+CD-caddy.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.8." name="Q4.3.8."></a><b>4.3.8.</b> I'm trying to install from a tape
+drive but all I get is something like this on the screen:</p>
+
+<pre class="SCREEN">
+sa0(aha0:1:0) NOT READY csi 40,0,0,0
+</pre>
+</div>
+
+<div class="ANSWER">
+<p><b></b>There's a limitation in the current <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+that the tape <span class="emphasis"><i class="EMPHASIS">must</i></span> be in the drive
+while <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> is
+started or it won't be detected. Try again with the tape in the drive the whole time.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.9." name="Q4.3.9."></a><b>4.3.9.</b> I've installed FreeBSD onto my
+system, but it hangs when booting from the hard drive with the message:</p>
+
+<pre class="SCREEN">
+Changing root to /dev/da0a
+</pre>
+</div>
+
+<div class="ANSWER">
+<p><b></b>his problem may occur in a system with a 3com 3c509 Ethernet adapter. The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ep</span>(4)</span></a> device
+driver appears to be sensitive to probes for other devices that also use address 0x300.
+Boot your FreeBSD system by power cycling the machine (turn off and on). At the <var
+class="LITERAL">Boot:</var> prompt specify the <var class="OPTION">-c</var>. This will
+invoke UserConfig (see <a href="#REPAIRING">Section 4.1</a> above). Use the <var
+class="LITERAL">disable</var> command to disable the device probes for all devices at
+address 0x300 except the ep0 driver. On exit, your machine should successfully boot
+FreeBSD.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.10." name="Q4.3.10."></a><b>4.3.10.</b> My system can not find my Intel
+EtherExpress 16 card.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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 <tt
+class="FILENAME">softset.exe</tt> program.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.11." name="Q4.3.11."></a><b>4.3.11.</b> When installing on an EISA HP
+Netserver, my on-board AIC-7xxx SCSI controller isn't detected.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>This is a known problem, and will hopefully be fixed in the future. In order to
+get your system installed at all, boot with the <var class="OPTION">-c</var> option into
+UserConfig, but <span class="emphasis"><i class="EMPHASIS">don't</i></span> use the
+pretty visual mode but the plain old CLI mode. Type:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">eisa 12</kbd>
+<kbd class="USERINPUT">quit</kbd>
+</pre>
+
+<p>at the prompt. (Instead of `quit', you might also type `visual', and continue the rest
+of the configuration session in visual mode.) While it's recommended to compile a custom
+kernel, dset now also understands to save this value.</p>
+
+<p>Refer to the FAQ topic 3.16 for an explanation of the problem, and for how to
+continue. Remember that you can find the FAQ on your local system in /usr/share/doc/FAQ,
+provided you have installed the `doc' distribution.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.12." name="Q4.3.12."></a><b>4.3.12.</b> 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.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Your machine doesn't like the new <var class="LITERAL">i586_copyout</var> and
+<var class="LITERAL">i586_copyin</var> code for some reason. To disable this, boot the
+installation boot floppy and when it comes to the very first menu (the choice to drop
+into kernel UserConfig mode or not) choose the command-line interface (``expert mode'')
+version and type the following at it:</p>
+
+<pre class="SCREEN">
+<kbd class="USERINPUT">flags npx0 1</kbd>
+</pre>
+
+<p>Then proceed normally to boot. This will be saved into your kernel, so you only need
+to do it once.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.13." name="Q4.3.13."></a><b>4.3.13.</b> I have this CMD640 IDE controller
+that is said to be broken.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>Yes, it is. FreeBSD does not support this controller except through the legacy
+wdc driver.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.14." name="Q4.3.14."></a><b>4.3.14.</b> On a Compaq Aero notebook, I get
+the message ``No floppy devices found! Please check ...'' when trying to install from
+floppy.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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. Go to the UserConfig screen, and set
+the Flags value of the fdc0 device to 0x1. This pretends the existence of the first
+floppy drive (as a 1.44 MB drive) to the driver without asking the CMOS at all.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.15." name="Q4.3.15."></a><b>4.3.15.</b> When I go to boot my Intel AL440LX
+(``Atlanta'') -based system from the hard disk the first time, it stops with a <var
+class="LITERAL">Read Error</var> message.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>There appears to be a bug in the BIOS on at least some of these boards, this
+bug results in the FreeBSD bootloader thinking that it is booting from a floppy disk.
+This is only a problem if you are not using the BootEasy boot manager. Slice the disk in
+``compatible''mode and install BootEasy during the FreeBSD installation to avoid the bug,
+or upgrade the BIOS (see Intel's website for details).</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.16." name="Q4.3.16."></a><b>4.3.16.</b> When installing on an Dell
+Poweredge XE, Dell proprietary RAID controller DSA (Dell SCSI Array) isn't
+recognized.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.17." name="Q4.3.17."></a><b>4.3.17.</b> My Ethernet adapter is detected as
+an AMD PCnet-FAST (or similar) but it doesn't work. (Eg. onboard Ethernet on IBM
+Netfinity 5xxx or 7xxx)</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver is
+currently faulty, and will often not work correctly with the PCnet-FAST and PCnet-FAST+.
+You need to install a different Ethernet adapter.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.18." name="Q4.3.18."></a><b>4.3.18.</b> I have an IBM EtherJet PCI card,
+it is detected by the <span class="CITEREFENTRY"><span
+class="REFENTRYTITLE">fxp</span>(4)</span> driver correctly, but the lights on the card
+don't come on and it doesn't connect to the network.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.19." name="Q4.3.19."></a><b>4.3.19.</b> When I configure the network
+during installation on an IBM Netfinity 3500, the system freezes.</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+
+<div class="QANDAENTRY">
+<div class="QUESTION">
+<p><a id="Q4.3.20." name="Q4.3.20."></a><b>4.3.20.</b> When I install onto a drive
+managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a <var
+class="LITERAL">read error</var> message).</p>
+</div>
+
+<div class="ANSWER">
+<p><b></b>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.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+
diff --git a/en/releases/4.9R/readme.html b/en/releases/4.9R/readme.html
new file mode 100644
index 0000000000..77e3282e28
--- /dev/null
+++ b/en/releases/4.9R/readme.html
@@ -0,0 +1,384 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD 4.9-RELEASE README</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD 4.9-RELEASE README</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/readme/article.sgml,v
+1.1.2.17 2003/05/01 15:09:53 trhodes Exp $<br />
+</p>
+
+<hr />
+</div>
+
+<blockquote class="ABSTRACT">
+<div class="ABSTRACT"><a id="AEN12" name="AEN12"></a>
+<p>This document gives a brief introduction to FreeBSD 4.9-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.</p>
+</div>
+</blockquote>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN14" name="AEN14">1 Introduction</a></h2>
+
+<p>This distribution is a release of FreeBSD 4.9-RELEASE, the latest point along the
+4-STABLE branch.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN17" name="AEN17">1.1 About FreeBSD</a></h3>
+
+<p>FreeBSD is an operating system based on 4.4 BSD Lite for Intel, AMD, Cyrix or NexGen
+``x86'' based PC hardware and Compaq (formerly DEC) Alpha computers. Versions for the
+IA64, PowerPC, and Sparc64 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.</p>
+
+<p>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.</p>
+
+<p>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 9,200 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.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN26" name="AEN26">1.2 Target Audience</a></h3>
+
+<p>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.</p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN29" name="AEN29">2 Obtaining FreeBSD</a></h2>
+
+<p>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.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN32" name="AEN32">2.1 CDROM and DVD</a></h3>
+
+<p>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.</p>
+
+<p>A list of the CDROM and DVD publishers known to the project are listed in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html"
+target="_top">``Obtaining FreeBSD''</a> appendix to the Handbook.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN39" name="AEN39">2.2 FTP</a></h3>
+
+<p>You can use FTP to retrieve FreeBSD and any or all of its optional packages from <a
+href="ftp://ftp.FreeBSD.org/" target="_top">ftp://ftp.FreeBSD.org/</a>, which is the
+official FreeBSD release site, or any of its ``mirrors''.</p>
+
+<p>Lists of locations that mirror FreeBSD can be found in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"
+target="_top">FTP Sites</a> section of the Handbook, or on the <a
+href="http://www.freebsdmirrors.org/" target="_top">http://www.freebsdmirrors.org/</a>
+Web pages. Finding a close (in networking terms) mirror from which to download the
+distribution is highly recommended.</p>
+
+<p>Additional mirror sites are always welcome. Contact <code class="EMAIL">&#60;<a
+href="mailto:freebsd-admin@FreeBSD.org">freebsd-admin@FreeBSD.org</a>&#62;</code> for
+more details on becoming an official mirror site.</p>
+
+<p>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.</p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="CONTACTING" name="CONTACTING">3 Contacting the FreeBSD
+Project</a></h2>
+
+<div class="SECT2">
+<h3 class="SECT2"><a id="AEN52" name="AEN52">3.1 Email and Mailing Lists</a></h3>
+
+<p>For any questions or general technical support issues, please send mail to the <a
+href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions" target="_top">FreeBSD
+general questions mailing list</a>.</p>
+
+<p>If you are tracking the -STABLE development efforts, you <span class="emphasis"><i
+class="EMPHASIS">must</i></span> join the <a
+href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-stable"
+target="_top">FreeBSD-STABLE mailing list</a>, in order to keep abreast of recent
+developments and changes that may affect the way you use and maintain the system.</p>
+
+<p>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 <a
+href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hackers" target="_top">FreeBSD
+technical discussions mailing list</a>.</p>
+
+<p>Please note that these mailing lists can experience <span class="emphasis"><i
+class="EMPHASIS">significant</i></span> 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 <a
+href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-announce" target="_top">FreeBSD
+announcements mailing list</a>.</p>
+
+<p>All of the mailing lists can be freely joined by anyone wishing to do so. Visit <a
+href="http://www.FreeBSD.org/mailman/listinfo" target="_top">FreeBSD Mailman Info
+Page</a>. 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 through majordomo or the <a
+href="http://www.FreeBSD.org/support.html#mailing-list" target="_top">mailing lists
+section</a> of the FreeBSD Web site.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> Do <span class="emphasis"><i class="EMPHASIS">not</i></span> send
+email to the lists asking to be subscribed. Use the <code class="EMAIL">&#60;<a
+href="mailto:majordomo@FreeBSD.org">majordomo@FreeBSD.org</a>&#62;</code> address
+instead.</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN71" name="AEN71">3.2 Submitting Problem Reports</a></h3>
+
+<p>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.</p>
+
+<p>The preferred method to submit bug reports from a machine with Internet mail
+connectivity is to use the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">send-pr</span>(1)</span></a>
+command or use the Web form at <a href="http://www.FreeBSD.org/send-pr.html"
+target="_top">http://www.FreeBSD.org/send-pr.html</a>. ``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
+href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi" target="_top">A list of all active
+PRs</a> is available on the FreeBSD Web site; this list is useful to see what potential
+problems other users have encountered.</p>
+
+<p>Note that <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">send-pr</span>(1)</span></a>
+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 <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">send-pr</span>(1)</span></a> to
+submit a bug report, you can try to send it to the <a
+href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-bugs" target="_top">FreeBSD
+problem reports mailing list</a>.</p>
+
+<p>For more information, <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/problem-reports/"
+target="_top">``Writing FreeBSD Problem Reports''</a>, available on the FreeBSD Web site,
+has a number of helpful hints on writing and submitting effective problem reports.</p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN92" name="AEN92">4 Further Reading</a></h2>
+
+<p>There are many sources of information about FreeBSD; some are included with this
+distribution, while others are available on-line or in print versions.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="RELEASE-DOCS" name="RELEASE-DOCS">4.1 Release
+Documentation</a></h3>
+
+<p>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 (<tt class="FILENAME">.TXT</tt>) and HTML (<tt
+class="FILENAME">.HTM</tt>) renditions. Some distributions may also include other formats
+such as PostScript (<tt class="FILENAME">.PS</tt>) or Portable Document Format (<tt
+class="FILENAME">.PDF</tt>).</p>
+
+<ul>
+<li>
+<p><tt class="FILENAME">README.TXT</tt>: This file, which gives some general information
+about FreeBSD as well as some cursory notes about obtaining a distribution.</p>
+</li>
+
+<li>
+<p><tt class="FILENAME">RELNOTES.TXT</tt>: The release notes, showing what's new and
+different in FreeBSD 4.9-RELEASE compared to the previous release (FreeBSD
+4.8-RELEASE).</p>
+</li>
+
+<li>
+<p><tt class="FILENAME">HARDWARE.TXT</tt>: The hardware compatability list, showing
+devices with which FreeBSD has been tested and is known to work.</p>
+</li>
+
+<li>
+<p><tt class="FILENAME">INSTALL.TXT</tt>: Installation instructions for installing
+FreeBSD from its distribution media.</p>
+</li>
+
+<li>
+<p><tt class="FILENAME">ERRATA.TXT</tt>: 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.</p>
+</li>
+</ul>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Several of these documents (in particular, <tt
+class="FILENAME">RELNOTES.TXT</tt>, <tt class="FILENAME">HARDWARE.TXT</tt>, and <tt
+class="FILENAME">INSTALL.TXT</tt>) 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.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p>These documents are generally available via the Documentation menu during
+installation. Once the system is installed, you can revisit this menu by running the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
+utility.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> 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 <a href="http://www.FreeBSD.org/releases/"
+target="_top">http://www.FreeBSD.org/releases/</a> (as well as any sites which keep
+up-to-date mirrors of this location).</p>
+</blockquote>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN132" name="AEN132">4.2 Manual Pages</a></h3>
+
+<p>As with almost all UNIX-like operating systems, FreeBSD comes with a set of on-line
+manual pages, accessed through the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=man&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">man</span>(1)</span></a> command
+or through the <a href="http://www.FreeBSD.org/cgi/man.cgi" target="_top">hypertext
+manual pages gateway</a> on the FreeBSD Web site. In general, the manual pages provide
+information on the different commands and APIs available to the FreeBSD user.</p>
+
+<p>In some cases, manual pages are written to give information on particular topics.
+Notable examples of such manual pages are <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=tuning&amp;sektion=7&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tuning</span>(7)</span></a> (a
+guide to performance tuning), <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=security&amp;sektion=7&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">security</span>(7)</span></a> (an
+introduction to FreeBSD security), and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=style&amp;sektion=9&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">style</span>(9)</span></a> (a
+style guide to kernel coding).</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="AEN149" name="AEN149">4.3 Books and Articles</a></h3>
+
+<p>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 <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
+target="_top">Handbook</a> and <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/" target="_top">FAQ</a> are
+always available from the <a href="http://www.FreeBSD.org/docs.html"
+target="_top">FreeBSD Documentation page</a> or its mirrors. If you install the <tt
+class="FILENAME">doc</tt> distribution set, you can use a Web browser to read the
+Handbook and FAQ locally.</p>
+
+<p>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 <tt class="FILENAME">doc</tt>
+distribution set.</p>
+
+<p>A listing of other books and documents about FreeBSD can be found in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/bibliography.html"
+target="_top">bibliography</a> 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.</p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="AEN160" name="AEN160">5 Acknowledgments</a></h2>
+
+<p>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 <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/"
+target="_top">``Contributors to FreeBSD''</a> on the FreeBSD Web site or any of its
+mirrors.</p>
+
+<p>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.</p>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+
diff --git a/en/releases/4.9R/relnotes-alpha.html b/en/releases/4.9R/relnotes-alpha.html
new file mode 100644
index 0000000000..1356e8c0c2
--- /dev/null
+++ b/en/releases/4.9R/relnotes-alpha.html
@@ -0,0 +1,502 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD/alpha 4.9-RELEASE Release Notes</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD/alpha 4.9-RELEASE Release
+Notes</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.22.2.386 2003/10/19 18:33:34 bmah Exp $<br />
+</p>
+
+<div>
+<div class="ABSTRACT"><a id="AEN12" name="AEN12"></a>
+<p>The release notes for FreeBSD 4.9-RELEASE contain a summary of the changes made to the
+FreeBSD base system since 4.8-RELEASE. Both changes for kernel and userland are listed,
+as well as applicable security advisories for the base system that were issued since the
+last release. Some brief remarks on upgrading are also presented.</p>
+</div>
+</div>
+
+<hr />
+</div>
+
+<div class="TOC">
+<dl>
+<dt><b>Table of Contents</b></dt>
+
+<dt>1 <a href="#INTRO">Introduction</a></dt>
+
+<dt>2 <a href="#NEW">What's New</a></dt>
+
+<dd>
+<dl>
+<dt>2.1 <a href="#SECURITY">Security Advisories</a></dt>
+
+<dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt>
+
+<dd>
+<dl>
+<dt>2.2.1 <a href="#PROC">Platform-Specific Hardware Support</a></dt>
+
+<dt>2.2.2 <a href="#BOOT">Boot Loader Changes</a></dt>
+
+<dt>2.2.3 <a href="#NET-IF">Network Interface Support</a></dt>
+
+<dt>2.2.4 <a href="#NET-PROTO">Network Protocols</a></dt>
+
+<dt>2.2.5 <a href="#DISKS">Disks and Storage</a></dt>
+
+<dt>2.2.6 <a href="#FS">File Systems</a></dt>
+
+<dt>2.2.7 <a href="#PCCARD">PCCARD Support</a></dt>
+
+<dt>2.2.8 <a href="#MM">Multimedia Support</a></dt>
+</dl>
+</dd>
+
+<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt>
+
+<dt>2.4 <a href="#CONTRIB">Contributed Software</a></dt>
+
+<dt>2.5 <a href="#PORTS">Ports/Packages Collection Infrastructure</a></dt>
+
+<dt>2.6 <a href="#RELENG">Release Engineering and Integration</a></dt>
+</dl>
+</dd>
+
+<dt>3 <a href="#UPGRADE">Upgrading from previous releases of FreeBSD</a></dt>
+</dl>
+</div>
+
+<div class="SECT1">
+<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
+
+<p>This document contains the release notes for FreeBSD 4.9-RELEASE on the Alpha/AXP
+hardware platform. It describes new features of FreeBSD that have been added (or changed)
+since 4.8-RELEASE. It also provides some notes on upgrading from previous versions of
+FreeBSD.</p>
+
+<p>This distribution of FreeBSD 4.9-RELEASE is a release distribution. It can be found at
+<a href="ftp://ftp.FreeBSD.org/" target="_top">ftp://ftp.FreeBSD.org/</a> or any of its
+mirrors. More information on obtaining this (or other) release distributions of FreeBSD
+can be found in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html"
+target="_top">``Obtaining FreeBSD''</a> appendix in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a>.</p>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="NEW" name="NEW">2 What's New</a></h2>
+
+<p>This section describes the most user-visible new or changed features in FreeBSD since
+4.8-RELEASE. Typical release note items document new drivers or hardware support, new
+commands or options, major bugfixes, or contributed software upgrades. Security
+advisories for the base system that were issued after 4.8-RELEASE are also listed.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3>
+
+<p>A remotely-exploitable buffer overflow vulnerability in <b
+class="APPLICATION">sendmail</b> has been fixed. For more details, see security advisory
+<a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc"
+target="_top">FreeBSD-SA-03:07</a>. In FreeBSD 4.8-RELEASE, this vulnerability was fixed
+using a vendor-supplied patch (but too late for inclusion in the release notes). In
+FreeBSD 4.9-RELEASE, it has been fixed with the import of a new version of <b
+class="APPLICATION">sendmail</b>.</p>
+
+<p>A single-byte buffer overflow in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&amp;sektion=3&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">realpath</span>(3)</span></a> has
+been fixed. See security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:08.realpath.asc"
+target="_top">FreeBSD-SA-03:08</a>.</p>
+
+<p>A bug that could allow the kernel to attempt delivery of invalid signals has been
+fixed. The bug could have led to a kernel panic. For more information, see security
+advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:09.signal.asc"
+target="_top">FreeBSD-SA-03:09</a>.</p>
+
+<p>A bug in the iBCS2 emulation module, which could result in disclosing the contents of
+kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more
+information, see security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:10.ibcs2.asc"
+target="_top">FreeBSD-SA-03:10</a>.</p>
+
+<p>A programming error in the <b class="APPLICATION">sendmail</b> implementation of its
+``DNS maps'' feature has been fixed by the import of a new version of <b
+class="APPLICATION">sendmail</b>. More information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:11.sendmail.asc"
+target="_top">FreeBSD-SA-03:11</a>. Note that this feature is not used by the default
+configuration files shipped with FreeBSD.</p>
+
+<p>A buffer management bug in <b class="APPLICATION">OpenSSH</b>, which could potentially
+cause a crash, has been fixed. More information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:12.openssh.asc"
+target="_top">FreeBSD-SA-03:12</a>.</p>
+
+<p>A buffer overflow in <b class="APPLICATION">sendmail</b> has been fixed. More
+information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:13.sendmail.asc"
+target="_top">FreeBSD-SA-03:13</a>.</p>
+
+<p>A bug that could allow the kernel to cause resource starvation which eventually
+results in a system panic in the ARP cache code has been fixed. More information can be
+found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:14.arp.asc"
+target="_top">FreeBSD-SA-03:14</a>.</p>
+
+<p>Several errors in the <b class="APPLICATION">OpenSSH</b> PAM challenge/authentication
+subsystem have been fixed. The impacts of these bugs vary; details can be found in
+security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:15.openssh.asc"
+target="_top">FreeBSD-SA-03:15</a>.</p>
+
+<p>A bug in the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=readv&amp;sektion=2&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">readv</span>(2)</span></a> system
+call, which could potentially cause a system crash or privilege escalation has been
+fixed. More information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:16.filedesc.asc"
+target="_top">FreeBSD-SA-03:16</a>.</p>
+
+<p>A bug in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=procfs&amp;sektion=5&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">procfs</span>(5)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=linprocfs&amp;sektion=5&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">linprocfs</span>(5)</span></a>,
+which could result in disclosing the contents of kernel memory, has been fixed. More
+information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:17.procfs.asc"
+target="_top">FreeBSD-SA-03:17</a>.</p>
+
+<p>Four separate security flaws in <b class="APPLICATION">OpenSSL</b>, which could allow
+a remote attacker to crash an <b class="APPLICATION">OpenSSL</b>-using application or to
+execute arbitrary code with the privileges of the application, have been fixed. More
+information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:18.openssl.asc"
+target="_top">FreeBSD-SA-03:18</a>.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="PROC" name="PROC">2.2.1 Platform-Specific Hardware
+Support</a></h4>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.2 Boot Loader Changes</a></h4>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="NET-IF" name="NET-IF">2.2.3 Network Interface Support</a></h4>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> now
+supports Broadcom 5705 based Gigabit Ethernet NICs.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver
+once again transmits packets correctly through Davicom DC9102 cards.</p>
+
+<p>The proatm driver has been added to support ProSum's ProATM (IDT77252-based)
+interfaces. This driver is analogous to the patm driver in FreeBSD-CURRENT.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a> now
+supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs.</p>
+
+<p>The suspend/resume support for the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wi</span>(4)</span></a> driver now
+works correctly when the device is configured down.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.4 Network Protocols</a></h4>
+
+<p>A bug in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> limit
+rule processing that could cause various panics has been fixed.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rules
+now support comma-separated address lists (such as <var class="LITERAL">1.2.3.4,
+5.6.7.8/30, 9.10.11.12/22</var>), and allow spaces after commas to make lists of
+addresses more readable.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rules
+now support C++-style comments. Each comment is stored together with its rule and appears
+using the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> <var
+class="LITERAL">show</var> command.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> can now
+modify <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rules in
+set 31, which was read-only and used for the default rules. They can be deleted by <tt
+class="COMMAND">ipfw delete set 31</tt> command but are not deleted by the <tt
+class="COMMAND">ipfw flush</tt> command. This implements a flexible form of ``persistent
+rules''. More details can be found in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a>.</p>
+
+<p>Kernel support has been added for Protocol Independent Multicast routing.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.5 Disks and Storage</a></h4>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=da&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">da</span>(4)</span></a> driver no
+longer tries to send 6-byte commands to USB and Firewire devices. Quirks for USB devices
+(which hopefully are now unnecessary) have been disabled; to restore the old behavior,
+add <var class="LITERAL">options DA_OLD_QUIRKS</var> to the kernel configuration.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=twe&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twe</span>(4)</span></a> driver
+now supports the 3ware generic API.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="FS" name="FS">2.2.6 File Systems</a></h4>
+
+<p>A new <var class="LITERAL">DIRECTIO</var> kernel option enables support for read
+operations that bypass the buffer cache and put data directly into a userland buffer.
+This feature requires that the <var class="LITERAL">O_DIRECT</var> flag is set on the
+file descriptor and that both the offset and length for the read operation are multiples
+of the physical media sector size.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="PCCARD" name="PCCARD">2.2.7 PCCARD Support</a></h4>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="MM" name="MM">2.2.8 Multimedia Support</a></h4>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now
+supports a <var class="OPTION">-i</var> option to limit the scope of the current
+operation to the ARP entries on a particular interface. This option applies to the
+display operations only. It should be useful on routers with numerous network
+interfaces.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">chroot</span>(8)</span></a> now
+allows the optional setting of a user, primary group, or group list to use inside the
+chroot environment via the <var class="OPTION">-u</var>, <var class="OPTION">-g</var>,
+and <var class="OPTION">-G</var> options respectively.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> <var
+class="LITERAL">list</var> and <var class="LITERAL">show</var> command now support ranges
+of rule numbers.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> now
+supports a <var class="OPTION">-n</var> flag to test the syntax of commands without
+actually changing anything.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_msdos&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mount_msdos</span>(8)</span></a>
+utility now supports a <var class="OPTION">-M</var> option to specify the maximum file
+permissions for directories in the file system.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=systat&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">systat</span>(1)</span></a> now
+includes displays for IPv6 and ICMPv6 traffic.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uudecode&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uudecode</span>(1)</span></a> and
+<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=b64decode&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">b64decode</span>(1)</span></a> now
+support a <var class="OPTION">-r</var> flag for decoding raw (or broken) files that may
+be missing the initial and possibly final framing lines.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 Contributed Software</a></h3>
+
+<p><b class="APPLICATION">groff</b> has been updated from 1.18.1 to 1.19.</p>
+
+<p><b class="APPLICATION">lukemftpd</b> (not built by default) has been updated from a
+1.2beta1 to a 5 January 2003 snapshot from the NetBSD CVS repository.</p>
+
+<p><b class="APPLICATION">OpenSSL</b> has been updated from 0.9.7a to 0.9.7c.</p>
+
+<p><b class="APPLICATION">sendmail</b> has been updated to version 8.12.9.</p>
+
+<p><b class="APPLICATION">texinfo</b> has been updated from 4.5 to 4.6.</p>
+
+<p>The timezone database has been updated from the <tt class="FILENAME">tzdata2003a</tt>
+release to the <tt class="FILENAME">tzdata2003d</tt> release.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection
+Infrastructure</a></h3>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a>
+now supports a <var class="OPTION">-C</var> option, which allows packages to register a
+list of other packages with which they conflict. They will refuse to install (via <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>) if
+one of the listed packages is already present. The <var class="OPTION">-f</var> flag to
+<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>
+overrides this conflict-checking.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and
+Integration</a></h3>
+
+<p>The supported release of <b class="APPLICATION">GNOME</b> has been updated from 2.2 to
+2.4.</p>
+
+<p>The supported release of <b class="APPLICATION">KDE</b> has been updated from 3.1 to
+3.1.4.</p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of
+FreeBSD</a></h2>
+
+<p>If you're upgrading from a previous release of FreeBSD, you generally will have three
+options:</p>
+
+<ul>
+<li>
+<p>Using the binary upgrade option of <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>.
+This option is perhaps the quickest, although it presumes that your installation of
+FreeBSD uses no special compilation options.</p>
+</li>
+
+<li>
+<p>Performing a complete reinstall of FreeBSD. Technically, this is not an upgrading
+method, and in any case is usually less convenient than a binary upgrade, in that it
+requires you to manually backup and restore the contents of <tt
+class="FILENAME">/etc</tt>. However, it may be useful in cases where you want (or need)
+to change the partitioning of your disks.</p>
+</li>
+
+<li>
+<p>From source code in <tt class="FILENAME">/usr/src</tt>. This route is more flexible,
+but requires more disk space, time, and technical expertise. More information can be
+found in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html"
+target="_top">``Using <tt class="COMMAND">make world</tt>''</a> section of the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a>. Upgrading from very old versions of FreeBSD may be problematic; in cases
+like this, it is usually more effective to perform a binary upgrade or a complete
+reinstall.</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Please read the <tt class="FILENAME">INSTALL.TXT</tt> file for more information,
+preferably <span class="emphasis"><i class="EMPHASIS">before</i></span> beginning an
+upgrade. If you are upgrading from source, please be sure to read <tt
+class="FILENAME">/usr/src/UPDATING</tt> as well.</p>
+
+<p>Finally, if you want to use one of various means to track the -STABLE or -CURRENT
+branches of FreeBSD, please be sure to consult the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html"
+target="_top">``-CURRENT vs. -STABLE''</a> section of the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a>.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> Upgrading FreeBSD should, of course, only be attempted after backing
+up <span class="emphasis"><i class="EMPHASIS">all</i></span> data and configuration
+files.</p>
+</blockquote>
+</div>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+
diff --git a/en/releases/4.9R/relnotes-i386.html b/en/releases/4.9R/relnotes-i386.html
new file mode 100644
index 0000000000..8796585595
--- /dev/null
+++ b/en/releases/4.9R/relnotes-i386.html
@@ -0,0 +1,571 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>FreeBSD/i386 4.9-RELEASE Release Notes</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+</head>
+<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="ARTICLE">
+<div class="TITLEPAGE">
+<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD/i386 4.9-RELEASE Release
+Notes</a></h1>
+
+<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
+
+<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
+Project</p>
+
+<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.22.2.386 2003/10/19 18:33:34 bmah Exp $<br />
+</p>
+
+<div>
+<div class="ABSTRACT"><a id="AEN12" name="AEN12"></a>
+<p>The release notes for FreeBSD 4.9-RELEASE contain a summary of the changes made to the
+FreeBSD base system since 4.8-RELEASE. Both changes for kernel and userland are listed,
+as well as applicable security advisories for the base system that were issued since the
+last release. Some brief remarks on upgrading are also presented.</p>
+</div>
+</div>
+
+<hr />
+</div>
+
+<div class="TOC">
+<dl>
+<dt><b>Table of Contents</b></dt>
+
+<dt>1 <a href="#INTRO">Introduction</a></dt>
+
+<dt>2 <a href="#NEW">What's New</a></dt>
+
+<dd>
+<dl>
+<dt>2.1 <a href="#SECURITY">Security Advisories</a></dt>
+
+<dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt>
+
+<dd>
+<dl>
+<dt>2.2.1 <a href="#PROC">Platform-Specific Hardware Support</a></dt>
+
+<dt>2.2.2 <a href="#BOOT">Boot Loader Changes</a></dt>
+
+<dt>2.2.3 <a href="#NET-IF">Network Interface Support</a></dt>
+
+<dt>2.2.4 <a href="#NET-PROTO">Network Protocols</a></dt>
+
+<dt>2.2.5 <a href="#DISKS">Disks and Storage</a></dt>
+
+<dt>2.2.6 <a href="#FS">File Systems</a></dt>
+
+<dt>2.2.7 <a href="#PCCARD">PCCARD Support</a></dt>
+
+<dt>2.2.8 <a href="#MM">Multimedia Support</a></dt>
+</dl>
+</dd>
+
+<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt>
+
+<dt>2.4 <a href="#CONTRIB">Contributed Software</a></dt>
+
+<dt>2.5 <a href="#PORTS">Ports/Packages Collection Infrastructure</a></dt>
+
+<dt>2.6 <a href="#RELENG">Release Engineering and Integration</a></dt>
+</dl>
+</dd>
+
+<dt>3 <a href="#UPGRADE">Upgrading from previous releases of FreeBSD</a></dt>
+</dl>
+</div>
+
+<div class="SECT1">
+<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
+
+<p>This document contains the release notes for FreeBSD 4.9-RELEASE on the i386 hardware
+platform. It describes new features of FreeBSD that have been added (or changed) since
+4.8-RELEASE. It also provides some notes on upgrading from previous versions of
+FreeBSD.</p>
+
+<p>This distribution of FreeBSD 4.9-RELEASE is a release distribution. It can be found at
+<a href="ftp://ftp.FreeBSD.org/" target="_top">ftp://ftp.FreeBSD.org/</a> or any of its
+mirrors. More information on obtaining this (or other) release distributions of FreeBSD
+can be found in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html"
+target="_top">``Obtaining FreeBSD''</a> appendix in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a>.</p>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="NEW" name="NEW">2 What's New</a></h2>
+
+<p>This section describes the most user-visible new or changed features in FreeBSD since
+4.8-RELEASE. Typical release note items document new drivers or hardware support, new
+commands or options, major bugfixes, or contributed software upgrades. Security
+advisories for the base system that were issued after 4.8-RELEASE are also listed.</p>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3>
+
+<p>A remotely-exploitable buffer overflow vulnerability in <b
+class="APPLICATION">sendmail</b> has been fixed. For more details, see security advisory
+<a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc"
+target="_top">FreeBSD-SA-03:07</a>. In FreeBSD 4.8-RELEASE, this vulnerability was fixed
+using a vendor-supplied patch (but too late for inclusion in the release notes). In
+FreeBSD 4.9-RELEASE, it has been fixed with the import of a new version of <b
+class="APPLICATION">sendmail</b>.</p>
+
+<p>A single-byte buffer overflow in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&amp;sektion=3&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">realpath</span>(3)</span></a> has
+been fixed. See security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:08.realpath.asc"
+target="_top">FreeBSD-SA-03:08</a>.</p>
+
+<p>A bug that could allow the kernel to attempt delivery of invalid signals has been
+fixed. The bug could have led to a kernel panic. For more information, see security
+advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:09.signal.asc"
+target="_top">FreeBSD-SA-03:09</a>.</p>
+
+<p>A bug in the iBCS2 emulation module, which could result in disclosing the contents of
+kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more
+information, see security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:10.ibcs2.asc"
+target="_top">FreeBSD-SA-03:10</a>.</p>
+
+<p>A programming error in the <b class="APPLICATION">sendmail</b> implementation of its
+``DNS maps'' feature has been fixed by the import of a new version of <b
+class="APPLICATION">sendmail</b>. More information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:11.sendmail.asc"
+target="_top">FreeBSD-SA-03:11</a>. Note that this feature is not used by the default
+configuration files shipped with FreeBSD.</p>
+
+<p>A buffer management bug in <b class="APPLICATION">OpenSSH</b>, which could potentially
+cause a crash, has been fixed. More information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:12.openssh.asc"
+target="_top">FreeBSD-SA-03:12</a>.</p>
+
+<p>A buffer overflow in <b class="APPLICATION">sendmail</b> has been fixed. More
+information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:13.sendmail.asc"
+target="_top">FreeBSD-SA-03:13</a>.</p>
+
+<p>A bug that could allow the kernel to cause resource starvation which eventually
+results in a system panic in the ARP cache code has been fixed. More information can be
+found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:14.arp.asc"
+target="_top">FreeBSD-SA-03:14</a>.</p>
+
+<p>Several errors in the <b class="APPLICATION">OpenSSH</b> PAM challenge/authentication
+subsystem have been fixed. The impacts of these bugs vary; details can be found in
+security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:15.openssh.asc"
+target="_top">FreeBSD-SA-03:15</a>.</p>
+
+<p>A bug in the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=readv&amp;sektion=2&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">readv</span>(2)</span></a> system
+call, which could potentially cause a system crash or privilege escalation has been
+fixed. More information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:16.filedesc.asc"
+target="_top">FreeBSD-SA-03:16</a>.</p>
+
+<p>A bug in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=procfs&amp;sektion=5&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">procfs</span>(5)</span></a> and <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=linprocfs&amp;sektion=5&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">linprocfs</span>(5)</span></a>,
+which could result in disclosing the contents of kernel memory, has been fixed. More
+information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:17.procfs.asc"
+target="_top">FreeBSD-SA-03:17</a>.</p>
+
+<p>Four separate security flaws in <b class="APPLICATION">OpenSSL</b>, which could allow
+a remote attacker to crash an <b class="APPLICATION">OpenSSL</b>-using application or to
+execute arbitrary code with the privileges of the application, have been fixed. More
+information can be found in security advisory <a
+href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:18.openssl.asc"
+target="_top">FreeBSD-SA-03:18</a>.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3>
+
+<p>A bug that caused <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a> to
+register an AT keyboard during console initialization, even when no AT keyboard was
+connected, has been fixed. <tt class="COMMAND">kbdcontrol -k /dev/kbd1</tt> is no longer
+needed when only a USB keyboard is connected.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=hifn&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hifn</span>(4)</span></a> driver
+now supports symmetric crypto for the 7955 and 7956 chipsets.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=safe&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">safe</span>(4)</span></a> driver
+has been added to support SafeNet 1141- and 1741-based crypto accelerators.</p>
+
+<div class="WARNING">
+<blockquote class="WARNING">
+<p><b>Warning:</b> This driver should be considered experimental and and should be used
+with some caution.</p>
+</blockquote>
+</div>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> The public key support is not implemented.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="PROC" name="PROC">2.2.1 Platform-Specific Hardware
+Support</a></h4>
+
+<p>A bug which prevented the kernel from booting on an Intel 80386 processor has been
+corrected.</p>
+
+<p>Support for the Physical Address Extensions (PAE) capability on Intel Pentium Pro and
+higher processors has been added. This allows the use of up to 64GB of RAM in a machine,
+although the amount of memory usable by any single process (or the FreeBSD kernel) is
+unchanged. The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pae&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pae</span>(4)</span></a> manual
+page has more details on this feature.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.2 Boot Loader Changes</a></h4>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="NET-IF" name="NET-IF">2.2.3 Network Interface Support</a></h4>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> now
+supports Broadcom 5705 based Gigabit Ethernet NICs.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver
+once again transmits packets correctly through Davicom DC9102 cards.</p>
+
+<p>The proatm driver has been added to support ProSum's ProATM (IDT77252-based)
+interfaces. This driver is analogous to the patm driver in FreeBSD-CURRENT.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rue</span>(4)</span></a> network
+driver has been added, providing support for Ethernet adapters based on the RealTek
+RTL8150 USB to Fast Ethernet controller chip.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sbsh&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbsh</span>(4)</span></a> driver
+for the Granch SBNI16 SHDSL modem has been added.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a> now
+supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs.</p>
+
+<p>The suspend/resume support for the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">wi</span>(4)</span></a> driver now
+works correctly when the device is configured down.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.4 Network Protocols</a></h4>
+
+<p>A bug in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> limit
+rule processing that could cause various panics has been fixed.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rules
+now support comma-separated address lists (such as <var class="LITERAL">1.2.3.4,
+5.6.7.8/30, 9.10.11.12/22</var>), and allow spaces after commas to make lists of
+addresses more readable.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rules
+now support C++-style comments. Each comment is stored together with its rule and appears
+using the <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> <var
+class="LITERAL">show</var> command.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> can now
+modify <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rules in
+set 31, which was read-only and used for the default rules. They can be deleted by <tt
+class="COMMAND">ipfw delete set 31</tt> command but are not deleted by the <tt
+class="COMMAND">ipfw flush</tt> command. This implements a flexible form of ``persistent
+rules''. More details can be found in <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a>.</p>
+
+<p>Kernel support has been added for Protocol Independent Multicast routing.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.5 Disks and Storage</a></h4>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=da&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">da</span>(4)</span></a> driver no
+longer tries to send 6-byte commands to USB and Firewire devices. Quirks for USB devices
+(which hopefully are now unnecessary) have been disabled; to restore the old behavior,
+add <var class="LITERAL">options DA_OLD_QUIRKS</var> to the kernel configuration.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=twe&amp;sektion=4&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twe</span>(4)</span></a> driver
+now supports the 3ware generic API.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="FS" name="FS">2.2.6 File Systems</a></h4>
+
+<p>A new <var class="LITERAL">DIRECTIO</var> kernel option enables support for read
+operations that bypass the buffer cache and put data directly into a userland buffer.
+This feature requires that the <var class="LITERAL">O_DIRECT</var> flag is set on the
+file descriptor and that both the offset and length for the read operation are multiples
+of the physical media sector size.</p>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="PCCARD" name="PCCARD">2.2.7 PCCARD Support</a></h4>
+</div>
+
+<div class="SECT3">
+<hr />
+<h4 class="SECT3"><a id="MM" name="MM">2.2.8 Multimedia Support</a></h4>
+</div>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now
+supports a <var class="OPTION">-i</var> option to limit the scope of the current
+operation to the ARP entries on a particular interface. This option applies to the
+display operations only. It should be useful on routers with numerous network
+interfaces.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">chroot</span>(8)</span></a> now
+allows the optional setting of a user, primary group, or group list to use inside the
+chroot environment via the <var class="OPTION">-u</var>, <var class="OPTION">-g</var>,
+and <var class="OPTION">-G</var> options respectively.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> <var
+class="LITERAL">list</var> and <var class="LITERAL">show</var> command now support ranges
+of rule numbers.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> now
+supports a <var class="OPTION">-n</var> flag to test the syntax of commands without
+actually changing anything.</p>
+
+<p>The <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_msdos&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mount_msdos</span>(8)</span></a>
+utility now supports a <var class="OPTION">-M</var> option to specify the maximum file
+permissions for directories in the file system.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=systat&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">systat</span>(1)</span></a> now
+includes displays for IPv6 and ICMPv6 traffic.</p>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=uudecode&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uudecode</span>(1)</span></a> and
+<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=b64decode&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">b64decode</span>(1)</span></a> now
+support a <var class="OPTION">-r</var> flag for decoding raw (or broken) files that may
+be missing the initial and possibly final framing lines.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 Contributed Software</a></h3>
+
+<p>The Intel ACPI 20030228 distribution (with local FreeBSD changes and support code) has
+been imported. This feature should be considered experimental and should be tested prior
+to being deployed in a production environment.</p>
+
+<div class="NOTE">
+<blockquote class="NOTE">
+<p><b>Note:</b> Unlike on FreeBSD-CURRENT, the ACPI driver must be statically compiled
+into the kernel by adding <var class="LITERAL">device acpica</var> to a kernel
+configuration. There is no kernel module. This driver is not present in the default, <tt
+class="FILENAME">GENERIC</tt> kernel.</p>
+</blockquote>
+</div>
+
+<br />
+<br />
+<p><b class="APPLICATION">groff</b> has been updated from 1.18.1 to 1.19.</p>
+
+<p><b class="APPLICATION">lukemftpd</b> (not built by default) has been updated from a
+1.2beta1 to a 5 January 2003 snapshot from the NetBSD CVS repository.</p>
+
+<p><b class="APPLICATION">OpenSSL</b> has been updated from 0.9.7a to 0.9.7c.</p>
+
+<p><b class="APPLICATION">sendmail</b> has been updated to version 8.12.9.</p>
+
+<p><b class="APPLICATION">texinfo</b> has been updated from 4.5 to 4.6.</p>
+
+<p>The timezone database has been updated from the <tt class="FILENAME">tzdata2003a</tt>
+release to the <tt class="FILENAME">tzdata2003d</tt> release.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection
+Infrastructure</a></h3>
+
+<p><a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a>
+now supports a <var class="OPTION">-C</var> option, which allows packages to register a
+list of other packages with which they conflict. They will refuse to install (via <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>) if
+one of the listed packages is already present. The <var class="OPTION">-f</var> flag to
+<a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>
+overrides this conflict-checking.</p>
+</div>
+
+<div class="SECT2">
+<hr />
+<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and
+Integration</a></h3>
+
+<p>The supported release of <b class="APPLICATION">GNOME</b> has been updated from 2.2 to
+2.4.</p>
+
+<p>The supported release of <b class="APPLICATION">KDE</b> has been updated from 3.1 to
+3.1.4.</p>
+</div>
+</div>
+
+<div class="SECT1">
+<hr />
+<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of
+FreeBSD</a></h2>
+
+<p>If you're upgrading from a previous release of FreeBSD, you generally will have three
+options:</p>
+
+<ul>
+<li>
+<p>Using the binary upgrade option of <a
+href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+4.9-RELEASE">
+<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>.
+This option is perhaps the quickest, although it presumes that your installation of
+FreeBSD uses no special compilation options.</p>
+</li>
+
+<li>
+<p>Performing a complete reinstall of FreeBSD. Technically, this is not an upgrading
+method, and in any case is usually less convenient than a binary upgrade, in that it
+requires you to manually backup and restore the contents of <tt
+class="FILENAME">/etc</tt>. However, it may be useful in cases where you want (or need)
+to change the partitioning of your disks.</p>
+</li>
+
+<li>
+<p>From source code in <tt class="FILENAME">/usr/src</tt>. This route is more flexible,
+but requires more disk space, time, and technical expertise. More information can be
+found in the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html"
+target="_top">``Using <tt class="COMMAND">make world</tt>''</a> section of the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a>. Upgrading from very old versions of FreeBSD may be problematic; in cases
+like this, it is usually more effective to perform a binary upgrade or a complete
+reinstall.</p>
+</li>
+</ul>
+
+<br />
+<br />
+<p>Please read the <tt class="FILENAME">INSTALL.TXT</tt> file for more information,
+preferably <span class="emphasis"><i class="EMPHASIS">before</i></span> beginning an
+upgrade. If you are upgrading from source, please be sure to read <tt
+class="FILENAME">/usr/src/UPDATING</tt> as well.</p>
+
+<p>Finally, if you want to use one of various means to track the -STABLE or -CURRENT
+branches of FreeBSD, please be sure to consult the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html"
+target="_top">``-CURRENT vs. -STABLE''</a> section of the <a
+href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
+Handbook</a>.</p>
+
+<div class="IMPORTANT">
+<blockquote class="IMPORTANT">
+<p><b>Important:</b> Upgrading FreeBSD should, of course, only be attempted after backing
+up <span class="emphasis"><i class="EMPHASIS">all</i></span> data and configuration
+files.</p>
+</blockquote>
+</div>
+</div>
+</div>
+
+<hr />
+<p align="center"><small>This file, and other release-related documents, can be
+downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
+
+<p align="center"><small>For questions about FreeBSD, read the <a
+href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
+href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
+
+<p align="center"><small>For questions about this documentation, e-mail &#60;<a
+href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
+
+<br />
+<br />
+</body>
+</html>
+