did you re-attempt to upgrade as specified by the document?
Looks like the kernel image is either gone or corrupted, and I think the only way to recover from it is to re-flash your device.
did you re-attempt to upgrade as specified by the document?
I’m not sure to understand what you mean. I simply followed the chapter 1.3.2. Upgrade JetPack (but I encounter several issue while doing it, so some commands may have been run several time to make them work)
I think the only way to recover from it is to re-flash your device.
This is what I would like to avoid, it will cost me several days to reinstall my complex environement…
How the kernel image could have disappeared with a simple update? Isn’t possible to get another to replace it manually?
Do not reboot the device after running the below command, and before re-attempting the upgrade.
It should be possible, but the issue is that if your rootfs resides in the eMMC on the module, then there is no way to read/write it with another PC. If it’s on an USB drive/NVMe SSD, then you may simply unplug it, find a PC to mount it, and add the missing file back.
Or, if you really want to preserve the data, you may flash the device again with an USB drive/NVMe SSD as the rootfs, login to the system, mount the eMMC, and recover the kernel image.
No I didn’t reboot after this one, but after having successfully run everything without anymore error.
Note that I had some issue with the parted commands giving errors and that I had to launch some several times, maybe I did a mistake here wich could have erased some data?
Unfortunatly it is.
I don’t really know the procedure to recover the kernel, is it something complex to do?
If I have to, I think I will do a new image on a NVMe this time
If you can flash and login via NVMe/USB drive, then you can directly copy the kernel image and the extlinux folder back to your eMMC. Reboot and select eMMC in UEFI as the booting device.