home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Chip 2000 May
/
Chip_2000-05_cd2.bin
/
docu
/
ascii
/
suselxen
/
slxen-14.txt
< prev
next >
Wrap
Text File
|
2000-03-11
|
62KB
|
1,700 lines
Chapter 14
Kernel Parameters
14.1 Drivers in the Kernel
There is a wide variety of PC hardware components. In order to be able to use
this hardware properly, you need a "driver" with which the operating system
(in Linux, the "kernel"), can access this hardware. In general there are two
ways of integrating drivers into your system:
* The drivers can be compiled directly into the kernel. Such a kernel ("in
one piece") is referred to as a monolithic kernel.
Some drivers are only available in this form, justifying the need for mono-
lithic kernels.
* Drivers can be loaded on demand into the kernel, which is then referred
to as a modularised kernel. This has the advantage that only those drivers
are loaded which really are needed, and the kernel thus contains no un-
necessary ballast.
Our SuSE boot disk kernel makes use of modules to support most hard-
ware configurations.
Some drivers do not yet exist as modules.
Regardless of whether the drivers are compiled directly into the kernel or are
loaded as modules, it is still possible that a hardware component may not be
recognized by the kernel. If this is the case, you have the option of specifying
component attributes more exactly.
For monolithic kernels these parameters must be given at the boot prompt or
by means of a boot loader.1 Modular drivers get their parameters via insmod
or modprobe, which load the module itself simultaneously.
Unfortunately, the format for LILO parameters is different from that for pa-
rameters for insmod and modprobe. For this reason they are divided into two
different groups in the following pages. A few modules now have unified
parameters (e. g., CD-ROM drives), so that the same parameters can be given
whether you are using modules or the LILO prompt.
1 For this reason the parameters are also called LILO parameters, named after the time-honoured
loader for X86 architectures
325
14. Kernel Parameters
14.2 Some Tips
Before we present the list of parameters, here are some hints on recognizing
hardware, adding parameters and booting with the SuSE boot disk:
* Most drivers can do an autoprobing, e. g., test different standard addresses
where this hardware can usually be found. While autoprobing, a driver
might initialize an address that does not belong to it. This can cause the
machine to hang.
* Some modules can be loaded successfully, even if their hardware is not
installed. This applies mainly to 3Com network card drivers. You should
try autoprobing first. Unused drivers can be easily removed. Hardware
that is not automatically recognized must then be started using the appro-
priate parameters.
* Finally, there are some hardware components that have more than one
driver (e. g., NCR 53C810, Ultrastor). As far as we know, there is no sig-
nificant difference between the two Ultrastor drivers. The BSD driver for
NCR53C810 also supports other NCR53C8xx products (e. g., 53C875),
whereas the old NCR driver is the only one that recognizes CD writers.
Use the one that suits your needs.
* If you have just booted, the American keyboard will still be active. If your
keyboard has an alternate layout, some keys may be slightly different. For
example, if you have a German keyboard, the the = sign will be ' on
the keyboard. z and y are swapped round. To compare, take a look at
Figure 14.1.
Figure 14.1: The layout of a US keyboard
14.3 The Parameters
14.3.1 Notations and Meanings
Below you will see an alphabetical list of kernel parameters and the corre-
sponding devices. The following parameters always have the same meaning:
<addr> hexadecimal port address, (e. g., 0x300)
Table 14.1: continued overleaf. . . ...
326
14.3. The Parameters
<irq> interrupt the device will use (e. g., 7)
<dma> DMA channel of the device (e. g., 1)
<Start address>,
<End address> hexadecimal memory allocation for shared memory
Table 14.1: Frequently used variable names for kernel parameters
We are mainly concerned with the parameters that are required for a success-
ful installation. But there are other parameters for special aims and purposes.
Please keep in mind that upper case letters are significant.
A complete introduction to possible kernel parameters can be found after
installation in the BootPrompt-HOWTO, in /usr/doc/howto as well as
in the kernel sources in the file /usr/src/linux/Documentation/
kernel-parameters.txt.
14.3.2 Kernel Parameters at the Boot Prompt
The parameters listed in this section can only be entered to the kernel, for
example, at the SYSLINUX (supplied bootdiskette), at the LILO-Prompt or
via loadlin
If you plan to install one of these drivers as a module, please look at the
parameters in Section 14.3.4 page 339.
All parameters must be entered directly one after another, separated by
commas. There should be no blanks (whitespace) between the parameters.
For example, to enter the parameters for the aha1542 at the boot prompt
you should enter (please keep in mind that you always have to precede the
parameters with the boot configuration's name; on SuSE boot disks this is the
configuration with the name linux!):
linux aha1542=0x300
General Boot Parameters
By means of certain parameters the general behavior of the Linux kernel can General
be controlled. parameters
* Reboot mode (shutting down Linux)
reboot=<mode>
Here, you have the following values for <mode>:
Variable Values / Meaning
warm warm reboot (no memory check)
cold cold reboot (with memory check)
bios BIOS reboot
hard CPU crash reboot (triple fault)
327
14. Kernel Parameters
Example: reboot=cold
This boots the machine after shutdown as if the reset button had been
pressed.
* Protecting memory segments (Reserve)
reserve=<start1>,<range1>,...,<startN>,<rangeN>
By means of this parameter, you can reserve memory space for hardware
which does not like being autoprobed, and reacts with a system crash, for
example.
Example: A "sensitive" network card can be protected from being auto-
probed and initialized by entering:
reserve=0x330,32 ether=5,0x330,eth0
In this example, the network card has a 32 bit data bus which starts at
address 0x330 and uses interrupt 5.
For the full description of network card parameters, see Section 14.3.2
page 335.
* Passing root partitions
root=<partition>
Variable Values / Meaning
<partition> e. g., /dev/hda1, /dev/sdb5
Example: root=/dev/hda5
This boots the kernel and tries to load the root partition from the first
logical drive in the extended partition to the first (E)IDE hard disk.
* Size of RAM (RAM)
mem=<size>
You may enter the size of RAM in bytes, kilobytes or megabytes. Our
example shows the different settings for 96 MB RAM.
Example:
mem=96M
mem=98304k
On some rare occasions it might happen that the mainboard cannot free
the total amount of RAM. Please subtract the amount of memory the
mainboard reserves (up to 512 K is considered normal). The exact amount
can only be found by "trial and error". Let's assume that it is 512 KB for
our example:
mem=5ff8000
When using a Pentium clone
mem=nopentium
this line might make it work.
328
14.3. The Parameters
The SCSI Controller and the SCSI Subsystem
Most SCSI controllers can be configured via parameters. SCSI
controller
* SCSI Streamers
st=<buffer>,<threshold>[,<max>]
Variable Values / Meaning
<buffer> Buffer size (Amount of 1 KB block)
<threshold> Write threshold (Amount of 1 KB blocks)
<max> Maximum buffer size (optional) (e. g. 2)
Example: st=1000,2000
* Number of SCSI devices per ID
max scsi luns=<number>
Variable Values / Meaning
<number> 1..8
Example: If you want to use only the first LUN you need to set
max scsi luns=1
This is typically used for imperfect CD changers where the amount of
usable CDs equals the parameter max scsi luns=1.
* Adaptec AHA-1520 / 1522 / 1510 / 1515 / 1505 SCSI host adapter
aha152x=<addr>,<irq>,<id>[,<rec>[,<par>]]
Variable Values / Meaning
<id> (SCSI ID of the host adapter) 0, 1
<rec> (reconnect) 0, 1
<par> (parity) 0, 1
This driver is used to run multiple low-cost SCSI controllers. All sound
cards with a SCSI controller (except for Pro Audio Spectrum) can be
accessed using the installed Adaptec chip.
For all non-original 152x, the fourth parameter (RECONNECT) seems to
be necessary. For most types, it has to be set to `0'. Only the AHA2825
needs `1'.
Example: aha152x=0x300,10,7
* Adaptec AHA-1540 / 1542 SCSI host adapter
aha1542=<addr>[,<buson>,<busoff>[,<DMA speed>]]
Variable Values / Meaning
<buson> 2..15
<busoff> 1..64
<DMA speed> 5,6,7,8,10
Example: aha1542=0x300
329
14. Kernel Parameters
* Adaptec AHA-274x / 284x / 294x Hostadapter
aic7xxx=<modifier>[,<modifier>[, ...]]
Variable Values / Meaning
<modifier> extended
activates translation of hard drive geometry
no reset
disables reset of the
SCSI bus at the host adapter initialization
irq trigger:<x>
Only for Eisa systems
0 for flange triggered,
1 for lever driven
verbose
receive more messages
reverse scan
If multiple cards are treated in the wrong
order by the BIOS
7895 irq hack:<x>
-1 only for Tyan II Motherboards
pci parity:<x>
if pci parity is not used at all
parity is even
0 no parity check
1 parity odd
tag info:,,,,,,
Queue management for performance enhancement,
for experts, see kernel sources
Example: aic7xxx=no reset,
if the machine hangs while resetting the SCSI bus.
parameters for aic7xxx based SCSI host adaptors are only necessary if
they are faulty or malfunctioning.
From BIOS version 1.3 onwards the AHA-2940 AU causes no trouble.
Updates may be obtained from Adaptec support.
The SCSI hostadapter Adaptec 2920 is driven by the Future Domain
driver (see Section 14.3.2 on the next page)
* AdvanSys SCSI host adapter
advansys=<addr1>,<addr2>,...,<addrN>
Example: advansys=0x110,0x210
This example tells the kernel to search for the AdvanSys host adapter at
the given addresses.
* AM53/79C974 SCSI host adapter
AM53C974=<host-id>,<target-id>,<rate>,<offset>
330
14.3. The Parameters
Variable Values / Meaning
<host-id> the host adapter's SCSI ID (often 7)
<target-id> the device's SCSI ID (often 0..7)
<rate> 3,5,10 MHz/s max. transfer rate
<offset> transfer mode; 0 = asynchron
If the host adapter seems to "swallow" some packages, reduce the max-
imum transfer rate for this device (e. g., the first CD-ROM SCSI drive
/dev/scd0 with ID 5) on the SCSI bus with:
Example: AM53C974=7,5,3,0
* BusLogic SCSI host adapter
BusLogic=<addr>
BusLogic=<probing>
Example: BusLogic=0x300
Variable Values / Meaning
<addr> Address of the adapter, e. g. 0x300
<probing> NoProbe No adaptor is probed
NoProbeISA No ISA adapter is probed
NoProbePCI No PCI adapter is probed
NoSortPCI Order of multimaster adapter
set by PCI BIOS
MultiMasterFirst Multimaster before Flashpoint
FlashPointFirst Flashpoint before Multimaster
InhibitTargetInquiry For old devices that
cause trouble with scsi luns > 0
TraceProbe outputs additional messages
at initialization of the adapter
TraceHardwareReset outputs additional
messages at the adaptor hardware reset
TraceConfiguration outputs additional
messages at the adaptor configuration
TraceErrors outputs error messages of the
attached devices
Debug outputs all
This host adapter understands even more parameters. These are for fine
tuning the adaptor and are described in /usr/src/linux/drivers/
scsi/README.BusLogic
* Future Domain TMC-16x0 SCSI host adapter
fdomain=<addr>,<irq>[,<id>]
Variable Values / Meaning
<id> SCSI ID of the host adapter 0..7
This driver also controls the Adaptec 2920.
Example: fdomain=0x140,11,7
331
14. Kernel Parameters
* Future Domain TMC-885/950 host adapter
tmc8xx=<addr>,<irq>
Example: tmc8xx=0xca000,5
* NCR 5380 SCSI host adapter family
ncr5380=<addr>,<irq>,<dma>
Example: ncr5380=0x340,10,3
* NCR 53c400 SCSI host adapter family
ncr53c400=<addr>,<irq>
Example: ncr53c400=0x350,5
* NCR 53c406a SCSI host adapter family
ncr53c406a=<addr>[,<irq>[,<fastpio>]]
Variable Values / Meaning
<fastpio> 0, if no fast PIO mode is required
Example: ncr53c406a=0x330,10,0
* Seagate ST01/02 SCSI host adapter
st0x=<addr>,<irq>
Example: st0x=0xc8000,5
* Trantor T128/128F/228 SCSI host adapter
t128=<addr>,<irq>
Example: t128=0x340,10
(E)IDE Controllers and ATAPI Devices
(E)IDE Numerous parameters are available to configure the (E)IDE controllers and
controllers the devices connected to them.
ATAPI Devices * ATAPI CD-ROM on the (E)IDE controller
hd<x>=cdrom
hd<x>=serialize
Variable Values / Meaning
<x> a, b, c, d
where:
Variable Values / Meaning
a master on 1st IDE controller
b slave on 1st IDE controller
c master on 2nd IDE controller
d slave on 2nd IDE controller
Example: an ATAPI CD-ROM as master on the secondary IDE controller
is set by hdc=cdrom.
332
14.3. The Parameters
* Hard Drive
hd<x>=<cylinders>,<heads>,<sectors>[,<write>[,<irq>]]
Variable Values / Meaning
<x> a, b, . . . , h 1 to 8. Hard Drive
<cylinders> number of cylinders
<k"opfe> number of heads
<sektoren> number of sectors
<schreib> cylinders after which write compensation is used
<irq> interrupt
If the BIOS is an old one, it is possible that the geometry of the hard drive
is not recognized correctly. The correct parameters will then be passed on
so that the kernel can still access the complete hard drive.
Example: hdc=1050,32,64
hd<x>=<trouble>
Variable Values / Meaning
<x> a, b, . . . , h 1st to 8th hard drive
<trouble> noprobe, if testing an existing hard drive
causes problems
none ignore CMOS entry and don't test
nowerr ignore WREE STAT-bit
cdrom wrongly recognized as hard drive
or not recognized at all, or will not boot
autotune the fastest PIO mode is used
slow adds a long break after each access.
This makes it really slow, but it sometimes helps
if it is the only option left
If a CD-ROM drive is not recognized reliably, specifying <cdrom> can
register the device safely.
Example: hdd=cdrom
* EIDE controller chipsets
Some EIDE controllers have faulty chipsets or cause problems if the sec-
ondary controller is used.
Many of these chipsets are now supported in the kernel; this support needs
to be specially activated, however, using a kernel parameter.
The following chipsets can be configured:
333
14. Kernel Parameters
CMD 640 This chipset is found on many mother-
boards. Since it contains many bugs, the
kernel offers a special support which recog-
nizes the chip and bypasses the problems.
Moreover, in some cases, use of the sec-
ondary controller is only possible by using
this special support. In PCI systems, this
chip is automatically recognized. For VLB
systems, the following parameter is needed:
ide0=cmd640 vlb.
RZ 1000 This chip is used on many motherboards
that use the Neptune chipset and it is buggy.
If support for this chip is activated, the sys-
tem works a little slower but reliably. An
additional activation with a kernel parame-
ter is not required.
DTC-2278 Only activating this driver via
ide0=dtc2278 makes it possible to
use the secondary controller.
Holtek HT6560B The following parameter is needed
to activate the secondary controller:
ide0=ht6560b.
QDI QD6580 If this driver is activated, it enables a higher
speed: ide0=qd6580.
UMC 8672 For activating the secondary controller,
the following parameter is needed:
ide0=umc8672.
ALI M1439/M1445 For activating the secondary controller,
the following parameter is needed:
ide0=ali14xx.
PROMISE DC4030 For activating the secondary controller,
the following parameter is needed:
ide0=dc4030. CD-ROMs and tapes on
the secondary controller are not supported
yet.
Table 14.2: Special EIDE chipsets
If the chipset does not belong to the list of known faulty chipsets, and still is
not recognized, the following parameters can be added instead:
ide<number>=<basis>[,<control>[,<irq>]]
334
14.3. The Parameters
Variable Values / Meaning
<number> adapter number,
usually 0 or 1, but also 3 or 4
<basis> base address of the adapter,
usually 0x1f0, 0x170, 0x1e8 or 0x168
<control> control register of the adapters,
usually 0x3f6, 0x376, 0x3ee or 0x36e
<irq> interrupt of the adapters,
usually 14, 15, 11 or 10
If the chipset does not belong to the list of known faulty chipsets, but still
causes problems, the following parameters can be added instead:
ide<number>=<tune>
Variable Values / Meaning
<number> adapter number, usually 0 or 1, but also 3 or 4
<tune> autotune the highest possible PIO value
is tried, not supported by all chipsets
noautotune no improvement in speed
serialize no time overlapping of
operations with the next adapter
If the chipset does not belong to the list of known faulty chipsets, but the
highest possible speed should still be achieved, the bus speed can be passed
on; please refer to your motherboard manual.
idebus=<speed>
Other Devices
Network cards,
floppy drives
* Ethernet network cards
ether=<irq>,<addr>[,<par1>[,<par2>...<par8>]],<Name>
The various parameters for <par1> to <par8> have different mean-
ings for several drivers. Usually, only two parameters are needed, where
the first is the start address and the second is the end address of shared
memory. The first non-numerical argument is treated as the name.
<irq> the interrupt used; 0 for autoprobing
<addr> port address; 0 for autoprobing
<start> start address for shared memory. Some drivers use the
4 lowest bits for the debug level. The Lance uses them
for its DMA channel.
<end> end address for shared memory. The 3COM 3c503
driver uses this parameter to distinguish between in-
ternal and external transceivers.
Table 14.3: continued overleaf. . . ... 335
14. Kernel Parameters
The Cabletron E21XX card uses the lowest four bits
for selecting the media.
<Name> The interface's name (normally eth0)
Table 14.3: Variable names for Ethernet network cards
The main reason for specifying this parameter is to let the kernel recog-
nize more than one network card, since only the first card is searched by
default. This can easily be done with:
ether=0,0,eth1
Please note that, by passing 0 for both IRQ and address, the driver is
explicitly told to launch autoprobing, which means probing several ad-
dresses independently.
* Floppy disk drives
floppy=<drive>,<type>,cmos
Variable Values / Meaning
<drive> 0, 1, 2, 3
<type> 0 - unknown or not recognized
1 - 5 1/4" DD, 360 KB
2 - 5 1/4" HD, 1.2 MB
3 - 3 1/2" DD, 720 KB
4 - 3 1/2" HD, 1.44 MB
5 - 3 1/2" ED, 2.88 MB
6 - 3 1/2" ED, 2.88 MB
floppy=<value>
For <value>, the following values may be set (Table 14.4 on the facing
page):
all drives more than two floppy disk
drives
asus pci denies access to 3rd and 4th
floppy disk drives
daring use only with reliable
controllers-enhances per-
formance
0,daring opposite of daring
<addr>,two fdc if the value <addr> is omit-
ted while using a secondary
floppy controller, a port ad-
dress of 0x370 is set.
336 Table 14.4: continued overleaf. . . ...
14.3. The Parameters
thinkpad IBM Thinkpad machines
0,thinkpad not a Thinkpad machine
omnibook Omnibook computers
nodma for Omnibook computers
dma Standard
nofifo if a "Bus master arbi-
tration error" occurs
fifo Standard
0xX,fifo depth FIFO threshhold standard 0xA
unexpected interrupts show warnings if something
unexpected happens.
no unexpected interrupts and...
L40SX this value is the opposite of
unexpected interrupts.
Table 14.4: Kernel parameter values for floppy
* Logitech bus mouse
bmouse=<irq>
14.3.3 CD-ROM Drives on Proprietary Controllers
Old CD-ROM
drives
* Aztech CDA268-01 CD-ROM
aztcd=<addr>[,0x79]
The value 0x79 has only to be set when the firmware version is unknown.
Example: aztcd=0x320
* Goldstar R420 CD-ROM drive
gscd=<addr>
* Mitsumi CD-ROM drive
mcd=<addr>,<irq>[,<wait>]
Variable Values / Meaning
<wait> value for waiting time while starting
You can vary the parameter <wait> between 0 and 10 if the CD-ROM
drive does not react fast enough on system requests ("timeout") and,
therefore, does not find the root image while installing.
Example: mcd=0x300,10,5
* Mitsumi CD-ROM drive (multisession)
mcdx=<addr>,<irq>
Example: mcd=0x300,10
337
14. Kernel Parameters
* Mozart interface
isp16=<addr>,<irq>,<dma>,<type>
Variable Values / Meaning
<type> Sanyo, Panasonic, Sony, Mitsumi
This driver is responsible for CD-ROM drives connected to the types
ISP16, MAD16 or Mozart. The value of <type> follows the interface
plug where the CD-ROM is connected to the sound card.
Example: isp16=0x340,10,3,Sony
* Optics Storage 8000 AT CD-ROM drive
optcd=<addr>
Example: optcd=0x340
* Philips CM206 CD-ROM drives
cm206=<addr>,<irq>
Example: cm206=0x340,10
* Pro Audio Spectrum 16 - SCSI host adapter
pas16=<addr>,<irq>
On the Pro Audio Spectrum 16 sound card there is a SCSI-host adapter,
the settings of which can be passed to the kernel with this parameter.
Example: pas16=0x340,10
If the card is not recognized, it can be operated without an interrupt. In
this case the interrupt is set to 255.
Example: pas16=0x340,255
* Sanyo CD-ROM Drive
sjcd=<addr>
Example: sjcd=0x340
* Sony CDU 31/33 A
cdu31a=<addr>,<irq>
Autoprobing of this driver has been removed from the kernel. Thus, you
have to set any parameters explicitly.
Example: cdu31a=0x340,5
If there is no interrupt assigned to the drive, and if you can only access it
via polling mode, you have to enter 0 for the IRQ.
Example: cdu31a=0x340,0
As an example, if this drive is connected to a Pro Audio Spectrum card,
the parameter could be as follows:
Example: cdu31a=0x1f88,0,PAS
* Sony CDU 535
sonycd535=<addr>,<irq>
Example: sonycd535=0x340,10
338
14.3. The Parameters
* SoundBlaster Pro 16 MultiCD
sbpcd=<addr>,<type>
Variable Values / Meaning
<type> LaserMate, SPEA, SoundBlaster
Example: sbpcd=0x340,10
The Parallel Port
Parallel Port
* Parallelport
parport=<addr0>,[<irq0> [parport=<addr1>,[<irq1>
[parport=<addr2>,[<irq2>]]]]]
Variable Values / Meaning
<addrX> address
<irqX> interrupt
Example: parport=0x3bc parport=0x378,7 parport=0x278,auto
* Printer on the parallel port
lp=<parport0> [lp=<parport1> [lp=<parport2>]]
Variable Values / Meaning
<parportX> parallel port
Example: lp=parport0 lp=parport2
14.3.4 modprobe Parameters
This section describes those parameters which can be loaded as modules. If
you encounter difficulties while loading a driver (although you have entered
the parameters), or if there is no section describing the parameter, then you
may have to integrate this driver into a monolithic kernel.
Some drivers can not be built as modules yet and some recognize your hard-
ware properly only if they are compiled into the kernel. Despite this, we
recommend you try the "module variant" first.
If a driver is loaded as a module, each and every variable used can be over-
written on the command line. There is, e. g., the variable io in the NE2000
driver which specifies the used I/O range. For this, the correct command for
loading this module is (see Section 13.2 page 318):
earth:/ # insmod ne io=0x300 irq=10
or better with modprobe:
earth:/ # modprobe ne io=0x300 irq=10
Be aware that there should be no spaces before or after the "equal". Moreover,
hexadecimal values have to be set in the given form (with a leading `0x').
339
14. Kernel Parameters
If you want to enter more than one parameter they must be separated by
spaces. This is the main difference to entering parameters at the LILO
prompt, where no blanks should be used within the parameters for one
driver.
The parameters you enter here can also be integrated into
/etc/modules.conf. Here many parameters can be assigned to a partic-
ular module. This is done one line per module. The line should resemble the
following:
options <module name> <parm1>=<value1> ...
where:
Variable Values / Meaning
<module name> name of the module without the extension .o
<parm1> parameter #1
<value1> value that is assigned to parameter #1
An entry for the NE2000 card might look like:
options ne io=0x300 irq=10
SCSI Controllers and the SCSI Subsystem
* Adaptec AHA-1520 / 1522 / 1510 / 1515 / 1505 SCSI-Hostadapter
Name of module: aha152x.o
Variable Values / Meaning
<io> <addr>
<irq> <irq>
<id> SCSI-ID of the host adapter; by default, 7
<rec> reconnect; 0, 1
<par> parity; 0, 1
<sync> synchronous mode of operation; 0, 1
<delay> bus delay; default 100
<translat> "translation of the hard drive geometry; 0, 1
As at the LILO prompt:
Example: modprobe aha152x aha152x=0x340,10,7,1,1,0,0,0
For a second host adapter:
Example: modprobe aha152x aha152x1=0x140,12,7,1,1,0,0,0
* Future Domain TMC-16x0¡host adapter
Name of module: fdomain.o
This driver also serves the SCSI-host adapter Adaptec 2920, amongst
others.
fdomain=<addr>,<irq>[,<id>]
Variable Values / Meaning
<addr> <addr>
<irq> <irq>
<id> <id>
340
14.3. The Parameters
As at the LILO-Prompt:
Example: modprobe fdomain fdomain=0x140,11,7
* NCR 5380 bzw. NCR 53C400 SCSI-host adapter family
Name of module: g_NCR5380.o
Parameter Value
ncr addr <addr>
ncr irq <irq>; switch off with 255
ncr dma <dma>
ncr 5380 1 for an NCR5380 adapter
ncr 53c400 1 for an NCR53C400 adapter
For an NCR5380 adapter:
Example: modprobe g NCR5380 ncr irq=5 ncr addr=0x350
ncr 5380=1
For an NCR53C400 adapter with interrupts turned off:
Example: modprobe g NCR5380 ncr irq=255 ncr addr=0xc8000
ncr 53c400=1
This driver serves the widely-used Trantor T130B SCSI host adapter
Network Cards
* 3Com 3c501 / 3c503 / 3c505 / 3c507 network cards
Name of module: 3c501.o,3c503.o,3c505.o,3c507.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe 3c509 io=0x300 irq=10
* 3Com 3c509 / 3c579 network cards
Name of module: 3c509.o
Parameter Value
irq <irq>
xcvr 0: internal; 1: external
Example: modprobe 3c509 irq=10 xcvr=0
* 3Com 3c515 network card
Name of module: 3c515.o
Example: modprobe 3c515
* 3Com 3c59x / 3c90x network cards ("Vortex"/"Boomerang")
Name of module: 3c59x.o
For Compaq computers(PCI), you can try the following parameters:
341
14. Kernel Parameters
Parameter Value
compaq ioaddr <addr>
compaq irq <irq>
compaq prod id <id>
Example: modprobe 3c59x compaq irq=10
* Allied Telesis AT1700 network card
Name of module: at1700.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe at1700 io=0x300 irq=10
* Cabletron E21xx network card
Name of module: e2100.o
Parameter Value
io <addr>
irq <irq>
mem <addr>
xcvr 0: internal; 1: external
Example: modprobe e2100 io=0x300 irq=10 mem=0xd000 xcvr=0
* Digital DE425 / 434 / 435 / 450 / 500 network cards
Name of module: de4x5.o
io=0x<bus><device ID>
Parameter Value
bus number of the PCI bus, usually 0
device ID number des PCI device
With newer PCI BIOSes, these files are displayed when the machine
boots, and in Linux they can be seen with the command
earth: # cat /proc/pci
Example: modprobe de4x5 io=0x007
* Digital DEPCA / DE10x / DE20(012) / DE42, EtherWORKS network
cards
Name of module: depca.o
342
14.3. The Parameters
Parameter Value
io <addr>
irq <irq>
mem <mem>
adapter name <name> e.g. DEPCA,
de100, de101,
de200, de201,
de202, de210,
de422
Example: modprobe depca io=0x300 irq=10
* EtherWORKS 3 (DE203, DE204, DE205) network card
Name of module: ewrk3.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe ewrk3 io=0x300 irq=10
* Intel EtherExpress 16 network card
Name of module: eexpress.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe eexpress io=0x300 irq=10
* Intel EtherExpressPro network card
Name of module: eepro.o
Parameter Value
io <addr>
irq <irq>
mem <addr>
Example: modprobe eepro io=0x300 irq=10 mem=0xd000
* Intel EtherExpressPro 100 network card
Name of module: eepro100.o
The Intel EtherExpressPro contains the chips i82557/i82558.
Parameter Value
options <duplex operation>
<bus-transceiver>
16 full-duplex
32 100 MBit operation only
64 10 MBit operation only
343
14. Kernel Parameters
Example: modprobe eepro100 options=48
This sets full-duplex and 100-MBit operation simultaneously (48 = 32 +
16).
* Fujitsu FMV-181/182/183/184 network cards
Name of module: fmv18x.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe fmv18x io=0x300 irq=10
* HP PCLAN+ (27247B and 27252A) network card
Name of module: hp-plus.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe hp-plus io=0x300 irq=10
* HP PCLAN (27245 / 27xxx)
Name of module: hp.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe hp io=0x300 irq=10
* HP 10/100 VG-AnyLAN (ISA, EISA, PCI) network cards
Name of module: hp100.o
Parameter Value
hp100 port <addr>
Example: modprobe hp100 hp100 port=0x300
* ICL EtherTeam 16i / 32 network cards
Name of module: eth16i.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe eth16i io=0x300 irq=10
344
14.3. The Parameters
* Novell NE2000 / NE1000 network cards
Name of module: ne.o
Parameter Value
io <addr>
irq <irq>
bad bad, only if the card is not recognized
Example: modprobe ne io=0x300 irq=10
* NI6510 (AM7990 "lance" Chip) network card
Name of module: ni65.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
Example: modprobe ni65 io=0x300 irq=10
* SMC Ultra network card
Name of module: smc-ultra.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe smc-ultra io=0x300 irq=10
* SMC 9194 network card
Name of module: smc9194.o
Parameter Value
io <addr>
irq <irq>
if port <medium>
Variable Values / Meaning
<medium> 0 auto
1 TP
2 AUI, 10base2
Example: modprobe smc9194 io=0x300 irq=10 if port=2
* Western Digital WD80x3 network card
Name of module: wd.o
345
14. Kernel Parameters
Parameter Value
io <addr>
irq <irq>
mem <mem>
mem end <mem end>
Example: modprobe wd io=0x300 irq=10
* IBM Tropic chipset Token Ring network card
Name of module: ibmtr.o
Parameter Value
io <addr>
irq <irq>
mem start <mem start>
Example: modprobe ibmtr io=0x300
* D-Link DE620 Pocket-Adapter network card
Name of module: de620.o
Parameter Value
io <addr>
irq <irq>
bnc 1 if a BNC input/output
utp 1 if a UTP input/output
clone 1 if an equivalent device
Example: modprobe de620 io=0x300 irq=10 bnc=1 utp=0
Proprietary CD-ROM Drives
CD-ROM The following parameters concern CD-ROM drives attached to special
Drives, controllers. Whoever possesses one of these "oldies" will certainly know
proprietary about it. . .
* Aztech CDA268-01 CD-ROM drive
Name of module: aztcd.o
Parameter Value
aztcd <addr>
Example: modprobe aztcd aztcd=0x300
* Goldstar R420-CD-ROM drive
Name of module: gscd.o
Parameter Value
gscd <addr>
Example: modprobe gscd gscd=0x300
346
14.3. The Parameters
* Mitsumi CD-ROM drive
Name of module: mcd.o
mcd=<addr>,<irq>[,<wait>]
Variable Values / Meaning
<wait> Delay at startup time
You can vary the <wait> from 0 to 10 if the CD-ROM drive does not
react fast enough ("timeout"), thus probably not finding the root image
during installation.
Example: modprobe mcd mcd=0x300,10,5
* Mitsumi CD-ROM drive (Multisession)
Name of module: mcdx.o
mcdx=<addr>,<irq>[,<addr>,<irq>]
For a number of drivers the settings <addr>, <irq> can be repeated up
to 4 times.
* Mozart sound card with port for CD-ROM drives
Name of module: isp16.o
isp16 cdrom base=<addr>
isp16 cdrom irq=<irq> isp16 cdrom dma=<dma>
isp16 cdrom type=<typ>
Variable Values / Meaning
<typ> Sanyo, Panasonic, Sony, Mitsumi
This driver is not a real CDROM driver; it is only responsible for the in-
terface configuration of the CD-ROM drive when connected to a ISP16,
MAD16 or Mozart sound card. After this driver is loaded only the inter-
face is loaded accordingly; the corresponding CDROM driver needs to be
loaded as well. The value for the variable <type> is written on the plug
which connects the CD-ROM cable to the sound card.
Example: modprobe isp16 isp16 cdrom base=0x300
isp16 cdrom irq=10 isp16 cdrom dma=1
isp16 cdrom type=sony
* Optics Storage 8000 AT CD-ROM drive
Name of module: optcd.o
Parameter Value
optcd <addr>
Example: modprobe optcd optcd=0x300
* Philips CM206 CD-ROM drive
Name of module: cm206.o
cm206=<addr>,<irq>
Example: modprobe cm206 cm206=0x300,10
347
14. Kernel Parameters
* Sanyo CD-ROM drive
Name of module: sjcd.o
Parameter Value
sjcd <addr>
Example: modprobe sjcd sjcd=0x300
* Sony CDU 31/33 A
Name of module: cdu31a.o
Parameter Value
cdu31a port <addr>
cdu31a irq <irq>
Example: modprobe cdu31a cdu31a port=0x300 cdu31a irq=10
* Sony CDU 535
Name of module: sonycd535.o
Parameter Value
sonycd535 <addr>
Example: modprobe sonycd535 sonycd535=0x300
* Soundblaster Pro 16 MultiCD
Name of module: sbpcd.o
sbpcd=<addr>,<typ>
whereby <type> can have the following values:
Variable Values / Meaning
0 LaserMate
1 SoundBlaster
2 SoundScape
3 Teac16bit
Example: modprobe sbpcd sbpcd=0x300,0
Sound Cards and Sound Chipsets
Sound Since the 2.2.xx kernel sound support has been resolved in modular form and
can be controlled by numerous parameters.
* AD1816 Chip
Name of module: ad1816.o
The following cards, amongst others, are supported: Terratec Base 1,
Terratec Base 64, HP Kayak, Acer FX-3D, SY-1816, Highscreen Sound-
Boostar 32 Wave 3D
348
14.3. The Parameters
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma2 <dma2>
ad1816 clockfreq <clockfreq>
Example: modprobe ad1816 io=0x530 irq=5 dma=1
dma2=3 ad1816 clockfreq=33000
* AD1848/CS4248 Chip (MSS)
Name of module: ad1848.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma2 <dma2>
type <cardtype>
deskpro xl <magic>
* Generic OPLx driver
Name of module: adlib_card.o
Parameter Value
io <addr>
Example: modprobe adlib card io=0x330
* Crystal 423x chipsets
Name of module: cs4232.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma2 <dma2>
Example: modprobe cs4232 io=0x530 irq=5 dma=1 dma2=3
* Ensoniq 1370 chipset
Name of module: es1370.o
see also PCI64/128.
Parameter Value
joystick 1: activate joystick
lineout 1: line-in in line-out switch over
micz microphone impedancy
Example: modprobe es1370 joystick=1 lineout=1
349
14. Kernel Parameters
* Creative Ensoniq 1371 chipset
Name of module: es1371.o
Refer also to the PCI64/128.
Parameter Value
joystick <addr>
Valid values for <addr> are 0x200, 0x208, 0x210 and 0x218.
Example: modprobe es1371 joystick=0x200
* Gravis Ultrasound
Name of module: gus.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma16 <dma16>
type
gus16
no wave dma
db16
* MAD16
Name of module: mad16.o
Supports OPTi 82C928, OAK OTI-601D, OPTi 82C929, OPTi 82C930
and OPTi 82C924.
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma16 <dma2>
Example: modprobe mad16 io=0x530 irq=7 dma=0 dma16=1
* Turtle Beach Maui and Tropez
Name of module: maui.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe maui io=0x530 irq=5
* MPU401
Name of module: mpu401.o
350
14.3. The Parameters
Parameter Value
io <addr>
Example: modprobe mpu401 io=0x330
* Turtle Beach MultiSound
Name of module: msnd.o
Example: modprobe msnd
* Turtle Beach Classic/Monterey/Tahiti
Name of module: msnd_classic.o
Parameter Value
io <addr>
irq <irq>
mem
write ndelay
major
fifosize
calibrate signal
Example: modprobe io=0x290 irq=7 mem=0xd0000
* Turtle Beach Pinnacle/Fiji
Name of module: msnd_pinnacle.o
As well as the parameters of the Turtle Beach Classic/Monterey/Tahiti,
this card also understands:
Parameter Value
digital
cfg
reset
mpu io
mpu irq
ide io0
ide io1
ide irq
joystick io
Example: modprobe msnd pinnacle cfg=0x250 io=0x290 irq=5
mem=0xd0000
* OPL3
Name of module: opl3.o
Parameter Value
io <addr>
Example: modprobe io=0x388
351
14. Kernel Parameters
* OPL3-SA1
Name of module: opl3sa.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma2 <dma2>
mpu io <addr>
mpu irq <irq>
Example: modprobe opl3sa io=0x530 irq=11 dma=0 dma2=1
mpu io=0x330 mpu irq=5
* YMF711, YMF715, YMF719, OPL3-SA2, OPL3-SA3, OPL3-SAx
Name of module: opl3sa2.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma2 <dma2>
mss io <addr>
mpu io <addr>
Example: modprobe opl3sa2 io=0x370 irq=7 dma=0 dma2=3
mss io=0x530 mpu io=0x330
* Pro Audio Spectrum
Name of module: pas2.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma16 <dma16>
sb io <addr>
sb irq <irq>
sb dma <dma>
sb dma16 <dma16>
joystick
symphony
broken bus clock
* Personal Sound System (ECHO ESC614)
Name of module: pss.o
352
14.3. The Parameters
Parameter Value
pss io <addr>
mss io <addr>
mss irq <irq>
mss dma <dma>
mpu io <addr>
mpu irq <irq>
pss mixer activate 1 or 0
* Sound Blaster and Clones
Name of module: sb.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma16 <dma16>
mpu io <addr>
mad16 activate 1
trix activate1
pas2 activate1
sm games activate1
acer activate1, for Acer Notebooks
mwave bug activate1
Example: modprobe sb io=0x220 irq=5 dma=1 dma16=5 mpu io=0x330
* Aztech Sound Galaxy
Name of module: sgalaxy.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma2 <dma2>
sgbase
* S3 Sonic Vibes
Name of module: sonicvibes.o
No parameters.
* Ensoniq SoundScape
Name of module: sscape.o
353
14. Kernel Parameters
Parameter Value
io <addr>
irq <irq>
dma <dma>
mss
mpu io <addr>
mpu irq <irq>
spea 1
* MediaTrix AudioTrix Pro
Name of module: trix.o
Parameter Value
io <addr>
irq <irq>
dma <dma>
dma2 <dma2>
sb io <addr>
sb irq <irq>
sb dma <dma>
mpu io <addr>
mpu irq <irq>
* UART401
Name of module: uart401.o
Parameter Value
io <addr>
irq <irq>
Example: modprobe io=0x330 irq=9
* UART6850
Name of module: uart6850.o
Parameter Value
io <addr>
irq <irq>
* Sound Blaster DSP chipsets
Name of module: v_midi.o
No parameters.
* Turtle Beach Maui, Tropez, Tropez Plus
Name of module: wavefront.o
354
14.3. The Parameters
Parameter Value
io <addr>
irq <irq>
Example: modprobe wavefront io=0x200 irq=9
The Parallel Port
The operation of the parallel port is somewhat complex. After configuration, Parallel Port
a complete subsystem is available; see Section 10.4.3 page 267 pp.
* Parallel port
Name of module: parport.o
Example: modprobe parport
* Parallel port ¡ architecture-specific
Name of module: parport_pc.o
Parameter Value
io <addr>
irq <irq>
In order to set up 3 Ports in a PC style, for example, whereby one has the
address 0x3bc without an IRQ, one has the address 0x378 with IRQ 7
and one has the address 0x278 with automatically detected IRQ, you
should enter (all in one line!):
Example: modprobe parport pc io=0x3bc,0x378,0x278
irq=none,7,auto
* Printer driver
Name of module: lp.o
Parameter Value
parport <port>
Example: modprobe lp parport=0,2
* Parallel port IDE devices
Name of module: paride.o
If you want to use chains of Paride devices on a single parallel port, then
you must first load parport.o!
Example: modprobe paride
The parallel port should ¡ if possible ¡ be operated in "EPP mode"; please
set this mode in the BIOS of your computer.
* Parallel port IDE low-level protocol driver
Name of module: \variable{xxxx}.o
355
14. Kernel Parameters
protocol device
aten ATEN EH-100 (HK)
bpck Microsolutions backpack (US)
comm DataStor (old-type) "commuter" adapter (TW)
dstr DataStor EP-2000 (TW)
epat Shuttle EPAT (UK)
epia Shuttle EPIA (UK)
fit2 FIT TD-2000 (US)
fit3 FIT TD-3000 (US)
friq Freecom IQ cable (DE)
frpw Freecom Power (DE)
kbic KingByte KBIC-951A and KBIC-971A (TW)
ktti KT Technology PHd adapter (SG)
on20 OnSpec 90c20 (US)
on26 OnSpec 90c26 (US)
Example: modprobe epat
* Parallel port IDE hard drive
Name of module: pd.o
Parameter Value
verbose <value>
First load parport and the low-level driver
Example: modprobe pd verbose=1
* Parallel port ATAPI CD-ROM
Name of module: pcd.o
First load parport and the low-level driver
Example: modprobe pcd
* Parallel port ATAPI floppy disk drive
Name of module: pf.o
First load parport and the low-level driver
Example: modprobe pf
* Parallel port ATAPI streamer drive
Name of module: pt.o
First load parport and the low-level driver
Example: modprobe pt
* Parallel port generic ATAPI device
Name of module: pg.o
First load parport and the low-level driver
Example: modprobe pg
356