similar to: Com32/PXELINUX issues when booting on certain hardware

From: Sylvain Gault <sylvain.gault at gmail.com> Some firmware implementations may need ExitBootServices to be called twice. The second time with an updated memory map key. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- efi/main.c | 75 +++++++++++++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 64 insertions(+), 11 deletions(-) diff --git

Sometimes the UEFI memory map changes between GetMemoryMap() and ExitBootServices(), making the MapKey value incorrect. Per the UEFI spec, the memory map should then be fetched again and exiting retried. Signed-off-by: Tom Huibregtse <thuibregtse at xes-inc.com> --- efi/main.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 70 insertions(+), 11 deletions(-)

I am a UEFI/BIOS developer. We UEFI PXE boot dozens of times per night. We have run into this error more than a couple of times. We have also done thousands of UEFI PXE boots with debug statements to prove that the patch works. From: "Tom Huibregtse via Syslinux" <syslinux at syslinux.org> To: syslinux at syslinux.org Sent: Thursday, June 11, 2020 8:04:06 AM Subject:

On Wed, 26 Aug 2015 05:54:04 +0200 celelibi--- via Syslinux <syslinux at zytor.com> wrote: > From: Sylvain Gault <sylvain.gault at gmail.com> > > Some firmware implementations may need ExitBootServices to be called > twice. The second time with an updated memory map key. > > Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> > --- > efi/main.c |

2015-11-02 12:34 UTC+01:00, Gene Cumm <gene.cumm at gmail.com>: > On Tue, Aug 25, 2015 at 11:54 PM, celelibi--- via Syslinux > <syslinux at zytor.com> wrote: >> From: Sylvain Gault <sylvain.gault at gmail.com> >> >> Some firmware implementations may need ExitBootServices to be called >> twice. The second time with an updated memory map key. >>

On Tue, Aug 25, 2015 at 11:54 PM, celelibi--- via Syslinux <syslinux at zytor.com> wrote: > From: Sylvain Gault <sylvain.gault at gmail.com> > > Some firmware implementations may need ExitBootServices to be called > twice. The second time with an updated memory map key. > > Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> > --- > efi/main.c | 75

2015-11-03 11:24 UTC+01:00, Gene Cumm <gene.cumm at gmail.com>: > On Mon, Nov 2, 2015 at 10:23 PM, Celelibi <celelibi at gmail.com> wrote: >> 2015-11-02 12:34 UTC+01:00, Gene Cumm <gene.cumm at gmail.com>: >>> On Tue, Aug 25, 2015 at 11:54 PM, celelibi--- via Syslinux >>> <syslinux at zytor.com> wrote: >>>> From: Sylvain Gault

On Mon, Nov 2, 2015 at 10:23 PM, Celelibi <celelibi at gmail.com> wrote: > 2015-11-02 12:34 UTC+01:00, Gene Cumm <gene.cumm at gmail.com>: >> On Tue, Aug 25, 2015 at 11:54 PM, celelibi--- via Syslinux >> <syslinux at zytor.com> wrote: >>> From: Sylvain Gault <sylvain.gault at gmail.com> >>> >>> Some firmware implementations may need

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

From: Sylvain Gault <sylvain.gault at gmail.com> On some architecture, including my hardware, the function ExitBootServices may need to be called twice in order to successfully exit the boot services. As stated by the UEFI spec, the first call to ExitBootServices may perform a partial shutdown of the services. It seems that during this partial shutdown, the memory map can be modified, thus

On 07/26/2013 01:27 AM, syslinux-bot for Matt Fleming wrote: > diff --git a/com32/lib/syslinux/load_linux.c b/com32/lib/syslinux/load_linux.c > index 851d467..37c8df0 100644 > --- a/com32/lib/syslinux/load_linux.c > +++ b/com32/lib/syslinux/load_linux.c > @@ -125,10 +125,29 @@ static int map_initramfs(struct syslinux_movelist **fraglist, > } > > static size_t

On 07/29/2013 06:28 AM, Matt Fleming wrote: > On Fri, 26 Jul, at 09:49:28AM, H. Peter Anvin wrote: >> Hmm... this might constrain the heap excessively if the SMT_TERMINAL >> cutoff is at the wrong place (because there will be just enough SMT_FREE >> to fit.) I'm wondering if we shouldn't use the highest of these two >> regions. > > Could you give an

On Fri, 26 Jul, at 09:49:28AM, H. Peter Anvin wrote: > Hmm... this might constrain the heap excessively if the SMT_TERMINAL > cutoff is at the wrong place (because there will be just enough SMT_FREE > to fit.) I'm wondering if we shouldn't use the highest of these two > regions. Could you give an example memory map where this would be a problem? I not sure I understand what

On 12/04/2013 12:38 AM, Christian Hesse wrote: > > Sure. Here we go: > > boot: debug -e bios_boot_linux calc_cmdline_offset > boot: ipxe.lkrn > Loading ipxe.lkrn... ok > cmdline_offset at 0x9f7e0 > Initial memory map: > Could not find location for protected-mode code > Booting kernel failed: Invalid argument > OK, that was a useful clue. I think I know what is

On 06/30/2013 09:45 AM, Gene Cumm wrote: > > My cuent understanding is as follows: HPA is using the label "ancient > kernel" for any kernel that has a hard-coded load address and that > linux.c32 and all 5.xx+ (they're actually the same code) are less > likely to be able to succeed in loading these kernels due to how the > core/linux.c32 responds to the memory map

Is there a way for isolinux/syslinux to execute a list of comboot files immediately at startup, and only once? I have a bunch of small comboot .com files that I want to batch run immediately, then after that do a DISPLAY boot.msg similar in some ways to an autoexec.bat. For example: DEFAULT mycd APPEND ramdisk_size=100000 init=/etc/init lang=us .... TIMEOUT 300 ONSTARTUP mybatch <- ???

First off, Thank you for pxelinux. It works as expected and for my needs it is a most useful project. I apologize in advance for posting this question as it is in part off topic, but I have searched extensively with little results. Are there any alternatives to memdisk for use with pxelinux for booting troublesome floppy images with such applications that fail to use INT 15h, AX=E820h. Having

On Sat, Jun 29, 2013 at 3:04 PM, Ady <ady-sf at hotmail.com> wrote: > If with "ancient kernel" you are referring to the memtest(86|86+) > issue, I don't see the same *exact* problem / behavior. My cuent understanding is as follows: HPA is using the label "ancient kernel" for any kernel that has a hard-coded load address and that linux.c32 and all 5.xx+

Reply All should keep it on the list. On Wed, Sep 9, 2015 at 9:40 PM, <john_cutler at dell.com> wrote: > Gene, > > Thank you for your response I have a follow up to that. > > I have 2 different machines using the same pxe boot for both machines > machine A fails at pxe boot if i don?t have mem=2048m while machine b > will fail if it contains mem=2048m Not

Impact: None. The end of memory needs to be page aligned: if the initrd expands beyond it, Linux kernels won't be able to access the last few bytes. Signed-off-by: Pierre-Alexandre Meyer <pierre at mouraf.org> --- com32/lib/syslinux/load_linux.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/com32/lib/syslinux/load_linux.c b/com32/lib/syslinux/load_linux.c