From owner-freebsd-questions@FreeBSD.ORG Mon Jul 14 09:54:35 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5BEB37B401 for ; Mon, 14 Jul 2003 09:54:35 -0700 (PDT) Received: from mta1.adelphia.net (mta1.adelphia.net [64.8.50.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBDAF43F75 for ; Mon, 14 Jul 2003 09:54:34 -0700 (PDT) (envelope-from fbsd_user@a1poweruser.com) Received: from barbish ([68.169.105.49]) by mta1.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with SMTP id <20030714165943.RGUU25556.mta1.adelphia.net@barbish>; Mon, 14 Jul 2003 12:59:43 -0400 From: "fbsd_user" To: "Gary W. Swearingen" , Date: Mon, 14 Jul 2003 12:54:33 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <0tel0tagy4.l0t@mail.comcast.net> Subject: RE: dmesg(.boot) has no useful boot messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: fbsd_user@a1poweruser.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 16:54:36 -0000 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"