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

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,

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/" merely "works" because it's the same as not specifying the option at all: files get transferred by TFTP. Thus, the

> > 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

>> 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 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/"

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 >

Hello, Apparently I can't put absolute path in the config file. Here is what happen. The DHCP server send the option filename = "/srv/tftp/efi64/syslinux.efi". The client download and boot on this file. It find its first configuration in /srv/tftp/efi64/pxelinux.cfg/default Then, I'd like to chain on the config file /srv/tftp/debian-installer/efi64/pxelinux.cfg/default. Thus

Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for

On 31-07-15 14:25, Patrick Masotta wrote: > ""exponential-like decay of IO rate"" could you please post a link on > your comments on this? Sure, see the thread starting at: http://www.syslinux.org/archives/2015-June/023621.html And Gene's confirmation at: http://www.syslinux.org/archives/2015-June/023629.html > OK I got lost. > are you saying you finally

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 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

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

Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 (with an optional Syslinux menu containing multiple entries). Problem (solved) #1: The default directory location for both syslinux.efi is the same. Solution #1: Rename each syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solution #2:

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

> Some magic in dhcpd.conf: > > if option architecture-type = 00:09 { > filename "efi64/syslinux-87020-or.efi"; > option pxelinux.pathprefix "http://bla/efi64/"; > } elsif option > architecture-type = 00:07 { > filename "efi64/ipxe-git87981.efi"; > } else { > filename

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 09/22/2013 12:56 PM, Celelibi wrote: > Hello, > > Apparently I can't put absolute path in the config file. Here is what happen. > > The DHCP server send the option filename = "/srv/tftp/efi64/syslinux.efi". > The client download and boot on this file. > It find its first configuration in /srv/tftp/efi64/pxelinux.cfg/default > Then, I'd like to chain

Hello, I am pxebooting a large linux kernel (with embedded initramfs) that is around 250 MB in size. When booting a board in legacy BIOS mode, the pxelinux.0 executable is transferred to the board and takes over, from where loading and booting this large kernel works as expected. Actually, better than expected, as no tftp file size limit is incurred. If I change the BIOS settings to UEFI mode,

Hi, I see that 6.x release is out. UEFI support is included. How can I boot Windows 2008 through EFI? What steps of configuration pxelinux I should follow? Also can I boot both BIOS and EFI client from one pxelinux environment? My configuration is syslinux(pxelinux) + ISC dhcp. Thanks.