From owner-freebsd-questions@FreeBSD.ORG Tue Jun 6 00:44:14 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38A7E16C52A for ; Mon, 5 Jun 2006 23:45:49 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57A6C43D45 for ; Mon, 5 Jun 2006 23:45:47 +0000 (GMT) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.13.4/8.13.4) with ESMTP id k55Njfho082378; Mon, 5 Jun 2006 19:45:41 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.13.4/8.13.4/Submit) with ESMTP id k55NjZgX082368; Mon, 5 Jun 2006 19:45:36 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Mon, 5 Jun 2006 19:45:35 -0400 (EDT) From: doug To: Chris Maness In-Reply-To: <20060605145453.S55741@ns1.internetinsite.com> Message-ID: <20060605193741.N62495@fledge.watson.org> References: <44843B61.5050209@chrismaness.com> <448469D5.8060700@scls.lib.wi.us> <20060605105358.Q54670@ns1.internetinsite.com> <44847336.9050908@scls.lib.wi.us> <448xobpi30.fsf@be-well.ilk.org> <20060605145453.S55741@ns1.internetinsite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Greg Barniskis , freebsd-questions@freebsd.org Subject: Re: dmesg not working on new system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2006 00:44:24 -0000 A couple of things you can try: turn on the all.log line in syslog.conf; and, mkae sure syslog.conf and newsyslog.conf match the source tree. If all that looks okay, do a boot verbose (I forget the syntax). If you are getting any warning or status messages that could cause this either the all.log or the boot should show them. On Mon, 5 Jun 2006, Chris Maness wrote: > > > On Mon, 5 Jun 2006, Lowell Gilbert wrote: > >> Greg Barniskis 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? >> > Yes, it does, but why would it not show anything without the flag right after > a reboot? Wierd. I almost suspect hard drive issues. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >