Jetson AGX Orin 64 GB Developer kit flashed with Jetpack 5.1.5 after boot screen no display signal

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

I have a jetson agx orin 64 GB developer kit installed Jetpack 5.1.5 to NVMe SSD with SDK Manager.

It sucecssfully installed, and seems like I can ssh to it, but after boot screen it show No signal …

I tried to restart the gdm3 and the dmesg show this errors.

[  145.367079] NVRM: loading NVIDIA UNIX Open Kernel Module for aarch64  35.6.1  Release Build  (buildbrain@mobile-u64-6291-d8000)  Tue Mar  4 01:52:31 PST 2025
[  145.398520] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for aarch64  35.6.1  Release Build  (buildbrain@mobile-u64-6291-d8000)  Tue Mar  4 01:52:33 PST 2025
[  145.682055] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:

I noticed that already have some topic that regarding same problem. but no clear answer how can I fix it.

I already reflash multiple times ,but it have same problem.

How can I fix it?

2

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

I understand your concern about the “No signal” issue on your Jetson AGX Orin 64 GB developer kit after installing Jetpack 5.1.5 to NVMe SSD with SDK Manager. Despite successful installation and SSH connectivity, the boot screen displays “No signal.” You’ve tried restarting gdm3, and dmesg shows errors, but you’re unsure how to fix it.

Firstly, let’s compare your issue with similar problems discussed in the provided context:

  1. Similar issues on other Jetson devices: There are topics discussing similar “No signal” or boot issues on other Jetson devices, such as the Jetson Orin NX, Jetson Xavier NX, and Jetson Nano. However, these topics don’t provide a clear solution for your specific problem.
  2. HDMI-related issues: Some topics mention HDMI-related problems, such as “ORIN NX unable to use HDMI display” and “Hdmi does not work after replace boot.img and dtb file!” These issues might be related to your problem, but they don’t provide a direct solution.
  3. Boot and kernel-related issues: Topics like “Boot failed” and “Call trace observed in during boot in preempt-rt kernel” discuss boot and kernel-related problems, which might be relevant to your issue.

To troubleshoot your problem, I recommend the following steps:

  1. Verify HDMI configuration: Ensure that your HDMI configuration is correct. You can try configuring HDMI instead of DP on your customized carrier board, as discussed in the topic “How to configure HDMI, instead of DP, on customized carrier board.”
  2. Check kernel and boot logs: Analyze your kernel and boot logs to identify any errors or issues that might be causing the “No signal” problem. You can use the dmesg command to check the kernel logs and look for any error messages related to HDMI or display.
  3. Reflash with a different Jetpack version: Try reflashing your Jetson AGX Orin with a different Jetpack version, such as Jetpack 6.2, to see if the issue persists.
  4. Check for hardware issues: Verify that your hardware is functioning correctly. Ensure that your NVMe SSD is properly connected and configured.
  5. Seek support from NVIDIA: If none of the above steps resolve your issue, consider seeking support from NVIDIA through their forums or support channels.

In summary, while there are similar issues discussed in the provided context, there is no clear solution for your specific problem. By following the troubleshooting steps outlined above, you may be able to identify and resolve the issue causing the “No signal” problem on your Jetson AGX Orin 64 GB developer kit.

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

3

Okay no matter how many times i reflash the jetson on eemc or nvme is same. How can i solve it?

It always no signal after boot screen

5

Hi,

Do you connect the monitor with DP cable?
Some user will meet issue when connect to the HDMI monitor using DP-HDMI adapter.

Thanks

6

Yes, of course I have been plugged DP cable with monitor.

But for Jetpack version 5.x.x i can’t get the monitor work. But if i install Jetpack 6.1.0, i’m able to get the monitor work.

Currently I trying to install with 5.x.x is because some of the cameras need to use 5.x.x version due to the driver compatibility.

7

okay it seems like i need to always replug to make the monitor to work.

Doesn’t it reload when the jetson is restart?

8

Hi,

Please provide below log for us to review

  • /var/log/Xorg.0.log
  • The output of lsmod saved to a file: lsmod > lsmod.txt
  • The output of dmesg saved to a file: dmesg > dmesg.txt
  • ps aux | grep gdm3

Thanks

9

Okay these are the logs.
dmesg.txt (75.9 KB)
lsmod.txt (3.5 KB)
Xorg.0.log (38.1 KB)

ai@ubuntu:~$ ps aux | grep gdm3
root        1099  0.0  0.0 241200  7740 ?        Ssl  17:50   0:00 /usr/sbin/gdm3
gdm         1709  0.0  0.0 165192  5816 tty1     Ssl+ 17:50   0:00 /usr/lib/gdm3/gdm-x-session dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart
ai          2736  0.0  0.0 165192  5828 tty2     Ssl+ 17:51   0:00 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu
ai          4947  0.0  0.0   9608   648 pts/0    S+   18:22   0:00 grep --color=auto gdm3
10

Hi,

Based on your dmesg log

Loading NVIDIA UNIX Open Kernel Mode Setting Driver for aarch64  35.4.1  Release Build

It seems like still remain 35.4.1 (JP5.1.2).
Please make sure flash latest JP 5 version (JP 5.1.5)

Thanks

11

Hi.

I don’t know what is going on there.

From your xorg log

50.764] (–) NVIDIA(GPU-0): RTK Dopesplay (DFP-1): connected
[ 50.764] (–) NVIDIA(GPU-0): RTK Dopesplay (DFP-1): Internal TMDS
[ 50.764] (–) NVIDIA(GPU-0): RTK Dopesplay (DFP-1): 340.0 MHz maximum pixel clock

There is always TMDS signal. Which means actually we are output a signal for HDMI. The DP one turns out nothing connected.

12

this log appear when i replug my RTK Dopesplay(which is a display)

I trying with Jetpack 5.1.5, but somehow now i got another problem that i can’t Flash to SSD…?

I’m able to flash to EMMC, but when i trying to flash to SSD, i got following errors from the SDK Manager logs

From issue Jetson AGX Orin Flash Failure – Invalid Argument on /dev/mmcblk0, Partprobe Failed - #5 by cheesiangleow5284

invalid argument during seek for read on /dev/mmcbkl0

I need to use Tier IV Camera since it only support for Jetpack 5.1.1 or Jetpack 5.1.2, Does the I2C affect for Jetpack 5.1.5?

13

Hi,

I would say please just focus on original problem first. If you want something for flash, then you could file another topic for it.

For the display issue, I just saw somehow you think you are using a DP but actually a DP-HDMI seems to be in use.

14

I’m using a dopesplay with a hdmi to display port.

I have been using this with jetpack 6..x.x that with ubuntu 22.04 based os working without problem. I think it might a problem relating to the ubuntu 20.04

15

I would suggest to use a native DP display. Jetpack5 will no longer have much update.

16

okay it seems like NVIDIA is not going to work on this issue. I would just use dummy display for it.