Jetson AGX Orin Black Screen on Boot

Hello everyone,

I’m having an issue with my Jetson AGX Orin Developer Kit. Initially, I had only the internal eMMC for my OS. Later, I added a 512GB SSD to store Docker container images (no OS on that drive). This worked fine: I could see the 512GB SSD in the Disks application, and I mounted it to store containers.

Recently, I decided to upgrade that SSD to a 2TB model (same brand, just larger capacity). After I powered off the Jetson, removed the 512GB SSD, and installed the 2TB SSD, the system booted to the NVIDIA splash screen but then went to a black screen. Even returning to the 512GB SSD didn’t fix the black-screen problem. Now, the device always boots to a black screen after the splash screen.

What I’ve Tried

  1. UEFI Settings / Boot Order

    • I accessed the UEFI/BIOS by pressing Esc during boot.
    • In Boot Maintenance ManagerBoot OptionsChange Boot Order, I made sure “UEFI eMMC Device” is first.
    • I also tried manually booting from file (BOOTAA64.efi) in the eMMC’s EFI partition.
    • Secure Boot is disabled; L4T Boot Mode is extlinux.
  2. Physical Removal of SSD

    • I physically removed the SSD entirely to ensure the system is only using the eMMC.
    • Still ends in a black screen after the NVIDIA logo.
  3. Logs

    • I see a few “Failed to start NVIDIA specific power script” or “Dependency failed for nvpmodel” lines in the boot logs, but I’m not sure if these are fatal.
    • I suspect I may need a serial console cable to see the full kernel log.
  4. UEFI Observations

    • In the File Explorer, I see two “No Volume Label” partitions on the eMMC:
      • One with standard Linux directories (/boot, /dev, /etc, etc.).
      • Another with EFI/BOOT/BOOTAA64.efi.
    • The external SSD (labeled “TakesiSSD”) just has folders like jetson-containers, Datasets, lost+found, etc.
    • Changing the boot order to only the eMMC or using “Boot from file” hasn’t solved the black screen.

System Details

  • ** Advantech AIR-030 **
  • Internal eMMC for the OS (Jetson Linux).
  • 512GB SSD (original) and 2TB SSD (attempted upgrade) used only for data/docker.
  • 64GB RAM (as shown in UEFI).
  • Secure Boot disabled.
  • UEFI Quick Boot disabled.

Any guidance or suggestions would be greatly appreciated. I’d like to avoid a full reflash if possible, but I’ll do that if there’s no simpler fix. Thank you!

Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks
~0326

Hi,

Do you use the sdk manager to flash your device with your 2TB SSD?

Thanks