FreeBSD/powerpc 6.3-RELEASE Hardware +Notes

+ +

The FreeBSD Documentation Project

+ +

Table of Contents

1 Introduction

2 Supported Processors and Motherboards

3 Supported Devices

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

+ +

+
+
This is a preliminary document. It is incomplete, and in need of additional +content.
+
+

+ +

1 Introduction

+ +

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

+ +

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

+ +

2 Supported Processors and +Motherboards

+ +

The information for this paragraph has yet to be compiled.

+ +

3 Supported Devices

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

This section describes the devices currently known to be supported by with FreeBSD on +the PowerPC platform. Other configurations may also work, but simply have not been tested +yet. Feedback, updates, and corrections to this list are encouraged.

+ +

Where possible, the drivers applicable to each device or class of devices is listed. +If the driver in question has a manual page in the FreeBSD base distribution (most +should), it is referenced here. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.

+ +

+
Note: The device lists in this document are being generated automatically from +FreeBSD manual pages. This means that some devices, which are supported by multiple +drivers, may appear multiple times.
+

+ +

3.1 Disk Controllers

+ +

The +ahc(4) driver +supports the following SCSI host adapter chips and SCSI controller cards:

+ +

+
Adaptec AIC7770 host adapter chip
+
+
Adaptec AIC7850 host adapter chip
+
+
Adaptec AIC7860 host adapter chip
+
+
Adaptec AIC7870 host adapter chip
+
+
Adaptec AIC7880 host adapter chip
+
+
Adaptec AIC7890 host adapter chip
+
+
Adaptec AIC7891 host adapter chip
+
+
Adaptec AIC7892 host adapter chip
+
+
Adaptec AIC7895 host adapter chip
+
+
Adaptec AIC7896 host adapter chip
+
+
Adaptec AIC7897 host adapter chip
+
+
Adaptec AIC7899 host adapter chip
+
+
Adaptec 274X(W)
+
+
Adaptec 274X(T)
+
+
Adaptec 284X
+
+
Adaptec 2910
+
+
Adaptec 2915
+
+
Adaptec 2920
+
+
Adaptec 2930C
+
+
Adaptec 2930U2
+
+
Adaptec 2940
+
+
Adaptec 2940J
+
+
Adaptec 2940N
+
+
Adaptec 2940U
+
+
Adaptec 2940AU
+
+
Adaptec 2940UW
+
+
Adaptec 2940UW Dual
+
+
Adaptec 2940UW Pro
+
+
Adaptec 2940U2W
+
+
Adaptec 2940U2B
+
+
Adaptec 2950U2W
+
+
Adaptec 2950U2B
+
+
Adaptec 19160B
+
+
Adaptec 29160B
+
+
Adaptec 29160N
+
+
Adaptec 3940
+
+
Adaptec 3940U
+
+
Adaptec 3940AU
+
+
Adaptec 3940UW
+
+
Adaptec 3940AUW
+
+
Adaptec 3940U2W
+
+
Adaptec 3950U2
+
+
Adaptec 3960
+
+
Adaptec 39160
+
+
Adaptec 3985
+
+
Adaptec 4944UW
+
+
NEC PC-9821Xt13 (PC-98)
+
+
NEC RvII26 (PC-98)
+
+
NEC PC-9821X-B02L/B09 (PC-98)
+
+
NEC SV-98/2-B03 (PC-98)
+
+
Many motherboards with on-board SCSI support
+

+ +

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

+ +

+
MegaRAID SATA 150-4
+
+
MegaRAID SATA 150-6
+
+
MegaRAID SATA 300-4X
+
+
MegaRAID SATA 300-8X
+
+
MegaRAID SCSI 320-1E
+
+
MegaRAID SCSI 320-2E
+
+
MegaRAID SCSI 320-4E
+
+
MegaRAID SCSI 320-0X
+
+
MegaRAID SCSI 320-2X
+
+
MegaRAID SCSI 320-4X
+
+
MegaRAID SCSI 320-0
+
+
MegaRAID SCSI 320-1
+
+
MegaRAID SCSI 320-2
+
+
MegaRAID SCSI 320-4
+
+
MegaRAID Series 418
+
+
MegaRAID i4 133 RAID
+
+
MegaRAID Elite 1500 (Series 467)
+
+
MegaRAID Elite 1600 (Series 493)
+
+
MegaRAID Elite 1650 (Series 4xx)
+
+
MegaRAID Enterprise 1200 (Series 428)
+
+
MegaRAID Enterprise 1300 (Series 434)
+
+
MegaRAID Enterprise 1400 (Series 438)
+
+
MegaRAID Enterprise 1500 (Series 467)
+
+
MegaRAID Enterprise 1600 (Series 471)
+
+
MegaRAID Express 100 (Series 466WS)
+
+
MegaRAID Express 200 (Series 466)
+
+
MegaRAID Express 300 (Series 490)
+
+
MegaRAID Express 500 (Series 475)
+
+
Dell PERC
+
+
Dell PERC 2/SC
+
+
Dell PERC 2/DC
+
+
Dell PERC 3/DCL
+
+
Dell PERC 3/QC
+
+
Dell PERC 4/DC
+
+
Dell PERC 4/IM
+
+
Dell PERC 4/SC
+
+
Dell PERC 4/Di
+
+
Dell PERC 4e/DC
+
+
Dell PERC 4e/Di
+
+
Dell PERC 4e/Si
+
+
Dell PERC 4ei
+
+
HP NetRAID-1/Si
+
+
HP NetRAID-3/Si (D4943A)
+
+
HP Embedded NetRAID
+
+
Intel RAID Controller SRCS16
+
+
Intel RAID Controller SRCU42X
+

+ +

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

+ +

+
ISP1000
+
+
ISP1020
+
+
ISP1040
+
+
Qlogic 1240
+
+
Qlogic 1020
+
+
Qlogic 1040
+
+
Qlogic 1080
+
+
Qlogic 1280
+
+
Qlogic 12160
+
+
Qlogic 210X
+
+
Qlogic 220X
+
+
Qlogic 2300
+
+
Qlogic 2312
+
+
Qlogic 234X
+
+
Qlogic 2322
+
+
Qlogic 200
+
+
Qlogic 2422
+
+
Qlogic 2432
+

+ +

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

+ +

+
LSI Logic 53c1030, LSI Logic LSI2x320-X (Single and Dual Ultra320 SCSI)
+
+
LSI Logic AS1064, LSI Logic AS1068
+
+
LSI Logic FC909 (1Gb/s Fibre Channel)
+
+
LSI Logic FC909A (Dual 1Gb/s Fibre Channel)
+
+
LSI Logic FC919, LSI Logic 7102XP-LC (Single 2Gb/s Fibre Channel)
+
+
LSI Logic FC929, LSI Logic FC929X, LSI Logic 7202XP-LC (Dual 2Gb/s Fibre Channel)
+
+
LSI Logic FC949X (Dual 4Gb/s Fibre Channel)
+
+
LSI Logic FC949ES (Dual 4Gb/s Fibre Channel PCI-Express)
+

+ +

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

+ +

+
Dell PowerEdge 1750 thru 2850
+
+
IBM eServer xSeries 335
+

+ +

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

+ +

The +sym(4) driver +provides support for the following Symbios/LSI Logic PCI SCSI controllers:

+ +

+
53C810
+
+
53C810A
+
+
53C815
+
+
53C825
+
+
53C825A
+
+
53C860
+
+
53C875
+
+
53C876
+
+
53C895
+
+
53C895A
+
+
53C896
+
+
53C897
+
+
53C1000
+
+
53C1000R
+
+
53C1010-33
+
+
53C1010-66
+
+
53C1510D
+

+ +

The SCSI controllers supported by +sym(4) can be +either embedded on a motherboard, or on one of the following add-on boards:

+ +

+
ASUS SC-200, SC-896
+
+
Data Technology DTC3130 (all variants)
+
+
DawiControl DC2976UW
+
+
Diamond FirePort (all)
+
+
I-O DATA SC-UPCI (PC-98)
+
+
Logitec LHA-521UA (PC-98)
+
+
NCR cards (all)
+
+
Symbios cards (all)
+
+
Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and 390U3W
+
+
Tyan S1365
+

+ +

With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and +SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, +8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM +drives. WORM devices that support CD-ROM commands are supported for read-only access by +the CD-ROM drivers (such as cd(4)). +WORM/CD-R/CD-RW writing support is provided by cdrecord(1), which is +a part of the sysutils/cdrtools port in the Ports Collection.

+ +

The following CD-ROM type systems are supported at this time:

+ +

+
SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (cd(4))
+
+
ATAPI IDE interface ( +acd(4))
+

+ +
+
+

+ +

3.2 Ethernet Interfaces

+ +

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

+ +

+
Abocom UFE1000, DSB650TX_NA
+
+
Accton USB320-EC, SpeedStream
+
+
ADMtek AN986, AN8511
+
+
Billionton USB100, USB100LP, USB100EL, USBE100
+
+
Corega Ether FEther USB-T, FEther USB-TX, FEther USB-TXS
+
+
D-Link DSB-650, DSB-650TX, DSB-650TX-PNA
+
+
Elecom LD-USBL/TX
+
+
Elsa Microlink USB2Ethernet
+
+
HP hn210e
+
+
I-O Data USB ETTX
+
+
Kingston KNU101TX
+
+
LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, +USB100TX, USB100H1
+
+
MELCO LUA-TX, LUA2-TX
+
+
Netgear FA101
+
+
Planex UE-200TX
+
+
Sandberg USB to Network Link (model number 133-06)
+
+
Siemens Speedstream
+
+
SmartBridges smartNIC
+
+
SMC 2202USB
+
+
SOHOware NUB100
+

+ +

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

+ +

+
Buffalo (Melco Inc.) LUA-U2-KTX
+
+
D-Link DUB-E100, revision A
+
+
LinkSys USB200M
+
+
Netgear FA120
+
+
Sitecom LN-029
+
+
System TALKS Inc. SGC-X2UL
+

+ +

The +cue(4) driver +supports CATC USB-EL1210A based USB Ethernet adapters including:

+ +

+
Belkin F5U011/F5U111
+
+
CATC Netmate
+
+
CATC Netmate II
+
+
SmartBridges SmartLink
+

+ +

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

+ +

+
DEC/Intel 21143
+
+
ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II
+
+
ASIX Electronics AX88140A and AX88141
+
+
Conexant LANfinity RS7112 (miniPCI)
+
+
Davicom DM9009, DM9100, DM9102 and DM9102A
+
+
Lite-On 82c168 and 82c169 PNIC
+
+
Lite-On/Macronix 82c115 PNIC II
+
+
Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732
+
+
Xircom X3201 (cardbus only)
+

+ +

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

+ +

+
3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)
+
+
Abocom FE2500
+
+
Accton EN1217 (98715A)
+
+
Accton EN2242 MiniPCI
+
+
Adico AE310TX (98715A)
+
+
Alfa Inc GFC2204 (ASIX AX88140A)
+
+
Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, +non-MII)
+
+
Built in DE500-BA on DEC Alpha workstations (21143, non-MII)
+
+
Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, +MII)
+
+
Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)
+
+
CNet Pro110B (ASIX AX88140A)
+
+
CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)
+
+
Compex RL100-TX (98713 or 98713A)
+
+
D-Link DFE-570TX (21143, MII, quad port)
+
+
Digital DE500-BA 10/100 (21143, non-MII)
+
+
ELECOM Laneed LD-CBL/TXA (ADMtek AN985)
+
+
Hawking CB102 CardBus
+
+
IBM EtherJet Cardbus Adapter
+
+
Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)
+
+
Jaton XpressNet (Davicom DM9102)
+
+
Kingston KNE100TX (21143, MII)
+
+
Kingston KNE110TX (PNIC 82c169)
+
+
LinkSys LNE100TX (PNIC 82c168, 82c169)
+
+
LinkSys LNE100TX v2.0 (PNIC II 82c115)
+
+
LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)
+
+
Matrox FastNIC 10/100 (PNIC 82c168, 82c169)
+
+
Melco LGY-PCI-TXL
+
+
Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)
+
+
Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)
+
+
NDC SOHOware SFA110A (98713A)
+
+
NDC SOHOware SFA110A Rev B4 (98715AEC-C)
+
+
NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)
+
+
Netgear FA511
+
+
PlaneX FNW-3602-T (ADMtek AN985)
+
+
SMC EZ Card 10/100 1233A-TX (ADMtek AN985)
+
+
SVEC PN102-TX (98713)
+
+
Xircom Cardbus Realport
+
+
Xircom Cardbus Ethernet 10/100
+
+
Xircom Cardbus Ethernet II 10/100
+

+ +

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

+ +

+
Intel EtherExpress PRO/10
+
+
Intel InBusiness 10/100
+
+
Intel PRO/100B / EtherExpressPRO/100 B PCI Adapter
+
+
Intel PRO/100+ Management Adapter
+
+
Intel PRO/100 VE Desktop Adapter
+
+
Intel PRO/100 M Desktop Adapter
+
+
Intel PRO/100 S Desktop, Server and Dual-Port Server Adapters
+
+
Contec C-NET(PI)-100TX (PC-98)
+
+
NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)
+
+
NEC PC-9821X-B06 (PC-98)
+
+
Many on-board network interfaces on Intel motherboards
+

+ +

Chips supported by the +gem(4) driver +include:

+ +

+
Apple GMAC
+
+
Sun ERI 10/100 Mbps Ethernet
+
+
Sun GEM Gigabit Ethernet
+

+ +

The +hme(4) driver +supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server +models. Cards supported by the +hme(4) driver +include:

+ +

+
Sun PCI SunSwift Adapter
+
+
Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)
+
+
Sun PCI Sun100BaseT Adapter 2.0
+
+
Sun SBus Sun100BaseT 2.0
+
+
Sun PCI Quad FastEthernet Controller
+
+
Sun SBus Quad FastEthernet Controller
+

+ +

The +kue(4) driver +supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:

+ +

+
3Com 3c19250
+
+
3Com 3c460 HomeConnect Ethernet USB Adapter
+
+
ADS Technologies USB-10BT
+
+
AOX USB101
+
+
ATen UC10T
+
+
Abocom URE 450
+
+
Corega USB-T
+
+
D-Link DSB-650C
+
+
Entrega NET-USB-E45, NET-HUB-3U1E
+
+
I/O Data USB ETT
+
+
Kawasaki DU-H3E
+
+
LinkSys USB10T
+
+
Netgear EA101
+
+
Peracom USB Ethernet Adapter
+
+
Psion Gold Port USB Ethernet adapter
+
+
SMC 2102USB, 2104USB
+

+ +

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

+ +

+
Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)
+
+
Compaq Evo N1015v Integrated Ethernet (8139C+)
+
+
Corega CG-LAPCIGT Gigabit Ethernet (8169S)
+
+
D-Link DGE-528(T) Gigabit Ethernet (8169S)
+
+
Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)
+
+
LevelOne GNC-0105T (8169S)
+
+
LinkSys EG1032 (32-bit PCI)
+
+
PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)
+
+
Xterasys XN-152 10/100/1000 NIC (8169)
+

+ +

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

+ +

+
Accton “Cheetah” EN1207D (MPX 5030/5038; RealTek 8139 clone)
+
+
Allied Telesyn AT2550
+
+
Allied Telesyn AT2500TX
+
+
Belkin F5D5000
+
+
BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)
+
+
Compaq HNE-300
+
+
CompUSA no-name 10/100 PCI Ethernet NIC
+
+
Corega FEther CB-TXD
+
+
Corega FEtherII CB-TXD
+
+
D-Link DFE-528TX
+
+
D-Link DFE-530TX+
+
+
D-Link DFE-538TX
+
+
D-Link DFE-690TXD
+
+
Edimax EP-4103DL CardBus
+
+
Encore ENL832-TX 10/100 M PCI
+
+
Farallon NetLINE 10/100 PCI
+
+
Genius GF100TXR
+
+
GigaFast Ethernet EE100-AXP
+
+
KTX-9130TX 10/100 Fast Ethernet
+
+
LevelOne FPC-0106TX
+
+
Longshine LCS-8038TX-R
+
+
NDC Communications NE100TX-E
+
+
Netronix Inc. EA-1210 NetEther 10/100
+
+
Nortel Networks 10/100BaseTX
+
+
OvisLink LEF-8129TX
+
+
OvisLink LEF-8139TX
+
+
Peppercon AG ROL-F
+
+
Planex FNW-3603-TX
+
+
Planex FNW-3800-TX
+
+
SMC EZ Card 10/100 PCI 1211-TX
+
+
SOHO (PRAGMATIC) UE-1211C
+

+ +

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

+ +

+
3Com 3c900-TPO
+
+
3Com 3c900-COMBO
+
+
3Com 3c905-TX
+
+
3Com 3c905-T4
+
+
3Com 3c900B-TPO
+
+
3Com 3c900B-TPC
+
+
3Com 3c900B-FL
+
+
3Com 3c900B-COMBO
+
+
3Com 3c905B-T4
+
+
3Com 3c905B-TX
+
+
3Com 3c905B-FX
+
+
3Com 3c905B-COMBO
+
+
3Com 3c905C-TX
+
+
3Com 3c980, 3c980B, and 3c980C server adapters
+
+
3Com 3cSOHO100-TX OfficeConnect adapters
+
+
3Com 3c450 HomeConnect adapters
+
+
3Com 3c555, 3c556 and 3c556B mini-PCI adapters
+
+
3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, +3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters
+
+
3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded +adapters
+

+ +

Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a +built-in proprietary modem. Neither the xl(4) driver nor any +other driver supports this modem.

+ +

3.3 Token Ring Interfaces

+ +

3.4 FDDI Interfaces

+ +

3.5 ATM Interfaces

+ +

3.6 Wireless Network Interfaces

+ +

[i386, amd64] Intel PRO/Wireless 2100 MiniPCI network adapter ( +ipw(4) +driver)

+ +

[i386, amd64] Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network +adapters ( +iwi(4) +driver)

+ +

3.7 Miscellaneous +Networks

+ +

3.8 ISDN Interfaces

+ +

3.9 Serial Interfaces

+ +

3.10 Sound Devices

+ +

3.11 Camera and Video Capture +Devices

+ +

3.12 USB Devices

+ +

The +ohci(4) driver +supports all OHCI v1.0 compliant controllers including:

+ +

+
AcerLabs M5237 (Aladdin-V)
+
+
AMD-756
+
+
OPTi 82C861 (FireLink)
+
+
NEC uPD 9210
+
+
CMD Tech 670 (USB0670)
+
+
CMD Tech 673 (USB0673)
+
+
NVIDIA nForce3
+
+
Sun PCIO-2 (RIO USB)
+

+ +

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

+ +

+
Intel 82371AB/EB (PIIX4)
+
+
Intel 82371SB (PIIX3)
+
+
VIA 83C572
+

+ +

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

+ +

+
Diamond MultiMedia Rio 500
+
+
Diamond MultiMedia Rio 600
+
+
Diamond MultiMedia Rio 800
+

+ +

The +ulpt(4) driver +provides support for USB printers and parallel printer conversion cables, including the +following:

+ +

+
ATen parallel printer adapter
+
+
Belkin F5U002 parallel printer adapter
+
+
Canon BJ F850, S600
+
+
Canon LBP-1310, 350
+
+
Entrega USB-to-parallel printer adapter
+
+
Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)
+
+
Oki Data MICROLINE ML660PS
+
+
Seiko Epson PM-900C, 880C, 820C, 730C
+

+ +

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

+ +

+
Belkin F5U109
+
+
Belkin F5U409
+
+
D-Link DU-H3SP USB BAY Hub
+
+
Magic Control Technology USB-232
+
+
Sitecom USB-232
+

+ +

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

+ +

+
Acer Acerscan: 320U, 620U, 640U, 640BT, 1240U, C310U;
+
+
AGFA SnapScan: 1212U, 1236U, e20, e25, e26, e40, e50, e52, SnapScan Touch;
+
+
Avision 1200U
+
+
Canon CanoScan: D660U, N656U, N676U, N1220U, LIDE 20, LIDE 25, LIDE 30;
+
+
Epson Perfection: 610, 636U / 636Photo, 640U, 1200U / 1200Photo, 1240U / 1240Photo, +1250, 1260, 1270, 1600, 1640SU, 1650, 1660, 1670, 2480, 3200, 3500, 3590, 4200, 4990;
+
+
Epson: GT-8400UF, GT-9300UF, GT-9700F;
+
+
Epson Stylus: Photo RX425, CX3650, DX-5000, DX-5050, DX-6000, DX-6050 (and possibly +more in the CX-5000 and DX-3800..DX-7000 family);
+
+
Hewlett Packard: Photosmart S20
+
+
Hewlett Packard Scanjet: 2200C, 3300C, 3400CSE, 4100C, 4200C, 4300C, 5200C, 5300C, +5400C, 6200C, 6300C, 8200C, 8250C, 8290C;
+
+
KYE ColorPage Vivid-Pro
+
+
Microtek Phantom: 336CX, C6;
+
+
Microtek ScanMaker: V6UL V6USL, X6U;
+
+
Minolta 5400
+
+
Mustek: 600 CU, 1200 CU, 1200 UB, 1200 USB;
+
+
Mustek BearPaw: 1200F, 1200TA;
+
+
NatSemi BearPaw 1200
+
+
Nikon CoolScan LS40 ED
+
+
Primax 6200
+
+
Primax Colorado: 1200u, 600u, USB 19200, USB 9600;
+
+
Primax: G2-200, G2-300, G2-600, G2600, G2E-300, G2E-3002, G2E-600, G2E600, G2X-300, +G600, ReadyScan 636i;
+
+
Ultima 1200 UB Plus
+
+
UMAX Astra: 1220U, 1236U, 2000U, 2100U, 2200U, 3400;
+
+
Visioneer OneTouch: 3000, 5300, 7600, 6100, 6200, 8100, 8600;
+

+ +

The +umass(4) driver +supports USB Mass Storage devices, including:

+ +

+
ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M
+
+
Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20
+
+
FujiFilm Zip USB Drive ZDR100 USB A
+
+
GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M
+
+
IBM 32MB USB Memory Key (P/N 22P5296)
+
+
IBM 256MB USB Drive (MSYSTEM DiskOnKey2)
+
+
IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)
+
+
I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)
+
+
I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)
+
+
I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI
+
+
Iomega USB Zip 100/250 drive
+
+
Iomega Zip750 USB2.0 drive
+
+
Keian USB1.1/2.0 3.5-inch HDD Case KU350A
+
+
Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0
+
+
LaCie P3 HardDrive USB 200GB
+
+
Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive
+
+
Logitec Mobile USB Memory LMC-256UD
+
+
Logitec USB1.1/2.0 HDD Unit SHD-E60U2
+
+
Logitec USB Double-Speed Floppy Drive LFD-31U2
+
+
Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)
+
+
MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M
+
+
MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm
+
+
MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2
+
+
MELCO USB2.0 MO Drive MO-CH640U2
+
+
Matshita CF-VFDU03 floppy drive
+
+
Merlin SM300 MP3/WMA Player (256Mb)
+
+
Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable
+
+
Motorola E398 Mobile Phone (TransFlash memory card)
+
+
NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U
+
+
PNY Attache Flash Drive
+
+
Panasonic ("Matshita FDD CF-VFDU03")
+
+
Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW
+
+
Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW)
+
+
Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)
+
+
Panasonic floppy drive
+
+
Qware BeatZkey! Pro
+
+
RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B
+
+
SanDisk SDDR-31 (Compact Flash)
+
+
SanDisk SDDR-75 (only Compact Flash port works)
+
+
Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick)
+
+
Sony Portable CD-R/RW Drive CRX10U (CDROM only)
+
+
TEAC Portable USB CD-ROM Unit CD-110PU/210PU
+
+
Time DPA20B MP3 Player (1Gb)
+
+
Trek Thumbdrive 8MB
+
+
VAIO floppy drive (includes Y-E Data Flashbuster-U)
+
+
Y-E Data floppy drive (720/1.44/2.88Mb)
+

+ +

Among the supported digital cameras are:

+ +

+
Asahi Optical (PENTAX) Optio 230 & 330
+

+ +

3.13 IEEE 1394 (Firewire) +Devices

+ +

The +fwohci(4) driver +provides support for PCI/CardBus FireWire interface cards. The driver supports the +following IEEE 1394 OHCI chipsets:

+ +

+
Adaptec AHA-894x/AIC-5800
+
+
Apple Pangea
+
+
Apple UniNorth
+
+
Intel 82372FB
+
+
IOGEAR GUF320
+
+
Lucent / Agere FW322/323
+
+
NEC uPD72861
+
+
NEC uPD72870
+
+
NEC uPD72871/2
+
+
NEC uPD72873
+
+
NEC uPD72874
+
+
National Semiconductor CS4210
+
+
Ricoh R5C551
+
+
Ricoh R5C552
+
+
Sony CX3022
+
+
Sony i.LINK (CXD1947)
+
+
Sony i.LINK (CXD3222)
+
+
Sun PCIO-2 (RIO 1394)
+
+
Texas Instruments PCI4410A
+
+
Texas Instruments PCI4450
+
+
Texas Instruments PCI4451
+
+
Texas Instruments TSB12LV22
+
+
Texas Instruments TSB12LV23
+
+
Texas Instruments TSB12LV26
+
+
Texas Instruments TSB43AA22
+
+
Texas Instruments TSB43AB21/A/AI/A-EP
+
+
Texas Instruments TSB43AB22/A
+
+
Texas Instruments TSB43AB23
+
+
Texas Instruments TSB82AA2
+
+
VIA Fire II (VT6306)
+

+ +

3.14 Bluetooth Devices

+ +

3.15 Cryptographic +Accelerators

+ +

3.16 Miscellaneous

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

The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.

Hardware notes for FreeBSD 6.3-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

FreeBSD/powerpc 6.3-RELEASE Installation +Instructions

+ +

The FreeBSD Project

+ +

+
+
This article gives some brief instructions on installing FreeBSD/powerpc 6.3-RELEASE, +with particular emphasis given to obtaining a FreeBSD distribution. Some notes on +troubleshooting and frequently-asked questions are also given.
+
+

+ +

1 Installing FreeBSD

+ +

This section documents the process of installing a new distribution of FreeBSD. These +instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE +distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.

+ +

If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

+ +

1.1 Getting +Started

+ +

Probably the most important pre-installation step that can be taken is that of reading +the various instruction documents provided with FreeBSD. A roadmap of documents +pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this +file; most of these documents, such as the release notes and the hardware compatibility +list, are also accessible in the Documentation menu of the installer.

+ +

Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

+ +

This collection of documents may seem daunting, but the time spent reading them will +likely be saved many times over. Being familiar with what resources are available can +also be helpful in the event of problems during installation.

+ +

The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You +should also read an updated copy of ERRATA.TXT before +installing, since this will alert you to any problems which have reported in the interim +for your particular release.

+ +

+
Important: While FreeBSD does its best to safeguard against accidental loss of +data, it's still more than possible to wipe +out your entire disk with this installation if you make a mistake. Please do +not proceed to the final FreeBSD installation menu unless you've adequately backed up any +important data first.
+

+ +

1.2 Hardware Requirements

+ +

If you are not familiar with configuring hardware for FreeBSD, you should be sure to +read the HARDWARE.TXT file; it contains important information +on what hardware is supported by FreeBSD.

+ +

1.3 Floppy Disk Image +Instructions

+ +

1.4 Installing +FreeBSD from CDROM or the Internet

+ +

1.5 Detail on various installation +types

+ +

Once you've gotten yourself to the initial installation screen somehow, you should be +able to follow the various menu prompts and go from there. If you've never used the +FreeBSD installation before, you are also encouraged to read some of the documentation in +the Documentation submenu as well as the general “Usage” instructions on the +first menu.

+ +

+
Note: If you get stuck at a screen, press the F1 key for +online documentation relevant to that specific section.
+

+ +

If you've never installed FreeBSD before, or even if you have, the +“Standard” installation mode is the most recommended since it makes sure that +you'll visit all the various important checklist items along the way. If you're much more +comfortable with the FreeBSD installation process and know exactly what you want to do, use the “Express” or +“Custom” installation options. If you're upgrading an existing system, use +the “Upgrade” option.

+ +

The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS +and UFS partitions as installation media; further tips on installing from each type of +media are listed below.

+ +

1.5.1 Installing from a Network +CDROM

+ +

If you simply wish to install from a local CDROM drive then see Section 1.4. If you don't have a CDROM drive on your +system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to +which you have network connectivity, there are also several ways of going about it:

+ +

+
If you would be able to FTP install FreeBSD directly from the CDROM drive in some +FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add +the following line to the password file (using the +vipw(8) +command):
+ +
```
+ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
```
+ +
On the machine on which you are running the install, go to the Options menu and set +Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp +sites menu.
+ +
+
+
Warning: This may allow anyone on the local network (or Internet) to make +“anonymous FTP” connections to this machine, which may not be desirable.
+
+
+
+
If you would rather use NFS to export the CDROM directly to the machine(s) you'll be +installing from, you need to first add an entry to the /etc/exports file (on the machine with the CDROM drive). The +example below allows the machine ziggy.foo.com to mount the CDROM +directly via NFS during installation:
+ +
```
+/cdrom          -ro             ziggy.foo.com
+
```
+ +
The machine with the CDROM must also be configured as an NFS server, of course, and if +you're not sure how to do that then an NFS installation is probably not the best choice +for you unless you're willing to read up on +rc.conf(5) and +configure things appropriately. Assuming that this part goes smoothly, you should be able +to enter: cdrom-host:/cdrom +as the path for an NFS installation when the target machine is installed, e.g. wiggy:/cdrom.
+

+ +

1.5.2 Installing from Floppies

+ +

If you must install from floppy disks, either due to unsupported hardware or just +because you enjoy doing things the hard way, you must first prepare some floppies for the +install.

+ +

First, make your boot floppies as described in Section +1.3.

+ +

Second, peruse Section 2 and pay special attention to the +“Distribution Format” section since it describes which files you're going to +need to put onto floppy and which you can safely skip.

+ +

Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files +in the bin (binary distribution) directory. If you're preparing +these floppies under DOS, then these floppies must be formatted using the MS-DOS FORMAT command. If you're using Windows, use the Windows File +Manager format command.

+ +

+
Important: Frequently, floppy disks come “factory preformatted”. +While convenient, many problems reported by users in the past have resulted from the use +of improperly formatted media. Re-format them yourself, just to make sure.
+

+ +

If you're creating the floppies from another FreeBSD machine, a format is still not a +bad idea though you don't need to put a DOS filesystem on each floppy. You can use the +disklabel(8) and + +newfs(8) +commands to put a UFS filesystem on a floppy, as the following sequence of commands +illustrates:

+ +

+# fdformat -f 1440 fd0
+# disklabel -w fd0 floppy3
+# newfs -i 65536 /dev/fd0
+

+ +

After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto +them. The distribution files are sized so that a floppy disk will hold a single file. +Each distribution should go into its own subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +

+
Important: The bin.inf file also needs to go on the +first floppy of the bin set since it is read by the +installation program in order to figure out how many additional pieces to look for when +fetching and concatenating the distribution. When putting distributions onto floppies, +the distname.inf file must occupy the first floppy of each distribution set.
+

+ +

Once you come to the Media screen of the install, select “Floppy” and +you'll be prompted for the rest.

+ +

1.5.4 Installing from QIC/SCSI +Tape

+ +

When installing from tape, the installation program expects the files to be simply +tar'ed onto it, so after fetching all of the files for the distributions you're +interested in, simply use +tar(1) to get +them onto the tape with a command something like this:

+ +

+# cd /where/you/have/your/dists
+# tar cvf /dev/sa0 dist1 .. dist2
+

+ +

When you go to do the installation, you should also make sure that you leave enough +room in some temporary directory (which you'll be allowed to choose) to accommodate the +full contents of the tape you've +created. Due to the non-random access nature of tapes, this method of installation +requires quite a bit of temporary storage. You should expect to require as much temporary +storage as you have stuff written on tape.

+ +

+
Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. +The installation “probe” may otherwise fail to find it.
+

+ +

Now create a boot floppy as described in Section 1.3 and +proceed with the installation.

+ +

1.5.5 Installing over a Network using FTP +or NFS

+ +

After making the boot floppies as described in the first section, you can load the +rest of the installation over a network using one of 3 types of connections: serial port, +parallel port, or Ethernet.

+ +

1.5.5.1 Serial Port

+ +

SLIP support is rather primitive, and is limited primarily to hard-wired links, such +as a serial cable running between two computers. The link must be hard-wired because the +SLIP installation doesn't currently offer a dialing capability. If you need to dial out +with a modem or otherwise dialog with the link before connecting to it, then the PPP +utility should be used instead.

+ +

If you're using PPP, make sure that you have your Internet Service Provider's IP +address and DNS information handy as you'll need to know it fairly early in the +installation process. You may also need to know your own IP address, though PPP supports +dynamic address negotiation and may be able to pick up this information directly from +your ISP if they support it.

+ +

You will also need to know how to use the various “AT commands” for +dialing out with your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator.

+ +

1.5.5.2 Parallel Port

+ +

If a hard-wired connection to another FreeBSD or Linux machine is available, you might +also consider installing over a “laplink” style parallel port cable. The data +rate over the parallel port is much higher than what is typically possible over a serial +line (up to 50k/sec), thus resulting in a quicker installation. It's not typically +necessary to use “real” IP addresses when using a point-to-point parallel +cable in this way and you can generally just use RFC 1918 style addresses for the ends of +the link (e.g. 10.0.0.1, 10.0.0.2, +etc).

+ +

+
Important: If you use a Linux machine rather than a FreeBSD machine as your +PLIP peer, you will also have to specify link0 in the TCP/IP +setup screen's “extra options for ifconfig” field in order to be compatible +with Linux's slightly different PLIP protocol.
+

+ +

1.5.5.3 Ethernet

+ +

FreeBSD supports most common Ethernet cards; a table of supported cards is provided as +part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the +Documentation menu on the boot floppy or the top level directory of the CDROM). If you +are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in +before the laptop is powered on. +FreeBSD does not, unfortunately, currently support “hot insertion” of PCMCIA +cards during installation.

+ +

You will also need to know your IP address on the network, the netmask value for your subnet and the name of your machine. Your +system administrator can tell you which values are appropriate to your particular network +setup. If you will be referring to other hosts by name rather than IP address, you'll +also need a name server and possibly the address of a gateway (if you're using PPP, it's +your provider's IP address) to use in talking to it. If you want to install by FTP via an +HTTP proxy (see below), you will also need the proxy's address.

+ +

If you do not know the answers to these questions then you should really probably talk +to your system administrator first +before trying this type of installation. Using a randomly chosen IP address or netmask on +a live network is almost guaranteed not to work, and will probably result in a lecture +from said system administrator.

+ +

Once you have a network connection of some sort working, the installation can continue +over NFS or FTP.

+ +

1.5.5.4 NFS installation tips

+ +

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution +files you want onto a server somewhere and then point the NFS media selection at it.

+ +

If this server supports only “privileged port” access (this is generally +the default for Sun and Linux workstations), you may need to set this option in the +Options menu before installation can proceed.

+ +

If you have a poor quality Ethernet card which suffers from very slow transfer rates, +you may also wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server must also support “subdir +mounts”, e.g. if your FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr +or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled by the +-alldirs option. Other NFS servers may have different +conventions. If you are getting Permission Denied messages from +the server then it's likely that you don't have this properly enabled.

+ +

1.5.5.5 FTP Installation tips

+ +

FTP installation may be done from any mirror site containing a reasonably up-to-date +version of FreeBSD. A full menu of reasonable choices for almost any location in the +world is provided in the FTP site menu during installation.

+ +

If you are installing from some other FTP site not listed in this menu, or you are +having troubles getting your name server configured properly, you can also specify your +own URL by selecting the “URL” choice in that menu. A URL can contain a +hostname or an IP address, so something like the following would work in the absence of a +name server:

+ +

+ftp://216.66.64.162/pub/FreeBSD/releases/powerpc/4.2-RELEASE
+

+ +

There are three FTP installation modes you can use:

+ +

+
FTP: This method uses the standard “Active” mode for transfers, in which +the server initiates a connection to the client. This will not work through most +firewalls but will often work best with older FTP servers that do not support passive +mode. If your connection hangs with passive mode, try this one.
+
+
FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening +connections to the client. This option is best for users to pass through firewalls that +do not allow incoming connections on random port addresses.
+
+
FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy +for all FTP operations. The proxy will translate the requests and send them to the FTP +server. This allows the user to pass through firewalls that do not allow FTP at all, but +offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP +server.
+ +
In the rare case that you have an FTP proxy that does not go through HTTP, you can +specify the URL as something like:
+ +
```
+ftp://foo.bar.com:port/pub/FreeBSD
+
```
+ +
In the URL above, port is the port number of the +proxy FTP server.
+

+ +

1.6 Question and Answer Section for +PowerPC Architecture Users

+ +

2 Distribution Format

+ +

A typical FreeBSD distribution directory looks something like this (exact details may +vary depending on version, architecture, and other factors):

+ +

+ERRATA.HTM      README.TXT      compat1x        dict            kernel
+ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
+HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
+HARDWARE.TXT    base            compat22        filename.txt    ports
+INSTALL.HTM     boot            compat3x        floppies        proflibs
+INSTALL.TXT     catpages        compat4x        games           src
+README.HTM      cdrom.inf       crypto          info            tools
+

+ +

These same files are contained in the first CDROM of a multi-disk set, but they are +laid out slightly differently on the disk. On most architectures, the installation CDROM +also contains a “live filesystem” in addition to the distribution files. The +live filesystem is useful when repairing or troubleshooting an existing FreeBSD +installation (see Section 4 for how to use this).

+ +

The floppies directory will be of particular interest to +users who are unable to boot from the CDROM media (but are able to read the CDROM by +other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for +instructions on how to do this) and use these to start an installation from CDROM, FTP, +or NFS. The rest of the data needed during the installation will be obtained +automatically based on your selections. If you've never installed FreeBSD before, you +also want to read the entirety of this document (the installation instructions) file.

+ +

If you're trying to do some other type of installation or are merely curious about how +a distribution is organized, what follows is a more thorough description of some of these +items in more detail:

+ +

+
The *.TXT and *.HTM files contain +documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should +be read before starting an installation. The *.TXT files are +plain text, while the *.HTM files are HTML files that can be +read by almost any Web browser. Some distributions may contain documentation in other +formats as well, such as PDF or PostScript.
+
+
docbook.css is a Cascading Style Sheet (CSS) file used by +some Web browsers for formatting the HTML documentation.
+
+
The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the +primary distribution components of FreeBSD itself and are split into smaller files for +easy packing onto floppies (should that be necessary).
+
+
The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories +contain distributions for compatibility with older releases and are distributed as single +gzip'd tar files - they can be installed during release time or later by running their +install.sh scripts.
+
+
The floppies/ subdirectory contains the floppy installation +images; further information on using them can be found in Section +1.3.
+
+
The packages and ports directories +contain the FreeBSD Packages and Ports Collections. Packages may be installed from the +packages directory by running the command:
+ +
```
+# sysinstall configPackages
+
```
+ +
Packages can also be installed by feeding individual filenames in packages/ to the +pkg_add(1) +command.
+ +
The Ports Collection may be installed like any other distribution and requires about +190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or +locally from /usr/share/doc/handbook if you've installed the +doc distribution.
+
+
Last of all, the tools directory contains various DOS tools +for discovering disk geometries, installing boot managers and the like. It is purely +optional and provided only for user convenience.
+

+ +

A typical distribution directory (for example, the info +distribution) looks like this internally:

+ +

+CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
+info.aa         info.ac         info.ae         info.mtree
+

+ +

The CHECKSUM.MD5 file contains MD5 signatures for each file, +should data corruption be suspected, and is purely for reference. It is not used by the +actual installation and does not need to be copied with the rest of the distribution +files. The info.a* files are split, gzip'd tar files, the +contents of which can be viewed by doing:

+ +

+# cat info.a* | tar tvzf -
+

+ +

During installation, they are automatically concatenated and extracted by the +installation procedure.

+ +

The info.inf file is also necessary since it is read by the +installation program in order to figure out how many pieces to look for when fetching and +concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

+ +

The info.mtree file is another non-essential file which is +provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be +later used with the +mtree(8) program +to verify the installation permissions and checksums against any possible modifications +to the file. When used with the base distribution, this can be +an excellent way of detecting trojan horse attacks on your system.

+ +

Finally, the install.sh file is for use by those who want to +install the distribution after installation time. To install the info distribution from +CDROM after a system was installed, for example, you'd do:

+ +

+# cd /cdrom/info
+# sh install.sh
+

+ +

3 Upgrading FreeBSD

+ +

These instructions describe a procedure for doing a binary upgrade from an older +version of FreeBSD.

+ +

+
Warning: While the FreeBSD upgrade procedure does its best to safeguard against +accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do +not accept the final confirmation request unless you have adequately backed up any +important data files.
+

+ +

+
Important: These notes assume that you are using the version of +sysinstall(8) +supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched +version of +sysinstall(8) is +almost guaranteed to cause problems and has been known to leave systems in an unusable +state. The most commonly made mistake in this regard is the use of an old copy of +sysinstall(8) +from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.
+

+ +

+
Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).
+ +
These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 6-STABLE snapshots.
+

+ +

3.1 Introduction

+ +

The upgrade procedure replaces distributions selected by the user with those +corresponding to the new FreeBSD release. It preserves standard system configuration +data, as well as user data, installed packages and other software.

+ +

Administrators contemplating an upgrade are encouraged to study this section in its +entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or +loss of data.

+ +

3.1.1 Upgrade Overview

+ +

Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.

+ +

System configuration is preserved by retaining and restoring the previous version of +the following files:

+ +

Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

+ +

The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.

+ +

During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.

+ +

3.2 Procedure

+ +

This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.

+ +

3.2.1 Backup

+ +

User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.

+ +

3.2.2 Mount Filesystems

+ +

The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” +for any filesystems, as this will cause data loss.

+ +

3.2.3 Select Distributions

+ +

When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.

+ +

3.2.4 After Installation

+ +

Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.

+ +

3.3 Upgrading from Source Code

+ +

Those interested in an upgrade method that allows more flexibility and sophistication +should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves +rebuilding all of FreeBSD from source code. It requires reliable network connectivity, +extra disk space, and time, but has advantages for networks and other more complex +installations. This is roughly the same procedure as is used for track the -STABLE or +-CURRENT development branches.

+ +

/usr/src/UPDATING contains important information on updating +a FreeBSD system from source code. It lists various issues resulting from changes in +FreeBSD that may affect an upgrade.

+ +

4 Troubleshooting

+ +

4.1 Repairing an Existing FreeBSD +Installation

+ +

FreeBSD features a “fixit” option in the top menu of the +sysinstall(8) +installation program. It provides a shell with common programs from the FreeBSD base +system; this environment is useful for repairing or troubleshooting an existing FreeBSD +installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot +floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD +distributions, the live filesystem image is typically located on the installation disk. +Note that some UNIX system administration experience is required to use the fixit +option.

+ +

Generally, there are two ways of invoking fixit mode. Users who can boot from the +FreeBSD installation CDROM, should do so and then choose the “fixit” item +from the main +sysinstall(8) +menu. Then select the “CDROM/DVD” option from the fixit menu.

+ +

Users who cannot boot from CDROM, but can boot from floppy disk, require a few more +steps. In addition to the boot.flp and kernX.flp disks required for +installation, create the fixit.flp floppy disk, in the same way +as the other floppy disks. Follow the instructions for booting the installation program +from floppy disk until reaching the main +sysinstall(8) +menu. At that point, choose the “fixit” item from the main +sysinstall(8) +menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

+ +

The CDROM and floppy fixit environments are similar, but not identical. Both offer a +shell with a variety of commands available for checking, repairing and examining +filesystems and their contents. The CDROM version of fixit provides all of the commands +and programs available in the FreeBSD base system, through the live filesystem. By +contrast, the floppy fixit environment can only offer a subset of commands due to space +constraints.

+ +

In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM +version of fixit, these same programs can be found in /stand or +/mnt2/rescue (as well as the rest of the programs from the live +filesystem, which can be found under /mnt).

+ +

4.2 Common Installation Problems for +PowerPC Architecture Users

All users of FreeBSD 6-STABLE should subscribe to the <stable@FreeBSD.org> mailing list.

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 6.3-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

FreeBSD/powerpc 6.3-RELEASE Release +Notes

+ +

The FreeBSD Project

+ +

$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v +1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
+

+ +

FreeBSD is a registered trademark of the FreeBSD Foundation.

+ +

IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks +of International Business Machines Corporation in the United States, other countries, or +both.

+ +

IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and +Electronics Engineers, Inc. in the United States.

+ +

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

+ +

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

+ +

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

+ +

The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the +FreeBSD base system on the 6.3-STABLE development line. This document lists applicable +security advisories that were issued since the last release, as well as significant +changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also +presented.

+ +

Table of Contents

1 Introduction

2 What's New

2.1 Security Advisories

2.2 Kernel Changes

2.2.1 Boot Loader Changes
2.2.2 Hardware Support
2.2.3 Network Protocols
2.2.4 Disks and Storage
2.2.5 File Systems

2.3 Userland Changes

2.3.1 /etc/rc.d Scripts

2.4 Contributed Software

2.5 Ports/Packages Collection Infrastructure

2.6 Release Engineering and Integration

2.7 Documentation

3 Upgrading from previous releases of FreeBSD

+ +

1 Introduction

+ +

This document contains the release notes for FreeBSD 6.3-RELEASE on the PowerPC +hardware platform. It describes recently added, changed, or deleted features of FreeBSD. +It also provides some notes on upgrading from previous versions of FreeBSD.

+ +

This distribution of FreeBSD 6.3-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the “Obtaining FreeBSD” appendix to the FreeBSD +Handbook.

+ +

All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with “late-breaking” information discovered late +in the release cycle or after the release. Typically, it contains information on known +bugs, security advisories, and corrections to documentation. An up-to-date copy of the +errata for FreeBSD 6.3-RELEASE can be found on the FreeBSD Web site.

+ +

2 What's New

+ +

This section describes the most user-visible new or changed features in FreeBSD since +6.2-RELEASE.

+ +

Typical release note items document recent security advisories issued after +6.2-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.

+ +

2.1 Security Advisories

+ +

Two remote denials of service in BIND (one involving DNSSEC and one involving +recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

+ +

Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to +0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

+ +

Problems with +libarchive(3) +and +tar(1) handling +corrupted +tar(5) archive +files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

+ +

A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has +been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

+ +

An flaw that could lead to the disclosure of previously-generated +random(4) data +has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

+ +

Information disclosure issues found in +openpty(3) and + +ptsname(3) have +been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

+ +

A programming error in +inet_network(3) +Internet address manipulation function that could lead to overwriting a region of memory +with user defined data has been corrected. Information regarding this issue can be found +in security advisory FreeBSD-SA-08:02.libc.

+ +

2.2 Kernel Changes

+ +

+acpi(4) now has +support for the HPET time counter.

+ +

Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts +(MSI-X) has been added to the kernel's PCI support code.

+ +

2.2.1 Boot Loader Changes

+ +

2.2.2 Hardware Support

+ +

An +acpi_dock(4) +driver has been added to provide support for controlling laptop docking station functions +via ACPI.

+ +

2.2.2.1 Multimedia Support

+ +

The +snd_envy24(4) +driver has been added to support the Envy24 series of audio chips.

+ +

The +snd_envy24ht(4) +driver has been added to support the VIA Envy24HT series of audio chips.

+ +

The +snd_hda(4) +driver has been added. It supports devices that conform to revision 1.0 of the Intel High +Definition Audio specification.

+ +

The +snd_spicds(4) +driver has been added to support I2S SPI audio codec chips.

+ +

2.2.2.2 Network Interface Support

+ +

The +ath(4) driver +has been updated to HAL version 0.9.20.3.

+ +

The +axe(4) driver +now supports +altq(4).

+ +

The +cxgb(4) driver +has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio +T3 and T3B chipsets.

+ +

The +edsc(4) driver, +which provides Ethernet discard network interfaces, has been added.

+ +

The em(4) driver has been +updated to version 6.7.2 from Intel.

+ +

The +msk(4) driver +has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II +Gigabit Ethernet controller.

+ +

The +vge(4) driver +now supports +altq(4).

+ +

The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and +half-channel support for 802.11a.

+ +

2.2.3 Network Protocols

+ +

The +if_bridge(4) +driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

+ +

The +lagg(4) driver, +ported from OpenBSD and NetBSD, has been added to support a variety of protocols and +algorithms for link aggregation, failover, and fault tolerance.

+ +

A new +ng_deflate(4) +NetGraph node type has been added. It implements Deflate PPP compression.

+ +

The +ng_ppp(4) +Netgraph node is now MPSAFE.

+ +

A new +ng_pred1(4) +NetGraph node type has been added to implement Predictor-1 PPP compression.

+ +

A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over +gif(4) tunnels +has been fixed.

+ +

The net.link.tap.up_on_open sysctl variable has been +added to the +tap(4) driver. +If enabled, new tap devices will marked up upon creation.

+ +

2.2.4 Disks and Storage

+ +

The +mpt(4) driver +has been updated to support various new features such as RAID volume and RAID member +state/settings reporting, periodic volume re-synchronization status reporting, and sysctl +variables for volume re-synchronization rate, volume member write cache status, and +volume transaction queue depth.

+ +

The +mpt(4) driver +now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

+ +

The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG +passthrough device API, has been added. It is intended to allow programs running under +Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by +Linux.

+ +

The +twa(4) driver +has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's +3ware 9650 series of SATA controllers.

+ +

2.2.5 File Systems

+ +

The unionfs file system has been re-implemented. This version solves many crashing and +locking issues compared to the previous implementation. It also adds new +“transparent” and “masquerade” modes for automatically creating +files in the upper file system layer of unions. More information can be found in the +mount_unionfs(8) +manual page.

+ +

2.3 Userland Changes

+ +

The +camcontrol(8) +utility now supports a readcap command to display the size of +devices.

+ +

A bug in +freebsd-update(8), which caused it not to update +SMP kernels correctly, has been fixed.

+ +

The +fdisk(8) program +now supports a -p flag to print the slice table in fdisk +configuration format.

+ +

The +freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different +versions of FreeBSD.

+ +

The +ftpd(8) utility +now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The +RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the +ftpd(8) manual +page.

+ +

The +ipfwpcap(8) +utility has been added; it captures packets on a +divert(4) socket +and writes them as +pcap(3) (also +known as +tcpdump(1)) +format data to a file or pipe.

+ +

The +rpc.lockd(8) and + +rpc.statd(8) +programs now accept -p options to indicate which port they +should bind to.

+ +

The pw(8) program now +supports a -M option to set the permissions of a user's newly +created home directory.

+ +

The +top(1) program +now supports a -j flag to display the +jail(8) ID for +each process.

+ +

The +touch(1) utility +now supports a -A flag that allows the access and +modification times of a file be adjusted by a specified value.

+ +

The +wpa_passphrase(8) utility has been added. It +generates a 256-bit pre-shared WPA key from an ASCII passphrase.

+ +

2.3.1 `/etc/rc.d` Scripts

+ +

The sendmail script can be instructed not to rebuild the +aliases database if it is missing or older than the aliases file. If desired, set the new +rc.conf option sendmail_rebuild_aliases to "NO" to turn off +that functionality.

+ +

The /etc/rc.d/nfslocking script has been deprecated and will +be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd +scripts.

+ +

2.4 Contributed Software

+ +

awk has been updated from the 24 April 2005 release to the +1 May 2007 release.

+ +

BIND has been updated from 9.3.3 to 9.3.4-p1.

+ +

BZIP2 has been updated from 1.0.3 to 1.0.4.

+ +

GNU Diffutils has been updated from 2.7 to 2.8.7.

+ +

The GNU version of gzip has been replaced with a modified +version of gzip ported from NetBSD.

+ +

IPFilter has been updated from 4.1.13 to 4.1.28.

+ +

less has been updated from v381 to v416.

+ +

ncurses has been updated from 5.2-20020615 to 5.6-20061217. +ncurses now also has wide character support.

+ +

netcat has been updated from the version in a 4 February +2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

+ +

GNU Readline library has been updated from 5.0 to 5.2 patch +2.

+ +

sendmail has been updated from 8.13.8 to 8.14.2.

+ +

The timezone database has been updated from the tzdata2006g +release to the tzdata2007k release.

+ +

TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to +1.0.

+ +

2.5 Ports/Packages Collection +Infrastructure

+ +

2.6 Release Engineering and +Integration

+ +

The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

+ +

The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

+ +

The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

+ +

The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default +value of LOCALBASE.

+ +

2.7 Documentation

+ +

3 Upgrading from previous releases of +FreeBSD

+ +

Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or +later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to +FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

+ +

+
Important: Upgrading FreeBSD should, of course, only be attempted after backing +up all data and configuration +files.
+

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

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 6.3-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.