From owner-freebsd-current@FreeBSD.ORG Tue May 20 14:31:15 2003 Return-Path: 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 06ECE37B401 for ; Tue, 20 May 2003 14:31:15 -0700 (PDT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EDC643FAF for ; Tue, 20 May 2003 14:31:13 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: from bremen.shuttle.de (localhost [127.0.0.1]) by bremen.shuttle.de (Postfix) with ESMTP id 6C0C818A08; Tue, 20 May 2003 23:03:13 +0200 (CEST) Received: (from uucp@localhost)h4KL3Cn2018776; Tue, 20 May 2003 23:03:12 +0200 Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.12.9/8.12.9) id h4KL3ENk004092; Tue, 20 May 2003 23:03:14 +0200 (CEST) (envelope-from schweikh) Date: Tue, 20 May 2003 23:03:14 +0200 From: Jens Schweikhardt To: Michael Nottebrock Message-ID: <20030520210314.GA3521@schweikhardt.net> References: <20030520152026.P4097@gong> <200305201539.49550.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305201539.49550.michaelnottebrock@gmx.net> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: No output from kernel during boot ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2003 21:31:15 -0000 On Tue, May 20, 2003 at 03:39:46PM +0200, Michael Nottebrock wrote: Content-Description: signed data # On Tuesday 20 May 2003 15:23, freebsd@lislegaard.net wrote: # > Probably a stupid question, but I can't see why this happens. The # > system is a recent build of Current. # > # > At boot I see the loader messages, but when the kernel starts there is # > no more output to the console before I get the login prompt. I've seen this, too. It appears in my case it had to do with my disabling of ACPI for test purposes. Now I run a recent -current, no messing with ACPI in loader.conf and everything is fine again. # Do you have console="comconsole" set in /boot/loader.conf, by chance? In my case, no. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)