RE: dmesg(.boot) has no useful boot messages

From: fbsd_user (fbsd_user_at_a1poweruser.com)
Date: 07/14/03

  • Next message: lewiz: "GNOME/CUPS printing." 
    To: "Gary W. Swearingen" <underway@comcast.net>, <freebsd-questions@freebsd.org>
Date: Mon, 14 Jul 2003 12:54:33 -0400

    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@freebsd.org
    [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Gary W.
    Swearingen
    Sent: Monday, July 14, 2003 12:08 AM
    To: freebsd-questions@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@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to
    "freebsd-questions-unsubscribe@freebsd.org"

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

  • Next message: lewiz: "GNOME/CUPS printing."

    Relevant Pages

    • Re: Why cant I scroll when in a cmd.exe window, but can with a command.exe window?
      ... Wrong buffer, you want screen buffer not command history buffer. ... Layout tab. ... If I click in the top left of the cmd.exe window and go ... my "Scroll" menu option there is grayed out as well. ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: capturing terminal scrollback buffer?
      ... problem that I want to save, but its just sitting in the scroll back ... buffer of an aterm. ... When you are running your terminal sessions under gnu/screen and you ... such as advanced copying & pasting between terminal sessions and ...
      (Debian-User)
    • mdacon and scroll buffer
      ... This is the only mail list I could find that discussed mdacon. ... Mdacon appears to have no Scroll_Backward or _Forward feature (scroll ... buffer) like vgacon does (shift Page Up or shift Page Down). ...
      (Linux-Kernel)
    • Re: capturing terminal scrollback buffer?
      ... i've got about 1000 lines of debug stuff from a network ... problem that I want to save, but its just sitting in the scroll back ... buffer of an aterm. ... lines of scroll back using the two click method (I didn't realise the ...
      (Debian-User)
    • Re: Xdefaults and Xresources not working
      ... Are you expecting to be able to scroll ... back in a freshly-opened xterm where you haven't even typed any commands ... Each window has its own private buffer, ... login shell, or "-bash" if it's a login shell. ...
      (comp.sys.mac.apps)