mirror of https://github.com/mkerrisk/man-pages
Reformat headings.
This commit is contained in:
Michael Kerrisk
parent
492562689a
commit
bebbbd1ff7
401
man7/bootparam.7
401
man7/bootparam.7
|
|
@ -24,7 +24,7 @@
|
|||
.\" (dated v1.0.1, 15/08/95).
|
||||
.\" Major update, aeb, 970114.
|
||||
.\"
|
||||
.TH BOOTPARAM 7 1995-01-14 "Linux" "Linux Programmer's Manual"
|
||||
.TH BOOTPARAM 7 1997-01-14 "Linux" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
bootparam \- Introduction to boot time parameters of the Linux kernel
|
||||
.SH DESCRIPTION
|
||||
|
|
@ -68,7 +68,7 @@ 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.
|
||||
.SH "THE ARGUMENT LIST"
|
||||
.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:
|
||||
|
|
@ -115,8 +115,10 @@ 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
|
||||
your system to see what arguments it accepts.
|
||||
.SH "GENERAL NON-DEVICE SPECIFIC BOOT ARGS"
|
||||
.SS "`init=...'"
|
||||
.SS "GENERAL NON-DEVICE SPECIFIC BOOT ARGS"
|
||||
.TP
|
||||
.B "`init=...'"
|
||||
.br
|
||||
This sets the initial command to be executed by the kernel.
|
||||
If this is not set, or cannot be found, the kernel will try
|
||||
.IR /sbin/init ,
|
||||
|
|
@ -127,16 +129,19 @@ then
|
|||
then
|
||||
.IR /bin/sh
|
||||
and panic if all of this fails.
|
||||
.SS "`nfsaddrs=...'"
|
||||
.TP
|
||||
.B "`nfsaddrs=...'"
|
||||
This sets the nfs boot address to the given string.
|
||||
This boot address is used in case of a net boot.
|
||||
.SS "`nfsroot=...'"
|
||||
.TP
|
||||
.B "`nfsroot=...'"
|
||||
This sets the nfs root name to the given string.
|
||||
If this string
|
||||
does not begin with '/' or ',' or a digit, then it is prefixed by
|
||||
`/tftpboot/'.
|
||||
This root name is used in case of a net boot.
|
||||
.SS "`no387'"
|
||||
.TP
|
||||
.B "`no387'"
|
||||
(Only when CONFIG_BUGi386 is defined.)
|
||||
Some i387 coprocessor chips have bugs that show up when used in 32 bit
|
||||
protected mode.
|
||||
|
|
@ -146,7 +151,8 @@ Using the `no387' boot arg 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!
|
||||
.SS "`no-hlt'"
|
||||
.TP
|
||||
.B "`no-hlt'"
|
||||
(Only when CONFIG_BUGi386 is defined.)
|
||||
Some of the early i486DX-100 chips have a problem with the `hlt'
|
||||
instruction, in that they can't reliably return to operating mode
|
||||
|
|
@ -156,7 +162,8 @@ Linux to just run an infinite loop when there is nothing else to do,
|
|||
and to not halt the CPU.
|
||||
This allows people with these broken chips
|
||||
to use Linux.
|
||||
.SS "`root=...'"
|
||||
.TP
|
||||
.B "`root=...'"
|
||||
This argument tells the kernel what device is to be used as the root
|
||||
filesystem while booting.
|
||||
The default of this setting is determined
|
||||
|
|
@ -191,7 +198,8 @@ 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
|
||||
alternative.)
|
||||
.SS "`ro' and `rw'"
|
||||
.TP
|
||||
.B "`ro' and `rw'"
|
||||
The `ro' option tells the kernel to mount the root filesystem
|
||||
as `readonly' so that filesystem consistency check programs (fsck)
|
||||
can do their work on a quiescent file system.
|
||||
|
|
@ -206,12 +214,13 @@ This is the default.
|
|||
|
||||
The choice between read-only and read/write can also be set using
|
||||
.BR rdev (8).
|
||||
.SS "`reserve=...'"
|
||||
.TP
|
||||
.B "`reserve=...'"
|
||||
This is used to protect I/O port regions from probes.
|
||||
The form of the command is:
|
||||
.IP
|
||||
.BI reserve= iobase,extent[,iobase,extent]...
|
||||
.LP
|
||||
.sp
|
||||
In some machines it may be necessary to prevent device drivers from
|
||||
checking for devices (auto-probing) in a specific region.
|
||||
This may be
|
||||
|
|
@ -227,10 +236,11 @@ unless another boot argument explicitly specifies that it do so.
|
|||
For example, the boot line
|
||||
.IP
|
||||
reserve=0x300,32 blah=0x300
|
||||
.LP
|
||||
.IP
|
||||
keeps all device drivers except the driver for `blah' from probing
|
||||
0x300-0x31f.
|
||||
.SS "`mem=...'"
|
||||
.TP
|
||||
.B "`mem=...'"
|
||||
The BIOS call defined in the PC specification that returns
|
||||
the amount of installed memory was only designed to be able
|
||||
to report up to 64MB.
|
||||
|
|
@ -263,11 +273,13 @@ surely eventually.''
|
|||
You can also use the boot argument `mem=nopentium' to turn off 4 MB
|
||||
page tables on kernels configured for IA32 systems with a pentium or newer
|
||||
CPU.
|
||||
.SS "`panic=N'"
|
||||
.TP
|
||||
.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 > 0).
|
||||
This panic timeout can also be set by "echo N > /proc/sys/kernel/panic".
|
||||
.SS "`reboot=[warm|cold][,[bios|hard]]'"
|
||||
.TP
|
||||
.B "`reboot=[warm|cold][,[bios|hard]]'"
|
||||
(Only when CONFIG_BUGi386 is defined.)
|
||||
Since 2.0.22 a reboot is by default a cold reboot.
|
||||
One asks for the old default with `reboot=warm'.
|
||||
|
|
@ -279,13 +291,15 @@ to pulse the reset line low, but there is at least one type
|
|||
of motherboard where that doesn't work.
|
||||
The option `reboot=bios' will
|
||||
instead jump through the BIOS.
|
||||
.SS "`nosmp'" and "`maxcpus=N'"
|
||||
.TP
|
||||
.B "`nosmp'" and "`maxcpus=N'"
|
||||
(Only when __SMP__ is defined.)
|
||||
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.
|
||||
.SH "BOOT ARGUMENTS FOR USE BY KERNEL DEVELOPERS"
|
||||
.SS "`debug'"
|
||||
.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
|
||||
may be logged to disk.
|
||||
Messages with a priority above
|
||||
|
|
@ -300,7 +314,8 @@ The console loglevel can also be set at run time via an option
|
|||
to klogd.
|
||||
See
|
||||
.BR klogd (8).
|
||||
.SS "`profile=N'"
|
||||
.TP
|
||||
.B "`profile=N'"
|
||||
It is possible to enable a kernel profiling function,
|
||||
if one wishes to find out where the kernel is spending its CPU cycles.
|
||||
Profiling is enabled by setting the variable
|
||||
|
|
@ -317,24 +332,26 @@ gives the granularity of the profiling: each clock tick, if the
|
|||
system was executing kernel code, a counter is incremented:
|
||||
.IP
|
||||
profile[address >> prof_shift]++;
|
||||
.LP
|
||||
.sp
|
||||
The raw profiling information can be read from
|
||||
.IR /proc/profile .
|
||||
Probably you'll want to use a tool such as readprofile.c to digest it.
|
||||
Writing to
|
||||
.I /proc/profile
|
||||
will clear the counters.
|
||||
.SS "`swap=N1,N2,N3,N4,N5,N6,N7,N8'"
|
||||
.TP
|
||||
.B "`swap=N1,N2,N3,N4,N5,N6,N7,N8'"
|
||||
Set the eight parameters max_page_age, page_advance, page_decline,
|
||||
page_initial_age, age_cluster_fract, age_cluster_min, pageout_weight,
|
||||
bufferout_weight that control the kernel swap algorithm.
|
||||
For kernel tuners only.
|
||||
.SS "`buff=N1,N2,N3,N4,N5,N6'"
|
||||
.TP
|
||||
.B "`buff=N1,N2,N3,N4,N5,N6'"
|
||||
Set the six parameters max_buff_age, buff_advance, buff_decline,
|
||||
buff_initial_age, bufferout_weight, buffermem_grace that control
|
||||
kernel buffer memory management.
|
||||
For kernel tuners only.
|
||||
.SH "BOOT ARGUMENTS FOR RAMDISK USE"
|
||||
.SS "BOOT ARGUMENTS FOR RAMDISK USE"
|
||||
(Only if the kernel was compiled with 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.
|
||||
|
|
@ -358,23 +375,28 @@ in conjunction with the new ramdisk setup), see
|
|||
.IR /usr/src/linux/Documentation/ramdisk.txt .
|
||||
|
||||
There are four parameters, two boolean and two integral.
|
||||
.SS "`load_ramdisk=N'"
|
||||
.TP
|
||||
.B "`load_ramdisk=N'"
|
||||
If N=1, do load a ramdisk.
|
||||
If N=0, do not load a ramdisk.
|
||||
(This is the default.)
|
||||
.SS "`prompt_ramdisk=N'"
|
||||
.TP
|
||||
.B "`prompt_ramdisk=N'"
|
||||
If N=1, do prompt for insertion of the floppy.
|
||||
(This is the default.)
|
||||
If N=0, do not prompt.
|
||||
(Thus, this parameter is never needed.)
|
||||
.SS "`ramdisk_size=N' or (obsolete) `ramdisk=N'"
|
||||
.TP
|
||||
.B "`ramdisk_size=N' or (obsolete) `ramdisk=N'"
|
||||
Set the maximal size of the ramdisk(s) to N kB.
|
||||
The default is 4096 (4 MB).
|
||||
.SS "`ramdisk_start=N'"
|
||||
.TP
|
||||
.B "`ramdisk_start=N'"
|
||||
Sets the starting block number (the offset on the floppy where
|
||||
the ramdisk starts) to N.
|
||||
This is needed in case the ramdisk follows a kernel image.
|
||||
.SS "`noinitrd'"
|
||||
.TP
|
||||
.B "`noinitrd'"
|
||||
(Only if the kernel was compiled with CONFIG_BLK_DEV_RAM
|
||||
and CONFIG_BLK_DEV_INITRD.)
|
||||
These days it is possible to compile the kernel to use initrd.
|
||||
|
|
@ -395,7 +417,7 @@ leave the initrd data under
|
|||
(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 .)
|
||||
.SH "BOOT ARGUMENTS FOR SCSI DEVICES"
|
||||
.SS "BOOT ARGUMENTS FOR SCSI DEVICES"
|
||||
General notation for this section:
|
||||
|
||||
.I iobase
|
||||
|
|
@ -426,7 +448,8 @@ Specifying a one indicates parity checking is enabled,
|
|||
and a zero disables parity checking.
|
||||
Again, not all adapters will support selection of parity
|
||||
behavior as a boot argument.
|
||||
.SS "`max_scsi_luns=...'"
|
||||
.TP
|
||||
.B "`max_scsi_luns=...'"
|
||||
A SCSI device can have a number of `sub-devices' contained within
|
||||
itself.
|
||||
The most common example is one of the new SCSI CD-ROMs that
|
||||
|
|
@ -448,12 +471,13 @@ To specify the number of probed LUNs at boot, one enters
|
|||
eight.
|
||||
To avoid problems as described above, one would use n=1 to
|
||||
avoid upsetting such broken devices.
|
||||
.SS "SCSI tape configuration"
|
||||
.TP
|
||||
.B "SCSI tape configuration"
|
||||
Some boot time configuration of the SCSI tape driver can be achieved
|
||||
by using the following:
|
||||
.IP
|
||||
.BI st= buf_size[,write_threshold[,max_bufs]]
|
||||
.LP
|
||||
.sp
|
||||
The first two numbers are specified in units of kB.
|
||||
The default
|
||||
.I buf_size
|
||||
|
|
@ -468,10 +492,11 @@ with the number of drives detected, and has a default of two.
|
|||
An example usage would be:
|
||||
.IP
|
||||
st=32,30,2
|
||||
.LP
|
||||
.IP
|
||||
Full details can be found in the README.st file that is in the scsi
|
||||
directory of the kernel source tree.
|
||||
.SS "Adaptec aha151x, aha152x, aic6260, aic6360, SB16-SCSI configuration"
|
||||
.TP
|
||||
.B "Adaptec aha151x, aha152x, aic6260, aic6360, SB16-SCSI configuration"
|
||||
The aha numbers refer to cards and the aic numbers refer to the actual
|
||||
SCSI chip on these type of cards, including the Soundblaster-16 SCSI.
|
||||
|
||||
|
|
@ -481,7 +506,7 @@ Then you will
|
|||
have to use a boot arg of the form:
|
||||
.IP
|
||||
.BI aha152x= iobase[,irq[,scsi-id[,reconnect[,parity]]]]
|
||||
.LP
|
||||
.IP
|
||||
If the driver was compiled with debugging enabled, a sixth
|
||||
value can be specified to set the debug level.
|
||||
|
||||
|
|
@ -492,11 +517,12 @@ is used.
|
|||
An example usage is as follows:
|
||||
.IP
|
||||
aha152x=0x340,11,7,1
|
||||
.LP
|
||||
.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
|
||||
iobase, irq, scsi-id and reconnect value as well.
|
||||
.SS "Adaptec aha154x configuration"
|
||||
.TP
|
||||
.B "Adaptec aha154x configuration"
|
||||
The aha1542 series cards have an i82077 floppy controller onboard,
|
||||
while the aha1540 series cards do not.
|
||||
These are busmastering cards,
|
||||
|
|
@ -505,7 +531,7 @@ the bus with other devices.
|
|||
The boot arg looks like the following.
|
||||
.IP
|
||||
.BI aha1542= iobase[,buson,busoff[,dmaspeed]]
|
||||
.LP
|
||||
.IP
|
||||
Valid iobase values are usually one of: 0x130, 0x134, 0x230, 0x234,
|
||||
0x330, 0x334.
|
||||
Clone cards may permit other values.
|
||||
|
|
@ -528,11 +554,12 @@ soft-configuration, older cards use jumpers.
|
|||
You can use values up to
|
||||
10MB/s assuming that your motherboard is capable of handling it.
|
||||
Experiment with caution if using values over 5MB/s.
|
||||
.SS "Adaptec aha274x, aha284x, aic7xxx configuration"
|
||||
.TP
|
||||
.B "Adaptec aha274x, aha284x, aic7xxx configuration"
|
||||
These boards can accept an argument of the form:
|
||||
.IP
|
||||
.BI aic7xxx= extended,no_reset
|
||||
.LP
|
||||
.IP
|
||||
The
|
||||
.I extended
|
||||
value, if non-zero, indicates that extended translation for large
|
||||
|
|
@ -541,7 +568,8 @@ The
|
|||
.I no_reset
|
||||
value, if non-zero, tells the driver not to reset the SCSI bus when
|
||||
setting up the host adapter at boot.
|
||||
.SS "AdvanSys SCSI Hosts configuration (`advansys=')"
|
||||
.TP
|
||||
.B "AdvanSys SCSI Hosts configuration (`advansys=')"
|
||||
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
|
||||
|
|
@ -553,13 +581,15 @@ compiled with debugging enabled, the level of debugging output can be
|
|||
set by adding an 0xdeb[0-f] parameter.
|
||||
The 0-f allows setting the
|
||||
level of the debugging messages to any of 16 levels of verbosity.
|
||||
.SS "AM53C974"
|
||||
.TP
|
||||
.B "AM53C974"
|
||||
.IP
|
||||
.BI AM53C974= host-scsi-id,target-scsi-id,max-rate,max-offset
|
||||
.SS "BusLogic SCSI Hosts configuration (`BusLogic=')"
|
||||
.TP
|
||||
.B "BusLogic SCSI Hosts configuration (`BusLogic=')"
|
||||
.IP
|
||||
.BI BusLogic= N1,N2,N3,N4,N5,S1,S2,...
|
||||
.LP
|
||||
.IP
|
||||
For an extensive discussion of the BusLogic command line parameters,
|
||||
see
|
||||
.IR /usr/src/linux/drivers/scsi/BusLogic.c
|
||||
|
|
@ -584,55 +614,62 @@ The string options are used to provide control over Tagged Queuing
|
|||
Error Recovery (ER:Default, ER:HardReset, ER:BusDeviceReset,
|
||||
ER:None, ER:<Per-Target-Spec>), and over Host Adapter Probing
|
||||
(NoProbe, NoProbeISA, NoSortPCI).
|
||||
.SS "EATA/DMA configuration"
|
||||
.TP
|
||||
.B "EATA/DMA configuration"
|
||||
The default list of i/o ports to be probed can be changed by
|
||||
.IP
|
||||
.BI eata= iobase,iobase,... .
|
||||
.SS "Future Domain TMC-16x0 configuration"
|
||||
.TP
|
||||
.B "Future Domain TMC-16x0 configuration"
|
||||
.IP
|
||||
.BI fdomain= iobase,irq[,adapter_id]
|
||||
.SS "Great Valley Products (GVP) SCSI controller configuration"
|
||||
.TP
|
||||
.B "Great Valley Products (GVP) SCSI controller configuration"
|
||||
.IP
|
||||
.BI gvp11= dma_transfer_bitmask
|
||||
.SS "Future Domain TMC-8xx, TMC-950 configuration"
|
||||
.TP
|
||||
.B "Future Domain TMC-8xx, TMC-950 configuration"
|
||||
.IP
|
||||
.BI tmc8xx= mem_base,irq
|
||||
.LP
|
||||
.IP
|
||||
The
|
||||
.I mem_base
|
||||
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.
|
||||
.SS "IN2000 configuration"
|
||||
.TP
|
||||
.B "IN2000 configuration"
|
||||
.IP
|
||||
.BI in2000= S
|
||||
.LP
|
||||
.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 .
|
||||
.SS "NCR5380 and NCR53C400 configuration"
|
||||
.TP
|
||||
.B "NCR5380 and NCR53C400 configuration"
|
||||
The boot arg is of the form
|
||||
.IP
|
||||
.BI ncr5380= iobase,irq,dma
|
||||
.LP
|
||||
.IP
|
||||
or
|
||||
.IP
|
||||
.BI ncr53c400= iobase,irq
|
||||
.LP
|
||||
.IP
|
||||
If the card doesn't use interrupts, then an IRQ value of 255 (0xff) will
|
||||
disable interrupts.
|
||||
An IRQ value of 254 means to autoprobe.
|
||||
More
|
||||
details can be found in the file
|
||||
.IR /usr/src/linux/drivers/scsi/README.g_NCR5380 .
|
||||
.SS "NCR53C8xx configuration"
|
||||
.TP
|
||||
.B "NCR53C8xx configuration"
|
||||
.IP
|
||||
.BI ncr53c8xx= S
|
||||
.LP
|
||||
.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),
|
||||
|
|
@ -640,63 +677,71 @@ 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 .
|
||||
.SS "NCR53c406a configuration"
|
||||
.TP
|
||||
.B "NCR53c406a configuration"
|
||||
.IP
|
||||
.BI ncr53c406a= iobase[,irq[,fastpio]]
|
||||
.LP
|
||||
.IP
|
||||
Specify irq = 0 for non-interrupt driven mode.
|
||||
Set fastpio = 1 for fast pio mode, 0 for slow mode.
|
||||
.SS "Pro Audio Spectrum configuration"
|
||||
.TP
|
||||
.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
|
||||
.BI pas16= iobase,irq
|
||||
.LP
|
||||
.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
|
||||
performance loss.
|
||||
The iobase is usually 0x388.
|
||||
.SS "Seagate ST-0x configuration"
|
||||
.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
|
||||
.BI st0x= mem_base,irq
|
||||
.LP
|
||||
.IP
|
||||
The
|
||||
.I mem_base
|
||||
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.
|
||||
.SS "Trantor T128 configuration"
|
||||
.TP
|
||||
.B "Trantor T128 configuration"
|
||||
These cards are also based on the NCR5380 chip, and accept the
|
||||
following options:
|
||||
.IP
|
||||
.BI t128= mem_base,irq
|
||||
.LP
|
||||
.IP
|
||||
The valid values for
|
||||
.I mem_base
|
||||
are as follows: 0xcc000, 0xc8000, 0xdc000, 0xd8000.
|
||||
.SS "UltraStor 14F/34F configuration"
|
||||
.TP
|
||||
.B "UltraStor 14F/34F configuration"
|
||||
The default list of i/o ports to be probed can be changed by
|
||||
.IP
|
||||
.BI eata= iobase,iobase,... .
|
||||
.SS "WD7000 configuration"
|
||||
.TP
|
||||
.B "WD7000 configuration"
|
||||
.IP
|
||||
.BI wd7000= irq,dma,iobase
|
||||
.SS "Commodore Amiga A2091/590 SCSI controller configuration"
|
||||
.TP
|
||||
.B "Commodore Amiga A2091/590 SCSI controller configuration"
|
||||
.IP
|
||||
.BI wd33c93= S
|
||||
.LP
|
||||
.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 .
|
||||
.SH "HARD DISKS"
|
||||
.SS "IDE Disk/CD-ROM Driver Parameters"
|
||||
.SS "HARD DISKS"
|
||||
.TP
|
||||
.B "IDE Disk/CD-ROM Driver Parameters"
|
||||
The IDE driver accepts a number of parameters, which range from disk
|
||||
geometry specifications, to support for broken controller chips.
|
||||
Drive specific options are specified by using `hdX=' with X in `a'-`h'.
|
||||
|
|
@ -711,7 +756,8 @@ For the following discussions,
|
|||
the `hd=' option will be cited for brevity.
|
||||
See the file
|
||||
README.ide in linux/drivers/block for more details.
|
||||
.SS "The `hd=cyls,heads,sects[,wpcom[,irq]]' options"
|
||||
.TP
|
||||
.B "The `hd=cyls,heads,sects[,wpcom[,irq]]' options"
|
||||
These options are used to specify the physical geometry of the disk.
|
||||
Only the first three values are required.
|
||||
The cylinder/head/sectors
|
||||
|
|
@ -721,35 +767,41 @@ is ignored for IDE disks.
|
|||
The IRQ value specified will be the IRQ
|
||||
used for the interface that the drive resides on, and is not really a
|
||||
drive specific parameter.
|
||||
.SS "The `hd=serialize' option"
|
||||
.TP
|
||||
.B "The `hd=serialize' option"
|
||||
The dual IDE interface CMD-640 chip is broken as designed such that
|
||||
when drives on the secondary interface are used at the same time as
|
||||
drives on the primary interface, it will corrupt your data.
|
||||
Using this
|
||||
option tells the driver to make sure that both interfaces are never
|
||||
used at the same time.
|
||||
.SS "The `hd=dtc2278' option"
|
||||
.TP
|
||||
.B "The `hd=dtc2278' option"
|
||||
This option tells the driver that you have a DTC-2278D IDE interface.
|
||||
The driver then tries to do DTC specific operations to enable the
|
||||
second interface and to enable faster transfer modes.
|
||||
.SS "The `hd=noprobe' option"
|
||||
.TP
|
||||
.B "The `hd=noprobe' option"
|
||||
Do not probe for this drive.
|
||||
For example,
|
||||
.IP
|
||||
hdb=noprobe hdb=1166,7,17
|
||||
.LP
|
||||
.IP
|
||||
would disable the probe, but still specify the drive geometry so
|
||||
that it would be registered as a valid block device, and hence
|
||||
usable.
|
||||
.SS "The `hd=nowerr' option"
|
||||
.TP
|
||||
.B "The `hd=nowerr' option"
|
||||
Some drives apparently have the WRERR_STAT bit stuck on permanently.
|
||||
This enables a work-around for these broken devices.
|
||||
.SS "The `hd=cdrom' option"
|
||||
.TP
|
||||
.B "The `hd=cdrom' option"
|
||||
This tells the IDE driver that there is an ATAPI compatible CD-ROM
|
||||
attached in place of a normal IDE hard disk.
|
||||
In most cases the CD-ROM
|
||||
is identified automatically, but if it isn't then this may help.
|
||||
.SS "Standard ST-506 Disk Driver Options (`hd=')"
|
||||
.TP
|
||||
.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
|
||||
|
|
@ -759,16 +811,17 @@ and so on are not valid here.
|
|||
The format is as follows:
|
||||
.IP
|
||||
hd=cyls,heads,sects
|
||||
.LP
|
||||
.IP
|
||||
If there are two disks installed, the above is repeated with the
|
||||
geometry parameters of the second disk.
|
||||
.SS "XT Disk Driver Options (`xd=')"
|
||||
.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
|
||||
xd=type,irq,iobase,dma_chan
|
||||
.LP
|
||||
.IP
|
||||
The type value specifies the particular manufacturer of the card,
|
||||
overriding autodetection.
|
||||
For the types to use, consult the
|
||||
|
|
@ -793,54 +846,60 @@ example usage for a WD1002 controller with the BIOS disabled/removed,
|
|||
using the `default' XT controller parameters:
|
||||
.IP
|
||||
xd=2,5,0x320,3
|
||||
.SS "Syquest's EZ* removable disks"
|
||||
.TP
|
||||
.B "Syquest's EZ* removable disks"
|
||||
.IP
|
||||
.BI ez= iobase[,irq[,rep[,nybble]]]
|
||||
.SH "IBM MCA BUS DEVICES"
|
||||
.SS "IBM MCA BUS DEVICES"
|
||||
See also
|
||||
.IR /usr/src/linux/Documentation/mca.txt .
|
||||
.SS "PS/2 ESDI hard disks"
|
||||
.TP
|
||||
.B "PS/2 ESDI hard disks"
|
||||
It is possible to specify the desired geometry at boot time:
|
||||
.IP
|
||||
.BI ed= cyls,heads,sectors.
|
||||
.LP
|
||||
.IP
|
||||
For a ThinkPad-720, add the option
|
||||
.IP
|
||||
.BR tp720=1 .
|
||||
.SS "IBM Microchannel SCSI Subsystem configuration"
|
||||
.TP
|
||||
.B "IBM Microchannel SCSI Subsystem configuration"
|
||||
.IP
|
||||
.BI ibmmcascsi= N
|
||||
.LP
|
||||
.IP
|
||||
where N is the \fIpun\fP (SCSI ID) of the subsystem.
|
||||
.SS "The Aztech Interface"
|
||||
.TP
|
||||
.B "The Aztech Interface"
|
||||
The syntax for this type of card is:
|
||||
.IP
|
||||
aztcd=iobase[,magic_number]
|
||||
.LP
|
||||
.IP
|
||||
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.
|
||||
.SS "Parallel port CD-ROM drives"
|
||||
.TP
|
||||
.B "Parallel port CD-ROM drives"
|
||||
Syntax:
|
||||
.IP
|
||||
pcd.driveN=prt,pro,uni,mod,slv,dly
|
||||
.br
|
||||
pcd.nice=nice
|
||||
.LP
|
||||
.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
|
||||
to choose the best automatically), `slv' is 1 if it should be a slave,
|
||||
and `dly' is a small integer for slowing down port accesses.
|
||||
The `nice' parameter controls the driver's use of idle CPU time, at the
|
||||
expense of some speed.
|
||||
.SS "The CDU-31A and CDU-33A Sony Interface"
|
||||
.TP
|
||||
.B "The CDU-31A and CDU-33A Sony Interface"
|
||||
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
|
||||
cdu31a=iobase,[irq[,is_pas_card]]
|
||||
.LP
|
||||
.IP
|
||||
Specifying an IRQ value of zero tells the driver that hardware
|
||||
interrupts aren't supported (as on some PAS cards).
|
||||
If your card
|
||||
|
|
@ -851,32 +910,36 @@ The
|
|||
.I is_pas_card
|
||||
should be entered as `PAS' if using a Pro Audio Spectrum card,
|
||||
and otherwise it should not be specified at all.
|
||||
.SS "The CDU-535 Sony Interface"
|
||||
.TP
|
||||
.B "The CDU-535 Sony Interface"
|
||||
The syntax for this CD-ROM interface is:
|
||||
.IP
|
||||
sonycd535=iobase[,irq]
|
||||
.LP
|
||||
.IP
|
||||
A zero can be used for the I/O base as a `placeholder' if one wishes
|
||||
to specify an IRQ value.
|
||||
.SS "The GoldStar Interface"
|
||||
.TP
|
||||
.B "The GoldStar Interface"
|
||||
The syntax for this CD-ROM interface is:
|
||||
.IP
|
||||
gscd=iobase
|
||||
.SS "The ISP16 CD-ROM Interface"
|
||||
.TP
|
||||
.B "The ISP16 CD-ROM Interface"
|
||||
Syntax:
|
||||
.IP
|
||||
isp16=[iobase[,irq[,dma[,type]]]]
|
||||
.LP
|
||||
.IP
|
||||
(three integers and a string).
|
||||
If the type is given as `noisp16',
|
||||
the interface will not be configured.
|
||||
Other recognized types
|
||||
are: `Sanyo", `Sony', `Panasonic' and `Mitsumi'.
|
||||
.SS "The Mitsumi Standard Interface"
|
||||
.TP
|
||||
.B "The Mitsumi Standard Interface"
|
||||
The syntax for this CD-ROM interface is:
|
||||
.IP
|
||||
mcd=iobase,[irq[,wait_value]]
|
||||
.LP
|
||||
.IP
|
||||
The
|
||||
.I wait_value
|
||||
is used as an internal timeout value for people who are
|
||||
|
|
@ -884,45 +947,50 @@ having problems with their drive, and may or may not be implemented
|
|||
depending on a compile time #define.
|
||||
The Mitsumi FX400 is an IDE/ATAPI CD-ROM player and does not use
|
||||
the mcd driver.
|
||||
.SS "The Mitsumi XA/MultiSession Interface"
|
||||
.TP
|
||||
.B "The Mitsumi XA/MultiSession Interface"
|
||||
This is for the same hardware as above, but the driver has extended features.
|
||||
Syntax:
|
||||
.IP
|
||||
mcdx=iobase[,irq]
|
||||
.SS "The Optics Storage Interface"
|
||||
.TP
|
||||
.B "The Optics Storage Interface"
|
||||
The syntax for this type of card is:
|
||||
.IP
|
||||
optcd=iobase
|
||||
.SS "The Phillips CM206 Interface"
|
||||
.TP
|
||||
.B "The Phillips CM206 Interface"
|
||||
The syntax for this type of card is:
|
||||
.IP
|
||||
cm206=[iobase][,irq]
|
||||
.LP
|
||||
.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,
|
||||
or both numbers, in any order.
|
||||
It also accepts `cm206=auto' to enable
|
||||
autoprobing.
|
||||
.SS "The Sanyo Interface"
|
||||
.TP
|
||||
.B "The Sanyo Interface"
|
||||
The syntax for this type of card is:
|
||||
.IP
|
||||
sjcd=iobase[,irq[,dma_channel]]
|
||||
.SS "The SoundBlaster Pro Interface"
|
||||
.TP
|
||||
.B "The SoundBlaster Pro Interface"
|
||||
The syntax for this type of card is:
|
||||
.IP
|
||||
sbpcd=iobase,type
|
||||
.LP
|
||||
.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.
|
||||
.SH "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
|
||||
ether=irq,iobase[,param_1[,...param_8]],name
|
||||
.LP
|
||||
.IP
|
||||
The first non-numeric argument is taken as the name.
|
||||
The param_n values (if applicable) usually have different meanings for each
|
||||
different card/driver.
|
||||
|
|
@ -935,7 +1003,7 @@ ethercard, as the default is to only probe for one.
|
|||
This can be accomplished with a simple:
|
||||
.IP
|
||||
ether=0,0,eth1
|
||||
.LP
|
||||
.IP
|
||||
Note that the values of zero for the IRQ and I/O base in the above
|
||||
example tell the driver(s) to autoprobe.
|
||||
|
||||
|
|
@ -944,12 +1012,13 @@ cards and on the card/driver specific implementation
|
|||
of the param_n values where used.
|
||||
Interested readers should refer to
|
||||
the section in that document on their particular card.
|
||||
.SH "THE FLOPPY DISK DRIVER"
|
||||
.SS "THE FLOPPY DISK DRIVER"
|
||||
There are many floppy driver options, and they are all listed in
|
||||
README.fd in linux/drivers/block.
|
||||
This information is taken directly
|
||||
from that file.
|
||||
.SS "floppy=mask,allowed_drive_mask"
|
||||
.TP
|
||||
.B "floppy=mask,allowed_drive_mask"
|
||||
Sets the bitmask of allowed drives to mask.
|
||||
By default, only units 0
|
||||
and 1 of each floppy controller are allowed.
|
||||
|
|
@ -958,35 +1027,44 @@ 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.
|
||||
.SS "floppy=all_drives"
|
||||
.TP
|
||||
.B "floppy=all_drives"
|
||||
Sets the bitmask of allowed drives to all drives.
|
||||
Use this if you have
|
||||
more than two drives connected to a floppy controller.
|
||||
.SS "floppy=asus_pci"
|
||||
.TP
|
||||
.B "floppy=asus_pci"
|
||||
Sets the bitmask to allow only units 0 and 1. (The default)
|
||||
.SS "floppy=daring"
|
||||
.TP
|
||||
.B "floppy=daring"
|
||||
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.
|
||||
.SS "floppy=0,daring"
|
||||
.TP
|
||||
.B "floppy=0,daring"
|
||||
Tells the floppy driver that your floppy controller should be used
|
||||
with caution.
|
||||
.SS "floppy=one_fdc"
|
||||
.TP
|
||||
.B "floppy=one_fdc"
|
||||
Tells the floppy driver that you have only floppy controller (default)
|
||||
.SS "floppy=two_fdc or floppy=address,two_fdc"
|
||||
.TP
|
||||
.B "floppy=two_fdc or floppy=address,two_fdc"
|
||||
Tells the floppy driver that you have two floppy controllers.
|
||||
The second floppy controller is assumed to be at address.
|
||||
If address is
|
||||
not given, 0x370 is assumed.
|
||||
.SS "floppy=thinkpad"
|
||||
.TP
|
||||
.B "floppy=thinkpad"
|
||||
Tells the floppy driver that you have a Thinkpad.
|
||||
Thinkpads use an
|
||||
inverted convention for the disk change line.
|
||||
.SS "floppy=0,thinkpad"
|
||||
.TP
|
||||
.B "floppy=0,thinkpad"
|
||||
Tells the floppy driver that you don't have a Thinkpad.
|
||||
.SS "floppy=drive,type,cmos"
|
||||
.TP
|
||||
.B "floppy=drive,type,cmos"
|
||||
Sets the cmos type of drive to type.
|
||||
Additionally, this drive is
|
||||
allowed in the bitmask.
|
||||
|
|
@ -996,17 +1074,19 @@ your BIOS uses non-standard CMOS types.
|
|||
Setting the CMOS to 0 for the
|
||||
first two drives (default) makes the floppy driver read the physical
|
||||
cmos for those drives.
|
||||
.SS "floppy=unexpected_interrupts"
|
||||
.TP
|
||||
.B "floppy=unexpected_interrupts"
|
||||
Print a warning message when an unexpected interrupt is received
|
||||
(default behavior)
|
||||
.SS "floppy=no_unexpected_interrupts or floppy=L40SX"
|
||||
.TP
|
||||
.B "floppy=no_unexpected_interrupts or floppy=L40SX"
|
||||
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.)
|
||||
.SH "THE SOUND DRIVER"
|
||||
.SS "THE SOUND DRIVER"
|
||||
The sound driver can also accept boot args to override the compiled in
|
||||
values.
|
||||
This is not recommended, as it is rather complex.
|
||||
|
|
@ -1015,7 +1095,7 @@ It accepts
|
|||
a boot arg of the form:
|
||||
.IP
|
||||
sound=device1[,device2[,device3...[,device10]]]
|
||||
.LP
|
||||
.IP
|
||||
where each deviceN value is of the following format 0xTaaaId and the
|
||||
bytes are used as follows:
|
||||
|
||||
|
|
@ -1032,45 +1112,50 @@ 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
|
||||
`sound=0' will disable the sound driver entirely.
|
||||
.SH "ISDN DRIVERS"
|
||||
.SS "The ICN ISDN driver"
|
||||
.SS "ISDN DRIVERS"
|
||||
.TP
|
||||
.B "The ICN ISDN driver"
|
||||
Syntax:
|
||||
.IP
|
||||
icn=iobase,membase,icn_id1,icn_id2
|
||||
.LP
|
||||
.IP
|
||||
where icn_id1,icn_id2 are two strings used to identify the
|
||||
card in kernel messages.
|
||||
.SS "The PCBIT ISDN driver"
|
||||
.TP
|
||||
.B "The PCBIT ISDN driver"
|
||||
Syntax:
|
||||
.IP
|
||||
pcbit=membase1,irq1[,membase2,irq2]
|
||||
.LP
|
||||
.IP
|
||||
where membaseN is the shared memory base of the N'th card, and irqN is
|
||||
the interrupt setting of the N'th card.
|
||||
The default is IRQ 5 and
|
||||
membase 0xD0000.
|
||||
.SS "The Teles ISDN driver"
|
||||
.TP
|
||||
.B "The Teles ISDN driver"
|
||||
Syntax:
|
||||
.IP
|
||||
teles=iobase,irq,membase,protocol,teles_id
|
||||
.LP
|
||||
.IP
|
||||
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.
|
||||
.SH "SERIAL PORT DRIVERS"
|
||||
.SS "The RISCom/8 Multiport Serial Driver (`riscom8=')"
|
||||
.SS "SERIAL PORT DRIVERS"
|
||||
.TP
|
||||
.B "The RISCom/8 Multiport Serial Driver (`riscom8=')"
|
||||
Syntax:
|
||||
.IP
|
||||
riscom=iobase1[,iobase2[,iobase3[,iobase4]]]
|
||||
.LP
|
||||
.IP
|
||||
More details can be found in
|
||||
.IR /usr/src/linux/Documentation/riscom8.txt .
|
||||
.SS "The DigiBoard Driver (`digi=')"
|
||||
.TP
|
||||
.B "The DigiBoard Driver (`digi=')"
|
||||
If this option is used, it should have precisely six parameters.
|
||||
Syntax:
|
||||
.IP
|
||||
digi=status,type,altpin,numports,iobase,membase
|
||||
.LP
|
||||
.IP
|
||||
The parameters maybe given as integers, or as strings.
|
||||
If strings are used, then iobase and membase should be given
|
||||
in hexadecimal.
|
||||
|
|
@ -1086,14 +1171,15 @@ Thus, the following two boot prompt arguments are equivalent:
|
|||
digi=E,PC/Xi,D,16,200,D0000
|
||||
.br
|
||||
digi=1,0,0,16,0x200,851968
|
||||
.LP
|
||||
.IP
|
||||
More details can be found in
|
||||
.IR /usr/src/linux/Documentation/digiboard.txt .
|
||||
.SS "The Baycom Serial/Parallel Radio Modem"
|
||||
.TP
|
||||
.B "The Baycom Serial/Parallel Radio Modem"
|
||||
Syntax:
|
||||
.IP
|
||||
baycom=iobase,irq,modem
|
||||
.LP
|
||||
.IP
|
||||
There are precisely 3 parameters; for several cards, give
|
||||
several `baycom=' commands.
|
||||
The modem parameter is a string
|
||||
|
|
@ -1102,18 +1188,20 @@ Here the * denotes that software DCD is to be used, and
|
|||
ser12/par96 chooses between the supported modem types.
|
||||
For more details, see
|
||||
.IR /usr/src/linux/drivers/net/README.baycom .
|
||||
.SS "Soundcard radio modem driver"
|
||||
.TP
|
||||
.B "Soundcard radio modem driver"
|
||||
Syntax:
|
||||
.IP
|
||||
soundmodem=iobase,irq,dma[,dma2[,serio[,pario]]],0,mode
|
||||
.LP
|
||||
.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.
|
||||
.SH "THE LINE PRINTER DRIVER"
|
||||
.SS "`lp='"
|
||||
.SS "THE LINE PRINTER DRIVER"
|
||||
.TP
|
||||
.B "`lp='"
|
||||
Syntax:
|
||||
.IP
|
||||
lp=0
|
||||
|
|
@ -1123,7 +1211,7 @@ lp=auto
|
|||
lp=reset
|
||||
.br
|
||||
lp=port[,port...]
|
||||
.LP
|
||||
.IP
|
||||
You can tell the printer driver what ports to use and what ports not
|
||||
to use.
|
||||
The latter comes in handy if you don't want the printer driver
|
||||
|
|
@ -1136,18 +1224,22 @@ lp=none,parport0 would use the first parallel port for lp1, and
|
|||
disable lp0.
|
||||
To disable the printer driver entirely, one can use
|
||||
lp=0.
|
||||
.SS "WDT500/501 driver"
|
||||
.TP
|
||||
.B "WDT500/501 driver"
|
||||
Syntax:
|
||||
.IP
|
||||
wdt=io,irq
|
||||
.SH "MOUSE DRIVERS"
|
||||
.SS "`bmouse=irq'"
|
||||
.SS "MOUSE DRIVERS"
|
||||
.TP
|
||||
.B "`bmouse=irq'"
|
||||
The busmouse driver only accepts one parameter, that being the
|
||||
hardware IRQ value to be used.
|
||||
.SS "`msmouse=irq'"
|
||||
.TP
|
||||
.B "`msmouse=irq'"
|
||||
And precisely the same is true for the msmouse driver.
|
||||
.SS "ATARI mouse setup"
|
||||
.LP
|
||||
.TP
|
||||
.B "ATARI mouse setup"
|
||||
.IP
|
||||
atamouse=threshold[,y-threshold]
|
||||
.IP
|
||||
If only one argument is given, it is used for both
|
||||
|
|
@ -1155,8 +1247,9 @@ 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.
|
||||
.SH "VIDEO HARDWARE"
|
||||
.SS "`no-scroll'"
|
||||
.SS "VIDEO HARDWARE"
|
||||
.TP
|
||||
.B "`no-scroll'"
|
||||
This option tells the console driver not to use hardware scroll
|
||||
(where a scroll is effected by moving the screen origin in video
|
||||
memory, instead of moving the data).
|
||||
|
|
|
|||
Loading…
Reference in New Issue