On 2/18/26 8:31 PM, Alwin Antreich wrote:
FWIW, I'm also working on PXELINUX support, but that has a few quirks.
Tested this with a TFTP server and default iPXE. I.e. copying
`boot.ipxe`, `vmlinuz`, `initrd.img` and the `.iso` file to the TFTP
server root, and then booting off it using the iPXE commandline using:
$ dhcp
$ chain --autofree tftp://<ip-of-tftp-server>/boot.ipxe
In addition, tested this with OPNsense set up such that it automatically
instructs iPXE to load `boot.ipxe` from the set TFTP server, completely
automating an installation from booting the machine to being able to
log into the finished system.
Frank and I have tested your patch and aside from what Hannes already wrote, it
worked nicely. +1
I've tried additionally to PXE boot it with secure boot. It would be awesome if
you could add a signed ipxe.efi.
Sadly I had to go with the shimx64.efi route (my test with the shim command
didn't work :/ ).
We can't do the signing our self, but @f.gruenbichler told me yesterday
that there is finally secureboot support from ipxe upstream since last
november.
Further information and a link to download the signed ipxe-shim can be
found in the pull-request [0]
[0]
https://github.com/rhboot/shim-review/issues/319#issuecomment-3521239969
I also love the idea of a netboot image that could bring down the memory usage
and load time. Otherwise ipxe has sanboot, that might help on the ipxe front.
Thanks
Cheers,
Alwin
