From owner-freebsd-questions@FreeBSD.ORG Tue Jun 6 02:24:00 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 EB43916ADAC for ; Tue, 6 Jun 2006 01:42:24 +0000 (UTC) (envelope-from chris@chrismaness.com) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id D510743D69 for ; Tue, 6 Jun 2006 01:42:19 +0000 (GMT) (envelope-from chris@chrismaness.com) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm29.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k561fJVw007428 for ; Mon, 5 Jun 2006 21:41:19 -0400 X-ORBL: [69.238.213.227] Received: from [192.168.4.2] (ppp-69-238-213-227.dsl.irvnca.pacbell.net [69.238.213.227]) by pimout5-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k561gFck144372; Mon, 5 Jun 2006 21:42:18 -0400 Message-ID: <4484DD76.7050206@chrismaness.com> Date: Mon, 05 Jun 2006 18:42:14 -0700 From: Chris Maness User-Agent: Thunderbird 1.5.0.2 (X11/20060425) MIME-Version: 1.0 To: doug@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> <20060605205202.H85348@fledge.watson.org> In-Reply-To: <20060605205202.H85348@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2006 02:24:00 -0000 doug@safeport.com wrote: > 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: > Looks like another reader had the same issue. I feel better about it now. I thought maybe something was corrupt or mis configured.