diff --git a/release/sysinstall/help/hardware.hlp b/release/sysinstall/help/hardware.hlp index 91ca5d2fcee7..cde6c4d9cba8 100644 --- a/release/sysinstall/help/hardware.hlp +++ b/release/sysinstall/help/hardware.hlp @@ -1,447 +1,447 @@ ardware Documentation Guide: $FreeBSD$ Contents last changed: Jan 14th, 1997 Table of Contents ----------------- 0. Document Conventions 1. Default Configuration (GENERIC kernel) 2. Using UserConfig to change FreeBSD kernel settings 3. LINT - other possible configurations. 4. Known Hardware Problems. ========================================================================= 0. Document Conventions -- -------------------- We have `underlined' text which represents user input with `-' symbols throughout this document to differentiate it from the machine output. 1. Default (GENERIC) Configuration -- ------------------------------- The following table contains a list of all of the devices that are present in the GENERIC kernel, that being the kernel (the operating system) that was placed in your root partition during the FreeBSD installation process. A compressed version of the GENERIC kernel is also used on the installation floppy diskette and DOS boot image. The table describes the various parameters used by the driver to communicate with the hardware in your system. There are four parameters in the table, though not all are used by each and every device. Detail: Port The starting I/O port used by the device, shown in hexadecimal. IOMem The lowest (or starting) memory address used by the device, also shown in hexadecimal. IRQ The interrupt the device uses to alert the driver to an event, given in decimal. DRQ The DMA (direct memory access) channel the device uses to move data to and from main memory, also given in decimal. If an entry in the table has `n/a' for a value then it means that the parameter in question does not apply to that device. A value of `dyn' means that the correct value should be determined automatically by the kernel when the system boots. FreeBSD GENERIC kernel: Port IRQ DRQ IOMem Description ---- --- --- ----- --------------------------------- fdc0 3f0 6 2 n/a Floppy disk controller wdc0 1f0 14 n/a n/a IDE/MFM/RLL disk controller wdc1 170 15 n/a n/a IDE/MFM/RLL disk controller ncr0 n/a n/a n/a n/a NCR PCI SCSI controller bt0 330 dyn dyn dyn Buslogic SCSI controller uha0 330 dyn 6 dyn Ultrastore 14f -aha0 330 dyn 5 dyn Adaptec 154x SCSI controller +aha0 330 dyn 5 dyn Adaptec 154x/1535 SCSI controller ahb0 dyn dyn dyn dyn Adaptec 174x SCSI controller ahc0 dyn dyn dyn dyn Adaptec 274x/284x/294x SCSI controller aic0 340 11 dyn dyn Adaptec 152x/AIC-6360 SCSI controller amd0 n/a n/a n/a n/a Tekram DC-390(T) / AMD 53c974 PCI SCSI nca0 1f88 10 dyn dyn ProAudioSpectrum cards sea0 dyn 5 dyn c8000 Seagate ST01/02 8 bit controller wt0 300 5 1 dyn Wangtek and Archive QIC-02/QIC-36 mse0 23c 5 n/a n/a Microsoft Bus Mouse psm0 60 12 n/a n/a PS/2 Mouse (disabled by default) mcd0 300 10 n/a n/a Mitsumi CD-ROM matcd0 230 n/a n/a n/a Matsushita/Panasonic CD-ROM scd0 230 n/a n/a n/a Sony CD-ROM sio0 3f8 4 n/a n/a Serial Port 0 (COM1) sio1 2f8 3 n/a n/a Serial Port 1 (COM2) lpt0 dyn 7 n/a n/a Printer Port 0 lpt1 dyn dyn n/a n/a Printer Port 1 de0 n/a n/a n/a n/a DEC DC21x40 PCI based cards (including 21140 100bT cards) ed0 280 5 dyn d8000 WD & SMC 80xx; Novell NE1000 & NE2000; 3Com 3C503; HP PC Lan+ ed1 300 5 dyn d8000 Same as ed0 eg0 310 5 dyn dyn 3Com 3C505 ep0 300 10 dyn dyn 3Com 3C509 fe0 300 dyn n/a n/a Allied-Telesis AT1700, RE2000 and Fujitsu FMV-180 series cards. fxp0 dyn dyn n/a dyn Intel EtherExpress Pro/100B ie0 360 7 dyn d0000 AT&T StarLAN 10 and EN100; 3Com 3C507; NI5210 ix0 300 10 dyn d0000 Intel EtherExpress cards ex0 dyn dyn dyn dyn Intel EtherExpress Pro/10 cards le0 300 5 dyn d0000 Digital Equipment EtherWorks 2 and EtherWorks 3 lnc0 280 10 n/a dyn Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL) vx0 dyn dyn n/a dyn 3Com 3c59x / 3c9xx ze0 300 5 dyn d8000 IBM/National Semiconductor PCMCIA Ethernet Controller zp0 300 10 dyn d8000 3Com PCMCIA Etherlink III Ethernet Controller --- End of table --- If the hardware in your computer is not set to the same settings as those shown in the table and the item in conflict is not marked 'dyn', you will have to either reconfigure your hardware or use UserConfig to reconfigure the kernel to match the way your hardware is currently set (see the next section). If the settings do not match, the kernel may be unable to locate or reliably access the devices in your system. 2. Using UserConfig to change FreeBSD kernel settings -- -------------------------------------------------- The FreeBSD kernel on the install floppy contains drivers for every piece of hardware that could conceivably be used to install the rest of the system with. Unfortunately, PC hardware being what it is, some of these devices can be difficult to detect accurately, and for some, the process of detecting another can cause irreversible confusion. To make this process easier, FreeBSD provides UserConfig. With this UserConfig, the user can configure and disable device drivers before the kernel is loaded, avoiding potential conflicts, and eliminating the need to reconfigure hardware to suit the default driver settings. Once FreeBSD is installed, it will remember the changes made using UserConfig, so that they only need be made once. It is important to disable drivers that are not relevant to a system in order to minimize the possibility of interference, which can cause problems that are difficult to track down. UserConfig features a command line interface for users with serial consoles or a need to type commands, and a full screen 'visual' interface, which provides point-and-shoot configuration functionality. Here is a sample UserConfig screen shot in 'visual' mode: ---Active Drivers---------------------------10 Conflicts------Dev---IRQ--Port-- Storage : (Collapsed) Network : NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed0 5 0x280 NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed1 5 0x300 Communications : (Collapsed) Input : (Collapsed) Multimedia : ---Inactive Drivers-------------------------------------------Dev-------------- Storage : Network : (Collapsed) Communications : Input : Multimedia : PCI : ---Parameters-for-device-ed0--------------------------------------------------- Port address : 0x280 Memory address : 0xd8000 IRQ number : 5 Memory size : 0x2000 Flags : 0x0000 ------------------------------------------------------------------------------- IO Port address (Hexadecimal, 0x1-0x2000) [TAB] Change fields [Q] Save device parameters The screen is divided into four sections : - Active Drivers. Listed here are the device drivers that are currently enabled, and their basic parameters. - Inactive Drivers. These drivers are present, but are disabled. - Parameter edit field. This area is used for editing driver parameters. - Help area. Keystroke help is displayed here. One of the Active and Inactive lists is always in use, and the current entry in the list will be shown with a highlight bar. If there are more entries in a list than can be shown, it will scroll. The bar can be moved up and down using the cursor keys, and moved between lists with the TAB key. Drivers in the Active list may be marked "CONF". This indicates that one or more of their parameters conflicts with another device, and indicates a potential for problems. The total number of conflicts is displayed at the top of the screen. As a general rule, conflicts should be avoided, either by disabling conflicting devices that are not present in the system, or by altering their configuration so that they match the installed hardware. In the list areas, drivers are grouped by their basic function. Groups can be 'Collapsed' to simplify the display (this is the default state for all groups). If a group is collapsed, it will be shown with '(Collapsed)' in the list, as above. To Expand a Collapsed group, position the highlight bar over the group heading and press Enter. To Collapse it again, repeat the process. When a device driver in the Active list is highlighted, its full parameters are displayed in the Parameter edit area. Note that not all drivers use all possible parameters, and some hardware supported by drivers may not use all the parameters the driver supports. To disable a driver, go to the Active list, Expand the group it is in, highlight the driver and press Del. The driver will move to its group in the Inactive list. (If the group is collapsed or off the screen, you may not see the driver in its new location.) To enable a driver, go to the Inactive list, Expand the group it is in, highlight the driver and press Enter. The highlight will move to the Active list, and the driver you have just enabled will be highlighted, ready to be configured. To configure a driver, go to the Active list, Expand the group it is in, highlight the driver and press Enter. The cursor will move to the Parameter edit area, and the device's parameters may be edited. While editing parameters, the TAB and cursor keys can be used to move between fields. Most numeric values (except IRQ) are entered in hexadecimal, as indicated by the '0x' at the beginning of the field. The allowable values for a given field are show in the Key Help area when the field is active. To finish configuring a driver, press 'Q'. Note that PCI and EISA devices can be probed reliably, therefore are not shown in the table above, nor can be changed using UserConfig. 3. LINT - other possible configurations -- ------------------------------------ The following drivers are not in the GENERIC kernel but remain available to those who do not mind compiling a custom kernel (see section 6 of FreeBSD.FAQ). The LINT configuration file (/sys/i386/conf/LINT) also contains prototype entries for just about every device supported by FreeBSD and is a good general reference. The device names and a short description of each are listed below. The port numbers, etc, are not meaningful here since you will need to compile a custom kernel to gain access to these devices anyway and can thus adjust the addresses to match the hardware in your computer in the process. The LINT file contains prototype entries for all of the below which you can easily cut-and-paste into your own file (or simply copy LINT and edit it to taste): ctx: Cortex-I frame grabber cx: Cronyx/Sigma multiport sync/async cy: Cyclades high-speed serial driver el: 3Com 3C501 fea: DEV DEFEA EISA FDDI adater fpa: DEC DEFPA PCI FDDI adapter gp: National Instruments AT-GPIB and AT-GPIB/TNT board gsc: Genius GS-4500 hand scanner gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX gusxvi: Gravis Ultrasound 16-bit PCM joy: Joystick labpc: National Instrument's Lab-PC and Lab-PC+ meteor: Matrox Meteor frame-grabber card mpu: Roland MPU-401 stand-alone card mse: Logitech & ATI InPort bus mouse ports mss: Microsoft Sound System opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum pas: ProAudioSpectrum PCM and MIDI pca: PCM audio ("/dev/audio") through your PC speaker psm: PS/2 mouse port rc: RISCom/8 multiport card sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum sbmidi: SoundBlaster 16 MIDI interface sbxvi: SoundBlaster 16 spigot: Creative Labs Video Spigot video-acquisition board uart: Stand-alone 6850 UART for MIDI wds: Western Digital WD7000 IDE --- end of list --- 4. Known Hardware Problems, Q & A: -- ------------------------------- Q: mcd0 keeps thinking that it has found a device and this stops my Intel EtherExpress card from working. A: Use the UserConfig utility (see section 1.0) and disable the probing of the mcd0 and mcd1 devices. Generally speaking, you should only leave the devices that you will be using enabled in your kernel. Q: The system finds my ed network card, but I keep getting device timeout errors. A: Your card is probably on a different IRQ from what is specified in the kernel configuration. The ed driver does not use the `soft' configuration by default (values entered using EZSETUP in DOS), but it will use the software configuration if you specify `?' in the IRQ field of your kernel config file. Either move the jumper on the card to a hard configuration setting (altering the kernel settings if necessary), or specify the IRQ as `-1' in UserConfig or `?' in your kernel config file. This will tell the kernel to use the soft configuration. Another possibility is that your card is at IRQ 9, which is shared by IRQ 2 and frequently a cause of problems (especially when you have a VGA card using IRQ 2! :). You should not use IRQ 2 or 9 if at all possible. Q: I go to boot from the hard disk for the first time after installing FreeBSD, but the Boot Manager prompt just prints `F?' at the boot menu each time but the boot won't go any further. A: The hard disk geometry was set incorrectly in the Partition editor when you installed FreeBSD. Go back into the partition editor and specify the actual geometry of your hard disk. You must reinstall FreeBSD again from the beginning with the correct geometry. If you are failing entirely in figuring out the correct geometry for your machine, here's a tip: Install a small DOS partition at the beginning of the disk and install FreeBSD after that. The install program will see the DOS partition and try to infer the correct geometry from it, which usually works. If you are setting up a truly dedicated FreeBSD server or work- station where you don't care for (future) compatibility with DOS, Linux or another operating system, you've also got the option to use the entire disk (`A' in the partition editor), selecting the non-standard option where FreeBSD occupies the entire disk from the very first to the very last sector. This will leave all geometry considerations aside, but is somewhat limiting unless you're never going to run anything other than FreeBSD on a disk. Q: I have a Matsushita/Panasonic drive but it isn't recognized by the system. A: Make certain that the I/O port that the matcd driver is set to is correct for the host interface card you have. (Some SoundBlaster DOS drivers report a hardware I/O port address for the CD-ROM interface that is 0x10 lower than it really is.) If you are unable to determine the settings for the card by examining the board or documentation, you can use UserConfig to change the 'port' address (I/O port) to -1 and start the system. This setting causes the driver to look at a number of I/O ports that various manufacturers use for their Matsushita/Panasonic/Creative CD-ROM interfaces. Once the driver locates the address, you should run UserConfig again and specify the correct address. Leaving the 'port' parameter set to -1 increases the amount of time that it takes the system to boot, and this could interfere with other devices. The double-speed Matsushita CR-562 and CR-563 are the only drives that are supported. Q: I booted the install floppy on my IBM ThinkPad (tm) laptop, and the keyboard is all messed up. A: Older IBM laptops use a non-standard keyboard controller, so you must tell the console driver (sc0) to go into a special mode which works on the ThinkPads. Change the sc0 'Flags' to 0x10 in UserConfig and it should work fine. (Look in the Input Menu for 'Syscons Console Driver'.) Q: I have a Matsushita/Panasonic CR-522, a Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is not recognized even when the correct I/O port is set. A: These CD-ROM drives are currently not supported by FreeBSD. The command sets for these drives are not compatible with the double-speed CR-562 and CR-563 drives. The single-speed CR-522 and CR-523 drives can be identified by their use of a CD-caddy. Q: I'm trying to install from a tape drive but all I get is something like: st0(aha0:1:0) NOT READY csi 40,0,0,0 on the screen. Help! A: There's a limitation in the current sysinstall that the tape MUST be in the drive while sysinstall is started or it won't be detected. Try again with the tape in the drive the whole time. Q: I've installed FreeBSD onto my system, but it hangs when booting from the hard drive with the message: ``Changing root to /dev/sd0a''. A: This problem may occur in a system with a 3com 3c509 Ethernet adaptor. The ep0 device driver appears to be sensitive to probes for other devices that also use address 0x300. Boot your FreeBSD system by power cycling the machine (turn off and on). At the ``Boot:'' prompt specify the ``-c''. This will invoke UserConfig (see Section 1. above). Use the ``disable'' command to disable the device probes for all devices at address 0x300 except the ep0 driver. On exit, your machine should successfully boot FreeBSD. Q: My system hangs during boot, right after the "fd0: [my floppy drive]" line. A: This is not actually a hang, simply a very LONG "wdc0" probe that often takes a long time to complete on certain systems (where there usually _isn't_ a WD controller). Be patient, your system will boot! To eliminate the problem, boot with the -c flag and eliminate the wdc0 device, or compile a custom kernel. Q: My system can not find my Intel EtherExpress 16 card. A: You must set your Intel EtherExpress 16 card to be memory mapped at address 0xD0000, and set the amount of mapped memory to 32K using the Intel supplied softset.exe program. Q: When installing on an EISA HP Netserver, my on-board AIC-7xxx SCSI controller isn't detected. A: This is a known problem, and will hopefully be fixed in the future. In order to get your system installed at all, boot with the -c option into UserConfig, but _don't_ use the pretty visual mode but the plain old CLI mode. Type eisa 12 quit there at the prompt. (Instead of `quit', you might also type `visual', and continue the rest of the configuration session in visual mode.) Don't forget to install the kernel source code distribution, you will need to install a custom kernel on those systems. Refer to the FAQ topic 3.16 for an explanation of the problem, and for how to continue. Remember that you can find the FAQ on your local system in /usr/share/doc/FAQ, provided you have installed the `doc' distribution. [ Please add more hardware tips to this Q&A section! ] diff --git a/release/sysinstall/help/relnotes.hlp b/release/sysinstall/help/relnotes.hlp index fcee0465d425..4d6f2c5e64a2 100644 --- a/release/sysinstall/help/relnotes.hlp +++ b/release/sysinstall/help/relnotes.hlp @@ -1,549 +1,550 @@ RELEASE NOTES FreeBSD Release 3.0-SNAPSHOT This is a SNAPSHOT release of FreeBSD 3.0-CURRENT and is aimed primarily at release testers. Some parts of the documentation may not be updated yet and should be reported if and when seen. Naturally, any installation failures or crashes should also be reported ASAP by sending mail to bugs@freebsd.org or using the send-pr command (those preferring a WEB based interface can also see http://www.freebsd.org/send-pr.html). For information about the layout of the 3.0-SNAPSHOT release directory, see ABOUT.TXT. For general information about FreeBSD, see README.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. 0. What's new since 2.2.X-RELEASE ------------------------------------ The ATAPI CD-ROM support is now reported to work for quite an impressive number of drives. In other words, all the drives that basically adhere to the ATAPI standard are likely to work. There are many new drivers available in the kernel, too many to keep them in mind. Tekram supplied a driver for their DC390 and DC390T controllers. These controllers are based on the AMD 53c974, and the driver is also able to handle other SCSI controllers based on that chip. Of course, with Tekram being generous enough to support the FreeBSD project with their driver, we'd like to encourage you to buy their product. The `ed' and `lnc' drivers now support auto-configuration for the respective PCI ethernet cards, including many NE2000 clones and the AMD PCnet chips. The SDL RISCom N2 support is new, as well as the PCI version of the Cyclades driver. The Intel Etherexpress Pro/10 card is now supported. Support for APM BIOSes is now in a much better shape. The manual section 9 has been started, describing `official' kernel programming interfaces. We are still seeking volunteers to document interfaces here! 2. Technical overview --------------------- FreeBSD is a freely available, full source 4.4 BSD Lite based release for Intel i386/i486/Pentium (or compatible) based PC's. It is based primarily on software from U.C. Berkeley's CSRG group, with some enhancements from NetBSD, 386BSD, and the Free Software Foundation. Since our release of FreeBSD 2.0 over 2 years ago, the performance, feature set and stability of FreeBSD has improved dramatically. The largest change is a revamped VM system with a merged VM/file buffer cache that not only increases performance but reduces FreeBSD's memory footprint, making a 5MB configuration a more acceptable minimum. Other enhancements include full NIS client and server support, transaction TCP support, dial-on-demand PPP, an improved SCSI subsystem, early ISDN support, support for FDDI and Fast Ethernet (100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and narrow) and 3940 SCSI adaptors along with many hundreds of bug fixes. We've taken the comments and suggestions of many of our users to heart and have attempted to provide what we hope is a more sane and easily understood installation process. Your feedback on this (constantly evolving) process is especially welcome! In addition to the base distributions, FreeBSD offers a ported software collection with over 700 commonly sought-after programs. The list of ports ranges from http (WWW) servers, to games, languages, editors and almost everything in between. The entire ports collection requires only 6MB of storage, all ports being expressed as "deltas" to their original sources. This makes it much easier for us to update ports and greatly reduces the disk space demands made by the ports collection. To compile a port, you simply change to the directory of the program you wish to install, type make and let the system do the rest. The full original distribution for each port you build is retrieved dynamically off of CDROM or a local ftp site, so you need only enough disk space to build the ports you want. (Almost) every port is also provided as a pre-compiled "package" which can be installed with a simple command (pkg_add). See also the new Packages option in the Configuration menu for an especially convenient interface to the package collection. A number of additional documents which you may find helpful in the process of installing and using FreeBSD may now also be found in the /usr/share/doc directory. You may view the manuals with any HTML capable browser by saying: To read the handbook: file:/usr/share/doc/handbook/handbook.html To read the FAQ: file:/usr/share/doc/FAQ/FAQ.html You can also visit the master (and most frequently updated) copies at http://www.freebsd.org. The core of FreeBSD does not contain DES code which would inhibit its being exported outside the United States. There is an add-on package to the core distribution, for use only in the United States, that contains the programs that normally use DES. The auxiliary packages provided separately can be used by anyone. A freely (from outside the U.S.) exportable distribution of DES for our non-U.S. users also exists at ftp://ftp.internat.freebsd.org/pub/FreeBSD. If password security for FreeBSD is all you need and you have no requirement for copying encrypted passwords from different hosts (Suns, DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5 based security may be all you require! We feel that our default security model is more than a match for DES, and without any messy export issues to deal with. If you're outside (or even inside) the U.S., give it a try! This snapshot also includes support for mixed password files - either DES or MD5 passwords will be accepted, making it easier to transition from one scheme to the other. 3. Supported Configurations --------------------------- FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus based PC's, ranging from 386sx to Pentium class machines (though the 386sx is not recommended). Support for generic IDE or ESDI drive configurations, various SCSI controller, network and serial cards is also provided. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 3.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers +Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers. Adaptec AIC7850 on-board SCSI controllers. Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. ** Note: You cannot boot from the SoundBlaster cards as they have no on-board BIOS, such being necessary for mapping the boot device into the system BIOS I/O vectors. They're perfectly usable for external tapes, CDROMs, etc, however. The same goes for any other AIC-6x60 based card without a boot ROM. Some systems DO have a boot ROM, which is generally indicated by some sort of message when the system is first powered up or reset, and in such cases you *will* also be able to boot from them. Check your system/board documentation for more details. Buslogic 545S & 545c Buslogic 445S/445c VLB SCSI controller Buslogic 742A, 747S, 747c EISA SCSI controller. Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including Disks, tape drives (including DAT and 8mm Exabyte) and CD ROM drives. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (mcd) Mitsumi proprietary interface (all models) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface (experimental and should be considered ALPHA quality!). 3.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra is also supported. DEC EtherWORKS III NICs (DE203, DE204, and DE205) DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/100B PCI Fast Ethernet Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 ethernet interface. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL Toshiba ethernet cards PCMCIA ethernet cards from IBM and National Semiconductor are also supported. Note that NO token ring cards are supported at this time as we're still waiting for someone to donate a driver for one of them. Any takers? 3.3. Misc --------- AST 4 port serial card using shared IRQ. ARNET 8 port serial card using shared IRQ. ARNET (now Digiboard) Sync 570/i high-speed serial. Boca BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 4. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 4.1. FTP/Mail You can ftp FreeBSD and any or all of its optional packages from `ftp.freebsd.org' - the official FreeBSD release site. For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! Contact admin@freebsd.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@decwrl.dec.com' - putting the keyword "help" in your message to get more information on how to fetch files using this mechanism. Please do note, however, that this will end up sending many *tens of megabytes* through the mail and should only be employed as an absolute LAST resort! 4.2. CDROM FreeBSD 2.1.6-RELEASE and 2.2-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite D Concord CA 94520 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). With a subscription, you will automatically receive updates as they are released. Your credit card will be billed when each disk is shipped and you may cancel your subscription at any time without further obligation. Shipping (per order not per disc) is $5 in the US, Canada or Mexico and $9.00 overseas. They accept Visa, Mastercard, Discover, American Express or checks in U.S. Dollars and ship COD within the United States. California residents please add 8.25% sales tax. Should you be dissatisfied for any reason, the CD comes with an unconditional return policy. Reporting problems, making suggestions, submitting code ------------------------------------------------------- Your suggestions, bug reports and contributions of code are always valued - please do not hesitate to report any problems you may find (preferably with a fix attached, if you can!). The preferred method to submit bug reports from a machine with Internet mail connectivity is to use the send-pr command or use the CGI script at http://www.freebsd.org/send-pr.html. Bug reports will be dutifully filed by our faithful bugfiler program and you can be sure that we'll do our best to respond to all reported bugs as soon as possible. Bugs filed in this way are also visible on our WEB site in the support section and are therefore valuable both as bug reports and as "signposts" for other users concerning potential problems to watch out for. If, for some reason, you are unable to use the send-pr command to submit a bug report, you can try to send it to: bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or suggestions, please send mail to: questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: announce@FreeBSD.org All but the freebsd-bugs groups can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This will give you more information on joining the various lists, accessing archives, etc. There are a number of mailing lists targeted at special interest groups not mentioned here, so send mail to majordomo and ask about them! 6. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. It would be very difficult, if not impossible, to enumerate everyone who's contributed to FreeBSD, but nonetheless we shall try (in alphabetical order, of course). If you've contributed something substantive to us and your name is not mentioned here, please be assured that its omission is entirely accidental. Please contact hackers@FreeBSD.org for any desired updates to the lists that follow: The Computer Systems Research Group (CSRG), U.C. Berkeley. Bill Jolitz, for his initial work with 386BSD. The FreeBSD Core Team (in alphabetical order by last name): Satoshi Asami Andrey A. Chernov John Dyson Bruce Evans Justin Gibbs David Greenman Jordan K. Hubbard Poul-Henning Kamp Rich Murphey Gary Palmer Søren Schmidt Peter Wemm Garrett A. Wollman Jörg Wunsch The FreeBSD Development Team, excluding core team members (in alphabetical order by last name): Torsten Blum Gary Clark II Adam David Peter Dufault Frank Durda IV Julian Elischer Sean Eric Fagan Stefan Esser Bill Fenner John Fieber Lars Fredriksen Thomas Gellekum Thomas Graichen Rod Grimes James FitzGibbon John Hay Jeffrey Hsu Ugen J.S. Antsilevich Gary Jennejohn Andreas Klemm Warner Losh L Jonas Olsson Eric L. Hernes Scott Mace Atsushi Murai Mark Murray Alex Nash Masafumi NAKANE David E. O'Brien Andras Olah Steve Passe Sujal Patel Bill Paul Joshua Peck Macdonald John Polstra Steve Price Mike Pritchard Doug Rabson James Raynard Geoff Rehmet Martin Renters Paul Richards Ollivier Robert Chuck Robey Dima Ruban Wolfram Schneider Andreas Schulz Karl Strickland Michael Smith Paul Traina Guido van Rooij Steven Wallace Nate Williams Jean-Marc Zucconi Additional FreeBSD helpers and beta testers: Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis Special mention to: Walnut Creek CDROM, without whose help (and continuing support) this release would never have been possible. Dermot McDonnell for his donation of a Toshiba XM3401B CDROM drive. Chuck Robey for his donation of a floppy tape streamer for testing. Larry Altneu and Wilko Bulte for providing us with Wangtek and Archive QIC-02 tape drives for testing and driver hacking. CalWeb Internet Services for the loan of a P6/200 machine for speedy package building. Everyone at Montana State University for their initial support. And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Core Team $FreeBSD$