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

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

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 value is correct but nothing happens. It worked well with extlinux 4.06... I tried with extlinux 5.01, 5.10, 5.11-pre3 and

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

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:

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 #

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

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

Yes. Prior versions (all to 6.01 inclusive) are working very well. ?And yes it fail before invoking chain.c32 (as I said in qemu there is no errors). ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent: Tuesday, July 23, 2013 5:16 PM

Hi. I am currently using EXTLINUX 4.03 in my PC. i wanted to upgrade it to extlinux 5.01. I copied the extlinux binary to my LINUX PC but extlinux binary doesn't work. The isue is the extlinux 5.01 requires GLIBC 2.7 where as the linux GLIBC version i have is 2.5. Please suggest how to run extlinux 5.01 on my linux (2.6.35.6)? Regards, Seetaram

"H. Peter Anvin" <hpa at zytor.com> wrote on Mon, 17 Dec 2007 21:09:09 -0800: > Hi Gordon, > > I just looked at your patch to review it for integration. Unfortunately > it seems to have seriously gotten stale. > Not a surprise, it's been a while on that one - and I'm not actually positive I wrote it against the most current thing available then. (I

? In qemu (virtual machine) it is working ok. ? On?a physsical machine syslinux does not boot at all : ? ? SYSLINUX 6.02 EDD 6.02-pre9 ... ? Boot error. ? ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent: Monday, July 22, 2013 4:37 PM

On 2013-07-24 15:39, Adrian Irimia wrote: > I just tested 6.02-pre10 version. > > On physsical machine it is booting ok now, but chain.c32 result is the same errors : ERR: Primary partition (in MBR) with invalid offset and/or length. > ERR: Cant't find myself on the drive I booted from > Adding 'relax' option to chain.c32 invocation resolves the problem. > Then

? In qemu (virtual machine) it is working ok. ? On?a physsical machine syslinux does not boot at all : ? ? SYSLINUX 6.02 EDD 6.02-pre9 ... ? Boot error. I attached the usb drive info. ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent:

I just tested 6.02-pre10 version. ? On physsical machine it is booting ok now,?but chain.c32 result is the same errors :? ERR: Primary partition (in MBR) with invalid offset and/or length. ? ERR: Cant't find myself on the drive I booted from Adding 'relax' option to chain.c32 invocation resolves the problem. ? In qemu the boot and chaining works ok (without 'relax' option).

Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit LABEL halt com32 poweroff.c32 Does not power off my qemu, it stays open in halt mode. qemu -cdrom ubuntu.iso -boot d -net nic,model=virtio -m 1024 -curses If I boot into ubuntu first and do sudo halt -p it powers off and closes qemu. Can poweroff.c32 do the same as sudo halt -p in ubuntu?

Hello, I've been having a problem trying to boot from first hard drive via pxelinux 5.01 on a HP Proliant server having a SmartArray P220i RAID controller. On other hardware and VMs that i've tried it works. My config file looks like this: label localboot kernel chain.c32 append hd0 Is this a known issue or has anyone experienced this? Thanks, Andrei

On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 27, 2013 at 6:03 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit >> >> LABEL halt >> com32 poweroff.c32 >> >> Does not power off my qemu, it stays open in halt mode. >> qemu -cdrom

Gert Cuykens wrote: > On Fri, Jun 28, 2013 at 2:41 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Thu, Jun 27, 2013 at 6:03 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >>>> Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit >>>>