Conversation
majst01
force-pushed
the
snponly
branch
2 times, most recently
from
f9bc342 to
333a13d
Compare
Contributor
Author
|
I turns out that the root cause of this problem, at least on dell servers, is the shear presence of broadcom based network cards, even if they are not involved in the pxe boot process. Removing these cards solved the issue and pxe booting works again with a unmodified version of pixiecore and stand ipxe boot payload. |
majst01
added
the
keep branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Booting with ipxe actually leads to:
According to ipxe/ipxe#1391 using snponly should fix that.