Copyright (C) 2000-2012 |
Whole document tree 13. Individual ModulesIn this chapter, I document individual LKMs. Where possible, I do this by reference to more authoritative documentation for the particular LKM (probably maintained by the same person who maintains the LKM code). 13.1. Executable InterpretersYou must have at least one executable interpreter bound into the base kernel, because in order to load an executable interpreter LKM, you have to run an executable and something has to interpret that executable. That one bound-in executable interpreter is almost certainly the ELF interpreter, since virtually all executables in a Linux system are ELF. Historical note: Before ELF existed on Linux (c. 1995), the normal executable format was a.out. For a while, part ELF/part a.out systems were common. Some still exist. 13.1.1. binfmt_aout: executable interpreter for a.out formata.out is the venerable executable format that was common in Unix's early history and originally Linux's only executable format. To this day, the default name of the executable output file of the GNU compiler is a.out (regardless of what it's format is). If you try to run an a.out executable without this, your exec system call fails with a "cannot execute binary file" error. There are no LKM parameters. Example:
13.1.2. binfmt_elf: executable interpreter for ELF formatELF is the normal executable format on Linux systems. It's almost inconceivable that you wouldn't have this executable interpreter bound into the base kernel (if for no other reason that your insmod is probably an ELF executable). However, it is conceptually possible to leave it out of the base kernel and insert it as an LKM. There are no LKM parameters. Example:
13.1.3. binfmt_java: executable interpreter for Java bytecodeJava is a relatively modern object oriented programming language. Java programs are traditionally compiled into "Java bytecode" which is meant to be interpreted by a Java bytecode interpreter. The point of this new object language is that the bytecode object files are portable: Although different systems require different object formats, as long as each system has a bytecode interpreter, it can run bytecode object files. (This only works for a while, of course. If portability were that easy, all systems today would use the same object format anyway). While the intent was that the bytecode interpreter would run as a user space program, with this LKM you can make the Linux kernel interpret Java bytecode like any other executable format. So you can run a program compiled from Java the same as you would run a program compiled from C (e.g. type its name at a command shell prompt). In practice, the advantages of the intermediate bytecode language have not been proven and it is quite common to compile Java directly to a more traditional executable format, such as ELF. If you do that, you don't need binfmt_java. There are no LKM parameters. Example:
13.2. Block Device Drivers13.2.1. floppy: floppy disk driverThis is the device driver for floppy disks. You need this in order to access a floppy disk in any way. This LKM is documented in the file README.fd in the linux/drivers/block directory of the Linux source tree. For detailed up to date information refer directly to this file. Note that if you boot (or might boot) from a floppy disk or with a root filesystem on a floppy disk, you must have this driver bound into the base kernel, because your system will need it before it has a chance to insert the LKM. Example:
There is only one LKM parameter: floppy. But it contains many subparameters. The reason for this unusual parameter format is to be consistent with the way you would specify the same things in the kernel boot parameters if the driver were bound into the base kernel. The value of floppy is a sequence of blank-delimited words. Each of those words is one of the following sequences of comma-delimited words:
13.2.2. loop: loop device driverThis module lets you mount a filesystem that is stored in a regular file (in another filesystem). One use of this is to test an ISO 9660 filesystem before irreversibly burning it onto a CD. You build the filesystem in a 650 MB regular file. That file will be the input to the CD burning program. But you can define that file as a loopback device and then mount the filesystem right from the file. It can also give you a handy way to transmit collections of files over a network. It's like a tar file, only you don't have to pack and unpack it -- you just mount the original file. You can also encrypt or compress the file. To do that, you need a recent version of mount and other patches for DES and IDEA. They can Do not confuse these loop devices with the "loopback device" used for network connections from the machine to itself. That isn't actually a device at all - it's a network interface. Example:
The module has no parameters. 13.2.3. linear: linear (non-RAID) disk array device driverThis driver lets you combine several disk partitions into one logical block device. If you use this, then your multiple devices driver will be able to use the so-called linear mode, i.e. it will combine the disk partitions by simply appending one to the other. See Software-RAID-HOWTO. Example:
There are no module parameters. 13.2.4. raid0: RAID-0 device driverThis driver lets you combine several disk partitions into one logical block device. If you use this, then your multiple devices driver will be able to use the so-called raid0 mode, i.e. it will combine the disk partitions into one logical device in such a fashion as to fill them up evenly, one chunk here and one chunk there. This will increase the throughput rate if the partitions reside on distinct disks. See Software-RAID-HOWTO. Example:
There are no module parameters. 13.2.5. rd: ramdisk device driverA ramdisk is a block device whose storage is composed of system memory (real memory; not virtual). You can use it like a very fast disk device and also in circumstances where you need a device, but don't have traditional hardware devices to play with. A common example of the latter is for a rescue system -- a system you use to diagnose and repair your real system. Since you don't want to mess with your real disks, you run off ramdisks. You might load data into these ramdisks from external media such as floppy disks. Sometimes, you have your boot loader (e.g. lilo) create a ramdisk and load it with data (perhaps from a floppy disk). Of course, if you do this, you cannot use the LKM version of the ramdisk driver because the driver will have to be in the kernel at boot time. A ramdisk is actually conceptually simple in Linux. Disk devices operate through memory because of the buffer cache. The only difference with a ramdisk is that you never actually get past the buffer cache to a real device. This is because with a ramdisk, 1) when you first access a particular block, Linux just assumes it is all zeroes; and 2) the device's buffer cache blocks are never written to the device, ergo never stolen for use with other devices. This means reads and writes are always to the buffer cache and never reach the device. There is additional information about ramdisks in the file Documentation/ramdisk.txt in the Linux source tree. Example:
There are no module parameters that you can supply to the LKM, but if you bind the module into the base kernel, there are kernel parameters you can pass to it. See BootPrompt-HOWTO. 13.2.6. xd: XT disk device driverVery old 8 bit hard disk controllers used in the IBM XT computer. No, the existence of XT disk support does NOT mean that you can run Linux on an IBM XT :). Example:
There are no module parameters. 13.3. SCSI DriversDetailed information about SCSI drivers is in SCSI-2.4-HOWTO. Linux's SCSI function is implemented in three layers, and there are LKMs for all of them. In the middle is the mid-level driver or SCSI core. This consists of the scsi_mod LKM. It does all those things that are common among SCSI devices regardless of what SCSI adapter you use and what class of device (disk, scanner, CD-ROM drive, etc.) it is. There is a low-level driver for each kind of SCSI adapter -- typically, a different driver for each brand. For example, the low-level driver for Advansys adapters (made by the company which is now Connect.com) is named advansys. (If you are comparing ATA (aka IDE) and SCSI disk devices, this is a major difference -- ATA is simple and standard enough that one driver works with all adapters from all companies. SCSI is less standard and as a result you should have less confidence in any particular adapter being perfectly compatible with your system). High-level drivers present to the rest of the kernel an interface appropriate to a certain class of devices. The SCSI high-level driver for tape devices, st, for example, has ioctls to rewind. The high-level SCSI driver for CD-ROM drives, sr, does not. Note that you rarely need a high-level driver specific to a certain brand of device. At this level, there is little room for one brand to be distinguishable from another. One SCSI high-level driver that deserves special mention is sg. This driver, called the "SCSI generic" driver, is a fairly thin layer that presents a rather raw representation of the SCSI mid-level driver to the rest of the kernel. User space programs that operate through the SCSI generic driver (because they access device special files whose major number is the one registered by sg (to wit, 21)) have a detailed understanding of SCSI protocols, whereas user space programs that operate through other SCSI high-level drivers typically don't even know what SCSI is. SCSI-Programming-HOWTO has complete documentation of the SCSI generic driver. The layering order of the SCSI modules belies the way the LKMs depend upon each other and the order in which they must be loaded. You always load the mid-level driver first and unload it last. The low-level and high-level drivers can be loaded and unloaded in any order after that, and they hook themselves into and establish dependency on the mid-level driver at both ends. If you don't have a complete set, you will get a "device not found" error when you try to access a device. Most SCSI low-level (adapter) drivers don't have LKM parameters; they do generally autoprobe for card settings. If your card responds to some unconventional port address you must bind the driver into the base kernel and use kernel "command line" options. See BootPrompt-HOWTO. Or you can twiddle The Source and recompile. Many SCSI low-level drivers have documentation in the drivers/scsi directory in the Linux source tree, in files called README.*. 13.3.2. sd_mod: SCSI high-level driver for disk devicesExample:
There are no module parameters. 13.3.3. st: SCSI high-level driver for tape devicesExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. 13.3.4. sr_mod: SCSI high-level driver for CD-ROM drivesExample:
There are no module parameters. 13.3.5. sg: SCSI high-level driver for generic SCSI devicesSee the explanation of this special high-level driver above. Example:
There are no module parameters. 13.3.6. wd7000: SCSI low-level driver for 7000FASSTExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver atoprobes the card and requires installed BIOS. 13.3.7. aha154x: SCSI low-level driver for Adaptec AHA152X/2825Example:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver atoprobes the card and requires installed BIOS. 13.3.8. aha1542: SCSI low-level driver for Adaptec AHA1542Example:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes the card at 0x330 and 0x334 only. 13.3.9. aha1740: SCSI low-level driver for Adaptec AHA1740 EISAExample:
There are no module parameters. This driver autoprobes the card. 13.3.10. aic7xxx: SCSI low-level driver for Adaptec AHA274X/284X/294XExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes the card and BIOS must be enabled. 13.3.11. advansys: SCSI low-level driver for AdvanSys/Connect.comExample:
Module Parameters:
If you bind this driver into the base kernel, you can pass parameters to it via the kernel boot parameters. See BootPrompt-HOWTO. 13.3.12. in2000: SCSI low-level driver for Always IN2000Example:
There are no module parameters. This driver autoprobes the card. No BIOS is required. 13.3.13. BusLogic: SCSI low-level driver for BusLogicThe list of BusLogic cards this driver can drive is long. Read file drivers/scsi/README.BusLogic in the Linux source tree to get the total picture. Example:
There are no module parameters. If you bind this driver into the base kernel, you can pass parameters to it via the kernel boot parameters. See BootPrompt-HOWTO. 13.3.14. dtc: SCSI low-level driver for DTC3180/3280Example:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes the card. 13.3.15. eata: SCSI low-level driver for EATA ISA/EISAThis driver handles DPT PM2011/021/012/022/122/322. Example:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. 13.3.16. eata_dma: SCSI low-level driver for EATA-DMAThis driver handles DPT, NEC, AT&T, SNI, AST, Olivetti, and Alphatronix. This driver handles DPT Smartcache, Smartcache III and SmartRAID. Example:
There are no module parameters. Autoprobe works in all configurations. 13.3.17. eata_pio: SCSI low-level driver for EATA-PIOThis driver handles old DPT PM2001, PM2012A. Example:
There are no module parameters. 13.3.18. fdomain: SCSI low-level driver for Future Domain 16xxExample:
There are no module parameters. This driver autoprobes the card and requires installed BIOS. 13.3.19. NCR5380: SCSI low-level driver for NCR5380/53c400Example:
Parameters:
If you bind this driver into the base kernel, you can pass parameters to it via the kernel boot parameters. See BootPrompt-HOWTO. 13.3.20. NCR53c406a: SCSI low-level driver for NCR53c406aExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. 13.3.21. 53c7,8xx.o: SCSI low-level driver for NCR53c7,8xxExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes the card and requires installed BIOS. 13.3.22. ncr53c8xx: SCSI low-level driver for PCI-SCS NCR538xx familyExample:
There are no module parameters. 13.3.23. ppa: low-level SCSI driver for IOMEGA parallel port ZIP driveSee the file drivers/scsi/README.ppa in the Linux source tree for details. Example:
Parameters:
13.3.24. pas16: SCSI low-level driver for PAS16Example:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes the card. No BIOS is required. 13.3.25. qlogicfas: SCSI low-level driver for Qlogic FASExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. 13.3.26. qlogicisp: SCSI low-level driver for Qlogic ISPExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. Requires firmware. 13.3.27. seagate: SCSI low-level driver for Seagate, Future DomainThis driver is for Seagate ST-02 and Future Domain TMC-8xx. Example:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes for address only. The IRQ is fixed at 5. The driver requires installed BIOS. 13.3.28. t128: SCSI low-level driver for Trantor T128/T128F/T228Example:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes the card. The driver requires installed BIOS. 13.3.29. u14-34f: SCSI low-level driver for UltraStor 14F/34FExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. This driver autoprobes the card, but not the 0x310 port. No BIOS is required. 13.3.30. ultrastor: low-level SCSI driver for UltraStorExample:
There are no module parameters for the LKM, but if you bind this module into the base kernel, you can pass some parameters via the Linux boot parameters. See BootPrompt-HOWTO. 13.4. Network Device Drivers13.4.1. bsd_comp: optional BSD compressor for PPPExample:
There are no module parameters. This module depends on module ppp. 13.4.2. slhc: SLHC compressor for PPPThis module contains routines to compress and uncompress tcp packets (for transmission over low speed serial lines). These routines are required by PPP (also ISDN-PP) and SLIP protocols, and are used by the LKMs that implement those protocols. Example:
There are no module parameters. 13.4.3. 8390: General NS8390 Ethernet driver coreThis is driver code for the 8390 Ethernet chip on which many Ethernet adapters are based. This is not a complete interface driver; the routines in this module are used by drivers for particular Ethernet adapters, such as ne and 3c503. Example:
There are no module parameters. 13.4.4. dummy: Dummy network interface driverThis is said to be a bit-bucket device (i.e. traffic you send to this device is consigned into oblivion) with a configurable IP address. It is most commonly used in order to make your currently inactive SLIP address seem like a real address for local programs. However, it also functions as a sort of loopback device. You configure it for a particular IP address and any packet you send to that IP address via this interface comes back and appears as a packet received by that interface for that IP address. This is especially handy for an IP address that would normally be reflected by another interface (a PPP interface, perhaps), but that interface is down right now. You can have multiple dummy interfaces. They are named dummy0, dummy1, etc. Example:
There are no module parameters. 13.4.5. eql: serial line load balancerIf you have two serial connections to some other computer (this usually requires two modems and two telephone lines) and you use PPP (a protocol for sending internet traffic over telephone lines) or SLIP (an older alternative to PPP) on them, you can make them behave like one double speed connection using this driver. Example:
There are no module parameters. 13.4.6. dlci: frame relay DLCI driverThis implements the frame relay protocol; frame relay is a fast low-cost way to connect to a remote internet access provider or to form a private wide area network. The one physical line from your box to the local "switch" (i.e. the entry point to the frame relay network) can carry several logical point-to-point connections to other computers connected to the frame relay network. To use frame relay, you need supporting hardware (FRAD) and certain programs from the net- tools package as explained in Documentation/networking/framerelay.txt in the Linux source tree. Example:
There are no module parameters. 13.4.7. sdla: Sangoma S502A FRAD driverThis is a driver for the Sangoma S502A, S502E and S508 Frame Relay Access Devices. These are multi-protocol cards, but this driver can drive only frame relay right now. Please read Documentation/networking/framerelay.txt in the Linux source tree. Example:
There are no module parameters. This module depends on module dlci. 13.4.8. plip: PLIP network interface driverPLIP (Parallel Line Internet Protocol) is used to create a mini network consisting of two (or, rarely, more) local machines. The parallel ports (the connectors virtually all ISA-descendant computers have that are normally used to attach printers) are connected using "null printer" or "Turbo Laplink" cables which can transmit 4 bits at a time or using special PLIP cables, to be used on bidirectional parallel ports only, which can transmit 8 bits at a time. The cables can be up to 15 meters long. This works also if one of the machines runs DOS/Windows and has some PLIP software installed, e.g. the Crynwr PLIP packet driver and winsock or NCSA's telnet. See PLIP-Install-HOWTO. Example:
Parameters:
13.4.9. ppp: PPP network protocol driverPPP (Point to Point Protocol) is the most common protocol to use over a serial port (with or without a modem attached) to create an IP network link between two computers. Along with this kernel driver, you need the user space program pppd running. See PPP-HOWTO. Example:
There are no module parameters. This module depends on module slhc. The module also accesses serial devices, which are driven by the serial module, so it depends on that module too. This dependency is not detected by depmod, so you either have to declare it manually or load serial explicitly. 13.4.10. slip: SLIP network protocol driverSLIP (Serial Line Internet Protocol) is like PPP, only older and simpler. Example:
Parameters:
This module depends on module slhc. The module also accesses serial devices, which are driven by the serial module, so it depends on that module too. This dependency is not detected by depmod, so you either have to declare it manually or load serial explicitly. 13.4.11. baycom: BAYCOM AX.25 amateur radio driverThis is a driver for Baycom style simple amateur radio modems that connect to either a serial interface or a parallel interface. The driver works with the ser12 and par96 designs. For more information, see http://www.baycom.org/~tom. Example:
Parameters:
13.4.12. strip: STRIP (Metricom starmode radio IP) driverSTRIP is a radio protocol developed for the MosquitoNet project to send Internet traffic using Metricom radios. Metricom radios are small, battery powered, 100kbit/sec packet radio transceivers, about the size and weight of a wireless telephone. (You may also have heard them called "Metricom modems" but we avoid the term "modem" because it misleads many people into thinking that you can plug a Metricom modem into a phone line and use it as a modem.) You can use STRIP on any Linux machine with a serial port, although it is obviously most useful for people with laptop computers. Example:
There are no module parameters. 13.4.13. wavelan: WaveLAN driverWaveLAN card are for wireless ethernet-like networking. This driver drives AT&T GIS and NCR WaveLAN cards. Example:
Parameters:
13.4.14. wic: WIC Radio IP bridge driverThis is a driver for the WIC parallel port radio bridge. Example:
It appears that devices wic0, wic1 and wic2 are directly related to corresponding lpN ports. 13.4.15. scc: Z8530 SCC kiss emulation driverThese cards are used to connect your Linux box to an amateur radio in order to communicate with other computers. If you want to use this, read Documentation/networking/z8530drv.txt in the Linux kernel source tree and HAM-HOWTO. Example:
There are no module parameters. 13.4.16. 3c501: 3COM 3c501 Ethernet driverThis is a driver for 3COM's 3c501 Ethernet adapter. Example: modprobe 3c501 io=0x280 irq=5 Parameters:
13.4.17. 3c503: 3COM 3c503 driverThis is a driver for 3COM's 3c503 Ethernet adapter. Example:
Parameters:
This module depends on module 8390. 13.4.18. 3c505: 3COM 3c505 driverThis is a driver for 3COM's 3c505 Ethernet adapter. Example:
Parameters:
This module depends on module 8390. 13.4.19. 3c507: 3COM 3c507 driverThis is a driver for 3COM's 3c507 Ethernet adapter. Example:
Parameters:
This module depends on module 8390. 13.4.20. 3c509: 3COM 3c509/3c579 driverThis is a driver for 3COM's 3c507 and 3c579 Ethernet adapters. Example:
Parameters:
Module load-time probing Works reliably only on EISA, ISA ID-PROBE IS NOT RELIABLE! Bind this driver into the base kernel for now, if you need it auto-probing on an ISA-bus machine. 13.4.21. 3c59x: 3COM 3c590 series "Vortex" driverThis is a driver for the following 3COM Ethernet adapters:
Example:
Parameters:
Details of the device driver implementation are at the top of the source file. 13.4.22. wd: Western Digital/SMC WD80*3 driverThis is a driver for the Western Digital WD80*3 Ethernet adapters. Example:
Parameters:
If you don't specify an I/O port, the driver probes 0x300, 0x280, 0x380, and 0x240. If you don't specify an IRQ, the driver reads it from the adapter's EEPROM and with ancient cards that don't have it, the driver uses autoIRQ. The driver depends on module 8390. 13.4.23. smc-ultra: SMC Ultra/EtherEZ driverThis is a driver for the Western Digital WD80*3 Ethernet adapters. Example:
Parameters:
This driver depends on module 8390. 13.4.24. smc9194: SMC 9194 driverThis is a driver for SMC's 9000 series of Ethernet cards. Example:
Parameters:
The debug level is settable in the source code. 13.4.25. at1700: AT1700 driverThis is a driver for the AT1700 Ethernet adapter. Example:
Parameters:
13.4.26. e2100: Cabletron E21xx driverExample:
Parameters:
This module depends on module 8390. 13.4.27. depca: DEPCA, DE10x, DE200, DE201, DE202, DE422 driverThis is a driver for the DEPCA, DE10x, DE200, DE201, DE202, and DE422 Ethernet adapters. Example:
13.4.28. ewrk3: EtherWORKS 3 (DE203, DE204, DE205) driverThis is a driver for the EtherWORKS 3 (DE203, D3204, and DE205) Ethernet adapters. Example:
On an EISA bus, this driver does EISA probing. On an ISA bus, this driver does no autoprobing when loaded as an LKM. However, if you bind it into the base kernel, it probes addresses 0x100, 0x120, etc. up through 0x3C0 except 0x1E0 and 0x320. 13.4.29. eexpress: EtherExpress 16 driverThis is a driver for the EtherExpress 16 Ethernet adapter. Example:
Parameters:
13.4.30. eepro: EtherExpressPro driverThis is a driver for the EtherExpressPro Ethernet adapter. Example:
Parameters:
13.4.31. fmv18k: Fujitsu FMV-181/182/183/184 driverThis is a driver for the Fujitsu FMV-181, FMV-182, FMV-183, FMV-183, and FMV-184 Ethernet adapters. Example:
Parameters:
13.4.32. hp-plus: HP PCLAN+ (27247B and 27252A) driverThis is a driver for HP's PCLAN+ (27247B and 27252A) Ethernet adapters. Example:
Parameters:
This module depends on module 8390. 13.4.33. hp: HP PCLAN (27245, 27xxx) driverThis is a driver for HP's PCLAN (27245 and other 27xxx series) Ethernet adapters. Example:
Parameters:
This module depends on module 8390. 13.4.34. hp100: HP 10/100VG PCLAN (ISA, EISA, PCI) driverThis is a driver for HP's 10/100VG PCLAN Ethernet adapters. It works with the ISA, EISA, and PCI versions. Example:
Parameters:
13.4.35. eth16i: ICL EtherTeam 16i/32 driverThis is a driver for ICL's EtherTeam 16i (eth16i) and 32i (eth32i) Ethernet adapters. Example:
Parameters:
13.4.36. ne: NE2000/NE1000 driverThis is a driver for the venerable NE2000 Ethernet adapter, its NE1000 forerunner, and all the generic Ethernet adapters that emulate this de facto standard card. Example:
Parameters:
This module depends on module 8390. 13.4.37. ni52: NI5210 driverThis is a driver for the NI5210 Ethernet adapter. Example:
13.4.38. ac3200: Ansel Communications EISA 3200 driverThis is a driver for the Ansel Communications EISA 3200 Ethernet adapter. Example:
This module depends on module 8390. 13.4.39. apricot: Apricot Xen-II on board ethernet driverExample:
Parameters:
13.4.40. de4x5: DE425, DE434, DE435, DE450, DE500 driverThis is a driver for the DE425, DE434, DE435, DE450, and DE500 Ethernet adapters. Example:
Parameters:
13.4.41. tulip: DECchip Tulip (dc21x4x) PCI driverExample:
Read Documentation/networking/tulip.txt in the Linux source tree. 13.4.42. dgrs: Digi Intl RightSwitch SE-X driverThis is a driver for the Digi International RightSwitch SE-X EISA and PCI boards. These boards have a 4 (EISA) or 6 (PCI) port Ethernet switch and a NIC combined into a single board. There is a tool for setting up input and output packet filters on each port, called dgrsfilt. The management tool lets you watch the performance graphically, as well as set the SNMP agent IP and IPX addresses, IEEE Spanning Tree, and Aging time. These can also be set from the command line when the driver is loaded. There is also a companion management tool, called xrightswitch. Examples:
Parameters:
13.4.43. de600: D-Link DE600 pocket adapter driverThis is a driver for the D-Link DE600 pocket Ethernet adapter. Example:
Parameters:
13.4.44. de620: D-Link DE620 pocket adapter driverThis is a driver for the D-Link DE620 pocket Ethernet adapter. Example:
Parameters:
You can't specify both bnc=1 and utp=1. 13.4.45. ibmtr: Tropic chipset based token ring adapter driverExample:
Parameters:
13.4.46. arcnet: ARCnet driverRead The Fine Information in Documentation/networking/arcnet.txt in the Linux source tree. Also Arcnet hardware information arcnet-hardware.txt is found in same place. Example:
Parameters:
13.4.47. isdn: basic ISDN functionsThis module provides ISDN functions used by ISDN adapter drivers. Setting up ISDN networking is a complicated task. Read documentation found in Documentation/isdn in the Linux source tree. Example:
There are no module parameters. This module depends on module slhc. 13.4.48. icn: ICN 2B and 4B driverThis is a driver for the ICN 2B and ICN 4B ISDN adapters. Example:
Parameters:
This module depends on module isdn. 13.4.49. pcbit: PCBIT-D driverThis is a driver for the PCBIT-D ISDN adapter driver. Example:
Parameters:
This module depend on module isdn. 13.4.50. teles: Teles/NICCY1016PC/Creatix driverThis is a driver for the Teles/NICCY1016PC/Creatix ISDN adapter. It can drive up to 16 cards. Example:
Parameters:
The driver determines the type of card from the port, irq and shared memory address:
This module depends on module isdn. 13.5. CDROM Device Drivers13.5.1. axtcd: Aztech/Orchid/Okano/Wearnes/TXC/CDROM driverThis is a driver for the Aztech, Orchid, Okano, Wearnes, TXC, and CDROM devices (which have special non-SCSI non-ATA interfaces). Example:
Parameters:
Read Documentation/cdrom/aztcd in the Linux source tree for full information. 13.5.2. gscd: Goldstar R420 CDROM driverThis is a driver for the Goldstar R420 CDROM drive, which does not use either an ATA or SCSI interface. Example:
Parameters:
13.5.3. sbpcd: Sound Blaster CDROM driverThis is a driver for the Matsushita, Panasonic, Creative, Longshine, and TEAC CDROM drives that don't attach via ATA or SCSI. Example:
Parameters:
An additional parameter is an SBPRO setting, as described in Documentation/cdrom/sbpcd in the Linux source tree. 13.5.4. mcd: Mitsumi CDROM driverThis is a driver for Mitsumi CDROM drives that don't attach via ATA or SCSI. It does not handle XA or multisession. Example:
Parameters:
13.5.5. mcdx: Mitsumi XA/MultiSession driverThis driver is like mcd, only it has XA and multisession functions. Example:
13.5.6. optcd: Optics Storage DOLPHIN 8000AT CDROM driverThis is the driver for the so-called "dolphin" CDROM drive form Optics Storage, with the 34-pin Sony-compatible interface. For the ATA-compatible Optics Storage 8001 drive, you will want the ATAPI CDROM driver. The driver also seems to work with the Lasermate CR328A. Example:
Parameters:
13.5.7. cm206: Philips/LMS CM206 CDROM driverThis is the driver for the Philips/LMS cm206 CDROM drive in combination with the cm260 host adapter card. Example:
Parameters:
13.5.8. sjcd: Sanyo CDR-H94A CDROM driverExample:
Parameters:
The driver uses no IRQ and no DMA channel. 13.5.9. isp16: ISP16/MAD16/Mozart soft configurable cdrom driverThis is a driver for the ISP16 or MAD16 or Mozart soft configurable cdrom interface. Example:
Parameters:
13.5.10. cdu31a: Sony CDU31A/CDU33A CDROM driverExample:
Parameters:
13.5.11. sonycd535: Sony CDU535 CDROM driverExample:
Parameters:
13.6. Filesystem Drivers13.6.3. ext2: "Second extended" filessystem driverExample:
There are no module parameters. 13.6.5. fat: DOS FAT filesystem functionsThis module provides services for use by the MSDOS and VFAT filesystem drivers. Example:
There are no module parameters. 13.6.6. msdos: MSDOS filesystem driverExample:
There are no module parameters. This module depends on the module fat. 13.6.7. vfat: VFAT (Windows-95) filesystem driverExample:
There are no module parameters. This module depends on module fat. 13.6.8. umsdos: UMSDOS filesystem driverThis is a driver for the UMSDOS filesystem type, which is a unix style filesystem built on top of an MSDOS FAT filesystem. Example:
There are no module parameters. This module depends on the fat and msdos modules. 13.6.10. smbfs: SMB filesystem driverSMBFS is a filesystem type which has an SMB protocol interface. This is the protocol Windows for Workgroups, Windows NT or Lan Manager use to talk to each other. SMBFS was inspired by Samba, the program written by Andrew Tridgell that turns any unix host into a file server for DOS or Windows clients. See ftp://nimbus.anu.edu.au/pub/tridge/samba/ for this interesting program suite and lots of more information on SMB and NetBIOS over TCP/IP. There you also find explanation for concepts like netbios name or share. To use SMBFS, you need a special mount program, which can be found in the ksmbfs package, found on ftp://ibiblio.org/pub/Linux/system/Filesystems/smbfs. Example:
There are no module parameters 13.6.11. ncpfs: NCP (Netware) filesystem driverNCPFS is a filesystem type which has an NCP protocol interface, designed by the Novell Corporation for their NetWare product. NCP is functionally similar to the NFS used in the TCP/IP community. To mount a Netware filesystem, you need a special mount program, which can be found in the ncpfs package. Homesite for ncpfs is ftp.gwdg.de/pub/linux/misc/ncpfs, but Ibiblio and its many mirrors will have it as well. Related products are Linware and Mars_nwe, which will give Linux partial NetWare Server functionality. Mars_nwe can be found on ftp.gwdg.de/pub/linux/misc/ncpfs. Example:
There are no module parameters. This module depends on module ipx. 13.6.12. isofs: ISO 9660 (CDROM) filesystem driverExample:
There are no module parameters. 13.6.13. hpfs: OS/2 HPFS filesystem driverThis filesystem driver for OS/2's HPFS filesystem provides only read-only access. Example:
There are no module parameters. 13.6.14. sysv: System V and Coherent filesystem driverThis is the implementation of the SystemV/Coherent filesystem type for Linux. It implements all of
Example:
There are no module parameters. 13.6.16. ufs: UFS filesystem driverApparently for mounting disks with FreeBSD and/or Sun partitions. No documentation exists, apart from The Source. This filesystem driver provides only read-only access. Example:
There are no module parameters. 13.7. Miscellaneous Device Driver13.7.1. misc: device driver for "miscellaneous" character devicesA whole bunch of device types that don't appear in large enough numbers on a system to deserve major numbers of their own share Major Number 10 and are collectively called "miscellaneous" character devices. This module provides the common interface to serve that major number, but there are individual drivers for the specific device types. Those drivers register themselves with this driver. Example:
There are no module parameters. 13.8. Serial Device Drivers13.8.1. serial: serial communication port (UART) device driverThis driver drives conventional serial ports (UARTs), but not some of the specialized high performance multi-port devices. NOTE: serial is required by other modules, such as ppp and slip. Also it is required by serial mice and accordingly by gpm. However this isn't the regular kind of dependency that is detected by module handling tools, so you must load serial manually. Example:
There are no module parameters. 13.8.2. cyclades: Cyclades async mux device driverExample:
There are no module parameters. The intelligent boards also need to have their firmware code downloaded to them. This is done via a user level application supplied in the driver package called stlload. Compile this program where ever you dropped the package files, by typing make. In its simplest form you can then type stlload in this directory and that will download firmware into board 0 (assuming board 0 is an EasyConnection 8/64 board). To download to an ONboard, Brumby or Stallion do: Read the information in the file Documentation/stallion.txt in the Linux source tree. 13.8.3. stallion: Stallion EasyIO or EC8/32 device driverThe intelligent boards also need to have their firmware code downloaded to them. This is done via a user level application supplied in the driver package called stlload. Read the information in the file Documentation/stallion.txt in the Linux source tree. Example:
There are no module parameters. 13.8.4. istallion: Stallion EC8/64, ONboard, Brumby device driverThe intelligent boards also need to have their firmware code downloaded to them. This is done via a user level application supplied in the driver package called stlload. Read the information at /usr/src/linux/drivers/char/README.stallion. Example:
There are no module parameters. 13.8.5. riscom8: SDL RISCom/8 card device driverExample:
This driver can drive up to 4 boards at time. 13.9. Parallel Device Drivers13.9.1. lp: Parallel printer device driverExample:
This driver probes ports 0x278, 0x378, and 0x3bc. Note: loading lp without any parameters will grab all parallel ports. 13.10. Bus Mouse Device Drivers13.10.1. atixlmouse: ATIXL busmouse driverExample:
There are no parameters. This module depends on module misc. 13.10.2. busmouse: Logitech busmouse driverExample:
There are no module parameters. This module depends on module misc. 13.10.3. msbusmouse: Microsoft busmouse driverExample:
There are no module parameters. This module depends on module misc. 13.10.4. psaux: PS/2 mouse (aka "auxiliary device") driverExample:
There are no module parameters. This module depends on module misc. 13.11. Tape Device DriversFor SCSI tape device drivers, see Section 13.3. There are no LKMs for QIC-02 tape devices, but there is a device driver you can bind into the base kernel. 13.11.1. ftape: floppy tape (QIC-80/Travan) device driverExample:
Optional parameter tracing can take following values
The default is 3. 13.12. Watchdog Timers13.12.1. WDT: WDT Watchdog timer device driverExample:
There are no module parameters. The device address is hardcoded as 0x240. The IRQ is hardcoded as 14. This module depends on module misc. 13.12.2. softdog: Software Watchdog TimerExample:
There are no module parameters. This module depends on module misc. 13.12.3. pcwd: Berkshire Products PC Watchdog DriverExample:
There are no module parameters. This module depends on module misc. 13.13. Sound Device DriversConfiguring sound is a complex task. Read the files in directory Documention/sound in the Linux source tree. Example:
Option: dma_buffsize=32768 |