dmesg(.boot) has no useful boot messages

[fbsd_user]

If you all talking about the scroll lock history to capture all of
the boot messages.
You have to increase the buffer size beyond the default value of the
kernel option SC_HISTORY_SIZE.

adding  'options SC_HISTORY_SIZE=1000'  to the kernel source and
recompile, will capture the first 1000 lines of the boot messages.

Note this option reserves real memory which can not be used for
anything else. The last 1000 lines displayed on the console is all
ways scrollable by hitting the 'scroll lock keyboard key' followed
by the up arrow key to scroll through the buffer.




-----Original Message-----
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Gary W.
Swearingen
Sent: Monday, July 14, 2003 12:08 AM
To: freebsd-questions at freebsd.org
Subject: dmesg(.boot) has no useful boot messages

I've just switched from 4.8 to 5.1-CURRENT and all the dmesg files
are full of stuff that I've never seen before, like this:

6 start_16_io RW *Handler
    307 start_32_io RW *Handler
    308 debug RW *Handler
  309 pci R  Node
    310 enable_io_modes RW *Handler Int
    311 allow_unsupported_io_range R  *Handler Int
  327 usb RW Node
  328 wi R  Node
    329 txerate RW *Handler Int
    330 debug RW *Handler Int

which would be OK, except that all the more useful messages seem to
get scrolled off the end of the dmesg buffer so if you can't read
the
boot messages while they're flashing by on the boot console your out
of luck.  I see nothing about it in UPDATING or the handbook.

How do I turn off the more useless debugging boot messages or make
the
dmesg buffer larger?

Thanks.
_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"