similar to: Problems with EFI PXE boot on Hp DL380p Gen9

Displaying 20 results from an estimated 2000 matches similar to: "Problems with EFI PXE boot on Hp DL380p Gen9"

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
2015 Feb 05
2
Problems with EFI PXE boot on Hp DL380p Gen9
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
2015 Feb 06
0
Problems with EFI PXE boot on Hp DL380p Gen9
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
2015 Feb 06
0
Problems with EFI PXE boot on Hp DL380p Gen9
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
2015 Feb 06
2
Problems with EFI PXE boot on Hp DL380p Gen9
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
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 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
2015 Feb 07
0
Problems with EFI PXE boot on Hp DL380p Gen9
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:
2015 Jun 22
1
EFI: PXE: "My IP is 0.0.0.0"
On Mon, Jun 22, 2015 at 6:03 AM, S. Schauenburg <s.schauenburg at gmail.com> wrote: > Ady2 suggested to me on IRC to add additional information to the ML. > > With BIOS P89 v1.32 (03/05/2015) I saw errors from core_udp_sendto: > Getting cached packet > My IP is 0.0.0.0 > core_udp_sendto: stalling on configure with no mapping > core_udp_sendto: stalling on configure with
2015 Jun 22
5
EFI: PXE: "My IP is 0.0.0.0"
Hello Gene, thanks a lot for your patch! It doesn't work yet, but I have some more information. Before the patch, the boot sequence ended with the following: NBP file download successfully. Getting cached packet My IP is 0.0.0.0 After the patch it ended with the following (note that the IP is the same as the Station IP address): NBP file download successfully. LibLocateHandle returned
2015 Feb 07
2
Problems with EFI PXE boot on Hp DL380p Gen9
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
2015 Jun 12
0
EFI/PXE boot on Oracle X5-2
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
2015 Jun 15
1
EFI/PXE boot on Oracle X5-2
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
2015 Feb 09
0
Problems with EFI PXE boot on Hp DL380p Gen9
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
2003 Jun 26
4
Problems with eepro100 or BroadCom NetXtreme and syslinux 2.04
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
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
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 Oct 09
1
syslinux64.efi boot problems
Hi there, I've been trying to boot some new machines via uEFI and it does not work, as you can see below. From my hunting around on the mailing list, there may have been a bunch of fixes that have been committed that have some bearing on uEFI, and even some on the mailing list that appear to be aimed at solving similar problems. However, I can't manage to build a new one based on the
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
2017 Nov 27
5
core_udp_sendto: no mapping
Bringing the discussion to the list. You stated you see the following on your Lenovo ThinkPad T470s with UEFI firmware N1WET41W (1.20 date: 10/17/2017): core_udp_sendto: stalling on configure with no mapping OUI 54-E1-AD lspci -s 0:1f.6 -v 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21) Subsystem: Lenovo Ethernet Connection (4) I219-V