similar to: Problems with NBP chaining

Displaying 20 results from an estimated 700 matches similar to: "Problems with NBP chaining"

2003 Nov 20
1
interested in others' pre-7 NBP experience
Dirk Haus wrote: >What would be the syntax to call other NBPs vom >pxelinux (and has someone already tried it with 3Com`s >Boot Image Editor "imgedit" bootstraps)? I haven`t >found a single word about this feature in the pre-7 >tarball. Mr. Haus, I would very much like to know about your experience invoking another NBP from PXELINUX. I'm trying and failing to
2005 Apr 22
1
loading new config file or an NBP on another server
> - PXELINUX: Support changing the default server and boot file prefix? > - Support loading a new configuration file. What are the time frames/progress on these? Would it be possible for pxelinux.0 to accept command line arguments, like: KERNEL pxelinux.0 APPEND keeppxe conf=<new config file> I also need a way to change the boot server ip that is left in the pxe stack, i.e. I want
2011 Apr 17
2
gpxelinux.0: pxechain to another NBP then RET fails
IRC user ernini first noticed this. We both tried using gpxe/gpxelinux.0 from Syslinux-4.04-pre22. ernini used pxechain to a commercial NBP which RETs (the same as PXELINUX) and failed. Both of us had success with core/pxelinux.0 from Syslinux-4.04-pre22. For my test, I have a VM in VMware Server 2.0.2 (VMHW v7). I loaded gpxelinux.0 using the VM's built-in PXE ROM. Then I used
2003 Dec 30
1
nbp hell
Greetings, I spent the better part of a day tracking down a rather annoying problem. I would like someone more knowledgeable than myself to confirm this diagnosis. I have a RH 8.0 Linux box with three NICS. I had been developing it testing with an XP box. Everything seemed groovy. Today I went to put it into "production" and Win98 clients were having all sorts of problems.
2017 Dec 13
2
core_udp_sendto: no mapping
> > efistub.jpg: > > >>Start PXE over IPv4. > Station IP address is 192.168.201.185 > > Server IP address is 10.210.32.100 > NBP filename is pxelinux.0 > NBP filesize is 6644000 Bytes > Downloading NBP file... > > Succeed to download NBP file. > > Downloading NBP file... > > Succeed to download NBP file. > I will not
2015 Oct 07
3
Hyper-V Gen 2 waiting for ldlinux.e64
> On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > Which makes > > > * text which is on the screen of the netbooting (virtual) machine > > >
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
> On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > > > 13:36:47.974245 IP 192.168.205.50.1939 >
2015 Feb 05
4
Problems with EFI PXE boot on Hp DL380p Gen9
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 -
2017 Dec 06
4
core_udp_sendto: no mapping
On Wed, Nov 29, 2017 at 6:30 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Nov 28, 2017 at 2:38 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: >> On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > >>> On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund >>> <Joakim.Tjernlund at infinera.com> wrote: >>> > On
2015 Jun 11
2
EFI/PXE boot on Oracle X5-2
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.
2015 Feb 05
0
Problems with EFI PXE boot on Hp DL380p Gen9
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
2014 Apr 09
2
questions about pxelinux.
I google that pxelinux is a NBP, and i have there questions after glancing the source code, exactly pxelinux.asm. 1 should NBP specify target processor mode to 16? but also found 'BITS 32'in the pxelinux.asm. 2 should pxelinux.asm assemble into a raw binary file? but found '$(NASM) -f elf' in MAKEFILE under ./core/ dir. 3 can be used to boot window OS? thanks for
2017 Dec 14
1
core_udp_sendto: no mapping
On Wed, 2017-12-13 at 10:34 -0500, Gene Cumm 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. > > > On Wed, Dec 13, 2017 at 7:03 AM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Mon, 2017-12-11 at 08:59 +0100, Joakim
2015 Jul 31
2
EFI: HP + syslinux = crash
In another mail I discussed my adventures on netbooting syslinux 6.03 and newer from iPXE, either from an emulated rom on qemu/kvm/ovmf or by chainloading via ipxe.efi onto a real HP Proliant DL360 gen9 piece of iron. You might have asked yourself, why chainload? Why not load it directly? Believe me, i tried. First I had to 'fix' my dhcpd.conf because HP probably read the docs on
2015 Jan 11
3
PXE Booting EFI
>First, I was looking for the actual values.? >For a VM with (among other values): > config.version = "8" > virtualHW.version = "10" > ethernet0.virtualDev = "e1000" > guestOS = "rhel6-64" > firmware = "efi" > I see: > option-93 = 0x07 > option-60 ="PXEClient:Arch:00007:UNDI:003016" OK I take
2012 Sep 02
2
RFC:documents for new modules; Interest in rewriting exiting documentation
I'm interested in redoing doc/syslinux.txt into 2 AsciiDoc documents, splitting configuration from command. First, however, I'm requesting comments on my recent documentation of several modules I have written. My goal is to be clear, concise, and complete. Acknowledgements and constructive comments are welcome. If it would help to also post converted copies of these documents (HTML,
2015 Jan 11
0
PXE Booting EFI
On Sun, Jan 11, 2015 at 10:32 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > >>First, I was looking for the actual values. >>For a VM with (among other values): > >> config.version = "8" >> virtualHW.version = "10" >> ethernet0.virtualDev = "e1000" >> guestOS = "rhel6-64" >> firmware =
2014 Dec 03
3
vesamenu back to text before booting
On Wed, 3 Dec 2014, H. Peter Anvin wrote: > Ah, depends on the image type. We spoke reset for an NBP though. ?! //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228 54881-235 HRB 5168 (AG Bonn) ? USt-ID (VAT): DE122264941 Gesch?ftsf?hrer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
2008 Nov 10
2
PXE booting BartPE ISO file to Eee Pc
So I've been playing with this for hours and still unable to get everything working properly. In short I'm trying to boot an ISO image created by BartPE over pxelinux. When I attempt to do this it goes directly to a blank screen that just has a blinking cursor. Here's what my setup looks like: pebuilder.iso - the ISO file created from BartPE using WinXP SP2 CD as source but with
2015 Feb 09
1
Problems with EFI PXE boot on Hp DL380p Gen9
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