search for: memtests

Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file

Hello, FYI. This problem looks similar to the problem I reported in Februari http://www.syslinux.org/archives/2013-February/019517.html Kind regards, Wim. On 06/28/2013 10:02 AM, Matt Fleming wrote: > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: >> Hi guys! >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and >> i have issues to boot it with

> Hello, > > FYI. This problem looks similar to the problem I reported in Februari > http://www.syslinux.org/archives/2013-February/019517.html > > Kind regards, > Wim. > > On 06/28/2013 10:02 AM, Matt Fleming wrote: > > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > >> Hi guys! > >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to

Additional information: I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. So memtest 4.1 and 4.2 worked with pxelinux 4.06 Peter > Date: Fri, 28 Jun 2013 09:02:30 +0100 > From: matt at console-pimps.org > To: coolpet80 at hotmail.com > CC:

Hello, I'm trying to pass the serial port options to memtest86+ using Syslinux 5.01 but is not working. Debugging the memtest86+, the check at main.cpp function static void parse_command_line(void) if (*OLD_CL_MAGIC_ADDR != OLD_CL_MAGIC) return; Is being evaluated to true. What should I do? There is a way to instruct memtest to use the "old way" to pass

Hello, This is my first post to this list. After searching through the archives and google searches I could not find a solution for my memtest problem. In previous versions of pxelinux/gpxelinux (4.04 and 4.06) I could successfully start the memtest utility. But using pxelinux/gpxelinux versions 5.01 and 5.02 the memtest utility does not boot and I get an error message: boot: Loading

Hello list, any try the new memtest86 v3.2 with isolinux 3.11 cd and pxeboot? How is the proper way to chainload memtest86 I was tried: label memtest kernel memtest.bin but, nothing happens just a weird hang (my older versions of memtest hangs too). Anyway chainloading in a floppy image with memdisk on CD or pxeboot was fine but if I use memory to emulate a floppy I was not using this memory

Hi there, ----- Original Message ----- From: koxudaxi at gmail.com To: syslinux at zytor.com Date: 01.04.2013 10:00:27 Subject: Re: [syslinux] Problem with pxelinux 5.0 and memtest > On 04/01/2013 09:28 AM, H. Peter Anvin wrote: >> On 03/31/2013 05:26 PM, Koudai Aono wrote: >>> I ran the test on a x86 emulator is called Oracle VirtualBox. >>> I think it might not be

Hi! At first thanks for your great work! I started to make multiboot CDs 1,5 years ago, with Bart Lagerweij 's utils. I have a problem with the memtest86 floppy image, made by the authors in the .zip file, downloadable from it's homepage, when I use diskemu. Some days ago I found on Bart's page a new method to select boot images on CD with syslinux/isolinux/memdisk. I thought this is

Hi there, I am using the latest version of both syslinux ( acutally isolinux ) and memtest86. I get the error "Cannot load a ramdisk with an old kernel image." the memtest is just called memtest ( renamed from .bin as I read that in the archives that was bad ) My isolinux.cfg is just label memtest kernel memtest I searched google with not much avail. Is this a known issue to you?

On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > Hi guys! > I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and > i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 > works fine both memtest 4.1 and 4.2. > With version 6.00 no error message caught, only writes out dots. Any > keypress does a reboot.With version 5.01 the error message is the

I have written a bash script (see below) to generate bootable SD-USB images using syslinux as booter. The script works OK with versions 3.63 and 3.71, but I get a null pointer error executing /tmp/$SYSLINUX/linux/syslinux -sf -o 16384 SD.img in 3.72. If you execute $ sudo sh SDformat.sh sys then you can test the image easily with qemu $ qemu -hda SD.img ++++++ SDformat.sh

On 06/28/2013 04:25 AM, Ady wrote: > > @Wim and @All, > FWIW, in 2013-February there still were other additional issues with > some kernels, including memory testers, so having a problem to boot > memtest(86|86+|other) might or might not be related to the > "PXE-stack-smasher" bug. > > For example, in v.4.06, the cfg entry could be: > LINUX memtest >

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

HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel

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

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. The pxelinux before version 5, e.g. version 4.06, worked very well with memtest86+ 4.20, all my PXE client machines, including VMWare workstation 9, VirtualBox 4.2, and all the real

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

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.

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