(split) Apply minor changes from v3.32 to v3.35 in the upstream.

[linuxjm/LDP_man-pages.git] / draft / man7 / bootparam.7

.\" Copyright (c) 1995,1997 Paul Gortmaker and Andries Brouwer
.\"
.\" 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
.\" the License, or (at your option) any later version.
.\"
.\" The GNU General Public License's references to "object code"
.\" and "executables" are to be interpreted as the output of any
.\" document formatting or typesetting system, including
.\" intermediate and printed output.
.\"
.\" This manual is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\" 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.
.\"
.\" 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
.\" rest of man-pages.
.\"
.\" Japanese Version Copyright (c) 1999 MATSUURA Masaaki
.\"         all rights reserved.
.\" Translated 1999-02-04, MATSUURA Masaaki <masa386@yk.rim.or.jp>
.\" Modified 2001-07-08, Yuichi SATO <ysato@h4.dion.ne.jp>
.\" Updated & Modified  2001-09-10, NAKANO Takeo <nakano@apm.seikei.ac.jp>
.\" Updated 2002-04-21, NAKANO Takeo <nakano@apm.seikei.ac.jp>
.\" Updated 2007-05-04, Akihiro MOTOKI <amotoki@dd.iij4u.or.jp>, LDP v2.46
.\"
.TH BOOTPARAM 7 2007-12-16 "Linux" "Linux Programmer's Manual"
.\"O .SH NAME
.\"O bootparam \- Introduction to boot time parameters of the Linux kernel
.SH ̾Á°
bootparam \- Linux ¥«¡¼¥Í¥ëµ¯Æ°»þ¥Ñ¥é¥á¡¼¥¿¤Î²òÀâ
.\"O .SH DESCRIPTION
.SH ÀâÌÀ
.\"O The Linux kernel accepts certain 'command-line options' or 'boot time
.\"O parameters' at the moment it is started.
.\"O In general this is used to
.\"O supply the kernel with information about hardware parameters that
.\"O the kernel would not be able to determine on its own, or to avoid/override
.\"O the values that the kernel would otherwise detect.
Linux ¥«¡¼¥Í¥ë¤Ïµ¯Æ°¤¹¤ë¤È¤­¤Ë¡Ö¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¡×¤¢¤ë¤¤¤Ï
¡Öµ¯Æ°»þ¥Ñ¥é¥á¡¼¥¿¡×¤ò¼õ¤±ÉÕ¤±¤ë¡£
¤³¤ì¤Ï°ìÈ̤ˡ¢
¥«¡¼¥Í¥ë¤Ë¤Ï·èÄê¤Ç¤­¤Ê¤¤¥Ï¡¼¥É¥¦¥§¥¢¤Î¥Ñ¥é¥á¡¼¥¿¤ò¥«¡¼¥Í¥ë¤ËÅϤ·¤¿¤¤¾ì¹ç¤ä¡¢
¥«¡¼¥Í¥ë¤¬¸¡½Ð¤¹¤ë¤Ç¤¢¤í¤¦Ãͤò°Õ¿ÞŪ¤Ë̵¸ú¤Ë¤·¤¿¤êÊѹ¹¤·¤¿¤ê¤¹¤ë¾ì¹ç¤ËÍѤ¤¤ë¡£

.\"O When the kernel is booted directly by the BIOS (say from a floppy to
.\"O which you copied a kernel using 'cp zImage /dev/fd0'),
.\"O you have no opportunity to specify any parameters.
.\"O So, in order to take advantage of this possibility you have to
.\"O use software that is able to pass parameters, like LILO or loadlin.
.\"O For a few parameters one can also modify the kernel image itself,
.\"O using rdev, see
.\"O .BR rdev (8)
.\"O for further details.
¥«¡¼¥Í¥ë¤¬ BIOS ¤«¤éľÀܵ¯Æ°¤µ¤ì¤ë¤È¤­
(¤¿¤È¤¨¤Ð 'cp zImage /dev/fd0'
¤Ç¥Õ¥í¥Ã¥Ô¡¼¤Ë¥³¥Ô¡¼¤·¤¿¥«¡¼¥Í¥ë¤«¤éµ¯Æ°¤¹¤ë¤Ê¤É) ¤Ï¡¢
¥Ñ¥é¥á¡¼¥¿¤ò»ØÄꤹ¤ëµ¡²ñ¤Ï¤Ê¤¤¡£
¤æ¤¨¤Ë¡¢¤³¤Îµ¯Æ°»þ¥Ñ¥é¥á¡¼¥¿µ¡Ç½¤òÍøÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢
.I LILO
¤ä
.I loadlin
¤Î¤è¤¦¤Ë¥Ñ¥é¥á¡¼¥¿¤ò»ØÄê¤Ç¤­¤ë¥½¥Õ¥È¥¦¥§¥¢¤ò»ÈÍѤ·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
¤¤¤¯¤Ä¤«¤Î¥Ñ¥é¥á¡¼¥¿¤Ë¤Ä¤¤¤Æ¤Ï¡¢
.I rdev
¤ò»È¤Ã¤Æ¥«¡¼¥Í¥ë¥¤¥á¡¼¥¸¤½¤Î¤â¤Î¤ò½¤Àµ¤¹¤ë¤³¤È¤â¤Ç¤­¤ë¡£
¾ÜºÙ¤Ï
.BR rdev (8)
¤ò»²¾È¤Î¤³¤È¡£

.\"O The LILO program (LInux LOader) written by Werner Almesberger is the
.\"O most commonly used.
.\"O It has the ability to boot various kernels, and
.\"O stores the configuration information in a plain text file.
.\"O (See
.\"O .BR lilo (8)
.\"O and
.\"O .BR lilo.conf (5).)
.\"O LILO can boot DOS, OS/2, Linux, FreeBSD, UnixWare, etc., and is quite flexible.
Werner Almesberger ¤Ë¤è¤ë
LILO (LInux LOader) ¥×¥í¥°¥é¥à¤ÏºÇ¤â¹­¤¯»ÈÍѤµ¤ì¤Æ¤¤¤ë¡£
LILO ¤Ï¤¤¤í¤¤¤í¤Ê¥«¡¼¥Í¥ë¤òÁªÂò¤·¤Æ¥Ö¡¼¥È¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¡¢
ÀßÄê¾ðÊó¤ò¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤ËÊÝ»ý¤¹¤ë
.RB ( lilo (8)
¤È
.BR lilo.conf (5)
¤ò»²¾È)¡£ LILO ¤Ï DOS, OS/2, Linux, FreeBSD ¤Ê¤É¤òµ¯Æ°¤Ç¤­¡¢
Èó¾ï¤Ë½ÀÆð¤Ç¤¢¤ë¡£

.\"O The other commonly used Linux loader is 'LoadLin' which is a DOS
.\"O program that has the capability to launch a Linux kernel from the DOS
.\"O prompt (with boot-args) assuming that certain resources are available.
.\"O This is good for people that want to launch Linux from DOS.
¤Û¤«¤Ë¤Ï
.I loadLin
¤â¤è¤¯»È¤ï¤ì¤Æ¤¤¤ë Linux ¥í¡¼¥À¤Ç¤¢¤ë¡£
¤³¤ì¤Ï DOS ¤Î¥×¥í¥°¥é¥à¤Ç¡¢DOS ¥×¥í¥ó¥×¥È¤«¤é
(µ¯Æ°»þ°ú¿ô¤È¤È¤â¤Ë) Linux ¥«¡¼¥Í¥ë¤òµ¯Æ°¤Ç¤­¤ë
(¤¤¤¯¤Ä¤«¤ÎÆÃÄê¤Î¥ê¥½¡¼¥¹¤¬ÍøÍѲÄǽ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤)¡£
loadlin ¤Ï DOS ¤«¤é Linux ¤òµ¯Æ°¤µ¤»¤¿¤¤¿Í¤Ë¤¢¤Ã¤Æ¤¤¤ë¡£

.\"O It is also very useful if you have certain hardware which relies on
.\"O the supplied DOS driver to put the hardware into a known state.
.\"O A common example is 'SoundBlaster Compatible' sound cards that require
.\"O the DOS driver to twiddle a few mystical registers to put the card
.\"O into a SB compatible mode.
.\"O Booting DOS with the supplied driver, and
.\"O then loading Linux from the DOS prompt with loadlin avoids the reset
.\"O of the card that happens if one rebooted instead.
¤Þ¤¿ loadlin ¤Ï¡¢DOS ¤Î¥É¥é¥¤¥Ð¤Ç¤¢¤ë¾õÂÖ¤Ë
ÀßÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¥Ï¡¼¥É¥¦¥§¥¢¤ò
»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤âÈó¾ï¤ËÊØÍø¤Ç¤¢¤ë¡£
¤è¤¯¤¢¤ëÎã¤Ï
¡ÖSoundBlaster ¸ß´¹¡×¤Î¥µ¥¦¥ó¥É¥«¡¼¥É¤Ç¡¢
¤³¤ì¤é¤ÎÃæ¤Ë¤Ï DOS ¤Î¥É¥é¥¤¥Ð¤ò»È¤Ã¤Æ
¤¤¤¯¤Ä¤«ÈëÌ©¤Î¥ì¥¸¥¹¥¿¤ò¤¤¤¸¤Ã¤Æ¤ä¤é¤Ê¤¤¤È¡¢
ËÜÅö¤Î SB ¸ß´¹¥â¡¼¥É¤Ë¤Ï¤Ê¤é¤Ê¤¤¤è¤¦¤Ê¤â¤Î¤¬¤¢¤ë¡£
¤Þ¤º¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ä¤¤¤Æ¤­¤¿¥É¥é¥¤¥Ð¤òÁȤ߹þ¤ó¤Ç DOS ¤òµ¯Æ°¤·¡¢
¤½¤Î¸å loadlin ¤ò»ÈÍѤ·¤Æ Linux ¥«¡¼¥Í¥ë¤òÆɤ߹þ¤á¤Ð¡¢
¥ê¥Ö¡¼¥È¤Ë¤è¤Ã¤Æ¥«¡¼¥É¤ÎÀßÄ꤬¥ê¥»¥Ã¥È¤µ¤ì¤ë¤Î¤òËɤ²¤ë¤ï¤±¤À¡£
.\"O .SS "The Argument List"
.SS °ú¿ô¥ê¥¹¥È
.\"O The kernel command line is parsed into a list of strings
.\"O (boot arguments) separated by spaces.
.\"O Most of the boot args take the form of:
¥«¡¼¥Í¥ë¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ï¥¹¥Ú¡¼¥¹¤Ç¶èÀÚ¤é¤ì¤¿Ê¸»úÎó
.RI ( "µ¯Æ°»þ°ú¿ô: boot arguments" )
¤Î¥ê¥¹¥È¤«¤éÀ®¤Ã¤Æ¤¤¤ë¡£¤Û¤È¤ó¤É¤Îµ¯Æ°»þ°ú¿ô¤Ï¼¡¤Î½ñ¼°¤Ë½¾¤¦¡£
.IP
name[=value_1][,value_2]...[,value_10]
.LP
.\"O where 'name' is a unique keyword that is used to identify what part of
.\"O the kernel the associated values (if any) are to be given to.
.\"O Note the limit of 10 is real, as the present code only handles 10 comma
.\"O separated parameters per keyword.
.\"O (However, you can reuse the same
.\"O keyword with up to an additional 10 parameters in unusually
.\"O complicated situations, assuming the setup function supports it.)
¤³¤³¤Ç 'name' ¤Ï¡¢¤½¤ì¤ËÂбþ¤¹¤ëÃͤ¬¥«¡¼¥Í¥ë¤Î¤É¤ÎÉôʬ¤ËÅϤµ¤ì¤ë¤â¤Î¤Ê¤Î¤«¤ò
¼±Ê̤¹¤ë¤¿¤á¤Î¡¢Â¾¤È½Å¤Ê¤é¤Ê¤¤¥­¡¼¥ï¡¼¥É¤Ç¤¢¤ë¡£
½ñ¼°Ãæ¤Î 10 ¤È¤¤¤¦À©¸Â¤Ï¼ÂºÝ¤Ë¸ºß¤¹¤ë¡£
¸½ºß¤Î¥³¡¼¥É¤Ï¡¢¥­¡¼¥ï¡¼¥É¤Ò¤È¤Ä¤¢¤¿¤ê¡¢¥³¥ó¥Þ¤Ç¶èÀÚ¤é¤ì¤¿¥Ñ¥é¥á¡¼¥¿¤ò
10 ¸Ä¤Þ¤Ç¤·¤«¼è¤ê°·¤¦¤³¤È¤¬¤Ç¤­¤Ê¤¤¡£
(¤·¤«¤·¡¢»ö¾ð¤¬Èó¾ï¤ËÊ£»¨¤Ê¾ì¹ç¤Ë¤Ï¡¢Æ±¤¸¥­¡¼¥ï¡¼¥É¤òºÆÅÙÍøÍѤ·¤Æ
10 ¸Ä°Ê¾å¤Î¥Ñ¥é¥á¡¼¥¿¤òÍ¿¤¨¤ë¤³¤È¤¬¤Ç¤­¤ë¤«¤â¤·¤ì¤Ê¤¤¡£
ÂоݤȤʤë¥Ï¡¼¥É¥¦¥§¥¢¤ÎÀßÄê´Ø¿ô¤¬¤½¤ì¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ì¤Ð¡¢¤À¤¬¡£)

.\"O Most of the sorting goes on in linux/init/main.c.
.\"O First, the kernel
.\"O checks to see if the argument is any of the special arguments 'root=',
.\"O \&'nfsroot=', 'nfsaddrs=', 'ro', 'rw', 'debug' or 'init'.
.\"O The meaning of these special arguments is described below.
¥«¡¼¥Í¥ë¥³¥Þ¥ó¥É¥é¥¤¥ó¤Î°·¤¤¤Ï¤Û¤È¤ó¤É linux/init/main.c ¤¬¹Ô¤Ê¤Ã¤Æ¤¤¤ë¡£
½é¤á¤Ë¡¢¥«¡¼¥Í¥ë¤Ï
\&'root=', 'nfsroot=', 'nfsaddrs=', 'ro', 'rw', 'debug', 'init'
¤È¤¤¤Ã¤¿ÆÃÊ̤ʰú¿ô¤¬¤¢¤ë¤«¤ò¥Á¥§¥Ã¥¯¤¹¤ë¡£
¤³¤ì¤é¤Î°ÕÌ£¤Ë¤Ä¤¤¤Æ¤Ï¸å½Ò¤¹¤ë¡£

.\"O Then it walks a list of setup functions (contained in the bootsetups
.\"O array) to see if the specified argument string (such as 'foo') has
.\"O been associated with a setup function ('foo_setup()') for a particular
.\"O device or part of the kernel.
.\"O If you passed the kernel the line
.\"O foo=3,4,5,6 then the kernel would search the bootsetups array to see
.\"O if 'foo' was registered.
.\"O If it was, then it would call the setup
.\"O function associated with 'foo' (foo_setup()) and hand it the arguments
.\"O 3, 4, 5 and 6 as given on the kernel command line.
¥«¡¼¥Í¥ë¤Ï¼¡¤ËÀßÄê´Ø¿ô¤Î¥ê¥¹¥È
(ÇÛÎó bootsetups ¤Ë´Þ¤Þ¤ì¤Æ¤¤¤ë) ¤ò¥¹¥­¥ã¥ó¤·¡¢
»ØÄꤵ¤ì¤¿°ú¿ôʸ»úÎó (Î㤨¤Ð 'foo') ¤¬
ÆÃÄê¤Î¥Ç¥Ð¥¤¥¹¤ä¥«¡¼¥Í¥ë¤Î°ìÉô¤ËÂФ¹¤ëÀßÄê´Ø¿ô
('foo_setup()') ¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤ë¤«¤òÄ´¤Ù¤ë¡£
Î㤨¤Ð¥«¡¼¥Í¥ë¤Ë foo=3,4,5,6 ¤Î¤è¤¦¤Ê¥Ñ¥é¥á¡¼¥¿¤òÍ¿¤¨¤¿¤È¤¹¤ë¤È¡¢
¥«¡¼¥Í¥ë¤ÏÇÛÎó bootsetups ¤òÄ´¤Ù¤Æ¡¢ 'foo' ¤¬ÅÐÏ¿¤µ¤ì¤Æ¤¤¤ë¤«Ä´¤Ù¤ë¡£
ÅÐÏ¿¤µ¤ì¤Æ¤¤¤¿¤é¡¢'foo' ¤ËÂбþ¤¹¤ëÀßÄê´Ø¿ô ('foo_setup()') ¤ò¥³¡¼¥ë¤·¡¢
¥«¡¼¥Í¥ë¥³¥Þ¥ó¥É¥é¥¤¥ó¤ËÍ¿¤¨¤é¤ì¤¿°ú¿ô¤Ç¤¢¤ë 3, 4, 5, 6 ¤òÀßÄê´Ø¿ô¤ËÅϤ¹¡£

.\"O Anything of the form 'foo=bar' that is not accepted as a setup function
.\"O as described above is then interpreted as an environment variable to
.\"O be set.
.\"O A (useless?) example would be to use 'TERM=vt100' as a boot
.\"O argument.
\&'foo=bar' ¤È¤¤¤¦·Á¼°¤Î°ú¿ô¤Î¤¦¤Á¡¢
¾åµ­¤Î¤è¤¦¤ËÀßÄê´Ø¿ô¤Ë¼õ¤±Æþ¤ì¤é¤ì¤Ê¤«¤Ã¤¿¤â¤Î¤Ï¡¢
´Ä¶­ÊÑ¿ô¤È²ò¼á¤µ¤ì¤ÆÀßÄꤵ¤ì¤ë¡£
(¤¢¤Þ¤êÌò¤ËΩ¤¿¤Ê¤¤?) Îã¤È¤·¤Æ¤Ï¡¢'TERM=VT100' ¤¬¤¢¤ë¡£

.\"O Any remaining arguments that were not picked up by the kernel and were
.\"O not interpreted as environment variables are then passed onto process
.\"O one, which is usually the init program.
.\"O The most common argument that
.\"O is passed to the init process is the word 'single' which instructs init
.\"O to boot the computer in single user mode, and not launch all the usual
.\"O daemons.
.\"O Check the manual page for the version of init installed on
.\"O your system to see what arguments it accepts.
¥«¡¼¥Í¥ë¤Ë¤è¤Ã¤Æ½èÍý¤µ¤ì¤º¡¢´Ä¶­ÊÑ¿ô¤È¤·¤Æ¤â²ò¼á¤µ¤ì¤Ê¤«¤Ã¤¿
»Ä¤ê¤Î°ú¿ô¤Ï¡¢¥×¥í¥»¥¹ 1 ¤ËÅϤµ¤ì¤ë¤³¤È¤Ë¤Ê¤ë¡£
Ä̾盧¤Î¥×¥í¥»¥¹ 1 ¤Ï
.I init
¥×¥í¥°¥é¥à¤Ç¤¢¤ë¡£
¥×¥í¥»¥¹ 1 ¤ËÅϤµ¤ì¤ë°ú¿ô¤ÇºÇ¤âÎɤ¯»È¤ï¤ì¤ë¤Î¤Ï¡¢
\&'single' ¤È¤¤¤¦¥­¡¼¥ï¡¼¥É¤Ç¤¢¤ë¡£
¤³¤ì¤ò»ØÄꤹ¤ë¤È init ¤Ï¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤Ç¥³¥ó¥Ô¥å¡¼¥¿¤òµ¯Æ°¤·¡¢
Ä̾ï»È¤ï¤ì¤ë¥Ç¡¼¥â¥ó¤Ï°ìÀÚµ¯Æ°¤·¤Ê¤¤¡£
¥·¥¹¥Æ¥à¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë init ¤¬
¤É¤ó¤Ê°ú¿ô¤ò¼õ¤±ÉÕ¤±¤ë¤«¤Ï¡¢
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ÇÄ´¤Ù¤ë¤³¤È¡£
.\"O .SS "General Non-Device Specific Boot Arguments"
.SS °ìÈÌŪ¤Ê¡¢¥Ç¥Ð¥¤¥¹¸ÇÍ­¤Ç¤Ï¤Ê¤¤µ¯Æ°»þ°ú¤­¿ô
.TP
.B "'init=...'"
.\"O This sets the initial command to be executed by the kernel.
.\"O If this is not set, or cannot be found, the kernel will try
.\"O .IR /sbin/init ,
.\"O then
.\"O .IR /etc/init ,
.\"O then
.\"O .IR /bin/init ,
.\"O then
.\"O .I /bin/sh
.\"O and panic if all of this fails.
¥«¡¼¥Í¥ë¤¬¼Â¹Ô¤¹¤ë½é´ü¥³¥Þ¥ó¥É¤òÀßÄꤹ¤ë¡£
¤³¤Î»ØÄ꤬¤Ê¤µ¤ì¤Ê¤«¤Ã¤¿¤ê¡¢»ØÄꤷ¤¿¥³¥Þ¥ó¥É¤¬¸«¤Ä¤«¤é¤Ê¤«¤Ã¤¿¾ì¹ç¤Ë¤Ï¡¢
¥«¡¼¥Í¥ë¤Ï
.IR /sbin/init ,
.IR /etc/init ,
.IR /bin/init ,
.I /bin/sh
¤Î½ç¤Ç¼Â¹Ô¤ò»î¤ß¡¢¤¹¤Ù¤Æ¤Ë¼ºÇÔ¤·¤¿¤é panic ¤òµ¯¤³¤¹¡£
.TP
.B "'nfsaddrs=...'"
.\"O This sets the nfs boot address to the given string.
.\"O This boot address is used in case of a net boot.
nfs ¤Î¥Ö¡¼¥È¥¢¥É¥ì¥¹¤ò»ØÄꤷ¤¿Ê¸»úÎó¤ËÀßÄꤹ¤ë¡£
¤³¤Î¥Ö¡¼¥È¥¢¥É¥ì¥¹¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¥Ö¡¼¥È¤Î¾ì¹ç¤ËÍѤ¤¤é¤ì¤ë¡£
.TP
.B "'nfsroot=...'"
.\"O This sets the nfs root name to the given string.
.\"O If this string
.\"O does not begin with '/' or ',' or a digit, then it is prefixed by
.\"O \&'/tftpboot/'.
.\"O This root name is used in case of a net boot.
nfs ¥ë¡¼¥È¤Î̾Á°¤òÀßÄꤹ¤ë¡£
¤³¤Îʸ»úÎó¤ÎÀèƬ¤¬ '/'¡¢','¡¢¿ô»ú¤Î¤¤¤º¤ì¤Ç¤â¤Ç¤Ê¤¤¤È¤­¤Ï¡¢
\&'/tftpboot/' ¤¬ÀèƬ¤ËÉղ䵤ì¤ë¡£
¤³¤Î̾Á°¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¥Ö¡¼¥È¤Î¾ì¹ç¤ËÍѤ¤¤é¤ì¤ë¡£
.TP
.B  "'no387'"
.\"O (Only when
.\"O .B CONFIG_BUGi386
.\"O is defined.)
.\"O Some i387 coprocessor chips have bugs that show up when used in 32 bit
.\"O protected mode.
.\"O For example, some of the early ULSI-387 chips would
.\"O cause solid lockups while performing floating-point calculations.
.\"O Using the 'no387' boot arg causes Linux to ignore the maths
.\"O coprocessor even if you have one.
.\"O Of course you must then have your
.\"O kernel compiled with math emulation support!
(¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤Ë
.B CONFIG_BUGi386
¤¬»ØÄꤵ¤ì¤¿¤È¤­¤Î¤ßÍ­¸ú¡£)
°ìÉô¤Î i387 ¥³¥×¥í¥»¥Ã¥µ¥Á¥Ã¥×¤Ë¤Ï¡¢
32 ¥Ó¥Ã¥È¥×¥í¥Æ¥¯¥È¥â¡¼¥É¤Ç¤Î»ÈÍÑ»þ¤ËÀ¸¤¸¤ë¥Ð¥°¤¬¤¢¤ë¡£
Î㤨¤Ð½é´ü¤Î ULSI-387 ¥Á¥Ã¥×¤Ï¡¢
ÉâÆ°¾®¿ôÅÀ±é»»¤ò¹Ô¤Ê¤¦¤È³Î¼Â¤Ë¥í¥Ã¥¯¥¢¥Ã¥×¤·¤Æ¤·¤Þ¤¦¡£
¤³¤Îµ¯Æ°»þ°ú¿ô 'no387' ¤ò»ØÄꤹ¤ë¤È¡¢
Linux ¤Ï¥³¥×¥í¥»¥Ã¥µ¤¬¤¢¤Ã¤Æ¤â¤½¤ì¤ò̵»ë¤¹¤ë¤è¤¦¤Ë¤Ê¤ë¡£
¤Ê¤ª¤â¤Á¤í¤ó¡¢¥«¡¼¥Í¥ë¥³¥ó¥Ñ¥¤¥ë»þ¤ËÉâÆ°¾®¿ôÅÀ±é»»¤ò¥¨¥ß¥å¥ì¡¼¥È¤¹¤ë
(kernel math emulation) »ØÄê¤ò¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤!
.TP
.B "'no-hlt'"
.\"O (Only when
.\"O .B CONFIG_BUGi386
.\"O is defined.)
.\"O Some of the early i486DX-100 chips have a problem with the 'hlt'
.\"O instruction, in that they can't reliably return to operating mode
.\"O after this instruction is used.
.\"O Using the 'no-hlt' instruction tells
.\"O Linux to just run an infinite loop when there is nothing else to do,
.\"O and to not halt the CPU.
.\"O This allows people with these broken chips
.\"O to use Linux.
(¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤Ë
.B CONFIG_BUGi386
¤¬»ØÄꤵ¤ì¤¿¤È¤­¤Î¤ßÍ­¸ú¡£)
½é´ü¤Î i486DX-100 ¥Á¥Ã¥×¤Î°ìÉô¤Ç¤Ï 'hlt' Ì¿Îá¤ËÌäÂ꤬¤¢¤Ã¤Æ¡¢
¤³¤ÎÌ¿Îá¤ò»È¤¦¤È¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥â¡¼¥É¤ËÀµ¤·¤¯Ìá¤Ã¤ÆÍè¤Ê¤¤¡£
\&'no-hlt' ¤ò»ØÄꤹ¤ì¤Ð¡¢Linux ¤Ï¥¢¥¤¥É¥ê¥ó¥°»þ¤Ë CPU ¤òÄä»ß
(halt) ¤¹¤ë¤«¤ï¤ê¤Ë̵¸Â¥ë¡¼¥×¤ò¼Â¹Ô¤¹¤ë¤è¤¦¤Ë¤Ê¤ë¡£
¤³¤ì¤Ë¤è¤Ã¤Æ¡¢¤½¤Î¤è¤¦¤Ê¥Ð¥°¤Î¤¢¤ë¥Á¥Ã¥×¤Ç¤â Linux ¤ò»ÈÍѤǤ­¤ë¡£
.TP
.B "'root=...'"
.\"O This argument tells the kernel what device is to be used as the root
.\"O file system while booting.
.\"O The default of this setting is determined
.\"O at compile time, and usually is the value of the root device of the
.\"O system that the kernel was built on.
.\"O To override this value, and
.\"O select the second floppy drive as the root device, one would
.\"O use 'root=/dev/fd1'.
.\"O (The root device can also be set using
.\"O .BR rdev (8).)
µ¯Æ°»þ¤Ë¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤È¤·¤Æ»È¤ï¤ì¤ë¥Ç¥Ð¥¤¥¹¤ò¥«¡¼¥Í¥ë¤Ë»ØÄꤹ¤ë¡£
¥Ç¥Õ¥©¥ë¥È¤Ï¥³¥ó¥Ñ¥¤¥ë»þ¤Ë·èÄꤵ¤ì¡¢
Ä̾ï¤Ï¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¤¿¥·¥¹¥Æ¥à¤Î¥ë¡¼¥È¥Ç¥Ð¥¤¥¹¤Ë¤Ê¤ë¡£
¤³¤ÎÃͤò̵¸ú¤Ë¤·¤Æ¡¢
Î㤨¤Ð 2 ÈÖÌܤΥեí¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ò¥ë¡¼¥È¥Ç¥Ð¥¤¥¹¤Ë»ØÄꤹ¤ë¾ì¹ç¤Ï¡¢
\&'root=/dev/fd1' ¤È¤¹¤ë¡£
(¥ë¡¼¥È¥Ç¥Ð¥¤¥¹¤Ï
.BR rdev (8)
¤òÍѤ¤¤Æ¤âÀßÄê¤Ç¤­¤ë¡£)

.\"O The root device can be specified symbolically or numerically.
.\"O A symbolic specification has the form /dev/XXYN, where XX designates
.\"O the device type ('hd' for ST-506 compatible hard disk, with Y in
.\"O \&'a'-'d'; 'sd' for SCSI compatible disk, with Y in 'a'-'e';
.\"O \&'ad' for Atari ACSI disk, with Y in 'a'-'e',
.\"O \&'ez' for a Syquest EZ135 parallel port removable drive, with Y='a',
.\"O \&'xd' for XT compatible disk, with Y either 'a' or 'b'; 'fd' for
.\"O floppy disk, with Y the floppy drive number\(emfd0 would be
.\"O the DOS 'A:' drive, and fd1 would be 'B:'), Y the driver letter or
.\"O number, and N the number (in decimal) of the partition on this device
.\"O (absent in the case of floppies).
.\"O Recent kernels allow many other
.\"O types, mostly for CD-ROMs: nfs, ram, scd, mcd, cdu535, aztcd, cm206cd,
.\"O gscd, sbpcd, sonycd, bpcd.
.\"O (The type nfs specifies a net boot; ram refers to a ram disk.)
¥ë¡¼¥È¥Ç¥Ð¥¤¥¹¤Î»ØÄê¤Ë¤Ï¥·¥ó¥Ü¥ë·Á¼°¤È¿ôÃÍ·Á¼°¤òÍѤ¤¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
¥·¥ó¥Ü¥ë·Á¼°¤Î¾ì¹ç¤Ï /dev/XXYN ¤È¤¤¤¦½ñ¼°¤Ç»ØÄꤹ¤ë¡£
XX ¤Ë¤Ï¥Ç¥Ð¥¤¥¹¥¿¥¤¥×¤ò»ØÄꤹ¤ë¡£
Y ¤Ë¤Ï¥É¥é¥¤¥Ö¥ì¥¿¡¼¤â¤·¤¯¤Ï¥É¥é¥¤¥ÖÈֹ桢
N ¤Ë¤Ï (¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò½ü¤¯) ¥Ç¥£¥¹¥¯¤Î
¥Ñ¡¼¥Æ¥£¥·¥ç¥óÈÖ¹æ¤ò 10 ¿Ê¿ô¤Î¿ôÃͤǻØÄꤹ¤ë¡£
(ST-506 ¸ß´¹¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ç¤Ï¥Ç¥Ð¥¤¥¹¥¿¥¤¥×¤¬ 'hd' ¤Ç
Y ¤ÎÈÏ°Ï¤Ï 'a' ¤«¤é 'd'¡¢
SCSI ¥Ç¥£¥¹¥¯¤Ï 'sd' ¤Ç Y ¤Ï 'a' ¤«¤é 'e'¡¢
Atari ACSI ¥Ç¥£¥¹¥¯¤Ï 'ad' ¤Ç Y ¤Ï 'a' ¤«¤é 'e'¡¢
Syquest EZ135 ¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¥ê¥à¡¼¥Ð¥Ö¥ë¥Ç¥£¥¹¥¯¤Ï 'ez' ¤Ç Y ¤Ï 'a' ¤Î¤ß¡¢
XT ¥Ç¥£¥¹¥¯¤Ï 'xt' ¤Ç Y ¤Ï 'a' ¤« 'b'¡¢
¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ï 'fd' ¤Ç Y ¤Ë¤Ï¥É¥é¥¤¥ÖÈÖ¹æ¤ò»ØÄꤹ¤ë¡£
fd0 ¤Ï DOS ¤Î 'A:'¡¢fd1 ¤Ï 'B:' ¤ËÂбþ¤·¤Æ¤¤¤ë¡£
¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï¸ºß¤·¤Ê¤¤¤Î¤Ç N ¤Ï»ØÄꤷ¤Ê¤¤¡£)
ºÇ¿·¤Î¥«¡¼¥Í¥ë¤Ç¤Ï¡¢Â¾¤Ë¤â¼¡¤Î¤è¤¦¤Ê¿¤¯¤Î¥Ç¥Ð¥¤¥¹¥¿¥¤¥×¤ò»ØÄê¤Ç¤­¤ë
(¤Û¤È¤ó¤É¤Ï CD-ROM ¤À¤¬):
nfs, ram, scd, mcd, cdu535, aztcd, cm206cd, gscd, sbpcd, sonycd, bpcd¡£
(nfs ¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¥Ö¡¼¥È¤Ë¡¢ram ¤Ï RAM ¥Ç¥£¥¹¥¯¤ò»ÈÍѤ¹¤ë¾ì¹ç¤ËÍѤ¤¤ë¡£)

.\"O Note that this has nothing to do with the designation of these
.\"O devices on your file system.
.\"O The '/dev/' part is purely conventional.
¤Ê¤ª¡¢¤³¤ì¤é¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ç¤Î¥Ç¥Ð¥¤¥¹¤Î»ØÄêÊýË¡¤È¤ÏÁ´¤¯´Ø·¸¤Ê¤¤¡£
\&'/dev/' ¤òÍѤ¤¤ë¤Î¤Ïñ¤Ë´·½¬¤Ë²á¤®¤Ê¤¤¡£

.\"O The more awkward and less portable numeric specification of the above
.\"O possible root devices in major/minor format is also accepted.
.\"O (E.g., /dev/sda3 is major 8, minor 3, so you could use 'root=0x803' as an
.\"O alternative.)
°·¤¤¤Ë¤¯¤¤¤·°Ü¿¢À­¤âÎɤ¯¤Ê¤¤¤¬¡¢
¾åµ­¤Î¥Ç¥Ð¥¤¥¹¤ò major/minor ÈÖ¹æ¤Î¿ôÃͤǻØÄꤷ¤Æ¤â¤è¤¤¡£
(Î㤨¤Ð /dev/sda3 ¤Ï major ÈÖ¹æ 8¡¢minor ÈÖ¹æ 3 ¤Ê¤Î¤Ç¡¢
\&'root=0x803' ¤Èµ­½Ò¤Ç¤­¤ë¡£)
.TP
.\"O .B "'ro' and 'rw'"
.B "'ro' ¤È 'rw'"
.\"O The 'ro' option tells the kernel to mount the root file system
.\"O as 'readonly' so that file system consistency check programs (fsck)
.\"O can do their work on a quiescent file system.
.\"O No processes can
.\"O write to files on the file system in question until it is 'remounted'
.\"O as read/write capable, for example, by 'mount \-w \-n \-o remount /'.
.\"O (See also
.\"O .BR mount (8).)
\&'ro' ¥ª¥×¥·¥ç¥ó¤Ï¡¢¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò
¡ÖÆɤ߽Ф·ÀìÍѡפǥޥ¦¥ó¥È¤¹¤ë¤è¤¦¥«¡¼¥Í¥ë¤Ë»Ø¼¨¤·¡¢
fsck ¥×¥í¥°¥é¥à¤¬¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÌ·½â¤ò¸¡ºº¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¡£
¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¡ÖÆɤ߽ñ¤­²Äǽ¡×¤È¤·¤ÆºÆ¥Þ¥¦¥ó¥È¤µ¤ì¤ë
(¤Ä¤Þ¤ê 'mount \-w \-n \-o remount /') ¤Þ¤Ç¤Î´Ö¤Ï¡¢
¤¤¤«¤Ê¤ë¥×¥í¥»¥¹¤â¤³¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¥Õ¥¡¥¤¥ë¤Ë½ñ¤­¹þ¤à¤³¤È¤Ï¤Ç¤­¤Ê¤¤¡£
.RB ( mount (8)
¤â»²¾È¤»¤è¡£)

.\"O The 'rw' option tells the kernel to mount the root file system read/write.
.\"O This is the default.
rw ¥ª¥×¥·¥ç¥ó¤Ï¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò
¡ÖÆɤ߽ñ¤­²Äǽ¡×¤Ç¥Þ¥¦¥ó¥È¤¹¤ë¤è¤¦¥«¡¼¥Í¥ë¤Ë»Ø¼¨¤¹¤ë¡£
¤³¤Á¤é¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¢¤ë¡£

.\"O The choice between read-only and read/write can also be set using
.\"O .BR rdev (8).
¾Êά»þ¤Î»ØÄê¤ò¡ÖÆɤ߽Ф·ÀìÍѡפÈ
¡ÖÆɤ߽ñ¤­²Äǽ¡×¤È¤Î¤É¤Á¤é¤Ë¤¹¤ë¤«¤Ï¡¢
.BR rdev (8)
¤Ë¤è¤Ã¤Æ¤âÀßÄê¤Ç¤­¤ë¡£
.TP
.B "'reserve=...'"
.\"O This is used to protect I/O port regions from probes.
.\"O The form of the command is:
¥Ç¥Ð¥¤¥¹¤Î¼«Æ°¸¡½Ð¤«¤é I/O ¥Ý¡¼¥È¤òÊݸ¤ë¤¿¤á¤ËÍѤ¤¤ë¡£
¥³¥Þ¥ó¥É¤Î·Á¼°¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
.BI reserve= iobase,extent[,iobase,extent]...
.sp
.\"O In some machines it may be necessary to prevent device drivers from
.\"O checking for devices (auto-probing) in a specific region.
.\"O This may be
.\"O because of hardware that reacts badly to the probing, or hardware
.\"O that would be mistakenly identified, or merely
.\"O hardware you don't want the kernel to initialize.
µ¡¼ï¤Ë¤è¤Ã¤Æ¤Ï¡¢
¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Ë¤è¤ë¥Ç¥Ð¥¤¥¹¤Î¼«Æ°¸¡½Ð¤ò¡¢
ÆÃÄê¤ÎÈϰϤËÂФ·¤Æ¤Ï¶Ø»ß¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤¬¤¢¤ë¡£
¥Ï¡¼¥É¥¦¥§¥¢¤¬¸¡½ÐÆ°ºî¤Ë¤è¤Ã¤Æ¿¼¹ï¤ÊÌäÂê¤ò°ú¤­µ¯¤³¤¹¾ì¹ç¤ä¡¢
¸íǧ¼±¤µ¤ì¤ë²ÄǽÀ­¤¬¤¢¤ë¾ì¹ç¡¢
¤Þ¤¿Ã±¤Ë¥«¡¼¥Í¥ë¤Ë¥Ï¡¼¥É¥¦¥§¥¢¤ò½é´ü²½¤µ¤»¤¿¤¯¤Ê¤¤¾ì¹ç¤Ê¤É¤¬¤¢¤ê¤¦¤ë¤À¤í¤¦¡£

.\"O The reserve boot-time argument specifies an I/O port region that
.\"O shouldn't be probed.
.\"O A device driver will not probe a reserved region,
.\"O unless another boot argument explicitly specifies that it do so.
¤³¤Îµ¯Æ°»þ°ú¿ô reserve ¤Ï¡¢¼«Æ°¸¡½Ð¤ÎÂоݳ°¤È¤¹¤ë I/O ¥Ý¡¼¥È¤ÎÈϰϤò»ØÄꤹ¤ë¡£
¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Ï¡¢
¾¤Îµ¯Æ°»þ°ú¿ô¤Ë¤è¤Ã¤ÆÌÀ¼¨Åª¤Ë»ØÄꤵ¤ì¤Ê¤¤¸Â¤ê¡¢
ͽÌ󤵤줿ÈϰϤËÂФ·¤Æ¼«Æ°¸¡½ÐÆ°ºî¤ò¹Ô¤ï¤Ê¤¤¡£

.\"O For example, the boot line
Î㤨¤Ð¥Ö¡¼¥È»þ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ë
.IP
reserve=0x300,32  blah=0x300
.IP
.\"O keeps all device drivers except the driver for 'blah' from probing
.\"O 0x300-0x31f.
¤È»ØÄꤹ¤ë¤È¡¢'blah' ¤ò½ü¤¯¤¹¤Ù¤Æ¤Î¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Ï
0x300 ¤«¤é 0x31f ¤ÎÈϰϤò¼«Æ°¸¡½Ð¤ÎÂоݳ°¤È¤¹¤ë¡£
.TP
.B "'mem=...'"
.\"O The BIOS call defined in the PC specification that returns
.\"O the amount of installed memory was only designed to be able
.\"O to report up to 64MB.
.\"O Linux uses this BIOS call at boot to
.\"O determine how much memory is installed.
.\"O If you have more than 64MB of
.\"O RAM installed, you can use this boot arg to tell Linux how much memory
.\"O you have.
.\"O The value is in decimal or hexadecimal (prefix 0x),
.\"O and the suffixes 'k' (times 1024) or 'M' (times 1048576) can be used.
.\"O Here is a quote from Linus on usage of the 'mem=' parameter.
ÅëºÜ¤µ¤ì¤Æ¤¤¤ë¥á¥â¥ê¤ÎÎ̤òÊÖ¤¹ BIOS ¥³¡¼¥ë¤Ï
PC ¤Î»ÅÍͤÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¤¬¡¢¤³¤ì¤ÏºÇÂç 64MB ¤Þ¤Ç¤·¤«ÊÖ¤¹¤³¤È¤¬¤Ç¤­¤Ê¤¤¡£
Linux ¤ÏÅëºÜ¥á¥â¥ê¤ÎÎ̤òÄ´¤Ù¤ë¤¿¤á¤Ë¡¢
µ¯Æ°»þ¤Ë¤³¤Î BIOS ¥³¡¼¥ë¤ò»ÈÍѤ¹¤ë¡£
¤â¤· 64MB °Ê¾å¤Î RAM ¤òÅëºÜ¤·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
¤³¤Îµ¯Æ°»þ°ú¿ô¤òÍѤ¤¤Æ
¼ÂºÝ¤Î¥á¥â¥êÍÆÎ̤ò Linux ¤ËÃΤ餻¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
ÃÍ¤Ï 10 ¿Ê¿ô¤Þ¤¿¤Ï 16 ¿Ê¿ô (ÀèƬ¤Ë 0x ¤òÉÕ²Ã) ¤Î¿ôÃͤǻØÄꤷ¡¢
1024 Çܤòɽ¤¹ 'k' ¤Þ¤¿¤Ï 1048576 Çܤòɽ¤¹ 'M'
¤òËöÈø¤ËÉղäǤ­¤ë¡£
°Ê²¼¤Ï Linus ¤Ë¤è¤ë 'mem=' ¥Ñ¥é¥á¡¼¥¿¤Î²òÀâ¤Ç¤¢¤ë¡£

.in +0.5i
.\"O The kernel will accept any 'mem=xx' parameter you give it, and if it
.\"O turns out that you lied to it, it will crash horribly sooner or later.
.\"O The parameter indicates the highest addressable RAM address, so
.\"O \&'mem=0x1000000' means you have 16MB of memory, for example.
.\"O For a 96MB machine this would be 'mem=0x6000000'.
¥«¡¼¥Í¥ë¤Ï 'mem=xx' ¥Ñ¥é¥á¡¼¥¿¤È¤·¤Æ
¤É¤ó¤ÊÃͤò»ØÄꤷ¤Æ¤â¤½¤ì¤ò¤½¤Î¤Þ¤Þ¼õ¤±Æþ¤ì¤ë¡£
¤À¤«¤é¤½¤ì¤¬±³¤À¤È¤ï¤«¤Ã¤¿¤é¡¢
ÃÙ¤«¤ìÁᤫ¤ì¤Ò¤É¤¤¥¯¥é¥Ã¥·¥å¤ò¤¹¤ë¤À¤í¤¦¡£
¥Ñ¥é¥á¡¼¥¿¤Ï¥¢¥¯¥»¥¹¤·¤¦¤ëºÇ¤â¹â°Ì¤Î RAM ¥¢¥É¥ì¥¹¤ò»Ø¼¨¤¹¤ë¡£
¤À¤«¤éÎ㤨¤Ð 'mem=0x1000000' ¤Ã¤Æ¤¤¤¦¤Î¤Ï
16MB ¤Î¥á¥â¥ê¤¬¤¢¤ë¡¢¤È¤¤¤¦°ÕÌ£¤Ë¤Ê¤ë¡£
96MB ¤Î¥Þ¥·¥ó¤Ê¤é 'mem=0x6000000' ¤À¡£

.\"O .BR NOTE :
.\"O some machines might use the top of memory for BIOS
.\"O caching or whatever, so you might not actually have up to the full
.\"O 96MB addressable.
.\"O The reverse is also true: some chipsets will map
.\"O the physical memory that is covered by the BIOS area into the area
.\"O just past the top of memory, so the top-of-mem might actually be 96MB
.\"O + 384kB for example.
.\"O If you tell linux that it has more memory than
.\"O it actually does have, bad things will happen: maybe not at once, but
.\"O surely eventually.
.BR "Ãí°Õ" :
¥Þ¥·¥ó¤Ë¤è¤Ã¤Æ¤Ï¥á¥â¥ê¤ÎºÇ¾å°Ì¤ÎÎΰè¤ò BIOS ¤Î¥­¥ã¥Ã¥·¥å¤ä¤é²¿¤ä¤é¤Î
¤¿¤á¤Ë»È¤Ã¤Æ¤¤¤ë¤³¤È¤¬¤¢¤ë¤«¤é¡¢
¼ÂºÝ¤Ë¤Ï 96MB ¤ò¥Õ¥ë¤Ë¥¢¥É¥ì¥¹¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Ê¤¤¤«¤â¤·¤ì¤Ê¤¤¡£
µÕ¤Î¾ì¹ç¤â¤¢¤ë¡£
¤¤¤¯¤Ä¤«¤Î¥Á¥Ã¥×¥»¥Ã¥È¤Ç¤Ï¡¢
BIOS Îΰè¤ËÆþ¤Ã¤Æ¤¤¤ëʪÍý¥á¥â¥ê¤òºÇ¾å°Ì¤Î¥á¥â¥ê¤Î¤µ¤é¤Ë¾å¤Ë¥Þ¥Ã¥×¤¹¤ë¡£
¤è¤Ã¤ÆºÇ¾å°Ì¤Î¥á¥â¥ê¤Ï¤¿¤È¤¨¤Ð 96MB + 384kB ¤Ê¤ó¤ÆÃͤˤʤ뤫¤â¤·¤ì¤Ê¤¤¡£
linux ¤Ë¼ÂºÝ¤è¤ê¿¤¤¥á¥â¥ê¤ò¶µ¤¨¤Æ¤·¤Þ¤Ã¤¿¤È¤·¤¿¤é¡¢
¤Þ¤º¤¤¤³¤È¤¬µ¯¤­¤ë¤À¤í¤¦¡£
¤¹¤°¤Ë¤Ç¤Ï¤Ê¤¤¤«¤â¤·¤ì¤Ê¤¤¤±¤É¡¢¤æ¤¯¤æ¤¯¤Ï³Î¼Â¤Ë¤Í¡£
.in

.\"O You can also use the boot argument 'mem=nopentium' to turn off 4 MB
.\"O page tables on kernels configured for IA32 systems with a pentium or newer
.\"O CPU.
¤Þ¤¿¡¢µ¯Æ°»þ°ú¿ô¤Ë 'mem=nopentium' ¤ò»ØÄꤹ¤ë¤È¡¢
pentium ¤È¤½¤ì°Ê¹ß¤Î CPU ¤ò»È¤Ã¤¿ IA32 ¥·¥¹¥Æ¥àÍѤËÀßÄꤵ¤ì¤¿¥«¡¼¥Í¥ë¤Ç
4MB ¤Î¥Ú¡¼¥¸¥Æ¡¼¥Ö¥ë¤ò̵¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
.TP
.B "'panic=N'"
.\"O By default the kernel will not reboot after a panic, but this option
.\"O will cause a kernel reboot after N seconds (if N is greater than zero).
.\"O This panic timeout can also be set by "echo N > /proc/sys/kernel/panic".
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥«¡¼¥Í¥ë¤Ï¥Ñ¥Ë¥Ã¥¯¤Î¸å¥ê¥Ö¡¼¥È¤·¤Ê¤¤¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤Æ (N ¤ò 0 ¤è¤êÂ礭¤ÊÃͤȤ¹¤ì¤Ð)
N Éøå¤Ë¥ê¥Ö¡¼¥È¤¹¤ë¤è¤¦¤Ë¤Ê¤ë¡£
¤³¤ÎÃͤϡ¢µ¯Æ°¸å¤Ë "echo N > /proc/sys/kernel/panic"
¤È¤·¤ÆÀßÄꤹ¤ë¤³¤È¤â¤Ç¤­¤ë¡£
.TP
.B "'reboot=[warm|cold][,[bios|hard]]'"
.\"O (Only when
.\"O .B CONFIG_BUGi386
.\"O is defined.)
.\"O Since 2.0.22 a reboot is by default a cold reboot.
.\"O One asks for the old default with 'reboot=warm'.
.\"O (A cold reboot may be required to reset certain hardware,
.\"O but might destroy not yet written data in a disk cache.
.\"O A warm reboot may be faster.)
.\"O By default a reboot is hard, by asking the keyboard controller
.\"O to pulse the reset line low, but there is at least one type
.\"O of motherboard where that doesn't work.
.\"O The option 'reboot=bios' will
.\"O instead jump through the BIOS.
(¥«¡¼¥Í¥ë¥³¥ó¥Ñ¥¤¥ë»þ¤Ë
.B CONFIG_BUGi386
¤¬»ØÄꤵ¤ì¤¿¤È¤­¤Î¤ßÍ­¸ú¡£)
¥«¡¼¥Í¥ë¥Ð¡¼¥¸¥ç¥ó 2.0.22 ¤«¤é¡¢
¥ê¥Ö¡¼¥È¤Î¥Ç¥Õ¥©¥ë¥È¤Ï¥³¡¼¥ë¥É¥Ö¡¼¥È¤Ë¤Ê¤Ã¤¿¡£
°ÊÁ°¤Î¥Ç¥Õ¥©¥ë¥È¤Ç¤¢¤ë¥¦¥©¡¼¥à¥Ö¡¼¥È¤ò¤¹¤ë¤Ë¤Ï
\&'reboot=warm' ¤È»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
(¤¢¤ë¼ï¤Î¥Ï¡¼¥É¥¦¥§¥¢¤ò¥ê¥»¥Ã¥È¤¹¤ë¤Ë¤Ï¥³¡¼¥ë¥É¥Ö¡¼¥È¤¬É¬Íפˤʤ뤬¡¢
¥Ç¥£¥¹¥¯¥­¥ã¥Ã¥·¥å¤Ë¤¢¤ë½ñ¤­¹þ¤ó¤Ç¤¤¤Ê¤¤¥Ç¡¼¥¿¤ÏÇ˲õ¤µ¤ì¤ë¡£
¥¦¥©¡¼¥à¥Ö¡¼¥È¤Ç¤Ï¡¢¤è¤êÁÇÁ᤯¥ê¥Ö¡¼¥È¤Ç¤­¤ë¡£)
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥ê¥Ö¡¼¥È¤Ï 'hard' ¤Ç¹Ô¤ï¤ì¤ë¡£
¤¹¤Ê¤ï¤Á¥ê¥»¥Ã¥È¥é¥¤¥ó¤Ë low ¤ò½ÐÎϤ¹¤ë¤è¤¦¥­¡¼¥Ü¡¼¥É¥³¥ó¥È¥í¡¼¥é¤ËÍ׵ᤷ¤Æ¡¢
¥ê¥Ö¡¼¥È¤ò¹Ô¤¦¡£
¤·¤«¤·°ìÉô¤Î¥Þ¥¶¡¼¥Ü¡¼¥É¤Ç¤Ï¤³¤ì¤¬¤Ç¤­¤Ê¤¤¡£
\&'reboot=bios' ¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢
Âå¤ï¤ê¤Ë BIOS ¤ò·Ðͳ¤¹¤ë¤è¤¦¤Ë¤Ê¤ë¡£
.TP
.\"O .B "'nosmp'" and "'maxcpus=N'"
.B "'nosmp'" ¤È "'maxcpus=N'"
.\"O (Only when __SMP__ is defined.)
.\"O A command-line option of 'nosmp' or 'maxcpus=0' will disable SMP
.\"O activation entirely; an option 'maxcpus=N' limits the maximum number
.\"O of CPUs activated in SMP mode to N.
(¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤Ë __SMP__ ¤¬»ØÄꤵ¤ì¤¿¤È¤­¤Î¤ßÍ­¸ú¡£)
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Ë 'nosmp' ¤Þ¤¿¤Ï 'maxcpus=0' ¤ò»ØÄꤹ¤ë¤È¡¢
SMP (Symmetric Multi Processing) ¤ò´°Á´¤Ë̵¸ú¤Ë¤¹¤ë¡£
\&'maxcpus=N' ¥ª¥×¥·¥ç¥ó¤Ï¡¢
SMP ¥â¡¼¥É¤ÇÍ­¸ú¤Ë¤¹¤ë CPU ¤ÎºÇÂç¿ô¤ò N ¤ËÀ©¸Â¤¹¤ë¡£
.\"O .SS "Boot Arguments for Use by Kernel Developers"
.SS ¥«¡¼¥Í¥ë³«È¯¼ÔÍѤε¯Æ°»þ°ú¿ô
.TP
.B "'debug'"
.\"O Kernel messages are handed off to the kernel log daemon klogd so that they
.\"O may be logged to disk.
.\"O Messages with a priority above
.\"O .I console_loglevel
.\"O are also printed on the console.
.\"O (For these levels, see \fI<linux/kernel.h>\fP.)
.\"O By default this variable is set to log anything more important than
.\"O debug messages.
.\"O This boot argument will cause the kernel to also
.\"O print the messages of DEBUG priority.
.\"O The console loglevel can also be set at run time via an option
.\"O to klogd.
.\"O See
.\"O .BR klogd (8).
¥«¡¼¥Í¥ë¤¬½ÐÎϤ¹¤ë¥á¥Ã¥»¡¼¥¸¤Ï¥«¡¼¥Í¥ë¥í¥°¥Ç¡¼¥â¥ó klogd ¤ËÅϤµ¤ì¡¢
¥Ç¥£¥¹¥¯¤Ëµ­Ï¿¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ë¡£
¥×¥é¥¤¥ª¥ê¥Æ¥£¤¬
.I console_loglevel
¤Î¥á¥Ã¥»¡¼¥¸¤Ï¥³¥ó¥½¡¼¥ë¤Ë¤âɽ¼¨¤µ¤ì¤ë¡£
(¤³¤ì¤é¤Î¥ì¥Ù¥ë¤Ë¤Ä¤¤¤Æ¤Ï¡¢\fI<linux/kernel.h>\fP ¤ò»²¾È¡£)
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¤³¤ÎÊÑ¿ô¤Ï¡¢
¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤è¤ê¤â½ÅÍפʤ¢¤é¤æ¤ë¥á¥Ã¥»¡¼¥¸¤òµ­Ï¿¤¹¤ë¤è¤¦ÀßÄꤵ¤ì¤Æ¤¤¤ë
(¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤Ï´Þ¤Þ¤Ê¤¤)¡£
¤³¤Îµ¯Æ°»þ°ú¿ô¤ò»ØÄꤹ¤ë¤È¡¢
¥«¡¼¥Í¥ë¤Ï¥×¥é¥¤¥ª¥ê¥Æ¥£¤¬ DEBUG ¤Î¥á¥Ã¥»¡¼¥¸¤â½ÐÎϤ¹¤ë¤è¤¦¤Ë¤Ê¤ë¡£
.I console_loglevel
¤â klogd ¤Ë¥ª¥×¥·¥ç¥ó¤òÅϤ»¤Ð¼Â¹Ô»þ¤ËÀßÄê¤Ç¤­¤ë¡£
.BR klogd (8)
¤ò¸«¤è¡£
.TP
.B "'profile=N'"
.\"O It is possible to enable a kernel profiling function,
.\"O if one wishes to find out where the kernel is spending its CPU cycles.
.\"O Profiling is enabled by setting the variable
.\"O .I prof_shift
.\"O to a nonzero value.
.\"O This is done either by specifying
.\"O .B CONFIG_PROFILE
.\"O at compile time, or by giving the 'profile=' option.
.\"O compile time, or by giving the 'profile=' option.
.\"O Now the value that
.\"O .I prof_shift
.\"O gets will be N, when given, or
.\"O .BR CONFIG_PROFILE_SHIFT ,
.\"O when that is given, or 2, the default.
.\"O The significance of this variable is that it
.\"O gives the granularity of the profiling: each clock tick, if the
.\"O system was executing kernel code, a counter is incremented:
¥«¡¼¥Í¥ë¤¬¤É¤³¤Ç CPU ¥µ¥¤¥¯¥ë¤ò¾ÃÈñ¤·¤Æ¤¤¤ë¤«Ä´¤Ù¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢
¥«¡¼¥Í¥ë¤Î¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°µ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ì¤Ð¤³¤ì¤ò¼Â¸½¤Ç¤­¤ë¡£
¥«¡¼¥Í¥ë¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°¤Ï¡¢ÊÑ¿ô
.I prof_shift
¤ò 0 °Ê³°¤ÎÃͤ˥»¥Ã¥È¤¹¤ë¤ÈÍ­¸ú¤Ë¤Ê¤ë¡£
¤³¤ÎÃͤϥ³¥ó¥Ñ¥¤¥ë»þ¤Ë
.B CONFIG_PROFILE
¤Ç»ØÄꤹ¤ë¤«¡¢
¤³¤Î 'prifile=N' ¥ª¥×¥·¥ç¥ó¤Ç»ØÄê¤Ç¤­¤ë¡£
.I prof_shift
¤ÎÃÍ¤Ï N ¤¬»ØÄꤵ¤ì¤ì¤Ð N ¤È¤Ê¤ê¡¢N ¤¬»ØÄꤵ¤ì¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï
.B CONFIG_PROFILE_SHIFT
¤ÎÃͤ¬ÍѤ¤¤é¤ì¤ë¡£
¤É¤Á¤é¤â»ØÄꤵ¤ì¤Ê¤±¤ì¤Ð¥Ç¥Õ¥©¥ë¥ÈÃͤΠ2 ¤¬ÍѤ¤¤é¤ì¤ë¡£
¤³¤ÎÊÑ¿ô¤¬½ÅÍפʤΤϡ¢
¥«¡¼¥Í¥ë¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°¤ÎγÅÙ¤ò·èÄꤹ¤ë¤È¤³¤í¤Ë¤¢¤ë¡£
¤¹¤Ê¤ï¤Á¡¢³Æ¥¯¥í¥Ã¥¯¤Î³ä¹þ¤ß¤´¤È¤Ë¡¢¥·¥¹¥Æ¥à¤¬¥«¡¼¥Í¥ë¥³¡¼¥É¤ò¼Â¹Ô¤·¤Æ¤¤¤ì¤Ð¡¢
°Ê²¼¤Î¤è¤¦¤Ë¥«¥¦¥ó¥¿¤ÎÃͤ¬¥¤¥ó¥¯¥ê¥á¥ó¥È¤µ¤ì¤ë¡£
.IP
profile[address >> prof_shift]++;
.sp
.\"O The raw profiling information can be read from
.\"O .IR /proc/profile .
.\"O Probably you'll want to use a tool such as readprofile.c to digest it.
.\"O Writing to
.\"O .I /proc/profile
.\"O will clear the counters.
À¸¤Î¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°¾ðÊó¤Ï¡¢
.I /proc/profile
¤«¤é¸«¤ë¤³¤È¤¬¤Ç¤­¤ë¤¬¡¢readprofile.c
¤Î¤è¤¦¤Ê¾ðÊó¤ò²Ã¹©¤¹¤ë¥Ä¡¼¥ë¤ò»È¤Ã¤¿¤Û¤¦¤¬Îɤ¤¤À¤í¤¦¡£
.I /proc/profile
¤ËǤ°Õ¤Î¥Ç¡¼¥¿¤ò½ñ¹þ¤à¤È¡¢
¥«¥¦¥ó¥¿¤Ï¥ê¥»¥Ã¥È¤µ¤ì¤ë¡£
.TP
.B "'swap=N1,N2,N3,N4,N5,N6,N7,N8'"
.\"O Set the eight parameters max_page_age, page_advance, page_decline,
.\"O page_initial_age, age_cluster_fract, age_cluster_min, pageout_weight,
.\"O bufferout_weight that control the kernel swap algorithm.
.\"O For kernel tuners only.
¥«¡¼¥Í¥ë¤Î¥¹¥ï¥Ã¥×¥¢¥ë¥´¥ê¥º¥à¤ò¥³¥ó¥È¥í¡¼¥ë¤¹¤ë
¼¡¤Î 8 ¤Ä¤Î¥Ñ¥é¥á¡¼¥¿¤ò¥»¥Ã¥È¤¹¤ë¡£
max_page_age, page_advance,
page_decline, page_initial_age, age_cluster_fract,
age_cluster_min, pageout_weight, bufferout_weight.
¤³¤ì¤Ï¥«¡¼¥Í¥ë¤ò¥Á¥å¡¼¥ó¤¹¤ë¿Í¤Î¤¿¤á¤Î¥ª¥×¥·¥ç¥ó¤Ç¤¢¤ë¡£
.TP
.B "'buff=N1,N2,N3,N4,N5,N6'"
.\"O Set the six parameters max_buff_age, buff_advance, buff_decline,
.\"O buff_initial_age, bufferout_weight, buffermem_grace that control
.\"O kernel buffer memory management.
.\"O For kernel tuners only.
¥«¡¼¥Í¥ë¤Î¥Ð¥Ã¥Õ¥¡¥á¥â¥ê´ÉÍý¤ò¥³¥ó¥È¥í¡¼¥ë¤¹¤ë
¼¡¤Î 6 ¤Ä¤Î¥Ñ¥é¥á¡¼¥¿¤ò¥»¥Ã¥È¤¹¤ë¡£
max_buff_age, buff_advance,
buff_decline, buff_initial_age, bufferout_weight,
buffermem_grace.
¤³¤ì¤Ï¥«¡¼¥Í¥ë¤ò¥Á¥å¡¼¥ó¤¹¤ë¿Í¤Î¤¿¤á¤Î¥ª¥×¥·¥ç¥ó¤Ç¤¢¤ë¡£
.\"O .SS "Boot Arguments for Ramdisk Use"
.SS "RAM ¥Ç¥£¥¹¥¯´ØÏ¢¤Îµ¯Æ°»þ°ú¿ô"
.\"O (Only if the kernel was compiled with
.\"O .BR CONFIG_BLK_DEV_RAM .)
.\"O In general it is a bad idea to use a ramdisk under Linux\(emthe
.\"O system will use available memory more efficiently itself.
.\"O But while booting (or while constructing boot floppies)
.\"O it is often useful to load the floppy contents into a
.\"O ramdisk.
.\"O One might also have a system in which first
.\"O some modules (for file system or hardware) must be loaded
.\"O before the main disk can be accessed.
(¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤Ë
.B CONFIG_BLK_DEV_RAM
¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤¿¤È¤­¤Î¤ßÍ­¸ú¡£)
°ìÈÌŪ¤Ë¤Ï¡¢Linux ¤Ç RAM ¥Ç¥£¥¹¥¯¤ò»ÈÍѤ¹¤ë¤Î¤Ï¤¢¤Þ¤êÎɤ¤¹Í¤¨¤Ç¤Ï¤Ê¤¤¡£
¥·¥¹¥Æ¥à¤ËǤ¤»¤Æ¤ª¤±¤Ð¤â¤Ã¤È¸úΨŪ¤Ë¥á¥â¥ê¤ò»ÈÍѤ¹¤ë¡£
¤·¤«¤·¥Ö¡¼¥È»þ (¤Þ¤¿¤Ï¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤ÎºîÀ®Ãæ) ¤Ë¤Ï¡¢
¥Õ¥í¥Ã¥Ô¡¼¤ÎÆâÍƤò RAM ¥Ç¥£¥¹¥¯¤Ë¥í¡¼¥É¤¹¤ë¤ÈÊØÍø¤«¤â¤·¤ì¤Ê¤¤¡£
¥á¥¤¥ó¥Ç¥£¥¹¥¯¤¬¥¢¥¯¥»¥¹²Äǽ¤Ë¤Ê¤ëÁ°¤Ë¡¢
(¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ä¥Ï¡¼¥É¥¦¥§¥¢¤Ë´Ø¤¹¤ë)
¥â¥¸¥å¡¼¥ë¤ò¤¤¤¯¤Ä¤«¥í¡¼¥É¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¥·¥¹¥Æ¥à¤â¤¢¤ë¤À¤í¤¦¡£

.\"O In Linux 1.3.48, ramdisk handling was changed drastically.
.\"O Earlier, the memory was allocated statically, and there was
.\"O a 'ramdisk=N' parameter to tell its size.
.\"O (This could also
.\"O be set in the kernel image at compile time, or by use of
.\"O .BR rdev (8).)
.\"O These days ram disks use the buffer cache, and grow dynamically.
.\"O For a lot of information (e.g., how to use
.\"O .BR rdev (8)
.\"O in conjunction with the new ramdisk setup), see
.\"O .IR /usr/src/linux/Documentation/ramdisk.txt .
Linux ¤Î¥Ð¡¼¥¸¥ç¥ó 1.3.48 ¤Ë¤ª¤¤¤Æ¡¢
RAM ¥Ç¥£¥¹¥¯¤Î¼è¤ê°·¤¤¤¬º¬Ä줫¤éÊѲ½¤·¤¿¡£
¤½¤ì°ÊÁ°¤Þ¤Ç¤Ï¡¢¥á¥â¥ê¤ÏÀÅŪ¤Ë³ä¤êÅö¤Æ¤é¤ì¡¢
\&'ramdisk=N' ¥Ñ¥é¥á¡¼¥¿¤Ç¤½¤Î¥µ¥¤¥º¤ò»ØÄꤷ¤Æ¤¤¤¿¡£
(¤³¤ÎÃͤϥ«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤ä
.BR rdev (8)
¤Ë¤è¤Ã¤Æ¤âÊѹ¹¤Ç¤­¤¿¡£)
¸½ºß¤Ï RAM ¥Ç¥£¥¹¥¯¤Ï¥Ð¥Ã¥Õ¥¡¥­¥ã¥Ã¥·¥å¤ò»ÈÍѤ·¤Æ¤ª¤ê¡¢
ưŪ¤ËÀ®Ä¹¤¹¤ë¡£
¤µ¤é¤Ë¿¤¯¤Î¾ðÊó (¤¿¤È¤¨¤Ð
.BR rdev (8)
¤¬¿·¤·¤¤ RAM ¥Ç¥£¥¹¥¯¤ÎÀßÄê¤È¤É¤Î¤è¤¦¤Ë´Ø·¸¤¹¤ë¤«) ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
.I /usr/src/linux/Documentation/ramdisk.txt
¤ò»²¾È¡£

.\"O There are four parameters, two boolean and two integral.
4 ¤Ä¤Î¥Ñ¥é¥á¡¼¥¿¤¬¤¢¤ë¡£ÏÀÍýÃͤò¤È¤ë¤â¤Î¤¬ 2 ¤Ä¡¢À°¿ôÃͤò¤È¤ë¤â¤Î¤¬ 2 ¤Ä¡£
.TP
.B "'load_ramdisk=N'"
.\"O If N=1, do load a ramdisk.
.\"O If N=0, do not load a ramdisk.
.\"O (This is the default.)
N=1 ¤Ê¤é RAM ¥Ç¥£¥¹¥¯¤ò¥í¡¼¥É¤¹¤ë¡£N=0 ¤Ê¤é¥í¡¼¥É¤·¤Ê¤¤ (¥Ç¥Õ¥©¥ë¥È)¡£
.TP
.B "'prompt_ramdisk=N'"
.\"O If N=1, do prompt for insertion of the floppy.
.\"O (This is the default.)
.\"O If N=0, do not prompt.
.\"O (Thus, this parameter is never needed.)
N=1 ¤Ê¤é¥Õ¥í¥Ã¥Ô¡¼ÁÞÆþ¤òÂ¥¤¹¥×¥í¥ó¥×¥È¤ò½Ð¤¹ (¥Ç¥Õ¥©¥ë¥È)¡£
N=0 ¤Ê¤é¥×¥í¥ó¥×¥È¤ò½Ð¤µ¤Ê¤¤¡£
(½¾¤Ã¤Æ¡¢¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ò»ØÄꤹ¤ëɬÍפϤޤºÌµ¤¤¤Ç¤¢¤í¤¦¡£)
.TP
.\"O .BR 'ramdisk_size=N' " or (obsolete) " 'ramdisk=N'
.BR 'ramdisk_size=N' " ¤â¤·¤¯¤Ï (¸Å¤¤·Á¼°¤Î) " 'ramdisk=N'
.\"O Set the maximal size of the ramdisk(s) to N kB.
.\"O The default is 4096 (4 MB).
¥é¥à¥Ç¥£¥¹¥¯¤ÎºÇÂ祵¥¤¥º¤ò N kB (¥­¥í¥Ð¥¤¥È) ¤Ë¥»¥Ã¥È¤¹¤ë¡£
¾Êά»þ¤Ï 4096 (4 MB)¡£
.TP
.B "'ramdisk_start=N'"
.\"O Sets the starting block number (the offset on the floppy where
.\"O the ramdisk starts) to N.
.\"O This is needed in case the ramdisk follows a kernel image.
³«»Ï¥Ö¥í¥Ã¥¯ÈÖ¹æ
(¥Õ¥í¥Ã¥Ô¡¼ÀèƬ¤«¤é¤Î¥ª¥Õ¥»¥Ã¥È¤Ç»ØÄꤷ¤¿ RAM ¥Ç¥£¥¹¥¯¤Î³«»ÏÅÀ)
¤ò N ¤Ë¥»¥Ã¥È¤¹¤ë¡£
¤³¤ì¤Ï¥«¡¼¥Í¥ë¥¤¥á¡¼¥¸¤Î¤¢¤È¤Ë RAM ¥Ç¥£¥¹¥¯¥¤¥á¡¼¥¸¤òÃÖ¤¯¾ì¹ç¤ËɬÍפȤʤ롣
.TP
.B "'noinitrd'"
.\"O (Only if the kernel was compiled with
.\"O .B CONFIG_BLK_DEV_RAM
.\"O and
.\"O .BR CONFIG_BLK_DEV_INITRD .)
.\"O These days it is possible to compile the kernel to use initrd.
.\"O When this feature is enabled, the boot process will load the kernel
.\"O and an initial ramdisk; then the kernel converts initrd into
.\"O a "normal" ramdisk, which is mounted read-write as root device;
.\"O then /linuxrc is executed; afterward the "real" root file system is mounted,
.\"O and the initrd file system is moved over to /initrd; finally
.\"O the usual boot sequence (e.g., invocation of /sbin/init) is performed.
(¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤Ë
.B CONFIG_BLK_DEV_RAM
¤È
.B CONFIG_BLK_DEV_INITRD
¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤È¤­¤Î¤ßÍ­¸ú¡£)
ºÇ¶á¤Ï initrd ¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë¥«¡¼¥Í¥ë¤ò¥³¥ó¥Ñ¥¤¥ë¤Ç¤­¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤ë¤È¡¢
¥Ö¡¼¥È¥×¥í¥»¥¹¤Ï¥«¡¼¥Í¥ë¤È RAM ¥Ç¥£¥¹¥¯¤ò¥í¡¼¥É¤·¡¢
¥«¡¼¥Í¥ë¤Ï initrd ¤ò¡ÖÉáÄÌ¤Î¡× RAM ¥Ç¥£¥¹¥¯¤ËÊÑ´¹¤·¡¢
¤³¤Î RAM ¥Ç¥£¥¹¥¯¤¬¥ë¡¼¥È¥Ç¥Ð¥¤¥¹¤È¤·¤Æ¡ÖÆɤ߽ñ¤­²Äǽ¡×¤Ç¥Þ¥¦¥ó¥È¤µ¤ì¤ë¡£
¼¡¤Ë /linuxrc ¤¬¼Â¹Ô¤µ¤ì¤ë¡£
¤½¤Î¸å¡Ö¿¿¤Î¡×¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥Þ¥¦¥ó¥È¤µ¤ì¡¢
initrd ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï /initrd ¤Ë°Ü¤µ¤ì¤ë¡£
ºÇ¸å¤ËÄ̾ï¤Î¥Ö¡¼¥È¥·¡¼¥±¥ó¥¹ (¶ñÂÎŪ¤Ë¤Ï /sbin/init ¤Î¸Æ¤Ó½Ð¤·) ¤¬¼Â¹Ô¤µ¤ì¤ë¡£

.\"O For a detailed description of the initrd feature, see
.\"O .IR /usr/src/linux/Documentation/initrd.txt .
initrd ¤Ë´Ø¤¹¤ë¾ÜºÙ¤Ê²òÀâ¤Ï
.I /usr/src/linux/Documentation/initrd.txt
¤ò»²¾È¡£

.\"O The 'noinitrd' option tells the kernel that although it was compiled for
.\"O operation with initrd, it should not go through the above steps, but
.\"O leave the initrd data under
.\"O .IR /dev/initrd .
.\"O (This device can be used only once: the data is freed as soon as
.\"O the last process that used it has closed
.\"O .IR /dev/initrd .)
\&'noinitrd' ¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤ë¤È¡¢
¥«¡¼¥Í¥ë¤Ï (initrd Æ°ºî¤ò¹Ô¤¦¤è¤¦¤Ë¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ç¤â)
¾åµ­¤ÎÆ°ºî¤ò¹Ô¤Ê¤ï¤º¡¢Âå¤ï¤ê¤Ë initrd ¤Î¥Ç¡¼¥¿¤ò
.I /dev/initrd
¤Ë»Ä¤¹¡£
(¤³¤Î¥Ç¥Ð¥¤¥¹¤Ï°ìÅÙ¤·¤«»È¤¨¤Ê¤¤¡£
¥Ç¡¼¥¿¤Ï¡¢¤½¤Î¥Ç¡¼¥¿¤ò»È¤Ã¤¿ºÇ¸å¤Î¥×¥í¥»¥¹¤¬
.I /dev/initrd
¤ò¥¯¥í¡¼¥º¤¹¤ë¤È¤¹¤°¤Ë²òÊü¤µ¤ì¤ë¡£)
.\"O .SS "BOOT ARGUMENTS FOR SCSI DEVICES"
.SS "SCSI ¥Ç¥Ð¥¤¥¹ÍѤε¯Æ°»þ°ú¿ô"
.\"O General notation for this section:
¤³¤ÎÀá¤Ë¤ª¤±¤ëÍѸ졧

.\"O .I iobase
.\"O -- the first I/O port that the SCSI host occupies.
.\"O These are specified in hexadecimal notation,
.\"O and usually lie in the range from 0x200 to 0x3ff.
.I iobase
-- SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤¬ÀêÍ­¤¹¤ë I/O ¥Ý¡¼¥È¤ÎÀèƬ¥¢¥É¥ì¥¹¡£
16 ¿Êɽµ­¤Ç»ØÄꤷ¡¢Ä̾ï 0x200 ¤«¤é 0x3ff ¤ÎÈϰϤ˰ÌÃÖ¤¹¤ë¡£

.\"O .I irq
.\"O -- the hardware interrupt that the card is configured to use.
.\"O Valid values will be dependent on the card in question, but will
.\"O usually be 5, 7, 9, 10, 11, 12, and 15.
.\"O The other values are usually
.\"O used for common peripherals like IDE hard disks, floppies, serial
.\"O ports, etc.
.I irq
-- ¥«¡¼¥É¤¬ÍøÍѤ¹¤ë¥Ï¡¼¥É¥¦¥§¥¢³ä¤ê¹þ¤ß¡£Í­¸ú¤ÊÃͤϥ«¡¼¥É¤Ë
¤è¤Ã¤Æ°Û¤Ê¤ë¤¬¡¢Ä̾ï¤Ï 5, 7, 9, 10, 11, 12, 15 ¤Ç¤¢¤ë¡£
¤³¤ì°Ê³°¤ÎÃͤÏÄ̾IDE ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¡¢¥Õ¥í¥Ã¥Ô¡¼¡¢
¥·¥ê¥¢¥ë¥Ý¡¼¥È¤È¤¤¤Ã¤¿°ìÈÌŪ¤Ê¼þÊÕµ¡´ï¤Ë¤è¤Ã¤Æ»ÈÍѤµ¤ì¤ë¡£

.\"O .I scsi-id
.\"O -- the ID that the host adapter uses to identify itself on the
.\"O SCSI bus.
.\"O Only some host adapters allow you to change this value, as
.\"O most have it permanently specified internally.
.\"O The usual default value
.\"O is 7, but the Seagate and Future Domain TMC-950 boards use 6.
.I scsi-id
-- SCSI ¥Ð¥¹¾å¤Î¥Û¥¹¥È¥¢¥À¥×¥¿¤¬¼«Ê¬¼«¿È¤ò¼±Ê̤¹¤ë¤¿¤á¤Ë»ÈÍѤ¹¤ë ID Èֹ档
¤³¤ÎÃͤòÊѹ¹¤Ç¤­¤ë¥Û¥¹¥È¥¢¥À¥×¥¿¤â¤´¤¯´õ¤Ë¸ºß¤¹¤ë¤¬¡¢
¤Û¤È¤ó¤É¤Ï¥¢¥À¥×¥¿ÆâÉô¤Ç¸ÇÄꤵ¤ì¤Æ¤¤¤ë¡£
¤è¤¯»È¤ï¤ì¤ë¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 7 ¤Ç¤¢¤ë¤¬¡¢Seagate ¤â¤·¤¯¤Ï
Future Domain À½¤Î TMC-950 ¥Ü¡¼¥É¤Ç¤Ï 6 ¤¬»È¤ï¤ì¤ë¡£

.\"O .I parity
.\"O -- whether the SCSI host adapter expects the attached devices
.\"O to supply a parity value with all information exchanges.
.\"O Specifying a one indicates parity checking is enabled,
.\"O and a zero disables parity checking.
.\"O Again, not all adapters will support selection of parity
.\"O behavior as a boot argument.
.I parity
-- SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤¬¼è¤êÉÕ¤±¤é¤ì¤¿¥Ç¥Ð¥¤¥¹¤È¤ÎÄÌ¿®¤ËºÝ¤·¤Æ
¥Ñ¥ê¥Æ¥£ÃͤòɬÍפȤ¹¤ë¤«¤É¤¦¤«¡£
1 ¤ò»ØÄꤹ¤ë¤È¥Ñ¥ê¥Æ¥£¥Á¥§¥Ã¥¯¤¬Í­¸ú¤Ë¤Ê¤ê¡¢
0 ¤Ç¥Ñ¥ê¥Æ¥£¥Á¥§¥Ã¥¯¤¬Ìµ¸ú¤Ë¤Ê¤ë¡£
¤·¤«¤·¡¢¤¹¤Ù¤Æ¤Î¥Ç¥Ð¥¤¥¹¤¬¤³¤Îµ¯Æ°»þ°ú¿ô¤Ë¤è¤ë¥Ñ¥ê¥Æ¥£¤ÎÁªÂò¤ò
¥µ¥Ý¡¼¥È¤¹¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¡£
.TP
.B "'max_scsi_luns=...'"
.\"O A SCSI device can have a number of 'subdevices' contained within
.\"O itself.
.\"O The most common example is one of the new SCSI CD-ROMs that
.\"O handle more than one disk at a time.
.\"O Each CD is addressed as a
.\"O \&'Logical Unit Number' (LUN) of that particular device.
.\"O But most
.\"O devices, such as hard disks, tape drives and such are only one device,
.\"O and will be assigned to LUN zero.
SCSI ¥Ç¥Ð¥¤¥¹¤ÏÊ£¿ô¤Î¡Ö¥µ¥Ö¥Ç¥Ð¥¤¥¹¡×¤ò¼«Ê¬¼«¿È¤ÎÆâÉô¤Ë»ý¤Ä¤³¤È¤¬¤Ç¤­¤ë¡£
ºÇ¤â¤è¤¯¤¢¤ëÎã¤È¤·¤Æ¡¢°ì»þ¤Ë 1 Ëç°Ê¾å¤Î¥Ç¥£¥¹¥¯¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤ë
(¥Á¥§¥ó¥¸¥ã¡¼µ¡Ç½ÉÕ¤Î) SCSI CD-ROM ¤¬¤¢¤ë¡£
¤½¤ì¤¾¤ì¤Î CD ¤Ï¤½¤Î¥Ç¥Ð¥¤¥¹¤Î
¡ÖÏÀÍý¥æ¥Ë¥Ã¥ÈÈÖ¹æ (LUN)¡×¤Ë¤è¤Ã¤ÆÆÃÄꤵ¤ì¤ë¡£
¤·¤«¤·¤Û¤È¤ó¤É¤Î¥Ç¥Ð¥¤¥¹ (Î㤨¤Ð¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ä¥Æ¡¼¥×¥É¥é¥¤¥Ö) ¤Ï¡¢
LUN ÈÖ¹æ 0 ¤¬³ä¤êÅö¤Æ¤é¤ì¤¿¡¢¤¿¤À¤Ò¤È¤Ä¤Î¥Ç¥Ð¥¤¥¹¤«¤é¤Ê¤ë¡£

.\"O Some poorly designed SCSI devices cannot handle being probed for
.\"O LUNs not equal to zero.
.\"O Therefore, if the compile-time flag
.\"O .B CONFIG_SCSI_MULTI_LUN
.\"O is not set, newer kernels will by default
.\"O only probe LUN zero.
À߷פ¬ÉÔ½½Ê¬¤Ê SCSI ¥Ç¥Ð¥¤¥¹¤Ç¤Ï 0 °Ê³°¤Î LUN ÈÖ¹æ¤Ø¤Î¼«Æ°¸¡½Ð¤ò
°·¤¨¤Ê¤¤¤³¤È¤¬¤¢¤ë¡£
¤·¤¿¤¬¤Ã¤Æ¡¢¥³¥ó¥Ñ¥¤¥ë»þ¤Ë
.B CONFIG_SCSI_MULTI_LUN
¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¡¢
ºÇ¶á¤Î¥«¡¼¥Í¥ë¤Ç¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï LUN ÈÖ¹æ 0 ¤Î¤ß¤ò¸¡½Ð¤¹¤ë¡£

.\"O To specify the number of probed LUNs at boot, one enters
.\"O \&'max_scsi_luns=n' as a boot arg, where n is a number between one and
.\"O eight.
.\"O To avoid problems as described above, one would use n=1 to
.\"O avoid upsetting such broken devices.
µ¯Æ°»þ¤ËÄ´¤Ù¤ë LUN ÈÖ¹æ¤ò»ØÄꤹ¤ë¾ì¹ç¡¢µ¯Æ°»þ°ú¿ô¤È¤·¤Æ
\&'max_scsi_luns=n' ¤ò»ØÄꤹ¤ë¡£n ¤Ï 1 ¤«¤é 8 ¤Î´Ö¤Ç»ØÄꤹ¤ë¡£
n=1 °Ê¾å¤ÎÃͤò»ÈÍѤ·¤Ê¤¤¤è¤¦¤Ë¤¹¤ì¤Ð¡¢
¤³¤Î¤è¤¦¤Ê¤¤¤«¤ì¤¿µ¡³£¤Ë¤Ò¤É¤¤Ìܤˤ¢¤ï¤µ¤ì¤º¤Ë¤¹¤à¤À¤í¤¦¡£
.TP
.\"O .B "SCSI tape configuration"
.B SCSI ¥Æ¡¼¥×¥É¥é¥¤¥Ö¤ÎÀßÄê
.\"O Some boot time configuration of the SCSI tape driver can be achieved
.\"O by using the following:
SCSI ¥Æ¡¼¥×¥É¥é¥¤¥Ð¤Îµ¯Æ°»þÀßÄê¤Î°ìÉô¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤ë¡£
.IP
.BI st= buf_size[,write_threshold[,max_bufs]]
.sp
.\"O The first two numbers are specified in units of kB.
.\"O The default
.\"O .I buf_size
.\"O is 32kB, and the maximum size that can be specified is a
.\"O ridiculous 16384kB.
.\"O The
.\"O .I write_threshold
.\"O is the value at which the buffer is committed to tape, with a
.\"O default value of 30kB.
.\"O The maximum number of buffers varies
.\"O with the number of drives detected, and has a default of two.
.\"O An example usage would be:
ºÇ½é¤Î 2 ¤Ä¤Î¿ô»ú¤Ï kB ñ°Ì¤Ç»ØÄꤹ¤ë¡£
.I buf_size
¤Î¥Ç¥Õ¥©¥ë¥È¤Ï 32kB ¤Ç¤¢¤ë¡£¾å¸Â¤Ï 16384kB ¤Þ¤Ç»ØÄê¤Ç¤­¤ë¡£
.I write_threshold
¤Ï¥Ç¡¼¥¿½ñ¤­½Ð¤·¤ÎïçÃͤǡ¢
¥Ð¥Ã¥Õ¥¡¤Î¥Ç¡¼¥¿¤Î¥µ¥¤¥º¤¬¤³¤ÎÃͤò±Û¤¨¤ë¤È¥Ç¡¼¥¿¤Ï¥Æ¡¼¥×¤Ë½ñ¤­½Ð¤µ¤ì¤ë¡£
¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 30kB ¤Ç¤¢¤ë¡£
¥Ð¥Ã¥Õ¥¡¿ô¤ÎºÇÂçÃÍ
.RI ( max_bufs )
¤Ï¸¡½Ð¤µ¤ì¤¿¥É¥é¥¤¥Ö¤Î¿ô¤Ë¤è¤Ã¤ÆÊѲ½¤¹¤ë¤¬¡¢¥Ç¥Õ¥©¥ë¥È¤Ï 2 ¤Ç¤¢¤ë¡£
»ÈÍÑÎã¤ò°Ê²¼¤Ë¼¨¤¹¡£
.IP
st=32,30,2
.IP
.\"O Full details can be found in the file
.\"O .I Documentation/scsi/st.txt
.\"O (or
.\"O .I drivers/scsi/README.st
.\"O for older kernels) in the kernel source.
¾ÜºÙ¤Ï¥«¡¼¥Í¥ë¥½¡¼¥¹Æâ¤Î
.I Documentation/scsi/st.txt
(¸Å¤¤¥«¡¼¥Í¥ë¤Î¾ì¹ç¤Ï
.IR drivers/scsi/README.st )
¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¡£
.TP
.\"O .B "Adaptec aha151x, aha152x, aic6260, aic6360, SB16-SCSI configuration"
.B Adaptec aha151x, aha152x, aic6260, aic6360, SB16-SCSI ¤ÎÀßÄê
.\"O The aha numbers refer to cards and the aic numbers refer to the actual
.\"O SCSI chip on these type of cards, including the Soundblaster-16 SCSI.
aha ¤Ë³¤¯ÈÖ¹æ¤Ï¥«¡¼¥É¤òɽ¤·¡¢
aic ¤Ë³¤¯ÈÖ¹æ¤Ï¥«¡¼¥É¤ËÅëºÜ¤µ¤ì¤Æ¤¤¤ë¼ÂºÝ¤Î¥Á¥Ã¥×¤òɽ¤¹
(Soundblaster-16 SCSI ¤â¸å¼Ô¤Ë´Þ¤Þ¤ì¤ë)¡£

.\"O The probe code for these SCSI hosts looks for an installed BIOS, and
.\"O if none is present, the probe will not find your card.
.\"O Then you will
.\"O have to use a boot arg of the form:
SCSI ¥Û¥¹¥È¤Î¸¡½Ð¥³¡¼¥É¤Ï¡¢
¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë BIOS ¤òõ¤¹¡£
¸«¤Ä¤«¤é¤Ê¤¤¤È¡¢¥«¡¼¥É¤Ï¸¡½Ð¤Ç¤­¤Ê¤¤¡£
¤³¤Î¾ì¹ç¤Ï°Ê²¼¤Î¤è¤¦¤Ëµ¯Æ°»þ°ú¿ô¤ò»ØÄꤹ¤ë¤³¤È¤Ë¤Ê¤ë¡£
.IP
.BI aha152x= iobase[,irq[,scsi-id[,reconnect[,parity]]]]
.IP
.\"O If the driver was compiled with debugging enabled, a sixth
.\"O value can be specified to set the debug level.
¤â¤·¥É¥é¥¤¥Ð¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¥Ç¥Ð¥Ã¥°¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æ¤¤¤¿¾ì¹ç¤Ï¡¢
6 ÈÖÌܤÎÃͤǥǥХå°¥ì¥Ù¥ë¤ò»ØÄê¤Ç¤­¤ë¡£

.\"O All the parameters are as described at the top of this section, and the
.\"O .I reconnect
.\"O value will allow device disconnect/reconnect if a nonzero value
.\"O is used.
.\"O An example usage is as follows:
¤¹¤Ù¤Æ¤Î¥Ñ¥é¥á¡¼¥¿¤Ï¡¢¤³¤Î¥»¥¯¥·¥ç¥ó¤ÎºÇ½é¤ÇÀâÌÀ¤·¤¿Ä̤ê¤Ç¤¢¤ë¡£
.I reconnect
¤Ë 0 °Ê³°¤ÎÃͤò»ØÄꤹ¤ë¤È¡¢¥Ç¥Ð¥¤¥¹¤òÀÚÃǤ·¤¿¤êÀܳ¤·¤¿¤ê¤Ç¤­¤ë¡£
°Ê²¼¤ËÎã¤ò¼¨¤¹¡£
.IP
aha152x=0x340,11,7,1
.IP
.\"O Note that the parameters must be specified in order, meaning that if
.\"O you want to specify a parity setting, then you will have to specify an
.\"O iobase, irq, scsi-id and reconnect value as well.
¥Ñ¥é¥á¡¼¥¿¤Ïɬ¤º¾åµ­¤Î½çÈ֤ɤª¤ê¤Ë»ØÄꤵ¤ì¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
Î㤨¤Ð¡¢¥Ñ¥ê¥Æ¥£ (parity) ¤òÀßÄꤷ¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢
iobase, irq, scsi-id, reconnect ¤âƱ»þ¤Ë»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¡£
.TP
.\"O .B "Adaptec aha154x configuration"
.B Adaptec aha154x ¤ÎÀßÄê
.\"O The aha1542 series cards have an i82077 floppy controller onboard,
.\"O while the aha1540 series cards do not.
.\"O These are busmastering cards,
.\"O and have parameters to set the ''fairness'' that is used to share
.\"O the bus with other devices.
.\"O The boot arg looks like the following.
aha1542 ¥·¥ê¡¼¥º¤Î¥«¡¼¥É¤Ï
i82077 ¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¥³¥ó¥È¥í¡¼¥é¤ò¥Ü¡¼¥É¤ËÅëºÜ¤·¤Æ¤¤¤ë¡£
°ìÊý aha1540 ¥·¥ê¡¼¥º¤Î¥«¡¼¥É¤ÏÅëºÜ¤·¤Æ¤¤¤Ê¤¤¡£
¤³¤ì¤é¤Ï¶¦¤Ë¥Ð¥¹¥Þ¥¹¥¿¥«¡¼¥É¤Ç¤¢¤ê¡¢
¾¤Î¥Ç¥Ð¥¤¥¹¤È¥Ð¥¹¤ò¶¦Í­¤¹¤ëºÝ¤Ë¡¢
¤É¤Î¤¯¤é¤¤¡Ö¥Õ¥§¥¢¤Ë¡×¿¶¤ëÉñ¤¦¤«¤ò»ØÄꤹ¤ë¥Ñ¥é¥á¡¼¥¿¤¬¤¢¤ë¡£
µ¯Æ°»þ°ú¿ô¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ»ØÄꤹ¤ë¡£
.IP
.BI aha1542= iobase[,buson,busoff[,dmaspeed]]
.IP
.\"O Valid iobase values are usually one of: 0x130, 0x134, 0x230, 0x234,
.\"O 0x330, 0x334.
.\"O Clone cards may permit other values.
Í­¸ú¤Ê iobase ¤ÎÃͤϼ¡¤ÎÄ̤ꡣ
0x130, 0x134, 0x230, 0x234, 0x330, 0x334¡£
¥¯¥í¡¼¥ó¥«¡¼¥É¤ÎÃæ¤Ë¤Ï¾¤ÎÃͤò»ØÄê¤Ç¤­¤ë¤â¤Î¤â¤¢¤ë¡£

.\"O The
.\"O .IR buson ", " busoff
.\"O values refer to the number of microseconds that the
.\"O card dominates the ISA bus.
.\"O The defaults are 11us on, and 4us off, so
.\"O that other cards (such as an ISA LANCE Ethernet card) have a chance to
.\"O get access to the ISA bus.
.IR buson ", " busoff
Ãͤϥ«¡¼¥É¤¬ISA ¥Ð¥¹¤òÀêÍ­¤¹¤ë»þ´Ö¤ò¥Þ¥¤¥¯¥íÉÃñ°Ì¤Ç»ØÄꤹ¤ë¡£
¾Êά»þ¤Ï¤½¤ì¤¾¤ì 11us on ¤È 4us off ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¡¢
¾¤Î¥«¡¼¥É (Î㤨¤Ð ISA LANCE ¥¤¡¼¥µ¥Í¥Ã¥È¥«¡¼¥É) ¤â
ISA ¥Ð¥¹¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¡£

.\"O The
.\"O .I dmaspeed
.\"O value refers to the rate (in MB/s) at which the DMA
.\"O (Direct Memory Access) transfers proceed.
.\"O The default is 5MB/s.
.\"O Newer revision cards allow you to select this value as part of the
.\"O soft-configuration, older cards use jumpers.
.\"O You can use values up to
.\"O 10MB/s assuming that your motherboard is capable of handling it.
.\"O Experiment with caution if using values over 5MB/s.
.I dmaspeed
ÃÍ¤Ï DMA (Direct Memory Access) žÁ÷®ÅÙ¤ò MB/s ñ°Ì¤ÇÀßÄꤹ¤ë¡£
¾Êά»þ¤Ï 5MB/s ¤Ç¤¢¤ë¡£¿·¤·¤¤¥ê¥Ó¥¸¥ç¥ó¤Î¥«¡¼¥É¤Ç¤Ï¡¢
¤³¤ÎÃͤò»È¤Ã¤¿¥½¥Õ¥È¥¦¥§¥¢¤Ë¤è¤ëÀßÄ꤬¤Ç¤­¤ë¡£
¸Å¤¤¥«¡¼¥É¤Ï¥¸¥ã¥ó¥ÑÀßÄê¤òɬÍפȤ¹¤ë¡£
¥Þ¥¶¡¼¥Ü¡¼¥É¤¬Âбþ¤·¤Æ¤¤¤ì¤ÐºÇÂç 10MB/s ¤Þ¤Ç»ØÄê²Äǽ¤Ç¤¢¤ë¡£
5MB/s °Ê¾å¤ÎÃͤò»È¤¦¾ì¹ç¤ÏÃí°Õ¤·¤Æ¼Â¸³¤·¤Æ¤«¤é¤Ë¤¹¤ë¤³¤È¡£
.TP
.\"O .B "Adaptec aha274x, aha284x, aic7xxx configuration"
.B Adaptec aha274x, aha284x, aic7xxx ¤ÎÀßÄê
.\"O These boards can accept an argument of the form:
¤³¤ì¤é¤Î¥Ü¡¼¥É¤Ï°Ê²¼¤Î·Á¼°¤Ç»ØÄꤹ¤ë¡£
.IP
.BI aic7xxx= extended,no_reset
.IP
.\"O The
.\"O .I extended
.\"O value, if nonzero, indicates that extended translation for large
.\"O disks is enabled.
.\"O The
.\"O .I no_reset
.\"O value, if nonzero, tells the driver not to reset the SCSI bus when
.\"O setting up the host adapter at boot.
.I extended
Ãͤ¬ 0 °Ê³°¤Î»þ¤Ï¡¢ÂçÍÆÎ̥ǥ£¥¹¥¯ÍѤγÈÄ¥ÊÑ´¹¤¬Í­¸ú¤Ë¤Ê¤ë¡£
.I no_reset
Ãͤò 0 °Ê³°¤ÎÃͤˤ¹¤ë¤È¡¢¥Û¥¹¥È¥¢¥À¥×¥¿¤Î¸¡½Ð»þ¤Ë¡¢
¥É¥é¥¤¥Ð¤Ë¤è¤ë SCSI ¥Ð¥¹¤Î½é´ü²½¤ò¹Ô¤ï¤Ê¤¤¡£
.TP
.\"O .B "AdvanSys SCSI Hosts configuration ('advansys=')"
.B "AdvanSys SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤ÎÀßÄê ('advansys=')"
.\"O The AdvanSys driver can accept up to four i/o addresses that will be
.\"O probed for an AdvanSys SCSI card.
.\"O Note that these values (if used) do
.\"O not effect EISA or PCI probing in any way.
.\"O They are only used for
.\"O probing ISA and VLB cards.
.\"O In addition, if the driver has been
.\"O compiled with debugging enabled, the level of debugging output can be
.\"O set by adding an 0xdeb[0-f] parameter.
.\"O The 0-f allows setting the
.\"O level of the debugging messages to any of 16 levels of verbosity.
AdvanSys ¥É¥é¥¤¥Ð¤Ï¥«¡¼¥É¤Î¸¡½ÐÀè¤È¤·¤Æ
4 ¤Ä¤Î I/O ¥¢¥É¥ì¥¹¤ò¼õ¤±ÉÕ¤±¤ë¡£
EISA ¤ä PCI ¥«¡¼¥É¤Ç¤Ï¤³¤ì¤é¤ò»ØÄꤷ¤Æ¤âÁ´¤¯¸ú²Ì¤¬Ìµ¤¤¡£
ISA µÚ¤Ó VLB ¥«¡¼¥É¤Î¸¡½Ð¤ËÂФ·¤Æ¤Î¤ßÍѤ¤¤é¤ì¤ë¡£
¤µ¤é¤Ë¡¢¥Ç¥Ð¥Ã¥°¥ª¥×¥·¥ç¥óÉÕ¤­¤Ç¥É¥é¥¤¥Ð¤¬¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
¥Ç¥Ð¥Ã¥°¾ðÊó¤Î½ÐÎÏ¥ì¥Ù¥ë¤È¤·¤Æ 0xdeb[0-f] ¥Ñ¥é¥á¡¼¥¿¤òÄɲäǤ­¤ë¡£
0-f ¤Ë¤è¤ê¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤Î¾ðÊó¤Î¥ì¥Ù¥ë¤ò 16 Ãʳ¬¤Ç»ØÄꤹ¤ë¡£
.TP
.B "AM53C974"
.IP
.BI AM53C974= host-scsi-id,target-scsi-id,max-rate,max-offset
.TP
.\"O .B "BusLogic SCSI Hosts configuration ('BusLogic=')"
.B BusLogic SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤ÎÀßÄê ('BusLogic=')
.IP
.BI BusLogic= N1,N2,N3,N4,N5,S1,S2,...
.IP
.\"O For an extensive discussion of the BusLogic command-line parameters,
.\"O see
.\"O .I /usr/src/linux/drivers/scsi/BusLogic.c
.\"O (lines 3149-3270 in the kernel version I am looking at).
.\"O The text
.\"O below is a very much abbreviated extract.
Buslogic ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¥Ñ¥é¥á¡¼¥¿¤Ë´Ø¤¹¤ë¾ÜºÙ¤ÊµÄÏÀ¤Ï
.I /usr/src/linux/drivers/scsi/BusLogic.c
(Ãø¼Ô¤¬¤¤¤Þ¸«¤Æ¤¤¤ë¥«¡¼¥Í¥ë¤Ç¤Ï 4350-4497 ¹ÔÌÜ) ¤ò»²¾È¤¹¤ë¤³¤È¡£
°Ê²¼¤Ï¤³¤ì¤òÈó¾ï¤Ë¤ª¤ª¤¶¤Ã¤Ñ¤ËÍ×Ìó¤·¤¿¤â¤Î¤Ç¤¢¤ë¡£

.\"O The parameters N1-N5 are integers.
.\"O The parameters S1,... are strings.
.\"O N1 is the I/O Address at which the Host Adapter is located.
.\"O N2 is the Tagged Queue Depth to use for Target Devices that support
.\"O Tagged Queuing.
.\"O N3 is the Bus Settle Time in seconds.
.\"O This is the amount of time
.\"O to wait between a Host Adapter Hard Reset which
.\"O initiates a SCSI Bus Reset and issuing any SCSI Commands.
.\"O N4 is the Local Options (for one Host Adapter).
.\"O N5 is the Global Options (for all Host Adapters).
¥Ñ¥é¥á¡¼¥¿ N1 ¤«¤é N5 ¤Þ¤Ç¤ÏÀ°¿ô¤Ç¤¢¤ë¡£
¥Ñ¥é¥á¡¼¥¿ S1 °Ê¹ß¤Ïʸ»úÎó¤Ç¤¢¤ë¡£
N1 ¤Ï¥Û¥¹¥È¥¢¥À¥×¥¿¤¬Â¸ºß¤¹¤ë I/O ¥¢¥É¥ì¥¹¡£
N2 ¤Ï¥¿¥°¥­¥å¡¼¥¤¥ó¥°¤ò¥µ¥Ý¡¼¥È¤¹¤ë¥Ç¥Ð¥¤¥¹¤ËÂФ·¤Æ»ÈÍѤ¹¤ë¥­¥å¡¼¤Î¿¼¤µ¡£
N3 ¤Ï¥Ð¥¹°ÂÄê»þ´Ö (BST) ¤òÉÃñ°Ì¤Ç»ØÄꤹ¤ë¡£
¤³¤ì¤Ï¥Û¥¹¥È¥¢¥À¥×¥¿¤Î¥Ï¡¼¥É¥ê¥»¥Ã¥È¤Ë¤è¤ê SCSI ¥Ð¥¹¤ò¥ê¥»¥Ã¥È¤·¤Æ¤«¤é
SCSI ¥³¥Þ¥ó¥É¤Îȯ¹Ô¤ò³«»Ï¤¹¤ë¤Þ¤Ç¤ÎÂÔ¤Á»þ´Ö¤Ç¤¢¤ë¡£
N4 ¤Ï¥í¡¼¥«¥ë¥ª¥×¥·¥ç¥ó (¤Ò¤È¤Ä¤Î¥Û¥¹¥È¥¢¥À¥×¥¿ÍÑ)¡£
N5 ¤Ï¥°¥í¡¼¥Ð¥ë¥ª¥×¥·¥ç¥ó (¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¥¢¥À¥×¥¿ÍÑ)¡£

.\"O The string options are used to provide control over Tagged Queuing
.\"O (TQ:Default, TQ:Enable, TQ:Disable, TQ:<Per-Target-Spec>), over
.\"O Error Recovery (ER:Default, ER:HardReset, ER:BusDeviceReset,
.\"O ER:None, ER:<Per-Target-Spec>), and over Host Adapter Probing
.\"O (NoProbe, NoProbeISA, NoSortPCI).
ʸ»úÎ󥪥ץ·¥ç¥ó¤Ï°Ê²¼¤ÎÆ°ºî¤òÀ©¸æ¤¹¤ë:
¥¿¥°¥­¥å¡¼¥¤¥ó¥° (TQ:Default, TQ:Enable, TQ:Disable, TQ:<Per-Target-Spec>)¡¢
¥¨¥é¡¼Éüµ¢ (ER:Default, ER:HardReset, ER:BusDeviceReset,
ER:None, ER:<Per-Target-Spec>)¡¢
¥Û¥¹¥È¥¢¥À¥×¥¿¤Î¸¡½Ð (NoProbe, NoProbeISA, NoSortPCI)¡£
.TP
.\"O .B "EATA/DMA configuration"
.B EATA/DMA ¤ÎÀßÄê
.\"O The default list of i/o ports to be probed can be changed by
¸¡½ÐÂоݤˤ¹¤ë I/O ¥Ý¡¼¥È¤Î¥ê¥¹¥È¤ò°Ê²¼¤Î¤è¤¦¤Ë¤·¤ÆÊѹ¹¤Ç¤­¤ë¡£
.IP
.BI eata= iobase,iobase,...\fP.
.TP
.\"O .B "Future Domain TMC-16x0 configuration"
.B Future Domain TMC-16x0 ¤ÎÀßÄê
.IP
.BI fdomain= iobase,irq[,adapter_id]
.TP
.\"O .B "Great Valley Products (GVP) SCSI controller configuration"
.B Great Valley Products (GVP) SCSI ¥³¥ó¥È¥í¡¼¥é¤ÎÀßÄê
.IP
.BI gvp11= dma_transfer_bitmask
.TP
.\"O .B "Future Domain TMC-8xx, TMC-950 configuration"
.B Future Domain À½ TMC-8xx, TMC-950 ¤ÎÀßÄê
.IP
.BI tmc8xx= mem_base,irq
.IP
.\"O The
.\"O .I mem_base
.\"O value is the value of the memory mapped I/O region that
.\"O the card uses.
.\"O This will usually be one of the following values:
.\"O 0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.
.I mem_base
¤Ë¤Ï¥«¡¼¥É¤¬»ÈÍѤ¹¤ë¥á¥â¥ê¥Þ¥Ã¥× I/O ¤ÎÎΰè¤ò»ØÄꤹ¤ë¡£Ä̾ï
¤Ï¼¡¤ÎÃͤΤɤ줫¤¬»È¤ï¤ì¤ë: 0xc8000, 0xca000, 0xcc000,
0xce000, 0xdc000, 0xde000¡£
.TP
.\"O .B "IN2000 configuration"
.B IN2000 ¤ÎÀßÄê
.IP
.BI in2000= S
.IP
.\"O where S is a comma-separated string of items keyword[:value].
.\"O Recognized keywords (possibly with value) are:
.\"O ioport:addr, noreset, nosync:x, period:ns, disconnect:x,
.\"O debug:x, proc:x.
.\"O For the function of these parameters, see
.\"O .IR /usr/src/linux/drivers/scsi/in2000.c .
S ¤Ï¥³¥ó¥Þ¶èÀÚ¤ê¤Îʸ»úÎó¤Ç¡¢³Æ¹àÌÜ¤Ï keyword[:value] ·Á¼°¤Ç»ØÄꤹ¤ë¡£
»ØÄê¤Ç¤­¤ë¥­¡¼¥ï¡¼¥É¤Ï°Ê²¼¤ÎÄ̤ꡣ
ioport:addr, noreset, nosync:x, period:ns, disconnect:x, debug:x, proc:x¡£
¤³¤ì¤é¤Î¥Ñ¥é¥á¡¼¥¿¤Îµ¡Ç½¤Ë¤Ä¤¤¤Æ¤Ï
.I /usr/src/linux/drivers/scsi/in2000.c
¤ò»²¾È¡£
.TP
.\"O .B "NCR5380 and NCR53C400 configuration"
.B NCR5380 ¤ª¤è¤Ó NCR53C400 ¤ÎÀßÄê
.\"O The boot arg is of the form
¤³¤Îµ¯Æ°»þ°ú¿ô¤Ï°Ê²¼¤Î½ñ¼°¤Ç»ØÄꤹ¤ë¡£
.IP
.BI ncr5380= iobase,irq,dma
.IP
.\"O or
¤Þ¤¿¤Ï
.IP
.BI ncr53c400= iobase,irq
.IP
.\"O If the card doesn't use interrupts, then an IRQ value of 255 (0xff) will
.\"O disable interrupts.
.\"O An IRQ value of 254 means to autoprobe.
.\"O More details can be found in the file
.\"O .I Documentation/scsi/g_NCR5380.txt
.\"O (or
.\"O .I drivers/scsi/README.g_NCR5380
.\"O for older kernels) in the kernel source.
¥«¡¼¥É¤¬ IRQ ¤ò»ÈÍѤ·¤Ê¤¤¾ì¹ç¤Ï¡¢
255 (0xff) ¤ò»ØÄꤹ¤ì¤Ð̵¸ú¤Ë¤Ç¤­¤ë¡£
IRQ ¤Ë 254 ¤ò»ØÄꤹ¤ë¤È¼«Æ°¸¡½Ð¤¹¤ë¡£
¾ÜºÙ¤Ï¥«¡¼¥Í¥ë¥½¡¼¥¹Æâ¤Î
.I Documentation/scsi/g_NCR5380.txt
(¸Å¤¤¥«¡¼¥Í¥ë¤Î¾ì¹ç¤Ï
.IR drivers/scsi/README.g_NCR5380 )
¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¡£
.TP
.\"O .B "NCR53C8xx configuration"
.B NCR53C8xx ¤ÎÀßÄê
.IP
.BI ncr53c8xx= S
.IP
.\"O where S is a comma-separated string of items keyword:value.
.\"O Recognized keywords are: mpar (master_parity), spar (scsi_parity),
.\"O disc (disconnection), specf (special_features), ultra (ultra_scsi),
.\"O fsn (force_sync_nego), tags (default_tags), sync (default_sync),
.\"O verb (verbose), debug (debug), burst (burst_max).
.\"O For the function of the assigned values, see
.\"O .IR /usr/src/linux/drivers/scsi/ncr53c8xx.c .
S ¤Ï¥³¥ó¥Þ¶èÀÚ¤ê¤Îʸ»úÎó¤Ç¡¢³Æ¹àÌÜ¤Ï keyword[:value] ·Á¼°¤Ç»ØÄꤹ¤ë¡£
»ØÄê¤Ç¤­¤ë¥­¡¼¥ï¡¼¥É¤Ï°Ê²¼¤ÎÄ̤ꡣ
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)¡£
¤³¤ì¤é¤Î¥ª¥×¥·¥ç¥ó¤Îµ¡Ç½¤Ë¤Ä¤¤¤Æ¤Ï
.I /usr/src/linux/drivers/scsi/README.ncr53c8xx
¤ò»²¾È¤¹¤ë¤³¤È¡£
.TP
.\"O .B "NCR53c406a configuration"
.B NCR53c406a ¤ÎÀßÄê
.IP
.BI ncr53c406a= iobase[,irq[,fastpio]]
.IP
.\"O Specify irq = 0 for noninterrupt driven mode.
.\"O Set fastpio = 1 for fast pio mode, 0 for slow mode.
³ä¤ê¹þ¤ß̵¤·¤ÇÆ°ºî¤¹¤ë¥â¡¼¥É¤Ë¤Ï irq ¤Ë 0 ¤ò»ØÄꤹ¤ë¡£
¹â® PIO ¥â¡¼¥É¤Ï fastpio ¤Ë 1 ¤ò»ØÄꤷ¡¢Ä㮥⡼¥É¤Ï 0 ¤ò»ØÄꤹ¤ë¡£
.TP
.\"O .B "Pro Audio Spectrum configuration"
.B Pro Audio Spectrum ¤ÎÀßÄê
.\"O The PAS16 uses a NC5380 SCSI chip, and newer models support
.\"O jumperless configuration.
.\"O The boot arg is of the form:
PAS16 ¤Ï NC5380 SCSI ¥Á¥Ã¥×¤ò»ÈÍѤ·¤Æ¤ª¤ê¡¢
ºÇ¶á¤Î¥â¥Ç¥ë¤Ï¥¸¥ã¥ó¥Ñ¥ì¥¹¤ÎÀßÄê¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¡£
µ¯Æ°»þ°ú¿ô¤Î½ñ¼°¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
.BI pas16= iobase,irq
.IP
.\"O The only difference is that you can specify an IRQ value of 255, which
.\"O will tell the driver to work without using interrupts, albeit at a
.\"O performance loss.
.\"O The iobase is usually 0x388.
Í£°ì¤Î°ã¤¤¤È¤·¤Æ¡¢
IRQ ¤Ë 255 ¤ò»ØÄꤹ¤ì¤Ð³ä¤ê¹þ¤ß¤ò»ÈÍѤ·¤Ê¤¤¤è¤¦¥É¥é¥¤¥Ð¤Ë»Ø¼¨¤Ç¤­¤ë
(¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤ÏÄã²¼¤¹¤ë)¡£
Ä̾ï iobase ¤Ï 0x388 ¤Ç¤¢¤ë¡£
.TP
.\"O .B "Seagate ST-0x configuration"
.B Seagate À½ ST-0x ¤ÎÀßÄê
.\"O If your card is not detected at boot time,
.\"O you will then have to use a boot arg of the form:
¥«¡¼¥É¤¬µ¯Æ°»þ¤Ëǧ¼±¤µ¤ì¤Ê¤¤¾ì¹ç¤Ï°Ê²¼¤Î¤è¤¦¤Ê»ØÄ꤬ɬÍפˤʤë¤À¤í¤¦¡£
.IP
.BI st0x= mem_base,irq
.IP
.\"O The
.\"O .I mem_base
.\"O value is the value of the memory mapped I/O region that
.\"O the card uses.
.\"O This will usually be one of the following values:
.\"O 0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.
.I mem_base
¤Ë¤Ï¥«¡¼¥É¤¬»ÈÍѤ¹¤ë¥á¥â¥ê¥Þ¥Ã¥× I/O ¤ÎÎΰè¤ò»ØÄꤹ¤ë¡£
Ä̾ï¤Ï¼¡¤Î¤É¤ì¤«:
0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000¡£
TP
.\"O .B "Trantor T128 configuration"
.B Trantor À½ T128 ¤ÎÀßÄê
.\"O These cards are also based on the NCR5380 chip, and accept the
.\"O following options:
¤³¤Î¥«¡¼¥É¤â NCR5380 ¥Á¥Ã¥×¤òÍøÍѤ·¤Æ¤ª¤ê¡¢
°Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤ò¼õ¤±ÉÕ¤±¤ë¡£
.IP
.BI t128= mem_base,irq
.IP
.\"O The valid values for
.\"O .I mem_base
.\"O are as follows: 0xcc000, 0xc8000, 0xdc000, 0xd8000.
Í­¸ú¤Ê
.I mem_base
¤ÎÃͤϼ¡¤ÎÄ̤ê¤Ç¤¢¤ë: 0xcc000, 0xc8000, 0xdc000, 0xd8000¡£
.TP
.\"O .B "UltraStor 14F/34F configuration"
.B UltraStor À½ 14F/34F ¤ÎÀßÄê
.\"O The default list of i/o ports to be probed can be changed by
¼«Æ°¸¡½Ð¤ò»î¤ß¤ë I/O ¥Ý¡¼¥È¤Î¥ê¥¹¥È¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤ÆÊѹ¹¤Ç¤­¤ë¡£
.IP
.BI eata= iobase,iobase,... .
.TP
.\"O .B "WD7000 configuration"
.B WD7000 ¤ÎÀßÄê
.IP
.BI wd7000= irq,dma,iobase
.\"O .SS "Commodore Amiga A2091/590 SCSI controller configuration"
.SS Commodore Amiga À½ A2091/590 SCSI ¥³¥ó¥È¥í¡¼¥é¤ÎÀßÄê
.IP
.BI wd33c93= S
.IP
.\"O where S is a comma-separated string of options.
.\"O Recognized options are
.\"O nosync:bitmask, nodma:x, period:ns, disconnect:x, debug:x,
.\"O clock:x, next.
.\"O For details, see
.\"O .IR /usr/src/linux/drivers/scsi/wd33c93.c .
S ¤Ï¥³¥ó¥Þ¶èÀÚ¤ê¤Îʸ»úÎó¤Ç¡¢³Æ¹àÌÜ¤Ï keyword[:value] ·Á¼°¤Ç»ØÄꤹ¤ë¡£
ǧ¼±¤µ¤ì¤ë¥ª¥×¥·¥ç¥ó¤Ï°Ê²¼¤ÎÄ̤ꡣ
nosync:bitmask, nodma:x, period:ns,
disconnect:x, debug:x, clock:x, next¡£
¾ÜºÙ¤Ï
.I /usr/src/linux/drivers/scsi/wd33c93.c
¤ò»²¾È¤»¤è¡£
.\"O .SS "Hard Disks"
.SS ¥Ï¡¼¥É¥Ç¥£¥¹¥¯
.TP
.\"O .B "IDE Disk/CD-ROM Driver Parameters"
.B "IDE Disk/CD-ROM ¥É¥é¥¤¥Ð¤Î¥Ñ¥é¥á¡¼¥¿"
.\"O The IDE driver accepts a number of parameters, which range from disk
.\"O geometry specifications, to support for broken controller chips.
.\"O Drive specific options are specified by using 'hdX=' with X in 'a'-'h'.
IDE ¥É¥é¥¤¥Ð¤Ï¡¢
¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê»ØÄ꤫¤é¥Ð¥°¤Î¤¢¤ë¥³¥ó¥È¥í¡¼¥é¥Á¥Ã¥×¤Î¥µ¥Ý¡¼¥È¤Þ¤Ç¡¢
¿ô¿¤¯¤Î¥Ñ¥é¥á¡¼¥¿¤ò¼õ¤±ÉÕ¤±¤ë¡£
¥É¥é¥¤¥Ö¤òÆÃÄꤹ¤ë¤Ë¤Ï 'hdX=' ¤ò»È¤¦¡£
¤³¤³¤Ç X ¤Ë¤Ï 'a' ¤«¤é 'h' ¤Îʸ»ú¤ò»ØÄꤹ¤ë¡£

.\"O Non-drive specific options are specified with the prefix 'hd='.
.\"O Note that using a drive specific prefix for a non-drive specific option
.\"O will still work, and the option will just be applied as expected.
¤¢¤ë¥É¥é¥¤¥Ö¤ËÆÃÍ­¤Ê¤â¤Î¤Ç¤Ï¤Ê¤¤¥ª¥×¥·¥ç¥ó¤Ï¡¢hd= ¤òÁ°¤ËÉÕ¤±¤Æ»ØÄꤹ¤ë¡£
¥É¥é¥¤¥ÖÆÃÍ­¤Ç¤Ê¤¤¥ª¥×¥·¥ç¥ó¤ËÂФ·¤Æ¥É¥é¥¤¥Ö»ØÄê
('hdX=') ¤òÁ°ÃÖ¤·¤Æ¤âÌäÂê¤Ï¤Ê¤¤¡£
¤½¤Î¥ª¥×¥·¥ç¥ó¤Ï´üÂÔÄ̤ꤽ¤Î¥É¥é¥¤¥Ö¤ËŬÍѤµ¤ì¤ë¡£
.\"nakano ¤È¤¤¤¦¤Î¤¬ "as expected" ¤À¤È»×¤¦¤ó¤À¤±¤É...

.\"O Also note that 'hd=' can be used to refer to the next unspecified
.\"O drive in the (a, ..., h) sequence.
.\"O For the following discussions,
.\"O the 'hd=' option will be cited for brevity.
.\"O See the file
.\"O .I Documentation/ide.txt
.\"O (or
.\"O .I drivers/block/README.ide
.\"O for older kernels) in the kernel source for more details.
\&'hd=' ¤Ï¡¢(a, ..., h) ¤Î¥·¡¼¥±¥ó¥¹¤Ë¤ª¤¤¤Æ¡¢
¤Þ¤À»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¼¡¤Î¥É¥é¥¤¥Ö¤ò»Ø¤¹¤¿¤á¤Ë¤â»È¤¨¤ë¡£
¤³¤ì°Ê¹ß¤Ç¤Ï´Êñ¤Î¤¿¤á¤Ë 'hd=' ¤ò»È¤Ã¤ÆÀâÌÀ¤¹¤ë¡£
¤µ¤é¤Ë¾Ü¤·¤¤¾ðÊó¤òÆÀ¤ë¤Ë¤Ï¡¢¥«¡¼¥Í¥ë¥½¡¼¥¹Æâ¤Î
.I Documentation/ide.txt
(¸Å¤¤¥«¡¼¥Í¥ë¤Î¾ì¹ç¤Ï
.IR drivers/block/README.ide )
¤ò»²¾È¤Î¤³¤È¡£
.TP
.\"O .B "The 'hd=cyls,heads,sects[,wpcom[,irq]]' options"
.B 'hd=cyls,heads,sects[,wpcom[,irq]]' ¥ª¥×¥·¥ç¥ó
.\"O These options are used to specify the physical geometry of the disk.
.\"O Only the first three values are required.
.\"O The cylinder/head/sectors
.\"O values will be those used by fdisk.
.\"O The write precompensation value
.\"O is ignored for IDE disks.
.\"O The IRQ value specified will be the IRQ
.\"O used for the interface that the drive resides on, and is not really a
.\"O drive-specific parameter.
¤³¤ì¤é¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥£¥¹¥¯¤ÎʪÍýŪ¤Ê¥¸¥ª¥á¥È¥ê¤ò»ØÄꤹ¤ë¤¿¤á¤Ë»È¤¦¡£
ºÇ½é¤Î 3 ¤Ä¤ÎÃͰʹߤϾÊά¤Ç¤­¤ë¡£
¥·¥ê¥ó¥À (cyls)¡¢¥Ø¥Ã¥É (heads)¡¢¥»¥¯¥¿ (sects) ¤Î³ÆÃͤÏ
fdisk ¤ÇÍѤ¤¤é¤ì¤ë¤â¤Î¤ÈƱ¤¸¤Ç¤¢¤ë¡£
½ñ¤­¹þ¤ßÊäÀµ (wpcom) ÃÍ¤Ï IDE ¥Ç¥£¥¹¥¯¤Ç¤Ï̵»ë¤µ¤ì¤ë¡£
IRQ Ãͤˤϡ¢¤½¤Î¥É¥é¥¤¥Ö¤¬Àܳ¤µ¤ì¤Æ¤¤¤ë¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤¬ÍѤ¤¤ë
IRQ ¤ò»ØÄꤹ¤ë
(ËÜÍè¤Î°ÕÌ£¤Ç¤Ï¡Ö¥É¥é¥¤¥Ö¤ËÆÃÍ­¡×¤Î¥Ñ¥é¥á¡¼¥¿¤Ç¤Ï¤Ê¤¤)¡£
.TP
.\"O .B "The 'hd=serialize' option"
.B 'hd=serialize' ¥ª¥×¥·¥ç¥ó
.\"O The dual IDE interface CMD-640 chip is broken as designed such that
.\"O when drives on the secondary interface are used at the same time as
.\"O drives on the primary interface, it will corrupt your data.
.\"O Using this
.\"O option tells the driver to make sure that both interfaces are never
.\"O used at the same time.
¥Ç¥å¥¢¥ë IDE ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ç¤¢¤ë CMD-640 ¥Á¥Ã¥×¤Ë¤ÏÀß·×¾å¤ÎÌäÂ꤬¤¢¤Ã¤Æ¡¢
¥»¥«¥ó¥À¥ê¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¾å¤Î¥É¥é¥¤¥Ö¤È
¥×¥é¥¤¥Þ¥ê¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¾å¤Î¥É¥é¥¤¥Ö¤ò
Ʊ»þ¤Ë»ÈÍѤ¹¤ë¤È¥Ç¡¼¥¿¤¬Ç˲õ¤µ¤ì¤ë¤³¤È¤¬¤¢¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤È¡¢
¥É¥é¥¤¥Ð¤ÏξÊý¤Î¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤¬
Ʊ»þ¤Ë»ÈÍѤµ¤ì¤ë¤³¤È¤¬ÀäÂФˤʤ¤¤è¤¦¤Ë¤¹¤ë¡£
.TP
.\"O .B "The 'hd=dtc2278' option"
.B 'hd=dtc2278' ¥ª¥×¥·¥ç¥ó
.\"O This option tells the driver that you have a DTC-2278D IDE interface.
.\"O The driver then tries to do DTC-specific operations to enable the
.\"O second interface and to enable faster transfer modes.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢DTC-2278D IDE ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤¬»È¤ï¤ì¤Æ¤¤¤ë
¤³¤È¤ò¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë¡£
¤¹¤ë¤È¥É¥é¥¤¥Ð¤Ï¡¢DTC ÆÃÍ­¤Îµ¡Ç½
(2 ÈÖÌܤΥ¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤È¹â®žÁ÷¥â¡¼¥É)
¤ò»ÈÍѲÄǽ¤Ë¤¹¤ë¤è¤¦»î¤ß¤ë¡£
.TP
.\"O .B "The 'hd=noprobe' option"
.B 'hd=noprobe' ¥ª¥×¥·¥ç¥ó
.\"O Do not probe for this drive.
.\"O For example,
¤³¤Î¥É¥é¥¤¥Ö¤Î¼«Æ°¸¡½Ð¤ò¤·¤Ê¤¤¡£
Î㤨¤Ð
.IP
hdb=noprobe hdb=1166,7,17
.IP
.\"O would disable the probe, but still specify the drive geometry so
.\"O that it would be registered as a valid block device, and hence
.\"O usable.
¤È¤¹¤ë¤È¼«Æ°¸¡½Ð¤¬Ìµ¸ú¤Ë¤Ê¤ë¡£
¤·¤«¤·¥É¥é¥¤¥Ö¤Î¥¸¥ª¥á¥È¥ê¤ò»ØÄꤷ¤Æ¤¤¤ë¤Î¤Ç¡¢
¤³¤Î¥É¥é¥¤¥Ö¤ÏÀµ¤·¤¤¥Ö¥í¥Ã¥¯¥Ç¥Ð¥¤¥¹¤È¤·¤ÆÅÐÏ¿¤µ¤ì¡¢»ÈÍѲÄǽ¤Ë¤Ê¤ë¡£
.TP
.\"O .B "The 'hd=nowerr' option"
.B 'hd=nowerr' ¥ª¥×¥·¥ç¥ó
.\"O Some drives apparently have the
.\"O .B WRERR_STAT
.\"O bit stuck on permanently.
.\"O This enables a work-around for these broken devices.
¥É¥é¥¤¥Ö¤Ë¤è¤Ã¤Æ¤Ï¡¢½ñ¤­¹þ¤ß¥¨¥é¡¼
.RB ( WRERR_STAT )
¥Ó¥Ã¥È¤¬¥¯¥ê¥¢¤Ç¤­¤Ê¤¯¤Ê¤ë¤³¤È¤¬¤¢¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢
¤³¤Î¤è¤¦¤Ê²õ¤ì¤¿¥Ç¥Ð¥¤¥¹¤ËÂФ¹¤ë²óÈòµ¡Ç½¤¬Í­¸ú¤Ë¤Ê¤ë¡£
.TP
.\"O .B "The 'hd=cdrom' option"
.B "'hd=cdrom' ¥ª¥×¥·¥ç¥ó"
.\"O This tells the IDE driver that there is an ATAPI compatible CD-ROM
.\"O attached in place of a normal IDE hard disk.
.\"O In most cases the CD-ROM
.\"O is identified automatically, but if it isn't then this may help.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢Ä̾ï¤Î IDE ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ÎÂå¤ï¤ê¤Ë¡¢
ATAPI ¸ß´¹¤Î CDROM ¤¬Â³¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò IDE ¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë¡£
CD-ROM ¤Ï¤¿¤¤¤Æ¤¤¼«Æ°Åª¤Ëǧ¼±¤µ¤ì¤ë¤¬¡¢
¤¦¤Þ¤¯¹Ô¤«¤Ê¤¤¾ì¹ç¤Ë»î¤·¤Æ¤ß¤ë¤ÈÎɤ¤¡£
.TP
.\"O .B "Standard ST-506 Disk Driver Options ('hd=')"
.B ¥¹¥¿¥ó¥À¡¼¥É ST-506 ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ð¤Î¥ª¥×¥·¥ç¥ó ('hd=')
.\"O The standard disk driver can accept geometry arguments for the disks
.\"O similar to the IDE driver.
.\"O Note however that it only expects three
.\"O values (C/H/S); any more or any less and it will silently ignore you.
.\"O Also, it only accepts 'hd=' as an argument, that is, 'hda='
.\"O and so on are not valid here.
.\"O The format is as follows:
¥¹¥¿¥ó¥À¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ð¤Ï
IDE ¥É¥é¥¤¥Ð¤ÈƱÍͤΥ¸¥ª¥á¥È¥ê»ØÄê¤ò°ú¿ô¤Ë¤È¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
¤¿¤À¤·¼õ¤±ÉÕ¤±¤ëÃͤϤÁ¤ç¤¦¤É 3 ¤Ä (C/H/S) ¤Ë¸Â¤é¤ì¤ë¡£
¤½¤ì°Ê¾å¤ÎÃͤ䤽¤ì°Ê²¼¤ÎÃͤò»ØÄꤹ¤ë¤È¡¢¥É¥é¥¤¥Ð¤ÏÌۤäƤ½¤Î»ØÄê¤ò̵»ë¤¹¤ë¡£
¤Þ¤¿°ú¿ô¤È¤·¤Æ¼õ¤±Æþ¤ì¤é¤ì¤ë¤Î¤Ï 'hd=' ¤Î·Á¼°¤À¤±¤Ç¤¢¤ë¡£
¤Ä¤Þ¤ê 'hda=' ¤Î¤è¤¦¤Ê»ØÄê¤Ï¤³¤³¤Ç¤ÏÀµ¤·¤¯¤Ê¤¤¡£
½ñ¼°¤Ï¼¡¤ÎÄ̤ꡣ
.IP
hd=cyls,heads,sects
.IP
.\"O If there are two disks installed, the above is repeated with the
.\"O geometry parameters of the second disk.
2 Âæ¤Î¥Ç¥£¥¹¥¯¤¬Àܳ¤µ¤ì¤Æ¤¤¾ì¹ç¤Ï¡¢
2 ÈÖÌܤΥǥ£¥¹¥¯¤ËÂФ·¤Æ¤â¾åµ­¤Î¥¸¥ª¥á¥È¥ê¤¬ÀßÄꤵ¤ì¤ë¡£
.TP
.\"O .B "XT Disk Driver Options ('xd=')"
.B XT ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ð¤Î¥ª¥×¥·¥ç¥ó ('xd=')
.\"O If you are unfortunate enough to be using one of these old 8 bit cards
.\"O that move data at a whopping 125kB/s then here is the scoop.
.\"O If the card is not recognized, you will have to use a boot arg of the form:
¤³¤ì¤é¤Î¸Å¤¤ 8 bit ¥«¡¼¥É (125kB/s ¤ÎžÁ÷®ÅÙ¤·¤«¤Ê¤¤!)
¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤ÉÔ¹¬¤Ê¿Í¤Î¤¿¤á¤Î¥ª¥×¥·¥ç¥ó¤Ç¤¢¤ë¡£
¥«¡¼¥É¤¬Ç§¼±¤µ¤ì¤Ê¤¤¾ì¹ç¤Ï°Ê²¼¤Î½ñ¼°¤Çµ¯Æ°»þ°ú¿ô¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¤À¤í¤¦¡£
.IP
xd=type,irq,iobase,dma_chan
.IP
.\"O The type value specifies the particular manufacturer of the card,
.\"O overriding autodetection.
.\"O For the types to use, consult the
.\"O .I drivers/block/xd.c
.\"O source file of the kernel you are using.
.\"O The type is an index in the list
.\"O .I xd_sigs
.\"O and in the course of time
.\" 1.1.50, 1.3.81, 1.3.99, 2.0.34, 2.1.67, 2.1.78, 2.1.127
.\"O types have been added to or deleted from the middle of the list,
.\"O changing all type numbers.
.\"O Today (Linux 2.5.0) the types are
.\"O 0=generic; 1=DTC 5150cx; 2,3=DTC 5150x; 4,5=Western Digital;
.\"O 6,7,8=Seagate; 9=Omti; 10=XEBEC, and where here several types are
.\"O given with the same designation, they are equivalent.
type Ãͤˤϥ«¡¼¥É¤Î¥á¡¼¥«¡¼¤ò»ØÄꤷ¡¢¤³¤ì¤Ï¼«Æ°¸¡ÃΤè¤êÍ¥À褵¤ì¤ë¡£
»ØÄꤹ¤Ù¤­ type ¤ÎÃͤˤĤ¤¤Æ¤Ï¡¢»È¤Ã¤Æ¤¤¤ë¥«¡¼¥Í¥ë¤Î¥½¡¼¥¹¥Õ¥¡¥¤¥ë
.I drivers/block/xd.c
¤òÄ´¤Ù¤Æ¤Û¤·¤¤¡£type ¤Ï¥ê¥¹¥È
.I xd_sigs
¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¡¢Îò»Ë¤È¶¦¤ËÄɲ䵤줿¤êºï½ü¤µ¤ì¤¿¤ê¤·¤Æ¤­¤¿¡£
¥ê¥¹¥È¤ÎÅÓÃæ¤Ç¤ÎÄɲᦺï½ü¤â¹Ô¤ï¤ì¤¿¤Î¤Ç¡¢
¤½¤Î¾ì¹ç¤Ï¤¹¤Ù¤Æ¤Î type Èֹ椬Êѹ¹¤µ¤ì¤¿¡£
º£Æü (Linux 2.5.0) ¤Ë¤ª¤±¤ë type ¤Ï¡¢
0=generic; 1=DTC 5150cx; 2,3=DTC 5150x; 4,5=Western Digital;
6,7,8=Seagate; 9=Omti; 10=XEBEC ¤Ç¤¢¤ë¡£
¤³¤³¤Ç¤Ï¤¤¤¯¤Ä¤«¤Î type ¤ËƱ¤¸»ØÄ꤬Ϳ¤¨¤é¤ì¤Æ¤¤¤ë¤¬¡¢
¤½¤ì¤é¤ÏÅù²Á¤Ç¤¢¤ë¡£

0=¥Î¡¼¥Ö¥é¥ó¥É¡¢1=DTC¡¢2,3,4=Western Digital¡¢5,6,7=Seagate¡¢8=OMTI
Ʊ¤¸¥á¡¼¥«¡¼¤ËÊ£¿ô¤ÎÃͤ¬¤¢¤ë¤Î¤Ï¸¡½Ð¤Ë»ÈÍѤµ¤ì¤ë BIOS ʸ»úÎó¤Î°ã¤¤¤Ç¤¢¤ë¡£
BIOS ʸ»úÎó¤Ï type ¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¤Ë¤Ï»ÈÍѤµ¤ì¤Ê¤¤¡£

.\"O The xd_setup() function does no checking on the values, and assumes
.\"O that you entered all four values.
.\"O Don't disappoint it.
.\"O Here is an
.\"O example usage for a WD1002 controller with the BIOS disabled/removed,
.\"O using the 'default' XT controller parameters:
xd_setup() ´Ø¿ô¤Ï°ú¿ô¤ò¥Á¥§¥Ã¥¯¤»¤º¡¢
4 ¤Ä¤ÎÃͤ¬¤¹¤Ù¤Æ»ØÄꤵ¤ì¤ë¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤ë¡£
°ú¿ô¤ò¾Êά¤·¤Æ¤Ï¤Ê¤é¤Ê¤¤¡£
Îã¤È¤·¤Æ¡¢BIOS ¤¬Ìµ¸ú¤Ë¤µ¤ì¤¿ (¤¢¤ë¤¤¤Ïºï½ü¤µ¤ì¤¿)
WD1002 ¥³¥ó¥È¥í¡¼¥é¤Î¾ì¹ç¤ò¼¨¤¹
(¥Ñ¥é¥á¡¼¥¿¤Ë¤Ï XT ¥³¥ó¥È¥í¡¼¥é¤Î¡Ö¥Ç¥Õ¥©¥ë¥È¡×¤ÎÃͤò»È¤Ã¤Æ¤¤¤ë)¡£
.IP
xd=2,5,0x320,3
.TP
.\"O .B "Syquest's EZ* removable disks"
.B Syquest À½ EZ* ¥ê¥à¡¼¥Ð¥Ö¥ë¥Ç¥£¥¹¥¯
.IP
.BI ez= iobase[,irq[,rep[,nybble]]]
.\"O .SS "IBM MCA Bus Devices"
.SS "IBM MCA ¥Ð¥¹¾å¤Î¥Ç¥Ð¥¤¥¹"
.\"O See also
.\"O .IR /usr/src/linux/Documentation/mca.txt .
.I /usr/src/linux/Documentation/mca.txt
¤â»²¾È¤»¤è¡£
.TP
.\"O .B "PS/2 ESDI hard disks"
.B PS/2 ESDI ¥Ï¡¼¥É¥Ç¥£¥¹¥¯
.\"O It is possible to specify the desired geometry at boot time:
˾¤à¥¸¥ª¥á¥È¥ê¤òµ¯Æ°»þ¤Ë»ØÄê¤Ç¤­¤ë¡£
.IP
.BI ed= cyls,heads,sectors.
.IP
.\"O For a ThinkPad-720, add the option
ThinkPad-720 ¤ò»ÈÍѤ¹¤ë¾ì¹ç¤Ï°Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤òÄɲ乤뤳¤È¡£
.IP
.\"O .BR tp720=1 .
.B tp720=1
.TP
.\"O .B "IBM Microchannel SCSI Subsystem configuration"
.B IBM Microchannel SCSI ¥µ¥Ö¥·¥¹¥Æ¥à¤ÎÀßÄê
.IP
.BI ibmmcascsi= N
.IP
.\"O where N is the \fIpun\fP (SCSI ID) of the subsystem.
N ¤Ï¥µ¥Ö¥·¥¹¥Æ¥à¤Î \fIpun\fP (SCSI ID) ¤òɽ¤¹¡£
.TP
.\"O .B "The Aztech Interface"
.B Aztech ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this type of card is:
¤³¤Î¥¿¥¤¥×¤Î¥«¡¼¥É¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
aztcd=iobase[,magic_number]
.IP
.\"O If you set the magic_number to 0x79 then the driver will try and run
.\"O anyway in the event of an unknown firmware version.
.\"O All other values
.\"O are ignored.
magic_number ¤Ë 0x79 ¤ò¥»¥Ã¥È¤¹¤ë¤È¡¢
¥É¥é¥¤¥Ð¤Ï¥Õ¥¡¡¼¥à¥¦¥§¥¢¤Î¥Ð¡¼¥¸¥ç¥ó¤¬Ê¬¤«¤é¤Ê¤¤¾ì¹ç¤Ç¤â¡¢
¤È¤Ë¤«¤¯¼Â¹Ô¤ò»î¤ß¤ë¡£
¤½¤Î¾¤ÎÃͤϤ¹¤Ù¤Æ̵»ë¤µ¤ì¤ë¡£
.TP
.\"O .B "Parallel port CD-ROM drives"
.B "¥Ñ¥é¥ì¥ë¥Ý¡¼¥È CD-ROM ¥É¥é¥¤¥Ö"
.\"O Syntax:
½ñ¼°:
.IP
.\"O pcd.driveN=prt,pro,uni,mod,slv,dly
pcd.driveN=port,pro,uni,mod,slv,dly
.br
pcd.nice=nice
.IP
.\"O where 'port' is the base address, 'pro' is the protocol number, 'uni'
.\"O is the unit selector (for chained devices), 'mod' is the mode (or \-1
.\"O to choose the best automatically), 'slv' is 1 if it should be a slave,
.\"O and 'dly' is a small integer for slowing down port accesses.
.\"O The 'nice' parameter controls the driver's use of idle CPU time, at the
.\"O expense of some speed.
¤³¤³¤Ç 'port' ¤Ï¥Ù¡¼¥¹¥¢¥É¥ì¥¹¡¢'pro'
¤Ï¥×¥í¥È¥³¥ëÈֹ桢'uni' ¤Ï¥æ¥Ë¥Ã¥È¥»¥ì¥¯¥¿
(¥Á¥§¥¤¥ó¥Ç¥Ð¥¤¥¹ÍÑ)¡¢'mod' ¤Ï¥â¡¼¥É
(¤¢¤ë¤¤¤Ï¼«Æ°Åª¤ËºÇŬ¤Î¤â¤Î¤òÁª¤Ð¤»¤ë¤Ë¤Ï \-1)¡¢'slv'
¤Ï¥¹¥ì¡¼¥Ö¤Ë¤·¤¿¤¤¾ì¹ç¤Ë 1¡¢'dly'
¤Ï¥Ý¡¼¥È¥¢¥¯¥»¥¹¤òÃÙ¤¯¤·¤¿¤¤¾ì¹ç¤Ë¾®¤µ¤ÊÀ°¿ô¤òÍ¿¤¨¤ë¡£'nice' ¥Ñ¥é¥á¡¼¥¿¤Ï¡¢
¥É¥é¥¤¥Ð¤Î¥¢¥¤¥É¥ë CPU »þ´Ö¤Î»È¤¤Êý¤òÀ©¸æ¤¹¤ë¡£
¤¿¤À¤·Â®Å٤Ϥ¢¤ëÄøÅÙÄã²¼¤¹¤ë¡£
.TP
.\"O .B "The CDU-31A and CDU-33A Sony Interface"
.B Sony À½ CDU-31A ¤È CDU-33A ¤Î¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O This CD-ROM interface is found on some of the Pro Audio Spectrum sound
.\"O cards, and other Sony supplied interface cards.
.\"O The syntax is as follows:
¤³¤Î CD-ROM ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ï¡¢
Pro Audio Spectrum ¥µ¥¦¥ó¥É¥«¡¼¥É¤Î°ìÉô¤ä
¥½¥Ë¡¼¤¬¶¡µë¤¹¤ë¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¥«¡¼¥É¤Ç»È¤ï¤ì¤Æ¤¤¤ë¡£
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
cdu31a=iobase,[irq[,is_pas_card]]
.IP
.\"O Specifying an IRQ value of zero tells the driver that hardware
.\"O interrupts aren't supported (as on some PAS cards).
.\"O If your card
.\"O supports interrupts, you should use them as it cuts down on the CPU
.\"O usage of the driver.
IRQ ¤Ë 0 ¤ò»ØÄꤹ¤ë¤È¡¢
¥Ï¡¼¥É¥¦¥§¥¢³ä¤ê¹þ¤ß¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¤³¤È¤ò¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë
(PAS ¥«¡¼¥É¤Ë¤Ï¤½¤Î¤è¤¦¤Ê¤â¤Î¤¬¤¢¤ë)¡£
»ÈÍѤ¹¤ë¥«¡¼¥É¤¬³ä¤ê¹þ¤ß¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤Ê¤é¡¢
¥É¥é¥¤¥Ð¤Ë¤è¤ë CPU ¤ÎÉé²Ù¤ò¸º¤é¤¹¤¿¤á¤Ë¤â³ä¤ê¹þ¤ß¤ò»ÈÍѤ¹¤Ù¤­¤Ç¤¢¤ë¡£

.\"O The
.\"O .I is_pas_card
.\"O should be entered as 'PAS' if using a Pro Audio Spectrum card,
.\"O and otherwise it should not be specified at all.
.I is_pas_card
¤Ë¤Ï¡¢Pro Audio Spectrum ¥«¡¼¥É¤ò»ÈÍѤ·¤Æ¤¤¤ë¤È¤­¤Ë¤Ï 'PAS' ¤ò»ØÄꤷ¡¢
¤½¤¦¤Ç¤Ê¤¤¤È¤­¤Ë¤Ï¤Ê¤Ë¤â»ØÄꤷ¤Ê¤¤¡£
.TP
.\"O .B "The CDU-535 Sony Interface"
.B Sony À½ CDU-535 ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this CD-ROM interface is:
¤³¤Î CD-ROM ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
sonycd535=iobase[,irq]
.IP
.\"O A zero can be used for the I/O base as a 'placeholder' if one wishes
.\"O to specify an IRQ value.
IRQ ¤ÎÃͤÀ¤±¤ò»ØÄꤷ¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢
iobase Ãͤò 0 ¤È¤¹¤ì¤Ðñ¤Ê¤ë·êËä¤á¤È²ò¼á¤µ¤ì¤ë¡£
.TP
.\"O .B "The GoldStar Interface"
.B GoldStar ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this CD-ROM interface is:
¤³¤Î CD-ROM ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
gscd=iobase
.TP
.\"O .B "The ISP16 CD-ROM Interface"
.B ISP16 CD-ROM ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O Syntax:
½ñ¼°:
.IP
isp16=[iobase[,irq[,dma[,type]]]]
.IP
.\"O (three integers and a string).
.\"O If the type is given as 'noisp16',
.\"O the interface will not be configured.
.\"O Other recognized types
.\"O are: 'Sanyo", 'Sony', 'Panasonic' and 'Mitsumi'.
(À°¿ôÃÍ 3 ¤Ä¤Èʸ»úÎó 1 ¤Ä¡£) type ¤Ë 'noisp16' ¤ò»ØÄꤹ¤ë¤È¡¢
¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ÎÀßÄê¤Ï¹Ô¤Ê¤ï¤ì¤Ê¤¤¡£
type ¤Ë¤Ï¤³¤Î¾¤Ë¤â 'Sanyo', 'Sony', 'Panasonic', 'Mitsumi' ¤¬»ØÄê¤Ç¤­¤ë¡£
.TP
.\"O .B "The Mitsumi Standard Interface"
.B Mitsumi ɸ½à¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this CD-ROM interface is:
¤³¤ÎCD-ROM ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
mcd=iobase,[irq[,wait_value]]
.IP
.\"O The
.\"O .I wait_value
.\"O is used as an internal timeout value for people who are
.\"O having problems with their drive, and may or may not be implemented
.\"O depending on a compile-time #define.
.\"O The Mitsumi FX400 is an IDE/ATAPI CD-ROM player and does not use
.\"O the mcd driver.
.I wait_value
¤Ï¥É¥é¥¤¥Ö¤ËÌäÂ꤬¤¢¤ë¾ì¹ç¤Ë¡¢
¥É¥é¥¤¥ÐÆâÉô¤Î¥¿¥¤¥à¥¢¥¦¥È¤Î»ØÄê¤ËÍѤ¤¤ë¡£
¥³¥ó¥Ñ¥¤¥ë»þ¤Î #define ¤Ë¤è¤Ã¤Æ¼ÂÁõ¤µ¤ì¤ë¤«¤µ¤ì¤Ê¤¤¤«¤¬·è¤Þ¤ë¡£
Mitsumi FX400 ¤Ï IDE/ATAPI CD-ROM ¥×¥ì¥¤¥ä¡¼¤Ç¤¢¤ê¡¢
¤³¤Î mcd ¥É¥é¥¤¥Ð¤Ï»ÈÍѤ·¤Ê¤¤¡£
.TP
.\"O .B "The Mitsumi XA/MultiSession Interface"
.B Mitsumi XA/¥Þ¥ë¥Á¥»¥Ã¥·¥ç¥ó¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O This is for the same hardware as above, but the driver has extended features.
.\"O Syntax:
¤³¤ì¤Ï¾åµ­¤ÈƱ¤¸¥Ï¡¼¥É¥¦¥§¥¢¤À¤¬¡¢³ÈÄ¥µ¡Ç½¤¬¤¢¤ë¡£
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
mcdx=iobase[,irq]
.TP
.\"O .B "The Optics Storage Interface"
.B Optics ¥¹¥È¥ì¡¼¥¸¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this type of card is:
¤³¤Î¥«¡¼¥É¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
optcd=iobase
.TP
.\"O .B "The Phillips CM206 Interface"
.B Phillips CM206 ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this type of card is:
¤³¤Î¥«¡¼¥É¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
cm206=[iobase][,irq]
.IP
.\"O The driver assumes numbers between 3 and 11 are IRQ values, and
.\"O numbers between 0x300 and 0x370 are I/O ports, so you can specify one,
.\"O or both numbers, in any order.
.\"O It also accepts 'cm206=auto' to enable
.\"O autoprobing.
¥É¥é¥¤¥Ð¤Ï IRQ ÃͤȤ·¤Æ 3 ¤«¤é 11 ¤Þ¤Ç¡¢
I/O ¥Ý¡¼¥È¥¢¥É¥ì¥¹¤ÎÃͤȤ·¤Æ 0x300 ¤«¤é 0x370 ¤òÁÛÄꤷ¤Æ¤¤¤ë¡£
¤¤¤º¤ì¤«°ìÊý¡¢¤¢¤ë¤¤¤ÏξÊý¤ò»ØÄê¤Ç¤­¤ë¡£½çÈÖ¤âÌä¤ï¤Ê¤¤¡£
\&'cm206=auto' ¤È¤¹¤ë¤³¤È¤Ë¤è¤ê¼«Æ°¸¡½Ð¤â¤Ç¤­¤ë¡£
.TP
.\"O .B "The Sanyo Interface"
.B Sanyo ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this type of card is:
¤³¤Î¥«¡¼¥É¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
sjcd=iobase[,irq[,dma_channel]]
.TP
.\"O .B "The SoundBlaster Pro Interface"
.B SoundBlaster Pro ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹
.\"O The syntax for this type of card is:
¤³¤Î¥«¡¼¥É¤Î¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
sbpcd=iobase,type
.IP
.\"O where type is one of the following (case sensitive) strings:
.\"O \&'SoundBlaster', 'LaserMate', or 'SPEA'.
.\"O The I/O base is that of the
.\"O CD-ROM interface, and not that of the sound portion of the card.
type ÃÍ¤Ë¤Ï 'SoundBlaster', 'LaserMate', 'SPEA' ¤Î¤¦¤Á¤Ò¤È¤Ä¤ò»ØÄê¤Ç¤­¤ë
(Âçʸ»ú¾®Ê¸»ú¤¬¶èÊ̤µ¤ì¤ë)¡£
iobase ¤Ï CD-ROM ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ÎÃͤǤ¢¤ë¡£
¥«¡¼¥É¤Î¥µ¥¦¥ó¥ÉÉô¤ÎÃͤȴְ㤨¤Ê¤¤¤³¤È¡£
.\"O .SS "Ethernet Devices"
.SS "¥¤¡¼¥µ¥Í¥Ã¥È¥Ç¥Ð¥¤¥¹"
.\"O Different drivers make use of different parameters, but they all at
.\"O least share having an IRQ, an I/O port base value, and a name.
.\"O In its most generic form, it looks something like this:
¥É¥é¥¤¥Ð¤¬°Û¤Ê¤ë¤ÈÍѤ¤¤ë¥Ñ¥é¥á¡¼¥¿¤â°Û¤Ê¤ë¤¬¡¢
¤¹¤Ù¤Æ¤Î¥É¥é¥¤¥Ð¤Ï¡¢¾¯¤Ê¤¯¤È¤â³ä¤ê¹þ¤ßÈÖ¹æ (irq)¡¢
I/O ¥Ý¡¼¥È¤Î¥Ù¡¼¥¹¥¢¥É¥ì¥¹ (iobase)¡¢Ì¾Á° (name) ¤ò»ý¤Ä¡£
ºÇ¤â°ìÈÌŪ¤Ê·Á¼°¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
ether=irq,iobase[,param_1[,...param_8]],name
.IP
.\"O The first nonnumeric argument is taken as the name.
.\"O The param_n values (if applicable) usually have different meanings for each
.\"O different card/driver.
.\"O Typical param_n values are used to specify
.\"O things like shared memory address, interface selection, DMA channel
.\"O and the like.
ºÇ½é¤Î¿ô»ú¤Ç¤Ê¤¤ÃͤÏ̾Á°¤È¤·¤Æ»ÈÍѤµ¤ì¤ë¡£
param_n ¤ÎÃͤϥ«¡¼¥É (¥É¥é¥¤¥Ð) ¤´¤È¤Ë°Û¤Ê¤ë°ÕÌ£¤ò»ý¤Ä¡£
¤è¤¯¤¢¤ëÌÜŪ¤Ï¡¢¶¦Í­¥á¥â¥ê¥¢¥É¥ì¥¹¤Î»ØÄê¡¢¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ÎÁªÂò¡¢
DMA ¥Á¥ã¥Í¥ë¤Ê¤É¤Ç¤¢¤ë¡£

.\"O The most common use of this parameter is to force probing for a second
.\"O ethercard, as the default is to only probe for one.
.\"O This can be accomplished with a simple:
¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ÎºÇ¤â¤è¤¯¤¢¤ëÍøÍÑË¡¤Ï¡¢
2 ÈÖÌܤΠEthernet ¥«¡¼¥É¤ò¶¯À©Åª¤Ë¸¡½Ð¤µ¤»¤ë¾ì¹ç¤Ç¤¢¤ë
(¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï 1 Ë礷¤«¸¡½Ð¤·¤Ê¤¤)¡£
¤³¤ì¤Ï´Êñ¤Ç¡¢¼¡¤Î¤è¤¦¤Ë¤¹¤ì¤Ð¤è¤¤¡£
.IP
ether=0,0,eth1
.IP
.\"O Note that the values of zero for the IRQ and I/O base in the above
.\"O example tell the driver(s) to autoprobe.
¤³¤ÎÎã¤Ç IRQ ¤È I/O ¥Ù¡¼¥¹¥¢¥É¥ì¥¹¤Ë 0 ¤ò»ØÄꤷ¤Æ¤¤¤ë¤Î¤Ï¡¢
¥É¥é¥¤¥Ð¤Ë¼«Æ°¸¡½Ð¤ò¤¹¤ë¤è¤¦ÅÁ¤¨¤Æ¤¤¤ë¤Î¤Ç¤¢¤ë¡£

.\"O The Ethernet-HowTo has extensive documentation on using multiple
.\"O cards and on the card/driver-specific implementation
.\"O of the param_n values where used.
.\"O Interested readers should refer to
.\"O the section in that document on their particular card.
Ethernet-HOWTO ¤Ç¤Ï¡¢Ê£¿ô¤Î¥«¡¼¥É¤ò»È¤¦¤ä¤êÊý¤ä¡¢
¥«¡¼¥É¤ä¥É¥é¥¤¥Ð¤ËÆÃÍ­¤Î param_n ÃͤΰÕÌ£¤Ë¤Ä¤¤¤Æ¡¢
¤º¤Ã¤È¾ÜºÙ¤Ë²òÀ⤵¤ì¤Æ¤¤¤ë¡£
¶½Ì£¤ò»ý¤Ã¤¿ÆɼԤϡ¢¤³¤Îʸ½ñ¤Ë¤¢¤¿¤ê¡¢
¼«Ê¬¤Î¥«¡¼¥É¤Ë´Ø¤·¤Æ½ñ¤«¤ì¤Æ¤¤¤ë¥»¥¯¥·¥ç¥ó¤ò»²¾È¤¹¤ë¤ÈÎɤ¤¡£
.\"O .SS "The Floppy Disk Driver"
.SS ¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ð
.\"O There are many floppy driver options, and they are all listed in
.\"O .I Documentation/floppy.txt
.\"O (or
.\"O .I drivers/block/README.fd
.\"O for older kernels) in the kernel source.
.\"O This information is taken directly
.\"O from that file.
¥Õ¥í¥Ã¥Ô¡¼¥É¥é¥¤¥Ð¤Î¥ª¥×¥·¥ç¥ó¤Ï¿¿ô¤¢¤ê¡¢
¥«¡¼¥Í¥ë¥½¡¼¥¹Æâ¤Î
.I Documentation/floppy.txt
(¸Å¤¤¥«¡¼¥Í¥ë¤Î¾ì¹ç¤Ï
.IR drivers/block/README.fd )
¤Ë¤¹¤Ù¤Æµ­ºÜ¤µ¤ì¤Æ¤¤¤ë¡£
°Ê²¼¤Î¾ðÊó¤Ï¤³¤Î¥Õ¥¡¥¤¥ë¤«¤é¤È¤Ã¤¿¤â¤Î¤Ç¤¢¤ë¡£
.TP
.B "floppy=mask,allowed_drive_mask"
.\"O Sets the bit mask of allowed drives to mask.
.\"O By default, only units 0
.\"O and 1 of each floppy controller are allowed.
.\"O This is done because
.\"O certain nonstandard hardware (ASUS PCI motherboards) mess up the
.\"O keyboard when accessing units 2 or 3.
.\"O This option is somewhat
.\"O obsoleted by the cmos option.
»È¤Ã¤Æ¤è¤¤¥É¥é¥¤¥Ö¤Ë¤«¤±¤ë¥Ó¥Ã¥È¥Þ¥¹¥¯¤òÀßÄꤹ¤ë¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢
¥æ¥Ë¥Ã¥È 0 ¤È 1 ¤Î¥Õ¥í¥Ã¥Ô¡¼¥³¥ó¥È¥í¡¼¥é¤À¤±¤¬µö²Ä¤µ¤ì¤Æ¤¤¤ë¡£
¤³¤ì¤Ï¡¢É¸½à¤Ç¤Ê¤¤¥Ï¡¼¥É¥¦¥§¥¢ (Î㤨¤Ð ASUS ¤Î PCI¥Þ¥¶¡¼¥Ü¡¼¥É¤Ê¤É)
¤Ç¥æ¥Ë¥Ã¥È 2 ¤ä 3 ¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤È¡¢
¥­¡¼¥Ü¡¼¥É¤¬¤ª¤«¤·¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¦¤«¤é¤Ç¤¢¤ë¡£
cmos ¥ª¥×¥·¥ç¥ó (¸å½Ò) ¤ÎƳÆþ¤Ë¤è¤Ã¤Æ¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¤¢¤Þ¤ê»È¤ï¤ì¤Ê¤¯¤Ê¤Ã¤¿¡£
.TP
.B "floppy=all_drives"
.\"O Sets the bit mask of allowed drives to all drives.
.\"O Use this if you have
.\"O more than two drives connected to a floppy controller.
µö²Ä¤¹¤ë¥É¥é¥¤¥Ö¤ò¼¨¤¹¥Ó¥Ã¥È¥Þ¥¹¥¯¤ò¡¢¡Ö¤¹¤Ù¤Æ¤Î¥É¥é¥¤¥Ö¡×¤Ë¤¹¤ë¡£
1 ¤Ä¤Î¥Õ¥í¥Ã¥Ô¡¼¥³¥ó¥È¥í¡¼¥é¤Ë 2 Âæ°Ê¾å¤Î¥É¥é¥¤¥Ö¤òÀܳ¤¹¤ë¾ì¹ç¤ËÍѤ¤¤ë¡£
.TP
.B "floppy=asus_pci"
.\"O Sets the bit mask to allow only units 0 and 1.
.\"O (The default)
¥æ¥Ë¥Ã¥È 0 ¤È 1 ¤Î¤ß¤òµö²Ä¤¹¤ë¤è¤¦¥Ó¥Ã¥È¥Þ¥¹¥¯¤òÀßÄꤹ¤ë¡£
(¥Ç¥Õ¥©¥ë¥È)¡£
.TP
.B "floppy=daring"
.\"O Tells the floppy driver that you have a well behaved floppy
.\"O controller.
.\"O This allows more efficient and smoother operation, but
.\"O may fail on certain controllers.
.\"O This may speed up certain operations.
Àµ¤·¤¯¿¶¤ëÉñ¤¦¥Õ¥í¥Ã¥Ô¡¼¥³¥ó¥È¥í¡¼¥é¤ò»È¤Ã¤Æ¤¤¤ë¤³¤È¤ò¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤ÈÆ°ºî¤Ï¤è¤ê¸úΨŪ¤«¤Ä¥¹¥à¡¼¥¹¤Ë¤Ê¤ë¤¬¡¢
¥³¥ó¥È¥í¡¼¥é¤Ë¤è¤Ã¤Æ¤ÏÆ°ºî¤Ë¼ºÇÔ¤¹¤ë¤³¤È¤¬¤¢¤ë¡£
¤³¤ì¤ò»ØÄꤹ¤ë¤È¤¢¤ë¼ï¤ÎÆ°ºî¤¬¹â®¤Ë¤Ê¤ë¡£
.TP
.B "floppy=0,daring"
.\"O Tells the floppy driver that your floppy controller should be used
.\"O with caution.
Ãí°Õ¤·¤Æ°·¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤
¥Õ¥í¥Ã¥Ô¡¼¥³¥ó¥È¥í¡¼¥é¤Ç¤¢¤ë¤³¤È¤ò¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë¡£
.TP
.B "floppy=one_fdc"
.\"O Tells the floppy driver that you have only floppy controller (default)
¥Õ¥í¥Ã¥Ô¡¼¥³¥ó¥È¥í¡¼¥é¤¬¤Ò¤È¤Ä¤·¤«¤Ê¤¤¤³¤È¤ò¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë
(¥Ç¥Õ¥©¥ë¥È)¡£
.TP
.\"O .BR floppy=two_fdc " or " floppy=address,two_fdc
.BR floppy=two_fdc " ¤Þ¤¿¤Ï " floppy=address,two_fdc
.\"O Tells the floppy driver that you have two floppy controllers.
.\"O The second floppy controller is assumed to be at address.
.\"O If address is
.\"O not given, 0x370 is assumed.
¥Õ¥í¥Ã¥Ô¡¼¥³¥ó¥È¥í¡¼¥é¤¬¤Õ¤¿¤Ä¤¢¤ë¤³¤È¤ò¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë¡£
2 ÈÖÌܤΥ³¥ó¥È¥í¡¼¥é¤Î I/O ¥¢¥É¥ì¥¹¤Ï address ¤Ç»ØÄꤹ¤ë¡£
address ¤¬»ØÄꤵ¤ì¤Ê¤¤¾ì¹ç¤Ï 0x370 ¤¬»È¤ï¤ì¤ë¡£
.TP
.B "floppy=thinkpad"
.\"O Tells the floppy driver that you have a Thinkpad.
.\"O Thinkpads use an
.\"O inverted convention for the disk change line.
Thinkpad ¤ò»È¤Ã¤Æ¤¤¤ë¤³¤È¤ò¥Õ¥í¥Ã¥Ô¡¼¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë¡£
Thinkpad ¤Ï¥Ç¥£¥¹¥¯¼è½Ð¤Î¸¡½Ð¿®¹æ¤òȿž¤·¤Æ»È¤Ã¤Æ¤¤¤ë¡£
.TP
.B "floppy=0,thinkpad"
.\"O Tells the floppy driver that you don't have a Thinkpad.
Thinkpad ¤ò»È¤Ã¤Æ¤¤¤Ê¤¤¤³¤È¤ò¥É¥é¥¤¥Ð¤ËÅÁ¤¨¤ë¡£
.TP
.B "floppy=drive,type,cmos"
.\"O Sets the cmos type of drive to type.
.\"O Additionally, this drive is
.\"O allowed in the bit mask.
.\"O This is useful if you have more than two
.\"O floppy drives (only two can be described in the physical cmos), or if
.\"O your BIOS uses nonstandard CMOS types.
.\"O Setting the CMOS to 0 for the
.\"O first two drives (default) makes the floppy driver read the physical
.\"O cmos for those drives.
¥É¥é¥¤¥Ö¤Î cmos ¥¿¥¤¥×¤ò type ¤ËÀßÄꤹ¤ë¡£
¤µ¤é¤Ë¥Ó¥Ã¥È¥Þ¥¹¥¯¤òÊѹ¹¤·¡¢¤³¤Î¥É¥é¥¤¥Ö¤Î»ÈÍѤòµö²Ä¤¹¤ë¡£
¤³¤Î»ØÄ꤬ÊØÍø¤Ê¤Î¤Ï¡¢¥Õ¥í¥Ã¥Ô¡¼¥É¥é¥¤¥Ö¤¬ 2 Âæ°Ê¾å¤¢¤ë¾ì¹ç
(ʪÍý cmos ¤Ëµ­½Ò¤Ç¤­¤ë¤Î¤Ï 2 Âæ¤Þ¤Ç) ¤ä¡¢
BIOS ¤¬É¸½àŪ¤Ç¤Ê¤¤ CMOS ¥¿¥¤¥×¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ç¤¢¤ë¡£
ºÇ½é¤Î 2 Âæ¤Î¥É¥é¥¤¥Ö¤Î CMOS ¤Ë 0 ¤ò»ØÄꤹ¤ë (¥Ç¥Õ¥©¥ë¥È) ¤È¡¢
¥Õ¥í¥Ã¥Ô¡¼¥É¥é¥¤¥Ð¤Ï¤³¤ì¤é¤Î¥É¥é¥¤¥Ö¤ÎʪÍý cmos ¤ò»²¾È¤¹¤ë¡£
.TP
.B "floppy=unexpected_interrupts"
.\"O Print a warning message when an unexpected interrupt is received
.\"O (default behavior)
ͽ´ü¤·¤Ê¤¤³ä¤ê¹þ¤ß¤ò¼õ¤±¤¿»þ¤Ë·Ù¹ð¥á¥Ã¥»¡¼¥¸¤òɽ¼¨¤¹¤ë (¥Ç¥Õ¥©¥ë¥È)¡£
.TP
.\"O .BR floppy=no_unexpected_interrupts " or " floppy=L40SX
.BR floppy=no_unexpected_interrupts " ¤Þ¤¿¤Ï " floppy=L40SX
.\"O Don't print a message when an unexpected interrupt is received.
.\"O This is needed on IBM L40SX laptops in certain video modes.
.\"O (There seems to
.\"O be an interaction between video and floppy.
.\"O The unexpected interrupts
.\"O only affect performance, and can safely be ignored.)
ͽ´ü¤·¤Ê¤¤³ä¤ê¹þ¤ß¤ò¼õ¤±¤¿»þ¤Ç¤â·Ù¹ð¥á¥Ã¥»¡¼¥¸¤òɽ¼¨¤·¤Ê¤¤¡£
¤³¤ì¤Ï IBM L40SX ¥é¥Ã¥×¥È¥Ã¥×¥³¥ó¥Ô¥å¡¼¥¿¤ò
ÆÃÄê¤Î¥Ó¥Ç¥ª¥â¡¼¥É¤Ç»ÈÍѤ¹¤ë»þ¤ËɬÍפȤʤ롣
(¥Ó¥Ç¥ª¤È¥Õ¥í¥Ã¥Ô¡¼¤È¤Î´Ö¤Ç²¿¤é¤«¤ÎÁê¸ßºîÍѤ¬¤¢¤ë¤è¤¦¤À¡£
ͽ´ü¤·¤Ê¤¤³ä¤ê¹þ¤ß¤ÏÀ­Ç½¤À¤±¤Ë±Æ¶Á¤·¡¢Ìµ»ë¤·¤Æ¤â°ÂÁ´¤Ç¤¢¤ë¡£)
.\"O .SS "The Sound Driver"
.SS ¥µ¥¦¥ó¥É¥É¥é¥¤¥Ð
.\"O The sound driver can also accept boot args to override the compiled in
.\"O values.
.\"O This is not recommended, as it is rather complex.
.\"O It is described in the kernel source file
.\"O .IR Documentation/sound/oss/README.OSS
.\"O .RI ( drivers/sound/Readme.linux
.\"O in older kernel versions).
.\"O Readme.Linux file, in linux/drivers/sound.
.\"O It accepts
.\"O a boot arg of the form:
¥µ¥¦¥ó¥É¥É¥é¥¤¥Ð¤âµ¯Æ°»þ°ú¿ô¤ò¼õ¤±ÉÕ¤±¡¢
¥³¥ó¥Ñ¥¤¥ë»þ¤Ë»ØÄꤵ¤ì¤¿ÃͤòÊѹ¹¤Ç¤­¤ë¡£
¤³¤ì¤Ï¤ä¤äÌÌÅݤʤ¿¤á¡¢¤¢¤Þ¤ê¤ªÁ¦¤á¤Ç¤­¤Ê¤¤¡£
¾ÜºÙ¤Ï¡¢¥«¡¼¥Í¥ë¥½¡¼¥¹Æâ¤Î
.IR Documentation/sound/oss/README.OSS
(¸Å¤¤¥«¡¼¥Í¥ë¤Î¾ì¹ç¤Ï
.IR drivers/sound/Readme.linux )
¤Ëµ­ºÜ¤µ¤ì¤Æ¤¤¤ë¡£
°ú¿ô¤Î·Á¼°¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
sound=device1[,device2[,device3...[,device10]]]
.IP
.\"O where each deviceN value is of the following format 0xTaaaId and the
.\"O bytes are used as follows:
³Æ deviceN ¤Ï¤½¤ì¤¾¤ì 0xTaaaId ¤È¤¤¤¦·Á¼°¤Ç»ØÄꤹ¤ë¡£
³Æ¥Ð¥¤¥È¤Î°ÕÌ£¤Ï°Ê²¼¤ÎÄ̤ꡣ

.\"O T \- device type: 1=FM, 2=SB, 3=PAS, 4=GUS, 5=MPU401, 6=SB16,
.\"O 7=SB16-MPU401
T \- ¥Ç¥Ð¥¤¥¹¤Î¥¿¥¤¥×: 1=FM, 2=SB, 3=PAS, 4=GUS, 5=MPU401, 6=SB16, 7=SB16-MPU401

.\"O aaa \- I/O address in hex.
aaa \- I/O ¥Ý¡¼¥È¥¢¥É¥ì¥¹ (16¿ÊÃÍ)

.\"O I \- interrupt line in hex (i.e 10=a, 11=b, ...)
I \- ³ä¤ê¹þ¤ßÈÖ¹æ (16 ¿ÊÃÍ¡£Îã: 10=a, 11=b, ...)

.\"O d \- DMA channel.
d \- DMA ¥Á¥ã¥Í¥ë

.\"O As you can see it gets pretty messy, and you are better off to compile
.\"O in your own personal values as recommended.
.\"O Using a boot arg of
.\"O \&'sound=0' will disable the sound driver entirely.
¾åµ­¤ÎÄ̤ꡢ¤«¤Ê¤ê°·¤¤¤Ë¤¯¤¤·Á¼°¤È¤Ê¤Ã¤Æ¤ª¤ê¡¢
¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¼«Ê¬¤Ë¤¢¤Ã¤¿Ãͤò»ØÄꤹ¤ëÊý¤¬Îɤ¤¤À¤í¤¦¡£
¤Ê¤ªµ¯Æ°»þ°ú¿ô¤È¤·¤Æ 'sound=0' ¤ò»ØÄꤹ¤ë¤È¡¢
¥µ¥¦¥ó¥É¥É¥é¥¤¥Ð¤ò´°Á´¤Ë̵¸ú¤Ë¤¹¤ë¡£
.\"O .SS "ISDN Drivers"
.SS "ISDN ¥É¥é¥¤¥Ð"
.TP
.\"O .B "The ICN ISDN driver"
.B ICN ISDN ¥É¥é¥¤¥Ð
.\"O Syntax:
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
icn=iobase,membase,icn_id1,icn_id2
.IP
.\"O where icn_id1,icn_id2 are two strings used to identify the
.\"O card in kernel messages.
icn_id1,icn_id2 ¤Ï¥«¡¼¥É¤ò¼±Ê̤¹¤ë¤¿¤á¤Î 2 ¤Ä¤Îʸ»úÎó¤Ç¤¢¤ë¡£
¥«¡¼¥Í¥ë¥á¥Ã¥»¡¼¥¸¤ÇÍѤ¤¤é¤ì¤ë¡£
.TP
.\"O .B "The PCBIT ISDN driver"
.B PCBIT ISDN ¥É¥é¥¤¥Ð
.\"O Syntax:
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
pcbit=membase1,irq1[,membase2,irq2]
.IP
.\"O where membaseN is the shared memory base of the N'th card, and irqN is
.\"O the interrupt setting of the N'th card.
.\"O The default is IRQ 5 and
.\"O membase 0xD0000.
membaseN ¤Ï N ÈÖÌܤΥ«¡¼¥É¤Î¶¦Í­¥á¥â¥ê¤Î¥Ù¡¼¥¹¥¢¥É¥ì¥¹¤Ç¤¢¤ê¡¢
irqN ¤Ï N ÈÖÌܤΥ«¡¼¥É¤Î³ä¤ê¹þ¤ßÀßÄê¤Ç¤¢¤ë¡£
̵»ØÄê»þ¤Ë¤Ï IRQ = 5, membase = 0xD0000 ¤È¤Ê¤ë¡£
.TP
.\"O .B "The Teles ISDN driver"
.B Teles ISDN ¥É¥é¥¤¥Ð
.\"O Syntax:
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
teles=iobase,irq,membase,protocol,teles_id
.IP
.\"O where iobase is the i/o port address of the card, membase is the
.\"O shared memory base address of the card, irq is the interrupt channel
.\"O the card uses, and teles_id is the unique ASCII string identifier.
iobase ¤Ï¥«¡¼¥É¤Î I/O ¥Ý¡¼¥È¥¢¥É¥ì¥¹¡¢
membase ¤Ï¥«¡¼¥É¤Î¶¦Í­¥á¥â¥ê¤Î¥Ù¡¼¥¹¥¢¥É¥ì¥¹¡¢
¤½¤·¤Æ irq ¤Ï¥«¡¼¥É¤¬»ÈÍѤ¹¤ë³ä¤ê¹þ¤ß¥Á¥ã¥Í¥ë¤Ç¤¢¤ë¡£
teles_id ¤Ï¥¢¥¹¥­¡¼Ê¸»úÎó¤Ë¤è¤ë¼±ÊÌʸ»úÎó¤Ç¤¢¤ë (¾¤È½Å¤Ê¤é¤Ê¤¤¤è¤¦¤Ë¤¹¤ë)¡£
.\"O .SS "Serial Port Drivers"
.SS ¥·¥ê¥¢¥ë¥Ý¡¼¥È¥É¥é¥¤¥Ð
.TP
.\"O .B "The RISCom/8 Multiport Serial Driver ('riscom8=')"
.B RISCom/8 ¥Þ¥ë¥Á¥Ý¡¼¥È¥·¥ê¥¢¥ë¥É¥é¥¤¥Ð ('riscom8=')
.\"O Syntax:
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
riscom=iobase1[,iobase2[,iobase3[,iobase4]]]
.IP
.\"O More details can be found in
.\"O .IR /usr/src/linux/Documentation/riscom8.txt .
¾ÜºÙ¤Ï
.I /usr/src/linux/Documentation/riscom8.txt
¤ò»²¾È¤Î¤³¤È¡£
.TP
.\"O .B "The DigiBoard Driver ('digi=')"
.B DigiBoard ¥É¥é¥¤¥Ð ('digi=')
.\"O If this option is used, it should have precisely six parameters.
.\"O Syntax:
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¾ì¹ç¤Ï¡¢
6 ¤Ä¤Á¤ç¤¦¤É¤Î¥Ñ¥é¥á¡¼¥¿¤òÍ¿¤¨¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
digi=status,type,altpin,numports,iobase,membase
.IP
.\"O The parameters maybe given as integers, or as strings.
.\"O If strings are used, then iobase and membase should be given
.\"O in hexadecimal.
.\"O The integer arguments (fewer may be given) are in order:
.\"O status (Enable(1) or Disable(0) this card),
.\"O type (PC/Xi(0), PC/Xe(1), PC/Xeve(2), PC/Xem(3)),
.\"O altpin (Enable(1) or Disable(0) alternate pin arrangement),
.\"O numports (number of ports on this card),
.\"O iobase (I/O Port where card is configured (in HEX)),
.\"O membase (base of memory window (in HEX)).
.\"O Thus, the following two boot prompt arguments are equivalent:
¥Ñ¥é¥á¡¼¥¿¤ÏÀ°¿ôÃͤ«Ê¸»úÎó¤ÇÍ¿¤¨¤ë¡£
ʸ»úÎó¤Ç»ØÄꤹ¤ë¾ì¹ç¤Ï¡¢
iobase ¤È membase ¤Ï 16 ¿ÊÃͤǤʤ±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
À°¿ôÃͤǻØÄꤹ¤ë¾ì¹ç¤Ï¥Ñ¥é¥á¡¼¥¿¤Î¸Ä¿ô¤Ï¾¯¤Ê¤¯¤Æ¤âÎɤ¯¡¢½ç¤Ë:
status ¤³¤Î¥«¡¼¥É¤ÎÆ°ºî¤ò»ØÄꤹ¤ë (Enable(1) ¤Þ¤¿¤Ï Disable(0)),
type ¥«¡¼¥É¤Î¥¿¥¤¥× (PC/Xi(0), PC/Xe(1), PC/Xeve(2), PC/Xem(3)),
altpin ¥Ô¥óÇÛÃÖ¤òȿž¤µ¤»¤ë (Enable(1) or Disable(0)),
numports ¥«¡¼¥É¤Î¥Ý¡¼¥ÈÈÖ¹æ,
iobase ¤³¤Î¥«¡¼¥É¤Î I/O ¥Ý¡¼¥È (ʸ»úÎó»ØÄê¤Î¾ì¹ç¤Ï 16 ¿Êɽµ­),
membase ¥á¥â¥ê¥¦¥£¥ó¥É¥¦¤Î¥Ù¡¼¥¹¥¢¥É¥ì¥¹ (ʸ»úÎó»ØÄê¤Î¾ì¹ç¤Ï 16 ¿Êɽµ­)¡£
¤·¤¿¤¬¤Ã¤Æ°Ê²¼¤Î¤Õ¤¿¤Ä¤Îµ¯Æ°»þ°ú¿ô¤ÏƱ¤¸°ÕÌ£¤ò»ý¤Ä¡£
.IP
digi=E,PC/Xi,D,16,200,D0000
.br
digi=1,0,0,16,0x200,851968
.IP
.\"O More details can be found in
.\"O .IR /usr/src/linux/Documentation/digiboard.txt .
¾ÜºÙ¤Ï
.I /usr/src/linux/Documentation/digiboard.txt
¤ò»²¾È¤»¤è¡£
.TP
.\"O .B "The Baycom Serial/Parallel Radio Modem"
.B Baycom ¥·¥ê¥¢¥ë¡¦¥Ñ¥é¥ì¥ë ¥é¥¸¥ª¥â¥Ç¥à
.\"O Syntax:
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
baycom=iobase,irq,modem
.IP
.\"O There are precisely 3 parameters; for several cards, give
.\"O several 'baycom=' commands.
.\"O The modem parameter is a string
.\"O that can take one of the values ser12, ser12*, par96, par96*.
.\"O Here the * denotes that software DCD is to be used, and
.\"O ser12/par96 chooses between the supported modem types.
.\"O For more details, see the file
.\"O .I Documentation/networking/baycom.txt
.\"O (or
.\"O .I drivers/net/README.baycom
.\"O for older kernels) in the kernel source.
¤Á¤ç¤¦¤É 3 ¤Ä¤Î¥Ñ¥é¥á¡¼¥¿¤òÍ¿¤¨¤ë¡£
Ê£¿ô¤Î¥«¡¼¥É¤¬¤¢¤ë¾ì¹ç¤Ï¡¢'baycom=' ¥³¥Þ¥ó¥É¤âÊ£¿ôµ­½Ò¤¹¤ë¡£
modem ¥Ñ¥é¥á¡¼¥¿¤Ïʸ»úÎó¤Ç¡¢
ser12, ser12*, par96, par96* ¤ÎÃ椫¤é¤Ò¤È¤Ä¤òÁª¤Ö¡£
* ¤ò¤Ä¤±¤ë¤È¥½¥Õ¥È¥¦¥§¥¢ DCD ¤ò»ÈÍѤ¹¤ë¡£
¥â¥Ç¥à¤Î¼ïÎà¤Ë±þ¤¸¤Æ ser12 ¤« par96 ¤«¤òÁªÂò¤¹¤ë¡£
¾ÜºÙ¤Ï¥«¡¼¥Í¥ë¥½¡¼¥¹Æâ¤Î
.I Documentation/networking/baycom.txt
(¸Å¤¤¥«¡¼¥Í¥ë¤Î¾ì¹ç¤Ï
.IR drivers/net/README.baycom )
¤ò»²¾È¡£
.TP
.\"O .B "Soundcard radio modem driver"
.B ¥µ¥¦¥ó¥É¥«¡¼¥É¥é¥¸¥ª¥â¥Ç¥à¥É¥é¥¤¥Ð
.\"O Syntax:
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
soundmodem=iobase,irq,dma[,dma2[,serio[,pario]]],0,mode
.IP
.\"O All parameters except the last are integers;
.\"O the dummy 0 is required because of a bug in the setup code.
.\"O The mode parameter is a string with syntax hw:modem,
.\"O where hw is one of sbc, wss, wssfdx and modem is one of
.\"O afsk1200, fsk9600.
ºÇ¸å¤Î¥Ñ¥é¥á¡¼¥¿¤ò½ü¤¯¤¹¤Ù¤Æ¤Î¥Ñ¥é¥á¡¼¥¿¤ÏÀ°¿ô¤Ç¤¢¤ë¡£
¥À¥ß¡¼¤Î 0 ¤¬¤¢¤ë¤Î¤Ï¡¢ÀßÄê¥×¥í¥°¥é¥à¤Î¥Ð¥°¤Î¤»¤¤¤Ç¤¢¤ë¡£
mode ¥Ñ¥é¥á¡¼¥¿¤Ïʸ»úÎó¤Ç¡¢hw:modem ¤È¤¤¤¦½ñ¼°¤Ç»ØÄꤹ¤ë¡£
hw ¤Ï sbc, wss, wssfdx ¤Î¤¦¤Á¤Ò¤È¤Ä¡¢
modem ¤Ï afsk1200, fsk9600 ¤Î¤É¤Á¤é¤«¤òÁªÂò¤·¤Æµ­½Ò¤¹¤ë¡£
.\" HERE GOES (NAKANO)
.\"O .SS "The Line Printer Driver"
.SS ¥é¥¤¥ó¥×¥ê¥ó¥¿¥É¥é¥¤¥Ð
.TP
.B "'lp='"
.\"O Syntax:
½ñ¼°:
.IP
lp=0
.br
lp=auto
.br
lp=reset
.br
lp=port[,port...]
.IP
.\"O You can tell the printer driver what ports to use and what ports not
.\"O to use.
.\"O The latter comes in handy if you don't want the printer driver
.\"O to claim all available parallel ports, so that other drivers
.\"O (e.g., PLIP, PPA) can use them instead.
¥×¥ê¥ó¥¿¥É¥é¥¤¥Ð¤Ë¤Ï¡¢¤É¤Î¥Ý¡¼¥È¤ò»È¤¦¤«¡¢
¤É¤Î¥Ý¡¼¥È¤ò»È¤Ã¤Æ¤Ï¤¤¤±¤Ê¤¤¤«¤òÅÁ¤¨¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
¸å¼Ô¤Ï¡¢
ÍøÍѲÄǽ¤Ê¤¢¤é¤æ¤ë¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤ò¥×¥ê¥ó¥¿¥É¥é¥¤¥Ð¤¬Í׵ᤷ¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¡¢
¾¤Î¥É¥é¥¤¥Ð (PLIP ¤ä PPA ¤Ê¤É) ¤«¤é
¤½¤ì¤é¤ò»È¤¨¤ë¤è¤¦¤Ë¤·¤¿¤¤¾ì¹ç¤ËÊØÍø¤Ç¤¢¤ë¡£

.\"O The format of the argument is multiple port names.
.\"O For example,
.\"O lp=none,parport0 would use the first parallel port for lp1, and
.\"O disable lp0.
.\"O To disable the printer driver entirely, one can use
.\"O lp=0.
°ú¿ô¤Î½ñ¼°¤Ï¡¢Ê£¿ô¤Î¥Ý¡¼¥È̾¤Ç¤¢¤ë¡£
Î㤨¤Ð lp=none,parport0 ¤È¤¹¤ë¤È¡¢
ºÇ½é¤Î¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤ò lp1 ¤È¤·¤Æ»È¤¤¡¢
lp0 ¤Ï̵¸ú¤Ë¤¹¤ë¡£¥×¥ê¥ó¥¿¡¼¥É¥é¥¤¥Ð¤ò´°Á´¤Ë̵¸ú¤Ë¤¹¤ë¤Ë¤Ï
lp=0 ¤È¤¹¤ì¤Ð¤è¤¤¡£
.TP
.\"O .B "WDT500/501 driver"
.B WDT500/501 ¥É¥é¥¤¥Ð
.\"O Syntax:
¹½Ê¸¤Ï°Ê²¼¤ÎÄ̤ꡣ
.IP
wdt=io,irq
.\"O .SS "Mouse Drivers"
.SS ¥Þ¥¦¥¹¥É¥é¥¤¥Ð
.TP
.B "'bmouse=irq'"
.\"O The busmouse driver only accepts one parameter, that being the
.\"O hardware IRQ value to be used.
¥Ð¥¹¥Þ¥¦¥¹¥É¥é¥¤¥Ð¤Ï¥Ñ¥é¥á¡¼¥¿¤ò¤Ò¤È¤Ä¤À¤±¤È¤ê¡¢
¥Ï¡¼¥É¥¦¥§¥¢ IRQ ¤ò»ØÄê¤Ç¤­¤ë¡£
.TP
.B "'msmouse=irq'"
.\"O And precisely the same is true for the msmouse driver.
msmouse ¥É¥é¥¤¥Ð¤Ç¤â¤³¤Î»ö¾ð¤Ï¤Þ¤Ã¤¿¤¯Æ±¤¸¤Ç¤¢¤ë¡£
.TP
.\"O .B "ATARI mouse setup"
.B ATARI ¥Þ¥¦¥¹¤ÎÀßÄê
.IP
atamouse=threshold[,y-threshold]
.IP
.\"O If only one argument is given, it is used for both
.\"O x-threshold and y-threshold.
.\"O Otherwise, the first argument
.\"O is the x-threshold, and the second the y-threshold.
.\"O These values must lie between 1 and 20 (inclusive); the default is 2.
¥Ñ¥é¥á¡¼¥¿¤¬¤Ò¤È¤Ä¤À¤±Í¿¤¨¤é¤ì¤¿¾ì¹ç¤Ë¤Ï¡¢
x-threshold ¤È y-threshold ¤òξÊý¤ËÍѤ¤¤é¤ì¤ë¡£
¤Õ¤¿¤ÄÍ¿¤¨¤é¤ì¤¿¾ì¹ç¤Ï¡¢ºÇ½é¤ÎÃͤ¬ x-threshold ¤È¤·¤ÆÍѤ¤¤é¤ì¡¢
2 ÈÖÌܤÎÃͤ¬ y-threshold ¤È¤·¤ÆÍѤ¤¤é¤ì¤ë¡£
ÃÍ¤Ï 1 ¤«¤é 20 ¤Þ¤Ç¤Î¿ôÃͤǻØÄꤹ¤ë¡£
¥Ç¥Õ¥©¥ë¥È¤Ï 2¡£
.\"O .SS "Video Hardware"
.SS ¥Ó¥Ç¥ªµ¡´ï
.TP
.B "'no-scroll'"
.\"O This option tells the console driver not to use hardware scroll
.\"O (where a scroll is effected by moving the screen origin in video
.\"O memory, instead of moving the data).
.\"O It is required by certain
.\"O Braille machines.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¥³¥ó¥½¡¼¥ë¥É¥é¥¤¥Ð¤Ë¡¢
¥Ï¡¼¥É¥¦¥§¥¢¥¹¥¯¥í¡¼¥ë¤òÍѤ¤¤Ê¤¤¤è¤¦ÅÁ¤¨¤ë
(¤³¤³¤Ç¸À¤¦¥Ï¡¼¥É¥¦¥§¥¢¥¹¥¯¥í¡¼¥ë¤È¤Ï¡¢
¥Ó¥Ç¥ª¥á¥â¥ê¾å¤Î¥Ç¡¼¥¿¤ò°ÜÆ°¤µ¤»¤ë¤³¤È¤Ë¤è¤Ã¤Æ
¥¹¥¯¥ê¡¼¥óɽ¼¨Îΰè¤ò¥¹¥¯¥í¡¼¥ë¤µ¤»¤ë¤³¤È¤ò»Ø¤¹)¡£
ÆÃÄê¤ÎÅÀ»ú¥Þ¥·¥ó¤Ç¤Ï¤³¤Î»ØÄ꤬ɬÍפȤʤ롣
.\"O .\" .SH AUTHORS
.\"O .\" Linus Torvalds (and many others)
.\" .SH Ãø¼Ô
.\" Linus Torvalds (¾¿¿ô)
.\"O .SH "SEE ALSO"
.SH ´ØÏ¢¹àÌÜ
.BR lilo.conf (5),
.BR klogd (8),
.BR lilo (8),
.BR mount (8),
.BR rdev (8)

.\"O Large parts of this man page have been derived from the
.\"O Boot Parameter HOWTO (version 1.0.1) written by Paul Gortmaker.
.\"O More information may be found in this (or a more recent) HOWTO.
.\"O An up-to-date source of information is
.\"O .IR /usr/src/linux/Documentation/kernel-parameters.txt .
¤³¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ÎÂçÉôʬ¤Ï Paul Gortmaker ¤Ë¤è¤ë
Boot Parameter HOWTO (version 1.0.1) ¤ò´ð¤Ë¤·¤Æ¤¤¤ë¡£
¤³¤Î (¤¢¤ë¤¤¤ÏºÇ¿·¤Î) HOWTO ¤ò¤¢¤¿¤ì¤Ð¡¢
¤µ¤é¤Ë¿¤¯¤Î¾ðÊó¤¬Æþ¼ê¤Ç¤­¤ë¤À¤í¤¦¡£
ºÇ¿·¤Î¾ðÊ󸻤Ï
.I /usr/src/linux/Documentation/kernel-parameters.txt
¤Ç¤¢¤ë¡£

(ÌõÃí) Boot Parameter HOWTO ¤Ï¸½ºß BootPrompt-HOWTO ¤È¤·¤Æ
¥á¥ó¥Æ¥Ê¥ó¥¹¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ËÙ¹¾À¿°ì¤µ¤ó¤Ë¤è¤ëÆüËܸìÈǤϡ¢
.UR http://www.linux.or.jp/JF/JFdocs/BootPrompt-HOWTO.html
http://www.linux.or.jp/JF/JFdocs/BootPrompt-HOWTO.html
.UE
¤Ë¤¢¤ê¤Þ¤¹¡£±Ñ¸ìÈÇ¥ª¥ê¥¸¥Ê¥ë¤Ï¡¢
.UR http://linuxdoc.org/HOWTO/BootPrompt-HOWTO.html
http://linuxdoc.org/HOWTO/BootPrompt-HOWTO.html
.UE
¤Ë¤¢¤ê¤Þ¤¹¡£
¤¬¡¢¤¤¤º¤ì¤â May 1999 ¤Þ¤Ç¤Î¤â¤Î¤Ê¤Î¤Ç¤ä¤ä¸Å¤¤¤Ç¤¹¡£