Hello,
I have Jetson Orin NX and Jetpack6.2. I backup my orin nx(1) and clone to another orin nx(2). When I open it, Jetson gets stuck at Start HTTP boot over IPv6. Boot order is different in nx(1) (backuped one) but when I clone it to the nx(2) boot order changes. I want to fix this clonening issue, I read Disable IPv6 boot and did everything such as modified l4t_backup_restore.sh and modified L4TConfiguration.dtbo from UEFI Adaptation — NVIDIA Jetson Linux Developer Guide but didn’t change anything. Can you help me?
( I have nvme, httpv4, pxev6, pxev4, httpv6 order)
@KevinFFF
Hi ragony2001,
Are you using the devkit or custom board for Orin NX?
Could you check if configuring “NewDeviceHierarchy” as “bottom” on the Orin NX(1) before creating backup image can help for the correct boot order on Orin NX(2) after restore?
Hello @KevinFFF,
I use devkit. How can I check ‘newdevicehierarch’ is bottom? In where? And olsa can you explain for both devkit and custom board?
You can simply run the following commands for this.
$ sudo chattr -i /sys/firmware/efi/efivars/NewDeviceHierarchy-781e084c-a330-417c-b678-38e696380cb9
$ sudo chmod 777 /sys/firmware/efi/efivars/NewDeviceHierarchy-781e084c-a330-417c-b678-38e696380cb9
$ sudo chown $USER:$USER /sys/firmware/efi/efivars/NewDeviceHierarchy-781e084c-a330-417c-b678-38e696380cb9
$ sudo printf "\x07\x00\x00\x00\x00" > /sys/firmware/efi/efivars/NewDeviceHierarchy-781e084c-a330-417c-b678-38e696380cb9
For this configuration, it should be similar for both the devkit and custom carrier board
Hello @KevinFFF
I tried everything you said but when I restore it to Orin Nx(2), boot orders changes but now it gets UEFI Shell to first boot, not with my order. I write in dtb file: 'data = “nvme,httpv4,pxev6,pxev4,httpv6”;’
I am curious as to whether you actually might need all of those protocols? For example, do you really want to change the order to make IPv6 lower priority, such that you might actually use IPv6 at some time? Since order is not doing what you want it to do, have you considered something like completely removing things like “pxev6” or “httpv6”? Even if this was just as a test, you could remove everything you think you won’t ever use and check if the removal is honored.
Hello @linuxdev
Frankly, my priority is not whether or not ipv6 is available, my priority is to be able to decide on the boot order and clone it this way. Right now, no matter how I define the order, it does not clone the way I specified. In the last cloning I did (even though I didn’t it), UEFI Shell came first in the boot order and I do not want that.
Sorry that the boot-order cannot be transferred to other devices because UEFI relies on hardware ID for boot order; and the NVMe SSDs on each devices are different.
Could you try using efibootmgr to configure the boot-order after restore as L4t_backup_restore restore backup long boot up times - #3 by lhoang
Hello @KevinFFF
So, does the boot order customization mentioned in ’ UEFI Adaptation — NVIDIA Jetson Linux Developer Guide’ only work if it is done for the same device?
I might be wrong, but I think this is saying that partitions and boot order are tied to the partition UID (PUID) or other UUID. Each partition differs in any UID of partition or disk. This is something that could be considered part of the environment. @KevinFFF can you verify if this is a correct interpretation?
If it is, then making it work would require having a cloned MAC address and cloned disk UIDs. If this is correct, then it would perhaps mean that the UIDs in question are in some location which is not part of the clone process itself.
However, if that is the case, perhaps a running Jetson has some ability to access and read that location? Knowing this would allow working on a method to achieve the equivalent on first boot or by modifying the flash.
It would only work for the first boot.
@KevinFFF
Actually, I’m very confused. Everything into consideration, how can I set the boot order between the two different devices (but models are the same) I mentioned at the beginning?
Please refer to my explanation here.
Backup/Restore can work for different devices, but the boot-order or some uefi variables can not be transferred to another device.