Open Banshee1221 opened 1 year ago
Apparently iPXE scripting lets you use goto
statements now for jumping to previous labels: https://ipxe.org/scripting
but it is an iPXE issue rather than Pi4 UEFI. I have found the boot order to only persist with specific versions of RPI_EFI.fd and not with others, as there was an issue with saving boot variables on USB disks, then with SD cards, then with USB disks again.
Network boot became the priority either way (HTTP).
I've changed my approach and am using MAAS for now. I'm still encountering the first part of this issue.
Whenever MAAS deploys the image to the Pi and the Pi gets cold power cycled, a new ubuntu
entry is sent to the top of the boot order. Ideally, PXE (or whatever your last configured boot entry was) is kept at the top. This appears to happen with 1.31, 1.33 and 1.34. The Pi is configured with Boot Discovery Policy as minimal
UEFI running off of SD card. I have confirmed that the settings persist across reboots.
@TheMindVirus do you know which version of the RPI_EFI.fd
could work?
The versions I based my display mods from were 1.28, 1.29 and 1.33, 1.33 seems to be in common. In each one, especially after boot order fixes, it sometimes started with HTTP boot. https://github.com/TheMindVirus/pftf-rpi4
I am not having luck. I guess I'll have to dig into the code sometime.
I've tried it again:
If I reboot the Pi, warm or cold, a new ubuntu
entry is present at the top of the boot order. Making PXE non-default. This means that there will always have to be physical intervention to reprovision.
I haven't tried 1.35 because I get boot errors with it.
Note: I seem to have been able to work around it by flashing the SD card, booting for the first time and changing the config, shutting down the Pi and setting the SD card to write-protected using a Linux box and this code: https://github.com/BertoldVdb/sdtool (but I also set it on a Windows box with disktool)
With the SD as readonly, I've been able to provision repeatedly with PXE staying at the top and no new ubuntu
entry being added. Not an ideal solution.
Hey, I am experiencing the same. Would love to have a generic Image for all Pis, no matter if they are 4 or 8GB and:
Hi there,
I'm really interested in using this project to provision Raspberry Pi nodes via the Ironic bare-metal provisioner. I've managed to make some progress with it in that I'm able to PXE boot the node and provision the disk image onto a USB attached SSD, but I've noticed 2 issues:
I want the failure of pxe booting to result in the next non-network device to boot instead of it to fall back into the UEFI firmware settings menu.
Is this expected behaviour?