Network booting no longer works #1605
Comments
|
These log entries suggest that the Kernel and DTB were loaded correctly. The firmware would then start Linux. "Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/bcm2710-rpi-3-b-plus.dtb to 192.168.1.116" What's the failure mode e.g. kernel panic? If you have a USB serial cable then adding "uart_2ndstage=1" to config.txt will show the TFTP logs from VideoCore |
|
The Raspberry Pi 4B does not exhibit the problem. With 5.10.27 or below, the Ethernet port is enabled and the kernel is successfully downloaded and started. With anything above 5.10.27, the Ethernet port is enabled and the kernel is successfully downloaded and started. |
I can confirm what @reraikes is stating. The issue only occurs on my 3B+ units and not on 4B units. In performing further tests, I was able to install and netboot the latest kernel on the 3B+ (5.10.52); however, the issue presents itself when installing the most recent update to raspberrypi-bootloader and its dependencies (1:1.20210527-1). If I remain at the old version of raspberrypi-bootloader (1:1.20210527-1), I do not experience these issues. I am using this as a current workaround. In addition, the 3B+ is able to use the latest bootcode.bin file from the 1:1.20210527-1 update without issue, but the problem seems to be related to the NIC drivers and dependencies loaded in the prior to the linux kernel. I hope this helps. -John |
|
I just tried network booting a Raspberry Pi 2B (v1.1) using an SD card containing only bootcode.bin (the one from 5.10.52 or previous ones all work). The results are the same as with a Raspberry Pi 3B+. 5.10.52 fails after successfully downloading the kernel and starting. After simply downgrading the firmware to 5.10.27 (rpi-update acf3b95a82bdecd28d95c7b294cf5d5a9c3ced31), all is well. |
|
I can reproduce this as reported acf3b95a is ok. The kernel seems to get stuck on boot when using 922deae6d |
|
Please can you post the cmdline/config.txt files and UART logs |
|
No UART logs available. |
|
UART logs: |
|
Thanks. It looks as though NFS boot was working enough to load systemd but something is happening late in boot which fails
|
|
The Raspberry Pi 3B+ boots/runs fine from an SD card (Raspberry Pi OS Lite + apt update + apt full-upgrade + rpi-update). Setting 'arm_freq=600' in config.txt changes nothing with NFS boot. |
|
I have the same problem and I revert my NFS server to the last state before the "apt dist-upgrade", but without success, still not booting with the reverted state... This is the apt/term.log maybe it helps Here, the Raspi hangig around: |
You need to revert the firmware of the OS that is served up to the client, NOT the firmware of the OS running the server itself: rpi-update acf3b95a82bdecd28d95c7b294cf5d5a9c3ced31 It's the client's downloaded OS that has the problem, NOT the server's OS (running the latest on the server is not a problem). Depending on how you have things implemented, this may require doing a chroot to the client OS before running rpi-update (or simply replacing the client's OS on the server with a firmware version no higher than 5.10.27). |
I reverted my /nfs (for / on Raspi) and my /var/lib/tftpboot (for /boot on Raspi) directory on the (ubuntu) server, where all the bootcode etc. resists from the Raspi's. I have to revert the firmware as well - thanks for the hint, so I have to boot from SD card... |
|
hmmm, I tried the downgrade "rpi-update acf3b95a82bdecd28d95c7b294cf5d5a9c3ced31", but it did an upgrade from 5.10.17 to 5.10.27 and it still not working. |
"rpi-update acf3b95a82bdecd28d95c7b294cf5d5a9c3ced31" will install firmware 5.10.27 regardless of the version you are currently on. Anything up to and including 5.10.27 runs perfectly as the client OS for me and the other posters, Anything higher fails. It's the OS firmware files that are downloaded to the client over Ethernet that matter (the server OS can remain at 5.10.52). |
|
...I have no idea, but it looks like, that my tftp service do caching... After I reboot the TFTP/NFS server it took the old files and my Raspi will start now |
|
I know what's happen...
|
|
I think we understand the problem now. Something in the firmware is trying to access a file after the file system has been closed down. If you want to use the latest firmware for testing there's a workaround until the problem is fixed. Put "start_x=1" in config.txt and start_x.elf will be loaded instead - it doesn't suffer from this problem. I just tried this and it seemed to allow the device to boot properly. Can anyone else double check if this works for them? |
|
Putting "start_x=1" in config.txt allows 5.10.52 to boot and run here. |
|
Thanks for confirming that @reraikes |
|
Putting "start_x=1" in config.txt does NOT allow 5.10.52 to boot and run when network booting 64-bit Raspberry Pi OS on a client. Any version up to and including 5.10.27 boots and runs 64-bit Raspberry Pi OS on a client. |
popcornmix
added a commit
that referenced
this issue
Aug 11, 2021
See: raspberrypi/linux#4518 kernel: Revert overlays: Update display GPIO declarations for Goodix See: raspberrypi/linux#4507 kernel: Add midi-uart{2345}-overlay.dts See: raspberrypi/linux#4514 firmware: firmware: Disable VLL loading from file system See: #1605
popcornmix
added a commit
to Hexxeh/rpi-firmware
that referenced
this issue
Aug 11, 2021
See: raspberrypi/linux#4518 kernel: Revert overlays: Update display GPIO declarations for Goodix See: raspberrypi/linux#4507 kernel: Add midi-uart{2345}-overlay.dts See: raspberrypi/linux#4514 firmware: firmware: Disable VLL loading from file system See: raspberrypi/firmware#1605
|
There is a rpi-update available which may fix this issue. Please update and report. |
The latest commit appears to fix Raspberry Pi OS 32-bit. The latest commit does NOT fix Raspberry Pi OS 64-bit. Raspberry Pi OS 64-bit boots/run fine with 5.10.27 or lower. |
|
The situation with network booting Raspberry Pi OS 64-bit is a little different... With "start_x=1" in config.txt: 5.10.46 (23fd671886ba071e04e9787835a05dfc84137679) : OK 5.10.46 (48aef33c6139b7a38013c741f18bf4a1851a1b6d) : OK 5.10.46 (f29ab05611eef385d17675c77190df0b87a0d456) : BROKEN |
|
Salü @popcornmix So looks fine... My Raspi is booting with this combination and the "start_x=1" in config.txt. gruss ivo |
"start_x=1" in config.txt can (should) be removed with this fix. |
Hmmm, no, it's not working |
Then you must not have updated (rpi-update) the firmware that's being downloaded over the network into the client Raspberry Pi. I just tested again (Raspberry Pi OS 32-bit without "start_x=1" in client's config.txt): 5.10.52 (2073a27299fc17cf93152e9c8d9f6998fe484c97) : FAILURE 5.10.52 (3f30de94e5128211a4b3c310cf5a37503af5df96) : SUCCESS |
@reraikes I've updated to 3f30de9 and I put arm_64bit=1 in config. ini. It seems to boot ok and according to "uname -m" is running "aarch64". What problems are you seeing? |
Are you starting with?: Simply adding "arm_64bit=1" to a 32-bit image is not the same. |
|
I just rechecked and the failure is 100% reproducible here. Here are the steps for the client Raspberry Pi OS:
apt update && apt full-upgrade
rpi-update 5.10.46 48aef33c6139b7a38013c741f18bf4a1851a1b6d
rpi-update f29ab05611eef385d17675c77190df0b87a0d456
|
|
It seems to work for me, as does the tip at ad5406d7597e017298474a96323ced593da01457 |
What is "the tip at ad5406d7597e017298474a96323ced593da01457"? Can we get some input from the Raspberry Pi OS developers (@popcornmix), please? |
peterharperuk is a Raspberry Pi OS developer and he fixed the firmware issue. Given the nature of the fix the 64 bit issue sounds like a different problem. Logs from your 64 bit setup showing the exactly where during boot would likely speed up the debugging process. |
cmdline.txt |
|
Please ignore the close/reopen. My mouse pointer jumped as I clicked on "Comment". |
|
@reraikes are you running headless? Can you try with kms driver commented out? |
Yes
That's the source of the problem. With the kms driver commented out, all is well without "start_x=1" in config.txt up through the latest commit: 5.10.52 (ad5406d7597e017298474a96323ced593da01457) |
|
Duplicate of raspberrypi/linux#4457 |
|
I'm going to close this as I believe the original network boot issue is fixed. We have tweaked our testing to catch regressions like this in future. Please reopen if you disagree. |
|
Should I open a new issue for the 64-bit problem? Or is the solution going to be that the KMS driver must be removed in headless network boot installations? |
|
I assumed that issue would be addressed by raspberrypi/linux#4457 ? |
|
I'm confused. I was not aware of raspberrypi/linux#4457 (it was not mentioned here before 10 minutes ago). The problem is still present in the currently available Raspberry Pi OS 64-bit software. Is there a forthcoming update that will incorporate a solution to this problem? It's still broken in the latest updates (apt + rpi-update). |
|
I'll clarify and get back to you. Reopening so I don't forget. |
|
The latest commit (895ca75fe52090a2893725c2e752cce86aeb227f) appears to fix this problem with Raspberry Pi OS 64-bit (dtoverlay=vc4-kms-v3d present in config.txt with no HDMI attached). |
|
Seeing this issue in 5.10.103-v8+ when there is a data HDD attached to the USB port. |
|
Can you report a new issue with logs? This one is confusing and should be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using RPF's "Network boot your Raspberry Pi" tutorial (https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net_tutorial.md), a Raspberry Pi 3B+ client network boots perfectly from a Raspberry Pi 4B server using firmware versions up through and including 5.10.27 (acf3b95a82bdecd28d95c7b294cf5d5a9c3ced31). Monitoring /var/log/daemon.log displays:
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 PXE(eth0) b8:27:eb:6c:4c:16 proxy
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 tags: eth0
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 broadcast response
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 1 option: 53 message-type 2
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 4 option: 54 server-identifier 192.168.1.117
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 17 option: 97 client-machine-id 00:16:4c:6c:b6:16:4c:6c:b6:16:4c:6c:b6:16...
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 32 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/bootsig.bin not found
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/bootcode.bin to 192.168.1.116
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 PXE(eth0) b8:27:eb:6c:4c:16 proxy
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 tags: eth0
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 broadcast response
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 1 option: 53 message-type 2
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 4 option: 54 server-identifier 192.168.1.117
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 17 option: 97 client-machine-id 00:16:4c:6c:b6:16:4c:6c:b6:16:4c:6c:b6:16...
Aug 2 12:21:02 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 32 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/start.elf to 192.168.1.116
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/autoboot.txt not found
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/start.elf to 192.168.1.116
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:21:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.elf not found
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/start.elf to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/fixup.dat to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.elf not found
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/dt-blob.bin not found
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.elf not found
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/bootcfg.txt not found
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/bcm2710-rpi-3-b-plus.dtb to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/bcm2710-rpi-3-b-plus.dtb to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/overlays/overlay_map.dtb to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/overlays/overlay_map.dtb to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/cmdline.txt to 192.168.1.116
Aug 2 12:21:04 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/cmdline.txt to 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery8.img not found
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery8-32.img not found
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery7.img not found
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.img not found
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel8.img to 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/kernel8-32.img not found
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel8.img to 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/armstub8-32.bin not found
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:21:06 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:21:09 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:21:19 raspberrypi dnsmasq-dhcp[548]: 3072402798 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:21:19 raspberrypi dnsmasq-dhcp[548]: 3072402798 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:21:28 raspberrypi dnsmasq-dhcp[548]: 119991861 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:21:28 raspberrypi dnsmasq-dhcp[548]: 119991861 vendor class: dhcpcd-8.1.2:Linux-5.10.27-v7+:armv7l:BCM2835
Aug 2 12:21:28 raspberrypi dnsmasq-dhcp[548]: 119991861 client provides name: raspberrypi
Expected logs are produced in /var/log:
root@raspberrypi:/pxe-root/b66c4c16/var/log# ls -l
total 192
-rw-r--r-- 1 root root 0 May 7 10:00 alternatives.log
drwxr-xr-x 2 root root 4096 Aug 2 00:42 apt
-rw-r----- 1 root adm 986 Aug 2 12:45 auth.log
-rw-r--r-- 1 root root 0 May 7 10:00 bootstrap.log
-rw-rw---- 1 root utmp 0 May 7 10:00 btmp
-rw-r----- 1 root adm 20042 Aug 2 12:45 daemon.log
-rw-r----- 1 root adm 1454 Aug 2 12:45 debug
-rw-r--r-- 1 root root 26956 Aug 2 00:42 dpkg.log
-rw-r--r-- 1 root root 0 May 7 10:00 faillog
-rw-r----- 1 root adm 30517 Aug 2 12:45 kern.log
-rw-rw-r-- 1 root utmp 292292 Aug 2 12:45 lastlog
-rw-r----- 1 root adm 29170 Aug 2 12:45 messages
drwx------ 2 root root 4096 Aug 2 12:45 private
-rw-r----- 1 root adm 51325 Aug 2 12:45 syslog
-rw-r----- 1 root adm 208 Aug 2 12:45 user.log
-rw-rw-r-- 1 root utmp 2304 Aug 2 12:45 wtmp
Beginning with the next commit (922deae6d1ff141d53cf9e703ffecd6f994e9d4e), all further firmware versions including the latest commit (ce56fb43ea36888b94026edd1f08aea78cf32262) fail to start in a network boot scenario. Monitoring /var/log/daemon.log displays:
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 PXE(eth0) b8:27:eb:6c:4c:16 proxy
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 tags: eth0
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 broadcast response
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 1 option: 53 message-type 2
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 4 option: 54 server-identifier 192.168.1.117
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 17 option: 97 client-machine-id 00:16:4c:6c:b6:16:4c:6c:b6:16:4c:6c:b6:16...
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 32 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/bootsig.bin not found
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/bootcode.bin to 192.168.1.116
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 PXE(eth0) b8:27:eb:6c:4c:16 proxy
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 tags: eth0
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 broadcast response
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 1 option: 53 message-type 2
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 4 option: 54 server-identifier 192.168.1.117
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 17 option: 97 client-machine-id 00:16:4c:6c:b6:16:4c:6c:b6:16:4c:6c:b6:16...
Aug 2 12:32:58 raspberrypi dnsmasq-dhcp[548]: 653460281 sent size: 32 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/start.elf to 192.168.1.116
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/autoboot.txt not found
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/start.elf to 192.168.1.116
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:32:58 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.elf not found
Aug 2 12:32:59 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/start.elf to 192.168.1.116
Aug 2 12:32:59 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/fixup.dat to 192.168.1.116
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.elf not found
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/dt-blob.bin not found
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.elf not found
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:33:00 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/bootcfg.txt not found
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/bcm2710-rpi-3-b-plus.dtb to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/bcm2710-rpi-3-b-plus.dtb to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/overlays/overlay_map.dtb to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/overlays/overlay_map.dtb to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/config.txt to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/cmdline.txt to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/cmdline.txt to 192.168.1.116
Aug 2 12:33:01 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery8.img not found
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery8-32.img not found
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery7.img not found
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/recovery.img not found
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel8.img to 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/kernel8-32.img not found
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel8.img to 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: file /pxe-boot/b66c4c16/armstub8-32.bin not found
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: error 0 Early terminate received from 192.168.1.116
Aug 2 12:33:02 raspberrypi dnsmasq-tftp[548]: failed sending /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:33:05 raspberrypi dnsmasq-tftp[548]: sent /pxe-boot/b66c4c16/kernel7.img to 192.168.1.116
Aug 2 12:33:14 raspberrypi dnsmasq-dhcp[548]: 2344883336 available DHCP subnet: 192.168.1.255/255.255.255.0
Aug 2 12:33:14 raspberrypi dnsmasq-dhcp[548]: 2344883336 available DHCP subnet: 192.168.1.255/255.255.255.0
Expected logs are NOT produced in /var/log:
root@raspberrypi:/pxe-root/b66c4c16/var/log# ls -l
total 40
-rw-r--r-- 1 root root 0 May 7 10:00 alternatives.log
drwxr-xr-x 2 root root 4096 Aug 2 00:42 apt
-rw-r--r-- 1 root root 0 May 7 10:00 bootstrap.log
-rw-rw---- 1 root utmp 0 May 7 10:00 btmp
-rw-r--r-- 1 root root 26956 Aug 2 00:42 dpkg.log
-rw-r--r-- 1 root root 0 May 7 10:00 faillog
-rw-rw-r-- 1 root utmp 0 May 7 10:00 lastlog
drwx------ 2 root root 4096 Aug 2 12:33 private
-rw-rw-r-- 1 root utmp 384 Aug 2 12:33 wtmp
The text was updated successfully, but these errors were encountered: