[EMAIL PROTECTED] 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 abou
Reko Turja wrote:
- Original Message - From: "Chris Maness" <[EMAIL PROTECTED]>
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
afte
- Original Message -
From: "Chris Maness" <[EMAIL PROTECTED]>
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 release
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 lin
I am assuming you do not have a serial console but yes check out 'man
loader.conf'.
I did not remember but got it pretty quickly by search 'boot+verbose'. The
handbook is really pretty good these days. That said I have never tried the
loader.conf option.
On Mon, 5 Jun 2006, Chris Maness wrot
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 tha
Is /var/run/dmesg.boot populated correctly?
Yes
What kinds of things are in the -a output?
named error messages mostly (this is a name server)
Same results booting with or without network attached?
Haven't tried, but there are no messages displayed by dmesg (without a
flag) at the time
(a
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.lo
Chris Maness wrote:
Interesting. Does "dmesg -a" show anything different?
Yes, it does, but why would it not show anything without the flag right
after a reboot? Wierd. I almost suspect hard drive issues.
OK, THAT does not seem normal. Sorry, didn't catch that detail at first.
Right afte
On Mon, 5 Jun 2006, Lowell Gilbert wrote:
Greg Barniskis <[EMAIL PROTECTED]> writes:
Chris Maness wrote:
On Mon, 5 Jun 2006, Greg Barniskis wrote:
Chris Maness wrote:
I just installed 6.1 and upgraded to RELEASE-p1. The command
dmesg is not displaying any kernel messages, any suggesti
Lowell Gilbert wrote:
Greg Barniskis <[EMAIL PROTECTED]> writes:
Chris Maness wrote:
On Mon, 5 Jun 2006, Greg Barniskis wrote:
Chris Maness wrote:
I just installed 6.1 and upgraded to RELEASE-p1. The command
dmesg is not displaying any kernel messages, any suggestions?
Suggests all is w
On Monday 05 June 2006 19:08, Greg Barniskis wrote:
> Not new behavior. A dmesg on any of my running systems (4.x, 5.x)
> returns nothing after a time. You were just catching it before the
> buffer was flushed. I don't know what triggers that, and it is
> possible that the trigger/timing of it may
Greg Barniskis <[EMAIL PROTECTED]> writes:
> Chris Maness wrote:
>>
>>
>> On Mon, 5 Jun 2006, Greg Barniskis wrote:
>>
>>> Chris Maness wrote:
I just installed 6.1 and upgraded to RELEASE-p1. The command
dmesg is not displaying any kernel messages, any suggestions?
>>>
>>> Suggests all
Chris Maness wrote:
On Mon, 5 Jun 2006, Greg Barniskis wrote:
Chris Maness wrote:
I just installed 6.1 and upgraded to RELEASE-p1. The command dmesg
is not displaying any kernel messages, any suggestions?
Suggests all is well?
dmesg outputs stuff from the current system message buffer,
On Mon, 5 Jun 2006, Greg Barniskis wrote:
Chris Maness wrote:
I just installed 6.1 and upgraded to RELEASE-p1. The command dmesg is not
displaying any kernel messages, any suggestions?
Suggests all is well?
dmesg outputs stuff from the current system message buffer, which contains
your
Chris Maness wrote:
I just installed 6.1 and upgraded to RELEASE-p1. The command dmesg is
not displaying any kernel messages, any suggestions?
Suggests all is well?
dmesg outputs stuff from the current system message buffer, which
contains your boot messages right after booting but those c
I just installed 6.1 and upgraded to RELEASE-p1. The command dmesg is
not displaying any kernel messages, any suggestions? I am running a
SCSI hard drive on this box too.
Here is a snipit from the message log in case these issues have anything
to do with it.
Timecounter "TSC" frequency 66
17 matches
Mail list logo
