No Display Output on NVIDIA Jetson AGX Orin 64GB After Flashing JetPack 6.2

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hello,

I’m using the NVIDIA Jetson AGX Orin 64GB Developer Kit, and I successfully flashed JetPack 6.2 onto the board using SDK Manager.

However, I’m encountering an issue where, after flashing, there is no display output when connecting the device to a monitor via HDMI (with DisplayPort adaptor). The monitor just shows “No Signal.”

Here’s what I’ve checked so far:

  • The flashing process completed successfully with no errors.
  • I’m using the original power supply that came with the developer kit.
  • The HDMI cable and the displayport adaptor works fine with other devices.
  • I’ve tested multiple monitors — same result.

Is there any additional step required after flashing to enable video output?
Are there any known issues with HDMI/DP output on JetPack 6.2 for the AGX Orin?

Any help would be greatly appreciated.

Thanks in advance!

3

Please use a native DP monitor. We notice some DP-HDMI adapter not work on rel-36/jetpack6.

4

Which kind of adapter are you using ? Any brand name or model ID?

5

Hello,
I tried the Jetson with a new monitor using a brand-new DisplayPort (DP) cable directly.
The result is the same. Still no image. The cable is from the brand Cablexpert.
Any other ideas?

6

How did you flash your board?
I can provide some debug methods here but this requires some background knowledge. For example, if you don’t even know how to flash the board manually, then I may need to guide from the beginning.

7

I have a laptop with linux 22.04 and I flashed it using the sdkmanager manually. What information do you need? Can I send you the whole process somewhere? I’ve recorded it on video.

8

Hi,

Please go to your BSP directory on your host PC. Sdkmanager already installed that thing on your PC with path ~/nvidia.

Follow this process:

  1. Run l4t_create_default_users.sh to set your user account first.
    Flashing Support — NVIDIA Jetson Linux Developer Guide

  2. Put your Jetson into recovery mode.

  3. Start to flash it again with manual commands with below document.
    Quick Start — NVIDIA Jetson Linux Developer Guide

After flash, use this method to check the console on the board.

As your GUI is dead, it is the only method that you could access the board.

After you login into the console, go to check /var/log/Xorg.0.log and share that log here.

If you don’t run l4t_create_default_users.sh, your console won’t work in first boot.

9

Hello.
I executed the script l4t_create_default_user.sh to create the user. The process was completed successfully.

I put the Jetson into Recovery Mode and confirmed it using the lsusb command, where the Jetson appeared as NVIDIA Corp. APX.

We performed the flash with the command sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1, and the process completed without errors, causing the Jetson to reboot.

I connected via serial console and confirmed that the Jetson is recognized as /dev/ttyACM0.
When i run “sudo screen /dev/ttyACM0 115200” i see only a black screen.

10

UPDATE

I am connected to the Jetson via terminal, but I don’t get any display output.
It seems I’m having an issue with the Nvidia drivers.

11

Hi,

Please use the “micro usb port” on your Orin AGX devkit instead of type C port to dump log.

That one is always alive, but the type C port one does not always give out log.

12

Hi,
I have connecting the Jetson via micro usb. I have access in jetson via terminal.
I started by running the command lsmod | grep nvidia to check if the NVIDIA kernel modules are loaded. The result showed that the nvidia and nvidia_modeset modules are correctly loaded, indicating that the NVIDIA graphics card is recognized by the system.
Since the system couldn’t display the connected monitors with the command xrandr --listmonitors (I received the message “Can’t open display”), i concluded that the X server is likely not functioning correctly or it is not recognizing the external display via DisplayPort.
Furthermore I used the command for f in /sys/class/drm/card0-*/status; do echo "$f: $(cat $f)"; done to check the status of graphic outputs, but the result showed that the system could not find any entries, meaning that no external display or DisplayPort output is recognized.
Also, I checked whether the Display Manager (GDM) is running correctly with the command systemctl status display-manager. The result showed that GDM is active and running, meaning the Display Manager doesn’t seem to be the cause of the issue.
Finally based on the above, the likely cause seems to be either that the NVIDIA driver is not correctly recognizing the DisplayPort or that the nvidia-drm module or the xorg.conf file configuration needs modification.

13

Hi,

Please share the /var/log/Xorg.0.log first.

14

xorg.txt (16.2 KB)
Hi, Do you need this attachment ?

15

Is it possible that there’s a hardware issue? Could it need a jumper on the GPIO pins?

16

No, it does not need any jumper.

18.503] (–) NVIDIA(GPU-0): DFP-0: disconnected
[ 18.503] (–) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 18.503] (–) NVIDIA(GPU-0): DFP-0: 2380.0 MHz maximum pixel clock

The issue here is this monitor directly be recognized as “disconnected”.

Do you have other monitors can test here?

17

Hello,

I don’t have other monitors. This is the second monitor (1st with DP) and using a new DP cable. My monitors and cables works good with my pc.
I believe that the problem is the DP of jetson or the drivers..

18

It is not possible to help check anything in such remote way.

I can only offer you some test steps here.
If you flash your board back to Jetpack5.1.5, will same monitor work on the board?

Again, this is just debug process.

20

I ran into the same DisplayPort-to-HDMI adapter issue after flashing to JetPack 6.2 and wanted to share a workaround that might help you and others stuck in the same situation. After the flash, my AGX Orin completely lost DisplayPort output — no GUI, no login screen, either nothing or blue screen. I did some digging and discovered that EDID parsing isn’t properly handled for many adapters in JetPack 6.2. The system boots fine, but the display fails to initialize due to missing or unsupported display configs.

Workaround:

Remote into your Orin and set up a VNC session. I’ve documented the full workaround and included it in the attached PDF/markdown. It walks through:

Forcing headless CLI boot via multi-user.target

Setting up LightDM + GTK Greeter manually

Configuring VNC (TightVNC/TigerVNC) for remote GUI access

Avoiding common pitfalls during X server startup

And diagnosing why card0-DP-1 isn’t showing up

I would also recommend SSH’ing into the Orin from a host computer or using the debugging connection.

Disclaimer:

I’m not affiliated with NVIDIA — just an engineer who said, “I’m not waiting for the next JetPack patch.”

I’m actively working on a fix to restore native DisplayPort output via custom EDID injection or patching the DRM layer. If successful, I’ll share the patch here.

If you follow this guide and modify system configs, there’s a risk of soft-bricking your flash. Always back up before making changes. Proceed at your own risk.

Hope this helps you. Feel free to reach out if you’re debugging something similar.

etPack 6.2 No Display Fix (AGX Orin, DisplayPort-to-HDMI Adapter Bug.pdf (80.4 KB)

EDIT::

Also manually flashing the board is another option. I would recommend learning how to manually flash, or avoiding SDK Manager in general…

The AGX Orin Dev Kit guide is here ^^^

22

Hello,
So I’ve tried some workarounds but I’m still facing troubles with the device. Here are the details:

  1. Different displays: Tried 3 different displays, two of them with DP (DisplayPort 1.2 and DisplayPort 1.4) and one with HDMI with an active DP-HDMI adapter.
  2. Different Jetpack Versions: I flashed Jetpacks 5.1.5, 5.1.3 and 6.2 using both the SDK Manager and manual flashing as described in the NVIDIA documentation.

In every configuration, I have the same issue. The device boots up and I only get black screen. However, I can access the device via SSH and minicom. In the device tree I can see the display@13800000 node, but I can’t find any reference to the DP nodes, but I assume since this is a Dev Kit it should be enabled by default. On xrandr --query I always get Can't open display.

I’m attaching the output of dmesg the boot log and the Xorg log for your reference.

dmesg.log (72.0 KB)
Xorg.0.log (22.1 KB)
boot.log (54.9 KB)

Is there anything I’m missing? Is it possible the DP is faulty?

Thanks for your help!

23

I saw your xorg log always give out the monitor is not connected.

Do you have other Orin AGX or Orin NX device on your side that can cross check whether this monitor can work fine there or not?