similar to: isolinux 6.04-pre3-3-g05ac953 - failed to load ldlinux.c32

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

> 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 Debian Testing. Please avoid official 6.04-pre2 and 6.04-pre3 (and official git master head at the time of this email). These _will_ fail at some point or another. > "make official' ? Second, I did have to modify >

> Okay, thanks. I just tried 6.01-pre1, downloading the .xz file. > But that won't build because the gnu-efi directory is empty. ?? As already mentioned in several places/pages/docs... Since Syslinux 6.00, the respective binary files (e.g. boot loaders, installers, Syslinux modules,...) are located under respective "./bios/", "./efi32/",

Testing with a floppy image booting a VM: SYSLINUX 6.04 CHS 6.04-pre3 Copyright... Failed to load ldlinux.c32 Boot failed: please change disks and press a key to continue. The same floppy image and the same VM, when using 6.04-pre2 at least got to the boot prompt. Regards, Ady. PS: In relation to my prior email about the mixing of source/binary files in 6.04-pre3, please also note the

Hello there I built development version of syslinux from git 6.04-pre3-3-(sometag) and I am trying to boot a slackware-current system with it. I do not use a separated partition for `/boot`. It's just `/dev/sda1` here for `/` and `/boot` is just a folder. I simply use `mbr.bin` against a DOS partition table and the first partition having the bootable flag. With this layout, the only

I think I botched syslinux-6.04-pre3. There are two fundamental problems with the build: a) The selection of what pieces of the library gets included in the core is done manually whereas it really should be automatic; b) The build doesn't fail if there are unresolved dependencies between the libraries and the core. I will fix these. (b) is IMO fundamental to avoid this error in the

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

I am new to syslinux/extlinux. Can I boot from a linux btrfs subvolume? I am getting "Failed to load ldlinux.c32" when I attempt to boot from a btrfs subvolume. Setup: 1) I have a USB disk with one partition. The partition is marked "active". 2) I make a btrfs filesystem with "mkfs.btrfs /dev/sdd1". I mount the partiton and execute "btrfs su create

On Thu, Mar 21, 2019 at 04:26:19PM +0000, Patrick Welche via Syslinux wrote: > On Thu, Mar 21, 2019 at 04:15:48PM +0000, Patrick Welche via Syslinux wrote: > > I just idly git cloned head and roughly compiled it on a stock ubuntu 18 box. > > Using the generated pxelinux.0 and ldlinux.c32, I see > > > > "Failed to load ldlinux.c32" > > > > If I

> I built development version of syslinux from git 6.04-pre3-3-(sometag) > and I am trying to boot a slackware-current system with it. I do not > use a separated partition for `/boot`. It's just `/dev/sda1` here for > `/` and `/boot` is just a folder. I simply use `mbr.bin` against a DOS > partition table and the first partition having the bootable flag. > > With this

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]: ***

> The end result was that I ended up refactoring much of the tree so that it now It is known that, since version 6.00, the binary files are located under: _ ./bios/ _ ./efi32/ _ ./efi64/ Those directories should _only_ include binary files and documentation. IOW, source code and/or (temporary) building files should not be in there. Within those subdirectories, the new 6.04-pre3 has a mix

On Mon, 2019-02-11 at 12:15 -0800, H. Peter Anvin via Syslinux wrote: > > > I think I botched syslinux-6.04-pre3. There are two fundamental > problems with the build: > > a) The selection of what pieces of the library gets included in the core > is done manually whereas it really should be automatic; > > b) The build doesn't fail if there are unresolved

On February 11, 2019 12:29:41 PM PST, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: >On Mon, 2019-02-11 at 12:15 -0800, H. Peter Anvin via Syslinux wrote: >> >> >> I think I botched syslinux-6.04-pre3. There are two fundamental >> problems with the build: >> >> a) The selection of what pieces of the library gets included in the >core

I just pushed out SYSLINUX 3.73-pre3. The only significant difference over -pre2 was changing MEMDISK to use "safeint" by default. -hpa

I have a project G4L that has used syslinux for many years. I've upgraded the syslinux from the kernel.org builds over the years up to 6.03 and just copied the newer files, and it has worked. Saw that the new build machine I setup with Fedora 30 had the version 6.04 files. I tried the same process, and then booting the iso comes up with message that it can not load ldlinux.c32, which is

Hello, I just received a serious bug report from Stas Kysel of rPath (with a great test case); it appears that deleted files can confuse extlinux so that it misses files. This is bad. As a result, I have pushed out 3.63-pre3, and intend to make a 3.63 final shortly. I would appreciate any help testing this. Furthermore, I would like to finish the SDI booting module, but I have yet to

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

I just idly git cloned head and roughly compiled it on a stock ubuntu 18 box. Using the generated pxelinux.0 and ldlinux.c32, I see "Failed to load ldlinux.c32" If I replace those files with the ones out of the ubuntu installer, I get the prompt (i.e., ldlinux.c32 is loaded). Is head known to have issues, or is there a way of building broken binaries? Cheers, Patrick

Hello, Thanks for your feedback. On Tue, 24 Mar 2020 18:17:09 +0200 Ady via Syslinux <syslinux at syslinux.org> wrote: > > Building syslinux against gnu-efi 3.0.10 currently fails with: > > FWIW, gnu-efi version 3.0.11 was released just 20 days after the > release of version 3.0.10. Building on top of gnu-efi 3.0.10 should be > considered irrelevant. A more-relevant