Cannot start Jetson Nano after upgrade

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hello, I recently ran sudo apt-get upgrade on my Jetson Nano and encountered the following boot errors. Can anyone help me understand and resolve them?

[ 1.174770] teradc_teradcx:1: dpd enable lookup fail:-19
[ 1.325903] imx219 6-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.325711] imx219 6-0010: board setup failed
p: not writing through dangling symlink 'etc/resolv.conf'
[ 1.976080] group: cgroup2: unknown option "nsdelegate"
[ 3.424190] random: crng init done
[ 3.427611] random: 7 urandom warning(s) missed due to ratelimiting
[ 3.528451] using random self ethernet address
[ 3.530601] using random host ethernet address
[ 4.512021] using random self ethernet address
[ 4.522380] using random host ethernet address

I was able to run initial setup then I updated using
sudo apt-get update -y
sudo apt-get upgrade -y

After that I reboot the Jetson Nano, and the above error shows. I have tried multiple times reflashing the image.

I am following the docs: https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-devkit#intro
For my Jetson Nano 4GB.

I have checked other similar issue and most of the time people wasn’t able to boot for first time and recommendation was to use Linux to flash. I am using Windows and Balen Etcher to flash and it works, it just after reboot it doesn’t works. Also I am using external monitor, keyboard and mouse (not headless start)

Any insights or suggestions would be greatly appreciated. Thank you!"

2

It is kind of a common mistake that everyone thinks “I hit those errors and cannot boot” and paste these logs.

Actually, these logs are not the real problem. These logs exist there even in normal boot up case. The real problem here is your desktop GUI is gone from some unknown reason so you see those logs printed on screen. And that leads you think those logs are cause.

To identify why your GUI is gone, I need you to help dump /var/log/Xorg.0.log from your jetson.

The board is still fine if you have other method to access the terminal. For example, use ssh to access the board. Or use the serial console pin as below link.

3

Thanks for your prompt response.
I will try to get those logs and provide you soon.

But just for context I have used two different Jetson Nano, and I faced the same issue on both with same image. And those are the only 2 commands (update and upgrade then reboot) I used after the first boot.

4

There is another fact that even running out of disk space would lead to GUI not able to show up as well.
You could check that too. If disk space is still sufficient, then you need to dump the log I need.

5

Yup, I am using 64GB and 128GB memory cards so I guess there is enough space.

6

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