os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
doc/en/releases/4.4R/hardware-alpha.html
Bruce A. Mah 3c690effe0 Commit the hardware notes for 4.4-RELEASE to the Web tree, with 
appropriate infrastructure changes and pointers from the appropriate
places.  (With RELNOTESng, the hardware notes are no longer duplicated
in the release notes; they're a separate document.)

Suggested by:	Jed Clear <clear@alum.mit.edu>
2001-10-21 23:21:27 +00:00

8000 lines
253 KiB
HTML
Raw Blame History

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD 4.4-RELEASE alpha Hardware Notes</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.71 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD 4.4-RELEASE alpha
Hardware Notes</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Documentation
Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001 by The
FreeBSD Documentation Project</p>
<hr>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN9">1 Introduction</a></h1>
<p>This document contains the hardware compatability notes
for FreeBSD 4.4-RELEASE on the alpha hardware platform. 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 hardware platform. Versions of
the hardware compatability notes for other
architectures will differ in some details.</p>
</blockquote>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN14">2 Supported processors
and motherboards</a></h1>
$FreeBSD:
src/release/doc/en_US.ISO8859-1/hardware/alpha/proc-alpha.sgml,v
1.13.2.10 2001/08/30 13:20:59 wilko Exp $
<p>This section is maintained by Wilko Bulte <tt class=
"EMAIL">&lt;<a href=
"mailto:wilko@FreeBSD.org">wilko@FreeBSD.org</a>&gt;</tt>.</p>
<p>Additions, corrections and constructive criticism are
invited. In particular information on system quirks is more
than welcome.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN21">2.1 Overview</a></h2>
<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>
<br>
<br>
<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. 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 <tt class=
"USERINPUT"><b>UPPER CASE</b></tt>. Lower case input
is also acceptible to SRM. Upper case is used for
clarity.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN37">2.2 In general, what do
you need to run FreeBSD on an Alpha?</a></h2>
<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 <i class="EMPHASIS">no</i> FreeBSD (or
NetBSD, OpenBSD, Tru64 Unix or OpenVMS for that matter).
With the demise of WindowsNT/alpha a lot of former NT
boxes are sold on the second hand market. They have
little or no trade-in value when they are NT-only from
the console firmware perspective. So, be suspicious if
the price appears too good.</p>
<p>Known non-SRM machines are:</p>
<ul>
<li>
<p>Digital XL series</p>
</li>
<li>
<p>Digital XLT series</p>
</li>
<li>
<p>Samsung PC164UX</p>
</li>
<li>
<p>Samsung 164B</p>
</li>
</ul>
<br>
<br>
<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 <i class="EMPHASIS">other</i>
adapter types that it can boot from than the SRM. For
example you can boot from an Adaptec 2940UW with
ARC/AlphaBios but (generally) not with SRM. Some newer
machine types have introduced Adaptec boot support.
Please consult the machine specific section for
details.</p>
<p>Most adapters that cannot be booted from work fine for
data-only disks. The differences between SRM and ARC
could also get you pre-packaged IDE CDROMs and hard
drives in some (former WindowsNT) systems. SRM versions
exist (depends on the machine type) that can boot from
IDE disks and CDROMs. Check the machine specific section
for details.</p>
<p>FreeBSD 4.0 and later can be booted from the
distribution CDROM. Earlier versions needed booting from
a 2 disk floppy set.</p>
<p>In order to be bootable the root partition (partition
a) must be at offset 0 of the disk drive. This means you
have to use the installer's partitioning menu and start
with assigning partiton a at offset 0 to the root
partition. Subsequently layout the rest of the partitions
to your liking. If you do not adhere to this rule the
install will proceed just fine, but the system will not
be bootable from the freshly installed disk.</p>
<p>If you don't have/want a local disk drive you can boot
via the Ethernet. This assumes an Ethernet adapter/chip
that is recognized by the SRM console. Generally speaking
this boils down to either a 21040 or 21142 or 21143 based
Ethernet interface. Older machines or SRM versions may
not recognize the 21142 / 21143 Fast Ethernet chips, you
are then limited to using 10Mbit Ethernet for net booting
those machines. Non-DEC cards based on said chips will
generally (but are not guaranteed to) work. Note that
Intel took over the 21x4x chips when it bought Digital
Semiconductor. So you might see an Intel logo on them
these days. Recent machine designs have SRM support for
Intel 8255x Ethernet chips.</p>
<p>Alpha machines can be run with SRM on a graphics
console or on a serial console. ARC can also be run on a
serial consoles if need be. VT100 emulation with 8 bit
controls should at least allow you to switch from
ARC/AlphaBIOS to SRM mode without having to install a
graphics card first.</p>
<p>If you want to run your Alpha machine without a
monitor/graphics card just don't connect a keyboard/mouse
to the machine. Instead hook up a serial
terminal[emulator] to serial port #1. The SRM will talk
9600N81 to you. This can also be really practical for
debugging purposes. Beware: some/most (?) SRMs will also
present you with a console prompt at serial port #2. The
booting kernel, however, will display the boot messages
on serial port #1 and will also put the console there. <i
class="EMPHASIS">This can be extremely confusing.</i></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. Please
note that TGA-based cards are not currently supported as
FreeBSD console display cards. Digital ZLXp-xx cards are
often found in Alpha machines and are TGA based. You will
either have to use a serial console or another display
card.</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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET PCI_PARITY OFF</b></tt>
</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.
The EVs with double digit numbers are slightly improved
versions. For example EV45 has an improved FPU and 16
kByte on-chip separate I &amp; D caches compared to the
EV4 on which it is based. Rule of thumb: the higher the
digit immediately following ``EV'' the more desirable
(read: faster / more modern).</p>
<p>For memory you want at least 32 Mbytes. I have had
FreeBSD run on a 16 Mbyte system but you will not enjoy
that. Kernel build times halved when I went to 32 Mbytes.
Note that the SRM console steals 2Mbyte from the total
system memory (and keeps it). For more serious work 64
Mbytes or more are recommended.</p>
<p>While on the subject of memory: pay close attention to
the type of memory your machine uses. There are very
different memory configurations and requirements for the
various machines.</p>
<p>Final word: I expect the above to sound a bit daunting
to the first-time Alpha user. Don't be daunted too much.
And do feel free to ask questions if something is not
clear after reading this document.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN83">2.3 System-specific
information</a></h2>
<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>
<h3 class="SECT3"><a name="AEN88">2.3.1 AXPpci33
(``NoName'')</a></h3>
<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 &amp; 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>
<br>
<br>
</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>
<br>
<br>
</li>
<li>
<p>embedded Fast SCSI using a Symbios 53C810
chip</p>
</li>
</ul>
<br>
<br>
<p>NoNames can either have SRM <i class=
"EMPHASIS">or</i> ARC console firmware in their Flash
ROM. The Flash ROM is not big enough to hold both ARC
and SRM at the same time and allow software selection
of alternate console code. But you only need SRM
anyway.</p>
<p>Cache for the NoNames are 15 or 20 ns DIL chips. For
a 256 kByte cache you want to check your junked 486
mainboard. Chips for a 1 Mbyte cache are a rarer breed
unfortunately. Getting at least a 256kByte cache is
recommended performance wise. Cache-less they are
really slow.</p>
<p>The NoName mainboard has a PC/AT-standard power
connector. It also has a power connector for 3.3 Volts.
No need to rush out to get a new power supply. The 3.3
Volts is only needed in case you run 3.3 Volts PCI
expansion boards. These are quite rare.</p>
<p>The IDE interface is supported by FreeBSD and
requires a line in the kernel configuration file as
follows:</p>
<pre class="PROGRAMLISTING">
device ata0 at isa? port IO_WD1 irq 14
</pre>
<p>The SRM console unfortunately <i class=
"EMPHASIS">cannot boot</i> from IDE disks. This means
you will have to use a SCSI disk as the boot
device.</p>
<p>The NoName is somewhat stubborn when it comes to
serial consoles. It needs</p>
<pre class="SCREEN">
&gt;&gt;&gt; <tt class=
"USERINPUT"><b>SET CONSOLE SERIAL</b></tt>
</pre>
<p>before it goes for a serial console. Pulling the
keyboard from the machine is not sufficient, like it is
on most other Alpha models. Going back to a graphical
console needs</p>
<pre class="SCREEN">
&gt;&gt;&gt; <tt class=
"USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt>
</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 <i class="EMPHASIS">will not work</i>. 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>
<h3 class="SECT3"><a name="AEN162">2.3.2 Universal
Desktop Box (UDB or ``Multia'')</a></h3>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Multia can be either Intel or Alpha
CPU based. We assume Alpha based ones here for
obvious reasons.</p>
</blockquote>
</div>
<p>Multia is a small desktop box intended as a sort of
personal workstation. They come in a considerable
number of variations, check closely what you get.</p>
<p>Features:</p>
<ul>
<li>
<p>21066 Alpha CPU at 166 MHz or 21066A CPU at
233MHz</p>
</li>
<li>
<p>on-board Bcache / L2 cache: COAST-like 256 kByte
cache module; 233MHz models have 512kByte of cache;
166MHz models have soldered-on 256kB caches</p>
</li>
<li>
<p>PS/2 mouse &amp; keyboard port</p>
</li>
<li>
<p>memory:</p>
<ul>
<li>
<p>bus width: 64 bits</p>
</li>
<li>
<p>PS/2 style 72 pin 36 bit Fast Page Mode
SIMMs</p>
</li>
<li>
<p>70ns or better</p>
</li>
<li>
<p>SIMMs are installed in pairs of 2</p>
</li>
<li>
<p>4 SIMM sockets</p>
</li>
<li>
<p>uses ECC</p>
</li>
</ul>
<br>
<br>
</li>
<li>
<p>2 16550A serial ports</p>
</li>
<li>
<p>1 parallel port</p>
</li>
<li>
<p>floppy interface</p>
</li>
<li>
<p>Intel 82378ZB PCI to ISA bridge</p>
</li>
<li>
<p>1 embedded 21040 based 10Mbit Ethernet, AUI and
10base2 connector</p>
</li>
<li>
<p>expansion:</p>
<ul>
<li>
<p>1 32 bit PCI slot</p>
</li>
<li>
<p>2 PCMCIA slots</p>
</li>
</ul>
<br>
<br>
</li>
<li>
<p>on-board Crystal CS4231 or AD1848 sound chip</p>
</li>
<li>
<p>embedded Fast SCSI, using a Symbios 53C810[A]
chip on the PCI riser card</p>
</li>
</ul>
<br>
<br>
<p>Multia has enough Flash ROM to store both SRM and
ARC code at the same time and allow software selection
of one of them.</p>
<p>Multia has only one 32 bit PCI slot for expansion,
and it is only suitable for a small form factor PCI
card. By sacrificing the PCI slot space you can mount a
3.5" hard disk drive. Mounting stuff may have come with
your Multia. Adding a 3.5" disk is <i class=
"EMPHASIS">not</i> a recommended upgrade due to the
limited power rating of the power supply and the
extremely marginal cooling of the system box.</p>
<p>Multia also has 2 PCMCIA expansion slots. These are
currently not supported by FreeBSD.</p>
<p>The CPU might or might not be socketed, check this
before considering CPU upgrade hacks. The low-end
Multias have a soldered-in CPU.</p>
<p>It comes with a TGA based graphics on-board. TGA is
not currently suitable for console use with FreeBSD.
This means you will have to run Multia using a serial
console. Note that the boot of the installation disk
will appear to work fine using the TGA console, but
then switches to using the serial port. This is even
mentioned during by installer (but never read by the
human doing the install). Your keyboard appears dead
from that point on.</p>
<p>Multia has 2 serial ports but routes both of them to
the outside world on a single 25 pin sub-D connector.
The Multia FAQ explains how to build your own Y-cable
to allow both ports to be used.</p>
<p>Although the Multia SRM supports booting from floppy
this can be problematic. Typically the errors look
like:</p>
<pre class="SCREEN">
*** Soft Error - Error #10 - FDC: Data overrun or underrun
</pre>
<p>This is not a FreeBSD problem, it is a SRM problem.
The best available workaround to install FreeBSD is to
boot from a SCSI CDROM.</p>
<p>There have been reports that you sometimes need to
press <b class="KEYCAP">Control</b>-<b class=
"KEYCAP">Alt</b>-<b class="KEYCAP">Del</b> to capture
the SRM's attention. I have never seen this myself, but
it is worth trying when you are greeted by a blank
screen after powerup.</p>
<p>Sound works fine using <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pcm</span>(4)</span></a> driver and a
line in the kernel configuration file as follows for
the Crystal CS4231 chip:</p>
<pre class="PROGRAMLISTING">
device pcm0 at isa? port 0x530 irq 9 drq 3 flags 0x15
</pre>
<p>I have not yet been successful in getting my Multia
with the AD1848 to play any sound.</p>
<p>While verifying playback I was reminded of the lack
of CPU power of the 166MHz CPU. MP3 only plays
acceptable using 22kHz down-sampling.</p>
<p>Multias are somewhat notorious for dying of heat
strokes. The very compact box does not really allow
access to cooling air. Please use the Multia on its
vertical stand, don't put it horizontally (``pizza
style''). Replacing the fan with something which pushes
around more air is really recommended. You can also cut
one of the wires to the fan speed sensor. Once cut, the
fan runs at a (loud) full speed. Beware of PCI cards
with high power consumption. If your system has died
you might want to check the Multia-Heat-Death pages at
the <a href="http://www.netbsd.org/" target=
"_top">NetBSD Web site</a> for help in reviving it.</p>
<p>The Intel 82378ZB PCI to ISA bridge enables the use
of an IDE disk. This requires a line in the kernel
configuration file as follows:</p>
<pre class="PROGRAMLISTING">
device ata0 at isa? port IO_WD1 irq 14
</pre>
<p>The IDE connector pin spacing is thought for 2.5"
laptop disks. A 3.5" IDE disk would not fit in the case
anyway. At least not without sacrificing your only PCI
slot. The SRM console unfortunately does not know how
to boot from IDE disks. You will need to use a SCSI
disk as the bootdisk.</p>
<p>In case you want to change the internal hard drive:
the internal flat cable running from the PCI riser
board to the <i class="EMPHASIS">2.5"</i> hard drive
has a finer pitch than the standard SCSI flat cables.
Otherwise it would not fit on the 2.5" drives. There
are also riser cards that have a standard-pitch SCSI
cable attached to it, which will fit an ordinary SCSI
disk.</p>
<p>Again, I recommend against trying to cram a
replacement hard disk inside. Use the external SCSI
connector and put your disk in an external enclosure.
Multias run hot enough as-is. In most cases you will
have the external high density 50-pin SCSI connector
but some Multia models came without disk and may lack
the connector. Something to check before buying
one.</p>
<p>The kernel configuration file for a Multia kernel
must contain:</p>
<pre class="PROGRAMLISTING">
options DEC_AXPPCI_33
cpu EV4
</pre>
<p>Recommended reading on Multia can be found at <a
href="http://www.netbsd.org/Ports/alpha/multiafaq.html"
target=
"_top">http://www.netbsd.org/Ports/alpha/multiafaq.html</a>
or <a href=
"http://www.brouhaha.com/~eric/computers/udb.html"
target=
"_top">http://www.brouhaha.com/~eric/computers/udb.html</a>.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN247">2.3.3 Personal
Workstation (``Miata'')</a></h3>
<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 set</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>
<br>
<br>
</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>
<br>
<br>
</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 &amp; mouse port</p>
</li>
<li>
<p>USB interface [MiataGL only]</p>
</li>
<li>
<p>embedded sound based on an ESS1888 chip</p>
</li>
</ul>
<br>
<br>
<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 <tt class=
"USERINPUT"><b>set pci_device_override</b></tt> at the
SRM prompt. Just don't complain if your data
mysteriously gets mangled.</p>
<p>The complete command is:</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET PCI_DEVICE_OVERRIDE <tt class=
"REPLACEABLE"><i>&lt;vendor_id&gt;</i></tt><tt class=
"REPLACEABLE"><i>&lt;device_id&gt;</i></tt></b></tt>
</pre>
<p>For example:</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET PCI_DEVICE_OVERRIDE 88c15333</b></tt>
</pre>
<p>The most radical approach is to use:</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET PCI_DEVICE_OVERRIDE -1</b></tt>
</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>
<br>
<br>
<p>The FreeBSD kernel reports it when it sees a buggy
Pyxis chip:</p>
<pre class="SCREEN">
Sep 16 18:39:43 miata /kernel: cia0: Pyxis, pass 1
Sep 16 18:39:43 miata /kernel: cia0: extended capabilities: 1&lt;BWEN&gt;
Sep 16 18:39:43 miata /kernel: cia0: WARNING: Pyxis pass 1 DMA bug; no bets...
</pre>
<p>A MiataGL probes as:</p>
<pre class="SCREEN">
Jan 3 12:22:32 miata /kernel: cia0: Pyxis, pass 1
Jan 3 12:22:32 miata /kernel: cia0: extended capabilities: 1&lt;BWEN&gt;
Jan 3 12:22:32 miata /kernel: pcib0: &lt;2117x PCI host bus adapter&gt; on cia0
</pre>
<p>MiataGL does not have the DMA problems of the MX5.
PCI cards that make the MX5 SRM choke when installed in
the 64bit slots are accepted without problems by the
MiataGL SRM.</p>
<p>The latest mainboard revisions of MX5 contain a
hardware workaround for the bug. The SRM does not know
about the ECO and will complain about unknown cards as
before. So does the FreeBSD kernel by the way.</p>
<p>The Miata SRM can boot from IDE CDROM drives. IDE
harddisk 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 <i class="EMPHASIS">not</i>
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 <i class=
"EMPHASIS">same</i> 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.</p>
<p>Both MX5 and MiataGL have an on-board sound chip, an
ESS1888. It emulates a SoundBlaster and can be enabled
by putting</p>
<pre class="PROGRAMLISTING">
device pcm0
device sbc0
</pre>
<p>in your kernel configuration file:</p>
<p>in case your Miata has the optional cache board
installed make sure it is firmly seated. A slightly
loose cache has been observed to cause weird crashes
(not surprising obviously, but maybe not so obvious
when troubleshooting). The cache module is identical
between MX5 and MiataGL.</p>
<p>Installing a 2Mb cache module achieves, apart from a
10-15% speed increase (based on buildworld elapsed
time), a <i class="EMPHASIS">decrease</i> 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>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 <i class="EMPHASIS">even</i> 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>
<h3 class="SECT3"><a name="AEN356">2.3.4 DEC3000 family
(the ``Bird'' machines)</a></h3>
<p>The DEC3000 series were among the first Alpha
machines ever produced. They are based on an I/O bus
called the TurboChannel (TC) bus. These machines are
built like tanks (watch your back).</p>
<p>DEC3000 can be subdivided in DEC3000/500-class and
DEC3000/300-class. The DEC3000/500-class is the early
high-end workstation/server Alpha family. Servers use
serial consoles, workstations have graphics tubes.
DEC3000/300-class is the lower-cost workstation
class.</p>
<p>DEC3000/500-class are quite fast (considering their
age) thanks to the good memory design. DEC3000/300 is
crippled compared to DEC3000/500 because of its much
narrower memory bus.</p>
<p>They are called ``Birds'' because their internal DEC
code names were bird names:</p>
<div class="INFORMALTABLE">
<a name="AEN364"></a>
<table border="1" class="CALSTABLE">
<tbody>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/400</td>
<td width="25%" align="LEFT" valign="TOP">
Sandpiper</td>
<td width="50%" align="LEFT" valign="TOP">
133MHz CPU, desktop</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/500</td>
<td width="25%" align="LEFT" valign="TOP">
Flamingo</td>
<td width="50%" align="LEFT" valign="TOP">
150MHz CPU, floor standing</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/500X</td>
<td width="25%" align="LEFT" valign="TOP">Hot
Pink</td>
<td width="50%" align="LEFT" valign="TOP">
200MHz CPU, floor standing</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/600</td>
<td width="25%" align="LEFT" valign="TOP">
Sandpiper+</td>
<td width="50%" align="LEFT" valign="TOP">
175MHz CPU, desktop</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/700</td>
<td width="25%" align="LEFT" valign="TOP">
Sandpiper45</td>
<td width="50%" align="LEFT" valign="TOP">
225MHz CPU, floor standing</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/800</td>
<td width="25%" align="LEFT" valign="TOP">
Flamingo Ultra</td>
<td width="50%" align="LEFT" valign="TOP">
200MHz CPU, floor standing</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/900</td>
<td width="25%" align="LEFT" valign="TOP">
Flamingo45</td>
<td width="50%" align="LEFT" valign="TOP">
275MHz CPU, floor standing</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/300</td>
<td width="25%" align="LEFT" valign="TOP">
Pelican</td>
<td width="50%" align="LEFT" valign="TOP">
150MHz CPU, desktop, 2 TC slots</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/300X</td>
<td width="25%" align="LEFT" valign="TOP">
Pelican+</td>
<td width="50%" align="LEFT" valign="TOP">
175MHz CPU, desktop, 2 TC slots</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/300LX</td>
<td width="25%" align="LEFT" valign="TOP">
Pelican+</td>
<td width="50%" align="LEFT" valign="TOP">
125MHz CPU, desktop, 2 TC slots</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
DEC3000/300L</td>
<td width="25%" align="LEFT" valign="TOP">
&nbsp;</td>
<td width="50%" align="LEFT" valign="TOP">
100MHz CPU, desktop, no TC slots</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
<p>Features:</p>
<ul>
<li>
<p>21064 CPU (100 to 200 MHz) or 21064A CPU (225 to
275 MHz)</p>
</li>
<li>
<p>memory DEC3000/500 class:</p>
<ul>
<li>
<p>bus width: 256 bit, with ECC</p>
</li>
<li>
<p>proprietary 100pin SIMMs</p>
</li>
<li>
<p>installed in sets of 8</p>
</li>
</ul>
<br>
<br>
</li>
<li>
<p>memory DEC3000/300 class:</p>
<ul>
<li>
<p>bus width: 64 bit, with ECC</p>
</li>
<li>
<p>PS/2 style 72pin 36 bit FPM SIMMs 70ns or
better</p>
</li>
<li>
<p>used in pairs of 2</p>
</li>
</ul>
<br>
<br>
</li>
<li>
<p>Bcache / L2 cache: varying sizes, 512 kB to 2
Mbyte</p>
</li>
<li>
<p>built-in 10Mbit Ethernet based on a Lance 7990
chip, AUI and UTP</p>
</li>
<li>
<p>one or two SCSI buses based on a NCR53C94 or a
NCR53CF94-2 chip</p>
</li>
<li>
<p>2 serial ports based on Zilog 8530 (one usable
as a serial console)</p>
</li>
<li>
<p>embedded ISDN interface</p>
</li>
<li>
<p>on-board 8 bit sound</p>
</li>
<li>
<p>8 bit graphics on-board or via a TC card
(depending on model)</p>
</li>
</ul>
<br>
<br>
<p>Currently DEC3000 machines can only be used diskless
on FreeBSD. The reason for this is that the SCSI
drivers needed for the TC SCSI adapters were not
brought into CAM that the recent FreeBSD versions use.
TC option cards for single (PMAZ-A) or dual fast SCSI
(PMAZC-AA) are also available. These cards currently
have no drivers on FreeBSD either.</p>
<p>&#13;</p>
<p>DEC3000/300 has 5 MBytes/sec SCSI on-board. This bus
is used for both internal and external devices.
DEC3000/500 has 2 SCSI buses. One is for internal
devices only, the other one is for external devices
only.</p>
<p>&#13;</p>
<p>Floppy devices found in the DEC3000s are attached to
the SCSI bus (via a bridge card). This makes it
possible to boot from them using the same device names
as ordinary SCSI hard-disks, for example:</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>BOOT DKA300</b></tt>
</pre>
<p>The 3000/300 series has a half-speed TurboChannel
compared to the other 3000 machines. Some TC expansion
cards have troubles with the half-speed bus. Caveat
emptor.</p>
<p>The embedded ISDN interface is not supported on
FreeBSD.</p>
<p>DEC3000/300-class uses standard 36 bit, 72 pin Fast
Page Mode SIMMs. EDO SIMMs, 32 or 33 bit SIMMs all will
not work in Pelicans. For 32Mbyte SIMMs to work on the
DEC3000/300-class the presence detect bits/pins of the
SIMM must correspond to what the machine expects. If
they don't, the SIMM is ``seen'' as a 8 Mbyte SIMM. 8
Mbyte and 32 Mbyte SIMMs can be mixed, as long as the
pairs themselves are identical.</p>
<p>When you find yourself in need of fixing 32Mbyte
SIMMs that lack correct presence bits the following
info might be of use:</p>
<p>There are four presence detection bits on PS/2
SIMMs. Two of the bits indicate the access time. The
other two indicate the memory size.</p>
<p>At one end of the SIMM there are two rows of four
solder pads. One row is connected to Vss (GND) and the
other is connected to pins 67 (PRD1), 68 (PRD2), 69
(PRD3), 70 (PRD4).</p>
<p>If you bridge a pair of pads with a small resistor
or a drop of solder you ground that particular bit.</p>
<div class="INFORMALTABLE">
<a name="AEN466"></a>
<table border="1" class="CALSTABLE">
<thead>
<tr>
<th width="25%" align="LEFT" valign="TOP">
PRD1</th>
<th width="25%" align="LEFT" valign="TOP">
PRD2</th>
<th width="50%" align="LEFT" valign="TOP">
Memory Size</th>
</tr>
</thead>
<tbody>
<tr>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="50%" align="LEFT" valign="TOP">4 or
64 Mbyte</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="50%" align="LEFT" valign="TOP">2 or
32 Mbyte</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="50%" align="LEFT" valign="TOP">1 or
16 Mbyte</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="50%" align="LEFT" valign="TOP">8
Mbyte</td>
</tr>
</tbody>
</table>
</div>
<div class="INFORMALTABLE">
<a name="AEN493"></a>
<table border="1" class="CALSTABLE">
<thead>
<tr>
<th width="25%" align="LEFT" valign="TOP">
PRD3</th>
<th width="25%" align="LEFT" valign="TOP">
PRD4</th>
<th width="50%" align="LEFT" valign="TOP">
Access Time</th>
</tr>
</thead>
<tbody>
<tr>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="50%" align="LEFT" valign="TOP">50 or
100 nsec</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="50%" align="LEFT" valign="TOP">80
nsec</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
GND</td>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="50%" align="LEFT" valign="TOP">70
nsec</td>
</tr>
<tr>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="25%" align="LEFT" valign="TOP">
Open</td>
<td width="50%" align="LEFT" valign="TOP">60
nsec</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
<p>DEC3000/500-class can use 2, 4, 8, 16 and 32 Mbyte
100pin SIMMs. Note that the maximum memory size varies
from system to system, desktop machines have sacrificed
box size for less memory SIMM sockets. Given enough
sockets and enough SIMMs you can get to 512 Mbytes
maximum. This is one of the main differences between
floor standing and desktop machines, the latter have
far less SIMM sockets.</p>
<p>The sound hardware is not supported on any of the
Birds.</p>
<p>There is no X-Windows version available for the TC
machines. DEC3000/300 needs a serial console.
DEC3000/500-class might work with a graphical console.
I ran mine with a serial console so I cannot verify
this.</p>
<p>Birds can be obtained from surplus sales etc. As
they are not PCI based they are no longer actively
maintained. TC expansion boards can be difficult to
obtain these days and support for them is not too good
unless you write/debug the code yourself. Programming
information for TC boards is hard to find. Birds are
recommended only if a. you can get them cheap and b. if
you prepared to work on the code to support them
better.</p>
<p>For the DEC3000/[4-9]00 series machines the kernel
config file must contain:</p>
<pre class="PROGRAMLISTING">
options DEC_3000_500
cpu EV4
</pre>
<p>For the DEC3000/300 (``Pelican'') machines the
kernel config file must contain:</p>
<pre class="PROGRAMLISTING">
options DEC_3000_300
cpu EV4
</pre>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN529">2.3.5 Evaluation
Board 64plus (``EB64+''), Aspen Alpine</a></h3>
<p>In its attempts to popularize the Alpha CPU DEC
produced a number of so called Evaluation Boards. 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>
<br>
<br>
</li>
<li>
<p>Bcache / L2 cache: 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>Symbios 53C810 Fast-SCSI</p>
</li>
<li>
<p>embedded 10 Mbit Ethernet</p>
</li>
<li>
<p>2 PCI slots</p>
</li>
<li>
<p>3 ISA slots</p>
</li>
</ul>
<br>
<br>
<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 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>For the EB64+ class machines the kernel config file
must contain:</p>
<pre class="PROGRAMLISTING">
options DEC_EB64PLUS
cpu EV4
</pre>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN576">2.3.6 Evaluation
Board 164 (``EB164, PC164, PC164LX, PC164SX'')
family</a></h3>
<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>21174 (Alcor) chip set</p>
</li>
<li>
<p>Bcache / L3 cache: EB164 uses special
cache-SIMMs</p>
</li>
<li>
<p>memory bus: 128 bit / 256 bit</p>
</li>
<li>
<p>memory:</p>
<ul>
<li>
<p>PS/2 style SIMMs in sets of 4 or 8</p>
</li>
<li>
<p>36 bit, Fast Page Mode, uses ECC, [EB164 /
PC164]</p>
</li>
<li>
<p>SDRAM DIMMs in sets of 2, uses ECC [PC164SX
/ PC164LX]</p>
</li>
</ul>
<br>
<br>
</li>
<li>
<p>2 16550A serial ports</p>
</li>
<li>
<p>PS/2 style keyboard &amp; 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>
<br>
<br>
<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.</p>
<p>The SRM can boot from Qlogic 10xx boards or the
Symbios 53C810[A]. Newer Symbios 810 revisions like the
Symbios 810AE are not recognized by the SRM on PC164.
PC164 SRM does not appear to recognize a Symbios 53C895
based host adapter (tested with a Tekram DC-390U2W). On
the other hand some no-name Symbios 53C985 board has
been reported to work. Cards like the Tekram DC-390F
(Symbios875 based) have been confirmed to work fine on
the PC164. Unfortunately this seems to be dependent on
the actual version of the chip/board.</p>
<p>Symbios 53C825[a] will also work as boot adapter.
Diamond FirePort, although based on Symbios chips, is
not bootable by the PC164SX SRM. PC164SX is reported to
boot fine with Symbios825, Symbios875 and Symbios876
based cards. In addition, Adaptec 2940U and 2940UW are
reported to work for booting (verified on SRM V5.7-1).
Adaptec 2930U2 and 2940U2[W] do not work.</p>
<p>164LX and 164SX with SRM firmware version 5.8 or
later can boot from Adaptec 2940-series adapters.</p>
<p>In summary: this family of machines is ``blessed''
with a challenging compatibility as far as SCSI
adapters go.</p>
<p>On PC164 the SRM sometimes seems to loose its
variable settings. ``For PC164, current superstition
says that, to avoid losing settings, you want to first
downgrade to SRM 4.x and then upgrade to 5.x.'' One
sample error that was observed was:</p>
<pre class="SCREEN">
ERROR: ISA table corrupt!
</pre>
<p>A sequence of a downgrade to SRM4.9, an</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>ISACFG -INIT</b></tt>
</pre>
<p>followed by</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>INIT</b></tt>
</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 it's 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>
<h3 class="SECT3"><a name="AEN640">2.3.7 AlphaStation
200 (``Mustang'') and 400 (``Avanti'') series</a></h3>
<p>The Digital AlphaStation 200 and 400 series systems
are early low end PCI based workstations. The 200 and
250 series are desktop boxes, the 400 series is a
desk-side mini-tower.</p>
<p>Features:</p>
<ul>
<li>
<p>21064 or 21064A CPU at speeds of 166 up to 333
MHz</p>
</li>
<li>
<p>DECchip 21071-AA core logic chip-set</p>
</li>
<li>
<p>Bcache / L2 cache: 512 Kbytes (200 and 400
series) or 2048KBytes (250 series)</p>
</li>
<li>
<p>memory:</p>
<ul>
<li>
<p>64 bit bus width</p>
</li>
<li>
<p>8 to 384 MBytes of RAM</p>
</li>
<li>
<p>70 ns or better Fast Page DRAM</p>
</li>
<li>
<p>in three pairs (200 and 400 series)</p>
</li>
<li>
<p>in two quads, so banks of four. (250
series)</p>
</li>
<li>
<p>the memory subsystem uses parity</p>
</li>
</ul>
<br>
<br>
</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 &amp; 250-series)</p>
</li>
<li>
<p>ISA expansion slots (4 for the AS400-series, 2
for the AS200 &amp; 250-series) (some ISA/PCI slots
are physically shared)</p>
</li>
<li>
<p>embedded 21040-based Ethernet (200 &amp; 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 &amp; 250 series)</p>
</li>
</ul>
<br>
<br>
<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 &amp; AS250 sound hardware is reported to
work OK assuming you have the following line in your
kernel config file:</p>
<pre class="PROGRAMLISTING">
device pcm0 at isa? port 0x530 irq 9 drq 0 flags 0x10011
</pre>
<p>AlphaStation 200 &amp; 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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET CONTROL_SCSI_TERM EXTERNAL</b></tt>.
</pre>
<p>If only internal SCSI devices are present use:</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET CONTROL_SCSI_TERM INTERNAL</b></tt>
</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>
<h3 class="SECT3"><a name="AEN705">2.3.8 AlphaStation
500 and 600 (``Alcor'' &amp; ``Maverick'' for EV5,
``Bret'' for EV56)</a></h3>
<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>
<p></p>
</li>
<li>
<p>21171 or 21172 (Alcor) 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>
<br>
<br>
</li>
<li>
<p>memory buswidth: 256 bits</p>
</li>
<li>
<p>AS500 memory:</p>
<ul>
<li>
<p>industry standard 72 bit wide buffered
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>
<br>
<br>
</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>
<br>
<br>
</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>
<br>
<br>
</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>
<br>
<br>
</li>
</ul>
<br>
<br>
</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>
<br>
<br>
<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. +++ This is what some DEC docs suggest. Did
they ever go UltraSCSI?</p>
<p>AS600 has one Qlogic SCSI chip dedicated to the
internal devices whereas the other Qlogic SCSI chip is
dedicated to external SCSI devices.</p>
<p>In AS500 DIMMs are installed in sets of 4, in
``physically interleaved'' layout. So, a bank of 4
DIMMs is <i class="EMPHASIS">not</i> 4 physically
adjacent 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>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>
<h3 class="SECT3"><a name="AEN808">2.3.9 AlphaServer
1000 (``Mikasa''), 1000A (``Noritake'') and
800</a></h3>
<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>
<br>
<br>
</li>
<li>
<p>AS800: Uses 60ns 3.3Volts EDO DIMMs</p>
</li>
</ul>
<br>
<br>
</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>
<br>
<br>
<p>AS1000 based machines come in multiple enclosure
types. Floor standing, rack-mount, with or without
StorageWorks SCSI chassis etc. The electronics are the
same.</p>
<p>AS1000-systems: All EV4 based machines use standard
PS/2 style 36 bit 72pin SIMMs in sets of 5. The fifth
SIMM is used for ECC. All EV5 based machines use
standard PS/2 style 36 bit 72pin SIMMs in sets of 4.
The ECC is done based on the 4 extra bits per SIMM (4
bits out of 36). The EV5 mainboards have 16 SIMM slots,
the EV4 mainboards have 20 slots.</p>
<p>AS800 machines use DIMMs in sets of 4. DIMM
installation must start in slots marked bank 0. A bank
is four physically adjacent slots. The biggest size
DIMMs must be installed in bank 0 in case 2 banks of
different DIMM sizes are used. Max memory size is 2GB.
Note that these are EDO DIMMs.</p>
<p>The AS1000/800 are somewhat stubborn when it comes
to serial consoles. They need</p>
<pre class="SCREEN">
&gt;&gt;&gt; <tt class=
"USERINPUT"><b>SET CONSOLE SERIAL</b></tt>
</pre>
<p>before they go for a serial console. Pulling the
keyboard from the machine is not sufficient, like it is
on most other Alpha models. Going back to a graphical
console needs</p>
<pre class="SCREEN">
&gt;&gt;&gt; <tt class=
"USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt>
</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>
<h3 class="SECT3"><a name="AEN863">2.3.10
DS10/VS10/XP900 (``Webbrick'') / XP1000 (``Monet'') /
DS10L (``Slate'')</a></h3>
<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>
<h4 class="SECT4"><a name="AEN869">2.3.10.1
``Webbrick / Slate''</a></h4>
<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 bandwith</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>
<br>
<br>
</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 &amp; 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>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.</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 disabled by
Compaq.</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&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">config</span>(8)</span></a>
happy.</p>
</blockquote>
</div>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN931">2.3.10.2
``Monet''</a></h4>
<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>
<br>
<br>
</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 &amp; 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 <tt class=
"VARNAME">usb_enable</tt> is set to <tt class=
"LITERAL">on</tt>. You can change this by
performing:</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET USB_ENABLE ON</b></tt>
</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&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">config</span>(8)</span></a>
happy.</p>
</blockquote>
</div>
</div>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN1011">2.3.11 DS20/DS20E
(``Goldrush'')</a></h3>
<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>
<br>
<br>
</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>
<br>
<br>
</li>
</ul>
<br>
<br>
<p>DS20 needs</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET CONSOLE SERIAL</b></tt>
</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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt>
</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 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.</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&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">config</span>(8)</span></a>
happy.</p>
</blockquote>
</div>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN1076">2.3.12 AlphaPC
264DP / UP2000</a></h3>
<p>UP2000 is built by Alpha Processor Inc.</p>
<p>Features:</p>
<ul>
<li>
<p>21264 EV6 CPU at 670 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>embedded Adaptec AIC7890/91 Wide Ultra SCSI</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>
<br>
<br>
</li>
</ul>
<br>
<br>
<p>Currently a maximum of 2GB memory is supported by
FreeBSD.</p>
<p>The on-board Adaptec is not bootable but works with
FreeBSD 4.0 and later as a datadisk-only SCSI bus.</p>
<p>Busmaster DMA is supported on the first IDE
interface only.</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&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">config</span>(8)</span></a>
happy.</p>
</blockquote>
</div>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN1122">2.3.13 AlphaServer
2000 (``DemiSable''), 2100 (``Sable''), 2100A
(``Lynx'')</a></h3>
<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 &amp; 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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>CLEAR_ERROR ALL</b></tt>
</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
1Mb x36 bit (4 Mbyte) and 4Mb 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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET CONSOLE SERIAL</b></tt>
</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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt>
</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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET OCP_TEXT "FreeBSD"
</b></tt>
</pre>
<p>The SRM</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SHOW FRU</b></tt>
</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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SHOW PKA0_FAST</b></tt>
</pre>
<p>When set to 1 it is negotiating for Fast speeds.</p>
<pre class="SCREEN">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>SET PKA0_FAST 1</b></tt>
</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">
<tt class="PROMPT">&gt;&gt;&gt;</tt> <tt class=
"USERINPUT"><b>RUNECU</b></tt>
</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>
<h3 class="SECT3"><a name="AEN1193">2.3.14 AlphaServer
4x00 (``Rawhide'')</a></h3>
<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.
This is medium iron, not a typical hobbyist system.
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 MHz or 21164A EV56
CPUs at 400, 466, 533, 600 and 666 Mhz</p>
</li>
<li>
<p>cache: 4 Mbytes per CPU. EV5 300 MHz was also
available cache-less. 8 Mbytes for EV5 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 &amp; mouse port</p>
</li>
</ul>
<br>
<br>
<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 Rawhide has 4 pairs
of memory modules. Given the choice use SDRAM for best
performance. The highest capacity memory board must be
in memory slot 0. A mix of memory board sizes is
allowed. A mix of EDO and SDRAM is also reported as
working (assuming you don't try to mix EDO and SDRAM in
one module pair). A mix of EDO and SDRAM results in the
<i class="EMPHASIS">entire</i> memory subsystem running
at the slower EDO timing</p>
<p>Rawhide has an embedded Symbios 810 chip that gives
you a narrow fast-SCSI bus. Generally only the SCSI
CDROM is driven by this interface.</p>
<p>Rawhides are available with a 8 64-bit PCI / 3 EISA
slot expansion backplanes (called ``Saddle'' modules).
There are 2 separate PCI buses, PCI0 and PCI1. PCI0 has
1 dedicated PCI slot and (shared) 3 PCI/EISA slots.
PCI0 also has a PCI/EISA bridge that drives things like
the serial and parallel ports, keyboard/mouse etc. PCI1
has 4 PCI slots and an Symbios 810 SCSI chip. VGA
console cards must be installed in a slot connected to
PCI0.</p>
<p>The current FreeBSD implementation has problems in
handling PCI bridges. There is currently a limited fix
in place which allows for single level, single device
PCI bridges. The fix allows the use of the Digital
supplied Qlogic SCSI card which sits behind a 21054 PCI
bridge chip.</p>
<p>&#13;</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 OK as a console.</p>
</blockquote>
</div>
<br>
<br>
<p>Rawhide 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.</p>
<p>The kernel config file must contain:</p>
<pre class="PROGRAMLISTING">
options DEC_KN300
cpu EV5
</pre>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN1226">2.3.15 AlphaServer
1200 (``Tincup'') and AlphaStation 1200
(``DaVinci'')</a></h3>
<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 &amp; mouse port</p>
</li>
</ul>
<br>
<br>
<p>AS1200 uses 2 memory daughter cards. On each of
these cards are 8 DIMM slots. DIMMs must be installed
in pairs. The maximum memory size is 4 GBytes. Slots
must be filled in order and slot 0 must contain the
largest size DIMM if different sized DIMMs are used.
AS1200 employs fixed starting addresses for DIMMs, each
DIMM pair starts at a 512 Mbyte boundary. This means
that if DIMMs smaller than 256 Mbyte are used the
system's physical memory map will contain ``holes''.
Supported DIMM sizes are 64 Mbytes and 256 Mbytes. The
DIMMs are 72 bit SDRAM based, as the system employs
ECC.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> FreeBSD currently supports up to
2GBytes</p>
</blockquote>
</div>
<p>AS1200 has an embedded Symbios 810 drive Fast SCSI
bus.</p>
<p>Tincup has 5 64-bit PCI slots, one 1 32-bit PCI slot
and one EISA slot (which is physically shared with one
of the 64-bit PCI slots). There are 2 separate PCI
buses, PCI0 and PCI1. PCI0 has the 32-bit PCI slot and
the 2 top-most 64-bit PCI slots. PCI0 also has an Intel
82375EB PCI/EISA bridge that drives things like the
serial and parallel ports, keyboard/mouse etc. PCI1 has
4 64-bit PCI slots and an Symbios 810 SCSI chip. VGA
console cards must be installed in a slot connected to
PCI0.</p>
<p>The system employs an I2C based power controller
system. If you want to be sure all power is removed
from the system remove the mains cables from the
system. Tincup uses dual power supplies in load-sharing
mode and not as a redundancy pair.</p>
<p>The kernel config file must contain:</p>
<pre class="PROGRAMLISTING">
options DEC_KN300
cpu EV5
</pre>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN1256">2.3.16 AlphaServer
8200 and 8400 (``TurboLaser'')</a></h3>
<p>The AlphaServer 8200 and 8400 machines are
enterprise servers. Expect a tall 19" cabinet (8200) or
fat (8400) 19" rack. This is big iron, not a hobbyist
system. TurboLasers are multi-CPU machines, up to 12
CPUs can be in a single machine. The TurboLaser System
Bus (TLSB) allows 9 nodes on the AS8400 and 5 nodes on
the AS8200. TLSB is 256 bit data, 40 bit address
allowing 2.1 GBytes/sec. Nodes on the TLSB can be CPUs,
memory or I/O. A maximum of 3 I/O ports are supported
on a TLSB.</p>
<p>Basic disk storage is housed in a StorageWorks
shelf. AS8400 uses 3 phase power, AS8200 uses single
phase power.</p>
<p>Features:</p>
<ul>
<li>
<p>21164 EV5/EV56 CPUs at up to 467 MHz or 21264
EV67 CPUs at up to 625 MHz</p>
</li>
<li>
<p>one or two CPUs per CPU module</p>
</li>
<li>
<p>cache: 4Mbytes B-cache per CPU</p>
</li>
<li>
<p>memory bus: 256 bit with ECC</p>
</li>
<li>
<p>memory: big memory modules that plug into the
TLSB, which in turn hold special SIMM modules.
Memory modules come in varying sizes, up to 4
GBytes a piece. Uses ECC (8 bits per 64 bits of
data) 7 memory modules max for AS8400, 3 modules
max for AS8200. Maximum memory is 28 GBytes.</p>
</li>
<li>
<p>expansion: 3 system ``I/O ports'' that allow up
to 12 I/O channels each I/O channel can connect to
XMI, Futurebus+ or PCI boxes</p>
</li>
</ul>
<br>
<br>
<p>FreeBSD supports (and has been tested with) up to 2
GBytes of memory on TurboLaser. There is a trade-off to
be made between TLSB slots occupied by memory modules
and TLSB slots occupied by CPU modules. For example you
can have 28GBytes of memory but only 2 CPUs (1 module)
at the same time.</p>
<p>Only PCI expansion is supported on FreeBSD. XMI or
Futurebus+ (which are AS8400 only) are both
unsupported.</p>
<p>The I/O port modules are designated KFTIA or KFTHA.
The I/O port modules supply so called ``hoses'' that
connect to up to 4 (KFTHA) PCI buses or 1 PCI bus
(KFTIA). KFTIA has embedded dual 10baseT Ethernet,
single FDDI, 3 SCSI Fast Wide Differential SCSI buses
and a single Fast Wide Single Ended SCSI bus. The FWSE
SCSI is intended for the CDROM.</p>
<p>KFTHA can drive via each of its 4 hoses a DWLPA or
DWLPB box. The DWLPx house a 12 slots 32 bit PCI
backplane. Physically the 12 slots are 3 4-slot buses
but to the software it appears as a single 12 slots PCI
bus. A fully expanded AS8x00 can have 3 (I/O ports)
times 4 (hoses) times 12 (PCI slots/DWLPx) = 144 PCI
slots. The maximum bandwidth per KFTHA is 500
Mbytes/second. DWLPA can also house 8 EISA cards, 2
slots are PCI-only, 2 slots are EISA only. Of the 12
slots 2 are always occupied by an I/O and connector
module. DWLPB are the prefered I/O boxes.</p>
<p>For best performance distribute high bandwidth
(FibreChannel, Gigabit Ethernet) over multiple hoses
and/or multiple KFTHA/KFTIA.</p>
<p>Currently PCI expansion cards containing PCI bridges
are not usable with FreeBSD. Don't use them at this
time.</p>
<p>The single ended narrow SCSI bus on the KFTIA will
turn up as the <i class="EMPHASIS">fourth</i> SCSI bus.
The 3 fast-wide differential SCSI buses of the KFTIA
precede it.</p>
<p>AS8x00 are generally run with serial consoles. Some
newer machines might have a graphical console of some
sorts but FreeBSD has only been tested on a serial
console.</p>
<p>For serial console usage either change <tt class=
"FILENAME">/etc/ttys</tt> to have:</p>
<pre class="PROGRAMLISTING">
console "/usr/libexec/getty std.9600" unknown on secure
</pre>
<p>as the console entry, or add</p>
<pre class="PROGRAMLISTING">
zs0 "/usr/libexec/getty std.9600" unknown on secure
</pre>
<p>For the AlphaServer 8x00 machines the kernel config
file must contain:</p>
<pre class="PROGRAMLISTING">
options DEC_KN8AE # Alpha 8200/8400 (Turbolaser)
cpu EV5
</pre>
<p>Contrary to expectation there is no <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&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">config</span>(8)</span></a> happy.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN1299">2.3.17 Alpha
Processor Inc. UP1000</a></h3>
<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 &amp; 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>
<br>
<br>
</li>
</ul>
<br>
<br>
<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 <i class=
"EMPHASIS">2</i>. 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 &amp; cpu. But as always you
will have to take your expansion cards and peripherals
into account. The M1543C chip contains power management
functionality &amp; 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. website. 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>
<h3 class="SECT3"><a name="AEN1348">2.3.18 Alpha
Processor Inc. UP1100</a></h3>
<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 &amp; 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>
<br>
<br>
<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 <i class=
"EMPHASIS">2</i>. 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 &amp; cpu. But as always you
will have to take your expansion cards and peripherals
into account. The M1535D chip contains power management
functionality &amp; 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&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">config</span>(8)</span></a> happy.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN1396">2.3.19 Alpha
Processor Inc. CS20</a></h3>
<p>The CS20 is a 19", 1U high rackmount server based on
the 21264[ab] CPU. It can have a maximum of 2 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 &amp; 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>
<br>
<br>
<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
<i class="EMPHASIS">buffered</i> 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 it's 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&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">config</span>(8)</span></a> happy.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1443">2.4 Supported
Hardware Overview</a></h2>
<p>A word of caution: the installed base for FreeBSD is
not nearly as large as for FreeBSD/Intel. This means that
the enormous variation of PCI/ISA expansion cards out
there has much less chance of having been tested on alpha
than on Intel. This is not to imply they are doomed to
fail, just that the chance of running into something
never tested before is much higher. <tt class=
"FILENAME">GENERIC</tt> contains things that are known to
work on Alpha only.</p>
<p>The PCI and ISA expansion busses are fully supported.
Turbo Channel is not in <tt class="FILENAME">GENERIC</tt>
and has limited support (see the relevant machine model
info). The MCA bus is not supported. The EISA bus is not
supported for use with EISA expansion cards as the EISA
support code is lacking. ISA cards in EISA slots are
reported to work. The Compaq Qvision EISA VGA card is
driven in ISA mode and works OK as a console.</p>
<p>1.44 Mbyte and 1.2 Mbyte floppy drives are supported.
2.88 Mbyte drives sometimes found in Alpha machines are
supported up to 1.44Mbyte.</p>
<p>ATA and ATAPI (IDE) devices are supported via the <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4">
<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. Be aware of the machine-specific boot-ability
issues for the various adapter types.</p>
<p>The Qlogic QL2x00 FibreChannel host adapters are fully
supported.</p>
<p>If you want to boot your Alpha over the Ethernet you
will obviously need an Ethernet card that the SRM console
recognizes. This generally means you need a board with an
21x4x Ethernet chip as that is what Digital used. These
chips are driven by the FreeBSD <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=de&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">de</span>(4)</span></a> (older driver) or
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> (newer driver).
Some new SRM versions are known to recognize the Intel
8255x Ethernet chips as driven by the FreeBSD <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span></a> driver. But
beware: the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span></a> driver is
reported not to work correctly with FreeBSD (although it
works excellently on FreeBSD/x86).</p>
<p>DEC DEFPA PCI FDDI network adapters are supported on
alpha.</p>
<p>In general the SRM console emulates a
VGA-compatibility mode on PCI VGA cards. This is,
however, not guaranteed to work by Compaq/DEC for each
and every card type out there. When the SRM thinks the
VGA is acceptable FreeBSD will be able to use it. The
console driver works just like on a FreeBSD/intel
machine. The TGA video graphics which is embedded on for
example Multia does <i class="EMPHASIS">not</i> work with
FreeBSD. TGA based PCI cards are also <i class=
"EMPHASIS">not</i> supported. Please note that VESA modes
are not supported on Alpha, so that leaves you with 80x25
consoles.</p>
<p>The ``PC standard'' serial ports found on most Alphas
are supported. For TurboChannel machines the serial ports
are also supported.</p>
<p>ISDN (i4b) is not supported on FreeBSD/alpha.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1476">2.5
Acknowledgments</a></h2>
<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 <tt class="EMAIL">&lt;<a href=
"mailto:gallatin@FreeBSD.org">gallatin@FreeBSD.org</a>&gt;</tt></p>
</li>
<li>
<p>Chuck Robey <tt class="EMAIL">&lt;<a href=
"mailto:chuckr@FreeBSD.org">chuckr@FreeBSD.org</a>&gt;</tt></p>
</li>
<li>
<p>Matthew Jacob <tt class="EMAIL">&lt;<a href=
"mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;</tt></p>
</li>
<li>
<p>Michael Smith <tt class="EMAIL">&lt;<a href=
"mailto:msmith@FreeBSD.org">msmith@FreeBSD.org</a>&gt;</tt></p>
</li>
<li>
<p>David O'Brien <tt class="EMAIL">&lt;<a href=
"mailto:obrien@FreeBSD.org">obrien@FreeBSD.org</a>&gt;</tt></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>
<br>
<br>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN1517">3 Supported
Devices</a></h1>
$FreeBSD:
src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v
1.13.2.14 2001/09/06 23:17:00 bmah Exp $
<p>This section describes the devices currently known to be
supported by with FreeBSD on the alpha platform. Other
configurations may also work, but simply have not been
tested yet. Feedback, updates, and corrections to this list
are encouraged.</p>
<p>Where possible, the drivers applicable to each device or
class of devices is listed. If the driver in question has a
manual page in the FreeBSD base distribution (most should),
it is referenced here.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1523">3.1 Disk
Controllers</a></h2>
<p>IDE/ATA controllers (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ata</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Acerlabs Aladdin</p>
</li>
<li>
<p>AMD 756</p>
</li>
<li>
<p>CMD 646, 648 ATA66, and 649 ATA100</p>
</li>
<li>
<p>Cypress 82C693</p>
</li>
<li>
<p>Cyrex 5530</p>
</li>
<li>
<p>HighPoint HPT366, HPT370</p>
</li>
<li>
<p>Intel PIIX, PIIX3, PIIX4</p>
</li>
<li>
<p>Intel ICH, ICH2</p>
</li>
<li>
<p>Promise ATA100 OEM chip (pdc20265)</p>
</li>
<li>
<p>Promise Fasttrak-33, -66, -100</p>
</li>
<li>
<p>Promise Ultra-33, -66, -100</p>
</li>
<li>
<p>ServerWorks ROSB4 ATA33</p>
</li>
<li>
<p>SiS 5591</p>
</li>
<li>
<p>VIA 82C586, 82C686a, 82C686b</p>
</li>
</ul>
<br>
<br>
<p>Adaptec SCSI Controllers</p>
<ul>
<li>
<p>Adaptec 1535 ISA SCSI controllers</p>
</li>
<li>
<p>Adaptec 154x series ISA SCSI controllers (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=aha&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">aha</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Adaptec
19160/274x/284x/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x
series EISA/VLB/PCI SCSI controllers, including
Narrow/Wide/Twin/Ultra/Ultra2 variants (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ahc</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Adaptec AIC7770, AIC7850, AIC7860, AIC7870,
AIC7880, and AIC789x on-board SCSI controllers (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ahc</span>(4)</span></a> driver)</p>
</li>
</ul>
<br>
<br>
<p>AdvanSys SCSI controllers (all models, <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=adv&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">adv</span>(4)</span></a> and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=adw&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">adw</span>(4)</span></a> drivers)</p>
<p>BusLogic MultiMaster ``W'' Series Host Adapters (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bt</span>(4)</span></a> driver):</p>
<ul>
<li>
<p>BT-948</p>
</li>
<li>
<p>BT-958</p>
</li>
<li>
<p>BT-958D</p>
</li>
</ul>
<br>
<br>
<p>BusLogic MultiMaster ``C'' Series Host Adapters (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bt</span>(4)</span></a> driver):</p>
<ul>
<li>
<p>BT-946C</p>
</li>
<li>
<p>BT-956C</p>
</li>
<li>
<p>BT-956CD</p>
</li>
<li>
<p>BT-445C</p>
</li>
<li>
<p>BT-747C</p>
</li>
<li>
<p>BT-757C</p>
</li>
<li>
<p>BT-757CD</p>
</li>
<li>
<p>BT-545C</p>
</li>
<li>
<p>BT-540CF</p>
</li>
</ul>
<br>
<br>
<p>BusLogic MultiMaster ``S'' Series Host Adapters (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bt</span>(4)</span></a> driver):</p>
<ul>
<li>
<p>BT-445S</p>
</li>
<li>
<p>BT-747S</p>
</li>
<li>
<p>BT-747D</p>
</li>
<li>
<p>BT-757S</p>
</li>
<li>
<p>BT-757D</p>
</li>
<li>
<p>BT-545S</p>
</li>
<li>
<p>BT-542D</p>
</li>
<li>
<p>BT-742A</p>
</li>
<li>
<p>BT-542B</p>
</li>
</ul>
<br>
<br>
<p>BusLogic MultiMaster ``A'' Series Host Adapters (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bt&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bt</span>(4)</span></a> driver):</p>
<ul>
<li>
<p>BT-742A</p>
</li>
<li>
<p>BT-542B</p>
</li>
</ul>
<br>
<br>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> BusLogic/Mylex ``Flashpoint''
adapters are not yet supported.</p>
</blockquote>
</div>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> AMI FastDisk controllers that are
true BusLogic MultiMaster clones are also
supported.</p>
</blockquote>
</div>
<p>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III,
SmartCACHE IV and SmartRAID IV SCSI/RAID controllers (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dpt&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dpt</span>(4)</span></a> driver)</p>
<p>AMI MegaRAID Express and Enterprise family RAID
controllers (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=amr&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">amr</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>MegaRAID Series 418</p>
</li>
<li>
<p>MegaRAID Enterprise 1200 (Series 428)</p>
</li>
<li>
<p>MegaRAID Enterprise 1300 (Series 434)</p>
</li>
<li>
<p>MegaRAID Enterprise 1400 (Series 438)</p>
</li>
<li>
<p>MegaRAID Enterprise 1500 (Series 467)</p>
</li>
<li>
<p>MegaRAID Enterprise 1600 (Series 471)</p>
</li>
<li>
<p>MegaRAID Elite 1500 (Series 467)</p>
</li>
<li>
<p>MegaRAID Elite 1600 (Series 493)</p>
</li>
<li>
<p>MegaRAID Express 100 (Series 466WS)</p>
</li>
<li>
<p>MegaRAID Express 200 (Series 466)</p>
</li>
<li>
<p>MegaRAID Express 300 (Series 490)</p>
</li>
<li>
<p>MegaRAID Express 500 (Series 475)</p>
</li>
<li>
<p>Dell PERC</p>
</li>
<li>
<p>Dell PERC 2/SC</p>
</li>
<li>
<p>Dell PERC 2/DC</p>
</li>
<li>
<p>Dell PERC 3/DCL</p>
</li>
<li>
<p>HP NetRaid-1si</p>
</li>
<li>
<p>HP NetRaid-3si</p>
</li>
<li>
<p>HP Embedded NetRaid</p>
</li>
</ul>
<br>
<br>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Booting from these controllers is not
supported due to SRM limitations.</p>
</blockquote>
</div>
<p>Mylex DAC960 and DAC1100 RAID controllers with 2.x,
3.x, 4.x and 5.x firmware (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=mlx&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">mlx</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>DAC960P</p>
</li>
<li>
<p>DAC960PD</p>
</li>
<li>
<p>DAC960PDU</p>
</li>
<li>
<p>DAC960PL</p>
</li>
<li>
<p>DAC960PJ</p>
</li>
<li>
<p>DAC960PG</p>
</li>
<li>
<p>AcceleRAID 150</p>
</li>
<li>
<p>AcceleRAID 250</p>
</li>
<li>
<p>eXtremeRAID 1100</p>
</li>
</ul>
<br>
<br>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Booting from these controllers is
supported. EISA adapters are not supported.</p>
<p>Booting from these controllers is not supported
due to SRM limitations. This list includes
controllers sold by Digital/Compaq in Alpha systems
in the StorageWorks family, e.g. KZPSC or KZPAC.</p>
</blockquote>
</div>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Compatible Mylex controllers not
listed should work, but have not been verified.</p>
</blockquote>
</div>
<p>3ware Escalade ATA RAID controllers (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=twe&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">twe</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>5000 series</p>
</li>
</ul>
<br>
<br>
<p>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815,
53C825, 53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885,
53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000,
53C1000R PCI SCSI controllers, either embedded on
motherboard or on add-on boards (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ncr&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ncr</span>(4)</span></a> and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sym&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sym</span>(4)</span></a> drivers)</p>
<ul>
<li>
<p>ASUS SC-200, SC-896</p>
</li>
<li>
<p>Data Technology DTC3130 (all variants)</p>
</li>
<li>
<p>DawiControl DC2976UW</p>
</li>
<li>
<p>Diamond FirePort (all)</p>
</li>
<li>
<p>NCR cards (all)</p>
</li>
<li>
<p>Symbios cards (all)</p>
</li>
<li>
<p>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D,
and 390U3W</p>
</li>
<li>
<p>Tyan S1365</p>
</li>
</ul>
<br>
<br>
<p>Qlogic controllers and variants (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=isp&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">isp</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Qlogic 1020, 1040 SCSI and Ultra SCSI host
adapters</p>
</li>
<li>
<p>Qlogic 1240 dual Ultra SCSI controllers</p>
</li>
<li>
<p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD
controllers</p>
</li>
<li>
<p>Qlogic 12160 Ultra3 LVD controllers</p>
</li>
<li>
<p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI
controllers</p>
</li>
<li>
<p>Performance Technology SBS440 ISP1000 variants</p>
</li>
<li>
<p>Performance Technology SBS450 ISP1040 variants</p>
</li>
<li>
<p>Performance Technology SBS470 ISP2100 variants</p>
</li>
<li>
<p>Antares Microsystems P-0033 ISP2100 variants</p>
</li>
</ul>
<br>
<br>
<p>Tekram DC390 and DC390T controllers, maybe other cards
based on the AMD 53c974 as well (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=amd&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">amd</span>(4)</span></a> driver)</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&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">cd</span>(4)</span></a>). WORM/CD-R/CD-RW
writing support is provided by <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&amp;sektion=1">
<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="PORT">sysutils/cdrtools</tt></a> port in the
Ports Collection.</p>
<p>The following CD-ROM type systems are supported at
this time:</p>
<ul>
<li>
<p>SCSI interface (also includes ProAudio Spectrum
and SoundBlaster SCSI) (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=cd&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">cd</span>(4)</span></a>)</p>
</li>
<li>
<p>ATAPI IDE interface (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=acd&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">acd</span>(4)</span></a>)</p>
</li>
</ul>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="ETHERNET">3.2 Ethernet
Interfaces</a></h2>
<p>Adaptec Duralink PCI Fast Ethernet adapters based on
the Adaptec AIC-6915 Fast Ethernet controller chip (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sf&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sf</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>ANA-62011 64-bit single port 10/100baseTX
adapter</p>
</li>
<li>
<p>ANA-62022 64-bit dual port 10/100baseTX
adapter</p>
</li>
<li>
<p>ANA-62044 64-bit quad port 10/100baseTX
adapter</p>
</li>
<li>
<p>ANA-69011 32-bit single port 10/100baseTX
adapter</p>
</li>
<li>
<p>ANA-62020 64-bit single port 100baseFX adapter</p>
</li>
</ul>
<br>
<br>
<p>Alteon Networks PCI Gigabit Ethernet NICs based on the
Tigon 1 and Tigon 2 chipsets (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ti&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ti</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>3Com 3c985-SX (Tigon 1 and 2)</p>
</li>
<li>
<p>Alteon AceNIC (Tigon 1 and 2)</p>
</li>
<li>
<p>Alteon AceNIC 1000baseT (Tigon 2)</p>
</li>
<li>
<p>Asante PCI 1000BASE-SX Gigabit Ethernet
Adapter</p>
</li>
<li>
<p>Asante GigaNIX1000T Gigabit Ethernet Adapter</p>
</li>
<li>
<p>DEC/Compaq EtherWORKS 1000</p>
</li>
<li>
<p>Farallon PN9000SX</p>
</li>
<li>
<p>NEC Gigabit Ethernet</p>
</li>
<li>
<p>Netgear GA620 (Tigon 2)</p>
</li>
<li>
<p>Netgear GA620T (Tigon 2, 1000baseT)</p>
</li>
<li>
<p>Silicon Graphics Gigabit Ethernet</p>
</li>
</ul>
<br>
<br>
<p>AMD PCnet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=lnc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">lnc</span>(4)</span></a> and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pcn&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pcn</span>(4)</span></a> drivers)</p>
<ul>
<li>
<p>AMD PCnet/PCI (79c970 &amp; 53c974 or 79c974)</p>
</li>
<li>
<p>AMD PCnet/FAST</p>
</li>
<li>
<p>PCnet/FAST+</p>
</li>
<li>
<p>PCnet/FAST III</p>
</li>
<li>
<p>PCnet/PRO</p>
</li>
<li>
<p>PCnet/Home</p>
</li>
<li>
<p>HomePNA</p>
</li>
</ul>
<br>
<br>
<p>RealTek 8129/8139 Fast Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=rl&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">rl</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek
8139 clone)</p>
</li>
<li>
<p>Allied Telesyn AT2550</p>
</li>
<li>
<p>Allied Telesyn AT2500TX</p>
</li>
<li>
<p>D-Link DFE-538TX</p>
</li>
<li>
<p>Genius GF100TXR (RTL8139)</p>
</li>
<li>
<p>KTX-9130TX 10/100 Fast Ethernet</p>
</li>
<li>
<p>NDC Communications NE100TX-E</p>
</li>
<li>
<p>Netronix Inc. EA-1210 NetEther 10/100</p>
</li>
<li>
<p>OvisLink LEF-8129TX</p>
</li>
<li>
<p>OvisLink LEF-8139TX</p>
</li>
<li>
<p>SMC EZ Card 10/100 PCI 1211-TX</p>
</li>
</ul>
<br>
<br>
<p>Lite-On 82c168/82c169 PNIC Fast Ethernet NICs (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Kingston KNE110TX</p>
</li>
<li>
<p>LinkSys EtherFast LNE100TX</p>
</li>
<li>
<p>Matrox FastNIC 10/100</p>
</li>
<li>
<p>NetGear FA310-TX Rev. D1</p>
</li>
</ul>
<br>
<br>
<p>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast
Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Accton EN1217 (98715A)</p>
</li>
<li>
<p>Adico AE310TX (98715A)</p>
</li>
<li>
<p>Compex RL100-TX (98713 or 98713A)</p>
</li>
<li>
<p>CNet Pro120A (98713 or 98713A)</p>
</li>
<li>
<p>CNet Pro120B (98715)</p>
</li>
<li>
<p>NDC Communications SFA100A (98713A)</p>
</li>
<li>
<p>SVEC PN102TX (98713)</p>
</li>
</ul>
<br>
<br>
<p>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs
(<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>LinkSys EtherFast LNE100TX Version 2</p>
</li>
</ul>
<br>
<br>
<p>Winbond W89C840F Fast Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=wb&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">wb</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Trendware TE100-PCIE</p>
</li>
</ul>
<br>
<br>
<p>VIA Technologies VT3043 ``Rhine I'' and VT86C100A
``Rhine II'' Fast Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=vr&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">vr</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>AOpen/Acer ALN-320</p>
</li>
<li>
<p>D-Link DFE-530TX</p>
</li>
<li>
<p>Hawking Technologies PN102TX</p>
</li>
</ul>
<br>
<br>
<p>Silicon Integrated Systems SiS 900 and SiS 7016 PCI
Fast Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sis&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sis</span>(4)</span></a> driver)</p>
<p>National Semiconductor DP83815 Fast Ethernet NICs (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sis&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sis</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>NetGear FA311-TX</p>
</li>
<li>
<p>NetGear FA312-TX</p>
</li>
</ul>
<br>
<br>
<p>National Semiconductor DP83820 and DP83821 Gigabit
Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=nge&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">nge</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Addtron AEG320T</p>
</li>
<li>
<p>Asante FriendlyNet GigaNIC 1000TA and 1000TPC</p>
</li>
<li>
<p>D-Link DGE-500T</p>
</li>
<li>
<p>LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit
PCI)</p>
</li>
<li>
<p>Netgear GA622T</p>
</li>
<li>
<p>SMC EZ Card 1000 (SMC9462TX)</p>
</li>
<li>
<p>Surecom Technology EP-320G-TX</p>
</li>
</ul>
<br>
<br>
<p>Sundance Technologies ST201 PCI Fast Ethernet NICs (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ste&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ste</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>D-Link DFE-550TX</p>
</li>
</ul>
<br>
<br>
<p>SysKonnect SK-984x PCI Gigabit Ethernet cards (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sk&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sk</span>(4)</span></a> drivers)</p>
<ul>
<li>
<p>SK-9821 1000baseT copper, single port</p>
</li>
<li>
<p>SK-9822 1000baseT copper, dual port</p>
</li>
<li>
<p>SK-9841 1000baseLX single mode fiber, single
port</p>
</li>
<li>
<p>SK-9842 1000baseLX single mode fiber, dual
port</p>
</li>
<li>
<p>SK-9843 1000baseSX multimode fiber, single
port</p>
</li>
<li>
<p>SK-9844 1000baseSX multimode fiber, dual port</p>
</li>
</ul>
<br>
<br>
<p>Texas Instruments ThunderLAN PCI NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tl&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tl</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Compaq Netelligent 10, 10/100, 10/100 Proliant,
10/100 Dual-Port</p>
</li>
<li>
<p>Compaq Netelligent 10/100 TX Embedded UTP, 10 T
PCI UTP/Coax, 10/100 TX UTP</p>
</li>
<li>
<p>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</p>
</li>
<li>
<p>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX
UTP</p>
</li>
<li>
<p>Racore 8165 10/100baseTX</p>
</li>
<li>
<p>Racore 8148 10baseT/100baseTX/100baseFX
multi-personality</p>
</li>
</ul>
<br>
<br>
<p>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<p>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>LinkSys EtherFast LNE100TX v4.0/4.1</p>
</li>
</ul>
<br>
<br>
<p>ADMtek Inc. AN986-based USB Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=aue&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">aue</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Billionton USB100</p>
</li>
<li>
<p>D-Link DSB-650TX</p>
</li>
<li>
<p>LinkSys USB100TX</p>
</li>
<li>
<p>Melco Inc. LUA-TX</p>
</li>
<li>
<p>SMC 2202USB</p>
</li>
</ul>
<br>
<br>
<p>CATC USB-EL1210A-based USB Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=cue&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">cue</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Belkin F5U011</p>
</li>
<li>
<p>Belkin F5U111</p>
</li>
<li>
<p>CATC Netmate</p>
</li>
<li>
<p>CATC Netmate II</p>
</li>
</ul>
<br>
<br>
<p>Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=kue&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">kue</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>3Com 3c19250</p>
</li>
<li>
<p>Abocom URE 450</p>
</li>
<li>
<p>ADS Technologies USB-10BT</p>
</li>
<li>
<p>ATen UC10T</p>
</li>
<li>
<p>Corega USB-T</p>
</li>
<li>
<p>D-Link DSB-650</p>
</li>
<li>
<p>Entrega NET-USB-E45</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</p>
</li>
<li>
<p>SMC 2104USB</p>
</li>
</ul>
<br>
<br>
<p>ASIX Electronics AX88140A PCI NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Alfa Inc. GFC2204</p>
</li>
<li>
<p>CNet Pro110B</p>
</li>
</ul>
<br>
<br>
<p>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and
DC21143 based NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=de&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">de</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Asante</p>
</li>
<li>
<p>Cogent EM100FX and EM440TX</p>
</li>
<li>
<p>DEC DE425, DE435, DE450, and DE500</p>
</li>
<li>
<p>SMC Etherpower 8432T, 9332, and 9334</p>
</li>
<li>
<p>ZYNX ZX 3xx</p>
</li>
</ul>
<br>
<br>
<p>DEC/Intel 21143 based Fast Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>DEC DE500-BA</p>
</li>
<li>
<p>Compaq Presario 7900 series built-in Ethernet</p>
</li>
<li>
<p>D-Link DFE-570TX</p>
</li>
<li>
<p>Kingston KNE100TX</p>
</li>
<li>
<p>LinkSys EtherFast 10/100 Instant GigaDrive
built-in Ethernet</p>
</li>
</ul>
<br>
<br>
<p>Davicom DM9100 and DM9102 PCI Fast Ethernet NICs (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Jaton Corporation XpressNet</p>
</li>
</ul>
<br>
<br>
<p>Intel EtherExpress NICs</p>
<ul>
<li>
<p>Intel EtherExpress Pro/100B PCI Fast Ethernet (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Intel PRO/1000, PRO/1000-F, and PRO/1000-T Gigabit
Ethernet (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=wx&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">wx</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Intel InBusiness 10/100 PCI Network Adapter (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Intel PRO/100+ Management Adapter (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span></a> driver)</p>
</li>
</ul>
<br>
<br>
<p>Isolan AT 4141-0 (16 bit)</p>
<p>Isolink 4110 (8 bit)</p>
<p>Novell NE1000, NE2000, and NE2100 Ethernet interface
(<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ed</span>(4)</span></a> driver)</p>
<p>Novell NE2000 clones (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ed</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>NetVin 5000</p>
</li>
<li>
<p>RealTek 8029</p>
</li>
<li>
<p>Surecom NE-34</p>
</li>
<li>
<p>VIA VT86C926</p>
</li>
<li>
<p>Winbond W89C940</p>
</li>
</ul>
<br>
<br>
<p>3Com Ethernet and Fast Ethernet NICs</p>
<ul>
<li>
<p>3C450-TX HomeConnect adapter (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">xl</span>(4)</span></a> driver)</p>
</li>
<li>
<p>3C503 Etherlink II (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ed&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ed</span>(4)</span></a> driver)</p>
</li>
<li>
<p>3C589/589B/589C/589D/589E/XE589ET/574TX/574B
PC-card/PCMCIA (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ep&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ep</span>(4)</span></a> driver)</p>
</li>
<li>
<p>3C900/905/905B/905C PCI (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">xl</span>(4)</span></a> driver)</p>
</li>
<li>
<p>3C556/556B MiniPCI (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">xl</span>(4)</span></a> driver)</p>
</li>
<li>
<p>EISA (Fast) Etherlink III / (Fast) Etherlink
XL</p>
</li>
<li>
<p>3c980/3c980B Fast Etherlink XL server adapter (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">xl</span>(4)</span></a> driver)</p>
</li>
<li>
<p>3cSOHO100-TX OfficeConnect adapter (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">xl</span>(4)</span></a> driver)</p>
</li>
</ul>
<br>
<br>
<p>Gigabit Ethernet cards based on the Level 1 LXT1001
NetCellerator controller (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=lge&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">lge</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>D-Link DGE-500SX</p>
</li>
<li>
<p>SMC TigerCard 1000 (SMC9462SX)</p>
</li>
</ul>
<br>
<br>
<p>Ethernet and Fast Ethernet NICs based on the 3Com 3XP
Typhoon/Sidewinder (3CR990) chipset (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=txp&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">txp</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>3Com 3CR990-TX-95</p>
</li>
<li>
<p>3Com 3CR990-TX-97</p>
</li>
<li>
<p>3Com 3CR990B-SRV</p>
</li>
<li>
<p>3Com 3CR990B-TXM</p>
</li>
<li>
<p>3Com 3CR990SVR95</p>
</li>
<li>
<p>3Com 3CR990SVR97</p>
</li>
</ul>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2637">3.3 FDDI
Interfaces</a></h2>
<p>DEC DEFPA/DEFEA FDDI NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fpa&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fpa</span>(4)</span></a> driver)</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2643">3.4 ATM
Interfaces</a></h2>
<p>Efficient Networks, Inc. ENI-155p ATM PCI Adapters
(hea driver)</p>
<p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa
driver)</p>
<p>The ATM support in FreeBSD supports the following
signaling protocols:</p>
<ul>
<li>
<p>The ATM Forum UNI 3.1 signaling protocol</p>
</li>
<li>
<p>The ATM Forum UNI 3.0 signaling protocol</p>
</li>
<li>
<p>The ATM Forum ILMI address registration</p>
</li>
<li>
<p>FORE Systems' proprietary SPANS signaling
protocol</p>
</li>
<li>
<p>Permanent Virtual Channels (PVCs)</p>
</li>
</ul>
<br>
<br>
<p>Support for the IETF ``Classical IP and ARP over ATM''
model is provided, compliant with the following RFCs and
Internet Drafts:</p>
<ul>
<li>
<p>RFC 1483, ``Multiprotocol Encapsulation over ATM
Adaptation Layer 5''</p>
</li>
<li>
<p>RFC 1577, ``Classical IP and ARP over ATM''</p>
</li>
<li>
<p>RFC 1626, ``Default IP MTU for use over ATM
AAL5''</p>
</li>
<li>
<p>RFC 1755, ``ATM Signaling Support for IP over
ATM''</p>
</li>
<li>
<p>RFC 2225, ``Classical IP and ARP over ATM''</p>
</li>
<li>
<p>RFC 2334, ``Server Cache Synchronization Protocol
(SCSP)''</p>
</li>
<li>
<p>Internet Draft <tt class=
"FILENAME">draft-ietf-ion-scsp-atmarp-00.txt</tt>,
``A Distributed ATMARP Service Using SCSP''</p>
</li>
</ul>
<br>
<br>
<p>Support for an ATM sockets interface is also
provided.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2685">3.5 Wireless Network
Interfaces</a></h2>
<p>Aironet 802.11 wireless adapters (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=an&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">an</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Aironet 4500/4800 series (PCMCIA, PCI, and ISA
adapters are all supported)</p>
</li>
<li>
<p>Cisco Systems Aironet 340, 341, and 342</p>
</li>
</ul>
<br>
<br>
<p>AMD Am79C930 and Harris (Intersil) based 802.11 cards
(awi driver)</p>
<ul>
<li>
<p>BayStack 650 and 660</p>
</li>
<li>
<p>Farallon SkyLINE Wireless</p>
</li>
<li>
<p>Icom SL-200</p>
</li>
<li>
<p>Melco WLI-PCM</p>
</li>
<li>
<p>NEL SSMagic</p>
</li>
<li>
<p>Netwave AirSurfer Plus and AirSurfer Pro</p>
</li>
<li>
<p>ZoomAir 4000</p>
</li>
</ul>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2823">3.7 Multi-port Serial
Interfaces</a></h2>
<p>AST 4 port serial card using shared IRQ</p>
<p>Boca multi-port serial cards</p>
<ul>
<li>
<p>Boca BB1004 4-Port serial card (Modems <i class=
"EMPHASIS">not</i> supported)</p>
</li>
<li>
<p>Boca IOAT66 6-Port serial card (Modems
supported)</p>
</li>
<li>
<p>Boca BB1008 8-Port serial card (Modems <i class=
"EMPHASIS">not</i> supported)</p>
</li>
<li>
<p>Boca BB2016 16-Port serial card (Modems
supported)</p>
</li>
</ul>
<br>
<br>
<p>STB 4 port card using shared IRQ</p>
<p>DigiBoard intelligent serial cards (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dgb&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dgb</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>DigiBoard PC/Xe series</p>
</li>
<li>
<p>DigiBoard PC/Xi series</p>
</li>
</ul>
<br>
<br>
<p>Specialix SI/XIO/SX multiport serial cards, with both
the older SIHOST2.x and the new ``enhanced'' (transputer
based, aka JET) host cards (ISA, EISA and PCI are
supported) (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=si&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">si</span>(4)</span></a> driver)</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2903">3.8 Audio
Devices</a></h2>
<p>Advance (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sbc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Asound 100 and 110</p>
</li>
<li>
<p>Logic ALS120 and ALS4000</p>
</li>
</ul>
<br>
<br>
<p>CMedia sound chips</p>
<ul>
<li>
<p>CMI8338/CMI8738</p>
</li>
</ul>
<br>
<br>
<p>Crystal Semiconductor (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=csa&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">csa</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>CS461x/462x Audio Accelerator</p>
</li>
<li>
<p>CS428x Audio Controller</p>
</li>
</ul>
<br>
<br>
<p>ENSONIQ (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pcm</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>AudioPCI ES1370/1371</p>
</li>
</ul>
<br>
<br>
<p>ESS</p>
<ul>
<li>
<p>ES1868, ES1869, ES1879 and ES1888 (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sbc</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Maestro-1, Maestro-2, and Maestro-2E</p>
</li>
<li>
<p>Maestro-3/Allegro</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> The Maestro-3/Allegro cannot be
compiled into the FreeBSD kernel due to licensing
restrictions, it cannot be compiled into the
kernel. To use this driver, add the following
line to <tt class=
"FILENAME">/boot/loader.conf</tt>:</p>
<pre class="SCREEN">
<tt class="USERINPUT"><b>maestro3_load="YES"</b></tt>
</pre>
</blockquote>
</div>
</li>
</ul>
<br>
<br>
<p>ForteMedia fm801</p>
<p>Gravis (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=gusc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">gusc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>UltraSound MAX</p>
</li>
<li>
<p>UltraSound PnP</p>
</li>
</ul>
<br>
<br>
<p>MSS/WSS Compatible DSPs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pcm</span>(4)</span></a> driver)</p>
<p>NeoMagic 256AV/ZX (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pcm</span>(4)</span></a> driver)</p>
<p>OPTi 931/82C931 (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pcm</span>(4)</span></a> driver)</p>
<p>S3 Sonicvibes</p>
<p>Creative Technologies SoundBlaster series (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sbc&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sbc</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>SoundBlaster</p>
</li>
<li>
<p>SoundBlaster Pro</p>
</li>
<li>
<p>SoundBlaster AWE-32</p>
</li>
<li>
<p>SoundBlaster AWE-64</p>
</li>
<li>
<p>SoundBlaster AWE-64 GOLD</p>
</li>
<li>
<p>SoundBlaster ViBRA-16</p>
</li>
</ul>
<br>
<br>
<p>Trident 4DWave DX/NX (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pcm</span>(4)</span></a> driver)</p>
<p>VIA Technologies VT82C686A</p>
<p>Yamaha</p>
<ul>
<li>
<p>DS1</p>
</li>
<li>
<p>DS1e</p>
</li>
</ul>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN3005">3.9 Camera and Video
Capture Devices</a></h2>
<p>Brooktree Bt848/849/878/879-based frame grabbers (<a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bktr&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bktr</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>AverMedia cards</p>
</li>
<li>
<p>Hauppauge Wincast TV and WinTV boards (PCI)</p>
</li>
<li>
<p>Intel Smart Video Recorder III</p>
</li>
<li>
<p>Miro PC TV</p>
</li>
<li>
<p>STB TV PCI</p>
</li>
<li>
<p>Video Highway XTreme</p>
</li>
<li>
<p>VideoLogic Captivator PCI</p>
</li>
</ul>
<br>
<br>
<p>Connectix QuickCam</p>
<p>Matrox Meteor Video frame grabber (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=meteor&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">meteor</span>(4)</span></a> driver)</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="USB">3.10 USB Devices</a></h2>
<p>A range of USB peripherals are supported; devices
known to work are listed in this section. Owing to the
generic nature of most USB devices, with some exceptions
any device of a given class will be supported, even if
not explicitly listed here.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> USB Ethernet adapters can be found in
the section listing <a href="#ETHERNET">Ethernet
interfaces</a>.</p>
</blockquote>
</div>
<p>Host Controllers (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ohci&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ohci</span>(4)</span></a> and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=uhci&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">uhci</span>(4)</span></a> drivers)</p>
<ul>
<li>
<p>ALi Aladdin-V</p>
</li>
<li>
<p>AMD-756</p>
</li>
<li>
<p>CMD Tech 670 &amp; 673</p>
</li>
<li>
<p>Intel 82371SB (PIIX3)</p>
</li>
<li>
<p>Intel 82371AB and EB (PIIX4)</p>
</li>
<li>
<p>Intel 82801AA (ICH)</p>
</li>
<li>
<p>Intel 82801AB (ICH0)</p>
</li>
<li>
<p>Intel 82801BA/BAM (ICH2)</p>
</li>
<li>
<p>Intel 82443MX</p>
</li>
<li>
<p>NEC uPD 9210</p>
</li>
<li>
<p>OPTi 82C861 (FireLink)</p>
</li>
<li>
<p>SiS 5571</p>
</li>
<li>
<p>VIA 83C572 USB</p>
</li>
<li>
<p>UHCI or OHCI compliant motherboard chipsets (no
exceptions known)</p>
</li>
</ul>
<br>
<br>
<p>USB host controllers (PCI)</p>
<ul>
<li>
<p>ADS Electronics PCI plug-in card (2 ports)</p>
</li>
<li>
<p>Entrega PCI plug-in card (4 ports)</p>
</li>
</ul>
<br>
<br>
<p>Hubs</p>
<ul>
<li>
<p>Andromeda hub</p>
</li>
<li>
<p>MacAlly self powered hub (4 ports)</p>
</li>
<li>
<p>NEC hub</p>
</li>
</ul>
<br>
<br>
<p>Keyboards (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ukbd</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Apple iMac keyboard</p>
</li>
<li>
<p>BTC BTC7935 keyboard with PS/2 mouse port</p>
</li>
<li>
<p>Cherry G81-3504 keyboard</p>
</li>
<li>
<p>Logitech M2452 keyboard</p>
</li>
<li>
<p>MacAlly iKey keyboard</p>
</li>
<li>
<p>Microsoft keyboard</p>
</li>
</ul>
<br>
<br>
<p>Miscellaneous</p>
<ul>
<li>
<p>ActiveWire I/O Board</p>
</li>
<li>
<p>Rio500 MP3 player (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=urio&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">urio</span>(4)</span></a> driver)</p>
</li>
</ul>
<br>
<br>
<p>Modems (umodem driver)</p>
<ul>
<li>
<p>3Com 5605</p>
</li>
<li>
<p>Metricom Ricochet GS USB wireless modem</p>
</li>
</ul>
<br>
<br>
<p>Mice (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ums&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ums</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Agiler Mouse 29UO</p>
</li>
<li>
<p>Apple iMac Mouse</p>
</li>
<li>
<p>Belkin Mouse</p>
</li>
<li>
<p>Chic mouse</p>
</li>
<li>
<p>Cypress mouse</p>
</li>
<li>
<p>Genius Niche mouse</p>
</li>
<li>
<p>Kensington Mouse-in-a-Box</p>
</li>
<li>
<p>Logitech wheel mouse (3 buttons)</p>
</li>
<li>
<p>Logitech PS/2 / USB mouse (3 buttons)</p>
</li>
<li>
<p>MacAlly mouse (3 buttons)</p>
</li>
<li>
<p>Microsoft IntelliMouse (3 buttons)</p>
</li>
<li>
<p>Trust Ami Mouse (3 buttons)</p>
</li>
</ul>
<br>
<br>
<p>Printers and parallel printer conversion cables (ulpt
driver)</p>
<ul>
<li>
<p>ATen parallel printer adapter</p>
</li>
<li>
<p>Belkin F5U002 parallel printer adapter</p>
</li>
<li>
<p>Entrega USB-to-parallel printer adapter</p>
</li>
</ul>
<br>
<br>
<p>Scanners (through SANE) (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=uscanner&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">uscanner</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Perfection 636U</p>
</li>
<li>
<p>HP ScanJet 4100C, 5200C, 6300C</p>
</li>
</ul>
<br>
<br>
<p>Storage (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=umass&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">umass</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Iomega USB Zip 100Mb (primitive support still)</p>
</li>
<li>
<p>Matshita CF-VFDU03 floppy drive</p>
</li>
<li>
<p>Microtech USB-SCSI-HD 50 USB to SCSI cable</p>
</li>
<li>
<p>Panasonic floppy drive</p>
</li>
<li>
<p>Y-E Data floppy drive (720/1.44/2.88Mb)</p>
</li>
</ul>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN3182">3.11
Miscellaneous</a></h2>
<p>Floppy drives (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fd&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fd</span>(4)</span></a> driver)</p>
<p>Genius and Mustek hand scanners</p>
<p>GPB and Transputer drivers</p>
<p>HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon
CD-R drives</p>
<p>Keyboards including:</p>
<ul>
<li>
<p>AT-style keyboards</p>
</li>
<li>
<p>PS/2 keyboards</p>
</li>
</ul>
<br>
<br>
<p>Loran-C receiver (Dave Mills experimental hardware,
loran driver).</p>
<p>Mice including:</p>
<ul>
<li>
<p>PS/2 mice (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=psm&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">psm</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Serial mice</p>
</li>
</ul>
<br>
<br>
<p>Parallel ports</p>
<p>PC-compatible joysticks (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=joy&amp;sektion=4">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">joy</span>(4)</span></a> driver)</p>
<p>Serial ports</p>
<p>Xilinx XC6200-based reconfigurable hardware cards
compatible with the HOT1 from <a href=
"http://www.vcc.com/" target="_top">Virtual Computers</a>
(xrpu driver).</p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN3244">4 Boot-time Kernel
Configuration</a></h1>
<p>This section describes the boot-time configuration of
the FreeBSD kernel.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN3247">4.1 Default
Configuration</a></h2>
<p>The following table contains a list of all of the
devices that are present in the <tt class=
"FILENAME">GENERIC</tt> kernel. This is the essential
part of the operating system that is placed in your root
partition during the installation process. A compressed
version of the <tt class="FILENAME">GENERIC</tt> kernel
is also used on the installation floppy diskette and DOS
boot image.</p>
<p>The table describes the various parameters used by the
driver to communicate with the hardware in your system.
There are four parameters in the table, though not all
are used by each and every device:</p>
<div class="INFORMALTABLE">
<a name="AEN3253"></a>
<table border="0" class="CALSTABLE">
<tbody>
<tr>
<td width="17%" align="LEFT" valign="TOP">
Port</td>
<td width="83%" align="LEFT" valign="TOP">The
starting I/O port used by the device, shown in
hexadecimal.</td>
</tr>
<tr>
<td width="17%" align="LEFT" valign="TOP">
IRQ</td>
<td width="83%" align="LEFT" valign="TOP">The
interrupt the device uses to alert the driver to
an event, given in decimal.</td>
</tr>
<tr>
<td width="17%" align="LEFT" valign="TOP">
DRQ</td>
<td width="83%" align="LEFT" valign="TOP">The DMA
(direct memory access) channel the device uses to
move data to and from main memory, also given in
decimal.</td>
</tr>
<tr>
<td width="17%" align="LEFT" valign="TOP">
IOMem</td>
<td width="83%" align="LEFT" valign="TOP">The
lowest (or starting) memory address used by the
device, also shown in hexadecimal.</td>
</tr>
</tbody>
</table>
</div>
If an entry in the table has `n/a' for a value then it
means that the parameter in question does not apply to
that device. A value of `dyn' means that the correct
value should be determined automatically by the kernel
when the system boots and that you don't need to worry
about it.<br>
<br>
<p>If an entry is marked with an *, it means that support
is currently not available for it but should be back as
soon as someone converts the driver to work within the
new (post-4.0) framework.</p>
<p></p>
<div class="INFORMALTABLE">
<a name="AEN3272"></a>
<table border="0" class="CALSTABLE">
<thead>
<tr>
<th width="10%" align="LEFT" valign="TOP">
Device</th>
<th width="10%" align="LEFT" valign="TOP">
Port</th>
<th width="10%" align="LEFT" valign="TOP">
IRQ</th>
<th width="10%" align="LEFT" valign="TOP">
DRQ</th>
<th width="10%" align="LEFT" valign="TOP">
IOMem</th>
<th width="50%" align="LEFT" valign="TOP">
Description</th>
</tr>
</thead>
<tbody>
<tr>
<td width="10%" align="LEFT" valign="TOP">
fdc0</td>
<td width="10%" align="LEFT" valign="TOP">
3f0</td>
<td width="10%" align="LEFT" valign="TOP">6</td>
<td width="10%" align="LEFT" valign="TOP">2</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Floppy
disk controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ata0</td>
<td width="10%" align="LEFT" valign="TOP">
170</td>
<td width="10%" align="LEFT" valign="TOP">14</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">
ATA/ATAPI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ata1</td>
<td width="10%" align="LEFT" valign="TOP">
170</td>
<td width="10%" align="LEFT" valign="TOP">15</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">
ATA/ATAPI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
atadisk0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">ATA
disk drives</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
atapicd0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">ATAPI
CDROM drives</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
atapifd0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">ATAPI
floppy drives</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
atapist0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">ATAPI
tape drives</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
adv0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">
AdvanSys Narrow SCSI controllers</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
adw0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">
AdvanSys Wide SCSI controllers</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
amd0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">AMD
53C974 (Tekram DC390(T))</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ncr0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">NCR PCI
SCSI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
bt0</td>
<td width="10%" align="LEFT" valign="TOP">
330</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">
Buslogic SCSI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
aha0</td>
<td width="10%" align="LEFT" valign="TOP">
330</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">5</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Adaptec
154x/1535 SCSI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ahb0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Adaptec
174x SCSI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ahc0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Adaptec
274x/284x/294x SCSI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
aic0</td>
<td width="10%" align="LEFT" valign="TOP">
340</td>
<td width="10%" align="LEFT" valign="TOP">11</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Adaptec
152x/AIC-6360/AIC-6260 SCSI controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
isp0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">QLogic
10X0, 1240 Ultra SCSI, 1080/1280 Ultra2 SCSI,
12160 Ultra3 SCSI, 2X00 Fibre Channel SCSI
controller</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
dpt0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">DPT
RAID SCSI controllers</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
amr0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">AMI
MegaRAID controllers</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
mlx0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Mylex
DAC960 RAID controllers</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
twe0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">3ware
Escalade RAID controllers</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
asr0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">DPT
SmartRaid V, VI, and Adaptec SCSI RAID</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
mly0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Mylex
AcceleRAID/eXtremeRAID</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
aac</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Adaptec
FSA family PCI SCSI RAID</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ncv</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">NCR
53C500 based PC-Card SCSI</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
nsp</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Workbit
Ninja SCSI-3 based PC-Card SCSI</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
stg</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">TMC
18C30/50 based ISA/PC-Card SCSI</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
wt0</td>
<td width="10%" align="LEFT" valign="TOP">
300</td>
<td width="10%" align="LEFT" valign="TOP">5</td>
<td width="10%" align="LEFT" valign="TOP">1</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Wangtek
and Archive QIC-02/QIC-36</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
psm0</td>
<td width="10%" align="LEFT" valign="TOP">60</td>
<td width="10%" align="LEFT" valign="TOP">12</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">PS/2
Mouse</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
mcd0</td>
<td width="10%" align="LEFT" valign="TOP">
300</td>
<td width="10%" align="LEFT" valign="TOP">10</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Mitsumi
CD-ROM</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
matcd0</td>
<td width="10%" align="LEFT" valign="TOP">
230</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">
Matsushita/Panasonic CD-ROM</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
scd0</td>
<td width="10%" align="LEFT" valign="TOP">
230</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Sony
CD-ROM</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
sio0</td>
<td width="10%" align="LEFT" valign="TOP">
3f8</td>
<td width="10%" align="LEFT" valign="TOP">4</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Serial
Port 0 (COM1)</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
sio1</td>
<td width="10%" align="LEFT" valign="TOP">
2f8</td>
<td width="10%" align="LEFT" valign="TOP">3</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Serial
Port 1 (COM2)</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ppc0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">7</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Printer
ports</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
dc0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">
DEC/Intel 21143 cards and workalikes</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
de0</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">DEC
DC21x40 PCI based cards (including 21140 100bT
cards)</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ed0</td>
<td width="10%" align="LEFT" valign="TOP">
280</td>
<td width="10%" align="LEFT" valign="TOP">10</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
d8000</td>
<td width="50%" align="LEFT" valign="TOP">WD
&amp; SMC 80xx; Novell NE1000 &amp; NE2000; 3Com
3C503; HP PC Lan+</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ep0</td>
<td width="10%" align="LEFT" valign="TOP">
300</td>
<td width="10%" align="LEFT" valign="TOP">10</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">3Com
3C509, 3C529, 3C556, 3C562D, 3C563D, 3C572,
3C574X, 3C579, 3C589</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ex0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Intel
EtherExpress Pro/10 cards</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
fe0</td>
<td width="10%" align="LEFT" valign="TOP">
300</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">
Allied-Telesyn AT1700, RE2000 and Fujitsu FMV-180
series cards.</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
fxp0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Intel
EtherExpress Pro/100B and Intel PRO/100+
Management Adapter</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ie0</td>
<td width="10%" align="LEFT" valign="TOP">
300</td>
<td width="10%" align="LEFT" valign="TOP">10</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
d0000</td>
<td width="50%" align="LEFT" valign="TOP">
AT&amp;T StarLAN 10 and EN100; 3Com 3C507;
NI5210; Intel EtherExpress (8/16,16[TP])
cards</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
le0</td>
<td width="10%" align="LEFT" valign="TOP">
300</td>
<td width="10%" align="LEFT" valign="TOP">5</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
d0000</td>
<td width="50%" align="LEFT" valign="TOP">Digital
Equipment EtherWorks 2 and EtherWorks 3</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
lnc0</td>
<td width="10%" align="LEFT" valign="TOP">
280</td>
<td width="10%" align="LEFT" valign="TOP">10</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">
Lance/PCnet cards (Isolan, Novell NE2100,
NE32-VL, some PCnet-PCI cards)</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
pcn0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">AMD
PCnet/FAST, PCnet/FAST+, PCnet/FAST III,
PCnet/PRO, PCnet/Home, and HomePNA cards</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
rl0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">RealTek
8129/8139 fast ethernet</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
sf0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Adaptec
AIC-6915 fast ethernet</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
sis0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">SiS
900/SiS 7016 fast ethernet</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
sn0</td>
<td width="10%" align="LEFT" valign="TOP">
0x300</td>
<td width="10%" align="LEFT" valign="TOP">10</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">SMC
91xx ethernet</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
ste0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">
Sundance ST201 fast ethernet</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
tl0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">TI
TNET100 'ThunderLAN' cards.</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
tx0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">SMC
9432 'Epic' fast ethernet</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
wb0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Winbond
W89C840F PCI based cards.</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
vr0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">VIA
VT3043/VT86C100A PCI based cards.</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
vx0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">3Com
3c59x ((Fast) Etherlink III)</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
xe0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">Xircom
CreditCard adapters (16 bit)</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
xl0</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="50%" align="LEFT" valign="TOP">3Com
3c900, 3c905, 3c905B, 3c905C, 3c980, 3cSOHO100
((Fast) Etherlink XL)</td>
</tr>
<tr>
<td width="10%" align="LEFT" valign="TOP">
cs0</td>
<td width="10%" align="LEFT" valign="TOP">
0x300</td>
<td width="10%" align="LEFT" valign="TOP">
dyn</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="10%" align="LEFT" valign="TOP">
n/a</td>
<td width="50%" align="LEFT" valign="TOP">Crystal
Semiconductor CS89x0-based cards.</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
<p>If the hardware in your computer is not set to the
same settings as those shown in the table and the item in
conflict is not marked 'dyn', you will have to either
reconfigure your hardware or use UserConfig to
reconfigure the kernel to match the way your hardware is
currently set (see the next section).</p>
<p>If the settings do not match, the kernel may be unable
to locate or reliably access the devices in your
system.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN3704">4.2 Using UserConfig
to change FreeBSD kernel settings</a></h2>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> The markup for this section leaves a
lot to be desired.</p>
</blockquote>
</div>
<p>The FreeBSD kernel on the install floppy contains
drivers for every piece of hardware that could
conceivably be used to install the rest of the system
with. Unfortunately, PC hardware being what it is, some
of these devices can be difficult to detect accurately,
and for some, the process of detecting another can cause
irreversible confusion.</p>
<p>To make this process easier, FreeBSD provides
UserConfig. With this tool the user can configure and
disable device drivers before the kernel is loaded,
avoiding potential conflicts, and eliminating the need to
reconfigure hardware to suit the default driver
settings.</p>
<p>Once FreeBSD is installed, it will remember the
changes made using UserConfig, so that they only need be
made once.</p>
<p>It is important to disable drivers that are not
relevant to a system in order to minimize the possibility
of interference, which can cause problems that are
difficult to track down.</p>
<p>UserConfig features a command line interface for users
with serial consoles or a need to type commands, and a
full screen ``visual'' interface, which provides
point-and-shoot configuration functionality.</p>
<p>Here is a sample UserConfig screen shot in ``visual''
mode:</p>
<pre class="SCREEN">
---Active Drivers---------------------------10 Conflicts------Dev---IRQ--Port--
Storage : (Collapsed)
Network :
NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed0 5 0x280
NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed1 5 0x300
Communications : (Collapsed)
Input : (Collapsed)
Multimedia :
---Inactive Drivers-------------------------------------------Dev--------------
Storage :
Network : (Collapsed)
Communications :
Input :
Multimedia :
---Parameters-for-device-ed0---------------------------------------------------
Port address : 0x280 Memory address : 0xd8000
IRQ number : 5 Memory size : 0x2000
Flags : 0x0000
-------------------------------------------------------------------------------
IO Port address (Hexadecimal, 0x1-0x2000)
[TAB] Change fields [Q] Save device parameters
</pre>
<p>The screen is divided into four sections:</p>
<ul>
<li>
<p>Active Drivers. Listed here are the device drivers
that are currently enabled, and their basic
parameters.</p>
</li>
<li>
<p>Inactive Drivers. These drivers are present, but
are disabled.</p>
</li>
<li>
<p>Parameter edit field. This area is used for
editing driver parameters.</p>
</li>
<li>
<p>Help area. Keystroke help is displayed here.</p>
</li>
</ul>
<br>
<br>
<p>One of the Active and Inactive lists is always in use,
and the current entry in the list will be shown with a
highlight bar. If there are more entries in a list than
can be shown, it will scroll. The bar can be moved up and
down using the cursor keys, and moved between lists with
the TAB key.</p>
<p>Drivers in the Active list may be marked <tt class=
"LITERAL">CONF</tt>. This indicates that one or more of
their parameters conflicts with another device, and
indicates a potential for problems. The total number of
conflicts is displayed at the top of the screen.</p>
<p>As a general rule, conflicts should be avoided, either
by disabling conflicting devices that are not present in
the system, or by altering their configuration so that
they match the installed hardware.</p>
<p>In the list areas, drivers are grouped by their basic
function. Groups can be <tt class=
"LITERAL">Collapsed</tt> to simplify the display (this is
the default state for all groups). If a group is
collapsed, it will be shown with <tt class=
"LITERAL">Collapsed</tt> in the list, as above. To Expand
a Collapsed group, position the highlight bar over the
group heading and press Enter. To Collapse it again,
repeat the process.</p>
<p>When a device driver in the Active list is
highlighted, its full parameters are displayed in the
Parameter edit area. Note that not all drivers use all
possible parameters, and some hardware supported by
drivers may not use all the parameters the driver
supports.</p>
<p>To disable a driver, go to the Active list, Expand the
group it is in, highlight the driver and press Del. The
driver will move to its group in the Inactive list. (If
the group is collapsed or off the screen, you may not see
the driver in its new location.)</p>
<p>To enable a driver, go to the Inactive list, Expand
the group it is in, highlight the driver and press Enter.
The highlight will move to the Active list, and the
driver you have just enabled will be highlighted, ready
to be configured.</p>
<p>To configure a driver, go to the Active list, Expand
the group it is in, highlight the driver and press Enter.
The cursor will move to the Parameter edit area, and the
device's parameters may be edited.</p>
<p>While editing parameters, the TAB and cursor keys can
be used to move between fields. Most numeric values
(except IRQ) are entered in hexadecimal, as indicated by
the '0x' at the beginning of the field. The allowable
values for a given field are show in the Key Help area
when the field is active.</p>
<p>To finish configuring a driver, press 'Q'.</p>
<p>Note that PCI, Microchannel and EISA devices can be
probed reliably, therefore they are not shown in the
table above nor can their settings be changed using
UserConfig.</p>
</div>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp://ftp.FreeBSD.org/pub/FreeBSD/</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 &lt;<a href=
"mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&gt;.</small></p>
<p align="center"><small><small>All users of FreeBSD 4-STABLE
should subscribe to the &lt;<a href=
"mailto:stable@FreeBSD.org">stable@FreeBSD.org</a>&gt; mailing
list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &lt;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&gt;.</p>
<br>
<br>
</body>
</html>
Reference in a new issue View git blame Copy permalink