similar to: SYSLINUX 3.72-pre2 released

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick

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

On 11/26/2013 01:14 AM, H. Peter Anvin wrote: > On 11/25/2013 06:32 PM, H. Peter Anvin wrote: >> 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: *

Well, it has to happen at some point, so I have officially pushed out SYSLINUX 3.72. The big news in this release is of course the ISOLINUX hybrid mode support (a single image which can be booted either from a CD-ROM or from a hard disk/USB stick), but there are plenty of more goodies in here, including the label listing (not technically completion) on the Tab key. As usual, huge thanks to

We use "isolinux.bin" 3.72 and meet an issue : we put all the files(including config file, kernel and initrd file) under the root directory and some additional normal files in it. If adding enough files in the root directory, the created ISO will fail to boot, hanging at "ISOLINUX 3.72 3.72 ETCD Copyright (C) 1994-2008 H. Peter Anvin". Is this a known issue? Is it fixed in the

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

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

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.

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 not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > Hi all, > > > > It has been the case for

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

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 Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin 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 not click links or open attachments

I have just released SYSLINUX 2.06-pre2. This, I hope, fixes the ISOLINUX directory length bug, a.k.a. the "SRPMS bug." ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ I haven't done anything to the lss tools yet; I was hoping to actually get some sleep tonight. Please, if you have had problems with either SYSLINUX or ISOLINUX lately, please test these out...

I just pushed out Syslinux 3.86-pre2. Absolutely last call for Syslinux 3.86. -hpa

> On 2/6/19 11:44 AM, Joakim Tjernlund wrote: > > On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin wrote: > > > > Great, that tree now against a somewhat old gnu-efi though. > > > > To build against >= 3.0.8 I need to do: > > #gnu-efi >= 3.0.8 has memset/memcpy defined causing multiple syms errors > > sed -i 's/LDFLAGS =/LDFLAGS =

Hi everyone, I have pushed out Syslinux 3.81 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.81 is primarily a bug fix release. The main new features are halt-on-idle support and some features to isohybrid, including the ability to boot from an image written to a partition. Changes in 3.81: *

I just pushed out SYSLINUX 3.73-pre3. The only significant difference over -pre2 was changing MEMDISK to use "safeint" by default. -hpa

With the same configuration an ISOLINUX CD which boots a FreeDOS Floppy image via MEMDISK Syslinux-3.73 crashes in VMWare and also on several newer boxes just after the kernel loading with "invalid OPCODE ...". Same CD with Syslinux-3.72 is working fine. Build environment for 3.72 was gcc-4.3.2 for 3.73 gcc-4.3.3 - any idea what can cause the troubles? --

Hello, I would like to achieve this goal: - start bootloader using syslinux or isolinux from hard drive or CD (not pxe) - init network, get IP address somehow from DHCP - download kernel and initrd from FTP server (hosted on public internet) - boot it Is this currently possible with syslinux or isolinux? I can do it when I boot over PXE from network, using PXELINUX. But I would like to have the

I just released 6.02-pre2 which includes support for booting 32-bit kernels from efi64. I know a number of people wanted this feature, so hopefully it will be tested in various environments. One thing to note is that it is not possible to boot a 32-bit kernel from efi64 via the EFI handover protocol (or from firmware via the EFI boot stub), but the kernel loader in Syslinux is smart enough to