From owner-freebsd-current Wed Oct 2 4:56:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DB3737B401; Wed, 2 Oct 2002 04:56:34 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (fump.kawo2.RWTH-Aachen.DE [134.130.181.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5148D43E65; Wed, 2 Oct 2002 04:56:33 -0700 (PDT) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (localhost [127.0.0.1]) by fump.kawo2.rwth-aachen.de (8.12.5/8.12.5) with ESMTP id g92BmKu6091816; Wed, 2 Oct 2002 13:48:20 +0200 (CEST) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.12.5/8.12.5/Submit) id g92BmKba091815; Wed, 2 Oct 2002 13:48:20 +0200 (CEST) Date: Wed, 2 Oct 2002 13:48:20 +0200 From: Alexander Langer To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: kernel boot messages absent Message-ID: <20021002114820.GD90861@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , John Baldwin , current@FreeBSD.ORG References: <20021002002620.GJ85009@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Fingerprint: 7EC1 5B98 4554 2A63 9079 2B2F 9A94 CD6F 7F14 EFA4 X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake John Baldwin (jhb@FreeBSD.ORG): > > Can anyone explain me why with a recent kernel (last kernel was from > > 1 year ago) the kernel boot messages disappear from the monitor > > once the "propellor" of the kernel boot has done like 5 rounds > > (last message is the last line of the > > "Booting kernel in X seconds" line, followed by a single "-" on > > the line, which used to be the propellor) > You need to setup a /boot/device.hints file if you haven't already so > that the kernel can configure it's console device. Nah, that machine already had a device.hints installed. And also with an upgraded device.hints (GENERIC.hints copied from /sys/i386/conf) the same problem occurs. And I don't think I'd have to edit device.hints on common hardware, using a GENERIC kernel, do I? It used to work before :-( Any more tips? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message