I’m using the ‘JETSON ORIN NANO Developer Kit’ with Jetpack 6.0 and Jetson Linux 36.3.
I followed the official instructions to configure L4T and flash the device (Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation). During this process, I used the dtc tool to check the default boot order (UEFI Adaptation — NVIDIA Jetson Linux Developer Guide 1 documentation). The boot order was listed as “usb, nvme, emmc, sd, ufs.”
DefaultBootPriority {
data = "usb,nvme,emmc,sd,ufs";
locked;
The first time I inserted the R8125 module (a PCIe 2.5G network card, MAC address 88C9), the boot order had NVMe as the first priority, which matched the DTB configuration.
After removing the R8125 module and rebooting, the boot order was still normal, with NVMe as the top priority.
However, when I reinserted the R8125 module and rebooted again, an HTTPV6 boot option associated with the R8125 module suddenly appeared at the top of the boot order.
This issue occurs every time. Since we’re planning to use this in our product, it’s concerning. If a customer removes the network card and reboots the device, the boot order will likely change, causing the system to get stuck trying to boot from HTTP for several minutes.
