[gPXE] chainloading xxx.c32
Tom Baumann
tom at thomasbaumann.com
Sun Jul 3 15:24:35 EDT 2011
On Sun, Jul 3, 2011 at 13:01, Tom tiri Baumann wrote:
>> But how can I load c32 then without the use of tftp or dhcp-options?
>> Are there plans to solve this issue?
>> And, will it work with Syslinux-3 c32-Files?
> Files from Syslinux 3.86 should work. Bear in mind that gPXE can set
> these DHCP options (manually or via a script) such that they need not
> be set in the DHCP server.
>
OK, This helps.
#!gpxe
echo "booting via http"
dhcp net0
set 209:string default
set 210:string http://boot3.kernel.org/bko/
chain http://boot3.kernel.org/bko/pxelinux.0
Then the following will be loaded from bko.
Including the new comboot files.
Best
regards,
tom
>> Am 03.07.2011 17:41, schrieb Gene Cumm:
>>> On Sun, Jul 3, 2011 at 11:34, Tom Baumann<tom at thomasbaumann.com> wrote:
>>>> Hello list,
>>>>
>>>> I currently try to chainload the Menu from kernel.org's bko.
>>>> But when performing a
>>>>
>>>> chain http://boot3.kernel.org/bko/menu.c32
>>>>
>>>> I always get "Requested memory not available (0x46038001)".
>>>>
>>>> I tried as well with undionly.kpxe.
>>>>
>>>> Version is gPXE 1.0.1.
>>>> gPXE 1.0.1 -- Open Source Boot Firmware -- http://etherboot.org
>>>> Features: HTTP HTTPS iSCSI DNS TFTP bzImage COMBOOT ELF Multiboot NBI PXE
>>>> PXEXT
>>>>
>>>> How could this being solved?
>>>> How will it be possible to chainload the comboot.c32?
>>> IIRC, BKO has been updated to Syslinux 4.xx. Those .c32 files are in
>>> the new COM32R format which gPXE does not support. Loading PXELINUX
>>> first with appropriate DHCP options should solve this issue.
More information about the gPXE
mailing list