Jetson AGX Orin (JetPack 6 / L4T 36.5.0) stuck at UEFI screen or black screen after NVIDIA logo when booting from NVMe

Hello,

I am experiencing a boot issue with my Jetson AGX Orin 64GB Developer Kit running JetPack 6 (L4T 36.5.0).

System Information

  • Board: Jetson AGX Orin 64GB Dev Kit

  • JetPack / L4T: 36.5.0

  • Boot device: NVMe (Kingston SNV3S1000G 1TB – NV3)

  • Internal eMMC present

  • Secure Boot: Disabled

  • HDMI connected directly to monitor

Problem Description

When powering on the device:

  1. The NVIDIA logo appears.

  2. After that, either:

    • The screen turns completely black

The system does not reach the graphical login screen.

No kernel messages are displayed.

UEFI Observations

  • NVMe is detected correctly:
    UEFI KINGSTON SNV3S1000G

  • Boot order:

    1. NVMe

    2. eMMC

  • I can access:

    1. ESC → Setup

    2. F11 → Boot Manager

    3. S → UEFI Shell

Firmware reports:

Jetson AGX Orin System Firmware 36.5.0

Background Before Failure

The system was previously working normally.

Recent activity before the issue:

  • Installed llama.cpp

  • Downloaded large GGUF models

  • Installed additional AI/LLM packages via apt

No manual firmware update was performed.

Any guidance would be appreciated.

Thank you.

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing a boot issue with your Jetson AGX Orin 64GB Developer Kit running JetPack 6 L4T 3650. The issue is characterized by the NVIDIA logo appearing, followed by either a completely black screen or the system not reaching the graphical login screen, with no kernel messages displayed.

To troubleshoot this issue, let’s consider the following potential causes and solutions:

  1. Boot Order: Ensure that the NVMe drive is set as the first boot device in the UEFI settings. You can access the UEFI settings by pressing the ESC key during boot. Verify that the NVMe drive is listed as the first boot device, and if not, adjust the boot order accordingly.
  2. Secure Boot: Although you mentioned that Secure Boot is disabled, it’s essential to ensure that it’s not causing any issues. Try enabling Secure Boot and set it to UEFI mode to see if it resolves the issue.
  3. NVMe Drive: The NVMe drive is detected correctly, but it’s possible that there’s an issue with the drive itself. Try booting from a different NVMe drive or a USB drive to rule out any issues with the current drive.
  4. Firmware: The firmware reports Jetson AGX Orin System Firmware 3650, which is the latest version. However, it’s possible that there’s a firmware issue specific to your device. Try flashing the firmware again to ensure that it’s up-to-date and correctly installed.
  5. Recent Activity: You mentioned that you installed llamacpp, downloaded large GGUF models, and installed additional AILLM packages via apt. It’s possible that one of these activities caused a conflict or issue with the system. Try removing these packages or rolling back to a previous state to see if it resolves the issue.
  6. Boot Logs: Since you’re not seeing any kernel messages, it’s challenging to diagnose the issue. Try booting with the debug parameter to enable debug logging. This might provide more information about the issue.

To compare with other similar issues, let’s look at some of the other questions in the context:

  • Jetson Orin Nano Developer Kit – Black Screen and Fan Stops After Boot (JetPack 5.1.3): This issue is similar, but it’s specific to the Jetson Orin Nano Developer Kit and JetPack 5.1.3. The solution involves updating the firmware and ensuring that the NVMe drive is set as the first boot device.
  • Booting issue: This issue is also similar, but it’s specific to the Jetson Orin Nano. The solution involves updating the firmware and ensuring that the NVMe drive is set as the first boot device.
  • Assertion issue in UEFI during boot: This issue is specific to the Jetson AGX Orin and involves an assertion issue in the UEFI firmware. The solution involves updating the firmware to the latest version.

In summary, to resolve the boot issue with your Jetson AGX Orin 64GB Developer Kit, try the following:

  1. Ensure that the NVMe drive is set as the first boot device in the UEFI settings.
  2. Enable Secure Boot and set it to UEFI mode.
  3. Try booting from a different NVMe drive or a USB drive.
  4. Flash the firmware again to ensure that it’s up-to-date and correctly installed.
  5. Remove any recently installed packages or roll back to a previous state.
  6. Boot with the debug parameter to enable debug logging.

If none of these solutions resolve the issue, please provide more information about your system configuration and any recent changes you’ve made.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

Hi brayandhf,

(move the topic to the correct category for AGX Orin)

Could you share the full serial console log from your board to check the boot issue?

Could it boot if you remove external NVMe SSD?
Have you tried to reflash the devkit through SDK manager to check if it helps?

Thank you for your guidance.

Here are the updates:

  1. Boot without NVMe

I removed the external NVMe SSD and attempted to boot from internal eMMC only.

The behavior is the same. The UEFI screen shows:

L4TLauncher: Attempting Recovery Boot

After that, the screen turns black and the system does not reach the login screen.

This suggests the issue is not related to the NVMe device.

  1. Serial Console Log

I am in the process of capturing the full serial console log via the debug USB-C port and will share the complete boot log shortly.

  1. Reflash Attempt

I have not yet reflashed the devkit. I wanted to first capture the serial log to better understand the failure point before performing a clean flash.

Please let me know if there are specific boot parameters I should enable for additional verbosity.

Thank you.

It seems trying for the recovery boot rather than Direct boot.
I think it boots into recovery kernel instead.

Please share the serial console log to check if it boots into recovery kernel.