L4T-35.1.0-5.0.2-beta1 - installation messes boot ordrer

[ah-gus]

just installed L4T-35.1.0-5.0.2-beta1,

does installation change boot order?

our system was setup to boot from an NVME ssd.
after installation, boot order has been changed back to emmc boot first and system hanged.
after manually changing boot order, everything works fine.
reporting a possible issue (might actually be an NVIDIA thing)
currently we cannot afford to try to reproduce since we're dealing with technical debts regarding latest JETPACK.

will be happy to report further issues with beta

[ah-gus]

can confirm this happens, when re-installing after dealing with fallout from issue #58

[kicsoft-ai]

Hi ah-gus,
I have tried many times to install different driver versions on a Xavier NX production module with various Jetpack versions installed using the NV SDKManager, and every time it ended with the system failing to boot after installing the driver!
Reading your comment about the boot order being changed from the NVME SSD back to SD/Emmc then I believe this could be same issue.
I have been forced to use NVME SSD boot or else the NX module runs out of space if it is flashed to the internal 16GB EMMC.
How do you manually change the boot order in order to get it to run again after the driver is installed?

[ah-gus]

@kicsoft-ai
If you are using jetpack 5.0.+ (which you probably are since YOU ARE BOOTING FROM Nvme) pressing escape on boot screen should bring you to the uefi menu. There, u think its the last option before last that will get you to the boot order. You should change so it tries nvme first.
Im not next to the kit and don't remomber by hart.
It might be different with the nx

[langenf1]

Have you found a solution for this?