search for: git20190206

...ry packages in Debian are: > > _ extlinux > _ isolinux > _ pxelinux > _ syslinux > _ syslinux-common > _ syslinux-efi > _ syslinux-utils > okay thanks a lot for explaining that :-) So for the record at the moment: I've tried the syslinux.efi from syslinux-efi_6.04~git20190206.bf6db5b4+dfsg1-1_all.deb and ldlinux.e64 from syslinux-common_6.04~git20190206.bf6db5b4+dfsg1-1_all.deb On my hardware from AsRock (J4105) and Gigabyte (J1900) the following recent versions of pxelinux/syslinux: 1) debian 6.04~git20190206.bf6db5b4+dfsg1-1 2) vanilla git master at the moment 3)...

...oot signature 0x2, bailing out > Booting kernel failed: Bad file number > """ Which syslinux version? What is the APPEND for mboot.efi ? (In order to boot The Hurd on Devuan I had to edit mboot as it handled arguments differently from grub. This is published as version 3:6.04~git20190206.bf6db5b4+dfsg1-3+devuan6 in Devuan repo. So it might be related here, or not) Ralph. > > Secure boot is disabled. > > Thoughts? > > The reason why it would be nice using PXE and syslinux here is because we > have this automation set up where we can choose from the menu wha...

...ries to load anything related to ESX8TEST.cfg, I guess that's because it errors out before even looking at the append command Marki > > (In order to boot The Hurd on Devuan I had to edit mboot as it handled > arguments differently from grub. This is published as version > 3:6.04~git20190206.bf6db5b4+dfsg1-3+devuan6 in Devuan repo. So it > might be related here, or not) > > Ralph. > >> Secure boot is disabled. >> >> Thoughts? >> >> The reason why it would be nice using PXE and syslinux here is because we >> have this automation set up whe...

On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: > >> the PXELINUX log line is >> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >> Anvin et al), > > (snip) > > FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good > for troubleshooting. > > Is the same behavior present when testing with other versions? I would

Dear gentlemen, I think I'd better start another thread for this... thanks to Ady Ady and Gregory Lee Bartholomew for their responses to my early question. Just for the record, my fresh experience with PXElinux 6.x follows: syslinux.efi version 6.03 does boot to the extent that it shows a prompt, but if I provide it with a CFG file containing several labels, no matter what label I type

If they are useful, then one should note where they can be found and how to extract them for anyone not using a Debian-based distro. Saying just that they are in the Debian Testing repo, doesn't mean much to a non-Debian-er... On Thu, Nov 14, 2019 at 09:50:40PM +0000, Ady Ady via Syslinux wrote: > > Do note that not everyone is running a Debian based system, > > so "the

...more up-to-date than official upstream 6.04-pre1). >> Please note that you need to replace _all_ binaries (e.g. *.c32), not >> just lpxelinux.0, from the same exact build/version/package. Thanks for letting me know. I have repeated my tests with 6.04-pre1 and Debian unstable?s 3:6.04~git20190206.bf6db5b4+dfsg1-1. Both versions exhibit the same problem. > Indeed; it would also be a good idea to test both pxelinux.0 and lpxelinux.0. > They access the PXE stack in very different ways, so it is a good idea to > check both. I can confirm that using pxelinux.0 instead of lpxelinux.0 d...

Hello everybody, I am looking for the efi64/syslinux.efi with IP support like the bios/lpxelinux.0 version has. I am using debian buster with: syslinux-efi 3:6.04~git20190206.bf6db5b4+dfsg1-1 all collection of bootloaders (UEFI bootloader) Thank you in advance, Kind regards, Jelle de Jong

...ou for the great tech! However it seems the syslinux.efi does not support HTTP / IP? How can I get efi boot load syslinux with an IP stack? # dpkg -S /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi syslinux-efi: /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi # dpkg -l syslinux-efi ii syslinux-efi 3:6.04~git20190206.bf6db5b4+dfsg1-1 Kind regards, Jelle de Jong

Hello, So I'm running syslinux.efi Which loads menu.c32 Which is supposed to start ESXi's bootx64.efi/mboot.efi But that gives """ Loading mboot.efi... ok Invalid Boot signature 0x2, bailing out Booting kernel failed: Bad file number """ Secure boot is disabled. Thoughts? The reason why it would be nice using PXE and syslinux here is because we have

...ficial upstream 6.04-pre1). >>> Please note that you need to replace _all_ binaries (e.g. *.c32), not >>> just lpxelinux.0, from the same exact build/version/package. > > Thanks for letting me know. I have repeated my tests with 6.04-pre1 and > Debian unstable?s 3:6.04~git20190206.bf6db5b4+dfsg1-1. Both versions > exhibit the same problem. > >> Indeed; it would also be a good idea to test both pxelinux.0 and lpxelinux.0. >> They access the PXE stack in very different ways, so it is a good idea to >> check both. > > I can confirm that using pxe...