Date: Mon, 5 Jun 2006 10:55:32 -0700 (PDT) From: Chris Maness <chris@chrismaness.com> To: Greg Barniskis <nalists@scls.lib.wi.us> Cc: freebsd-questions@freebsd.org Subject: Re: dmesg not working on new system Message-ID: <20060605105358.Q54670@ns1.internetinsite.com> In-Reply-To: <448469D5.8060700@scls.lib.wi.us> References: <44843B61.5050209@chrismaness.com> <448469D5.8060700@scls.lib.wi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Jun 2006, Greg Barniskis wrote: > Chris Maness wrote: >> I just installed 6.1 and upgraded to RELEASE-p1. The command dmesg is not >> displaying any kernel messages, any suggestions? > > Suggests all is well? > > dmesg outputs stuff from the current system message buffer, which contains > your boot messages right after booting but those can get flushed over time. > Boot messages are saved to a file though, for reference. > > more /var/run/dmesg.boot > > > -- > Greg Barniskis, Computer Systems Integrator > South Central Library System (SCLS) > Library Interchange Network (LINK) > <gregb at scls.lib.wi.us>, (608) 266-6348 > I just thought it was strange because every other system I have it at least displays dmesg.boot if there is no other messages. Is this new behavior for 6.1?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060605105358.Q54670>