-
Notifications
You must be signed in to change notification settings - Fork 215
PXE support (with iPXE) #87
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
gamozolabs/orange_slice may be an intersting ressource given that it has a PXE bootloader. |
This would be definitely useful. However, I don't have the time to look into this right now, as there are other roadmap items with a higher priority (support for multiboot and UEFI). If someone wants to work on this, I would be happy to provide mentoring for the bootloader integration. |
Shouldn't this just work out of the box? Considering that the bootloader is linked with the kernel, no intermediate steps should be necessary other than flashing the iPXE ROM and setting up an iPXE boot script to download the binary. |
I've opened a pr that implements PXE support for the UEFI bootloader. Is there any demand for implementing Legacy PXE support? I have been working on a simple implementation for a Legacy PXE (see https://github.com/Freax13/bootloader/tree/legacy-pxe). If there's not much demand for it I'm not sure if it's worth integrating: Most newer devices don't implement Legacy PXE anymore, the code's not that pretty (mostly copied from the BIOS bootloader, but different in a few places that make it hard to split out the common parts) and the only platform I have to test behaves wildly differently compared to QEMU. |
Btw if you don't want to deal with TFTP (like me) you can use iPXE with http to load this bootloader. With something like this:
but I will probably just use http since iPXE doesn't support modern certificate algorithms. |
Would it be possible to have support to boot using PXE or iPXE (with iPXE downloading the bootimage.bin using TFTP for instance).
This would require changing the logic to load the files in memory (which iPXE probably takes care of).
This could be poretty helpful for development on real hardware, as it wuld allow to network boot instead of going through the write to USB manipulations.
The text was updated successfully, but these errors were encountered: