Open cleverca22 opened 1 month ago
Pi3B and Pi3B+ seem to be working ok with network boot here with Bookworm 64-bit
Did you upgrade bootcode.bin as well as start.elf
root@pxe:/tftpboot/44bee3d2# sha256sum bootcode.bin 6505bbc8798698bd8f1dff30789b22289ebb865ccba7833b87705264525cbe46 bootcode.bin
start.elf VC_BUILD_ID_USER: dom VC_BUILD_ID_TIME: 15:31:28 VC_BUILD_ID_VARIANT: start VC_BUILD_ID_TIME: May 24 2024 VC_BUILD_ID_BRANCH: bcm2711_2 VC_BUILD_ID_HOSTNAME: buildbot VC_BUILD_ID_PLATFORM: raspberrypi_linux VC_BUILD_ID_VERSION: 4942b7633c0ff1af1ee95a51a33b56a9dae47529 (clean)
Describe the bug tftp client in
start.elf
is brokenTo reproduce attempt to network boot a pi3 with the latest firmware, using https://github.com/openSUSE/xinetd and https://github.com/mmaraya/netkit-ftp/tree/master
Expected behaviour the rpi to actually boot
Actual behaviour all tftp transfers finish and then act like the file didnt exist
Logs If applicable, add the relevant output from
dmesg
or similar.Additional context
unfortunately, a bisect of the firmware repo points to the commit where the pi4 code got merged in, and it has remained broke until latest master