similar to: PXE EFI booting - 2 issues!

Hi Gene, (some text snipped throughout) > > issue #1: > > I can only get this working on 6.02-pre16 and before back to 6.01-pre2, > > but definitely not working for me on the latest precompiled 6.02 zip & tar.gz. > http://bugzilla.syslinux.org/show_bug.cgi?id=35 although my current > branch needs just a little more work for the cross-subnet case. Thanks for that,

On Sat, Nov 16, 2013 at 6:11 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > Hi, > > background: > I've managed to get EFI32, EFI64 and 'BIOS' modes all booting & working from the same TFTP/DHCP server using the setup described in message #10 here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10 > > I'm running this inside VMWare 9 -

Hi all.. Quick one if someone could show me a line out of their configuration for these two scenario's . We're trying to do two things via EFI64 network boot & SYSLINUX: * boot a CentOS 6.5 installation vmlinuz/initrd.img combination - machines just reboot after downloading the initrd.img. * boot windows server 2012 r2 PE menu via bootmgfw.efi - unsure of the commands to

> 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

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

With the BIOS architecture, I was used to boot WinPE from PXELINUX. I used 4 different ways: 1- Calling windows' native PXE loader directly from the config file with a 'kernel' line. 2- Calling windows' native PXE loader with pxechn.c32. 3- Loading an ISO with memdisk 4- iPXE project's wimboot, which relies on memdisk Methods 1 and 2 are slow because loading the bulk of the

Hi >On Wed, 24 Jul, at 03:48:14PM, Matt Fleming wrote: >> On Wed, 24 Jul, at 09:04:17PM, Victor Sudakov wrote: >> > memtest86 does not work any more after upgrading PXELINUX to 6.01. >> > When trying to boot, I get the following message: >> > >> > PXELINUX 6.01 2013-07-04 Copyright (C) 1994-2013 H. Peter Anvin et al >> > Loading memtest86...

> -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: 06 June 2014 16:14 > To: Andrew Rae; 'syslinux at zytor.com' > Subject: Re: [syslinux] EFI booting over network - can't then load anything > > On 06/06/2014 07:27 AM, Andrew Rae wrote: > > Hi all.. > > > > Quick one if someone could show me a line out of their

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

> I use Syslinux 6.03 EFI64 on a VMware Workstation 10 VM on > 10.0.2 on Linux. > w/o any problem? >> correctly sends back w/o error the "corresponding" syslinux.efi >> "EFI BC" -> EFI64\syslinux.efi >> "EFI IA32"-> EFI32\syslinux.efi >I only send back 1 filename. > Me too, I just send the

> 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

> > From: Matt Fleming [matt at console-pimps.org] > > Sent: 25 June 2014 07:39 > > To: Andrew Rae > > Cc: Gene Cumm; syslinux at zytor.com > > Subject: Re: [syslinux] testing out 6.03 network booting... > > > > Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release > > button yesterday and -pre18 contains my change. It would be

>>> 1) SYSLINUX on EFI must be extended to load arbitrary >>> EFI binaries >>> (perhaps through a module first >>> like how linux.c32's code became the >>> Linux loader). >> >> Do you know 6.03 status on this topic? >> i.e. can something like bootmgfw.efi be booted today ornot? > http://bugzilla.syslinux.org/show_bug.cgi?id=17

On Thu, Jun 19, 2014 at 2:51 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > 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. I'd say this is an excellent place to start. I'm getting some similar results here with the precompiled

On Wed, Sep 23, 2015 at 4:24 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > > > BTW if you take a minute and read the first report > > https://communities.vmware.com/message/2536774 > > You'll realize that VMWare TFTP "surprisingly" does not present slow TFTP transfers > > when they are driven by MS

On Sat, Jan 10, 2015 at 5:44 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >> I use Syslinux 6.03 EFI64 on a VMware Workstation 10 VM on >> 10.0.2 on Linux. >> > w/o any problem? Yes. > Me too, I just send the ""corresponding"" syslinux.efi >> Are they actually transferring the syslinux.efi files? > > sure > >> What

On Sun, 22 Jun, at 06:15:50PM, Andrew Rae wrote: > > Matt - I'd love to try it - but I'm not so good at fixing compiling > issues. right now I get stuck at being unable to 'make' the efi32 or > efi64 components due to an error: Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release button yesterday and -pre18 contains my change. It would be good to

I upgraded from syslinux 4.x to syslinux 6.01 and am now having issues with pxe chaining. I've tried moving up as far as 6.02-pre16, but I'm still experiencing the same problem. The original config called the next server as follows: LABEL Cobbler KERNEL pxechain.com APPEND 10.x.x.x::pxelinux.0 Which worked for the previous version, but I started getting an error after

On Fri, 02 Aug, at 07:51:12PM, Jonas Keidel wrote: > So will the patch be applied in 6.02? It's in 6.02-pre16. -- Matt Fleming, Intel Open Source Technology Center

On Thu, Sep 12, 2013 at 12:24 AM, Steven Shiau <steven at nchc.org.tw> wrote: > On 2013/9/12 11:55, Steven Shiau wrote: >> >> Deal developers, >> I'd like to follow the thread >> http://www.zytor.com/pipermail/syslinux/2013-April/019761.html >> but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and >> provide more test cases.