diff --git a/en/releases/6.1R/errata.html b/en/releases/6.1R/errata.html new file mode 100644 index 0000000000..e379b3e8d0 --- /dev/null +++ b/en/releases/6.1R/errata.html @@ -0,0 +1,445 @@ +<!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 6.0-RELEASE Errata</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.0-RELEASE Errata</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The +FreeBSD Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v +1.73.2.15.2.1 2006/04/24 01:05:46 delphij Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN22" name="AEN22"></a> +<p>This document lists errata items for FreeBSD 6.0-RELEASE, containing significant +information discovered after the release or too late in the release cycle to be otherwise +included in the release documentation. This information includes security advisories, as +well as news relating to the software or documentation that could affect its operation or +usability. An up-to-date version of this document should always be consulted before +installing this version of FreeBSD.</p> + +<p>This errata document for FreeBSD 6.0-RELEASE will be maintained until the release of +FreeBSD 6.2-RELEASE.</p> +</div> +</blockquote> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This errata document contains “late-breaking news” about FreeBSD +6.0-RELEASE. Before installing this version, it is important to consult this document to +learn about any post-release discoveries or problems that may already have been found and +fixed.</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 6.1-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="LATE-NEWS" name="LATE-NEWS">2 Update Information</a></h2> + +<p>No news.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SECURITY" name="SECURITY">3 Security Advisories</a></h2> + +<p>The following security advisories pertain to FreeBSD 6.0-RELEASE. For more +information, consult the individual advisories available from <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/" +target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/</a>.</p> + +<div class="INFORMALTABLE"><a id="AEN43" name="AEN43"></a> +<table border="0" frame="void" class="CALSTABLE"> +<col width="1*" /> +<col width="1*" /> +<col width="3*" /> +<thead> +<tr> +<th>Advisory</th> +<th>Date</th> +<th>Topic</th> +</tr> +</thead> + +<tbody> +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:14.fpu.asc" +target="_top">06:14.fpu</a></td> +<td>19 April 2006</td> +<td> +<p>FPU information disclosure</p> +</td> +</tr> + +<tr> +<td><a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc" +target="_top">06:13.sendmail</a></td> +<td>22 March 2006</td> +<td> +<p>Race condition in sendmail</p> +</td> +</tr> + +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc" +target="_top">06:12.opie</a></td> +<td>22 March 2006</td> +<td> +<p>OPIE arbitrary password change</p> +</td> +</tr> + +<tr> +<td><a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc" +target="_top">06:11.ipsec</a></td> +<td>22 March 2006</td> +<td> +<p>IPsec replay attack vulnerability</p> +</td> +</tr> + +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc" +target="_top">06:10.nfs</a></td> +<td>1 March 2006</td> +<td> +<p>Remote denial of service in NFS server</p> +</td> +</tr> + +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc" +target="_top">06:07.pf</a></td> +<td>25 January 2006</td> +<td> +<p>IP fragment handling panic in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a></p> +</td> +</tr> + +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc" +target="_top">06:06.kmem</a></td> +<td>25 January 2006</td> +<td> +<p>Local kernel memory disclosure</p> +</td> +</tr> + +<tr> +<td><a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc" +target="_top">06:05.80211</a></td> +<td>18 January 2006</td> +<td> +<p>IEEE 802.11 buffer overflow</p> +</td> +</tr> + +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc" +target="_top">06:04.ipfw</a></td> +<td>11 January 2006</td> +<td> +<p><a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +fragment denial of service</p> +</td> +</tr> + +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc" +target="_top">06:03.cpio</a></td> +<td>11 January 2006</td> +<td> +<p>Multiple vulnerabilities in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a></p> +</td> +</tr> + +<tr> +<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc" +target="_top">06:02.eex</a></td> +<td>11 January 2006</td> +<td> +<p><a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> temporary file +privilege escalation</p> +</td> +</tr> + +<tr> +<td><a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc" +target="_top">06:01.texindex</a></td> +<td>11 January 2006</td> +<td> +<p>Texindex temporary file privilege escalation</p> +</td> +</tr> +</tbody> +</table> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="KNOWN-PROBLEMS" name="KNOWN-PROBLEMS">4 Known Problems and +Solutions</a></h2> + +<p>(2005/11/26) On 6.0-RELEASE, the following <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rule is +interpreted in a different way from the previous releases:</p> + +<pre class="PROGRAMLISTING"> +allow ipv6 from 192.168.0.2 to me +</pre> + +<p>When <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> does not +support IPv6 (see the next entry for the details), <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> accepts +this rule and this blocks an IPv6 packet encapsulated in an IPv4 packet (IPv6-over-IPv4 +tunneling, protocol number 41) whose source address is <tt +class="LITERAL">192.168.0.2</tt>. When it supports IPv6, on the other hand, this means a +rule to allow an IPv6 packet from <tt class="LITERAL">192.168.0.2</tt>, and actually <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> rejects +this rule because the syntax is incorrect (“an IPv6 packet from an IPv4 +address” never happens). Unfortunately there is no simple workaround for this +problem.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IPv6 +support still has rough edges and there are other problems due to incompatibility between +the two. As a workaround for them, you can use a combination of IPv4-only <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a>, which +is almost compatible with the prior releases, instead of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> with +IPv6 support. To disable IPv6 support of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a>, use the +<tt class="FILENAME">ipfw.ko</tt> kernel module and do not use the kernel option <tt +class="LITERAL">IPFIREWALL</tt>.</p> + +<p>(2005/11/19) Although the FreeBSD 6.0-RELEASE Release Notes states that <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> +subsystem now supports IPv6, the combination of the <tt class="FILENAME">GENERIC</tt> +kernel and a kernel module <tt class="FILENAME">ipfw.ko</tt> does not support the <tt +class="LITERAL">ip6</tt> protocol keyword for packet filtering rule. This is because the +kernel option <tt class="LITERAL">INET6</tt> in the kernel configuration file is not +recognized when the <tt class="FILENAME">ipfw.ko</tt> is built. To enable IPv6 support of +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a>, rebuild +the kernel with kernel options <tt class="LITERAL">INET6</tt> and <tt +class="LITERAL">IPFIREWALL</tt> instead of using the <tt class="FILENAME">ipfw.ko</tt> +module.</p> + +<p>(2005/11/16) Using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> in +combination with a packet filter such as <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a> can prevent the +network stack from working and/or lead to a system panic after a certain period of time. +This is because it allocates <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mbuf&sektion=9&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mbuf</span>(9)</span></a> buffers +for network packets and never releases a part of them, so eventually all of the buffer +memory will be exhausted. This problem has been fixed in the HEAD and the RELENG_6 branch +after 10:17:15 2005/11/16 UTC.</p> + +<p>(2005/11/16, updated on 2005/11/19) When an <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt +class="LITERAL">divert</tt> rule is specified with the protocol keyword <tt +class="LITERAL">ip</tt> or <tt class="LITERAL">all</tt>, IPv6 packets are silently +discarded at that rule since the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=divert&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">divert</span>(4)</span></a> socket +does not support IPv6. This can be a problem especially for an IPv4 and IPv6 dual-stack +host with <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=natd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">natd</span>(8)</span></a> enabled. +<span class="bold"><b class="EMPHASIS">Note that the kernel module <tt +class="FILENAME">ipfw.ko</tt> does not have this problem because it does not support +IPv6.</b></span> To avoid this problem, use an IPv4 specific divert rule such as <tt +class="LITERAL">divert natd ipv4</tt> instead of <tt class="LITERAL">divert natd +all</tt>.</p> + +<p>(2005/11/6) The FreeBSD 6.0-RELEASE Release Notes wrongly states a kernel option +related to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> as <tt +class="LITERAL">IPFIRWALL_FORWARD</tt>. The correct option keyword is <tt +class="LITERAL">IPFIREWALL_FORWARD</tt>.</p> + +<p>(2005/11/5) The FreeBSD 6.0-RELEASE Release Notes wrongly states the version number of +OpenSSH and IPFilter integrated into FreeBSD as 4.1p1 and 4.1.18. The correct versions +are 4.2p1 and 4.1.8 respectively.</p> + +<p>(2005/11/5) Distribution of 6.0-RELEASE contains <tt +class="FILENAME">CHECKSUM.MD5</tt> and <tt class="FILENAME">CHECKSUM.SHA256</tt> files +for protecting the integrity of data. However, these files in 6.0-RELEASE erroneously +include checksums for the checksum files themselves. Although the checksums look like +wrong, they can be safely ignored because a checksum for the checksum file never +corresponds to one in the file. This problem will be fixed in the next releases.</p> + +<p>(2005/11/5, FreeBSD/amd64 specific) The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pmcstat&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pmcstat</span>(8)</span></a> +utility cannot yet handle 32-bit executables when converting <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hwpmc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hwpmc</span>(4)</span></a> log +files to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gprof&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gprof</span>(1)</span></a> +format.</p> + +<p>(2005/11/5, FreeBSD/powerpc specific) The following panic may occur at boot-time on +some older PowerMac G4 systems:</p> + +<pre class="SCREEN"> +... +KDB: current backend: ddb +panic: Assertion curthread != NULL failed at +/usr/src/sys/kern/kern_mutex.c:268 +KDB: enter panic +</pre> + +<p>This is a known problem with no workaround, and will be fixed in the next release.</p> + +<p>(2005/11/5) Changes of on-disk format of <tt +class="FILENAME">/usr/share/locale/*/LC_*</tt> files in 6.0-RELEASE prevent third-party +software which uses <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=setlocale&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">setlocale</span>(3)</span></a> for +its localization from working after a 5.x system upgraded. The software includes ones +installed into the 5.x system by using FreeBSD Ports Collection and so on. To solve this +problem, perform one of the following:</p> + +<ul> +<li> +<p>Install misc/compat5x package into the upgraded 6.0 system. This package installs a +library <tt class="FILENAME">lib/compat/libc.so.5</tt> which makes the software complied +in a 5.x system use the old locale files to keep compatibility. Note that you need to +remove <tt class="FILENAME">/lib/libc.so.5</tt> after upgrading.</p> + +<p>This package is available only for Tier-1 platforms.</p> +</li> + +<li> +<p>Recompile the software on the 6.0 system.</p> +</li> +</ul> + +<p>(2005/10/3) At boot time the FreeBSD/sparc64 GENERIC kernel may output the following +messages when the machine has no framebuffer:</p> + +<pre class="SCREEN"> +Aug 26 19:31:27 hostname getty[429]: open /dev/ttyv1: No such file or directory +</pre> + +<p>This is because the machine with no supported graphics hardware does not recognize <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and +<tt class="FILENAME">/dev/ttyv*</tt> device nodes are not created. This is not a harmful +error and can be suppressed by disabling <tt class="FILENAME">/dev/ttyv*</tt> entries in +<tt class="FILENAME">/etc/ttys</tt>.</p> + +<p>(2005/10/3) Kernel modules do not work on FreeBSD/sparc64 when the machine has more +than 4GB memory. There is no workaround for this issue except for compiling the modules +statically into your custom kernel in advance.</p> + +<p>(2005/10/3) The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kgdb&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kgdb</span>(1)</span></a> utility +does not work properly on FreeBSD/sparc64 for debugging panics which include traps. As a +workaround you can use <tt class="FILENAME">devel/gdb53</tt>.</p> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/hardware-alpha.html b/en/releases/6.1R/hardware-alpha.html new file mode 100644 index 0000000000..ff6256c5f5 --- /dev/null +++ b/en/releases/6.1R/hardware-alpha.html @@ -0,0 +1,5701 @@ +<!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 6.1-RELEASE Hardware Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.1-RELEASE Hardware +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<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="#SUPPORT-PROC">Supported processors and motherboards</a></dt> + +<dd> +<dl> +<dt>2.1 <a href="#AEN29">Overview</a></dt> + +<dt>2.2 <a href="#AEN45">In general, what do you need to run FreeBSD on an +Alpha?</a></dt> + +<dt>2.3 <a href="#AEN106">System-specific information</a></dt> + +<dd> +<dl> +<dt>2.3.1 <a href="#AEN111">AXPpci33 (“NoName”)</a></dt> + +<dt>2.3.2 <a href="#AEN186">Personal Workstation (“Miata”)</a></dt> + +<dt>2.3.3 <a href="#AEN296">Evaluation Board 64 family</a></dt> + +<dt>2.3.4 <a href="#AEN351">Evaluation Board 164 (“EB164, PC164, PC164LX, +PC164SX”) family</a></dt> + +<dt>2.3.5 <a href="#AEN420">AlphaStation 200 (“Mustang”) and 400 +(“Avanti”) series</a></dt> + +<dt>2.3.6 <a href="#AEN487">AlphaStation 500 and 600 (“Alcor” & +“Maverick” for EV5, “Bret” for EV56)</a></dt> + +<dt>2.3.7 <a href="#AEN599">AlphaServer 1000 (“Mikasa”), 1000A +(“Noritake”) and 800(“Corelle”)</a></dt> + +<dt>2.3.8 <a href="#AEN655">DS10/VS10/XP900 (“Webbrick”) / XP1000 +(“Monet”) / DS10L (“Slate”)</a></dt> + +<dt>2.3.9 <a href="#AEN806">DS20/DS20E (“Goldrush”)</a></dt> + +<dt>2.3.10 <a href="#AEN875">AlphaPC 264DP / UP2000</a></dt> + +<dt>2.3.11 <a href="#AEN921">AlphaServer 2000 (“DemiSable”), 2100 +(“Sable”), 2100A (“Lynx”)</a></dt> + +<dt>2.3.12 <a href="#AEN992">AlphaServer 4x00 (“Rawhide”)</a></dt> + +<dt>2.3.13 <a href="#AEN1025">AlphaServer 1200 (“Tincup”) and AlphaStation +1200 (“DaVinci”)</a></dt> + +<dt>2.3.14 <a href="#AEN1055">Alpha Processor Inc. UP1000</a></dt> + +<dt>2.3.15 <a href="#AEN1104">Alpha Processor Inc. UP1100</a></dt> + +<dt>2.3.16 <a href="#AEN1152">Alpha Processor Inc. CS20, Compaq DS20L</a></dt> + +<dt>2.3.17 <a href="#AEN1199">Compaq AlphaServer ES40 (“Clipper”)</a></dt> +</dl> +</dd> + +<dt>2.4 <a href="#AEN1236">Supported Hardware Overview</a></dt> + +<dt>2.5 <a href="#AEN1267">Acknowledgments</a></dt> +</dl> +</dd> + +<dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + +<dd> +<dl> +<dt>3.1 <a href="#DISK">Disk Controllers</a></dt> + +<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt> + +<dt>3.3 <a href="#TOKENRING">Token Ring Interfaces</a></dt> + +<dt>3.4 <a href="#FDDI">FDDI Interfaces</a></dt> + +<dt>3.5 <a href="#ATM">ATM Interfaces</a></dt> + +<dt>3.6 <a href="#WLAN">Wireless Network Interfaces</a></dt> + +<dt>3.7 <a href="#MISC-NETWORK">Miscellaneous Networks</a></dt> + +<dt>3.8 <a href="#ISDN">ISDN Interfaces</a></dt> + +<dt>3.9 <a href="#SERIAL">Serial Interfaces</a></dt> + +<dt>3.10 <a href="#SOUND">Sound Devices</a></dt> + +<dt>3.11 <a href="#CAMERA">Camera and Video Capture Devices</a></dt> + +<dt>3.12 <a href="#USB">USB Devices</a></dt> + +<dt>3.13 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt> + +<dt>3.14 <a href="#BLUETOOTH">Bluetooth Devices</a></dt> + +<dt>3.15 <a href="#CRYPTO-ACCEL">Cryptographic Accelerators</a></dt> + +<dt>3.16 <a href="#MISC">Miscellaneous</a></dt> +</dl> +</dd> +</dl> +</div> + +<div class="SECT1"> +<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This document contains the hardware compatibility notes for FreeBSD 6.1-RELEASE on the +Alpha/AXP hardware platform (also referred to as FreeBSD/alpha 6.1-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 compatibility notes for other architectures will +differ in some details.</p> +</blockquote> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT-PROC" name="SUPPORT-PROC">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="AEN29" name="AEN29">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> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN45" name="AEN45">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>In case you have problems making your selection of SRM 'stick', in other words if the +system falls back to AlphaBIOS after you selected the SRM console, it is time to check if +the battery of your CMOS clock/parameter RAM is empty. If so, a replacement battery most +likely fixes the issue.</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>In order to be bootable the root partition (partition a) must be at offset 0 of the +disk drive. This means you have to use the installer's partitioning menu and start with +assigning partition a at offset 0 to the root partition. Subsequently layout the rest of +the partitions to your liking. If you do not adhere to this rule the install will proceed +just fine, but the system will not be bootable from the freshly installed disk. Note that +fdisk is not used on FreeBSD running on Alpha, disks are directly labeled using +disklabel.</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">>>></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 & D +caches compared to the EV4 on which it is based. Rule of thumb: the higher the digit +immediately following “EV” the more desirable (read: faster / more modern). +Spending money on anything less than an EV5 is not recommended. Hardware available for +free is a different matter of course.</p> + +<p>For memory you want at least 32 Mbytes. I have had FreeBSD run on a 16 Mbyte system +years ago but you will not enjoy that. Kernel build times halved when I went to 32 +Mbytes. Note that the SRM console steals 2Mbyte from the total system memory (and keeps +it). For more serious work 128 Mbytes or more are recommended. Although Alpha machines +typically can accommodate large to very large physical memory sizes, FreeBSD is limited +to 1 or 2 Gbytes (dependent on the core chipset) of RAM. This restriction is due to the +current implementation of the VM system.</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="AEN106" name="AEN106">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="AEN111" name="AEN111">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 & 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 ata +</pre> + +<p>The ATA interface uses irq 14.</p> + +<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"> +>>> <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"> +>>> <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="AEN186" name="AEN186">2.3.2 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 & 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">>>></samp> <kbd +class="USERINPUT">SET PCI_DEVICE_OVERRIDE <tt +class="REPLACEABLE"><i><vendor_id></i></tt><tt +class="REPLACEABLE"><i><device_id></i></tt></kbd> +</pre> + +<p>For example:</p> + +<pre class="SCREEN"> +<samp class="PROMPT">>>></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">>>></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<BWEN> +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<BWEN> +Jan 3 12:22:32 miata /kernel: pcib0: <2117x PCI host bus adapter> 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 pcm +device sbc +</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="AEN296" name="AEN296">2.3.3 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 ata +</pre> + +<p>The ATA interface uses irq 14.</p> + +<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="AEN351" name="AEN351">2.3.4 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, non-ECC or ECC can be used [PC164SX]</p> +</li> + +<li> +<p>SDRAM DIMMs in sets of 2, uses ECC [PC164LX]</p> +</li> +</ul> +</li> + +<li> +<p>2 16550A serial ports</p> +</li> + +<li> +<p>PS/2 style keyboard & 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. Symbios 53C896 has been confirmed to not work.</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. A test with an Adaptec 3940UW showed that that one is not supported +however. 164SX SRM recognises Intel 8255x Ethernet cards which show up as eia. Using such +a NIC allows network booting.</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 (PC100 or PC133) 256MB +DIMMs are reported to work just fine. Whether 512MB DIMMs will also work is currently +unknown. You can use ECC or non-ECC DIMMs. The non-ECC ones are the same as commonly +found in PCs. Unfortunately the 164SX is quite picky on which DIMMs it likes, so be +prepared to test and experiment.</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 lose its variable settings. “For PC164, +current superstition says that, to avoid losing settings, you want to first downgrade to +SRM 4.x and then upgrade to 5.x.” One sample error that was observed was:</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">>>></samp> <kbd class="USERINPUT">ISACFG -INIT</kbd> +</pre> + +<p>followed by</p> + +<pre class="SCREEN"> +<samp class="PROMPT">>>></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="AEN420" name="AEN420">2.3.5 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 100 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 & +250-series)</p> +</li> + +<li> +<p>ISA expansion slots (4 for the AS400-series, 2 for the AS200 & 250-series) (some +ISA/PCI slots are physically shared)</p> +</li> + +<li> +<p>embedded 21040-based Ethernet (200 & 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 & 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 & AS250 sound hardware is reported to work OK assuming you have the +following line in your kernel config file:</p> + +<pre class="PROGRAMLISTING"> +device pcm +</pre> + +<p>The sound device uses port 0x530, IRQ 10 and drq 0. You also need to specify flags +0x10011 in the <tt class="FILENAME">device.hints</tt> file.</p> + +<p>AlphaStation 200 & 250 series have an automatic SCSI terminator. This means that +as soon as you plug a cable onto the external SCSI connector the internal terminator of +the system is disabled. It also means that you should not leave unterminated cables +plugged into the machine.</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">>>></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">>>></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="AEN487" name="AEN487">2.3.6 AlphaStation 500 and 600 +(“Alcor” & “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: <DEC RRD45 DEC 0436> 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. Keep the card, which apart from +the two SCSI interfaces also houses the Ethernet chip by the way in the DEC-recommended, +topmost, 32bit PCI slot. You get machine checks if you plug it into one of the 64 bit +slots.</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 pcm +</pre> + +<p>to the kernel configuration file.</p> + +<p>Using the ECU I configured my AS500 to use IRQ 10, port 0x530, drq 0. Corresponding +entries along with flags 0x10011 must go into the <tt class="FILENAME">device.hints</tt> +file. Note that the flags value is rather non-standard.</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="AEN599" name="AEN599">2.3.7 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"> +>>> <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"> +>>> <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="AEN655" name="AEN655">2.3.8 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="AEN661" name="AEN661">2.3.8.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 & 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 <tt class="LITERAL">cpu EV6</tt> +defined for inclusion in the kernel config file. The <tt class="LITERAL">cpu EV5</tt> is +mandatory to keep <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-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="AEN726" name="AEN726">2.3.8.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 & 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 <code class="VARNAME">usb_enable</code> is +set to <tt class="LITERAL">on</tt>. You can change this by performing:</p> + +<pre class="SCREEN"> +<samp class="PROMPT">>>></samp> <kbd class="USERINPUT">SET USB_ENABLE ON</kbd> +</pre> + +<div class="IMPORTANT"> +<blockquote class="IMPORTANT"> +<p><b>Important:</b> 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.</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 <tt class="LITERAL">cpu EV6</tt> +defined for inclusion in the kernel config file. The <tt class="LITERAL">cpu EV5</tt> is +mandatory to keep <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-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="AEN806" name="AEN806">2.3.9 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">>>></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">>>></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 +<tt class="LITERAL">CONSOLE</tt> 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" 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 <tt class="LITERAL">0</tt> 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 <tt class="LITERAL">cpu EV6</tt> +defined for inclusion in the kernel config file. The <tt class="LITERAL">cpu EV5</tt> is +mandatory to keep <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-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="AEN875" name="AEN875">2.3.10 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 <tt class="LITERAL">cpu EV6</tt> +defined for inclusion in the kernel config file. The <tt class="LITERAL">cpu EV5</tt> is +mandatory to keep <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-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="AEN921" name="AEN921">2.3.11 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" 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 & 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">>>></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">>>></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">>>></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">>>></samp> <kbd class="USERINPUT">SET OCP_TEXT "FreeBSD" + </kbd> +</pre> + +<p>The SRM</p> + +<pre class="SCREEN"> +<samp class="PROMPT">>>></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">>>></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">>>></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">>>></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="AEN992" name="AEN992">2.3.12 AlphaServer 4x00 +(“Rawhide”)</a></h4> + +<p>The AlphaServer 4x00 machines are intended as small enterprise servers. Expect a +30" high pedestal cabinet or alternatively the same system box in a 19" rack. +Rawhides are multi-CPU machines, up to 4 CPUs can be in a single machine. Basic disk +storage is housed in one or two StorageWorks shelves at the bottom of the pedestal. The +Rawhides intended for the NT market are designated DIGITAL Server 7300 (5/400 CPU), +DIGITAL Server 7305 (5/533 CPU). A trailing R on the part-number means a rackmount +variant.</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 & 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 a 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 +interchangeably. Note that if you want remote power on/off to function you need to +connect a small DC adapter to the machine in order to have the RCM logic powered. You +need to supply 9-12V DC to the small inlet located next to the keyboard connector.</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="AEN1025" name="AEN1025">2.3.13 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 & 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 a 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="AEN1055" name="AEN1055">2.3.14 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 & 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 +& cpu. But as always you will have to take your expansion cards and peripherals into +account. The M1543C chip contains power management functionality & temperature +monitoring (via I2C / SM bus).</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="AEN1104" name="AEN1104">2.3.15 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 & 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 +& cpu. But as always you will have to take your expansion cards and peripherals into +account. The M1535D chip contains power management functionality & temperature +monitoring (via I2C / SM bus using a LM75 thermal sensor).</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 <tt class="LITERAL">cpu EV6</tt> defined for +inclusion in the kernel config file. The <tt class="LITERAL">cpu EV5</tt> is mandatory to +keep <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +happy.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN1152" name="AEN1152">2.3.16 Alpha Processor Inc. CS20, Compaq +DS20L</a></h4> + +<p>The CS20 is a 19", 1U high rackmount server based on the 21264[ab] CPU. It can +have a maximum of 2 CPUs. Compaq sells the CS20 rebranded as the AlphaServer DS20L. DS20L +has 833MHz CPUs.</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 & 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" high 3.5" 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 <tt class="LITERAL">cpu EV6</tt> defined for +inclusion in the kernel config file. The <tt class="LITERAL">cpu EV5</tt> is mandatory to +keep <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +happy.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN1199" name="AEN1199">2.3.17 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 & 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 & +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 <tt class="LITERAL">cpu EV6</tt> defined for +inclusion in the kernel config file. The <tt class="LITERAL">cpu EV5</tt> is mandatory to +keep <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-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="AEN1236" name="AEN1236">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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver is +reported not to work correctly with FreeBSD/alpha (although it works excellently on +FreeBSD/x86).</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. TGA support in +FreeBSD is not as robust as it should be. In case of problems it is advisable to try +either a serial console or a plain VGA card.</p> + +<p>The “PC standard” serial ports found on most Alphas are supported.</p> + +<p>ISDN (i4b) is not supported on FreeBSD/alpha.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN1267" name="AEN1267">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"><<a +href="mailto:gallatin@FreeBSD.org">gallatin@FreeBSD.org</a>></code></p> +</li> + +<li> +<p>Chuck Robey <code class="EMAIL"><<a +href="mailto:chuckr@FreeBSD.org">chuckr@FreeBSD.org</a>></code></p> +</li> + +<li> +<p>Matthew Jacob <code class="EMAIL"><<a +href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>></code></p> +</li> + +<li> +<p>Michael Smith <code class="EMAIL"><<a +href="mailto:msmith@FreeBSD.org">msmith@FreeBSD.org</a>></code></p> +</li> + +<li> +<p>David O'Brien <code class="EMAIL"><<a +href="mailto:obrien@FreeBSD.org">obrien@FreeBSD.org</a>></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="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2> + +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.9.2.2 +2006/05/01 08:26:00 brueffer 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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> The device lists in this document are being generated automatically from +FreeBSD manual pages. This means that some devices, which are supported by multiple +drivers, may appear multiple times.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DISK" name="DISK">3.1 Disk Controllers</a></h3> + +<p>IDE/ATA controllers (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a> driver +supports the following SCSI host adapter chips and SCSI controller cards:</p> + +<ul> +<li> +<p>Adaptec AIC7770 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7850 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7860 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7870 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7880 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7890 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7891 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7892 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7895 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7896 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7897 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7899 host adapter chip</p> +</li> + +<li> +<p>Adaptec 274X(W)</p> +</li> + +<li> +<p>Adaptec 274X(T)</p> +</li> + +<li> +<p>Adaptec 284X</p> +</li> + +<li> +<p>Adaptec 2910</p> +</li> + +<li> +<p>Adaptec 2915</p> +</li> + +<li> +<p>Adaptec 2920</p> +</li> + +<li> +<p>Adaptec 2930C</p> +</li> + +<li> +<p>Adaptec 2930U2</p> +</li> + +<li> +<p>Adaptec 2940</p> +</li> + +<li> +<p>Adaptec 2940J</p> +</li> + +<li> +<p>Adaptec 2940N</p> +</li> + +<li> +<p>Adaptec 2940U</p> +</li> + +<li> +<p>Adaptec 2940AU</p> +</li> + +<li> +<p>Adaptec 2940UW</p> +</li> + +<li> +<p>Adaptec 2940UW Dual</p> +</li> + +<li> +<p>Adaptec 2940UW Pro</p> +</li> + +<li> +<p>Adaptec 2940U2W</p> +</li> + +<li> +<p>Adaptec 2940U2B</p> +</li> + +<li> +<p>Adaptec 2950U2W</p> +</li> + +<li> +<p>Adaptec 2950U2B</p> +</li> + +<li> +<p>Adaptec 19160B</p> +</li> + +<li> +<p>Adaptec 29160B</p> +</li> + +<li> +<p>Adaptec 29160N</p> +</li> + +<li> +<p>Adaptec 3940</p> +</li> + +<li> +<p>Adaptec 3940U</p> +</li> + +<li> +<p>Adaptec 3940AU</p> +</li> + +<li> +<p>Adaptec 3940UW</p> +</li> + +<li> +<p>Adaptec 3940AUW</p> +</li> + +<li> +<p>Adaptec 3940U2W</p> +</li> + +<li> +<p>Adaptec 3950U2</p> +</li> + +<li> +<p>Adaptec 3960</p> +</li> + +<li> +<p>Adaptec 39160</p> +</li> + +<li> +<p>Adaptec 3985</p> +</li> + +<li> +<p>Adaptec 4944UW</p> +</li> + +<li> +<p>NEC PC-9821Xt13 (PC-98)</p> +</li> + +<li> +<p>NEC RvII26 (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B02L/B09 (PC-98)</p> +</li> + +<li> +<p>NEC SV-98/2-B03 (PC-98)</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MegaRAID SCSI 320-1E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-8X</p> +</li> + +<li> +<p>MegaRAID SATA 150-4</p> +</li> + +<li> +<p>MegaRAID SATA 150-6</p> +</li> + +<li> +<p>MegaRAID i4 133 RAID</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0</p> +</li> + +<li> +<p>MegaRAID SCSI 320-1</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4</p> +</li> + +<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 Elite 1650 (Series 4xx)</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 3/QC</p> +</li> + +<li> +<p>Dell PERC 4/DC</p> +</li> + +<li> +<p>Dell PERC 4/IM</p> +</li> + +<li> +<p>Dell PERC 4/SC</p> +</li> + +<li> +<p>Dell PERC 4/Di</p> +</li> + +<li> +<p>Dell PERC 4e/DC</p> +</li> + +<li> +<p>Dell PERC 4e/Di</p> +</li> + +<li> +<p>Dell PERC 4e/Si</p> +</li> + +<li> +<p>Dell PERC 4ei</p> +</li> + +<li> +<p>HP NetRAID-1/Si</p> +</li> + +<li> +<p>HP NetRAID-3/Si (D4943A)</p> +</li> + +<li> +<p>HP Embedded NetRAID</p> +</li> + +<li> +<p>Intel RAID Controller SRCS16</p> +</li> + +<li> +<p>Intel RAID Controller SRCU42X</p> +</li> +</ul> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p>Booting from these controllers is not supported due to SRM limitations.</p> +</blockquote> +</div> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>ISP1000</p> +</li> + +<li> +<p>ISP1020</p> +</li> + +<li> +<p>ISP1040</p> +</li> + +<li> +<p>Qlogic 1240</p> +</li> + +<li> +<p>Qlogic 1020</p> +</li> + +<li> +<p>Qlogic 1040</p> +</li> + +<li> +<p>Qlogic 1080</p> +</li> + +<li> +<p>Qlogic 1280</p> +</li> + +<li> +<p>Qlogic 12160</p> +</li> + +<li> +<p>Qlogic 210X</p> +</li> + +<li> +<p>Qlogic 220X</p> +</li> + +<li> +<p>Qlogic 2300</p> +</li> + +<li> +<p>Qlogic 2312</p> +</li> + +<li> +<p>Qlogic 234X</p> +</li> + +<li> +<p>Qlogic 2322</p> +</li> + +<li> +<p>Qlogic 200</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver +supports the following hardware:</p> + +<ul> +<li> +<p>LSI MegaRAID SAS 8408E</p> +</li> + +<li> +<p>LSI MegaRAID SAS 8480E</p> +</li> + +<li> +<p>Dell PERC5/i</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mlx</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Mylex DAC960P</p> +</li> + +<li> +<p>Mylex DAC960PD / DEC KZPSC (Fast Wide)</p> +</li> + +<li> +<p>Mylex DAC960PDU</p> +</li> + +<li> +<p>Mylex DAC960PL</p> +</li> + +<li> +<p>Mylex DAC960PJ</p> +</li> + +<li> +<p>Mylex DAC960PG</p> +</li> + +<li> +<p>Mylex DAC960PU / DEC PZPAC (Ultra Wide)</p> +</li> + +<li> +<p>Mylex AcceleRAID 150 (DAC960PRL)</p> +</li> + +<li> +<p>Mylex AcceleRAID 250 (DAC960PTL1)</p> +</li> + +<li> +<p>Mylex eXtremeRAID 1100 (DAC1164P)</p> +</li> + +<li> +<p>RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA +(3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)</p> +</li> +</ul> + +<p>All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is +always advisable to upgrade to the most recent firmware available for the controller. +Compatible Mylex controllers not listed should work, but have not been verified.</p> + +<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> + +<p>The following controllers are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>LSI Logic 53c1030 (Dual Ultra320 SCSI)</p> +</li> + +<li> +<p>LSI Logic FC909 (1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC909A (Dual 1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC919 (2Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC929, LSI Logic FC929X (Dual 2Gb/s Fibre Channel)</p> +</li> +</ul> + +<p>The SCSI controller chips supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver +can be found onboard on many systems including:</p> + +<ul> +<li> +<p>Dell PowerEdge 1750</p> +</li> + +<li> +<p>IBM eServer xSeries 335</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> driver +provides support for the following NCR/Symbios SCSI controller chips:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C820</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C875J</p> +</li> + +<li> +<p>53C885</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The following add-on boards are known to be supported:</p> + +<ul> +<li> +<p>I-O DATA SC-98/PCI (PC-98)</p> +</li> + +<li> +<p>I-O DATA SC-PCI (PC-98)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> driver +provides support for the following Symbios/LSI Logic PCI SCSI controllers:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C825</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C876</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C897</p> +</li> + +<li> +<p>53C1000</p> +</li> + +<li> +<p>53C1000R</p> +</li> + +<li> +<p>53C1010-33</p> +</li> + +<li> +<p>53C1010-66</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The SCSI controllers supported by <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> can be +either embedded on a motherboard, or on one of the following add-on boards:</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>I-O DATA SC-UPCI (PC-98)</p> +</li> + +<li> +<p>Logitec LHA-521UA (PC-98)</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> + +<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&sektion=4&manpath=FreeBSD+6.1-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&sektion=1&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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver provides +support for the following chipsets:</p> + +<ul> +<li> +<p>DEC/Intel 21143</p> +</li> + +<li> +<p>ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II</p> +</li> + +<li> +<p>ASIX Electronics AX88140A and AX88141</p> +</li> + +<li> +<p>Conexant LANfinity RS7112 (miniPCI)</p> +</li> + +<li> +<p>Davicom DM9009, DM9100, DM9102 and DM9102A</p> +</li> + +<li> +<p>Lite-On 82c168 and 82c169 PNIC</p> +</li> + +<li> +<p>Lite-On/Macronix 82c115 PNIC II</p> +</li> + +<li> +<p>Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732</p> +</li> + +<li> +<p>Xircom X3201 (cardbus only)</p> +</li> +</ul> + +<p>The following NICs are known to work with the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver at this +time:</p> + +<ul> +<li> +<p>3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Abocom FE2500</p> +</li> + +<li> +<p>Accton EN1217 (98715A)</p> +</li> + +<li> +<p>Accton EN2242 MiniPCI</p> +</li> + +<li> +<p>Adico AE310TX (98715A)</p> +</li> + +<li> +<p>Alfa Inc GFC2204 (ASIX AX88140A)</p> +</li> + +<li> +<p>Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, +non-MII)</p> +</li> + +<li> +<p>Built in DE500-BA on DEC Alpha workstations (21143, non-MII)</p> +</li> + +<li> +<p>Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, +MII)</p> +</li> + +<li> +<p>Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)</p> +</li> + +<li> +<p>CNet Pro110B (ASIX AX88140A)</p> +</li> + +<li> +<p>CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)</p> +</li> + +<li> +<p>Compex RL100-TX (98713 or 98713A)</p> +</li> + +<li> +<p>D-Link DFE-570TX (21143, MII, quad port)</p> +</li> + +<li> +<p>Digital DE500-BA 10/100 (21143, non-MII)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CBL/TXA (ADMtek AN985)</p> +</li> + +<li> +<p>Hawking CB102 CardBus</p> +</li> + +<li> +<p>IBM EtherJet Cardbus Adapter</p> +</li> + +<li> +<p>Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)</p> +</li> + +<li> +<p>Jaton XpressNet (Davicom DM9102)</p> +</li> + +<li> +<p>Kingston KNE100TX (21143, MII)</p> +</li> + +<li> +<p>Kingston KNE110TX (PNIC 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX v2.0 (PNIC II 82c115)</p> +</li> + +<li> +<p>LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Matrox FastNIC 10/100 (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>Melco LGY-PCI-TXL</p> +</li> + +<li> +<p>Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)</p> +</li> + +<li> +<p>Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A (98713A)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A Rev B4 (98715AEC-C)</p> +</li> + +<li> +<p>NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)</p> +</li> + +<li> +<p>Netgear FA511</p> +</li> + +<li> +<p>PlaneX FNW-3602-T (ADMtek AN985)</p> +</li> + +<li> +<p>SMC EZ Card 10/100 1233A-TX (ADMtek AN985)</p> +</li> + +<li> +<p>SVEC PN102-TX (98713)</p> +</li> + +<li> +<p>Xircom Cardbus Realport</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet 10/100</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet II 10/100</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec ANA-6944/TX</p> +</li> + +<li> +<p>Cogent EM100FX and EM440TX</p> +</li> + +<li> +<p>Corega FastEther PCI-TX</p> +</li> + +<li> +<p>D-Link DFE-500TX</p> +</li> + +<li> +<p>DEC DE435, DEC DE450, and DEC DE500</p> +</li> + +<li> +<p>ELECOM LD-PCI2T, LD-PCITS</p> +</li> + +<li> +<p>I-O DATA LA2/T-PCI</p> +</li> + +<li> +<p>SMC Etherpower 8432, 9332 and 9334</p> +</li> + +<li> +<p>ZNYX ZX3xx</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, +82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 controller +chips:</p> + +<ul> +<li> +<p>Intel PRO/1000 CT Network Connection (82547)</p> +</li> + +<li> +<p>Intel PRO/1000 F Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 Gigabit Server Adapter (82542)</p> +</li> + +<li> +<p>Intel PRO/1000 GT Desktop Adapter (82541PI)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (LX) (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82540)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82541)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Quad Port Server Adapter (82546EB)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 T Desktop Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 T Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 XF Server Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 XT Server Adapter (82544)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel EtherExpress PRO/10</p> +</li> + +<li> +<p>Intel InBusiness 10/100</p> +</li> + +<li> +<p>Intel PRO/100B / EtherExpressPRO/100 B PCI 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>Contec C-NET(PI)-100TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B06 (PC-98)</p> +</li> + +<li> +<p>Many on-board network interfaces on Intel motherboards</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server +models. Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Sun PCI SunSwift Adapter</p> +</li> + +<li> +<p>Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)</p> +</li> + +<li> +<p>Sun PCI Sun100BaseT Adapter 2.0</p> +</li> + +<li> +<p>Sun SBus Sun100BaseT 2.0</p> +</li> + +<li> +<p>Sun PCI Quad FastEthernet Controller</p> +</li> + +<li> +<p>Sun SBus Quad FastEthernet Controller</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nge</span>(4)</span></a> driver +supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters +including:</p> + +<ul> +<li> +<p>Addtron AEG320T</p> +</li> + +<li> +<p>Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI)</p> +</li> + +<li> +<p>Asante FriendlyNet GigaNIX 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</p> +</li> + +<li> +<p>Netgear GA622T</p> +</li> + +<li> +<p>SMC EZ Card 1000 (SMC9462TX)</p> +</li> + +<li> +<p>Surecom Technology EP-320G-TX</p> +</li> + +<li> +<p>Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcn</span>(4)</span></a> driver +supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, +PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:</p> + +<ul> +<li> +<p>AMD Am79C971 PCnet-FAST</p> +</li> + +<li> +<p>AMD Am79C972 PCnet-FAST+</p> +</li> + +<li> +<p>AMD Am79C973/Am79C975 PCnet-FAST III</p> +</li> + +<li> +<p>AMD Am79C976 PCnet-PRO</p> +</li> + +<li> +<p>AMD Am79C978 PCnet-Home</p> +</li> + +<li> +<p>Allied-Telesis LA-PCI</p> +</li> + +<li> +<p>NEC SV-98/2-B05, B06</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">re</span>(4)</span></a> driver supports +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based Fast Ethernet and Gigabit +Ethernet adapters including:</p> + +<ul> +<li> +<p>Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)</p> +</li> + +<li> +<p>Compaq Evo N1015v Integrated Ethernet (8139C+)</p> +</li> + +<li> +<p>Corega CG-LAPCIGT Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>D-Link DGE-528(T) Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)</p> +</li> + +<li> +<p>LevelOne GNC-0105T (8169S)</p> +</li> + +<li> +<p>PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)</p> +</li> + +<li> +<p>Xterasys XN-152 10/100/1000 NIC (8169)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a> driver +include:</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>Belkin F5D5000</p> +</li> + +<li> +<p>BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)</p> +</li> + +<li> +<p>Compaq HNE-300</p> +</li> + +<li> +<p>CompUSA no-name 10/100 PCI Ethernet NIC</p> +</li> + +<li> +<p>Corega FEther CB-TXD</p> +</li> + +<li> +<p>Corega FEtherII CB-TXD</p> +</li> + +<li> +<p>D-Link DFE-528TX</p> +</li> + +<li> +<p>D-Link DFE-530TX+</p> +</li> + +<li> +<p>D-Link DFE-538TX</p> +</li> + +<li> +<p>D-Link DFE-690TXD</p> +</li> + +<li> +<p>Edimax EP-4103DL CardBus</p> +</li> + +<li> +<p>Encore ENL832-TX 10/100 M PCI</p> +</li> + +<li> +<p>Farallon NetLINE 10/100 PCI</p> +</li> + +<li> +<p>Genius GF100TXR</p> +</li> + +<li> +<p>GigaFast Ethernet EE100-AXP</p> +</li> + +<li> +<p>KTX-9130TX 10/100 Fast Ethernet</p> +</li> + +<li> +<p>LevelOne FPC-0106TX</p> +</li> + +<li> +<p>Longshine LCS-8038TX-R</p> +</li> + +<li> +<p>NDC Communications NE100TX-E</p> +</li> + +<li> +<p>Netronix Inc. EA-1210 NetEther 10/100</p> +</li> + +<li> +<p>Nortel Networks 10/100BaseTX</p> +</li> + +<li> +<p>OvisLink LEF-8129TX</p> +</li> + +<li> +<p>OvisLink LEF-8139TX</p> +</li> + +<li> +<p>Peppercon AG ROL-F</p> +</li> + +<li> +<p>Planex FNW-3800-TX</p> +</li> + +<li> +<p>SMC EZ Card 10/100 PCI 1211-TX</p> +</li> + +<li> +<p>SOHO (PRAGMATIC) UE-1211C</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sf</span>(4)</span></a> driver +include:</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a> driver +supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and +embedded controllers, as well as Fast Ethernet adapters based on the National +Semiconductor DP83815 (MacPhyter) chip. Supported adapters include:</p> + +<ul> +<li> +<p>@Nifty FNECHARD IFC USUP-TX</p> +</li> + +<li> +<p>MELCO LGY-PCI-TXC</p> +</li> + +<li> +<p>Netgear FA311-TX (DP83815)</p> +</li> + +<li> +<p>Netgear FA312-TX (DP83815)</p> +</li> + +<li> +<p>SiS 630, 635, and 735 motherboard chipsets</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>3Com 3C940 single port, 1000baseT adapter</p> +</li> + +<li> +<p>3Com 3C2000-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Belkin F5D5005 single port, 1000baseT adapter</p> +</li> + +<li> +<p>D-Link DGE-530T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Linksys EG1032 single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9521 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9821 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9822 SK-NET GE-T dual port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9841 SK-NET GE-LX single port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9842 SK-NET GE-LX dual port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9843 SK-NET GE-SX single port, multimode fiber adapter</p> +</li> + +<li> +<p>SK-9844 SK-NET GE-SX dual port, multimode fiber adapter</p> +</li> + +<li> +<p>SMC 9452TX single port, 1000baseT adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ste</span>(4)</span></a> driver +supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded +controllers including:</p> + +<ul> +<li> +<p>D-Link DFE-530TXS</p> +</li> + +<li> +<p>D-Link DFE-550TX</p> +</li> + +<li> +<p>D-Link DFE-580TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver supports +Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large +number of Compaq PCI Ethernet adapters. Also supported are:</p> + +<ul> +<li> +<p>Olicom OC-2135/2138 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Olicom OC-2325/OC-2326 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Racore 8148 10baseT/100baseTX/100baseFX adapter</p> +</li> + +<li> +<p>Racore 8165 10/100baseTX adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver also +supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq +Deskpro desktop machines including:</p> + +<ul> +<li> +<p>Compaq Netelligent 10</p> +</li> + +<li> +<p>Compaq Netelligent 10 T PCI UTP/Coax</p> +</li> + +<li> +<p>Compaq Netelligent 10/100</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Dual-Port</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Proliant</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX Embedded UTP</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX UTP</p> +</li> + +<li> +<p>Compaq NetFlex 3P</p> +</li> + +<li> +<p>Compaq NetFlex 3P Integrated</p> +</li> + +<li> +<p>Compaq NetFlex 3P w/BNC</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">txp</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>3Com 3CR990-TX-95</p> +</li> + +<li> +<p>3Com 3CR990-TX-97</p> +</li> + +<li> +<p>3Com 3cR990B-TXM</p> +</li> + +<li> +<p>3Com 3CR990SVR95</p> +</li> + +<li> +<p>3Com 3CR990SVR97</p> +</li> + +<li> +<p>3Com 3cR990B-SRV</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vr</span>(4)</span></a> driver supports +VIA Technologies Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters +including:</p> + +<ul> +<li> +<p>AOpen/Acer ALN-320</p> +</li> + +<li> +<p>D-Link DFE530-TX</p> +</li> + +<li> +<p>Hawking Technologies PN102TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wb</span>(4)</span></a> driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:</p> + +<ul> +<li> +<p>Trendware TE100-PCIE</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver supports +the following hardware:</p> + +<ul> +<li> +<p>3Com 3c900-TPO</p> +</li> + +<li> +<p>3Com 3c900-COMBO</p> +</li> + +<li> +<p>3Com 3c905-TX</p> +</li> + +<li> +<p>3Com 3c905-T4</p> +</li> + +<li> +<p>3Com 3c900B-TPO</p> +</li> + +<li> +<p>3Com 3c900B-TPC</p> +</li> + +<li> +<p>3Com 3c900B-FL</p> +</li> + +<li> +<p>3Com 3c900B-COMBO</p> +</li> + +<li> +<p>3Com 3c905B-T4</p> +</li> + +<li> +<p>3Com 3c905B-TX</p> +</li> + +<li> +<p>3Com 3c905B-FX</p> +</li> + +<li> +<p>3Com 3c905B-COMBO</p> +</li> + +<li> +<p>3Com 3c905C-TX</p> +</li> + +<li> +<p>3Com 3c980, 3c980B, and 3c980C server adapters</p> +</li> + +<li> +<p>3Com 3cSOHO100-TX OfficeConnect adapters</p> +</li> + +<li> +<p>3Com 3c450 HomeConnect adapters</p> +</li> + +<li> +<p>3Com 3c555, 3c556 and 3c556B mini-PCI adapters</p> +</li> + +<li> +<p>3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, +3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters</p> +</li> + +<li> +<p>3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded +adapters</p> +</li> +</ul> + +<p>Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a +built-in proprietary modem. Neither the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver nor any +other driver supports this modem.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="TOKENRING" name="TOKENRING">3.3 Token Ring Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FDDI" name="FDDI">3.4 FDDI Interfaces</a></h3> + +<p>DEC DEFPA PCI (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fpa</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ATM" name="ATM">3.5 ATM Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="WLAN" name="WLAN">3.6 Wireless Network Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC-NETWORK" name="MISC-NETWORK">3.7 Miscellaneous +Networks</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ISDN" name="ISDN">3.8 ISDN Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SERIAL" name="SERIAL">3.9 Serial Interfaces</a></h3> + +<p>“PC standard” 8250, 16450, and 16550-based serial ports (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uart&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uart</span>(4)</span></a> driver +supports the following classes of UARTs:</p> + +<ul> +<li> +<p>NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 +UARTs</p> +</li> + +<li> +<p>SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.</p> +</li> + +<li> +<p>Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.</p> +</li> +</ul> + +<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&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rp</span>(4)</span></a> driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SOUND" name="SOUND">3.10 Sound Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_maestro&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_maestro</span>(4)</span></a> +driver supports the following PCI sound cards:</p> + +<ul> +<li> +<p>ESS Technology Maestro-1</p> +</li> + +<li> +<p>ESS Technology Maestro-2</p> +</li> + +<li> +<p>ESS Technology Maestro-2E</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_maestro3&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_maestro3</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>ESS Technology Allegro-1</p> +</li> + +<li> +<p>ESS Technology Maestro3</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_sbc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_sbc</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Avance Asound 110</p> +</li> + +<li> +<p>Avance Logic ALS100+</p> +</li> + +<li> +<p>Avance Logic ALS120</p> +</li> + +<li> +<p>Creative SB16</p> +</li> + +<li> +<p>Creative SB32</p> +</li> + +<li> +<p>Creative AWE64</p> +</li> + +<li> +<p>Creative AWE64 Gold</p> +</li> + +<li> +<p>Creative ViBRA16C</p> +</li> + +<li> +<p>Creative ViBRA16X</p> +</li> + +<li> +<p>ESS ES1681</p> +</li> + +<li> +<p>ESS ES1688</p> +</li> + +<li> +<p>ESS ES1868</p> +</li> + +<li> +<p>ESS ES1869</p> +</li> + +<li> +<p>ESS ES1878</p> +</li> + +<li> +<p>ESS ES1879</p> +</li> + +<li> +<p>ESS ES1888</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CAMERA" name="CAMERA">3.11 Camera and Video Capture +Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USB" name="USB">3.12 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> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> USB Bluetooth adapters can be found in <a href="#BLUETOOTH">Bluetooth</a> +section.</p> +</blockquote> +</div> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a> driver +supports all OHCI v1.0 compliant controllers including:</p> + +<ul> +<li> +<p>AcerLabs M5237 (Aladdin-V)</p> +</li> + +<li> +<p>AMD-756</p> +</li> + +<li> +<p>OPTi 82C861 (FireLink)</p> +</li> + +<li> +<p>NEC uPD 9210</p> +</li> + +<li> +<p>CMD Tech 670 (USB0670)</p> +</li> + +<li> +<p>CMD Tech 673 (USB0673)</p> +</li> + +<li> +<p>NVIDIA nForce3</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO USB)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a> driver +supports all UHCI v1.1 compliant controllers including:</p> + +<ul> +<li> +<p>Intel 82371AB/EB (PIIX4)</p> +</li> + +<li> +<p>Intel 82371SB (PIIX3)</p> +</li> + +<li> +<p>VIA 83C572</p> +</li> +</ul> + +<p>Hubs</p> + +<p>Keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> + +<p>Mice (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ulpt</span>(4)</span></a> driver +provides support for USB printers and parallel printer conversion cables, including the +following:</p> + +<ul> +<li> +<p>ATen parallel printer adapter</p> +</li> + +<li> +<p>Belkin F5U002 parallel printer adapter</p> +</li> + +<li> +<p>Canon BJ F850, S600</p> +</li> + +<li> +<p>Canon LBP-1310, 350</p> +</li> + +<li> +<p>Entrega USB-to-parallel printer adapter</p> +</li> + +<li> +<p>Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)</p> +</li> + +<li> +<p>Oki Data MICROLINE ML660PS</p> +</li> + +<li> +<p>Seiko Epson PM-900C, 880C, 820C, 730C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umct&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umct</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U109</p> +</li> + +<li> +<p>Belkin F5U409</p> +</li> + +<li> +<p>D-Link DU-H3SP USB BAY Hub</p> +</li> + +<li> +<p>Magic Control Technology USB-232</p> +</li> + +<li> +<p>Sitecom USB-232</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umass</span>(4)</span></a> driver +supports USB Mass Storage devices, including:</p> + +<ul> +<li> +<p>ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M</p> +</li> + +<li> +<p>Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20</p> +</li> + +<li> +<p>FujiFilm Zip USB Drive ZDR100 USB A</p> +</li> + +<li> +<p>GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M</p> +</li> + +<li> +<p>IBM 32MB USB Memory Key (P/N 22P5296)</p> +</li> + +<li> +<p>IBM 256MB USB Drive (MSYSTEM DiskOnKey2)</p> +</li> + +<li> +<p>IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)</p> +</li> + +<li> +<p>I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)</p> +</li> + +<li> +<p>I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)</p> +</li> + +<li> +<p>I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI</p> +</li> + +<li> +<p>Iomega USB Zip 100/250 drive</p> +</li> + +<li> +<p>Iomega Zip750 USB2.0 drive</p> +</li> + +<li> +<p>Keian USB1.1/2.0 3.5-inch HDD Case KU350A</p> +</li> + +<li> +<p>Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0</p> +</li> + +<li> +<p>LaCie P3 HardDrive USB 200GB</p> +</li> + +<li> +<p>Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive</p> +</li> + +<li> +<p>Logitec Mobile USB Memory LMC-256UD</p> +</li> + +<li> +<p>Logitec USB1.1/2.0 HDD Unit SHD-E60U2</p> +</li> + +<li> +<p>Logitec USB Double-Speed Floppy Drive LFD-31U2</p> +</li> + +<li> +<p>Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)</p> +</li> + +<li> +<p>MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M</p> +</li> + +<li> +<p>MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm</p> +</li> + +<li> +<p>MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2</p> +</li> + +<li> +<p>MELCO USB2.0 MO Drive MO-CH640U2</p> +</li> + +<li> +<p>Matshita CF-VFDU03 floppy drive</p> +</li> + +<li> +<p>Merlin SM300 MP3/WMA Player (256Mb)</p> +</li> + +<li> +<p>Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable</p> +</li> + +<li> +<p>Motorola E398 Mobile Phone (TransFlash memory card)</p> +</li> + +<li> +<p>NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U</p> +</li> + +<li> +<p>PNY Attache Flash Drive</p> +</li> + +<li> +<p>Panasonic ("Matshita FDD CF-VFDU03")</p> +</li> + +<li> +<p>Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW</p> +</li> + +<li> +<p>Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW)</p> +</li> + +<li> +<p>Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)</p> +</li> + +<li> +<p>Panasonic floppy drive</p> +</li> + +<li> +<p>Qware BeatZkey! Pro</p> +</li> + +<li> +<p>RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B</p> +</li> + +<li> +<p>SanDisk SDDR-31 (Compact Flash)</p> +</li> + +<li> +<p>SanDisk SDDR-75 (only Compact Flash port works)</p> +</li> + +<li> +<p>Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick)</p> +</li> + +<li> +<p>Sony Portable CD-R/RW Drive CRX10U (CDROM only)</p> +</li> + +<li> +<p>TEAC Portable USB CD-ROM Unit CD-110PU/210PU</p> +</li> + +<li> +<p>Time DPA20B MP3 Player (1Gb)</p> +</li> + +<li> +<p>Trek Thumbdrive 8MB</p> +</li> + +<li> +<p>VAIO floppy drive (includes Y-E Data Flashbuster-U)</p> +</li> + +<li> +<p>Y-E Data floppy drive (720/1.44/2.88Mb)</p> +</li> +</ul> + +<p>Among the supported digital cameras are:</p> + +<ul> +<li> +<p>Asahi Optical (PENTAX) Optio 230 & 330</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.13 IEEE 1394 (Firewire) +Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.14 Bluetooth Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CRYPTO-ACCEL" name="CRYPTO-ACCEL">3.15 Cryptographic +Accelerators</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC" name="MISC">3.16 Miscellaneous</a></h3> + +<p>Floppy drives (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fdc&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>USB keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<br /> +<br /> +<p>Pointing devices including:</p> + +<ul> +<li> +<p>PS/2 mice and compatible devices, including many laptop pointing devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+6.1-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 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.org/</a>.</p> +</blockquote> +</div> + +<br /> +<br /> +<p>“PC standard” parallel ports (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppc</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/hardware-amd64.html b/en/releases/6.1R/hardware-amd64.html new file mode 100644 index 0000000000..0a874314f5 --- /dev/null +++ b/en/releases/6.1R/hardware-amd64.html @@ -0,0 +1,5877 @@ +<!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/amd64 6.1-RELEASE Hardware Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/amd64 6.1-RELEASE Hardware +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<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="#PROC">Supported Processors and Motherboards</a></dt> + +<dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + +<dd> +<dl> +<dt>3.1 <a href="#DISK">Disk Controllers</a></dt> + +<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt> + +<dt>3.3 <a href="#TOKENRING">Token Ring Interfaces</a></dt> + +<dt>3.4 <a href="#FDDI">FDDI Interfaces</a></dt> + +<dt>3.5 <a href="#ATM">ATM Interfaces</a></dt> + +<dt>3.6 <a href="#WLAN">Wireless Network Interfaces</a></dt> + +<dt>3.7 <a href="#MISC-NETWORK">Miscellaneous Networks</a></dt> + +<dt>3.8 <a href="#ISDN">ISDN Interfaces</a></dt> + +<dt>3.9 <a href="#SERIAL">Serial Interfaces</a></dt> + +<dt>3.10 <a href="#SOUND">Sound Devices</a></dt> + +<dt>3.11 <a href="#CAMERA">Camera and Video Capture Devices</a></dt> + +<dt>3.12 <a href="#USB">USB Devices</a></dt> + +<dt>3.13 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt> + +<dt>3.14 <a href="#BLUETOOTH">Bluetooth Devices</a></dt> + +<dt>3.15 <a href="#CRYPTO-ACCEL">Cryptographic Accelerators</a></dt> + +<dt>3.16 <a href="#MISC">Miscellaneous</a></dt> +</dl> +</dd> +</dl> +</div> + +<div class="SECT1"> +<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This document contains the hardware compatibility notes for FreeBSD 6.1-RELEASE on the +AMD64 hardware platform (also referred to as FreeBSD/amd64 6.1-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 AMD64 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.</p> +</blockquote> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="PROC" name="PROC">2 Supported Processors and +Motherboards</a></h2> + +<p>Since mid-2003 FreeBSD/amd64 has supported the AMD64 (“Hammer”) and Intel +EM64T architecture, and is now one of the Tier-1 platforms (fully supported +architecture), which are expected to be Production Quality with respects to all aspects +of the FreeBSD operating system, including installation and development environments.</p> + +<p>Note that there are two names for this architecture, AMD64 (AMD) and Intel EM64T +(Extended Memory 64-bit Technology). 64-bit mode of the two architectures are almost +compatible with each other, and FreeBSD/amd64 should support them both.</p> + +<p>As of this writing, the following processors are supported:</p> + +<ul> +<li> +<p>AMD Athlon64 (“Clawhammer”).</p> +</li> + +<li> +<p>AMD Opteron (“Sledgehammer”).</p> +</li> + +<li> +<p>Intel 64-bit Xeon (“Nacona”). This processor is fabricated on 90nm process +technology, and operates with 2.80 to 3.60 GHz (FSB 800MHz) and Intel E7520/E7525/E7320 +chipsets.</p> +</li> + +<li> +<p>Intel Pentium 4 Processor supporting Intel EM64T (“Prescott”). This is +fabricated on 90nm process technology, uses FC-LGA775 package, and operates with +3.20F/3.40F/3.60F GHz and Intel 925X Express chipsets. The corresponding S-Spec numbers +are SL7L9, SL7L8, SL7LA, SL7NZ, SL7PZ, and SL7PX. Note that processors marked as 5xx +numbers do not support EM64T.</p> +</li> +</ul> + +<p>Intel EM64T is an extended version of IA-32 (x86) and different from Intel IA-64 +(Itanium) architecture, which FreeBSD/ia64 supports. Some Intel's old documentation +refers to Intel EM64T as “64-bit extension technology” or +“IA-32e”.</p> + +<p>The largest tested memory configuration to date is 8GB. SMP support has been recently +completed and is reasonably robust.</p> + +<p>In many respects, FreeBSD/amd64 is similar to FreeBSD/i386, in terms of drivers +supported. There may be some issues with 64-bit cleanliness in some (particularly older) +drivers. Generally, drivers that already function correctly on other 64-bit platforms +should work.</p> + +<p>FreeBSD/amd64 is a very young platform on FreeBSD. While the core FreeBSD kernel and +base system components are generally fairly robust, there are likely to still be rough +edges, particularly with third party packages.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2> + +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.9.2.2 +2006/05/01 08:26:00 brueffer Exp $ + +<p>This section describes the devices currently known to be supported by with FreeBSD on +the AMD64 platform. Other configurations may also work, but simply have not been tested +yet. Feedback, updates, and corrections to this list are encouraged.</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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> The device lists in this document are being generated automatically from +FreeBSD manual pages. This means that some devices, which are supported by multiple +drivers, may appear multiple times.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DISK" name="DISK">3.1 Disk Controllers</a></h3> + +<p>IDE/ATA controllers (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> +driver)</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aac</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec AAC-364</p> +</li> + +<li> +<p>Adaptec SATA RAID 2410SA</p> +</li> + +<li> +<p>Adaptec SATA RAID 2810SA</p> +</li> + +<li> +<p>Adaptec SATA RAID 21610SA</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2120S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2130S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2200S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2130SLP</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2230SLP</p> +</li> + +<li> +<p>Adaptec SCSI RAID 5400S</p> +</li> + +<li> +<p>Dell CERC SATA RAID 2</p> +</li> + +<li> +<p>Dell PERC 2/Si</p> +</li> + +<li> +<p>Dell PERC 2/QC</p> +</li> + +<li> +<p>Dell PERC 3/Si</p> +</li> + +<li> +<p>Dell PERC 3/Di</p> +</li> + +<li> +<p>Dell PERC 320/DC</p> +</li> + +<li> +<p>HP NetRAID 4M</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=adv&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adv</span>(4)</span></a> driver +supports the following SCSI controllers:</p> + +<ul> +<li> +<p>AdvanSys ABP510/5150</p> +</li> + +<li> +<p>AdvanSys ABP5140</p> +</li> + +<li> +<p>AdvanSys ABP5142</p> +</li> + +<li> +<p>AdvanSys ABP902/3902</p> +</li> + +<li> +<p>AdvanSys ABP3905</p> +</li> + +<li> +<p>AdvanSys ABP915</p> +</li> + +<li> +<p>AdvanSys ABP920</p> +</li> + +<li> +<p>AdvanSys ABP3922</p> +</li> + +<li> +<p>AdvanSys ABP3925</p> +</li> + +<li> +<p>AdvanSys ABP930, ABP930U, ABP930UA</p> +</li> + +<li> +<p>AdvanSys ABP960, ABP960U</p> +</li> + +<li> +<p>AdvanSys ABP542</p> +</li> + +<li> +<p>AdvanSys ABP742</p> +</li> + +<li> +<p>AdvanSys ABP842</p> +</li> + +<li> +<p>AdvanSys ABP940</p> +</li> + +<li> +<p>AdvanSys ABP940UA/3940UA</p> +</li> + +<li> +<p>AdvanSys ABP940U</p> +</li> + +<li> +<p>AdvanSys ABP3960UA</p> +</li> + +<li> +<p>AdvanSys ABP970, ABP970U</p> +</li> + +<li> +<p>AdvanSys ABP752</p> +</li> + +<li> +<p>AdvanSys ABP852</p> +</li> + +<li> +<p>AdvanSys ABP950</p> +</li> + +<li> +<p>AdvanSys ABP980, ABP980U</p> +</li> + +<li> +<p>AdvanSys ABP980UA/3980UA</p> +</li> + +<li> +<p>MELCO IFC-USP (PC-98)</p> +</li> + +<li> +<p>RATOC REX-PCI30 (PC-98)</p> +</li> + +<li> +<p>@Nifty FNECHARD IFC-USUP-TX (PC-98)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=adw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adw</span>(4)</span></a> driver +supports SCSI controllers including:</p> + +<ul> +<li> +<p>AdvanSys ABP940UW/ABP3940UW</p> +</li> + +<li> +<p>AdvanSys ABP950UW</p> +</li> + +<li> +<p>AdvanSys ABP970UW</p> +</li> + +<li> +<p>AdvanSys ABP3940U2W</p> +</li> + +<li> +<p>AdvanSys ABP3950U2W</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a> driver +supports the following SCSI host adapter chips and SCSI controller cards:</p> + +<ul> +<li> +<p>Adaptec AIC7770 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7850 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7860 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7870 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7880 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7890 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7891 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7892 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7895 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7896 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7897 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7899 host adapter chip</p> +</li> + +<li> +<p>Adaptec 274X(W)</p> +</li> + +<li> +<p>Adaptec 274X(T)</p> +</li> + +<li> +<p>Adaptec 284X</p> +</li> + +<li> +<p>Adaptec 2910</p> +</li> + +<li> +<p>Adaptec 2915</p> +</li> + +<li> +<p>Adaptec 2920</p> +</li> + +<li> +<p>Adaptec 2930C</p> +</li> + +<li> +<p>Adaptec 2930U2</p> +</li> + +<li> +<p>Adaptec 2940</p> +</li> + +<li> +<p>Adaptec 2940J</p> +</li> + +<li> +<p>Adaptec 2940N</p> +</li> + +<li> +<p>Adaptec 2940U</p> +</li> + +<li> +<p>Adaptec 2940AU</p> +</li> + +<li> +<p>Adaptec 2940UW</p> +</li> + +<li> +<p>Adaptec 2940UW Dual</p> +</li> + +<li> +<p>Adaptec 2940UW Pro</p> +</li> + +<li> +<p>Adaptec 2940U2W</p> +</li> + +<li> +<p>Adaptec 2940U2B</p> +</li> + +<li> +<p>Adaptec 2950U2W</p> +</li> + +<li> +<p>Adaptec 2950U2B</p> +</li> + +<li> +<p>Adaptec 19160B</p> +</li> + +<li> +<p>Adaptec 29160B</p> +</li> + +<li> +<p>Adaptec 29160N</p> +</li> + +<li> +<p>Adaptec 3940</p> +</li> + +<li> +<p>Adaptec 3940U</p> +</li> + +<li> +<p>Adaptec 3940AU</p> +</li> + +<li> +<p>Adaptec 3940UW</p> +</li> + +<li> +<p>Adaptec 3940AUW</p> +</li> + +<li> +<p>Adaptec 3940U2W</p> +</li> + +<li> +<p>Adaptec 3950U2</p> +</li> + +<li> +<p>Adaptec 3960</p> +</li> + +<li> +<p>Adaptec 39160</p> +</li> + +<li> +<p>Adaptec 3985</p> +</li> + +<li> +<p>Adaptec 4944UW</p> +</li> + +<li> +<p>NEC PC-9821Xt13 (PC-98)</p> +</li> + +<li> +<p>NEC RvII26 (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B02L/B09 (PC-98)</p> +</li> + +<li> +<p>NEC SV-98/2-B03 (PC-98)</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahd</span>(4)</span></a> driver +supports the following:</p> + +<ul> +<li> +<p>Adaptec AIC7901 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7901A host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7902 host adapter chip</p> +</li> + +<li> +<p>Adaptec 29320 host adapter</p> +</li> + +<li> +<p>Adaptec 39320 host adapter</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>The adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aic&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aic</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec AHA-1505 (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1510A, AHA-1510B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1520A, AHA-1520B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1522A, AHA-1522B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1535 (ISA)</p> +</li> + +<li> +<p>Creative Labs SoundBlaster SCSI host adapter (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1460, AHA-1460B, AHA-1460C, AHA-1460D (PC Card)</p> +</li> + +<li> +<p>Adaptec AHA-1030B, AHA-1030P (PC98)</p> +</li> + +<li> +<p>NEC PC-9801-100 (PC98)</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amd</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MELCO IFC-DP (PC-98)</p> +</li> + +<li> +<p>Tekram DC390</p> +</li> + +<li> +<p>Tekram DC390T</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MegaRAID SCSI 320-1E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-8X</p> +</li> + +<li> +<p>MegaRAID SATA 150-4</p> +</li> + +<li> +<p>MegaRAID SATA 150-6</p> +</li> + +<li> +<p>MegaRAID i4 133 RAID</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0</p> +</li> + +<li> +<p>MegaRAID SCSI 320-1</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4</p> +</li> + +<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 Elite 1650 (Series 4xx)</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 3/QC</p> +</li> + +<li> +<p>Dell PERC 4/DC</p> +</li> + +<li> +<p>Dell PERC 4/IM</p> +</li> + +<li> +<p>Dell PERC 4/SC</p> +</li> + +<li> +<p>Dell PERC 4/Di</p> +</li> + +<li> +<p>Dell PERC 4e/DC</p> +</li> + +<li> +<p>Dell PERC 4e/Di</p> +</li> + +<li> +<p>Dell PERC 4e/Si</p> +</li> + +<li> +<p>Dell PERC 4ei</p> +</li> + +<li> +<p>HP NetRAID-1/Si</p> +</li> + +<li> +<p>HP NetRAID-3/Si (D4943A)</p> +</li> + +<li> +<p>HP Embedded NetRAID</p> +</li> + +<li> +<p>Intel RAID Controller SRCS16</p> +</li> + +<li> +<p>Intel RAID Controller SRCU42X</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arcmsr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arcmsr</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>ARC-1110</p> +</li> + +<li> +<p>ARC-1120</p> +</li> + +<li> +<p>ARC-1130</p> +</li> + +<li> +<p>ARC-1160</p> +</li> + +<li> +<p>ARC-1130-ML</p> +</li> + +<li> +<p>ARC-1160-ML</p> +</li> + +<li> +<p>ARC-1210</p> +</li> + +<li> +<p>ARC-1220</p> +</li> + +<li> +<p>ARC-1230</p> +</li> + +<li> +<p>ARC-1260</p> +</li> + +<li> +<p>ARC-1230-ML</p> +</li> + +<li> +<p>ARC-1260-ML</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a> driver supports +the following BusLogic MultiMaster “W”, “C”, “S”, and +“A” series and compatible SCSI host adapters:</p> + +<ul> +<li> +<p>BusLogic BT-445C</p> +</li> + +<li> +<p>BusLogic BT-445S</p> +</li> + +<li> +<p>BusLogic BT-540CF</p> +</li> + +<li> +<p>BusLogic BT-542B</p> +</li> + +<li> +<p>BusLogic BT-542B</p> +</li> + +<li> +<p>BusLogic BT-542D</p> +</li> + +<li> +<p>BusLogic BT-545C</p> +</li> + +<li> +<p>BusLogic BT-545S</p> +</li> + +<li> +<p>BusLogic/BusTek BT-640</p> +</li> + +<li> +<p>BusLogic BT-742A</p> +</li> + +<li> +<p>BusLogic BT-742A</p> +</li> + +<li> +<p>BusLogic BT-747C</p> +</li> + +<li> +<p>BusLogic BT-747D</p> +</li> + +<li> +<p>BusLogic BT-747S</p> +</li> + +<li> +<p>BusLogic BT-757C</p> +</li> + +<li> +<p>BusLogic BT-757CD</p> +</li> + +<li> +<p>BusLogic BT-757D</p> +</li> + +<li> +<p>BusLogic BT-757S</p> +</li> + +<li> +<p>BusLogic BT-946C</p> +</li> + +<li> +<p>BusLogic BT-948</p> +</li> + +<li> +<p>BusLogic BT-956C</p> +</li> + +<li> +<p>BusLogic BT-956CD</p> +</li> + +<li> +<p>BusLogic BT-958</p> +</li> + +<li> +<p>BusLogic BT-958D</p> +</li> + +<li> +<p>Storage Dimensions SDC3211B / SDC3211F</p> +</li> +</ul> + +<p>AMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also +supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a> driver.</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ciss&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ciss</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Compaq Smart Array 5300</p> +</li> + +<li> +<p>Compaq Smart Array 532</p> +</li> + +<li> +<p>Compaq Smart Array 5i</p> +</li> + +<li> +<p>HP Smart Array 5312</p> +</li> + +<li> +<p>HP Smart Array 6i</p> +</li> + +<li> +<p>HP Smart Array 641</p> +</li> + +<li> +<p>HP Smart Array 642</p> +</li> + +<li> +<p>HP Smart Array 6400</p> +</li> + +<li> +<p>HP Smart Array 6400 EM</p> +</li> + +<li> +<p>HP Smart Array E400</p> +</li> + +<li> +<p>HP Smart Array P600</p> +</li> + +<li> +<p>HP Smart Array P800</p> +</li> + +<li> +<p>HP Modular Smart Array 20 (MSA20)</p> +</li> + +<li> +<p>HP Modular Smart Array 500 (MSA500)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dpt</span>(4)</span></a> driver +provides support for the following RAID adapters:</p> + +<ul> +<li> +<p>DPT Smart Cache Plus</p> +</li> + +<li> +<p>Smart Cache II (PM2?2?, PM2022 [EISA], PM2024/PM2124 [PCI]) (Gen2)</p> +</li> + +<li> +<p>Smart RAID II (PM3?2?, PM3021, PM3222)</p> +</li> + +<li> +<p>Smart Cache III (PM2?3?)</p> +</li> + +<li> +<p>Smart RAID III (PM3?3?, PM3332 [EISA], PM3334UW [PCI]) (Gen3)</p> +</li> + +<li> +<p>Smart Cache IV (PM2?4?, PM2042 [EISA], PM2044/PM2144 [PCI]) (Gen4)</p> +</li> + +<li> +<p>Smart RAID IV</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hptmv&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hptmv</span>(4)</span></a> driver +supports the following ATA RAID controllers:</p> + +<ul> +<li> +<p>HighPoint's RocketRAID 182x series</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">iir</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel RAID Controller SRCMR</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-l (SRCU31a)</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-1L (SRCU31La)</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-2 (SRCU32)</p> +</li> + +<li> +<p>All past and future releases of Intel and ICP RAID Controllers.</p> +</li> +</ul> + +<ul> +<li> +<p>Intel RAID Controller SRCU21 (discontinued)</p> +</li> + +<li> +<p>Intel RAID Controller SRCU31 (older revision, not compatible)</p> +</li> + +<li> +<p>Intel RAID Controller SRCU31L (older revision, not compatible)</p> +</li> +</ul> + +<p>The SRCU31 and SRCU31L can be updated via a firmware update available from Intel.</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ips&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ips</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>IBM ServeRAID 3H</p> +</li> + +<li> +<p>ServeRAID 4L/4M/4H</p> +</li> + +<li> +<p>ServeRAID Series 5</p> +</li> + +<li> +<p>ServeRAID 6i/6M</p> +</li> +</ul> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>ISP1000</p> +</li> + +<li> +<p>ISP1020</p> +</li> + +<li> +<p>ISP1040</p> +</li> + +<li> +<p>Qlogic 1240</p> +</li> + +<li> +<p>Qlogic 1020</p> +</li> + +<li> +<p>Qlogic 1040</p> +</li> + +<li> +<p>Qlogic 1080</p> +</li> + +<li> +<p>Qlogic 1280</p> +</li> + +<li> +<p>Qlogic 12160</p> +</li> + +<li> +<p>Qlogic 210X</p> +</li> + +<li> +<p>Qlogic 220X</p> +</li> + +<li> +<p>Qlogic 2300</p> +</li> + +<li> +<p>Qlogic 2312</p> +</li> + +<li> +<p>Qlogic 234X</p> +</li> + +<li> +<p>Qlogic 2322</p> +</li> + +<li> +<p>Qlogic 200</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver +supports the following hardware:</p> + +<ul> +<li> +<p>LSI MegaRAID SAS 8408E</p> +</li> + +<li> +<p>LSI MegaRAID SAS 8480E</p> +</li> + +<li> +<p>Dell PERC5/i</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mlx</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Mylex DAC960P</p> +</li> + +<li> +<p>Mylex DAC960PD / DEC KZPSC (Fast Wide)</p> +</li> + +<li> +<p>Mylex DAC960PDU</p> +</li> + +<li> +<p>Mylex DAC960PL</p> +</li> + +<li> +<p>Mylex DAC960PJ</p> +</li> + +<li> +<p>Mylex DAC960PG</p> +</li> + +<li> +<p>Mylex DAC960PU / DEC PZPAC (Ultra Wide)</p> +</li> + +<li> +<p>Mylex AcceleRAID 150 (DAC960PRL)</p> +</li> + +<li> +<p>Mylex AcceleRAID 250 (DAC960PTL1)</p> +</li> + +<li> +<p>Mylex eXtremeRAID 1100 (DAC1164P)</p> +</li> + +<li> +<p>RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA +(3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)</p> +</li> +</ul> + +<p>All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is +always advisable to upgrade to the most recent firmware available for the controller. +Compatible Mylex controllers not listed should work, but have not been verified.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> Booting from these controllers is supported. EISA adapters are not +supported.</p> +</blockquote> +</div> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mly</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Mylex AcceleRAID 160</p> +</li> + +<li> +<p>Mylex AcceleRAID 170</p> +</li> + +<li> +<p>Mylex AcceleRAID 352</p> +</li> + +<li> +<p>Mylex eXtremeRAID 2000</p> +</li> + +<li> +<p>Mylex eXtremeRAID 3000</p> +</li> +</ul> + +<p>Compatible Mylex controllers not listed should work, but have not been verified.</p> + +<p>The following controllers are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>LSI Logic 53c1030 (Dual Ultra320 SCSI)</p> +</li> + +<li> +<p>LSI Logic FC909 (1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC909A (Dual 1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC919 (2Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC929, LSI Logic FC929X (Dual 2Gb/s Fibre Channel)</p> +</li> +</ul> + +<p>The SCSI controller chips supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver +can be found onboard on many systems including:</p> + +<ul> +<li> +<p>Dell PowerEdge 1750</p> +</li> + +<li> +<p>IBM eServer xSeries 335</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> driver +provides support for the following NCR/Symbios SCSI controller chips:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C820</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C875J</p> +</li> + +<li> +<p>53C885</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The following add-on boards are known to be supported:</p> + +<ul> +<li> +<p>I-O DATA SC-98/PCI (PC-98)</p> +</li> + +<li> +<p>I-O DATA SC-PCI (PC-98)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> driver +supports the following hardware:</p> + +<ul> +<li> +<p>HighPoint RocketRAID 2320</p> +</li> + +<li> +<p>HighPoint RocketRAID 2322</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> driver +provides support for the following Symbios/LSI Logic PCI SCSI controllers:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C825</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C876</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C897</p> +</li> + +<li> +<p>53C1000</p> +</li> + +<li> +<p>53C1000R</p> +</li> + +<li> +<p>53C1010-33</p> +</li> + +<li> +<p>53C1010-66</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The SCSI controllers supported by <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> can be +either embedded on a motherboard, or on one of the following add-on boards:</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>I-O DATA SC-UPCI (PC-98)</p> +</li> + +<li> +<p>Logitec LHA-521UA (PC-98)</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> + +<p>SCSI controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=trm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">trm</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Tekram DC-315 PCI Ultra SCSI adapter without BIOS and internal SCSI connector</p> +</li> + +<li> +<p>Tekram DC-315U PCI Ultra SCSI adapter without BIOS</p> +</li> + +<li> +<p>Tekram DC-395F PCI Ultra-Wide SCSI adapter with flash BIOS and 68-pin external SCSI +connector</p> +</li> + +<li> +<p>Tekram DC-395U PCI Ultra SCSI adapter with flash BIOS</p> +</li> + +<li> +<p>Tekram DC-395UW PCI Ultra-Wide SCSI adapter with flash BIOS</p> +</li> + +<li> +<p>Tekram DC-395U2W PCI Ultra2-Wide SCSI adapter with flash BIOS</p> +</li> +</ul> + +<p>For the Tekram DC-310/U and DC-390F/U/UW/U2B/U2W/U3W PCI SCSI host adapters, use the +sym(4) driver.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +supports the following SATA RAID controllers:</p> + +<ul> +<li> +<p>AMCC's 3ware 9500S-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-8</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-8MI</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-12</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-12MI</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-8LP</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-12</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-12MI</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-16ML</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-8LP</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-12</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-12MI</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-16ML</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twe</span>(4)</span></a> driver +supports the following PATA/SATA RAID controllers:</p> + +<ul> +<li> +<p>AMCC's 3ware 5000 series</p> +</li> + +<li> +<p>AMCC's 3ware 6000 series</p> +</li> + +<li> +<p>AMCC's 3ware 7000-2</p> +</li> + +<li> +<p>AMCC's 3ware 7006-2</p> +</li> + +<li> +<p>AMCC's 3ware 7500-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 7500-8</p> +</li> + +<li> +<p>AMCC's 3ware 7500-12</p> +</li> + +<li> +<p>AMCC's 3ware 7506-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 7506-8</p> +</li> + +<li> +<p>AMCC's 3ware 7506-12</p> +</li> + +<li> +<p>AMCC's 3ware 8006-2LP</p> +</li> + +<li> +<p>AMCC's 3ware 8500-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 8500-8</p> +</li> + +<li> +<p>AMCC's 3ware 8500-12</p> +</li> + +<li> +<p>AMCC's 3ware 8506-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 8506-8</p> +</li> + +<li> +<p>AMCC's 3ware 8506-8MI</p> +</li> + +<li> +<p>AMCC's 3ware 8506-12</p> +</li> + +<li> +<p>AMCC's 3ware 8506-12MI</p> +</li> +</ul> + +<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&sektion=4&manpath=FreeBSD+6.1-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&sektion=1&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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aue</span>(4)</span></a> driver +include:</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-T, FEther USB-TX, FEther USB-TXS</p> +</li> + +<li> +<p>D-Link DSB-650, DSB-650TX, DSB-650TX-PNA</p> +</li> + +<li> +<p>Elecom LD-USBL/TX</p> +</li> + +<li> +<p>Elsa Microlink USB2Ethernet</p> +</li> + +<li> +<p>HP hn210e</p> +</li> + +<li> +<p>I-O Data USB ETTX</p> +</li> + +<li> +<p>Kingston KNU101TX</p> +</li> + +<li> +<p>LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, +USB100TX, USB100H1</p> +</li> + +<li> +<p>MELCO LUA-TX, LUA2-TX</p> +</li> + +<li> +<p>Planex UE-200TX</p> +</li> + +<li> +<p>Sandberg USB to Network Link (model number 133-06)</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">axe</span>(4)</span></a> driver +supports ASIX Electronics AX88172 based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Buffalo (Melco Inc.) LUA-U2-KTX</p> +</li> + +<li> +<p>D-Link DUBE100</p> +</li> + +<li> +<p>LinkSys USB200M</p> +</li> + +<li> +<p>Netgear FA120</p> +</li> + +<li> +<p>Sitecom LN-029</p> +</li> + +<li> +<p>System TALKS Inc. SGC-X2UL</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bce&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bce</span>(4)</span></a> driver +provides support for various NICs based on the Broadcom NetXtreme II family of Gigabit +Ethernet controllers, including the following:</p> + +<ul> +<li> +<p>HP NC370T Multifunction Gigabit Server Adapter</p> +</li> + +<li> +<p>HP NC370i Multifunction Gigabit Server Adapter</p> +</li> +</ul> + +<p>Broadcom BCM4401 based Fast Ethernet adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +provides support for various NICs based on the Broadcom BCM570x family of Gigabit +Ethernet controller chips, including the following:</p> + +<ul> +<li> +<p>3Com 3c996-T (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Netgear GA302T (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D21 (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D41 (1000baseSX)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cue</span>(4)</span></a> driver +supports CATC USB-EL1210A based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Belkin F5U011/F5U111</p> +</li> + +<li> +<p>CATC Netmate</p> +</li> + +<li> +<p>CATC Netmate II</p> +</li> + +<li> +<p>SmartBridges SmartLink</p> +</li> +</ul> + +<p>Crystal Semiconductor CS89x0-based NICs (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cs&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">cs</span>(4)</span></a> driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver provides +support for the following chipsets:</p> + +<ul> +<li> +<p>DEC/Intel 21143</p> +</li> + +<li> +<p>ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II</p> +</li> + +<li> +<p>ASIX Electronics AX88140A and AX88141</p> +</li> + +<li> +<p>Conexant LANfinity RS7112 (miniPCI)</p> +</li> + +<li> +<p>Davicom DM9009, DM9100, DM9102 and DM9102A</p> +</li> + +<li> +<p>Lite-On 82c168 and 82c169 PNIC</p> +</li> + +<li> +<p>Lite-On/Macronix 82c115 PNIC II</p> +</li> + +<li> +<p>Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732</p> +</li> + +<li> +<p>Xircom X3201 (cardbus only)</p> +</li> +</ul> + +<p>The following NICs are known to work with the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver at this +time:</p> + +<ul> +<li> +<p>3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Abocom FE2500</p> +</li> + +<li> +<p>Accton EN1217 (98715A)</p> +</li> + +<li> +<p>Accton EN2242 MiniPCI</p> +</li> + +<li> +<p>Adico AE310TX (98715A)</p> +</li> + +<li> +<p>Alfa Inc GFC2204 (ASIX AX88140A)</p> +</li> + +<li> +<p>Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, +non-MII)</p> +</li> + +<li> +<p>Built in DE500-BA on DEC Alpha workstations (21143, non-MII)</p> +</li> + +<li> +<p>Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, +MII)</p> +</li> + +<li> +<p>Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)</p> +</li> + +<li> +<p>CNet Pro110B (ASIX AX88140A)</p> +</li> + +<li> +<p>CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)</p> +</li> + +<li> +<p>Compex RL100-TX (98713 or 98713A)</p> +</li> + +<li> +<p>D-Link DFE-570TX (21143, MII, quad port)</p> +</li> + +<li> +<p>Digital DE500-BA 10/100 (21143, non-MII)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CBL/TXA (ADMtek AN985)</p> +</li> + +<li> +<p>Hawking CB102 CardBus</p> +</li> + +<li> +<p>IBM EtherJet Cardbus Adapter</p> +</li> + +<li> +<p>Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)</p> +</li> + +<li> +<p>Jaton XpressNet (Davicom DM9102)</p> +</li> + +<li> +<p>Kingston KNE100TX (21143, MII)</p> +</li> + +<li> +<p>Kingston KNE110TX (PNIC 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX v2.0 (PNIC II 82c115)</p> +</li> + +<li> +<p>LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Matrox FastNIC 10/100 (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>Melco LGY-PCI-TXL</p> +</li> + +<li> +<p>Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)</p> +</li> + +<li> +<p>Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A (98713A)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A Rev B4 (98715AEC-C)</p> +</li> + +<li> +<p>NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)</p> +</li> + +<li> +<p>Netgear FA511</p> +</li> + +<li> +<p>PlaneX FNW-3602-T (ADMtek AN985)</p> +</li> + +<li> +<p>SMC EZ Card 10/100 1233A-TX (ADMtek AN985)</p> +</li> + +<li> +<p>SVEC PN102-TX (98713)</p> +</li> + +<li> +<p>Xircom Cardbus Realport</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet 10/100</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet II 10/100</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec ANA-6944/TX</p> +</li> + +<li> +<p>Cogent EM100FX and EM440TX</p> +</li> + +<li> +<p>Corega FastEther PCI-TX</p> +</li> + +<li> +<p>D-Link DFE-500TX</p> +</li> + +<li> +<p>DEC DE435, DEC DE450, and DEC DE500</p> +</li> + +<li> +<p>ELECOM LD-PCI2T, LD-PCITS</p> +</li> + +<li> +<p>I-O DATA LA2/T-PCI</p> +</li> + +<li> +<p>SMC Etherpower 8432, 9332 and 9334</p> +</li> + +<li> +<p>ZNYX ZX3xx</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, +82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 controller +chips:</p> + +<ul> +<li> +<p>Intel PRO/1000 CT Network Connection (82547)</p> +</li> + +<li> +<p>Intel PRO/1000 F Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 Gigabit Server Adapter (82542)</p> +</li> + +<li> +<p>Intel PRO/1000 GT Desktop Adapter (82541PI)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (LX) (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82540)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82541)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Quad Port Server Adapter (82546EB)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 T Desktop Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 T Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 XF Server Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 XT Server Adapter (82544)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ep</span>(4)</span></a> driver supports +Ethernet adapters based on the 3Com 3C5x9 Etherlink III Parallel Tasking chipset, +including:</p> + +<ul> +<li> +<p>3Com 3C1 CF</p> +</li> + +<li> +<p>3Com 3C509-TP, 3C509-BNC, 3C509-Combo, 3C509-TPO, 3C509-TPC ISA</p> +</li> + +<li> +<p>3Com 3C509B-TP, 3C509B-BNC, 3C509B-Combo, 3C509B-TPO, 3C509B-TPC ISA</p> +</li> + +<li> +<p>3Com 3C529, 3C529-TP MCA</p> +</li> + +<li> +<p>3Com 3C562/3C563 PCMCIA</p> +</li> + +<li> +<p>3Com 3C569B-J-TPO, 3C569B-J-COMBO CBUS</p> +</li> + +<li> +<p>3Com 3C574, 3C574TX, 3C574-TX, 3CCFE574BT, 3CXFE574BT, 3C3FE574BT PCMCIA</p> +</li> + +<li> +<p>3Com 3C579-TP, 3C579-BNC EISA</p> +</li> + +<li> +<p>3Com 3C589, 3C589B, 3C589C, 3C589D, 3CXE589DT PCMCIA</p> +</li> + +<li> +<p>3Com 3CCFEM556B, 3CCFEM556BI PCMCIA</p> +</li> + +<li> +<p>3Com 3CXE589EC, 3CCE589EC, 3CXE589ET, 3CCE589ET PCMCIA</p> +</li> + +<li> +<p>3Com Megahertz 3CCEM556, 3CXEM556, 3CCEM556B, 3CXEM556B, 3C3FEM556C PCMCIA</p> +</li> + +<li> +<p>3Com OfficeConnect 3CXSH572BT, 3CCSH572BT PCMCIA</p> +</li> + +<li> +<p>Farallon EtherWave and EtherMac PC Card (P/n 595/895 with BLUE arrow)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ex&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ex</span>(4)</span></a> driver supports +the following Ethernet adapters:</p> + +<ul> +<li> +<p>Intel EtherExpress Pro/10</p> +</li> + +<li> +<p>Intel EtherExpress Pro/10+</p> +</li> + +<li> +<p>The Olicom OC2220</p> +</li> +</ul> + +<p>Controllers and cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">fe</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin)</p> +</li> + +<li> +<p>CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard)</p> +</li> + +<li> +<p>CONTEC C-NET(PC)C PCMCIA Ethernet</p> +</li> + +<li> +<p>Eagle Tech NE200T</p> +</li> + +<li> +<p>Eiger Labs EPX-10BT</p> +</li> + +<li> +<p>Fujitsu FMV-J182, FMV-J182A</p> +</li> + +<li> +<p>Fujitsu MB86960A, MB86965A</p> +</li> + +<li> +<p>Fujitsu MBH10303, MBH10302 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, and REX-R280</p> +</li> + +<li> +<p>RATOC REX-9880/9881/9882/9883</p> +</li> + +<li> +<p>TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin)</p> +</li> + +<li> +<p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p> +</li> + +<li> +<p>Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE N98(PC86132) +(110-pin)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel EtherExpress PRO/10</p> +</li> + +<li> +<p>Intel InBusiness 10/100</p> +</li> + +<li> +<p>Intel PRO/100B / EtherExpressPRO/100 B PCI 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>Contec C-NET(PI)-100TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B06 (PC-98)</p> +</li> + +<li> +<p>Many on-board network interfaces on Intel motherboards</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server +models. Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Sun PCI SunSwift Adapter</p> +</li> + +<li> +<p>Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)</p> +</li> + +<li> +<p>Sun PCI Sun100BaseT Adapter 2.0</p> +</li> + +<li> +<p>Sun SBus Sun100BaseT 2.0</p> +</li> + +<li> +<p>Sun PCI Quad FastEthernet Controller</p> +</li> + +<li> +<p>Sun SBus Quad FastEthernet Controller</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ixgb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ixgb</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>Intel PRO/10GbE LR Server Adapter</p> +</li> + +<li> +<p>Intel PRO/10GbE SR Server Adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kue</span>(4)</span></a> driver +supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>3Com 3c19250</p> +</li> + +<li> +<p>3Com 3c460 HomeConnect Ethernet USB Adapter</p> +</li> + +<li> +<p>ADS Technologies USB-10BT</p> +</li> + +<li> +<p>AOX USB101</p> +</li> + +<li> +<p>ATen UC10T</p> +</li> + +<li> +<p>Abocom URE 450</p> +</li> + +<li> +<p>Corega USB-T</p> +</li> + +<li> +<p>D-Link DSB-650C</p> +</li> + +<li> +<p>Entrega NET-USB-E45, NET-HUB-3U1E</p> +</li> + +<li> +<p>I/O Data USB ETT</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> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>SMC TigerCard 1000 (SMC9462SX)</p> +</li> + +<li> +<p>D-Link DGE-500SX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nge</span>(4)</span></a> driver +supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters +including:</p> + +<ul> +<li> +<p>Addtron AEG320T</p> +</li> + +<li> +<p>Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI)</p> +</li> + +<li> +<p>Asante FriendlyNet GigaNIX 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</p> +</li> + +<li> +<p>Netgear GA622T</p> +</li> + +<li> +<p>SMC EZ Card 1000 (SMC9462TX)</p> +</li> + +<li> +<p>Surecom Technology EP-320G-TX</p> +</li> + +<li> +<p>Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nve&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nve</span>(4)</span></a> driver +supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets:</p> + +<ul> +<li> +<p>nForce</p> +</li> + +<li> +<p>nForce2</p> +</li> + +<li> +<p>nForce3</p> +</li> + +<li> +<p>nForce4</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcn</span>(4)</span></a> driver +supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, +PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:</p> + +<ul> +<li> +<p>AMD Am79C971 PCnet-FAST</p> +</li> + +<li> +<p>AMD Am79C972 PCnet-FAST+</p> +</li> + +<li> +<p>AMD Am79C973/Am79C975 PCnet-FAST III</p> +</li> + +<li> +<p>AMD Am79C976 PCnet-PRO</p> +</li> + +<li> +<p>AMD Am79C978 PCnet-Home</p> +</li> + +<li> +<p>Allied-Telesis LA-PCI</p> +</li> + +<li> +<p>NEC SV-98/2-B05, B06</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">re</span>(4)</span></a> driver supports +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based Fast Ethernet and Gigabit +Ethernet adapters including:</p> + +<ul> +<li> +<p>Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)</p> +</li> + +<li> +<p>Compaq Evo N1015v Integrated Ethernet (8139C+)</p> +</li> + +<li> +<p>Corega CG-LAPCIGT Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>D-Link DGE-528(T) Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)</p> +</li> + +<li> +<p>LevelOne GNC-0105T (8169S)</p> +</li> + +<li> +<p>PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)</p> +</li> + +<li> +<p>Xterasys XN-152 10/100/1000 NIC (8169)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a> driver +include:</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>Belkin F5D5000</p> +</li> + +<li> +<p>BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)</p> +</li> + +<li> +<p>Compaq HNE-300</p> +</li> + +<li> +<p>CompUSA no-name 10/100 PCI Ethernet NIC</p> +</li> + +<li> +<p>Corega FEther CB-TXD</p> +</li> + +<li> +<p>Corega FEtherII CB-TXD</p> +</li> + +<li> +<p>D-Link DFE-528TX</p> +</li> + +<li> +<p>D-Link DFE-530TX+</p> +</li> + +<li> +<p>D-Link DFE-538TX</p> +</li> + +<li> +<p>D-Link DFE-690TXD</p> +</li> + +<li> +<p>Edimax EP-4103DL CardBus</p> +</li> + +<li> +<p>Encore ENL832-TX 10/100 M PCI</p> +</li> + +<li> +<p>Farallon NetLINE 10/100 PCI</p> +</li> + +<li> +<p>Genius GF100TXR</p> +</li> + +<li> +<p>GigaFast Ethernet EE100-AXP</p> +</li> + +<li> +<p>KTX-9130TX 10/100 Fast Ethernet</p> +</li> + +<li> +<p>LevelOne FPC-0106TX</p> +</li> + +<li> +<p>Longshine LCS-8038TX-R</p> +</li> + +<li> +<p>NDC Communications NE100TX-E</p> +</li> + +<li> +<p>Netronix Inc. EA-1210 NetEther 10/100</p> +</li> + +<li> +<p>Nortel Networks 10/100BaseTX</p> +</li> + +<li> +<p>OvisLink LEF-8129TX</p> +</li> + +<li> +<p>OvisLink LEF-8139TX</p> +</li> + +<li> +<p>Peppercon AG ROL-F</p> +</li> + +<li> +<p>Planex FNW-3800-TX</p> +</li> + +<li> +<p>SMC EZ Card 10/100 PCI 1211-TX</p> +</li> + +<li> +<p>SOHO (PRAGMATIC) UE-1211C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rue</span>(4)</span></a> driver +supports RealTek RTL8150 based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Buffalo (Melco Inc.) LUA-KTX</p> +</li> + +<li> +<p>Green House GH-USB100B</p> +</li> + +<li> +<p>LinkSys USB100M</p> +</li> + +<li> +<p>Billionton 10/100 FastEthernet USBKR2</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sf</span>(4)</span></a> driver +include:</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a> driver +supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and +embedded controllers, as well as Fast Ethernet adapters based on the National +Semiconductor DP83815 (MacPhyter) chip. Supported adapters include:</p> + +<ul> +<li> +<p>@Nifty FNECHARD IFC USUP-TX</p> +</li> + +<li> +<p>MELCO LGY-PCI-TXC</p> +</li> + +<li> +<p>Netgear FA311-TX (DP83815)</p> +</li> + +<li> +<p>Netgear FA312-TX (DP83815)</p> +</li> + +<li> +<p>SiS 630, 635, and 735 motherboard chipsets</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>3Com 3C940 single port, 1000baseT adapter</p> +</li> + +<li> +<p>3Com 3C2000-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Belkin F5D5005 single port, 1000baseT adapter</p> +</li> + +<li> +<p>D-Link DGE-530T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Linksys EG1032 single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9521 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9821 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9822 SK-NET GE-T dual port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9841 SK-NET GE-LX single port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9842 SK-NET GE-LX dual port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9843 SK-NET GE-SX single port, multimode fiber adapter</p> +</li> + +<li> +<p>SK-9844 SK-NET GE-SX dual port, multimode fiber adapter</p> +</li> + +<li> +<p>SMC 9452TX single port, 1000baseT adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sn</span>(4)</span></a> driver supports +SMC91Cxx based ISA and PCMCIA cards including:</p> + +<ul> +<li> +<p>3Com Megahertz X-Jack Ethernet PC-Card XJ10BT</p> +</li> + +<li> +<p>3Com Megahertz X-Jack Ethernet PC-Card XJ10BC</p> +</li> + +<li> +<p>Farallon EtherMac PC Card 595a</p> +</li> + +<li> +<p>Motorola Mariner Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Ositech Seven of Diamonds Ethernet PC Card</p> +</li> + +<li> +<p>Ositech Jack of Hearts Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Psion Gold Card Netglobal Ethernet PC Card</p> +</li> + +<li> +<p>Psion Gold Card Netglobal 10/100 Fast Ethernet PC Card</p> +</li> + +<li> +<p>Psion Gold Card Netglobal 56k+10Mb Ethernet PC Card</p> +</li> + +<li> +<p>SMC EZEther PC Card (8020BT)</p> +</li> + +<li> +<p>SMC EZEther PC Card (8020T)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sn</span>(4)</span></a> driver supports +the SMC 91C90, SMC 91C92, SMC 91C94, SMC 91C95, SMC 91C96, SMC91C100 and SMC 91C100FD +chips from SMC. The Farallon EtherWave and EtherMac card came in two varieties. The ep(4) +driver supports the 595 and 895 cards. These cards have the blue arrow on the front along +with a 3Com logo. The Farallon 595a cards, which have a red arrow on the front, are also +called EtherWave and EtherMac. They are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sn</span>(4)</span></a> driver.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ste</span>(4)</span></a> driver +supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded +controllers including:</p> + +<ul> +<li> +<p>D-Link DFE-530TXS</p> +</li> + +<li> +<p>D-Link DFE-550TX</p> +</li> + +<li> +<p>D-Link DFE-580TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ti</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Alteon Tigon I and II chips. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ti</span>(4)</span></a> driver has been +tested with the following adapters:</p> + +<ul> +<li> +<p>3Com 3c985-SX Gigabit Ethernet adapter (Tigon 1)</p> +</li> + +<li> +<p>3Com 3c985B-SX Gigabit Ethernet adapter (Tigon 2)</p> +</li> + +<li> +<p>Alteon AceNIC V Gigabit Ethernet adapter (1000baseSX)</p> +</li> + +<li> +<p>Alteon AceNIC V Gigabit Ethernet adapter (1000baseT)</p> +</li> + +<li> +<p>Digital EtherWORKS 1000SX PCI Gigabit adapter</p> +</li> + +<li> +<p>Netgear GA620 Gigabit Ethernet adapter (1000baseSX)</p> +</li> + +<li> +<p>Netgear GA620T Gigabit Ethernet adapter (1000baseT)</p> +</li> +</ul> + +<p>The following adapters should also be supported but have not yet been tested:</p> + +<ul> +<li> +<p>Asante GigaNIX1000T Gigabit Ethernet adapter</p> +</li> + +<li> +<p>Asante PCI 1000BASE-SX Gigabit Ethernet adapter</p> +</li> + +<li> +<p>Farallon PN9000SX Gigabit Ethernet adapter</p> +</li> + +<li> +<p>NEC Gigabit Ethernet</p> +</li> + +<li> +<p>Silicon Graphics PCI Gigabit Ethernet adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver supports +Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large +number of Compaq PCI Ethernet adapters. Also supported are:</p> + +<ul> +<li> +<p>Olicom OC-2135/2138 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Olicom OC-2325/OC-2326 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Racore 8148 10baseT/100baseTX/100baseFX adapter</p> +</li> + +<li> +<p>Racore 8165 10/100baseTX adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver also +supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq +Deskpro desktop machines including:</p> + +<ul> +<li> +<p>Compaq Netelligent 10</p> +</li> + +<li> +<p>Compaq Netelligent 10 T PCI UTP/Coax</p> +</li> + +<li> +<p>Compaq Netelligent 10/100</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Dual-Port</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Proliant</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX Embedded UTP</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX UTP</p> +</li> + +<li> +<p>Compaq NetFlex 3P</p> +</li> + +<li> +<p>Compaq NetFlex 3P Integrated</p> +</li> + +<li> +<p>Compaq NetFlex 3P w/BNC</p> +</li> +</ul> + +<p>SMC 83c17x (EPIC)-based Ethernet NICs (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tx</span>(4)</span></a> driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">txp</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>3Com 3CR990-TX-95</p> +</li> + +<li> +<p>3Com 3CR990-TX-97</p> +</li> + +<li> +<p>3Com 3cR990B-TXM</p> +</li> + +<li> +<p>3Com 3CR990SVR95</p> +</li> + +<li> +<p>3Com 3CR990SVR97</p> +</li> + +<li> +<p>3Com 3cR990B-SRV</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=udav&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">udav</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Corega FEther USB-TXC</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vge</span>(4)</span></a> driver +supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including:</p> + +<ul> +<li> +<p>VIA Networking LAN-on-motherboard Gigabit Ethernet</p> +</li> + +<li> +<p>ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701)</p> +</li> + +<li> +<p>ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vr</span>(4)</span></a> driver supports +VIA Technologies Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters +including:</p> + +<ul> +<li> +<p>AOpen/Acer ALN-320</p> +</li> + +<li> +<p>D-Link DFE530-TX</p> +</li> + +<li> +<p>Hawking Technologies PN102TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vx</span>(4)</span></a> driver supports +the following cards:</p> + +<ul> +<li> +<p>3Com 3c590 EtherLink III PCI</p> +</li> + +<li> +<p>3Com 3c592 EtherLink III EISA</p> +</li> + +<li> +<p>3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode</p> +</li> + +<li> +<p>3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wb</span>(4)</span></a> driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:</p> + +<ul> +<li> +<p>Trendware TE100-PCIE</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xe&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xe</span>(4)</span></a> driver supports +the following cards:</p> + +<ul> +<li> +<p>Xircom CreditCard Ethernet (PS-CE2-10)</p> +</li> + +<li> +<p>Xircom CreditCard Ethernet + Modem 28 (PS-CEM-28)</p> +</li> + +<li> +<p>Xircom CreditCard Ethernet + Modem 33 (CEM33)</p> +</li> + +<li> +<p>Xircom CreditCard 10/100 (CE3, CE3B)</p> +</li> + +<li> +<p>Xircom CreditCard Ethernet 10/100 + Modem 56 (CEM56)</p> +</li> + +<li> +<p>Xircom RealPort Ethernet 10 (RE10)</p> +</li> + +<li> +<p>Xircom RealPort Ethernet 10/100 (RE100)</p> +</li> + +<li> +<p>Xircom RealPort Ethernet 10/100 + Modem 56 (REM56, REM56G)</p> +</li> + +<li> +<p>Accton Fast EtherCard-16 (EN2226)</p> +</li> + +<li> +<p>Compaq Microcom CPQ550 Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 PC Card (CPQ-10/100)</p> +</li> + +<li> +<p>Intel EtherExpress Pro/100 PC Card Mobile Adapter 16 (Pro/100 M16A)</p> +</li> + +<li> +<p>Intel EtherExpress Pro/100 LAN/Modem PC Card Adapter (Pro/100 M16B)</p> +</li> +</ul> + +<p>Other similar devices using the same hardware may also be supported.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver supports +the following hardware:</p> + +<ul> +<li> +<p>3Com 3c900-TPO</p> +</li> + +<li> +<p>3Com 3c900-COMBO</p> +</li> + +<li> +<p>3Com 3c905-TX</p> +</li> + +<li> +<p>3Com 3c905-T4</p> +</li> + +<li> +<p>3Com 3c900B-TPO</p> +</li> + +<li> +<p>3Com 3c900B-TPC</p> +</li> + +<li> +<p>3Com 3c900B-FL</p> +</li> + +<li> +<p>3Com 3c900B-COMBO</p> +</li> + +<li> +<p>3Com 3c905B-T4</p> +</li> + +<li> +<p>3Com 3c905B-TX</p> +</li> + +<li> +<p>3Com 3c905B-FX</p> +</li> + +<li> +<p>3Com 3c905B-COMBO</p> +</li> + +<li> +<p>3Com 3c905C-TX</p> +</li> + +<li> +<p>3Com 3c980, 3c980B, and 3c980C server adapters</p> +</li> + +<li> +<p>3Com 3cSOHO100-TX OfficeConnect adapters</p> +</li> + +<li> +<p>3Com 3c450 HomeConnect adapters</p> +</li> + +<li> +<p>3Com 3c555, 3c556 and 3c556B mini-PCI adapters</p> +</li> + +<li> +<p>3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, +3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters</p> +</li> + +<li> +<p>3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded +adapters</p> +</li> +</ul> + +<p>Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a +built-in proprietary modem. Neither the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver nor any +other driver supports this modem.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="TOKENRING" name="TOKENRING">3.3 Token Ring Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FDDI" name="FDDI">3.4 FDDI Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ATM" name="ATM">3.5 ATM Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="WLAN" name="WLAN">3.6 Wireless Network Interfaces</a></h3> + +<p>Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes +using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and +Symbol Spectrum24 chipsets (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wi</span>(4)</span></a> driver)</p> + +<p>Cisco/Aironet 802.11b wireless adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">an</span>(4)</span></a> driver)</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=awi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">awi</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>BayStack 650</p> +</li> + +<li> +<p>BayStack 660</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</p> +</li> + +<li> +<p>Netwave AirSurfer Pro</p> +</li> + +<li> +<p>Nokia C020 WLAN</p> +</li> + +<li> +<p>Farallon SkyLINE</p> +</li> +</ul> + +<p>The original Xircom Netwave AirSurfer is supported by the cnw(4) driver.</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cnw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cnw</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Xircom CreditCard Netwave</p> +</li> + +<li> +<p>NetWave AirSurfer</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC-NETWORK" name="MISC-NETWORK">3.7 Miscellaneous +Networks</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ISDN" name="ISDN">3.8 ISDN Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SERIAL" name="SERIAL">3.9 Serial Interfaces</a></h3> + +<p>“PC standard” 8250, 16450, and 16550-based serial ports (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uart&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uart</span>(4)</span></a> driver +supports the following classes of UARTs:</p> + +<ul> +<li> +<p>NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 +UARTs</p> +</li> + +<li> +<p>SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.</p> +</li> + +<li> +<p>Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.</p> +</li> +</ul> + +<p>AST 4 port serial card using shared IRQ</p> + +<p>PCI-Based multi-port serial boards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=puc&sektion=4&manpath=FreeBSD+6.1-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, Smartio C104H-PCI 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>Specialix SI/XIO/SX multiport serial cards, with both the older SIHOST2.x and the +“enhanced” (transputer based, aka JET) host cards (ISA, EISA and PCI) are +supported. Note that the newer SX+ PCI cards are not currently supported. (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=si&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">si</span>(4)</span></a> driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SOUND" name="SOUND">3.10 Sound Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ad1816&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ad1816</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Analog Devices AD1816</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver supports the following audio chipsets:</p> + +<ul> +<li> +<p>ATI IXP 200</p> +</li> + +<li> +<p>ATI IXP 300</p> +</li> + +<li> +<p>ATI IXP 400</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_cmi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_cmi</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>CMedia CMI8338A</p> +</li> + +<li> +<p>CMedia CMI8338B</p> +</li> + +<li> +<p>CMedia CMI8738</p> +</li> + +<li> +<p>CMedia CMI8738B</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_cs4281&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_cs4281</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Crystal Semiconductor CS4281</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_csa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_csa</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Crystal Semiconductor CS4280</p> +</li> + +<li> +<p>Crystal Semiconductor CS4610</p> +</li> + +<li> +<p>Crystal Semiconductor CS4611</p> +</li> + +<li> +<p>Crystal Semiconductor CS4614</p> +</li> + +<li> +<p>Crystal Semiconductor CS4615</p> +</li> + +<li> +<p>Crystal Semiconductor CS4622</p> +</li> + +<li> +<p>Crystal Semiconductor CS4624</p> +</li> + +<li> +<p>Crystal Semiconductor CS4630</p> +</li> + +<li> +<p>Genius Soundmaker 128 Value</p> +</li> + +<li> +<p>Hercules Game Theatre XP</p> +</li> + +<li> +<p>Turtle Beach Santa Cruz</p> +</li> +</ul> + +<p>Some onboard CS4610 chips are accompanied by the CS423x ISA codec instead of the +CS4297 AC97 codec. Such configurations are not supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_csa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_csa</span>(4)</span></a> +driver yet.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ds1&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ds1</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Yamaha DS-1</p> +</li> + +<li> +<p>Yamaha DS-1E</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_emu10k1&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_emu10k1</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Creative SoundBlaster Live! (EMU10K1 Chipset)</p> +</li> + +<li> +<p>Creative SoundBlaster Audigy (EMU10K2 Chipset)</p> +</li> + +<li> +<p>Creative SoundBlaster Audigy 2 (EMU10K2 Chipset)</p> +</li> + +<li> +<p>Creative SoundBlaster Audigy 2 (EMU10K3 Chipset)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Creative CT5880-A</p> +</li> + +<li> +<p>Creative CT5880-C</p> +</li> + +<li> +<p>Creative CT5880-D</p> +</li> + +<li> +<p>Creative CT5880-E</p> +</li> + +<li> +<p>Creative SB AudioPCI CT4730</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1370</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1371-A</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1371-B</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-A</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-B</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-8</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ess&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ess</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Ensoniq ESS ISA PnP/non-PnP</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_fm801&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_fm801</span>(4)</span></a> +driver supports audio devices based on the following chipset:</p> + +<ul> +<li> +<p>Forte Media FM801</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_gusc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_gusc</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Gravis UltraSound MAX</p> +</li> + +<li> +<p>Gravis UltraSound PnP</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>AMD 768</p> +</li> + +<li> +<p>AMD 8111</p> +</li> + +<li> +<p>Intel 443MX</p> +</li> + +<li> +<p>Intel ICH</p> +</li> + +<li> +<p>Intel ICH revision 1</p> +</li> + +<li> +<p>Intel ICH2</p> +</li> + +<li> +<p>Intel ICH3</p> +</li> + +<li> +<p>Intel ICH4</p> +</li> + +<li> +<p>Intel ICH5</p> +</li> + +<li> +<p>Intel ICH6</p> +</li> + +<li> +<p>Intel ICH7</p> +</li> + +<li> +<p>NVIDIA nForce</p> +</li> + +<li> +<p>NVIDIA nForce2</p> +</li> + +<li> +<p>NVIDIA nForce2 400</p> +</li> + +<li> +<p>NVIDIA nForce3</p> +</li> + +<li> +<p>NVIDIA nForce3 250</p> +</li> + +<li> +<p>NVIDIA nForce4</p> +</li> + +<li> +<p>SiS 7012</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_maestro&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_maestro</span>(4)</span></a> +driver supports the following PCI sound cards:</p> + +<ul> +<li> +<p>ESS Technology Maestro-1</p> +</li> + +<li> +<p>ESS Technology Maestro-2</p> +</li> + +<li> +<p>ESS Technology Maestro-2E</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_maestro3&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_maestro3</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>ESS Technology Allegro-1</p> +</li> + +<li> +<p>ESS Technology Maestro3</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_neomagic&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_neomagic</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>NeoMagic 256AV</p> +</li> + +<li> +<p>NeoMagic 256ZX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_sbc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_sbc</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Avance Asound 110</p> +</li> + +<li> +<p>Avance Logic ALS100+</p> +</li> + +<li> +<p>Avance Logic ALS120</p> +</li> + +<li> +<p>Creative SB16</p> +</li> + +<li> +<p>Creative SB32</p> +</li> + +<li> +<p>Creative AWE64</p> +</li> + +<li> +<p>Creative AWE64 Gold</p> +</li> + +<li> +<p>Creative ViBRA16C</p> +</li> + +<li> +<p>Creative ViBRA16X</p> +</li> + +<li> +<p>ESS ES1681</p> +</li> + +<li> +<p>ESS ES1688</p> +</li> + +<li> +<p>ESS ES1868</p> +</li> + +<li> +<p>ESS ES1869</p> +</li> + +<li> +<p>ESS ES1878</p> +</li> + +<li> +<p>ESS ES1879</p> +</li> + +<li> +<p>ESS ES1888</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>ESS Solo-1 (ES1938 Chipset)</p> +</li> + +<li> +<p>ESS Solo-1E (ES1946 Chipset)</p> +</li> +</ul> + +<p>Note that older ESS ISA cards with ES18xx chipset are supported via snd_ess(4) and/or +snd_sbc(4).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_t4dwave&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_t4dwave</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>Acer Labs M5451</p> +</li> + +<li> +<p>SIS 7018</p> +</li> + +<li> +<p>Trident 4DWave DX</p> +</li> + +<li> +<p>Trident 4DWave NX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver supports audio devices based on the following chipset:</p> + +<ul> +<li> +<p>VIA 82C686A</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_vibes&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_vibes</span>(4)</span></a> +driver supports audio devices based on the following chipset:</p> + +<ul> +<li> +<p>S3 SonicVibes</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CAMERA" name="CAMERA">3.11 Camera and Video Capture +Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USB" name="USB">3.12 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> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> USB Bluetooth adapters can be found in <a href="#BLUETOOTH">Bluetooth</a> +section.</p> +</blockquote> +</div> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a> driver +supports all OHCI v1.0 compliant controllers including:</p> + +<ul> +<li> +<p>AcerLabs M5237 (Aladdin-V)</p> +</li> + +<li> +<p>AMD-756</p> +</li> + +<li> +<p>OPTi 82C861 (FireLink)</p> +</li> + +<li> +<p>NEC uPD 9210</p> +</li> + +<li> +<p>CMD Tech 670 (USB0670)</p> +</li> + +<li> +<p>CMD Tech 673 (USB0673)</p> +</li> + +<li> +<p>NVIDIA nForce3</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO USB)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a> driver +supports all UHCI v1.1 compliant controllers including:</p> + +<ul> +<li> +<p>Intel 82371AB/EB (PIIX4)</p> +</li> + +<li> +<p>Intel 82371SB (PIIX3)</p> +</li> + +<li> +<p>VIA 83C572</p> +</li> +</ul> + +<p>USB 2.0 controllers using the EHCI interface (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ehci</span>(4)</span></a> +driver)</p> + +<p>Hubs</p> + +<p>Keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> + +<p>Miscellaneous</p> + +<ul> +<li> +<p>Assist Computer Systems PC Camera C-M1</p> +</li> + +<li> +<p>ActiveWire I/O Board</p> +</li> + +<li> +<p>Creative Technology Video Blaster WebCam Plus</p> +</li> + +<li> +<p>D-Link DSB-R100 USB Radio (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ufm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ufm</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>Mirunet AlphaCam Plus</p> +</li> +</ul> + +<br /> +<br /> +<p>The following devices are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=urio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">urio</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>Diamond MultiMedia Rio 500</p> +</li> + +<li> +<p>Diamond MultiMedia Rio 600</p> +</li> + +<li> +<p>Diamond MultiMedia Rio 800</p> +</li> +</ul> + +<p>Devices supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umodem&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umodem</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>3Com 5605</p> +</li> + +<li> +<p>Metricom Ricochet GS USB wireless modem</p> +</li> + +<li> +<p>Yamaha Broadband Wireless Router RTW65b</p> +</li> + +<li> +<p>ELSA MicroLink 56k USB modem</p> +</li> +</ul> + +<p>Mice (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ulpt</span>(4)</span></a> driver +provides support for USB printers and parallel printer conversion cables, including the +following:</p> + +<ul> +<li> +<p>ATen parallel printer adapter</p> +</li> + +<li> +<p>Belkin F5U002 parallel printer adapter</p> +</li> + +<li> +<p>Canon BJ F850, S600</p> +</li> + +<li> +<p>Canon LBP-1310, 350</p> +</li> + +<li> +<p>Entrega USB-to-parallel printer adapter</p> +</li> + +<li> +<p>Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)</p> +</li> + +<li> +<p>Oki Data MICROLINE ML660PS</p> +</li> + +<li> +<p>Seiko Epson PM-900C, 880C, 820C, 730C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsa</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U103</p> +</li> + +<li> +<p>Belkin F5U120</p> +</li> + +<li> +<p>e-Tek Labs Kwik232</p> +</li> + +<li> +<p>GoHubs GoCOM232</p> +</li> + +<li> +<p>Peracom single port serial adapter</p> +</li> + +<li> +<p>Vodafone Mobile Connect 3G datacard</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubser&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubser</span>(4)</span></a> driver +provides support for the BWCT console management serial adapters.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uftdi</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>B&B Electronics USB->RS422/485 adapter</p> +</li> + +<li> +<p>HP USB-Serial adapter shipped with some HP laptops</p> +</li> + +<li> +<p>Inland UAS111</p> +</li> + +<li> +<p>QVS USC-1000</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uplcom&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uplcom</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>ATEN UC-232A</p> +</li> + +<li> +<p>BAFO BF-800</p> +</li> + +<li> +<p>BAFO BF-810</p> +</li> + +<li> +<p>ELECOM UC-SGT</p> +</li> + +<li> +<p>HAL Corporation Crossam2+USB IR commander</p> +</li> + +<li> +<p>Hama USB RS-232 Serial Adapter</p> +</li> + +<li> +<p>IOGEAR UC-232A</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ2</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ3</p> +</li> + +<li> +<p>PLANEX USB-RS232 URS-03</p> +</li> + +<li> +<p>RATOC REX-USB60</p> +</li> + +<li> +<p>Sandberg USB to Serial Link (model number 133-08)</p> +</li> + +<li> +<p>SOURCENEXT KeikaiDenwa 8 (with and without charger)</p> +</li> + +<li> +<p>Sony Ericsson USB Cable (Susteen USB Data Cable)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umct&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umct</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U109</p> +</li> + +<li> +<p>Belkin F5U409</p> +</li> + +<li> +<p>D-Link DU-H3SP USB BAY Hub</p> +</li> + +<li> +<p>Magic Control Technology USB-232</p> +</li> + +<li> +<p>Sitecom USB-232</p> +</li> +</ul> + +<p>The following devices are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uscanner&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uscanner</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>Acer Acerscan 320U</p> +</li> + +<li> +<p>Acer Acerscan 620U</p> +</li> + +<li> +<p>Acer Acerscan 640U</p> +</li> + +<li> +<p>Acer Acerscan 1240U</p> +</li> + +<li> +<p>Acer Acerscan C310U</p> +</li> + +<li> +<p>AGFA SnapScan 1212U</p> +</li> + +<li> +<p>AGFA SnapScan 1236U</p> +</li> + +<li> +<p>AGFA SnapScan e20</p> +</li> + +<li> +<p>AGFA SnapScan e25</p> +</li> + +<li> +<p>AGFA SnapScan e26</p> +</li> + +<li> +<p>AGFA SnapScan e40</p> +</li> + +<li> +<p>AGFA SnapScan e50</p> +</li> + +<li> +<p>AGFA SnapScan e52</p> +</li> + +<li> +<p>AGFA SnapScan Touch</p> +</li> + +<li> +<p>Avision 1200U</p> +</li> + +<li> +<p>Canon CanoScan N656U</p> +</li> + +<li> +<p>Canon CanoScan N676U</p> +</li> + +<li> +<p>Canon CanoScan N1220U</p> +</li> + +<li> +<p>Canon CanoScan LIDE 20</p> +</li> + +<li> +<p>Canon CanoScan LIDE 30</p> +</li> + +<li> +<p>Epson Perfection 610</p> +</li> + +<li> +<p>Epson Perfection 636U / 636Photo</p> +</li> + +<li> +<p>Epson Perfection 640U</p> +</li> + +<li> +<p>Epson Perfection 1200U / 1200Photo</p> +</li> + +<li> +<p>Epson Perfection 1240U / 1240Photo</p> +</li> + +<li> +<p>Epson Perfection 1250</p> +</li> + +<li> +<p>Epson Perfection 1260</p> +</li> + +<li> +<p>Epson Expression 1600</p> +</li> + +<li> +<p>Epson Perfection 1640SU</p> +</li> + +<li> +<p>Epson Perfection 1650</p> +</li> + +<li> +<p>Epson Perfection 1660</p> +</li> + +<li> +<p>Epson Perfection 1670</p> +</li> + +<li> +<p>Epson Perfection 3200</p> +</li> + +<li> +<p>Epson GT-8400UF</p> +</li> + +<li> +<p>Epson GT-9300UF</p> +</li> + +<li> +<p>Epson GT-9700F</p> +</li> + +<li> +<p>Hewlett Packard Photosmart S20</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 2200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 3300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 3400CSE</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4100C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5400C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 6200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 6300C</p> +</li> + +<li> +<p>KYE ColorPage Vivid-Pro</p> +</li> + +<li> +<p>Microtek Phantom 336CX</p> +</li> + +<li> +<p>Microtek Phantom C6</p> +</li> + +<li> +<p>Microtek ScanMaker V6UL</p> +</li> + +<li> +<p>Microtek ScanMaker V6USL</p> +</li> + +<li> +<p>Microtek ScanMaker X6U</p> +</li> + +<li> +<p>Minolta 5400</p> +</li> + +<li> +<p>Mustek 600 CU</p> +</li> + +<li> +<p>Mustek 1200 CU</p> +</li> + +<li> +<p>Mustek 1200 UB</p> +</li> + +<li> +<p>Mustek 1200 USB</p> +</li> + +<li> +<p>Mustek BearPaw 1200F</p> +</li> + +<li> +<p>Mustek BearPaw 1200TA</p> +</li> + +<li> +<p>NatSemi BearPaw 1200</p> +</li> + +<li> +<p>Nikon CoolScan LS40 ED</p> +</li> + +<li> +<p>Primax 6200</p> +</li> + +<li> +<p>Primax Colorado 1200u</p> +</li> + +<li> +<p>Primax Colorado 600u</p> +</li> + +<li> +<p>Primax Colorado USB 19200</p> +</li> + +<li> +<p>Primax Colorado USB 9600</p> +</li> + +<li> +<p>Primax G2-200</p> +</li> + +<li> +<p>Primax G2-300</p> +</li> + +<li> +<p>Primax G2-600</p> +</li> + +<li> +<p>Primax G2600</p> +</li> + +<li> +<p>Primax G2E-300</p> +</li> + +<li> +<p>Primax G2E-3002</p> +</li> + +<li> +<p>Primax G2E-600</p> +</li> + +<li> +<p>Primax G2E600</p> +</li> + +<li> +<p>Primax G2X-300</p> +</li> + +<li> +<p>Primax G600</p> +</li> + +<li> +<p>Primax ReadyScan 636i</p> +</li> + +<li> +<p>Ultima 1200 UB Plus</p> +</li> + +<li> +<p>UMAX Astra 1220U</p> +</li> + +<li> +<p>UMAX Astra 1236U</p> +</li> + +<li> +<p>UMAX Astra 2000U</p> +</li> + +<li> +<p>UMAX Astra 2100U</p> +</li> + +<li> +<p>UMAX Astra 2200U</p> +</li> + +<li> +<p>UMAX Astra 3400</p> +</li> + +<li> +<p>Visioneer OneTouch 3000</p> +</li> + +<li> +<p>Visioneer OneTouch 5300</p> +</li> + +<li> +<p>Visioneer OneTouch 7600</p> +</li> + +<li> +<p>Visioneer OneTouch 6100</p> +</li> + +<li> +<p>Visioneer OneTouch 6200</p> +</li> + +<li> +<p>Visioneer OneTouch 8100</p> +</li> + +<li> +<p>Visioneer OneTouch 8600</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umass</span>(4)</span></a> driver +supports USB Mass Storage devices, including:</p> + +<ul> +<li> +<p>ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M</p> +</li> + +<li> +<p>Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20</p> +</li> + +<li> +<p>FujiFilm Zip USB Drive ZDR100 USB A</p> +</li> + +<li> +<p>GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M</p> +</li> + +<li> +<p>IBM 32MB USB Memory Key (P/N 22P5296)</p> +</li> + +<li> +<p>IBM 256MB USB Drive (MSYSTEM DiskOnKey2)</p> +</li> + +<li> +<p>IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)</p> +</li> + +<li> +<p>I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)</p> +</li> + +<li> +<p>I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)</p> +</li> + +<li> +<p>I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI</p> +</li> + +<li> +<p>Iomega USB Zip 100/250 drive</p> +</li> + +<li> +<p>Iomega Zip750 USB2.0 drive</p> +</li> + +<li> +<p>Keian USB1.1/2.0 3.5-inch HDD Case KU350A</p> +</li> + +<li> +<p>Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0</p> +</li> + +<li> +<p>LaCie P3 HardDrive USB 200GB</p> +</li> + +<li> +<p>Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive</p> +</li> + +<li> +<p>Logitec Mobile USB Memory LMC-256UD</p> +</li> + +<li> +<p>Logitec USB1.1/2.0 HDD Unit SHD-E60U2</p> +</li> + +<li> +<p>Logitec USB Double-Speed Floppy Drive LFD-31U2</p> +</li> + +<li> +<p>Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)</p> +</li> + +<li> +<p>MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M</p> +</li> + +<li> +<p>MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm</p> +</li> + +<li> +<p>MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2</p> +</li> + +<li> +<p>MELCO USB2.0 MO Drive MO-CH640U2</p> +</li> + +<li> +<p>Matshita CF-VFDU03 floppy drive</p> +</li> + +<li> +<p>Merlin SM300 MP3/WMA Player (256Mb)</p> +</li> + +<li> +<p>Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable</p> +</li> + +<li> +<p>Motorola E398 Mobile Phone (TransFlash memory card)</p> +</li> + +<li> +<p>NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U</p> +</li> + +<li> +<p>PNY Attache Flash Drive</p> +</li> + +<li> +<p>Panasonic ("Matshita FDD CF-VFDU03")</p> +</li> + +<li> +<p>Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW</p> +</li> + +<li> +<p>Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW)</p> +</li> + +<li> +<p>Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)</p> +</li> + +<li> +<p>Panasonic floppy drive</p> +</li> + +<li> +<p>Qware BeatZkey! Pro</p> +</li> + +<li> +<p>RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B</p> +</li> + +<li> +<p>SanDisk SDDR-31 (Compact Flash)</p> +</li> + +<li> +<p>SanDisk SDDR-75 (only Compact Flash port works)</p> +</li> + +<li> +<p>Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick)</p> +</li> + +<li> +<p>Sony Portable CD-R/RW Drive CRX10U (CDROM only)</p> +</li> + +<li> +<p>TEAC Portable USB CD-ROM Unit CD-110PU/210PU</p> +</li> + +<li> +<p>Time DPA20B MP3 Player (1Gb)</p> +</li> + +<li> +<p>Trek Thumbdrive 8MB</p> +</li> + +<li> +<p>VAIO floppy drive (includes Y-E Data Flashbuster-U)</p> +</li> + +<li> +<p>Y-E Data floppy drive (720/1.44/2.88Mb)</p> +</li> +</ul> + +<p>Among the supported digital cameras are:</p> + +<ul> +<li> +<p>Asahi Optical (PENTAX) Optio 230 & 330</p> +</li> +</ul> + +<p>Audio Devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uaudio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uaudio</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uvisor&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uvisor</span>(4)</span></a> driver +supports the following devices:</p> + +<ul> +<li> +<p>Handspring Treo</p> +</li> + +<li> +<p>Handspring Treo 600</p> +</li> + +<li> +<p>Handspring Visor</p> +</li> + +<li> +<p>Palm I705</p> +</li> + +<li> +<p>Palm M125</p> +</li> + +<li> +<p>Palm M130</p> +</li> + +<li> +<p>Palm M500</p> +</li> + +<li> +<p>Palm M505</p> +</li> + +<li> +<p>Palm M515</p> +</li> + +<li> +<p>Palm Tungsten T</p> +</li> + +<li> +<p>Palm Tungsten Z</p> +</li> + +<li> +<p>Palm Zire</p> +</li> + +<li> +<p>Palm Zire 31</p> +</li> + +<li> +<p>Sony Clie 4.0</p> +</li> + +<li> +<p>Sony Clie 4.1</p> +</li> + +<li> +<p>Sony Clie 5.0</p> +</li> + +<li> +<p>Sony Clie PEG-S500C</p> +</li> + +<li> +<p>Sony Clie NX60</p> +</li> + +<li> +<p>Sony Clie S360</p> +</li> + +<li> +<p>Sony Clie TJ37</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.13 IEEE 1394 (Firewire) +Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fwohci</span>(4)</span></a> driver +provides support for PCI/CardBus FireWire interface cards. The driver supports the +following IEEE 1394 OHCI chipsets:</p> + +<ul> +<li> +<p>Adaptec AHA-894x/AIC-5800</p> +</li> + +<li> +<p>Apple Pangea</p> +</li> + +<li> +<p>Apple UniNorth</p> +</li> + +<li> +<p>Intel 82372FB</p> +</li> + +<li> +<p>IOGEAR GUF320</p> +</li> + +<li> +<p>Lucent / Agere FW322/323</p> +</li> + +<li> +<p>NEC uPD72861</p> +</li> + +<li> +<p>NEC uPD72870</p> +</li> + +<li> +<p>NEC uPD72871/2</p> +</li> + +<li> +<p>NEC uPD72873</p> +</li> + +<li> +<p>NEC uPD72874</p> +</li> + +<li> +<p>National Semiconductor CS4210</p> +</li> + +<li> +<p>Ricoh R5C551</p> +</li> + +<li> +<p>Ricoh R5C552</p> +</li> + +<li> +<p>Sony CX3022</p> +</li> + +<li> +<p>Sony i.LINK (CXD1947)</p> +</li> + +<li> +<p>Sony i.LINK (CXD3222)</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO 1394)</p> +</li> + +<li> +<p>Texas Instruments PCI4410A</p> +</li> + +<li> +<p>Texas Instruments PCI4450</p> +</li> + +<li> +<p>Texas Instruments PCI4451</p> +</li> + +<li> +<p>Texas Instruments TSB12LV22</p> +</li> + +<li> +<p>Texas Instruments TSB12LV23</p> +</li> + +<li> +<p>Texas Instruments TSB12LV26</p> +</li> + +<li> +<p>Texas Instruments TSB43AA22</p> +</li> + +<li> +<p>Texas Instruments TSB43AB21/A/AI/A-EP</p> +</li> + +<li> +<p>Texas Instruments TSB43AB22/A</p> +</li> + +<li> +<p>Texas Instruments TSB43AB23</p> +</li> + +<li> +<p>Texas Instruments TSB82AA2</p> +</li> + +<li> +<p>VIA Fire II (VT6306)</p> +</li> +</ul> + +<p>Serial Bus Protocol 2 (SBP-2) storage devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sbp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbp</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.14 Bluetooth Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_bt3c&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_bt3c</span>(4)</span></a> +driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_ubt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_ubt</span>(4)</span></a> driver +supports all Bluetooth USB devices that conform with the Bluetooth specification v1.1, +including:</p> + +<ul> +<li> +<p>3Com 3CREB96</p> +</li> + +<li> +<p>AIPTEK BR0R02</p> +</li> + +<li> +<p>EPoX BT-DG02</p> +</li> + +<li> +<p>Mitsumi Bluetooth USB adapter</p> +</li> + +<li> +<p>MSI MS-6967</p> +</li> + +<li> +<p>TDK Bluetooth USB adapter</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CRYPTO-ACCEL" name="CRYPTO-ACCEL">3.15 Cryptographic +Accelerators</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hifn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hifn</span>(4)</span></a> driver +supports various cards containing the Hifn 7751, 7951, 7811, 7955, and 7956 chipsets, +such as:</p> + +<ul> +<li> +<p>Invertex AEON</p> +</li> + +<li> +<p>Hifn 7751</p> +</li> + +<li> +<p>PowerCrypt</p> +</li> + +<li> +<p>XL-Crypt</p> +</li> + +<li> +<p>NetSec 7751</p> +</li> + +<li> +<p>Soekris Engineering vpn1201 and vpn1211</p> +</li> + +<li> +<p>Soekris Engineering vpn1401 and vpn1411</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=safe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">safe</span>(4)</span></a> driver +supports cards containing any of the following chips:</p> + +<ul> +<li> +<p>SafeNet 1141</p> +</li> + +<li> +<p>SafeNet 1741</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsec</span>(4)</span></a> driver +supports cards containing any of the following chips:</p> + +<ul> +<li> +<p>Bluesteel 5501</p> +</li> + +<li> +<p>Bluesteel 5601</p> +</li> + +<li> +<p>Broadcom BCM5801</p> +</li> + +<li> +<p>Broadcom BCM5802</p> +</li> + +<li> +<p>Broadcom BCM5805</p> +</li> + +<li> +<p>Broadcom BCM5820</p> +</li> + +<li> +<p>Broadcom BCM5821</p> +</li> + +<li> +<p>Broadcom BCM5822</p> +</li> + +<li> +<p>Broadcom BCM5823</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC" name="MISC">3.16 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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.org/</a>.</p> +</blockquote> +</div> + +<br /> +<br /> +<p>Keyboards including:</p> + +<ul> +<li> +<p>PS/2 keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>USB keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<br /> +<br /> +<p>Pointing devices including:</p> + +<ul> +<li> +<p>Bus mice and compatible devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mse&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mse</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>PS/2 mice and compatible devices, including many laptop pointing devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+6.1-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 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.org/</a>.</p> +</blockquote> +</div> + +<br /> +<br /> +<p>“PC standard” parallel ports (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">joy</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/hardware-i386.html b/en/releases/6.1R/hardware-i386.html new file mode 100644 index 0000000000..9c69a3ce64 --- /dev/null +++ b/en/releases/6.1R/hardware-i386.html @@ -0,0 +1,7537 @@ +<!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 6.1-RELEASE Hardware Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.1-RELEASE Hardware +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<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="#PROC">Supported Processors and Motherboards</a></dt> + +<dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + +<dd> +<dl> +<dt>3.1 <a href="#DISK">Disk Controllers</a></dt> + +<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt> + +<dt>3.3 <a href="#TOKENRING">Token Ring Interfaces</a></dt> + +<dt>3.4 <a href="#FDDI">FDDI Interfaces</a></dt> + +<dt>3.5 <a href="#ATM">ATM Interfaces</a></dt> + +<dt>3.6 <a href="#WLAN">Wireless Network Interfaces</a></dt> + +<dt>3.7 <a href="#MISC-NETWORK">Miscellaneous Networks</a></dt> + +<dt>3.8 <a href="#ISDN">ISDN Interfaces</a></dt> + +<dt>3.9 <a href="#SERIAL">Serial Interfaces</a></dt> + +<dt>3.10 <a href="#SOUND">Sound Devices</a></dt> + +<dt>3.11 <a href="#CAMERA">Camera and Video Capture Devices</a></dt> + +<dt>3.12 <a href="#USB">USB Devices</a></dt> + +<dt>3.13 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt> + +<dt>3.14 <a href="#BLUETOOTH">Bluetooth Devices</a></dt> + +<dt>3.15 <a href="#CRYPTO-ACCEL">Cryptographic Accelerators</a></dt> + +<dt>3.16 <a href="#MISC">Miscellaneous</a></dt> +</dl> +</dd> +</dl> +</div> + +<div class="SECT1"> +<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This document contains the hardware compatibility notes for FreeBSD 6.1-RELEASE on the +i386 hardware platform (also referred to as FreeBSD/i386 6.1-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 compatibility notes for other architectures will +differ in some details.</p> +</blockquote> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="PROC" name="PROC">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 with a floating point unit are supported. All +Intel processors beginning with the 80486 are supported, including the 80486, Pentium, +Pentium Pro, Pentium II, Pentium III, Pentium 4, and variants thereof, such as the Xeon +and Celeron processors. All i386-compatible AMD processors are also supported, including +the Am486, Am5x86, K5, K6 (and variants), Athlon (including Athlon-MP, Athlon-XP, +Athlon-4, and Athlon Thunderbird), and Duron processors. The AMD Élan SC520 +embedded processor is supported. The Transmeta Crusoe is recognized and supported, as are +i386-compatible processors from Cyrix and NexGen.</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 take advantage of HyperThreading (HTT) support on Intel CPUs that support +this feature. A kernel with the <tt class="LITERAL">options SMP</tt> feature enabled +will automatically detect the additional logical processors. The default FreeBSD +scheduler treats the logical processors the same as additional physical processors; in +other words, no attempt is made to optimize scheduling decisions given the shared +resources between logical processors within the same CPU. Because this naive scheduling +can result in suboptimal performance, under certain circumstances it may be useful to +disable the logical processors with the the <code +class="VARNAME">machdep.hlt_logical_cpus</code> sysctl variable. It is also possible to +halt any CPU in the idle loop with the <code class="VARNAME">machdep.hlt_cpus</code> +sysctl variable. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=smp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">smp</span>(4)</span></a> manual +page has more details.</p> + +<p>FreeBSD will take advantage of Physical Address Extensions (PAE) support on CPUs that +support this feature. A kernel with the <tt class="LITERAL">PAE</tt> feature enabled will +detect memory above 4 gigabytes and allow it to be used by the system. This feature +places constraints on the device drivers and other features of FreeBSD which may be used; +consult the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pae&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pae</span>(4)</span></a> manpage +for more details.</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> + +<p>Most modern laptops (as well as many desktops) use the Advanced Configuration and +Power Management (ACPI) standard. FreeBSD supports ACPI via the ACPI Component +Architecture reference implementation from Intel, as described in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi</span>(4)</span></a> manual +page. The use of ACPI causes instabilities on some machines and it may be necessary to +disable the ACPI driver, which is normally loaded via a kernel module. This may be +accomplished by adding the following line to <tt +class="FILENAME">/boot/device.hints</tt>:</p> + +<pre class="PROGRAMLISTING"> +hint.acpi.0.disabled="1" +</pre> + +<p>Users debugging ACPI-related problems may find it useful to disable portions of the +ACPI functionality. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi</span>(4)</span></a> manual +page has more information on how to do this via loader tunables.</p> + +<p>ACPI depends on a Differentiated System Descriptor Table (DSDT) provided by each +machine's BIOS. Some machines have bad or incomplete DSDTs, which prevents ACPI from +functioning correctly. Replacement DSDTs for some machines can be found at the <a +href="http://acpi.sourceforge.net/dsdt/index.php" target="_top">DSDT</a> section of the +<a href="http://acpi.sourceforge.net/" target="_top">ACPI4Linux</a> project Web site. +FreeBSD can use these DSDTs to override the DSDT provided by the BIOS; see the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi</span>(4)</span></a> manual +page for more information.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2> + +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.9.2.2 +2006/05/01 08:26:00 brueffer 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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> The device lists in this document are being generated automatically from +FreeBSD manual pages. This means that some devices, which are supported by multiple +drivers, may appear multiple times.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DISK" name="DISK">3.1 Disk Controllers</a></h3> + +<p>IDE/ATA controllers (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> +driver)</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aac</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec AAC-364</p> +</li> + +<li> +<p>Adaptec SATA RAID 2410SA</p> +</li> + +<li> +<p>Adaptec SATA RAID 2810SA</p> +</li> + +<li> +<p>Adaptec SATA RAID 21610SA</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2120S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2130S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2200S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2130SLP</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2230SLP</p> +</li> + +<li> +<p>Adaptec SCSI RAID 5400S</p> +</li> + +<li> +<p>Dell CERC SATA RAID 2</p> +</li> + +<li> +<p>Dell PERC 2/Si</p> +</li> + +<li> +<p>Dell PERC 2/QC</p> +</li> + +<li> +<p>Dell PERC 3/Si</p> +</li> + +<li> +<p>Dell PERC 3/Di</p> +</li> + +<li> +<p>Dell PERC 320/DC</p> +</li> + +<li> +<p>HP NetRAID 4M</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=adv&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adv</span>(4)</span></a> driver +supports the following SCSI controllers:</p> + +<ul> +<li> +<p>AdvanSys ABP510/5150</p> +</li> + +<li> +<p>AdvanSys ABP5140</p> +</li> + +<li> +<p>AdvanSys ABP5142</p> +</li> + +<li> +<p>AdvanSys ABP902/3902</p> +</li> + +<li> +<p>AdvanSys ABP3905</p> +</li> + +<li> +<p>AdvanSys ABP915</p> +</li> + +<li> +<p>AdvanSys ABP920</p> +</li> + +<li> +<p>AdvanSys ABP3922</p> +</li> + +<li> +<p>AdvanSys ABP3925</p> +</li> + +<li> +<p>AdvanSys ABP930, ABP930U, ABP930UA</p> +</li> + +<li> +<p>AdvanSys ABP960, ABP960U</p> +</li> + +<li> +<p>AdvanSys ABP542</p> +</li> + +<li> +<p>AdvanSys ABP742</p> +</li> + +<li> +<p>AdvanSys ABP842</p> +</li> + +<li> +<p>AdvanSys ABP940</p> +</li> + +<li> +<p>AdvanSys ABP940UA/3940UA</p> +</li> + +<li> +<p>AdvanSys ABP940U</p> +</li> + +<li> +<p>AdvanSys ABP3960UA</p> +</li> + +<li> +<p>AdvanSys ABP970, ABP970U</p> +</li> + +<li> +<p>AdvanSys ABP752</p> +</li> + +<li> +<p>AdvanSys ABP852</p> +</li> + +<li> +<p>AdvanSys ABP950</p> +</li> + +<li> +<p>AdvanSys ABP980, ABP980U</p> +</li> + +<li> +<p>AdvanSys ABP980UA/3980UA</p> +</li> + +<li> +<p>MELCO IFC-USP (PC-98)</p> +</li> + +<li> +<p>RATOC REX-PCI30 (PC-98)</p> +</li> + +<li> +<p>@Nifty FNECHARD IFC-USUP-TX (PC-98)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=adw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adw</span>(4)</span></a> driver +supports SCSI controllers including:</p> + +<ul> +<li> +<p>AdvanSys ABP940UW/ABP3940UW</p> +</li> + +<li> +<p>AdvanSys ABP950UW</p> +</li> + +<li> +<p>AdvanSys ABP970UW</p> +</li> + +<li> +<p>AdvanSys ABP3940U2W</p> +</li> + +<li> +<p>AdvanSys ABP3950U2W</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aha</span>(4)</span></a> driver +supports the following SCSI host adapters:</p> + +<ul> +<li> +<p>Adaptec AHA-154xB</p> +</li> + +<li> +<p>Adaptec AHA-154xC</p> +</li> + +<li> +<p>Adaptec AHA-154xCF</p> +</li> + +<li> +<p>Adaptec AHA-154xCP</p> +</li> + +<li> +<p>Adaptec AHA-1640</p> +</li> + +<li> +<p>Adaptec AHA-174x in 154x emulation mode</p> +</li> + +<li> +<p>DTC 3290 SCSI controller in 1542 emulation mode</p> +</li> + +<li> +<p>Tekram SCSI controllers in 154x emulation mode</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahb</span>(4)</span></a> driver +supports the following SCSI host adapters:</p> + +<ul> +<li> +<p>Adaptec AHA-1740</p> +</li> + +<li> +<p>Adaptec AHA-1742</p> +</li> + +<li> +<p>Adaptec AHA-1740A</p> +</li> + +<li> +<p>Adaptec AHA-1742A</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a> driver +supports the following SCSI host adapter chips and SCSI controller cards:</p> + +<ul> +<li> +<p>Adaptec AIC7770 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7850 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7860 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7870 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7880 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7890 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7891 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7892 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7895 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7896 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7897 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7899 host adapter chip</p> +</li> + +<li> +<p>Adaptec 274X(W)</p> +</li> + +<li> +<p>Adaptec 274X(T)</p> +</li> + +<li> +<p>Adaptec 284X</p> +</li> + +<li> +<p>Adaptec 2910</p> +</li> + +<li> +<p>Adaptec 2915</p> +</li> + +<li> +<p>Adaptec 2920</p> +</li> + +<li> +<p>Adaptec 2930C</p> +</li> + +<li> +<p>Adaptec 2930U2</p> +</li> + +<li> +<p>Adaptec 2940</p> +</li> + +<li> +<p>Adaptec 2940J</p> +</li> + +<li> +<p>Adaptec 2940N</p> +</li> + +<li> +<p>Adaptec 2940U</p> +</li> + +<li> +<p>Adaptec 2940AU</p> +</li> + +<li> +<p>Adaptec 2940UW</p> +</li> + +<li> +<p>Adaptec 2940UW Dual</p> +</li> + +<li> +<p>Adaptec 2940UW Pro</p> +</li> + +<li> +<p>Adaptec 2940U2W</p> +</li> + +<li> +<p>Adaptec 2940U2B</p> +</li> + +<li> +<p>Adaptec 2950U2W</p> +</li> + +<li> +<p>Adaptec 2950U2B</p> +</li> + +<li> +<p>Adaptec 19160B</p> +</li> + +<li> +<p>Adaptec 29160B</p> +</li> + +<li> +<p>Adaptec 29160N</p> +</li> + +<li> +<p>Adaptec 3940</p> +</li> + +<li> +<p>Adaptec 3940U</p> +</li> + +<li> +<p>Adaptec 3940AU</p> +</li> + +<li> +<p>Adaptec 3940UW</p> +</li> + +<li> +<p>Adaptec 3940AUW</p> +</li> + +<li> +<p>Adaptec 3940U2W</p> +</li> + +<li> +<p>Adaptec 3950U2</p> +</li> + +<li> +<p>Adaptec 3960</p> +</li> + +<li> +<p>Adaptec 39160</p> +</li> + +<li> +<p>Adaptec 3985</p> +</li> + +<li> +<p>Adaptec 4944UW</p> +</li> + +<li> +<p>NEC PC-9821Xt13 (PC-98)</p> +</li> + +<li> +<p>NEC RvII26 (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B02L/B09 (PC-98)</p> +</li> + +<li> +<p>NEC SV-98/2-B03 (PC-98)</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahd</span>(4)</span></a> driver +supports the following:</p> + +<ul> +<li> +<p>Adaptec AIC7901 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7901A host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7902 host adapter chip</p> +</li> + +<li> +<p>Adaptec 29320 host adapter</p> +</li> + +<li> +<p>Adaptec 39320 host adapter</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>The adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aic&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aic</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec AHA-1505 (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1510A, AHA-1510B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1520A, AHA-1520B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1522A, AHA-1522B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1535 (ISA)</p> +</li> + +<li> +<p>Creative Labs SoundBlaster SCSI host adapter (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1460, AHA-1460B, AHA-1460C, AHA-1460D (PC Card)</p> +</li> + +<li> +<p>Adaptec AHA-1030B, AHA-1030P (PC98)</p> +</li> + +<li> +<p>NEC PC-9801-100 (PC98)</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amd</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MELCO IFC-DP (PC-98)</p> +</li> + +<li> +<p>Tekram DC390</p> +</li> + +<li> +<p>Tekram DC390T</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MegaRAID SCSI 320-1E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-8X</p> +</li> + +<li> +<p>MegaRAID SATA 150-4</p> +</li> + +<li> +<p>MegaRAID SATA 150-6</p> +</li> + +<li> +<p>MegaRAID i4 133 RAID</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0</p> +</li> + +<li> +<p>MegaRAID SCSI 320-1</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4</p> +</li> + +<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 Elite 1650 (Series 4xx)</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 3/QC</p> +</li> + +<li> +<p>Dell PERC 4/DC</p> +</li> + +<li> +<p>Dell PERC 4/IM</p> +</li> + +<li> +<p>Dell PERC 4/SC</p> +</li> + +<li> +<p>Dell PERC 4/Di</p> +</li> + +<li> +<p>Dell PERC 4e/DC</p> +</li> + +<li> +<p>Dell PERC 4e/Di</p> +</li> + +<li> +<p>Dell PERC 4e/Si</p> +</li> + +<li> +<p>Dell PERC 4ei</p> +</li> + +<li> +<p>HP NetRAID-1/Si</p> +</li> + +<li> +<p>HP NetRAID-3/Si (D4943A)</p> +</li> + +<li> +<p>HP Embedded NetRAID</p> +</li> + +<li> +<p>Intel RAID Controller SRCS16</p> +</li> + +<li> +<p>Intel RAID Controller SRCU42X</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arcmsr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arcmsr</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>ARC-1110</p> +</li> + +<li> +<p>ARC-1120</p> +</li> + +<li> +<p>ARC-1130</p> +</li> + +<li> +<p>ARC-1160</p> +</li> + +<li> +<p>ARC-1130-ML</p> +</li> + +<li> +<p>ARC-1160-ML</p> +</li> + +<li> +<p>ARC-1210</p> +</li> + +<li> +<p>ARC-1220</p> +</li> + +<li> +<p>ARC-1230</p> +</li> + +<li> +<p>ARC-1260</p> +</li> + +<li> +<p>ARC-1230-ML</p> +</li> + +<li> +<p>ARC-1260-ML</p> +</li> +</ul> + +<p>The adapters currently supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">asr</span>(4)</span></a> driver +include the following:</p> + +<ul> +<li> +<p>Adaptec Zero-Channel SCSI RAID 2000S, 2005S, 2010S, 2015S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2100S, 2110S</p> +</li> + +<li> +<p>Adaptec ATA-100 RAID 2400A</p> +</li> + +<li> +<p>Adaptec SCSI RAID 3200S, 3210S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 3400S, 3410S</p> +</li> + +<li> +<p>Adaptec SmartRAID PM1554</p> +</li> + +<li> +<p>Adaptec SmartRAID PM1564</p> +</li> + +<li> +<p>Adaptec SmartRAID PM2554</p> +</li> + +<li> +<p>Adaptec SmartRAID PM2564</p> +</li> + +<li> +<p>Adaptec SmartRAID PM2664</p> +</li> + +<li> +<p>Adaptec SmartRAID PM2754</p> +</li> + +<li> +<p>Adaptec SmartRAID PM2865</p> +</li> + +<li> +<p>Adaptec SmartRAID PM3754</p> +</li> + +<li> +<p>Adaptec SmartRAID PM3755U2B / SmartRAID V Millennium</p> +</li> + +<li> +<p>Adaptec SmartRAID PM3757</p> +</li> + +<li> +<p>DEC KZPCC-AC (LVD 1-ch, 4MB or 16MB cache), DEC KZPCC-CE (LVD 3-ch, 64MB cache), DEC +KZPCC-XC (LVD 1-ch, 16MB cache), DEC KZPCC-XE (LVD 3-ch, 64MB cache) -- rebadged +SmartRAID V Millennium</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a> driver supports +the following BusLogic MultiMaster “W”, “C”, “S”, and +“A” series and compatible SCSI host adapters:</p> + +<ul> +<li> +<p>BusLogic BT-445C</p> +</li> + +<li> +<p>BusLogic BT-445S</p> +</li> + +<li> +<p>BusLogic BT-540CF</p> +</li> + +<li> +<p>BusLogic BT-542B</p> +</li> + +<li> +<p>BusLogic BT-542B</p> +</li> + +<li> +<p>BusLogic BT-542D</p> +</li> + +<li> +<p>BusLogic BT-545C</p> +</li> + +<li> +<p>BusLogic BT-545S</p> +</li> + +<li> +<p>BusLogic/BusTek BT-640</p> +</li> + +<li> +<p>BusLogic BT-742A</p> +</li> + +<li> +<p>BusLogic BT-742A</p> +</li> + +<li> +<p>BusLogic BT-747C</p> +</li> + +<li> +<p>BusLogic BT-747D</p> +</li> + +<li> +<p>BusLogic BT-747S</p> +</li> + +<li> +<p>BusLogic BT-757C</p> +</li> + +<li> +<p>BusLogic BT-757CD</p> +</li> + +<li> +<p>BusLogic BT-757D</p> +</li> + +<li> +<p>BusLogic BT-757S</p> +</li> + +<li> +<p>BusLogic BT-946C</p> +</li> + +<li> +<p>BusLogic BT-948</p> +</li> + +<li> +<p>BusLogic BT-956C</p> +</li> + +<li> +<p>BusLogic BT-956CD</p> +</li> + +<li> +<p>BusLogic BT-958</p> +</li> + +<li> +<p>BusLogic BT-958D</p> +</li> + +<li> +<p>Storage Dimensions SDC3211B / SDC3211F</p> +</li> +</ul> + +<p>AMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also +supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">bt</span>(4)</span></a> driver.</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ciss&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ciss</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Compaq Smart Array 5300</p> +</li> + +<li> +<p>Compaq Smart Array 532</p> +</li> + +<li> +<p>Compaq Smart Array 5i</p> +</li> + +<li> +<p>HP Smart Array 5312</p> +</li> + +<li> +<p>HP Smart Array 6i</p> +</li> + +<li> +<p>HP Smart Array 641</p> +</li> + +<li> +<p>HP Smart Array 642</p> +</li> + +<li> +<p>HP Smart Array 6400</p> +</li> + +<li> +<p>HP Smart Array 6400 EM</p> +</li> + +<li> +<p>HP Smart Array E400</p> +</li> + +<li> +<p>HP Smart Array P600</p> +</li> + +<li> +<p>HP Smart Array P800</p> +</li> + +<li> +<p>HP Modular Smart Array 20 (MSA20)</p> +</li> + +<li> +<p>HP Modular Smart Array 500 (MSA500)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dpt</span>(4)</span></a> driver +provides support for the following RAID adapters:</p> + +<ul> +<li> +<p>DPT Smart Cache Plus</p> +</li> + +<li> +<p>Smart Cache II (PM2?2?, PM2022 [EISA], PM2024/PM2124 [PCI]) (Gen2)</p> +</li> + +<li> +<p>Smart RAID II (PM3?2?, PM3021, PM3222)</p> +</li> + +<li> +<p>Smart Cache III (PM2?3?)</p> +</li> + +<li> +<p>Smart RAID III (PM3?3?, PM3332 [EISA], PM3334UW [PCI]) (Gen3)</p> +</li> + +<li> +<p>Smart Cache IV (PM2?4?, PM2042 [EISA], PM2044/PM2144 [PCI]) (Gen4)</p> +</li> + +<li> +<p>Smart RAID IV</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hptmv&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hptmv</span>(4)</span></a> driver +supports the following ATA RAID controllers:</p> + +<ul> +<li> +<p>HighPoint's RocketRAID 182x series</p> +</li> +</ul> + +<p>The following controllers are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ida&sektion=4&manpath=FreeBSD+6.1-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</p> +</li> + +<li> +<p>Compaq SMART Array 4250ES</p> +</li> + +<li> +<p>Compaq SMART 3200 Controller</p> +</li> + +<li> +<p>Compaq SMART 3100ES Controller</p> +</li> + +<li> +<p>Compaq SMART-2/DH Controller</p> +</li> + +<li> +<p>Compaq SMART-2/SL Controller</p> +</li> + +<li> +<p>Compaq SMART-2/P Controller</p> +</li> + +<li> +<p>Compaq SMART-2/E Controller</p> +</li> + +<li> +<p>Compaq SMART Controller</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">iir</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel RAID Controller SRCMR</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-l (SRCU31a)</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-1L (SRCU31La)</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-2 (SRCU32)</p> +</li> + +<li> +<p>All past and future releases of Intel and ICP RAID Controllers.</p> +</li> +</ul> + +<ul> +<li> +<p>Intel RAID Controller SRCU21 (discontinued)</p> +</li> + +<li> +<p>Intel RAID Controller SRCU31 (older revision, not compatible)</p> +</li> + +<li> +<p>Intel RAID Controller SRCU31L (older revision, not compatible)</p> +</li> +</ul> + +<p>The SRCU31 and SRCU31L can be updated via a firmware update available from Intel.</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ips&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ips</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>IBM ServeRAID 3H</p> +</li> + +<li> +<p>ServeRAID 4L/4M/4H</p> +</li> + +<li> +<p>ServeRAID Series 5</p> +</li> + +<li> +<p>ServeRAID 6i/6M</p> +</li> +</ul> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>ISP1000</p> +</li> + +<li> +<p>ISP1020</p> +</li> + +<li> +<p>ISP1040</p> +</li> + +<li> +<p>Qlogic 1240</p> +</li> + +<li> +<p>Qlogic 1020</p> +</li> + +<li> +<p>Qlogic 1040</p> +</li> + +<li> +<p>Qlogic 1080</p> +</li> + +<li> +<p>Qlogic 1280</p> +</li> + +<li> +<p>Qlogic 12160</p> +</li> + +<li> +<p>Qlogic 210X</p> +</li> + +<li> +<p>Qlogic 220X</p> +</li> + +<li> +<p>Qlogic 2300</p> +</li> + +<li> +<p>Qlogic 2312</p> +</li> + +<li> +<p>Qlogic 234X</p> +</li> + +<li> +<p>Qlogic 2322</p> +</li> + +<li> +<p>Qlogic 200</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver +supports the following hardware:</p> + +<ul> +<li> +<p>LSI MegaRAID SAS 8408E</p> +</li> + +<li> +<p>LSI MegaRAID SAS 8480E</p> +</li> + +<li> +<p>Dell PERC5/i</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mlx</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Mylex DAC960P</p> +</li> + +<li> +<p>Mylex DAC960PD / DEC KZPSC (Fast Wide)</p> +</li> + +<li> +<p>Mylex DAC960PDU</p> +</li> + +<li> +<p>Mylex DAC960PL</p> +</li> + +<li> +<p>Mylex DAC960PJ</p> +</li> + +<li> +<p>Mylex DAC960PG</p> +</li> + +<li> +<p>Mylex DAC960PU / DEC PZPAC (Ultra Wide)</p> +</li> + +<li> +<p>Mylex AcceleRAID 150 (DAC960PRL)</p> +</li> + +<li> +<p>Mylex AcceleRAID 250 (DAC960PTL1)</p> +</li> + +<li> +<p>Mylex eXtremeRAID 1100 (DAC1164P)</p> +</li> + +<li> +<p>RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA +(3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)</p> +</li> +</ul> + +<p>All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is +always advisable to upgrade to the most recent firmware available for the controller. +Compatible Mylex controllers not listed should work, but have not been verified.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> Booting from these controllers is supported. EISA adapters are not +supported.</p> +</blockquote> +</div> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mly</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Mylex AcceleRAID 160</p> +</li> + +<li> +<p>Mylex AcceleRAID 170</p> +</li> + +<li> +<p>Mylex AcceleRAID 352</p> +</li> + +<li> +<p>Mylex eXtremeRAID 2000</p> +</li> + +<li> +<p>Mylex eXtremeRAID 3000</p> +</li> +</ul> + +<p>Compatible Mylex controllers not listed should work, but have not been verified.</p> + +<p>The following controllers are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>LSI Logic 53c1030 (Dual Ultra320 SCSI)</p> +</li> + +<li> +<p>LSI Logic FC909 (1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC909A (Dual 1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC919 (2Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC929, LSI Logic FC929X (Dual 2Gb/s Fibre Channel)</p> +</li> +</ul> + +<p>The SCSI controller chips supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver +can be found onboard on many systems including:</p> + +<ul> +<li> +<p>Dell PowerEdge 1750</p> +</li> + +<li> +<p>IBM eServer xSeries 335</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> driver +provides support for the following NCR/Symbios SCSI controller chips:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C820</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C875J</p> +</li> + +<li> +<p>53C885</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The following add-on boards are known to be supported:</p> + +<ul> +<li> +<p>I-O DATA SC-98/PCI (PC-98)</p> +</li> + +<li> +<p>I-O DATA SC-PCI (PC-98)</p> +</li> +</ul> + +<p>The following devices are currently supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ncv&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncv</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>I-O DATA PCSC-DV</p> +</li> + +<li> +<p>KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004, and UJDCD450</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 (SCSI only)</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nsp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nsp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Alpha-Data AD-PCS201</p> +</li> + +<li> +<p>I-O DATA CBSC16</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pst&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pst</span>(4)</span></a> driver +supports the Promise Supertrak SX6000 ATA hardware RAID controller.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> driver +supports the following hardware:</p> + +<ul> +<li> +<p>HighPoint RocketRAID 2320</p> +</li> + +<li> +<p>HighPoint RocketRAID 2322</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=stg&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">stg</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec 2920/A</p> +</li> + +<li> +<p>Future Domain SCSI2GO</p> +</li> + +<li> +<p>Future Domain TMC-18XX/3260</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> + +<p>Note that the Adaptec 2920C is supported by the ahc(4) driver.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> driver +provides support for the following Symbios/LSI Logic PCI SCSI controllers:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C825</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C876</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C897</p> +</li> + +<li> +<p>53C1000</p> +</li> + +<li> +<p>53C1000R</p> +</li> + +<li> +<p>53C1010-33</p> +</li> + +<li> +<p>53C1010-66</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The SCSI controllers supported by <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> can be +either embedded on a motherboard, or on one of the following add-on boards:</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>I-O DATA SC-UPCI (PC-98)</p> +</li> + +<li> +<p>Logitec LHA-521UA (PC-98)</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> + +<p>SCSI controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=trm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">trm</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Tekram DC-315 PCI Ultra SCSI adapter without BIOS and internal SCSI connector</p> +</li> + +<li> +<p>Tekram DC-315U PCI Ultra SCSI adapter without BIOS</p> +</li> + +<li> +<p>Tekram DC-395F PCI Ultra-Wide SCSI adapter with flash BIOS and 68-pin external SCSI +connector</p> +</li> + +<li> +<p>Tekram DC-395U PCI Ultra SCSI adapter with flash BIOS</p> +</li> + +<li> +<p>Tekram DC-395UW PCI Ultra-Wide SCSI adapter with flash BIOS</p> +</li> + +<li> +<p>Tekram DC-395U2W PCI Ultra2-Wide SCSI adapter with flash BIOS</p> +</li> +</ul> + +<p>For the Tekram DC-310/U and DC-390F/U/UW/U2B/U2W/U3W PCI SCSI host adapters, use the +sym(4) driver.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +supports the following SATA RAID controllers:</p> + +<ul> +<li> +<p>AMCC's 3ware 9500S-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-8</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-8MI</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-12</p> +</li> + +<li> +<p>AMCC's 3ware 9500S-12MI</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-8LP</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-12</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-12MI</p> +</li> + +<li> +<p>AMCC's 3ware 9500SX-16ML</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-8LP</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-12</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-12MI</p> +</li> + +<li> +<p>AMCC's 3ware 9550SX-16ML</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twe</span>(4)</span></a> driver +supports the following PATA/SATA RAID controllers:</p> + +<ul> +<li> +<p>AMCC's 3ware 5000 series</p> +</li> + +<li> +<p>AMCC's 3ware 6000 series</p> +</li> + +<li> +<p>AMCC's 3ware 7000-2</p> +</li> + +<li> +<p>AMCC's 3ware 7006-2</p> +</li> + +<li> +<p>AMCC's 3ware 7500-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 7500-8</p> +</li> + +<li> +<p>AMCC's 3ware 7500-12</p> +</li> + +<li> +<p>AMCC's 3ware 7506-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 7506-8</p> +</li> + +<li> +<p>AMCC's 3ware 7506-12</p> +</li> + +<li> +<p>AMCC's 3ware 8006-2LP</p> +</li> + +<li> +<p>AMCC's 3ware 8500-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 8500-8</p> +</li> + +<li> +<p>AMCC's 3ware 8500-12</p> +</li> + +<li> +<p>AMCC's 3ware 8506-4LP</p> +</li> + +<li> +<p>AMCC's 3ware 8506-8</p> +</li> + +<li> +<p>AMCC's 3ware 8506-8MI</p> +</li> + +<li> +<p>AMCC's 3ware 8506-12</p> +</li> + +<li> +<p>AMCC's 3ware 8506-12MI</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vpo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vpo</span>(4)</span></a> driver +supports the following parallel to SCSI interfaces:</p> + +<ul> +<li> +<p>Adaptec AIC-7110 Parallel to SCSI interface (built-in to Iomega ZIP drives)</p> +</li> + +<li> +<p>Iomega Jaz Traveller interface</p> +</li> + +<li> +<p>Iomega MatchMaker SCSI interface (built-in to Iomega ZIP+ drives)</p> +</li> +</ul> + +<p>The wds(4) driver supports the WD7000 SCSI controller.</p> + +<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&sektion=4&manpath=FreeBSD+6.1-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&sektion=1&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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acd</span>(4)</span></a>)</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&sektion=4&manpath=FreeBSD+6.1-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>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aue</span>(4)</span></a> driver +include:</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-T, FEther USB-TX, FEther USB-TXS</p> +</li> + +<li> +<p>D-Link DSB-650, DSB-650TX, DSB-650TX-PNA</p> +</li> + +<li> +<p>Elecom LD-USBL/TX</p> +</li> + +<li> +<p>Elsa Microlink USB2Ethernet</p> +</li> + +<li> +<p>HP hn210e</p> +</li> + +<li> +<p>I-O Data USB ETTX</p> +</li> + +<li> +<p>Kingston KNU101TX</p> +</li> + +<li> +<p>LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, +USB100TX, USB100H1</p> +</li> + +<li> +<p>MELCO LUA-TX, LUA2-TX</p> +</li> + +<li> +<p>Planex UE-200TX</p> +</li> + +<li> +<p>Sandberg USB to Network Link (model number 133-06)</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">axe</span>(4)</span></a> driver +supports ASIX Electronics AX88172 based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Buffalo (Melco Inc.) LUA-U2-KTX</p> +</li> + +<li> +<p>D-Link DUBE100</p> +</li> + +<li> +<p>LinkSys USB200M</p> +</li> + +<li> +<p>Netgear FA120</p> +</li> + +<li> +<p>Sitecom LN-029</p> +</li> + +<li> +<p>System TALKS Inc. SGC-X2UL</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bce&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bce</span>(4)</span></a> driver +provides support for various NICs based on the Broadcom NetXtreme II family of Gigabit +Ethernet controllers, including the following:</p> + +<ul> +<li> +<p>HP NC370T Multifunction Gigabit Server Adapter</p> +</li> + +<li> +<p>HP NC370i Multifunction Gigabit Server Adapter</p> +</li> +</ul> + +<p>Broadcom BCM4401 based Fast Ethernet adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +provides support for various NICs based on the Broadcom BCM570x family of Gigabit +Ethernet controller chips, including the following:</p> + +<ul> +<li> +<p>3Com 3c996-T (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Netgear GA302T (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D21 (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D41 (1000baseSX)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cue</span>(4)</span></a> driver +supports CATC USB-EL1210A based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Belkin F5U011/F5U111</p> +</li> + +<li> +<p>CATC Netmate</p> +</li> + +<li> +<p>CATC Netmate II</p> +</li> + +<li> +<p>SmartBridges SmartLink</p> +</li> +</ul> + +<p>Crystal Semiconductor CS89x0-based NICs (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cs&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">cs</span>(4)</span></a> driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver provides +support for the following chipsets:</p> + +<ul> +<li> +<p>DEC/Intel 21143</p> +</li> + +<li> +<p>ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II</p> +</li> + +<li> +<p>ASIX Electronics AX88140A and AX88141</p> +</li> + +<li> +<p>Conexant LANfinity RS7112 (miniPCI)</p> +</li> + +<li> +<p>Davicom DM9009, DM9100, DM9102 and DM9102A</p> +</li> + +<li> +<p>Lite-On 82c168 and 82c169 PNIC</p> +</li> + +<li> +<p>Lite-On/Macronix 82c115 PNIC II</p> +</li> + +<li> +<p>Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732</p> +</li> + +<li> +<p>Xircom X3201 (cardbus only)</p> +</li> +</ul> + +<p>The following NICs are known to work with the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver at this +time:</p> + +<ul> +<li> +<p>3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Abocom FE2500</p> +</li> + +<li> +<p>Accton EN1217 (98715A)</p> +</li> + +<li> +<p>Accton EN2242 MiniPCI</p> +</li> + +<li> +<p>Adico AE310TX (98715A)</p> +</li> + +<li> +<p>Alfa Inc GFC2204 (ASIX AX88140A)</p> +</li> + +<li> +<p>Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, +non-MII)</p> +</li> + +<li> +<p>Built in DE500-BA on DEC Alpha workstations (21143, non-MII)</p> +</li> + +<li> +<p>Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, +MII)</p> +</li> + +<li> +<p>Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)</p> +</li> + +<li> +<p>CNet Pro110B (ASIX AX88140A)</p> +</li> + +<li> +<p>CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)</p> +</li> + +<li> +<p>Compex RL100-TX (98713 or 98713A)</p> +</li> + +<li> +<p>D-Link DFE-570TX (21143, MII, quad port)</p> +</li> + +<li> +<p>Digital DE500-BA 10/100 (21143, non-MII)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CBL/TXA (ADMtek AN985)</p> +</li> + +<li> +<p>Hawking CB102 CardBus</p> +</li> + +<li> +<p>IBM EtherJet Cardbus Adapter</p> +</li> + +<li> +<p>Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)</p> +</li> + +<li> +<p>Jaton XpressNet (Davicom DM9102)</p> +</li> + +<li> +<p>Kingston KNE100TX (21143, MII)</p> +</li> + +<li> +<p>Kingston KNE110TX (PNIC 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX v2.0 (PNIC II 82c115)</p> +</li> + +<li> +<p>LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Matrox FastNIC 10/100 (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>Melco LGY-PCI-TXL</p> +</li> + +<li> +<p>Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)</p> +</li> + +<li> +<p>Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A (98713A)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A Rev B4 (98715AEC-C)</p> +</li> + +<li> +<p>NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)</p> +</li> + +<li> +<p>Netgear FA511</p> +</li> + +<li> +<p>PlaneX FNW-3602-T (ADMtek AN985)</p> +</li> + +<li> +<p>SMC EZ Card 10/100 1233A-TX (ADMtek AN985)</p> +</li> + +<li> +<p>SVEC PN102-TX (98713)</p> +</li> + +<li> +<p>Xircom Cardbus Realport</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet 10/100</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet II 10/100</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec ANA-6944/TX</p> +</li> + +<li> +<p>Cogent EM100FX and EM440TX</p> +</li> + +<li> +<p>Corega FastEther PCI-TX</p> +</li> + +<li> +<p>D-Link DFE-500TX</p> +</li> + +<li> +<p>DEC DE435, DEC DE450, and DEC DE500</p> +</li> + +<li> +<p>ELECOM LD-PCI2T, LD-PCITS</p> +</li> + +<li> +<p>I-O DATA LA2/T-PCI</p> +</li> + +<li> +<p>SMC Etherpower 8432, 9332 and 9334</p> +</li> + +<li> +<p>ZNYX ZX3xx</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span></a> driver supports +the following Ethernet NICs:</p> + +<ul> +<li> +<p>3Com 3c503 Etherlink II</p> +</li> + +<li> +<p>AR-P500 Ethernet</p> +</li> + +<li> +<p>Accton EN1644 (old model), EN1646 (old model), EN2203 (old model) (110pin) (flags +0xd00000)</p> +</li> + +<li> +<p>Accton EN2212/EN2216/UE2216</p> +</li> + +<li> +<p>Allied Telesis CentreCOM LA100-PCM_V2</p> +</li> + +<li> +<p>Allied Telesis LA-98 (flags 0x000000) (PC-98)</p> +</li> + +<li> +<p>Allied Telesis SIC-98, SIC-98NOTE (110pin), SIU-98 (flags 0x600000) (PC-98)</p> +</li> + +<li> +<p>Allied Telesis SIU-98-D (flags 0x610000) (PC-98)</p> +</li> + +<li> +<p>AmbiCom 10BaseT card</p> +</li> + +<li> +<p>Bay Networks NETGEAR FA410TXC Fast Ethernet</p> +</li> + +<li> +<p>Belkin F5D5020 PC Card Fast Ethernet</p> +</li> + +<li> +<p>Billionton LM5LT-10B Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Bromax iPort 10/100 Ethernet PC Card</p> +</li> + +<li> +<p>Bromax iPort 10 Ethernet PC Card</p> +</li> + +<li> +<p>Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX PC Card</p> +</li> + +<li> +<p>CNet BC40 adapter</p> +</li> + +<li> +<p>Compex Net-A adapter</p> +</li> + +<li> +<p>Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) (flags 0xa00000) (PC-98)</p> +</li> + +<li> +<p>Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P (flags 0x300000) (PC-98)</p> +</li> + +<li> +<p>Corega Ether98-T (flags 0x000000) (PC-98)</p> +</li> + +<li> +<p>Corega Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD</p> +</li> + +<li> +<p>CyQ've ELA-010</p> +</li> + +<li> +<p>DEC EtherWorks DE305</p> +</li> + +<li> +<p>Danpex EN-6200P2</p> +</li> + +<li> +<p>D-Link DE-298, DE-298P (flags 0x500000) (PC-98)</p> +</li> + +<li> +<p>D-Link DE-650/660</p> +</li> + +<li> +<p>D-Link IC-CARD/IC-CARD+ Ethernet</p> +</li> + +<li> +<p>ELECOM LD-98P (flags 0x500000) (PC-98)</p> +</li> + +<li> +<p>ELECOM LD-BDN, LD-NW801G (flags 0x200000) (PC-98)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A)</p> +</li> + +<li> +<p>HP PC Lan+ 27247B and 27252A</p> +</li> + +<li> +<p>IBM Creditcard Ethernet I/II</p> +</li> + +<li> +<p>ICM AD-ET2-T, DT-ET-25, DT-ET-T5, IF-2766ET, IF-2771ET, NB-ET-T (110pin) (flags +0x500000) (PC-98)</p> +</li> + +<li> +<p>I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 (flags 0x900000) (PC-98)</p> +</li> + +<li> +<p>I-O DATA ET2/T-PCI</p> +</li> + +<li> +<p>I-O DATA PCLATE</p> +</li> + +<li> +<p>Kansai KLA-98C/T (flags 0x900000) (PC-98)</p> +</li> + +<li> +<p>Kingston KNE-PC2, CIO10T, KNE-PCM/x Ethernet</p> +</li> + +<li> +<p>Linksys EC2T/PCMPC100/PCM100, PCMLM56</p> +</li> + +<li> +<p>Linksys EtherFast 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 V2)</p> +</li> + +<li> +<p>Logitec LAN-98T (flags 0xb00000) (PC-98)</p> +</li> + +<li> +<p>MACNICA Ethernet ME1 for JEIDA</p> +</li> + +<li> +<p>MACNICA ME98 (flags 0x900000) (PC-98)</p> +</li> + +<li> +<p>MACNICA NE2098 (flags 0x400000) (PC-98)</p> +</li> + +<li> +<p>MELCO EGY-98 (flags 0x300000) (PC-98)</p> +</li> + +<li> +<p>MELCO LGH-98, LGY-98, LGY-98-N (110pin), IND-SP, IND-SS (flags 0x400000) (PC-98)</p> +</li> + +<li> +<p>MELCO LGY-PCI-TR</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>NEC PC-9801-77, PC-9801-78 (flags 0x910000) (PC-98)</p> +</li> + +<li> +<p>NEC PC-9801-107, PC-9801-108 (flags 0x800000) (PC-98)</p> +</li> + +<li> +<p>National Semiconductor InfoMover NE4100</p> +</li> + +<li> +<p>NetGear FA-410TX</p> +</li> + +<li> +<p>NetVin 5000</p> +</li> + +<li> +<p>Network Everywhere Ethernet 10BaseT PC Card</p> +</li> + +<li> +<p>Networld 98X3 (flags 0xd00000) (PC-98)</p> +</li> + +<li> +<p>Networld EC-98X, EP-98X (flags 0xd10000) (PC-98)</p> +</li> + +<li> +<p>New Media LANSurfer 10+56 Ethernet/Modem</p> +</li> + +<li> +<p>New Media LANSurfer</p> +</li> + +<li> +<p>Novell NE1000/NE2000/NE2100</p> +</li> + +<li> +<p>PLANEX ENW-8300-T</p> +</li> + +<li> +<p>PLANEX EN-2298-C (flags 0x200000) (PC-98)</p> +</li> + +<li> +<p>PLANEX EN-2298P-T, EN-2298-T (flags 0x500000) (PC-98)</p> +</li> + +<li> +<p>PLANEX FNW-3600-T</p> +</li> + +<li> +<p>Psion 10/100 LANGLOBAL Combine iT</p> +</li> + +<li> +<p>RealTek 8029</p> +</li> + +<li> +<p>Relia Combo-L/M-56k PC Card</p> +</li> + +<li> +<p>SMC Elite 16 WD8013</p> +</li> + +<li> +<p>SMC Elite Ultra</p> +</li> + +<li> +<p>SMC EtherEZ98 (flags 0x000000) (PC-98)</p> +</li> + +<li> +<p>SMC WD8003E/WD8003EBT/WD8003S/WD8003SBT/WD8003W/WD8013EBT/WD8013W and clones</p> +</li> + +<li> +<p>SMC EZCard PC Card, 8040-TX, 8041-TX</p> +</li> + +<li> +<p>Socket LP-E, ES-1000 Ethernet/Serial, LP-E CF, LP-FE CF</p> +</li> + +<li> +<p>Surecom EtherPerfect EP-427</p> +</li> + +<li> +<p>Surecom NE-34</p> +</li> + +<li> +<p>TDK 3000/3400/5670 Fast Etherenet/Modem</p> +</li> + +<li> +<p>TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card</p> +</li> + +<li> +<p>TDK DFL5610WS Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Telecom Device SuperSocket RE450T</p> +</li> + +<li> +<p>VIA VT86C926</p> +</li> + +<li> +<p>Winbond W89C940</p> +</li> +</ul> + +<p>C-Bus, ISA, PCI and PC Card devices are supported.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=el&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">el</span>(4)</span></a> driver supports +the 3Com 3c501 8bit ISA Ethernet card.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, +82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 controller +chips:</p> + +<ul> +<li> +<p>Intel PRO/1000 CT Network Connection (82547)</p> +</li> + +<li> +<p>Intel PRO/1000 F Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 Gigabit Server Adapter (82542)</p> +</li> + +<li> +<p>Intel PRO/1000 GT Desktop Adapter (82541PI)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (LX) (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82540)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82541)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Quad Port Server Adapter (82546EB)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 T Desktop Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 T Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 XF Server Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 XT Server Adapter (82544)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ep</span>(4)</span></a> driver supports +Ethernet adapters based on the 3Com 3C5x9 Etherlink III Parallel Tasking chipset, +including:</p> + +<ul> +<li> +<p>3Com 3C1 CF</p> +</li> + +<li> +<p>3Com 3C509-TP, 3C509-BNC, 3C509-Combo, 3C509-TPO, 3C509-TPC ISA</p> +</li> + +<li> +<p>3Com 3C509B-TP, 3C509B-BNC, 3C509B-Combo, 3C509B-TPO, 3C509B-TPC ISA</p> +</li> + +<li> +<p>3Com 3C529, 3C529-TP MCA</p> +</li> + +<li> +<p>3Com 3C562/3C563 PCMCIA</p> +</li> + +<li> +<p>3Com 3C569B-J-TPO, 3C569B-J-COMBO CBUS</p> +</li> + +<li> +<p>3Com 3C574, 3C574TX, 3C574-TX, 3CCFE574BT, 3CXFE574BT, 3C3FE574BT PCMCIA</p> +</li> + +<li> +<p>3Com 3C579-TP, 3C579-BNC EISA</p> +</li> + +<li> +<p>3Com 3C589, 3C589B, 3C589C, 3C589D, 3CXE589DT PCMCIA</p> +</li> + +<li> +<p>3Com 3CCFEM556B, 3CCFEM556BI PCMCIA</p> +</li> + +<li> +<p>3Com 3CXE589EC, 3CCE589EC, 3CXE589ET, 3CCE589ET PCMCIA</p> +</li> + +<li> +<p>3Com Megahertz 3CCEM556, 3CXEM556, 3CCEM556B, 3CXEM556B, 3C3FEM556C PCMCIA</p> +</li> + +<li> +<p>3Com OfficeConnect 3CXSH572BT, 3CCSH572BT PCMCIA</p> +</li> + +<li> +<p>Farallon EtherWave and EtherMac PC Card (P/n 595/895 with BLUE arrow)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ex&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ex</span>(4)</span></a> driver supports +the following Ethernet adapters:</p> + +<ul> +<li> +<p>Intel EtherExpress Pro/10</p> +</li> + +<li> +<p>Intel EtherExpress Pro/10+</p> +</li> + +<li> +<p>The Olicom OC2220</p> +</li> +</ul> + +<p>Controllers and cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">fe</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin)</p> +</li> + +<li> +<p>CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard)</p> +</li> + +<li> +<p>CONTEC C-NET(PC)C PCMCIA Ethernet</p> +</li> + +<li> +<p>Eagle Tech NE200T</p> +</li> + +<li> +<p>Eiger Labs EPX-10BT</p> +</li> + +<li> +<p>Fujitsu FMV-J182, FMV-J182A</p> +</li> + +<li> +<p>Fujitsu MB86960A, MB86965A</p> +</li> + +<li> +<p>Fujitsu MBH10303, MBH10302 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, and REX-R280</p> +</li> + +<li> +<p>RATOC REX-9880/9881/9882/9883</p> +</li> + +<li> +<p>TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin)</p> +</li> + +<li> +<p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p> +</li> + +<li> +<p>Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE N98(PC86132) +(110-pin)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel EtherExpress PRO/10</p> +</li> + +<li> +<p>Intel InBusiness 10/100</p> +</li> + +<li> +<p>Intel PRO/100B / EtherExpressPRO/100 B PCI 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>Contec C-NET(PI)-100TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B06 (PC-98)</p> +</li> + +<li> +<p>Many on-board network interfaces on Intel motherboards</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server +models. Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Sun PCI SunSwift Adapter</p> +</li> + +<li> +<p>Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)</p> +</li> + +<li> +<p>Sun PCI Sun100BaseT Adapter 2.0</p> +</li> + +<li> +<p>Sun SBus Sun100BaseT 2.0</p> +</li> + +<li> +<p>Sun PCI Quad FastEthernet Controller</p> +</li> + +<li> +<p>Sun SBus Quad FastEthernet Controller</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ie&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ie</span>(4)</span></a> driver provides +supports the following 8 and 16bit ISA Ethernet cards that are based on the Intel i82586 +chip:</p> + +<ul> +<li> +<p>3COM 3C507</p> +</li> + +<li> +<p>AT&T EN100</p> +</li> + +<li> +<p>AT&T Starlan 10</p> +</li> + +<li> +<p>AT&T Starlan Fiber</p> +</li> + +<li> +<p>Intel EtherExpress 16</p> +</li> + +<li> +<p>RACAL Interlan NI5210</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ixgb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ixgb</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>Intel PRO/10GbE LR Server Adapter</p> +</li> + +<li> +<p>Intel PRO/10GbE SR Server Adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kue</span>(4)</span></a> driver +supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>3Com 3c19250</p> +</li> + +<li> +<p>3Com 3c460 HomeConnect Ethernet USB Adapter</p> +</li> + +<li> +<p>ADS Technologies USB-10BT</p> +</li> + +<li> +<p>AOX USB101</p> +</li> + +<li> +<p>ATen UC10T</p> +</li> + +<li> +<p>Abocom URE 450</p> +</li> + +<li> +<p>Corega USB-T</p> +</li> + +<li> +<p>D-Link DSB-650C</p> +</li> + +<li> +<p>Entrega NET-USB-E45, NET-HUB-3U1E</p> +</li> + +<li> +<p>I/O Data USB ETT</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> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>SMC TigerCard 1000 (SMC9462SX)</p> +</li> + +<li> +<p>D-Link DGE-500SX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Diamond HomeFree</p> +</li> + +<li> +<p>Digital DEPCA</p> +</li> + +<li> +<p>Hewlett Packard Vectra 486/66XM</p> +</li> + +<li> +<p>Hewlett Packard Vectra XU</p> +</li> + +<li> +<p>Isolan AT 4141-0 (16 bit)</p> +</li> + +<li> +<p>Isolan BICC</p> +</li> + +<li> +<p>Isolink 4110 (8 bit)</p> +</li> + +<li> +<p>Novell NE2100</p> +</li> + +<li> +<p>Novell NE32-VL</p> +</li> +</ul> + +<p>Also supported are adapters working with the pcn(4) driver. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +runs these in compatibility mode, thus the pcn(4) driver should be preferred.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=my&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">my</span>(4)</span></a> driver provides +support for various NICs based on the Myson chipset. Supported models include:</p> + +<ul> +<li> +<p>Myson MTD800 PCI Fast Ethernet chip</p> +</li> + +<li> +<p>Myson MTD803 PCI Fast Ethernet chip</p> +</li> + +<li> +<p>Myson MTD89X PCI Gigabit Ethernet chip</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nge</span>(4)</span></a> driver +supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters +including:</p> + +<ul> +<li> +<p>Addtron AEG320T</p> +</li> + +<li> +<p>Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI)</p> +</li> + +<li> +<p>Asante FriendlyNet GigaNIX 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</p> +</li> + +<li> +<p>Netgear GA622T</p> +</li> + +<li> +<p>SMC EZ Card 1000 (SMC9462TX)</p> +</li> + +<li> +<p>Surecom Technology EP-320G-TX</p> +</li> + +<li> +<p>Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nve&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nve</span>(4)</span></a> driver +supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets:</p> + +<ul> +<li> +<p>nForce</p> +</li> + +<li> +<p>nForce2</p> +</li> + +<li> +<p>nForce3</p> +</li> + +<li> +<p>nForce4</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcn</span>(4)</span></a> driver +supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, +PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:</p> + +<ul> +<li> +<p>AMD Am79C971 PCnet-FAST</p> +</li> + +<li> +<p>AMD Am79C972 PCnet-FAST+</p> +</li> + +<li> +<p>AMD Am79C973/Am79C975 PCnet-FAST III</p> +</li> + +<li> +<p>AMD Am79C976 PCnet-PRO</p> +</li> + +<li> +<p>AMD Am79C978 PCnet-Home</p> +</li> + +<li> +<p>Allied-Telesis LA-PCI</p> +</li> + +<li> +<p>NEC SV-98/2-B05, B06</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">re</span>(4)</span></a> driver supports +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based Fast Ethernet and Gigabit +Ethernet adapters including:</p> + +<ul> +<li> +<p>Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)</p> +</li> + +<li> +<p>Compaq Evo N1015v Integrated Ethernet (8139C+)</p> +</li> + +<li> +<p>Corega CG-LAPCIGT Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>D-Link DGE-528(T) Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)</p> +</li> + +<li> +<p>LevelOne GNC-0105T (8169S)</p> +</li> + +<li> +<p>PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)</p> +</li> + +<li> +<p>Xterasys XN-152 10/100/1000 NIC (8169)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a> driver +include:</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>Belkin F5D5000</p> +</li> + +<li> +<p>BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)</p> +</li> + +<li> +<p>Compaq HNE-300</p> +</li> + +<li> +<p>CompUSA no-name 10/100 PCI Ethernet NIC</p> +</li> + +<li> +<p>Corega FEther CB-TXD</p> +</li> + +<li> +<p>Corega FEtherII CB-TXD</p> +</li> + +<li> +<p>D-Link DFE-528TX</p> +</li> + +<li> +<p>D-Link DFE-530TX+</p> +</li> + +<li> +<p>D-Link DFE-538TX</p> +</li> + +<li> +<p>D-Link DFE-690TXD</p> +</li> + +<li> +<p>Edimax EP-4103DL CardBus</p> +</li> + +<li> +<p>Encore ENL832-TX 10/100 M PCI</p> +</li> + +<li> +<p>Farallon NetLINE 10/100 PCI</p> +</li> + +<li> +<p>Genius GF100TXR</p> +</li> + +<li> +<p>GigaFast Ethernet EE100-AXP</p> +</li> + +<li> +<p>KTX-9130TX 10/100 Fast Ethernet</p> +</li> + +<li> +<p>LevelOne FPC-0106TX</p> +</li> + +<li> +<p>Longshine LCS-8038TX-R</p> +</li> + +<li> +<p>NDC Communications NE100TX-E</p> +</li> + +<li> +<p>Netronix Inc. EA-1210 NetEther 10/100</p> +</li> + +<li> +<p>Nortel Networks 10/100BaseTX</p> +</li> + +<li> +<p>OvisLink LEF-8129TX</p> +</li> + +<li> +<p>OvisLink LEF-8139TX</p> +</li> + +<li> +<p>Peppercon AG ROL-F</p> +</li> + +<li> +<p>Planex FNW-3800-TX</p> +</li> + +<li> +<p>SMC EZ Card 10/100 PCI 1211-TX</p> +</li> + +<li> +<p>SOHO (PRAGMATIC) UE-1211C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rue</span>(4)</span></a> driver +supports RealTek RTL8150 based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Buffalo (Melco Inc.) LUA-KTX</p> +</li> + +<li> +<p>Green House GH-USB100B</p> +</li> + +<li> +<p>LinkSys USB100M</p> +</li> + +<li> +<p>Billionton 10/100 FastEthernet USBKR2</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sf</span>(4)</span></a> driver +include:</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a> driver +supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and +embedded controllers, as well as Fast Ethernet adapters based on the National +Semiconductor DP83815 (MacPhyter) chip. Supported adapters include:</p> + +<ul> +<li> +<p>@Nifty FNECHARD IFC USUP-TX</p> +</li> + +<li> +<p>MELCO LGY-PCI-TXC</p> +</li> + +<li> +<p>Netgear FA311-TX (DP83815)</p> +</li> + +<li> +<p>Netgear FA312-TX (DP83815)</p> +</li> + +<li> +<p>SiS 630, 635, and 735 motherboard chipsets</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>3Com 3C940 single port, 1000baseT adapter</p> +</li> + +<li> +<p>3Com 3C2000-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Belkin F5D5005 single port, 1000baseT adapter</p> +</li> + +<li> +<p>D-Link DGE-530T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Linksys EG1032 single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9521 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9821 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9822 SK-NET GE-T dual port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9841 SK-NET GE-LX single port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9842 SK-NET GE-LX dual port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9843 SK-NET GE-SX single port, multimode fiber adapter</p> +</li> + +<li> +<p>SK-9844 SK-NET GE-SX dual port, multimode fiber adapter</p> +</li> + +<li> +<p>SMC 9452TX single port, 1000baseT adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sn</span>(4)</span></a> driver supports +SMC91Cxx based ISA and PCMCIA cards including:</p> + +<ul> +<li> +<p>3Com Megahertz X-Jack Ethernet PC-Card XJ10BT</p> +</li> + +<li> +<p>3Com Megahertz X-Jack Ethernet PC-Card XJ10BC</p> +</li> + +<li> +<p>Farallon EtherMac PC Card 595a</p> +</li> + +<li> +<p>Motorola Mariner Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Ositech Seven of Diamonds Ethernet PC Card</p> +</li> + +<li> +<p>Ositech Jack of Hearts Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Psion Gold Card Netglobal Ethernet PC Card</p> +</li> + +<li> +<p>Psion Gold Card Netglobal 10/100 Fast Ethernet PC Card</p> +</li> + +<li> +<p>Psion Gold Card Netglobal 56k+10Mb Ethernet PC Card</p> +</li> + +<li> +<p>SMC EZEther PC Card (8020BT)</p> +</li> + +<li> +<p>SMC EZEther PC Card (8020T)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sn</span>(4)</span></a> driver supports +the SMC 91C90, SMC 91C92, SMC 91C94, SMC 91C95, SMC 91C96, SMC91C100 and SMC 91C100FD +chips from SMC. The Farallon EtherWave and EtherMac card came in two varieties. The ep(4) +driver supports the 595 and 895 cards. These cards have the blue arrow on the front along +with a 3Com logo. The Farallon 595a cards, which have a red arrow on the front, are also +called EtherWave and EtherMac. They are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sn</span>(4)</span></a> driver.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ste</span>(4)</span></a> driver +supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded +controllers including:</p> + +<ul> +<li> +<p>D-Link DFE-530TXS</p> +</li> + +<li> +<p>D-Link DFE-550TX</p> +</li> + +<li> +<p>D-Link DFE-580TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ti</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Alteon Tigon I and II chips. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ti</span>(4)</span></a> driver has been +tested with the following adapters:</p> + +<ul> +<li> +<p>3Com 3c985-SX Gigabit Ethernet adapter (Tigon 1)</p> +</li> + +<li> +<p>3Com 3c985B-SX Gigabit Ethernet adapter (Tigon 2)</p> +</li> + +<li> +<p>Alteon AceNIC V Gigabit Ethernet adapter (1000baseSX)</p> +</li> + +<li> +<p>Alteon AceNIC V Gigabit Ethernet adapter (1000baseT)</p> +</li> + +<li> +<p>Digital EtherWORKS 1000SX PCI Gigabit adapter</p> +</li> + +<li> +<p>Netgear GA620 Gigabit Ethernet adapter (1000baseSX)</p> +</li> + +<li> +<p>Netgear GA620T Gigabit Ethernet adapter (1000baseT)</p> +</li> +</ul> + +<p>The following adapters should also be supported but have not yet been tested:</p> + +<ul> +<li> +<p>Asante GigaNIX1000T Gigabit Ethernet adapter</p> +</li> + +<li> +<p>Asante PCI 1000BASE-SX Gigabit Ethernet adapter</p> +</li> + +<li> +<p>Farallon PN9000SX Gigabit Ethernet adapter</p> +</li> + +<li> +<p>NEC Gigabit Ethernet</p> +</li> + +<li> +<p>Silicon Graphics PCI Gigabit Ethernet adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver supports +Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large +number of Compaq PCI Ethernet adapters. Also supported are:</p> + +<ul> +<li> +<p>Olicom OC-2135/2138 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Olicom OC-2325/OC-2326 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Racore 8148 10baseT/100baseTX/100baseFX adapter</p> +</li> + +<li> +<p>Racore 8165 10/100baseTX adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver also +supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq +Deskpro desktop machines including:</p> + +<ul> +<li> +<p>Compaq Netelligent 10</p> +</li> + +<li> +<p>Compaq Netelligent 10 T PCI UTP/Coax</p> +</li> + +<li> +<p>Compaq Netelligent 10/100</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Dual-Port</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Proliant</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX Embedded UTP</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX UTP</p> +</li> + +<li> +<p>Compaq NetFlex 3P</p> +</li> + +<li> +<p>Compaq NetFlex 3P Integrated</p> +</li> + +<li> +<p>Compaq NetFlex 3P w/BNC</p> +</li> +</ul> + +<p>SMC 83c17x (EPIC)-based Ethernet NICs (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tx</span>(4)</span></a> driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">txp</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>3Com 3CR990-TX-95</p> +</li> + +<li> +<p>3Com 3CR990-TX-97</p> +</li> + +<li> +<p>3Com 3cR990B-TXM</p> +</li> + +<li> +<p>3Com 3CR990SVR95</p> +</li> + +<li> +<p>3Com 3CR990SVR97</p> +</li> + +<li> +<p>3Com 3cR990B-SRV</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=udav&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">udav</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Corega FEther USB-TXC</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vge</span>(4)</span></a> driver +supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including:</p> + +<ul> +<li> +<p>VIA Networking LAN-on-motherboard Gigabit Ethernet</p> +</li> + +<li> +<p>ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701)</p> +</li> + +<li> +<p>ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vr</span>(4)</span></a> driver supports +VIA Technologies Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters +including:</p> + +<ul> +<li> +<p>AOpen/Acer ALN-320</p> +</li> + +<li> +<p>D-Link DFE530-TX</p> +</li> + +<li> +<p>Hawking Technologies PN102TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vx</span>(4)</span></a> driver supports +the following cards:</p> + +<ul> +<li> +<p>3Com 3c590 EtherLink III PCI</p> +</li> + +<li> +<p>3Com 3c592 EtherLink III EISA</p> +</li> + +<li> +<p>3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode</p> +</li> + +<li> +<p>3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wb</span>(4)</span></a> driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:</p> + +<ul> +<li> +<p>Trendware TE100-PCIE</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xe&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xe</span>(4)</span></a> driver supports +the following cards:</p> + +<ul> +<li> +<p>Xircom CreditCard Ethernet (PS-CE2-10)</p> +</li> + +<li> +<p>Xircom CreditCard Ethernet + Modem 28 (PS-CEM-28)</p> +</li> + +<li> +<p>Xircom CreditCard Ethernet + Modem 33 (CEM33)</p> +</li> + +<li> +<p>Xircom CreditCard 10/100 (CE3, CE3B)</p> +</li> + +<li> +<p>Xircom CreditCard Ethernet 10/100 + Modem 56 (CEM56)</p> +</li> + +<li> +<p>Xircom RealPort Ethernet 10 (RE10)</p> +</li> + +<li> +<p>Xircom RealPort Ethernet 10/100 (RE100)</p> +</li> + +<li> +<p>Xircom RealPort Ethernet 10/100 + Modem 56 (REM56, REM56G)</p> +</li> + +<li> +<p>Accton Fast EtherCard-16 (EN2226)</p> +</li> + +<li> +<p>Compaq Microcom CPQ550 Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 PC Card (CPQ-10/100)</p> +</li> + +<li> +<p>Intel EtherExpress Pro/100 PC Card Mobile Adapter 16 (Pro/100 M16A)</p> +</li> + +<li> +<p>Intel EtherExpress Pro/100 LAN/Modem PC Card Adapter (Pro/100 M16B)</p> +</li> +</ul> + +<p>Other similar devices using the same hardware may also be supported.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver supports +the following hardware:</p> + +<ul> +<li> +<p>3Com 3c900-TPO</p> +</li> + +<li> +<p>3Com 3c900-COMBO</p> +</li> + +<li> +<p>3Com 3c905-TX</p> +</li> + +<li> +<p>3Com 3c905-T4</p> +</li> + +<li> +<p>3Com 3c900B-TPO</p> +</li> + +<li> +<p>3Com 3c900B-TPC</p> +</li> + +<li> +<p>3Com 3c900B-FL</p> +</li> + +<li> +<p>3Com 3c900B-COMBO</p> +</li> + +<li> +<p>3Com 3c905B-T4</p> +</li> + +<li> +<p>3Com 3c905B-TX</p> +</li> + +<li> +<p>3Com 3c905B-FX</p> +</li> + +<li> +<p>3Com 3c905B-COMBO</p> +</li> + +<li> +<p>3Com 3c905C-TX</p> +</li> + +<li> +<p>3Com 3c980, 3c980B, and 3c980C server adapters</p> +</li> + +<li> +<p>3Com 3cSOHO100-TX OfficeConnect adapters</p> +</li> + +<li> +<p>3Com 3c450 HomeConnect adapters</p> +</li> + +<li> +<p>3Com 3c555, 3c556 and 3c556B mini-PCI adapters</p> +</li> + +<li> +<p>3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, +3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters</p> +</li> + +<li> +<p>3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded +adapters</p> +</li> +</ul> + +<p>Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a +built-in proprietary modem. Neither the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver nor any +other driver supports this modem.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="TOKENRING" name="TOKENRING">3.3 Token Ring Interfaces</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=oltr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">oltr</span>(4)</span></a> driver +supports the following ISA based Olicom Token Ring adapters:</p> + +<ul> +<li> +<p>Olicom OC-3115</p> +</li> + +<li> +<p>Olicom ISA 16/4 Adapter (OC-3117)</p> +</li> + +<li> +<p>Olicom ISA 16/4 Adapter (OC-3118)</p> +</li> +</ul> + +<p>The following PCI based adapters are supported:</p> + +<ul> +<li> +<p>Olicom PCI 16/4 Adapter (OC-3136)</p> +</li> + +<li> +<p>Olicom PCI/II 16/4 Adapter (OC-3137)</p> +</li> + +<li> +<p>Olicom PCI 16/4 Adapter (OC-3139)</p> +</li> + +<li> +<p>Olicom RapidFire 3140 16/4 PCI Adapter (OC-3140)</p> +</li> + +<li> +<p>Olicom RapidFire 3141 Fiber Adapter (OC-3141)</p> +</li> + +<li> +<p>Olicom RapidFire 3540 100/16/4 Adapter (OC-3540)</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FDDI" name="FDDI">3.4 FDDI Interfaces</a></h3> + +<p>DEC DEFPA PCI (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fpa</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ATM" name="ATM">3.5 ATM Interfaces</a></h3> + +<p>Midway-based ATM interfaces (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=en&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">en</span>(4)</span></a> driver)</p> + +<p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fatm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fatm</span>(4)</span></a> +drivers)</p> + +<p>IDT NICStAR 77201/211-based ATM Adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=idt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">idt</span>(4)</span></a> +driver)</p> + +<p>FORE Systems, Inc. HE155 and HE622 ATM interfaces (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hatm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hatm</span>(4)</span></a> +driver)</p> + +<p>IDT77252-based ATM cards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=patm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">patm</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="WLAN" name="WLAN">3.6 Wireless Network Interfaces</a></h3> + +<p>NCR / AT&T / Lucent Technologies WaveLan T1-speed ISA/radio LAN cards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wl</span>(4)</span></a> driver)</p> + +<p>Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes +using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and +Symbol Spectrum24 chipsets (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wi</span>(4)</span></a> driver)</p> + +<p>Cisco/Aironet 802.11b wireless adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">an</span>(4)</span></a> driver)</p> + +<p>Raytheon Raylink 2.4GHz wireless adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ray&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ray</span>(4)</span></a> +driver)</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=awi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">awi</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>BayStack 650</p> +</li> + +<li> +<p>BayStack 660</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</p> +</li> + +<li> +<p>Netwave AirSurfer Pro</p> +</li> + +<li> +<p>Nokia C020 WLAN</p> +</li> + +<li> +<p>Farallon SkyLINE</p> +</li> +</ul> + +<p>The original Xircom Netwave AirSurfer is supported by the cnw(4) driver.</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cnw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cnw</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Xircom CreditCard Netwave</p> +</li> + +<li> +<p>NetWave AirSurfer</p> +</li> +</ul> + +<p>The following cards are among those supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>Aztech WL830PC</p> +</li> + +<li> +<p>Cisco AIR-CB21AG</p> +</li> + +<li> +<p>Cisco AIR-PI21AG</p> +</li> + +<li> +<p>D-Link DWL-A650</p> +</li> + +<li> +<p>D-Link DWL-AB650</p> +</li> + +<li> +<p>D-Link DWL-A520</p> +</li> + +<li> +<p>D-Link DWL-AG520</p> +</li> + +<li> +<p>D-Link DWL-AG650</p> +</li> + +<li> +<p>D-Link DWL-G520B</p> +</li> + +<li> +<p>D-Link DWL-G650B</p> +</li> + +<li> +<p>Elecom LD-WL54AG</p> +</li> + +<li> +<p>Elecom LD-WL54</p> +</li> + +<li> +<p>Fujitsu E5454</p> +</li> + +<li> +<p>Fujitsu FMV-JW481</p> +</li> + +<li> +<p>Fujitsu E5454</p> +</li> + +<li> +<p>HP NC4000</p> +</li> + +<li> +<p>I/O Data WN-AB</p> +</li> + +<li> +<p>I/O Data WN-AG</p> +</li> + +<li> +<p>I/O Data WN-A54</p> +</li> + +<li> +<p>Linksys WMP55AG</p> +</li> + +<li> +<p>Linksys WPC51AB</p> +</li> + +<li> +<p>Linksys WPC55AG</p> +</li> + +<li> +<p>NEC PA-WL/54AG</p> +</li> + +<li> +<p>Netgear WAG311</p> +</li> + +<li> +<p>Netgear WAB501</p> +</li> + +<li> +<p>Netgear WAG511</p> +</li> + +<li> +<p>Netgear WG311T</p> +</li> + +<li> +<p>Netgear WG511T</p> +</li> + +<li> +<p>Orinoco 8480</p> +</li> + +<li> +<p>Orinoco 8470WD</p> +</li> + +<li> +<p>Proxim Skyline 4030</p> +</li> + +<li> +<p>Proxim Skyline 4032</p> +</li> + +<li> +<p>Samsung SWL-5200N</p> +</li> + +<li> +<p>SMC SMC2536W-AG</p> +</li> + +<li> +<p>SMC SMC2735W</p> +</li> + +<li> +<p>Sony PCWA-C700</p> +</li> + +<li> +<p>Sony PCWA-C300S</p> +</li> + +<li> +<p>Sony PCWA-C500</p> +</li> + +<li> +<p>3Com 3CRPAG175</p> +</li> +</ul> + +<p>An up to date list can be found at <a +href="http://customerproducts.atheros.com/customerproducts" +target="_top">http://customerproducts.atheros.com/customerproducts</a>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC-NETWORK" name="MISC-NETWORK">3.7 Miscellaneous +Networks</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ce&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ce</span>(4)</span></a> driver supports +the following models of Tau-PCI/32 WAN adapters:</p> + +<ul> +<li> +<p>Cronyx Tau-PCI/32</p> +</li> + +<li> +<p>Cronyx Tau-PCI/32-Lite</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">cx</span>(4)</span></a> driver supports +the following cards:</p> + +<ul> +<li> +<p>Cronyx Sigma-22, Sigma-24</p> +</li> + +<li> +<p>Cronyx Sigma-100</p> +</li> + +<li> +<p>Cronyx Sigma-400, Sigma-401, Sigma-404, Sigma-410, Sigma-440</p> +</li> + +<li> +<p>Cronyx Sigma-500</p> +</li> + +<li> +<p>Cronyx Sigma-703</p> +</li> + +<li> +<p>Cronyx Sigma-800, Sigma-801, Sigma-810, Sigma-840</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cp&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">cp</span>(4)</span></a> driver supports +the following models of Tau-PCI WAN adapters:</p> + +<ul> +<li> +<p>Cronyx Tau-PCI</p> +</li> + +<li> +<p>Cronyx Tau-PCI/R</p> +</li> + +<li> +<p>Cronyx Tau-PCI-L</p> +</li> + +<li> +<p>Cronyx Tau-PCI-L/R</p> +</li> + +<li> +<p>Cronyx Tau-PCI-E1</p> +</li> + +<li> +<p>Cronyx Tau-PCI-G703</p> +</li> + +<li> +<p>Cronyx Tau-PCI-2E1</p> +</li> + +<li> +<p>Cronyx Tau-PCI-4E1</p> +</li> + +<li> +<p>Cronyx Tau-PCI-E3</p> +</li> + +<li> +<p>Cronyx Tau-PCI-T3</p> +</li> + +<li> +<p>Cronyx Tau-PCI-STS1</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ctau&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ctau</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>Cronyx Tau (RS-232/V.35)</p> +</li> + +<li> +<p>Cronyx Tau/R (RS-530/RS-449)</p> +</li> + +<li> +<p>Cronyx Tau/E1 (fractional E1)</p> +</li> + +<li> +<p>Cronyx Tau/G703 (unframed E1)</p> +</li> +</ul> + +<p>Granch SBNI12 point-to-point communications adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sbni&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbni</span>(4)</span></a> +driver)</p> + +<p>Granch SBNI16 SHDSL modems (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sbsh&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbsh</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cm&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">cm</span>(4)</span></a> driver supports +the following card models:</p> + +<ul> +<li> +<p>SMC90c26</p> +</li> + +<li> +<p>SMC90c56</p> +</li> + +<li> +<p>SMC90c66 in '56 compatibility mode.</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ISDN" name="ISDN">3.8 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&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 ( < 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="SERIAL" name="SERIAL">3.9 Serial Interfaces</a></h3> + +<p>“PC standard” 8250, 16450, and 16550-based serial ports (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uart&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uart</span>(4)</span></a> driver +supports the following classes of UARTs:</p> + +<ul> +<li> +<p>NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 +UARTs</p> +</li> + +<li> +<p>SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.</p> +</li> + +<li> +<p>Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.</p> +</li> +</ul> + +<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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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 (digi driver)</p> + +<p>PCI-Based multi-port serial boards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=puc&sektion=4&manpath=FreeBSD+6.1-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, Smartio C104H-PCI 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>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rc</span>(4)</span></a> driver provides +support for the SDL Communications RISCom/8 boards.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sr&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sr</span>(4)</span></a> driver supports +the following hardware:</p> + +<ul> +<li> +<p>SDL Communications RISCom/N2 ISA</p> +</li> + +<li> +<p>SDL Communications N2pci</p> +</li> + +<li> +<p>SDL Communications WANic 400/405 PCI</p> +</li> +</ul> + +<p>Specialix SI/XIO/SX multiport serial cards, with both the older SIHOST2.x and the +“enhanced” (transputer based, aka JET) host cards (ISA, EISA and PCI) are +supported. Note that the newer SX+ PCI cards are not currently supported. (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=si&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">si</span>(4)</span></a> driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SOUND" name="SOUND">3.10 Sound Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ad1816&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ad1816</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Analog Devices AD1816</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_als4000&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_als4000</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Avance Logic ALS4000</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver supports the following audio chipsets:</p> + +<ul> +<li> +<p>ATI IXP 200</p> +</li> + +<li> +<p>ATI IXP 300</p> +</li> + +<li> +<p>ATI IXP 400</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_cmi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_cmi</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>CMedia CMI8338A</p> +</li> + +<li> +<p>CMedia CMI8338B</p> +</li> + +<li> +<p>CMedia CMI8738</p> +</li> + +<li> +<p>CMedia CMI8738B</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_cs4281&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_cs4281</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Crystal Semiconductor CS4281</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_csa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_csa</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Crystal Semiconductor CS4280</p> +</li> + +<li> +<p>Crystal Semiconductor CS4610</p> +</li> + +<li> +<p>Crystal Semiconductor CS4611</p> +</li> + +<li> +<p>Crystal Semiconductor CS4614</p> +</li> + +<li> +<p>Crystal Semiconductor CS4615</p> +</li> + +<li> +<p>Crystal Semiconductor CS4622</p> +</li> + +<li> +<p>Crystal Semiconductor CS4624</p> +</li> + +<li> +<p>Crystal Semiconductor CS4630</p> +</li> + +<li> +<p>Genius Soundmaker 128 Value</p> +</li> + +<li> +<p>Hercules Game Theatre XP</p> +</li> + +<li> +<p>Turtle Beach Santa Cruz</p> +</li> +</ul> + +<p>Some onboard CS4610 chips are accompanied by the CS423x ISA codec instead of the +CS4297 AC97 codec. Such configurations are not supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_csa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_csa</span>(4)</span></a> +driver yet.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ds1&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ds1</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Yamaha DS-1</p> +</li> + +<li> +<p>Yamaha DS-1E</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_emu10k1&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_emu10k1</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Creative SoundBlaster Live! (EMU10K1 Chipset)</p> +</li> + +<li> +<p>Creative SoundBlaster Audigy (EMU10K2 Chipset)</p> +</li> + +<li> +<p>Creative SoundBlaster Audigy 2 (EMU10K2 Chipset)</p> +</li> + +<li> +<p>Creative SoundBlaster Audigy 2 (EMU10K3 Chipset)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Creative CT5880-A</p> +</li> + +<li> +<p>Creative CT5880-C</p> +</li> + +<li> +<p>Creative CT5880-D</p> +</li> + +<li> +<p>Creative CT5880-E</p> +</li> + +<li> +<p>Creative SB AudioPCI CT4730</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1370</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1371-A</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1371-B</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-A</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-B</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-8</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ess&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ess</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Ensoniq ESS ISA PnP/non-PnP</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_fm801&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_fm801</span>(4)</span></a> +driver supports audio devices based on the following chipset:</p> + +<ul> +<li> +<p>Forte Media FM801</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_gusc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_gusc</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Gravis UltraSound MAX</p> +</li> + +<li> +<p>Gravis UltraSound PnP</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>AMD 768</p> +</li> + +<li> +<p>AMD 8111</p> +</li> + +<li> +<p>Intel 443MX</p> +</li> + +<li> +<p>Intel ICH</p> +</li> + +<li> +<p>Intel ICH revision 1</p> +</li> + +<li> +<p>Intel ICH2</p> +</li> + +<li> +<p>Intel ICH3</p> +</li> + +<li> +<p>Intel ICH4</p> +</li> + +<li> +<p>Intel ICH5</p> +</li> + +<li> +<p>Intel ICH6</p> +</li> + +<li> +<p>Intel ICH7</p> +</li> + +<li> +<p>NVIDIA nForce</p> +</li> + +<li> +<p>NVIDIA nForce2</p> +</li> + +<li> +<p>NVIDIA nForce2 400</p> +</li> + +<li> +<p>NVIDIA nForce3</p> +</li> + +<li> +<p>NVIDIA nForce3 250</p> +</li> + +<li> +<p>NVIDIA nForce4</p> +</li> + +<li> +<p>SiS 7012</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_maestro&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_maestro</span>(4)</span></a> +driver supports the following PCI sound cards:</p> + +<ul> +<li> +<p>ESS Technology Maestro-1</p> +</li> + +<li> +<p>ESS Technology Maestro-2</p> +</li> + +<li> +<p>ESS Technology Maestro-2E</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_maestro3&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_maestro3</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>ESS Technology Allegro-1</p> +</li> + +<li> +<p>ESS Technology Maestro3</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_mss&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_mss</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>AD1845</p> +</li> + +<li> +<p>AD1848</p> +</li> + +<li> +<p>Aztech 2320</p> +</li> + +<li> +<p>CMedia CMI8330</p> +</li> + +<li> +<p>Crystal Semiconductor CS4231</p> +</li> + +<li> +<p>Crystal Semiconductor CS4232</p> +</li> + +<li> +<p>Crystal Semiconductor CS4234</p> +</li> + +<li> +<p>Crystal Semiconductor CS4235</p> +</li> + +<li> +<p>Crystal Semiconductor CS4236</p> +</li> + +<li> +<p>Crystal Semiconductor CS4237</p> +</li> + +<li> +<p>ENSONIQ SoundscapeVIVO ENS4081</p> +</li> + +<li> +<p>NeoMagic 256AV (non-AC97)</p> +</li> + +<li> +<p>OPTi 924</p> +</li> + +<li> +<p>OPTi 925</p> +</li> + +<li> +<p>OPTi 930</p> +</li> + +<li> +<p>OPTi 931</p> +</li> + +<li> +<p>OPTi 933</p> +</li> + +<li> +<p>Yamaha OPL-SA2</p> +</li> + +<li> +<p>Yamaha OPL-SA3</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_neomagic&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_neomagic</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>NeoMagic 256AV</p> +</li> + +<li> +<p>NeoMagic 256ZX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_sbc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_sbc</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Avance Asound 110</p> +</li> + +<li> +<p>Avance Logic ALS100+</p> +</li> + +<li> +<p>Avance Logic ALS120</p> +</li> + +<li> +<p>Creative SB16</p> +</li> + +<li> +<p>Creative SB32</p> +</li> + +<li> +<p>Creative AWE64</p> +</li> + +<li> +<p>Creative AWE64 Gold</p> +</li> + +<li> +<p>Creative ViBRA16C</p> +</li> + +<li> +<p>Creative ViBRA16X</p> +</li> + +<li> +<p>ESS ES1681</p> +</li> + +<li> +<p>ESS ES1688</p> +</li> + +<li> +<p>ESS ES1868</p> +</li> + +<li> +<p>ESS ES1869</p> +</li> + +<li> +<p>ESS ES1878</p> +</li> + +<li> +<p>ESS ES1879</p> +</li> + +<li> +<p>ESS ES1888</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>ESS Solo-1 (ES1938 Chipset)</p> +</li> + +<li> +<p>ESS Solo-1E (ES1946 Chipset)</p> +</li> +</ul> + +<p>Note that older ESS ISA cards with ES18xx chipset are supported via snd_ess(4) and/or +snd_sbc(4).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_t4dwave&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_t4dwave</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>Acer Labs M5451</p> +</li> + +<li> +<p>SIS 7018</p> +</li> + +<li> +<p>Trident 4DWave DX</p> +</li> + +<li> +<p>Trident 4DWave NX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via8233&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via8233</span>(4)</span></a> +driver supports the following audio chipsets:</p> + +<ul> +<li> +<p>VIA VT8233</p> +</li> + +<li> +<p>VIA VT8233A</p> +</li> + +<li> +<p>VIA VT8233C</p> +</li> + +<li> +<p>VIA VT8235</p> +</li> + +<li> +<p>VIA VT8237</p> +</li> + +<li> +<p>VIA VT8251</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver supports audio devices based on the following chipset:</p> + +<ul> +<li> +<p>VIA 82C686A</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_vibes&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_vibes</span>(4)</span></a> +driver supports audio devices based on the following chipset:</p> + +<ul> +<li> +<p>S3 SonicVibes</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CAMERA" name="CAMERA">3.11 Camera and Video Capture +Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bktr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bktr</span>(4)</span></a> driver +supports video capture cards based on the Brooktree Bt848/849/878/879 chips, as well as +Pinnacle PCTV cards, including:</p> + +<ul> +<li> +<p>AOpen VA1000</p> +</li> + +<li> +<p>AVerMedia AVerTV Studio</p> +</li> + +<li> +<p>AVerMedia TF/FM-98</p> +</li> + +<li> +<p>ATI TV Wonder VE</p> +</li> + +<li> +<p>Hauppauge WinCast/TV</p> +</li> + +<li> +<p>Hauppauge WinTV-Go-FM</p> +</li> + +<li> +<p>Hauppauge WinTV-pci</p> +</li> + +<li> +<p>Hauppauge WinTV-radio</p> +</li> + +<li> +<p>Intel Smart Video Recorder III</p> +</li> + +<li> +<p>KWORLD PCI TV Tuner</p> +</li> + +<li> +<p>Miro PC TV</p> +</li> + +<li> +<p>Pinnacle PCTV Pro</p> +</li> + +<li> +<p>Pinnacle PCTV Rave</p> +</li> + +<li> +<p>PixelView PlayTV PAK</p> +</li> + +<li> +<p>PixelView PlayTV Pro (rev 4C, 9D)</p> +</li> + +<li> +<p>SIGMA TV II</p> +</li> + +<li> +<p>STB TV PCI Television Tuner</p> +</li> + +<li> +<p>Super TV Tuner</p> +</li> + +<li> +<p>TerraTec TValue</p> +</li> + +<li> +<p>V-Stream XPERT TV-PVR 878</p> +</li> + +<li> +<p>Video Highway XTreme</p> +</li> + +<li> +<p>VideoLogic Captivator PCI</p> +</li> +</ul> + +<p>Connectix QuickCam</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USB" name="USB">3.12 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> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> USB Bluetooth adapters can be found in <a href="#BLUETOOTH">Bluetooth</a> +section.</p> +</blockquote> +</div> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a> driver +supports all OHCI v1.0 compliant controllers including:</p> + +<ul> +<li> +<p>AcerLabs M5237 (Aladdin-V)</p> +</li> + +<li> +<p>AMD-756</p> +</li> + +<li> +<p>OPTi 82C861 (FireLink)</p> +</li> + +<li> +<p>NEC uPD 9210</p> +</li> + +<li> +<p>CMD Tech 670 (USB0670)</p> +</li> + +<li> +<p>CMD Tech 673 (USB0673)</p> +</li> + +<li> +<p>NVIDIA nForce3</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO USB)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a> driver +supports all UHCI v1.1 compliant controllers including:</p> + +<ul> +<li> +<p>Intel 82371AB/EB (PIIX4)</p> +</li> + +<li> +<p>Intel 82371SB (PIIX3)</p> +</li> + +<li> +<p>VIA 83C572</p> +</li> +</ul> + +<p>USB 2.0 controllers using the EHCI interface (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ehci</span>(4)</span></a> +driver)</p> + +<p>Hubs</p> + +<p>Keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> + +<p>Miscellaneous</p> + +<ul> +<li> +<p>Assist Computer Systems PC Camera C-M1</p> +</li> + +<li> +<p>ActiveWire I/O Board</p> +</li> + +<li> +<p>Creative Technology Video Blaster WebCam Plus</p> +</li> + +<li> +<p>D-Link DSB-R100 USB Radio (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ufm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ufm</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>Mirunet AlphaCam Plus</p> +</li> +</ul> + +<br /> +<br /> +<p>The following devices are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=urio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">urio</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>Diamond MultiMedia Rio 500</p> +</li> + +<li> +<p>Diamond MultiMedia Rio 600</p> +</li> + +<li> +<p>Diamond MultiMedia Rio 800</p> +</li> +</ul> + +<p>Devices supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umodem&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umodem</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>3Com 5605</p> +</li> + +<li> +<p>Metricom Ricochet GS USB wireless modem</p> +</li> + +<li> +<p>Yamaha Broadband Wireless Router RTW65b</p> +</li> + +<li> +<p>ELSA MicroLink 56k USB modem</p> +</li> +</ul> + +<p>Mice (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ulpt</span>(4)</span></a> driver +provides support for USB printers and parallel printer conversion cables, including the +following:</p> + +<ul> +<li> +<p>ATen parallel printer adapter</p> +</li> + +<li> +<p>Belkin F5U002 parallel printer adapter</p> +</li> + +<li> +<p>Canon BJ F850, S600</p> +</li> + +<li> +<p>Canon LBP-1310, 350</p> +</li> + +<li> +<p>Entrega USB-to-parallel printer adapter</p> +</li> + +<li> +<p>Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)</p> +</li> + +<li> +<p>Oki Data MICROLINE ML660PS</p> +</li> + +<li> +<p>Seiko Epson PM-900C, 880C, 820C, 730C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsa</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U103</p> +</li> + +<li> +<p>Belkin F5U120</p> +</li> + +<li> +<p>e-Tek Labs Kwik232</p> +</li> + +<li> +<p>GoHubs GoCOM232</p> +</li> + +<li> +<p>Peracom single port serial adapter</p> +</li> + +<li> +<p>Vodafone Mobile Connect 3G datacard</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubser&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubser</span>(4)</span></a> driver +provides support for the BWCT console management serial adapters.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uftdi</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>B&B Electronics USB->RS422/485 adapter</p> +</li> + +<li> +<p>HP USB-Serial adapter shipped with some HP laptops</p> +</li> + +<li> +<p>Inland UAS111</p> +</li> + +<li> +<p>QVS USC-1000</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uplcom&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uplcom</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>ATEN UC-232A</p> +</li> + +<li> +<p>BAFO BF-800</p> +</li> + +<li> +<p>BAFO BF-810</p> +</li> + +<li> +<p>ELECOM UC-SGT</p> +</li> + +<li> +<p>HAL Corporation Crossam2+USB IR commander</p> +</li> + +<li> +<p>Hama USB RS-232 Serial Adapter</p> +</li> + +<li> +<p>IOGEAR UC-232A</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ2</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ3</p> +</li> + +<li> +<p>PLANEX USB-RS232 URS-03</p> +</li> + +<li> +<p>RATOC REX-USB60</p> +</li> + +<li> +<p>Sandberg USB to Serial Link (model number 133-08)</p> +</li> + +<li> +<p>SOURCENEXT KeikaiDenwa 8 (with and without charger)</p> +</li> + +<li> +<p>Sony Ericsson USB Cable (Susteen USB Data Cable)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umct&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umct</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U109</p> +</li> + +<li> +<p>Belkin F5U409</p> +</li> + +<li> +<p>D-Link DU-H3SP USB BAY Hub</p> +</li> + +<li> +<p>Magic Control Technology USB-232</p> +</li> + +<li> +<p>Sitecom USB-232</p> +</li> +</ul> + +<p>The following devices are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uscanner&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uscanner</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>Acer Acerscan 320U</p> +</li> + +<li> +<p>Acer Acerscan 620U</p> +</li> + +<li> +<p>Acer Acerscan 640U</p> +</li> + +<li> +<p>Acer Acerscan 1240U</p> +</li> + +<li> +<p>Acer Acerscan C310U</p> +</li> + +<li> +<p>AGFA SnapScan 1212U</p> +</li> + +<li> +<p>AGFA SnapScan 1236U</p> +</li> + +<li> +<p>AGFA SnapScan e20</p> +</li> + +<li> +<p>AGFA SnapScan e25</p> +</li> + +<li> +<p>AGFA SnapScan e26</p> +</li> + +<li> +<p>AGFA SnapScan e40</p> +</li> + +<li> +<p>AGFA SnapScan e50</p> +</li> + +<li> +<p>AGFA SnapScan e52</p> +</li> + +<li> +<p>AGFA SnapScan Touch</p> +</li> + +<li> +<p>Avision 1200U</p> +</li> + +<li> +<p>Canon CanoScan N656U</p> +</li> + +<li> +<p>Canon CanoScan N676U</p> +</li> + +<li> +<p>Canon CanoScan N1220U</p> +</li> + +<li> +<p>Canon CanoScan LIDE 20</p> +</li> + +<li> +<p>Canon CanoScan LIDE 30</p> +</li> + +<li> +<p>Epson Perfection 610</p> +</li> + +<li> +<p>Epson Perfection 636U / 636Photo</p> +</li> + +<li> +<p>Epson Perfection 640U</p> +</li> + +<li> +<p>Epson Perfection 1200U / 1200Photo</p> +</li> + +<li> +<p>Epson Perfection 1240U / 1240Photo</p> +</li> + +<li> +<p>Epson Perfection 1250</p> +</li> + +<li> +<p>Epson Perfection 1260</p> +</li> + +<li> +<p>Epson Expression 1600</p> +</li> + +<li> +<p>Epson Perfection 1640SU</p> +</li> + +<li> +<p>Epson Perfection 1650</p> +</li> + +<li> +<p>Epson Perfection 1660</p> +</li> + +<li> +<p>Epson Perfection 1670</p> +</li> + +<li> +<p>Epson Perfection 3200</p> +</li> + +<li> +<p>Epson GT-8400UF</p> +</li> + +<li> +<p>Epson GT-9300UF</p> +</li> + +<li> +<p>Epson GT-9700F</p> +</li> + +<li> +<p>Hewlett Packard Photosmart S20</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 2200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 3300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 3400CSE</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4100C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5400C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 6200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 6300C</p> +</li> + +<li> +<p>KYE ColorPage Vivid-Pro</p> +</li> + +<li> +<p>Microtek Phantom 336CX</p> +</li> + +<li> +<p>Microtek Phantom C6</p> +</li> + +<li> +<p>Microtek ScanMaker V6UL</p> +</li> + +<li> +<p>Microtek ScanMaker V6USL</p> +</li> + +<li> +<p>Microtek ScanMaker X6U</p> +</li> + +<li> +<p>Minolta 5400</p> +</li> + +<li> +<p>Mustek 600 CU</p> +</li> + +<li> +<p>Mustek 1200 CU</p> +</li> + +<li> +<p>Mustek 1200 UB</p> +</li> + +<li> +<p>Mustek 1200 USB</p> +</li> + +<li> +<p>Mustek BearPaw 1200F</p> +</li> + +<li> +<p>Mustek BearPaw 1200TA</p> +</li> + +<li> +<p>NatSemi BearPaw 1200</p> +</li> + +<li> +<p>Nikon CoolScan LS40 ED</p> +</li> + +<li> +<p>Primax 6200</p> +</li> + +<li> +<p>Primax Colorado 1200u</p> +</li> + +<li> +<p>Primax Colorado 600u</p> +</li> + +<li> +<p>Primax Colorado USB 19200</p> +</li> + +<li> +<p>Primax Colorado USB 9600</p> +</li> + +<li> +<p>Primax G2-200</p> +</li> + +<li> +<p>Primax G2-300</p> +</li> + +<li> +<p>Primax G2-600</p> +</li> + +<li> +<p>Primax G2600</p> +</li> + +<li> +<p>Primax G2E-300</p> +</li> + +<li> +<p>Primax G2E-3002</p> +</li> + +<li> +<p>Primax G2E-600</p> +</li> + +<li> +<p>Primax G2E600</p> +</li> + +<li> +<p>Primax G2X-300</p> +</li> + +<li> +<p>Primax G600</p> +</li> + +<li> +<p>Primax ReadyScan 636i</p> +</li> + +<li> +<p>Ultima 1200 UB Plus</p> +</li> + +<li> +<p>UMAX Astra 1220U</p> +</li> + +<li> +<p>UMAX Astra 1236U</p> +</li> + +<li> +<p>UMAX Astra 2000U</p> +</li> + +<li> +<p>UMAX Astra 2100U</p> +</li> + +<li> +<p>UMAX Astra 2200U</p> +</li> + +<li> +<p>UMAX Astra 3400</p> +</li> + +<li> +<p>Visioneer OneTouch 3000</p> +</li> + +<li> +<p>Visioneer OneTouch 5300</p> +</li> + +<li> +<p>Visioneer OneTouch 7600</p> +</li> + +<li> +<p>Visioneer OneTouch 6100</p> +</li> + +<li> +<p>Visioneer OneTouch 6200</p> +</li> + +<li> +<p>Visioneer OneTouch 8100</p> +</li> + +<li> +<p>Visioneer OneTouch 8600</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umass</span>(4)</span></a> driver +supports USB Mass Storage devices, including:</p> + +<ul> +<li> +<p>ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M</p> +</li> + +<li> +<p>Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20</p> +</li> + +<li> +<p>FujiFilm Zip USB Drive ZDR100 USB A</p> +</li> + +<li> +<p>GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M</p> +</li> + +<li> +<p>IBM 32MB USB Memory Key (P/N 22P5296)</p> +</li> + +<li> +<p>IBM 256MB USB Drive (MSYSTEM DiskOnKey2)</p> +</li> + +<li> +<p>IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)</p> +</li> + +<li> +<p>I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)</p> +</li> + +<li> +<p>I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)</p> +</li> + +<li> +<p>I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI</p> +</li> + +<li> +<p>Iomega USB Zip 100/250 drive</p> +</li> + +<li> +<p>Iomega Zip750 USB2.0 drive</p> +</li> + +<li> +<p>Keian USB1.1/2.0 3.5-inch HDD Case KU350A</p> +</li> + +<li> +<p>Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0</p> +</li> + +<li> +<p>LaCie P3 HardDrive USB 200GB</p> +</li> + +<li> +<p>Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive</p> +</li> + +<li> +<p>Logitec Mobile USB Memory LMC-256UD</p> +</li> + +<li> +<p>Logitec USB1.1/2.0 HDD Unit SHD-E60U2</p> +</li> + +<li> +<p>Logitec USB Double-Speed Floppy Drive LFD-31U2</p> +</li> + +<li> +<p>Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)</p> +</li> + +<li> +<p>MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M</p> +</li> + +<li> +<p>MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm</p> +</li> + +<li> +<p>MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2</p> +</li> + +<li> +<p>MELCO USB2.0 MO Drive MO-CH640U2</p> +</li> + +<li> +<p>Matshita CF-VFDU03 floppy drive</p> +</li> + +<li> +<p>Merlin SM300 MP3/WMA Player (256Mb)</p> +</li> + +<li> +<p>Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable</p> +</li> + +<li> +<p>Motorola E398 Mobile Phone (TransFlash memory card)</p> +</li> + +<li> +<p>NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U</p> +</li> + +<li> +<p>PNY Attache Flash Drive</p> +</li> + +<li> +<p>Panasonic ("Matshita FDD CF-VFDU03")</p> +</li> + +<li> +<p>Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW</p> +</li> + +<li> +<p>Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW)</p> +</li> + +<li> +<p>Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)</p> +</li> + +<li> +<p>Panasonic floppy drive</p> +</li> + +<li> +<p>Qware BeatZkey! Pro</p> +</li> + +<li> +<p>RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B</p> +</li> + +<li> +<p>SanDisk SDDR-31 (Compact Flash)</p> +</li> + +<li> +<p>SanDisk SDDR-75 (only Compact Flash port works)</p> +</li> + +<li> +<p>Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick)</p> +</li> + +<li> +<p>Sony Portable CD-R/RW Drive CRX10U (CDROM only)</p> +</li> + +<li> +<p>TEAC Portable USB CD-ROM Unit CD-110PU/210PU</p> +</li> + +<li> +<p>Time DPA20B MP3 Player (1Gb)</p> +</li> + +<li> +<p>Trek Thumbdrive 8MB</p> +</li> + +<li> +<p>VAIO floppy drive (includes Y-E Data Flashbuster-U)</p> +</li> + +<li> +<p>Y-E Data floppy drive (720/1.44/2.88Mb)</p> +</li> +</ul> + +<p>Among the supported digital cameras are:</p> + +<ul> +<li> +<p>Asahi Optical (PENTAX) Optio 230 & 330</p> +</li> +</ul> + +<p>Audio Devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uaudio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uaudio</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uvisor&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uvisor</span>(4)</span></a> driver +supports the following devices:</p> + +<ul> +<li> +<p>Handspring Treo</p> +</li> + +<li> +<p>Handspring Treo 600</p> +</li> + +<li> +<p>Handspring Visor</p> +</li> + +<li> +<p>Palm I705</p> +</li> + +<li> +<p>Palm M125</p> +</li> + +<li> +<p>Palm M130</p> +</li> + +<li> +<p>Palm M500</p> +</li> + +<li> +<p>Palm M505</p> +</li> + +<li> +<p>Palm M515</p> +</li> + +<li> +<p>Palm Tungsten T</p> +</li> + +<li> +<p>Palm Tungsten Z</p> +</li> + +<li> +<p>Palm Zire</p> +</li> + +<li> +<p>Palm Zire 31</p> +</li> + +<li> +<p>Sony Clie 4.0</p> +</li> + +<li> +<p>Sony Clie 4.1</p> +</li> + +<li> +<p>Sony Clie 5.0</p> +</li> + +<li> +<p>Sony Clie PEG-S500C</p> +</li> + +<li> +<p>Sony Clie NX60</p> +</li> + +<li> +<p>Sony Clie S360</p> +</li> + +<li> +<p>Sony Clie TJ37</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.13 IEEE 1394 (Firewire) +Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fwohci</span>(4)</span></a> driver +provides support for PCI/CardBus FireWire interface cards. The driver supports the +following IEEE 1394 OHCI chipsets:</p> + +<ul> +<li> +<p>Adaptec AHA-894x/AIC-5800</p> +</li> + +<li> +<p>Apple Pangea</p> +</li> + +<li> +<p>Apple UniNorth</p> +</li> + +<li> +<p>Intel 82372FB</p> +</li> + +<li> +<p>IOGEAR GUF320</p> +</li> + +<li> +<p>Lucent / Agere FW322/323</p> +</li> + +<li> +<p>NEC uPD72861</p> +</li> + +<li> +<p>NEC uPD72870</p> +</li> + +<li> +<p>NEC uPD72871/2</p> +</li> + +<li> +<p>NEC uPD72873</p> +</li> + +<li> +<p>NEC uPD72874</p> +</li> + +<li> +<p>National Semiconductor CS4210</p> +</li> + +<li> +<p>Ricoh R5C551</p> +</li> + +<li> +<p>Ricoh R5C552</p> +</li> + +<li> +<p>Sony CX3022</p> +</li> + +<li> +<p>Sony i.LINK (CXD1947)</p> +</li> + +<li> +<p>Sony i.LINK (CXD3222)</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO 1394)</p> +</li> + +<li> +<p>Texas Instruments PCI4410A</p> +</li> + +<li> +<p>Texas Instruments PCI4450</p> +</li> + +<li> +<p>Texas Instruments PCI4451</p> +</li> + +<li> +<p>Texas Instruments TSB12LV22</p> +</li> + +<li> +<p>Texas Instruments TSB12LV23</p> +</li> + +<li> +<p>Texas Instruments TSB12LV26</p> +</li> + +<li> +<p>Texas Instruments TSB43AA22</p> +</li> + +<li> +<p>Texas Instruments TSB43AB21/A/AI/A-EP</p> +</li> + +<li> +<p>Texas Instruments TSB43AB22/A</p> +</li> + +<li> +<p>Texas Instruments TSB43AB23</p> +</li> + +<li> +<p>Texas Instruments TSB82AA2</p> +</li> + +<li> +<p>VIA Fire II (VT6306)</p> +</li> +</ul> + +<p>Serial Bus Protocol 2 (SBP-2) storage devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sbp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbp</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.14 Bluetooth Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_bt3c&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_bt3c</span>(4)</span></a> +driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_ubt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_ubt</span>(4)</span></a> driver +supports all Bluetooth USB devices that conform with the Bluetooth specification v1.1, +including:</p> + +<ul> +<li> +<p>3Com 3CREB96</p> +</li> + +<li> +<p>AIPTEK BR0R02</p> +</li> + +<li> +<p>EPoX BT-DG02</p> +</li> + +<li> +<p>Mitsumi Bluetooth USB adapter</p> +</li> + +<li> +<p>MSI MS-6967</p> +</li> + +<li> +<p>TDK Bluetooth USB adapter</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CRYPTO-ACCEL" name="CRYPTO-ACCEL">3.15 Cryptographic +Accelerators</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hifn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hifn</span>(4)</span></a> driver +supports various cards containing the Hifn 7751, 7951, 7811, 7955, and 7956 chipsets, +such as:</p> + +<ul> +<li> +<p>Invertex AEON</p> +</li> + +<li> +<p>Hifn 7751</p> +</li> + +<li> +<p>PowerCrypt</p> +</li> + +<li> +<p>XL-Crypt</p> +</li> + +<li> +<p>NetSec 7751</p> +</li> + +<li> +<p>Soekris Engineering vpn1201 and vpn1211</p> +</li> + +<li> +<p>Soekris Engineering vpn1401 and vpn1411</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=safe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">safe</span>(4)</span></a> driver +supports cards containing any of the following chips:</p> + +<ul> +<li> +<p>SafeNet 1141</p> +</li> + +<li> +<p>SafeNet 1741</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsec</span>(4)</span></a> driver +supports cards containing any of the following chips:</p> + +<ul> +<li> +<p>Bluesteel 5501</p> +</li> + +<li> +<p>Bluesteel 5601</p> +</li> + +<li> +<p>Broadcom BCM5801</p> +</li> + +<li> +<p>Broadcom BCM5802</p> +</li> + +<li> +<p>Broadcom BCM5805</p> +</li> + +<li> +<p>Broadcom BCM5820</p> +</li> + +<li> +<p>Broadcom BCM5821</p> +</li> + +<li> +<p>Broadcom BCM5822</p> +</li> + +<li> +<p>Broadcom BCM5823</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC" name="MISC">3.16 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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>USB keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<br /> +<br /> +<p>Pointing devices including:</p> + +<ul> +<li> +<p>Bus mice and compatible devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mse&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mse</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>PS/2 mice and compatible devices, including many laptop pointing devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+6.1-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 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.org/</a>.</p> +</blockquote> +</div> + +<br /> +<br /> +<p>“PC standard” parallel ports (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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>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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/hardware-ia64.html b/en/releases/6.1R/hardware-ia64.html new file mode 100644 index 0000000000..5fccd17160 --- /dev/null +++ b/en/releases/6.1R/hardware-ia64.html @@ -0,0 +1,2674 @@ +<!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/ia64 6.1-RELEASE Hardware Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/ia64 6.1-RELEASE Hardware +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<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="#PROC-IA64">Supported Processors and Motherboards</a></dt> + +<dd> +<dl> +<dt>2.1 <a href="#AEN37">Supported Devices Overview</a></dt> +</dl> +</dd> + +<dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + +<dd> +<dl> +<dt>3.1 <a href="#DISK">Disk Controllers</a></dt> + +<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt> + +<dt>3.3 <a href="#TOKENRING">Token Ring Interfaces</a></dt> + +<dt>3.4 <a href="#FDDI">FDDI Interfaces</a></dt> + +<dt>3.5 <a href="#ATM">ATM Interfaces</a></dt> + +<dt>3.6 <a href="#WLAN">Wireless Network Interfaces</a></dt> + +<dt>3.7 <a href="#MISC-NETWORK">Miscellaneous Networks</a></dt> + +<dt>3.8 <a href="#ISDN">ISDN Interfaces</a></dt> + +<dt>3.9 <a href="#SERIAL">Serial Interfaces</a></dt> + +<dt>3.10 <a href="#SOUND">Sound Devices</a></dt> + +<dt>3.11 <a href="#CAMERA">Camera and Video Capture Devices</a></dt> + +<dt>3.12 <a href="#USB">USB Devices</a></dt> + +<dt>3.13 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt> + +<dt>3.14 <a href="#BLUETOOTH">Bluetooth Devices</a></dt> + +<dt>3.15 <a href="#CRYPTO-ACCEL">Cryptographic Accelerators</a></dt> + +<dt>3.16 <a href="#MISC">Miscellaneous</a></dt> +</dl> +</dd> +</dl> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a> +<p>This is a preliminary document. It is incomplete, and in need of additional content. +Please send additional information on IA-64 processors, motherboards, and various devices +working on FreeBSD to the <a +href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ia64" target="_top">FreeBSD IA64 +porting mailing list</a>.</p> +</div> +</blockquote> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This document contains the hardware compatibility notes for FreeBSD 6.1-RELEASE on the +IA-64 hardware platform (also referred to as FreeBSD/ia64 6.1-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 IA-64 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.</p> +</blockquote> +</div> + +<p>More information on FreeBSD/ia64 is contained on the <a +href="http://www.FreeBSD.org/platforms/ia64/index.html" target="_top">FreeBSD/ia64 +Project</a> page.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="PROC-IA64" name="PROC-IA64">2 Supported Processors and +Motherboards</a></h2> + +<p>Currently supported processors are the <a +href="http://people.freebsd.org/~marcel/refs/ia64/itanium/24532003.pdf" +target="_top">Itanium</a> and the <a +href="http://people.freebsd.org/~marcel/refs/ia64/itanium2/25111003.pdf" +target="_top">Itanium 2</a>.</p> + +<p>Supported chipsets include:</p> + +<ul> +<li> +<p>HP zx1</p> +</li> + +<li> +<p>Intel 460GX</p> +</li> + +<li> +<p>Intel E8870</p> +</li> +</ul> + +<p>Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) configurations are +supported.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN37" name="AEN37">2.1 Supported Devices Overview</a></h3> + +<p>Most devices that can be found in or are compatible with ia64 machines are fully +supported. The notable exception is the VGA console. The FreeBSD support for VGA consoles +is at this time too much based on PC hardware and not all ia64 machines have chipsets +that provide sufficient PC legacy support. As such <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> can +not be enabled and the use of a serial console is required.</p> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2> + +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.9.2.2 +2006/05/01 08:26:00 brueffer Exp $ + +<p>This section describes the devices currently known to be supported by with FreeBSD on +the IA-64 platform. Other configurations may also work, but simply have not been tested +yet. Feedback, updates, and corrections to this list are encouraged.</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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> The device lists in this document are being generated automatically from +FreeBSD manual pages. This means that some devices, which are supported by multiple +drivers, may appear multiple times.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DISK" name="DISK">3.1 Disk Controllers</a></h3> + +<p>IDE/ATA controllers (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> +driver)</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aac</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec AAC-364</p> +</li> + +<li> +<p>Adaptec SATA RAID 2410SA</p> +</li> + +<li> +<p>Adaptec SATA RAID 2810SA</p> +</li> + +<li> +<p>Adaptec SATA RAID 21610SA</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2120S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2130S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2200S</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2130SLP</p> +</li> + +<li> +<p>Adaptec SCSI RAID 2230SLP</p> +</li> + +<li> +<p>Adaptec SCSI RAID 5400S</p> +</li> + +<li> +<p>Dell CERC SATA RAID 2</p> +</li> + +<li> +<p>Dell PERC 2/Si</p> +</li> + +<li> +<p>Dell PERC 2/QC</p> +</li> + +<li> +<p>Dell PERC 3/Si</p> +</li> + +<li> +<p>Dell PERC 3/Di</p> +</li> + +<li> +<p>Dell PERC 320/DC</p> +</li> + +<li> +<p>HP NetRAID 4M</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a> driver +supports the following SCSI host adapter chips and SCSI controller cards:</p> + +<ul> +<li> +<p>Adaptec AIC7770 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7850 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7860 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7870 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7880 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7890 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7891 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7892 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7895 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7896 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7897 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7899 host adapter chip</p> +</li> + +<li> +<p>Adaptec 274X(W)</p> +</li> + +<li> +<p>Adaptec 274X(T)</p> +</li> + +<li> +<p>Adaptec 284X</p> +</li> + +<li> +<p>Adaptec 2910</p> +</li> + +<li> +<p>Adaptec 2915</p> +</li> + +<li> +<p>Adaptec 2920</p> +</li> + +<li> +<p>Adaptec 2930C</p> +</li> + +<li> +<p>Adaptec 2930U2</p> +</li> + +<li> +<p>Adaptec 2940</p> +</li> + +<li> +<p>Adaptec 2940J</p> +</li> + +<li> +<p>Adaptec 2940N</p> +</li> + +<li> +<p>Adaptec 2940U</p> +</li> + +<li> +<p>Adaptec 2940AU</p> +</li> + +<li> +<p>Adaptec 2940UW</p> +</li> + +<li> +<p>Adaptec 2940UW Dual</p> +</li> + +<li> +<p>Adaptec 2940UW Pro</p> +</li> + +<li> +<p>Adaptec 2940U2W</p> +</li> + +<li> +<p>Adaptec 2940U2B</p> +</li> + +<li> +<p>Adaptec 2950U2W</p> +</li> + +<li> +<p>Adaptec 2950U2B</p> +</li> + +<li> +<p>Adaptec 19160B</p> +</li> + +<li> +<p>Adaptec 29160B</p> +</li> + +<li> +<p>Adaptec 29160N</p> +</li> + +<li> +<p>Adaptec 3940</p> +</li> + +<li> +<p>Adaptec 3940U</p> +</li> + +<li> +<p>Adaptec 3940AU</p> +</li> + +<li> +<p>Adaptec 3940UW</p> +</li> + +<li> +<p>Adaptec 3940AUW</p> +</li> + +<li> +<p>Adaptec 3940U2W</p> +</li> + +<li> +<p>Adaptec 3950U2</p> +</li> + +<li> +<p>Adaptec 3960</p> +</li> + +<li> +<p>Adaptec 39160</p> +</li> + +<li> +<p>Adaptec 3985</p> +</li> + +<li> +<p>Adaptec 4944UW</p> +</li> + +<li> +<p>NEC PC-9821Xt13 (PC-98)</p> +</li> + +<li> +<p>NEC RvII26 (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B02L/B09 (PC-98)</p> +</li> + +<li> +<p>NEC SV-98/2-B03 (PC-98)</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahd</span>(4)</span></a> driver +supports the following:</p> + +<ul> +<li> +<p>Adaptec AIC7901 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7901A host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7902 host adapter chip</p> +</li> + +<li> +<p>Adaptec 29320 host adapter</p> +</li> + +<li> +<p>Adaptec 39320 host adapter</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MegaRAID SCSI 320-1E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-8X</p> +</li> + +<li> +<p>MegaRAID SATA 150-4</p> +</li> + +<li> +<p>MegaRAID SATA 150-6</p> +</li> + +<li> +<p>MegaRAID i4 133 RAID</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0</p> +</li> + +<li> +<p>MegaRAID SCSI 320-1</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4</p> +</li> + +<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 Elite 1650 (Series 4xx)</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 3/QC</p> +</li> + +<li> +<p>Dell PERC 4/DC</p> +</li> + +<li> +<p>Dell PERC 4/IM</p> +</li> + +<li> +<p>Dell PERC 4/SC</p> +</li> + +<li> +<p>Dell PERC 4/Di</p> +</li> + +<li> +<p>Dell PERC 4e/DC</p> +</li> + +<li> +<p>Dell PERC 4e/Di</p> +</li> + +<li> +<p>Dell PERC 4e/Si</p> +</li> + +<li> +<p>Dell PERC 4ei</p> +</li> + +<li> +<p>HP NetRAID-1/Si</p> +</li> + +<li> +<p>HP NetRAID-3/Si (D4943A)</p> +</li> + +<li> +<p>HP Embedded NetRAID</p> +</li> + +<li> +<p>Intel RAID Controller SRCS16</p> +</li> + +<li> +<p>Intel RAID Controller SRCU42X</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ciss&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ciss</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Compaq Smart Array 5300</p> +</li> + +<li> +<p>Compaq Smart Array 532</p> +</li> + +<li> +<p>Compaq Smart Array 5i</p> +</li> + +<li> +<p>HP Smart Array 5312</p> +</li> + +<li> +<p>HP Smart Array 6i</p> +</li> + +<li> +<p>HP Smart Array 641</p> +</li> + +<li> +<p>HP Smart Array 642</p> +</li> + +<li> +<p>HP Smart Array 6400</p> +</li> + +<li> +<p>HP Smart Array 6400 EM</p> +</li> + +<li> +<p>HP Smart Array E400</p> +</li> + +<li> +<p>HP Smart Array P600</p> +</li> + +<li> +<p>HP Smart Array P800</p> +</li> + +<li> +<p>HP Modular Smart Array 20 (MSA20)</p> +</li> + +<li> +<p>HP Modular Smart Array 500 (MSA500)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dpt</span>(4)</span></a> driver +provides support for the following RAID adapters:</p> + +<ul> +<li> +<p>DPT Smart Cache Plus</p> +</li> + +<li> +<p>Smart Cache II (PM2?2?, PM2022 [EISA], PM2024/PM2124 [PCI]) (Gen2)</p> +</li> + +<li> +<p>Smart RAID II (PM3?2?, PM3021, PM3222)</p> +</li> + +<li> +<p>Smart Cache III (PM2?3?)</p> +</li> + +<li> +<p>Smart RAID III (PM3?3?, PM3332 [EISA], PM3334UW [PCI]) (Gen3)</p> +</li> + +<li> +<p>Smart Cache IV (PM2?4?, PM2042 [EISA], PM2044/PM2144 [PCI]) (Gen4)</p> +</li> + +<li> +<p>Smart RAID IV</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">iir</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel RAID Controller SRCMR</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-l (SRCU31a)</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-1L (SRCU31La)</p> +</li> + +<li> +<p>Intel Server RAID Controller U3-2 (SRCU32)</p> +</li> + +<li> +<p>All past and future releases of Intel and ICP RAID Controllers.</p> +</li> +</ul> + +<ul> +<li> +<p>Intel RAID Controller SRCU21 (discontinued)</p> +</li> + +<li> +<p>Intel RAID Controller SRCU31 (older revision, not compatible)</p> +</li> + +<li> +<p>Intel RAID Controller SRCU31L (older revision, not compatible)</p> +</li> +</ul> + +<p>The SRCU31 and SRCU31L can be updated via a firmware update available from Intel.</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>ISP1000</p> +</li> + +<li> +<p>ISP1020</p> +</li> + +<li> +<p>ISP1040</p> +</li> + +<li> +<p>Qlogic 1240</p> +</li> + +<li> +<p>Qlogic 1020</p> +</li> + +<li> +<p>Qlogic 1040</p> +</li> + +<li> +<p>Qlogic 1080</p> +</li> + +<li> +<p>Qlogic 1280</p> +</li> + +<li> +<p>Qlogic 12160</p> +</li> + +<li> +<p>Qlogic 210X</p> +</li> + +<li> +<p>Qlogic 220X</p> +</li> + +<li> +<p>Qlogic 2300</p> +</li> + +<li> +<p>Qlogic 2312</p> +</li> + +<li> +<p>Qlogic 234X</p> +</li> + +<li> +<p>Qlogic 2322</p> +</li> + +<li> +<p>Qlogic 200</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver +supports the following hardware:</p> + +<ul> +<li> +<p>LSI MegaRAID SAS 8408E</p> +</li> + +<li> +<p>LSI MegaRAID SAS 8480E</p> +</li> + +<li> +<p>Dell PERC5/i</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mlx</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Mylex DAC960P</p> +</li> + +<li> +<p>Mylex DAC960PD / DEC KZPSC (Fast Wide)</p> +</li> + +<li> +<p>Mylex DAC960PDU</p> +</li> + +<li> +<p>Mylex DAC960PL</p> +</li> + +<li> +<p>Mylex DAC960PJ</p> +</li> + +<li> +<p>Mylex DAC960PG</p> +</li> + +<li> +<p>Mylex DAC960PU / DEC PZPAC (Ultra Wide)</p> +</li> + +<li> +<p>Mylex AcceleRAID 150 (DAC960PRL)</p> +</li> + +<li> +<p>Mylex AcceleRAID 250 (DAC960PTL1)</p> +</li> + +<li> +<p>Mylex eXtremeRAID 1100 (DAC1164P)</p> +</li> + +<li> +<p>RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA +(3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)</p> +</li> +</ul> + +<p>All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is +always advisable to upgrade to the most recent firmware available for the controller. +Compatible Mylex controllers not listed should work, but have not been verified.</p> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mly</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Mylex AcceleRAID 160</p> +</li> + +<li> +<p>Mylex AcceleRAID 170</p> +</li> + +<li> +<p>Mylex AcceleRAID 352</p> +</li> + +<li> +<p>Mylex eXtremeRAID 2000</p> +</li> + +<li> +<p>Mylex eXtremeRAID 3000</p> +</li> +</ul> + +<p>Compatible Mylex controllers not listed should work, but have not been verified.</p> + +<p>The following controllers are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>LSI Logic 53c1030 (Dual Ultra320 SCSI)</p> +</li> + +<li> +<p>LSI Logic FC909 (1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC909A (Dual 1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC919 (2Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC929, LSI Logic FC929X (Dual 2Gb/s Fibre Channel)</p> +</li> +</ul> + +<p>The SCSI controller chips supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver +can be found onboard on many systems including:</p> + +<ul> +<li> +<p>Dell PowerEdge 1750</p> +</li> + +<li> +<p>IBM eServer xSeries 335</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> driver +provides support for the following Symbios/LSI Logic PCI SCSI controllers:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C825</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C876</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C897</p> +</li> + +<li> +<p>53C1000</p> +</li> + +<li> +<p>53C1000R</p> +</li> + +<li> +<p>53C1010-33</p> +</li> + +<li> +<p>53C1010-66</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The SCSI controllers supported by <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> can be +either embedded on a motherboard, or on one of the following add-on boards:</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>I-O DATA SC-UPCI (PC-98)</p> +</li> + +<li> +<p>Logitec LHA-521UA (PC-98)</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> + +<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&sektion=4&manpath=FreeBSD+6.1-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&sektion=1&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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aue</span>(4)</span></a> driver +include:</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-T, FEther USB-TX, FEther USB-TXS</p> +</li> + +<li> +<p>D-Link DSB-650, DSB-650TX, DSB-650TX-PNA</p> +</li> + +<li> +<p>Elecom LD-USBL/TX</p> +</li> + +<li> +<p>Elsa Microlink USB2Ethernet</p> +</li> + +<li> +<p>HP hn210e</p> +</li> + +<li> +<p>I-O Data USB ETTX</p> +</li> + +<li> +<p>Kingston KNU101TX</p> +</li> + +<li> +<p>LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, +USB100TX, USB100H1</p> +</li> + +<li> +<p>MELCO LUA-TX, LUA2-TX</p> +</li> + +<li> +<p>Planex UE-200TX</p> +</li> + +<li> +<p>Sandberg USB to Network Link (model number 133-06)</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +provides support for various NICs based on the Broadcom BCM570x family of Gigabit +Ethernet controller chips, including the following:</p> + +<ul> +<li> +<p>3Com 3c996-T (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Netgear GA302T (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D21 (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D41 (1000baseSX)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cue</span>(4)</span></a> driver +supports CATC USB-EL1210A based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Belkin F5U011/F5U111</p> +</li> + +<li> +<p>CATC Netmate</p> +</li> + +<li> +<p>CATC Netmate II</p> +</li> + +<li> +<p>SmartBridges SmartLink</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver provides +support for the following chipsets:</p> + +<ul> +<li> +<p>DEC/Intel 21143</p> +</li> + +<li> +<p>ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II</p> +</li> + +<li> +<p>ASIX Electronics AX88140A and AX88141</p> +</li> + +<li> +<p>Conexant LANfinity RS7112 (miniPCI)</p> +</li> + +<li> +<p>Davicom DM9009, DM9100, DM9102 and DM9102A</p> +</li> + +<li> +<p>Lite-On 82c168 and 82c169 PNIC</p> +</li> + +<li> +<p>Lite-On/Macronix 82c115 PNIC II</p> +</li> + +<li> +<p>Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732</p> +</li> + +<li> +<p>Xircom X3201 (cardbus only)</p> +</li> +</ul> + +<p>The following NICs are known to work with the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver at this +time:</p> + +<ul> +<li> +<p>3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Abocom FE2500</p> +</li> + +<li> +<p>Accton EN1217 (98715A)</p> +</li> + +<li> +<p>Accton EN2242 MiniPCI</p> +</li> + +<li> +<p>Adico AE310TX (98715A)</p> +</li> + +<li> +<p>Alfa Inc GFC2204 (ASIX AX88140A)</p> +</li> + +<li> +<p>Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, +non-MII)</p> +</li> + +<li> +<p>Built in DE500-BA on DEC Alpha workstations (21143, non-MII)</p> +</li> + +<li> +<p>Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, +MII)</p> +</li> + +<li> +<p>Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)</p> +</li> + +<li> +<p>CNet Pro110B (ASIX AX88140A)</p> +</li> + +<li> +<p>CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)</p> +</li> + +<li> +<p>Compex RL100-TX (98713 or 98713A)</p> +</li> + +<li> +<p>D-Link DFE-570TX (21143, MII, quad port)</p> +</li> + +<li> +<p>Digital DE500-BA 10/100 (21143, non-MII)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CBL/TXA (ADMtek AN985)</p> +</li> + +<li> +<p>Hawking CB102 CardBus</p> +</li> + +<li> +<p>IBM EtherJet Cardbus Adapter</p> +</li> + +<li> +<p>Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)</p> +</li> + +<li> +<p>Jaton XpressNet (Davicom DM9102)</p> +</li> + +<li> +<p>Kingston KNE100TX (21143, MII)</p> +</li> + +<li> +<p>Kingston KNE110TX (PNIC 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX v2.0 (PNIC II 82c115)</p> +</li> + +<li> +<p>LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Matrox FastNIC 10/100 (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>Melco LGY-PCI-TXL</p> +</li> + +<li> +<p>Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)</p> +</li> + +<li> +<p>Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A (98713A)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A Rev B4 (98715AEC-C)</p> +</li> + +<li> +<p>NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)</p> +</li> + +<li> +<p>Netgear FA511</p> +</li> + +<li> +<p>PlaneX FNW-3602-T (ADMtek AN985)</p> +</li> + +<li> +<p>SMC EZ Card 10/100 1233A-TX (ADMtek AN985)</p> +</li> + +<li> +<p>SVEC PN102-TX (98713)</p> +</li> + +<li> +<p>Xircom Cardbus Realport</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet 10/100</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet II 10/100</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec ANA-6944/TX</p> +</li> + +<li> +<p>Cogent EM100FX and EM440TX</p> +</li> + +<li> +<p>Corega FastEther PCI-TX</p> +</li> + +<li> +<p>D-Link DFE-500TX</p> +</li> + +<li> +<p>DEC DE435, DEC DE450, and DEC DE500</p> +</li> + +<li> +<p>ELECOM LD-PCI2T, LD-PCITS</p> +</li> + +<li> +<p>I-O DATA LA2/T-PCI</p> +</li> + +<li> +<p>SMC Etherpower 8432, 9332 and 9334</p> +</li> + +<li> +<p>ZNYX ZX3xx</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, +82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 controller +chips:</p> + +<ul> +<li> +<p>Intel PRO/1000 CT Network Connection (82547)</p> +</li> + +<li> +<p>Intel PRO/1000 F Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 Gigabit Server Adapter (82542)</p> +</li> + +<li> +<p>Intel PRO/1000 GT Desktop Adapter (82541PI)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (LX) (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82540)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82541)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Quad Port Server Adapter (82546EB)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 T Desktop Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 T Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 XF Server Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 XT Server Adapter (82544)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel EtherExpress PRO/10</p> +</li> + +<li> +<p>Intel InBusiness 10/100</p> +</li> + +<li> +<p>Intel PRO/100B / EtherExpressPRO/100 B PCI 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>Contec C-NET(PI)-100TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B06 (PC-98)</p> +</li> + +<li> +<p>Many on-board network interfaces on Intel motherboards</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server +models. Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Sun PCI SunSwift Adapter</p> +</li> + +<li> +<p>Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)</p> +</li> + +<li> +<p>Sun PCI Sun100BaseT Adapter 2.0</p> +</li> + +<li> +<p>Sun SBus Sun100BaseT 2.0</p> +</li> + +<li> +<p>Sun PCI Quad FastEthernet Controller</p> +</li> + +<li> +<p>Sun SBus Quad FastEthernet Controller</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kue</span>(4)</span></a> driver +supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>3Com 3c19250</p> +</li> + +<li> +<p>3Com 3c460 HomeConnect Ethernet USB Adapter</p> +</li> + +<li> +<p>ADS Technologies USB-10BT</p> +</li> + +<li> +<p>AOX USB101</p> +</li> + +<li> +<p>ATen UC10T</p> +</li> + +<li> +<p>Abocom URE 450</p> +</li> + +<li> +<p>Corega USB-T</p> +</li> + +<li> +<p>D-Link DSB-650C</p> +</li> + +<li> +<p>Entrega NET-USB-E45, NET-HUB-3U1E</p> +</li> + +<li> +<p>I/O Data USB ETT</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcn</span>(4)</span></a> driver +supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, +PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:</p> + +<ul> +<li> +<p>AMD Am79C971 PCnet-FAST</p> +</li> + +<li> +<p>AMD Am79C972 PCnet-FAST+</p> +</li> + +<li> +<p>AMD Am79C973/Am79C975 PCnet-FAST III</p> +</li> + +<li> +<p>AMD Am79C976 PCnet-PRO</p> +</li> + +<li> +<p>AMD Am79C978 PCnet-Home</p> +</li> + +<li> +<p>Allied-Telesis LA-PCI</p> +</li> + +<li> +<p>NEC SV-98/2-B05, B06</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">re</span>(4)</span></a> driver supports +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based Fast Ethernet and Gigabit +Ethernet adapters including:</p> + +<ul> +<li> +<p>Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)</p> +</li> + +<li> +<p>Compaq Evo N1015v Integrated Ethernet (8139C+)</p> +</li> + +<li> +<p>Corega CG-LAPCIGT Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>D-Link DGE-528(T) Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)</p> +</li> + +<li> +<p>LevelOne GNC-0105T (8169S)</p> +</li> + +<li> +<p>PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)</p> +</li> + +<li> +<p>Xterasys XN-152 10/100/1000 NIC (8169)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a> driver +include:</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>Belkin F5D5000</p> +</li> + +<li> +<p>BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)</p> +</li> + +<li> +<p>Compaq HNE-300</p> +</li> + +<li> +<p>CompUSA no-name 10/100 PCI Ethernet NIC</p> +</li> + +<li> +<p>Corega FEther CB-TXD</p> +</li> + +<li> +<p>Corega FEtherII CB-TXD</p> +</li> + +<li> +<p>D-Link DFE-528TX</p> +</li> + +<li> +<p>D-Link DFE-530TX+</p> +</li> + +<li> +<p>D-Link DFE-538TX</p> +</li> + +<li> +<p>D-Link DFE-690TXD</p> +</li> + +<li> +<p>Edimax EP-4103DL CardBus</p> +</li> + +<li> +<p>Encore ENL832-TX 10/100 M PCI</p> +</li> + +<li> +<p>Farallon NetLINE 10/100 PCI</p> +</li> + +<li> +<p>Genius GF100TXR</p> +</li> + +<li> +<p>GigaFast Ethernet EE100-AXP</p> +</li> + +<li> +<p>KTX-9130TX 10/100 Fast Ethernet</p> +</li> + +<li> +<p>LevelOne FPC-0106TX</p> +</li> + +<li> +<p>Longshine LCS-8038TX-R</p> +</li> + +<li> +<p>NDC Communications NE100TX-E</p> +</li> + +<li> +<p>Netronix Inc. EA-1210 NetEther 10/100</p> +</li> + +<li> +<p>Nortel Networks 10/100BaseTX</p> +</li> + +<li> +<p>OvisLink LEF-8129TX</p> +</li> + +<li> +<p>OvisLink LEF-8139TX</p> +</li> + +<li> +<p>Peppercon AG ROL-F</p> +</li> + +<li> +<p>Planex FNW-3800-TX</p> +</li> + +<li> +<p>SMC EZ Card 10/100 PCI 1211-TX</p> +</li> + +<li> +<p>SOHO (PRAGMATIC) UE-1211C</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sf</span>(4)</span></a> driver +include:</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a> driver +supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and +embedded controllers, as well as Fast Ethernet adapters based on the National +Semiconductor DP83815 (MacPhyter) chip. Supported adapters include:</p> + +<ul> +<li> +<p>@Nifty FNECHARD IFC USUP-TX</p> +</li> + +<li> +<p>MELCO LGY-PCI-TXC</p> +</li> + +<li> +<p>Netgear FA311-TX (DP83815)</p> +</li> + +<li> +<p>Netgear FA312-TX (DP83815)</p> +</li> + +<li> +<p>SiS 630, 635, and 735 motherboard chipsets</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">txp</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>3Com 3CR990-TX-95</p> +</li> + +<li> +<p>3Com 3CR990-TX-97</p> +</li> + +<li> +<p>3Com 3cR990B-TXM</p> +</li> + +<li> +<p>3Com 3CR990SVR95</p> +</li> + +<li> +<p>3Com 3CR990SVR97</p> +</li> + +<li> +<p>3Com 3cR990B-SRV</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vx</span>(4)</span></a> driver supports +the following cards:</p> + +<ul> +<li> +<p>3Com 3c590 EtherLink III PCI</p> +</li> + +<li> +<p>3Com 3c592 EtherLink III EISA</p> +</li> + +<li> +<p>3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode</p> +</li> + +<li> +<p>3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver supports +the following hardware:</p> + +<ul> +<li> +<p>3Com 3c900-TPO</p> +</li> + +<li> +<p>3Com 3c900-COMBO</p> +</li> + +<li> +<p>3Com 3c905-TX</p> +</li> + +<li> +<p>3Com 3c905-T4</p> +</li> + +<li> +<p>3Com 3c900B-TPO</p> +</li> + +<li> +<p>3Com 3c900B-TPC</p> +</li> + +<li> +<p>3Com 3c900B-FL</p> +</li> + +<li> +<p>3Com 3c900B-COMBO</p> +</li> + +<li> +<p>3Com 3c905B-T4</p> +</li> + +<li> +<p>3Com 3c905B-TX</p> +</li> + +<li> +<p>3Com 3c905B-FX</p> +</li> + +<li> +<p>3Com 3c905B-COMBO</p> +</li> + +<li> +<p>3Com 3c905C-TX</p> +</li> + +<li> +<p>3Com 3c980, 3c980B, and 3c980C server adapters</p> +</li> + +<li> +<p>3Com 3cSOHO100-TX OfficeConnect adapters</p> +</li> + +<li> +<p>3Com 3c450 HomeConnect adapters</p> +</li> + +<li> +<p>3Com 3c555, 3c556 and 3c556B mini-PCI adapters</p> +</li> + +<li> +<p>3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, +3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters</p> +</li> + +<li> +<p>3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded +adapters</p> +</li> +</ul> + +<p>Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a +built-in proprietary modem. Neither the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver nor any +other driver supports this modem.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="TOKENRING" name="TOKENRING">3.3 Token Ring Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FDDI" name="FDDI">3.4 FDDI Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ATM" name="ATM">3.5 ATM Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="WLAN" name="WLAN">3.6 Wireless Network Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC-NETWORK" name="MISC-NETWORK">3.7 Miscellaneous +Networks</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ISDN" name="ISDN">3.8 ISDN Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SERIAL" name="SERIAL">3.9 Serial Interfaces</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uart&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uart</span>(4)</span></a> driver +supports the following classes of UARTs:</p> + +<ul> +<li> +<p>NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 +UARTs</p> +</li> + +<li> +<p>SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.</p> +</li> + +<li> +<p>Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.</p> +</li> +</ul> + +<p>PCI-Based multi-port serial boards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=puc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">puc</span>(4)</span></a> +driver)</p> + +<ul> +<li> +<p>Diva Serial (GSP) Multiport UART</p> +</li> +</ul> + +<br /> +<br /> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SOUND" name="SOUND">3.10 Sound Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CAMERA" name="CAMERA">3.11 Camera and Video Capture +Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USB" name="USB">3.12 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> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> USB Bluetooth adapters can be found in <a href="#BLUETOOTH">Bluetooth</a> +section.</p> +</blockquote> +</div> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a> driver +supports all OHCI v1.0 compliant controllers including:</p> + +<ul> +<li> +<p>AcerLabs M5237 (Aladdin-V)</p> +</li> + +<li> +<p>AMD-756</p> +</li> + +<li> +<p>OPTi 82C861 (FireLink)</p> +</li> + +<li> +<p>NEC uPD 9210</p> +</li> + +<li> +<p>CMD Tech 670 (USB0670)</p> +</li> + +<li> +<p>CMD Tech 673 (USB0673)</p> +</li> + +<li> +<p>NVIDIA nForce3</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO USB)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a> driver +supports all UHCI v1.1 compliant controllers including:</p> + +<ul> +<li> +<p>Intel 82371AB/EB (PIIX4)</p> +</li> + +<li> +<p>Intel 82371SB (PIIX3)</p> +</li> + +<li> +<p>VIA 83C572</p> +</li> +</ul> + +<p>USB 2.0 controllers using the EHCI interface (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ehci</span>(4)</span></a> +driver)</p> + +<p>Hubs</p> + +<p>Keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> + +<p>Mice (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umct&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umct</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U109</p> +</li> + +<li> +<p>Belkin F5U409</p> +</li> + +<li> +<p>D-Link DU-H3SP USB BAY Hub</p> +</li> + +<li> +<p>Magic Control Technology USB-232</p> +</li> + +<li> +<p>Sitecom USB-232</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.13 IEEE 1394 (Firewire) +Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fwohci</span>(4)</span></a> driver +provides support for PCI/CardBus FireWire interface cards. The driver supports the +following IEEE 1394 OHCI chipsets:</p> + +<ul> +<li> +<p>Adaptec AHA-894x/AIC-5800</p> +</li> + +<li> +<p>Apple Pangea</p> +</li> + +<li> +<p>Apple UniNorth</p> +</li> + +<li> +<p>Intel 82372FB</p> +</li> + +<li> +<p>IOGEAR GUF320</p> +</li> + +<li> +<p>Lucent / Agere FW322/323</p> +</li> + +<li> +<p>NEC uPD72861</p> +</li> + +<li> +<p>NEC uPD72870</p> +</li> + +<li> +<p>NEC uPD72871/2</p> +</li> + +<li> +<p>NEC uPD72873</p> +</li> + +<li> +<p>NEC uPD72874</p> +</li> + +<li> +<p>National Semiconductor CS4210</p> +</li> + +<li> +<p>Ricoh R5C551</p> +</li> + +<li> +<p>Ricoh R5C552</p> +</li> + +<li> +<p>Sony CX3022</p> +</li> + +<li> +<p>Sony i.LINK (CXD1947)</p> +</li> + +<li> +<p>Sony i.LINK (CXD3222)</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO 1394)</p> +</li> + +<li> +<p>Texas Instruments PCI4410A</p> +</li> + +<li> +<p>Texas Instruments PCI4450</p> +</li> + +<li> +<p>Texas Instruments PCI4451</p> +</li> + +<li> +<p>Texas Instruments TSB12LV22</p> +</li> + +<li> +<p>Texas Instruments TSB12LV23</p> +</li> + +<li> +<p>Texas Instruments TSB12LV26</p> +</li> + +<li> +<p>Texas Instruments TSB43AA22</p> +</li> + +<li> +<p>Texas Instruments TSB43AB21/A/AI/A-EP</p> +</li> + +<li> +<p>Texas Instruments TSB43AB22/A</p> +</li> + +<li> +<p>Texas Instruments TSB43AB23</p> +</li> + +<li> +<p>Texas Instruments TSB82AA2</p> +</li> + +<li> +<p>VIA Fire II (VT6306)</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.14 Bluetooth Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CRYPTO-ACCEL" name="CRYPTO-ACCEL">3.15 Cryptographic +Accelerators</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC" name="MISC">3.16 Miscellaneous</a></h3> + +<p>Keyboards including:</p> + +<ul> +<li> +<p>USB keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<br /> +<br /> +<p>Pointing devices including:</p> + +<ul> +<li> +<p>Serial mice and compatible devices</p> +</li> + +<li> +<p>USB mice (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.org/</a>.</p> +</blockquote> +</div> + +<br /> +<br /> +</div> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/hardware-pc98.html b/en/releases/6.1R/hardware-pc98.html new file mode 100644 index 0000000000..dc22ce0173 --- /dev/null +++ b/en/releases/6.1R/hardware-pc98.html @@ -0,0 +1,5018 @@ +<!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/pc98 6.1-RELEASE Hardware Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/pc98 6.1-RELEASE Hardware +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<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="#SUPPORT-SYS">Supported Systems</a></dt> + +<dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + +<dd> +<dl> +<dt>3.1 <a href="#DISK">Disk Controllers</a></dt> + +<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt> + +<dt>3.3 <a href="#TOKENRING">Token Ring Interfaces</a></dt> + +<dt>3.4 <a href="#FDDI">FDDI Interfaces</a></dt> + +<dt>3.5 <a href="#ATM">ATM Interfaces</a></dt> + +<dt>3.6 <a href="#WLAN">Wireless Network Interfaces</a></dt> + +<dt>3.7 <a href="#MISC-NETWORK">Miscellaneous Networks</a></dt> + +<dt>3.8 <a href="#ISDN">ISDN Interfaces</a></dt> + +<dt>3.9 <a href="#SERIAL">Serial Interfaces</a></dt> + +<dt>3.10 <a href="#SOUND">Sound Devices</a></dt> + +<dt>3.11 <a href="#CAMERA">Camera and Video Capture Devices</a></dt> + +<dt>3.12 <a href="#USB">USB Devices</a></dt> + +<dt>3.13 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt> + +<dt>3.14 <a href="#BLUETOOTH">Bluetooth Devices</a></dt> + +<dt>3.15 <a href="#CRYPTO-ACCEL">Cryptographic Accelerators</a></dt> + +<dt>3.16 <a href="#MISC">Miscellaneous</a></dt> +</dl> +</dd> +</dl> +</div> + +<div class="SECT1"> +<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This document contains the hardware compatibility notes for FreeBSD 6.1-RELEASE on the +NEC PC-98x1 hardware platform (also referred to as FreeBSD/pc98 6.1-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 NEC PC-98x1 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.</p> +</blockquote> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT-SYS" name="SUPPORT-SYS">2 Supported Systems</a></h2> + +<p>NEC PC-9801/9821 series with almost all i386-compatible processors, including 80486, +Pentium, Pentium Pro, Pentium II, and variants. All i386-compatible processors by AMD, +Cyrix, IBM, and IDT are also supported.</p> + +<p>NEC FC-9801/9821 series, and NEC SV-98 series (both of them are compatible with +PC-9801/9821 series) should be supported.</p> + +<p>EPSON PC-386/486/586 series, which are compatible with NEC PC-9801 series are +supported.</p> + +<p>High-resolution mode is not supported. NEC PC-98XA/XL/RL/XL^2, and NEC PC-H98 series +are supported in normal (PC-9801 compatible) mode only.</p> + +<p>Although there are some multi-processor systems (such as Rs20/B20), SMP-related +features of FreeBSD are not supported yet.</p> + +<p>PC-9801/9821 standard bus (called C-Bus), PC-9801NOTE expansion bus (110pin), and PCI +bus are supported. New Extend Standard Architecture (NESA) bus (used in PC-H98, SV-H98, +and FC-H98 series) is not supported.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2> + +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.9.2.2 +2006/05/01 08:26:00 brueffer Exp $ + +<p>This section describes the devices currently known to be supported by with FreeBSD on +the NEC PC-98x1 platform. Other configurations may also work, but simply have not been +tested yet. Feedback, updates, and corrections to this list are encouraged.</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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> The device lists in this document are being generated automatically from +FreeBSD manual pages. This means that some devices, which are supported by multiple +drivers, may appear multiple times.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DISK" name="DISK">3.1 Disk Controllers</a></h3> + +<p>IDE/ATA controllers (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> +driver)</p> + +<p>IDE/ATA controllers (wdc driver)</p> + +<ul> +<li> +<p>On-board IDE controller</p> +</li> +</ul> + +<br /> +<br /> +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=adv&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adv</span>(4)</span></a> driver +supports the following SCSI controllers:</p> + +<ul> +<li> +<p>AdvanSys ABP510/5150</p> +</li> + +<li> +<p>AdvanSys ABP5140</p> +</li> + +<li> +<p>AdvanSys ABP5142</p> +</li> + +<li> +<p>AdvanSys ABP902/3902</p> +</li> + +<li> +<p>AdvanSys ABP3905</p> +</li> + +<li> +<p>AdvanSys ABP915</p> +</li> + +<li> +<p>AdvanSys ABP920</p> +</li> + +<li> +<p>AdvanSys ABP3922</p> +</li> + +<li> +<p>AdvanSys ABP3925</p> +</li> + +<li> +<p>AdvanSys ABP930, ABP930U, ABP930UA</p> +</li> + +<li> +<p>AdvanSys ABP960, ABP960U</p> +</li> + +<li> +<p>AdvanSys ABP542</p> +</li> + +<li> +<p>AdvanSys ABP742</p> +</li> + +<li> +<p>AdvanSys ABP842</p> +</li> + +<li> +<p>AdvanSys ABP940</p> +</li> + +<li> +<p>AdvanSys ABP940UA/3940UA</p> +</li> + +<li> +<p>AdvanSys ABP940U</p> +</li> + +<li> +<p>AdvanSys ABP3960UA</p> +</li> + +<li> +<p>AdvanSys ABP970, ABP970U</p> +</li> + +<li> +<p>AdvanSys ABP752</p> +</li> + +<li> +<p>AdvanSys ABP852</p> +</li> + +<li> +<p>AdvanSys ABP950</p> +</li> + +<li> +<p>AdvanSys ABP980, ABP980U</p> +</li> + +<li> +<p>AdvanSys ABP980UA/3980UA</p> +</li> + +<li> +<p>MELCO IFC-USP (PC-98)</p> +</li> + +<li> +<p>RATOC REX-PCI30 (PC-98)</p> +</li> + +<li> +<p>@Nifty FNECHARD IFC-USUP-TX (PC-98)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=adw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">adw</span>(4)</span></a> driver +supports SCSI controllers including:</p> + +<ul> +<li> +<p>AdvanSys ABP940UW/ABP3940UW</p> +</li> + +<li> +<p>AdvanSys ABP950UW</p> +</li> + +<li> +<p>AdvanSys ABP970UW</p> +</li> + +<li> +<p>AdvanSys ABP3940U2W</p> +</li> + +<li> +<p>AdvanSys ABP3950U2W</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a> driver +supports the following SCSI host adapter chips and SCSI controller cards:</p> + +<ul> +<li> +<p>Adaptec AIC7770 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7850 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7860 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7870 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7880 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7890 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7891 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7892 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7895 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7896 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7897 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7899 host adapter chip</p> +</li> + +<li> +<p>Adaptec 274X(W)</p> +</li> + +<li> +<p>Adaptec 274X(T)</p> +</li> + +<li> +<p>Adaptec 284X</p> +</li> + +<li> +<p>Adaptec 2910</p> +</li> + +<li> +<p>Adaptec 2915</p> +</li> + +<li> +<p>Adaptec 2920</p> +</li> + +<li> +<p>Adaptec 2930C</p> +</li> + +<li> +<p>Adaptec 2930U2</p> +</li> + +<li> +<p>Adaptec 2940</p> +</li> + +<li> +<p>Adaptec 2940J</p> +</li> + +<li> +<p>Adaptec 2940N</p> +</li> + +<li> +<p>Adaptec 2940U</p> +</li> + +<li> +<p>Adaptec 2940AU</p> +</li> + +<li> +<p>Adaptec 2940UW</p> +</li> + +<li> +<p>Adaptec 2940UW Dual</p> +</li> + +<li> +<p>Adaptec 2940UW Pro</p> +</li> + +<li> +<p>Adaptec 2940U2W</p> +</li> + +<li> +<p>Adaptec 2940U2B</p> +</li> + +<li> +<p>Adaptec 2950U2W</p> +</li> + +<li> +<p>Adaptec 2950U2B</p> +</li> + +<li> +<p>Adaptec 19160B</p> +</li> + +<li> +<p>Adaptec 29160B</p> +</li> + +<li> +<p>Adaptec 29160N</p> +</li> + +<li> +<p>Adaptec 3940</p> +</li> + +<li> +<p>Adaptec 3940U</p> +</li> + +<li> +<p>Adaptec 3940AU</p> +</li> + +<li> +<p>Adaptec 3940UW</p> +</li> + +<li> +<p>Adaptec 3940AUW</p> +</li> + +<li> +<p>Adaptec 3940U2W</p> +</li> + +<li> +<p>Adaptec 3950U2</p> +</li> + +<li> +<p>Adaptec 3960</p> +</li> + +<li> +<p>Adaptec 39160</p> +</li> + +<li> +<p>Adaptec 3985</p> +</li> + +<li> +<p>Adaptec 4944UW</p> +</li> + +<li> +<p>NEC PC-9821Xt13 (PC-98)</p> +</li> + +<li> +<p>NEC RvII26 (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B02L/B09 (PC-98)</p> +</li> + +<li> +<p>NEC SV-98/2-B03 (PC-98)</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>The adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aic&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aic</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec AHA-1505 (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1510A, AHA-1510B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1520A, AHA-1520B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1522A, AHA-1522B (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1535 (ISA)</p> +</li> + +<li> +<p>Creative Labs SoundBlaster SCSI host adapter (ISA)</p> +</li> + +<li> +<p>Adaptec AHA-1460, AHA-1460B, AHA-1460C, AHA-1460D (PC Card)</p> +</li> + +<li> +<p>Adaptec AHA-1030B, AHA-1030P (PC98)</p> +</li> + +<li> +<p>NEC PC-9801-100 (PC98)</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amd</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MELCO IFC-DP (PC-98)</p> +</li> + +<li> +<p>Tekram DC390</p> +</li> + +<li> +<p>Tekram DC390T</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MegaRAID SCSI 320-1E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-8X</p> +</li> + +<li> +<p>MegaRAID SATA 150-4</p> +</li> + +<li> +<p>MegaRAID SATA 150-6</p> +</li> + +<li> +<p>MegaRAID i4 133 RAID</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0</p> +</li> + +<li> +<p>MegaRAID SCSI 320-1</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4</p> +</li> + +<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 Elite 1650 (Series 4xx)</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 3/QC</p> +</li> + +<li> +<p>Dell PERC 4/DC</p> +</li> + +<li> +<p>Dell PERC 4/IM</p> +</li> + +<li> +<p>Dell PERC 4/SC</p> +</li> + +<li> +<p>Dell PERC 4/Di</p> +</li> + +<li> +<p>Dell PERC 4e/DC</p> +</li> + +<li> +<p>Dell PERC 4e/Di</p> +</li> + +<li> +<p>Dell PERC 4e/Si</p> +</li> + +<li> +<p>Dell PERC 4ei</p> +</li> + +<li> +<p>HP NetRAID-1/Si</p> +</li> + +<li> +<p>HP NetRAID-3/Si (D4943A)</p> +</li> + +<li> +<p>HP Embedded NetRAID</p> +</li> + +<li> +<p>Intel RAID Controller SRCS16</p> +</li> + +<li> +<p>Intel RAID Controller SRCU42X</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ct&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ct</span>(4)</span></a> driver supports +the following adapters:</p> + +<ul> +<li> +<p>ELECOM bus-master SCSI adapters</p> +</li> + +<li> +<p>I-O DATA SC-98II</p> +</li> + +<li> +<p>ICM IF-2660, IF-2766, IF-2766ET, IF-2767 and IF-2769</p> +</li> + +<li> +<p>Logitec LHA-N151 and LHA-20x series</p> +</li> + +<li> +<p>Midori-Denshi MDC-554NA and MDC-926R</p> +</li> + +<li> +<p>NEC PC-9801-55, 92 and compatibles</p> +</li> + +<li> +<p>SMIT transfer type SCSI host adapters</p> +</li> + +<li> +<p>TEXA HA-55BS2 and its later models</p> +</li> +</ul> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>ISP1000</p> +</li> + +<li> +<p>ISP1020</p> +</li> + +<li> +<p>ISP1040</p> +</li> + +<li> +<p>Qlogic 1240</p> +</li> + +<li> +<p>Qlogic 1020</p> +</li> + +<li> +<p>Qlogic 1040</p> +</li> + +<li> +<p>Qlogic 1080</p> +</li> + +<li> +<p>Qlogic 1280</p> +</li> + +<li> +<p>Qlogic 12160</p> +</li> + +<li> +<p>Qlogic 210X</p> +</li> + +<li> +<p>Qlogic 220X</p> +</li> + +<li> +<p>Qlogic 2300</p> +</li> + +<li> +<p>Qlogic 2312</p> +</li> + +<li> +<p>Qlogic 234X</p> +</li> + +<li> +<p>Qlogic 2322</p> +</li> + +<li> +<p>Qlogic 200</p> +</li> +</ul> + +<p>The following controllers are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>LSI Logic 53c1030 (Dual Ultra320 SCSI)</p> +</li> + +<li> +<p>LSI Logic FC909 (1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC909A (Dual 1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC919 (2Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC929, LSI Logic FC929X (Dual 2Gb/s Fibre Channel)</p> +</li> +</ul> + +<p>The SCSI controller chips supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver +can be found onboard on many systems including:</p> + +<ul> +<li> +<p>Dell PowerEdge 1750</p> +</li> + +<li> +<p>IBM eServer xSeries 335</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> driver +provides support for the following NCR/Symbios SCSI controller chips:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C820</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C875J</p> +</li> + +<li> +<p>53C885</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The following add-on boards are known to be supported:</p> + +<ul> +<li> +<p>I-O DATA SC-98/PCI (PC-98)</p> +</li> + +<li> +<p>I-O DATA SC-PCI (PC-98)</p> +</li> +</ul> + +<p>The following devices are currently supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ncv&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncv</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>I-O DATA PCSC-DV</p> +</li> + +<li> +<p>KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004, and UJDCD450</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 (SCSI only)</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nsp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nsp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Alpha-Data AD-PCS201</p> +</li> + +<li> +<p>I-O DATA CBSC16</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=stg&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">stg</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec 2920/A</p> +</li> + +<li> +<p>Future Domain SCSI2GO</p> +</li> + +<li> +<p>Future Domain TMC-18XX/3260</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> + +<p>Note that the Adaptec 2920C is supported by the ahc(4) driver.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> driver +provides support for the following Symbios/LSI Logic PCI SCSI controllers:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C825</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C876</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C897</p> +</li> + +<li> +<p>53C1000</p> +</li> + +<li> +<p>53C1000R</p> +</li> + +<li> +<p>53C1010-33</p> +</li> + +<li> +<p>53C1010-66</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The SCSI controllers supported by <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> can be +either embedded on a motherboard, or on one of the following add-on boards:</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>I-O DATA SC-UPCI (PC-98)</p> +</li> + +<li> +<p>Logitec LHA-521UA (PC-98)</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> + +<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&sektion=4&manpath=FreeBSD+6.1-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&sektion=1&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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=aue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">aue</span>(4)</span></a> driver +include:</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-T, FEther USB-TX, FEther USB-TXS</p> +</li> + +<li> +<p>D-Link DSB-650, DSB-650TX, DSB-650TX-PNA</p> +</li> + +<li> +<p>Elecom LD-USBL/TX</p> +</li> + +<li> +<p>Elsa Microlink USB2Ethernet</p> +</li> + +<li> +<p>HP hn210e</p> +</li> + +<li> +<p>I-O Data USB ETTX</p> +</li> + +<li> +<p>Kingston KNU101TX</p> +</li> + +<li> +<p>LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, +USB100TX, USB100H1</p> +</li> + +<li> +<p>MELCO LUA-TX, LUA2-TX</p> +</li> + +<li> +<p>Planex UE-200TX</p> +</li> + +<li> +<p>Sandberg USB to Network Link (model number 133-06)</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">axe</span>(4)</span></a> driver +supports ASIX Electronics AX88172 based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Buffalo (Melco Inc.) LUA-U2-KTX</p> +</li> + +<li> +<p>D-Link DUBE100</p> +</li> + +<li> +<p>LinkSys USB200M</p> +</li> + +<li> +<p>Netgear FA120</p> +</li> + +<li> +<p>Sitecom LN-029</p> +</li> + +<li> +<p>System TALKS Inc. SGC-X2UL</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +provides support for various NICs based on the Broadcom BCM570x family of Gigabit +Ethernet controller chips, including the following:</p> + +<ul> +<li> +<p>3Com 3c996-T (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX)</p> +</li> + +<li> +<p>Netgear GA302T (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D21 (10/100/1000baseTX)</p> +</li> + +<li> +<p>SysKonnect SK-9D41 (1000baseSX)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cue</span>(4)</span></a> driver +supports CATC USB-EL1210A based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Belkin F5U011/F5U111</p> +</li> + +<li> +<p>CATC Netmate</p> +</li> + +<li> +<p>CATC Netmate II</p> +</li> + +<li> +<p>SmartBridges SmartLink</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver provides +support for the following chipsets:</p> + +<ul> +<li> +<p>DEC/Intel 21143</p> +</li> + +<li> +<p>ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II</p> +</li> + +<li> +<p>ASIX Electronics AX88140A and AX88141</p> +</li> + +<li> +<p>Conexant LANfinity RS7112 (miniPCI)</p> +</li> + +<li> +<p>Davicom DM9009, DM9100, DM9102 and DM9102A</p> +</li> + +<li> +<p>Lite-On 82c168 and 82c169 PNIC</p> +</li> + +<li> +<p>Lite-On/Macronix 82c115 PNIC II</p> +</li> + +<li> +<p>Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732</p> +</li> + +<li> +<p>Xircom X3201 (cardbus only)</p> +</li> +</ul> + +<p>The following NICs are known to work with the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver at this +time:</p> + +<ul> +<li> +<p>3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Abocom FE2500</p> +</li> + +<li> +<p>Accton EN1217 (98715A)</p> +</li> + +<li> +<p>Accton EN2242 MiniPCI</p> +</li> + +<li> +<p>Adico AE310TX (98715A)</p> +</li> + +<li> +<p>Alfa Inc GFC2204 (ASIX AX88140A)</p> +</li> + +<li> +<p>Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, +non-MII)</p> +</li> + +<li> +<p>Built in DE500-BA on DEC Alpha workstations (21143, non-MII)</p> +</li> + +<li> +<p>Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, +MII)</p> +</li> + +<li> +<p>Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)</p> +</li> + +<li> +<p>CNet Pro110B (ASIX AX88140A)</p> +</li> + +<li> +<p>CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)</p> +</li> + +<li> +<p>Compex RL100-TX (98713 or 98713A)</p> +</li> + +<li> +<p>D-Link DFE-570TX (21143, MII, quad port)</p> +</li> + +<li> +<p>Digital DE500-BA 10/100 (21143, non-MII)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CBL/TXA (ADMtek AN985)</p> +</li> + +<li> +<p>Hawking CB102 CardBus</p> +</li> + +<li> +<p>IBM EtherJet Cardbus Adapter</p> +</li> + +<li> +<p>Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)</p> +</li> + +<li> +<p>Jaton XpressNet (Davicom DM9102)</p> +</li> + +<li> +<p>Kingston KNE100TX (21143, MII)</p> +</li> + +<li> +<p>Kingston KNE110TX (PNIC 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX v2.0 (PNIC II 82c115)</p> +</li> + +<li> +<p>LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Matrox FastNIC 10/100 (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>Melco LGY-PCI-TXL</p> +</li> + +<li> +<p>Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)</p> +</li> + +<li> +<p>Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A (98713A)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A Rev B4 (98715AEC-C)</p> +</li> + +<li> +<p>NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)</p> +</li> + +<li> +<p>Netgear FA511</p> +</li> + +<li> +<p>PlaneX FNW-3602-T (ADMtek AN985)</p> +</li> + +<li> +<p>SMC EZ Card 10/100 1233A-TX (ADMtek AN985)</p> +</li> + +<li> +<p>SVEC PN102-TX (98713)</p> +</li> + +<li> +<p>Xircom Cardbus Realport</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet 10/100</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet II 10/100</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">de</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Adaptec ANA-6944/TX</p> +</li> + +<li> +<p>Cogent EM100FX and EM440TX</p> +</li> + +<li> +<p>Corega FastEther PCI-TX</p> +</li> + +<li> +<p>D-Link DFE-500TX</p> +</li> + +<li> +<p>DEC DE435, DEC DE450, and DEC DE500</p> +</li> + +<li> +<p>ELECOM LD-PCI2T, LD-PCITS</p> +</li> + +<li> +<p>I-O DATA LA2/T-PCI</p> +</li> + +<li> +<p>SMC Etherpower 8432, 9332 and 9334</p> +</li> + +<li> +<p>ZNYX ZX3xx</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ed</span>(4)</span></a> driver supports +the following Ethernet NICs:</p> + +<ul> +<li> +<p>3Com 3c503 Etherlink II</p> +</li> + +<li> +<p>AR-P500 Ethernet</p> +</li> + +<li> +<p>Accton EN1644 (old model), EN1646 (old model), EN2203 (old model) (110pin) (flags +0xd00000)</p> +</li> + +<li> +<p>Accton EN2212/EN2216/UE2216</p> +</li> + +<li> +<p>Allied Telesis CentreCOM LA100-PCM_V2</p> +</li> + +<li> +<p>Allied Telesis LA-98 (flags 0x000000) (PC-98)</p> +</li> + +<li> +<p>Allied Telesis SIC-98, SIC-98NOTE (110pin), SIU-98 (flags 0x600000) (PC-98)</p> +</li> + +<li> +<p>Allied Telesis SIU-98-D (flags 0x610000) (PC-98)</p> +</li> + +<li> +<p>AmbiCom 10BaseT card</p> +</li> + +<li> +<p>Bay Networks NETGEAR FA410TXC Fast Ethernet</p> +</li> + +<li> +<p>Belkin F5D5020 PC Card Fast Ethernet</p> +</li> + +<li> +<p>Billionton LM5LT-10B Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Bromax iPort 10/100 Ethernet PC Card</p> +</li> + +<li> +<p>Bromax iPort 10 Ethernet PC Card</p> +</li> + +<li> +<p>Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX PC Card</p> +</li> + +<li> +<p>CNet BC40 adapter</p> +</li> + +<li> +<p>Compex Net-A adapter</p> +</li> + +<li> +<p>Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) (flags 0xa00000) (PC-98)</p> +</li> + +<li> +<p>Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P (flags 0x300000) (PC-98)</p> +</li> + +<li> +<p>Corega Ether98-T (flags 0x000000) (PC-98)</p> +</li> + +<li> +<p>Corega Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD</p> +</li> + +<li> +<p>CyQ've ELA-010</p> +</li> + +<li> +<p>DEC EtherWorks DE305</p> +</li> + +<li> +<p>Danpex EN-6200P2</p> +</li> + +<li> +<p>D-Link DE-298, DE-298P (flags 0x500000) (PC-98)</p> +</li> + +<li> +<p>D-Link DE-650/660</p> +</li> + +<li> +<p>D-Link IC-CARD/IC-CARD+ Ethernet</p> +</li> + +<li> +<p>ELECOM LD-98P (flags 0x500000) (PC-98)</p> +</li> + +<li> +<p>ELECOM LD-BDN, LD-NW801G (flags 0x200000) (PC-98)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A)</p> +</li> + +<li> +<p>HP PC Lan+ 27247B and 27252A</p> +</li> + +<li> +<p>IBM Creditcard Ethernet I/II</p> +</li> + +<li> +<p>ICM AD-ET2-T, DT-ET-25, DT-ET-T5, IF-2766ET, IF-2771ET, NB-ET-T (110pin) (flags +0x500000) (PC-98)</p> +</li> + +<li> +<p>I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 (flags 0x900000) (PC-98)</p> +</li> + +<li> +<p>I-O DATA ET2/T-PCI</p> +</li> + +<li> +<p>I-O DATA PCLATE</p> +</li> + +<li> +<p>Kansai KLA-98C/T (flags 0x900000) (PC-98)</p> +</li> + +<li> +<p>Kingston KNE-PC2, CIO10T, KNE-PCM/x Ethernet</p> +</li> + +<li> +<p>Linksys EC2T/PCMPC100/PCM100, PCMLM56</p> +</li> + +<li> +<p>Linksys EtherFast 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 V2)</p> +</li> + +<li> +<p>Logitec LAN-98T (flags 0xb00000) (PC-98)</p> +</li> + +<li> +<p>MACNICA Ethernet ME1 for JEIDA</p> +</li> + +<li> +<p>MACNICA ME98 (flags 0x900000) (PC-98)</p> +</li> + +<li> +<p>MACNICA NE2098 (flags 0x400000) (PC-98)</p> +</li> + +<li> +<p>MELCO EGY-98 (flags 0x300000) (PC-98)</p> +</li> + +<li> +<p>MELCO LGH-98, LGY-98, LGY-98-N (110pin), IND-SP, IND-SS (flags 0x400000) (PC-98)</p> +</li> + +<li> +<p>MELCO LGY-PCI-TR</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>NEC PC-9801-77, PC-9801-78 (flags 0x910000) (PC-98)</p> +</li> + +<li> +<p>NEC PC-9801-107, PC-9801-108 (flags 0x800000) (PC-98)</p> +</li> + +<li> +<p>National Semiconductor InfoMover NE4100</p> +</li> + +<li> +<p>NetGear FA-410TX</p> +</li> + +<li> +<p>NetVin 5000</p> +</li> + +<li> +<p>Network Everywhere Ethernet 10BaseT PC Card</p> +</li> + +<li> +<p>Networld 98X3 (flags 0xd00000) (PC-98)</p> +</li> + +<li> +<p>Networld EC-98X, EP-98X (flags 0xd10000) (PC-98)</p> +</li> + +<li> +<p>New Media LANSurfer 10+56 Ethernet/Modem</p> +</li> + +<li> +<p>New Media LANSurfer</p> +</li> + +<li> +<p>Novell NE1000/NE2000/NE2100</p> +</li> + +<li> +<p>PLANEX ENW-8300-T</p> +</li> + +<li> +<p>PLANEX EN-2298-C (flags 0x200000) (PC-98)</p> +</li> + +<li> +<p>PLANEX EN-2298P-T, EN-2298-T (flags 0x500000) (PC-98)</p> +</li> + +<li> +<p>PLANEX FNW-3600-T</p> +</li> + +<li> +<p>Psion 10/100 LANGLOBAL Combine iT</p> +</li> + +<li> +<p>RealTek 8029</p> +</li> + +<li> +<p>Relia Combo-L/M-56k PC Card</p> +</li> + +<li> +<p>SMC Elite 16 WD8013</p> +</li> + +<li> +<p>SMC Elite Ultra</p> +</li> + +<li> +<p>SMC EtherEZ98 (flags 0x000000) (PC-98)</p> +</li> + +<li> +<p>SMC WD8003E/WD8003EBT/WD8003S/WD8003SBT/WD8003W/WD8013EBT/WD8013W and clones</p> +</li> + +<li> +<p>SMC EZCard PC Card, 8040-TX, 8041-TX</p> +</li> + +<li> +<p>Socket LP-E, ES-1000 Ethernet/Serial, LP-E CF, LP-FE CF</p> +</li> + +<li> +<p>Surecom EtherPerfect EP-427</p> +</li> + +<li> +<p>Surecom NE-34</p> +</li> + +<li> +<p>TDK 3000/3400/5670 Fast Etherenet/Modem</p> +</li> + +<li> +<p>TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card</p> +</li> + +<li> +<p>TDK DFL5610WS Ethernet/Modem PC Card</p> +</li> + +<li> +<p>Telecom Device SuperSocket RE450T</p> +</li> + +<li> +<p>VIA VT86C926</p> +</li> + +<li> +<p>Winbond W89C940</p> +</li> +</ul> + +<p>C-Bus, ISA, PCI and PC Card devices are supported.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, +82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 controller +chips:</p> + +<ul> +<li> +<p>Intel PRO/1000 CT Network Connection (82547)</p> +</li> + +<li> +<p>Intel PRO/1000 F Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 Gigabit Server Adapter (82542)</p> +</li> + +<li> +<p>Intel PRO/1000 GT Desktop Adapter (82541PI)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MF Server Adapter (LX) (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82540)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Desktop Adapter (82541)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Dual Port Server Adapter (82546)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Quad Port Server Adapter (82546EB)</p> +</li> + +<li> +<p>Intel PRO/1000 MT Server Adapter (82545)</p> +</li> + +<li> +<p>Intel PRO/1000 T Desktop Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 T Server Adapter (82543)</p> +</li> + +<li> +<p>Intel PRO/1000 XF Server Adapter (82544)</p> +</li> + +<li> +<p>Intel PRO/1000 XT Server Adapter (82544)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ep</span>(4)</span></a> driver supports +Ethernet adapters based on the 3Com 3C5x9 Etherlink III Parallel Tasking chipset, +including:</p> + +<ul> +<li> +<p>3Com 3C1 CF</p> +</li> + +<li> +<p>3Com 3C509-TP, 3C509-BNC, 3C509-Combo, 3C509-TPO, 3C509-TPC ISA</p> +</li> + +<li> +<p>3Com 3C509B-TP, 3C509B-BNC, 3C509B-Combo, 3C509B-TPO, 3C509B-TPC ISA</p> +</li> + +<li> +<p>3Com 3C529, 3C529-TP MCA</p> +</li> + +<li> +<p>3Com 3C562/3C563 PCMCIA</p> +</li> + +<li> +<p>3Com 3C569B-J-TPO, 3C569B-J-COMBO CBUS</p> +</li> + +<li> +<p>3Com 3C574, 3C574TX, 3C574-TX, 3CCFE574BT, 3CXFE574BT, 3C3FE574BT PCMCIA</p> +</li> + +<li> +<p>3Com 3C579-TP, 3C579-BNC EISA</p> +</li> + +<li> +<p>3Com 3C589, 3C589B, 3C589C, 3C589D, 3CXE589DT PCMCIA</p> +</li> + +<li> +<p>3Com 3CCFEM556B, 3CCFEM556BI PCMCIA</p> +</li> + +<li> +<p>3Com 3CXE589EC, 3CCE589EC, 3CXE589ET, 3CCE589ET PCMCIA</p> +</li> + +<li> +<p>3Com Megahertz 3CCEM556, 3CXEM556, 3CCEM556B, 3CXEM556B, 3C3FEM556C PCMCIA</p> +</li> + +<li> +<p>3Com OfficeConnect 3CXSH572BT, 3CCSH572BT PCMCIA</p> +</li> + +<li> +<p>Farallon EtherWave and EtherMac PC Card (P/n 595/895 with BLUE arrow)</p> +</li> +</ul> + +<p>Controllers and cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">fe</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin)</p> +</li> + +<li> +<p>CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard)</p> +</li> + +<li> +<p>CONTEC C-NET(PC)C PCMCIA Ethernet</p> +</li> + +<li> +<p>Eagle Tech NE200T</p> +</li> + +<li> +<p>Eiger Labs EPX-10BT</p> +</li> + +<li> +<p>Fujitsu FMV-J182, FMV-J182A</p> +</li> + +<li> +<p>Fujitsu MB86960A, MB86965A</p> +</li> + +<li> +<p>Fujitsu MBH10303, MBH10302 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, and REX-R280</p> +</li> + +<li> +<p>RATOC REX-9880/9881/9882/9883</p> +</li> + +<li> +<p>TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin)</p> +</li> + +<li> +<p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p> +</li> + +<li> +<p>Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE N98(PC86132) +(110-pin)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel EtherExpress PRO/10</p> +</li> + +<li> +<p>Intel InBusiness 10/100</p> +</li> + +<li> +<p>Intel PRO/100B / EtherExpressPRO/100 B PCI 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>Contec C-NET(PI)-100TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B06 (PC-98)</p> +</li> + +<li> +<p>Many on-board network interfaces on Intel motherboards</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server +models. Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Sun PCI SunSwift Adapter</p> +</li> + +<li> +<p>Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)</p> +</li> + +<li> +<p>Sun PCI Sun100BaseT Adapter 2.0</p> +</li> + +<li> +<p>Sun SBus Sun100BaseT 2.0</p> +</li> + +<li> +<p>Sun PCI Quad FastEthernet Controller</p> +</li> + +<li> +<p>Sun SBus Quad FastEthernet Controller</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kue</span>(4)</span></a> driver +supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>3Com 3c19250</p> +</li> + +<li> +<p>3Com 3c460 HomeConnect Ethernet USB Adapter</p> +</li> + +<li> +<p>ADS Technologies USB-10BT</p> +</li> + +<li> +<p>AOX USB101</p> +</li> + +<li> +<p>ATen UC10T</p> +</li> + +<li> +<p>Abocom URE 450</p> +</li> + +<li> +<p>Corega USB-T</p> +</li> + +<li> +<p>D-Link DSB-650C</p> +</li> + +<li> +<p>Entrega NET-USB-E45, NET-HUB-3U1E</p> +</li> + +<li> +<p>I/O Data USB ETT</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> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>SMC TigerCard 1000 (SMC9462SX)</p> +</li> + +<li> +<p>D-Link DGE-500SX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Diamond HomeFree</p> +</li> + +<li> +<p>Digital DEPCA</p> +</li> + +<li> +<p>Hewlett Packard Vectra 486/66XM</p> +</li> + +<li> +<p>Hewlett Packard Vectra XU</p> +</li> + +<li> +<p>Isolan AT 4141-0 (16 bit)</p> +</li> + +<li> +<p>Isolan BICC</p> +</li> + +<li> +<p>Isolink 4110 (8 bit)</p> +</li> + +<li> +<p>Novell NE2100</p> +</li> + +<li> +<p>Novell NE32-VL</p> +</li> +</ul> + +<p>Also supported are adapters working with the pcn(4) driver. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +runs these in compatibility mode, thus the pcn(4) driver should be preferred.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=my&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">my</span>(4)</span></a> driver provides +support for various NICs based on the Myson chipset. Supported models include:</p> + +<ul> +<li> +<p>Myson MTD800 PCI Fast Ethernet chip</p> +</li> + +<li> +<p>Myson MTD803 PCI Fast Ethernet chip</p> +</li> + +<li> +<p>Myson MTD89X PCI Gigabit Ethernet chip</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=nge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nge</span>(4)</span></a> driver +supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters +including:</p> + +<ul> +<li> +<p>Addtron AEG320T</p> +</li> + +<li> +<p>Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI)</p> +</li> + +<li> +<p>Asante FriendlyNet GigaNIX 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</p> +</li> + +<li> +<p>Netgear GA622T</p> +</li> + +<li> +<p>SMC EZ Card 1000 (SMC9462TX)</p> +</li> + +<li> +<p>Surecom Technology EP-320G-TX</p> +</li> + +<li> +<p>Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcn</span>(4)</span></a> driver +supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, +PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:</p> + +<ul> +<li> +<p>AMD Am79C971 PCnet-FAST</p> +</li> + +<li> +<p>AMD Am79C972 PCnet-FAST+</p> +</li> + +<li> +<p>AMD Am79C973/Am79C975 PCnet-FAST III</p> +</li> + +<li> +<p>AMD Am79C976 PCnet-PRO</p> +</li> + +<li> +<p>AMD Am79C978 PCnet-Home</p> +</li> + +<li> +<p>Allied-Telesis LA-PCI</p> +</li> + +<li> +<p>NEC SV-98/2-B05, B06</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">re</span>(4)</span></a> driver supports +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based Fast Ethernet and Gigabit +Ethernet adapters including:</p> + +<ul> +<li> +<p>Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)</p> +</li> + +<li> +<p>Compaq Evo N1015v Integrated Ethernet (8139C+)</p> +</li> + +<li> +<p>Corega CG-LAPCIGT Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>D-Link DGE-528(T) Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)</p> +</li> + +<li> +<p>LevelOne GNC-0105T (8169S)</p> +</li> + +<li> +<p>PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)</p> +</li> + +<li> +<p>Xterasys XN-152 10/100/1000 NIC (8169)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a> driver +include:</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>Belkin F5D5000</p> +</li> + +<li> +<p>BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)</p> +</li> + +<li> +<p>Compaq HNE-300</p> +</li> + +<li> +<p>CompUSA no-name 10/100 PCI Ethernet NIC</p> +</li> + +<li> +<p>Corega FEther CB-TXD</p> +</li> + +<li> +<p>Corega FEtherII CB-TXD</p> +</li> + +<li> +<p>D-Link DFE-528TX</p> +</li> + +<li> +<p>D-Link DFE-530TX+</p> +</li> + +<li> +<p>D-Link DFE-538TX</p> +</li> + +<li> +<p>D-Link DFE-690TXD</p> +</li> + +<li> +<p>Edimax EP-4103DL CardBus</p> +</li> + +<li> +<p>Encore ENL832-TX 10/100 M PCI</p> +</li> + +<li> +<p>Farallon NetLINE 10/100 PCI</p> +</li> + +<li> +<p>Genius GF100TXR</p> +</li> + +<li> +<p>GigaFast Ethernet EE100-AXP</p> +</li> + +<li> +<p>KTX-9130TX 10/100 Fast Ethernet</p> +</li> + +<li> +<p>LevelOne FPC-0106TX</p> +</li> + +<li> +<p>Longshine LCS-8038TX-R</p> +</li> + +<li> +<p>NDC Communications NE100TX-E</p> +</li> + +<li> +<p>Netronix Inc. EA-1210 NetEther 10/100</p> +</li> + +<li> +<p>Nortel Networks 10/100BaseTX</p> +</li> + +<li> +<p>OvisLink LEF-8129TX</p> +</li> + +<li> +<p>OvisLink LEF-8139TX</p> +</li> + +<li> +<p>Peppercon AG ROL-F</p> +</li> + +<li> +<p>Planex FNW-3800-TX</p> +</li> + +<li> +<p>SMC EZ Card 10/100 PCI 1211-TX</p> +</li> + +<li> +<p>SOHO (PRAGMATIC) UE-1211C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rue</span>(4)</span></a> driver +supports RealTek RTL8150 based USB Ethernet adapters including:</p> + +<ul> +<li> +<p>Buffalo (Melco Inc.) LUA-KTX</p> +</li> + +<li> +<p>Green House GH-USB100B</p> +</li> + +<li> +<p>LinkSys USB100M</p> +</li> + +<li> +<p>Billionton 10/100 FastEthernet USBKR2</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sf</span>(4)</span></a> driver +include:</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> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sis</span>(4)</span></a> driver +supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and +embedded controllers, as well as Fast Ethernet adapters based on the National +Semiconductor DP83815 (MacPhyter) chip. Supported adapters include:</p> + +<ul> +<li> +<p>@Nifty FNECHARD IFC USUP-TX</p> +</li> + +<li> +<p>MELCO LGY-PCI-TXC</p> +</li> + +<li> +<p>Netgear FA311-TX (DP83815)</p> +</li> + +<li> +<p>Netgear FA312-TX (DP83815)</p> +</li> + +<li> +<p>SiS 630, 635, and 735 motherboard chipsets</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>3Com 3C940 single port, 1000baseT adapter</p> +</li> + +<li> +<p>3Com 3C2000-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Belkin F5D5005 single port, 1000baseT adapter</p> +</li> + +<li> +<p>D-Link DGE-530T single port, 1000baseT adapter</p> +</li> + +<li> +<p>Linksys EG1032 single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9521 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9821 SK-NET GE-T single port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9822 SK-NET GE-T dual port, 1000baseT adapter</p> +</li> + +<li> +<p>SK-9841 SK-NET GE-LX single port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9842 SK-NET GE-LX dual port, single mode fiber adapter</p> +</li> + +<li> +<p>SK-9843 SK-NET GE-SX single port, multimode fiber adapter</p> +</li> + +<li> +<p>SK-9844 SK-NET GE-SX dual port, multimode fiber adapter</p> +</li> + +<li> +<p>SMC 9452TX single port, 1000baseT adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snc</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>National Semiconductor DP83934AVQB</p> +</li> + +<li> +<p>NEC PC-9801-83</p> +</li> + +<li> +<p>NEC PC-9801-84</p> +</li> + +<li> +<p>NEC PC-9801-103</p> +</li> + +<li> +<p>NEC PC-9801-104</p> +</li> + +<li> +<p>NEC PC-9801N-15</p> +</li> + +<li> +<p>NEC PC-9801N-25</p> +</li> + +<li> +<p>NEC PC-9801N-J02 PCMCIA</p> +</li> + +<li> +<p>NEC PC-9801N-J02R PCMCIA</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snc</span>(4)</span></a> driver +also includes support for the National Semiconductor NS46C46 as 64 * 16 bits Microwave +Serial EEPROM.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ste</span>(4)</span></a> driver +supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded +controllers including:</p> + +<ul> +<li> +<p>D-Link DFE-530TXS</p> +</li> + +<li> +<p>D-Link DFE-550TX</p> +</li> + +<li> +<p>D-Link DFE-580TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ti</span>(4)</span></a> driver supports +Gigabit Ethernet adapters based on the Alteon Tigon I and II chips. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ti</span>(4)</span></a> driver has been +tested with the following adapters:</p> + +<ul> +<li> +<p>3Com 3c985-SX Gigabit Ethernet adapter (Tigon 1)</p> +</li> + +<li> +<p>3Com 3c985B-SX Gigabit Ethernet adapter (Tigon 2)</p> +</li> + +<li> +<p>Alteon AceNIC V Gigabit Ethernet adapter (1000baseSX)</p> +</li> + +<li> +<p>Alteon AceNIC V Gigabit Ethernet adapter (1000baseT)</p> +</li> + +<li> +<p>Digital EtherWORKS 1000SX PCI Gigabit adapter</p> +</li> + +<li> +<p>Netgear GA620 Gigabit Ethernet adapter (1000baseSX)</p> +</li> + +<li> +<p>Netgear GA620T Gigabit Ethernet adapter (1000baseT)</p> +</li> +</ul> + +<p>The following adapters should also be supported but have not yet been tested:</p> + +<ul> +<li> +<p>Asante GigaNIX1000T Gigabit Ethernet adapter</p> +</li> + +<li> +<p>Asante PCI 1000BASE-SX Gigabit Ethernet adapter</p> +</li> + +<li> +<p>Farallon PN9000SX Gigabit Ethernet adapter</p> +</li> + +<li> +<p>NEC Gigabit Ethernet</p> +</li> + +<li> +<p>Silicon Graphics PCI Gigabit Ethernet adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver supports +Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large +number of Compaq PCI Ethernet adapters. Also supported are:</p> + +<ul> +<li> +<p>Olicom OC-2135/2138 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Olicom OC-2325/OC-2326 10/100 TX UTP adapter</p> +</li> + +<li> +<p>Racore 8148 10baseT/100baseTX/100baseFX adapter</p> +</li> + +<li> +<p>Racore 8165 10/100baseTX adapter</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tl</span>(4)</span></a> driver also +supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq +Deskpro desktop machines including:</p> + +<ul> +<li> +<p>Compaq Netelligent 10</p> +</li> + +<li> +<p>Compaq Netelligent 10 T PCI UTP/Coax</p> +</li> + +<li> +<p>Compaq Netelligent 10/100</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Dual-Port</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 Proliant</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX Embedded UTP</p> +</li> + +<li> +<p>Compaq Netelligent 10/100 TX UTP</p> +</li> + +<li> +<p>Compaq NetFlex 3P</p> +</li> + +<li> +<p>Compaq NetFlex 3P Integrated</p> +</li> + +<li> +<p>Compaq NetFlex 3P w/BNC</p> +</li> +</ul> + +<p>SMC 83c17x (EPIC)-based Ethernet NICs (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">tx</span>(4)</span></a> driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">txp</span>(4)</span></a> driver +supports the following cards:</p> + +<ul> +<li> +<p>3Com 3CR990-TX-95</p> +</li> + +<li> +<p>3Com 3CR990-TX-97</p> +</li> + +<li> +<p>3Com 3cR990B-TXM</p> +</li> + +<li> +<p>3Com 3CR990SVR95</p> +</li> + +<li> +<p>3Com 3CR990SVR97</p> +</li> + +<li> +<p>3Com 3cR990B-SRV</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=udav&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">udav</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Corega FEther USB-TXC</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vge</span>(4)</span></a> driver +supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including:</p> + +<ul> +<li> +<p>VIA Networking LAN-on-motherboard Gigabit Ethernet</p> +</li> + +<li> +<p>ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701)</p> +</li> + +<li> +<p>ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vr</span>(4)</span></a> driver supports +VIA Technologies Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters +including:</p> + +<ul> +<li> +<p>AOpen/Acer ALN-320</p> +</li> + +<li> +<p>D-Link DFE530-TX</p> +</li> + +<li> +<p>Hawking Technologies PN102TX</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vx&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">vx</span>(4)</span></a> driver supports +the following cards:</p> + +<ul> +<li> +<p>3Com 3c590 EtherLink III PCI</p> +</li> + +<li> +<p>3Com 3c592 EtherLink III EISA</p> +</li> + +<li> +<p>3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode</p> +</li> + +<li> +<p>3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wb</span>(4)</span></a> driver supports +Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:</p> + +<ul> +<li> +<p>Trendware TE100-PCIE</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver supports +the following hardware:</p> + +<ul> +<li> +<p>3Com 3c900-TPO</p> +</li> + +<li> +<p>3Com 3c900-COMBO</p> +</li> + +<li> +<p>3Com 3c905-TX</p> +</li> + +<li> +<p>3Com 3c905-T4</p> +</li> + +<li> +<p>3Com 3c900B-TPO</p> +</li> + +<li> +<p>3Com 3c900B-TPC</p> +</li> + +<li> +<p>3Com 3c900B-FL</p> +</li> + +<li> +<p>3Com 3c900B-COMBO</p> +</li> + +<li> +<p>3Com 3c905B-T4</p> +</li> + +<li> +<p>3Com 3c905B-TX</p> +</li> + +<li> +<p>3Com 3c905B-FX</p> +</li> + +<li> +<p>3Com 3c905B-COMBO</p> +</li> + +<li> +<p>3Com 3c905C-TX</p> +</li> + +<li> +<p>3Com 3c980, 3c980B, and 3c980C server adapters</p> +</li> + +<li> +<p>3Com 3cSOHO100-TX OfficeConnect adapters</p> +</li> + +<li> +<p>3Com 3c450 HomeConnect adapters</p> +</li> + +<li> +<p>3Com 3c555, 3c556 and 3c556B mini-PCI adapters</p> +</li> + +<li> +<p>3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, +3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters</p> +</li> + +<li> +<p>3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded +adapters</p> +</li> +</ul> + +<p>Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a +built-in proprietary modem. Neither the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver nor any +other driver supports this modem.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="TOKENRING" name="TOKENRING">3.3 Token Ring Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FDDI" name="FDDI">3.4 FDDI Interfaces</a></h3> + +<p>DEC DEFPA PCI (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fpa</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ATM" name="ATM">3.5 ATM Interfaces</a></h3> + +<p>Midway-based ATM interfaces (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=en&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">en</span>(4)</span></a> driver)</p> + +<p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fatm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fatm</span>(4)</span></a> +drivers)</p> + +<p>IDT NICStAR 77201/211-based ATM Adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=idt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">idt</span>(4)</span></a> +driver)</p> + +<p>FORE Systems, Inc. HE155 and HE622 ATM interfaces (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hatm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hatm</span>(4)</span></a> +driver)</p> + +<p>IDT77252-based ATM cards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=patm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">patm</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="WLAN" name="WLAN">3.6 Wireless Network Interfaces</a></h3> + +<p>Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes +using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and +Symbol Spectrum24 chipsets (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">wi</span>(4)</span></a> driver)</p> + +<p>Cisco/Aironet 802.11b wireless adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">an</span>(4)</span></a> driver)</p> + +<p>Raytheon Raylink 2.4GHz wireless adapters (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ray&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ray</span>(4)</span></a> +driver)</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=awi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">awi</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>BayStack 650</p> +</li> + +<li> +<p>BayStack 660</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</p> +</li> + +<li> +<p>Netwave AirSurfer Pro</p> +</li> + +<li> +<p>Nokia C020 WLAN</p> +</li> + +<li> +<p>Farallon SkyLINE</p> +</li> +</ul> + +<p>The original Xircom Netwave AirSurfer is supported by the cnw(4) driver.</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cnw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cnw</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Xircom CreditCard Netwave</p> +</li> + +<li> +<p>NetWave AirSurfer</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC-NETWORK" name="MISC-NETWORK">3.7 Miscellaneous +Networks</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ce&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ce</span>(4)</span></a> driver supports +the following models of Tau-PCI/32 WAN adapters:</p> + +<ul> +<li> +<p>Cronyx Tau-PCI/32</p> +</li> + +<li> +<p>Cronyx Tau-PCI/32-Lite</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cp&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">cp</span>(4)</span></a> driver supports +the following models of Tau-PCI WAN adapters:</p> + +<ul> +<li> +<p>Cronyx Tau-PCI</p> +</li> + +<li> +<p>Cronyx Tau-PCI/R</p> +</li> + +<li> +<p>Cronyx Tau-PCI-L</p> +</li> + +<li> +<p>Cronyx Tau-PCI-L/R</p> +</li> + +<li> +<p>Cronyx Tau-PCI-E1</p> +</li> + +<li> +<p>Cronyx Tau-PCI-G703</p> +</li> + +<li> +<p>Cronyx Tau-PCI-2E1</p> +</li> + +<li> +<p>Cronyx Tau-PCI-4E1</p> +</li> + +<li> +<p>Cronyx Tau-PCI-E3</p> +</li> + +<li> +<p>Cronyx Tau-PCI-T3</p> +</li> + +<li> +<p>Cronyx Tau-PCI-STS1</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ISDN" name="ISDN">3.8 ISDN Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SERIAL" name="SERIAL">3.9 Serial Interfaces</a></h3> + +<p>Internel serial interfaces (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<ul> +<li> +<p>PC-9801 on-board</p> +</li> + +<li> +<p>PC-9821 2'nd CCU (flags 0x12000000)</p> +</li> +</ul> + +<br /> +<br /> +<p>NEC PC-9861K, PC-9801-101 and Midori-Denshi MDC-926Rs (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<ul> +<li> +<p>COM2 (flags 0x01000000)</p> +</li> + +<li> +<p>COM3 (flags 0x02000000)</p> +</li> +</ul> + +<br /> +<br /> +<p>NEC PC-9801-120 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> "flags 0x11000000" is necessary in kernel configuration.</p> +</blockquote> +</div> + +<p>Microcore MC-16550, MC-16550II, MC-RS98 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> "flags 0x14000?01" is necessary in kernel configuration.</p> +</blockquote> +</div> + +<p>Media Intelligent RSB-2000, RSB-3000 and AIWA B98-02 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> "flags 0x15000?01" is necessary in kernel configuration.</p> +</blockquote> +</div> + +<p>Media Intelligent RSB-384 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> "flags 0x16000001" is necessary in kernel configuration.</p> +</blockquote> +</div> + +<p>I-O DATA RSA-98III (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> "flags 0x18000?01" is necessary in kernel configuration.</p> +</blockquote> +</div> + +<p>Hayes ESP98 (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> +driver)</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> "options COM_ESP" and "flags 0x19000000" are necessary in kernel +configuration.</p> +</blockquote> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SOUND" name="SOUND">3.10 Sound Devices</a></h3> + +<p>NEC PC-9801-73, 86 and compatibles (nss driver)</p> + +<ul> +<li> +<p>NEC A-MATE internal sound</p> +</li> + +<li> +<p>Q-Vision WaveStar, WaveMaster</p> +</li> +</ul> + +<br /> +<br /> +<p>NEC X-MATE, CanBe, ValueStar internal (mss driver)</p> + +<p>Creative Technologies SoundBlaster(98) (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sb&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sb</span>(4)</span></a> driver)</p> + +<p>I-O DATA CD-BOX (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sb&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">sb</span>(4)</span></a> driver)</p> + +<p>MPU-401 and compatible interfaces (mpu driver)</p> + +<ul> +<li> +<p>Q-Vision WaveStar</p> +</li> +</ul> + +<br /> +<br /> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CAMERA" name="CAMERA">3.11 Camera and Video Capture +Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bktr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bktr</span>(4)</span></a> driver +supports video capture cards based on the Brooktree Bt848/849/878/879 chips, as well as +Pinnacle PCTV cards, including:</p> + +<ul> +<li> +<p>AOpen VA1000</p> +</li> + +<li> +<p>AVerMedia AVerTV Studio</p> +</li> + +<li> +<p>AVerMedia TF/FM-98</p> +</li> + +<li> +<p>ATI TV Wonder VE</p> +</li> + +<li> +<p>Hauppauge WinCast/TV</p> +</li> + +<li> +<p>Hauppauge WinTV-Go-FM</p> +</li> + +<li> +<p>Hauppauge WinTV-pci</p> +</li> + +<li> +<p>Hauppauge WinTV-radio</p> +</li> + +<li> +<p>Intel Smart Video Recorder III</p> +</li> + +<li> +<p>KWORLD PCI TV Tuner</p> +</li> + +<li> +<p>Miro PC TV</p> +</li> + +<li> +<p>Pinnacle PCTV Pro</p> +</li> + +<li> +<p>Pinnacle PCTV Rave</p> +</li> + +<li> +<p>PixelView PlayTV PAK</p> +</li> + +<li> +<p>PixelView PlayTV Pro (rev 4C, 9D)</p> +</li> + +<li> +<p>SIGMA TV II</p> +</li> + +<li> +<p>STB TV PCI Television Tuner</p> +</li> + +<li> +<p>Super TV Tuner</p> +</li> + +<li> +<p>TerraTec TValue</p> +</li> + +<li> +<p>V-Stream XPERT TV-PVR 878</p> +</li> + +<li> +<p>Video Highway XTreme</p> +</li> + +<li> +<p>VideoLogic Captivator PCI</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USB" name="USB">3.12 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> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> USB Bluetooth adapters can be found in <a href="#BLUETOOTH">Bluetooth</a> +section.</p> +</blockquote> +</div> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a> driver +supports all OHCI v1.0 compliant controllers including:</p> + +<ul> +<li> +<p>AcerLabs M5237 (Aladdin-V)</p> +</li> + +<li> +<p>AMD-756</p> +</li> + +<li> +<p>OPTi 82C861 (FireLink)</p> +</li> + +<li> +<p>NEC uPD 9210</p> +</li> + +<li> +<p>CMD Tech 670 (USB0670)</p> +</li> + +<li> +<p>CMD Tech 673 (USB0673)</p> +</li> + +<li> +<p>NVIDIA nForce3</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO USB)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a> driver +supports all UHCI v1.1 compliant controllers including:</p> + +<ul> +<li> +<p>Intel 82371AB/EB (PIIX4)</p> +</li> + +<li> +<p>Intel 82371SB (PIIX3)</p> +</li> + +<li> +<p>VIA 83C572</p> +</li> +</ul> + +<p>USB 2.0 controllers using the EHCI interface (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ehci</span>(4)</span></a> +driver)</p> + +<p>Hubs</p> + +<p>Keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> + +<p>Miscellaneous</p> + +<ul> +<li> +<p>Assist Computer Systems PC Camera C-M1</p> +</li> + +<li> +<p>ActiveWire I/O Board</p> +</li> + +<li> +<p>Creative Technology Video Blaster WebCam Plus</p> +</li> + +<li> +<p>D-Link DSB-R100 USB Radio (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ufm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ufm</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>Mirunet AlphaCam Plus</p> +</li> +</ul> + +<br /> +<br /> +<p>The following devices are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=urio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">urio</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>Diamond MultiMedia Rio 500</p> +</li> + +<li> +<p>Diamond MultiMedia Rio 600</p> +</li> + +<li> +<p>Diamond MultiMedia Rio 800</p> +</li> +</ul> + +<p>Devices supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umodem&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umodem</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>3Com 5605</p> +</li> + +<li> +<p>Metricom Ricochet GS USB wireless modem</p> +</li> + +<li> +<p>Yamaha Broadband Wireless Router RTW65b</p> +</li> + +<li> +<p>ELSA MicroLink 56k USB modem</p> +</li> +</ul> + +<p>Mice (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ulpt</span>(4)</span></a> driver +provides support for USB printers and parallel printer conversion cables, including the +following:</p> + +<ul> +<li> +<p>ATen parallel printer adapter</p> +</li> + +<li> +<p>Belkin F5U002 parallel printer adapter</p> +</li> + +<li> +<p>Canon BJ F850, S600</p> +</li> + +<li> +<p>Canon LBP-1310, 350</p> +</li> + +<li> +<p>Entrega USB-to-parallel printer adapter</p> +</li> + +<li> +<p>Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)</p> +</li> + +<li> +<p>Oki Data MICROLINE ML660PS</p> +</li> + +<li> +<p>Seiko Epson PM-900C, 880C, 820C, 730C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsa</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U103</p> +</li> + +<li> +<p>Belkin F5U120</p> +</li> + +<li> +<p>e-Tek Labs Kwik232</p> +</li> + +<li> +<p>GoHubs GoCOM232</p> +</li> + +<li> +<p>Peracom single port serial adapter</p> +</li> + +<li> +<p>Vodafone Mobile Connect 3G datacard</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubser&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubser</span>(4)</span></a> driver +provides support for the BWCT console management serial adapters.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uftdi</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>B&B Electronics USB->RS422/485 adapter</p> +</li> + +<li> +<p>HP USB-Serial adapter shipped with some HP laptops</p> +</li> + +<li> +<p>Inland UAS111</p> +</li> + +<li> +<p>QVS USC-1000</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uplcom&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uplcom</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>ATEN UC-232A</p> +</li> + +<li> +<p>BAFO BF-800</p> +</li> + +<li> +<p>BAFO BF-810</p> +</li> + +<li> +<p>ELECOM UC-SGT</p> +</li> + +<li> +<p>HAL Corporation Crossam2+USB IR commander</p> +</li> + +<li> +<p>Hama USB RS-232 Serial Adapter</p> +</li> + +<li> +<p>IOGEAR UC-232A</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ2</p> +</li> + +<li> +<p>I/O DATA USB-RSAQ3</p> +</li> + +<li> +<p>PLANEX USB-RS232 URS-03</p> +</li> + +<li> +<p>RATOC REX-USB60</p> +</li> + +<li> +<p>Sandberg USB to Serial Link (model number 133-08)</p> +</li> + +<li> +<p>SOURCENEXT KeikaiDenwa 8 (with and without charger)</p> +</li> + +<li> +<p>Sony Ericsson USB Cable (Susteen USB Data Cable)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umct&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umct</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U109</p> +</li> + +<li> +<p>Belkin F5U409</p> +</li> + +<li> +<p>D-Link DU-H3SP USB BAY Hub</p> +</li> + +<li> +<p>Magic Control Technology USB-232</p> +</li> + +<li> +<p>Sitecom USB-232</p> +</li> +</ul> + +<p>The following devices are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uscanner&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uscanner</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>Acer Acerscan 320U</p> +</li> + +<li> +<p>Acer Acerscan 620U</p> +</li> + +<li> +<p>Acer Acerscan 640U</p> +</li> + +<li> +<p>Acer Acerscan 1240U</p> +</li> + +<li> +<p>Acer Acerscan C310U</p> +</li> + +<li> +<p>AGFA SnapScan 1212U</p> +</li> + +<li> +<p>AGFA SnapScan 1236U</p> +</li> + +<li> +<p>AGFA SnapScan e20</p> +</li> + +<li> +<p>AGFA SnapScan e25</p> +</li> + +<li> +<p>AGFA SnapScan e26</p> +</li> + +<li> +<p>AGFA SnapScan e40</p> +</li> + +<li> +<p>AGFA SnapScan e50</p> +</li> + +<li> +<p>AGFA SnapScan e52</p> +</li> + +<li> +<p>AGFA SnapScan Touch</p> +</li> + +<li> +<p>Avision 1200U</p> +</li> + +<li> +<p>Canon CanoScan N656U</p> +</li> + +<li> +<p>Canon CanoScan N676U</p> +</li> + +<li> +<p>Canon CanoScan N1220U</p> +</li> + +<li> +<p>Canon CanoScan LIDE 20</p> +</li> + +<li> +<p>Canon CanoScan LIDE 30</p> +</li> + +<li> +<p>Epson Perfection 610</p> +</li> + +<li> +<p>Epson Perfection 636U / 636Photo</p> +</li> + +<li> +<p>Epson Perfection 640U</p> +</li> + +<li> +<p>Epson Perfection 1200U / 1200Photo</p> +</li> + +<li> +<p>Epson Perfection 1240U / 1240Photo</p> +</li> + +<li> +<p>Epson Perfection 1250</p> +</li> + +<li> +<p>Epson Perfection 1260</p> +</li> + +<li> +<p>Epson Expression 1600</p> +</li> + +<li> +<p>Epson Perfection 1640SU</p> +</li> + +<li> +<p>Epson Perfection 1650</p> +</li> + +<li> +<p>Epson Perfection 1660</p> +</li> + +<li> +<p>Epson Perfection 1670</p> +</li> + +<li> +<p>Epson Perfection 3200</p> +</li> + +<li> +<p>Epson GT-8400UF</p> +</li> + +<li> +<p>Epson GT-9300UF</p> +</li> + +<li> +<p>Epson GT-9700F</p> +</li> + +<li> +<p>Hewlett Packard Photosmart S20</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 2200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 3300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 3400CSE</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4100C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 4300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5300C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 5400C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 6200C</p> +</li> + +<li> +<p>Hewlett Packard Scanjet 6300C</p> +</li> + +<li> +<p>KYE ColorPage Vivid-Pro</p> +</li> + +<li> +<p>Microtek Phantom 336CX</p> +</li> + +<li> +<p>Microtek Phantom C6</p> +</li> + +<li> +<p>Microtek ScanMaker V6UL</p> +</li> + +<li> +<p>Microtek ScanMaker V6USL</p> +</li> + +<li> +<p>Microtek ScanMaker X6U</p> +</li> + +<li> +<p>Minolta 5400</p> +</li> + +<li> +<p>Mustek 600 CU</p> +</li> + +<li> +<p>Mustek 1200 CU</p> +</li> + +<li> +<p>Mustek 1200 UB</p> +</li> + +<li> +<p>Mustek 1200 USB</p> +</li> + +<li> +<p>Mustek BearPaw 1200F</p> +</li> + +<li> +<p>Mustek BearPaw 1200TA</p> +</li> + +<li> +<p>NatSemi BearPaw 1200</p> +</li> + +<li> +<p>Nikon CoolScan LS40 ED</p> +</li> + +<li> +<p>Primax 6200</p> +</li> + +<li> +<p>Primax Colorado 1200u</p> +</li> + +<li> +<p>Primax Colorado 600u</p> +</li> + +<li> +<p>Primax Colorado USB 19200</p> +</li> + +<li> +<p>Primax Colorado USB 9600</p> +</li> + +<li> +<p>Primax G2-200</p> +</li> + +<li> +<p>Primax G2-300</p> +</li> + +<li> +<p>Primax G2-600</p> +</li> + +<li> +<p>Primax G2600</p> +</li> + +<li> +<p>Primax G2E-300</p> +</li> + +<li> +<p>Primax G2E-3002</p> +</li> + +<li> +<p>Primax G2E-600</p> +</li> + +<li> +<p>Primax G2E600</p> +</li> + +<li> +<p>Primax G2X-300</p> +</li> + +<li> +<p>Primax G600</p> +</li> + +<li> +<p>Primax ReadyScan 636i</p> +</li> + +<li> +<p>Ultima 1200 UB Plus</p> +</li> + +<li> +<p>UMAX Astra 1220U</p> +</li> + +<li> +<p>UMAX Astra 1236U</p> +</li> + +<li> +<p>UMAX Astra 2000U</p> +</li> + +<li> +<p>UMAX Astra 2100U</p> +</li> + +<li> +<p>UMAX Astra 2200U</p> +</li> + +<li> +<p>UMAX Astra 3400</p> +</li> + +<li> +<p>Visioneer OneTouch 3000</p> +</li> + +<li> +<p>Visioneer OneTouch 5300</p> +</li> + +<li> +<p>Visioneer OneTouch 7600</p> +</li> + +<li> +<p>Visioneer OneTouch 6100</p> +</li> + +<li> +<p>Visioneer OneTouch 6200</p> +</li> + +<li> +<p>Visioneer OneTouch 8100</p> +</li> + +<li> +<p>Visioneer OneTouch 8600</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umass</span>(4)</span></a> driver +supports USB Mass Storage devices, including:</p> + +<ul> +<li> +<p>ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M</p> +</li> + +<li> +<p>Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20</p> +</li> + +<li> +<p>FujiFilm Zip USB Drive ZDR100 USB A</p> +</li> + +<li> +<p>GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M</p> +</li> + +<li> +<p>IBM 32MB USB Memory Key (P/N 22P5296)</p> +</li> + +<li> +<p>IBM 256MB USB Drive (MSYSTEM DiskOnKey2)</p> +</li> + +<li> +<p>IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)</p> +</li> + +<li> +<p>I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)</p> +</li> + +<li> +<p>I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)</p> +</li> + +<li> +<p>I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI</p> +</li> + +<li> +<p>Iomega USB Zip 100/250 drive</p> +</li> + +<li> +<p>Iomega Zip750 USB2.0 drive</p> +</li> + +<li> +<p>Keian USB1.1/2.0 3.5-inch HDD Case KU350A</p> +</li> + +<li> +<p>Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0</p> +</li> + +<li> +<p>LaCie P3 HardDrive USB 200GB</p> +</li> + +<li> +<p>Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive</p> +</li> + +<li> +<p>Logitec Mobile USB Memory LMC-256UD</p> +</li> + +<li> +<p>Logitec USB1.1/2.0 HDD Unit SHD-E60U2</p> +</li> + +<li> +<p>Logitec USB Double-Speed Floppy Drive LFD-31U2</p> +</li> + +<li> +<p>Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)</p> +</li> + +<li> +<p>MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M</p> +</li> + +<li> +<p>MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm</p> +</li> + +<li> +<p>MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2</p> +</li> + +<li> +<p>MELCO USB2.0 MO Drive MO-CH640U2</p> +</li> + +<li> +<p>Matshita CF-VFDU03 floppy drive</p> +</li> + +<li> +<p>Merlin SM300 MP3/WMA Player (256Mb)</p> +</li> + +<li> +<p>Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable</p> +</li> + +<li> +<p>Motorola E398 Mobile Phone (TransFlash memory card)</p> +</li> + +<li> +<p>NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U</p> +</li> + +<li> +<p>PNY Attache Flash Drive</p> +</li> + +<li> +<p>Panasonic ("Matshita FDD CF-VFDU03")</p> +</li> + +<li> +<p>Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW</p> +</li> + +<li> +<p>Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW)</p> +</li> + +<li> +<p>Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)</p> +</li> + +<li> +<p>Panasonic floppy drive</p> +</li> + +<li> +<p>Qware BeatZkey! Pro</p> +</li> + +<li> +<p>RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B</p> +</li> + +<li> +<p>SanDisk SDDR-31 (Compact Flash)</p> +</li> + +<li> +<p>SanDisk SDDR-75 (only Compact Flash port works)</p> +</li> + +<li> +<p>Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick)</p> +</li> + +<li> +<p>Sony Portable CD-R/RW Drive CRX10U (CDROM only)</p> +</li> + +<li> +<p>TEAC Portable USB CD-ROM Unit CD-110PU/210PU</p> +</li> + +<li> +<p>Time DPA20B MP3 Player (1Gb)</p> +</li> + +<li> +<p>Trek Thumbdrive 8MB</p> +</li> + +<li> +<p>VAIO floppy drive (includes Y-E Data Flashbuster-U)</p> +</li> + +<li> +<p>Y-E Data floppy drive (720/1.44/2.88Mb)</p> +</li> +</ul> + +<p>Among the supported digital cameras are:</p> + +<ul> +<li> +<p>Asahi Optical (PENTAX) Optio 230 & 330</p> +</li> +</ul> + +<p>Audio Devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uaudio&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uaudio</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uvisor&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uvisor</span>(4)</span></a> driver +supports the following devices:</p> + +<ul> +<li> +<p>Handspring Treo</p> +</li> + +<li> +<p>Handspring Treo 600</p> +</li> + +<li> +<p>Handspring Visor</p> +</li> + +<li> +<p>Palm I705</p> +</li> + +<li> +<p>Palm M125</p> +</li> + +<li> +<p>Palm M130</p> +</li> + +<li> +<p>Palm M500</p> +</li> + +<li> +<p>Palm M505</p> +</li> + +<li> +<p>Palm M515</p> +</li> + +<li> +<p>Palm Tungsten T</p> +</li> + +<li> +<p>Palm Tungsten Z</p> +</li> + +<li> +<p>Palm Zire</p> +</li> + +<li> +<p>Palm Zire 31</p> +</li> + +<li> +<p>Sony Clie 4.0</p> +</li> + +<li> +<p>Sony Clie 4.1</p> +</li> + +<li> +<p>Sony Clie 5.0</p> +</li> + +<li> +<p>Sony Clie PEG-S500C</p> +</li> + +<li> +<p>Sony Clie NX60</p> +</li> + +<li> +<p>Sony Clie S360</p> +</li> + +<li> +<p>Sony Clie TJ37</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.13 IEEE 1394 (Firewire) +Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.14 Bluetooth Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_bt3c&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_bt3c</span>(4)</span></a> +driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_ubt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_ubt</span>(4)</span></a> driver +supports all Bluetooth USB devices that conform with the Bluetooth specification v1.1, +including:</p> + +<ul> +<li> +<p>3Com 3CREB96</p> +</li> + +<li> +<p>AIPTEK BR0R02</p> +</li> + +<li> +<p>EPoX BT-DG02</p> +</li> + +<li> +<p>Mitsumi Bluetooth USB adapter</p> +</li> + +<li> +<p>MSI MS-6967</p> +</li> + +<li> +<p>TDK Bluetooth USB adapter</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CRYPTO-ACCEL" name="CRYPTO-ACCEL">3.15 Cryptographic +Accelerators</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hifn&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hifn</span>(4)</span></a> driver +supports various cards containing the Hifn 7751, 7951, 7811, 7955, and 7956 chipsets, +such as:</p> + +<ul> +<li> +<p>Invertex AEON</p> +</li> + +<li> +<p>Hifn 7751</p> +</li> + +<li> +<p>PowerCrypt</p> +</li> + +<li> +<p>XL-Crypt</p> +</li> + +<li> +<p>NetSec 7751</p> +</li> + +<li> +<p>Soekris Engineering vpn1201 and vpn1211</p> +</li> + +<li> +<p>Soekris Engineering vpn1401 and vpn1411</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=safe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">safe</span>(4)</span></a> driver +supports cards containing any of the following chips:</p> + +<ul> +<li> +<p>SafeNet 1141</p> +</li> + +<li> +<p>SafeNet 1741</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ubsec</span>(4)</span></a> driver +supports cards containing any of the following chips:</p> + +<ul> +<li> +<p>Bluesteel 5501</p> +</li> + +<li> +<p>Bluesteel 5601</p> +</li> + +<li> +<p>Broadcom BCM5801</p> +</li> + +<li> +<p>Broadcom BCM5802</p> +</li> + +<li> +<p>Broadcom BCM5805</p> +</li> + +<li> +<p>Broadcom BCM5820</p> +</li> + +<li> +<p>Broadcom BCM5821</p> +</li> + +<li> +<p>Broadcom BCM5822</p> +</li> + +<li> +<p>Broadcom BCM5823</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC" name="MISC">3.16 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&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fdc</span>(4)</span></a> +driver)</p> + +<p>Keyboards including:</p> + +<ul> +<li> +<p>Standard keyboards</p> +</li> + +<li> +<p>USB keyboards (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ukbd</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<br /> +<br /> +<p>Pointing devices including:</p> + +<ul> +<li> +<p>Bus mice and compatible devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mse&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mse</span>(4)</span></a> +driver)</p> +</li> + +<li> +<p>Serial mice and compatible devices</p> +</li> + +<li> +<p>USB mice (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ums</span>(4)</span></a> +driver)</p> +</li> +</ul> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-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">Xorg</b> can be found at <a href="http://www.x.org/" +target="_top">http://www.x.org/</a>.</p> +</blockquote> +</div> + +<br /> +<br /> +<p>“PC-9821 standard” parallel ports (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppc</span>(4)</span></a> +driver)</p> + +<p>Joystick port of SoundBlaster(98) (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=joy&sektion=4&manpath=FreeBSD+6.1-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>Power Management Controller of NEC PC-98 Note (pmc driver)</p> +</div> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/hardware-sparc64.html b/en/releases/6.1R/hardware-sparc64.html new file mode 100644 index 0000000000..2cbacab847 --- /dev/null +++ b/en/releases/6.1R/hardware-sparc64.html @@ -0,0 +1,2008 @@ +<!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/sparc64 6.1-RELEASE Hardware Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/sparc64 6.1-RELEASE Hardware +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<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="#SUPPORT-SYS">Supported Systems</a></dt> + +<dd> +<dl> +<dt>2.1 <a href="#AEN27">Fully Supported Systems</a></dt> + +<dt>2.2 <a href="#AEN81">Partially Supported Systems</a></dt> + +<dt>2.3 <a href="#AEN89">Unsupported Systems</a></dt> +</dl> +</dd> + +<dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + +<dd> +<dl> +<dt>3.1 <a href="#DISK">Disk Controllers</a></dt> + +<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt> + +<dt>3.3 <a href="#TOKENRING">Token Ring Interfaces</a></dt> + +<dt>3.4 <a href="#FDDI">FDDI Interfaces</a></dt> + +<dt>3.5 <a href="#ATM">ATM Interfaces</a></dt> + +<dt>3.6 <a href="#WLAN">Wireless Network Interfaces</a></dt> + +<dt>3.7 <a href="#MISC-NETWORK">Miscellaneous Networks</a></dt> + +<dt>3.8 <a href="#ISDN">ISDN Interfaces</a></dt> + +<dt>3.9 <a href="#SERIAL">Serial Interfaces</a></dt> + +<dt>3.10 <a href="#SOUND">Sound Devices</a></dt> + +<dt>3.11 <a href="#CAMERA">Camera and Video Capture Devices</a></dt> + +<dt>3.12 <a href="#USB">USB Devices</a></dt> + +<dt>3.13 <a href="#FIREWIRE">IEEE 1394 (Firewire) Devices</a></dt> + +<dt>3.14 <a href="#BLUETOOTH">Bluetooth Devices</a></dt> + +<dt>3.15 <a href="#CRYPTO-ACCEL">Cryptographic Accelerators</a></dt> + +<dt>3.16 <a href="#MISC">Miscellaneous</a></dt> +</dl> +</dd> +</dl> +</div> + +<div class="SECT1"> +<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This document contains the hardware compatibility notes for FreeBSD 6.1-RELEASE on the +UltraSPARC hardware platform (also referred to as FreeBSD/sparc64 6.1-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 UltraSPARC hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.</p> +</blockquote> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT-SYS" name="SUPPORT-SYS">2 Supported Systems</a></h2> + +<p>This section describes the systems currently known to be supported by FreeBSD on the +UltraSPARC platform. For background information on the various hardware designs see the +<a href="http://sunsolve.sun.com/handbook_pub/" target="_top">Sun System +Handbook</a>.</p> + +<p>SMP is supported on all systems with more than 1 processor.</p> + +<p>If you have a system that is not listed here, it may not have been tested with FreeBSD +6.1-RELEASE. We encourage you to try it and send a note to the <a +href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-sparc64" target="_top">FreeBSD +SPARC porting mailing list</a> with your results, including which devices work and which +do not.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN27" name="AEN27">2.1 Fully Supported Systems</a></h3> + +<p>The following systems are fully supported by FreeBSD.</p> + +<ul> +<li> +<p>Blade 100</p> +</li> + +<li> +<p>Blade 150</p> +</li> + +<li> +<p>Enterprise 220R</p> +</li> + +<li> +<p>Enterprise 250</p> +</li> + +<li> +<p>Enterprise 420R</p> +</li> + +<li> +<p>Enterprise 450</p> +</li> + +<li> +<p>Fire V100</p> +</li> + +<li> +<p>Fire V120</p> +</li> + +<li> +<p>Netra t1 105</p> +</li> + +<li> +<p>Netra T1 AC200/DC200</p> +</li> + +<li> +<p>Netra t 1100</p> +</li> + +<li> +<p>Netra t 1120</p> +</li> + +<li> +<p>Netra t 1125</p> +</li> + +<li> +<p>Netra t 1400/1405</p> +</li> + +<li> +<p>Netra 120</p> +</li> + +<li> +<p>Netra X1</p> +</li> + +<li> +<p>SPARCEngine Ultra AXi</p> +</li> + +<li> +<p>SPARCEngine Ultra AXmp</p> +</li> + +<li> +<p>Ultra 1E</p> +</li> + +<li> +<p>Ultra 2</p> +</li> + +<li> +<p>Ultra 5</p> +</li> + +<li> +<p>Ultra 10</p> +</li> + +<li> +<p>Ultra 30</p> +</li> + +<li> +<p>Ultra 60</p> +</li> + +<li> +<p>Ultra 80</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN81" name="AEN81">2.2 Partially Supported Systems</a></h3> + +<p>The following systems are partially supported by FreeBSD. In particular the onboard +scsi controller in sbus systems is not supported.</p> + +<ul> +<li> +<p>Enterprise 3500</p> +</li> + +<li> +<p>Enterprise 4500</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN89" name="AEN89">2.3 Unsupported Systems</a></h3> + +<p>The following systems are not supported by FreeBSD. This may be due to lack of +processor support (UltraSPARC III), due to a quirk in the system design that makes +FreeBSD unstable, or due to lack of support for sufficient onboard devices to make +FreeBSD generally useful.</p> + +<ul> +<li> +<p>All systems containing UltraSPARC III processor(s).</p> +</li> + +<li> +<p>Ultra 1</p> +</li> +</ul> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2> + +$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.9.2.2 +2006/05/01 08:26:00 brueffer Exp $ + +<p>This section describes the devices currently known to be supported by with FreeBSD on +the UltraSPARC platform. Other configurations may also work, but simply have not been +tested yet. Feedback, updates, and corrections to this list are encouraged.</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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.</p> + +<div class="NOTE"> +<blockquote class="NOTE"> +<p><b>Note:</b> The device lists in this document are being generated automatically from +FreeBSD manual pages. This means that some devices, which are supported by multiple +drivers, may appear multiple times.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DISK" name="DISK">3.1 Disk Controllers</a></h3> + +<p>IDE/ATA controllers (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> +driver)</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a> driver +supports the following SCSI host adapter chips and SCSI controller cards:</p> + +<ul> +<li> +<p>Adaptec AIC7770 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7850 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7860 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7870 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7880 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7890 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7891 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7892 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7895 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7896 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7897 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7899 host adapter chip</p> +</li> + +<li> +<p>Adaptec 274X(W)</p> +</li> + +<li> +<p>Adaptec 274X(T)</p> +</li> + +<li> +<p>Adaptec 284X</p> +</li> + +<li> +<p>Adaptec 2910</p> +</li> + +<li> +<p>Adaptec 2915</p> +</li> + +<li> +<p>Adaptec 2920</p> +</li> + +<li> +<p>Adaptec 2930C</p> +</li> + +<li> +<p>Adaptec 2930U2</p> +</li> + +<li> +<p>Adaptec 2940</p> +</li> + +<li> +<p>Adaptec 2940J</p> +</li> + +<li> +<p>Adaptec 2940N</p> +</li> + +<li> +<p>Adaptec 2940U</p> +</li> + +<li> +<p>Adaptec 2940AU</p> +</li> + +<li> +<p>Adaptec 2940UW</p> +</li> + +<li> +<p>Adaptec 2940UW Dual</p> +</li> + +<li> +<p>Adaptec 2940UW Pro</p> +</li> + +<li> +<p>Adaptec 2940U2W</p> +</li> + +<li> +<p>Adaptec 2940U2B</p> +</li> + +<li> +<p>Adaptec 2950U2W</p> +</li> + +<li> +<p>Adaptec 2950U2B</p> +</li> + +<li> +<p>Adaptec 19160B</p> +</li> + +<li> +<p>Adaptec 29160B</p> +</li> + +<li> +<p>Adaptec 29160N</p> +</li> + +<li> +<p>Adaptec 3940</p> +</li> + +<li> +<p>Adaptec 3940U</p> +</li> + +<li> +<p>Adaptec 3940AU</p> +</li> + +<li> +<p>Adaptec 3940UW</p> +</li> + +<li> +<p>Adaptec 3940AUW</p> +</li> + +<li> +<p>Adaptec 3940U2W</p> +</li> + +<li> +<p>Adaptec 3950U2</p> +</li> + +<li> +<p>Adaptec 3960</p> +</li> + +<li> +<p>Adaptec 39160</p> +</li> + +<li> +<p>Adaptec 3985</p> +</li> + +<li> +<p>Adaptec 4944UW</p> +</li> + +<li> +<p>NEC PC-9821Xt13 (PC-98)</p> +</li> + +<li> +<p>NEC RvII26 (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B02L/B09 (PC-98)</p> +</li> + +<li> +<p>NEC SV-98/2-B03 (PC-98)</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahd</span>(4)</span></a> driver +supports the following:</p> + +<ul> +<li> +<p>Adaptec AIC7901 host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7901A host adapter chip</p> +</li> + +<li> +<p>Adaptec AIC7902 host adapter chip</p> +</li> + +<li> +<p>Adaptec 29320 host adapter</p> +</li> + +<li> +<p>Adaptec 39320 host adapter</p> +</li> + +<li> +<p>Many motherboards with on-board SCSI support</p> +</li> +</ul> + +<p>Controllers supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>MegaRAID SCSI 320-1E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4E</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2X</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-4X</p> +</li> + +<li> +<p>MegaRAID SATA 300-8X</p> +</li> + +<li> +<p>MegaRAID SATA 150-4</p> +</li> + +<li> +<p>MegaRAID SATA 150-6</p> +</li> + +<li> +<p>MegaRAID i4 133 RAID</p> +</li> + +<li> +<p>MegaRAID SCSI 320-0</p> +</li> + +<li> +<p>MegaRAID SCSI 320-1</p> +</li> + +<li> +<p>MegaRAID SCSI 320-2</p> +</li> + +<li> +<p>MegaRAID SCSI 320-4</p> +</li> + +<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 Elite 1650 (Series 4xx)</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 3/QC</p> +</li> + +<li> +<p>Dell PERC 4/DC</p> +</li> + +<li> +<p>Dell PERC 4/IM</p> +</li> + +<li> +<p>Dell PERC 4/SC</p> +</li> + +<li> +<p>Dell PERC 4/Di</p> +</li> + +<li> +<p>Dell PERC 4e/DC</p> +</li> + +<li> +<p>Dell PERC 4e/Di</p> +</li> + +<li> +<p>Dell PERC 4e/Si</p> +</li> + +<li> +<p>Dell PERC 4ei</p> +</li> + +<li> +<p>HP NetRAID-1/Si</p> +</li> + +<li> +<p>HP NetRAID-3/Si (D4943A)</p> +</li> + +<li> +<p>HP Embedded NetRAID</p> +</li> + +<li> +<p>Intel RAID Controller SRCS16</p> +</li> + +<li> +<p>Intel RAID Controller SRCU42X</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=esp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">esp</span>(4)</span></a> driver +provides support for the Qlogic FAS216 and FAS408 SCSI controller chips found in a wide +variety of systems and peripheral boards. This includes the Qlogic SCSI cards found in +most Sun Ultra 1e and Ultra 2 machines. For Qlogic PCI SCSI host adapters, the isp(4) +driver should be used in place of the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=esp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">esp</span>(4)</span></a> +driver.</p> + +<p>Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>ISP1000</p> +</li> + +<li> +<p>ISP1020</p> +</li> + +<li> +<p>ISP1040</p> +</li> + +<li> +<p>Qlogic 1240</p> +</li> + +<li> +<p>Qlogic 1020</p> +</li> + +<li> +<p>Qlogic 1040</p> +</li> + +<li> +<p>Qlogic 1080</p> +</li> + +<li> +<p>Qlogic 1280</p> +</li> + +<li> +<p>Qlogic 12160</p> +</li> + +<li> +<p>Qlogic 210X</p> +</li> + +<li> +<p>Qlogic 220X</p> +</li> + +<li> +<p>Qlogic 2300</p> +</li> + +<li> +<p>Qlogic 2312</p> +</li> + +<li> +<p>Qlogic 234X</p> +</li> + +<li> +<p>Qlogic 2322</p> +</li> + +<li> +<p>Qlogic 200</p> +</li> +</ul> + +<p>The following controllers are supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> +driver:</p> + +<ul> +<li> +<p>LSI Logic 53c1030 (Dual Ultra320 SCSI)</p> +</li> + +<li> +<p>LSI Logic FC909 (1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC909A (Dual 1Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC919 (2Gb/s Fibre Channel)</p> +</li> + +<li> +<p>LSI Logic FC929, LSI Logic FC929X (Dual 2Gb/s Fibre Channel)</p> +</li> +</ul> + +<p>The SCSI controller chips supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver +can be found onboard on many systems including:</p> + +<ul> +<li> +<p>Dell PowerEdge 1750</p> +</li> + +<li> +<p>IBM eServer xSeries 335</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> driver +provides support for the following NCR/Symbios SCSI controller chips:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C820</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C875J</p> +</li> + +<li> +<p>53C885</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The following add-on boards are known to be supported:</p> + +<ul> +<li> +<p>I-O DATA SC-98/PCI (PC-98)</p> +</li> + +<li> +<p>I-O DATA SC-PCI (PC-98)</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> driver +provides support for the following Symbios/LSI Logic PCI SCSI controllers:</p> + +<ul> +<li> +<p>53C810</p> +</li> + +<li> +<p>53C810A</p> +</li> + +<li> +<p>53C815</p> +</li> + +<li> +<p>53C825</p> +</li> + +<li> +<p>53C825A</p> +</li> + +<li> +<p>53C860</p> +</li> + +<li> +<p>53C875</p> +</li> + +<li> +<p>53C876</p> +</li> + +<li> +<p>53C895</p> +</li> + +<li> +<p>53C895A</p> +</li> + +<li> +<p>53C896</p> +</li> + +<li> +<p>53C897</p> +</li> + +<li> +<p>53C1000</p> +</li> + +<li> +<p>53C1000R</p> +</li> + +<li> +<p>53C1010-33</p> +</li> + +<li> +<p>53C1010-66</p> +</li> + +<li> +<p>53C1510D</p> +</li> +</ul> + +<p>The SCSI controllers supported by <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a> can be +either embedded on a motherboard, or on one of the following add-on boards:</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>I-O DATA SC-UPCI (PC-98)</p> +</li> + +<li> +<p>Logitec LHA-521UA (PC-98)</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> + +<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&sektion=4&manpath=FreeBSD+6.1-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&sektion=1&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&sektion=4&manpath=FreeBSD+6.1-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&sektion=4&manpath=FreeBSD+6.1-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>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver provides +support for the following chipsets:</p> + +<ul> +<li> +<p>DEC/Intel 21143</p> +</li> + +<li> +<p>ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II</p> +</li> + +<li> +<p>ASIX Electronics AX88140A and AX88141</p> +</li> + +<li> +<p>Conexant LANfinity RS7112 (miniPCI)</p> +</li> + +<li> +<p>Davicom DM9009, DM9100, DM9102 and DM9102A</p> +</li> + +<li> +<p>Lite-On 82c168 and 82c169 PNIC</p> +</li> + +<li> +<p>Lite-On/Macronix 82c115 PNIC II</p> +</li> + +<li> +<p>Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732</p> +</li> + +<li> +<p>Xircom X3201 (cardbus only)</p> +</li> +</ul> + +<p>The following NICs are known to work with the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a> driver at this +time:</p> + +<ul> +<li> +<p>3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Abocom FE2500</p> +</li> + +<li> +<p>Accton EN1217 (98715A)</p> +</li> + +<li> +<p>Accton EN2242 MiniPCI</p> +</li> + +<li> +<p>Adico AE310TX (98715A)</p> +</li> + +<li> +<p>Alfa Inc GFC2204 (ASIX AX88140A)</p> +</li> + +<li> +<p>Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, +non-MII)</p> +</li> + +<li> +<p>Built in DE500-BA on DEC Alpha workstations (21143, non-MII)</p> +</li> + +<li> +<p>Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, +MII)</p> +</li> + +<li> +<p>Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)</p> +</li> + +<li> +<p>CNet Pro110B (ASIX AX88140A)</p> +</li> + +<li> +<p>CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)</p> +</li> + +<li> +<p>Compex RL100-TX (98713 or 98713A)</p> +</li> + +<li> +<p>D-Link DFE-570TX (21143, MII, quad port)</p> +</li> + +<li> +<p>Digital DE500-BA 10/100 (21143, non-MII)</p> +</li> + +<li> +<p>ELECOM Laneed LD-CBL/TXA (ADMtek AN985)</p> +</li> + +<li> +<p>Hawking CB102 CardBus</p> +</li> + +<li> +<p>IBM EtherJet Cardbus Adapter</p> +</li> + +<li> +<p>Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)</p> +</li> + +<li> +<p>Jaton XpressNet (Davicom DM9102)</p> +</li> + +<li> +<p>Kingston KNE100TX (21143, MII)</p> +</li> + +<li> +<p>Kingston KNE110TX (PNIC 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>LinkSys LNE100TX v2.0 (PNIC II 82c115)</p> +</li> + +<li> +<p>LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)</p> +</li> + +<li> +<p>Matrox FastNIC 10/100 (PNIC 82c168, 82c169)</p> +</li> + +<li> +<p>Melco LGY-PCI-TXL</p> +</li> + +<li> +<p>Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)</p> +</li> + +<li> +<p>Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A (98713A)</p> +</li> + +<li> +<p>NDC SOHOware SFA110A Rev B4 (98715AEC-C)</p> +</li> + +<li> +<p>NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)</p> +</li> + +<li> +<p>Netgear FA511</p> +</li> + +<li> +<p>PlaneX FNW-3602-T (ADMtek AN985)</p> +</li> + +<li> +<p>SMC EZ Card 10/100 1233A-TX (ADMtek AN985)</p> +</li> + +<li> +<p>SVEC PN102-TX (98713)</p> +</li> + +<li> +<p>Xircom Cardbus Realport</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet 10/100</p> +</li> + +<li> +<p>Xircom Cardbus Ethernet II 10/100</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fxp</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Intel EtherExpress PRO/10</p> +</li> + +<li> +<p>Intel InBusiness 10/100</p> +</li> + +<li> +<p>Intel PRO/100B / EtherExpressPRO/100 B PCI 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>Contec C-NET(PI)-100TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)</p> +</li> + +<li> +<p>NEC PC-9821X-B06 (PC-98)</p> +</li> + +<li> +<p>Many on-board network interfaces on Intel motherboards</p> +</li> +</ul> + +<p>Cards supported by <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gem&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gem</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Sun GEM gigabit Ethernet</p> +</li> + +<li> +<p>Sun ERI 10/100 Mbps Ethernet</p> +</li> + +<li> +<p>Apple GMAC</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server +models. Cards supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a> driver +include:</p> + +<ul> +<li> +<p>Sun PCI SunSwift Adapter</p> +</li> + +<li> +<p>Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)</p> +</li> + +<li> +<p>Sun PCI Sun100BaseT Adapter 2.0</p> +</li> + +<li> +<p>Sun SBus Sun100BaseT 2.0</p> +</li> + +<li> +<p>Sun PCI Quad FastEthernet Controller</p> +</li> + +<li> +<p>Sun SBus Quad FastEthernet Controller</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">re</span>(4)</span></a> driver supports +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based Fast Ethernet and Gigabit +Ethernet adapters including:</p> + +<ul> +<li> +<p>Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)</p> +</li> + +<li> +<p>Compaq Evo N1015v Integrated Ethernet (8139C+)</p> +</li> + +<li> +<p>Corega CG-LAPCIGT Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>D-Link DGE-528(T) Gigabit Ethernet (8169S)</p> +</li> + +<li> +<p>Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)</p> +</li> + +<li> +<p>LevelOne GNC-0105T (8169S)</p> +</li> + +<li> +<p>PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)</p> +</li> + +<li> +<p>Xterasys XN-152 10/100/1000 NIC (8169)</p> +</li> +</ul> + +<p>Adapters supported by the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a> driver +include:</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>Belkin F5D5000</p> +</li> + +<li> +<p>BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)</p> +</li> + +<li> +<p>Compaq HNE-300</p> +</li> + +<li> +<p>CompUSA no-name 10/100 PCI Ethernet NIC</p> +</li> + +<li> +<p>Corega FEther CB-TXD</p> +</li> + +<li> +<p>Corega FEtherII CB-TXD</p> +</li> + +<li> +<p>D-Link DFE-528TX</p> +</li> + +<li> +<p>D-Link DFE-530TX+</p> +</li> + +<li> +<p>D-Link DFE-538TX</p> +</li> + +<li> +<p>D-Link DFE-690TXD</p> +</li> + +<li> +<p>Edimax EP-4103DL CardBus</p> +</li> + +<li> +<p>Encore ENL832-TX 10/100 M PCI</p> +</li> + +<li> +<p>Farallon NetLINE 10/100 PCI</p> +</li> + +<li> +<p>Genius GF100TXR</p> +</li> + +<li> +<p>GigaFast Ethernet EE100-AXP</p> +</li> + +<li> +<p>KTX-9130TX 10/100 Fast Ethernet</p> +</li> + +<li> +<p>LevelOne FPC-0106TX</p> +</li> + +<li> +<p>Longshine LCS-8038TX-R</p> +</li> + +<li> +<p>NDC Communications NE100TX-E</p> +</li> + +<li> +<p>Netronix Inc. EA-1210 NetEther 10/100</p> +</li> + +<li> +<p>Nortel Networks 10/100BaseTX</p> +</li> + +<li> +<p>OvisLink LEF-8129TX</p> +</li> + +<li> +<p>OvisLink LEF-8139TX</p> +</li> + +<li> +<p>Peppercon AG ROL-F</p> +</li> + +<li> +<p>Planex FNW-3800-TX</p> +</li> + +<li> +<p>SMC EZ Card 10/100 PCI 1211-TX</p> +</li> + +<li> +<p>SOHO (PRAGMATIC) UE-1211C</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver supports +the following hardware:</p> + +<ul> +<li> +<p>3Com 3c900-TPO</p> +</li> + +<li> +<p>3Com 3c900-COMBO</p> +</li> + +<li> +<p>3Com 3c905-TX</p> +</li> + +<li> +<p>3Com 3c905-T4</p> +</li> + +<li> +<p>3Com 3c900B-TPO</p> +</li> + +<li> +<p>3Com 3c900B-TPC</p> +</li> + +<li> +<p>3Com 3c900B-FL</p> +</li> + +<li> +<p>3Com 3c900B-COMBO</p> +</li> + +<li> +<p>3Com 3c905B-T4</p> +</li> + +<li> +<p>3Com 3c905B-TX</p> +</li> + +<li> +<p>3Com 3c905B-FX</p> +</li> + +<li> +<p>3Com 3c905B-COMBO</p> +</li> + +<li> +<p>3Com 3c905C-TX</p> +</li> + +<li> +<p>3Com 3c980, 3c980B, and 3c980C server adapters</p> +</li> + +<li> +<p>3Com 3cSOHO100-TX OfficeConnect adapters</p> +</li> + +<li> +<p>3Com 3c450 HomeConnect adapters</p> +</li> + +<li> +<p>3Com 3c555, 3c556 and 3c556B mini-PCI adapters</p> +</li> + +<li> +<p>3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, +3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters</p> +</li> + +<li> +<p>3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded +adapters</p> +</li> +</ul> + +<p>Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a +built-in proprietary modem. Neither the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a> driver nor any +other driver supports this modem.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="TOKENRING" name="TOKENRING">3.3 Token Ring Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FDDI" name="FDDI">3.4 FDDI Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ATM" name="ATM">3.5 ATM Interfaces</a></h3> + +<p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fatm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fatm</span>(4)</span></a> +drivers)</p> + +<p>FORE Systems, Inc. HE155 and HE622 ATM interfaces (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hatm&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hatm</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="WLAN" name="WLAN">3.6 Wireless Network Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC-NETWORK" name="MISC-NETWORK">3.7 Miscellaneous +Networks</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="ISDN" name="ISDN">3.8 ISDN Interfaces</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SERIAL" name="SERIAL">3.9 Serial Interfaces</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=uart&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uart</span>(4)</span></a> driver +supports the following classes of UARTs:</p> + +<ul> +<li> +<p>NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 +UARTs</p> +</li> + +<li> +<p>SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous +mode.</p> +</li> + +<li> +<p>Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SOUND" name="SOUND">3.10 Sound Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_audiocs&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_audiocs</span>(4)</span></a> +driver supports the following audio devices:</p> + +<ul> +<li> +<p>CS4231 on SBus based UltraSPARC</p> +</li> + +<li> +<p>CS4231 on PCI/EBus based UltraSPARC</p> +</li> +</ul> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver supports the following sound cards:</p> + +<ul> +<li> +<p>Creative CT5880-A</p> +</li> + +<li> +<p>Creative CT5880-C</p> +</li> + +<li> +<p>Creative CT5880-D</p> +</li> + +<li> +<p>Creative CT5880-E</p> +</li> + +<li> +<p>Creative SB AudioPCI CT4730</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1370</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1371-A</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1371-B</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-A</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-B</p> +</li> + +<li> +<p>Ensoniq AudioPCI ES1373-8</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CAMERA" name="CAMERA">3.11 Camera and Video Capture +Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USB" name="USB">3.12 USB Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=umct&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">umct</span>(4)</span></a> driver +supports the following adapters:</p> + +<ul> +<li> +<p>Belkin F5U109</p> +</li> + +<li> +<p>Belkin F5U409</p> +</li> + +<li> +<p>D-Link DU-H3SP USB BAY Hub</p> +</li> + +<li> +<p>Magic Control Technology USB-232</p> +</li> + +<li> +<p>Sitecom USB-232</p> +</li> +</ul> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.13 IEEE 1394 (Firewire) +Devices</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fwohci</span>(4)</span></a> driver +provides support for PCI/CardBus FireWire interface cards. The driver supports the +following IEEE 1394 OHCI chipsets:</p> + +<ul> +<li> +<p>Adaptec AHA-894x/AIC-5800</p> +</li> + +<li> +<p>Apple Pangea</p> +</li> + +<li> +<p>Apple UniNorth</p> +</li> + +<li> +<p>Intel 82372FB</p> +</li> + +<li> +<p>IOGEAR GUF320</p> +</li> + +<li> +<p>Lucent / Agere FW322/323</p> +</li> + +<li> +<p>NEC uPD72861</p> +</li> + +<li> +<p>NEC uPD72870</p> +</li> + +<li> +<p>NEC uPD72871/2</p> +</li> + +<li> +<p>NEC uPD72873</p> +</li> + +<li> +<p>NEC uPD72874</p> +</li> + +<li> +<p>National Semiconductor CS4210</p> +</li> + +<li> +<p>Ricoh R5C551</p> +</li> + +<li> +<p>Ricoh R5C552</p> +</li> + +<li> +<p>Sony CX3022</p> +</li> + +<li> +<p>Sony i.LINK (CXD1947)</p> +</li> + +<li> +<p>Sony i.LINK (CXD3222)</p> +</li> + +<li> +<p>Sun PCIO-2 (RIO 1394)</p> +</li> + +<li> +<p>Texas Instruments PCI4410A</p> +</li> + +<li> +<p>Texas Instruments PCI4450</p> +</li> + +<li> +<p>Texas Instruments PCI4451</p> +</li> + +<li> +<p>Texas Instruments TSB12LV22</p> +</li> + +<li> +<p>Texas Instruments TSB12LV23</p> +</li> + +<li> +<p>Texas Instruments TSB12LV26</p> +</li> + +<li> +<p>Texas Instruments TSB43AA22</p> +</li> + +<li> +<p>Texas Instruments TSB43AB21/A/AI/A-EP</p> +</li> + +<li> +<p>Texas Instruments TSB43AB22/A</p> +</li> + +<li> +<p>Texas Instruments TSB43AB23</p> +</li> + +<li> +<p>Texas Instruments TSB82AA2</p> +</li> + +<li> +<p>VIA Fire II (VT6306)</p> +</li> +</ul> + +<p>Serial Bus Protocol 2 (SBP-2) storage devices (<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sbp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbp</span>(4)</span></a> +driver)</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.14 Bluetooth Devices</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="CRYPTO-ACCEL" name="CRYPTO-ACCEL">3.15 Cryptographic +Accelerators</a></h3> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="MISC" name="MISC">3.16 Miscellaneous</a></h3> + +<p>OpenFirmware console (ofwcons driver)</p> +</div> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/installation-alpha.html b/en/releases/6.1R/installation-alpha.html new file mode 100644 index 0000000000..bda0114898 --- /dev/null +++ b/en/releases/6.1R/installation-alpha.html @@ -0,0 +1,1202 @@ +<!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 6.1-RELEASE Installation Instructions</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.1-RELEASE Installation +Instructions</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a> +<p>This article gives some brief instructions on installing FreeBSD/alpha 6.1-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="INSTALL" name="INSTALL">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 6.1-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 compatibility +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="AEN38" name="AEN38">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 <tt +class="LITERAL">a</tt>) 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 three) 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 most CDROM or network installations, all you need to copy onto actual floppies +from the <tt class="FILENAME">floppies/</tt> directory are the <tt +class="FILENAME">boot.flp</tt> and <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> images (for 1.44MB floppies).</p> + +<p>Getting these images over the network is easy. Simply fetch the <tt +class="REPLACEABLE"><i>release</i></tt><tt class="FILENAME">/floppies/boot.flp</tt>, and +all of the <tt class="REPLACEABLE"><i>release</i></tt><tt +class="FILENAME">/floppies/kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> files from +<a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</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://mirrorlist.FreeBSD.org/" target="_top">http://mirrorlist.FreeBSD.org/</a> +Web pages.</p> + +<p>Get several blank, freshly formatted floppies and image copy <tt +class="FILENAME">boot.flp</tt> onto one and the <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> files onto the others. 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&sektion=1&manpath=FreeBSD+6.1-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></samp> <kbd class="USERINPUT">fdimage boot.flp a:</kbd> +</pre> + +<p>Assuming that you'd copied <tt class="FILENAME">fdimage.exe</tt> and <tt +class="FILENAME">boot.flp</tt> into a directory somewhere. You would do the same for the +<tt class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> files, 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/boot.flp of=/dev/rfd0</kbd> +</pre> + +<p>or</p> + +<pre class="SCREEN"> +<samp class="PROMPT">#</samp> <kbd +class="USERINPUT">dd if=floppies/boot.flp of=/dev/fd0</kbd> +</pre> + +<p>or</p> + +<pre class="SCREEN"> +<samp class="PROMPT">#</samp> <kbd +class="USERINPUT">dd if=floppies/boot.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, 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"> +>>><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 <tt +class="FILENAME">floppies/boot.flp</tt> and <tt class="FILENAME">floppies/kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> files using the instructions found in <a +href="#FLOPPIES">Section 1.3</a>. From the SRM console prompt (<tt +class="LITERAL">>>></tt>), just insert the <tt class="FILENAME">boot.flp</tt> +floppy and type the following command to start the installation:</p> + +<pre class="SCREEN"> +>>><kbd class="USERINPUT">boot dva0</kbd> +</pre> + +<p>Insert the other floppies 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="AEN213" name="AEN213">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"> +>>><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 <tt class="LITERAL">show device</tt> command:</p> + +<pre class="SCREEN"> +>>><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> respectively.</p> + +<p>You can specify which kernel file to load and what boot options to use with the <code +class="OPTION">-file</code> and <code class="OPTION">-flags</code> options, for +example:</p> + +<pre class="SCREEN"> +<samp class="PROMPT">>>></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">>>></samp> <kbd class="USERINPUT">set boot_osflags a</kbd> +<samp class="PROMPT">>>></samp> <kbd +class="USERINPUT">set bootdef_dev dkc0</kbd> +<samp class="PROMPT">>>></samp> <kbd +class="USERINPUT">set auto_action BOOT</kbd> +</pre> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN252" name="AEN252">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 ensure an FTP server is running and then simply add +the following line to the password file (using the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+6.1-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 <tt class="LITERAL">any</tt>. You may then choose a Media type of <tt +class="LITERAL">FTP</tt> and type in <tt class="FILENAME">ftp://<tt +class="REPLACEABLE"><i>machine</i></tt></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&sektion=5&manpath=FreeBSD+6.1-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"><tt class="REPLACEABLE"><i>cdrom-host</i></tt>:/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="AEN284" name="AEN284">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&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+6.1-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</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file. +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.</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="AEN353" name="AEN353">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&sektion=1&manpath=FreeBSD+6.1-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 <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/sa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt class="REPLACEABLE"><i>dist2</i></tt></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="AEN378" name="AEN378">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 the PPP +utility should 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="AEN384" name="AEN384">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 <code class="OPTION">link0</code> 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="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5> + +<p>FreeBSD supports most 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 <code +class="OPTION">netmask</code> 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="AEN406" name="AEN406">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 may 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 +<code class="OPTION">-alldirs</code> option. Other NFS servers may have different +conventions. If you are getting <tt class="LITERAL">Permission Denied</tt> 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="AEN423" name="AEN423">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:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</kbd> +</pre> + +<p>In the URL above, <tt class="REPLACEABLE"><i>port</i></tt> 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="AEN444" name="AEN444">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 class="STEP"> +<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 class="STEP"> +<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 class="STEP"> +<p>If you don't get any output on your serial console, plug the keyboard in again. If you +are booting from the CDROM, proceed to <a href="#HITSPACE">step 5</a> as soon as you hear +the beep.</p> +</li> + +<li class="STEP"> +<p>If booting from floppies, when access to the disk stops, insert the first of the <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks and press <b +class="KEYCAP">Enter</b>. When access to this disk finishes, insert the next <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disk and press <b +class="KEYCAP">Enter</b>, and repeat until all <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks have been inserted. When disk activity +finishes, reinsert the <tt class="FILENAME">boot.flp</tt> floppy disk and press <b +class="KEYCAP">Enter</b>.</p> +</li> + +<li class="STEP"><a id="HITSPACE" name="HITSPACE"></a> +<p>Once a beep is heard, hit the number <b class="KEYCAP">6</b>, 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="AEN474" name="AEN474">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 (exact details may +vary depending on version, architecture, and other factors):</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 base 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>These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see <a href="#TROUBLE">Section 4</a> for how to use this).</p> + +<p>The <tt class="FILENAME">floppies</tt> directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the <tt +class="FILENAME">floppies</tt> directory (see <a href="#FLOPPIES">Section 1.3</a> for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.</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">base</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&sektion=1&manpath=FreeBSD+6.1-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 +190MB 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&sektion=8&manpath=FreeBSD+6.1-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">base</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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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="WARNING"> +<blockquote class="WARNING"> +<p><b>Warning:</b> Binary upgrades to FreeBSD 6.1-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to +compile incorrectly (or not at all).</p> + +<p>These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.1-STABLE snapshots.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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">hosts.allow</tt>, <tt +class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt +class="FILENAME">inetd.conf</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">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">nsswitch.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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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 <tt class="LITERAL">base</tt> distribution should be selected for an +update, and the <tt class="LITERAL">man</tt> 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="AEN801" name="AEN801">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> +</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 <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the <tt +class="FILENAME">fixit.flp</tt> floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.</p> + +<p>Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “CDROM/DVD” option from the fixit menu.</p> + +<p>Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the <tt class="FILENAME">boot.flp</tt> and <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks required for +installation, create the <tt class="FILENAME">fixit.flp</tt> floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. At that point, choose the “fixit” item from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “Floppy” option from the fixit menu, and insert the <tt +class="FILENAME">fixit.flp</tt> floppy disk when prompted to do so.</p> + +<p>The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.</p> + +<p>In the floppy version of fixit, some standalone utilities can be found in <tt +class="FILENAME">/stand</tt> or <tt class="FILENAME">/mnt2/stand</tt>. In the CDROM +version of fixit, these same programs can be found in <tt class="FILENAME">/stand</tt> or +<tt class="FILENAME">/mnt2/rescue</tt> (as well as the rest of the programs from the live +filesystem, which can be found under <tt class="FILENAME">/mnt</tt>).</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN845" name="AEN845">4.2 Common Installation Problems for +Alpha/AXP Architecture Users</a></h3> +</div> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/installation-amd64.html b/en/releases/6.1R/installation-amd64.html new file mode 100644 index 0000000000..6205c02a1f --- /dev/null +++ b/en/releases/6.1R/installation-amd64.html @@ -0,0 +1,1407 @@ +<!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/amd64 6.1-RELEASE Installation Instructions</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/amd64 6.1-RELEASE Installation +Instructions</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a> +<p>This article gives some brief instructions on installing FreeBSD/amd64 6.1-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="INSTALL" name="INSTALL">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 6.1-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 compatibility +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="AEN38" name="AEN38">1.2 Hardware Requirements</a></h3> + +<p>FreeBSD for the AMD64 requires an Athlon64, Athlon64-FX, Opteron or better processor +to run.</p> + +<p>If you have an machine based on an nVidia nForce3 Pro-150, you MUST use the BIOS setup +to disable the IO APIC. If you do not have an option to do this, you will likely have to +disable ACPI instead. There are bugs in the Pro-150 chipset that we have not found a +workaround for yet.</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>Floppy disk based install is not supported on FreeBSD/amd64.</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 the “CDBOOT” standard for bootable CDROM media and +you have booting from CD enabled, simply put the FreeBSD installation CD in your CDROM +drive and boot the system to begin installation.</p> +</li> + +<li> +<p>Build a set of FreeBSD boot floppies from the <tt class="FILENAME">floppies/</tt> +directory in every FreeBSD distribution. 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 /> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN213" name="AEN213">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="AEN252" name="AEN252">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 ensure an FTP server is running and then simply add +the following line to the password file (using the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+6.1-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 <tt class="LITERAL">any</tt>. You may then choose a Media type of <tt +class="LITERAL">FTP</tt> and type in <tt class="FILENAME">ftp://<tt +class="REPLACEABLE"><i>machine</i></tt></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&sektion=5&manpath=FreeBSD+6.1-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"><tt class="REPLACEABLE"><i>cdrom-host</i></tt>:/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="AEN284" name="AEN284">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&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+6.1-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</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file. +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.</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="AEN325" name="AEN325">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:\></samp> <kbd class="USERINPUT">MD C:\FREEBSD</kbd> +<samp class="PROMPT">C:\></samp> <kbd +class="USERINPUT">XCOPY /S E:\BASE C:\FREEBSD\BASE</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="AEN353" name="AEN353">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&sektion=1&manpath=FreeBSD+6.1-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 <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/sa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt class="REPLACEABLE"><i>dist2</i></tt></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="AEN378" name="AEN378">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 the PPP +utility should 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="AEN384" name="AEN384">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 <code class="OPTION">link0</code> 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="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5> + +<p>FreeBSD supports most 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 <code +class="OPTION">netmask</code> 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="AEN406" name="AEN406">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 may 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 +<code class="OPTION">-alldirs</code> option. Other NFS servers may have different +conventions. If you are getting <tt class="LITERAL">Permission Denied</tt> 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="AEN423" name="AEN423">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/amd64/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:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</kbd> +</pre> + +<p>In the URL above, <tt class="REPLACEABLE"><i>port</i></tt> 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="AEN444" name="AEN444">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 class="STEP"> +<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 class="STEP"> +<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 class="STEP"> +<p>If you don't get any output on your serial console, plug the keyboard in again. If you +are booting from the CDROM, proceed to <a href="#HITSPACE">step 5</a> as soon as you hear +the beep.</p> +</li> + +<li class="STEP"> +<p>If booting from floppies, when access to the disk stops, insert the first of the <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks and press <b +class="KEYCAP">Enter</b>. When access to this disk finishes, insert the next <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disk and press <b +class="KEYCAP">Enter</b>, and repeat until all <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks have been inserted. When disk activity +finishes, reinsert the <tt class="FILENAME">boot.flp</tt> floppy disk and press <b +class="KEYCAP">Enter</b>.</p> +</li> + +<li class="STEP"><a id="HITSPACE" name="HITSPACE"></a> +<p>Once a beep is heard, hit the number <b class="KEYCAP">6</b>, 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="AEN474" name="AEN474">1.6 Question and Answer Section for AMD64 +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> + +<dt>1.6.5. <a href="#Q1.6.5.">Can I run <span +class="TRADEMARK">Microsoft</span>® <span class="TRADEMARK">Windows</span>® +applications under FreeBSD?</a></dt> + +<dt>1.6.6. <a href="#Q1.6.6.">Can I run other Operating Systems 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> + +<p><b class="APPLICATION">FIPS</b> does not work on extended DOS partitions. Windows +95/98/ME FAT32 primary partitions are supported.</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 <tt +class="LITERAL">ad</tt> for <tt class="LITERAL">da</tt> 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&sektion=1&manpath=FreeBSD+6.1-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. The <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/doscmd/pkg-descr"><tt +class="FILENAME">emulators/doscmd</tt></a> port/package can be found in the FreeBSD Ports +Collection. 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 class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q1.6.5." name="Q1.6.5."></a><b>1.6.5.</b> Can I run <span +class="TRADEMARK">Microsoft</span>® <span class="TRADEMARK">Windows</span>® +applications under FreeBSD?</p> +</div> + +<div class="ANSWER"> +<p><b></b>There are several ports/packages in the FreeBSD Ports Collection which can +enable the use of many <span class="TRADEMARK">Windows</span> applications. The <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/wine/pkg-descr"><tt +class="FILENAME">emulators/wine</tt></a> port/package provides a compatibility layer on +top of FreeBSD which allow many <span class="TRADEMARK">Windows</span> applications to be +run within X Windows (XFree86).</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> Can I run other Operating Systems +under FreeBSD?</p> +</div> + +<div class="ANSWER"> +<p><b></b>Again, there are several ports/packages in the FreeBSD Ports Collection which +simulate "virtual machines" and allow other operating systems to run on top of FreeBSD. +The <a href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/bochs/pkg-descr"><tt +class="FILENAME">emulators/bochs</tt></a> port/package allows <span +class="TRADEMARK">Microsoft</span> <span class="TRADEMARK">Windows</span>, Linux and +even other copies of FreeBSD to be run within a window on the FreeBSD desktop. The <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/vmware2/pkg-descr"><tt +class="FILENAME">emulators/vmware2</tt></a> and <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/vmware3/pkg-descr"><tt +class="FILENAME">emulators/vmware3</tt></a> ports/packages allow the commercial VMware +virtual machine software to be run on FreeBSD.</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 (exact details may +vary depending on version, architecture, and other factors):</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 base 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>These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see <a href="#TROUBLE">Section 4</a> for how to use this).</p> + +<p>The <tt class="FILENAME">floppies</tt> directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the <tt +class="FILENAME">floppies</tt> directory (see <a href="#FLOPPIES">Section 1.3</a> for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.</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">base</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&sektion=1&manpath=FreeBSD+6.1-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 +190MB 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&sektion=8&manpath=FreeBSD+6.1-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">base</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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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="WARNING"> +<blockquote class="WARNING"> +<p><b>Warning:</b> Binary upgrades to FreeBSD 6.1-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to +compile incorrectly (or not at all).</p> + +<p>These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.1-STABLE snapshots.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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">hosts.allow</tt>, <tt +class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt +class="FILENAME">inetd.conf</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">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">nsswitch.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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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 <tt class="LITERAL">base</tt> distribution should be selected for an +update, and the <tt class="LITERAL">man</tt> 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="AEN801" name="AEN801">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> +</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 <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the <tt +class="FILENAME">fixit.flp</tt> floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.</p> + +<p>Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “CDROM/DVD” option from the fixit menu.</p> + +<p>Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the <tt class="FILENAME">boot.flp</tt> and <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks required for +installation, create the <tt class="FILENAME">fixit.flp</tt> floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. At that point, choose the “fixit” item from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “Floppy” option from the fixit menu, and insert the <tt +class="FILENAME">fixit.flp</tt> floppy disk when prompted to do so.</p> + +<p>The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.</p> + +<p>In the floppy version of fixit, some standalone utilities can be found in <tt +class="FILENAME">/stand</tt> or <tt class="FILENAME">/mnt2/stand</tt>. In the CDROM +version of fixit, these same programs can be found in <tt class="FILENAME">/stand</tt> or +<tt class="FILENAME">/mnt2/rescue</tt> (as well as the rest of the programs from the live +filesystem, which can be found under <tt class="FILENAME">/mnt</tt>).</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN845" name="AEN845">4.2 Common Installation Problems for AMD64 +Architecture Users</a></h3> + +<div class="QANDASET"> +<dl> +<dt>4.2.1. <a href="#Q4.2.1.">My system hangs while probing hardware during boot, or it +behaves strangely during install, or the floppy drive isn't probed.</a></dt> + +<dt>4.2.2. <a href="#Q4.2.2.">My system uses the nVidia nForce3 Pro-150 chipset and I get +hangs at the end of boot or suddenly starts losing interrupts.</a></dt> + +<dt>4.2.4. <a href="#Q4.2.4.">I go to boot from the hard disk for the first time after +installing FreeBSD, the kernel loads and probes my hardware, but stops with messages +like:</a></dt> + +<dt>4.2.5. <a href="#Q4.2.5.">I go to boot from the hard disk for the first time after +installing FreeBSD, but the Boot Manager prompt just prints <tt class="LITERAL">F?</tt> +at the boot menu each time but the boot won't go any further.</a></dt> + +<dt>4.2.7. <a href="#Q4.2.7.">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.2.12. <a href="#Q4.2.12.">I have this CMD640 IDE controller that is said to be +broken.</a></dt> + +<dt>4.2.15. <a href="#Q4.2.15.">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.2.17. <a href="#Q4.2.17.">When I install onto a drive managed by a Mylex PCI RAID +controller, the system fails to boot (eg. with a <tt class="LITERAL">read error</tt> +message).</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> My system hangs while probing +hardware during boot, or it behaves strangely during install, or the floppy drive isn't +probed.</p> +</div> + +<div class="ANSWER"> +<p><b></b>FreeBSD 5.0 and above makes extensive use of the system ACPI service on the +i386, amd64 and ia64 platforms to aid in system configuration if it's detected during +boot. Unfortunately, some bugs still exist in both the ACPI driver and within system +motherboards and BIOS. The use of ACPI can be disabled by setting the +“hint.acpi.0.disabled” hint in the third stage boot loader:</p> + +<pre class="SCREEN"> +set hint.acpi.0.disabled="1" +</pre> + +<p>This is reset each time the system is booted, so it is necessary to add <tt +class="LITERAL">hint.acpi.0.disabled="1"</tt> to the file <tt +class="FILENAME">/boot/loader.conf</tt>. More information about the boot loader can be +found in the FreeBSD Handbook.</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> My system uses the nVidia nForce3 +Pro-150 chipset and I get hangs at the end of boot or suddenly starts losing +interrupts.</p> +</div> + +<div class="ANSWER"> +<p><b></b>There are problems with the apic on this chipset and/or the bios on every +machine that we had seen at the time of release. While disabling ACPI as above will work, +a less drastic option may be to set the “hint.apic.0.disabled” hint instead. +If you have the option in the bios, try disabling the APIC support. Unfortunately some +machines lack this option.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.4." name="Q4.2.4."></a><b>4.2.4.</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 ad1s1a panic: cannot mount root +</pre> + +<p>What is wrong? What can I do?</p> + +<p>What is this <tt class="LITERAL">bios_drive:interface(unit,partition)kernel_name</tt> +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">ad0</tt> +and <tt class="DEVICENAME">ad2</tt>.</p> + +<p>FreeBSD is on BIOS disk 1, of type <tt class="LITERAL">ad</tt> and the FreeBSD disk +number is 2, so you would say:</p> + +<pre class="SCREEN"> +<kbd class="USERINPUT">1:ad(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 <tt class="LITERAL">da</tt> 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 <tt class="LITERAL">boot:</tt> prompt.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.5." name="Q4.2.5."></a><b>4.2.5.</b> I go to boot from the hard disk for +the first time after installing FreeBSD, but the Boot Manager prompt just prints <tt +class="LITERAL">F?</tt> 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="AEN908" name="AEN908"></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 class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.7." name="Q4.2.7."></a><b>4.2.7.</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 <tt +class="FILENAME">/boot/device.hints</tt> file. The ed driver does not use the `soft' +configuration by default (values entered using EZSETUP in DOS), but it will use the +software configuration if you specify <tt class="LITERAL">-1</tt> in the hints for the +interface.</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 <tt class="LITERAL">-1</tt> by +setting the hint “hint.ed.0.irq="-1"” 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.2.12." name="Q4.2.12."></a><b>4.2.12.</b> I have this CMD640 IDE controller +that is said to be broken.</p> +</div> + +<div class="ANSWER"> +<p><b></b>FreeBSD does not support this controller.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.15." name="Q4.2.15."></a><b>4.2.15.</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.2.17." name="Q4.2.17."></a><b>4.2.17.</b> When I install onto a drive +managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a <tt +class="LITERAL">read error</tt> 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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/installation-i386.html b/en/releases/6.1R/installation-i386.html new file mode 100644 index 0000000000..e0100f893d --- /dev/null +++ b/en/releases/6.1R/installation-i386.html @@ -0,0 +1,1630 @@ +<!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 6.1-RELEASE Installation Instructions</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.1-RELEASE Installation +Instructions</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a> +<p>This article gives some brief instructions on installing FreeBSD/i386 6.1-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="INSTALL" name="INSTALL">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 6.1-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 compatibility +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="AEN38" name="AEN38">1.2 Hardware Requirements</a></h3> + +<p>FreeBSD for the i386 requires a 486 or better processor and at least 24 MB of +RAM. You will need at least 150MB of free hard drive space for the most minimal +installation. See below for ways of shrinking existing DOS partitions in order to install +FreeBSD.</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 three) 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 most CDROM or network installations, all you need to copy onto actual floppies +from the <tt class="FILENAME">floppies/</tt> directory are the <tt +class="FILENAME">boot.flp</tt> and <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> images (for 1.44MB floppies).</p> + +<p>Getting these images over the network is easy. Simply fetch the <tt +class="REPLACEABLE"><i>release</i></tt><tt class="FILENAME">/floppies/boot.flp</tt>, and +all of the <tt class="REPLACEABLE"><i>release</i></tt><tt +class="FILENAME">/floppies/kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> files from +<a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</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://mirrorlist.FreeBSD.org/" target="_top">http://mirrorlist.FreeBSD.org/</a> +Web pages.</p> + +<p>Get several blank, freshly formatted floppies and image copy <tt +class="FILENAME">boot.flp</tt> onto one and the <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> files onto the others. 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&sektion=1&manpath=FreeBSD+6.1-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></samp> <kbd class="USERINPUT">fdimage boot.flp a:</kbd> +</pre> + +<p>Assuming that you'd copied <tt class="FILENAME">fdimage.exe</tt> and <tt +class="FILENAME">boot.flp</tt> into a directory somewhere. You would do the same for the +<tt class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> files, 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/boot.flp of=/dev/rfd0</kbd> +</pre> + +<p>or</p> + +<pre class="SCREEN"> +<samp class="PROMPT">#</samp> <kbd +class="USERINPUT">dd if=floppies/boot.flp of=/dev/fd0</kbd> +</pre> + +<p>or</p> + +<pre class="SCREEN"> +<samp class="PROMPT">#</samp> <kbd +class="USERINPUT">dd if=floppies/boot.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 the “CDBOOT” standard for bootable CDROM media and +you have booting from CD enabled, simply put the FreeBSD installation CD in your CDROM +drive and boot the system to begin installation.</p> +</li> + +<li> +<p>Build a set of FreeBSD boot floppies from the <tt class="FILENAME">floppies/</tt> +directory in every FreeBSD distribution. 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/boot.flp</tt> and <tt class="FILENAME">floppies/kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> using the instructions found in <a +href="#FLOPPIES">Section 1.3</a>. Restart your computer using the <tt +class="FILENAME">boot.flp</tt> disk; when prompted, insert the other disks as required. +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="AEN213" name="AEN213">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="AEN252" name="AEN252">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 ensure an FTP server is running and then simply add +the following line to the password file (using the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+6.1-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 <tt class="LITERAL">any</tt>. You may then choose a Media type of <tt +class="LITERAL">FTP</tt> and type in <tt class="FILENAME">ftp://<tt +class="REPLACEABLE"><i>machine</i></tt></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&sektion=5&manpath=FreeBSD+6.1-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"><tt class="REPLACEABLE"><i>cdrom-host</i></tt>:/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="AEN284" name="AEN284">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&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+6.1-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</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file. +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.</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="AEN325" name="AEN325">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:\></samp> <kbd class="USERINPUT">MD C:\FREEBSD</kbd> +<samp class="PROMPT">C:\></samp> <kbd +class="USERINPUT">XCOPY /S E:\BASE C:\FREEBSD\BASE</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="AEN353" name="AEN353">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&sektion=1&manpath=FreeBSD+6.1-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 <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/sa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt class="REPLACEABLE"><i>dist2</i></tt></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="AEN378" name="AEN378">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 the PPP +utility should 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="AEN384" name="AEN384">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 <code class="OPTION">link0</code> 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="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5> + +<p>FreeBSD supports most 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 <code +class="OPTION">netmask</code> 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="AEN406" name="AEN406">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 may 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 +<code class="OPTION">-alldirs</code> option. Other NFS servers may have different +conventions. If you are getting <tt class="LITERAL">Permission Denied</tt> 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="AEN423" name="AEN423">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:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</kbd> +</pre> + +<p>In the URL above, <tt class="REPLACEABLE"><i>port</i></tt> 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="AEN444" name="AEN444">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 class="STEP"> +<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 class="STEP"> +<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 class="STEP"> +<p>If you don't get any output on your serial console, plug the keyboard in again. If you +are booting from the CDROM, proceed to <a href="#HITSPACE">step 5</a> as soon as you hear +the beep.</p> +</li> + +<li class="STEP"> +<p>If booting from floppies, when access to the disk stops, insert the first of the <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks and press <b +class="KEYCAP">Enter</b>. When access to this disk finishes, insert the next <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disk and press <b +class="KEYCAP">Enter</b>, and repeat until all <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks have been inserted. When disk activity +finishes, reinsert the <tt class="FILENAME">boot.flp</tt> floppy disk and press <b +class="KEYCAP">Enter</b>.</p> +</li> + +<li class="STEP"><a id="HITSPACE" name="HITSPACE"></a> +<p>Once a beep is heard, hit the number <b class="KEYCAP">6</b>, 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="AEN474" name="AEN474">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> + +<dt>1.6.5. <a href="#Q1.6.5.">Can I run <span +class="TRADEMARK">Microsoft</span>® <span class="TRADEMARK">Windows</span>® +applications under FreeBSD?</a></dt> + +<dt>1.6.6. <a href="#Q1.6.6.">Can I run other Operating Systems 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> + +<p><b class="APPLICATION">FIPS</b> does not work on extended DOS partitions. Windows +95/98/ME FAT32 primary partitions are supported.</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 <tt +class="LITERAL">ad</tt> for <tt class="LITERAL">da</tt> 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&sektion=1&manpath=FreeBSD+6.1-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. The <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/doscmd/pkg-descr"><tt +class="FILENAME">emulators/doscmd</tt></a> port/package can be found in the FreeBSD Ports +Collection. 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 class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q1.6.5." name="Q1.6.5."></a><b>1.6.5.</b> Can I run <span +class="TRADEMARK">Microsoft</span>® <span class="TRADEMARK">Windows</span>® +applications under FreeBSD?</p> +</div> + +<div class="ANSWER"> +<p><b></b>There are several ports/packages in the FreeBSD Ports Collection which can +enable the use of many <span class="TRADEMARK">Windows</span> applications. The <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/wine/pkg-descr"><tt +class="FILENAME">emulators/wine</tt></a> port/package provides a compatibility layer on +top of FreeBSD which allow many <span class="TRADEMARK">Windows</span> applications to be +run within X Windows (XFree86).</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> Can I run other Operating Systems +under FreeBSD?</p> +</div> + +<div class="ANSWER"> +<p><b></b>Again, there are several ports/packages in the FreeBSD Ports Collection which +simulate "virtual machines" and allow other operating systems to run on top of FreeBSD. +The <a href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/bochs/pkg-descr"><tt +class="FILENAME">emulators/bochs</tt></a> port/package allows <span +class="TRADEMARK">Microsoft</span> <span class="TRADEMARK">Windows</span>, Linux and +even other copies of FreeBSD to be run within a window on the FreeBSD desktop. The <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/vmware2/pkg-descr"><tt +class="FILENAME">emulators/vmware2</tt></a> and <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/vmware3/pkg-descr"><tt +class="FILENAME">emulators/vmware3</tt></a> ports/packages allow the commercial VMware +virtual machine software to be run on FreeBSD.</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 (exact details may +vary depending on version, architecture, and other factors):</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 base 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>These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see <a href="#TROUBLE">Section 4</a> for how to use this).</p> + +<p>The <tt class="FILENAME">floppies</tt> directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the <tt +class="FILENAME">floppies</tt> directory (see <a href="#FLOPPIES">Section 1.3</a> for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.</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">base</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&sektion=1&manpath=FreeBSD+6.1-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 +190MB 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&sektion=8&manpath=FreeBSD+6.1-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">base</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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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="WARNING"> +<blockquote class="WARNING"> +<p><b>Warning:</b> Binary upgrades to FreeBSD 6.1-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to +compile incorrectly (or not at all).</p> + +<p>These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.1-STABLE snapshots.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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">hosts.allow</tt>, <tt +class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt +class="FILENAME">inetd.conf</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">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">nsswitch.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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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 <tt class="LITERAL">base</tt> distribution should be selected for an +update, and the <tt class="LITERAL">man</tt> 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="AEN801" name="AEN801">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> +</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 <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the <tt +class="FILENAME">fixit.flp</tt> floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.</p> + +<p>Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “CDROM/DVD” option from the fixit menu.</p> + +<p>Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the <tt class="FILENAME">boot.flp</tt> and <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks required for +installation, create the <tt class="FILENAME">fixit.flp</tt> floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. At that point, choose the “fixit” item from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “Floppy” option from the fixit menu, and insert the <tt +class="FILENAME">fixit.flp</tt> floppy disk when prompted to do so.</p> + +<p>The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.</p> + +<p>In the floppy version of fixit, some standalone utilities can be found in <tt +class="FILENAME">/stand</tt> or <tt class="FILENAME">/mnt2/stand</tt>. In the CDROM +version of fixit, these same programs can be found in <tt class="FILENAME">/stand</tt> or +<tt class="FILENAME">/mnt2/rescue</tt> (as well as the rest of the programs from the live +filesystem, which can be found under <tt class="FILENAME">/mnt</tt>).</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN845" name="AEN845">4.2 Common Installation Problems for i386 +Architecture Users</a></h3> + +<div class="QANDASET"> +<dl> +<dt>4.2.1. <a href="#Q4.2.1.">My system hangs while probing hardware during boot, or it +behaves strangely during install, or the floppy drive isn't probed.</a></dt> + +<dt>4.2.3. <a href="#Q4.2.3.">My legacy ISA device used to be recognized in previous +versions of FreeBSD, but now it's not. What happened?</a></dt> + +<dt>4.2.4. <a href="#Q4.2.4.">I go to boot from the hard disk for the first time after +installing FreeBSD, the kernel loads and probes my hardware, but stops with messages +like:</a></dt> + +<dt>4.2.5. <a href="#Q4.2.5.">I go to boot from the hard disk for the first time after +installing FreeBSD, but the Boot Manager prompt just prints <tt class="LITERAL">F?</tt> +at the boot menu each time but the boot won't go any further.</a></dt> + +<dt>4.2.6. <a href="#Q4.2.6.">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.2.7. <a href="#Q4.2.7.">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.2.8. <a href="#Q4.2.8.">I booted the install floppy on my IBM ThinkPad (tm) laptop, +and the keyboard is all messed up.</a></dt> + +<dt>4.2.9. <a href="#Q4.2.9.">My system can not find my Intel EtherExpress 16 +card.</a></dt> + +<dt>4.2.10. <a href="#Q4.2.10.">When installing on an EISA HP Netserver, my on-board +AIC-7xxx SCSI controller isn't detected.</a></dt> + +<dt>4.2.11. <a href="#Q4.2.11.">I have a Panasonic AL-N1 or Rios Chandler Pentium machine +and I find that the system hangs before ever getting into the installation now.</a></dt> + +<dt>4.2.12. <a href="#Q4.2.12.">I have this CMD640 IDE controller that is said to be +broken.</a></dt> + +<dt>4.2.13. <a href="#Q4.2.13.">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.2.14. <a href="#Q4.2.14.">When installing on a Dell Poweredge XE, Dell proprietary +RAID controller DSA (Dell SCSI Array) isn't recognized.</a></dt> + +<dt>4.2.15. <a href="#Q4.2.15.">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.2.16. <a href="#Q4.2.16.">When I configure the network during installation on an +IBM Netfinity 3500, the system freezes.</a></dt> + +<dt>4.2.17. <a href="#Q4.2.17.">When I install onto a drive managed by a Mylex PCI RAID +controller, the system fails to boot (eg. with a <tt class="LITERAL">read error</tt> +message).</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> My system hangs while probing +hardware during boot, or it behaves strangely during install, or the floppy drive isn't +probed.</p> +</div> + +<div class="ANSWER"> +<p><b></b>FreeBSD 5.0 and above makes extensive use of the system ACPI service on the +i386, amd64 and ia64 platforms to aid in system configuration if it's detected during +boot. Unfortunately, some bugs still exist in both the ACPI driver and within system +motherboards and BIOS. The use of ACPI can be disabled by setting the +“hint.acpi.0.disabled” hint in the third stage boot loader:</p> + +<pre class="SCREEN"> +set hint.acpi.0.disabled="1" +</pre> + +<p>This is reset each time the system is booted, so it is necessary to add <tt +class="LITERAL">hint.acpi.0.disabled="1"</tt> to the file <tt +class="FILENAME">/boot/loader.conf</tt>. More information about the boot loader can be +found in the FreeBSD Handbook.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.3." name="Q4.2.3."></a><b>4.2.3.</b> My legacy ISA device used to be +recognized in previous versions of FreeBSD, but now it's not. What happened?</p> +</div> + +<div class="ANSWER"> +<p><b></b>Some device drivers, like matcd, were removed over time due to lack of +maintainership or other reasons. Others still exist but are disabled because of their +intrusive hardware probe routines. The following ISA device drivers fall into this +category and can re-enabled from the third stage boot loader: aha, ahv, aic, bt, ed, cs, +sn, ie, fe, le, and lnc. To do this, stop the loader during it's 10 second countdown and +enter the following at the prompt:</p> + +<pre class="SCREEN"> +unset hint.foo.0.disabled +</pre> + +<p>where <tt class="REPLACEABLE"><i>foo</i></tt> is the name of the driver to re-enable. +This can be set permanently by editing the file <tt +class="FILENAME">/boot/device.hints</tt> and removing the appropriate +“disabled” entry.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.4." name="Q4.2.4."></a><b>4.2.4.</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 ad1s1a panic: cannot mount root +</pre> + +<p>What is wrong? What can I do?</p> + +<p>What is this <tt class="LITERAL">bios_drive:interface(unit,partition)kernel_name</tt> +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">ad0</tt> +and <tt class="DEVICENAME">ad2</tt>.</p> + +<p>FreeBSD is on BIOS disk 1, of type <tt class="LITERAL">ad</tt> and the FreeBSD disk +number is 2, so you would say:</p> + +<pre class="SCREEN"> +<kbd class="USERINPUT">1:ad(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 <tt class="LITERAL">da</tt> 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 <tt class="LITERAL">boot:</tt> prompt.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.5." name="Q4.2.5."></a><b>4.2.5.</b> I go to boot from the hard disk for +the first time after installing FreeBSD, but the Boot Manager prompt just prints <tt +class="LITERAL">F?</tt> 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="AEN908" name="AEN908"></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 class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.6." name="Q4.2.6."></a><b>4.2.6.</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>Set the hints “hint.mcd.0.disabled="1"” and +“hint.mcd.1.disabled="1"” in the third stage boot loader to disable the +probing of the <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.2.7." name="Q4.2.7."></a><b>4.2.7.</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 <tt +class="FILENAME">/boot/device.hints</tt> file. The ed driver does not use the `soft' +configuration by default (values entered using EZSETUP in DOS), but it will use the +software configuration if you specify <tt class="LITERAL">-1</tt> in the hints for the +interface.</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 <tt class="LITERAL">-1</tt> by +setting the hint “hint.ed.0.irq="-1"” 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.2.8." name="Q4.2.8."></a><b>4.2.8.</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. Set the +hint “hint.atkbd.0.flags="4"” and it should work fine.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.9." name="Q4.2.9."></a><b>4.2.9.</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.2.10." name="Q4.2.10."></a><b>4.2.10.</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, set the hint “hw.eisa_slots="12"” in the +third stage loader.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.11." name="Q4.2.11."></a><b>4.2.11.</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 <tt class="LITERAL">i586_copyout</tt> and <tt +class="LITERAL">i586_copyin</tt> code for some reason. To disable this, set the hint +“hint.npx.0.flags="1"”</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.12." name="Q4.2.12."></a><b>4.2.12.</b> I have this CMD640 IDE controller +that is said to be broken.</p> +</div> + +<div class="ANSWER"> +<p><b></b>FreeBSD does not support this controller.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.13." name="Q4.2.13."></a><b>4.2.13.</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. Set the hint +“hint.fdc.0.flags="1"” This pretends the existence of the first floppy drive +(as a 1.44 MB drive) to the driver without asking the CMOS at all.</p> +</div> +</div> + +<div class="QANDAENTRY"> +<div class="QUESTION"> +<p><a id="Q4.2.14." name="Q4.2.14."></a><b>4.2.14.</b> When installing on a 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.2.15." name="Q4.2.15."></a><b>4.2.15.</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.2.16." name="Q4.2.16."></a><b>4.2.16.</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.2.17." name="Q4.2.17."></a><b>4.2.17.</b> When I install onto a drive +managed by a Mylex PCI RAID controller, the system fails to boot (eg. with a <tt +class="LITERAL">read error</tt> 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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/installation-ia64.html b/en/releases/6.1R/installation-ia64.html new file mode 100644 index 0000000000..38f97cdef2 --- /dev/null +++ b/en/releases/6.1R/installation-ia64.html @@ -0,0 +1,902 @@ +<!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/ia64 6.1-RELEASE Installation Instructions</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/ia64 6.1-RELEASE Installation +Instructions</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a> +<p>This article gives some brief instructions on installing FreeBSD/ia64 6.1-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="INSTALL" name="INSTALL">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 6.1-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 compatibility +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="AEN38" name="AEN38">1.2 Hardware Requirements</a></h3> + +<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> +</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> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN213" name="AEN213">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="AEN252" name="AEN252">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 ensure an FTP server is running and then simply add +the following line to the password file (using the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+6.1-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 <tt class="LITERAL">any</tt>. You may then choose a Media type of <tt +class="LITERAL">FTP</tt> and type in <tt class="FILENAME">ftp://<tt +class="REPLACEABLE"><i>machine</i></tt></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&sektion=5&manpath=FreeBSD+6.1-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"><tt class="REPLACEABLE"><i>cdrom-host</i></tt>:/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="AEN284" name="AEN284">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&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+6.1-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</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file. +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.</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="AEN353" name="AEN353">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&sektion=1&manpath=FreeBSD+6.1-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 <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/sa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt class="REPLACEABLE"><i>dist2</i></tt></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="AEN378" name="AEN378">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 the PPP +utility should 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="AEN384" name="AEN384">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 <code class="OPTION">link0</code> 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="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5> + +<p>FreeBSD supports most 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 <code +class="OPTION">netmask</code> 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="AEN406" name="AEN406">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 may 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 +<code class="OPTION">-alldirs</code> option. Other NFS servers may have different +conventions. If you are getting <tt class="LITERAL">Permission Denied</tt> 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="AEN423" name="AEN423">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/ia64/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:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</kbd> +</pre> + +<p>In the URL above, <tt class="REPLACEABLE"><i>port</i></tt> is the port number of the +proxy FTP server.</p> +</li> +</ul> + +<br /> +<br /> +</div> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN474" name="AEN474">1.6 Question and Answer Section for IA-64 +Architecture Users</a></h3> +</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 (exact details may +vary depending on version, architecture, and other factors):</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 base 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>These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see <a href="#TROUBLE">Section 4</a> for how to use this).</p> + +<p>The <tt class="FILENAME">floppies</tt> directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the <tt +class="FILENAME">floppies</tt> directory (see <a href="#FLOPPIES">Section 1.3</a> for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.</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">base</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&sektion=1&manpath=FreeBSD+6.1-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 +190MB 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&sektion=8&manpath=FreeBSD+6.1-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">base</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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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="WARNING"> +<blockquote class="WARNING"> +<p><b>Warning:</b> Binary upgrades to FreeBSD 6.1-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to +compile incorrectly (or not at all).</p> + +<p>These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.1-STABLE snapshots.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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">hosts.allow</tt>, <tt +class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt +class="FILENAME">inetd.conf</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">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">nsswitch.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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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 <tt class="LITERAL">base</tt> distribution should be selected for an +update, and the <tt class="LITERAL">man</tt> 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="AEN801" name="AEN801">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> +</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 <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the <tt +class="FILENAME">fixit.flp</tt> floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.</p> + +<p>Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “CDROM/DVD” option from the fixit menu.</p> + +<p>Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the <tt class="FILENAME">boot.flp</tt> and <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks required for +installation, create the <tt class="FILENAME">fixit.flp</tt> floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. At that point, choose the “fixit” item from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “Floppy” option from the fixit menu, and insert the <tt +class="FILENAME">fixit.flp</tt> floppy disk when prompted to do so.</p> + +<p>The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.</p> + +<p>In the floppy version of fixit, some standalone utilities can be found in <tt +class="FILENAME">/stand</tt> or <tt class="FILENAME">/mnt2/stand</tt>. In the CDROM +version of fixit, these same programs can be found in <tt class="FILENAME">/stand</tt> or +<tt class="FILENAME">/mnt2/rescue</tt> (as well as the rest of the programs from the live +filesystem, which can be found under <tt class="FILENAME">/mnt</tt>).</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN845" name="AEN845">4.2 Common Installation Problems for IA-64 +Architecture Users</a></h3> +</div> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/installation-pc98.html b/en/releases/6.1R/installation-pc98.html new file mode 100644 index 0000000000..833b2f5a22 --- /dev/null +++ b/en/releases/6.1R/installation-pc98.html @@ -0,0 +1,1025 @@ +<!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/pc98 6.1-RELEASE Installation Instructions</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/pc98 6.1-RELEASE Installation +Instructions</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a> +<p>This article gives some brief instructions on installing FreeBSD/pc98 6.1-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="INSTALL" name="INSTALL">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 6.1-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 compatibility +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="AEN38" name="AEN38">1.2 Hardware Requirements</a></h3> + +<p>FreeBSD for the NEC PC-98x1 requires a 486 or better processor and at least 24 MB +of RAM. You will need at least 150MB of free hard drive space for the most minimal +installation. See below for ways of shrinking existing DOS partitions in order to install +FreeBSD.</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 three) 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">boot.flp</tt> and <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> images (for 1.44MB floppies) or <tt +class="FILENAME">boot-small.flp</tt> and <tt class="FILENAME">kern-small.flp</tt> images +(for 1.2MB floppies).</p> + +<p>Getting these images over the network is easy. Simply fetch the <tt +class="REPLACEABLE"><i>release</i></tt><tt class="FILENAME">/floppies/boot.flp</tt>, and +all of the <tt class="REPLACEABLE"><i>release</i></tt><tt +class="FILENAME">/floppies/kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> files from +<a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</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://mirrorlist.FreeBSD.org/" target="_top">http://mirrorlist.FreeBSD.org/</a> +Web pages.</p> + +<p>Get several blank, freshly formatted floppies and image copy <tt +class="FILENAME">boot.flp</tt> onto one and the <tt class="FILENAME">kern<tt +class="REPLACEABLE"><i>X</i></tt>.flp</tt> files onto the others. 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">rawrite.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&sektion=1&manpath=FreeBSD+6.1-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">A></samp> <kbd class="USERINPUT">rawrite</kbd> +</pre> + +<p>Assuming that you'd copied <tt class="FILENAME">rawrite.exe</tt> and <tt +class="FILENAME">boot.flp</tt> into a directory somewhere. You would do the same for the +<tt class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> files, 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/boot.flp of=/dev/rfd0.1440</kbd> +</pre> + +<p>or</p> + +<pre class="SCREEN"> +<samp class="PROMPT">#</samp> <kbd +class="USERINPUT">dd if=floppies/boot-small.flp of=/dev/rfd0.1200</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 is a next way of starting the installation from +it:</p> + +<ul> +<li> +<p>Build a set of FreeBSD boot floppies from the <tt class="FILENAME">floppies/</tt> +directory in every FreeBSD distribution. 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 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/boot.flp</tt> and <tt +class="FILENAME">floppies/kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> using the +instructions found in <a href="#FLOPPIES">Section 1.3</a>. Restart your computer using +the <tt class="FILENAME">boot.flp</tt> disk; when prompted, insert the other disks as +required. 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="AEN213" name="AEN213">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="AEN252" name="AEN252">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 ensure an FTP server is running and then simply add +the following line to the password file (using the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+6.1-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 <tt class="LITERAL">any</tt>. You may then choose a Media type of <tt +class="LITERAL">FTP</tt> and type in <tt class="FILENAME">ftp://<tt +class="REPLACEABLE"><i>machine</i></tt></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&sektion=5&manpath=FreeBSD+6.1-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"><tt class="REPLACEABLE"><i>cdrom-host</i></tt>:/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="AEN284" name="AEN284">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&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+6.1-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</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file. +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.</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="AEN325" name="AEN325">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">A:</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">A:\></samp> <kbd class="USERINPUT">MD A:\FREEBSD</kbd> +<samp class="PROMPT">A:\></samp> <kbd +class="USERINPUT">XCOPY /S E:\BASE A:\FREEBSD\BASE</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">A:\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="AEN353" name="AEN353">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&sektion=1&manpath=FreeBSD+6.1-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 <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/sa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt class="REPLACEABLE"><i>dist2</i></tt></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="AEN378" name="AEN378">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 the PPP +utility should 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="AEN384" name="AEN384">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 <code class="OPTION">link0</code> 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="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5> + +<p>FreeBSD supports most 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 <code +class="OPTION">netmask</code> 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="AEN406" name="AEN406">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 may 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 +<code class="OPTION">-alldirs</code> option. Other NFS servers may have different +conventions. If you are getting <tt class="LITERAL">Permission Denied</tt> 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="AEN423" name="AEN423">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/pc98/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:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</kbd> +</pre> + +<p>In the URL above, <tt class="REPLACEABLE"><i>port</i></tt> is the port number of the +proxy FTP server.</p> +</li> +</ul> + +<br /> +<br /> +</div> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN474" name="AEN474">1.6 Question and Answer Section for NEC +PC-98x1 Architecture Users</a></h3> +</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 (exact details may +vary depending on version, architecture, and other factors):</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 base 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>These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see <a href="#TROUBLE">Section 4</a> for how to use this).</p> + +<p>The <tt class="FILENAME">floppies</tt> directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the <tt +class="FILENAME">floppies</tt> directory (see <a href="#FLOPPIES">Section 1.3</a> for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.</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">base</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&sektion=1&manpath=FreeBSD+6.1-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 +190MB 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&sektion=8&manpath=FreeBSD+6.1-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">base</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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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="WARNING"> +<blockquote class="WARNING"> +<p><b>Warning:</b> Binary upgrades to FreeBSD 6.1-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to +compile incorrectly (or not at all).</p> + +<p>These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.1-STABLE snapshots.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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">hosts.allow</tt>, <tt +class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt +class="FILENAME">inetd.conf</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">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">nsswitch.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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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 <tt class="LITERAL">base</tt> distribution should be selected for an +update, and the <tt class="LITERAL">man</tt> 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="AEN801" name="AEN801">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> +</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 <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the <tt +class="FILENAME">fixit.flp</tt> floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.</p> + +<p>Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “CDROM/DVD” option from the fixit menu.</p> + +<p>Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the <tt class="FILENAME">boot.flp</tt> and <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks required for +installation, create the <tt class="FILENAME">fixit.flp</tt> floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. At that point, choose the “fixit” item from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “Floppy” option from the fixit menu, and insert the <tt +class="FILENAME">fixit.flp</tt> floppy disk when prompted to do so.</p> + +<p>The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.</p> + +<p>In the floppy version of fixit, some standalone utilities can be found in <tt +class="FILENAME">/stand</tt> or <tt class="FILENAME">/mnt2/stand</tt>. In the CDROM +version of fixit, these same programs can be found in <tt class="FILENAME">/stand</tt> or +<tt class="FILENAME">/mnt2/rescue</tt> (as well as the rest of the programs from the live +filesystem, which can be found under <tt class="FILENAME">/mnt</tt>).</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN845" name="AEN845">4.2 Common Installation Problems for NEC +PC-98x1 Architecture Users</a></h3> +</div> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/installation-sparc64.html b/en/releases/6.1R/installation-sparc64.html new file mode 100644 index 0000000000..1afa285e90 --- /dev/null +++ b/en/releases/6.1R/installation-sparc64.html @@ -0,0 +1,957 @@ +<!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/sparc64 6.1-RELEASE Installation Instructions</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/sparc64 6.1-RELEASE Installation +Instructions</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a> +<p>This article gives some brief instructions on installing FreeBSD/sparc64 6.1-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="INSTALL" name="INSTALL">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 6.1-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 compatibility +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="AEN38" name="AEN38">1.2 Hardware Requirements</a></h3> + +<p>FreeBSD for the UltraSPARC supports the platforms described in <tt +class="FILENAME">HARDWARE.TXT</tt>.</p> + +<p>You will need a dedicated disk for FreeBSD/sparc64. It is not possible to share a disk +with another operating system at this time.</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>Floppy disk based install is not supported on FreeBSD/sparc64.</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>Most sparc64 systems are set up to boot automatically from disk. To install FreeBSD, +you need to boot over the network or from a CDROM, which requires you to break into the +PROM (OpenFirmware).</p> + +<p>To do this, reboot the system, and wait until the boot message appears. It depends on +the model, but should look about like:</p> + +<pre class="SCREEN"> +Sun Blade 100 (UltraSPARC-IIe), Keyboard Present +Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. +OpenBoot 4.2, 128 MB memory installed, Serial #51090132. +Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. +</pre> + +<p>If your system proceeds to boot from disk at this point, you need to press <b +class="KEYCAP">L1</b>+<b class="KEYCAP">A</b> or <b class="KEYCAP">Stop</b>+<b +class="KEYCAP">A</b> on the keyboard, or send a <tt class="COMMAND">BREAK</tt> over the +serial console (using for example <tt class="COMMAND">~#</tt> in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=tip&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tip</span>(1)</span></a> or <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cu&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">cu</span>(1)</span></a>) to get to the +PROM prompt. It looks like this:</p> + +<pre class="SCREEN"> +<samp class="PROMPT">ok </samp> <a id="PROMPT-SINGLE" +name="PROMPT-SINGLE"><b>(1)</b></a> +<samp class="PROMPT">ok {0}</samp> <a id="PROMPT-SMP" +name="PROMPT-SMP"><b>(2)</b></a> +</pre> + +<div class="CALLOUTLIST"> +<dl compact="COMPACT"> +<dt><a href="#PROMPT-SINGLE"><b>(1)</b></a></dt> + +<dd>This is the prompt used on systems with just one CPU.</dd> + +<dt><a href="#PROMPT-SMP"><b>(2)</b></a></dt> + +<dd>This is the prompt used on SMP systems, the digit indicates the number of the active +CPU.</dd> +</dl> +</div> + +<p>At this point, place the CDROM into your drive, and from the PROM prompt, type <tt +class="COMMAND">boot cdrom</tt>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN213" name="AEN213">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="AEN252" name="AEN252">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 ensure an FTP server is running and then simply add +the following line to the password file (using the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+6.1-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 <tt class="LITERAL">any</tt>. You may then choose a Media type of <tt +class="LITERAL">FTP</tt> and type in <tt class="FILENAME">ftp://<tt +class="REPLACEABLE"><i>machine</i></tt></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&sektion=5&manpath=FreeBSD+6.1-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"><tt class="REPLACEABLE"><i>cdrom-host</i></tt>:/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="AEN284" name="AEN284">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&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+6.1-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</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file. +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.</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="AEN353" name="AEN353">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&sektion=1&manpath=FreeBSD+6.1-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 <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></kbd> +<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/sa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt class="REPLACEABLE"><i>dist2</i></tt></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="AEN378" name="AEN378">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 the PPP +utility should 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="AEN384" name="AEN384">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 <code class="OPTION">link0</code> 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="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5> + +<p>FreeBSD supports most 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 <code +class="OPTION">netmask</code> 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="AEN406" name="AEN406">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 may 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 +<code class="OPTION">-alldirs</code> option. Other NFS servers may have different +conventions. If you are getting <tt class="LITERAL">Permission Denied</tt> 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="AEN423" name="AEN423">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/sparc64/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:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</kbd> +</pre> + +<p>In the URL above, <tt class="REPLACEABLE"><i>port</i></tt> is the port number of the +proxy FTP server.</p> +</li> +</ul> + +<br /> +<br /> +</div> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN474" name="AEN474">1.6 Question and Answer Section for +UltraSPARC Architecture Users</a></h3> +</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 (exact details may +vary depending on version, architecture, and other factors):</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 base 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>These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see <a href="#TROUBLE">Section 4</a> for how to use this).</p> + +<p>The <tt class="FILENAME">floppies</tt> directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the <tt +class="FILENAME">floppies</tt> directory (see <a href="#FLOPPIES">Section 1.3</a> for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.</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">base</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&sektion=1&manpath=FreeBSD+6.1-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 +190MB 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&sektion=8&manpath=FreeBSD+6.1-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">base</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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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&sektion=8&manpath=FreeBSD+6.1-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="WARNING"> +<blockquote class="WARNING"> +<p><b>Warning:</b> Binary upgrades to FreeBSD 6.1-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to +compile incorrectly (or not at all).</p> + +<p>These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6.1-STABLE snapshots.</p> +</blockquote> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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">hosts.allow</tt>, <tt +class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt +class="FILENAME">inetd.conf</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">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">nsswitch.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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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 <tt class="LITERAL">base</tt> distribution should be selected for an +update, and the <tt class="LITERAL">man</tt> 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="AEN801" name="AEN801">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> +</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 <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the <tt +class="FILENAME">fixit.flp</tt> floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.</p> + +<p>Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “CDROM/DVD” option from the fixit menu.</p> + +<p>Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the <tt class="FILENAME">boot.flp</tt> and <tt +class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks required for +installation, create the <tt class="FILENAME">fixit.flp</tt> floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. At that point, choose the “fixit” item from the main <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +menu. Then select the “Floppy” option from the fixit menu, and insert the <tt +class="FILENAME">fixit.flp</tt> floppy disk when prompted to do so.</p> + +<p>The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.</p> + +<p>In the floppy version of fixit, some standalone utilities can be found in <tt +class="FILENAME">/stand</tt> or <tt class="FILENAME">/mnt2/stand</tt>. In the CDROM +version of fixit, these same programs can be found in <tt class="FILENAME">/stand</tt> or +<tt class="FILENAME">/mnt2/rescue</tt> (as well as the rest of the programs from the live +filesystem, which can be found under <tt class="FILENAME">/mnt</tt>).</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN845" name="AEN845">4.2 Common Installation Problems for +UltraSPARC Architecture Users</a></h3> +</div> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/readme.html b/en/releases/6.1R/readme.html new file mode 100644 index 0000000000..250886b34a --- /dev/null +++ b/en/releases/6.1R/readme.html @@ -0,0 +1,416 @@ +<!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 6.1-RELEASE README</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.1-RELEASE README</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD +Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.37 +2005/04/19 09:43:53 hrs Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group +are trademarks of The Open Group in the United States and other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<hr /> +</div> + +<blockquote class="ABSTRACT"> +<div class="ABSTRACT"><a id="AEN22" name="AEN22"></a> +<p>This document gives a brief introduction to FreeBSD 6.1-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="INTRO" name="INTRO">1 Introduction</a></h2> + +<p>This distribution is a snapshot of FreeBSD 6.1-RELEASE, the latest point along the +6.1-STABLE branch.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN27" name="AEN27">1.1 About FreeBSD</a></h3> + +<p>FreeBSD is an operating system based on 4.4 BSD Lite for DEC/Compaq/HP Alpha/AXP +computers (alpha), AMD64 and Intel EM64T based PC hardware (amd64), Intel, AMD, Cyrix or +NexGen “x86” based PC hardware (i386), Intel Itanium Processor based +computers (ia64), NEC PC-9801/9821 series PCs and compatibles (pc98), and <span +class="TRADEMARK">UltraSPARC</span>® machines (sparc64). Versions for the <span +class="TRADEMARK">PowerPC</span>® (powerpc), and <span +class="TRADEMARK">MIPS</span>® (mips) architectures are currently under development +as well. FreeBSD works with a wide variety of peripherals and configurations and can be +used for everything from software development to games to Internet Service Provision.</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 +<span class="TRADEMARK">UNIX</span>® 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 13,300 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 <span +class="TRADEMARK">UNIX</span>. 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="AEN41" name="AEN41">1.2 Target Audience</a></h3> + +<p>This snapshot 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="OBTAIN" name="OBTAIN">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="AEN47" name="AEN47">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="AEN54" name="AEN54">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://mirrorlist.FreeBSD.org/" target="_top">http://mirrorlist.FreeBSD.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"><<a +href="mailto:freebsd-admin@FreeBSD.org">freebsd-admin@FreeBSD.org</a>></code> for +more details on becoming an official mirror site. You can also find useful information +for mirror sites at the <a +href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/hubs/" target="_top">Mirroring +FreeBSD</a> article.</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="AEN68" name="AEN68">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're tracking the 6.1-STABLE development efforts, you <span class="emphasis"><i +class="EMPHASIS">must</i></span> join the <a +href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-current" +target="_top">FreeBSD-CURRENT 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 the <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 from the Mailman pages 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 Mailman interface instead.</p> +</blockquote> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN86" name="AEN86">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&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">send-pr</span>(1)</span></a> +command. “Problem Reports” (PRs) submitted in this way will be filed and +their progress tracked; the FreeBSD developers will do their best to respond to all +reported bugs as soon as possible. <a +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&sektion=1&manpath=FreeBSD+6.1-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&sektion=1&manpath=FreeBSD+6.1-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="SEEALSO" name="SEEALSO">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 snapshot +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 6.1-RELEASE compared to the previous release (FreeBSD +6.0-RELEASE).</p> +</li> + +<li> +<p><tt class="FILENAME">HARDWARE.TXT</tt>: The hardware compatibility 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 <span class="TRADEMARK">i386</span>™, and vice versa. The +architecture for which each document applies will be listed in that document's title.</p> +</blockquote> +</div> + +<br /> +<br /> +<p>On platforms that support <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +(currently alpha, <span class="TRADEMARK">i386</span>, ia64, pc98, and <span +class="TRADEMARK">Sparc64</span>®), these documents are generally available via the +Documentation menu during installation. Once the system is installed, you can revisit +this menu by re-running the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-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="AEN152" name="AEN152">4.2 Manual Pages</a></h3> + +<p>As with almost all <span class="TRADEMARK">UNIX</span> 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&sektion=1&manpath=FreeBSD+6.1-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&sektion=7&manpath=FreeBSD+6.1-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&sektion=7&manpath=FreeBSD+6.1-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&sektion=9&manpath=FreeBSD+6.1-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="AEN170" name="AEN170">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 <span +class="TRADEMARK">UNIX</span> heritage, many other articles and books written for <span +class="TRADEMARK">UNIX</span> 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="ACKNOWLEDGEMENTS" name="ACKNOWLEDGEMENTS">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 +snapshot. 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 snapshot 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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/relnotes-alpha.html b/en/releases/6.1R/relnotes-alpha.html new file mode 100644 index 0000000000..ec75a641e5 --- /dev/null +++ b/en/releases/6.1R/relnotes-alpha.html @@ -0,0 +1,1011 @@ +<!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 6.1-RELEASE Release Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.1-RELEASE Release +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The +FreeBSD Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.15.2.7 2006/05/05 17:07:14 hrs Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.</p> + +<p>IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and +Electronics Engineers, Inc. in the United States.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<div> +<div class="ABSTRACT"><a id="AEN24" name="AEN24"></a> +<p>The release notes for FreeBSD 6.1-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.1-STABLE development line. This document lists applicable +security advisories that were issued since the last release, as well as significant +changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also +presented.</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="#BOOT">Boot Loader Changes</a></dt> + +<dt>2.2.2 <a href="#PROC">Hardware Support</a></dt> + +<dt>2.2.3 <a href="#NET-PROTO">Network Protocols</a></dt> + +<dt>2.2.4 <a href="#DISKS">Disks and Storage</a></dt> + +<dt>2.2.5 <a href="#FS">File Systems</a></dt> + +<dt>2.2.6 <a href="#AEN392">Contributed Software</a></dt> +</dl> +</dd> + +<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + +<dd> +<dl> +<dt>2.3.1 <a href="#RC-SCRIPTS"><tt class="FILENAME">/etc/rc.d</tt> Scripts</a></dt> +</dl> +</dd> + +<dt>2.4 <a href="#AEN580">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> + +<dt>2.7 <a href="#DOC">Documentation</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 6.1-RELEASE on the Alpha/AXP +hardware platform. It describes recently added, changed, or deleted features of FreeBSD. +It also provides some notes on upgrading from previous versions of FreeBSD.</p> + +<p>This distribution of FreeBSD 6.1-RELEASE is a snapshot distribution. It can be found +at <a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</a> or any of its mirrors. More +information on obtaining this (or other) snapshot 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” appendix</a> to the <a +href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD +Handbook</a>.</p> + +<p>All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with “late-breaking” information discovered late +in the release cycle or after the release. Typically, it contains information on known +bugs, security advisories, and corrections to documentation. An up-to-date copy of the +errata for FreeBSD 6.1-RELEASE can be found on the FreeBSD Web site.</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 +6.0-RELEASE.</p> + +<p>Typical release note items document recent security advisories issued after +6.0-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3> + +<p>A temporary file vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a>, +which could allow a local attacker to overwrite files in the context of a user running +the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a> +utility, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc" +target="_top">FreeBSD-SA-06:01.texindex</a>.</p> + +<p>A temporary file vulnerability in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> text editor, +which could allow a local attacker to overwrite files in the context of a user running <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a>, has been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc" +target="_top">FreeBSD-SA-06:02.ee</a>.</p> + +<p>Several vulnerabilities in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a> utility +have been corrected. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc" +target="_top">FreeBSD-SA-06:03.cpio</a>.</p> + +<p>An error in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +fragment handling, which could cause a crash, has been fixed. For more details see +security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc" +target="_top">FreeBSD-SA-06:04.ipfw</a>.</p> + +<p>A potential buffer overflow in the IEEE 802.11 scanning code has been corrected. For +more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc" +target="_top">FreeBSD-SA-06:05.80211</a>.</p> + +<p>Two instances in which portions of kernel memory could be disclosed to users have been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc" +target="_top">FreeBSD-SA-06:06.kmem</a>.</p> + +<p>A logic bug in the IP fragment handling in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>, which could +cause a crash under certain circumstances, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc" +target="_top">FreeBSD-SA-06:07.pf</a>.</p> + +<p>A logic bug in the NFS server code, which could cause a crash when the server received +a message with a zero-length payload, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc" +target="_top">FreeBSD-SA-06:10.nfs</a>.</p> + +<p>A programming error in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fast_ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fast_ipsec</span>(4)</span></a> +implementation results in the sequence number associated with a Security Association not +being updated, allowing packets to unconditionally pass sequence number verification +checks, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc" +target="_top">FreeBSD-SA-06:11.ipsec</a>.</p> + +<p>A logic bug that could cause <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=opiepasswd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">opiepasswd</span>(1)</span></a> to +allow an unprivileged user to configure OPIE authentication for the root user under +certain circumstances, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc" +target="_top">FreeBSD-SA-06:12.opie</a>.</p> + +<p>An asynchronous signal handling vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sendmail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sendmail</span>(8)</span></a>, +which could allow a remote attacker to execute arbitrary code with the privileges of the +user running sendmail, typically <tt class="USERNAME">root</tt>, has been fixed. For more +details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc" +target="_top">FreeBSD-SA-06:13.sendmail</a>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ddb</span>(4)</span></a> debugger +now supports the <tt class="LITERAL">show lock</tt> command. If the argument has a valid +lock class, this displays various information about the lock and calls a new function +pointer in lock_class (lc_ddb_show) to dump class-specific information about the lock as +well (such as the owner of a mutex or xlock'ed sx lock).</p> + +<p><tt class="FILENAME">DEFAULTS</tt> kernel configuration files for each platform have +been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=firmware&sektion=9&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">firmware</span>(9)</span></a> +subsystem has been added. This allows to load binary data into the kernel via a specially +crafted module.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=random&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">random</span>(4)</span></a> +entropy device driver is now MPSAFE.</p> + +<p>A new sysctl variable <code class="VARNAME">security.mac.biba.interfaces_equal</code> +which makes all network interfaces be created with the label <tt +class="LITERAL">biba/equal(equal-equal)</tt>, has been added. This is useful where +programs such as <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dhclient&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dhclient</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppp</span>(8)</span></a>. which +initialize network interfaces do not have any labeling support. This variable is set as +<tt class="LITERAL">0</tt>(disabled) by default.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.1 Boot Loader Changes</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="PROC" name="PROC">2.2.2 Hardware Support</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi_thermal&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi_thermal</span>(4)</span></a> +driver now supports passive cooling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> driver +has been integrated into <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and +the <tt class="DEVICENAME">kbd</tt> device driver. By default <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> will +look for the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> +keyboard first, and then, if not found, look for any keyboard. Switching to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> can be +done at boot time by loading the <tt class="LITERAL">kbdmux</tt> kernel module via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=loader&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">loader</span>(8)</span></a>, or at +runtime via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kldload&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kldload</span>(8)</span></a> and +releasing the active keyboard.</p> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="MM" name="MM">2.2.2.1 Multimedia Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=agp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">agp</span>(4)</span></a> driver +now supports ATI IGP chipsets.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sound&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sound</span>(4)</span></a> driver +has been updated in various aspects including fixing lock-related bugs that could cause +system panics in the previous releases and some performance improvements. Also this +driver now supports wider range sampling rate, multiple precisions choice, and 24/32-bit +PCM format conversion.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver has been added. This supports ATI IXP 200/300/400 series audio controllers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_als4000&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_als4000</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via8233&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via8233</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver is now MPSAFE.</p> +</div> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="NET-IF" name="NET-IF">2.2.2.2 Network Interface Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> driver +has been updated to version 0.9.16.16.</p> + +<p>A bug which prevents the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> driver +from working on a system with over 1GB RAM has been fixed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=polling&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">polling</span>(4)</span></a> +mode.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver now +supports big-endian architectures such as sparc64.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=le&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">le</span>(4)</span></a> driver, which +supports AMD Am7900 LANCE and Am79C9xx PCnet NICs and is based on NetBSD's +implementation, has been added. While the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +also supports these NICs, this driver has several advantages over it such as MPSAFE, +ALTQ, VLAN_MTU, ifmedia, and 32-bit DMA for PCI variants.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver is +now MPSAFE.</p> +</div> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.3 Network Protocols</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> +retransmission algorithm has been rewritten as that ARP requests are retransmitted +without suppression, while there is demand for such ARP entry. Due to this change, a +sysctl variable <code class="VARNAME">net.link.ether.inet.host_down_time</code> has been +removed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now +supports a sysctl variable <code +class="VARNAME">net.link.ether.inet.log_arp_permanent_modify</code> to suppress logging +of attempts to modify permanent ARP entries.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports creating span ports, which transmit a copy of every frame +received by the bridge. This feature can be enabled by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ifconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ifconfig</span>(8)</span></a>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports RFC 3378 EtherIP. This change makes it possible to add <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gif</span>(4)</span></a> +interfaces to bridges, which will then send and receive IP protocol 97 packets. Packets +are Ethernet frames with an EtherIP header prepended.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +packet filter now supports IPv6. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a> packet +filter is deprecated and will be removed in the future releases.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> now +supports substitution of the action argument with the value obtained from table lookup, +which allows some optimization of rulesets. This is now applicable only to <tt +class="LITERAL">pipe</tt>, <tt class="LITERAL">queue</tt>, <tt +class="LITERAL">divert</tt>, <tt class="LITERAL">tee</tt>, <tt +class="LITERAL">netgraph</tt>, and <tt class="LITERAL">ngtee</tt> rules. For example, the +following rules will throw different packets to different pipes:</p> + +<pre class="PROGRAMLISTING"> +pipe 1000 config bw 1000Kbyte/s +pipe 4000 config bw 4000Kbyte/s +table 1 add x.x.x.x 1000 +table 1 add x.x.x.y 4000 +pipe tablearg ip from table(1) to any +</pre> + +<p>A bug has been fixed in which NFS over TCP would not reconnect when the server sent a +FIN. This problem had occurred with Solaris NFS servers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_iface&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_iface</span>(4)</span></a> +Netgraph node now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p> + +<p>The path MTU discovery for multicast packets in the FreeBSD <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6</span>(4)</span></a> stack has +been disabled by default because notifying path MTU by a lot of routers in multicast can +be a kind of distributed Denial-of-Service attack to a router. This feature can be +re-enabled by using a new sysctl variable <code +class="VARNAME">net.inet6.ip6.mcast_pmtu</code>.</p> + +<p>The TCP bandwidth-delay product limiting feature has been disabled when the RTT is +below a certain threshold. This optimization does not make sense on a LAN as it has +trouble figuring out the maximal bandwidth due to the coarse tick granularity. A new +sysctl variable <code class="VARNAME">net.inet.tcp.inflight.rttthresh</code> specifies +the threshold in milliseconds below which this feature will disengage. It defaults to +10ms.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.4 Disks and Storage</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +has been improved on its performance and now supports full 64-bit DMA. While this feature +is enabled by default, this can be forced off by setting the <code +class="VARNAME">hw.amr.force_sg32</code> loader tunable for debugging purpose.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ioctl&sektion=2&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ioctl</span>(2)</span></a> +requests necessary for Linux LSI MegaRaid tools on FreeBSD's Linux emulation +environment.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports a workaround for some controllers whose DMA does not work properly in 48bit +mode. For the suspicious controllers the PIO mode will be used for access to over 137GB +areas.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports the ITE IT8211F IDE controller, and Promise PDC40718 and PDC40719 chip found +in Promise Fasttrak TX4300.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports DMA for kernel crash dump and crash dumping to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +device.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +driver now supports JMicron ATA RAID metadata.</p> + +<p>The <tt class="LITERAL">GEOM_LABEL</tt> class now supports Ext2FS, NTFS, and +ReiserFS.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> class now supports kernel crash dump to the +GEOM providers.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now support sysctl variables <code +class="VARNAME">kern.geom.mirror.disconnect_on_failure</code> and <code +class="VARNAME">kern.geom.graid3.disconnect_on_failure</code> to control whether failed +components will be disconnected or not. The default value is <tt class="LITERAL">1</tt> +to preserve the current behavior, and if it is set to <tt class="LITERAL">0</tt> such +components are not disconnected and the kernel will try to still use them (only first +error will be logged). This is helpful for the case of multiple broken components (in +different places), so actually all data is available. The broken components will be +visible in <tt class="COMMAND">gmirror list</tt> or <tt class="COMMAND">graid3 list</tt> +output with flag <tt class="LITERAL">BROKEN</tt>.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now use parallel I/O request for synchronization to improve the performance. New +sysctl variables <code class="VARNAME">kern.geom.mirror.sync_requests</code> and <code +class="VARNAME">kern.geom.raid3.sync_requests</code> define how many parallel I/O +requests should be used. Also, sysctl variables <code +class="VARNAME">kern.geom.mirror.reqs_per_sync</code>, <code +class="VARNAME">kern.geom.mirror.syncs_per_sec</code>, <code +class="VARNAME">kern.geom.raid3.reqs_per_sync</code>, and <code +class="VARNAME">kern.geom.raid3.syncs_per_sec</code> are deprecated and have been +removed.</p> + +<p>A new GEOM class <tt class="LITERAL">GEOM_ZERO</tt> has been added. It creates very +huge provider (41PB) <tt class="FILENAME">/dev/gzero</tt> and mainly for performance +testing. On <tt class="LITERAL">BIO_READ</tt> request it zero-fills <code +class="VARNAME">bio_data</code> and on <tt class="LITERAL">BIO_WRITE</tt> it does +nothing.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +has been updated to the 9.3.0.1 release on the 3ware Web site.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=geli&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geli</span>(8)</span></a> now +supports loading keyfiles before root file system is mounted. For example, the following +entries can be used in <tt class="FILENAME">/boot/loader.conf</tt> to enable it:</p> + +<pre class="PROGRAMLISTING"> +geli_da0_keyfile0_load="YES" +geli_da0_keyfile0_type="da0:geli_keyfile0" +geli_da0_keyfile0_name="/boot/keys/da0.key0" +geli_da0_keyfile1_load="YES" +geli_da0_keyfile1_type="da0:geli_keyfile1" +geli_da0_keyfile1_name="/boot/keys/da0.key1" +geli_da0_keyfile2_load="YES" +geli_da0_keyfile2_type="da0:geli_keyfile2" +geli_da0_keyfile2_name="/boot/keys/da0.key2" + +geli_da1s3a_keyfile0_load="YES" +geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" +geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" +</pre> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver, +which supports the LSI MegaRAID SAS controller family, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> +driver, which supports HighPoint's RocketRAID 232x series of RAID controllers, has been +added.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="FS" name="FS">2.2.5 File Systems</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN392" name="AEN392">2.2.6 Contributed Software</a></h4> + +<p><b class="APPLICATION">DRM</b> has been updated to a snapshot from DRI CVS as of +20051202.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bsnmpd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bsnmpd</span>(1)</span></a> +utility now supports the Host Resources MIB described in RFC 2790.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now supports the <tt class="LITERAL">nocpu</tt> directive, which cancels the +effect of a previous <tt class="LITERAL">cpu</tt> directive.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now reads <tt class="FILENAME">DEFAULTS</tt> kernel configuration file if it +exists in the current directory before the specified configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=csh&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">csh</span>(1)</span></a> utility +now supports NLS catalog. Note that this requires installing the <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/shells/tcsh_nls/pkg-descr"><tt +class="FILENAME">shells/tcsh_nls</tt></a> port.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> utility +now supports a <code class="OPTION">-f</code> option to specify a configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ln&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ln</span>(1)</span></a> utility now +supports an <code class="OPTION">-F</code> flag which allows to delete existing empty +directories, when creating symbolic links.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=locate&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">locate</span>(1)</span></a> +utility now supports a <code class="OPTION">-0</code> flag to make this utility +interoperable with <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xargs</span>(1)</span></a>'s <code +class="OPTION">-0</code> flag.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ls&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ls</span>(1)</span></a> utility now +supports an <code class="OPTION">-I</code> flag to disable the automatic <code +class="OPTION">-A</code> flag for the superuser.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> utility +now creates a PID file <tt class="FILENAME">/var/run/ftpd.pid</tt> even when no <code +class="OPTION">-p</code> option is specified.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">getfacl</span>(1)</span></a> +utility now supports a <code class="OPTION">-q</code> flag to suppress the per-file +header comment listing the file name, owner, and group.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gvinum&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gvinum</span>(8)</span></a> +utility now supports commands to rename objects and to move a subdisk from one drive to +another.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(8)</span></a> utility +supports a <code class="OPTION">-J <tt class="REPLACEABLE"><i>jid_file</i></tt></code> +option to write out a JidFile, similar to a PidFile, containing the jailid, path, +hostname, IP and the command used to start the jail.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> utility +now supports a <code class="OPTION">-H</code> flag, which causes kdump to print an +additional field holding the threadid.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> program +now supports a <code class="OPTION">-s</code> flag to suppress the display of I/O +data.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mergemaster</span>(8)</span></a> +utility now supports an <code class="OPTION">-A</code> option to explicitly specify an +architecture to pass through to the underlying makefiles.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> daemon +now supports an <code class="OPTION">-H</code> flag to enable horizontal virtual +scrolling similar to a <code class="OPTION">-V</code> flag for vertical virtual +scrolling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=netstat&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">netstat</span>(1)</span></a> +utility now supports printing <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipsec</span>(4)</span></a> +protocol statistics if the kernel was compiled with <tt class="LITERAL">FAST_IPSEC</tt> +rather than the KAME IPSEC stack. Note that the output of <tt class="COMMAND">netstat -s +-p ipsec</tt> differs depending on which stack is compiled into the kernel since they +each keep different statistics.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=periodic&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">periodic</span>(8)</span></a> +daily script now supports display of the status of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gmirror&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gmirror</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=graid3&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">graid3</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gstripe&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gstripe</span>(8)</span></a>, and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gconcat&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gconcat</span>(8)</span></a> +devices. Note that these are disabled by default.</p> + +<p>A new function, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pidfile&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pidfile</span>(3)</span></a>, +which provides reliable pidfiles handling, has been implemented in <tt +class="FILENAME">libutil</tt>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rfcomm_sppd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rfcomm_sppd</span>(1)</span></a> +now supports service name in addition to <code class="OPTION">-c</code> option with +channel number. The supported names are: DUN (Dial-Up Networking), FAX (Fax), LAN (LAN +Access Using PPP), and SP (Serial Port).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snapinfo&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snapinfo</span>(8)</span></a> +utility, which shows snapshot locations on UFS filesystems, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtonum&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtonum</span>(3)</span></a> +library function has been implemented based on OpenBSD's implementation. This is an +improved version of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtoll&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtoll</span>(3)</span></a>.</p> + +<p>A bug in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ypwhich&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ypwhich</span>(1)</span></a> +utility which causes the <code class="OPTION">-m</code> option to produce an incorrect +list of available named maps has been fixed.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="RC-SCRIPTS" name="RC-SCRIPTS">2.3.1 <tt +class="FILENAME">/etc/rc.d</tt> Scripts</a></h4> + +<p>The <tt class="FILENAME">bluetooth</tt> script has been added. This script will be +called from <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> in +response to device attachment/detachment events and to stop/start particular device +without unplugging it by hand. The configuration parameters are in <tt +class="FILENAME">/etc/defaults/bluetooth.device.conf</tt>, and can be overridden by using +<tt class="FILENAME">/etc/bluetooth/<tt class="REPLACEABLE"><i>$device</i></tt>.conf</tt> +(where <tt class="REPLACEABLE"><i>$device</i></tt> is <tt class="DEVICENAME">ubt0</tt>, +<tt class="DEVICENAME">btcc0</tt>, and so on.) For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bluetooth.conf&sektion=5&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span +class="REFENTRYTITLE">bluetooth.conf</span>(5)</span></a>.</p> + +<p>The <tt class="FILENAME">hcsecd</tt> and <tt class="FILENAME">sdpd</tt> scripts have +been added for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hcsecd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hcsecd</span>(8)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sdpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sdpd</span>(8)</span></a> daemons. +These daemons can run even if no Bluetooth devices are attached to the system, but both +daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets +layer must be either loaded as a module or compiled into kernel before the daemons can +run.</p> + +<p>The <tt class="FILENAME">hostapd</tt> script for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hostapd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hostapd</span>(8)</span></a> has +been added.</p> + +<p>The <tt class="FILENAME">jail</tt> script now supports the <code +class="VARNAME">jail_interface</code> option and the <code class="VARNAME">jail_<tt +class="REPLACEABLE"><i>jid</i></tt>_interface</code> option which create an IP alias on +the given interface.</p> + +<p>The <tt class="FILENAME">netif</tt> script now supports <code +class="VARNAME">ipv4_addrs_<tt class="REPLACEABLE"><i>ifn</i></tt></code>, which adds one +or more IPv4 address from a ranged list in CIRD notation. For example:</p> + +<pre class="PROGRAMLISTING"> +ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" +</pre> + +<p>The <tt class="FILENAME">ppp-user</tt> script has been renamed to <tt +class="FILENAME">ppp</tt>.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN580" name="AEN580">2.4 Contributed Software</a></h3> + +<p><b class="APPLICATION">BIND</b> has been updated from 9.3.1 to 9.3.2.</p> + +<p><b class="APPLICATION">hostapd</b> has been updated from version 0.3.9 to version +0.4.8.</p> + +<p><b class="APPLICATION">GNU Troff</b> has been updated from version 1.19 to version +1.19.2.</p> + +<p><b class="APPLICATION">sendmail</b> has been updated from 8.13.4 to 8.13.6.</p> + +<p>The timezone database has been updated from the <b class="APPLICATION">tzdata2005l</b> +release to the <b class="APPLICATION">tzdata2005r</b> release.</p> + +<p><b class="APPLICATION">WPA Supplicant</b> has been updated from version 0.3.9 to +version 0.4.8.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection +Infrastructure</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> +command now supports an <code class="OPTION">-P</code> flag, which is the same as the +<code class="OPTION">-p</code> flag except that the given prefix is also used recursively +for the dependency packages if any.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +utilities now support a <code class="OPTION">-K</code> flag to save packages to the +current directory (or <code class="VARNAME">PKGDIR</code> if defined) by default.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +program now supports an <code class="OPTION">-x</code> flag to support basic regular +expressions for package name, an <code class="OPTION">-E</code> flag for extended regular +expressions, and a <code class="OPTION">-G</code> for exact matching.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_version&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_version</span>(1)</span></a> +utility now supports an <code class="OPTION">-o</code> flag to show the origin recorded +on package generation instead of the package name, and an <code class="OPTION">-O</code> +flag to list packages whose registered origin is origin only.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility (<tt class="FILENAME">sysutils/portsnap</tt>) has been added into the FreeBSD +base system. This is a secure, easy to use, fast, lightweight, and generally good way for +users to keep their ports trees up to date.</p> + +<p>A incorrect handling of <code class="VARNAME">HTTP_PROXY_AUTH</code> in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility has been fixed.</p> + +<p>The startup scripts from the <code class="VARNAME">local_startup</code> directory now +evaluated by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rcorder&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rcorder</span>(8)</span></a> with +scripts in the base system.</p> + +<p>The suffix of startup scripts from the Ports Collection has been removed. This means +<tt class="FILENAME">foo.sh</tt> is renamed to <tt class="FILENAME">foo</tt>, and now +scripts whose name is something like <tt class="FILENAME">foo.ORG</tt> will also be +invoked. You are recommended to reinstall packages which install such scripts and remove +extra files in the <code class="VARNAME">local_startup</code> directory.</p> + +<p>New <tt class="FILENAME">rc.conf</tt> variables, <code +class="VARNAME">ldconfig_local_dirs</code> and <code +class="VARNAME">ldconfig_local32_dirs</code> have been added. These hold lists of local +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ldconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ldconfig</span>(8)</span></a> +directories.</p> + +<p>The <tt class="COMMAND">@cwd</tt> command in <tt class="FILENAME">pkg-plist</tt> now +allows no directory argument. If no directory argument is given, it will set current +working directory to the first prefix given by the <tt class="COMMAND">@cwd</tt> +command.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and +Integration</a></h3> + +<p>The <tt class="FILENAME">/var/audit</tt> directory and <tt class="LITERAL">audit</tt> +group have been added. These are for the TrustedBSD <b class="APPLICATION">OpenBSM</b> +distribution, which will be imported in the future releases.</p> + +<p>The supported version of the <b class="APPLICATION">GNOME</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/gnome2/pkg-descr"><tt +class="FILENAME">x11/gnome2</tt></a>) has been updated from 2.10.2 to 2.12.3.</p> + +<p>The supported version of the <b class="APPLICATION">KDE</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/kde2/pkg-descr"><tt +class="FILENAME">x11/kde2</tt></a>) has been updated from 3.4.2 to 3.5.1.</p> + +<p>The supported version of the <b class="APPLICATION">Perl</b> interpreter (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt +class="FILENAME">lang/perl5.8</tt></a>) has been updated from 5.8.7 to 5.8.8.</p> + +<p>The supported version of the <b class="APPLICATION">Xorg</b> windowing system (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/xorg/pkg-descr"><tt +class="FILENAME">x11/xorg</tt></a>) has been updated from 6.8.2 to 6.9.0.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DOC" name="DOC">2.7 Documentation</a></h3> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of +FreeBSD</a></h2> + +<p>Source upgrades to FreeBSD 6.1-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.1-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.1-RELEASE.</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/relnotes-amd64.html b/en/releases/6.1R/relnotes-amd64.html new file mode 100644 index 0000000000..f993edc3be --- /dev/null +++ b/en/releases/6.1R/relnotes-amd64.html @@ -0,0 +1,1035 @@ +<!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/amd64 6.1-RELEASE Release Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/amd64 6.1-RELEASE Release +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The +FreeBSD Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.15.2.7 2006/05/05 17:07:14 hrs Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.</p> + +<p>IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and +Electronics Engineers, Inc. in the United States.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<div> +<div class="ABSTRACT"><a id="AEN24" name="AEN24"></a> +<p>The release notes for FreeBSD 6.1-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.1-STABLE development line. This document lists applicable +security advisories that were issued since the last release, as well as significant +changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also +presented.</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="#BOOT">Boot Loader Changes</a></dt> + +<dt>2.2.2 <a href="#PROC">Hardware Support</a></dt> + +<dt>2.2.3 <a href="#NET-PROTO">Network Protocols</a></dt> + +<dt>2.2.4 <a href="#DISKS">Disks and Storage</a></dt> + +<dt>2.2.5 <a href="#FS">File Systems</a></dt> + +<dt>2.2.6 <a href="#AEN392">Contributed Software</a></dt> +</dl> +</dd> + +<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + +<dd> +<dl> +<dt>2.3.1 <a href="#RC-SCRIPTS"><tt class="FILENAME">/etc/rc.d</tt> Scripts</a></dt> +</dl> +</dd> + +<dt>2.4 <a href="#AEN580">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> + +<dt>2.7 <a href="#DOC">Documentation</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 6.1-RELEASE on the AMD64 hardware +platform. It describes recently added, changed, or deleted features of FreeBSD. It also +provides some notes on upgrading from previous versions of FreeBSD.</p> + +<p>This distribution of FreeBSD 6.1-RELEASE is a snapshot distribution. It can be found +at <a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</a> or any of its mirrors. More +information on obtaining this (or other) snapshot 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” appendix</a> to the <a +href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD +Handbook</a>.</p> + +<p>All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with “late-breaking” information discovered late +in the release cycle or after the release. Typically, it contains information on known +bugs, security advisories, and corrections to documentation. An up-to-date copy of the +errata for FreeBSD 6.1-RELEASE can be found on the FreeBSD Web site.</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 +6.0-RELEASE.</p> + +<p>Typical release note items document recent security advisories issued after +6.0-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3> + +<p>A temporary file vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a>, +which could allow a local attacker to overwrite files in the context of a user running +the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a> +utility, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc" +target="_top">FreeBSD-SA-06:01.texindex</a>.</p> + +<p>A temporary file vulnerability in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> text editor, +which could allow a local attacker to overwrite files in the context of a user running <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a>, has been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc" +target="_top">FreeBSD-SA-06:02.ee</a>.</p> + +<p>Several vulnerabilities in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a> utility +have been corrected. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc" +target="_top">FreeBSD-SA-06:03.cpio</a>.</p> + +<p>An error in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +fragment handling, which could cause a crash, has been fixed. For more details see +security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc" +target="_top">FreeBSD-SA-06:04.ipfw</a>.</p> + +<p>A potential buffer overflow in the IEEE 802.11 scanning code has been corrected. For +more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc" +target="_top">FreeBSD-SA-06:05.80211</a>.</p> + +<p>Two instances in which portions of kernel memory could be disclosed to users have been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc" +target="_top">FreeBSD-SA-06:06.kmem</a>.</p> + +<p>A logic bug in the IP fragment handling in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>, which could +cause a crash under certain circumstances, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc" +target="_top">FreeBSD-SA-06:07.pf</a>.</p> + +<p>A logic bug in the NFS server code, which could cause a crash when the server received +a message with a zero-length payload, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc" +target="_top">FreeBSD-SA-06:10.nfs</a>.</p> + +<p>A programming error in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fast_ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fast_ipsec</span>(4)</span></a> +implementation results in the sequence number associated with a Security Association not +being updated, allowing packets to unconditionally pass sequence number verification +checks, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc" +target="_top">FreeBSD-SA-06:11.ipsec</a>.</p> + +<p>A logic bug that could cause <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=opiepasswd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">opiepasswd</span>(1)</span></a> to +allow an unprivileged user to configure OPIE authentication for the root user under +certain circumstances, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc" +target="_top">FreeBSD-SA-06:12.opie</a>.</p> + +<p>An asynchronous signal handling vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sendmail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sendmail</span>(8)</span></a>, +which could allow a remote attacker to execute arbitrary code with the privileges of the +user running sendmail, typically <tt class="USERNAME">root</tt>, has been fixed. For more +details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc" +target="_top">FreeBSD-SA-06:13.sendmail</a>.</p> + +<p>An information disclosure issue found in the FreeBSD kernel running on 7th- and +8th-generation AMD processors has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:14.fpu.asc" +target="_top">FreeBSD-SA-06:14.fpu</a>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ddb</span>(4)</span></a> debugger +now supports the <tt class="LITERAL">show lock</tt> command. If the argument has a valid +lock class, this displays various information about the lock and calls a new function +pointer in lock_class (lc_ddb_show) to dump class-specific information about the lock as +well (such as the owner of a mutex or xlock'ed sx lock).</p> + +<p><tt class="FILENAME">DEFAULTS</tt> kernel configuration files for each platform have +been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=firmware&sektion=9&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">firmware</span>(9)</span></a> +subsystem has been added. This allows to load binary data into the kernel via a specially +crafted module.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=random&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">random</span>(4)</span></a> +entropy device driver is now MPSAFE.</p> + +<p>A new sysctl variable <code class="VARNAME">security.mac.biba.interfaces_equal</code> +which makes all network interfaces be created with the label <tt +class="LITERAL">biba/equal(equal-equal)</tt>, has been added. This is useful where +programs such as <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dhclient&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dhclient</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppp</span>(8)</span></a>. which +initialize network interfaces do not have any labeling support. This variable is set as +<tt class="LITERAL">0</tt>(disabled) by default.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.1 Boot Loader Changes</a></h4> + +<p>A new loader tunable <code class="VARNAME">comconsole_speed</code> to change the +serial console speed has been added. If the previous stage boot loader requested a serial +console then the default speed is determined from the current serial port speed, and +otherwise it is set to 9600 or the value of the kernel option <tt +class="LITERAL">BOOT_COMCONSOLE_SPEED</tt> at compile time.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="PROC" name="PROC">2.2.2 Hardware Support</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi_thermal&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi_thermal</span>(4)</span></a> +driver now supports passive cooling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> driver +has been integrated into <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and +the <tt class="DEVICENAME">kbd</tt> device driver. By default <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> will +look for the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> +keyboard first, and then, if not found, look for any keyboard. Switching to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> can be +done at boot time by loading the <tt class="LITERAL">kbdmux</tt> kernel module via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=loader&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">loader</span>(8)</span></a>, or at +runtime via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kldload&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kldload</span>(8)</span></a> and +releasing the active keyboard.</p> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="MM" name="MM">2.2.2.1 Multimedia Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=agp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">agp</span>(4)</span></a> driver +now supports ATI IGP chipsets.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sound&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sound</span>(4)</span></a> driver +has been updated in various aspects including fixing lock-related bugs that could cause +system panics in the previous releases and some performance improvements. Also this +driver now supports wider range sampling rate, multiple precisions choice, and 24/32-bit +PCM format conversion.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver has been added. This supports ATI IXP 200/300/400 series audio controllers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_als4000&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_als4000</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=speaker&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">speaker</span>(4)</span></a> +driver now supports FreeBSD/amd64.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via8233&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via8233</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver is now MPSAFE.</p> +</div> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="NET-IF" name="NET-IF">2.2.2.2 Network Interface Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> driver +has been updated to version 0.9.16.16.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bce&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bce</span>(4)</span></a> driver, +which supports Broadcom NetXtreme II (BCM5706/BCM5708) PCI/PCIe Gigabit Ethernet +controllers, has been added. For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bce&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bce</span>(4)</span></a>.</p> + +<p>A bug which prevents the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> driver +from working on a system with over 1GB RAM has been fixed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=polling&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">polling</span>(4)</span></a> +mode.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver now +supports big-endian architectures such as sparc64.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=le&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">le</span>(4)</span></a> driver, which +supports AMD Am7900 LANCE and Am79C9xx PCnet NICs and is based on NetBSD's +implementation, has been added. While the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +also supports these NICs, this driver has several advantages over it such as MPSAFE, +ALTQ, VLAN_MTU, ifmedia, and 32-bit DMA for PCI variants.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver is +now MPSAFE.</p> +</div> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.3 Network Protocols</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> +retransmission algorithm has been rewritten as that ARP requests are retransmitted +without suppression, while there is demand for such ARP entry. Due to this change, a +sysctl variable <code class="VARNAME">net.link.ether.inet.host_down_time</code> has been +removed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now +supports a sysctl variable <code +class="VARNAME">net.link.ether.inet.log_arp_permanent_modify</code> to suppress logging +of attempts to modify permanent ARP entries.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports creating span ports, which transmit a copy of every frame +received by the bridge. This feature can be enabled by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ifconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ifconfig</span>(8)</span></a>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports RFC 3378 EtherIP. This change makes it possible to add <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gif</span>(4)</span></a> +interfaces to bridges, which will then send and receive IP protocol 97 packets. Packets +are Ethernet frames with an EtherIP header prepended.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +packet filter now supports IPv6. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a> packet +filter is deprecated and will be removed in the future releases.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> now +supports substitution of the action argument with the value obtained from table lookup, +which allows some optimization of rulesets. This is now applicable only to <tt +class="LITERAL">pipe</tt>, <tt class="LITERAL">queue</tt>, <tt +class="LITERAL">divert</tt>, <tt class="LITERAL">tee</tt>, <tt +class="LITERAL">netgraph</tt>, and <tt class="LITERAL">ngtee</tt> rules. For example, the +following rules will throw different packets to different pipes:</p> + +<pre class="PROGRAMLISTING"> +pipe 1000 config bw 1000Kbyte/s +pipe 4000 config bw 4000Kbyte/s +table 1 add x.x.x.x 1000 +table 1 add x.x.x.y 4000 +pipe tablearg ip from table(1) to any +</pre> + +<p>A bug has been fixed in which NFS over TCP would not reconnect when the server sent a +FIN. This problem had occurred with Solaris NFS servers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_iface&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_iface</span>(4)</span></a> +Netgraph node now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p> + +<p>The path MTU discovery for multicast packets in the FreeBSD <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6</span>(4)</span></a> stack has +been disabled by default because notifying path MTU by a lot of routers in multicast can +be a kind of distributed Denial-of-Service attack to a router. This feature can be +re-enabled by using a new sysctl variable <code +class="VARNAME">net.inet6.ip6.mcast_pmtu</code>.</p> + +<p>The TCP bandwidth-delay product limiting feature has been disabled when the RTT is +below a certain threshold. This optimization does not make sense on a LAN as it has +trouble figuring out the maximal bandwidth due to the coarse tick granularity. A new +sysctl variable <code class="VARNAME">net.inet.tcp.inflight.rttthresh</code> specifies +the threshold in milliseconds below which this feature will disengage. It defaults to +10ms.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.4 Disks and Storage</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +has been improved on its performance and now supports full 64-bit DMA. While this feature +is enabled by default, this can be forced off by setting the <code +class="VARNAME">hw.amr.force_sg32</code> loader tunable for debugging purpose.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ioctl&sektion=2&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ioctl</span>(2)</span></a> +requests necessary for Linux LSI MegaRaid tools on FreeBSD's Linux emulation +environment.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports a workaround for some controllers whose DMA does not work properly in 48bit +mode. For the suspicious controllers the PIO mode will be used for access to over 137GB +areas.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports the ITE IT8211F IDE controller, and Promise PDC40718 and PDC40719 chip found +in Promise Fasttrak TX4300.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports DMA for kernel crash dump and crash dumping to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +device.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +driver now supports JMicron ATA RAID metadata.</p> + +<p>The <tt class="LITERAL">GEOM_LABEL</tt> class now supports Ext2FS, NTFS, and +ReiserFS.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> class now supports kernel crash dump to the +GEOM providers.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now support sysctl variables <code +class="VARNAME">kern.geom.mirror.disconnect_on_failure</code> and <code +class="VARNAME">kern.geom.graid3.disconnect_on_failure</code> to control whether failed +components will be disconnected or not. The default value is <tt class="LITERAL">1</tt> +to preserve the current behavior, and if it is set to <tt class="LITERAL">0</tt> such +components are not disconnected and the kernel will try to still use them (only first +error will be logged). This is helpful for the case of multiple broken components (in +different places), so actually all data is available. The broken components will be +visible in <tt class="COMMAND">gmirror list</tt> or <tt class="COMMAND">graid3 list</tt> +output with flag <tt class="LITERAL">BROKEN</tt>.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now use parallel I/O request for synchronization to improve the performance. New +sysctl variables <code class="VARNAME">kern.geom.mirror.sync_requests</code> and <code +class="VARNAME">kern.geom.raid3.sync_requests</code> define how many parallel I/O +requests should be used. Also, sysctl variables <code +class="VARNAME">kern.geom.mirror.reqs_per_sync</code>, <code +class="VARNAME">kern.geom.mirror.syncs_per_sec</code>, <code +class="VARNAME">kern.geom.raid3.reqs_per_sync</code>, and <code +class="VARNAME">kern.geom.raid3.syncs_per_sec</code> are deprecated and have been +removed.</p> + +<p>A new GEOM class <tt class="LITERAL">GEOM_ZERO</tt> has been added. It creates very +huge provider (41PB) <tt class="FILENAME">/dev/gzero</tt> and mainly for performance +testing. On <tt class="LITERAL">BIO_READ</tt> request it zero-fills <code +class="VARNAME">bio_data</code> and on <tt class="LITERAL">BIO_WRITE</tt> it does +nothing.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +has been updated to the 9.3.0.1 release on the 3ware Web site.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=geli&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geli</span>(8)</span></a> now +supports loading keyfiles before root file system is mounted. For example, the following +entries can be used in <tt class="FILENAME">/boot/loader.conf</tt> to enable it:</p> + +<pre class="PROGRAMLISTING"> +geli_da0_keyfile0_load="YES" +geli_da0_keyfile0_type="da0:geli_keyfile0" +geli_da0_keyfile0_name="/boot/keys/da0.key0" +geli_da0_keyfile1_load="YES" +geli_da0_keyfile1_type="da0:geli_keyfile1" +geli_da0_keyfile1_name="/boot/keys/da0.key1" +geli_da0_keyfile2_load="YES" +geli_da0_keyfile2_type="da0:geli_keyfile2" +geli_da0_keyfile2_name="/boot/keys/da0.key2" + +geli_da1s3a_keyfile0_load="YES" +geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" +geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" +</pre> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver, +which supports the LSI MegaRAID SAS controller family, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> +driver, which supports HighPoint's RocketRAID 232x series of RAID controllers, has been +added.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="FS" name="FS">2.2.5 File Systems</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN392" name="AEN392">2.2.6 Contributed Software</a></h4> + +<p><b class="APPLICATION">DRM</b> has been updated to a snapshot from DRI CVS as of +20051202.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bsnmpd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bsnmpd</span>(1)</span></a> +utility now supports the Host Resources MIB described in RFC 2790.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now supports the <tt class="LITERAL">nocpu</tt> directive, which cancels the +effect of a previous <tt class="LITERAL">cpu</tt> directive.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now reads <tt class="FILENAME">DEFAULTS</tt> kernel configuration file if it +exists in the current directory before the specified configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=csh&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">csh</span>(1)</span></a> utility +now supports NLS catalog. Note that this requires installing the <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/shells/tcsh_nls/pkg-descr"><tt +class="FILENAME">shells/tcsh_nls</tt></a> port.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> utility +now supports a <code class="OPTION">-f</code> option to specify a configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ln&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ln</span>(1)</span></a> utility now +supports an <code class="OPTION">-F</code> flag which allows to delete existing empty +directories, when creating symbolic links.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=locate&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">locate</span>(1)</span></a> +utility now supports a <code class="OPTION">-0</code> flag to make this utility +interoperable with <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xargs</span>(1)</span></a>'s <code +class="OPTION">-0</code> flag.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ls&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ls</span>(1)</span></a> utility now +supports an <code class="OPTION">-I</code> flag to disable the automatic <code +class="OPTION">-A</code> flag for the superuser.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> utility +now creates a PID file <tt class="FILENAME">/var/run/ftpd.pid</tt> even when no <code +class="OPTION">-p</code> option is specified.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">getfacl</span>(1)</span></a> +utility now supports a <code class="OPTION">-q</code> flag to suppress the per-file +header comment listing the file name, owner, and group.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gvinum&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gvinum</span>(8)</span></a> +utility now supports commands to rename objects and to move a subdisk from one drive to +another.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(8)</span></a> utility +supports a <code class="OPTION">-J <tt class="REPLACEABLE"><i>jid_file</i></tt></code> +option to write out a JidFile, similar to a PidFile, containing the jailid, path, +hostname, IP and the command used to start the jail.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> utility +now supports a <code class="OPTION">-H</code> flag, which causes kdump to print an +additional field holding the threadid.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> program +now supports a <code class="OPTION">-s</code> flag to suppress the display of I/O +data.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mergemaster</span>(8)</span></a> +utility now supports an <code class="OPTION">-A</code> option to explicitly specify an +architecture to pass through to the underlying makefiles.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> daemon +now supports an <code class="OPTION">-H</code> flag to enable horizontal virtual +scrolling similar to a <code class="OPTION">-V</code> flag for vertical virtual +scrolling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=netstat&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">netstat</span>(1)</span></a> +utility now supports printing <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipsec</span>(4)</span></a> +protocol statistics if the kernel was compiled with <tt class="LITERAL">FAST_IPSEC</tt> +rather than the KAME IPSEC stack. Note that the output of <tt class="COMMAND">netstat -s +-p ipsec</tt> differs depending on which stack is compiled into the kernel since they +each keep different statistics.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=periodic&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">periodic</span>(8)</span></a> +daily script now supports display of the status of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gmirror&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gmirror</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=graid3&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">graid3</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gstripe&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gstripe</span>(8)</span></a>, and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gconcat&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gconcat</span>(8)</span></a> +devices. Note that these are disabled by default.</p> + +<p>A new function, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pidfile&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pidfile</span>(3)</span></a>, +which provides reliable pidfiles handling, has been implemented in <tt +class="FILENAME">libutil</tt>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rfcomm_sppd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rfcomm_sppd</span>(1)</span></a> +now supports service name in addition to <code class="OPTION">-c</code> option with +channel number. The supported names are: DUN (Dial-Up Networking), FAX (Fax), LAN (LAN +Access Using PPP), and SP (Serial Port).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snapinfo&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snapinfo</span>(8)</span></a> +utility, which shows snapshot locations on UFS filesystems, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtonum&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtonum</span>(3)</span></a> +library function has been implemented based on OpenBSD's implementation. This is an +improved version of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtoll&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtoll</span>(3)</span></a>.</p> + +<p>A bug in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ypwhich&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ypwhich</span>(1)</span></a> +utility which causes the <code class="OPTION">-m</code> option to produce an incorrect +list of available named maps has been fixed.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="RC-SCRIPTS" name="RC-SCRIPTS">2.3.1 <tt +class="FILENAME">/etc/rc.d</tt> Scripts</a></h4> + +<p>The <tt class="FILENAME">bluetooth</tt> script has been added. This script will be +called from <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> in +response to device attachment/detachment events and to stop/start particular device +without unplugging it by hand. The configuration parameters are in <tt +class="FILENAME">/etc/defaults/bluetooth.device.conf</tt>, and can be overridden by using +<tt class="FILENAME">/etc/bluetooth/<tt class="REPLACEABLE"><i>$device</i></tt>.conf</tt> +(where <tt class="REPLACEABLE"><i>$device</i></tt> is <tt class="DEVICENAME">ubt0</tt>, +<tt class="DEVICENAME">btcc0</tt>, and so on.) For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bluetooth.conf&sektion=5&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span +class="REFENTRYTITLE">bluetooth.conf</span>(5)</span></a>.</p> + +<p>The <tt class="FILENAME">hcsecd</tt> and <tt class="FILENAME">sdpd</tt> scripts have +been added for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hcsecd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hcsecd</span>(8)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sdpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sdpd</span>(8)</span></a> daemons. +These daemons can run even if no Bluetooth devices are attached to the system, but both +daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets +layer must be either loaded as a module or compiled into kernel before the daemons can +run.</p> + +<p>The <tt class="FILENAME">hostapd</tt> script for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hostapd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hostapd</span>(8)</span></a> has +been added.</p> + +<p>The <tt class="FILENAME">jail</tt> script now supports the <code +class="VARNAME">jail_interface</code> option and the <code class="VARNAME">jail_<tt +class="REPLACEABLE"><i>jid</i></tt>_interface</code> option which create an IP alias on +the given interface.</p> + +<p>The <tt class="FILENAME">netif</tt> script now supports <code +class="VARNAME">ipv4_addrs_<tt class="REPLACEABLE"><i>ifn</i></tt></code>, which adds one +or more IPv4 address from a ranged list in CIRD notation. For example:</p> + +<pre class="PROGRAMLISTING"> +ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" +</pre> + +<p>The <tt class="FILENAME">ppp-user</tt> script has been renamed to <tt +class="FILENAME">ppp</tt>.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN580" name="AEN580">2.4 Contributed Software</a></h3> + +<p><b class="APPLICATION">BIND</b> has been updated from 9.3.1 to 9.3.2.</p> + +<p><b class="APPLICATION">hostapd</b> has been updated from version 0.3.9 to version +0.4.8.</p> + +<p><b class="APPLICATION">GNU Troff</b> has been updated from version 1.19 to version +1.19.2.</p> + +<p><b class="APPLICATION">sendmail</b> has been updated from 8.13.4 to 8.13.6.</p> + +<p>The timezone database has been updated from the <b class="APPLICATION">tzdata2005l</b> +release to the <b class="APPLICATION">tzdata2005r</b> release.</p> + +<p><b class="APPLICATION">WPA Supplicant</b> has been updated from version 0.3.9 to +version 0.4.8.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection +Infrastructure</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> +command now supports an <code class="OPTION">-P</code> flag, which is the same as the +<code class="OPTION">-p</code> flag except that the given prefix is also used recursively +for the dependency packages if any.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +utilities now support a <code class="OPTION">-K</code> flag to save packages to the +current directory (or <code class="VARNAME">PKGDIR</code> if defined) by default.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +program now supports an <code class="OPTION">-x</code> flag to support basic regular +expressions for package name, an <code class="OPTION">-E</code> flag for extended regular +expressions, and a <code class="OPTION">-G</code> for exact matching.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_version&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_version</span>(1)</span></a> +utility now supports an <code class="OPTION">-o</code> flag to show the origin recorded +on package generation instead of the package name, and an <code class="OPTION">-O</code> +flag to list packages whose registered origin is origin only.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility (<tt class="FILENAME">sysutils/portsnap</tt>) has been added into the FreeBSD +base system. This is a secure, easy to use, fast, lightweight, and generally good way for +users to keep their ports trees up to date.</p> + +<p>A incorrect handling of <code class="VARNAME">HTTP_PROXY_AUTH</code> in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility has been fixed.</p> + +<p>The startup scripts from the <code class="VARNAME">local_startup</code> directory now +evaluated by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rcorder&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rcorder</span>(8)</span></a> with +scripts in the base system.</p> + +<p>The suffix of startup scripts from the Ports Collection has been removed. This means +<tt class="FILENAME">foo.sh</tt> is renamed to <tt class="FILENAME">foo</tt>, and now +scripts whose name is something like <tt class="FILENAME">foo.ORG</tt> will also be +invoked. You are recommended to reinstall packages which install such scripts and remove +extra files in the <code class="VARNAME">local_startup</code> directory.</p> + +<p>New <tt class="FILENAME">rc.conf</tt> variables, <code +class="VARNAME">ldconfig_local_dirs</code> and <code +class="VARNAME">ldconfig_local32_dirs</code> have been added. These hold lists of local +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ldconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ldconfig</span>(8)</span></a> +directories.</p> + +<p>The <tt class="COMMAND">@cwd</tt> command in <tt class="FILENAME">pkg-plist</tt> now +allows no directory argument. If no directory argument is given, it will set current +working directory to the first prefix given by the <tt class="COMMAND">@cwd</tt> +command.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and +Integration</a></h3> + +<p>The <tt class="FILENAME">/var/audit</tt> directory and <tt class="LITERAL">audit</tt> +group have been added. These are for the TrustedBSD <b class="APPLICATION">OpenBSM</b> +distribution, which will be imported in the future releases.</p> + +<p>The supported version of the <b class="APPLICATION">GNOME</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/gnome2/pkg-descr"><tt +class="FILENAME">x11/gnome2</tt></a>) has been updated from 2.10.2 to 2.12.3.</p> + +<p>The supported version of the <b class="APPLICATION">KDE</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/kde2/pkg-descr"><tt +class="FILENAME">x11/kde2</tt></a>) has been updated from 3.4.2 to 3.5.1.</p> + +<p>The supported version of the <b class="APPLICATION">Perl</b> interpreter (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt +class="FILENAME">lang/perl5.8</tt></a>) has been updated from 5.8.7 to 5.8.8.</p> + +<p>The supported version of the <b class="APPLICATION">Xorg</b> windowing system (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/xorg/pkg-descr"><tt +class="FILENAME">x11/xorg</tt></a>) has been updated from 6.8.2 to 6.9.0.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DOC" name="DOC">2.7 Documentation</a></h3> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of +FreeBSD</a></h2> + +<p>Source upgrades to FreeBSD 6.1-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.1-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.1-RELEASE.</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/relnotes-i386.html b/en/releases/6.1R/relnotes-i386.html new file mode 100644 index 0000000000..ca1456700a --- /dev/null +++ b/en/releases/6.1R/relnotes-i386.html @@ -0,0 +1,1042 @@ +<!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 6.1-RELEASE Release Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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 6.1-RELEASE Release +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The +FreeBSD Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.15.2.7 2006/05/05 17:07:14 hrs Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.</p> + +<p>IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and +Electronics Engineers, Inc. in the United States.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<div> +<div class="ABSTRACT"><a id="AEN24" name="AEN24"></a> +<p>The release notes for FreeBSD 6.1-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.1-STABLE development line. This document lists applicable +security advisories that were issued since the last release, as well as significant +changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also +presented.</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="#BOOT">Boot Loader Changes</a></dt> + +<dt>2.2.2 <a href="#PROC">Hardware Support</a></dt> + +<dt>2.2.3 <a href="#NET-PROTO">Network Protocols</a></dt> + +<dt>2.2.4 <a href="#DISKS">Disks and Storage</a></dt> + +<dt>2.2.5 <a href="#FS">File Systems</a></dt> + +<dt>2.2.6 <a href="#AEN392">Contributed Software</a></dt> +</dl> +</dd> + +<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + +<dd> +<dl> +<dt>2.3.1 <a href="#RC-SCRIPTS"><tt class="FILENAME">/etc/rc.d</tt> Scripts</a></dt> +</dl> +</dd> + +<dt>2.4 <a href="#AEN580">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> + +<dt>2.7 <a href="#DOC">Documentation</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 6.1-RELEASE on the i386 hardware +platform. It describes recently added, changed, or deleted features of FreeBSD. It also +provides some notes on upgrading from previous versions of FreeBSD.</p> + +<p>This distribution of FreeBSD 6.1-RELEASE is a snapshot distribution. It can be found +at <a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</a> or any of its mirrors. More +information on obtaining this (or other) snapshot distributions of FreeBSD can be found +in the <a href="../../../../doc/en_US.ISO8859-1/books/handbook/mirrors.html" +target="_top">“Obtaining FreeBSD” appendix</a> to the <a +href="../../../../doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD +Handbook</a>.</p> + +<p>All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with “late-breaking” information discovered late +in the release cycle or after the release. Typically, it contains information on known +bugs, security advisories, and corrections to documentation. An up-to-date copy of the +errata for FreeBSD 6.1-RELEASE can be found on the FreeBSD Web site.</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 +6.0-RELEASE.</p> + +<p>Typical release note items document recent security advisories issued after +6.0-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3> + +<p>A temporary file vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a>, +which could allow a local attacker to overwrite files in the context of a user running +the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a> +utility, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc" +target="_top">FreeBSD-SA-06:01.texindex</a>.</p> + +<p>A temporary file vulnerability in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> text editor, +which could allow a local attacker to overwrite files in the context of a user running <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a>, has been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc" +target="_top">FreeBSD-SA-06:02.ee</a>.</p> + +<p>Several vulnerabilities in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a> utility +have been corrected. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc" +target="_top">FreeBSD-SA-06:03.cpio</a>.</p> + +<p>An error in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +fragment handling, which could cause a crash, has been fixed. For more details see +security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc" +target="_top">FreeBSD-SA-06:04.ipfw</a>.</p> + +<p>A potential buffer overflow in the IEEE 802.11 scanning code has been corrected. For +more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc" +target="_top">FreeBSD-SA-06:05.80211</a>.</p> + +<p>Two instances in which portions of kernel memory could be disclosed to users have been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc" +target="_top">FreeBSD-SA-06:06.kmem</a>.</p> + +<p>A logic bug in the IP fragment handling in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>, which could +cause a crash under certain circumstances, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc" +target="_top">FreeBSD-SA-06:07.pf</a>.</p> + +<p>A logic bug in the NFS server code, which could cause a crash when the server received +a message with a zero-length payload, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc" +target="_top">FreeBSD-SA-06:10.nfs</a>.</p> + +<p>A programming error in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fast_ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fast_ipsec</span>(4)</span></a> +implementation results in the sequence number associated with a Security Association not +being updated, allowing packets to unconditionally pass sequence number verification +checks, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc" +target="_top">FreeBSD-SA-06:11.ipsec</a>.</p> + +<p>A logic bug that could cause <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=opiepasswd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">opiepasswd</span>(1)</span></a> to +allow an unprivileged user to configure OPIE authentication for the root user under +certain circumstances, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc" +target="_top">FreeBSD-SA-06:12.opie</a>.</p> + +<p>An asynchronous signal handling vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sendmail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sendmail</span>(8)</span></a>, +which could allow a remote attacker to execute arbitrary code with the privileges of the +user running sendmail, typically <tt class="USERNAME">root</tt>, has been fixed. For more +details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc" +target="_top">FreeBSD-SA-06:13.sendmail</a>.</p> + +<p>An information disclosure issue found in the FreeBSD kernel running on 7th- and +8th-generation AMD processors has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:14.fpu.asc" +target="_top">FreeBSD-SA-06:14.fpu</a>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ddb</span>(4)</span></a> debugger +now supports the <tt class="LITERAL">show lock</tt> command. If the argument has a valid +lock class, this displays various information about the lock and calls a new function +pointer in lock_class (lc_ddb_show) to dump class-specific information about the lock as +well (such as the owner of a mutex or xlock'ed sx lock).</p> + +<p><tt class="FILENAME">DEFAULTS</tt> kernel configuration files for each platform have +been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=firmware&sektion=9&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">firmware</span>(9)</span></a> +subsystem has been added. This allows to load binary data into the kernel via a specially +crafted module.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=random&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">random</span>(4)</span></a> +entropy device driver is now MPSAFE.</p> + +<p>A new sysctl variable <code class="VARNAME">security.mac.biba.interfaces_equal</code> +which makes all network interfaces be created with the label <tt +class="LITERAL">biba/equal(equal-equal)</tt>, has been added. This is useful where +programs such as <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dhclient&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dhclient</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppp</span>(8)</span></a>. which +initialize network interfaces do not have any labeling support. This variable is set as +<tt class="LITERAL">0</tt>(disabled) by default.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.1 Boot Loader Changes</a></h4> + +<p>A new loader tunable <code class="VARNAME">comconsole_speed</code> to change the +serial console speed has been added. If the previous stage boot loader requested a serial +console then the default speed is determined from the current serial port speed, and +otherwise it is set to 9600 or the value of the kernel option <tt +class="LITERAL">BOOT_COMCONSOLE_SPEED</tt> at compile time.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="PROC" name="PROC">2.2.2 Hardware Support</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi_thermal&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi_thermal</span>(4)</span></a> +driver now supports passive cooling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ce&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ce</span>(4)</span></a> driver, which +supports Cronyx Tau-PCI/32 adapters, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> driver +has been integrated into <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and +the <tt class="DEVICENAME">kbd</tt> device driver. By default <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> will +look for the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> +keyboard first, and then, if not found, look for any keyboard. Switching to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> can be +done at boot time by loading the <tt class="LITERAL">kbdmux</tt> kernel module via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=loader&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">loader</span>(8)</span></a>, or at +runtime via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kldload&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kldload</span>(8)</span></a> and +releasing the active keyboard.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> driver +has been included in the <tt class="FILENAME">GENERIC</tt> kernel by default. Also, the +“Boot FreeBSD with USB keyboard” menu item in the boot loader menu has been +removed since this fixes USB keyboard probing problems.</p> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="MM" name="MM">2.2.2.1 Multimedia Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=agp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">agp</span>(4)</span></a> driver +now supports ATI IGP chipsets.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sound&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sound</span>(4)</span></a> driver +has been updated in various aspects including fixing lock-related bugs that could cause +system panics in the previous releases and some performance improvements. Also this +driver now supports wider range sampling rate, multiple precisions choice, and 24/32-bit +PCM format conversion.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver has been added. This supports ATI IXP 200/300/400 series audio controllers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_als4000&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_als4000</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via8233&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via8233</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver is now MPSAFE.</p> +</div> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="NET-IF" name="NET-IF">2.2.2.2 Network Interface Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> driver +has been updated to version 0.9.16.16.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bce&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bce</span>(4)</span></a> driver, +which supports Broadcom NetXtreme II (BCM5706/BCM5708) PCI/PCIe Gigabit Ethernet +controllers, has been added. For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bce&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bce</span>(4)</span></a>.</p> + +<p>A bug which prevents the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> driver +from working on a system with over 1GB RAM has been fixed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=polling&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">polling</span>(4)</span></a> +mode.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver now +supports big-endian architectures such as sparc64.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=le&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">le</span>(4)</span></a> driver, which +supports AMD Am7900 LANCE and Am79C9xx PCnet NICs and is based on NetBSD's +implementation, has been added. While the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +also supports these NICs, this driver has several advantages over it such as MPSAFE, +ALTQ, VLAN_MTU, ifmedia, and 32-bit DMA for PCI variants.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver is +now MPSAFE.</p> +</div> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.3 Network Protocols</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> +retransmission algorithm has been rewritten as that ARP requests are retransmitted +without suppression, while there is demand for such ARP entry. Due to this change, a +sysctl variable <code class="VARNAME">net.link.ether.inet.host_down_time</code> has been +removed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now +supports a sysctl variable <code +class="VARNAME">net.link.ether.inet.log_arp_permanent_modify</code> to suppress logging +of attempts to modify permanent ARP entries.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports creating span ports, which transmit a copy of every frame +received by the bridge. This feature can be enabled by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ifconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ifconfig</span>(8)</span></a>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports RFC 3378 EtherIP. This change makes it possible to add <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gif</span>(4)</span></a> +interfaces to bridges, which will then send and receive IP protocol 97 packets. Packets +are Ethernet frames with an EtherIP header prepended.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +packet filter now supports IPv6. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a> packet +filter is deprecated and will be removed in the future releases.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> now +supports substitution of the action argument with the value obtained from table lookup, +which allows some optimization of rulesets. This is now applicable only to <tt +class="LITERAL">pipe</tt>, <tt class="LITERAL">queue</tt>, <tt +class="LITERAL">divert</tt>, <tt class="LITERAL">tee</tt>, <tt +class="LITERAL">netgraph</tt>, and <tt class="LITERAL">ngtee</tt> rules. For example, the +following rules will throw different packets to different pipes:</p> + +<pre class="PROGRAMLISTING"> +pipe 1000 config bw 1000Kbyte/s +pipe 4000 config bw 4000Kbyte/s +table 1 add x.x.x.x 1000 +table 1 add x.x.x.y 4000 +pipe tablearg ip from table(1) to any +</pre> + +<p>A bug has been fixed in which NFS over TCP would not reconnect when the server sent a +FIN. This problem had occurred with Solaris NFS servers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_iface&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_iface</span>(4)</span></a> +Netgraph node now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p> + +<p>The path MTU discovery for multicast packets in the FreeBSD <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6</span>(4)</span></a> stack has +been disabled by default because notifying path MTU by a lot of routers in multicast can +be a kind of distributed Denial-of-Service attack to a router. This feature can be +re-enabled by using a new sysctl variable <code +class="VARNAME">net.inet6.ip6.mcast_pmtu</code>.</p> + +<p>The TCP bandwidth-delay product limiting feature has been disabled when the RTT is +below a certain threshold. This optimization does not make sense on a LAN as it has +trouble figuring out the maximal bandwidth due to the coarse tick granularity. A new +sysctl variable <code class="VARNAME">net.inet.tcp.inflight.rttthresh</code> specifies +the threshold in milliseconds below which this feature will disengage. It defaults to +10ms.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.4 Disks and Storage</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +has been improved on its performance and now supports full 64-bit DMA. While this feature +is enabled by default, this can be forced off by setting the <code +class="VARNAME">hw.amr.force_sg32</code> loader tunable for debugging purpose.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ioctl&sektion=2&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ioctl</span>(2)</span></a> +requests necessary for Linux LSI MegaRaid tools on FreeBSD's Linux emulation +environment.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports a workaround for some controllers whose DMA does not work properly in 48bit +mode. For the suspicious controllers the PIO mode will be used for access to over 137GB +areas.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports the ITE IT8211F IDE controller, and Promise PDC40718 and PDC40719 chip found +in Promise Fasttrak TX4300.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports DMA for kernel crash dump and crash dumping to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +device.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +driver now supports JMicron ATA RAID metadata.</p> + +<p>The <tt class="LITERAL">GEOM_LABEL</tt> class now supports Ext2FS, NTFS, and +ReiserFS.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> class now supports kernel crash dump to the +GEOM providers.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now support sysctl variables <code +class="VARNAME">kern.geom.mirror.disconnect_on_failure</code> and <code +class="VARNAME">kern.geom.graid3.disconnect_on_failure</code> to control whether failed +components will be disconnected or not. The default value is <tt class="LITERAL">1</tt> +to preserve the current behavior, and if it is set to <tt class="LITERAL">0</tt> such +components are not disconnected and the kernel will try to still use them (only first +error will be logged). This is helpful for the case of multiple broken components (in +different places), so actually all data is available. The broken components will be +visible in <tt class="COMMAND">gmirror list</tt> or <tt class="COMMAND">graid3 list</tt> +output with flag <tt class="LITERAL">BROKEN</tt>.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now use parallel I/O request for synchronization to improve the performance. New +sysctl variables <code class="VARNAME">kern.geom.mirror.sync_requests</code> and <code +class="VARNAME">kern.geom.raid3.sync_requests</code> define how many parallel I/O +requests should be used. Also, sysctl variables <code +class="VARNAME">kern.geom.mirror.reqs_per_sync</code>, <code +class="VARNAME">kern.geom.mirror.syncs_per_sec</code>, <code +class="VARNAME">kern.geom.raid3.reqs_per_sync</code>, and <code +class="VARNAME">kern.geom.raid3.syncs_per_sec</code> are deprecated and have been +removed.</p> + +<p>A new GEOM class <tt class="LITERAL">GEOM_ZERO</tt> has been added. It creates very +huge provider (41PB) <tt class="FILENAME">/dev/gzero</tt> and mainly for performance +testing. On <tt class="LITERAL">BIO_READ</tt> request it zero-fills <code +class="VARNAME">bio_data</code> and on <tt class="LITERAL">BIO_WRITE</tt> it does +nothing.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +has been updated to the 9.3.0.1 release on the 3ware Web site.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=geli&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geli</span>(8)</span></a> now +supports loading keyfiles before root file system is mounted. For example, the following +entries can be used in <tt class="FILENAME">/boot/loader.conf</tt> to enable it:</p> + +<pre class="PROGRAMLISTING"> +geli_da0_keyfile0_load="YES" +geli_da0_keyfile0_type="da0:geli_keyfile0" +geli_da0_keyfile0_name="/boot/keys/da0.key0" +geli_da0_keyfile1_load="YES" +geli_da0_keyfile1_type="da0:geli_keyfile1" +geli_da0_keyfile1_name="/boot/keys/da0.key1" +geli_da0_keyfile2_load="YES" +geli_da0_keyfile2_type="da0:geli_keyfile2" +geli_da0_keyfile2_name="/boot/keys/da0.key2" + +geli_da1s3a_keyfile0_load="YES" +geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" +geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" +</pre> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver, +which supports the LSI MegaRAID SAS controller family, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> +driver, which supports HighPoint's RocketRAID 232x series of RAID controllers, has been +added.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="FS" name="FS">2.2.5 File Systems</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN392" name="AEN392">2.2.6 Contributed Software</a></h4> + +<p><b class="APPLICATION">DRM</b> has been updated to a snapshot from DRI CVS as of +20051202.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bsnmpd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bsnmpd</span>(1)</span></a> +utility now supports the Host Resources MIB described in RFC 2790.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now supports the <tt class="LITERAL">nocpu</tt> directive, which cancels the +effect of a previous <tt class="LITERAL">cpu</tt> directive.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now reads <tt class="FILENAME">DEFAULTS</tt> kernel configuration file if it +exists in the current directory before the specified configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=csh&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">csh</span>(1)</span></a> utility +now supports NLS catalog. Note that this requires installing the <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/shells/tcsh_nls/pkg-descr"><tt +class="FILENAME">shells/tcsh_nls</tt></a> port.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> utility +now supports a <code class="OPTION">-f</code> option to specify a configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ln&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ln</span>(1)</span></a> utility now +supports an <code class="OPTION">-F</code> flag which allows to delete existing empty +directories, when creating symbolic links.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=locate&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">locate</span>(1)</span></a> +utility now supports a <code class="OPTION">-0</code> flag to make this utility +interoperable with <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xargs</span>(1)</span></a>'s <code +class="OPTION">-0</code> flag.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ls&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ls</span>(1)</span></a> utility now +supports an <code class="OPTION">-I</code> flag to disable the automatic <code +class="OPTION">-A</code> flag for the superuser.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> utility +now creates a PID file <tt class="FILENAME">/var/run/ftpd.pid</tt> even when no <code +class="OPTION">-p</code> option is specified.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">getfacl</span>(1)</span></a> +utility now supports a <code class="OPTION">-q</code> flag to suppress the per-file +header comment listing the file name, owner, and group.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gvinum&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gvinum</span>(8)</span></a> +utility now supports commands to rename objects and to move a subdisk from one drive to +another.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(8)</span></a> utility +supports a <code class="OPTION">-J <tt class="REPLACEABLE"><i>jid_file</i></tt></code> +option to write out a JidFile, similar to a PidFile, containing the jailid, path, +hostname, IP and the command used to start the jail.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> utility +now supports a <code class="OPTION">-H</code> flag, which causes kdump to print an +additional field holding the threadid.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> program +now supports a <code class="OPTION">-s</code> flag to suppress the display of I/O +data.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mergemaster</span>(8)</span></a> +utility now supports an <code class="OPTION">-A</code> option to explicitly specify an +architecture to pass through to the underlying makefiles.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> daemon +now supports an <code class="OPTION">-H</code> flag to enable horizontal virtual +scrolling similar to a <code class="OPTION">-V</code> flag for vertical virtual +scrolling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=netstat&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">netstat</span>(1)</span></a> +utility now supports printing <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipsec</span>(4)</span></a> +protocol statistics if the kernel was compiled with <tt class="LITERAL">FAST_IPSEC</tt> +rather than the KAME IPSEC stack. Note that the output of <tt class="COMMAND">netstat -s +-p ipsec</tt> differs depending on which stack is compiled into the kernel since they +each keep different statistics.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=periodic&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">periodic</span>(8)</span></a> +daily script now supports display of the status of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gmirror&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gmirror</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=graid3&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">graid3</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gstripe&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gstripe</span>(8)</span></a>, and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gconcat&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gconcat</span>(8)</span></a> +devices. Note that these are disabled by default.</p> + +<p>A new function, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pidfile&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pidfile</span>(3)</span></a>, +which provides reliable pidfiles handling, has been implemented in <tt +class="FILENAME">libutil</tt>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rfcomm_sppd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rfcomm_sppd</span>(1)</span></a> +now supports service name in addition to <code class="OPTION">-c</code> option with +channel number. The supported names are: DUN (Dial-Up Networking), FAX (Fax), LAN (LAN +Access Using PPP), and SP (Serial Port).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snapinfo&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snapinfo</span>(8)</span></a> +utility, which shows snapshot locations on UFS filesystems, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtonum&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtonum</span>(3)</span></a> +library function has been implemented based on OpenBSD's implementation. This is an +improved version of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtoll&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtoll</span>(3)</span></a>.</p> + +<p>A bug in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ypwhich&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ypwhich</span>(1)</span></a> +utility which causes the <code class="OPTION">-m</code> option to produce an incorrect +list of available named maps has been fixed.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="RC-SCRIPTS" name="RC-SCRIPTS">2.3.1 <tt +class="FILENAME">/etc/rc.d</tt> Scripts</a></h4> + +<p>The <tt class="FILENAME">bluetooth</tt> script has been added. This script will be +called from <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> in +response to device attachment/detachment events and to stop/start particular device +without unplugging it by hand. The configuration parameters are in <tt +class="FILENAME">/etc/defaults/bluetooth.device.conf</tt>, and can be overridden by using +<tt class="FILENAME">/etc/bluetooth/<tt class="REPLACEABLE"><i>$device</i></tt>.conf</tt> +(where <tt class="REPLACEABLE"><i>$device</i></tt> is <tt class="DEVICENAME">ubt0</tt>, +<tt class="DEVICENAME">btcc0</tt>, and so on.) For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bluetooth.conf&sektion=5&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span +class="REFENTRYTITLE">bluetooth.conf</span>(5)</span></a>.</p> + +<p>The <tt class="FILENAME">hcsecd</tt> and <tt class="FILENAME">sdpd</tt> scripts have +been added for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hcsecd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hcsecd</span>(8)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sdpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sdpd</span>(8)</span></a> daemons. +These daemons can run even if no Bluetooth devices are attached to the system, but both +daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets +layer must be either loaded as a module or compiled into kernel before the daemons can +run.</p> + +<p>The <tt class="FILENAME">hostapd</tt> script for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hostapd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hostapd</span>(8)</span></a> has +been added.</p> + +<p>The <tt class="FILENAME">jail</tt> script now supports the <code +class="VARNAME">jail_interface</code> option and the <code class="VARNAME">jail_<tt +class="REPLACEABLE"><i>jid</i></tt>_interface</code> option which create an IP alias on +the given interface.</p> + +<p>The <tt class="FILENAME">netif</tt> script now supports <code +class="VARNAME">ipv4_addrs_<tt class="REPLACEABLE"><i>ifn</i></tt></code>, which adds one +or more IPv4 address from a ranged list in CIRD notation. For example:</p> + +<pre class="PROGRAMLISTING"> +ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" +</pre> + +<p>The <tt class="FILENAME">ppp-user</tt> script has been renamed to <tt +class="FILENAME">ppp</tt>.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN580" name="AEN580">2.4 Contributed Software</a></h3> + +<p><b class="APPLICATION">BIND</b> has been updated from 9.3.1 to 9.3.2.</p> + +<p><b class="APPLICATION">hostapd</b> has been updated from version 0.3.9 to version +0.4.8.</p> + +<p><b class="APPLICATION">GNU Troff</b> has been updated from version 1.19 to version +1.19.2.</p> + +<p><b class="APPLICATION">sendmail</b> has been updated from 8.13.4 to 8.13.6.</p> + +<p>The timezone database has been updated from the <b class="APPLICATION">tzdata2005l</b> +release to the <b class="APPLICATION">tzdata2005r</b> release.</p> + +<p><b class="APPLICATION">WPA Supplicant</b> has been updated from version 0.3.9 to +version 0.4.8.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection +Infrastructure</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> +command now supports an <code class="OPTION">-P</code> flag, which is the same as the +<code class="OPTION">-p</code> flag except that the given prefix is also used recursively +for the dependency packages if any.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +utilities now support a <code class="OPTION">-K</code> flag to save packages to the +current directory (or <code class="VARNAME">PKGDIR</code> if defined) by default.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +program now supports an <code class="OPTION">-x</code> flag to support basic regular +expressions for package name, an <code class="OPTION">-E</code> flag for extended regular +expressions, and a <code class="OPTION">-G</code> for exact matching.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_version&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_version</span>(1)</span></a> +utility now supports an <code class="OPTION">-o</code> flag to show the origin recorded +on package generation instead of the package name, and an <code class="OPTION">-O</code> +flag to list packages whose registered origin is origin only.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility (<tt class="FILENAME">sysutils/portsnap</tt>) has been added into the FreeBSD +base system. This is a secure, easy to use, fast, lightweight, and generally good way for +users to keep their ports trees up to date.</p> + +<p>A incorrect handling of <code class="VARNAME">HTTP_PROXY_AUTH</code> in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility has been fixed.</p> + +<p>The startup scripts from the <code class="VARNAME">local_startup</code> directory now +evaluated by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rcorder&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rcorder</span>(8)</span></a> with +scripts in the base system.</p> + +<p>The suffix of startup scripts from the Ports Collection has been removed. This means +<tt class="FILENAME">foo.sh</tt> is renamed to <tt class="FILENAME">foo</tt>, and now +scripts whose name is something like <tt class="FILENAME">foo.ORG</tt> will also be +invoked. You are recommended to reinstall packages which install such scripts and remove +extra files in the <code class="VARNAME">local_startup</code> directory.</p> + +<p>New <tt class="FILENAME">rc.conf</tt> variables, <code +class="VARNAME">ldconfig_local_dirs</code> and <code +class="VARNAME">ldconfig_local32_dirs</code> have been added. These hold lists of local +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ldconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ldconfig</span>(8)</span></a> +directories.</p> + +<p>The <tt class="COMMAND">@cwd</tt> command in <tt class="FILENAME">pkg-plist</tt> now +allows no directory argument. If no directory argument is given, it will set current +working directory to the first prefix given by the <tt class="COMMAND">@cwd</tt> +command.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and +Integration</a></h3> + +<p>The <tt class="FILENAME">/var/audit</tt> directory and <tt class="LITERAL">audit</tt> +group have been added. These are for the TrustedBSD <b class="APPLICATION">OpenBSM</b> +distribution, which will be imported in the future releases.</p> + +<p>The supported version of the <b class="APPLICATION">GNOME</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/gnome2/pkg-descr"><tt +class="FILENAME">x11/gnome2</tt></a>) has been updated from 2.10.2 to 2.12.3.</p> + +<p>The supported version of the <b class="APPLICATION">KDE</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/kde2/pkg-descr"><tt +class="FILENAME">x11/kde2</tt></a>) has been updated from 3.4.2 to 3.5.1.</p> + +<p>The supported version of the <b class="APPLICATION">Perl</b> interpreter (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt +class="FILENAME">lang/perl5.8</tt></a>) has been updated from 5.8.7 to 5.8.8.</p> + +<p>The supported version of the <b class="APPLICATION">Xorg</b> windowing system (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/xorg/pkg-descr"><tt +class="FILENAME">x11/xorg</tt></a>) has been updated from 6.8.2 to 6.9.0.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DOC" name="DOC">2.7 Documentation</a></h3> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of +FreeBSD</a></h2> + +<p>Source upgrades to FreeBSD 6.1-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.1-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.1-RELEASE.</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/relnotes-ia64.html b/en/releases/6.1R/relnotes-ia64.html new file mode 100644 index 0000000000..3bb93b748c --- /dev/null +++ b/en/releases/6.1R/relnotes-ia64.html @@ -0,0 +1,1011 @@ +<!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/ia64 6.1-RELEASE Release Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/ia64 6.1-RELEASE Release +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The +FreeBSD Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.15.2.7 2006/05/05 17:07:14 hrs Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.</p> + +<p>IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and +Electronics Engineers, Inc. in the United States.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<div> +<div class="ABSTRACT"><a id="AEN24" name="AEN24"></a> +<p>The release notes for FreeBSD 6.1-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.1-STABLE development line. This document lists applicable +security advisories that were issued since the last release, as well as significant +changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also +presented.</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="#BOOT">Boot Loader Changes</a></dt> + +<dt>2.2.2 <a href="#PROC">Hardware Support</a></dt> + +<dt>2.2.3 <a href="#NET-PROTO">Network Protocols</a></dt> + +<dt>2.2.4 <a href="#DISKS">Disks and Storage</a></dt> + +<dt>2.2.5 <a href="#FS">File Systems</a></dt> + +<dt>2.2.6 <a href="#AEN392">Contributed Software</a></dt> +</dl> +</dd> + +<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + +<dd> +<dl> +<dt>2.3.1 <a href="#RC-SCRIPTS"><tt class="FILENAME">/etc/rc.d</tt> Scripts</a></dt> +</dl> +</dd> + +<dt>2.4 <a href="#AEN580">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> + +<dt>2.7 <a href="#DOC">Documentation</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 6.1-RELEASE on the IA-64 hardware +platform. It describes recently added, changed, or deleted features of FreeBSD. It also +provides some notes on upgrading from previous versions of FreeBSD.</p> + +<p>This distribution of FreeBSD 6.1-RELEASE is a snapshot distribution. It can be found +at <a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</a> or any of its mirrors. More +information on obtaining this (or other) snapshot 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” appendix</a> to the <a +href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD +Handbook</a>.</p> + +<p>All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with “late-breaking” information discovered late +in the release cycle or after the release. Typically, it contains information on known +bugs, security advisories, and corrections to documentation. An up-to-date copy of the +errata for FreeBSD 6.1-RELEASE can be found on the FreeBSD Web site.</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 +6.0-RELEASE.</p> + +<p>Typical release note items document recent security advisories issued after +6.0-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3> + +<p>A temporary file vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a>, +which could allow a local attacker to overwrite files in the context of a user running +the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a> +utility, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc" +target="_top">FreeBSD-SA-06:01.texindex</a>.</p> + +<p>A temporary file vulnerability in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> text editor, +which could allow a local attacker to overwrite files in the context of a user running <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a>, has been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc" +target="_top">FreeBSD-SA-06:02.ee</a>.</p> + +<p>Several vulnerabilities in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a> utility +have been corrected. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc" +target="_top">FreeBSD-SA-06:03.cpio</a>.</p> + +<p>An error in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +fragment handling, which could cause a crash, has been fixed. For more details see +security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc" +target="_top">FreeBSD-SA-06:04.ipfw</a>.</p> + +<p>A potential buffer overflow in the IEEE 802.11 scanning code has been corrected. For +more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc" +target="_top">FreeBSD-SA-06:05.80211</a>.</p> + +<p>Two instances in which portions of kernel memory could be disclosed to users have been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc" +target="_top">FreeBSD-SA-06:06.kmem</a>.</p> + +<p>A logic bug in the IP fragment handling in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>, which could +cause a crash under certain circumstances, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc" +target="_top">FreeBSD-SA-06:07.pf</a>.</p> + +<p>A logic bug in the NFS server code, which could cause a crash when the server received +a message with a zero-length payload, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc" +target="_top">FreeBSD-SA-06:10.nfs</a>.</p> + +<p>A programming error in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fast_ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fast_ipsec</span>(4)</span></a> +implementation results in the sequence number associated with a Security Association not +being updated, allowing packets to unconditionally pass sequence number verification +checks, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc" +target="_top">FreeBSD-SA-06:11.ipsec</a>.</p> + +<p>A logic bug that could cause <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=opiepasswd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">opiepasswd</span>(1)</span></a> to +allow an unprivileged user to configure OPIE authentication for the root user under +certain circumstances, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc" +target="_top">FreeBSD-SA-06:12.opie</a>.</p> + +<p>An asynchronous signal handling vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sendmail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sendmail</span>(8)</span></a>, +which could allow a remote attacker to execute arbitrary code with the privileges of the +user running sendmail, typically <tt class="USERNAME">root</tt>, has been fixed. For more +details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc" +target="_top">FreeBSD-SA-06:13.sendmail</a>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ddb</span>(4)</span></a> debugger +now supports the <tt class="LITERAL">show lock</tt> command. If the argument has a valid +lock class, this displays various information about the lock and calls a new function +pointer in lock_class (lc_ddb_show) to dump class-specific information about the lock as +well (such as the owner of a mutex or xlock'ed sx lock).</p> + +<p><tt class="FILENAME">DEFAULTS</tt> kernel configuration files for each platform have +been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=firmware&sektion=9&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">firmware</span>(9)</span></a> +subsystem has been added. This allows to load binary data into the kernel via a specially +crafted module.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=random&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">random</span>(4)</span></a> +entropy device driver is now MPSAFE.</p> + +<p>A new sysctl variable <code class="VARNAME">security.mac.biba.interfaces_equal</code> +which makes all network interfaces be created with the label <tt +class="LITERAL">biba/equal(equal-equal)</tt>, has been added. This is useful where +programs such as <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dhclient&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dhclient</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppp</span>(8)</span></a>. which +initialize network interfaces do not have any labeling support. This variable is set as +<tt class="LITERAL">0</tt>(disabled) by default.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.1 Boot Loader Changes</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="PROC" name="PROC">2.2.2 Hardware Support</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi_thermal&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi_thermal</span>(4)</span></a> +driver now supports passive cooling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> driver +has been integrated into <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and +the <tt class="DEVICENAME">kbd</tt> device driver. By default <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> will +look for the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> +keyboard first, and then, if not found, look for any keyboard. Switching to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> can be +done at boot time by loading the <tt class="LITERAL">kbdmux</tt> kernel module via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=loader&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">loader</span>(8)</span></a>, or at +runtime via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kldload&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kldload</span>(8)</span></a> and +releasing the active keyboard.</p> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="MM" name="MM">2.2.2.1 Multimedia Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=agp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">agp</span>(4)</span></a> driver +now supports ATI IGP chipsets.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sound&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sound</span>(4)</span></a> driver +has been updated in various aspects including fixing lock-related bugs that could cause +system panics in the previous releases and some performance improvements. Also this +driver now supports wider range sampling rate, multiple precisions choice, and 24/32-bit +PCM format conversion.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver has been added. This supports ATI IXP 200/300/400 series audio controllers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_als4000&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_als4000</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via8233&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via8233</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver is now MPSAFE.</p> +</div> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="NET-IF" name="NET-IF">2.2.2.2 Network Interface Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> driver +has been updated to version 0.9.16.16.</p> + +<p>A bug which prevents the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> driver +from working on a system with over 1GB RAM has been fixed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=polling&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">polling</span>(4)</span></a> +mode.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver now +supports big-endian architectures such as sparc64.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=le&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">le</span>(4)</span></a> driver, which +supports AMD Am7900 LANCE and Am79C9xx PCnet NICs and is based on NetBSD's +implementation, has been added. While the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +also supports these NICs, this driver has several advantages over it such as MPSAFE, +ALTQ, VLAN_MTU, ifmedia, and 32-bit DMA for PCI variants.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver is +now MPSAFE.</p> +</div> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.3 Network Protocols</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> +retransmission algorithm has been rewritten as that ARP requests are retransmitted +without suppression, while there is demand for such ARP entry. Due to this change, a +sysctl variable <code class="VARNAME">net.link.ether.inet.host_down_time</code> has been +removed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now +supports a sysctl variable <code +class="VARNAME">net.link.ether.inet.log_arp_permanent_modify</code> to suppress logging +of attempts to modify permanent ARP entries.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports creating span ports, which transmit a copy of every frame +received by the bridge. This feature can be enabled by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ifconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ifconfig</span>(8)</span></a>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports RFC 3378 EtherIP. This change makes it possible to add <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gif</span>(4)</span></a> +interfaces to bridges, which will then send and receive IP protocol 97 packets. Packets +are Ethernet frames with an EtherIP header prepended.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +packet filter now supports IPv6. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a> packet +filter is deprecated and will be removed in the future releases.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> now +supports substitution of the action argument with the value obtained from table lookup, +which allows some optimization of rulesets. This is now applicable only to <tt +class="LITERAL">pipe</tt>, <tt class="LITERAL">queue</tt>, <tt +class="LITERAL">divert</tt>, <tt class="LITERAL">tee</tt>, <tt +class="LITERAL">netgraph</tt>, and <tt class="LITERAL">ngtee</tt> rules. For example, the +following rules will throw different packets to different pipes:</p> + +<pre class="PROGRAMLISTING"> +pipe 1000 config bw 1000Kbyte/s +pipe 4000 config bw 4000Kbyte/s +table 1 add x.x.x.x 1000 +table 1 add x.x.x.y 4000 +pipe tablearg ip from table(1) to any +</pre> + +<p>A bug has been fixed in which NFS over TCP would not reconnect when the server sent a +FIN. This problem had occurred with Solaris NFS servers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_iface&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_iface</span>(4)</span></a> +Netgraph node now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p> + +<p>The path MTU discovery for multicast packets in the FreeBSD <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6</span>(4)</span></a> stack has +been disabled by default because notifying path MTU by a lot of routers in multicast can +be a kind of distributed Denial-of-Service attack to a router. This feature can be +re-enabled by using a new sysctl variable <code +class="VARNAME">net.inet6.ip6.mcast_pmtu</code>.</p> + +<p>The TCP bandwidth-delay product limiting feature has been disabled when the RTT is +below a certain threshold. This optimization does not make sense on a LAN as it has +trouble figuring out the maximal bandwidth due to the coarse tick granularity. A new +sysctl variable <code class="VARNAME">net.inet.tcp.inflight.rttthresh</code> specifies +the threshold in milliseconds below which this feature will disengage. It defaults to +10ms.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.4 Disks and Storage</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +has been improved on its performance and now supports full 64-bit DMA. While this feature +is enabled by default, this can be forced off by setting the <code +class="VARNAME">hw.amr.force_sg32</code> loader tunable for debugging purpose.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ioctl&sektion=2&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ioctl</span>(2)</span></a> +requests necessary for Linux LSI MegaRaid tools on FreeBSD's Linux emulation +environment.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports a workaround for some controllers whose DMA does not work properly in 48bit +mode. For the suspicious controllers the PIO mode will be used for access to over 137GB +areas.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports the ITE IT8211F IDE controller, and Promise PDC40718 and PDC40719 chip found +in Promise Fasttrak TX4300.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports DMA for kernel crash dump and crash dumping to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +device.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +driver now supports JMicron ATA RAID metadata.</p> + +<p>The <tt class="LITERAL">GEOM_LABEL</tt> class now supports Ext2FS, NTFS, and +ReiserFS.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> class now supports kernel crash dump to the +GEOM providers.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now support sysctl variables <code +class="VARNAME">kern.geom.mirror.disconnect_on_failure</code> and <code +class="VARNAME">kern.geom.graid3.disconnect_on_failure</code> to control whether failed +components will be disconnected or not. The default value is <tt class="LITERAL">1</tt> +to preserve the current behavior, and if it is set to <tt class="LITERAL">0</tt> such +components are not disconnected and the kernel will try to still use them (only first +error will be logged). This is helpful for the case of multiple broken components (in +different places), so actually all data is available. The broken components will be +visible in <tt class="COMMAND">gmirror list</tt> or <tt class="COMMAND">graid3 list</tt> +output with flag <tt class="LITERAL">BROKEN</tt>.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now use parallel I/O request for synchronization to improve the performance. New +sysctl variables <code class="VARNAME">kern.geom.mirror.sync_requests</code> and <code +class="VARNAME">kern.geom.raid3.sync_requests</code> define how many parallel I/O +requests should be used. Also, sysctl variables <code +class="VARNAME">kern.geom.mirror.reqs_per_sync</code>, <code +class="VARNAME">kern.geom.mirror.syncs_per_sec</code>, <code +class="VARNAME">kern.geom.raid3.reqs_per_sync</code>, and <code +class="VARNAME">kern.geom.raid3.syncs_per_sec</code> are deprecated and have been +removed.</p> + +<p>A new GEOM class <tt class="LITERAL">GEOM_ZERO</tt> has been added. It creates very +huge provider (41PB) <tt class="FILENAME">/dev/gzero</tt> and mainly for performance +testing. On <tt class="LITERAL">BIO_READ</tt> request it zero-fills <code +class="VARNAME">bio_data</code> and on <tt class="LITERAL">BIO_WRITE</tt> it does +nothing.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +has been updated to the 9.3.0.1 release on the 3ware Web site.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=geli&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geli</span>(8)</span></a> now +supports loading keyfiles before root file system is mounted. For example, the following +entries can be used in <tt class="FILENAME">/boot/loader.conf</tt> to enable it:</p> + +<pre class="PROGRAMLISTING"> +geli_da0_keyfile0_load="YES" +geli_da0_keyfile0_type="da0:geli_keyfile0" +geli_da0_keyfile0_name="/boot/keys/da0.key0" +geli_da0_keyfile1_load="YES" +geli_da0_keyfile1_type="da0:geli_keyfile1" +geli_da0_keyfile1_name="/boot/keys/da0.key1" +geli_da0_keyfile2_load="YES" +geli_da0_keyfile2_type="da0:geli_keyfile2" +geli_da0_keyfile2_name="/boot/keys/da0.key2" + +geli_da1s3a_keyfile0_load="YES" +geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" +geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" +</pre> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver, +which supports the LSI MegaRAID SAS controller family, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> +driver, which supports HighPoint's RocketRAID 232x series of RAID controllers, has been +added.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="FS" name="FS">2.2.5 File Systems</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN392" name="AEN392">2.2.6 Contributed Software</a></h4> + +<p><b class="APPLICATION">DRM</b> has been updated to a snapshot from DRI CVS as of +20051202.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bsnmpd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bsnmpd</span>(1)</span></a> +utility now supports the Host Resources MIB described in RFC 2790.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now supports the <tt class="LITERAL">nocpu</tt> directive, which cancels the +effect of a previous <tt class="LITERAL">cpu</tt> directive.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now reads <tt class="FILENAME">DEFAULTS</tt> kernel configuration file if it +exists in the current directory before the specified configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=csh&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">csh</span>(1)</span></a> utility +now supports NLS catalog. Note that this requires installing the <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/shells/tcsh_nls/pkg-descr"><tt +class="FILENAME">shells/tcsh_nls</tt></a> port.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> utility +now supports a <code class="OPTION">-f</code> option to specify a configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ln&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ln</span>(1)</span></a> utility now +supports an <code class="OPTION">-F</code> flag which allows to delete existing empty +directories, when creating symbolic links.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=locate&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">locate</span>(1)</span></a> +utility now supports a <code class="OPTION">-0</code> flag to make this utility +interoperable with <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xargs</span>(1)</span></a>'s <code +class="OPTION">-0</code> flag.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ls&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ls</span>(1)</span></a> utility now +supports an <code class="OPTION">-I</code> flag to disable the automatic <code +class="OPTION">-A</code> flag for the superuser.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> utility +now creates a PID file <tt class="FILENAME">/var/run/ftpd.pid</tt> even when no <code +class="OPTION">-p</code> option is specified.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">getfacl</span>(1)</span></a> +utility now supports a <code class="OPTION">-q</code> flag to suppress the per-file +header comment listing the file name, owner, and group.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gvinum&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gvinum</span>(8)</span></a> +utility now supports commands to rename objects and to move a subdisk from one drive to +another.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(8)</span></a> utility +supports a <code class="OPTION">-J <tt class="REPLACEABLE"><i>jid_file</i></tt></code> +option to write out a JidFile, similar to a PidFile, containing the jailid, path, +hostname, IP and the command used to start the jail.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> utility +now supports a <code class="OPTION">-H</code> flag, which causes kdump to print an +additional field holding the threadid.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> program +now supports a <code class="OPTION">-s</code> flag to suppress the display of I/O +data.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mergemaster</span>(8)</span></a> +utility now supports an <code class="OPTION">-A</code> option to explicitly specify an +architecture to pass through to the underlying makefiles.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> daemon +now supports an <code class="OPTION">-H</code> flag to enable horizontal virtual +scrolling similar to a <code class="OPTION">-V</code> flag for vertical virtual +scrolling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=netstat&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">netstat</span>(1)</span></a> +utility now supports printing <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipsec</span>(4)</span></a> +protocol statistics if the kernel was compiled with <tt class="LITERAL">FAST_IPSEC</tt> +rather than the KAME IPSEC stack. Note that the output of <tt class="COMMAND">netstat -s +-p ipsec</tt> differs depending on which stack is compiled into the kernel since they +each keep different statistics.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=periodic&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">periodic</span>(8)</span></a> +daily script now supports display of the status of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gmirror&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gmirror</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=graid3&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">graid3</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gstripe&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gstripe</span>(8)</span></a>, and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gconcat&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gconcat</span>(8)</span></a> +devices. Note that these are disabled by default.</p> + +<p>A new function, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pidfile&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pidfile</span>(3)</span></a>, +which provides reliable pidfiles handling, has been implemented in <tt +class="FILENAME">libutil</tt>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rfcomm_sppd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rfcomm_sppd</span>(1)</span></a> +now supports service name in addition to <code class="OPTION">-c</code> option with +channel number. The supported names are: DUN (Dial-Up Networking), FAX (Fax), LAN (LAN +Access Using PPP), and SP (Serial Port).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snapinfo&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snapinfo</span>(8)</span></a> +utility, which shows snapshot locations on UFS filesystems, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtonum&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtonum</span>(3)</span></a> +library function has been implemented based on OpenBSD's implementation. This is an +improved version of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtoll&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtoll</span>(3)</span></a>.</p> + +<p>A bug in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ypwhich&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ypwhich</span>(1)</span></a> +utility which causes the <code class="OPTION">-m</code> option to produce an incorrect +list of available named maps has been fixed.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="RC-SCRIPTS" name="RC-SCRIPTS">2.3.1 <tt +class="FILENAME">/etc/rc.d</tt> Scripts</a></h4> + +<p>The <tt class="FILENAME">bluetooth</tt> script has been added. This script will be +called from <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> in +response to device attachment/detachment events and to stop/start particular device +without unplugging it by hand. The configuration parameters are in <tt +class="FILENAME">/etc/defaults/bluetooth.device.conf</tt>, and can be overridden by using +<tt class="FILENAME">/etc/bluetooth/<tt class="REPLACEABLE"><i>$device</i></tt>.conf</tt> +(where <tt class="REPLACEABLE"><i>$device</i></tt> is <tt class="DEVICENAME">ubt0</tt>, +<tt class="DEVICENAME">btcc0</tt>, and so on.) For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bluetooth.conf&sektion=5&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span +class="REFENTRYTITLE">bluetooth.conf</span>(5)</span></a>.</p> + +<p>The <tt class="FILENAME">hcsecd</tt> and <tt class="FILENAME">sdpd</tt> scripts have +been added for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hcsecd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hcsecd</span>(8)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sdpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sdpd</span>(8)</span></a> daemons. +These daemons can run even if no Bluetooth devices are attached to the system, but both +daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets +layer must be either loaded as a module or compiled into kernel before the daemons can +run.</p> + +<p>The <tt class="FILENAME">hostapd</tt> script for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hostapd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hostapd</span>(8)</span></a> has +been added.</p> + +<p>The <tt class="FILENAME">jail</tt> script now supports the <code +class="VARNAME">jail_interface</code> option and the <code class="VARNAME">jail_<tt +class="REPLACEABLE"><i>jid</i></tt>_interface</code> option which create an IP alias on +the given interface.</p> + +<p>The <tt class="FILENAME">netif</tt> script now supports <code +class="VARNAME">ipv4_addrs_<tt class="REPLACEABLE"><i>ifn</i></tt></code>, which adds one +or more IPv4 address from a ranged list in CIRD notation. For example:</p> + +<pre class="PROGRAMLISTING"> +ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" +</pre> + +<p>The <tt class="FILENAME">ppp-user</tt> script has been renamed to <tt +class="FILENAME">ppp</tt>.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN580" name="AEN580">2.4 Contributed Software</a></h3> + +<p><b class="APPLICATION">BIND</b> has been updated from 9.3.1 to 9.3.2.</p> + +<p><b class="APPLICATION">hostapd</b> has been updated from version 0.3.9 to version +0.4.8.</p> + +<p><b class="APPLICATION">GNU Troff</b> has been updated from version 1.19 to version +1.19.2.</p> + +<p><b class="APPLICATION">sendmail</b> has been updated from 8.13.4 to 8.13.6.</p> + +<p>The timezone database has been updated from the <b class="APPLICATION">tzdata2005l</b> +release to the <b class="APPLICATION">tzdata2005r</b> release.</p> + +<p><b class="APPLICATION">WPA Supplicant</b> has been updated from version 0.3.9 to +version 0.4.8.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection +Infrastructure</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> +command now supports an <code class="OPTION">-P</code> flag, which is the same as the +<code class="OPTION">-p</code> flag except that the given prefix is also used recursively +for the dependency packages if any.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +utilities now support a <code class="OPTION">-K</code> flag to save packages to the +current directory (or <code class="VARNAME">PKGDIR</code> if defined) by default.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +program now supports an <code class="OPTION">-x</code> flag to support basic regular +expressions for package name, an <code class="OPTION">-E</code> flag for extended regular +expressions, and a <code class="OPTION">-G</code> for exact matching.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_version&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_version</span>(1)</span></a> +utility now supports an <code class="OPTION">-o</code> flag to show the origin recorded +on package generation instead of the package name, and an <code class="OPTION">-O</code> +flag to list packages whose registered origin is origin only.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility (<tt class="FILENAME">sysutils/portsnap</tt>) has been added into the FreeBSD +base system. This is a secure, easy to use, fast, lightweight, and generally good way for +users to keep their ports trees up to date.</p> + +<p>A incorrect handling of <code class="VARNAME">HTTP_PROXY_AUTH</code> in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility has been fixed.</p> + +<p>The startup scripts from the <code class="VARNAME">local_startup</code> directory now +evaluated by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rcorder&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rcorder</span>(8)</span></a> with +scripts in the base system.</p> + +<p>The suffix of startup scripts from the Ports Collection has been removed. This means +<tt class="FILENAME">foo.sh</tt> is renamed to <tt class="FILENAME">foo</tt>, and now +scripts whose name is something like <tt class="FILENAME">foo.ORG</tt> will also be +invoked. You are recommended to reinstall packages which install such scripts and remove +extra files in the <code class="VARNAME">local_startup</code> directory.</p> + +<p>New <tt class="FILENAME">rc.conf</tt> variables, <code +class="VARNAME">ldconfig_local_dirs</code> and <code +class="VARNAME">ldconfig_local32_dirs</code> have been added. These hold lists of local +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ldconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ldconfig</span>(8)</span></a> +directories.</p> + +<p>The <tt class="COMMAND">@cwd</tt> command in <tt class="FILENAME">pkg-plist</tt> now +allows no directory argument. If no directory argument is given, it will set current +working directory to the first prefix given by the <tt class="COMMAND">@cwd</tt> +command.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and +Integration</a></h3> + +<p>The <tt class="FILENAME">/var/audit</tt> directory and <tt class="LITERAL">audit</tt> +group have been added. These are for the TrustedBSD <b class="APPLICATION">OpenBSM</b> +distribution, which will be imported in the future releases.</p> + +<p>The supported version of the <b class="APPLICATION">GNOME</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/gnome2/pkg-descr"><tt +class="FILENAME">x11/gnome2</tt></a>) has been updated from 2.10.2 to 2.12.3.</p> + +<p>The supported version of the <b class="APPLICATION">KDE</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/kde2/pkg-descr"><tt +class="FILENAME">x11/kde2</tt></a>) has been updated from 3.4.2 to 3.5.1.</p> + +<p>The supported version of the <b class="APPLICATION">Perl</b> interpreter (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt +class="FILENAME">lang/perl5.8</tt></a>) has been updated from 5.8.7 to 5.8.8.</p> + +<p>The supported version of the <b class="APPLICATION">Xorg</b> windowing system (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/xorg/pkg-descr"><tt +class="FILENAME">x11/xorg</tt></a>) has been updated from 6.8.2 to 6.9.0.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DOC" name="DOC">2.7 Documentation</a></h3> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of +FreeBSD</a></h2> + +<p>Source upgrades to FreeBSD 6.1-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.1-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.1-RELEASE.</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/relnotes-pc98.html b/en/releases/6.1R/relnotes-pc98.html new file mode 100644 index 0000000000..c0a2ad90ef --- /dev/null +++ b/en/releases/6.1R/relnotes-pc98.html @@ -0,0 +1,1016 @@ +<!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/pc98 6.1-RELEASE Release Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/pc98 6.1-RELEASE Release +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The +FreeBSD Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.15.2.7 2006/05/05 17:07:14 hrs Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.</p> + +<p>IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and +Electronics Engineers, Inc. in the United States.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<div> +<div class="ABSTRACT"><a id="AEN24" name="AEN24"></a> +<p>The release notes for FreeBSD 6.1-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.1-STABLE development line. This document lists applicable +security advisories that were issued since the last release, as well as significant +changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also +presented.</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="#BOOT">Boot Loader Changes</a></dt> + +<dt>2.2.2 <a href="#PROC">Hardware Support</a></dt> + +<dt>2.2.3 <a href="#NET-PROTO">Network Protocols</a></dt> + +<dt>2.2.4 <a href="#DISKS">Disks and Storage</a></dt> + +<dt>2.2.5 <a href="#FS">File Systems</a></dt> + +<dt>2.2.6 <a href="#AEN392">Contributed Software</a></dt> +</dl> +</dd> + +<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + +<dd> +<dl> +<dt>2.3.1 <a href="#RC-SCRIPTS"><tt class="FILENAME">/etc/rc.d</tt> Scripts</a></dt> +</dl> +</dd> + +<dt>2.4 <a href="#AEN580">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> + +<dt>2.7 <a href="#DOC">Documentation</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 6.1-RELEASE on the NEC PC-98x1 +hardware platform. It describes recently added, changed, or deleted features of FreeBSD. +It also provides some notes on upgrading from previous versions of FreeBSD.</p> + +<p>This distribution of FreeBSD 6.1-RELEASE is a snapshot distribution. It can be found +at <a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</a> or any of its mirrors. More +information on obtaining this (or other) snapshot 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” appendix</a> to the <a +href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD +Handbook</a>.</p> + +<p>All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with “late-breaking” information discovered late +in the release cycle or after the release. Typically, it contains information on known +bugs, security advisories, and corrections to documentation. An up-to-date copy of the +errata for FreeBSD 6.1-RELEASE can be found on the FreeBSD Web site.</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 +6.0-RELEASE.</p> + +<p>Typical release note items document recent security advisories issued after +6.0-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3> + +<p>A temporary file vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a>, +which could allow a local attacker to overwrite files in the context of a user running +the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a> +utility, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc" +target="_top">FreeBSD-SA-06:01.texindex</a>.</p> + +<p>A temporary file vulnerability in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> text editor, +which could allow a local attacker to overwrite files in the context of a user running <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a>, has been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc" +target="_top">FreeBSD-SA-06:02.ee</a>.</p> + +<p>Several vulnerabilities in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a> utility +have been corrected. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc" +target="_top">FreeBSD-SA-06:03.cpio</a>.</p> + +<p>An error in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +fragment handling, which could cause a crash, has been fixed. For more details see +security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc" +target="_top">FreeBSD-SA-06:04.ipfw</a>.</p> + +<p>A potential buffer overflow in the IEEE 802.11 scanning code has been corrected. For +more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc" +target="_top">FreeBSD-SA-06:05.80211</a>.</p> + +<p>Two instances in which portions of kernel memory could be disclosed to users have been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc" +target="_top">FreeBSD-SA-06:06.kmem</a>.</p> + +<p>A logic bug in the IP fragment handling in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>, which could +cause a crash under certain circumstances, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc" +target="_top">FreeBSD-SA-06:07.pf</a>.</p> + +<p>A logic bug in the NFS server code, which could cause a crash when the server received +a message with a zero-length payload, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc" +target="_top">FreeBSD-SA-06:10.nfs</a>.</p> + +<p>A programming error in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fast_ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fast_ipsec</span>(4)</span></a> +implementation results in the sequence number associated with a Security Association not +being updated, allowing packets to unconditionally pass sequence number verification +checks, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc" +target="_top">FreeBSD-SA-06:11.ipsec</a>.</p> + +<p>A logic bug that could cause <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=opiepasswd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">opiepasswd</span>(1)</span></a> to +allow an unprivileged user to configure OPIE authentication for the root user under +certain circumstances, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc" +target="_top">FreeBSD-SA-06:12.opie</a>.</p> + +<p>An asynchronous signal handling vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sendmail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sendmail</span>(8)</span></a>, +which could allow a remote attacker to execute arbitrary code with the privileges of the +user running sendmail, typically <tt class="USERNAME">root</tt>, has been fixed. For more +details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc" +target="_top">FreeBSD-SA-06:13.sendmail</a>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ddb</span>(4)</span></a> debugger +now supports the <tt class="LITERAL">show lock</tt> command. If the argument has a valid +lock class, this displays various information about the lock and calls a new function +pointer in lock_class (lc_ddb_show) to dump class-specific information about the lock as +well (such as the owner of a mutex or xlock'ed sx lock).</p> + +<p><tt class="FILENAME">DEFAULTS</tt> kernel configuration files for each platform have +been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=firmware&sektion=9&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">firmware</span>(9)</span></a> +subsystem has been added. This allows to load binary data into the kernel via a specially +crafted module.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=random&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">random</span>(4)</span></a> +entropy device driver is now MPSAFE.</p> + +<p>A new sysctl variable <code class="VARNAME">security.mac.biba.interfaces_equal</code> +which makes all network interfaces be created with the label <tt +class="LITERAL">biba/equal(equal-equal)</tt>, has been added. This is useful where +programs such as <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dhclient&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dhclient</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppp</span>(8)</span></a>. which +initialize network interfaces do not have any labeling support. This variable is set as +<tt class="LITERAL">0</tt>(disabled) by default.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.1 Boot Loader Changes</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="PROC" name="PROC">2.2.2 Hardware Support</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi_thermal&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi_thermal</span>(4)</span></a> +driver now supports passive cooling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ce&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ce</span>(4)</span></a> driver, which +supports Cronyx Tau-PCI/32 adapters, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> driver +has been integrated into <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and +the <tt class="DEVICENAME">kbd</tt> device driver. By default <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> will +look for the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> +keyboard first, and then, if not found, look for any keyboard. Switching to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> can be +done at boot time by loading the <tt class="LITERAL">kbdmux</tt> kernel module via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=loader&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">loader</span>(8)</span></a>, or at +runtime via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kldload&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kldload</span>(8)</span></a> and +releasing the active keyboard.</p> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="MM" name="MM">2.2.2.1 Multimedia Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=agp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">agp</span>(4)</span></a> driver +now supports ATI IGP chipsets.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sound&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sound</span>(4)</span></a> driver +has been updated in various aspects including fixing lock-related bugs that could cause +system panics in the previous releases and some performance improvements. Also this +driver now supports wider range sampling rate, multiple precisions choice, and 24/32-bit +PCM format conversion.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver has been added. This supports ATI IXP 200/300/400 series audio controllers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_als4000&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_als4000</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via8233&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via8233</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver is now MPSAFE.</p> +</div> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="NET-IF" name="NET-IF">2.2.2.2 Network Interface Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> driver +has been updated to version 0.9.16.16.</p> + +<p>A bug which prevents the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> driver +from working on a system with over 1GB RAM has been fixed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=polling&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">polling</span>(4)</span></a> +mode.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver now +supports big-endian architectures such as sparc64.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=le&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">le</span>(4)</span></a> driver, which +supports AMD Am7900 LANCE and Am79C9xx PCnet NICs and is based on NetBSD's +implementation, has been added. While the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +also supports these NICs, this driver has several advantages over it such as MPSAFE, +ALTQ, VLAN_MTU, ifmedia, and 32-bit DMA for PCI variants.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver is +now MPSAFE.</p> +</div> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.3 Network Protocols</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> +retransmission algorithm has been rewritten as that ARP requests are retransmitted +without suppression, while there is demand for such ARP entry. Due to this change, a +sysctl variable <code class="VARNAME">net.link.ether.inet.host_down_time</code> has been +removed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now +supports a sysctl variable <code +class="VARNAME">net.link.ether.inet.log_arp_permanent_modify</code> to suppress logging +of attempts to modify permanent ARP entries.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports creating span ports, which transmit a copy of every frame +received by the bridge. This feature can be enabled by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ifconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ifconfig</span>(8)</span></a>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports RFC 3378 EtherIP. This change makes it possible to add <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gif</span>(4)</span></a> +interfaces to bridges, which will then send and receive IP protocol 97 packets. Packets +are Ethernet frames with an EtherIP header prepended.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +packet filter now supports IPv6. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a> packet +filter is deprecated and will be removed in the future releases.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> now +supports substitution of the action argument with the value obtained from table lookup, +which allows some optimization of rulesets. This is now applicable only to <tt +class="LITERAL">pipe</tt>, <tt class="LITERAL">queue</tt>, <tt +class="LITERAL">divert</tt>, <tt class="LITERAL">tee</tt>, <tt +class="LITERAL">netgraph</tt>, and <tt class="LITERAL">ngtee</tt> rules. For example, the +following rules will throw different packets to different pipes:</p> + +<pre class="PROGRAMLISTING"> +pipe 1000 config bw 1000Kbyte/s +pipe 4000 config bw 4000Kbyte/s +table 1 add x.x.x.x 1000 +table 1 add x.x.x.y 4000 +pipe tablearg ip from table(1) to any +</pre> + +<p>A bug has been fixed in which NFS over TCP would not reconnect when the server sent a +FIN. This problem had occurred with Solaris NFS servers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_iface&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_iface</span>(4)</span></a> +Netgraph node now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p> + +<p>The path MTU discovery for multicast packets in the FreeBSD <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6</span>(4)</span></a> stack has +been disabled by default because notifying path MTU by a lot of routers in multicast can +be a kind of distributed Denial-of-Service attack to a router. This feature can be +re-enabled by using a new sysctl variable <code +class="VARNAME">net.inet6.ip6.mcast_pmtu</code>.</p> + +<p>The TCP bandwidth-delay product limiting feature has been disabled when the RTT is +below a certain threshold. This optimization does not make sense on a LAN as it has +trouble figuring out the maximal bandwidth due to the coarse tick granularity. A new +sysctl variable <code class="VARNAME">net.inet.tcp.inflight.rttthresh</code> specifies +the threshold in milliseconds below which this feature will disengage. It defaults to +10ms.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.4 Disks and Storage</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +has been improved on its performance and now supports full 64-bit DMA. While this feature +is enabled by default, this can be forced off by setting the <code +class="VARNAME">hw.amr.force_sg32</code> loader tunable for debugging purpose.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ioctl&sektion=2&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ioctl</span>(2)</span></a> +requests necessary for Linux LSI MegaRaid tools on FreeBSD's Linux emulation +environment.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports a workaround for some controllers whose DMA does not work properly in 48bit +mode. For the suspicious controllers the PIO mode will be used for access to over 137GB +areas.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports the ITE IT8211F IDE controller, and Promise PDC40718 and PDC40719 chip found +in Promise Fasttrak TX4300.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports DMA for kernel crash dump and crash dumping to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +device.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +driver now supports JMicron ATA RAID metadata.</p> + +<p>The <tt class="LITERAL">GEOM_LABEL</tt> class now supports Ext2FS, NTFS, and +ReiserFS.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> class now supports kernel crash dump to the +GEOM providers.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now support sysctl variables <code +class="VARNAME">kern.geom.mirror.disconnect_on_failure</code> and <code +class="VARNAME">kern.geom.graid3.disconnect_on_failure</code> to control whether failed +components will be disconnected or not. The default value is <tt class="LITERAL">1</tt> +to preserve the current behavior, and if it is set to <tt class="LITERAL">0</tt> such +components are not disconnected and the kernel will try to still use them (only first +error will be logged). This is helpful for the case of multiple broken components (in +different places), so actually all data is available. The broken components will be +visible in <tt class="COMMAND">gmirror list</tt> or <tt class="COMMAND">graid3 list</tt> +output with flag <tt class="LITERAL">BROKEN</tt>.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now use parallel I/O request for synchronization to improve the performance. New +sysctl variables <code class="VARNAME">kern.geom.mirror.sync_requests</code> and <code +class="VARNAME">kern.geom.raid3.sync_requests</code> define how many parallel I/O +requests should be used. Also, sysctl variables <code +class="VARNAME">kern.geom.mirror.reqs_per_sync</code>, <code +class="VARNAME">kern.geom.mirror.syncs_per_sec</code>, <code +class="VARNAME">kern.geom.raid3.reqs_per_sync</code>, and <code +class="VARNAME">kern.geom.raid3.syncs_per_sec</code> are deprecated and have been +removed.</p> + +<p>A new GEOM class <tt class="LITERAL">GEOM_ZERO</tt> has been added. It creates very +huge provider (41PB) <tt class="FILENAME">/dev/gzero</tt> and mainly for performance +testing. On <tt class="LITERAL">BIO_READ</tt> request it zero-fills <code +class="VARNAME">bio_data</code> and on <tt class="LITERAL">BIO_WRITE</tt> it does +nothing.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +has been updated to the 9.3.0.1 release on the 3ware Web site.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=geli&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geli</span>(8)</span></a> now +supports loading keyfiles before root file system is mounted. For example, the following +entries can be used in <tt class="FILENAME">/boot/loader.conf</tt> to enable it:</p> + +<pre class="PROGRAMLISTING"> +geli_da0_keyfile0_load="YES" +geli_da0_keyfile0_type="da0:geli_keyfile0" +geli_da0_keyfile0_name="/boot/keys/da0.key0" +geli_da0_keyfile1_load="YES" +geli_da0_keyfile1_type="da0:geli_keyfile1" +geli_da0_keyfile1_name="/boot/keys/da0.key1" +geli_da0_keyfile2_load="YES" +geli_da0_keyfile2_type="da0:geli_keyfile2" +geli_da0_keyfile2_name="/boot/keys/da0.key2" + +geli_da1s3a_keyfile0_load="YES" +geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" +geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" +</pre> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver, +which supports the LSI MegaRAID SAS controller family, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> +driver, which supports HighPoint's RocketRAID 232x series of RAID controllers, has been +added.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="FS" name="FS">2.2.5 File Systems</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN392" name="AEN392">2.2.6 Contributed Software</a></h4> + +<p><b class="APPLICATION">DRM</b> has been updated to a snapshot from DRI CVS as of +20051202.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bsnmpd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bsnmpd</span>(1)</span></a> +utility now supports the Host Resources MIB described in RFC 2790.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now supports the <tt class="LITERAL">nocpu</tt> directive, which cancels the +effect of a previous <tt class="LITERAL">cpu</tt> directive.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now reads <tt class="FILENAME">DEFAULTS</tt> kernel configuration file if it +exists in the current directory before the specified configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=csh&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">csh</span>(1)</span></a> utility +now supports NLS catalog. Note that this requires installing the <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/shells/tcsh_nls/pkg-descr"><tt +class="FILENAME">shells/tcsh_nls</tt></a> port.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> utility +now supports a <code class="OPTION">-f</code> option to specify a configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ln&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ln</span>(1)</span></a> utility now +supports an <code class="OPTION">-F</code> flag which allows to delete existing empty +directories, when creating symbolic links.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=locate&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">locate</span>(1)</span></a> +utility now supports a <code class="OPTION">-0</code> flag to make this utility +interoperable with <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xargs</span>(1)</span></a>'s <code +class="OPTION">-0</code> flag.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ls&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ls</span>(1)</span></a> utility now +supports an <code class="OPTION">-I</code> flag to disable the automatic <code +class="OPTION">-A</code> flag for the superuser.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> utility +now creates a PID file <tt class="FILENAME">/var/run/ftpd.pid</tt> even when no <code +class="OPTION">-p</code> option is specified.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">getfacl</span>(1)</span></a> +utility now supports a <code class="OPTION">-q</code> flag to suppress the per-file +header comment listing the file name, owner, and group.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gvinum&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gvinum</span>(8)</span></a> +utility now supports commands to rename objects and to move a subdisk from one drive to +another.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(8)</span></a> utility +supports a <code class="OPTION">-J <tt class="REPLACEABLE"><i>jid_file</i></tt></code> +option to write out a JidFile, similar to a PidFile, containing the jailid, path, +hostname, IP and the command used to start the jail.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> utility +now supports a <code class="OPTION">-H</code> flag, which causes kdump to print an +additional field holding the threadid.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> program +now supports a <code class="OPTION">-s</code> flag to suppress the display of I/O +data.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mergemaster</span>(8)</span></a> +utility now supports an <code class="OPTION">-A</code> option to explicitly specify an +architecture to pass through to the underlying makefiles.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> daemon +now supports an <code class="OPTION">-H</code> flag to enable horizontal virtual +scrolling similar to a <code class="OPTION">-V</code> flag for vertical virtual +scrolling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=netstat&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">netstat</span>(1)</span></a> +utility now supports printing <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipsec</span>(4)</span></a> +protocol statistics if the kernel was compiled with <tt class="LITERAL">FAST_IPSEC</tt> +rather than the KAME IPSEC stack. Note that the output of <tt class="COMMAND">netstat -s +-p ipsec</tt> differs depending on which stack is compiled into the kernel since they +each keep different statistics.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=periodic&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">periodic</span>(8)</span></a> +daily script now supports display of the status of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gmirror&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gmirror</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=graid3&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">graid3</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gstripe&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gstripe</span>(8)</span></a>, and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gconcat&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gconcat</span>(8)</span></a> +devices. Note that these are disabled by default.</p> + +<p>A new function, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pidfile&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pidfile</span>(3)</span></a>, +which provides reliable pidfiles handling, has been implemented in <tt +class="FILENAME">libutil</tt>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rfcomm_sppd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rfcomm_sppd</span>(1)</span></a> +now supports service name in addition to <code class="OPTION">-c</code> option with +channel number. The supported names are: DUN (Dial-Up Networking), FAX (Fax), LAN (LAN +Access Using PPP), and SP (Serial Port).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snapinfo&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snapinfo</span>(8)</span></a> +utility, which shows snapshot locations on UFS filesystems, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtonum&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtonum</span>(3)</span></a> +library function has been implemented based on OpenBSD's implementation. This is an +improved version of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtoll&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtoll</span>(3)</span></a>.</p> + +<p>A bug in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ypwhich&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ypwhich</span>(1)</span></a> +utility which causes the <code class="OPTION">-m</code> option to produce an incorrect +list of available named maps has been fixed.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="RC-SCRIPTS" name="RC-SCRIPTS">2.3.1 <tt +class="FILENAME">/etc/rc.d</tt> Scripts</a></h4> + +<p>The <tt class="FILENAME">bluetooth</tt> script has been added. This script will be +called from <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> in +response to device attachment/detachment events and to stop/start particular device +without unplugging it by hand. The configuration parameters are in <tt +class="FILENAME">/etc/defaults/bluetooth.device.conf</tt>, and can be overridden by using +<tt class="FILENAME">/etc/bluetooth/<tt class="REPLACEABLE"><i>$device</i></tt>.conf</tt> +(where <tt class="REPLACEABLE"><i>$device</i></tt> is <tt class="DEVICENAME">ubt0</tt>, +<tt class="DEVICENAME">btcc0</tt>, and so on.) For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bluetooth.conf&sektion=5&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span +class="REFENTRYTITLE">bluetooth.conf</span>(5)</span></a>.</p> + +<p>The <tt class="FILENAME">hcsecd</tt> and <tt class="FILENAME">sdpd</tt> scripts have +been added for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hcsecd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hcsecd</span>(8)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sdpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sdpd</span>(8)</span></a> daemons. +These daemons can run even if no Bluetooth devices are attached to the system, but both +daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets +layer must be either loaded as a module or compiled into kernel before the daemons can +run.</p> + +<p>The <tt class="FILENAME">hostapd</tt> script for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hostapd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hostapd</span>(8)</span></a> has +been added.</p> + +<p>The <tt class="FILENAME">jail</tt> script now supports the <code +class="VARNAME">jail_interface</code> option and the <code class="VARNAME">jail_<tt +class="REPLACEABLE"><i>jid</i></tt>_interface</code> option which create an IP alias on +the given interface.</p> + +<p>The <tt class="FILENAME">netif</tt> script now supports <code +class="VARNAME">ipv4_addrs_<tt class="REPLACEABLE"><i>ifn</i></tt></code>, which adds one +or more IPv4 address from a ranged list in CIRD notation. For example:</p> + +<pre class="PROGRAMLISTING"> +ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" +</pre> + +<p>The <tt class="FILENAME">ppp-user</tt> script has been renamed to <tt +class="FILENAME">ppp</tt>.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN580" name="AEN580">2.4 Contributed Software</a></h3> + +<p><b class="APPLICATION">BIND</b> has been updated from 9.3.1 to 9.3.2.</p> + +<p><b class="APPLICATION">hostapd</b> has been updated from version 0.3.9 to version +0.4.8.</p> + +<p><b class="APPLICATION">GNU Troff</b> has been updated from version 1.19 to version +1.19.2.</p> + +<p><b class="APPLICATION">sendmail</b> has been updated from 8.13.4 to 8.13.6.</p> + +<p>The timezone database has been updated from the <b class="APPLICATION">tzdata2005l</b> +release to the <b class="APPLICATION">tzdata2005r</b> release.</p> + +<p><b class="APPLICATION">WPA Supplicant</b> has been updated from version 0.3.9 to +version 0.4.8.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection +Infrastructure</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> +command now supports an <code class="OPTION">-P</code> flag, which is the same as the +<code class="OPTION">-p</code> flag except that the given prefix is also used recursively +for the dependency packages if any.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +utilities now support a <code class="OPTION">-K</code> flag to save packages to the +current directory (or <code class="VARNAME">PKGDIR</code> if defined) by default.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +program now supports an <code class="OPTION">-x</code> flag to support basic regular +expressions for package name, an <code class="OPTION">-E</code> flag for extended regular +expressions, and a <code class="OPTION">-G</code> for exact matching.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_version&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_version</span>(1)</span></a> +utility now supports an <code class="OPTION">-o</code> flag to show the origin recorded +on package generation instead of the package name, and an <code class="OPTION">-O</code> +flag to list packages whose registered origin is origin only.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility (<tt class="FILENAME">sysutils/portsnap</tt>) has been added into the FreeBSD +base system. This is a secure, easy to use, fast, lightweight, and generally good way for +users to keep their ports trees up to date.</p> + +<p>A incorrect handling of <code class="VARNAME">HTTP_PROXY_AUTH</code> in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility has been fixed.</p> + +<p>The startup scripts from the <code class="VARNAME">local_startup</code> directory now +evaluated by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rcorder&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rcorder</span>(8)</span></a> with +scripts in the base system.</p> + +<p>The suffix of startup scripts from the Ports Collection has been removed. This means +<tt class="FILENAME">foo.sh</tt> is renamed to <tt class="FILENAME">foo</tt>, and now +scripts whose name is something like <tt class="FILENAME">foo.ORG</tt> will also be +invoked. You are recommended to reinstall packages which install such scripts and remove +extra files in the <code class="VARNAME">local_startup</code> directory.</p> + +<p>New <tt class="FILENAME">rc.conf</tt> variables, <code +class="VARNAME">ldconfig_local_dirs</code> and <code +class="VARNAME">ldconfig_local32_dirs</code> have been added. These hold lists of local +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ldconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ldconfig</span>(8)</span></a> +directories.</p> + +<p>The <tt class="COMMAND">@cwd</tt> command in <tt class="FILENAME">pkg-plist</tt> now +allows no directory argument. If no directory argument is given, it will set current +working directory to the first prefix given by the <tt class="COMMAND">@cwd</tt> +command.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and +Integration</a></h3> + +<p>The <tt class="FILENAME">/var/audit</tt> directory and <tt class="LITERAL">audit</tt> +group have been added. These are for the TrustedBSD <b class="APPLICATION">OpenBSM</b> +distribution, which will be imported in the future releases.</p> + +<p>The supported version of the <b class="APPLICATION">GNOME</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/gnome2/pkg-descr"><tt +class="FILENAME">x11/gnome2</tt></a>) has been updated from 2.10.2 to 2.12.3.</p> + +<p>The supported version of the <b class="APPLICATION">KDE</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/kde2/pkg-descr"><tt +class="FILENAME">x11/kde2</tt></a>) has been updated from 3.4.2 to 3.5.1.</p> + +<p>The supported version of the <b class="APPLICATION">Perl</b> interpreter (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt +class="FILENAME">lang/perl5.8</tt></a>) has been updated from 5.8.7 to 5.8.8.</p> + +<p>The supported version of the <b class="APPLICATION">Xorg</b> windowing system (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/xorg/pkg-descr"><tt +class="FILENAME">x11/xorg</tt></a>) has been updated from 6.8.2 to 6.9.0.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DOC" name="DOC">2.7 Documentation</a></h3> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of +FreeBSD</a></h2> + +<p>Source upgrades to FreeBSD 6.1-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.1-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.1-RELEASE.</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> + diff --git a/en/releases/6.1R/relnotes-sparc64.html b/en/releases/6.1R/relnotes-sparc64.html new file mode 100644 index 0000000000..1958348a85 --- /dev/null +++ b/en/releases/6.1R/relnotes-sparc64.html @@ -0,0 +1,1011 @@ +<!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/sparc64 6.1-RELEASE Release Notes</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +</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/sparc64 6.1-RELEASE Release +Notes</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The +FreeBSD Documentation Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.15.2.7 2006/05/05 17:07:14 hrs Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</p> + +<p>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.</p> + +<p>IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and +Electronics Engineers, Inc. in the United States.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.</p> + +<p>Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the “™” or the “®” symbol.</p> +</div> + +<div> +<div class="ABSTRACT"><a id="AEN24" name="AEN24"></a> +<p>The release notes for FreeBSD 6.1-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.1-STABLE development line. This document lists applicable +security advisories that were issued since the last release, as well as significant +changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also +presented.</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="#BOOT">Boot Loader Changes</a></dt> + +<dt>2.2.2 <a href="#PROC">Hardware Support</a></dt> + +<dt>2.2.3 <a href="#NET-PROTO">Network Protocols</a></dt> + +<dt>2.2.4 <a href="#DISKS">Disks and Storage</a></dt> + +<dt>2.2.5 <a href="#FS">File Systems</a></dt> + +<dt>2.2.6 <a href="#AEN392">Contributed Software</a></dt> +</dl> +</dd> + +<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + +<dd> +<dl> +<dt>2.3.1 <a href="#RC-SCRIPTS"><tt class="FILENAME">/etc/rc.d</tt> Scripts</a></dt> +</dl> +</dd> + +<dt>2.4 <a href="#AEN580">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> + +<dt>2.7 <a href="#DOC">Documentation</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 6.1-RELEASE on the UltraSPARC +hardware platform. It describes recently added, changed, or deleted features of FreeBSD. +It also provides some notes on upgrading from previous versions of FreeBSD.</p> + +<p>This distribution of FreeBSD 6.1-RELEASE is a snapshot distribution. It can be found +at <a href="http://www.FreeBSD.org/snapshots/" +target="_top">http://www.FreeBSD.org/snapshots/</a> or any of its mirrors. More +information on obtaining this (or other) snapshot 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” appendix</a> to the <a +href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD +Handbook</a>.</p> + +<p>All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with “late-breaking” information discovered late +in the release cycle or after the release. Typically, it contains information on known +bugs, security advisories, and corrections to documentation. An up-to-date copy of the +errata for FreeBSD 6.1-RELEASE can be found on the FreeBSD Web site.</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 +6.0-RELEASE.</p> + +<p>Typical release note items document recent security advisories issued after +6.0-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.</p> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3> + +<p>A temporary file vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a>, +which could allow a local attacker to overwrite files in the context of a user running +the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=texindex&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">texindex</span>(1)</span></a> +utility, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc" +target="_top">FreeBSD-SA-06:01.texindex</a>.</p> + +<p>A temporary file vulnerability in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> text editor, +which could allow a local attacker to overwrite files in the context of a user running <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a>, has been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc" +target="_top">FreeBSD-SA-06:02.ee</a>.</p> + +<p>Several vulnerabilities in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a> utility +have been corrected. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc" +target="_top">FreeBSD-SA-06:03.cpio</a>.</p> + +<p>An error in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +fragment handling, which could cause a crash, has been fixed. For more details see +security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc" +target="_top">FreeBSD-SA-06:04.ipfw</a>.</p> + +<p>A potential buffer overflow in the IEEE 802.11 scanning code has been corrected. For +more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc" +target="_top">FreeBSD-SA-06:05.80211</a>.</p> + +<p>Two instances in which portions of kernel memory could be disclosed to users have been +fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc" +target="_top">FreeBSD-SA-06:06.kmem</a>.</p> + +<p>A logic bug in the IP fragment handling in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>, which could +cause a crash under certain circumstances, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc" +target="_top">FreeBSD-SA-06:07.pf</a>.</p> + +<p>A logic bug in the NFS server code, which could cause a crash when the server received +a message with a zero-length payload, has been fixed. For more details see security +advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc" +target="_top">FreeBSD-SA-06:10.nfs</a>.</p> + +<p>A programming error in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=fast_ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fast_ipsec</span>(4)</span></a> +implementation results in the sequence number associated with a Security Association not +being updated, allowing packets to unconditionally pass sequence number verification +checks, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc" +target="_top">FreeBSD-SA-06:11.ipsec</a>.</p> + +<p>A logic bug that could cause <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=opiepasswd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">opiepasswd</span>(1)</span></a> to +allow an unprivileged user to configure OPIE authentication for the root user under +certain circumstances, has been fixed. For more details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc" +target="_top">FreeBSD-SA-06:12.opie</a>.</p> + +<p>An asynchronous signal handling vulnerability in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sendmail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sendmail</span>(8)</span></a>, +which could allow a remote attacker to execute arbitrary code with the privileges of the +user running sendmail, typically <tt class="USERNAME">root</tt>, has been fixed. For more +details see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc" +target="_top">FreeBSD-SA-06:13.sendmail</a>.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ddb</span>(4)</span></a> debugger +now supports the <tt class="LITERAL">show lock</tt> command. If the argument has a valid +lock class, this displays various information about the lock and calls a new function +pointer in lock_class (lc_ddb_show) to dump class-specific information about the lock as +well (such as the owner of a mutex or xlock'ed sx lock).</p> + +<p><tt class="FILENAME">DEFAULTS</tt> kernel configuration files for each platform have +been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=firmware&sektion=9&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">firmware</span>(9)</span></a> +subsystem has been added. This allows to load binary data into the kernel via a specially +crafted module.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=random&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">random</span>(4)</span></a> +entropy device driver is now MPSAFE.</p> + +<p>A new sysctl variable <code class="VARNAME">security.mac.biba.interfaces_equal</code> +which makes all network interfaces be created with the label <tt +class="LITERAL">biba/equal(equal-equal)</tt>, has been added. This is useful where +programs such as <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=dhclient&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dhclient</span>(8)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ppp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ppp</span>(8)</span></a>. which +initialize network interfaces do not have any labeling support. This variable is set as +<tt class="LITERAL">0</tt>(disabled) by default.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.1 Boot Loader Changes</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="PROC" name="PROC">2.2.2 Hardware Support</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi_thermal&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi_thermal</span>(4)</span></a> +driver now supports passive cooling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> driver +has been integrated into <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and +the <tt class="DEVICENAME">kbd</tt> device driver. By default <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> will +look for the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> +keyboard first, and then, if not found, look for any keyboard. Switching to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kbdmux&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kbdmux</span>(4)</span></a> can be +done at boot time by loading the <tt class="LITERAL">kbdmux</tt> kernel module via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=loader&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">loader</span>(8)</span></a>, or at +runtime via <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kldload&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kldload</span>(8)</span></a> and +releasing the active keyboard.</p> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="MM" name="MM">2.2.2.1 Multimedia Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=agp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">agp</span>(4)</span></a> driver +now supports ATI IGP chipsets.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sound&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sound</span>(4)</span></a> driver +has been updated in various aspects including fixing lock-related bugs that could cause +system panics in the previous releases and some performance improvements. Also this +driver now supports wider range sampling rate, multiple precisions choice, and 24/32-bit +PCM format conversion.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_atiixp&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_atiixp</span>(4)</span></a> +driver has been added. This supports ATI IXP 200/300/400 series audio controllers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_als4000&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_als4000</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_es137x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_es137x</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_ich&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_ich</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_solo&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_solo</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via8233&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via8233</span>(4)</span></a> +driver is now MPSAFE.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_via82c686&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_via82c686</span>(4)</span></a> +driver is now MPSAFE.</p> +</div> + +<div class="SECT4"> +<hr /> +<h5 class="SECT4"><a id="NET-IF" name="NET-IF">2.2.2.2 Network Interface Support</a></h5> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> driver +has been updated to version 0.9.16.16.</p> + +<p>A bug which prevents the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bfe&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bfe</span>(4)</span></a> driver +from working on a system with over 1GB RAM has been fixed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=polling&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">polling</span>(4)</span></a> +mode.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver now +supports big-endian architectures such as sparc64.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=le&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">le</span>(4)</span></a> driver, which +supports AMD Am7900 LANCE and Am79C9xx PCnet NICs and is based on NetBSD's +implementation, has been added. While the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lnc</span>(4)</span></a> driver +also supports these NICs, this driver has several advantages over it such as MPSAFE, +ALTQ, VLAN_MTU, ifmedia, and 32-bit DMA for PCI variants.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lge</span>(4)</span></a> driver is +now MPSAFE.</p> +</div> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.3 Network Protocols</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> +retransmission algorithm has been rewritten as that ARP requests are retransmitted +without suppression, while there is demand for such ARP entry. Due to this change, a +sysctl variable <code class="VARNAME">net.link.ether.inet.host_down_time</code> has been +removed.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=arp&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">arp</span>(8)</span></a> now +supports a sysctl variable <code +class="VARNAME">net.link.ether.inet.log_arp_permanent_modify</code> to suppress logging +of attempts to modify permanent ARP entries.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports creating span ports, which transmit a copy of every frame +received by the bridge. This feature can be enabled by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ifconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ifconfig</span>(8)</span></a>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> +bridge driver now supports RFC 3378 EtherIP. This change makes it possible to add <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gif</span>(4)</span></a> +interfaces to bridges, which will then send and receive IP protocol 97 packets. Packets +are Ethernet frames with an EtherIP header prepended.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP +packet filter now supports IPv6. The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a> packet +filter is deprecated and will be removed in the future releases.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> now +supports substitution of the action argument with the value obtained from table lookup, +which allows some optimization of rulesets. This is now applicable only to <tt +class="LITERAL">pipe</tt>, <tt class="LITERAL">queue</tt>, <tt +class="LITERAL">divert</tt>, <tt class="LITERAL">tee</tt>, <tt +class="LITERAL">netgraph</tt>, and <tt class="LITERAL">ngtee</tt> rules. For example, the +following rules will throw different packets to different pipes:</p> + +<pre class="PROGRAMLISTING"> +pipe 1000 config bw 1000Kbyte/s +pipe 4000 config bw 4000Kbyte/s +table 1 add x.x.x.x 1000 +table 1 add x.x.x.y 4000 +pipe tablearg ip from table(1) to any +</pre> + +<p>A bug has been fixed in which NFS over TCP would not reconnect when the server sent a +FIN. This problem had occurred with Solaris NFS servers.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_iface&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_iface</span>(4)</span></a> +Netgraph node now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p> + +<p>The path MTU discovery for multicast packets in the FreeBSD <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6</span>(4)</span></a> stack has +been disabled by default because notifying path MTU by a lot of routers in multicast can +be a kind of distributed Denial-of-Service attack to a router. This feature can be +re-enabled by using a new sysctl variable <code +class="VARNAME">net.inet6.ip6.mcast_pmtu</code>.</p> + +<p>The TCP bandwidth-delay product limiting feature has been disabled when the RTT is +below a certain threshold. This optimization does not make sense on a LAN as it has +trouble figuring out the maximal bandwidth due to the coarse tick granularity. A new +sysctl variable <code class="VARNAME">net.inet.tcp.inflight.rttthresh</code> specifies +the threshold in milliseconds below which this feature will disengage. It defaults to +10ms.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.4 Disks and Storage</a></h4> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +has been improved on its performance and now supports full 64-bit DMA. While this feature +is enabled by default, this can be forced off by setting the <code +class="VARNAME">hw.amr.force_sg32</code> loader tunable for debugging purpose.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">amr</span>(4)</span></a> driver +now supports <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ioctl&sektion=2&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ioctl</span>(2)</span></a> +requests necessary for Linux LSI MegaRaid tools on FreeBSD's Linux emulation +environment.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports a workaround for some controllers whose DMA does not work properly in 48bit +mode. For the suspicious controllers the PIO mode will be used for access to over 137GB +areas.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports the ITE IT8211F IDE controller, and Promise PDC40718 and PDC40719 chip found +in Promise Fasttrak TX4300.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> driver +now supports DMA for kernel crash dump and crash dumping to <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +device.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ataraid</span>(4)</span></a> +driver now supports JMicron ATA RAID metadata.</p> + +<p>The <tt class="LITERAL">GEOM_LABEL</tt> class now supports Ext2FS, NTFS, and +ReiserFS.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> class now supports kernel crash dump to the +GEOM providers.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now support sysctl variables <code +class="VARNAME">kern.geom.mirror.disconnect_on_failure</code> and <code +class="VARNAME">kern.geom.graid3.disconnect_on_failure</code> to control whether failed +components will be disconnected or not. The default value is <tt class="LITERAL">1</tt> +to preserve the current behavior, and if it is set to <tt class="LITERAL">0</tt> such +components are not disconnected and the kernel will try to still use them (only first +error will be logged). This is helpful for the case of multiple broken components (in +different places), so actually all data is available. The broken components will be +visible in <tt class="COMMAND">gmirror list</tt> or <tt class="COMMAND">graid3 list</tt> +output with flag <tt class="LITERAL">BROKEN</tt>.</p> + +<p>The <tt class="LITERAL">GEOM_MIRROR</tt> and <tt class="LITERAL">GEOM_RAID3</tt> +classes now use parallel I/O request for synchronization to improve the performance. New +sysctl variables <code class="VARNAME">kern.geom.mirror.sync_requests</code> and <code +class="VARNAME">kern.geom.raid3.sync_requests</code> define how many parallel I/O +requests should be used. Also, sysctl variables <code +class="VARNAME">kern.geom.mirror.reqs_per_sync</code>, <code +class="VARNAME">kern.geom.mirror.syncs_per_sec</code>, <code +class="VARNAME">kern.geom.raid3.reqs_per_sync</code>, and <code +class="VARNAME">kern.geom.raid3.syncs_per_sec</code> are deprecated and have been +removed.</p> + +<p>A new GEOM class <tt class="LITERAL">GEOM_ZERO</tt> has been added. It creates very +huge provider (41PB) <tt class="FILENAME">/dev/gzero</tt> and mainly for performance +testing. On <tt class="LITERAL">BIO_READ</tt> request it zero-fills <code +class="VARNAME">bio_data</code> and on <tt class="LITERAL">BIO_WRITE</tt> it does +nothing.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver +has been updated to the 9.3.0.1 release on the 3ware Web site.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=geli&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geli</span>(8)</span></a> now +supports loading keyfiles before root file system is mounted. For example, the following +entries can be used in <tt class="FILENAME">/boot/loader.conf</tt> to enable it:</p> + +<pre class="PROGRAMLISTING"> +geli_da0_keyfile0_load="YES" +geli_da0_keyfile0_type="da0:geli_keyfile0" +geli_da0_keyfile0_name="/boot/keys/da0.key0" +geli_da0_keyfile1_load="YES" +geli_da0_keyfile1_type="da0:geli_keyfile1" +geli_da0_keyfile1_name="/boot/keys/da0.key1" +geli_da0_keyfile2_load="YES" +geli_da0_keyfile2_type="da0:geli_keyfile2" +geli_da0_keyfile2_name="/boot/keys/da0.key2" + +geli_da1s3a_keyfile0_load="YES" +geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" +geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" +</pre> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mfi</span>(4)</span></a> driver, +which supports the LSI MegaRAID SAS controller family, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rr232x&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rr232x</span>(4)</span></a> +driver, which supports HighPoint's RocketRAID 232x series of RAID controllers, has been +added.</p> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="FS" name="FS">2.2.5 File Systems</a></h4> +</div> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="AEN392" name="AEN392">2.2.6 Contributed Software</a></h4> + +<p><b class="APPLICATION">DRM</b> has been updated to a snapshot from DRI CVS as of +20051202.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bsnmpd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bsnmpd</span>(1)</span></a> +utility now supports the Host Resources MIB described in RFC 2790.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now supports the <tt class="LITERAL">nocpu</tt> directive, which cancels the +effect of a previous <tt class="LITERAL">cpu</tt> directive.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> +utility now reads <tt class="FILENAME">DEFAULTS</tt> kernel configuration file if it +exists in the current directory before the specified configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=csh&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">csh</span>(1)</span></a> utility +now supports NLS catalog. Note that this requires installing the <a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/shells/tcsh_nls/pkg-descr"><tt +class="FILENAME">shells/tcsh_nls</tt></a> port.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> utility +now supports a <code class="OPTION">-f</code> option to specify a configuration file.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ln&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ln</span>(1)</span></a> utility now +supports an <code class="OPTION">-F</code> flag which allows to delete existing empty +directories, when creating symbolic links.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=locate&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">locate</span>(1)</span></a> +utility now supports a <code class="OPTION">-0</code> flag to make this utility +interoperable with <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xargs</span>(1)</span></a>'s <code +class="OPTION">-0</code> flag.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ls&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span + class="CITEREFENTRY"><span class="REFENTRYTITLE">ls</span>(1)</span></a> utility now +supports an <code class="OPTION">-I</code> flag to disable the automatic <code +class="OPTION">-A</code> flag for the superuser.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> utility +now creates a PID file <tt class="FILENAME">/var/run/ftpd.pid</tt> even when no <code +class="OPTION">-p</code> option is specified.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">getfacl</span>(1)</span></a> +utility now supports a <code class="OPTION">-q</code> flag to suppress the per-file +header comment listing the file name, owner, and group.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gvinum&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gvinum</span>(8)</span></a> +utility now supports commands to rename objects and to move a subdisk from one drive to +another.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(8)</span></a> utility +supports a <code class="OPTION">-J <tt class="REPLACEABLE"><i>jid_file</i></tt></code> +option to write out a JidFile, similar to a PidFile, containing the jailid, path, +hostname, IP and the command used to start the jail.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> utility +now supports a <code class="OPTION">-H</code> flag, which causes kdump to print an +additional field holding the threadid.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=kdump&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kdump</span>(1)</span></a> program +now supports a <code class="OPTION">-s</code> flag to suppress the display of I/O +data.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mergemaster</span>(8)</span></a> +utility now supports an <code class="OPTION">-A</code> option to explicitly specify an +architecture to pass through to the underlying makefiles.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> daemon +now supports an <code class="OPTION">-H</code> flag to enable horizontal virtual +scrolling similar to a <code class="OPTION">-V</code> flag for vertical virtual +scrolling.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=netstat&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">netstat</span>(1)</span></a> +utility now supports printing <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipsec&sektion=4&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipsec</span>(4)</span></a> +protocol statistics if the kernel was compiled with <tt class="LITERAL">FAST_IPSEC</tt> +rather than the KAME IPSEC stack. Note that the output of <tt class="COMMAND">netstat -s +-p ipsec</tt> differs depending on which stack is compiled into the kernel since they +each keep different statistics.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=periodic&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">periodic</span>(8)</span></a> +daily script now supports display of the status of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gmirror&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gmirror</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=graid3&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">graid3</span>(8)</span></a>, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gstripe&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gstripe</span>(8)</span></a>, and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=gconcat&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gconcat</span>(8)</span></a> +devices. Note that these are disabled by default.</p> + +<p>A new function, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pidfile&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pidfile</span>(3)</span></a>, +which provides reliable pidfiles handling, has been implemented in <tt +class="FILENAME">libutil</tt>.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rfcomm_sppd&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rfcomm_sppd</span>(1)</span></a> +now supports service name in addition to <code class="OPTION">-c</code> option with +channel number. The supported names are: DUN (Dial-Up Networking), FAX (Fax), LAN (LAN +Access Using PPP), and SP (Serial Port).</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=snapinfo&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snapinfo</span>(8)</span></a> +utility, which shows snapshot locations on UFS filesystems, has been added.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtonum&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtonum</span>(3)</span></a> +library function has been implemented based on OpenBSD's implementation. This is an +improved version of <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=strtoll&sektion=3&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">strtoll</span>(3)</span></a>.</p> + +<p>A bug in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ypwhich&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ypwhich</span>(1)</span></a> +utility which causes the <code class="OPTION">-m</code> option to produce an incorrect +list of available named maps has been fixed.</p> + +<div class="SECT3"> +<hr /> +<h4 class="SECT3"><a id="RC-SCRIPTS" name="RC-SCRIPTS">2.3.1 <tt +class="FILENAME">/etc/rc.d</tt> Scripts</a></h4> + +<p>The <tt class="FILENAME">bluetooth</tt> script has been added. This script will be +called from <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=devd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devd</span>(8)</span></a> in +response to device attachment/detachment events and to stop/start particular device +without unplugging it by hand. The configuration parameters are in <tt +class="FILENAME">/etc/defaults/bluetooth.device.conf</tt>, and can be overridden by using +<tt class="FILENAME">/etc/bluetooth/<tt class="REPLACEABLE"><i>$device</i></tt>.conf</tt> +(where <tt class="REPLACEABLE"><i>$device</i></tt> is <tt class="DEVICENAME">ubt0</tt>, +<tt class="DEVICENAME">btcc0</tt>, and so on.) For more details, see <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=bluetooth.conf&sektion=5&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span +class="REFENTRYTITLE">bluetooth.conf</span>(5)</span></a>.</p> + +<p>The <tt class="FILENAME">hcsecd</tt> and <tt class="FILENAME">sdpd</tt> scripts have +been added for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hcsecd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hcsecd</span>(8)</span></a> and <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sdpd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sdpd</span>(8)</span></a> daemons. +These daemons can run even if no Bluetooth devices are attached to the system, but both +daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets +layer must be either loaded as a module or compiled into kernel before the daemons can +run.</p> + +<p>The <tt class="FILENAME">hostapd</tt> script for <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=hostapd&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hostapd</span>(8)</span></a> has +been added.</p> + +<p>The <tt class="FILENAME">jail</tt> script now supports the <code +class="VARNAME">jail_interface</code> option and the <code class="VARNAME">jail_<tt +class="REPLACEABLE"><i>jid</i></tt>_interface</code> option which create an IP alias on +the given interface.</p> + +<p>The <tt class="FILENAME">netif</tt> script now supports <code +class="VARNAME">ipv4_addrs_<tt class="REPLACEABLE"><i>ifn</i></tt></code>, which adds one +or more IPv4 address from a ranged list in CIRD notation. For example:</p> + +<pre class="PROGRAMLISTING"> +ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" +</pre> + +<p>The <tt class="FILENAME">ppp-user</tt> script has been renamed to <tt +class="FILENAME">ppp</tt>.</p> +</div> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="AEN580" name="AEN580">2.4 Contributed Software</a></h3> + +<p><b class="APPLICATION">BIND</b> has been updated from 9.3.1 to 9.3.2.</p> + +<p><b class="APPLICATION">hostapd</b> has been updated from version 0.3.9 to version +0.4.8.</p> + +<p><b class="APPLICATION">GNU Troff</b> has been updated from version 1.19 to version +1.19.2.</p> + +<p><b class="APPLICATION">sendmail</b> has been updated from 8.13.4 to 8.13.6.</p> + +<p>The timezone database has been updated from the <b class="APPLICATION">tzdata2005l</b> +release to the <b class="APPLICATION">tzdata2005r</b> release.</p> + +<p><b class="APPLICATION">WPA Supplicant</b> has been updated from version 0.3.9 to +version 0.4.8.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection +Infrastructure</a></h3> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> +command now supports an <code class="OPTION">-P</code> flag, which is the same as the +<code class="OPTION">-p</code> flag except that the given prefix is also used recursively +for the dependency packages if any.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a> and +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +utilities now support a <code class="OPTION">-K</code> flag to save packages to the +current directory (or <code class="VARNAME">PKGDIR</code> if defined) by default.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_create</span>(1)</span></a> +program now supports an <code class="OPTION">-x</code> flag to support basic regular +expressions for package name, an <code class="OPTION">-E</code> flag for extended regular +expressions, and a <code class="OPTION">-G</code> for exact matching.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_version&sektion=1&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_version</span>(1)</span></a> +utility now supports an <code class="OPTION">-o</code> flag to show the origin recorded +on package generation instead of the package name, and an <code class="OPTION">-O</code> +flag to list packages whose registered origin is origin only.</p> + +<p>The <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility (<tt class="FILENAME">sysutils/portsnap</tt>) has been added into the FreeBSD +base system. This is a secure, easy to use, fast, lightweight, and generally good way for +users to keep their ports trees up to date.</p> + +<p>A incorrect handling of <code class="VARNAME">HTTP_PROXY_AUTH</code> in the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=portsnap&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">portsnap</span>(8)</span></a> +utility has been fixed.</p> + +<p>The startup scripts from the <code class="VARNAME">local_startup</code> directory now +evaluated by using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=rcorder&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rcorder</span>(8)</span></a> with +scripts in the base system.</p> + +<p>The suffix of startup scripts from the Ports Collection has been removed. This means +<tt class="FILENAME">foo.sh</tt> is renamed to <tt class="FILENAME">foo</tt>, and now +scripts whose name is something like <tt class="FILENAME">foo.ORG</tt> will also be +invoked. You are recommended to reinstall packages which install such scripts and remove +extra files in the <code class="VARNAME">local_startup</code> directory.</p> + +<p>New <tt class="FILENAME">rc.conf</tt> variables, <code +class="VARNAME">ldconfig_local_dirs</code> and <code +class="VARNAME">ldconfig_local32_dirs</code> have been added. These hold lists of local +<a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ldconfig&sektion=8&manpath=FreeBSD+6.1-RELEASE"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ldconfig</span>(8)</span></a> +directories.</p> + +<p>The <tt class="COMMAND">@cwd</tt> command in <tt class="FILENAME">pkg-plist</tt> now +allows no directory argument. If no directory argument is given, it will set current +working directory to the first prefix given by the <tt class="COMMAND">@cwd</tt> +command.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and +Integration</a></h3> + +<p>The <tt class="FILENAME">/var/audit</tt> directory and <tt class="LITERAL">audit</tt> +group have been added. These are for the TrustedBSD <b class="APPLICATION">OpenBSM</b> +distribution, which will be imported in the future releases.</p> + +<p>The supported version of the <b class="APPLICATION">GNOME</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/gnome2/pkg-descr"><tt +class="FILENAME">x11/gnome2</tt></a>) has been updated from 2.10.2 to 2.12.3.</p> + +<p>The supported version of the <b class="APPLICATION">KDE</b> desktop environment (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/kde2/pkg-descr"><tt +class="FILENAME">x11/kde2</tt></a>) has been updated from 3.4.2 to 3.5.1.</p> + +<p>The supported version of the <b class="APPLICATION">Perl</b> interpreter (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt +class="FILENAME">lang/perl5.8</tt></a>) has been updated from 5.8.7 to 5.8.8.</p> + +<p>The supported version of the <b class="APPLICATION">Xorg</b> windowing system (<a +href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/xorg/pkg-descr"><tt +class="FILENAME">x11/xorg</tt></a>) has been updated from 6.8.2 to 6.9.0.</p> +</div> + +<div class="SECT2"> +<hr /> +<h3 class="SECT2"><a id="DOC" name="DOC">2.7 Documentation</a></h3> +</div> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of +FreeBSD</a></h2> + +<p>Source upgrades to FreeBSD 6.1-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.1-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.1-RELEASE.</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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small>For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p> +</body> +</html> +