Date: Mon, 05 Jun 2006 18:42:14 -0700 From: Chris Maness <chris@chrismaness.com> To: doug@fledge.watson.org Cc: questions@freebsd.org Subject: Re: dmesg not working on new system Message-ID: <4484DD76.7050206@chrismaness.com> In-Reply-To: <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> <20060605205202.H85348@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4484DD76.7050206>