Re: pxeboot PC Engines WRAP

Hello.

After having a lot of trouble with FreeBSD's pxeboot I found that a 
two-stage solution works for me. I first boot an etherboot image
via pxe and from there directly load the FreeBSD kernel.

This is my dhcpd.conf:

subnet 10.47.11.0 netmask 255.255.255.0 {
   range dynamic-bootp 10.47.11.60 10.47.11.99;
   option routers 10.47.11.1;
   if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
     filename "eb-5.4.1-undi.zpxe";
   } else {
     filename "kernel";
   }
   next-server 10.47.11.1;
   option root-path "10.47.11.1:/usr/local/diskless_root";
}

I used these options at rom-o-matic:
NIC/ROM TYPE: undi:undi
Format: PXE bootstrap loader format ROM image (.zpxe)

BAR_PROGRESS
SIZEINDICATOR
ELF_IMAGE
IMAGE_FREEBSD
FREEBSD_KERNEL_ENV
DOWNLOAD_PROTO_TFTP
CONFIG_PCI

The rom-o-matic options might differ depending on your
hardware. The undi:undi type is hardware independant
and works for me for different nics.

I hope that helps,

Norbert



Ask Bjørn Hansen schrieb:
> 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/
> 
> 
> _______________________________________________
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-small
> To unsubscribe, send any mail to "[email protected]"
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-small
To unsubscribe, send any mail to "[email protected]"