similar to: make efi64 install in syslinux-6.02-pre3 fail

On Thu, 11 Jul, at 01:55:12PM, Michael Szerencsits wrote: > 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]: ***

> Sorry about that. I've fixed the Makefiles in 6.02-pre4. > > > Would this also create memdisk for efi64 boot? > > No, memdisk is inherently tied to bios and isn't build for efi32/efi64. > > -- > Matt Fleming, Intel Open Source Technology Center > Hi Matt, thanks for your response. Would there be memdisk or a similar program/methode to emulate a cdrom

> If the Windows OS is running and a program is checking for an optical > disc drive, then you really need one of: > - A physical optical disc drive with the expected disc > - A virtual optical disc drive with the expected disc > > Are you using either of these right now? If you are using a physical > OD, does it have a Syslinux EFI on it? If you are [thinking about]

> Which one, just out of curiosity? They are Sony notbooks > What is the "preload install script"? Is the DVD El-Torito-bootable and > it runs something which reports that the system must be EFI _before_ it > boots any OS? > If you are using PXE, then that's along the same lines as BIOS. If they > want EFI, that's a stronger requirement than CD/DVD. If

Okay, thanks. I just tried 6.01-pre1, downloading the .xz file. But that won't build because the gnu-efi directory is empty. ?? On Thu, Sep 19, 2019 at 9:29 PM Ady Ady via Syslinux <syslinux at syslinux.org> wrote: > > > fixes, decided to go with 6.04-pre3. First, is that about read for a > > > Please try either 6.04-pre1, or the current (binary) packages from

As suggested, I have made a 6.04-pre3 release. In addition to updating gnu-efi to the latest version available (3.0.9 + a few patches) I wanted to make the tree compile with -Werror on my box, which resulted in pulling a thread which in turn caused a whole bunch of things to unravel :) The end result was that I ended up refactoring much of the tree so that it now avoids building a ton of

Am 12. Juli 2013 15:06:54 schrieb Matt Fleming <matt at console-pimps.org>: > Which installer? I would hazard a guess that the installer is also bios > specific and is going to need to be tailored for EFI boot anyway. > > -- > Matt Fleming, Intel Open Source Technology Center It's a little be complex. It's a DVD based installer where I try to change this to be

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

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

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

On Fri, 12 Jul, at 02:40:00PM, Michael Szerencsits wrote: > Would there be memdisk or a similar program/methode to emulate a cdrom > and boot from a iso file available for efi boot in the future. I need > this, because the *stupid* installer check from which medium the > system was booted and if it's not cd than it fail. Which installer? I would hazard a guess that the installer

On 7/12/2013 14:22, Michael Szerencsits wrote: > Am 12. Juli 2013 15:06:54 schrieb Matt Fleming <matt at console-pimps.org>: >> Which installer? I would hazard a guess that the installer is also bios >> specific and is going to need to be tailored for EFI boot anyway. > > It's a little be complex. > It's a DVD based installer where I try to change this to be

On 07/12/2013 05:40 AM, Michael Szerencsits wrote: > I need this, because the *stupid* installer check from which medium the system was booted and if it's not cd than it fail. It is astonishing it works with memdisk then. -hpa

On 7/15/2013 05:35, Michael Szerencsits wrote: > >> Which one, just out of curiosity? > > They are Sony notbooks > Cool. > > The CD is based on Windows PE. It can be bootet in BIOS and EFI mode. > I already tried the bootmgfw.efi from Windows. This work, but after the WinPE is booted a program is stated and this check the BIOS > if it is set to EFI boot. If not it

Op 2013-07-12 om 14:06 schreef syslinux-owner at zytor.com: > Reason: Message body is too big: 1780404 bytes with a limit of 512 KB So previous not on the mailinglist. > Date: Fri, 12 Jul 2013 23:05:05 +0200 (CEST) > From: Michael Szerencsits <szerencsits.michael at gmx.at> > To: syslinux at zytor.com > Subject: efi64 boot fail during download from kernel and initrd

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 >

Hi, I am using qemu for testing new versions of syslinux before installing on an embedded computer. Everything works fine under qemu (1.5.0), so I updated extlinux from 4.06 to 5.11-pre3 on the computer. I found that the autostart's timeout does not work. The timeout value is correct but nothing happens. It worked well with extlinux 4.06... I tried with extlinux 5.01, 5.10, 5.11-pre3 and