From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 22 03:37:04 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F9EC16A417 for ; Sat, 22 Dec 2007 03:37:04 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id CCB8A13C44B for ; Sat, 22 Dec 2007 03:37:03 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 22919 invoked from network); 22 Dec 2007 03:37:03 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 22 Dec 2007 03:37:02 -0000 Message-ID: <476C85A0.7050402@chuckr.org> Date: Fri, 21 Dec 2007 22:33:52 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: ticso@cicely.de References: <476AF132.4080304@chuckr.org> <20071221074556.GA69673@cicely12.cicely.de> In-Reply-To: <20071221074556.GA69673@cicely12.cicely.de> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 22 Dec 2007 04:27:53 +0000 Cc: FreeBSD-Hackers Subject: Re: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2007 03:37:04 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bernd Walter wrote: > On Thu, Dec 20, 2007 at 05:48:18PM -0500, Chuck Robey wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I've lost the printing of all of th e messages you normally see, when you are >> booting yoiur machine (you know, mostly probe messages. I used to see them on >> this box. When I made my first kernel, I had begun (obviously, as we all do) >> with GENERIC as a base, but changing the first loaders.hints and the kernel, >> that's the last I saw of booting messages. >> >> To illustrate what I *do* see, I watch the first character of that little >> spiller, but only the very first char, because that's when it stops working, >> right after sicking the first char. Thbe nest thing I see, maybe 30 seconds >> later, is a Login: request. > > Sounds like your console is configured to a different device. > Maybe it is configured to serial while you are waiting on vga. > >> Any notion what I could do to get my booting messages back? > > Switch the console to the device you are looking at. > You can easily check the configured console by running conscontrol. > Maybe you've lost the device hint for your console device to flag > it as beeing a possible console candidate. OK, when I run conscontrol, it tells me I am using the dcons console. I looked at the man page for concontrol (and I've been gone from FreeBSD so long, I wasn't even awaare of conscontrol at all) and it informed me I am using the dcons device. I am not aware of any others, I was hoping that if there were such, there would be references to them in either the dcons or conscontrol man pages, but no lock. Is dcons good enough? You understand I would be ecstatic if it wasn't 9and if I could set it to something else, and thereby get my booting messages back.) I checked my kernel config file, it does indeed list the dcons device. Have any other ideas, I'm really listening here. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHbIWgz62J6PPcoOkRAigoAJ99PTNEEeK8LsBEXAtQS8Sc4tan2ACdESgM oBKqPU4TripnypwtKckxt6A= =r7GD -----END PGP SIGNATURE-----