I’m having a serious issue with my new Jetson Orin Nano Super and would like someone from the developer team to review this case, or advise me if I should request an RMA.
Issue Summary:
After a successful flash and firmware update using SDK Manager, my Jetson Orin Nano Super will not produce any display output.
What I did so far:
Used the latest NVIDIA SDK Manager on Ubuntu to flash JetPack OS to the device and update the firmware.
OS successfully installed on my NVMe drive.
Powered off, connected HDMI monitor, powered back on.
Symptoms:
Device powers on, fan spins normally.
No video signal to monitor (tested with multiple known-good HDMI displays and cables).
I am using a DisplayPort-to-HDMI adapter connected to an HDMI TV.
I’m not certain if the bootloader is actually booting from the NVMe, but I believe SDK Manager should have updated that automatically during the flash process.
No visible errors since the device never outputs video.
Hardware setup:
Jetson Orin Nano Super Developer Kit.
OS on NVMe (no SD card).
Official NVIDIA power supply.
DisplayPort-to-HDMI adapter to HDMI TV.
Multiple tested HDMI cables.
Support Context:
I contacted NVIDIA’s online chat support and was told there is no live support available for Jetson products. I was informed that posting here on the developer forum is the only way to get assistance from the Jetson development team.
What I’m requesting:
Assistance from the developer team to help diagnose this no-display issue.
If the board may be defective, please advise on the process to request an RMA.
Additional Info:
I am able to connect the device in recovery mode and can pull kernel, Xorg, and NVIDIA logs from the filesystem if needed. Please let me know exactly what logs you require, and I can attach them in .tar.gz format.
Thank you for the guidance on using a TTL serial cable to dump logs. I’ve followed the steps, acquired a USB to TTL serial converter, and connected it to the J50 header on my Jetson Orin Nano Super Developer Kit. After troubleshooting with swapped RX/TX wiring, I’m now able to capture boot output via minicom at 115200 baud.
Attached is the serial boot log (jetson_boot_log.txt) showing the full boot process. The device powers on (fan spins normally), initializes the NVMe drive, loads the kernel, and reaches systemd with a hostname of “ubuntu.” However, there’s still no display output on my HDMI TV using a DisplayPort-to-HDMI adapter. Key observations:
Bootloader and PCIe/UPHY init succeed, with NVMe detected.
No explicit display or DRM (graphics) messages in the log.
Systemd starts services, but no login prompt appears in serial (though I can test further if needed).
Some garbled text (e.g., “ITC WAG” warnings) might relate to I2C/display detection—possibly benign.
I wanted to provide an update following your advice and my previous response. Thank you for pointing out the UART setup issue—I’ve ensured a clean capture with a single, full-screen minicom session (115200 baud), and the attached updated serial boot log (jetson_boot_log_2.tar.gz) reflects this with no garbled text and proper ordering.
Since my last message, I’ve conducted additional testing to address the no-display issue:
I connected the Jetson Orin Nano Super directly to my TV using an HDMI cable (with DisplayPort-to-HDMI adapter), but there’s still no video output. The fan spins, and the serial log shows a successful boot to “Ubuntu 22.04.5 LTS ubuntu ttyTCU0” with a login prompt, confirming the OS is running.
The log indicates successful NVMe detection and PCIe initialization, but lacks any DRM, tegra-drm, or HDMI initialization messages, suggesting the display driver might not be loading or probing correctly.
I can interact via serial (minicom), logging in with default credentials (e.g., username: ubuntu, password: ubuntu), and ran dmesg | grep -i drm after login. The output (attached as dmesg_drm_log.tar.gz) shows no significant display-related activity beyond generic IOMMU group assignments (e.g., “host1x-context host1x-ctx.*: Adding to iommu group *”).
Based on this, it seems the issue persists despite direct HDMI connection, pointing possibly to a bootloader configuration mismatch for NVMe boot or a missing display driver initialization. I’d greatly appreciate your expert analysis of the updated logs to pinpoint the cause. If this requires a re-flash with specific NVMe/display settings (e.g., adjusting tegra234-mb1-bct-misc-p3767-0000.dts), please provide detailed steps. If it’s a hardware defect, please guide me through the RMA process.
Let me know if further logs (e.g., full dmesg or Xorg) or tests are needed. Thank you for your continued support!
Could you test a native DP port monitor instead of using adapter?
The log is still incomplete. Your uart log got truncated in each line once it exceed specific length. For example, there are still logs after Linux kernel version 5.15.148-tegra … after the red line I added, but it got truncated. Please resize your terminal to make sure it got fully log… or let console tool (picocom/minocom) directly output the log as text file.
I wanted to provide an update following your guidance. Based on your recommendation to test with proper hardware and my previous discussions about the DP-to-HDMI adapter issue, I ordered and tested a new adapter: the Cable Matters Active DisplayPort to HDMI Adapter (Active DP to HDMI Adapter) Supporting Eyefinity Technology and 4K Resolution (Amazon.ca ). I’m happy to report that this resolved the no-display problem!
After connecting the new active adapter between the Jetson Orin Nano Super’s DisplayPort and my HDMI TV, I powered on the device, and the display output now works correctly. The boot process completes, and I see the Ubuntu 22.04.5 LTS login screen as expected.
A few additional notes:
The previous adapter was likely passive, which explains the failure—your advice to use a native DP monitor or active adapter was spot-on.
