similar to: VFAT support

Hello everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent

> -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: 06 June 2014 16:14 > To: Andrew Rae; 'syslinux at zytor.com' > Subject: Re: [syslinux] EFI booting over network - can't then load anything > > On 06/06/2014 07:27 AM, Andrew Rae wrote: > > Hi all.. > > > > Quick one if someone could show me a line out of their

"H. Peter Anvin" <hpa at zytor.com> writes: > On 06/03/2014 02:59 AM, Ady wrote: > >> Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, >> boot: vesa.c32 >> Undef symbol FAIL: luaL_checklstring >> Failed to load COM32 file vesa.c32 >> boot: >> >> Is there a Lua-related issue? >> >> Is vesa.c32 expecting some kind of

Okay, I have found a workaround for the build problem that affected -pre13 and -pre14, and as a side bonus I have pulled a couple of fixes, including Sebastian's latest gfxboot updates. -hpa

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

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

Hi all, I can't suppress TAB menu prompt and I wonder if this feature is working or not. I'm using extlinux and here is a cut from extlinux.conf: UI menu.c32 prompt 0 MENU TITLE MYPC MENU AUTOBOOT Automatic boot in # second{,s}... MENU NOTABMSG timeout 100 TOTALTIMEOUT 1800 label main MENU DEFAULT MENU LABEL Linux Kernel 3.x ... I'm using latest code from the git tagged as

> "H. Peter Anvin" <hpa at zytor.com> writes: > > > On 06/03/2014 02:59 AM, Ady wrote: > > > >> Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, > >> boot: vesa.c32 > >> Undef symbol FAIL: luaL_checklstring > >> Failed to load COM32 file vesa.c32 > >> boot: > >> > >> Is there a Lua-related issue?

Shantanu, let's continue here. You first noticed this on a Dell OptiPlex 755. I think it covers all Dell OptiPlex/Latitude/Precision models that are PCIe based with Intel LoM (LAN on motherboard) utilizing the BIOS PXE OROM, based on the similarity of these systems. The symptoms are that PXELINUX requests pxelinux.cfg/<UUID> by TFTP (but it might not strictly be a TFTP issue) when not

On Thu, Jun 19, 2014 at 2:51 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > 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. I'd say this is an excellent place to start. I'm getting some similar results here with the precompiled

Hi all.. Quick one if someone could show me a line out of their configuration for these two scenario's . We're trying to do two things via EFI64 network boot & SYSLINUX: * boot a CentOS 6.5 installation vmlinuz/initrd.img combination - machines just reboot after downloading the initrd.img. * boot windows server 2012 r2 PE menu via bootmgfw.efi - unsure of the commands to

Hello everyone, I have released SYSLINUX 3.63. The main update is a fix to EXTLINUX, which would get confused by directories with deleted file entries. Special thanks to Stas Kysel of rPath, Inc. for spotting this problem and giving me an excellent test case; and of course to rPath, Inc. in general for being my employer and being extremely supportive of my SYSLINUX work! I have also

After way too long, a new production release of Syslinux is finally available. Syslinux 4.04 is primarily a bug fix release, but with some new features. Changes in 4.04: * PXELINUX: Fix handling of unqualified DNS names. * PXELINUX: Fix timer bug when PXELINUX might be unloaded (Gene Cumm). * core/writedec.inc: Fix duplicate declaration and overflow

On 11/20/2014 04:46 AM, Ady wrote: > > Patches are welcome here. > > Both repositories are official, but they are sometimes not fully > synchronized during development periods between stable releases. > > Currently the zytor git repo is down (and has been down since the > release of Syslinux 6.03). > > I have updated the wiki page to reflect the current

Hello all, I'm thinking about wrapping up a 3.70 release, even though gpxelinux.0 is technically not feature-complete. I'd like people's opinion on it. -hpa

Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, boot: vesa.c32 Undef symbol FAIL: luaL_checklstring Failed to load COM32 file vesa.c32 boot: Is there a Lua-related issue? Is vesa.c32 expecting some kind of argument? TIA, Ady.

Hello everyone, I have just released SYSLINUX 3.71. This is pretty much a bug fix and hardware support release. The major new *features* are the "initrd" command (syntactic sugar, but it supposedly makes it easier for some tools), the "hide" option to chain.c32, and the ifcpu64.c32 module. As always, special thanks to rPath, Inc., my employer, for the countless hours I

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

Greetings, I''ve had no success with mounting a vfat file system created by a Windows XP guest on a lvm volume. # mount -t vfat /dev/vg1/win1 /mnt/ mount: wrong fs type, bad option, bad superblock on /dev/vg1/win1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg FAT: invalid media value (0xb9) VFS: