[syslinux] Booting legacy Linux kernel in EFI mode

[Gene Cumm]

On Sun, Oct 20, 2013 at 9:02 AM, Celelibi <celelibi at gmail.com> wrote:
> 2013/10/17, Celelibi <celelibi at gmail.com>:

>> Sorry for answering that late. (I had some issues with my server's
>> Ethernet NIC, and without it, no PXE / syslinux.)
>>
>> So, it's time to be a bit more specific.
>> The kernel I want to boot in EFI mode is a debian installer. It *has*
>> a module "efivars" loaded. Which means this kernel has been compiled
>> with CONFIG_EFI_VARS, which itself depends on CONFIG_EFI. Therefore I
>> should be able to boot this kernel in EFI mode.
>>
>> I don't remember whether I tried or not, so I'll re-test ASAP.
>> However, as I discussed on IRC, the 'file' command only say "x86 boot
>> sector".
>>
>
> Well... I can't boot that kernel.
> All I see is a flashing message saying "No such file or directory"
> then the vesamenu come back and the timeout countdown restart.
> However, I can see that the kernel is not even downloaded from the tftp server.
> All wireshark show me is:
> - A Read Request for the kernel file: /debian-installer/efi64/linux.
> - An Option Acknowledgement from the server (that seems pretty valid to me).
> - An Error code (from the client to the server) with the code 0 and
> message "No error, file closed".
>
> I don't really know what happen at that time.
> I guess it doesn't like the file name for some reason.

So network boot on EFI?  see bugs 26 and 35.

http://bugzilla.syslinux.org/show_bug.cgi?id=26
http://bugzilla.syslinux.org/show_bug.cgi?id=35

-- 
-Gene