1 <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
2 <!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
5 <!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
7 <!ENTITY % devauto PUBLIC "-//FreeBSD//ENTITIES Auto Generated Device Lists//EN">
10 <!-- Text constants which probably don't need to be changed.-->
16 <title>&os; &release.current; Hardware Notes</title>
18 <corpauthor>The &os; Documentation Project</corpauthor>
20 <pubdate>$FreeBSD$</pubdate>
33 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
36 <legalnotice id="trademarks" role="trademarks">
49 <title>Introduction</title>
51 <para>This document contains the hardware compatibility notes for
52 &os; &release.current;. It lists the hardware platforms
53 supported by &os;, as well as the various types of hardware
54 devices (storage controllers, network interfaces, and so on),
55 along with known working instances of these devices.</para>
59 <title>Supported Processors and System Boards</title>
61 <para>This section provides some architecture-specific information
62 about the specific processors and systems that are supported by
63 each architecture.</para>
65 <sect2 id="proc-amd64">
68 <para>Since mid-2003 &os;/&arch.amd64; has supported the AMD64
69 (<quote>Hammer</quote>) and &intel; EM64T architecture, and is
70 now one of the Tier-1 platforms (fully supported
71 architecture), which are expected to be Production Quality
72 with respects to all aspects of the &os; operating system,
73 including installation and development environments.</para>
75 <para>Note that there are two names for this architecture, AMD64
76 (AMD) and Intel EM64T (Extended Memory 64-bit Technology).
77 64-bit mode of the two architectures are almost compatible
78 with each other, and &os;/&arch.amd64; should support them
81 <para>As of this writing, the following processors are
86 <para>&amd.athlon;64 (<quote>Clawhammer</quote>).</para>
90 <para>&amd.opteron; (<quote>Sledgehammer</quote>).</para>
94 <para>All multi-core &intel; &xeon; processors except
95 Sossaman have EM64T support.</para>
99 <para>The single-core &intel; &xeon;
100 processors <quote>Nocona</quote>, <quote>Irwindale</quote>,
101 <quote>Potomac</quote>, and <quote>Cranford</quote> have
102 EM64T support.</para>
106 <para>All &intel; Core 2 (not Core Duo) and later
111 <para>All &intel; &pentium; D processors</para>
115 <para>&intel; &pentium; 4s and Celeron Ds using
116 the <quote>Cedar Mill</quote> core have EM64T
121 <para>Some &intel; &pentium; 4s and Celeron Ds using
122 the <quote>Prescott</quote> core have EM64T support. See
123 the <ulink url="http://processorfinder.intel.com">Intel
124 Processor Spec Finder</ulink> for the definitive answer about
125 EM64T support in Intel processors.</para>
130 <para>&intel; EM64T is an extended version of IA-32 (x86) and
131 different from &intel; IA-64 (Itanium) architecture, which
132 &os;/ia64 supports. Some &intel;'s old documentation refers
133 to &intel; EM64T as <quote>64-bit extension technology</quote>
134 or <quote>IA-32e</quote>.</para>
136 <para>The largest tested memory configuration to date is 64GB.
137 SMP support has been recently completed and is reasonably
140 <para>In many respects, &os;/&arch.amd64; is similar to
141 &os;/&arch.i386;, in terms of drivers supported. There may be
142 some issues with 64-bit cleanliness in some (particularly
143 older) drivers. Generally, drivers that already function
144 correctly on other 64-bit platforms should work.</para>
146 <para>&os;/&arch.amd64; is a very young platform on &os;. While
147 the core &os; kernel and base system components are generally
148 fairly robust, there are likely to still be rough edges,
149 particularly with third party packages.</para>
153 <sect2 id="proc-i386">
156 <para>&os;/&arch.i386; runs on a wide variety of <quote>IBM PC
157 compatible</quote> machines. Due to the wide range of
158 hardware available for this architecture, it is impossible
159 to exhaustively list all combinations of equipment supported
160 by &os;. Nevertheless, some general guidelines are
161 presented here.</para>
163 <para>Almost all &i386;-compatible processors with a floating
164 point unit are supported. All &intel; processors beginning
165 with the 80486 are supported, including the 80486, &pentium;,
166 &pentium; Pro, &pentium; II, &pentium; III, &pentium; 4, and
167 variants thereof, such as the &xeon; and &celeron; processors.
168 All &i386;-compatible AMD processors are also supported,
169 including the &am486;, &am5x86;, K5, &amd.k6; (and variants),
170 &amd.athlon; (including Athlon-MP, Athlon-XP, Athlon-4, and
171 Athlon Thunderbird), and &amd.duron; processors. The AMD
172 Élan SC520 embedded processor is supported. The
173 Transmeta Crusoe is recognized and supported, as are
174 &i386;-compatible processors from Cyrix and NexGen.</para>
176 <para>There is a wide variety of motherboards available for this
177 architecture. Motherboards using the ISA, VLB, EISA, AGP, and
178 PCI expansion busses are well-supported. There is some
179 limited support for the MCA (<quote>MicroChannel</quote>)
180 expansion bus used in the IBM PS/2 line of PCs.</para>
182 <para>Symmetric multi-processor (SMP) systems are generally
183 supported by &os;, although in some cases, BIOS or motherboard
184 bugs may generate some problems. Perusal of the archives of
185 the &a.smp; may yield some clues.</para>
187 <para>&os; will take advantage of HyperThreading (HTT) support
188 on &intel; CPUs that support this feature. A kernel with the
189 <literal>options SMP</literal> feature enabled will
190 automatically detect the additional logical processors. The
191 default &os; scheduler treats the logical processors the same
192 as additional physical processors; in other words, no attempt
193 is made to optimize scheduling decisions given the shared
194 resources between logical processors within the same CPU.
195 Because this naive scheduling can result in suboptimal
196 performance, under certain circumstances it may be useful to
197 disable the logical processors with the the
198 <varname>machdep.hlt_logical_cpus</varname> sysctl variable.
199 It is also possible to halt any CPU in the idle loop with the
200 <varname>machdep.hlt_cpus</varname> sysctl variable. The
201 &man.smp.4; manual page has more details.</para>
203 <para>&os; will take advantage of Physical Address Extensions
204 (PAE) support on CPUs that support this feature. A kernel
205 with the <literal>PAE</literal> feature enabled will detect
206 memory above 4 gigabytes and allow it to be used by the
207 system. This feature places constraints on the device drivers
208 and other features of &os; which may be used; consult the
209 &man.pae.4; manpage for more details.</para>
211 <para>&os; will generally run on i386-based laptops, albeit with
212 varying levels of support for certain hardware features such
213 as sound, graphics, power management, and PCCARD expansion
214 slots. These features tend to vary in idiosyncratic ways
215 between machines, and frequently require special-case support
216 in &os; to work around hardware bugs or other oddities. When
217 in doubt, a search of the archives of the &a.mobile; may be
220 <para>Most modern laptops (as well as many desktops) use the
221 Advanced Configuration and Power Management (ACPI) standard.
222 &os; supports ACPI via the ACPI Component Architecture
223 reference implementation from &intel;, as described in the
224 &man.acpi.4; manual page. The use of ACPI causes
225 instabilities on some machines and it may be necessary to
226 disable the ACPI driver, which is normally loaded via a kernel
227 module. This may be accomplished by adding the following line
228 to <filename>/boot/device.hints</filename>:</para>
230 <programlisting>hint.acpi.0.disabled="1"</programlisting>
232 <para>Users debugging ACPI-related problems may find it useful
233 to disable portions of the ACPI functionality. The
234 &man.acpi.4; manual page has more information on how to do
235 this via loader tunables.</para>
237 <para>ACPI depends on a Differentiated System Descriptor Table
238 (DSDT) provided by each machine's BIOS. Some machines have
239 bad or incomplete DSDTs, which prevents ACPI from functioning
240 correctly. Replacement DSDTs for some machines can be found
242 url="http://acpi.sourceforge.net/dsdt/index.php">DSDT</ulink>
243 section of the <ulink
244 url="http://acpi.sourceforge.net/">ACPI4Linux</ulink> project
245 Web site. &os; can use these DSDTs to override the DSDT
246 provided by the BIOS; see the &man.acpi.4; manual page for
247 more information.</para>
250 <sect2 id="proc-ia64">
253 <para>Currently supported processors are the <ulink
254 url="http://people.freebsd.org/~marcel/refs/ia64/itanium/24532003.pdf">&itanium;</ulink>
256 url="http://people.freebsd.org/~marcel/refs/ia64/itanium2/25111003.pdf">&itanium;
259 <para>Supported chipsets include:</para>
267 <para>&intel; 460GX</para>
271 <para>&intel; E8870</para>
275 <para>Both Uniprocessor (UP) and Symmetric Multi-processor (SMP)
276 configurations are supported.</para>
278 <para>Most devices that can be found in or are compatible with
279 &arch.ia64; machines are fully supported. The notable
280 exception is the VGA console. The &os; support for VGA
281 consoles is at this time too much based on PC hardware and not
282 all &arch.ia64; machines have chipsets that provide sufficient
283 PC legacy support. As such &man.syscons.4; can not be enabled
284 and the use of a serial console is required.</para>
287 <sect2 id="proc-pc98">
290 <para>NEC PC-9801/9821 series with almost all &i386;-compatible
291 processors, including 80486, &pentium;, &pentium; Pro,
292 &pentium; II, and variants. All &i386;-compatible processors
293 by AMD, Cyrix, IBM, and IDT are also supported.</para>
295 <para>NEC FC-9801/9821 series, and NEC SV-98 series (both of
296 them are compatible with PC-9801/9821 series) should be
299 <para>EPSON PC-386/486/586 series, which are compatible with NEC
300 PC-9801 series are supported.</para>
302 <para>High-resolution mode is not supported. NEC
303 PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in
304 normal (PC-9801 compatible) mode only.</para>
306 <para>Although there are some multi-processor systems (such as
307 Rs20/B20), SMP-related features of &os; are not supported
310 <para>PC-9801/9821 standard bus (called C-Bus), PC-9801NOTE
311 expansion bus (110pin), and PCI bus are supported. New Extend
312 Standard Architecture (NESA) bus (used in PC-H98, SV-H98, and
313 FC-H98 series) is not supported.</para>
316 <sect2 id="proc-powerpc">
317 <title>powerpc</title>
319 <para>The information for this paragraph has yet to be
323 <sect2 id="proc-sparc64">
324 <title>sparc64</title>
326 <para>This section describes the systems currently known to be
327 supported by &os; on the &ultrasparc; platform. For
328 background information on the various hardware designs see the
329 <ulink url="http://sunsolve.sun.com/handbook_pub/">Sun System
330 Handbook</ulink>.</para>
332 <para>SMP is supported on all systems with more than 1
335 <para>When using the <filename>GENERIC</filename> kernel,
336 &os;/&arch.sparc64; systems not equipped with a framebuffer
337 supported by the &man.creator.4; (&sun; Creator, &sun; Creator3D
338 and &sun; Elite3D) or &man.machfb.4; (&sun; PGX and &sun; PGX64
339 as well as the ATI Mach64 chips found onboard in for example
340 &sun.blade; 100, &sun.blade; 150, &sun.ultra; 5 and &sun.ultra; 10)
341 driver must use the serial console.</para>
343 <para>If you have a system that is not listed here, it may not
344 have been tested with &os; &release.current;. We encourage
345 you to try it and send a note to the &a.sparc; with your
346 results, including which devices work and which do not.</para>
348 <para>The following systems are fully supported by &os;:</para>
352 <para>&sun.blade; 100</para>
356 <para>&sun.blade; 150</para>
360 <para>&sun.enterprise; 100</para>
364 <para>&sun.enterprise; 220R</para>
368 <para>&sun.enterprise; 250</para>
372 <para>&sun.enterprise; 420R</para>
376 <para>&sun.enterprise; 450</para>
380 <para>&sun.fire; V100</para>
384 <para>&sun.fire; V120</para>
388 <para>&netra; t1 105</para>
392 <para>&netra; T1 AC200/DC200</para>
396 <para>&netra; t 1100</para>
400 <para>&netra; t 1120</para>
404 <para>&netra; t 1125</para>
408 <para>&netra; t 1400/1405</para>
412 <para>&netra; 120</para>
416 <para>&netra; X1</para>
420 <para>&sparcengine; Ultra AX1105</para>
424 <para>&sparcengine; Ultra AXe</para>
428 <para>&sparcengine; Ultra AXi</para>
432 <para>&sparcengine; Ultra AXmp</para>
436 <para>&sun.ultra; 1</para>
440 <para>&sun.ultra; 1E</para>
444 <para>&sun.ultra; 2</para>
448 <para>&sun.ultra; 5</para>
452 <para>&sun.ultra; 10</para>
456 <para>&sun.ultra; 30</para>
460 <para>&sun.ultra; 60</para>
464 <para>&sun.ultra; 80</para>
468 <para>&sun.ultra; 450</para>
472 <para>The following systems are partially supported by &os;. In
473 particular the fibre channel controllers in SBus-based systems are not
474 supported. However, it is possible to use these with a SCSI controller
475 supported by the &man.esp.4 driver (&sun; ESP SCSI, &sun; FAS Fast-SCSI
476 and &sun; FAS366 Fast-Wide SCSI controllers).</para>
480 <para>&sun.enterprise; 3500</para>
484 <para>&sun.enterprise; 4500</para>
488 <para>Starting with 7.2-RELEASE, &arch.sparc64; systems based on
489 &ultrasparc; III and beyond are also supported by &os;, which includes
490 the following known working systems:</para>
494 <para>&sun.blade; 1000</para>
498 <para>&sun.blade; 1500</para>
502 <para>&sun.blade; 2000</para>
506 <para>&sun.blade; 2500</para>
510 <para>&sun.fire; 280R</para>
514 <para>&sun.fire; V210</para>
518 <para>&sun.fire; V215 (support first appeared in 7.3-RELEASE)</para>
522 <para>&sun.fire; V250</para>
526 <para>&sun.fire; V440 (support for the on-board NICs first
527 appeared in 8.0-RELEASE)</para>
531 <para>&sun.fire; V480 (501-6780 and 501-6790 centerplanes only, for
532 which support first appeared in 7.3-RELEASE)</para>
536 <para>&sun.fire; V880</para>
540 <para>&netra; 20/&netra; T4</para>
544 <para>The following &ultrasparc; IIIi systems are not tested but
545 believed to be also supported by &os;:</para>
549 <para>&sun.fire; V125</para>
553 <para>&sun.fire; V240</para>
557 <para>&sun.fire; V245 (support first appeared in 7.3-RELEASE)</para>
565 The "Supported Devices" section of the release notes.
566 Generally processor-independent, with conditional text
567 inclusion handling any architecture-dependent text.
569 Within each subsection describing a class of hardware
570 (i.e. Ethernet interfaces), list broad groups of devices
571 alphabetically as paragraphs sorted alphabetically (frequently
572 these groups will be arranged by manufacturer, i.e. 3Com
573 Ethernet interfaces).
575 Where applicable, a "Miscellaneous" section may follow all
576 other named sections.
578 These guidelines are not hard-and-fast rules, and exceptions
579 will occur. Following these guidelines (vague as they may be)
580 is highly recommended to try to keep the formatting of
581 this section consistent.
583 We give manpage references using the &man entities where
584 possible. If a driver has no manpage (and consequently no
585 &man entity, we simply give the name of the driver).
586 Please avoid doing &man entity conversions unless you
587 know for sure that an entity and manpage exist; sweeps through
588 this file to fix "missed" conversions are likely to break the
593 <title>Supported Devices</title>
595 <para>This section describes the devices currently known to be
596 supported by &os;. Other configurations may also work, but
597 simply have not been tested yet. Feedback, updates, and
598 corrections to this list are encouraged.</para>
600 <para>Where possible, the drivers applicable to each device or
601 class of devices is listed. If the driver in question has a
602 manual page in the &os; base distribution (most should), it is
603 referenced here. Information on specific models of supported
604 devices, controllers, etc. can be found in the manual
608 <para>The device lists in this document are being generated
609 automatically from &os; manual pages. This means that some
610 devices, which are supported by multiple drivers, may appear
611 multiple times.</para>
615 <title>Disk Controllers</title>
617 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;,
618 &arch.sparc64;] IDE/ATA controllers (&man.ata.4;
621 <para>[&arch.pc98;] IDE/ATA controllers (wdc driver)</para>
625 <para>On-board IDE controller</para>
662 <para>[&arch.amd64;, &arch.i386;] Booting from these
663 controllers is supported. EISA adapters are not
688 <para>[&arch.amd64;, &arch.i386;] Booting from these
689 controllers is supported. EISA adapters are not
717 <para>[&arch.i386;] The wds(4) driver supports the WD7000 SCSI
720 <para>With all supported SCSI controllers, full support is
721 provided for SCSI-I, SCSI-II, and SCSI-III peripherals,
722 including hard disks, optical disks, tape drives (including
723 DAT, 8mm Exabyte, Mammoth, and DLT), medium changers,
724 processor target devices and CD-ROM drives. WORM devices that
725 support CD-ROM commands are supported for read-only access by
726 the CD-ROM drivers (such as &man.cd.4;). WORM/CD-R/CD-RW
727 writing support is provided by &man.cdrecord.1;, which is a
728 part of the <filename
729 role="package">sysutils/cdrtools</filename> port in the Ports
732 <para>The following CD-ROM type systems are supported at this
737 <para>SCSI interface (also includes ProAudio Spectrum and
738 SoundBlaster SCSI) (&man.cd.4;)</para>
742 <para>[&arch.i386;] Sony proprietary interface (all models)
747 <para>ATAPI IDE interface (&man.acd.4;)</para>
751 <para>[&arch.i386;] The following device is unmaintained:</para>
755 <para>Mitsumi proprietary CD-ROM interface (all models)
761 <sect2 id="ethernet">
762 <title>Ethernet Interfaces</title>
776 <para>[&arch.amd64;, &arch.i386;] Broadcom BCM4401 based Fast
777 Ethernet adapters (&man.bfe.4; driver)</para>
785 <para>[&arch.amd64;, &arch.i386;] Crystal Semiconductor
786 CS89x0-based NICs (&man.cs.4; driver)</para>
866 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;] SMC 83c17x
867 (EPIC)-based Ethernet NICs (&man.tx.4; driver)</para>
888 <title>FDDI Interfaces</title>
890 <para>[&arch.i386;, &arch.pc98;] DEC DEFPA PCI (&man.fpa.4;
893 <para>[&arch.i386;] DEC DEFEA EISA (&man.fpa.4; driver)</para>
897 <title>ATM Interfaces</title>
899 <para>[&arch.i386;, &arch.pc98;] Midway-based ATM interfaces
900 (&man.en.4; driver)</para>
902 <para>[&arch.i386;, &arch.pc98; &arch.sparc64;] FORE Systems,
903 Inc. PCA-200E ATM PCI Adapters (hfa and &man.fatm.4;
906 <para>[&arch.i386;, &arch.pc98;] IDT NICStAR 77201/211-based ATM
907 Adapters (&man.idt.4; driver)</para>
909 <para>[&arch.i386;, &arch.pc98; &arch.sparc64;] FORE Systems,
910 Inc. HE155 and HE622 ATM interfaces (&man.hatm.4;
913 <para>[&arch.i386;, &arch.pc98;] IDT77252-based ATM cards
914 (&man.patm.4; driver)</para>
918 <title>Wireless Network Interfaces</title>
920 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;] Cisco/Aironet
921 802.11b wireless adapters (&man.an.4; driver)</para>
927 <para>[&arch.i386;, &arch.amd64;] Intel PRO/Wireless 2100
928 MiniPCI network adapter (&man.ipw.4; driver)</para>
930 <para>[&arch.i386;, &arch.amd64;] Intel PRO/Wireless
931 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters
932 (&man.iwi.4; driver)</para>
934 <para>[&arch.i386;, &arch.amd64;] Intel Wireless WiFi Link
935 4965AGN IEEE 802.11n PCI network adapters
936 (&man.iwn.4; driver)</para>
938 <para>[&arch.i386;, &arch.amd64;] Marvell Libertas IEEE 802.11b/g
939 PCI network adapters (&man.malo.4; driver)</para>
953 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;] Lucent
954 Technologies WaveLAN/IEEE 802.11b wireless network adapters
955 and workalikes using the Lucent Hermes, Intersil PRISM-II,
956 Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24
957 chipsets (&man.wi.4; driver)</para>
959 <para>[&arch.i386;] NCR / AT&T / Lucent Technologies WaveLan
960 T1-speed ISA/radio LAN cards (&man.wl.4; driver)</para>
962 <para>[&arch.i386;, &arch.amd64;] Intel PRO/Wireless 3945ABG
963 MiniPCI network adapters (&man.wpi.4; driver)</para>
968 <sect2 id="misc-network">
969 <title>Miscellaneous Networks</title>
983 <title>ISDN Interfaces</title>
985 <para>[&arch.i386;] AcerISDN P10 ISA PnP (experimental)</para>
987 <para>[&arch.i386;] Asuscom ISDNlink 128K ISA</para>
989 <para>[&arch.i386;] ASUSCOM P-IN100-ST-D (and other Winbond
990 W6692-based cards)</para>
992 <para>[&arch.i386;] AVM</para>
1000 <para>B1 ISA (tested with V2.0)</para>
1004 <para>B1 PCI (tested with V4.0)</para>
1008 <para>Fritz!Card classic</para>
1012 <para>Fritz!Card PnP</para>
1016 <para>Fritz!Card PCI</para>
1020 <para>Fritz!Card PCI, Version 2</para>
1028 <para>[&arch.i386;] Creatix</para>
1032 <para>ISDN-S0</para>
1036 <para>ISDN-S0 P&P</para>
1040 <para>[&arch.i386;] Compaq Microcom 610 ISDN (Compaq series
1041 PSB2222I) ISA PnP</para>
1043 <para>[&arch.i386;] Dr. Neuhaus Niccy Go@ and compatibles</para>
1045 <para>[&arch.i386;] Dynalink IS64PPH and IS64PPH+</para>
1047 <para>[&arch.i386;] Eicon Diehl DIVA 2.0 and 2.02</para>
1049 <para>[&arch.i386;] ELSA</para>
1053 <para>ELSA PCC-16</para>
1057 <para>QuickStep 1000pro ISA</para>
1061 <para>MicroLink ISDN/PCI</para>
1065 <para>QuickStep 1000pro PCI</para>
1069 <para>[&arch.i386;] ITK ix1 Micro ( < V.3, non-PnP version
1072 <para>[&arch.i386;] Sedlbauer Win Speed</para>
1074 <para>[&arch.i386;] Siemens I-Surf 2.0</para>
1076 <para>[&arch.i386;] TELEINT ISDN SPEED No.1
1077 (experimental)</para>
1079 <para>[&arch.i386;] Teles</para>
1091 <para>S0/16.3</para>
1095 <para>S0/16.3 PnP</para>
1099 <para>16.3c ISA PnP (experimental)</para>
1103 <para>Teles PCI-TJ</para>
1107 <para>[&arch.i386;] Traverse Technologies NETjet-S PCI</para>
1109 <para>[&arch.i386;] USRobotics Sportster ISDN TA intern</para>
1111 <para>[&arch.i386;] Winbond W6692 based PCI cards</para>
1115 <title>Serial Interfaces</title>
1117 <para>[&arch.amd64;, &arch.i386;] <quote>PC standard</quote>
1118 8250, 16450, and 16550-based serial ports (&man.sio.4;
1125 <para>[&arch.amd64;, &arch.i386;] AST 4 port serial card using
1130 <para>ARNET 8 port serial card using shared IRQ</para>
1134 <para>ARNET (now Digiboard) Sync 570/i high-speed
1139 <para>[&arch.i386;] Boca multi-port serial cards</para>
1143 <para>Boca BB1004 4-Port serial card (Modems
1144 <emphasis>not</emphasis> supported)</para>
1148 <para>Boca IOAT66 6-Port serial card (Modems
1153 <para>Boca BB1008 8-Port serial card (Modems
1154 <emphasis>not</emphasis> supported)</para>
1158 <para>Boca BB2016 16-Port serial card (Modems
1163 <para>[&arch.i386;] Comtrol Rocketport card (&man.rp.4;
1166 <para>[&arch.i386;] Cyclades Cyclom-Y serial board (&man.cy.4;
1169 <para>[&arch.i386;] STB 4 port card using shared IRQ</para>
1171 <para>[&arch.i386;] DigiBoard intelligent serial cards (digi
1174 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;] PCI-Based
1175 multi-port serial boards (&man.puc.4; driver)</para>
1179 <para>[&arch.amd64;, &arch.i386;] Actiontech 56K PCI</para>
1183 <para>[&arch.amd64;, &arch.i386;] Avlab Technology, PCI IO 2S
1184 and PCI IO 4S</para>
1188 <para>[&arch.amd64;, &arch.i386;] Comtrol RocketPort 550</para>
1192 <para>[&arch.amd64;, &arch.i386;] Decision Computers PCCOM
1193 4-port serial and dual port RS232/422/485</para>
1197 <para>[&arch.ia64;] Diva Serial (GSP) Multiport UART</para>
1201 <para>[&arch.amd64;, &arch.i386;] Dolphin Peripherals
1202 4025/4035/4036</para>
1206 <para>[&arch.amd64;, &arch.i386;] IC Book Labs Dreadnought
1207 16x Lite and Pro</para>
1211 <para>[&arch.amd64;, &arch.i386;] Lava Computers
1212 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550</para>
1216 <para>[&arch.amd64;, &arch.i386;] Middle Digital, Weasle
1221 <para>[&arch.amd64;, &arch.i386;] Moxa Industio CP-114,
1222 Smartio C104H-PCI and C168H/PCI</para>
1226 <para>[&arch.amd64;, &arch.i386;] NEC PK-UG-X001 and
1231 <para>[&arch.amd64;, &arch.i386;] Netmos NM9835
1236 <para>[&arch.amd64;, &arch.i386;] Oxford Semiconductor
1237 OX16PCI954 PCI UART</para>
1241 <para>[&arch.amd64;, &arch.i386;] Syba Tech SD-LAB
1242 PCI-4S2P-550-ECP</para>
1246 <para>[&arch.amd64;, &arch.i386;] SIIG Cyber I/O PCI
1247 16C550/16C650/16C850</para>
1251 <para>[&arch.amd64;, &arch.i386;] SIIG Cyber 2P1S PCI
1252 16C550/16C650/16C850</para>
1256 <para>[&arch.amd64;, &arch.i386;] SIIG Cyber 2S1P PCI
1257 16C550/16C650/16C850</para>
1261 <para>[&arch.amd64;, &arch.i386;] SIIG Cyber 4S PCI
1262 16C550/16C650/16C850</para>
1266 <para>[&arch.amd64;, &arch.i386;] SIIG Cyber Serial (Single
1267 and Dual) PCI 16C550/16C650/16C850</para>
1271 <para>[&arch.amd64;, &arch.i386;] Syba Tech
1272 Ltd. PCI-4S2P-550-ECP</para>
1276 <para>[&arch.amd64;, &arch.i386;] Titan PCI-200H and
1281 <para>[&arch.amd64;, &arch.i386;] US Robotics (3Com) 3CP5609
1286 <para>[&arch.amd64;, &arch.i386;] VScom PCI-400 and
1293 <para>[&arch.i386;, &arch.amd64;] Specialix SI/XIO/SX multiport
1294 serial cards, with both the older SIHOST2.x and the
1295 <quote>enhanced</quote> (transputer based, aka JET) host cards
1296 (ISA, EISA and PCI) are supported. Note that the newer SX+
1297 PCI cards are not currently supported. (&man.si.4;
1300 <para>[&arch.pc98;] Internel serial interfaces (&man.sio.4;
1305 <para>PC-9801 on-board</para>
1308 <para>PC-9821 2'nd CCU (flags 0x12000000)</para>
1312 <para>[&arch.pc98;] NEC PC-9861K, PC-9801-101 and Midori-Denshi
1313 MDC-926Rs (&man.sio.4; driver)</para>
1317 <para>COM2 (flags 0x01000000)</para>
1321 <para>COM3 (flags 0x02000000)</para>
1325 <para>[&arch.pc98;] NEC PC-9801-120 (&man.sio.4; driver)</para>
1328 <para>"flags 0x11000000" is necessary in kernel
1329 configuration.</para>
1332 <para>[&arch.pc98;] Microcore MC-16550, MC-16550II, MC-RS98
1333 (&man.sio.4; driver)</para>
1336 <para>"flags 0x14000?01" is necessary in kernel
1337 configuration.</para>
1340 <para>[&arch.pc98;] Media Intelligent RSB-2000, RSB-3000 and
1341 AIWA B98-02 (&man.sio.4; driver)</para>
1344 <para>"flags 0x15000?01" is necessary in kernel
1345 configuration.</para>
1348 <para>[&arch.pc98;] Media Intelligent RSB-384 (&man.sio.4;
1352 <para>"flags 0x16000001" is necessary in kernel
1353 configuration.</para>
1356 <para>[&arch.pc98;] I-O DATA RSA-98III (&man.sio.4;
1360 <para>"flags 0x18000?01" is necessary in kernel
1361 configuration.</para>
1364 <para>[&arch.pc98;] Hayes ESP98 (&man.sio.4; driver)</para>
1367 <para>"options COM_ESP" and "flags 0x19000000" are necessary
1368 in kernel configuration.</para>
1374 <title>Sound Devices</title>
1378 &hwlist.snd.als4000;
1382 &hwlist.snd.audiocs;
1392 &hwlist.snd.emu10k1;
1394 &hwlist.snd.emu10kx;
1398 &hwlist.snd.envy24ht;
1412 &hwlist.snd.maestro;
1414 &hwlist.snd.maestro3;
1418 &hwlist.snd.neomagic;
1426 &hwlist.snd.t4dwave;
1428 &hwlist.snd.via8233;
1430 &hwlist.snd.via82c686;
1434 <para>[&arch.pc98;] NEC PC-9801-73, 86 and compatibles (nss
1439 <para>NEC A-MATE internal sound</para>
1443 <para>Q-Vision WaveStar, WaveMaster</para>
1447 <para>[&arch.pc98;] NEC X-MATE, CanBe, ValueStar internal (mss
1450 <para>[&arch.pc98;] Creative Technologies SoundBlaster(98)
1451 (&man.sb.4; driver)</para>
1453 <para>[&arch.pc98;] I-O DATA CD-BOX (&man.sb.4; driver)</para>
1455 <para>[&arch.pc98;] MPU-401 and compatible interfaces (mpu
1460 <para>Q-Vision WaveStar</para>
1466 <title>Camera and Video Capture Devices</title>
1470 <para>[&arch.i386;] Connectix QuickCam</para>
1474 <title>USB Devices</title>
1476 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;] A
1477 range of USB peripherals are supported; devices known to work
1478 are listed in this section. Owing to the generic nature of
1479 most USB devices, with some exceptions any device of a given
1480 class will be supported, even if not explicitly listed
1484 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1485 USB Ethernet adapters can be found in the section listing
1486 <link linkend="ethernet">Ethernet
1487 interfaces</link>.</para>
1491 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1492 USB Bluetooth adapters can be found in <link
1493 linkend="bluetooth">Bluetooth</link> section.</para>
1500 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;] USB
1501 2.0 controllers using the EHCI interface (&man.ehci.4;
1504 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1507 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1508 Keyboards (&man.ukbd.4; driver)</para>
1510 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;]
1511 Miscellaneous</para>
1515 <para>Assist Computer Systems PC Camera C-M1</para>
1519 <para>ActiveWire I/O Board</para>
1523 <para>Creative Technology Video Blaster WebCam Plus</para>
1527 <para>D-Link DSB-R100 USB Radio (&man.ufm.4; driver)</para>
1531 <para>Mirunet AlphaCam Plus</para>
1539 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;] Mice
1540 (&man.ums.4; driver)</para>
1556 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;] Audio Devices
1557 (&man.uaudio.4; driver)</para>
1562 <sect2 id="firewire">
1563 <title>IEEE 1394 (Firewire) Devices</title>
1567 <para>[&arch.amd64;, &arch.i386;, &arch.sparc64;] Serial Bus
1568 Protocol 2 (SBP-2) storage devices (&man.sbp.4; driver)</para>
1571 <sect2 id="bluetooth">
1572 <title>Bluetooth Devices</title>
1579 <sect2 id="crypto-accel">
1580 <title>Cryptographic Accelerators</title>
1590 <title>Miscellaneous</title>
1592 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;]
1593 FAX-Modem/PCCARD</para>
1597 <para>MELCO IGM-PCM56K/IGM-PCM56KH</para>
1601 <para>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD
1606 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;] Floppy drives
1607 (&man.fdc.4; driver)</para>
1609 <para>[&arch.amd64;, &arch.i386;] VGA-compatible video cards
1610 (&man.vga.4; driver)</para>
1613 <para>Information regarding specific video cards and
1614 compatibility with <application>Xorg</application> can be
1615 found at <ulink url="http://www.x.org/"></ulink>.</para>
1618 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1619 Keyboards including:</para>
1623 <para>[&arch.i386;] AT-style keyboards (&man.atkbd.4;
1628 <para>[&arch.amd64;, &arch.i386;] PS/2 keyboards
1629 (&man.atkbd.4; driver)</para>
1633 <para>[&arch.pc98;] Standard keyboards</para>
1637 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1638 USB keyboards (&man.ukbd.4; driver)</para>
1642 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1643 Pointing devices including:</para>
1647 <para>[&arch.amd64;, &arch.i386;, &arch.pc98;] Bus mice and
1648 compatible devices (&man.mse.4; driver)</para>
1652 <para>[&arch.amd64;, &arch.i386;] PS/2 mice and compatible
1653 devices, including many laptop pointing devices
1654 (&man.psm.4; driver)</para>
1658 <para>Serial mice and compatible devices</para>
1662 <para>[&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;]
1663 USB mice (&man.ums.4; driver)</para>
1668 <para>&man.moused.8; has more information on using pointing
1669 devices with &os;. Information on using pointing devices
1670 with <application>Xorg</application> can be found at <ulink
1671 url="http://www.x.org/"></ulink>.</para>
1674 <para>[&arch.amd64;, &arch.i386;] <quote>PC standard</quote>
1675 parallel ports (&man.ppc.4; driver)</para>
1677 <para>[&arch.pc98;] <quote>PC-9821 standard</quote> parallel
1678 ports (&man.ppc.4; driver)</para>
1680 <para>[&arch.i386;, &arch.amd64;] PC-compatible joysticks
1681 (&man.joy.4; driver)</para>
1683 <para>[&arch.pc98;] Joystick port of SoundBlaster(98)
1684 (&man.joy.4; driver)</para>
1686 <para>[&arch.i386;, &arch.pc98;] PHS Data Communication
1691 <para>NTT DoCoMo P-in Comp@ct</para>
1695 <para>Panasonic KX-PH405</para>
1699 <para>SII MC-P200</para>
1703 <para>[&arch.i386;] Xilinx XC6200-based reconfigurable hardware
1704 cards compatible with the HOT1 from <ulink
1705 url="http://www.vcc.com/">Virtual Computers</ulink> (xrpu
1708 <para>[&arch.pc98;] Power Management Controller of NEC PC-98
1709 Note (pmc driver)</para>