Displaying 6 results from an estimated 6 matches for "pxelinux_scan_memory".
2017 Mar 05
0
[PATCH] Fix recognition of keeppxe option
...@@ int bios_boot_linux(void *kernel_buf, si
> }
> }
>
> + if (syslinux_filesystem() == SYSLINUX_FS_PXELINUX &&
> + find_argument(cmdline, "keeppxe")) {
> + extern __weak char KeepPXE;
> +
> + KeepPXE = 1; /* for pxelinux_scan_memory */
> + bootflags = 3; /* for unload_pxe */
> + }
> +
> /* Copy the header into private storage */
> /* Use whdr to modify the actual kernel header */
> memcpy(&hdr, kernel_buf, sizeof hdr);
> @@ -495,7 +507,7 @@ int bios_boot_linux(void *ker...
2016 Jun 10
4
[PATCH] Fix recognition of keeppxe option
...arg;
cmdline_size = strlen(cmdline) + 1;
@@ -200,6 +204,14 @@ int bios_boot_linux(void *kernel_buf, si
}
}
+ if (syslinux_filesystem() == SYSLINUX_FS_PXELINUX &&
+ find_argument(cmdline, "keeppxe")) {
+ extern __weak char KeepPXE;
+
+ KeepPXE = 1; /* for pxelinux_scan_memory */
+ bootflags = 3; /* for unload_pxe */
+ }
+
/* Copy the header into private storage */
/* Use whdr to modify the actual kernel header */
memcpy(&hdr, kernel_buf, sizeof hdr);
@@ -495,7 +507,7 @@ int bios_boot_linux(void *kernel_buf, si
dprintf("*** vga=current, not...
2016 Jun 16
2
[PATCH] Fix recognition of keeppxe option
> On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote:
> >
> >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote:
> >> >
> >> >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because
> >> >> > there is no convenient way in new_linux_kernel() to
2016 Jun 16
0
[PATCH] Fix recognition of keeppxe option
...chain.c32 is:
>
> COM32 chain.c32
> APPEND file=freeldr.sys seg=0x0F80 keeppxe
>
> which has been failing since Syslinux v.5.+.
chain.c32 has its own code to handle keeppxe. It looks like it's passing
the correct flag to syslinux_shuffle_boot_rm, but I wonder if the
problem is pxelinux_scan_memory is marking the PXE region as
SMT_TERMINAL?
-- Adam
2013 Jun 29
2
FW: pxelinux 5.x, 6.x memtest problem
It depends on the exact memory map of the system.
Gene Cumm <gene.cumm at gmail.com> wrote:
>On Fri, Jun 28, 2013 at 7:31 PM, H. Peter Anvin <hpa at zytor.com> wrote:
>> On 06/28/2013 04:07 PM, Gene Cumm wrote:
>>> On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com>
>wrote:
>>>> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf
2013 Jul 18
0
FW: pxelinux 5.x, 6.x memtest problem
...eter Anvin wrote:
> It depends on the exact memory map of the system.
Would anyone in this thread care to try out 6.02-pre6? It contains a
bunch of changes that should hopefully get us on the path to fixing this
regression.
If you're feeling adventurous, you could even try,
debug.c32 -e pxelinux_scan_memory
(either from the boot: prompt or via a config option) before invoking
memtest to see whether the PXE code is marking the memory regions as
available for use.
--
Matt Fleming, Intel Open Source Technology Center