mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 23:25:54 +03:00
[GH-ISSUE #839] netboot gets stuck on "iPXE initialising devices" #236
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#236
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 devicesTo Reproduce
Steps to reproduce the behavior:
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
@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.
@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
@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
@kaysond commented on GitHub (Feb 4, 2021):
I'm running FW 15.15.08
@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
@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.
@kaysond commented on GitHub (Feb 5, 2021):
Yeah I'm kinda shocked no one has run into this before...
@tombull89 commented on GitHub (Feb 6, 2021):
I have the same issue, I get stuck on
iPXE initialising deviceswhen 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.@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.
@kaysond commented on GitHub (Mar 8, 2021):
Issue filed upstream