7763 lines
120 KiB
HTML
7763 lines
120 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Individual Modules</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="Linux Loadable Kernel Module HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Related Documentation"
|
|
HREF="x973.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Maintenance Of This Document"
|
|
HREF="x2986.html"></HEAD
|
|
><BODY
|
|
CLASS="SECT1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Linux Loadable Kernel Module HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x973.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x2986.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="INDIVIDUAL"
|
|
></A
|
|
>15. Individual Modules</H1
|
|
><P
|
|
>In 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).</P
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN985"
|
|
></A
|
|
>15.1. Executable Interpreters</H2
|
|
><P
|
|
>You 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.</P
|
|
><P
|
|
>That one bound-in executable interpreter is almost certainly the ELF
|
|
interpreter, since virtually all executables in a Linux system are
|
|
ELF.</P
|
|
><P
|
|
>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.</P
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN990"
|
|
></A
|
|
>15.1.1. binfmt_aout: executable interpreter for a.out format</H3
|
|
><P
|
|
>a.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 <TT
|
|
CLASS="FILENAME"
|
|
>a.out</TT
|
|
> (regardless of what it's format
|
|
is).</P
|
|
><P
|
|
>If you try to run an a.out executable without this, your
|
|
<TT
|
|
CLASS="FUNCTION"
|
|
>exec</TT
|
|
> system call fails with a "cannot execute
|
|
binary file" error.</P
|
|
><P
|
|
>There are no LKM parameters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe binfmt_aout</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN999"
|
|
></A
|
|
>15.1.2. binfmt_elf: executable interpreter for ELF format</H3
|
|
><P
|
|
>ELF is the normal executable format on Linux systems.</P
|
|
><P
|
|
>It's almost inconceivable that you wouldn't have this executable
|
|
interpreter bound into the base kernel (if for no other reason that
|
|
your <B
|
|
CLASS="COMMAND"
|
|
>insmod</B
|
|
> is probably an ELF executable).
|
|
However, it is conceptually possible to leave it out of the base
|
|
kernel and insert it as an LKM.</P
|
|
><P
|
|
>There are no LKM parameters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe binfmt_elf</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1007"
|
|
></A
|
|
>15.1.3. binfmt_java: executable interpreter for Java bytecode</H3
|
|
><P
|
|
>Java 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).</P
|
|
><P
|
|
>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).</P
|
|
><P
|
|
>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 <B
|
|
CLASS="COMMAND"
|
|
>binfmt_java</B
|
|
>.</P
|
|
><P
|
|
>There are no LKM parameters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe binfmt_java</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN1016"
|
|
></A
|
|
>15.2. Block Device Drivers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1018"
|
|
></A
|
|
>15.2.1. floppy: floppy disk driver</H3
|
|
><P
|
|
>This is the device driver for floppy disks. You need this in order to
|
|
access a floppy disk in any way.</P
|
|
><P
|
|
>This LKM is documented in the file <TT
|
|
CLASS="FILENAME"
|
|
>README.fd</TT
|
|
> in
|
|
the <TT
|
|
CLASS="FILENAME"
|
|
>linux/drivers/block
|
|
directory</TT
|
|
> of the Linux source tree. For detailed up to date
|
|
information refer directly to this file.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>
|
|
modprobe floppy 'floppy="daring two_fdc 0,thinkpad 0x8,fifo_depth"'</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There is only one LKM parameter: <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>floppy</I
|
|
></TT
|
|
>. 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.</P
|
|
><P
|
|
>The value of <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>floppy</I
|
|
></TT
|
|
> is a sequence of
|
|
blank-delimited words. Each of those words is one of the following
|
|
sequences of comma-delimited words:</P
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>asus_pci</DT
|
|
><DD
|
|
><P
|
|
> Sets the bit mask of allowed drives to allow only units 0 and
|
|
1. Obsolete, as this is the default setting anyways
|
|
</P
|
|
></DD
|
|
><DT
|
|
>daring</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver that you have a well behaved floppy
|
|
controller. This allows more efficient and smoother
|
|
operation, but may fail on certain controllers. This may
|
|
speed up certain operations.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>0,daring</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver that your floppy controller should be used
|
|
with caution.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>one_fdc</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver that you have only floppy controller
|
|
(default).
|
|
</P
|
|
></DD
|
|
><DT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>address</TT
|
|
>,two_fdc</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver that you have two floppy
|
|
controllers. The second floppy controller is assumed to be
|
|
at <TT
|
|
CLASS="VARNAME"
|
|
>address</TT
|
|
>. This option is not needed if
|
|
the second controller is at address 0x370, and if you use
|
|
the 'cmos' option
|
|
</P
|
|
></DD
|
|
><DT
|
|
>two_fdc</DT
|
|
><DD
|
|
><P
|
|
> Like above, but with default address
|
|
</P
|
|
></DD
|
|
><DT
|
|
>thinkpad</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver that you have an IBM Thinkpad model
|
|
notebook computer. Thinkpads use an inverted convention for
|
|
the disk change line.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>0,thinkpad</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver that you don't have a Thinkpad.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>nodma</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver not to use DMA for data transfers.
|
|
This is needed on HP Omnibooks, which don't have a workable
|
|
DMA channel for the floppy driver. This option is also
|
|
useful if you frequently get "Unable to allocate DMA
|
|
memory" messages. Indeed, DMA memory needs to be
|
|
continuous in physical memory, and is thus harder to find,
|
|
whereas non-DMA buffers may be allocated in virtual
|
|
memory. However, I advise against this if you have an FDC
|
|
without a FIFO (8272A or 82072). 82072A and later are
|
|
OK). You also need at least a 486 to use nodma. If you use
|
|
nodma mode, I suggest you also set the FIFO threshold to 10
|
|
or lower, in order to limit the number of data transfer
|
|
interrupts.
|
|
</P
|
|
><P
|
|
> If you have a FIFO-able FDC, the floppy driver
|
|
automatically falls back on non DMA mode if it can't find
|
|
any DMA-able memory. If you want to avoid this, explicitly
|
|
specify "yesdma".
|
|
</P
|
|
></DD
|
|
><DT
|
|
>omnibook</DT
|
|
><DD
|
|
><P
|
|
> Same as <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>nodma</I
|
|
></TT
|
|
>.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>yesdma</DT
|
|
><DD
|
|
><P
|
|
> Tells the floppy driver that a workable DMA channel is available
|
|
(the default).
|
|
</P
|
|
></DD
|
|
><DT
|
|
>nofifo</DT
|
|
><DD
|
|
><P
|
|
> Disables the FIFO entirely. This is needed if you get "Bus
|
|
master arbitration error" messages from your Ethernet card (or
|
|
from other devices) while accessing the floppy.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>fifo</DT
|
|
><DD
|
|
><P
|
|
> Enables the FIFO (default)
|
|
</P
|
|
></DD
|
|
><DT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>threshold</TT
|
|
>,fifo_depth</DT
|
|
><DD
|
|
><P
|
|
> Sets the FIFO threshold. This is mostly relevant in DMA
|
|
mode. If this is higher, the floppy driver tolerates more
|
|
interrupt latency, but it triggers more interrupts (i.e. it
|
|
imposes more load on the rest of the system). If this is
|
|
lower, the interrupt latency should be lower too (faster
|
|
processor). The benefit of a lower threshold is fewer
|
|
interrupts.
|
|
</P
|
|
><P
|
|
> To tune the fifo threshold, switch on over/underrun
|
|
messages using 'floppycontrol --messages'. Then access a
|
|
floppy disk. If you get a huge amount of "Over/Underrun -
|
|
retrying" messages, then the fifo threshold is too low.
|
|
Try with a higher value, until you only get an occasional
|
|
Over/Underrun.
|
|
</P
|
|
><P
|
|
> The value must be between 0 and 0xf, inclusive.
|
|
</P
|
|
><P
|
|
> As you insert and remove the LKM to try different values,
|
|
remember to redo the 'floppycontrol --messages' every time
|
|
you insert the LKM. You shouldn't normally have to tune
|
|
the fifo, because the default (0xa) is reasonable.
|
|
</P
|
|
></DD
|
|
><DT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>drive</TT
|
|
>,<TT
|
|
CLASS="VARNAME"
|
|
>type</TT
|
|
>,cmos</DT
|
|
><DD
|
|
><P
|
|
> Sets the CMOS type of <TT
|
|
CLASS="VARNAME"
|
|
>drive</TT
|
|
> to
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>type</TT
|
|
>. This is mandatory if you have
|
|
more than two floppy drives (only two can be described in
|
|
the physical CMOS), or if your BIOS uses non-standard CMOS
|
|
types. The CMOS types are:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
> Use the value of the physical CMOS
|
|
</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>5 1/4 DD</P
|
|
></DD
|
|
><DT
|
|
>2</DT
|
|
><DD
|
|
><P
|
|
>5 1/4 HD</P
|
|
></DD
|
|
><DT
|
|
>3</DT
|
|
><DD
|
|
><P
|
|
>3 1/2 DD</P
|
|
></DD
|
|
><DT
|
|
>4</DT
|
|
><DD
|
|
><P
|
|
>3 1/2 HD</P
|
|
></DD
|
|
><DT
|
|
>5</DT
|
|
><DD
|
|
><P
|
|
>3 1/2 ED</P
|
|
></DD
|
|
><DT
|
|
>6</DT
|
|
><DD
|
|
><P
|
|
>3 1/2 ED</P
|
|
></DD
|
|
><DT
|
|
>16</DT
|
|
><DD
|
|
><P
|
|
>unknown or not installed</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
</P
|
|
><P
|
|
> (Note: there are two valid types for ED drives. This is
|
|
because 5 was initially chosen to represent floppy
|
|
<EM
|
|
>tapes</EM
|
|
>, and 6 for ED drives. AMI
|
|
ignored this, and used 5 for ED drives. That's why the
|
|
floppy driver handles both)
|
|
</P
|
|
></DD
|
|
><DT
|
|
>unexpected_interrupts</DT
|
|
><DD
|
|
><P
|
|
> Print a warning message when an unexpected interrupt is received.
|
|
(default behavior)
|
|
</P
|
|
></DD
|
|
><DT
|
|
>no_unexpected_interrupts</DT
|
|
><DD
|
|
><P
|
|
> Don't print a message when an unexpected interrupt is
|
|
received. This is needed on IBM L40SX laptops in certain
|
|
video modes. (There seems to be an interaction between
|
|
video and floppy. The unexpected interrupts only affect
|
|
performance, and can safely be ignored.)
|
|
</P
|
|
></DD
|
|
><DT
|
|
>L40SX</DT
|
|
><DD
|
|
><P
|
|
> Same as <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>no_unexpected_interrupts</I
|
|
></TT
|
|
>.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>broken_dcl</DT
|
|
><DD
|
|
><P
|
|
> Don't use the disk change line, but assume that the disk
|
|
was changed whenever the device node is reopened. Needed
|
|
on some boxes where the disk change line is broken or
|
|
unsupported. This should be regarded as a stopgap measure,
|
|
indeed it makes floppy operation less efficient due to
|
|
unneeded cache flushings, and slightly more unreliable.
|
|
Please verify your cable, connection and jumper settings if
|
|
you have any DCL problems. However, some older drives, and
|
|
also some laptops are known not to have a DCL.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>debug</DT
|
|
><DD
|
|
><P
|
|
> Print debugging messages
|
|
</P
|
|
></DD
|
|
><DT
|
|
>messages</DT
|
|
><DD
|
|
><P
|
|
> Print informational messages for some operations (disk change
|
|
notifications, warnings about over and underruns, and about
|
|
autodetection)
|
|
</P
|
|
></DD
|
|
><DT
|
|
>silent_dcl_clear</DT
|
|
><DD
|
|
><P
|
|
> Uses a less noisy way to clear the disk change line (which
|
|
doesn't involve seeks). Implied by daring.
|
|
</P
|
|
></DD
|
|
><DT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>nr</TT
|
|
>,irq</DT
|
|
><DD
|
|
><P
|
|
> Tells the driver to expect interrupts on IRQ
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>nr</TT
|
|
> instead of the conventional IRQ 6.
|
|
</P
|
|
></DD
|
|
><DT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>nr</TT
|
|
>,dma</DT
|
|
><DD
|
|
><P
|
|
> Tells the driver to use DMA channel <TT
|
|
CLASS="VARNAME"
|
|
>nr</TT
|
|
>
|
|
instead of the
|
|
conventional DMA channel 2.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>slow</DT
|
|
><DD
|
|
><P
|
|
> Use PS/2 stepping rate: PS/2 floppies have much slower step
|
|
rates than regular floppies. It's been recommended that
|
|
take about 1/4 of the default speed in some more extreme
|
|
cases.
|
|
</P
|
|
></DD
|
|
><DT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>mask</TT
|
|
>,allowed_drive_mask</DT
|
|
><DD
|
|
><P
|
|
> Sets the bitmask of allowed drives to <TT
|
|
CLASS="VARNAME"
|
|
>mask</TT
|
|
>.
|
|
By default,
|
|
only units 0 and 1 of each floppy controller are allowed.
|
|
This is done because certain non-standard hardware (ASUS
|
|
PCI motherboards) mess up the keyboard when accessing units
|
|
2 or 3. This option is somewhat obsoleted by the 'cmos'
|
|
option.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>all_drives</DT
|
|
><DD
|
|
><P
|
|
> Sets the bitmask of allowed drives to all drives. Use this
|
|
if you have more than two drives connected to a floppy
|
|
controller.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1194"
|
|
></A
|
|
>15.2.2. loop: loop device driver</H3
|
|
><P
|
|
>This module lets you mount a filesystem that is stored in a regular
|
|
file (in another filesystem). That other file is called the backing file.</P
|
|
><P
|
|
>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 a loopback device based on that file as backing file and
|
|
then mount the filesystem right from the backing file.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>Some people use loop devices on a machine that sometimes runs Windows
|
|
and sometimes runs Linux to allow them to maintain the Linux system
|
|
via the Windows system: put a Linux root filesystem in a file in a FAT
|
|
filesystem that Windows can access, then mount the Linux root
|
|
filesystem via a loop device when Linux is running.</P
|
|
><P
|
|
>You can keep the filesystem encrypted or compressed, or encoded in any
|
|
arbitrary way, in the backing file. The loop device encodes (e.g. encrypts)
|
|
as you write to it, and decodes (e.g. decrypts) as you read. (An
|
|
alternative more popular strategy for encrypting and compressing a
|
|
filesystem is to use an encrypted or compressed filesystem type,
|
|
either a native one or one backed by a normal filesystem. Cfs, Tcfs,
|
|
and Stegfs are examples of such filesystem types).</P
|
|
><P
|
|
>An encoding system is based on a "transfer function". There
|
|
are two tranfer functions built into the <TT
|
|
CLASS="FILENAME"
|
|
>loop</TT
|
|
> module: the
|
|
identify transfer function (which is for the normal no-encoding case
|
|
-- What you see in the loop device is exactly what is in the backing
|
|
file) and a simple XOR encryption function. A separate kernel module
|
|
can add any transfer function by calling the <TT
|
|
CLASS="FILENAME"
|
|
>loop</TT
|
|
>
|
|
module's exported <TT
|
|
CLASS="LITERAL"
|
|
>loop_register_transfer()</TT
|
|
> function.</P
|
|
><P
|
|
>There appear to be various modules floating around
|
|
that provide transfer functions to do compression and encryption (DES,
|
|
IDEA, Fish, etc.).
|
|
Some of them appear to be part of current Linux kernel distributions.
|
|
In addition, there appear to be various alternative loop device drivers,
|
|
many of them also called <TT
|
|
CLASS="FILENAME"
|
|
>loop</TT
|
|
>, that have such transfer
|
|
functions built in.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>This module is a block device driver. You set up a loop device by
|
|
issuing an ioctl to it to bind a file to it. The typical program to
|
|
issue this ioctl is <B
|
|
CLASS="COMMAND"
|
|
>losetup</B
|
|
>. See the documentation
|
|
of <B
|
|
CLASS="COMMAND"
|
|
>losetup</B
|
|
> for more details. There are also options
|
|
on the normal 'mount' command to do loop device setup under the covers,
|
|
but because that confuses the logically separate operations of setting
|
|
up a loop device and mounting a filesystem, for the sake of clarity
|
|
you're probably better off using <B
|
|
CLASS="COMMAND"
|
|
>losetup</B
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe loop</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Module Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>max_loop</DT
|
|
><DD
|
|
><P
|
|
>Number of loop devices that will exist. Contrary to what its
|
|
name suggests, the number you specify is the number of loop
|
|
devices that always exist. An existing device is not
|
|
necessarily configured (bound to a backing file), though,
|
|
so this number can be thought of as the maximum number of
|
|
loop devices that you can configure.
|
|
</P
|
|
><P
|
|
>The minor numbers for these loop devices are consecutive
|
|
starting at 0.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>There is more information on loop devices in the Loopback Encrypted Filesystem HOWTO and the Loopback Root Filesystem HOWTO and the manual for <B
|
|
CLASS="COMMAND"
|
|
>losetup</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1223"
|
|
></A
|
|
>15.2.3. linear: linear (non-RAID) disk array device driver</H3
|
|
><P
|
|
>This driver lets you combine several disk partitions into one
|
|
logical block device.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>See <I
|
|
CLASS="CITETITLE"
|
|
>Software-RAID-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe linear</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1232"
|
|
></A
|
|
>15.2.4. raid0: RAID-0 device driver</H3
|
|
><P
|
|
>This driver lets you combine several disk partitions into one logical
|
|
block device.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>See <I
|
|
CLASS="CITETITLE"
|
|
>Software-RAID-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe raid0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1241"
|
|
></A
|
|
>15.2.5. rd: ramdisk device driver</H3
|
|
><P
|
|
>A 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.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>Sometimes, you have your boot loader (e.g. <B
|
|
CLASS="COMMAND"
|
|
>lilo</B
|
|
>)
|
|
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.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>There is additional information about ramdisks in the file
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>Documentation/ramdisk.txt</TT
|
|
> in the Linux source
|
|
tree.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe rd</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1254"
|
|
></A
|
|
>15.2.6. xd: XT disk device driver</H3
|
|
><P
|
|
>Very 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 :).</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe xd</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="SCSI"
|
|
></A
|
|
>15.3. SCSI Drivers</H2
|
|
><P
|
|
>Detailed information about SCSI drivers is in
|
|
<I
|
|
CLASS="CITETITLE"
|
|
>SCSI-2.4-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>Linux's SCSI function is implemented in three layers, and there are
|
|
LKMs for all of them.</P
|
|
><P
|
|
>In the middle is the mid-level driver or SCSI core. This consists of
|
|
the <B
|
|
CLASS="COMMAND"
|
|
>scsi_mod</B
|
|
> 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.</P
|
|
><P
|
|
>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 <B
|
|
CLASS="COMMAND"
|
|
>advansys</B
|
|
>. (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).</P
|
|
><P
|
|
>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, <B
|
|
CLASS="COMMAND"
|
|
>st</B
|
|
>, for example, has ioctls to
|
|
rewind. The high-level SCSI driver for CD-ROM drives,
|
|
<B
|
|
CLASS="COMMAND"
|
|
>sr</B
|
|
>, does not.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>One SCSI high-level driver that deserves special mention is
|
|
<B
|
|
CLASS="COMMAND"
|
|
>sg</B
|
|
>. 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 <B
|
|
CLASS="COMMAND"
|
|
>sg</B
|
|
> (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.
|
|
<I
|
|
CLASS="CITETITLE"
|
|
>SCSI-Programming-HOWTO</I
|
|
> has complete
|
|
documentation of the SCSI generic driver.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>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
|
|
<I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>. Or you can twiddle The
|
|
Source and recompile.</P
|
|
><P
|
|
>Many SCSI low-level drivers have documentation in the <TT
|
|
CLASS="FILENAME"
|
|
>drivers/scsi</TT
|
|
> directory in the Linux
|
|
source tree, in files called <TT
|
|
CLASS="FILENAME"
|
|
>README.</TT
|
|
>*.</P
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1283"
|
|
></A
|
|
>15.3.1. scsi_mod: SCSI mid-level driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe scsi_mod</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1288"
|
|
></A
|
|
>15.3.2. sd_mod: SCSI high-level driver for disk devices</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sd_mod</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1293"
|
|
></A
|
|
>15.3.3. st: SCSI high-level driver for tape devices</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe st</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1299"
|
|
></A
|
|
>15.3.4. sr_mod: SCSI high-level driver for CD-ROM drives</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sr_mod</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1304"
|
|
></A
|
|
>15.3.5. sg: SCSI high-level driver for generic SCSI devices</H3
|
|
><P
|
|
>See the explanation of this special high-level driver above.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sg</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1310"
|
|
></A
|
|
>15.3.6. wd7000: SCSI low-level driver for 7000FASST</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe wd7000</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver atoprobes the card and requires installed BIOS.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1317"
|
|
></A
|
|
>15.3.7. aha152x: SCSI low-level driver for Adaptec AHA152X/2825</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe aha152x</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver atoprobes the card and requires installed BIOS.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1324"
|
|
></A
|
|
>15.3.8. aha1542: SCSI low-level driver for Adaptec AHA1542</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe aha1542</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes the card at 0x330 and 0x334 only.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1331"
|
|
></A
|
|
>15.3.9. aha1740: SCSI low-level driver for Adaptec AHA1740 EISA</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe aha1740</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This driver autoprobes the card.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1337"
|
|
></A
|
|
>15.3.10. aic7xxx: SCSI low-level driver for Adaptec AHA274X/284X/294X</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe aic7xxx</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes the card and BIOS must be enabled.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1344"
|
|
></A
|
|
>15.3.11. advansys: SCSI low-level driver for AdvanSys/Connect.com</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe advansys asc_iopflag=1 asc_ioport=0x110,0x330 asc_dbglvl=1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Module Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>asc_iopflag</DT
|
|
><DD
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>enable port scanning</P
|
|
></DD
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
>disable port scanning</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DD
|
|
><DT
|
|
>asc_ioport</DT
|
|
><DD
|
|
><P
|
|
>I/O port addresses to scan for Advansys SCSI adapters</P
|
|
></DD
|
|
><DT
|
|
>asc_dbglvl</DT
|
|
><DD
|
|
><P
|
|
> debugging level:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
>Errors only</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>High level tracing</P
|
|
></DD
|
|
><DT
|
|
>2-N</DT
|
|
><DD
|
|
><P
|
|
>Verbose tracing</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>If you bind this driver into the base kernel, you can pass parameters
|
|
to it via the kernel boot parameters. See
|
|
<I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1385"
|
|
></A
|
|
>15.3.12. in2000: SCSI low-level driver for Always IN2000</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe in2000</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This driver autoprobes the card. No BIOS is required.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1391"
|
|
></A
|
|
>15.3.13. BusLogic: SCSI low-level driver for BusLogic</H3
|
|
><P
|
|
>The list of BusLogic cards this driver can drive is long. Read file
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>drivers/scsi/README.BusLogic</TT
|
|
> in the Linux source
|
|
tree to get the total picture.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe BusLogic</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>If you bind this driver into the base kernel, you can pass parameters
|
|
to it via the kernel boot parameters. See
|
|
<I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1400"
|
|
></A
|
|
>15.3.14. dtc: SCSI low-level driver for DTC3180/3280</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe dtc</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes the card.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1407"
|
|
></A
|
|
>15.3.15. eata: SCSI low-level driver for EATA ISA/EISA</H3
|
|
><P
|
|
>This driver handles DPT PM2011/021/012/022/122/322.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe eata</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1414"
|
|
></A
|
|
>15.3.16. eata_dma: SCSI low-level driver for EATA-DMA</H3
|
|
><P
|
|
>This driver handles DPT, NEC, AT&T, SNI, AST, Olivetti, and Alphatronix.</P
|
|
><P
|
|
>This driver handles DPT Smartcache, Smartcache III and SmartRAID.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe eata_dma</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>Autoprobe works in all configurations.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1422"
|
|
></A
|
|
>15.3.17. eata_pio: SCSI low-level driver for EATA-PIO</H3
|
|
><P
|
|
>This driver handles old DPT PM2001, PM2012A.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe eata_pio</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1428"
|
|
></A
|
|
>15.3.18. fdomain: SCSI low-level driver for Future Domain 16xx</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe fdomain</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This driver autoprobes the card and requires installed BIOS.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1434"
|
|
></A
|
|
>15.3.19. NCR5380: SCSI low-level driver for NCR5380/53c400</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe NCR5380 ncr_irq=xx ncr_addr=xx ncr_dma=xx ncr_5380=1 \
|
|
ncr_53c400=1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
>
|
|
for a port mapped NCR5380 board:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe g_NCR5380 ncr_irq=5 ncr_addr=0x350 ncr_5380=1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
>
|
|
for a memory mapped NCR53C400 board with interrupts disabled:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe g_NCR5380 ncr_irq=255 ncr_addr=0xc8000 ncr_53c400=1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>ncr_irq</DT
|
|
><DD
|
|
><P
|
|
> the irq the driver is to service. 255 means no or DMA interrupt.
|
|
254 to autoprobe for an IRQ line if overridden on the command line.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ncr_addr</DT
|
|
><DD
|
|
><P
|
|
> the I/O port address or memory mapped I/O address, whichever
|
|
is appropriate, that the driver is to drive
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ncr_dma</DT
|
|
><DD
|
|
><P
|
|
> the DMA channel the driver is to use
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ncr_5380</DT
|
|
><DD
|
|
><P
|
|
> 1 = set up for a NCR5380 board
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ncr_53c400</DT
|
|
><DD
|
|
><P
|
|
> 1 = set up for a NCR53C400 board
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>If you bind this driver into the base kernel, you can pass parameters
|
|
to it via the kernel boot parameters. See
|
|
<I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1464"
|
|
></A
|
|
>15.3.20. NCR53c406a: SCSI low-level driver for NCR53c406a</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe NCR53c406a</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1470"
|
|
></A
|
|
>15.3.21. 53c7,8xx.o: SCSI low-level driver for NCR53c7,8xx</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe 53c7,8xx</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes the card and requires installed BIOS.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1477"
|
|
></A
|
|
>15.3.22. ncr53c8xx: SCSI low-level driver for PCI-SCS NCR538xx family</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ncr53c8xx</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1482"
|
|
></A
|
|
>15.3.23. ppa: low-level SCSI driver for IOMEGA parallel port ZIP drive</H3
|
|
><P
|
|
>See the file <TT
|
|
CLASS="FILENAME"
|
|
>drivers/scsi/README.ppa</TT
|
|
> in the Linux
|
|
source tree for details.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ppa ppa_base=0x378 ppa_nybble=1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>ppa_base</DT
|
|
><DD
|
|
><P
|
|
> Base address of the PPA's I/O port. Default 0x378.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ppa_speed_high</DT
|
|
><DD
|
|
><P
|
|
> Delay used in data transfers, in microseconds. Default is 1.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ppa_speed_low</DT
|
|
><DD
|
|
><P
|
|
> Delay used in other operations, in microseconds. Default is 6.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ppa_nybble</DT
|
|
><DD
|
|
><P
|
|
> 1 = Use 4-bit mode. 0 = don't. Default is 0.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1506"
|
|
></A
|
|
>15.3.24. pas16: SCSI low-level driver for PAS16</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe pas16</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes the card. No BIOS is required.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1513"
|
|
></A
|
|
>15.3.25. qlogicfas: SCSI low-level driver for Qlogic FAS</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe qlogicfas</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1519"
|
|
></A
|
|
>15.3.26. qlogicisp: SCSI low-level driver for Qlogic ISP</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe qlogicisp</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>Requires firmware.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1526"
|
|
></A
|
|
>15.3.27. seagate: SCSI low-level driver for Seagate, Future Domain</H3
|
|
><P
|
|
>This driver is for Seagate ST-02 and Future Domain TMC-8xx.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe seagate</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes for address only. The IRQ is fixed at 5.
|
|
The driver requires installed BIOS.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1534"
|
|
></A
|
|
>15.3.28. t128: SCSI low-level driver for Trantor T128/T128F/T228</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe t128</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes the card. The driver requires installed BIOS.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1541"
|
|
></A
|
|
>15.3.29. u14-34f: SCSI low-level driver for UltraStor 14F/34F</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe u14-34f</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>This driver autoprobes the card, but <EM
|
|
>not</EM
|
|
> the
|
|
0x310 port. No BIOS is required.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1549"
|
|
></A
|
|
>15.3.30. ultrastor: low-level SCSI driver for UltraStor</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ultrastor</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>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 <I
|
|
CLASS="CITETITLE"
|
|
>BootPrompt-HOWTO</I
|
|
>.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN1555"
|
|
></A
|
|
>15.4. Network Device Drivers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1557"
|
|
></A
|
|
>15.4.1. bsd_comp: optional BSD compressor for PPP</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe bsd_comp</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>ppp</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1564"
|
|
></A
|
|
>15.4.2. slhc: SLHC compressor for PPP</H3
|
|
><P
|
|
>This module contains routines to compress and uncompress tcp packets
|
|
(for transmission over low speed serial lines). </P
|
|
><P
|
|
>These routines are required by PPP (also ISDN-PP) and SLIP protocols,
|
|
and are used by the LKMs that implement those protocols.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe slhc</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1571"
|
|
></A
|
|
>15.4.3. dummy: Dummy network interface driver</H3
|
|
><P
|
|
>This 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.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>You can have multiple dummy interfaces. They are named
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>dummy0</TT
|
|
>, <TT
|
|
CLASS="LITERAL"
|
|
>dummy1</TT
|
|
>,
|
|
etc.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe dummy</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1581"
|
|
></A
|
|
>15.4.4. eql: serial line load balancer</H3
|
|
><P
|
|
>If 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.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe eql</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1587"
|
|
></A
|
|
>15.4.5. dlci: frame relay DLCI driver</H3
|
|
><P
|
|
>This 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
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>Documentation/networking/framerelay.txt</TT
|
|
> in the
|
|
Linux source tree.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe dlci</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1594"
|
|
></A
|
|
>15.4.6. sdla: Sangoma S502A FRAD driver</H3
|
|
><P
|
|
>This 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
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>Documentation/networking/framerelay.txt</TT
|
|
> in the
|
|
Linux source tree.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sdla</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>dlci</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1603"
|
|
></A
|
|
>15.4.7. plip: PLIP network interface driver</H3
|
|
><P
|
|
>PLIP (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 <SPAN
|
|
CLASS="APPLICATION"
|
|
>winsock</SPAN
|
|
> or
|
|
NCSA's <B
|
|
CLASS="COMMAND"
|
|
>telnet</B
|
|
>.</P
|
|
><P
|
|
>See <I
|
|
CLASS="CITETITLE"
|
|
>PLIP-Install-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe plip io=0x378 irq=7</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Port address of parallel port driver is to drive.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ number of IRQ driver is to service. Default is IRQ 5 for
|
|
port at 0x3bc, IRQ 7 for port at 0x378, and IRQ 9 for port
|
|
at 0x278.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
|
|
If you don't specify the <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>io</I
|
|
></TT
|
|
> parameter, the
|
|
driver probes addresses 0x278, 0x378, and 0x3bc.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1623"
|
|
></A
|
|
>15.4.8. ppp: PPP network protocol driver</H3
|
|
><P
|
|
>PPP (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.</P
|
|
><P
|
|
>Along with this kernel driver, you need the user space program
|
|
<B
|
|
CLASS="COMMAND"
|
|
>pppd</B
|
|
> running.</P
|
|
><P
|
|
>See <I
|
|
CLASS="CITETITLE"
|
|
>PPP-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ppp</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>slhc</B
|
|
>.</P
|
|
><P
|
|
>The module also accesses serial devices, which are driven by the
|
|
<B
|
|
CLASS="COMMAND"
|
|
>serial</B
|
|
> module, so it depends on that module too.
|
|
This dependency is not detected by <B
|
|
CLASS="COMMAND"
|
|
>depmod</B
|
|
>, so you
|
|
either have to declare it manually or load <B
|
|
CLASS="COMMAND"
|
|
>serial</B
|
|
>
|
|
explicitly.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1639"
|
|
></A
|
|
>15.4.9. slip: SLIP network protocol driver</H3
|
|
><P
|
|
>SLIP (Serial Line Internet Protocol) is like PPP, only older and simpler.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe slip slip_maxdev=1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>slip_maxdev</DT
|
|
><DD
|
|
><P
|
|
> Maximum number of devices the driver may use at one time. Default
|
|
is 256.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>slhc</B
|
|
>.</P
|
|
><P
|
|
>The module also accesses serial devices, which are driven by the
|
|
<B
|
|
CLASS="COMMAND"
|
|
>serial</B
|
|
> module, so it depends on that module too.
|
|
This dependency is not detected by <B
|
|
CLASS="COMMAND"
|
|
>depmod</B
|
|
>, so you
|
|
either have to declare it manually or load <B
|
|
CLASS="COMMAND"
|
|
>serial</B
|
|
>
|
|
explicitly.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1656"
|
|
></A
|
|
>15.4.10. baycom: BAYCOM AX.25 amateur radio driver</H3
|
|
><P
|
|
>This 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. </P
|
|
><P
|
|
>For more information, see <A
|
|
HREF="http://www.baycom.org/~tom<"
|
|
TARGET="_top"
|
|
>http://www.baycom.org/~tom</A
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe baycom modem=1 iobase=0x3f8 irq=4 options=1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>major</DT
|
|
><DD
|
|
><P
|
|
> major number the driver should use; default 60
|
|
</P
|
|
></DD
|
|
><DT
|
|
>modem</DT
|
|
><DD
|
|
><P
|
|
>
|
|
modem type of the first channel (minor 0):
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>ser12</P
|
|
></DD
|
|
><DT
|
|
>2</DT
|
|
><DD
|
|
><P
|
|
>par96/par97</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
</P
|
|
></DD
|
|
><DT
|
|
>iobase</DT
|
|
><DD
|
|
><P
|
|
> base address of the port the driver is to drive. Common
|
|
values are for ser12 0x3f8, 0x2f8, 0x3e8, 0x2e8 and for
|
|
par96/par97 0x378, 0x278, 0x3bc.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. Common values are 3 and 4 for ser12
|
|
and 7 for for par96/par97.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>options</DT
|
|
><DD
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
>use hardware DCD</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>use software DCD</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1702"
|
|
></A
|
|
>15.4.11. strip: STRIP (Metricom starmode radio IP) driver</H3
|
|
><P
|
|
>STRIP is a radio protocol developed for the <A
|
|
HREF="http://mosquitonet.stanford.edu/"
|
|
TARGET="_top"
|
|
>MosquitoNet project</A
|
|
> 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.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe strip</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1709"
|
|
></A
|
|
>15.4.12. wavelan: WaveLAN driver</H3
|
|
><P
|
|
>WaveLAN card are for wireless ethernet-like networking. This driver
|
|
drives AT&T GIS and NCR WaveLAN cards.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe wavelan io=0x390 irq=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. Default is 0x390. You can set
|
|
a different address on the card, but it is not recommended.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. Default is 0. Any other value
|
|
is ignored and the card still services IRQ 0.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1724"
|
|
></A
|
|
>15.4.13. wic: WIC Radio IP bridge driver</H3
|
|
><P
|
|
>This is a driver for the WIC parallel port radio bridge.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe wic</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>It appears that devices <TT
|
|
CLASS="LITERAL"
|
|
>wic0</TT
|
|
>,
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>wic1</TT
|
|
> and <TT
|
|
CLASS="LITERAL"
|
|
>wic2</TT
|
|
> are directly
|
|
related to corresponding <TT
|
|
CLASS="LITERAL"
|
|
>lp</TT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>N</TT
|
|
>
|
|
ports.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1735"
|
|
></A
|
|
>15.4.14. scc: Z8530 SCC kiss emulation driver</H3
|
|
><P
|
|
>These 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 <TT
|
|
CLASS="FILENAME"
|
|
>Documentation/networking/z8530drv.txt</TT
|
|
> in the
|
|
Linux kernel source tree and <I
|
|
CLASS="CITETITLE"
|
|
>HAM-HOWTO</I
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe scc</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1743"
|
|
></A
|
|
>15.4.15. 8390: General NS8390 Ethernet driver core</H3
|
|
><P
|
|
>This 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 <B
|
|
CLASS="COMMAND"
|
|
>ne</B
|
|
> and <B
|
|
CLASS="COMMAND"
|
|
>3c503</B
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>
|
|
modprobe 8390</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1751"
|
|
></A
|
|
>15.4.16. ne: NE2000/NE1000 driver</H3
|
|
><P
|
|
>This 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.
|
|
|
|
This is an ISA bus card. For the PCI version, see the ne2k-pci module. </P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ne io=0x300 irq=11</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. This parameter is mandatory,
|
|
but you may specify 0x000 to have the driver autoprobe 0x300,
|
|
0x280, 0x320, 0x340, and 0x360.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. If you don't specify this, the
|
|
driver determines it by autoIRQ probing.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>bad</DT
|
|
><DD
|
|
><P
|
|
> The value 0xBAD means to assume the card is poorly designed in
|
|
that it does not acknowledge a reset or does not have a valid
|
|
0x57,0x57 signature. If you have such a card and do not specify
|
|
this option, the driver will not recognize it.
|
|
</P
|
|
><P
|
|
> With any other value, the option has no effect.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>You can repeat the options to specify additional cards. The
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>n</TT
|
|
>th occurence of an option applies to the
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>n</TT
|
|
>th card.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1776"
|
|
></A
|
|
>15.4.17. ne2k-pci: NE2000 PCI Driver</H3
|
|
><P
|
|
>This is a driver for the PCI version of the venerable NE2000 Ethernet
|
|
adapter, and all the generic Ethernet adapters that emulate this de
|
|
facto standard card.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ne io=0x300 irq=11</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>debug</DT
|
|
><DD
|
|
><P
|
|
> Level of debug messages. 0 means no messages. 1 is the default.
|
|
Higher numbers mean more debugging messages.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>options</DT
|
|
><DD
|
|
><P
|
|
> The value of this option determines what options are set in the
|
|
network adapter. Each bit of the value, expressed as a binary
|
|
number, controls one option. The only option defined is full
|
|
duplex, which is the 6th least significant bit. It is much
|
|
easier to use the <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>full_duplex</I
|
|
></TT
|
|
> option
|
|
instead.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>full_duplex</DT
|
|
><DD
|
|
><P
|
|
> A "1" value sets the adapter in full duplex mode.
|
|
A "0" value sets it in half duplex mode. If you include
|
|
the full duplex flag in the flags you specify with the
|
|
<TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>options</I
|
|
></TT
|
|
> parameter, the
|
|
<TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>full_duplex</I
|
|
></TT
|
|
> has no effect.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>You may repeat the <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>options</I
|
|
></TT
|
|
> and
|
|
<TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>full_duplex</I
|
|
></TT
|
|
> parameters once per network
|
|
adapter, for up to 8 network adapter. </P
|
|
><P
|
|
>This driver can drive the following chipsets:
|
|
<P
|
|
></P
|
|
><UL
|
|
><LI
|
|
><P
|
|
>RealTek RTL-8029</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Winbond 89C940</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Winbond W89C940F</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>KTI ET32P2</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>NetVin NV5000SC</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Via 86C926</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>SureCom NE34</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Holtek HT80232</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Holtek HT80229</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Compex RL2000</P
|
|
></LI
|
|
></UL
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1825"
|
|
></A
|
|
>15.4.18. 3c501: 3COM 3c501 Ethernet driver</H3
|
|
><P
|
|
>This is a driver for 3COM's 3c501 Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
|
|
modprobe 3c501 io=0x280 irq=5 </P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. Default is 5.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
If you don't specify an I/O port, the driver probes addresses 0x280
|
|
and 0x300.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1839"
|
|
></A
|
|
>15.4.19. 3c503: 3COM 3c503 driver</H3
|
|
><P
|
|
>This is a driver for 3COM's 3c503 Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe 3c503 io=0x300 irq=5 xcvr=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>xcvr</DT
|
|
><DD
|
|
><P
|
|
> Determines whether to use external tranceiver.
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
> no
|
|
</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
> yes
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
If you don't specify an I/O port, the driver probes addresses 0x300,
|
|
0x310, 0x330, 0x350, 0x250, 0x280, 0x2A0, and 0x2E0. </P
|
|
><P
|
|
>
|
|
This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1869"
|
|
></A
|
|
>15.4.20. 3c505: 3COM 3c505 driver</H3
|
|
><P
|
|
>This is a driver for 3COM's 3c505 Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe 3c503 io=0x300 irq=5 xcvr=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
|
|
If you don't specify an I/O port, the driver probes addresses 0x300,
|
|
0x280, and 0x310.</P
|
|
><P
|
|
>
|
|
This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1886"
|
|
></A
|
|
>15.4.21. 3c507: 3COM 3c507 driver</H3
|
|
><P
|
|
>This is a driver for 3COM's 3c507 Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe 3c503 io=0x300 irq=5 xcvr=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
|
|
If you don't specify an I/O port, the driver probes addresses 0x300,
|
|
0x320, 0x340, and 0x280.</P
|
|
><P
|
|
>
|
|
This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1903"
|
|
></A
|
|
>15.4.22. 3c509: 3COM 3c509/3c579 driver</H3
|
|
><P
|
|
>This is a driver for 3COM's 3c507 and 3c579 Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe 3c503 io=0x300 irq=5 xcvr=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>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. </P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1919"
|
|
></A
|
|
>15.4.23. 3c59x: 3COM 3c590 series "Vortex" driver</H3
|
|
><P
|
|
>This is a driver for the following 3COM Ethernet adapters:
|
|
<P
|
|
></P
|
|
><UL
|
|
><LI
|
|
><P
|
|
>3c590 Vortex 10Mbps. </P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>3c595 Vortex 100baseTX. </P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>3c595 Vortex 100baseT4. </P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>3c595 Vortex 100base-MII. </P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>EISA Vortex 3c597. </P
|
|
></LI
|
|
></UL
|
|
></P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe 3c59x debug=1 options=0,,12</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>debug</DT
|
|
><DD
|
|
><P
|
|
> A number selecting the level of debug messages.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>options</DT
|
|
><DD
|
|
><P
|
|
> This is a string of options numbers separated by commas.
|
|
There is one option number for each adapter that the driver
|
|
drives (for the case that you have multiple Ethernet adapters
|
|
in the system of types driven by this driver). The order of
|
|
the option numbers is the order of the cards assigned by the
|
|
PCI BIOS.
|
|
</P
|
|
><P
|
|
> Each number represents a binary value. In that value, the
|
|
lower 3 bits is the media type:
|
|
</P
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
>10baseT</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>10Mbs AUI</P
|
|
></DD
|
|
><DT
|
|
>2</DT
|
|
><DD
|
|
><P
|
|
>undefined</P
|
|
></DD
|
|
><DT
|
|
>3</DT
|
|
><DD
|
|
><P
|
|
>10base2 (BNC)</P
|
|
></DD
|
|
><DT
|
|
>4</DT
|
|
><DD
|
|
><P
|
|
>100base-TX</P
|
|
></DD
|
|
><DT
|
|
>5</DT
|
|
><DD
|
|
><P
|
|
>100base-FX</P
|
|
></DD
|
|
><DT
|
|
>6</DT
|
|
><DD
|
|
><P
|
|
>MII (not yet available)</P
|
|
></DD
|
|
><DT
|
|
>7</DT
|
|
><DD
|
|
><P
|
|
>Use default setting</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
><P
|
|
> The next bit (the "8" bit) is on for full duplex, off for half.
|
|
</P
|
|
><P
|
|
>
|
|
The next bit (the "16" bit) is on to enable bus-master, which is
|
|
for experimental use only.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>
|
|
Details of the device driver implementation are at the top of the
|
|
source file.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN1982"
|
|
></A
|
|
>15.4.24. wd: Western Digital/SMC WD80*3 driver</H3
|
|
><P
|
|
>This is a driver for the Western Digital WD80*3 Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe wd io=0x300 irq=5 mem=0x0D0000 mem_end=0x0D8000</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. </P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. </P
|
|
></DD
|
|
><DT
|
|
>mem</DT
|
|
><DD
|
|
><P
|
|
> Shared memory address</P
|
|
></DD
|
|
><DT
|
|
>mem_end</DT
|
|
><DD
|
|
><P
|
|
> End of shared memory (address of next byte after it).</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>If you don't specify an I/O port, the driver probes 0x300, 0x280, 0x380,
|
|
and 0x240.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>The driver depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2009"
|
|
></A
|
|
>15.4.25. smc-ultra: SMC Ultra/EtherEZ driver</H3
|
|
><P
|
|
>This is a driver for the SMC Ultra/EtherEZ Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe smc-ultra io=0x200 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x200, 0x220, 0x240, 0x280, 0x300, 0x340,
|
|
and 0x380.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. Default is the value read from the
|
|
adapter's EEPROM.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>This driver depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2026"
|
|
></A
|
|
>15.4.26. smc9194: SMC 9194 driver</H3
|
|
><P
|
|
>This is a driver for SMC's 9000 series of Ethernet cards.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe smc9194 io=0x200 irq=5 ifport=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x200, 0x220, etc. up through 0x3E0.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ifport</DT
|
|
><DD
|
|
><P
|
|
> Type of Ethernet.
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
>autodetect</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>TP</P
|
|
></DD
|
|
><DT
|
|
>2</DT
|
|
><DD
|
|
><P
|
|
>AUI (or 10base2)</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>The debug level is settable in the source code.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2059"
|
|
></A
|
|
>15.4.27. at1700: AT1700 driver</H3
|
|
><P
|
|
>This is a driver for the AT1700 Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe at1700 io=0x260 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x260, 0x280, 0x2A0, 0x240, 0x340, 0x320,
|
|
0x380, and 0x300.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2074"
|
|
></A
|
|
>15.4.28. e2100: Cabletron E21xx driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe e2100 io=0x300 irq=5 mem=0xd0000 xcvr=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x300, 0x280, 0x380, and 0x220.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the card is to generate and the driver is to service. (The
|
|
driver sets this value in the card).
|
|
</P
|
|
></DD
|
|
><DT
|
|
>mem</DT
|
|
><DD
|
|
><P
|
|
> shared memory address. Default is 0xd0000.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>xcvr</DT
|
|
><DD
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
> Don't select external transceiver
|
|
</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
> Select external transceiver
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2106"
|
|
></A
|
|
>15.4.29. depca: DEPCA, DE10x, DE200, DE201, DE202, DE422 driver</H3
|
|
><P
|
|
>This is a driver for the DEPCA, DE10x, DE200, DE201, DE202, and DE422
|
|
Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe depca io=0x200 irq=7</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x300, and 0x200 on an ISA machine or
|
|
0x0c00 on an EISA machine.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. Default is 7.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2121"
|
|
></A
|
|
>15.4.30. ewrk3: EtherWORKS 3 (DE203, DE204, DE205) driver</H3
|
|
><P
|
|
>This is a driver for the EtherWORKS 3 (DE203, D3204, and DE205)
|
|
Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ewrk3 io=0x300 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. Default is 0x300.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. Default is 5.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
><P
|
|
>On an EISA bus, this driver does EISA probing.</P
|
|
><P
|
|
>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.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2137"
|
|
></A
|
|
>15.4.31. eexpress: EtherExpress 16 driver</H3
|
|
><P
|
|
>This is a driver for the EtherExpress 16 Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe eexpress io=0x300 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x300, 0x270, 0x320, and 0x340.
|
|
1</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. The default is the value read
|
|
from the adapter's EEPROM.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2152"
|
|
></A
|
|
>15.4.32. eepro: EtherExpressPro driver</H3
|
|
><P
|
|
>This is a driver for the EtherExpressPro Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe eepro io=0x200 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x200, 0x240, 0x280, 0x2C0, 0x300, 0x320, 0x340,
|
|
and 0x360.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2167"
|
|
></A
|
|
>15.4.33. fmv18k: Fujitsu FMV-181/182/183/184 driver</H3
|
|
><P
|
|
>This is a driver for the Fujitsu FMV-181, FMV-182, FMV-183, FMV-183,
|
|
and FMV-184 Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe fmv18x io=0x220 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x220, 0x240, 0x260, 0x280, 0x2a0, 0x2c0,
|
|
0x300, and 0x340.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2182"
|
|
></A
|
|
>15.4.34. hp-plus: HP PCLAN+ (27247B and 27252A) driver</H3
|
|
><P
|
|
>This is a driver for HP's PCLAN+ (27247B and 27252A) Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe hp-plus io=0x200 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x200, 0x240, 0x280, 0x2C0, 0x300, 0x320, and
|
|
0x340.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. The default is the value the driver
|
|
reads from the adapter's configuration register.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2199"
|
|
></A
|
|
>15.4.35. hp: HP PCLAN (27245, 27xxx) driver</H3
|
|
><P
|
|
>This is a driver for HP's PCLAN (27245 and other 27xxx series) Ethernet
|
|
adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe hp io=0x300 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes 0x300, 0x320, 0x340, 0x280, 0x2C0, 0x200,
|
|
and 0x240.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. If you don't specify this, the
|
|
driver determines it by autoIRQ probing.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2216"
|
|
></A
|
|
>15.4.36. hp100: HP 10/100VG PCLAN (ISA, EISA, PCI) driver</H3
|
|
><P
|
|
>This is a driver for HP's 10/100VG PCLAN Ethernet adapters. It works with
|
|
the ISA, EISA, and PCI versions.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe hp100 hp100_port=0x100</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>hp100_port</DT
|
|
><DD
|
|
><P
|
|
> Base address of I/O ports on the card. If you don't specify this,
|
|
the driver autoprobes 0x100, 0x120, etc. up through 0x3E0 on an
|
|
ISA bus. It does EISA probing on an EISA bus.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2227"
|
|
></A
|
|
>15.4.37. eth16i: ICL EtherTeam 16i/32 driver</H3
|
|
><P
|
|
>This is a driver for ICL's EtherTeam 16i (eth16i) and 32i (eth32i)
|
|
Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe eth16i io=0x2a0 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> Address of I/O port on the card. If you don't specify this,
|
|
the adapter probes the following adddresses. For the eth16i
|
|
adapter: 0x260, 0x280, 0x2A0, 0x340, 0x320, 0x380, and 0x300.
|
|
For the eth32i: 0x1000, 0x2000, 0x3000, 0x4000, 0x5000,
|
|
0x6000, 0x7000, 0x8000, 0x9000, 0xA000, 0xB000, 0xC000,
|
|
0xD000, 0xE000, and 0xF000.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. If you don't specify this, the
|
|
driver determines it by autoIRQ probing.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2242"
|
|
></A
|
|
>15.4.38. ni52: NI5210 driver</H3
|
|
><P
|
|
>This is a driver for the NI5210 Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ni52 io=0x360 irq=9 memstart=0xd0000 memend=0xd4000</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2247"
|
|
></A
|
|
>15.4.39. ac3200: Ansel Communications EISA 3200 driver</H3
|
|
><P
|
|
>This is a driver for the Ansel Communications EISA 3200 Ethernet
|
|
adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ac3200</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>8390</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2254"
|
|
></A
|
|
>15.4.40. apricot: Apricot Xen-II on board ethernet driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe apricot io=0x300 irq=10</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port on card.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ that driver is to service.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2268"
|
|
></A
|
|
>15.4.41. de4x5: DE425, DE434, DE435, DE450, DE500 driver</H3
|
|
><P
|
|
>This is a driver for the DE425, DE434, DE435, DE450, and DE500
|
|
Ethernet adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>
|
|
modprobe de4x5 io=0x000b irq=10 is_not_dec=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>is_not_dec</DT
|
|
><DD
|
|
><P
|
|
> For a non-DEC card using the DEC 21040, 21041, or 21140 chip,
|
|
set this to 1.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2287"
|
|
></A
|
|
>15.4.42. tulip: DECchip Tulip (dc21x4x) PCI driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe tulip</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Read <TT
|
|
CLASS="FILENAME"
|
|
>Documentation/networking/tulip.txt</TT
|
|
> in the Linux
|
|
source tree.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2293"
|
|
></A
|
|
>15.4.43. dgrs: Digi Intl RightSwitch SE-X driver</H3
|
|
><P
|
|
>This 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.</P
|
|
><P
|
|
>There is a tool for setting up input and output packet filters on each
|
|
port, called <B
|
|
CLASS="COMMAND"
|
|
>dgrsfilt</B
|
|
>.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>There is also a companion management tool, called
|
|
<B
|
|
CLASS="COMMAND"
|
|
>xrightswitch</B
|
|
>.</P
|
|
><P
|
|
>Examples:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe dgrs debug=1 dma=0 spantree=0 hashexpire=300 ipaddr=199,86,8,221
|
|
modprobe ipxnet=111</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>debug</DT
|
|
><DD
|
|
><P
|
|
> Level of debugging messages to print
|
|
</P
|
|
></DD
|
|
><DT
|
|
>dma</DT
|
|
><DD
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
> Disable DMA on PCI card
|
|
</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
> Enable DMA on PCI card
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DD
|
|
><DT
|
|
>spantree</DT
|
|
><DD
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
> Disable IEEE spanning tree
|
|
</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
> Enable IEEE spanning tree
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DD
|
|
><DT
|
|
>hashexpire</DT
|
|
><DD
|
|
><P
|
|
> Change address aging time, in seconds. Defaults is 300.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ipaddr</DT
|
|
><DD
|
|
><P
|
|
> SNMP agent IP address. Value is IP address in dotted decimal
|
|
notation, except with commas instead of periods.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>ipxnet</DT
|
|
><DD
|
|
><P
|
|
> SNMP agent IPX network number
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2345"
|
|
></A
|
|
>15.4.44. de600: D-Link DE600 pocket adapter driver</H3
|
|
><P
|
|
>This is a driver for the D-Link DE600 pocket Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe de600 de600_debug=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>de600_debug</DT
|
|
><DD
|
|
><P
|
|
> The driver expects the adapter to be at port 0x378 and
|
|
generate IRQ 7. This is the same as the DOS
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>lpt1</TT
|
|
> device. These are compile time
|
|
options.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2357"
|
|
></A
|
|
>15.4.45. de620: D-Link DE620 pocket adapter driver</H3
|
|
><P
|
|
>This is a driver for the D-Link DE620 pocket Ethernet adapter.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe de620 bnc=0 utp=0 io=0x378 irq=7</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>bnc</DT
|
|
><DD
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
> Network is 10Base2
|
|
</P
|
|
></DD
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
> Network is not 10Base2
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DD
|
|
><DT
|
|
>utp</DT
|
|
><DD
|
|
><P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
> Network is 10BaseT
|
|
</P
|
|
></DD
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
> Network is not 10BaseT
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></DD
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> I/O port address of port driver is to drive. Default is 0x378.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ driver is to service. Default is 7.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>You can't specify both <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>bnc=1</I
|
|
></TT
|
|
> and
|
|
<TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>utp=1</I
|
|
></TT
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2399"
|
|
></A
|
|
>15.4.46. ibmtr: Tropic chipset based token ring adapter driver</H3
|
|
><P
|
|
>Example:</P
|
|
><P
|
|
><TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ibmtr io=0xa20 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> I/O port address of port driver is to drive. Default is 0xa20.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ driver is to service. By default, the driver determines the
|
|
IRQ by autoIRQ probing.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2414"
|
|
></A
|
|
>15.4.47. arcnet: ARCnet driver</H3
|
|
><P
|
|
>Read The Fine Information in
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>Documentation/networking/arcnet.txt</TT
|
|
> in the Linux
|
|
source tree. Also Arcnet hardware information
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>arcnet-hardware.txt</TT
|
|
> is found in same place.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe arcnet io=0x300 irq=2 shmem=0xd0000 device=arc1</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> I/O port address of port driver is to drive. If you don't
|
|
specify this, the driver probes addresses 0x300, 0x2E0, 0x2F0,
|
|
0x2D0, 0x200, 0x210, 0x220, 0x230, 0x240, 0x250, 0x260, 0x270,
|
|
0x280, 0x290, 0x2A0, 0x2B0, 0x2C0, 0x310, 0x320, 0x330, 0x340,
|
|
0x350, 0x360, 0x370, 0x380, 0x390, 0x3A0, 0x3E0, and 0x3F0.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ driver is to service. By default, the driver determines the
|
|
IRQ by autoIRQ probing.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>device</DT
|
|
><DD
|
|
><P
|
|
> device name.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2435"
|
|
></A
|
|
>15.4.48. isdn: basic ISDN functions</H3
|
|
><P
|
|
>This module provides ISDN functions used by ISDN adapter drivers.</P
|
|
><P
|
|
>Setting up ISDN networking is a complicated task. Read documentation
|
|
found in <TT
|
|
CLASS="FILENAME"
|
|
>Documentation/isdn</TT
|
|
> in the Linux source
|
|
tree.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe isdn</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>slhc</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2445"
|
|
></A
|
|
>15.4.49. icn: ICN 2B and 4B driver</H3
|
|
><P
|
|
>This is a driver for the ICN 2B and ICN 4B ISDN adapters.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe icn portbase=0x320 membase=0xd0000 icn_id=idstring icn_id2=idstring2</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>portbase</DT
|
|
><DD
|
|
><P
|
|
> Address of the base I/O port on the adapter. Defaults is 0x320.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>membase</DT
|
|
><DD
|
|
><P
|
|
> Address of shared memory. Default is 0xd0000.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>icn_id</DT
|
|
><DD
|
|
><P
|
|
> idstring for the first adapter. Must start with a character!
|
|
This parameter is required.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>icn_id2</DT
|
|
><DD
|
|
><P
|
|
> idstring for the second adapter. Must start with a character!
|
|
This parameter is required with the double card.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>isdn</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2470"
|
|
></A
|
|
>15.4.50. pcbit: PCBIT-D driver</H3
|
|
><P
|
|
>This is a driver for the PCBIT-D ISDN adapter driver.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe pcbit mem=0xd0000 irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>mem</DT
|
|
><DD
|
|
><P
|
|
> Shared memory address. Default is 0xd0000
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ the driver is to service. Default is 5.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>This module depend on module <B
|
|
CLASS="COMMAND"
|
|
>isdn</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2487"
|
|
></A
|
|
>15.4.51. teles: Teles/NICCY1016PC/Creatix driver</H3
|
|
><P
|
|
>This is a driver for the Teles/NICCY1016PC/Creatix ISDN adapter.
|
|
It can drive up to 16 cards.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe teles io=0xd0000,15,0xd80,2 teles_id=idstring</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>io</DT
|
|
><DD
|
|
><P
|
|
> This is a whole collection of parameters in one. It's syntax is
|
|
|
|
<TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>io=</I
|
|
></TT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>card1options</TT
|
|
>
|
|
[<TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>,</I
|
|
></TT
|
|
><TT
|
|
CLASS="VARNAME"
|
|
>card2options</TT
|
|
>
|
|
<TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>,</I
|
|
></TT
|
|
>...]
|
|
|
|
where <TT
|
|
CLASS="VARNAME"
|
|
>card1options</TT
|
|
> is a set of options
|
|
for the first card, etc.
|
|
</P
|
|
><P
|
|
>
|
|
The syntax of <TT
|
|
CLASS="VARNAME"
|
|
>card1options</TT
|
|
>, etc. is
|
|
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>sharedmem</TT
|
|
><TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>,</I
|
|
></TT
|
|
>
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>irq</TT
|
|
><TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>,</I
|
|
></TT
|
|
>
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>portbase</TT
|
|
><TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>,</I
|
|
></TT
|
|
>
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>dprotocol</TT
|
|
>
|
|
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>sharedmem</DT
|
|
><DD
|
|
><P
|
|
> Address of shared memory. Default 0xd0000
|
|
</P
|
|
></DD
|
|
><DT
|
|
>irq</DT
|
|
><DD
|
|
><P
|
|
> IRQ driver is to service.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>portbase</DT
|
|
><DD
|
|
><P
|
|
> Address of base I/O port.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>dprotocol</DT
|
|
><DD
|
|
><P
|
|
> D-channel protocol of the card
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>1TR6</P
|
|
></DD
|
|
><DT
|
|
>2</DT
|
|
><DD
|
|
><P
|
|
> EDSS1. This is the default.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
>
|
|
</P
|
|
></DD
|
|
><DT
|
|
>teles_id</DT
|
|
><DD
|
|
><P
|
|
> Driver ID for accessing with utilities and identification
|
|
when using a line monitor. Value must start with a
|
|
character! Default: none.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>The driver determines the type of card from the port, irq and shared
|
|
memory address:
|
|
<P
|
|
></P
|
|
><UL
|
|
><LI
|
|
><P
|
|
>port == 0, shared memory != 0 -> Teles S0-8
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>port != 0, shared memory != 0 -> Teles S0-16.0
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>port != 0, shared memory == 0 -> Teles S0-16.3
|
|
</P
|
|
></LI
|
|
></UL
|
|
></P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>isdn</B
|
|
>.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2553"
|
|
></A
|
|
>15.5. CDROM Device Drivers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2555"
|
|
></A
|
|
>15.5.1. aztcd: Aztech/Orchid/Okano/Wearnes/TXC/CDROM driver</H3
|
|
><P
|
|
>This is a driver for the Aztech, Orchid, Okano, Wearnes, TXC, and
|
|
CDROM devices (which have special non-SCSI non-ATA interfaces).</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe aztcd aztcd=0x340</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>aztcd</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>Read <TT
|
|
CLASS="FILENAME"
|
|
>Documentation/cdrom/aztcd</TT
|
|
> in the Linux
|
|
source tree for full information.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2568"
|
|
></A
|
|
>15.5.2. gscd: Goldstar R420 CDROM driver</H3
|
|
><P
|
|
>This is a driver for the Goldstar R420 CDROM drive, which does not use
|
|
either an ATA or SCSI interface.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe gscd gscd=0x340</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>gscd</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port. Default is 0x340, which will
|
|
work for most applications. You select the address of the
|
|
drive with the PN801-1 through PN801-4 jumpers on the
|
|
Goldstar Interface Card. Appropriate settings are: 0x300,
|
|
0x310, 0x320, 0x330, 0x340, 0x350, 0x360, 0x370, 0x380,
|
|
0x390, 0x3A0, 0x3B0, 0x3C0, 0x3D0, 0x3E0, and 0x3F0.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2579"
|
|
></A
|
|
>15.5.3. sbpcd: Sound Blaster CDROM driver</H3
|
|
><P
|
|
>This is a driver for the Matsushita, Panasonic, Creative, Longshine, and
|
|
TEAC CDROM drives that don't attach via ATA or SCSI.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sbpcd sbpcd=0x340</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>sbpcd</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>An additional parameter is an SBPRO setting, as described in
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>Documentation/cdrom/sbpcd</TT
|
|
> in the Linux source tree.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2592"
|
|
></A
|
|
>15.5.4. mcd: Mitsumi CDROM driver</H3
|
|
><P
|
|
>This is a driver for Mitsumi CDROM drives that don't attach via ATA
|
|
or SCSI. It does not handle XA or multisession.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe mcd mcd=0x300,11,0x304,5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>mcd</DT
|
|
><DD
|
|
><P
|
|
> This is a comma separated list of i/o base addresses and IRQs,
|
|
in pairs.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2603"
|
|
></A
|
|
>15.5.5. mcdx: Mitsumi XA/MultiSession driver</H3
|
|
><P
|
|
>This driver is like <B
|
|
CLASS="COMMAND"
|
|
>mcd</B
|
|
>, only it has XA and
|
|
multisession functions.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe mcdx mcdx=0x300,11,0x304,5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2609"
|
|
></A
|
|
>15.5.6. optcd: Optics Storage DOLPHIN 8000AT CDROM driver</H3
|
|
><P
|
|
>This 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.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe optcd optcd=0x340</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>optcd</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2620"
|
|
></A
|
|
>15.5.7. cm206: Philips/LMS CM206 CDROM driver</H3
|
|
><P
|
|
>This is the driver for the Philips/LMS cm206 CDROM drive in
|
|
combination with the cm260 host adapter card.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe cm206 cm206=0x300,11</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>cm206</DT
|
|
><DD
|
|
><P
|
|
> The address of the base I/O port the driver is to drive and
|
|
the IRQ the driver is to service, separated by a comma. It doesn't
|
|
matter what order you put them in, and you may specify just one,
|
|
in which case the other defaults.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2631"
|
|
></A
|
|
>15.5.8. sjcd: Sanyo CDR-H94A CDROM driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sjcd sjcd_base=0x340</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>sjcd_base</DT
|
|
><DD
|
|
><P
|
|
> address of the base I/O port the driver is to drive.
|
|
Default is 0x340.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>The driver uses no IRQ and no DMA channel. </P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2642"
|
|
></A
|
|
>15.5.9. isp16: ISP16/MAD16/Mozart soft configurable cdrom driver</H3
|
|
><P
|
|
>This is a driver for the ISP16 or MAD16 or Mozart soft configurable
|
|
cdrom interface.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe isp16 isp16_cdrom_base=0x340 isp16_cdrom_irq=3
|
|
isp16_cdrom_dma=0 isp16_cdrom_type=Sanyo</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>isp16_cdrom_base</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port the driver is to drive. Valid values
|
|
are 0x340, 0x320, 0x330, and 0x360.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>isp16_cdrom_irq</DT
|
|
><DD
|
|
><P
|
|
>
|
|
IRQ the driver is to service. Valid values are 0, 3, 5, 7, 9, 10,
|
|
and 11.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>isp16_cdrom_dma</DT
|
|
><DD
|
|
><P
|
|
> DMA channel the driver is to use with the device. Valid
|
|
values are 0, 3, 5, 6, and 7.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>isp16_cdrom_type</DT
|
|
><DD
|
|
><P
|
|
>
|
|
Type of device being driven. Valid values are
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>noisp16</TT
|
|
>, <TT
|
|
CLASS="LITERAL"
|
|
>Sanyo</TT
|
|
>,
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>Panasonic</TT
|
|
>, <TT
|
|
CLASS="LITERAL"
|
|
>Sony</TT
|
|
> and
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>Mitsumi</TT
|
|
>. Note that these values are
|
|
case sensitive.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2670"
|
|
></A
|
|
>15.5.10. cdu31a: Sony CDU31A/CDU33A CDROM driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe cdu31a cdu31a_port=0x340 cdu31a_irq=5</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>cdu31a_port</DT
|
|
><DD
|
|
><P
|
|
> address of base I/O port the driver is to drive. This parameter
|
|
is mandatory.
|
|
</P
|
|
></DD
|
|
><DT
|
|
>cdu31a_irq</DT
|
|
><DD
|
|
><P
|
|
>
|
|
IRQ the driver is to service. If you don't specify this,
|
|
the driver does not use interrupts.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2684"
|
|
></A
|
|
>15.5.11. sonycd535: Sony CDU535 CDROM driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sonycd535 sonycd535=0x340</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Parameters:
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>sonycd535</DT
|
|
><DD
|
|
><P
|
|
> address of the base I/O port the driver is to drive.
|
|
</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2694"
|
|
></A
|
|
>15.6. Filesystem Drivers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2696"
|
|
></A
|
|
>15.6.1. minix: Minix filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe minix</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2701"
|
|
></A
|
|
>15.6.2. ext: "Extended" filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ext</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2706"
|
|
></A
|
|
>15.6.3. ext2: "Second extended" filessystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ext2</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2711"
|
|
></A
|
|
>15.6.4. xiafs: xiafs filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe xiafs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2716"
|
|
></A
|
|
>15.6.5. fat: DOS FAT filesystem functions</H3
|
|
><P
|
|
>This module provides services for use by the MSDOS and VFAT
|
|
filesystem drivers.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe fat</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2722"
|
|
></A
|
|
>15.6.6. msdos: MSDOS filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe msdos</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on the module <B
|
|
CLASS="COMMAND"
|
|
>fat</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2729"
|
|
></A
|
|
>15.6.7. vfat: VFAT (Windows-95) filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe vfat</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>fat</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2736"
|
|
></A
|
|
>15.6.8. umsdos: UMSDOS filesystem driver</H3
|
|
><P
|
|
>This is a driver for the UMSDOS filesystem type, which is a unix style
|
|
filesystem built on top of an MSDOS FAT filesystem.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe vfat</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on the <B
|
|
CLASS="COMMAND"
|
|
>fat</B
|
|
> and
|
|
<B
|
|
CLASS="COMMAND"
|
|
>msdos</B
|
|
> modules.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2745"
|
|
></A
|
|
>15.6.9. nfs: NFS filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe nfs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2750"
|
|
></A
|
|
>15.6.10. smbfs: SMB filesystem driver</H3
|
|
><P
|
|
>SMBFS 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 <A
|
|
HREF="ftp://nimbus.anu.edu.au/pub/tridge/samba/"
|
|
TARGET="_top"
|
|
>ftp://nimbus.anu.edu.au/pub/tridge/samba/</A
|
|
> 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.</P
|
|
><P
|
|
>To use SMBFS, you need a special mount program, which can be found
|
|
in the ksmbfs package, found on
|
|
<A
|
|
HREF="ftp://ibiblio.org/pub/Linux/system/Filesystems/smbfs"
|
|
TARGET="_top"
|
|
>ftp://ibiblio.org/pub/Linux/system/Filesystems/smbfs</A
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe smbfs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2759"
|
|
></A
|
|
>15.6.11. ncpfs: NCP (Netware) filesystem driver</H3
|
|
><P
|
|
>NCPFS 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 <SPAN
|
|
CLASS="APPLICATION"
|
|
>ncpfs</SPAN
|
|
> package.
|
|
Homesite for <SPAN
|
|
CLASS="APPLICATION"
|
|
>ncpfs</SPAN
|
|
> is
|
|
<A
|
|
HREF="ftp.gwdg.de/pub/linux/misc/ncpfs"
|
|
TARGET="_top"
|
|
>ftp.gwdg.de/pub/linux/misc/ncpfs</A
|
|
>, but Ibiblio and its many
|
|
mirrors will have it as well.</P
|
|
><P
|
|
>Related products are <SPAN
|
|
CLASS="APPLICATION"
|
|
>Linware</SPAN
|
|
> and
|
|
<SPAN
|
|
CLASS="APPLICATION"
|
|
>Mars_nwe</SPAN
|
|
>, which will give Linux partial
|
|
NetWare Server functionality.</P
|
|
><P
|
|
><SPAN
|
|
CLASS="APPLICATION"
|
|
>Mars_nwe</SPAN
|
|
> can be found on <A
|
|
HREF="ftp.gwdg.de/pub/linux/misc/ncpfs"
|
|
TARGET="_top"
|
|
>ftp.gwdg.de/pub/linux/misc/ncpfs</A
|
|
>.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ncpfs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>ipx</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2776"
|
|
></A
|
|
>15.6.12. isofs: ISO 9660 (CDROM) filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe isofs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2781"
|
|
></A
|
|
>15.6.13. hpfs: OS/2 HPFS filesystem driver</H3
|
|
><P
|
|
>This filesystem driver for OS/2's HPFS filesystem provides only read-only
|
|
access.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe hpfs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2787"
|
|
></A
|
|
>15.6.14. sysv: System V and Coherent filesystem driver</H3
|
|
><P
|
|
>This is the implementation of the SystemV/Coherent filesystem type for
|
|
Linux.</P
|
|
><P
|
|
>It implements all of
|
|
<P
|
|
></P
|
|
><UL
|
|
><LI
|
|
><P
|
|
>Xenix FS</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>SystemV/386 FS</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Coherent FS</P
|
|
></LI
|
|
></UL
|
|
></P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sysv</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2801"
|
|
></A
|
|
>15.6.15. affs: Amiga FFS filesystem driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe affs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2806"
|
|
></A
|
|
>15.6.16. ufs: UFS filesystem driver</H3
|
|
><P
|
|
>Apparently for mounting disks with FreeBSD and/or Sun partitions. No
|
|
documentation exists, apart from The Source.</P
|
|
><P
|
|
>This filesystem driver provides only read-only access.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ufs</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2813"
|
|
></A
|
|
>15.7. Miscellaneous Device Driver</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2815"
|
|
></A
|
|
>15.7.1. misc: device driver for "miscellaneous" character devices</H3
|
|
><P
|
|
>A 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.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe misc</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2821"
|
|
></A
|
|
>15.8. Serial Device Drivers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2823"
|
|
></A
|
|
>15.8.1. serial: serial communication port (UART) device driver</H3
|
|
><P
|
|
>This driver drives conventional serial ports (UARTs), but not some
|
|
of the specialized high performance multi-port devices.</P
|
|
><P
|
|
>NOTE: <B
|
|
CLASS="COMMAND"
|
|
>serial</B
|
|
> is required by other modules, such as
|
|
<B
|
|
CLASS="COMMAND"
|
|
>ppp</B
|
|
> and <B
|
|
CLASS="COMMAND"
|
|
>slip</B
|
|
>. Also it is
|
|
required by serial mice and accordingly by
|
|
<SPAN
|
|
CLASS="APPLICATION"
|
|
>gpm</SPAN
|
|
>. However this isn't the regular kind
|
|
of dependency that is detected by module handling tools, so you must
|
|
load <B
|
|
CLASS="COMMAND"
|
|
>serial</B
|
|
> manually.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe serial</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2835"
|
|
></A
|
|
>15.8.2. cyclades: Cyclades async mux device driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe cyclades</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>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
|
|
<SPAN
|
|
CLASS="APPLICATION"
|
|
>stlload</SPAN
|
|
>. Compile this program where ever
|
|
you dropped the package files, by typing <B
|
|
CLASS="COMMAND"
|
|
>make</B
|
|
>. In
|
|
its simplest form you can then type <B
|
|
CLASS="COMMAND"
|
|
>stlload</B
|
|
> 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:</P
|
|
><P
|
|
>Read the information in the file
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>Documentation/stallion.txt</TT
|
|
> in the Linux source
|
|
tree.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2846"
|
|
></A
|
|
>15.8.3. stallion: Stallion EasyIO or EC8/32 device driver</H3
|
|
><P
|
|
>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 <SPAN
|
|
CLASS="APPLICATION"
|
|
>stlload</SPAN
|
|
>.</P
|
|
><P
|
|
>Read the information in the file
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>Documentation/stallion.txt</TT
|
|
> in the Linux source
|
|
tree.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe stallion</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2855"
|
|
></A
|
|
>15.8.4. istallion: Stallion EC8/64, ONboard, Brumby device driver</H3
|
|
><P
|
|
>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 <SPAN
|
|
CLASS="APPLICATION"
|
|
>stlload</SPAN
|
|
>.</P
|
|
><P
|
|
>Read the information at /usr/src/linux/drivers/char/README.stallion.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe istallion</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2863"
|
|
></A
|
|
>15.8.5. riscom8: SDL RISCom/8 card device driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe riscom8 iobase=0xXXX iobase1=0xXXX iobase2=...</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>This driver can drive up to 4 boards at time.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2868"
|
|
></A
|
|
>15.9. Parallel Device Drivers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2870"
|
|
></A
|
|
>15.9.1. lp: Parallel printer device driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe lp.o io=0x378 irq=0</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>This driver probes ports 0x278, 0x378, and 0x3bc.</P
|
|
><P
|
|
>Note: loading <B
|
|
CLASS="COMMAND"
|
|
>lp</B
|
|
> without any parameters will
|
|
grab all parallel ports.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2877"
|
|
></A
|
|
>15.10. Bus Mouse Device Drivers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2879"
|
|
></A
|
|
>15.10.1. atixlmouse: ATIXL busmouse driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe atixlmouse</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>misc</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2886"
|
|
></A
|
|
>15.10.2. busmouse: Logitech busmouse driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe busmouse</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>misc</B
|
|
>.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2893"
|
|
></A
|
|
>15.10.3. msbusmouse: Microsoft busmouse driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe msbusmouse</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>misc</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2900"
|
|
></A
|
|
>15.10.4. psaux: PS/2 mouse (aka "auxiliary device") driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe psaux</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>misc</B
|
|
>.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2907"
|
|
></A
|
|
>15.11. Tape Device Drivers</H2
|
|
><P
|
|
>For SCSI tape device drivers, see <A
|
|
HREF="individual.html#SCSI"
|
|
>Section 15.3</A
|
|
>. There are no
|
|
LKMs for QIC-02 tape devices, but there is a device driver you can
|
|
bind into the base kernel.</P
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2911"
|
|
></A
|
|
>15.11.1. ftape: floppy tape (QIC-80/Travan) device driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe ftape tracing=3</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Optional parameter <TT
|
|
CLASS="PARAMETER"
|
|
><I
|
|
>tracing</I
|
|
></TT
|
|
> can take following
|
|
values
|
|
|
|
<P
|
|
></P
|
|
><DIV
|
|
CLASS="VARIABLELIST"
|
|
><DL
|
|
><DT
|
|
>0</DT
|
|
><DD
|
|
><P
|
|
>bugs</P
|
|
></DD
|
|
><DT
|
|
>1</DT
|
|
><DD
|
|
><P
|
|
>+ errors</P
|
|
></DD
|
|
><DT
|
|
>2</DT
|
|
><DD
|
|
><P
|
|
>+ warnings</P
|
|
></DD
|
|
><DT
|
|
>3</DT
|
|
><DD
|
|
><P
|
|
>+ information</P
|
|
></DD
|
|
><DT
|
|
>4</DT
|
|
><DD
|
|
><P
|
|
>+ more information</P
|
|
></DD
|
|
><DT
|
|
>5</DT
|
|
><DD
|
|
><P
|
|
>+ program flow</P
|
|
></DD
|
|
><DT
|
|
>6</DT
|
|
><DD
|
|
><P
|
|
>+ fdc/dma info</P
|
|
></DD
|
|
><DT
|
|
>7</DT
|
|
><DD
|
|
><P
|
|
>+ data flow</P
|
|
></DD
|
|
><DT
|
|
>8</DT
|
|
><DD
|
|
><P
|
|
>+ everything else</P
|
|
></DD
|
|
></DL
|
|
></DIV
|
|
></P
|
|
><P
|
|
>The default is 3.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2955"
|
|
></A
|
|
>15.12. Watchdog Timers</H2
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2957"
|
|
></A
|
|
>15.12.1. WDT: WDT Watchdog timer device driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe wdt</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>The device address is hardcoded as 0x240. The IRQ is hardcoded as 14.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>misc</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2965"
|
|
></A
|
|
>15.12.2. softdog: Software Watchdog Timer</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> modprobe softdog</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>misc</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN2972"
|
|
></A
|
|
>15.12.3. pcwd: Berkshire Products PC Watchdog Driver</H3
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe pcwd</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>There are no module parameters.</P
|
|
><P
|
|
>This module depends on module <B
|
|
CLASS="COMMAND"
|
|
>misc</B
|
|
>.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN2979"
|
|
></A
|
|
>15.13. Sound Device Drivers</H2
|
|
><P
|
|
>Configuring sound is a complex task. Read the files in
|
|
directory <TT
|
|
CLASS="FILENAME"
|
|
>Documention/sound</TT
|
|
> in
|
|
the Linux source tree.</P
|
|
><P
|
|
>Example:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>modprobe sound</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></P
|
|
><P
|
|
>Option: dma_buffsize=32768</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x973.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x2986.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Related Documentation</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Maintenance Of This Document</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |