[syslinux] Getting HTTP path-prefix to work with syslinux.efi

Gene Cumm gene.cumm at gmail.com
Mon Jun 13 19:05:49 PDT 2016

On Mon, Jun 13, 2016 at 7:41 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote:
>>  > Is syslinux.efi supposed to be able to handle HTTP URLs?
>> If the underlying firmware can.   Try just specifying an HTTP URL in the
>> config or on the command line instead of the path-prefix option.
> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP.

There's a lot of variation.  Sounds like a Nehalem/Westmere system
implementing UEFI 2.0 if I were to guess.  Do you have a shell option
in your boot selections?  Looking to get data like I did for an HP
system in http://www.syslinux.org/archives/2015-August/023999.html
http://www.syslinux.org/archives/2015-August/024005.html and

version > fs0:\efi-ver.txt
guid > fs0:\efi-guid.txt
  or     alias > fs0:\efi-alias.txt
dh > fs0:\efi-dh.txt
dh -p Net > fs0:\efi-dh-net.txt

I'm guessing a lack of TCPv4Sb (an alias for the

> Somehow I was under the impression improvements from pxelinux variants like
> lpxelinux were already wrapped into the EFI version.
> Is there an "l" version of syslinux.efi?


> Or any way to get HTTP transfers
> with UEFI on a system whose underlying firmware doesn't understand HTTP?

Perhaps with iPXE snponly.efi or the like tying to the underlying SNP
and providing HTTP.


More information about the Syslinux mailing list