Hi Ron,Here's a simple approach that I just updated for compatibility with Bookworm (in addition to Buster/Bullseye).
These scripts work with Buster/Bullseye/Bookworm (use pxe-add-bw with Bookworm until the bugs in Bookworm are fixed).
Are you aware you can define the PXE client's boot folder name?
from: https://github.com/dwhr-pi/Raspberry-Pi ... ftp_prefixTFTP_PREFIX
In order to support unique TFTP boot directories for each Pi the bootloader prefixes the filenames with a device specific directory. If neither start4.elf nor start.elf are found in the prefixed directory then the prefix is cleared. On earlier models the serial number is used as the prefix, however, on Pi 4 the MAC address is no longer generated from the serial number making it difficult to automatically create tftpboot directories on the server by inspecting DHCPDISCOVER packets. To support this the TFTP_PREFIX may be customized to either be the MAC address, a fixed value or the serial number (default).
Value Description
0 Use the serial number e.g. 9ffefdef/
1 Use the string specified by TFTP_PREFIX_STR
2 Use the MAC address e.g. dc-a6-32-01-36-c2/
Default: 0
Version: 2020-04-16
TFTP_PREFIX_STR
Specify the custom directory prefix string used when TFTP_PREFIX is set to 1. For example:- TFTP_PREFIX_STR=tftp_test/
Default: ""
Max length: 32 characters
Version: 2020-04-16
Also, I didn't even use (nfs)vers=3/4.1, and my 4B's on Bookworm are booting fine. Leaving out (nfs)vers=3/4.1 lets the host and client use the highest NFS version they have in common. Isn't this a better approach?
And, proto=tcp is redundant isn't it, as NFS version 4 requires TCP, and NFS version 3 uses TCP by default?
Statistics: Posted by jeremym — Sat Apr 06, 2024 7:39 pm