similar to: Syslinux 4.00-pre20: stabilization phase begins

Hi, HPA: Thanks for the nice new features, appreciate that. Syslinux is always a nice program. For the new version, 3.10-pre20, I encountered a problem now, my client machine uses sis900 chip, and it still can not run simple menu with pxelinux in this version (3.10-pre20). It's same situation as I encountered when I used syslinux 3.07, 3.08 and 3.09. For 3.10-pre20, I compiled in Fedora

I tried isolinux 3.10-pre20 on an Acer Aspire 1501LMi notebook and a Shuttle FS-40 desktop box; it fails on both, simply hanging after printing the first line. Last known good version is 3.10-pre16; will try pre17-pre19 when I have some time.

I think I finally have nailed down the problems with TFTP on the 4.10 branch, and so I have released 4.10-pre20. Please let me know if you have hardware on which 4.05/4.06-pre3 works, and 4.10-pre20 does not. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

> On Fri, Oct 09, 2015 at 10:55:11AM -0500, Clements, James wrote: > > > On Fri, Oct 09, 2015 at 09:45:23AM -0500, Clements, James wrote: > > > > From: Geert Stappers [mailto:stappers at stappers.nl] > > > > Sent: 09 October 2015 15:39 > > > > > On Fri, Oct 09, 2015 at 09:14:55AM -0500, Clements, James wrote: > > > > > > From:

> Ady <ady-sf at hotmail.com> writes: > > >> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: > >> > >>> What actions are _supposed_ to be triggered by each of: > >>> > >>> [Ctrl-J] > >>> [Ctrl-M] > >>> > >>> in the Syslinux command line in version 6.03-pre20? >

Ady <ady-sf at hotmail.com> writes: >> Ady <ady-sf at hotmail.com> writes: >> >>>> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: >>>> >>>>> What actions are _supposed_ to be triggered by each of: >>>>> >>>>> [Ctrl-J] >>>>> [Ctrl-M] >>>>>

> > > On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > Would someone please be so kind to explain / describe the PXERETRY > > > directive? > > > > $ git grep -ni pxeretry > > com32/elflink/ldlinux/readconfig.c:1305: else if (looking_at(p, "pxeretry")) > >

On Wed, Apr 27, 2016 at 7:55 AM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote: >> > Would someone please be so kind to explain / describe the PXERETRY >> > directive? >> >> $ git grep -ni pxeretry >> com32/elflink/ldlinux/readconfig.c:1305: else if

On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > James Clement > > Geert Stappers > > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote: > > > > The screen displays the following: > > > > > > > > PXE Network Boot using IPv4 > > > > .... > > > > Station IP address is 192.168.205.50

> On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > Would someone please be so kind to explain / describe the PXERETRY > > directive? > > $ git grep -ni pxeretry > com32/elflink/ldlinux/readconfig.c:1305: else if (looking_at(p, "pxeretry")) > com32/elflink/ldlinux/readconfig.c:1306: PXERetry = >

I've just pushed out a 6.00-pre1 release. This release includes support for booting EFI machines. The code is currently in the alpha stage. Having said that, you should expect most things to work correctly, including things like the graphical menu. Please help test if you can, and if you find any bugs, please report them. To facilitate building different versions of syslinux.efi (32-bit and

In another mail I discussed my adventures on netbooting syslinux 6.03 and newer from iPXE, either from an emulated rom on qemu/kvm/ovmf or by chainloading via ipxe.efi onto a real HP Proliant DL360 gen9 piece of iron. You might have asked yourself, why chainload? Why not load it directly? Believe me, i tried. First I had to 'fix' my dhcpd.conf because HP probably read the docs on

--- On Thu, 5/31/12, Geert Stappers <stappers at stappers.nl> wrote: > > P.S. > > As usual, eagerly (and patiently) waiting for the HTTP > bits to start > > working properly! ;) :) > > How should I read that??.? Does it mean "I'm waiting to > get time to test" > or do you mean "tested, it doesn't work yet"??? > Anyway, please

On 06/16/2014 07:12 PM, H. Peter Anvin wrote: > On 06/16/2014 02:57 PM, Alexander Perlis wrote: >> Here's what I mean by 'chainloading to install an automatic http prefix': > > The other option is to use a very small default configuration file > containing only: > > default reload > label reload > config http://...path to real config file .../

From: Matt Fleming <matt.fleming at linux.intel.com> This is a series of patches that, * shrink the core by moving things into an ldlinux ELF module * begin wiring up some of the C versions of various functions The core now only contains essential code and loads the ldlinux module to do everything else, like providing a command line interface and loading kernels. The config file parsing

In preparation for 4.00 product release, I have implemented the following changes: a) EXTLINUX is now finally removed as a separate derivative. SYSLINUX and EXTLINUX are fully merged as a single entity. The program extlinux(8) remains as an online nstaller for the SYSLINUX bootloader (ldlinux.sys), since the syslinux program (on Unix) is an offline installer. -> These may get

After 64 prereleases, 626 commits, 52,742 lines of changes, and tons of work by many, many people, Syslinux 4.00 is now officially released. Syslinux 4.00 is the first of a set of major code restructuring releases. The single biggest new features are btrfs and ext4 support, and support for disks larger than 2 TiB. Huge thanks to: - Intel, for sponsoring mine, Alek Du's and Feng Tang's

Ady <ady-sf at hotmail.com> writes: >> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> What actions are _supposed_ to be triggered by each of: >>> >>> [Ctrl-J] >>> [Ctrl-M] >>> >>> in the Syslinux command line in version 6.03-pre20? >> >> They should do nothing special but

Finally, the Syslinux 6.00 release is out. This release includes support for booting from EFI, both from disk-based media and over the network via PXE. Thanks to everyone who has been testing this out. There are some EFI bugs that I'm aware of, * booting Linux kernels without CONFIG_RELOCATABLE doesn't work * 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa *

Hello Ady, On 27.08.2014 16:46, Ady wrote: >> On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>>>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> >> wrote: >>>>>> On 24.07.2014 13:52, Gene Cumm wrote: >> ... >>>>>> Your special build gets the gateway working, but the