similar to: VMWare ESX mboot.c32

Apologies to the OP and all, I got my wires crossed and replied in the wrong thread. On Thu, Feb 5, 2015 at 5:40 PM, Lane < software.research.development at gmail.com> wrote: > I didn't understand that either, why DHCP was not captured. The DHCP > server and the TFTP server are both on the master node. But I do have > another capture file that collects everything and shows

Am 07.02.2015 um 19:50 schrieb Geert Stappers via Syslinux: > On Sat, Feb 07, 2015 at 01:06:06PM -0500, Gene Cumm wrote: >> On Fri, Feb 6, 2015 at 4:57 AM, Holger Baust wrote: >>> Am 06.02.2015 um 07:44 schrieb Geert Stappers: >>>>>> On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: >>>>>>> My IP is 0.0.0.0

Am 06.02.2015 um 07:44 schrieb Geert Stappers via Syslinux: > On Fri, Feb 06, 2015 at 12:08:58AM +0100, Holger Baust via Syslinux wrote: >> Hello... > Welcome the Syslinux project! > > >> Am 05.02.15 um 23:33 schrieb Geert Stappers via Syslinux: >>> On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: > <snip/> >>>> NBP file

Hello... Am 05.02.15 um 23:33 schrieb Geert Stappers via Syslinux: > 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

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 -

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

Hi all! We use pxelinux for booting a diskless Linux from whitch we install all our systems. But we discovered some Problems: - With v1.75 the Kernel is fetched from the TFTP-Server with no problem, but it gets not started on Broadcom NetXtreme with newer PXE-Bioses - With v2.04, pxelinux even seems not to be able to fetch the kernel from the TFTP-Server. This affects also Intel's

On Fri, Feb 06, 2015 at 12:08:58AM +0100, Holger Baust via Syslinux wrote: > Hello... Welcome the Syslinux project! > Am 05.02.15 um 23:33 schrieb Geert Stappers via Syslinux: > > On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: <snip/> > >> > >> NBP file downloaded successfully. > >> Getting chached packet > >> My IP is

On Sat, Feb 07, 2015 at 01:06:06PM -0500, Gene Cumm wrote: > On Fri, Feb 6, 2015 at 4:57 AM, Holger Baust wrote: > > Am 06.02.2015 um 07:44 schrieb Geert Stappers: > >>>> On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: > >>>>> My IP is 0.0.0.0 > >>>>> Any suggestion / hint ? > >>>> The (IMHO) missing

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

On Fri, Feb 6, 2015 at 4:57 AM, Holger Baust via Syslinux <syslinux at zytor.com> wrote: > Am 06.02.2015 um 07:44 schrieb Geert Stappers via Syslinux: >> On Fri, Feb 06, 2015 at 12:08:58AM +0100, Holger Baust via Syslinux wrote: >>> Hello... >> Welcome the Syslinux project! >> >> >>> Am 05.02.15 um 23:33 schrieb Geert Stappers via Syslinux:

On Wed, Oct 7, 2015 at 6:17 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote: > Gene, > > I have tested the binaries provided, it worked for me on DL380 Gen9. > I'm going to test this comprehensively in many different hardware and VM platforms. > I will get back in case I face any issue. > > Thanks a lot. I already found a regression that affects a rather

On Thu, Jun 11, 2015 at 12:46 PM, Michael Glasgow via Syslinux <syslinux at zytor.com> wrote: > Hello all, > > I am seeing the same symptoms described here by Holger Baust on > 5-Feb-2015. The only differences in our setups that I can see are > that Mr. Baust claimed to be using HP DL380p Gen9, whereas I'm on > an Oracle X5-2, and Mr. Baust claimed to be using vlan

Hello all, I am seeing the same symptoms described here by Holger Baust on 5-Feb-2015. The only differences in our setups that I can see are that Mr. Baust claimed to be using HP DL380p Gen9, whereas I'm on an Oracle X5-2, and Mr. Baust claimed to be using vlan tagging, while I am not. Boot log: Copyright (C) 2014, Oracle and/or its affiliates. All rights reserved. Version 2.16.1243.

On Thu, Jun 11, 2015 at 10:30 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 11, 2015 at 12:46 PM, Michael Glasgow via Syslinux > <syslinux at zytor.com> wrote: >> Hello all, >> >> I am seeing the same symptoms described here by Holger Baust on >> 5-Feb-2015. The only differences in our setups that I can see are >> that Mr. Baust

Hi all, I'm terribly sorry that I cannot follow emails in my gmail inbox, since gmail is blocked by China govement, as many of you may have already known. I'm a HP employee in China and we are going through the splitting process, so the blade server I was using were packed up and should be moved into a new room. I will try the latest source if possible. Thank you very much for your works.

On Mon, Feb 9, 2015 at 9:40 AM, Holger Baust via Syslinux <syslinux at zytor.com> wrote: > Am 07.02.2015 um 19:50 schrieb Geert Stappers via Syslinux: >> On Sat, Feb 07, 2015 at 01:06:06PM -0500, Gene Cumm wrote: >>> On Fri, Feb 6, 2015 at 4:57 AM, Holger Baust wrote: >>>> Am 06.02.2015 um 07:44 schrieb Geert Stappers: >>>>>>> On Thu, Feb

The program segments loaded presently in mboot.c only consists of a subset of sections described by the ELF Section Header Table (SHT) in the ELF kernel binary. Segments with useful information often needed for debugging purposes (symbol tables, string tables, etc.) aren't usually present in the program segments and hence not loaded above. Some kernels use this debugging information to

Hi, I have had a VMware ESXi network boot setup for quite some time now. After upgrading from 4.06 to 5.01 (or 5.10-pre3) the network boot fails with the following error: --- snip --- Failed to load COM32 file esxi/5.1.0/mboot.c32 boot: --- snip --- This error is seen for the ESXi bootup only. The default mboot.c32 from syslinux itself doesn't work and this setup has been working with

This is a resend since I didn't hear back from anyone. Hey guys, I noticed the appended ipappend options end up in the beginning of the cmdline argv[] when mboot is entered. mboot then tries to parse the first argument as the name of the kernel module and promptly fails cuz it can't find "ip=.." or "bootif=...". I'm attaching a patch which basically looks for any