similar to: Getting HTTP path-prefix to work with syslinux.efi

> > 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. Somehow I was under the impression improvements from pxelinux variants like lpxelinux were

For those who use pxelinux-options to modify your (l)pxelinux.0 or your syslinux.efi and are having trouble with HTTP, see below... Regarding the "-a" and "-b" options, with (l)pxelinux.0 I discovered at some point in the past, after some trials, that the following combination worked great for me: -b next-server my.ip.address -a path-prefix http://my.ip.address/

On Jun 13, 2016 7:21 PM, "Alexander Perlis via Syslinux" <syslinux at zytor.com> wrote: > > I previously wrote: > > On a whim, I then tried "-b path-prefix" instead of "-a path-prefix", > > and that was the solution! Everything works! > > Oops, I spoke too soon. With syslinux.efi, using "-b path-prefix http://my.ip.address/"

>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. > > There's a lot of variation. Do you have a shell option > in your boot selections? None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 (firmware A16) seem have a built-in EFI shell option, but in all three cases I had success running the external EFI shell from

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

On Tue, Jun 14, 2016 at 4:44 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. >> >> >> There's a lot of variation. Do you have a shell option >> in your boot selections? > > > None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 >

On Fri, Jun 10, 2016 at 4:30 PM, Alexander Perlis via Syslinux <syslinux at zytor.com> wrote: > For those who use pxelinux-options to modify your (l)pxelinux.0 or your > syslinux.efi and are having trouble with HTTP, see below... > > > Regarding the "-a" and "-b" options, with (l)pxelinux.0 I discovered at some > point in the past, after some trials,

Question: If syslinux.efi is loaded locally off USB rather than via an EFI PXE option ROM boot, but on a client whose EFI firmware has TCP support, should that locally-booted syslinux.efi be able to process HTTP URLs? Initial experiments indicate "no", but why not? Purpose: My TCP-capable EFI client is on a subnetwork with broken DHCP not under my control, so I can't

On Sat, Jun 18, 2016 at 4:09 AM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Fri, Jun 17, 2016 at 07:27:17PM -0500, Alexander Perlis via Syslinux wrote: >> Question: >> If syslinux.efi is loaded locally off USB rather than via an EFI >> PXE option ROM boot, but on a client whose EFI firmware has TCP >> support, should that locally-booted

Hi, We are currently testing PXE booting with syslinux.efi in UEFI mode. This is working fine. However the loading of syslinux.efi and the config files is still using TFTP protocol, the rest kernel and initrd is loaded using HTTP protocol. We would like to use only HTTP protocol. In UEFI it is possible to use HTTP boot instead off PXE boot. Questions: 1. If we load syslinux.efi with HTTP will

On 2019-12-13 08:36, Gregory Lee Bartholomew via Syslinux wrote: > On Fri, 2019-12-13 at 08:47 +0100, jps--- via Syslinux wrote: >> Hi, >> >> We are currently testing PXE booting with syslinux.efi in UEFI mode. >> This is working fine. >> However the loading of syslinux.efi and the config files is still using >> TFTP protocol, the rest kernel and initrd is

Hello, I'm trying to use http from syslinux.efi but it fails while trying to establish the connection to a FreeBSD http server. A packet capture shows: TCP healthd > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 TSval=1094 TSecr=0 TCP http > healthd [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=64 TSval=1596927428 TSecr=1094 TCP healthd > http [ACK] Seq=1 Ack=1 Win=2097152

Hello, is there a way to start a efi-application (bios update tool) from syslinux ? best regards Johann

Hi! I am currently trying upgrade my bios pxe server with additional uefi support. My current using memtest86+ doesn't seem to support uefi, so I would have to use memtest86, as it supports this. But the memtest86 file itself is an *.efi file. When booting this one directly without syslinux, its working. But I want to launch it later from the syslinux menu. Can I chainload somehow another

Hi, I am trying to get a UEFI bootable USB. And I am unable to make it working. I have two x86_64 systems and both of them 'hangs' when I choose to boot UEFI from USB. I've created fat32 formated partition with ef00 type. I placed EFI/BOOT there with content of efi64/ distribution, I've created syslinux.cfg and renamed syslinux.efi to BOOTX64.EFI. However, it does just

Hello everybody, I been using lpxelinux.0 with legacy boot to load KERNEL over http instead of tftp and I want to switch to efi boot. Thank you for the great tech! However it seems the syslinux.efi does not support HTTP / IP? How can I get efi boot load syslinux with an IP stack? # dpkg -S /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi syslinux-efi: /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi # dpkg

Sorry thinking about this problem at work, I'm using my cellphone. Won't get home until 1am. I run Gentoo. https://wiki.gentoo.org/wiki/Syslinux#Setup_on_EFI_systems is my distribution instructions on installing Syslinux. http://www.syslinux.org/wiki/index.php?title=Install#UEFI are your instructions. I have tried both instructions only to get a blank or black screen. Trying to make a

Hello everyone, I am trying to prepare a UEFI bootable thumb drive using syslinux and Linux foundations PreLoader.efi. I started the same as as it works with gummiboot-42: * Copy PRELOADER.EFI to EFI/BOOT/BOOTX64.EFI * Copy HASHTOOL.EFI to EFI/BOOT/BOOTX64.EFI * Copy gummibootx64.efi to EFI/BOOT/LOADER.EFI With just those files PreLoader asks to enroll gummiboot's hash. I do so and

On Tue, Jun 21, 2016 at 5:33 PM, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > On 06/18/16 03:50, Gene Cumm via Syslinux wrote: >> >> UEFI is very different. There's no option ROM nor PXE stack. >> Generally speaking, the underlying UEFI system has to get NIC drivers >> (commonly built-in) and initialize the network through a round of DHCP

Hi, When we meet UEFI or EFI firmware, lots of linux os release use GRUB bootloader. But I wanna use isolinux to boot the installation environment and also the linux os installed. Some question puzzled me. Now, I look for your help: 1. I didn't found information about how to use syslinux(isolinux,etc.) in uefi. I wanna know that are there some differences of the isolinux configuration