Date: Mon, 05 Jun 2006 14:34:27 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Greg Barniskis <nalists@scls.lib.wi.us> Cc: Chris Maness <chris@chrismaness.com>, freebsd-questions@freebsd.org Subject: Re: dmesg not working on new system Message-ID: <448xobpi30.fsf@be-well.ilk.org> In-Reply-To: <44847336.9050908@scls.lib.wi.us> (Greg Barniskis's message of "Mon, 05 Jun 2006 13:08:54 -0500") References: <44843B61.5050209@chrismaness.com> <448469D5.8060700@scls.lib.wi.us> <20060605105358.Q54670@ns1.internetinsite.com> <44847336.9050908@scls.lib.wi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Barniskis <nalists@scls.lib.wi.us> writes: > Chris Maness wrote: >> >> >> 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 >>> > >> >> 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? > > Not new behavior. A dmesg on any of my running systems (4.x, 5.x) > returns nothing after a time. You were just catching it before the > buffer was flushed. I don't know what triggers that, and it is > possible that the trigger/timing of it may have changed in 6.x (and as > always, YMMV). Interesting. Does "dmesg -a" show anything different?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448xobpi30.fsf>