[syslinux] can pxe localboot report failure to bios

H. Peter Anvin hpa at zytor.com
Thu May 19 10:07:06 PDT 2005


Carl Karsten wrote:
> <Docs>
> 
> LOCALBOOT type [ISOLINUX, PXELINUX]
> 
>     On PXELINUX, specifying "LOCALBOOT 0" instead of a "KERNEL" option 
> means invoking this particular label will cause a local disk boot 
> instead of booting a kernel.
> 
>     The argument 0 means perform a normal boot. The argument 4 will 
> perform a local boot with the Universal Network Driver Interface (UNDI) 
> driver still resident in memory. Finally, the argument 5 will perform a 
> local boot with the entire PXE stack, including the UNDI driver, still 
> resident in memory. All other values are undefined. If you don't know 
> what the UNDI or PXE stacks are, don't worry -- you don't want them, 
> just specify 0.
> 
>     On ISOLINUX, the "type" specifies the local drive number to boot 
> from; 0x00 is the primary floppy drive and 0x80 is the primary hard 
> drive. The special value -1 causes ISOLINUX to report failure to the 
> BIOS, which, on recent BIOSes, should mean that the next boot device in 
> the boot sequence should be activated.
> </Docs>
> 
> I think I want the bios to figure out what to boot next, as if pxe had 
> not happened.  What I get from the docs is when using pxelinux, I have 
> to specify what device to boot.
> 

I'm not sure how you get that for the docs, unless you're reading the 
paragraph which explicitly starts with "On ISOLINUX..."  You want 
"localboot 0" for PXELINUX.

	-hpa




More information about the Syslinux mailing list