after flashing the device, both NVMe and eMMC are bootable. It boots into the eMMC as expected and the UEFI menu shows the correct order of “usb,emmc,nvme,sd,ufs”. If the NVMe is removed the device boots to the eMMC. But if the NVMe is reinserted this is when the boot order gets reset to the NVIDIA default of “usb,nvme,emmc,sd,ufs”
Yes it boots to the eMMC before I remove the NVMe.
If I do a reboot it will boot to the eMMC, then power off and then reinsert the NVMe, this is when the boot order is reset to defult.
I can then change it at this point in the UEFI menu back to (usb,emmc,nvme,sd,ufs ).
Im hoping that there is a solution so that my boot order always stays the same without having to UEFI menu to reset it every time.
I think the default design prefer using NVMe to boot.
Could you help to verify if the boot-order would change back to " usb,nvme,emmc,sd,ufs" if you re-insert NVMe again?
(i.e. if the boot-order would still change to default after you have configured the boot-order in UEFI menu)
yes after an eMMC boot re-inserting the NVMe drive will result in the UEFI menu showing a boot order of
" usb,nvme,emmc,sd,ufs " even if previously I set it to "usb,emmc,nvme,sd,ufs " within the UEFI menu. This cycle will continue if I remove the NVMe drive, boot to eMMC, power off and re-inserting the NVMe andat this point is when I keep having to set it back to "usb,emmc,nvme,sd,ufs " with in the UEFI menu.
I don’t see how this can be expected behavior as it resets the boot order and this behavior does not account for failure states.
Lets say the Orin has two bootable medias, the eMMC and the NVMe and is configured to a boot order of “usb,emmc,nvme,sd,ufs”. If you are booted from the eMMC and for example the the NVMe gets too hot it can disable the controller on the NVMe and the device will “disappear”. It is totally possible that a user could then power cycle the Orin and it would boot to eMMC as expected. When the NVMe cools down and turns back on any subsequent boots would reset the boot order away from the defined above and boot to the NVMe disregarding the user set boot order.
Hi Kevin, no when an NVMe gets too hot its onboard controller can turn it off (not me unplugging it physically).
the failure state im describing is:
Boot order is: “usb,emmc,nvme,sd,ufs ”
System boots to eMMC as expected
NVMe gets too hot and onboard NVMe controller turns the NVMe drive off (Linux no longer sees the NVMe drive)
User at some point power cycles the Jetson while the NVMe is still off
System still boots to eMMC as expected
At some point the NVMe cools down and the onboard NVMe controller turns the device back on (Linux can now see the device)
User at some point power cycles the Jetson (NVMe is on)
UEFI would add the new device (NVMe) to the Top in boot-order and is reset to the Nvidia default boot-order of “usb,nvme,emmc,sd,ufs ”
System boots to NVMe (this is not our desired behavior as the boot order has changed)
I believe that the UEFI should not reset the boot order as the correct behavior. Our systems our fully remote and the ORIN is in an embedded device. Going in through serial to access the UEFI menu is not an option. Do you know if there is a way to get the UEFI to never change its boot order and always use our current set one of “usb,emmc,nvme,sd,ufs ”
Hi Kevin, there seems to be some mis-understanding here.
Our product is an embedded device, at the mercy of environmental swings. It is not unusual for NVMe devices to enact a sort of self-protection where high temperatures are seen, the device will shutdown - this is what causes the start of our problems, the boot order being over-written.
Going in through serial to access the UEFI menu is not an option.
As mentioned, this is an embedded device, connected to through ethernet access only. Please explain how in this type of setup a serial connection is to be initiated?
Do you know if there is a way to get the UEFI to never change its boot order and always use our current set one of “usb,emmc,nvme,sd,ufs ”
No, it would always detect the current available boot-device and set the boot-order if new added device connected. It should always put new connected device to somewhere(top or bottom).
This is our major problem with the current behaviour - ignoring all of the issues above, we require, and expect, the boot order to behave in a fixed way - much like on a PC, you set the boot order in the bios, and unless the user changes and saves the settings, they will persist.
We do not want the system to randomly adjust the boot order based on the appearance or otherwise of new devices - are you suggesting this is not possible, and also not planned?