[GH-ISSUE #839] netboot gets stuck on "iPXE initialising devices" #236

Closed
opened 2026-02-27 14:50:58 +03:00 by kerem · 10 comments
Owner

Originally created by @kaysond on GitHub (Feb 4, 2021).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/839

Describe the bug
net-booting my R720XD gets stuck oniPXE initialising devices

To Reproduce
Steps to reproduce the behavior:

  1. network boot on an R720XD with Broadcom 57800 10G/GbE 2+2P nic

Expected behavior
netboot loads

Additional context
My netboot setup works totally fine on my VM's, but those are using virtual intel nics. I suspect its some issue with broadcom drivers, but not sure how to further debug

Originally created by @kaysond on GitHub (Feb 4, 2021). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/839 **Describe the bug** net-booting my R720XD gets stuck on`iPXE initialising devices` **To Reproduce** Steps to reproduce the behavior: 1. network boot on an R720XD with Broadcom 57800 10G/GbE 2+2P nic **Expected behavior** netboot loads **Additional context** My netboot setup works totally fine on my VM's, but those are using virtual intel nics. I suspect its some issue with broadcom drivers, but not sure how to further debug
kerem 2026-02-27 14:50:58 +03:00
Author
Owner

@antonym commented on GitHub (Feb 4, 2021):

Have you tried the the undionly or snponly images? I would also check upstream with the iPXE project to see if anyone else has had difficulties with those NICs.

<!-- gh-comment-id:773022963 --> @antonym commented on GitHub (Feb 4, 2021): Have you tried the the undionly or snponly images? I would also check upstream with the iPXE project to see if anyone else has had difficulties with those NICs.
Author
Owner

@kaysond commented on GitHub (Feb 4, 2021):

So I tried the snponly, and it booted and gave me some errors:
https://ipxe.org/err/040ee1
https://ipxe.org/err/2a0860

I think the problem might be related to my vlan settings as it gives me this error when I try to manually set up the vlan: https://ipxe.org/err/7f11e094

image

<!-- gh-comment-id:773070206 --> @kaysond commented on GitHub (Feb 4, 2021): So I tried the snponly, and it booted and gave me some errors: https://ipxe.org/err/040ee1 https://ipxe.org/err/2a0860 I think the problem might be related to my vlan settings as it gives me this error when I try to manually set up the vlan: https://ipxe.org/err/7f11e094 ![image](https://user-images.githubusercontent.com/1147328/106854201-c1936f00-666f-11eb-898b-90eb634bb2c4.png)
Author
Owner

@Firminator commented on GitHub (Feb 4, 2021):

The BCM578xx on earlier FW[1] had issues w/ intermittent PXE boot failures. What firmware is this NIC running? The latest is 15.x.x but not because they were major new features warranting a new major version, but rather because vendors/FW developers changed like 3 times for this chip (Broadcom->Marvell->Qlogic->Cavium with no guarantee that this is the right order).

[1] the 7.12.x train specifically

<!-- gh-comment-id:773608301 --> @Firminator commented on GitHub (Feb 4, 2021): The BCM578xx on earlier FW[**1**] had issues w/ intermittent PXE boot failures. What firmware is this NIC running? The latest is 15.x.x but not because they were major new features warranting a new major version, but rather because vendors/FW developers changed like 3 times for this chip (Broadcom->Marvell->Qlogic->Cavium with no guarantee that this is the right order). [**1**] the 7.12.x train specifically
Author
Owner

@kaysond commented on GitHub (Feb 4, 2021):

vendors/FW developers changed like 3 times for this chip (Broadcom->Marvell->Qlogic->Cavium
I was wondering what the heck was going on with that.

I'm running FW 15.15.08

<!-- gh-comment-id:773641042 --> @kaysond commented on GitHub (Feb 4, 2021): > vendors/FW developers changed like 3 times for this chip (Broadcom->Marvell->Qlogic->Cavium I was wondering what the heck was going on with that. I'm running FW 15.15.08
Author
Owner

@kaysond commented on GitHub (Feb 4, 2021):

Seems like this is definitely an upstream issue related to vlans: https://github.com/ipxe/ipxe/discussions/248

<!-- gh-comment-id:773641312 --> @kaysond commented on GitHub (Feb 4, 2021): Seems like this is definitely an upstream issue related to vlans: https://github.com/ipxe/ipxe/discussions/248
Author
Owner

@Firminator commented on GitHub (Feb 5, 2021):

Awesome. You're on to something there. I'm sure they can figure this out. Because this card was in the default NIC selection list when buying 12G DELL servers the fix will benefit a lot of folks in corporate environments NETBOOT.XYZing... well, unless they still run a flat network.

<!-- gh-comment-id:773705068 --> @Firminator commented on GitHub (Feb 5, 2021): Awesome. You're on to something there. I'm sure they can figure this out. Because this card was in the default NIC selection list when buying 12G DELL servers the fix will benefit a lot of folks in corporate environments NETBOOT.XYZing... well, unless they still run a flat network.
Author
Owner

@kaysond commented on GitHub (Feb 5, 2021):

Awesome. You're on to something there. I'm sure they can figure this out. Because this card was in the default NIC selection list when buying 12G DELL servers the fix will benefit a lot of folks in corporate environments NETBOOT.XYZing... well, unless they still run a flat network.

Yeah I'm kinda shocked no one has run into this before...

<!-- gh-comment-id:773705698 --> @kaysond commented on GitHub (Feb 5, 2021): > Awesome. You're on to something there. I'm sure they can figure this out. Because this card was in the default NIC selection list when buying 12G DELL servers the fix will benefit a lot of folks in corporate environments NETBOOT.XYZing... well, unless they still run a flat network. Yeah I'm kinda shocked no one has run into this before...
Author
Owner

@tombull89 commented on GitHub (Feb 6, 2021):

I have the same issue, I get stuck on iPXE initialising devices when trying to boot my machine. This is a Generation 1 VM running on Hyper-V on Windows 10 Pro x64 20H2. Happens if I boot from the disk image, or pxe boot the DHCP-undionly/DHCP versions. I don't have any VLANs, and the image works fine on my ESXi VMs if I test boot them. I suspect it's due to the driver of the Hyper-V VM but unlike ESXi VMs there's only one network card type avalible, a virtual Intel one.

<!-- gh-comment-id:774370166 --> @tombull89 commented on GitHub (Feb 6, 2021): I have the same issue, I get stuck on `iPXE initialising devices` when trying to boot my machine. This is a Generation 1 VM running on Hyper-V on Windows 10 Pro x64 20H2. Happens if I boot from the disk image, or pxe boot the DHCP-undionly/DHCP versions. I don't have any VLANs, and the image works fine on my ESXi VMs if I test boot them. I suspect it's due to the driver of the Hyper-V VM but unlike ESXi VMs there's only one network card type avalible, a virtual Intel one.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 8, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

<!-- gh-comment-id:792412243 --> @github-actions[bot] commented on GitHub (Mar 8, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Author
Owner

@kaysond commented on GitHub (Mar 8, 2021):

Issue filed upstream

<!-- gh-comment-id:792515973 --> @kaysond commented on GitHub (Mar 8, 2021): Issue filed upstream
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/netboot.xyz#236
No description provided.