Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Jun 2006 02:16:11 +0300
From:      "Reko Turja" <reko.turja@liukuma.net>
To:        "Chris Maness" <chris@chrismaness.com>, <freebsd-questions@freebsd.org>
Subject:   Re: dmesg not working on new system
Message-ID:  <023401c688f6$090458d0$0a0aa8c0@rivendell>
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>

next in thread | previous in thread | raw e-mail | index | archive | help

----- Original Message ----- 
From: "Chris Maness" <chris@chrismaness.com>

> Yes, it does, but why would it not show anything without the flag 
> right after a reboot?  Wierd.  I almost suspect hard drive issues.

I got the exactly same happen to me with 6.1-RELEASE updated just after 
6.1 was released. Didn't think about the weirdness really until now 
seeing your messages. The symptoms were exactly the same, /var/dmesg 
file was empty right after the boot and of course dmesg command didn't 
print the booting messages either.

Things seems to be normalized for me with 6.1-STABLE from yesterday, but 
haven't booted since buildworld process after which I got proper dmesg 
output.

-Reko 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?023401c688f6$090458d0$0a0aa8c0>