similar to: PXE boot error

> Hi, > > We have some problems while network booting thin clients. The type is T5540. > > At this moment we are using pxe linux 6.03. > > The systems are booting correctly with pxe linux version 6.03-pre14. > We have seen the same error with version 6.03-pre9. > > The error message: > > Failed to load ldlinux.c32 > Boot failed: press a key to retry, or

>> Hi, >> >> We have some problems while network booting thin clients. The type is T5540. >> >> At this moment we are using pxe linux 6.03. >> >> The systems are booting correctly with pxe linux version 6.03-pre14. >> We have seen the same error with version 6.03-pre9. >> >> The error message: >> >> Failed to load ldlinux.c32

On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: > >> Hi, > >> > >> We have some problems while network booting thin clients. The type is T5540. > >> > >> At this moment we are using pxe linux 6.03. > >> > >> The systems are booting correctly with pxe linux version 6.03-pre14. > >> We have seen the same error

Hi, Thank you for your reply. Below the answers. _ When you update the version of pxelinux.0, are you also updating the version of ldlinux.c32? Yes, I've updated both files. _ The version of all the c32 files in use shall match the version of the boot loader. Yes, I've copied all the files which we are using. The version of all the files is the same. _ When you mention the error

On Wed, Dec 17, 2014 at 5:54 AM, Willem Bargeman <willem at bargeman.eu> wrote: > On Wed, Dec 17, 2014 at 2:55 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Tue, Dec 16, 2014 at 4:22 PM, Geert Stappers <stappers at stappers.nl> wrote: >>> On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: >>>> >> Hi, >>>>

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

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

> Message: 3 > Date: Fri, 06 Jun 2014 08:13:36 -0700 > From: "H. Peter Anvin" <hpa at zytor.com> > To: Andrew Rae <A.M.Rae at leeds.ac.uk>, "'syslinux at zytor.com'" > <syslinux at zytor.com> > Subject: Re: [syslinux] EFI booting over network - can't then load > anything > Message-ID: <5391DAA0.2050207 at

On Jun 05 2014, Ady wrote: > > I'm working on a system derived from ARCH linux, running what they > > call version 6.02-4 of the syslinux package (which would be your > > version 6.02 plus their/our patches). I've got a syslinux.cfg > > ArchLinux currently is already using 6.03-pre12 or newer, so I would > suggest for you to update. I want to keep the

Sebastian, On 01/15/2015 12:49 AM, Sebastian Herbszt wrote: > which version of pxelinux were you trying? Looks like < 5.x. the one from Fedora 20, syslinux-4.05. It turns out that pxelinux.0 from Fedora 21, syslinux-6.03, reports "Failed to load ldlinux.c32" when ldlinux.c32 can't be read, and "Loading <FILE>... failed: No such file or directory" when the

My ?default? was just a sample to prevent further tl;dr :) Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to 6.02 or X? Which version? Thanks, David Sent from my iPhone > On Feb 1, 2018, at 6:53 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > >> Hardware

> I'm testing syslinux PXE EFI boot with VMware workstation 9.04 running > on Windows 8.1 > > VMware correctly performs the DHCP request indicating either > the "EFI IA32" or "EFI BC" architecture and the TFTP server > correctly sends back w/o error the "corresponding" syslinux.efi > "EFI BC" -> EFI64\syslinux.efi >

On Tue, May 20, 2014 at 12:20 PM, Anatol Pomozov <anatol.pomozov at gmail.com> wrote: > Hi > > On Tue, May 20, 2014 at 9:18 AM, Anatol Pomozov > <anatol.pomozov at gmail.com> wrote: >> Hi >> >> On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On May 20, 2014 12:33 AM, "Anatol Pomozov"

Hi On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On May 20, 2014 12:33 AM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: >> >> Hi >> >> On Mon, May 19, 2014 at 6:58 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> > On May 19, 2014 5:17 PM, "Anatol Pomozov" <anatol.pomozov at

Hardware with issue is a Lenovo T410 (circa 2007?): SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is working for Ghostcast/peer to peer. SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is NOT working for Ghostcast/peer to

Hi On Mon, May 19, 2014 at 6:58 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On May 19, 2014 5:17 PM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: > >> Besides syslinux itself other things has changed e.g. gcc (but I >> really hope my problem not because of compiler). > > This alone can be the trigger.This might be a starting point: build

* Gene Cumm, 2014-06-10 : > If 4.05 or 3.86 acted nicely, this would mean a bug. OK, so, with unpatched official binaries: 3.86 ---- pxelinux.0 Loads fine, assumes terminal width 15, displays menu, but then freezes (I suspect it does not process any input from the serial port) gpxelinux.0 Displays: PXE->EB: !PXE at 9E64:0060, entry point at 9E64:00F6 UNDI code segment

Thanks Ady. I have to stick with stable vs. experimental but I appreciate the Debian suggestion. I don't mean to troll anyone, but... how is 6.03 considered stable if it does not correctly support keeppxe? I have to go all the way back to 4.xx for this to be supported? Wow. I still couldn't find it in the docs online where it states keeppxe doesn't work. I have some "detail

On Fri, Jan 9, 2015 at 12:00 PM, Ady <ady-sf at hotmail.com> wrote: > >> I'm testing syslinux PXE EFI boot with VMware workstation 9.04 running >> on Windows 8.1 I use Syslinux 6.03 EFI64 on a VMware Workstation 10 VM on 10.0.2 on Linux. >> VMware correctly performs the DHCP request indicating either >> the "EFI IA32" or "EFI BC"

> Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit : > Some news here. I didn't test with 5.01 yet (didn't see that one sorry). > With 5.01 i don't have any problem. Problems begin with 5.10. > -- > Eric PEYREMORTE Hello Eric: To sum up your report: _ 4.0x works; _ 4.10-pre22 (lwip branch) works; _ 5.01 (elflink branch) works; _ 5.10 (lwip merge into elflink) fails; I