Orin Nano 8GB No Display Issue

Issue Overview

Users are encountering a display issue with the Nvidia Jetson Orin Nano 8GB when running JetPack 5.1.1 on a custom board. The specific symptoms include:

• The device initially displays the UEFI screen with the NVIDIA logo, but then the screen goes black with no further output.
• Users can connect to the device via USB and SSH, indicating that the device is booting correctly despite the lack of display output.
• The issue persists across multiple monitors, suggesting it is not a monitor-specific problem.

The context of this problem occurs during the boot process, specifically after the initial UEFI screen. Users have noted that when using an Orin NX on the same custom carrier board and configuration files, the display functions correctly after booting. This inconsistency raises questions about compatibility or configuration specific to the Orin Nano.

Possible Causes

Several potential causes for this display issue have been identified:

• Hardware Incompatibilities: The custom board may have compatibility issues with the Orin Nano compared to the Orin NX.
• Software Bugs: There may be bugs in JetPack 5.1.1 affecting display output specifically for the Orin Nano.
• Driver Issues: The absence or failure to load the nvidia-modeset module could prevent proper display initialization.
• Configuration Errors: Incorrect configurations in .config files or device tree blobs (DTBs) could lead to improper hardware initialization.
• User Errors: Misconfigurations during setup or flashing processes might contribute to this issue.

Troubleshooting Steps, Solutions & Fixes

To diagnose and potentially resolve the display issue, users can follow these steps:

1. Verify Connections:

   • Ensure that the display is properly connected to the DisplayPort using a compatible adapter (e.g., HDMI to DisplayPort).

2. Check Kernel Modules:

   • Verify if nvidia-modeset.ko is loaded:

     lsmod | grep nvidia-modeset
     

   • If it is not loaded, attempt to manually load it:

     sudo modprobe nvidia-modeset
     

   • If you encounter errors like "No such device," investigate further.

3. Examine dmesg and Xorg Logs:

   • Review logs for errors related to display initialization:

     dmesg | grep nvidia
     cat /var/log/Xorg.0.log | grep EE
     

4. Check for Missing Symbols:

   • If loading nvidia-modeset fails, check for missing symbols:

     cat /proc/kallsyms | grep nvidia_register_module
     

   • If symbols like nvidia_register_module are missing, this indicates a deeper issue with driver compatibility.

5. Update Configuration Files:

   • Ensure that your .config file does not hardcode settings specific to other models (like NX). Start from jetson-orin-nano-devkit.conf and customize it for your board.

6. Test with Different BSPs:

   • If possible, test using different Board Support Packages (BSPs) or JetPack versions to see if the issue persists.

7. Use DevKit for Validation:

   • If available, test your setup on an official Jetson DevKit to confirm whether the issue lies with your custom board or configuration.

8. Firmware and Driver Updates:

   • Regularly check for updates in firmware and drivers from NVIDIA’s official repositories.

9. Seek Community Support:

   • Engage in forums or community discussions for additional insights or similar experiences from other users.

Recommended Approach

Multiple users have reported success after revising their .config files to ensure compatibility with their specific hardware setups, particularly avoiding hardcoded settings from other models. This adjustment has resolved both display issues and flashing problems in various cases.

Unresolved Aspects

Further investigation may be needed regarding specific driver versions and their compatibility with various configurations of the custom board used by different users. Additionally, understanding how environmental factors (like power supply stability) may affect performance can be beneficial for future troubleshooting efforts.