Monitor Displays “INPUT NOT SUPPORTED” on Nvidia Jetson Orin Nano Dev Board

Issue Overview

Users of the Nvidia Jetson Orin Nano Dev Kit are experiencing a critical issue where their monitor displays “INPUT NOT SUPPORTED,” preventing the Jetson desktop from appearing. This problem typically arises after flashing the Dev Kit using the SDKManager, leading to confusion and frustration among users. The symptoms include:

  • Error Message: The monitor shows “INPUT NOT SUPPORTED.”
  • Context: This issue occurs during the initial boot sequence after flashing with JetPack 5.1.2.
  • Hardware Specifications: Users report utilizing a pure DisplayPort (DP) monitor, specifically models from iiyama.
  • Frequency: The issue seems consistent across different monitors from the same manufacturer.
  • Impact: Users are unable to access the Jetson desktop environment, severely hindering functionality and usability of the device.
  • Additional Context: The problem surfaced post-flash, suggesting a potential compatibility or configuration issue related to the display settings.

Possible Causes

The following potential causes have been identified for this issue:

  • Hardware Incompatibilities: Some monitors may not be fully compatible with the output settings of the Jetson board, particularly if they require specific resolutions or refresh rates not supported by the board.

  • Software Bugs or Conflicts: There may be unresolved bugs in JetPack 5.1.2 that affect display output, especially after a fresh installation.

  • Configuration Errors: Incorrect display settings in Xorg or other configuration files could lead to output issues.

  • Driver Issues: Missing or outdated drivers for display output may prevent proper communication between the Jetson board and the monitor.

  • Environmental Factors: Power supply issues or overheating could affect performance and lead to display errors.

  • User Errors or Misconfigurations: Users might not have configured their systems correctly after flashing, leading to display problems.

Troubleshooting Steps, Solutions & Fixes

To resolve the “INPUT NOT SUPPORTED” issue on the Nvidia Jetson Orin Nano Dev Kit, follow these comprehensive troubleshooting steps:

  1. Verify Monitor Compatibility:

    • Test with different monitors to determine if the issue is specific to one model.
    • Ensure that the monitor supports the resolution and refresh rate set by the Jetson board.
  2. Check Display Output Settings:

    • Connect via SSH and run:
      export DISPLAY=:0
      xrandr
      
    • Confirm that the expected output (e.g., DP-0) is listed and check supported resolutions.
  3. Review Log Files:

    • Collect logs for further analysis:
      • Use dmesg to check for kernel messages related to display issues.
      • Review /var/log/Xorg.0.log for errors or warnings that could indicate configuration problems.
  4. Reconfigure Display Settings:

    • If using a DP-HDMI adapter, ensure it is functioning correctly; try a direct DP connection instead.
    • Modify Xorg configuration files if necessary to set preferred resolutions.
  5. Update Drivers and Firmware:

    • Ensure that you are using the latest version of JetPack (5.1.2 or later) as updates may contain important fixes.
    • Consider downgrading to an earlier version (e.g., JetPack 5.1.1) if compatibility issues persist after flashing.
  6. Power Cycle and Reboot:

    • Power off all devices, disconnect cables, and then reconnect them before powering on again.
    • Ensure that all connections are secure and that power supply is adequate.
  7. Use Recovery Mode for Flashing:

    • If problems persist, consider re-flashing the device while ensuring it is in recovery mode:
      sudo ./flash.sh jetson-orin-nano-devkit-qspi mmcblk1p1
      
  8. Consult Documentation and Community Forums:

    • Refer to Nvidia’s official documentation for any additional troubleshooting steps specific to your setup.
    • Engage with community forums for shared experiences and solutions from other users facing similar issues.
  9. Best Practices for Future Prevention:

    • Always back up configurations before making changes.
    • Regularly check for software updates and community feedback regarding compatibility with new hardware.

If multiple users have reported success with specific solutions (such as testing different monitors), these should be highlighted as recommended approaches for resolving similar issues in future cases. Further investigation may be required if problems remain unresolved after following these steps.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *