similar to: EFI Reboot Timer

On Sat, Jan 16, 2016 at 8:49 AM, Celelibi via Syslinux <syslinux at zytor.com> wrote: > 2016-01-15 22:23 UTC+01:00, Bateman, Matt via Syslinux <syslinux at zytor.com>: >> I am working on setting up a global boot server that serves up files across >> the WAN. I am running into a 5 minute timer that is rebooting my hosts >> before they can complete the kernel and

Hi, Since which version of pxelinux.0 is understood in pxelinux.cfg/default that kernel http://host.lan/netboot/vmlinuz means vmlinuz should be transported over HTTP? Since which version of pxelinux.0 is it possible to boot on UEFI? Those questions elaborated: What I want is fast netboot UEFI servers. What I'm looking for is an advice which version of PXELINUX between version

Op 2014-07-23 om 17:57 schreef Gene Cumm: > On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > > Hi, > > > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > > > kernel http://host.lan/netboot/vmlinuz > > > > means vmlinuz should be transported over HTTP? > > For non-EFI

On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > Hi, > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > kernel http://host.lan/netboot/vmlinuz > > means vmlinuz should be transported over HTTP? For non-EFI systems, this has meant use HTTP services if available (ie, iPXE/gPXE or lwIP as in

Hello. We are using pxelinux for years to boot Linux via PXE since years. Since EFI is spreading, I changed configuration to be able to boot EFI systems. The "Client": - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), FW: 5719-v1.38 The Server: - ISC-DHCP with tfpd-hpa running on Debian 6.x -

On Fri, Jan 15, 2016 at 09:23:44PM +0000, Bateman, Matt via Syslinux wrote: > I am working on setting up a global boot server that serves up files > across the WAN. I am running into a 5 minute timer that is rebooting > my hosts before they can complete the kernel and initrd file download. > > The servers in questions are HP DL60s, and they use UEFI. I am using > syslinux.efi

On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: > Hello. > > We are using pxelinux for years to boot Linux via PXE since years. > Since EFI is spreading, I changed configuration to be able to boot EFI > systems. > > The "Client": > - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available > - NIC used for booting: HP Embedded LOM 331i

2016-01-15 22:23 UTC+01:00, Bateman, Matt via Syslinux <syslinux at zytor.com>: > I am working on setting up a global boot server that serves up files across > the WAN. I am running into a 5 minute timer that is rebooting my hosts > before they can complete the kernel and initrd file download. > > The servers in questions are HP DL60s, and they use UEFI. I am using >

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

I'm still trying fruitlessly to get some sort of local disk boot from syslinux EFI to work... using the 6.03 modules. Tried various combinations of configurations on Gene's test binaries. For reference this is on different models of HP Proliant Gen-9 systems with UEFI. Firmware as up to date as it comes. The UEFI boot order has the hard drives and OS ESPs before the PXE interfaces

Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for

Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 (with an optional Syslinux menu containing multiple entries). Problem (solved) #1: The default directory location for both syslinux.efi is the same. Solution #1: Rename each syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solution #2:

Hello, I am pxebooting a large linux kernel (with embedded initramfs) that is around 250 MB in size. When booting a board in legacy BIOS mode, the pxelinux.0 executable is transferred to the board and takes over, from where loading and booting this large kernel works as expected. Actually, better than expected, as no tftp file size limit is incurred. If I change the BIOS settings to UEFI mode,

On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> -----Original Message----- >> From: Gene Cumm [mailto:gene.cumm at gmail.com] >> Sent: Wednesday, October 07, 2015 4:43 PM >> To: For discussion of Syslinux and tftp-hpa; Geert Stappers >> Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 >> >> On Wed, Oct

Hello I'm currently working on a project to rolling out a new TFTP boot server, for a fairly large infrastructure (>200 servers, >1500 clients, with heterogeneous configurations/setups). We are using Syslinux version 6.03 for all the function within our TFTP server. We are using Ubuntu as our main TFTP server for most deployments and WDS for our

On Mon, Dec 29, 2014 at 04:15:56AM -0800, Patrick Masotta wrote: > On Mon, Dec 29, 2014 at 08:47:54AM +0100, Luke Ledgerd wrote: > > I think I'd like to ask for a feature request to allow pxechn.c32 > > to work with EFI too and to have the ability for PXELinux to have a > > ROOT path variable (kind of like gpxelinux.0) that can either have > > HTTP or TFTP urls.

Gene, As it happened I started working on this again just as you mailed me. It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy. The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to

> Date: Thu, 25 Dec 2014 07:07:52 +0000 > From: Luke Ledgerd <luke.ledgerd at niteco.se> > To: "syslinux at zytor.com" <syslinux at zytor.com> > Subject: [syslinux] Chain-loading from WDS to PXELinux on a different > tftp server > Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se> > Content-Type: text/plain;

All, I was excited to hear about EFI boot support in pxelinux >= 6.00. So I tried it. Not working. I've tried 6.02 (from source), 6.02 (from RPM), early 6.03 (from RPM) and even pulled/compiled latest source from git. 6.0.3-pre7. No love. My boot client can boot/image fine in legacy PXE mode. My dhcpd.conf looks like this: # In initial DHCP DISCOVER packet, PXE client sets option

>> Are there any known problems with the performance of TFTP in (U)EFI >> environments in general or maybe just on VMWare? > I don't believe so. I use Workstation 10.0.2 on Ubuntu 12.04 for the > moment. <stupid question> and have EFI enabled? </stupid> > I hope this is a hex-core host with 6+GiB of RAM. Fedora runs on an AMD A8-6600K at 3Ghz and has 8G of