.\" Copyright (c) 1995,1997 Paul Gortmaker and Andries Brouwer
.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
.\" This is free documentation; you can redistribute it and/or
.\" modify it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2 of
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public
-.\" License along with this manual; if not, write to the Free
-.\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
-.\" USA.
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
.\"
.\" This man page written 950814 by aeb, based on Paul Gortmaker's HOWTO
.\" (dated v1.0.1, 15/08/95).
.\" Major update, aeb, 970114.
-.\" FIXME ? The use of quotes on this page is inconsistent with the
+.\" FIXME . The use of quotes on this page is inconsistent with the
.\" rest of man-pages.
.\"
-.TH BOOTPARAM 7 2007-12-16 "Linux" "Linux Programmer's Manual"
+.TH BOOTPARAM 7 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
-bootparam \- Introduction to boot time parameters of the Linux kernel
+bootparam \- introduction to boot time parameters of the Linux kernel
.SH DESCRIPTION
The Linux kernel accepts certain 'command-line options' or 'boot time
parameters' at the moment it is started.
which you copied a kernel using 'cp zImage /dev/fd0'),
you have no opportunity to specify any parameters.
So, in order to take advantage of this possibility you have to
-use software that is able to pass parameters, like LILO or loadlin.
-For a few parameters one can also modify the kernel image itself,
-using rdev, see
-.BR rdev (8)
-for further details.
-
-The LILO program (LInux LOader) written by Werner Almesberger is the
-most commonly used.
-It has the ability to boot various kernels, and
-stores the configuration information in a plain text file.
-(See
-.BR lilo (8)
-and
-.BR lilo.conf (5).)
-LILO can boot DOS, OS/2, Linux, FreeBSD, UnixWare, etc., and is quite flexible.
-
-The other commonly used Linux loader is 'LoadLin' which is a DOS
-program that has the capability to launch a Linux kernel from the DOS
-prompt (with boot-args) assuming that certain resources are available.
-This is good for people that want to launch Linux from DOS.
-
-It is also very useful if you have certain hardware which relies on
-the supplied DOS driver to put the hardware into a known state.
-A common example is 'SoundBlaster Compatible' sound cards that require
-the DOS driver to twiddle a few mystical registers to put the card
-into a SB compatible mode.
-Booting DOS with the supplied driver, and
-then loading Linux from the DOS prompt with loadlin avoids the reset
-of the card that happens if one rebooted instead.
-.SS "The Argument List"
+use a boot loader that is able to pass parameters, such as GRUB.
+
+.\" The LILO program (LInux LOader) written by Werner Almesberger is the
+.\" most commonly used.
+.\" It has the ability to boot various kernels, and
+.\" stores the configuration information in a plain text file.
+.\" (See
+.\" .BR lilo (8)
+.\" and
+.\" .BR lilo.conf (5).)
+.\" LILO can boot DOS, OS/2, Linux, FreeBSD, UnixWare, etc., and is quite flexible.
+.\"
+.\" The other commonly used Linux loader is 'LoadLin', which is a DOS
+.\" program that has the capability to launch a Linux kernel from the DOS
+.\" prompt (with boot-args) assuming that certain resources are available.
+.\" This is good for people that want to launch Linux from DOS.
+.\"
+.\" It is also very useful if you have certain hardware which relies on
+.\" the supplied DOS driver to put the hardware into a known state.
+.\" A common example is 'SoundBlaster Compatible' sound cards that require
+.\" the DOS driver to twiddle a few mystical registers to put the card
+.\" into a SB compatible mode.
+.\" Booting DOS with the supplied driver, and
+.\" then loading Linux from the DOS prompt with loadlin avoids the reset
+.\" of the card that happens if one rebooted instead.
+.SS The argument list
The kernel command line is parsed into a list of strings
(boot arguments) separated by spaces.
-Most of the boot args take the form of:
-.IP
+Most of the boot arguments take have the form:
+
+.in +4n
+.nf
name[=value_1][,value_2]...[,value_10]
+.fi
+.in
.LP
where 'name' is a unique keyword that is used to identify what part of
the kernel the associated values (if any) are to be given to.
-Note the limit of 10 is real, as the present code only handles 10 comma
+Note the limit of 10 is real, as the present code handles only 10 comma
separated parameters per keyword.
(However, you can reuse the same
keyword with up to an additional 10 parameters in unusually
complicated situations, assuming the setup function supports it.)
-Most of the sorting goes on in linux/init/main.c.
+Most of the sorting is coded in the kernel source file
+.IR init/main.c .
First, the kernel
checks to see if the argument is any of the special arguments 'root=',
\&'nfsroot=', 'nfsaddrs=', 'ro', 'rw', 'debug' or 'init'.
if 'foo' was registered.
If it was, then it would call the setup
function associated with 'foo' (foo_setup()) and hand it the arguments
-3, 4, 5 and 6 as given on the kernel command line.
+3, 4, 5, and 6 as given on the kernel command line.
Anything of the form 'foo=bar' that is not accepted as a setup function
as described above is then interpreted as an environment variable to
Any remaining arguments that were not picked up by the kernel and were
not interpreted as environment variables are then passed onto process
-one, which is usually the init program.
+one, which is usually the
+.BR init (1)
+program.
The most common argument that
-is passed to the init process is the word 'single' which instructs init
+is passed to the
+.I init
+process is the word 'single' which instructs it
to boot the computer in single user mode, and not launch all the usual
daemons.
-Check the manual page for the version of init installed on
+Check the manual page for the version of
+.BR init (1)
+installed on
your system to see what arguments it accepts.
-.SS "General Non-device Specific Boot Arguments"
+.SS General non-device-specific boot arguments
.TP
.B "'init=...'"
This sets the initial command to be executed by the kernel.
protected mode.
For example, some of the early ULSI-387 chips would
cause solid lockups while performing floating-point calculations.
-Using the 'no387' boot arg causes Linux to ignore the maths
+Using the 'no387' boot argument causes Linux to ignore the maths
coprocessor even if you have one.
Of course you must then have your
kernel compiled with math emulation support!
.TP
.B "'root=...'"
This argument tells the kernel what device is to be used as the root
-file system while booting.
+filesystem while booting.
The default of this setting is determined
at compile time, and usually is the value of the root device of the
system that the kernel was built on.
To override this value, and
select the second floppy drive as the root device, one would
use 'root=/dev/fd1'.
-(The root device can also be set using
-.BR rdev (8).)
The root device can be specified symbolically or numerically.
-A symbolic specification has the form /dev/XXYN, where XX designates
+A symbolic specification has the form
+.IR /dev/XXYN ,
+where XX designates
the device type ('hd' for ST-506 compatible hard disk, with Y in
\&'a'-'d'; 'sd' for SCSI compatible disk, with Y in 'a'-'e';
\&'ad' for Atari ACSI disk, with Y in 'a'-'e',
\&'ez' for a Syquest EZ135 parallel port removable drive, with Y='a',
\&'xd' for XT compatible disk, with Y either 'a' or 'b'; 'fd' for
-floppy disk, with Y the floppy drive number \(em fd0 would be
+floppy disk, with Y the floppy drive number\(emfd0 would be
the DOS 'A:' drive, and fd1 would be 'B:'), Y the driver letter or
number, and N the number (in decimal) of the partition on this device
(absent in the case of floppies).
(The type nfs specifies a net boot; ram refers to a ram disk.)
Note that this has nothing to do with the designation of these
-devices on your file system.
+devices on your filesystem.
The '/dev/' part is purely conventional.
The more awkward and less portable numeric specification of the above
possible root devices in major/minor format is also accepted.
-(E.g., /dev/sda3 is major 8, minor 3, so you could use 'root=0x803' as an
+(For example,
+.I /dev/sda3
+is major 8, minor 3, so you could use 'root=0x803' as an
alternative.)
.TP
+.BR "'rootdelay='"
+This parameter sets the delay (in seconds) to pause before attempting
+to mount the root filesystem.
+.TP
+.BR "'rootflags=...'"
+This parameter sets the mount option string for the root filesystem
+(see also
+.BR fstab (5)).
+.TP
+.BR "'rootfstype=...'"
+The 'rootfstype' option tells the kernel to mount the root filesystem as
+if it where of the type specified.
+This can be useful (for example) to
+mount an ext3 filesystem as ext2 and then remove the journal in the root
+filesystem, in fact reverting its format from ext3 to ext2 without the
+need to boot the box from alternate media.
+.TP
.BR 'ro' " and " 'rw'
-The 'ro' option tells the kernel to mount the root file system
-as 'read-only' so that file system consistency check programs (fsck)
-can do their work on a quiescent file system.
+The 'ro' option tells the kernel to mount the root filesystem
+as 'read-only' so that filesystem consistency check programs (fsck)
+can do their work on a quiescent filesystem.
No processes can
-write to files on the file system in question until it is 'remounted'
+write to files on the filesystem in question until it is 'remounted'
as read/write capable, for example, by 'mount \-w \-n \-o remount /'.
(See also
.BR mount (8).)
-The 'rw' option tells the kernel to mount the root file system read/write.
+The 'rw' option tells the kernel to mount the root filesystem read/write.
This is the default.
-The choice between read-only and read/write can also be set using
-.BR rdev (8).
+.TP
+.B "'resume=...'"
+This tells the kernel the location of the suspend-to-disk data that you want the machine to resume from after hibernation.
+Usually, it is the same as your swap partition or file. Example:
+
+.in +4n
+.nf
+resume=/dev/hda2
+.fi
+.in
.TP
.B "'reserve=...'"
This is used to protect I/O port regions from probes.
The form of the command is:
-.IP
+
+.in +4n
+.nf
.BI reserve= iobase,extent[,iobase,extent]...
+.fi
+.in
.sp
In some machines it may be necessary to prevent device drivers from
checking for devices (auto-probing) in a specific region.
unless another boot argument explicitly specifies that it do so.
For example, the boot line
-.IP
+
+.in +4n
+.nf
reserve=0x300,32 blah=0x300
+.fi
+.in
.IP
keeps all device drivers except the driver for 'blah' from probing
0x300\-0x31f.
.TP
.B "'mem=...'"
The BIOS call defined in the PC specification that returns
-the amount of installed memory was only designed to be able
+the amount of installed memory was designed only to be able
to report up to 64MB.
Linux uses this BIOS call at boot to
determine how much memory is installed.
If you have more than 64MB of
-RAM installed, you can use this boot arg to tell Linux how much memory
+RAM installed, you can use this boot argument to tell Linux how much memory
you have.
The value is in decimal or hexadecimal (prefix 0x),
and the suffixes 'k' (times 1024) or 'M' (times 1048576) can be used.
\&'mem=0x1000000' means you have 16MB of memory, for example.
For a 96MB machine this would be 'mem=0x6000000'.
-NOTE NOTE NOTE: some machines might use the top of memory for BIOS
+.BR NOTE :
+some machines might use the top of memory for BIOS
caching or whatever, so you might not actually have up to the full
96MB addressable.
The reverse is also true: some chipsets will map
.B "'panic=N'"
By default the kernel will not reboot after a panic, but this option
will cause a kernel reboot after N seconds (if N is greater than zero).
-This panic timeout can also be set by "echo N > /proc/sys/kernel/panic".
+This panic timeout can also be set by
+
+.in +4n
+.nf
+echo N > /proc/sys/kernel/panic
+.fi
+.in
.TP
.B "'reboot=[warm|cold][,[bios|hard]]'"
(Only when
A command-line option of 'nosmp' or 'maxcpus=0' will disable SMP
activation entirely; an option 'maxcpus=N' limits the maximum number
of CPUs activated in SMP mode to N.
-.SS "Boot Arguments for Use by Kernel Developers"
+.SS Boot arguments for use by kernel developers
.TP
.B "'debug'"
Kernel messages are handed off to the kernel log daemon klogd so that they
Messages with a priority above
.I console_loglevel
are also printed on the console.
-(For these levels, see \fI<linux/kernel.h>\fP.)
+(For these levels, see
+.IR <linux/kernel.h> .)
By default this variable is set to log anything more important than
debug messages.
This boot argument will cause the kernel to also
The significance of this variable is that it
gives the granularity of the profiling: each clock tick, if the
system was executing kernel code, a counter is incremented:
-.IP
+
+.in +4n
+.nf
profile[address >> prof_shift]++;
+.fi
+.in
.sp
The raw profiling information can be read from
.IR /proc/profile .
buff_initial_age, bufferout_weight, buffermem_grace that control
kernel buffer memory management.
For kernel tuners only.
-.SS "Boot Arguments for Ramdisk Use"
+.SS Boot arguments for ramdisk use
(Only if the kernel was compiled with
.BR CONFIG_BLK_DEV_RAM .)
-In general it is a bad idea to use a ramdisk under Linux \(em
-the system will use available memory more efficiently itself.
+In general it is a bad idea to use a ramdisk under Linux\(emthe
+system will use available memory more efficiently itself.
But while booting (or while constructing boot floppies)
it is often useful to load the floppy contents into a
ramdisk.
One might also have a system in which first
-some modules (for file system or hardware) must be loaded
+some modules (for filesystem or hardware) must be loaded
before the main disk can be accessed.
In Linux 1.3.48, ramdisk handling was changed drastically.
Earlier, the memory was allocated statically, and there was
a 'ramdisk=N' parameter to tell its size.
-(This could also
-be set in the kernel image at compile time, or by use of
-.BR rdev (8).)
+(This could also be set in the kernel image at compile time.)
These days ram disks use the buffer cache, and grow dynamically.
-For a lot of information (e.g., how to use
-.BR rdev (8)
-in conjunction with the new ramdisk setup), see
-.IR /usr/src/linux/Documentation/ramdisk.txt .
+For a lot of information in conjunction with the new ramdisk
+setup, see the kernel source file
+.IR Documentation/blockdev/ramdisk.txt
+.RI ( Documentation/ramdisk.txt
+in older kernels).
There are four parameters, two boolean and two integral.
.TP
When this feature is enabled, the boot process will load the kernel
and an initial ramdisk; then the kernel converts initrd into
a "normal" ramdisk, which is mounted read-write as root device;
-then /linuxrc is executed; afterwards the "real" root file system is mounted,
-and the initrd file system is moved over to /initrd; finally
-the usual boot sequence (e.g., invocation of /sbin/init) is performed.
+then
+.I /linuxrc
+is executed; afterward the "real" root filesystem is mounted,
+and the initrd filesystem is moved over to
+.IR /initrd ;
+finally
+the usual boot sequence (e.g., invocation of
+.IR /sbin/init )
+is performed.
-For a detailed description of the initrd feature, see
-.IR /usr/src/linux/Documentation/initrd.txt .
+For a detailed description of the initrd feature, see the kernel source file
+.IR Documentation/initrd.txt .
The 'noinitrd' option tells the kernel that although it was compiled for
operation with initrd, it should not go through the above steps, but
(This device can be used only once: the data is freed as soon as
the last process that used it has closed
.IR /dev/initrd .)
-.SS "Boot Arguments for SCSI Devices"
+.SS Boot arguments for SCSI devices
General notation for this section:
.I iobase
usually be 5, 7, 9, 10, 11, 12, and 15.
The other values are usually
used for common peripherals like IDE hard disks, floppies, serial
-ports, etc.
+ports, and so on.
.I scsi-id
-- the ID that the host adapter uses to identify itself on the
LUNs not equal to zero.
Therefore, if the compile-time flag
.B CONFIG_SCSI_MULTI_LUN
-is not set, newer kernels will by default only probe LUN zero.
+is not set, newer kernels will by default probe only LUN zero.
To specify the number of probed LUNs at boot, one enters
\&'max_scsi_luns=n' as a boot arg, where n is a number between one and
.B "SCSI tape configuration"
Some boot time configuration of the SCSI tape driver can be achieved
by using the following:
-.IP
+
+.in +4n
+.nf
.BI st= buf_size[,write_threshold[,max_bufs]]
+.fi
+.in
.sp
The first two numbers are specified in units of kB.
The default
The maximum number of buffers varies
with the number of drives detected, and has a default of two.
An example usage would be:
-.IP
+
+.in +4n
+.nf
st=32,30,2
+.fi
+.in
.IP
Full details can be found in the file
.I Documentation/scsi/st.txt
(or
.I drivers/scsi/README.st
-for older kernels) in the kernel source.
+for older kernels) in the Linux kernel source.
.TP
.B "Adaptec aha151x, aha152x, aic6260, aic6360, SB16-SCSI configuration"
The aha numbers refer to cards and the aic numbers refer to the actual
The probe code for these SCSI hosts looks for an installed BIOS, and
if none is present, the probe will not find your card.
Then you will
-have to use a boot arg of the form:
-.IP
+have to use a boot argument of the form:
+
+.in +4n
+.nf
.BI aha152x= iobase[,irq[,scsi-id[,reconnect[,parity]]]]
+.fi
+.in
.IP
If the driver was compiled with debugging enabled, a sixth
value can be specified to set the debug level.
value will allow device disconnect/reconnect if a nonzero value
is used.
An example usage is as follows:
-.IP
+
+.in +4n
+.nf
aha152x=0x340,11,7,1
+.fi
+.in
.IP
Note that the parameters must be specified in order, meaning that if
you want to specify a parity setting, then you will have to specify an
These are busmastering cards,
and have parameters to set the "fairness" that is used to share
the bus with other devices.
-The boot arg looks like the following.
-.IP
+The boot argument looks like the following.
+
+.in +4n
+.nf
.BI aha1542= iobase[,buson,busoff[,dmaspeed]]
+.fi
+.in
.IP
Valid iobase values are usually one of: 0x130, 0x134, 0x230, 0x234,
0x330, 0x334.
.TP
.B "Adaptec aha274x, aha284x, aic7xxx configuration"
These boards can accept an argument of the form:
-.IP
+
+.in +4n
+.nf
.BI aic7xxx= extended,no_reset
+.fi
+.in
.IP
The
.I extended
setting up the host adapter at boot.
.TP
.B "AdvanSys SCSI Hosts configuration ('advansys=')"
-The AdvanSys driver can accept up to four i/o addresses that will be
+The AdvanSys driver can accept up to four I/O addresses that will be
probed for an AdvanSys SCSI card.
Note that these values (if used) do
not effect EISA or PCI probing in any way.
-They are only used for
+They are used only for
probing ISA and VLB cards.
In addition, if the driver has been
compiled with debugging enabled, the level of debugging output can be
level of the debugging messages to any of 16 levels of verbosity.
.TP
.B "AM53C974"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI AM53C974= host-scsi-id,target-scsi-id,max-rate,max-offset
+.fi
+.in
.TP
.B "BusLogic SCSI Hosts configuration ('BusLogic=')"
-.IP
+
+Syntax:
+.in +4n
+.nf
.BI BusLogic= N1,N2,N3,N4,N5,S1,S2,...
+.fi
+.in
.IP
For an extensive discussion of the BusLogic command line parameters,
-see
-.I /usr/src/linux/drivers/scsi/BusLogic.c
-(lines 3149-3270 in the kernel version I am looking at).
+see the kernel source file
+.IR drivers/scsi/BusLogic.c .
+.\" (lines 3149-3270 in the kernel version I am looking at).
The text
below is a very much abbreviated extract.
(NoProbe, NoProbeISA, NoSortPCI).
.TP
.B "EATA/DMA configuration"
-The default list of i/o ports to be probed can be changed by
-.IP
-.BI eata= iobase,iobase,...\fP.
+The default list of I/O ports to be probed can be changed by
+
+.in +4n
+.nf
+.BI eata= iobase,iobase,... .
+.fi
+.in
.TP
.B "Future Domain TMC-16x0 configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI fdomain= iobase,irq[,adapter_id]
+.fi
+.in
.TP
.B "Great Valley Products (GVP) SCSI controller configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI gvp11= dma_transfer_bitmask
+.fi
+.in
.TP
.B "Future Domain TMC-8xx, TMC-950 configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI tmc8xx= mem_base,irq
+.fi
+.in
.IP
The
.I mem_base
-value is the value of the memory mapped I/O region that
+value is the value of the memory-mapped I/O region that
the card uses.
This will usually be one of the following values:
0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.
.TP
.B "IN2000 configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI in2000= S
+.fi
+.in
.IP
where S is a comma-separated string of items keyword[:value].
Recognized keywords (possibly with value) are:
ioport:addr, noreset, nosync:x, period:ns, disconnect:x,
debug:x, proc:x.
-For the function of these parameters, see
-.IR /usr/src/linux/drivers/scsi/in2000.c .
+For the function of these parameters, see the kernel source file
+.IR drivers/scsi/in2000.c .
.TP
.B "NCR5380 and NCR53C400 configuration"
-The boot arg is of the form
-.IP
+The boot argument is of the form
+
+.in +4n
+.nf
.BI ncr5380= iobase,irq,dma
+.fi
+.in
.IP
or
-.IP
+
+.in +4n
+.nf
.BI ncr53c400= iobase,irq
+.fi
+.in
.IP
If the card doesn't use interrupts, then an IRQ value of 255 (0xff) will
disable interrupts.
.I Documentation/scsi/g_NCR5380.txt
(or
.I drivers/scsi/README.g_NCR5380
-for older kernels) in the kernel source.
+for older kernels) in the Linux kernel source.
.TP
.B "NCR53C8xx configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI ncr53c8xx= S
+.fi
+.in
.IP
where S is a comma-separated string of items keyword:value.
Recognized keywords are: mpar (master_parity), spar (scsi_parity),
disc (disconnection), specf (special_features), ultra (ultra_scsi),
fsn (force_sync_nego), tags (default_tags), sync (default_sync),
verb (verbose), debug (debug), burst (burst_max).
-For the function of the assigned values, see
-.IR /usr/src/linux/drivers/scsi/ncr53c8xx.c .
+For the function of the assigned values, see the kernel source file
+.IR drivers/scsi/ncr53c8xx.c .
.TP
.B "NCR53c406a configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI ncr53c406a= iobase[,irq[,fastpio]]
+.fi
+.in
.IP
Specify irq = 0 for noninterrupt driven mode.
Set fastpio = 1 for fast pio mode, 0 for slow mode.
.B "Pro Audio Spectrum configuration"
The PAS16 uses a NC5380 SCSI chip, and newer models support
jumperless configuration.
-The boot arg is of the form:
-.IP
+The boot argument is of the form:
+
+.in +4n
+.nf
.BI pas16= iobase,irq
+.fi
+.in
.IP
The only difference is that you can specify an IRQ value of 255, which
will tell the driver to work without using interrupts, albeit at a
.TP
.B "Seagate ST-0x configuration"
If your card is not detected at boot time,
-you will then have to use a boot arg of the form:
-.IP
+you will then have to use a boot argument of the form:
+
+.in +4n
+.nf
.BI st0x= mem_base,irq
+.fi
+.in
.IP
The
.I mem_base
-value is the value of the memory mapped I/O region that
+value is the value of the memory-mapped I/O region that
the card uses.
This will usually be one of the following values:
0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.
.B "Trantor T128 configuration"
These cards are also based on the NCR5380 chip, and accept the
following options:
-.IP
+
+.in +4n
+.nf
.BI t128= mem_base,irq
+.fi
+.in
.IP
The valid values for
.I mem_base
are as follows: 0xcc000, 0xc8000, 0xdc000, 0xd8000.
.TP
.B "UltraStor 14F/34F configuration"
-The default list of i/o ports to be probed can be changed by
-.IP
+The default list of I/O ports to be probed can be changed by
+
+.in +4n
+.nf
.BI eata= iobase,iobase,... .
+.fi
+.in
.TP
.B "WD7000 configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI wd7000= irq,dma,iobase
+.fi
+.in
.TP
.B "Commodore Amiga A2091/590 SCSI controller configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI wd33c93= S
+.fi
+.in
.IP
where S is a comma-separated string of options.
Recognized options are
nosync:bitmask, nodma:x, period:ns, disconnect:x, debug:x,
clock:x, next.
-For details, see
-.IR /usr/src/linux/drivers/scsi/wd33c93.c .
-.SS "Hard Disks"
+For details, see the kernel source file
+.IR drivers/scsi/wd33c93.c .
+.SS Hard disks
.TP
.B "IDE Disk/CD-ROM Driver Parameters"
The IDE driver accepts a number of parameters, which range from disk
.I Documentation/ide.txt
(or
.I drivers/block/README.ide
-for older kernels) in the kernel source for more details.
+for older kernels) in the Linux kernel source for more details.
.TP
.B "The 'hd=cyls,heads,sects[,wpcom[,irq]]' options"
These options are used to specify the physical geometry of the disk.
.B "The 'hd=noprobe' option"
Do not probe for this drive.
For example,
-.IP
+
+.in +4n
+.nf
hdb=noprobe hdb=1166,7,17
+.fi
+.in
.IP
would disable the probe, but still specify the drive geometry so
that it would be registered as a valid block device, and hence
.B "Standard ST-506 Disk Driver Options ('hd=')"
The standard disk driver can accept geometry arguments for the disks
similar to the IDE driver.
-Note however that it only expects three
+Note however that it expects only three
values (C/H/S); any more or any less and it will silently ignore you.
-Also, it only accepts 'hd=' as an argument, that is, 'hda='
+Also, it accepts only 'hd=' as an argument, that is, 'hda='
and so on are not valid here.
The format is as follows:
-.IP
+
+.in +4n
+.nf
hd=cyls,heads,sects
+.fi
+.in
.IP
If there are two disks installed, the above is repeated with the
geometry parameters of the second disk.
.TP
.B "XT Disk Driver Options ('xd=')"
-If you are unfortunate enough to be using one of these old 8 bit cards
-that move data at a whopping 125kB/s then here is the scoop.
-If the card is not recognized, you will have to use a boot arg of the form:
-.IP
+If you are unfortunate enough to be using one of these old 8-bit cards
+that move data at a whopping 125kB/s, then here is the scoop.
+If the card is not recognized,
+you will have to use a boot argument of the form:
+
+.in +4n
+.nf
xd=type,irq,iobase,dma_chan
+.fi
+.in
.IP
The type value specifies the particular manufacturer of the card,
overriding autodetection.
Here is an
example usage for a WD1002 controller with the BIOS disabled/removed,
using the 'default' XT controller parameters:
-.IP
+
+.in +4n
+.nf
xd=2,5,0x320,3
+.fi
+.in
.TP
.B "Syquest's EZ* removable disks"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI ez= iobase[,irq[,rep[,nybble]]]
-.SS "IBM MCA Bus Devices"
-See also
-.IR /usr/src/linux/Documentation/mca.txt .
+.fi
+.in
+.SS IBM MCA bus devices
+See also the kernel source file
+.IR Documentation/mca.txt .
.TP
.B "PS/2 ESDI hard disks"
It is possible to specify the desired geometry at boot time:
-.IP
+
+.in +4n
+.nf
.BI ed= cyls,heads,sectors.
+.fi
+.in
.IP
For a ThinkPad-720, add the option
-.IP
+
+.in +4n
+.nf
.BR tp720=1 .
+.fi
+.in
.TP
.B "IBM Microchannel SCSI Subsystem configuration"
-.IP
+Syntax:
+
+.in +4n
+.nf
.BI ibmmcascsi= N
+.fi
+.in
.IP
-where N is the \fIpun\fP (SCSI ID) of the subsystem.
+where N is the
+.I pun
+(SCSI ID) of the subsystem.
.TP
.B "The Aztech Interface"
The syntax for this type of card is:
-.IP
+
+.in +4n
+.nf
aztcd=iobase[,magic_number]
+.fi
+.in
.IP
-If you set the magic_number to 0x79 then the driver will try and run
+If you set the magic_number to 0x79, then the driver will try and run
anyway in the event of an unknown firmware version.
All other values
are ignored.
.TP
.B "Parallel port CD-ROM drives"
Syntax:
-.IP
+
+.in +4n
+.nf
pcd.driveN=prt,pro,uni,mod,slv,dly
-.br
pcd.nice=nice
+.fi
+.in
.IP
where 'port' is the base address, 'pro' is the protocol number, 'uni'
is the unit selector (for chained devices), 'mod' is the mode (or \-1
This CD-ROM interface is found on some of the Pro Audio Spectrum sound
cards, and other Sony supplied interface cards.
The syntax is as follows:
-.IP
+
+.in +4n
+.nf
cdu31a=iobase,[irq[,is_pas_card]]
+.fi
+.in
.IP
Specifying an IRQ value of zero tells the driver that hardware
interrupts aren't supported (as on some PAS cards).
.TP
.B "The CDU-535 Sony Interface"
The syntax for this CD-ROM interface is:
-.IP
+
+.in +4n
+.nf
sonycd535=iobase[,irq]
+.fi
+.in
.IP
A zero can be used for the I/O base as a 'placeholder' if one wishes
to specify an IRQ value.
.TP
.B "The GoldStar Interface"
The syntax for this CD-ROM interface is:
-.IP
+
+.in +4n
+.nf
gscd=iobase
+.fi
+.in
.TP
.B "The ISP16 CD-ROM Interface"
Syntax:
-.IP
+
+.in +4n
+.nf
isp16=[iobase[,irq[,dma[,type]]]]
+.fi
+.in
.IP
-(three integers and a string).
+(Three integers and a string.)
If the type is given as 'noisp16',
the interface will not be configured.
Other recognized types
.TP
.B "The Mitsumi Standard Interface"
The syntax for this CD-ROM interface is:
-.IP
+
+.in +4n
+.nf
mcd=iobase,[irq[,wait_value]]
+.fi
+.in
.IP
The
.I wait_value
.B "The Mitsumi XA/MultiSession Interface"
This is for the same hardware as above, but the driver has extended features.
Syntax:
-.IP
+
+.in +4n
+.nf
mcdx=iobase[,irq]
+.fi
+.in
.TP
.B "The Optics Storage Interface"
The syntax for this type of card is:
-.IP
+
+.in +4n
+.nf
optcd=iobase
+.fi
+.in
.TP
.B "The Phillips CM206 Interface"
The syntax for this type of card is:
-.IP
+
+.in +4n
+.nf
cm206=[iobase][,irq]
+.fi
+.in
.IP
The driver assumes numbers between 3 and 11 are IRQ values, and
numbers between 0x300 and 0x370 are I/O ports, so you can specify one,
.TP
.B "The Sanyo Interface"
The syntax for this type of card is:
-.IP
+
+.in +4n
+.nf
sjcd=iobase[,irq[,dma_channel]]
+.fi
+.in
.TP
.B "The SoundBlaster Pro Interface"
The syntax for this type of card is:
-.IP
+
+.in +4n
+.nf
sbpcd=iobase,type
+.fi
+.in
.IP
where type is one of the following (case sensitive) strings:
\&'SoundBlaster', 'LaserMate', or 'SPEA'.
The I/O base is that of the
CD-ROM interface, and not that of the sound portion of the card.
-.SS "Ethernet Devices"
+.SS Ethernet devices
Different drivers make use of different parameters, but they all at
least share having an IRQ, an I/O port base value, and a name.
In its most generic form, it looks something like this:
-.IP
+
+.in +4n
+.nf
ether=irq,iobase[,param_1[,...param_8]],name
-.IP
+.fi
+.in
+
The first nonnumeric argument is taken as the name.
The param_n values (if applicable) usually have different meanings for each
different card/driver.
and the like.
The most common use of this parameter is to force probing for a second
-ethercard, as the default is to only probe for one.
+ethercard, as the default is to probe only for one.
This can be accomplished with a simple:
-.IP
+
+.in +4n
+.nf
ether=0,0,eth1
-.IP
+.fi
+.in
+
Note that the values of zero for the IRQ and I/O base in the above
example tell the driver(s) to autoprobe.
of the param_n values where used.
Interested readers should refer to
the section in that document on their particular card.
-.SS "The Floppy Disk Driver"
+.SS The floppy disk driver
There are many floppy driver options, and they are all listed in
.I Documentation/floppy.txt
(or
.I drivers/block/README.fd
-for older kernels) in the kernel source.
+for older kernels) in the Linux kernel source.
This information is taken directly
from that file.
.TP
be an interaction between video and floppy.
The unexpected interrupts
only affect performance, and can safely be ignored.)
-.SS "The Sound Driver"
-The sound driver can also accept boot args to override the compiled in
+.SS The sound driver
+The sound driver can also accept boot arguments to override the compiled in
values.
This is not recommended, as it is rather complex.
-It is described in the kernel source file
+It is described in the Linux kernel source file
.IR Documentation/sound/oss/README.OSS
.RI ( drivers/sound/Readme.linux
in older kernel versions).
It accepts
-a boot arg of the form:
-.IP
+a boot argument of the form:
+
+.in +4n
+.nf
sound=device1[,device2[,device3...[,device10]]]
+.fi
+.in
.IP
where each deviceN value is of the following format 0xTaaaId and the
bytes are used as follows:
As you can see it gets pretty messy, and you are better off to compile
in your own personal values as recommended.
-Using a boot arg of
+Using a boot argument of
\&'sound=0' will disable the sound driver entirely.
-.SS "ISDN Drivers"
+.SS ISDN drivers
.TP
.B "The ICN ISDN driver"
Syntax:
-.IP
+
+.in +4n
+.nf
icn=iobase,membase,icn_id1,icn_id2
+.fi
+.in
.IP
where icn_id1,icn_id2 are two strings used to identify the
card in kernel messages.
.TP
.B "The PCBIT ISDN driver"
Syntax:
-.IP
+
+.in +4n
+.nf
pcbit=membase1,irq1[,membase2,irq2]
+.fi
+.in
.IP
where membaseN is the shared memory base of the N'th card, and irqN is
the interrupt setting of the N'th card.
.TP
.B "The Teles ISDN driver"
Syntax:
-.IP
+
+.in +4n
+.nf
teles=iobase,irq,membase,protocol,teles_id
+.fi
+.in
.IP
-where iobase is the i/o port address of the card, membase is the
+where iobase is the I/O port address of the card, membase is the
shared memory base address of the card, irq is the interrupt channel
the card uses, and teles_id is the unique ASCII string identifier.
-.SS "Serial Port Drivers"
+.SS Serial port drivers
.TP
.B "The RISCom/8 Multiport Serial Driver ('riscom8=')"
Syntax:
-.IP
+
+.in +4n
+.nf
riscom=iobase1[,iobase2[,iobase3[,iobase4]]]
+.fi
+.in
.IP
-More details can be found in
-.IR /usr/src/linux/Documentation/riscom8.txt .
+More details can be found in the kernel source file
+.IR Documentation/riscom8.txt .
.TP
.B "The DigiBoard Driver ('digi=')"
If this option is used, it should have precisely six parameters.
Syntax:
-.IP
+
+.in +4n
+.nf
digi=status,type,altpin,numports,iobase,membase
+.fi
+.in
.IP
The parameters maybe given as integers, or as strings.
If strings are used, then iobase and membase should be given
iobase (I/O Port where card is configured (in HEX)),
membase (base of memory window (in HEX)).
Thus, the following two boot prompt arguments are equivalent:
-.IP
+
+.in +4n
+.nf
digi=E,PC/Xi,D,16,200,D0000
-.br
digi=1,0,0,16,0x200,851968
+.fi
+.in
.IP
-More details can be found in
-.IR /usr/src/linux/Documentation/digiboard.txt .
+More details can be found in the kernel source file
+.IR Documentation/digiboard.txt .
.TP
.B "The Baycom Serial/Parallel Radio Modem"
Syntax:
-.IP
+
+.in +4n
+.nf
baycom=iobase,irq,modem
+.fi
+.in
.IP
There are precisely 3 parameters; for several cards, give
several 'baycom=' commands.
.I Documentation/networking/baycom.txt
(or
.I drivers/net/README.baycom
-for older kernels) in the kernel source.
+for older kernels) in the Linux kernel source.
.TP
.B "Soundcard radio modem driver"
Syntax:
-.IP
+
+.in +4n
+.nf
soundmodem=iobase,irq,dma[,dma2[,serio[,pario]]],0,mode
+.fi
+.in
.IP
All parameters except the last are integers;
the dummy 0 is required because of a bug in the setup code.
The mode parameter is a string with syntax hw:modem,
-where hw is one of sbc, wss, wssfdx and modem is one of
-afsk1200, fsk9600.
-.SS "The Line Printer Driver"
+where hw is one of sbc, wss, or wssfdx, and modem is one of
+afsk1200 or fsk9600.
+.SS The line printer driver
.TP
.B "'lp='"
+.br
Syntax:
-.IP
+
+.in +4n
+.nf
lp=0
-.br
lp=auto
-.br
lp=reset
-.br
lp=port[,port...]
+.fi
+.in
.IP
You can tell the printer driver what ports to use and what ports not
to use.
.TP
.B "WDT500/501 driver"
Syntax:
-.IP
+
+.in +4n
+.nf
wdt=io,irq
-.SS "Mouse Drivers"
+.fi
+.in
+.SS Mouse drivers
.TP
.B "'bmouse=irq'"
-The busmouse driver only accepts one parameter, that being the
+The busmouse driver accepts only one parameter, that being the
hardware IRQ value to be used.
.TP
.B "'msmouse=irq'"
And precisely the same is true for the msmouse driver.
.TP
.B "ATARI mouse setup"
-.IP
+Syntax:
+
+.in +4n
+.nf
atamouse=threshold[,y-threshold]
+.fi
+.in
.IP
If only one argument is given, it is used for both
x-threshold and y-threshold.
Otherwise, the first argument
is the x-threshold, and the second the y-threshold.
These values must lie between 1 and 20 (inclusive); the default is 2.
-.SS "Video Hardware"
+.SS Video hardware
.TP
.B "'no-scroll'"
This option tells the console driver not to use hardware scroll
Braille machines.
.\" .SH AUTHORS
.\" Linus Torvalds (and many others)
-.SH "SEE ALSO"
-.BR lilo.conf (5),
+.SH SEE ALSO
.BR klogd (8),
-.BR lilo (8),
-.BR mount (8),
-.BR rdev (8)
+.BR mount (8)
Large parts of this man page have been derived from the
Boot Parameter HOWTO (version 1.0.1) written by Paul Gortmaker.
More information may be found in this (or a more recent) HOWTO.
-An up-to-date source of information is
-.IR /usr/src/linux/Documentation/kernel-parameters.txt .
+An up-to-date source of information is the kernel source file
+.IR Documentation/kernel-parameters.txt .
+.SH COLOPHON
+This page is part of release 3.79 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
OSDN Git Service
