similar to: extlinux >= 5.01 menu.c32 timeout doesn't work

Hi, I have the same problem as Helmut with INCLUDE keyword and extlinux 5.10 an later. The following configuration has been tested and worked with extlinux 4.05, 4.06, 5.01 Contents of "boot_label" file DEFAULT 1 --------------------------------------- Contents of "extlinux.conf" file # Enable menu.c32 UI menu.c32 # Disable the boot: prompt PROMPT 0 # 5 sec TIMEOUT 50 #

Le 29/06/2013 12:39, Gene Cumm a ?crit : > On Fri, Jun 28, 2013 at 7:24 AM, Romain Naour <romain.naour at openwide.fr> wrote: >> Hi, >> >> I am using qemu for testing new versions of syslinux before installing on an embedded computer. >> Everything works fine under qemu (1.5.0), so I updated extlinux from 4.06 to 5.11-pre3 on the computer. >> >> I found

On Thu, 27 Jun, at 02:34:43PM, Romain Naour wrote: > Hi, > > Tested with 5.11-pre3. And does it work? ;-) -- Matt Fleming, Intel Open Source Technology Center

On Thu, 27 Jun, at 11:45:28AM, Matt Fleming wrote: > I'll bisect to see why this broke after 5.01. Which is... commit 5447ef821c24b526079ef785d2454ed0efff3e2b Author: Matt Fleming <matt.fleming at intel.com> Date: Thu Feb 28 17:44:54 2013 +0000 ldlinux: Always update ConfigName when opening a config file With the introduction of commit aa7dd29db684 ("ldlinux:

Hallo, I wrote am 26.06.13: > Running "pxelinux": more problems than with 5.10. > 5.00-pre6: all worked fine > 5.10: the start menu (GUI) wasn't shown; "tab" showed the labels, and > the textual menus. Invoking the labels worked. > 6.00: no GUI start menu. "tab" showed the textual menus. Invoking > them seems to do nothing (after some

On Sun, Jun 30, 2013 at 7:42 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 30, 2013 at 1:12 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> Could it be that syslinux is waiting for ever if you use serial mode? >> >> SERIAL 0 115200 > >> TIMEOUT 300 > > Gert, Romain: Have you tried lowering the serial rate or timeout? ie: >

On Fri, Jun 28, 2013 at 7:24 AM, Romain Naour <romain.naour at openwide.fr> wrote: > Hi, > > I am using qemu for testing new versions of syslinux before installing on an embedded computer. > Everything works fine under qemu (1.5.0), so I updated extlinux from 4.06 to 5.11-pre3 on the computer. > > I found that the autostart's timeout does not work. > The timeout

Hi Matt, Your patch fix this bug, thank you. I tested it with qemu and on a physical machine. Best regards, Romain ----- Mail original ----- | De: "Matt Fleming" <matt at console-pimps.org> | ?: "Romain Naour" <romain.naour at openwide.fr> | Cc: syslinux at zytor.com | Envoy?: Lundi 1 Juillet 2013 11:41:54 | Objet: Re: [syslinux] extlinux >= 5.01 menu.c32

I have an issue to boot iPXE with Syslinux 5.01. However, the same method works for Syslinux 4.06. The error messages I got is (see attached png file): =================================== iPXE 1.0.0+git-20120202.f8840ba-3 -- Open Source Network Boot Firmware -- http://ipxe.org Features: VLAN HTTP iSCSI DNS TFTP AoE SRP BzImage COMBOOT ELF MBOOT PXE PXEXT /syslinux/ipxe.lkn: command not found

Hi, Tested with 5.11-pre3. Thanks, Romain ----- Mail original ----- | De: "Matt Fleming" <matt at console-pimps.org> | ?: "Romain Naour" <romain.naour at openwide.fr> | Cc: helmut at hullen.de, "For discussion of Syslinux and tftp-hpa" <syslinux at zytor.com> | Envoy?: Jeudi 27 Juin 2013 14:18:03 | Objet: Re: [syslinux] Syslinux 6.00 released | |

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

Hi, I am wondering how to implement the following customer's requirement : The system is a stand alone embedded system with no operator (with Linux). There is one SSD for the system's usage (and that is where the system loads from). The requirement is to have a duplication of the Linux Image, and that syslinux should calculate CRC of "the first image" (say bzImage_1). If the

Hi, I have had a VMware ESXi network boot setup for quite some time now. After upgrading from 4.06 to 5.01 (or 5.10-pre3) the network boot fails with the following error: --- snip --- Failed to load COM32 file esxi/5.1.0/mboot.c32 boot: --- snip --- This error is seen for the ESXi bootup only. The default mboot.c32 from syslinux itself doesn't work and this setup has been working with

On Thu, 27 Jun, at 10:46:24AM, Romain Naour wrote: > Hi, > > I have the same problem as Helmut with INCLUDE keyword and extlinux 5.10 an later. > The following configuration has been tested and worked with extlinux 4.05, 4.06, 5.01 > > Contents of "boot_label" file > DEFAULT 1 [...] > Thanks to Helmut report, the problem is fixed with: > INCLUDE

Hello there I built development version of syslinux from git 6.04-pre3-3-(sometag) and I am trying to boot a slackware-current system with it. I do not use a separated partition for `/boot`. It's just `/dev/sda1` here for `/` and `/boot` is just a folder. I simply use `mbr.bin` against a DOS partition table and the first partition having the bootable flag. With this layout, the only

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

Hi, I'm new the syslinux and found some bug. For example, when I install a boot file system into /mnt/boot during usb booted system, the extlinux reports the following error. /usr/bin/extlinux -i /mnt/boot /mnt/boot is device proc /usr/bin/extlinux: cannot open device proc But /mnt/boot is mounted on /dev/sda1 and ext3 file system. I read the source code and found the following code in

Hi, Fist of all thanks for all the work you put into gluster this product is fantastic. In our setup, we have to have some kind of nfs authentication. Not beeing able to set the rpc-auth option using the cli was a big draw-back for us. Setting the option auth.allow only set the gluster auth.addr.allow option in the bricks themselves but did not do any good regarding nfs access. Setting the

On 07/05/2013 01:02 PM, Gerardo Exequiel Pozzi wrote: > > 5.00 [pxelinux.0] OK 5.01 [pxelinux.0] OK 5.02-pre1 > [pxelinux.0] OK 5.02-pre2 [pxelinux.0] OK 5.02-pre3 [pxelinux.0] > BAD (freeze, no error messages, 100% CPU used) > > 5.10-pre1 [pxelinux.0] BAD (freeze, no error messages, 100% CPU > used) 5.10-pre2 [pxelinux.0] BAD (Failed to load: ldlinux.c32,

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