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

- Fix the tail tag.

Browse source 
- On occasion, the data from dmesg will only show system messages instead
  of the boot probe output. In these situations, the output may be obtained
  by viewing the /var/run/dmesg.boot instead of
  /var/log/dmesg.{today,yesterday} in case it was not today or yesterday.
This commit is contained in:
Chin-San Huang 2008-01-27 04:23:28 +00:00
parent 88eb7ce95f
commit 9073a61f4b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=31374
1 changed files with 2 additions and 3 deletions

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

@ -170,13 +170,12 @@ psm0: [ITHREAD]
psm0: model Generic PS/2 mouse, device ID 0</programlisting>
<para>This driver will need to be included in the custom kernel
configuration file or loaded using &man.loader.conf.5;.<para>
configuration file or loaded using &man.loader.conf.5;.</para>
<para>On occasion, the data from <command>dmesg</command> will
only show system messages instead of the boot probe output. In
these situations, the output may be obtained by viewing the
<filename>/var/log/dmesg.today</filename> and
<filename>/var/log/dmesg.yesterday</filename> files.</para>
<filename>/var/run/dmesg.boot</filename> file.</para>
<para>Another method of finding hardware is by using the
&man.pciconf.8; utility which provides more verbose output.