Since the output of dmesg(8) is not guaranteed to contain the boot messages,
suggest users check var/run/dmesg.boot when they need information about their devices, etc. Suggested by: Pierre-Paul Lavoie <ppl@nbnet.nb.ca> PR: docs/45981 Reviewed by: keramida, mheinen
This commit is contained in:
parent
4303099df7
commit
2c70db6304
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=15731
4 changed files with 7 additions and 7 deletions
|
@ -6197,7 +6197,7 @@ BUSY</literallayout></entry>
|
|||
<para>Confirm that both computers have a kernel with &man.lpt.4; driver
|
||||
support.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dmesg | grep lp</userinput>
|
||||
<screen>&prompt.root; <userinput>grep lp /var/run/dmesg.boot</userinput>
|
||||
lpt0 at 0x378-0x37f irq 7 on isa
|
||||
lpt0: Interrupt-driven
|
||||
lp0: TCP/IP capable interface</screen>
|
||||
|
|
|
@ -487,7 +487,7 @@ cpu I686_CPU</programlisting>
|
|||
sure whether you should use <literal>I586_CPU</literal> or
|
||||
<literal>I686_CPU</literal>), however, for a custom kernel, it is
|
||||
best to specify only the CPU you have. If you are unsure of your
|
||||
CPU type, you can use the &man.dmesg.8; command to view your boot
|
||||
CPU type, you can check the <filename>/var/run/dmesg.boot</filename> file to view your boot
|
||||
up messages.</para>
|
||||
|
||||
<note><para>In FreeBSD 5.0, support for <literal>I386_CPU</literal>
|
||||
|
|
|
@ -291,10 +291,10 @@ device csa</programlisting>
|
|||
<title>Creating and Testing the Device Nodes</title>
|
||||
|
||||
<indexterm><primary>device nodes</primary></indexterm>
|
||||
<para>After you reboot, log in and run <command>dmesg | grep
|
||||
pcm</command> as shown below:</para>
|
||||
<para>After you reboot, log in and check for the device in the
|
||||
<filename>/var/run/dmesg.boot</filename> file, as shown below:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dmesg | grep pcm</userinput>
|
||||
<screen>&prompt.root; <userinput>grep pcm /var/run/dmesg.boot</userinput>
|
||||
pcm0: <SB16 DSP 4.11> on sbc0</screen>
|
||||
|
||||
<para>The output from your system may look different. If no
|
||||
|
|
|
@ -469,7 +469,7 @@
|
|||
<para>To find out if the kernel you are currently using supports
|
||||
a serial interface, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dmesg | grep sio<replaceable>N</replaceable></userinput></screen>
|
||||
<screen>&prompt.root; <userinput>grep sio<replaceable>N</replaceable> /var/run/dmesg.boot</userinput></screen>
|
||||
|
||||
<para>Where <replaceable>N</replaceable> is the number of the
|
||||
serial port, starting from zero. If you see output similar to
|
||||
|
@ -483,7 +483,7 @@ sio2: type 16550A</screen>
|
|||
<para>To find out if the kernel supports a parallel interface,
|
||||
type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dmesg | grep ppc<replaceable>N</replaceable></userinput></screen>
|
||||
<screen>&prompt.root; <userinput>grep ppc<replaceable>N</replaceable> /var/run/dmesg.boot</userinput></screen>
|
||||
|
||||
<para>Where <replaceable>N</replaceable> is the number of the
|
||||
parallel port, starting from zero. If you see output similar
|
||||
|
|
Loading…
Reference in a new issue