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 at hotmail.com> wrote: >> >>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>> introduction to Syslinux 5.xx (please allow me to be not strictly >>> accurate in this sentence in this context). >>> >>> Booting with any variant of Syslinux 4.06, but using linux.c32, >>> memtest would fail, which indicated some kind of problem related to >>> the status of Syslinux 5.xx at the time v4.06 was released. >> >> >> PXELINUX 4.06 with Memtest86-4.20 and Memtest86+-4.20 binaries >> (renamed) using LINUX directly works. Using linux.c32: >> "syslinux_boot_linux() failed: Error 0" >> >> PXELINUX 5.10, 5.11-pre3, 6.01-pre5 with binaries LINUX directly: >> "Booting kernel failed: Invalid argument" > > N?meth P?ter : > Would you happen to have a link for the Memtest86+ binaries that you > attempted to use with PXELINUX? >It is presumably the stock memtest-86+ 4.20 binaries. As I wrote elsewhere in the thread, the problem is understood. -hpa
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 at hotmail.com> wrote: >>> >>>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>>> introduction to Syslinux 5.xx (please allow me to be not strictly >>>> accurate in this sentence in this context). >>>> >>>> Booting with any variant of Syslinux 4.06, but using linux.c32, >>>> memtest would fail, which indicated some kind of problem related to >>>> the status of Syslinux 5.xx at the time v4.06 was released. >>> >>> >>> PXELINUX 4.06 with Memtest86-4.20 and Memtest86+-4.20 binaries >>> (renamed) using LINUX directly works. Using linux.c32: >>> "syslinux_boot_linux() failed: Error 0" >>> >>> PXELINUX 5.10, 5.11-pre3, 6.01-pre5 with binaries LINUX directly: >>> "Booting kernel failed: Invalid argument" >> >> N?meth P?ter : >> Would you happen to have a link for the Memtest86+ binaries that you >> attempted to use with PXELINUX? >> > > It is presumably the stock memtest-86+ 4.20 binaries. As I wrote > elsewhere in the thread, the problem is understood.I posted my results from what I thought was "the stock memtest-86+ 4.20 binaries" which I presume to be Syslinux core safety measures. What was different? Why was Nemeth able to load something that should be expected to fail? Was it packed with something like upx (which failed to compress Memtest binaries for me)? -- -Gene
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 at hotmail.com> wrote: >>>> >>>>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>>>> introduction to Syslinux 5.xx (please allow me to be not strictly >>>>> accurate in this sentence in this context). >>>>> >>>>> Booting with any variant of Syslinux 4.06, but using linux.c32, >>>>> memtest would fail, which indicated some kind of problem related >to >>>>> the status of Syslinux 5.xx at the time v4.06 was released. >>>> >>>> >>>> PXELINUX 4.06 with Memtest86-4.20 and Memtest86+-4.20 binaries >>>> (renamed) using LINUX directly works. Using linux.c32: >>>> "syslinux_boot_linux() failed: Error 0" >>>> >>>> PXELINUX 5.10, 5.11-pre3, 6.01-pre5 with binaries LINUX directly: >>>> "Booting kernel failed: Invalid argument" >>> >>> N?meth P?ter : >>> Would you happen to have a link for the Memtest86+ binaries that you >>> attempted to use with PXELINUX? >>> >> >> It is presumably the stock memtest-86+ 4.20 binaries. As I wrote >> elsewhere in the thread, the problem is understood. > >I posted my results from what I thought was "the stock memtest-86+ >4.20 binaries" which I presume to be Syslinux core safety measures. >What was different? Why was Nemeth able to load something that should >be expected to fail? Was it packed with something like upx (which >failed to compress Memtest binaries for me)? > >-- >-Gene-- Sent from my mobile phone. Please excuse brevity and lack of formatting.