Jetson orin nano cannot access the ubuntu desktop after successfully booting

[chenrensong]

issue background

• software: jetson linux version is 36.4.4
• hardware: jetson orin nano 8G module + custom carrier board，edp display

issue describe

1. We use the following commands to flash the images:
   skip oem-config:

sudo ./tools/l4t_create_default_user.sh -u test -p test -n ubuntu --accept-license

flash:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1   -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml"   --showlogs --network usb0 jetson-orin-nano-devkit external

2. we can see screen display the boot logo and boot message, However, it seems that nothing is displayed after successful booting. couldn’t access the Ubuntu desktop
   nvidia logo display
   
   

boot message display

no display aafter successful booting

3. I used xrandr to check the display information, and it showed that

test@ubuntu:~$ xrandr
Can't open display 
test@ubuntu:~$ 

4. logs:
   boot_debug_serial_console.log (75.5 KB)
   latest_syslog.log (159.2 KB)

Could you please take a look at this issue ? Thanks !

[carolyuu]

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

Based on the provided context, it appears that you are experiencing an issue with your Jetson Orin Nano 8GB module, where the system boots successfully but does not display the Ubuntu desktop. You have flashed the images using the skip oemconfig command and can see the boot logo and boot message, but nothing is displayed after successful booting.

To troubleshoot this issue, let’s consider a few possible causes:

1. Display configuration: Since you are using a custom carrier board with a DP display, it’s possible that the display configuration is not set up correctly. You can try using the xrandr command to check the display information, as you mentioned. If the display is not detected, you may need to configure the display settings manually.
2. Graphics driver: The Jetson Orin Nano uses the NVIDIA graphics driver, which may not be configured correctly. You can try updating the graphics driver to the latest version or reinstalling it.
3. Ubuntu desktop configuration: It’s possible that the Ubuntu desktop configuration is not set up correctly. You can try reinstalling the Ubuntu desktop package or configuring the desktop settings manually.
4. Boot configuration: The skip oemconfig command may be causing issues with the boot configuration. You can try booting without this command to see if it makes a difference.

To further troubleshoot the issue, you can try the following:

1. Check the system logs: You can check the system logs to see if there are any error messages related to the display or graphics driver. You can use the dmesg command to view the system logs.
2. Use a different display: If possible, try using a different display to see if the issue is specific to the DP display.
3. Try a different boot configuration: Try booting without the skip oemconfig command to see if it makes a difference.

In comparison to other similar issues, such as the “Jetson Orin Nano Developer Kit – Black Screen and Fan Stops After Boot (JetPack 5.1.3)” issue, it’s possible that the cause of the issue is related to the display configuration or graphics driver. However, without more information, it’s difficult to say for certain.

To resolve the issue, you can try the following:

1. Update the graphics driver: Update the graphics driver to the latest version.
2. Reinstall the Ubuntu desktop package: Reinstall the Ubuntu desktop package to ensure that the desktop configuration is set up correctly.
3. Configure the display settings manually: Configure the display settings manually using the xrandr command.
4. Try a different boot configuration: Try booting without the skip oemconfig command to see if it makes a difference.

If none of these solutions work, you may need to provide more information about your system configuration and the exact error messages you are seeing to further troubleshoot the issue.

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

[DavidDDD]

Hi,

Please provide those logs 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