From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 12 00:42:59 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C852B16A41F for ; Fri, 12 Aug 2005 00:42:59 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 948FD43D53 for ; Fri, 12 Aug 2005 00:42:58 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j7C0gtum016717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 11 Aug 2005 17:42:55 -0700 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.8/Submit) id j7C0gs5h016714 for freebsd-hackers@freebsd.org; Thu, 11 Aug 2005 17:42:54 -0700 Date: Thu, 11 Aug 2005 17:42:54 -0700 From: "Loren M. Lang" To: FreeBSD Hackers Message-ID: <20050812004254.GA16614@alzatex.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C Subject: PXE Boot FreeBSD with Etherboot 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: Fri, 12 Aug 2005 00:42:59 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It seems there are some problems with using pxeboot in combination with the network boot code from the etherboot project. I have tried many combinations of options with no success. The result is very similar to the following photo I found: http://photos.night-shade.org.uk/photo.php?photo=3D6364 I have tried it both on my local machine and in vmware with the same result. It seems that somehow etherboot is not setting up the environment the way pxeboot expects it too. Now the native pxe boot code in vmware does load pxeboot correctly and I have successfully booted freebsd in vmware, however I can't get the pxe boot code on my network card to load at all, hence my need for etherboot. Also, both pxeboot from FreeBSD 4.11 and 6.0-BETA2 crash the same way. I'm assuming this is really a bug in etherboot, but I'm not sure how to get a crash dump to play with. With vmware, it seems like I should be able to save a memory image to examine, but I'm not sure how to do that. Any ideas on a fix for this? --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 =20 --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFC+/CObTXoRwEYo9IRAjQRAJ9bdPH1h1Zr6oOFZ4Z37R4dsLzaoQCfbMuE K+PLvJuq8SinEVZ7mHaBIcs= =JoT9 -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ--