I compared your script and the instruction from official documentation, it seems like the difference is the official documentation didn't mention it require client's board serial number. Anyhow I modified my code to add in the last 8 digits of board serial number to the mount points, modified /etc/fstab /etc/exports and cmdline.txt according to your script. However it didn't work.Here's a working implementation: pxe-boot
tcpdump did show the request come in from client but nothing afterwards
Code:
06:07:42.143772 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:1f:02:a5 (oui Unknown), length 32206:07:42.145742 IP 192.168.25.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 31406:07:58.143558 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:1f:02:a5 (oui Unknown), length 32206:07:58.144381 IP 192.168.25.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314When I connect the monitor, it shows this messages
Code:
Boot mode: NETWORK (02) order f145Boot mode: NETWORK (02) order f145USB2[1] 400202e1 connectedUSB2 root HUB port 1 initNETWORK e4:5f:01:1f:02:a5 wait for link TFTP: 0.0.0.0Link readyDHCP src: e4:5f:01:0d:24:96 192.168.25.1DHCP src: e4:5f:01:0d:24:96 192.168.25.1NETBOOT init failedBoot mode: BCM-USB-MSD (05) order f14Any idea what could be the issue based on these error messages?
Statistics: Posted by rasp14 — Thu Mar 21, 2024 6:26 am