From owner-freebsd-small@FreeBSD.ORG Tue May 23 10:40:33 2006 Return-Path: X-Original-To: freebsd-small@freebsd.org Delivered-To: freebsd-small@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 574FE16A42A for ; Tue, 23 May 2006 10:40:33 +0000 (UTC) (envelope-from ask@develooper.com) Received: from x8.develooper.com (x8.develooper.com [216.52.237.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0058443D45 for ; Tue, 23 May 2006 10:40:30 +0000 (GMT) (envelope-from ask@develooper.com) Received: (qmail 8341 invoked from network); 23 May 2006 10:40:30 -0000 Received: from gw.develooper.com (HELO ?10.0.201.111?) (ask@cleverpeople.org@64.81.84.140) by smtp.develooper.com with (RC4-SHA encrypted) SMTP; 23 May 2006 10:40:30 -0000 Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: <8AB6703D-3BAB-4C2A-988D-6CC25A31C2EF@develooper.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-small@freebsd.org From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= Date: Tue, 23 May 2006 03:40:27 -0700 X-Mailer: Apple Mail (2.750) Subject: pxeboot PC Engines WRAP X-BeenThere: freebsd-small@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 10:40:39 -0000 Hi everyone, I'm having trouble pxeboot'ing a PC Engines WRAP board. After changing the tftp server to one that supports blksize, pxeboot loads okay, but doesn't get very far: PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader Consoles: serial port BIOS drive C: is disk0 PXE version 2.1, real mode entry point @9a80:0680 [and it hangs ....] I was using an older pxeboot before which stopped after "Building the boot loader arguments". Any ideas? The wrap board is using Etherboot 5.3.12. I tried making that Etherboot load a newer Etherboot (5.4.2)[1], but it has the same problem. I've been told that it should be able to work if I load the kernel (a kernel with the appropriate BOOTP options), but I'd much rather use pxeboot so I can use the same kernel I'll use when the system has been transferred to a compact flash. - ask [1] the dhcpd.conf snippet to have Etherboot load a newer Etherboot is as follows. It took me a while to figure out that the etherboot VCI includes the version number. if substring (option vendor-class-identifier, 0, 13) = "Etherboot-5.4" { filename "tftp://10.0.201.50/pxeboot"; next-server 10.0.201.50; option root-path "10.0.201.50:/usr/netboot/foo"; } else { next-server 10.0.201.40; filename "eb-5.4.2-natsemi.zpxe-nfs"; } -- http://askask.com/ - http://develooper.com/