os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

iUpdated to reflect changes to kernel config on the 3.x branch, new

Browse source 
devices, and so on and so forth.

PR:		docs/11182
Submitted by:	Chris Costello <chris@holly.dyndns.org>
This commit is contained in:
Nik Clayton 1999-05-16 13:29:08 +00:00
parent 72d00f2591
commit 25dbcfcde2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=4898
3 changed files with 414 additions and 69 deletions
en/handbook/kernelconfig
chapter.sgml
en_US.ISO8859-1/books/handbook/kernelconfig
chapter.sgml
en_US.ISO_8859-1/books/handbook/kernelconfig
chapter.sgml

161
en/handbook/kernelconfig/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.14 1999-03-08 22:04:42 nik Exp $
$Id: chapter.sgml,v 1.15 1999-05-16 13:29:08 nik Exp $
-->
<chapter id="kernelconfig">
@ -101,8 +101,10 @@
editor. If you are just starting out, the only editor available will
probably be <command>vi</command>, which is too complex to explain here,
but is covered well in many books in the <link
linkend="bibliography">bibliography</link>. Feel free to change the
comment lines at the top to reflect your configuration or the changes
linkend="bibliography">bibliography</link>. However, FreeBSD does
offer an easier editor called &ldquo;ee&rdquo; which, if you are a
beginner, should be your editor of choise. Feel free to change the
comment lines at the top to reflect your configuration or the changes
you have made to differentiate it from
<filename>GENERIC</filename>.</para>
@ -197,14 +199,17 @@
<listitem>
<para>The first keyword is <literal>machine</literal>, which,
since FreeBSD only runs on Intel 386 and compatible chips, is
i386.</para>
since FreeBSD only runs on Intel 386 (and compatible) chips and
DEC Alpha processors, will be either
<replaceable>i386</replaceable> or
<replaceable>alpha</replaceable>.</para>
<note>
<para>Any keyword which contains numbers used as text must be
enclosed in quotation marks, otherwise
<command>config</command> gets confused and thinks you mean
the actual number 386.</para>
the actual number 386 if you enter
<literal>machine i386</literal>.</para>
</note>
</listitem>
</varlistentry>
@ -216,9 +221,10 @@
<listitem>
<para>The next keyword is <literal>cpu</literal>, which includes
support for each CPU supported by FreeBSD. The possible values
of <replaceable>cpu_type</replaceable> include:</para>
of <replaceable>cpu_type</replaceable> for i386 systems
include:</para>
<itemizedlist>
<listitem>
<para>I386_CPU</para>
</listitem>
@ -234,7 +240,19 @@
<listitem>
<para>I686_CPU</para>
</listitem>
</itemizedlist>
<para>The values availible for <replaceable>cpu_type</replaceable>
for Alpha systems include:</para>
<itemizedlist>
<listitem>
<para>EV4</para>
</listitem>
<listitem>
<para>EV5</para>
</listitem>
</itemizedlist>
<para>Multiple instances of the <literal>cpu</literal> line may be
@ -329,7 +347,7 @@
of the line specifies the disk and partition where the root
filesystem and kernel can be found. Typically this will be
<literal>wd0</literal> for systems with non-SCSI drives, or
<literal>sd0</literal> for systems with SCSI drives.</para>
<literal>da0</literal> for systems with SCSI drives.</para>
</listitem>
</varlistentry>
</variablelist>
@ -443,9 +461,9 @@
workstation from Ethernet. You can include other commonly-used
filesystems in the kernel, but feel free to comment out support for
filesystems you use less often (perhaps the MS-DOS filesystem?), since
they will be dynamically loaded from the Loadable Kernel Module
directory <filename>/lkm</filename> the first time you mount a
partition of that type.</para>
they will be dynamically loaded from the Kernel Module directory
<filename>/modules</filename> the first time you mount a partition
of that type.</para>
<variablelist>
<varlistentry>
@ -809,15 +827,19 @@
<listitem>
<para>NCR 53C810, 53C815, 53C825, 53C860, 53C875 PCI SCSI
controller</para>
<note>
<para>This also supports the Diamond FirePort
controller.</para>
</note>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "SCSI_DELAY=15"</literal></term>
<term><literal>options SCSI_DELAY=15000</literal></term>
<listitem>
<para>This causes the kernel to pause 15 seconds before probing
@ -840,7 +862,7 @@
</varlistentry>
<varlistentry>
<term><literal>device sd0</literal></term>
<term><literal>device da0</literal></term>
<listitem>
<para>Support for SCSI hard drives.</para>
@ -876,7 +898,7 @@
</sect2>
<sect2>
<title>Console, Bus Mouse, and X Server Support</title>
<title>Console, Bus Mouse, Keyboard, and X Server Support</title>
<para>You must choose one of these two console types, and, if you plan
to use the X Window System with the vt220 console, enable the XSERVER
@ -898,7 +920,74 @@
trouble running under this console.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller atkbdc0 at isa? port IO_KBD
tty</literal></term>
<listitem>
<para>The keyboard controller <literal>atkbdc</literal> provides
I/O services for the AT keyboard and PS/2 style pointing
devices. This controller is required by the keyboard driver
<literal>atkbd</literal> and the PS/2 pointing device driver
<literal>psm</literal>.
</para>
<variablelist>
<varlistentry>
<term><literal>options
"KBD_RESETDELAY=<replaceable>X</replaceable>", options
"KBD_MAXWAIT=<replaceable>Y</replaceable>"</literal></term>
<listitem>
<para>The keyboard driver <literal>atkbd</literal> and the
pointing device driver <literal>psm</literal> may ask the
<literal>atkbdc</literal> driver to reset the devices
during the boot process. It sometimes takes a long time
before these devices respond to the reset command. These
options control how long the <literal>atkbdc</literal>
driver should wait before giving up &mdash; the driver
will wait <replaceable>X</replaceable> *
<replaceable>Y</replaceable> milliseconds at most. If the
drivers seem unable to detect devices, you may want to
increase these values. The default values are 200
milliseconds for <replaceable>X</replaceable> and 5 for
<replaceable>Y</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options
"KBDIO_DEBUG=<replaceable>N</replaceable>"</literal></term>
<listitem>
<para>Sets the debug level to <replaceable>N</replaceable>.
The default value is zero, which supresses all debugging
output.</para>
</listitem>
</varlistentry>
</variablelist>
<note>
<para>There can only be one <literal>atkbdc</literal> device
configured into the system.
</para>
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device atkbd0 at isa? tty irq 1</literal></term>
<listitem>
<para>The <literal>atkbd</literal> driver, together with the
<literal>atkbdc</literal> controller, provides access to the
AT 84 keyboard or the AT enhanced keyboard which is connected
to the AT keyboard controller.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device vt0 at isa? port "IO_KBD" tty irq 1 vector
pcrint</literal></term>
@ -937,7 +1026,6 @@
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
@ -1051,14 +1139,24 @@
your particular Ethernet card(s):</para>
<variablelist>
<varlistentry>
<term><literal>device cs0</literal></term>
<listitem>
<para>IBM Etherjet and other Crystal Semi CS89x0-based
adapters.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device de0</literal></term>
<listitem>
<para>Ethernet adapters based on Digital Equipment DC21040,
DC21041 or DC21140 chips</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device fxp0</literal></term>
@ -1429,6 +1527,18 @@
warned (but it does not require a sound card).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0
</literal></term>
<listitem>
<para>The <literal>pcm</literal> driver provides support for
various ISA sound cards that are compatible with the WSS/MSS
specs, or with the Sound Blaster Pro and Sound Blaster
16.</para>
</listitem>
</varlistentry>
</variablelist>
<note>
@ -1457,6 +1567,11 @@
that have been compressed with <command>gzip</command>. The
programs in <filename>/stand</filename> are compressed so it is
a good idea to have this option in your kernel.</para>
<note>
<para>The <literal>gzip</literal> feature currently only works
with a.out binaries.</para>
</note>
</listitem>
</varlistentry>
@ -1652,7 +1767,7 @@ controller wcd0</programlisting>
<screen>config: line 17: syntax error</screen>
you can skip to the problem in <command>vi</command> by typing
<COMMAND>17G</COMMAND> in command mode. Make sure the keyword is
<command>17G</command> in command mode. Make sure the keyword is
typed correctly, by comparing it to the GENERIC kernel or another
reference.</para>
</listitem>
@ -1725,8 +1840,8 @@ controller wcd0</programlisting>
<listitem>
<para>If you have installed a different version of the kernel from
the one that the system utilities have been built with, for
example, an experimental &ldquo;2.2.0&rdquo; kernel on a
2.1.0-RELEASE system, many system-status commands like &man.ps.1;
example, an experimental &ldquo;4.0&rdquo; kernel on a
3.1-RELEASE system, many system-status commands like &man.ps.1;
and &man.vmstat.8; will not work any more. You must recompile the
<filename>libkvm</filename> library as well as these utilities.
This is one reason it is not normally a good idea to use a

161
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.14 1999-03-08 22:04:42 nik Exp $
$Id: chapter.sgml,v 1.15 1999-05-16 13:29:08 nik Exp $
-->
<chapter id="kernelconfig">
@ -101,8 +101,10 @@
editor. If you are just starting out, the only editor available will
probably be <command>vi</command>, which is too complex to explain here,
but is covered well in many books in the <link
linkend="bibliography">bibliography</link>. Feel free to change the
comment lines at the top to reflect your configuration or the changes
linkend="bibliography">bibliography</link>. However, FreeBSD does
offer an easier editor called &ldquo;ee&rdquo; which, if you are a
beginner, should be your editor of choise. Feel free to change the
comment lines at the top to reflect your configuration or the changes
you have made to differentiate it from
<filename>GENERIC</filename>.</para>
@ -197,14 +199,17 @@
<listitem>
<para>The first keyword is <literal>machine</literal>, which,
since FreeBSD only runs on Intel 386 and compatible chips, is
i386.</para>
since FreeBSD only runs on Intel 386 (and compatible) chips and
DEC Alpha processors, will be either
<replaceable>i386</replaceable> or
<replaceable>alpha</replaceable>.</para>
<note>
<para>Any keyword which contains numbers used as text must be
enclosed in quotation marks, otherwise
<command>config</command> gets confused and thinks you mean
the actual number 386.</para>
the actual number 386 if you enter
<literal>machine i386</literal>.</para>
</note>
</listitem>
</varlistentry>
@ -216,9 +221,10 @@
<listitem>
<para>The next keyword is <literal>cpu</literal>, which includes
support for each CPU supported by FreeBSD. The possible values
of <replaceable>cpu_type</replaceable> include:</para>
of <replaceable>cpu_type</replaceable> for i386 systems
include:</para>
<itemizedlist>
<listitem>
<para>I386_CPU</para>
</listitem>
@ -234,7 +240,19 @@
<listitem>
<para>I686_CPU</para>
</listitem>
</itemizedlist>
<para>The values availible for <replaceable>cpu_type</replaceable>
for Alpha systems include:</para>
<itemizedlist>
<listitem>
<para>EV4</para>
</listitem>
<listitem>
<para>EV5</para>
</listitem>
</itemizedlist>
<para>Multiple instances of the <literal>cpu</literal> line may be
@ -329,7 +347,7 @@
of the line specifies the disk and partition where the root
filesystem and kernel can be found. Typically this will be
<literal>wd0</literal> for systems with non-SCSI drives, or
<literal>sd0</literal> for systems with SCSI drives.</para>
<literal>da0</literal> for systems with SCSI drives.</para>
</listitem>
</varlistentry>
</variablelist>
@ -443,9 +461,9 @@
workstation from Ethernet. You can include other commonly-used
filesystems in the kernel, but feel free to comment out support for
filesystems you use less often (perhaps the MS-DOS filesystem?), since
they will be dynamically loaded from the Loadable Kernel Module
directory <filename>/lkm</filename> the first time you mount a
partition of that type.</para>
they will be dynamically loaded from the Kernel Module directory
<filename>/modules</filename> the first time you mount a partition
of that type.</para>
<variablelist>
<varlistentry>
@ -809,15 +827,19 @@
<listitem>
<para>NCR 53C810, 53C815, 53C825, 53C860, 53C875 PCI SCSI
controller</para>
<note>
<para>This also supports the Diamond FirePort
controller.</para>
</note>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "SCSI_DELAY=15"</literal></term>
<term><literal>options SCSI_DELAY=15000</literal></term>
<listitem>
<para>This causes the kernel to pause 15 seconds before probing
@ -840,7 +862,7 @@
</varlistentry>
<varlistentry>
<term><literal>device sd0</literal></term>
<term><literal>device da0</literal></term>
<listitem>
<para>Support for SCSI hard drives.</para>
@ -876,7 +898,7 @@
</sect2>
<sect2>
<title>Console, Bus Mouse, and X Server Support</title>
<title>Console, Bus Mouse, Keyboard, and X Server Support</title>
<para>You must choose one of these two console types, and, if you plan
to use the X Window System with the vt220 console, enable the XSERVER
@ -898,7 +920,74 @@
trouble running under this console.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller atkbdc0 at isa? port IO_KBD
tty</literal></term>
<listitem>
<para>The keyboard controller <literal>atkbdc</literal> provides
I/O services for the AT keyboard and PS/2 style pointing
devices. This controller is required by the keyboard driver
<literal>atkbd</literal> and the PS/2 pointing device driver
<literal>psm</literal>.
</para>
<variablelist>
<varlistentry>
<term><literal>options
"KBD_RESETDELAY=<replaceable>X</replaceable>", options
"KBD_MAXWAIT=<replaceable>Y</replaceable>"</literal></term>
<listitem>
<para>The keyboard driver <literal>atkbd</literal> and the
pointing device driver <literal>psm</literal> may ask the
<literal>atkbdc</literal> driver to reset the devices
during the boot process. It sometimes takes a long time
before these devices respond to the reset command. These
options control how long the <literal>atkbdc</literal>
driver should wait before giving up &mdash; the driver
will wait <replaceable>X</replaceable> *
<replaceable>Y</replaceable> milliseconds at most. If the
drivers seem unable to detect devices, you may want to
increase these values. The default values are 200
milliseconds for <replaceable>X</replaceable> and 5 for
<replaceable>Y</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options
"KBDIO_DEBUG=<replaceable>N</replaceable>"</literal></term>
<listitem>
<para>Sets the debug level to <replaceable>N</replaceable>.
The default value is zero, which supresses all debugging
output.</para>
</listitem>
</varlistentry>
</variablelist>
<note>
<para>There can only be one <literal>atkbdc</literal> device
configured into the system.
</para>
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device atkbd0 at isa? tty irq 1</literal></term>
<listitem>
<para>The <literal>atkbd</literal> driver, together with the
<literal>atkbdc</literal> controller, provides access to the
AT 84 keyboard or the AT enhanced keyboard which is connected
to the AT keyboard controller.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device vt0 at isa? port "IO_KBD" tty irq 1 vector
pcrint</literal></term>
@ -937,7 +1026,6 @@
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
@ -1051,14 +1139,24 @@
your particular Ethernet card(s):</para>
<variablelist>
<varlistentry>
<term><literal>device cs0</literal></term>
<listitem>
<para>IBM Etherjet and other Crystal Semi CS89x0-based
adapters.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device de0</literal></term>
<listitem>
<para>Ethernet adapters based on Digital Equipment DC21040,
DC21041 or DC21140 chips</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device fxp0</literal></term>
@ -1429,6 +1527,18 @@
warned (but it does not require a sound card).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0
</literal></term>
<listitem>
<para>The <literal>pcm</literal> driver provides support for
various ISA sound cards that are compatible with the WSS/MSS
specs, or with the Sound Blaster Pro and Sound Blaster
16.</para>
</listitem>
</varlistentry>
</variablelist>
<note>
@ -1457,6 +1567,11 @@
that have been compressed with <command>gzip</command>. The
programs in <filename>/stand</filename> are compressed so it is
a good idea to have this option in your kernel.</para>
<note>
<para>The <literal>gzip</literal> feature currently only works
with a.out binaries.</para>
</note>
</listitem>
</varlistentry>
@ -1652,7 +1767,7 @@ controller wcd0</programlisting>
<screen>config: line 17: syntax error</screen>
you can skip to the problem in <command>vi</command> by typing
<COMMAND>17G</COMMAND> in command mode. Make sure the keyword is
<command>17G</command> in command mode. Make sure the keyword is
typed correctly, by comparing it to the GENERIC kernel or another
reference.</para>
</listitem>
@ -1725,8 +1840,8 @@ controller wcd0</programlisting>
<listitem>
<para>If you have installed a different version of the kernel from
the one that the system utilities have been built with, for
example, an experimental &ldquo;2.2.0&rdquo; kernel on a
2.1.0-RELEASE system, many system-status commands like &man.ps.1;
example, an experimental &ldquo;4.0&rdquo; kernel on a
3.1-RELEASE system, many system-status commands like &man.ps.1;
and &man.vmstat.8; will not work any more. You must recompile the
<filename>libkvm</filename> library as well as these utilities.
This is one reason it is not normally a good idea to use a

161
en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.14 1999-03-08 22:04:42 nik Exp $
$Id: chapter.sgml,v 1.15 1999-05-16 13:29:08 nik Exp $
-->
<chapter id="kernelconfig">
@ -101,8 +101,10 @@
editor. If you are just starting out, the only editor available will
probably be <command>vi</command>, which is too complex to explain here,
but is covered well in many books in the <link
linkend="bibliography">bibliography</link>. Feel free to change the
comment lines at the top to reflect your configuration or the changes
linkend="bibliography">bibliography</link>. However, FreeBSD does
offer an easier editor called &ldquo;ee&rdquo; which, if you are a
beginner, should be your editor of choise. Feel free to change the
comment lines at the top to reflect your configuration or the changes
you have made to differentiate it from
<filename>GENERIC</filename>.</para>
@ -197,14 +199,17 @@
<listitem>
<para>The first keyword is <literal>machine</literal>, which,
since FreeBSD only runs on Intel 386 and compatible chips, is
i386.</para>
since FreeBSD only runs on Intel 386 (and compatible) chips and
DEC Alpha processors, will be either
<replaceable>i386</replaceable> or
<replaceable>alpha</replaceable>.</para>
<note>
<para>Any keyword which contains numbers used as text must be
enclosed in quotation marks, otherwise
<command>config</command> gets confused and thinks you mean
the actual number 386.</para>
the actual number 386 if you enter
<literal>machine i386</literal>.</para>
</note>
</listitem>
</varlistentry>
@ -216,9 +221,10 @@
<listitem>
<para>The next keyword is <literal>cpu</literal>, which includes
support for each CPU supported by FreeBSD. The possible values
of <replaceable>cpu_type</replaceable> include:</para>
of <replaceable>cpu_type</replaceable> for i386 systems
include:</para>
<itemizedlist>
<listitem>
<para>I386_CPU</para>
</listitem>
@ -234,7 +240,19 @@
<listitem>
<para>I686_CPU</para>
</listitem>
</itemizedlist>
<para>The values availible for <replaceable>cpu_type</replaceable>
for Alpha systems include:</para>
<itemizedlist>
<listitem>
<para>EV4</para>
</listitem>
<listitem>
<para>EV5</para>
</listitem>
</itemizedlist>
<para>Multiple instances of the <literal>cpu</literal> line may be
@ -329,7 +347,7 @@
of the line specifies the disk and partition where the root
filesystem and kernel can be found. Typically this will be
<literal>wd0</literal> for systems with non-SCSI drives, or
<literal>sd0</literal> for systems with SCSI drives.</para>
<literal>da0</literal> for systems with SCSI drives.</para>
</listitem>
</varlistentry>
</variablelist>
@ -443,9 +461,9 @@
workstation from Ethernet. You can include other commonly-used
filesystems in the kernel, but feel free to comment out support for
filesystems you use less often (perhaps the MS-DOS filesystem?), since
they will be dynamically loaded from the Loadable Kernel Module
directory <filename>/lkm</filename> the first time you mount a
partition of that type.</para>
they will be dynamically loaded from the Kernel Module directory
<filename>/modules</filename> the first time you mount a partition
of that type.</para>
<variablelist>
<varlistentry>
@ -809,15 +827,19 @@
<listitem>
<para>NCR 53C810, 53C815, 53C825, 53C860, 53C875 PCI SCSI
controller</para>
<note>
<para>This also supports the Diamond FirePort
controller.</para>
</note>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "SCSI_DELAY=15"</literal></term>
<term><literal>options SCSI_DELAY=15000</literal></term>
<listitem>
<para>This causes the kernel to pause 15 seconds before probing
@ -840,7 +862,7 @@
</varlistentry>
<varlistentry>
<term><literal>device sd0</literal></term>
<term><literal>device da0</literal></term>
<listitem>
<para>Support for SCSI hard drives.</para>
@ -876,7 +898,7 @@
</sect2>
<sect2>
<title>Console, Bus Mouse, and X Server Support</title>
<title>Console, Bus Mouse, Keyboard, and X Server Support</title>
<para>You must choose one of these two console types, and, if you plan
to use the X Window System with the vt220 console, enable the XSERVER
@ -898,7 +920,74 @@
trouble running under this console.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller atkbdc0 at isa? port IO_KBD
tty</literal></term>
<listitem>
<para>The keyboard controller <literal>atkbdc</literal> provides
I/O services for the AT keyboard and PS/2 style pointing
devices. This controller is required by the keyboard driver
<literal>atkbd</literal> and the PS/2 pointing device driver
<literal>psm</literal>.
</para>
<variablelist>
<varlistentry>
<term><literal>options
"KBD_RESETDELAY=<replaceable>X</replaceable>", options
"KBD_MAXWAIT=<replaceable>Y</replaceable>"</literal></term>
<listitem>
<para>The keyboard driver <literal>atkbd</literal> and the
pointing device driver <literal>psm</literal> may ask the
<literal>atkbdc</literal> driver to reset the devices
during the boot process. It sometimes takes a long time
before these devices respond to the reset command. These
options control how long the <literal>atkbdc</literal>
driver should wait before giving up &mdash; the driver
will wait <replaceable>X</replaceable> *
<replaceable>Y</replaceable> milliseconds at most. If the
drivers seem unable to detect devices, you may want to
increase these values. The default values are 200
milliseconds for <replaceable>X</replaceable> and 5 for
<replaceable>Y</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options
"KBDIO_DEBUG=<replaceable>N</replaceable>"</literal></term>
<listitem>
<para>Sets the debug level to <replaceable>N</replaceable>.
The default value is zero, which supresses all debugging
output.</para>
</listitem>
</varlistentry>
</variablelist>
<note>
<para>There can only be one <literal>atkbdc</literal> device
configured into the system.
</para>
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device atkbd0 at isa? tty irq 1</literal></term>
<listitem>
<para>The <literal>atkbd</literal> driver, together with the
<literal>atkbdc</literal> controller, provides access to the
AT 84 keyboard or the AT enhanced keyboard which is connected
to the AT keyboard controller.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device vt0 at isa? port "IO_KBD" tty irq 1 vector
pcrint</literal></term>
@ -937,7 +1026,6 @@
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
@ -1051,14 +1139,24 @@
your particular Ethernet card(s):</para>
<variablelist>
<varlistentry>
<term><literal>device cs0</literal></term>
<listitem>
<para>IBM Etherjet and other Crystal Semi CS89x0-based
adapters.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device de0</literal></term>
<listitem>
<para>Ethernet adapters based on Digital Equipment DC21040,
DC21041 or DC21140 chips</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device fxp0</literal></term>
@ -1429,6 +1527,18 @@
warned (but it does not require a sound card).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0
</literal></term>
<listitem>
<para>The <literal>pcm</literal> driver provides support for
various ISA sound cards that are compatible with the WSS/MSS
specs, or with the Sound Blaster Pro and Sound Blaster
16.</para>
</listitem>
</varlistentry>
</variablelist>
<note>
@ -1457,6 +1567,11 @@
that have been compressed with <command>gzip</command>. The
programs in <filename>/stand</filename> are compressed so it is
a good idea to have this option in your kernel.</para>
<note>
<para>The <literal>gzip</literal> feature currently only works
with a.out binaries.</para>
</note>
</listitem>
</varlistentry>
@ -1652,7 +1767,7 @@ controller wcd0</programlisting>
<screen>config: line 17: syntax error</screen>
you can skip to the problem in <command>vi</command> by typing
<COMMAND>17G</COMMAND> in command mode. Make sure the keyword is
<command>17G</command> in command mode. Make sure the keyword is
typed correctly, by comparing it to the GENERIC kernel or another
reference.</para>
</listitem>
@ -1725,8 +1840,8 @@ controller wcd0</programlisting>
<listitem>
<para>If you have installed a different version of the kernel from
the one that the system utilities have been built with, for
example, an experimental &ldquo;2.2.0&rdquo; kernel on a
2.1.0-RELEASE system, many system-status commands like &man.ps.1;
example, an experimental &ldquo;4.0&rdquo; kernel on a
3.1-RELEASE system, many system-status commands like &man.ps.1;
and &man.vmstat.8; will not work any more. You must recompile the
<filename>libkvm</filename> library as well as these utilities.
This is one reason it is not normally a good idea to use a