Hello everybody,
I would like to consult with you guys regarding the clone-restore process of Jetson AGX Xavier unit.
I use Ubuntu 18.04 machine with SDK Manager.
We have working Jetson AGX Xavier unit with Linux 18.04 and our application suite installed.
I am trying to create the image from the working device and extract it to another Jetson AGX Xavier unit.
Some info:
I succeeded to preform the fresh installation by flash.sh utility exactly as explained in NVIDIA site.
I am able to create an image (by dd command as well as by flash.sh utility) of our working unit and restore it on the new one. All phases are completed successfully without any errors.
Problem:
A new cloned unit freezes at startup. The last row of the startup screen is:
[ OK ] Started Process error reports when automatic reporting is enabled.
By the way, all lines of the startup screen are started with [ OK ].
Some lines from Xorg.0.log file:
(EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
(EE) NVIDIA(0): Failing initialization of X screen 0
(EE) Screens found, but none have a usable configuration
(EE)
Fatal server error:
(EE) no screens found(EE)
I use the same Monitor and HDMI cable for both the source and the target units.
I use the same SDK Manager and flash.sh version for clone/restore.
It looks like I miss some pre- or post-installation steps.
Could you guys help me to figure the issue out? Thank you very much in advance.
AGX is an eMMC model, and this has many partitions. Those non-rootfs (non-APP) partitions are used for booting, and much of this is eventually inherited by the Linux kernel once past the bootloader stages. If that other content does not match in the new AGX, then what the rootfs image expects may not work with that other content.
Note that using the “flash.sh” “-r” option to reuse an image flashes everything, but it uses your rootfs clone for the rootfs/APP. If for some reason you added flash options to just flash the rootfs, and the other partitions are not an exact match to the old system, then failure is expected.
To see the L4T release you can use “head -n 1 /etc/nv_tegra_release” on the working unit which is the donor of the rootfs.
Note that you can see older releases in JetPack/SDKM if you start SDKM like this (you can uncheck all options but L4T flash, and then say to download only, then use the command line flash.sh): sdkmanager --archivedversions
Use the exact L4T release from the donor to completely flash the recipient, and only the “-r” option to reuse a donor clone rootfs.
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks
Is this still an issue to support? Any result can be shared?