similar to: isolinux 3.10-pre20 doesn't work at all

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

> Hello, > > 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 downloaded InitRD > >>>> still

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

> Hello, > > 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: > >>> As expected. You have a different OUI (the first 3 octets of the MAC > >>> address). Try everything from 6.03-pre18 and then lpxelinux.0 from > >>>

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

Hello, 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 downloaded InitRD >>>> still gets corrupted sometimes. Boot-time is down

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

> -----Original Message----- > From: Matt Fleming [mailto:matt at console-pimps.org] > Sent: 09 July 2014 19:50 > Hey Andrew, > Sorry for the delay. Could you provide the packet dumps of the network > traffic involved in the failed EFI boot? > Hopefully that will allow us to track down exactly what's going wrong. Hi Matt, Appears to all be working under 6.03-pre19 on

> 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

Hi,I have a PXE server with pxelinux 6.02 in my school. It can boot the laptop and desktop computer and it working very well.but I had a problem in all of the IBM THINKPAD SL410 serise laptop,the error message say "pxelinux 6.02 lwIP 2003-10-13 copyright (c) 1994-2013 H. Peter Anvin et al Boot failed:press a key to retry, or wait for reset" when it boot,after a while automaticaly

On 08/11/2014 06:12 AM, Shantanu Gadgil wrote: > Hi all, > > I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. > > The symptom was that booting hangs on client side. > On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. > OR, alternatively it just stops completely. > > My

Hi all, I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. The symptom was that booting hangs on client side. On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. OR, alternatively it just stops completely. My server: OptiPlex 755. BIOS A22 The PXE booting client: OptiPlex 960. BIOS A17 * Things are

On Wed, Aug 27, 2014 at 12:21 PM, Philipp Hahn <hahn at univention.de> wrote: > 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

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.

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

Hi.... >From within Windows 7 NTFS I would like if possible to be able to do either of the following: * Force Windows 7 to reboot into a PXE boot from a TFTP server using a specific PXE/TFTP config file OR * Force Windows 7 to reboot and load a linux kernel from the NTFS partition. This kernel would then use an NFS root filesystem. All of my testing is being done on a Windows 7 NTFS

On Wed, Dec 17, 2014 at 5:54 AM, Willem Bargeman <willem at bargeman.eu> wrote: > On Wed, Dec 17, 2014 at 2:55 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Tue, Dec 16, 2014 at 4:22 PM, Geert Stappers <stappers at stappers.nl> wrote: >>> On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: >>>> >> Hi, >>>>

> > All of my testing is being done on a Windows 7 NTFS virtual machine ins > ESXi 5.5 and I am using syslinux 6.02. I have tried the following on my > Win7 NTFS C: drive: > > * mkdir c:\syslinux > * run 'syslinux.exe --force --mbr --active --directory /syslinux/ --install > C:' This works and I can see 2 hidden files ldlinux.sys and ldlinux.c32 in >

Hi all, I have finally gotten SYSLINUX 3.50 what it feels like feature-complete for release, or something pretty close to it. As a consequence, I am declaring 3.50-pre16 a release candidate. Here is what's news since 3.36: Changes in 3.50: * New keywords allow the type of file to be specified in the configuration file. * It is now supported to load a different

-------------------------------------------- On Mon, 8/11/14, H. Peter Anvin <hpa at zytor.com> wrote: Subject: Re: [syslinux] testing out 6.03 network booting... (6.03-pre19) To: "Shantanu Gadgil" <shantanugadgil at yahoo.com>, "syslinux at zytor.com" <syslinux at zytor.com> Date: Monday, August 11, 2014, 10:21 PM On 08/11/2014 06:12 AM, Shantanu