similar to: EFI32/64 doesn't boot 32 bits kernel

Hello, Thank you, for this information. This is, what I need. So I will switch from 6.03 to the last 6.04 pre. Regards Johann > -----Urspr?ngliche Nachricht----- > Von: Syslinux <syslinux-bounces at syslinux.org> Im Auftrag von Ady Ady via > Syslinux > Gesendet: Montag, 15. April 2019 18:53 > An: syslinux at syslinux.org > Betreff: Re: [syslinux] EFI32, EFI64 on one

> 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

Hello, PATH relative / absolute ? If I set PATH x86 -> /EFI/BOOT/x86 is search path ? What is the prefix for PATH <dir> ? Which files are search in the PATH ? Only *.c32 or also other one ? Thanks Regard Johann > -----Urspr?ngliche Nachricht----- > Von: Syslinux <syslinux-bounces at syslinux.org> Im Auftrag von Ady Ady via > Syslinux > Gesendet: Montag, 15.

> Den 21. april 2016 kl. 22.04.37 +02.00 skrev Gene Cumm <gene.cumm at gmail.com>: > > > On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <<gene.cumm at gmail.com>> wrote: > > > > > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <<atle at team-holm.net>> wrote: > > > > > > > Under EFI/BOOT are the following files: > >

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 ?

> Thank you all. > > It looks like -mno-red-zone flag is already in master branch since > commit 7d70885d, but it seems it is applied to all EFI builds. Finally we are on the same page. > > IIUC, the problem only affects efi64 builds. Have you actually tested efi32 (ia32) builds? > > So here's the modification of my patch to only apply -mno-red-zone >

Den 21. april 2016 kl. 22.04.37 +02.00 skrev Gene Cumm <gene.cumm at gmail.com>: > On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <<gene.cumm at gmail.com>> wrote: > > > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <<atle at team-holm.net>> wrote: > > > > > Under EFI/BOOT are the following files: > > > BOOTIA32.EFI (from

On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote: >> Under EFI/BOOT are the following files: >> BOOTIA32.EFI (from efi32/efi/syslinux.efi) >> BOOTX64.EFI (from efi64/efi/syslinux.efi) >> ldlinux.sys (copied from root of partition) >> lua.c32 >>

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

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

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 Tue, Apr 22, 2014 at 8:15 PM, Steven Shiau <steven at nchc.org.tw> wrote: > > 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,

On 11/28/2016 09:33 AM, Ady Ady via Syslinux wrote: > >> 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

Hi Ady, Would it work if we removed "ifdef EFI_BUILD" condition and just add -mno-red-zone for all x86_64 builds? If not, do you have any ideas how to pass this flag? This could work, because the patch is adding the -mno-red-zone flag only for x86_64 builds, which are only used in the form of the efi64 target. The efi32 and bios targets are both 32-bit. BTW. I also tried 6.04-pre1 and

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,

Hi.... I am trying to TFTP netboot a 32bit linux kernel (4.11.3) via efi64 syslinux.efi. If I build a 64 bit version of the same kernel, it TFTP netboots fine, but if I build the kernel (same config options as 64 bit working version) as 32 bit, the PC reboots almost immediately after loading the kernel over TFTP. I read before that support for loading 32 bit kernels in efi64 had been added in

Hello syslinux maintainers, I came across the issue of syslinux crashing with some EFIs in the UEFI boot mode. Upon closer investigation it turned out that most object files which go into syslinux efi64 are compiled with the so-called red zone. Some EFIs follow Windows ABI more strictly and cause syslinux to crash due to stack overwrite. Looking at mk/efi.mk there was a previous attempt to fix

I've just tried 4.07 and that has the same results. I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt to choose the Windows Deployment Services option, it hangs. Thanks, Dan Jackson (Lead ITServices Technician). -----Original

On Thu, Jun 16, 2016 at 4:53 AM, Jackson, Dan via Syslinux <syslinux at zytor.com> wrote: > Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). > > Thanks, > Dan Jackson (Lead ITServices Technician). > > -----Original Message----- > From: Syslinux

> On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > Here are some comments and questions for you. > > > > Thanks. > > I've have my scripts to a better state, including installing/using > qemu to uefi and legacy boot the usb stick for testing. > > It mostly works for me, but the "wget a tarball of