From owner-freebsd-questions@FreeBSD.ORG Tue Jun 6 01:26:21 2006 Return-Path: X-Original-To: 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 1BBAD16D54A for ; Tue, 6 Jun 2006 00:53:39 +0000 (UTC) (envelope-from doug@safeport.com) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A63643D48 for ; Tue, 6 Jun 2006 00:53:37 +0000 (GMT) (envelope-from doug@safeport.com) 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 k560rYpv085983; Mon, 5 Jun 2006 20:53:34 -0400 (EDT) (envelope-from doug@safeport.com) Received: from localhost (doug@localhost) by fledge.watson.org (8.13.4/8.13.4/Submit) with ESMTP id k560rXSf085980; Mon, 5 Jun 2006 20:53:34 -0400 (EDT) (envelope-from doug@safeport.com) X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs Date: Mon, 5 Jun 2006 20:53:33 -0400 (EDT) From: doug@safeport.com X-X-Sender: doug@fledge.watson.org To: Chris Maness In-Reply-To: <20060605173024.Q56395@ns1.internetinsite.com> Message-ID: <20060605205202.H85348@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> <20060605193741.N62495@fledge.watson.org> <20060605173024.Q56395@ns1.internetinsite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: 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 Reply-To: doug@fledge.watson.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2006 01:26:28 -0000 Belay my last response about loader.conf. I did not read that what does closely enough. Without a serial console, turning all all.log is the best I know how to do On Mon, 5 Jun 2006, Chris Maness wrote: > > > On Mon, 5 Jun 2006, doug wrote: > >> 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. >> > > There are no deltas between the two files and there originals from the source > tree. I administer this box via remote shell (ssh). Is there a way to boot > in verbose mode via a remote connection? >