Date: Mon, 5 Jun 2006 20:53:33 -0400 (EDT) From: doug@safeport.com To: Chris Maness <chris@chrismaness.com> Cc: questions@freebsd.org Subject: Re: dmesg not working on new system Message-ID: <20060605205202.H85348@fledge.watson.org> In-Reply-To: <20060605173024.Q56395@ns1.internetinsite.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060605205202.H85348>