similar to: Syslinux and EFI

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 Sun, Dec 2, 2018 at 12:32 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > When booting in UEFI x64 mode in your next test, you should see a boot > > > menu. > > > > Nope: > > > > *** Press enter to boot the default label *** > > Failed to load libcom32.c32 > > Failed to load COM32 file SYSLINUX/EFI64/vesamenu.c32 >

On Sun, Feb 2, 2014 at 1:53 PM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sun, Feb 2, 2014 at 12:34 PM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: Gene wrote: >>> Yes however I have no clue on the reliability of your system for building Syslinux. I can provide some test binaries if you would like. >> That would be a good idea! >> I've

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

Hi there, I am trying to setup a bootable PXELinux (Using 6.02) over UEFI. Currently, I am using DNSMasq for this. PXE with BIOS works perfectly fine for me. As I don't have any UEFI devices here, I am using VMware Workstation 10.0.1 for testing. My DNSMasq setup has been extended, to load also UEFI: dhcp-boot=pxelinux.0 dhcp-match=set:efi-ia32,option:client-arch,6

Ady Ady via Syslinux wrote: > >> We're using a CentOS 6 server running its native (ISC) dhcpd (v4.1.1) >> and tftpd (v 0.49). I've installed syslinux.efi and ldlinux.e64 from the >> syslinux-6.04-pre2 distro alongside the existing pxelinux.0 > > > Please avoid the official binaries from Syslinux 6.04-pre2 and > 6.04-pre3. Additionally, the current git

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

Ady Ady via Syslinux wrote: > > As usual, builds/versions should not be mixed, at least within the same > platform (bios/ia32/x64). > > Currently, the Syslinux-related binary packages in Debian are: > > _ extlinux > _ isolinux > _ pxelinux > _ syslinux > _ syslinux-common > _ syslinux-efi > _ syslinux-utils > > The list of packages and their

Hello! I've been attempting to add EFI support to a linux live distro (slax), it's built on a syslinux bootloader. I can get EFI to work using menu.c32 on syslinux 6.03; however ideally we'd like the VESA menu as well. When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a blank screen and the machine seems to hang. I've tried adding MENU RESOLUTION based on

Gene Cumm wrote: > > On Fri, Oct 4, 2019 at 7:47 AM James Pearson via Syslinux > <syslinux at syslinux.org> wrote: >> >> Ady Ady via Syslinux wrote: >>> >>>> We're using a CentOS 6 server running its native (ISC) dhcpd (v4.1.1) >>>> and tftpd (v 0.49). I've installed syslinux.efi and ldlinux.e64 from the >>>>

On Sun, Feb 2, 2014 at 12:34 PM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sun, Feb 2, 2014 at 7:18 AM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: >> On Sat, Feb 1, 2014 at 8:50 PM, Ady <ady-sf at hotmail.com> wrote: >>> >>>> On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: >>>> > Known

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

On Fri, Nov 30, 2018 at 9:56 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I have a proposal for you here (in the Syslinux mailing list): let's > first find out _what_ exactly is required in order to boot in UEFI > mode, and then you can take the info downstream. Whether "downstream" > means your own personal customized boot.img, or

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

We've been successfully installing Linux using pxelinux to bootstrap our Linux (CentOS) installs for many years, but we are about to take delivery of hardware that doesn't have legacy BIOS boot support for internal drives - so I'm making my first foray into the world of EFI - and can _almost_ get it all to work, but hit an issue that I'm not sure how to 'fix' ...

> Let me double check what the status of 6.04-pre1 is. Maybe this patch > is not necessary at all! Just a reminder: _ 6.04-pre1 can be downloaded from kernel.org, and it includes pre-built binaries, so no "make" anything is needed (and to some degree, not always recommended). _ In many cases, testing with pre-built official binaries is desired, so others can attempt to

> 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?) > > > > > > Yes, those 2 files came from your 'syslinux' command (in your other > > email). We don't want anything

Machine using HP DL380 Gen9 server Initially I got problem where boot hung at My IP 0.0.0.0 Then I referred to http://www.syslinux.org/archives/2015-June/023641.html And used the patch provided then it again hung but at different step Getting cached packet My IP 192.168.103.41 (hung here) >From /var/log/messages Oct 7 01:16:10 foreman in.tftpd[43905]: RRQ from 192.168.103.41 filename

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 i'm about to upgrade systems. yesterday i got https://www.zytor.com/pub/syslinux/Testing/6.04/syslinux-6.04-pre3.tar.xz in order to upgrade 6.04-pre1 version. i first was upgrading a usb-disk which was booting smootly with a simple configuration. i changed the EFI installation in /EFI/BOOT: efi64/efi/syslinux.efi (UEFI bootloader for EFI X64 (x86_64) firmware) ?