Jetson Orin Nano Devkit cannot continue to ubuntu GUI after boot successfully with serial terminal

Dear,

We write image to microSD card using JetPack 5.1.1 and we have SSD Nvme. Previously, there were no errors with the console display, but after we set the datetime to ‘off’ (disabled automatic synchronization using the internet), this error occurred. Below is the image documentation that can be displayed. We kindly ask for a solution to this issue. Thank you.

Booting Process is successfully

Cannot console display, but LED and fan indicator ON

Not quite sure what “console display” you are talking about. Rel-35 does not support console mode.

What do you mean by Rel-35? Previously, after the flashing process and installing the SDK on Ubuntu, we were able to access the console display

I mean “console display” like a login display, menu display, etc

Jetpack5 is with rel-35 code branch and Jetpack6 is with rel-36 code branch.

So when we say rel-35, it is equal to talking about the BSP of jetpack5.

Are you talking about the Ubuntu GUI? Or you are talking about the console on the screen?

Thank you for the explanation. Sorry, We are talking about the Ubuntu GUI

please use the UART serial console and dump the /var/log/xorg.0.log, attach it here.

We are new to using Jetson, how do we use UART serial console and dump the /var/log/xorg.0.log?

Check this post.

Okee thanks, we will try

We use USB to TTL Serial Cable for UART serial console. And software PuTTY for get data.
Here is the data
error-jetson-orin.txt (62.7 KB)

Your rootfs on sdcard is corrupted.

This is known issue on old rel35 release, please upgrade the BSP version and it shall get resolved.

Thank you for your input. Since this is the second time I’ve encountered this issue, could you recommend which BSP version is stable and reliable for my setup? I would like to ensure that I avoid this error moving forward

always use the latest one. For rel-35, it is rel-35.6 now.

Thank you for the clarification. I will make sure to update to rel-35.6 and hope this resolves the issue moving forward. Hopefully, there won’t be any more problems in the future

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.