NETDEV net0 link is down about ipxe HOT 10 OPEN

Get to an iPXE shell and run ifstat, post output.
Also helpful if you have pciid of your NIC(s)

from ipxe.

So your machine has one intel 219LM-7 which is found by iPXE native drivers, and one Marvell 1D6A 07B1 which isn't supported by native drivers. Your simplest workaround is to plug your cable in to the supported NIC ;)

For this nic to be supported development needs to funded... However consider boot with efi instead, and use SNP.efi build of iPXE to use any NIC provided network stack instead.

from ipxe.

How can I get into such a shell?

(Edit: I guess https://ipxe.org/cmdline is the corresponding help page for that)

from ipxe.

Build without embedded script and press ctrl-b, or use shell in embedded script.

from ipxe.

Yup, found out that my ISO is probably with embedded script, so I used the prebuilt version from https://ipxe.org/download.

Below the output.

For PCI ID, I didn't find a quick way to see that on Windows. Not sure whether one of the screenshots from device manager contain the relevant information?

Also note, that we use a separate NIC, not the onboard card.

from ipxe.

Alright. We already thought that this might be a solution, at least as workaround. But then, we couldn't have 10 Gigabit Ethernet.

Are there already Linux drivers available for that NIC? (i.e., how much effort is needed to support it, or how much funding for development)?

We'll also look into EFI. Will that then use the UEFI provided network interface (not an expert on this)?

from ipxe.

Development of iPXE drivers is done from scratch, hardware manuals for the NIC (chip) is required to do the work. See iPXE.org for commercial support.

If the NIC has a ROM that provides an efi network stack, then that will be used in EFI mode if no native support is available.

from ipxe.

Thanks for your quick support! We'll look into it and then decide, which way is the best.

from ipxe.

Adding further information for reference (after contacting commercial support): #370 seems to be the relevant PR for this.

from ipxe.

And this issue might then be a duplicate of #294?

from ipxe.