similar to: using Lua to check gPXE extensions

I'm bringing back an old thread, but I'm still having problem with this: http://etherboot.org/pipermail/gpxe/2010-March/000571.html The summary of that thread is that with gpxelinux.0, on some computers the command LOCALBOOT 0 will hang the computer. Around the same time as the original thread, there was a patch to add localboot -1. Also in the original thread, it was proposed to use

Alexandre Blanchette <blanalex at gmail.com> writes: > On Wed, Dec 10, 2014 at 10:14 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> Alexandre Blanchette <blanalex at gmail.com> writes: >> >>> We are doing a deployment across many sites, we're doing one site at >>> a time and we're bringing a "mobile server" (a laptop,

On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > <blanalex at gmail.com> wrote: > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to > use > > pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE > > script. > > > > The

On Jul 16, 2013 2:01 PM, "Alexandre Blanchette" <blanalex at gmail.com> wrote: > > On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > > <blanalex at gmail.com> wrote: > > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to >

With the BIOS architecture, I was used to boot WinPE from PXELINUX. I used 4 different ways: 1- Calling windows' native PXE loader directly from the config file with a 'kernel' line. 2- Calling windows' native PXE loader with pxechn.c32. 3- Loading an ISO with memdisk 4- iPXE project's wimboot, which relies on memdisk Methods 1 and 2 are slow because loading the bulk of the

In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to use pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE script. The relevant portion of my PXELinux config looks like this: LABEL MDT MENU LABEL ^B - MDT 2012 SP1 com32 pxechn.c32 APPEND undionly.kpxe -o 67.s=ipxe/mdt.ipxe However iPXE doesn't seem to get the option correctly, it goes into

We are doing a deployment across many sites, we're doing one site at a time and we're bringing a "mobile server" (a laptop, really) to keep traffic local instead saturating the WAN link of each site. I'd like to make a script so each client can determine if the mobile server is on the same subnet either with a ping with a zero TTL value, with the ip/netmask and a bit of

I successfully encapsulated option 210 inside 43 with Microsoft DHCP servers. I followed the template in the PXELINUX documentation, at the "using vendor options, handcrafted" heading. On Wed, Jan 15, 2014 at 6:45 AM, Alexandre Blanchette <blanalex at gmail.com>wrote: > A small how-to for encapsulating option 210 inside option 43 on Windows > DHCP servers would be welcome

Correction: Ctrl-J Bypasses labels and tries to load file So at the prompt if one inputs foo<Ctrl-J>, pxelinux looks for a file in the following order: foo.c32 foo.img foo.bss foo.bin foo.bs foo.0 foo On Sat, Feb 22, 2014 at 2:12 PM, Alexandre Blanchette <blanalex at gmail.com>wrote: > On Fri, Feb 21, 2014 at 2:50 AM, Ferenc Wagner <wferi at niif.hu> wrote: >

On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette <blanalex at gmail.com> wrote: > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to use > pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE > script. > > The relevant portion of my PXELinux config looks like this: > > LABEL MDT > MENU LABEL ^B - MDT 2012 SP1 >

A small how-to for encapsulating option 210 inside option 43 on Windows DHCP servers would be welcome then :-) And as far as UEFI x86 system go, one would simply have to create another vendor class with the value PXEClient:Arch:00006 On Wed, Jan 15, 2014 at 12:05 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Jan 14, 2014 at 8:52 PM, Alexandre Blanchette > <blanalex at

I'm currently using Microsoft DHCP to enable PXE booting. I've set options 66 and 67 for the relevant scopes and it's all fine and dandy. However, UEFI machines won't initiate PXE boot, they don't seem to recognize the options. Is there another setting that need to be set? And how to I filter UEFI clients so I set option 67 to the right value (lpxelinux.efi)? -- Alexandre

Is there a way to show some bits of information in the menu, like Syslinux version, MAC address and IP address? When the menu is loaded at startup, this information is quickly erased and is not easily readable. -- Alexandre Blanchette <blanalex at gmail.com>

I've found a way to support PXE booting both UEFI and BIOS architectures with Windows Server DHCP. This method uses a feature introduced in WinServer 2012: DHCP policies. First, in the the DHCP console, at the IPv4 root of the server, create a vendor class named PXEClient (UEFI x64) with the following value: PXEClient:Arch:00007 Then create your configuration for your BIOS clients in your

On Fri, Feb 21, 2014 at 2:50 AM, Ferenc Wagner <wferi at niif.hu> wrote: > Alexandre Blanchette <blanalex at gmail.com> writes: > > > Is there a way to show some bits of information in the menu, like > > Syslinux version, MAC address and IP address? When the menu is loaded > > at startup, this information is quickly erased and is not easily > > readable.

Syslinux 4.01 is a bug fix release for 4.00, but also includes the new experimental lua interpreter, as well as the ifplop module. Changes in 4.01: * ISOLINUX: fix initialization on systems which don't zero low memory. * SYSLINUX/EXTLINUX: fix handing of disk read retries in EDD mode. * ISOLINUX: change the initialization sequence to avoid

Op 20100701 om 18:15 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: 18de1534f9b69fb298a5b56e61919130d875b34b > Gitweb: http://syslinux.zytor.com/commit/18de1534f9b69fb298a5b56e61919130d875b34b > Author: H. Peter Anvin <hpa at linux.intel.com> > AuthorDate: Thu, 1 Jul 2010 18:12:41 -0700 > Committer: H. Peter Anvin <hpa at linux.intel.com> >

Cross-posting to the Syslinux mailing-list. Joakim Schicht wrote: > But part of the question is also about "memdisk raw" vs "memdisk iso". "raw" and "iso" are not mutually exclusive. I think that perhaps you meant "HDD versus El Torito emulation." One can do: LABEL ramwin KERNEL memdisk APPEND raw iso INITRD ramwin.iso > Lets say

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

Hey, It is some real awesome work you are doing. Thanks. I have been trying to use gpxe - pxelinux to boot Linux from a remote location. It works with pxelinux 2.02 and lower. However pxelinux 2.03 and higher return errors and booting is incomplete. Why? syslinux-3.00 gives the following dump and hence the system does not boot. Loading Linux...........................................Ready.