From owner-freebsd-current@FreeBSD.ORG Sat Oct 2 22:27:16 2004 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 2E3FC16A4CE for ; Sat, 2 Oct 2004 22:27:16 +0000 (GMT) Received: from clueful.shagged.org (clueful.shagged.org [212.13.201.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED62D43D39 for ; Sat, 2 Oct 2004 22:27:15 +0000 (GMT) (envelope-from chris@clueful.shagged.org) Received: from chris by clueful.shagged.org with local (Exim 4.40 (FreeBSD)) id 1CDsLN-000HAm-7V for current@freebsd.org; Sat, 02 Oct 2004 23:27:09 +0100 Date: Sat, 2 Oct 2004 23:27:09 +0100 From: Chris Elsworth To: current@freebsd.org Message-ID: <20041002222709.GA65629@shagged.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Sender: Chris Elsworth X-Shagged-MailScanner-Information: See www.mailscanner.info for information X-Shagged-MailScanner: Found to be clean X-MailScanner-From: chris@clueful.shagged.org Subject: PXE booting 5.3-BETA6 kernel message issues 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: Sat, 02 Oct 2004 22:27:16 -0000 Hello, I hope someone here has an idea what's going on here - I've been trying to get 5.3-BETA6 PXE booting; I don't want anything special at the moment, just an NFS mounted root with tools available to perform disaster recovery etc. I've got the kernel transferred via TFTP and an mfsroot. If I use the mfsroot.flp from a release I eventually see sysinstall pop up, so it looks like everything is working, with one exception - the last message I see before sysinstall appears is the acpi.ko loading notification. Where are all the kernel messages going? It makes it quite difficult to construct my own mfsroot that just gives me a prompt when I can't see what's going on :) I've verified that the console is set to vidconsole in the loader; I tried comconsole and attaching a serial console also, same result. Setting boot_verbose didn't change anything. I'm not sure what else to try. Does anyone have any ideas? Cheers, -- Chris