similar to: Outstanding issues?

Hi,, I wud just like to inform that the previous issue of memdisk not booting compressed images still persists !! The release 2.05 that was supposed to fix this issue dint yet solve the problem !! Please, let me know if more info on the problem is required !! Bye, Jassi >From: syslinux-request at zytor.com >Reply-To: syslinux at zytor.com >To: syslinux at zytor.com >Subject:

I have released a SYSLINUX 2.06-pre3. This includes modifications to ppmtolss16 so that it should now be completely compliant with all modes of the PNM specification, raw/plain, PBM/PGM/PPM, with comment lines or without. ftp://ftp.zytor.com/pub/linux/utils/boot/syslinux/Testing/ Please test it out ASAP if at all possible. Since the fixes for -pre1 and -pre2 were pretty essential, I'd like

On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >>> CAUTION: This email originated from outside of the organization. Do

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

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 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote: > > I made some more and more experiments beyond LBA 65535 > > Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size > 34816) > > Does not work: * isolinux-5.01.bin (size 34816) * isolinux-5.10.bin > (size 36864) * isolinux-6.00.bin (size 38912) * isolinux-6.02.bin > (size 43008) > > * I just

Hi all, It has been the case for quite a while that the master tree is unambiguously better than 6.03. I have thus tagged and pushed out a syslinux-6.04-pre2 release, however, due to the issues with continuing to keep the main archive on kernel.org, I have moved the release archive to: https://www.zytor.com/pub/syslinux/ Other than the URL, there is no difference from the kernel.org archive.

This sounds kind of like what happened with me for earlier attempts at using syslinux. Skip using HPA's tools entirely and dd if=vmlinuz of=/dev/fd0 bs=1440k count=1 and make sure that the kernel runs from a floppy disk. There'll be no file system or anything, but you'll make sure that your kernel isn't faulty. If it doesn't execute, then you can avoid the syslinux/pxelinux

I have just pushed out SYSLINUX 3.73-pre2. This prerelease adds support for the fact that the ACPI 3 definition changes the E820 memory detection spec in an incompatible(!!!) manner. Please test it out, as I'd really like to push a 3.73 out as soon as possible. -hpa

On Thu, 2019-02-07 at 06:12 -0500, Gene Cumm wrote: > On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux > <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > > > > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >

It appears that increasing the command line limit to 1023 caused the .bss memory area to overflow. Unfortunately NASM didn't detect this as it ought to have and therefore I didn't catch it as an error. I have dropped the command line limit to 511 characters and released it as 3.09-pre2. This is a release candidate; please test it out and if it works I'll make it 3.09. -hpa

Thanks. Any chance to update the changelog as well. The NEWS file in the archive over at https://www.zytor.com/pub/syslinux/Testing/6.04/ only lists changes for 6.03 On Tue, Feb 5, 2019 at 5:08 PM H. Peter Anvin via Syslinux < syslinux at zytor.com> wrote: > Hi all, > > It has been the case for quite a while that the master tree is > unambiguously better than 6.03. I have thus

HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel

On Jul 8, 2013 5:34 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > 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

This is a minor tweak on 3.11-pre2. If nothing new comes up, I will release this as 3.11 probably early next week. -hpa

Greetings, I have released SYSLINUX 2.05. It is almost identical to 2.05-pre4. I'm about to leave for a trip, so if there are any issues please let me know, but don't expect a response any time soon. -hpa 2.05 is mostly a bug fix/maintenance release. Changes in 2.05: * PXELINUX: Add a default query based on the hardware address of the boot device. This is in lower

Hi hpa, Ady, hpa at zytor.com (H. Peter Anvin) writes: > On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: >> >>> the PXELINUX log line is >>> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >>> Anvin et al), >> >> (snip) >> >> FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good >> for

On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: > >> the PXELINUX log line is >> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >> Anvin et al), > > (snip) > > FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good > for troubleshooting. > > Is the same behavior present when testing with other versions? I would

On 2/7/19 4:03 AM, Joakim Tjernlund wrote: >>> >>> Hi, >>> >>> I merged your tree and added the install patch on top of it. Thank you! >>> >>> -hpa >> >> Is it worth doing another -pre immediately since upgrading gnu-efi >> took such a large leap? My thought is if someone has an issue with >> the new proposed

Hi... I'm Jaspreet. I've been having the memdisk memory overlapping problems since 2.04 Its always seen in the compressed images whereas the uncompressed images works just fine !!! It just stops at the error "Ran out of input data".. Even the memdisk 2.05 dint solve my problem !!! maybe there r still some bugs remaining. !! My motherboard is Intel 845GEBV2 and i've got