FYI, one of the biggest “moving targets” of L4T releases is boot code. Everything leading up to and including the kernel load changes rapidly, while the actual Linux o/s does not change much. Anything touching the boot code such that it makes assumptions from another L4T release is probably going to fail. My R32.1 kernel is “4.9.140-tegra”, while I see the script you used is naming “4.9.201-tegra”. My R32.4.3 release also shows kernel “4.9.140-tegra” (there is an initrd involved in R32.4.3 as a default, so this is an example of changing boot requirements depending on L4T release). I don’t currently have an R32.5.x release installed, but what do you see from these commands?
uname -r
head -n 1 /etc/nv_tegra_release
ls -l /boot/Image*
ls -l /boot/initrd*
(I’m thinking there may be a kernel version change used in support of OverlayFS, and perhaps the kernel release and build may be at least at fault for whatever L4T release you are using)
Also, I’m not sure if the forums will upload some file types, but could you attach your “/boot/extlinux/extlinux.conf”? You might need to rename it “extlinux.txt”. I’d also like a copy of any “/boot/initrd*”. Beware that when you run “ls -l /boot/initrd*” a symbolic link will possibly show up with an arrow “initrd.img->...” pointing at some other file, and I do need to know about the sym link, but I only need a copy of the actual initrd file it points at. On my R32.4.1 system I see:
root@nx:/boot# cd
root@nx:~# ls -l /boot/initrd*
-rw-r--r-- 1 root root 5565615 Jun 25 2020 /boot/initrd
lrwxrwxrwx 1 root root 24 Jun 23 2020 /boot/initrd.img -> initrd.img-4.9.140-tegra
-rw-r--r-- 1 root root 15231643 Jan 28 13:51 /boot/initrd.img-4.9.140-tegra
…and in this case I’d be interested in a copy of “/boot/initrd” and “/boot/initrd-4.9.140-tegra”. I am only guessing, but your script may have installed another initrd (probably it would have “4.9.201-tegra” in its name, but that is only a guess).
You could make these files smaller by copying them somewhere else, and then running “bzip2 -9 initrd...” (use the actual file name), and this would compress to become “initrd...something.bz2” (the original file would be renamed the same thing with a “.bz2” file name extension). If you cannot attach these to the forum, then we can find another way to get the files.
Once again, I am only guessing, but I suspect that the issue is somewhere within the combination of kernel file, initrd files, and firmware related to those. All of these are related to boot.
One clue, which I don’t really know if it is involved yet, is that on your boot log I see:
## Flattened Device Tree blob at 83100000
Booting using the fdt blob at 0x83100000
ERROR: reserving fdt memory region failed (addr=0 size=0)
ERROR: reserving fdt memory region failed (addr=0 size=0)
…perhaps a kernel change needed to work with those memory regions is incompatible, and if the init software is mixing up 4.9.140-tegra and 4.9.201-tegra, perhaps it is as simple as getting a consistent kernel configuration both in and out of the initrd. I can unpack any initrd and figure out the flow of boot and hopefully make a guess at anything broken due to different kernel releases and device tree.
