similar to: TEXT HELP ... text ... ENDTEXT

> Message: 3 > Date: Fri, 06 Jun 2014 08:13:36 -0700 > From: "H. Peter Anvin" <hpa at zytor.com> > To: Andrew Rae <A.M.Rae at leeds.ac.uk>, "'syslinux at zytor.com'" > <syslinux at zytor.com> > Subject: Re: [syslinux] EFI booting over network - can't then load > anything > Message-ID: <5391DAA0.2050207 at

On 09/05/2013 01:55 AM, Gene Cumm wrote: > On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski > <piotr.karbowski at gmail.com> wrote: > >> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with >> 5.01 it will display list of elements, then allow me to choose which one I >> want to enter. >> >> Even if the include part contain a

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

Hi Brock, I'm trying set full duplex on a server that is being pxeboot/provisioned via autoyast. We want to ensure the duplex is full DURING the autoyast provisioning itself. I've played the syslinux configs to specify the bcm5600 driver, but was having trouble with setting the network options. I've tryed appending them as well, but nothing on the internet seems to indicate that

Conditions to trigger this bug(s): 1_ Boot with ISOLINUX (SYSLINUX seems fine). 2_ Do NOT use the UI directive. 3_ In between TEXT HELP - ENDTEXT directives, use more than one line of text. *** syslinux.cfg start *** DEFAULT vesamenu.c32 PROMPT 0 LABEL pwd1 COM32 pwd.c32 TEXT HELP one line of text two lines of text ENDTEXT *** syslinux.cfg end *** Result: the system ([vesa]menu) hangs.

>> Hi, >> >> We have some problems while network booting thin clients. The type is T5540. >> >> At this moment we are using pxe linux 6.03. >> >> The systems are booting correctly with pxe linux version 6.03-pre14. >> We have seen the same error with version 6.03-pre9. >> >> The error message: >> >> Failed to load ldlinux.c32

Another week, *another* -pre. I'm really planning on this being the last one. The shortlog is appended below. Apart from a better fix for the "disabled menu entry" bug it's only documentation updates. Testing from the last -pre's has been pretty quiet, so as soon as Ady and Matt have tested this one and confirmed that the disabled entry bug is finally gone I'll do the

Hi. I want to create a full-virtualization xen VM with autoyast installation. how can i do that? and how does the configuration file to be configured? I use suse linux 11 SP2. looking forward your replay. Jing. -- View this message in context: http://xen.1045712.n5.nabble.com/how-to-create-a-full-virtualization-xen-VM-with-autoyast-tp5714901.html Sent from the Xen - User mailing

Booting from the USB requires that there is a syslinux directory to boot off of. In EL6, there is only isolinux, which is what booting from a DVD uses. You should be able to copy isolinux to syslinux, rename the files from s/iso/sys/ and then update syslinux.cfg to point to the USB drive to boot from. Here's an example from my setup: ==== LABEL next MENU LABEL ^A) Boot the next device

I'm working with a Soekris net45xx SBC and I'm experiencing problems using any syslinux code (syslinux, pxelinux, extlinux) above version 2.20. I'm interfacing with the Soekris via the serial console port, which is the primary bios console. I've tried different configurations with setting serial in the config file, but no change (though I dont even thing it's getting to reading

I just tried to build syslinux-3.71-pre14-5-gfa6a60e and got the following: make[1]: Leaving directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/dos' make[1]: find-mingw.sh: Command not found make[1]: Entering directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/win32' gcc -Wp,-MT,syslinux.o,-MMD,.syslinux.o.d -W -Wall -Wno-sign-compare -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I.

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.

On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: > >> Hi, > >> > >> We have some problems while network booting thin clients. The type is T5540. > >> > >> At this moment we are using pxe linux 6.03. > >> > >> The systems are booting correctly with pxe linux version 6.03-pre14. > >> We have seen the same error

If there is anything that you think should have been in Syslinux 4.04 which isn't there please holler now. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

I am hoping for some advice regarding another index problem. The code below is intended to assign a value of 'V' if values on certain variables are >= 1, assign a value of 'N' if values on certain variables are >= 1 on other variables and assign a 'O' if values on any variable which have a value <= 0. The outcome of this code is to assign a single

Hi, We have some problems while network booting thin clients. The type is T5540. At this moment we are using pxe linux 6.03. The systems are booting correctly with pxe linux version 6.03-pre14. We have seen the same error with version 6.03-pre9. The error message: Failed to load ldlinux.c32 Boot failed: press a key to retry, or wait for reset... Any idea? Willem

Hello, we have the following problem: - a new Dell Optiplex 740 boots pxelinux.0 - loads the kernel - start to load the miniroot.gz and crashs after loading about 1/5 of the miniroot The tftpd messages are: Feb 21 14:48:32 srv006 atftpd[26225]: Advanced Trivial FTP server started (0.7) Feb 21 14:48:32 srv006 atftpd[26225]: Serving /linux/pxelinux.0 to 10.10.100.113:2070 Feb 21 14:48:32 srv006

> Hi, > > We have some problems while network booting thin clients. The type is T5540. > > At this moment we are using pxe linux 6.03. > > The systems are booting correctly with pxe linux version 6.03-pre14. > We have seen the same error with version 6.03-pre9. > > The error message: > > Failed to load ldlinux.c32 > Boot failed: press a key to retry, or