similar to: memtest86+.. How do I load it with pxelinux?

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

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

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

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

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

Hi, I am trying the simple menu passswd in syslinux 3.11, and it seems that if I set the timeout option, the menu passwd is ignored. For example: ----------- default menu.c32 timeout 70 prompt 0 noescape 1 MENU MARGIN 5 MENU MASTER PASSWD $4$x$03NXHMe7QS0Ukxlkyh684LkWdqY$ label local MENU DEFAULT # MENU HIDE MENU LABEL Local operating system (if available) MENU PASSWD localboot 0 label

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

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

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703586 Ideas how to move this forward? Debugging techniques? I''m guessing that it''s specific to my hardware, since I''m not seeing anyone else complaining. Anyone else succeed in doing this on an EliteBook?

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 all, At the end of README.menu there is : "... It is also possible to load a secondary configuration file, to get to another menu. To do that, invoke menu.c32 with the name of the secondary configuration file. LABEL othermenu MENU LABEL Another Menu KERNEL menu.c32 APPEND othermenu.conf" I'm unable to have such a conf. working. tftp logs shows

I have run one full test and got no errors on the memory module. Is it worth keeping it running overnight, just to see if temperature changes will afect the test? Regards, Keith -- In theory, theory and practice are the same; in practice they are not. This email was sent from my laptop with Centos 5.5

Hi! I am currently trying upgrade my bios pxe server with additional uefi support. My current using memtest86+ doesn't seem to support uefi, so I would have to use memtest86, as it supports this. But the memtest86 file itself is an *.efi file. When booting this one directly without syslinux, its working. But I want to launch it later from the syslinux menu. Can I chainload somehow another

El lun, 23-10-2006 a las 16:28 +0400, Kirill Korotaev escribi?: > J.J.Garcia, > > in july 2006 you reported hit of bio.c:99 bug on CentOs kernel: > http://lists.centos.org/pipermail/centos/2006-July/067539.html > > Recently, we also hit the same bug, so maybe you can provide some details on: > 1. whether it is doesn't work for you or was fixed. > 2. how it was

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to create a PXE setup with floppy images for all needed utilities - for example, BIOS flash for various motherboards, disk diagnostic tools, memtest86+, etc. I've gotten memtest86+ to work (using the .bin), and some of the disk images work - however, some disk images will not boot. All of the images were pulled from working, bootable

I've got a production system running CentOS 4 that was rock solid until I upgraded from 2.6.9-55 to 2.6.9-78.0.13 (now running 2.6.9-89.0.11). The system now crashes intermittently after a few weeks. I finally caught the panic message : EDAC MC0: INTERNAL ERROR: channel-b out of range (4 >= 4) Kernel panic - not syncing: MC0: Uncorrected Error Looking at the kernel changelog, I see that

> -----Original Message----- > Hi! > I am currently trying upgrade my bios pxe server with additional uefi support. > My current using memtest86+ doesn't seem to support uefi, so I would have to > use memtest86, as it supports this. > But the memtest86 file itself is an *.efi file. When booting this one directly > without syslinux, its working. > > But I want to