Display Output Issue with JetPack 5.1.4

Robotics & Edge Computing Jetson Systems Jetson Xavier NX
,
1

We have observed that after flashing a Jetson Xavier NX module with JetPack 5.1.4, the display behaves as follows:

  • When connected to a monitor with a resolution of 1920×1080 or 3840×2160 at boot time, the system displays correctly all the way through to the desktop environment.

  • However, when connected to a monitor with a resolution of 1440×900 or 1024×768 at boot time, the display shows the NVIDIA UEFI logo but then loses signal immediately afterward, showing no further output.

  • If the system first boots with a 3840×2160 display and reaches the desktop, and then the monitor is switched to 1440×900, the display works correctly.

Module: Jetson Xavier NX
JetPack Version: 5.1.4
Hardware: Issue reproduced on both custom carrier boards and the official NVIDIA Developer Kit.

Could you please provide specific troubleshooting steps?

custom_3840x2160.txt (68.8 KB)

custom_144x900.txt (71.0 KB)

devikit_1440x900.txt (71.6 KB)

3

Hello @waylo,

Quick question.
Does the weird behavior only shows on JetPack 5.1.4?

best regards,
Andrew
Embedded Software Engineer at ProventusNova

4

please help do the test that try to connect your monitor after boot up.

What I mean here is do not connect any monitor in the first boot up case. Only do the hotplug after the system is ready.

5

Yes, so far this issue has only been observed on JetPack 5.1.4. I’ve tested versions 4.5, 4.6, 5.1.1, and 5.1.2, and everything works normally on those.

6

I previously tried this operation, but the result was that regardless of whether I later connected a display with 3840×2160 or 1440×900 resolution, there was no signal output.

7

It’s as if the UEFI fails to read the EDID successfully, causing the display controller to fail to initialize properly.

8

What is the error log from dmesg when you did that test?

9

Also want to clarify. Is this NV devkit or a custom board?

10

Sorry, my previous reply was a bit disorganized. After further testing, the behavior is as follows:

  1. If the HDMI monitor is connected before powering on the device, both the NVIDIA developer kit and our custom carrier board exhibit no display output.
    Boot logs are attached at the top as: devkit_1440x900.txt and custom_1440x900.txt.

  2. If no monitor is connected during boot, and the HDMI display is hot-plugged only after the system is fully booted,
    both the NVIDIA developer kit and the custom carrier board output only: edid invalid,
    but then display works normally afterward.

For example:

Ubuntu 20.04.6 LTS nvidia-desktop ttyTCU0

nvidia-desktop login: [   49.654653] nvidia: loading out-of-tree module taints kernel.
[  123.382999] edid invalid
11

hot-plugged_log.txt (67.1 KB)

12

Just do me a favor to do a crosscheck. Please flash the “devkit” back to Jetpack4 and then try again if you could reproduce same issue with these monitors to boot up with monitor connected.

13

I’ve tested the approach you mentioned, and on both the NVIDIA developer kit and our custom carrier board, flashing other versions (e.g., JetPack 4.5, JetPack 4.6, JetPack 5.1.1) results in normal display output—this issue does not occur.

14

Please do more test between Jetpack5.1.1 ~ 5.1.4.

There is known issue on Jetpack5 that display might not be stable if bootloader enables it.

(i.e. If you see boot logo, then the display in kernel might not be stable).

However, such issue should happen in all Jetpack5 versions but won’t only happen on 5.1.4 but not 5.1.1.

Please check this link and it has some posts to prevent the error I mentioned.