I have a Seeed studio J40 ReComputer that I’m trying nail down the clone process on. My workload requires JP5.1.2. I have my host machine on 20.04 and have successfully performed a backup/restore, but after a restore, the device is sluggish to boot, going from ~30sec-1min up to ~5min.
Here’s my backup/restore process…
sudo apt update
sudo apt install qemu-user-static sshpass abootimg nfs-kernel-server libxml2-utils binutils -y
mkdir -p ~/seeed
cd seeed
wget "https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/release/jetson_linux_r35.4.1_aarch64.tbz2"
wget "https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/release/tegra_linux_sample-root-filesystem_r35.4.1_aarch64.tbz2"
tar xf jetson_linux_r35.4.1_aarch64.tbz2
sudo tar xpf tegra_linux_sample-root-filesystem_r35.4.1_aarch64.tbz2 -C Linux_for_Tegra/rootfs/
cd Linux_for_Tegra/
sudo ./apply_binaries.sh
sudo ./tools/l4t_flash_prerequisites.sh
Now flash host is ready. Move on to performing the backup from our golden device:
cd ~/seeed/Linux_for_Tegra
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b p3509-a02+p3767-0000
Now backup is created, move on to restore:
cd ~/seeed/Linux_for_Tegra
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r p3509-a02+p3767-0000
Verify newly cloned device is good to go: Boots, workload functions, etc and it does but every boot after the restore takes ~5min.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided information, it appears that you are experiencing issues with the boot time of your cloned Jetson Orin NX device, specifically after restoring from a backup. The boot time has increased significantly from 30 seconds to 1 minute to around 5 minutes.
To troubleshoot this issue, let’s break down the steps you’ve taken so far:
You have a host machine running on 2004 and have successfully performed a backup and restore process.
You have flashed the Jetpack on the Seeed Studio J40 ReComputer.
You have performed a backup from your golden device.
You have restored the backup to the new device.
Considering the provided documentation, here are a few potential causes for the slow boot time:
Incorrect configuration: Ensure that the device is configured correctly after the restore process. Check the nvpmodel power mode, as it might have been changed during the restore process. You can try running sudo /usr/bin/jetson_clocks --fan to maximize performance and fan speed.
Fan speed control: Verify that the fan speed is set correctly. You can try setting the fan speed manually using the command echo <PWM_duty_cycle> > /sys/class/hwmon/hwmon<x>/pwm<y>.
Bootloader configuration: Check the bootloader configuration to ensure that it is set correctly. You can try updating the bootloader or checking the bootloader section in the documentation.
DRAM-ECC configuration: Verify that the DRAM-ECC configuration is correct. You can try checking the DRAM-ECC section in the documentation.
SDRAM configuration: Ensure that the SDRAM configuration is correct. You can try checking the SDRAM Configuration section in the documentation.
GPIO configuration: Verify that the GPIO configuration is correct. You can try checking the GPIO section in the documentation.
Secure Boot configuration: Check the Secure Boot configuration to ensure that it is set correctly. You can try checking the Secure Boot section in the documentation.
To further troubleshoot the issue, you can try:
Checking the system logs for any errors or warnings during the boot process.
Running sudo /usr/bin/jetson_clocks --restore to restore the previous settings.
Verifying that the device is running the correct version of Jetpack.
Checking the documentation for any specific requirements or recommendations for the Seeed Studio J40 ReComputer.
It’s also worth noting that the documentation mentions that after running jetson_clocks, you cannot change the nvpmodel power mode without a system reboot. This might be related to the issue you’re experiencing.
In comparison to the provided documentation, it appears that you have followed the correct steps for backing up and restoring the device. However, the slow boot time suggests that there might be an issue with the configuration or settings on the device.
To resolve the issue, you can try the suggested troubleshooting steps and verify that the device is configured correctly. If the issue persists, you may want to consider seeking further assistance from the Seeed Studio community or NVIDIA support.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Ok so serial console cable is a must have, understood. Once that dumped it was obvious to see that the extended boot time was a result of it trying to boot to HTTP/PXE first and taking forever to time out, delaying the boot from the nvme.
After seeing that, I was able to access UEFI settings and change the boot order, reducing the delay significantly.
It brings up a couple more questions though:
Is there a way to automatically set the boot options after the flash process is complete so as to not require this change after every flash?
Is there something special about JP 5.1.2 that would result in it not showing the UEFI splash screen when booting, but still output it to the serial interface? I have a couple devices on 5.1.3 and they display the nice nvidia uefi menu when booting, where as the device on 5.1.2 shows nothing but a black screen during boot.