similar to: DON'T USE SYSLINUX 1.70

Since I've gotten convinced the really serious PXELINUX/ISOLINUX bug in 1.71 got squashed, I have released 1.72. Again, 1.72 is a bug fix release only. I have some additional rewrites pending before I want to introduce features that use the new core code, but let's make sure it gets usable again, first... -hpa SYSLINUX 1.70 doesn't introduce any new features, but contains a

SYSLINUX 1.70 doesn't introduce any new features, but contains a major rewrite of some of the internals. It also includes some bug fixes. Changes in 1.70: * Major code restructuring. * Relax the conventional memory limits somewhat. * MEMDISK: Set up the "version number string" pointer in the header correctly. * SYSLINUX: Fix, again,

I have released SYSLINUX 1.71 after fixing the total "brown-paper-bag" class bug in 1.70. My best guess is that I checked in the wrong verson of some code. -hpa SYSLINUX 1.70 doesn't introduce any new features, but contains a major rewrite of some of the internals. It also includes some bug fixes. SYSLINUX 1.71 is a bug fix to 1.70. Changes in 1.71: * Fix a

Hello, I just received a serious bug report from Stas Kysel of rPath (with a great test case); it appears that deleted files can confuse extlinux so that it misses files. This is bad. As a result, I have pushed out 3.63-pre3, and intend to make a 3.63 final shortly. I would appreciate any help testing this. Furthermore, I would like to finish the SDI booting module, but I have yet to

I decided the FAT directory-parsing bug was about as serious as it gets, so I decided to push out a new release. However, I decided I feel comfortable enough with the new features (or at least, that they wouldn't break anything else, knock on wood) that I did the patch off the 3.10 development tree and called it 3.05. Changes in 3.05: * New API function "shuffle and

"syslinux-bot for H. Peter Anvin" <hpa at zytor.com> on Wed, 2013/12/04 12:39: > Commit-ID: ef81a3ad54845ffb5ad62714cd62db4740ad5cff > Gitweb: > http://www.syslinux.org/commit/ef81a3ad54845ffb5ad62714cd62db4740ad5cff > Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Wed, 4 Dec 2013 > 12:35:09 -0800 Committer: H. Peter Anvin <hpa at zytor.com>

Hi All, I am still having troubling with PXE. Thanks for replying Shao.I did follow ur suggestions and my results have improved a bit.From Ethereal and TCPdump, I can see that the client sucessfully dowloads the file pxelinux.0 from the server but stops at this point. here is the output of tcpdump tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:05:41.966864 IP

> From: "H. Peter Anvin" <hpa at zytor.com> > To: SYSLINUX at zytor.com > Date: Fri, 05 Aug 2005 10:12:18 -0700 > Subject: [syslinux] Survey: SYSLINUX: 2.13 works, 3.0x don't > Okay, this applies particularly to SYSLINUX, not ISO/PXE/EXTLINUX. > > If you have a system on which 2.13 boots and 3.0x don't, I would like to > get as much information as

On Mon, May 27, 2013 at 2:03 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/27/2013 11:01 AM, Gene Cumm wrote: >> On Mon, May 27, 2013 at 12:04 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> On 05/27/2013 04:49 AM, Gene Cumm wrote: >>>> >>>> 115200 = 0x1C200 so "SERIAL 1 115200" should be setting the bit rate >>>>

On Oct 17, 2014, at 1:30 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > >> On 10/17/2014 12:19 AM, Ferenc Wagner wrote: >> "H. Peter Anvin" <hpa at zytor.com> writes: >> >>> I would like to do a short cycle for 6.04, because 64-bit support for >>> ext4 has come up as a very high priority. Therefore I do not want to

On Fri, 17 Oct 2014, Eric Sandeen wrote: > Date: Fri, 17 Oct 2014 15:04:41 -0400 (EDT) > From: Eric Sandeen <esandeen at redhat.com> > To: H. Peter Anvin <hpa at zytor.com> > Cc: Ferenc Wagner <wferi at niif.hu>, > For discussion of Syslinux and tftp-hpa <syslinux at zytor.com>, > Lukas Czerner <lczerner at redhat.com> > Subject: Re:

On Fri, Oct 17, 2014 at 3:04 PM, Eric Sandeen <esandeen at redhat.com> wrote: > On Oct 17, 2014, at 1:30 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: >> >>> On 10/17/2014 12:19 AM, Ferenc Wagner wrote: >>> "H. Peter Anvin" <hpa at zytor.com> writes: >>> >>>> I would like to do a short cycle for 6.04, because

Sorry Gene, I got the version of binutils is 2.17. I download the latest Binutils to make the *objdump* and *objcopy*. with both of these utilities to create new pxelinux.raw. then, the error message shows me that, objcopy -O binary pxelinux.elf pxelinux.raw ../lzo/prepcore pxelinux.raw pxelinux.bin ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0) make[1]: *** [pxelinux.bin] Error 1

Hi everyone, Kevin Tran of Broadcom just identified a very serious bug in PXELINUX where random parts of the PXE stack would get overwritten by PXELINUX. As a result, I have release SYSLINUX 2.00-pre9 for testing; if you have had problems with PXELINUX **PLEASE** test this version. I will try to make a SYSLINUX 2.00 some time this week if this tests out OK. I will also hunt for similar bugs

Op 2014-02-28 om 15:51 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: a06818de2a4c49bd64a024dd4f4a09a0caf1f0ac > Gitweb: http://www.syslinux.org/commit/a06818de2a4c49bd64a024dd4f4a09a0caf1f0ac > Author: H. Peter Anvin <hpa at linux.intel.com> > AuthorDate: Fri, 28 Feb 2014 15:48:53 -0800 > Committer: H. Peter Anvin <hpa at linux.intel.com> >

Thank you. Can I find any BIOS interrupt to wait on packet arrival NIC interrupt that can be used in COM32 program? And, how do I extend pxelinux.0 that enables this feature in PXE UDP RECEIVE INTERRUPT? Is gPXE has such kind of interrupt? On Thu, Sep 1, 2011 at 12:30 AM, <syslinux-request at zytor.com> wrote: > Send Syslinux mailing list submissions to > syslinux at

FWIW the tcpdump will be a few days at http://rosa.stappers.nl/ff/tcp_w.pcap md5sum a8090ca85202d62ddd5a3d5684b2e8fd tcp_w.pcap ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Thu, 06 Jun 2013 12:49:11 -0700 From: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from upendra.gandhi at gmail.com requires approval Message-ID:

After a few days of troubleshooting, we finally determined why we were having problems. It seems as though the tftp-hpa daemon requires the MTU of the interface it's running on to be >= 1500. We had the MTU set at 1400 (don't ask why) and the PXE client was receiving fragmented packets and failing. As soon as we set it to over 1500, it worked fine. hpa, Could you please update

I tracked down the source of the "invalid kernel image" in 1.73 -- it turns out that in two different places I was accessing word-sized variables as dwords :( Consequently, SYSLINUX would reject valid kernels. PXELINUX/ISOLINUX are unaffected. Thus, SYSLINUX 1.74 is out. Expect a 1.75-pre1 quite soon. I'm working on a rewrite using 32-bit code from the very beginning, which

Is there anything else I can try before I give up? I tried putting the verbosity of tftpd-hpa up to 9 but it's not giving me any extra clues. Can I make syslinux produce more verbose output of messages? Regards, Matt > -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: 26 June 2014 22:20 > To: Ross, Matt; Ady; syslinux at zytor.com > Subject: