similar to: EFI64 Boot 32 bit kernel....

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

On 07/11/17 12:48, cwbshaw . via Syslinux wrote: > > I'd be grateful for any suggestions on how to resolve this. Unfortunately, > for what I am doing I really need to TFTP netboot a 32 bit linux kernel via > EFI64 (long story). > Running 32-bit kernels on EFI64 is not really supported on any level, including the Linux kernel itself. The opposite, 64-bit kernels on EFI32, is

Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64' make[1]: ***

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

Hello, i would like create a bootdisk , that can be boot from Old BIOS, EFI32 and EFI64. But for EFI Boot there is only one directory /EFI/BOOT/ In this directory I can copy BOOTia32.EFI and BOOTx64.EFI. But the *.c32 files for EFI32 & EFI64 , I can install to this directory at the same time. Is there a way to load the *.c32 from different directory ? Or is there a other solution ?

On 2014/4/23 ?? 09:55, Gene Cumm wrote: > The resulting config would require suffix-less module references, i.e. > "UI menu" or "COM32 ls". > > Additionally, I documented the basics of my test system here: > > http://www.syslinux.org/archives/2014-February/021740.html > > Bear in mind, by "URL-like file locations", I mean that if we have >

Dear all, I'd like to have a DHCP/PXE server for different arch of clients, i.e. BIOS, EFI32, and EFI64 clients. As described here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 What Daniel has proposed (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10) should work, i.e. Using a file called pxelinux.cfg/bios containing the following 2 lines:

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

> There might be an alternative (and possibly others too): let the user > select the appropriate firmware from within pxelinux.cfg/default. > > So, keep using the same method you used in previous versions, instead > of selecting the Syslinux cfg / firmware from the DHCP snippet that > Daniel posted. > > If you actually get to pxelinux.cfg/default (as you probably used

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

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.

> > On 09/20/2013 02:34 AM, Ady wrote: > >> There might be an alternative (and possibly others too): let the user > >> select the appropriate firmware from within pxelinux.cfg/default. > >> > >> So, keep using the same method you used in previous versions, instead > >> of selecting the Syslinux cfg / firmware from the DHCP snippet that >

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

Using both a disk load and netboot, the precompiled binaries of Syslinux 6.03-pre7 for EFI64 appear broken. Testing 6.03-pre6 on the same system results in a successful boot. This does not appear to affect the BIOS architecture and likely affects EFI32 also. -- -Gene

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

On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > After some discussion/debugging behind the scenes, we are back on > track, with updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version

I just released 6.02-pre2 which includes support for booting 32-bit kernels from efi64. I know a number of people wanted this feature, so hopefully it will be tested in various environments. One thing to note is that it is not possible to boot a 32-bit kernel from efi64 via the EFI handover protocol (or from firmware via the EFI boot stub), but the kernel loader in Syslinux is smart enough to

Hi, The latest from the firmware branch is failing to build EFI64 as of the time of this message make[3]: Entering directory `/home/voltagex/src/syslinux/efi64/efi' gcc -I/usr/include/efi -I/usr/include/efi/x86_64 -DEFI_FUNCTION_WRAPPER -fPIC -fshort-wchar -ffreestanding -Wall -I/home/voltagex/src/syslinux/com32/include -I/home/voltagex/src/syslinux/com32/include/sys

Hello, I think I found another problem with gfxboot, and I think it is completely unrelated to the 'packed archive' issue. Again I tried using gfxboot with the Ubuntu gfxboot archive, this time with EFI64, using a real EFI-capable machine. I first verified that everything else actually works by commenting out 'ui gfxboot bootlogo' and got a working menu. Uncommented the line