[ipxe-devel] HPE QLogic NC382i quadport (hp Proliant DL385-G6) does not run iPXE boot.
Christian Nilsson
nikize at gmail.com
Wed Jan 16 18:22:15 UTC 2019
On Wed, 16 Jan 2019 at 16:45, michele pedrini <michelemikymoto at gmail.com> wrote:
>> Wat is the pciid of the card?
> Me:...
> Vendor ID: 0x14e4
> Device ID: 0x1639
So an Broadcom chipset based card, but 0x1639 is not supported by any
native iPXE driver.
This means that without a driver update in iPXE this won't run other
than via chainloaded drivers (such as with an UNDI/SNP/NII from other
ROM)
>
>> Which iPXE binary are you using? (examples: ipxe.pxe, ipxe.lkrn,
>> undionly.kpxe, ipxe.efi, snponly.efi)
> Me:...Tried to boot from the standard ISO, the so called "Bootable ISO image, joust to see if that ISO is able to map hardware and to start the iPXE console.
>
So that is ipxe.iso which is in PCBIOS mode, and that does not have
any alternate drivers available.
>
>> How is that binary started? (chainloading over network)
> Me:...ISO image mounted into the iLO and system started from CD.
>
>> What is the error message or what is it that isn't working for you?
> Me:...after start booting from iPXE ISO, the screen shows "FATAL HUB LINK ERROR" and stops going ahead.
>
That is probably a message from BIOS/Firmware, not from iPXE.
Or more likely the CD which is booted via iLO is connected by USB and
that fails?
You could try building ipxe.usb instead, but again that won't be able
to find your NIC
>> Output of ifstat inside of iPXE shell?
> Me:...after start booting from iPXE ISO, the screen shows "FATAL HUB LINK ERROR" and stops going ahead.
>
> Hoping to be clear and to have correctly answered to your questions.
> I'm looking forward your upgrades.
I'm still not sure if you want PCBIOS or EFI boot, but the best would
still be to use the existing NIC rom, and then chain into
undionly.kpxe or snponly.efi depending on which platform you want,
this needs to be done via DHCP and TFTP.
The other option is to invest in development of native driver in iPXE
for the NIC.
I find it unlikely, but if you are super lucky it might work by adding
PCI_ROM line in src/drivers/net/tg3/tg3.c
More information about the ipxe-devel
mailing list