From owner-freebsd-questions@FreeBSD.ORG Mon Oct 4 06:58:02 2004 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 C713C16A4CE for ; Mon, 4 Oct 2004 06:58:02 +0000 (GMT) Received: from clueful.shagged.org (clueful.shagged.org [212.13.201.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 912EC43D31 for ; Mon, 4 Oct 2004 06:58:02 +0000 (GMT) (envelope-from chris@clueful.shagged.org) Received: from chris by clueful.shagged.org with local (Exim 4.40 (FreeBSD)) id 1CEMnG-000Fky-0k for freebsd-questions@freebsd.org; Mon, 04 Oct 2004 07:57:58 +0100 Date: Mon, 4 Oct 2004 07:57:57 +0100 From: Chris Elsworth To: freebsd-questions@freebsd.org Message-ID: <20041004065757.GA60253@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-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:58:02 -0000 Hello, I did post this to -current a few days ago, but having got no response, perhaps here is a better place for it. I've also noted a few previous attempts to get an answer to this question on freebsd-questions in January and February, but nobody replied. This doesn't seem to be an isolated case.. 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, no messages. Setting boot_verbose didn't change anything. I'm not sure what else to try. Does anyone have any ideas? Cheers, -- Chris