First time booting a nano and the boot process is taking forever, seems to hang at two places and does not complete initial setup. Nano eventually reboots and the process continues. I’m attached with usb keyboard, mouse and HDMI display as well as monitoring the serial port on a laptop. I’m using the 5v 4amp power supply. At the end of this post I’ve included two boot logs using the serial cable method. The first boot log starts from the beginning until we appear to stall for about 300 seconds:
Next the Nano seems to struggle to boot and eventually cycles through 1, 2, 3, 4 and 5 of 5 start jobs for quite a while. This seems to fail and we end up with:
Thanks for the reply. I have moved the boot logs to an attachment to the original post. Additionally, I added one here which is probably the better one to look at. Its a full boot cycle with multiple forced reboots captured.
I am using the latest image from the NVIDIA Jetson Nano website. I’ve burned the image to two different SDCards. One from Linux, one from MacOS. Both with the same results.
not writing through dangling symlink 'etc/resolv.conf'
[FAILED] failed to start load/save Random seed
[FAILED] failed to start udev kernel device manager
If your device keeps booting again and again, probably also hits kernel panic. You could remove “quiet” keyword in your rootfs/boot/extlinux/extlinux.conf and the serial console will dump more verbose log.
However, I think the fastest way to resolve this issue is try sdkmanager.
Following your suggestion I’m trying to use SDK Manager to flash my Nano. It appears, in order for SDK Manager to fully flash the Nano, the Nano needs to boot into Ubuntu. The problem is, this Nano never makes it to the login screen in Ubuntu.
The flashing appears to complete to the point of rebooting the nano…and the SDK Manager is at the step “SDK Manager is about to install SDK components on your Jetson Nano (Developer Kit version)” although there are a lot of watchdog errors.
I can’t use automatic mode as that requires a working Linux system on the Nano and manual mode results in the same boot issue as before.
We need to enable more log. Current log is not enough to debug.
You could use either way in below.
method 1. Remove the “quiet” keyword in extlinux.conf under your Linux_for_Tegra/rootfs/boot/extlinux and re-flash your board. Please do not use sdkmanager to flash in this step. Just use the flash.sh. If you don’t know how to use it, please refer to quick start guide on download center.
method 2. Plug the micro usb cable on the port and unplug any monitor cable (HDMI/DP). Use oem-config to configure your user account through UART with interface /dev/ttyACM0.
I had the UART capturing the boot sequence on the Serial Debug Console on J44. I did not command the reboot - it just happened, and the device continued to reboot continually after about 2640 seconds. I’ve captured the boot sequence: https://gist.github.com/jmhebert/681ae906cc5d4c724b85e2ea4200003a
What I can’t seem to figure out is how to get oem-config to run.
Do you have any more detailed steps as to how oem-config can get started? Am I able to use oem-config from the serial debug console on J44 or do I have to use the microUSB cable? Specificaly, does Linux need to be running on the nano for oem-config to be running? I don’t think I am getting to the point where Linux is running. If I can ssh into the device, how do I determine the IP address?
Please do not remove the whole APPEND in extlinux.conf. Cbootargs is also important for boot up. Just need to delete the quiet.
I had the UART capturing the boot sequence on the Serial Debug Console on J44. I did not command the reboot - it just happened, and the device continued to reboot continually after about 2640 seconds. I’ve captured the boot sequence: Nano Boot Serial Console flash.sh · GitHub
I am not sure if this error comes from the missing of cbootargs or not. Does your nano alwasy reboot before we start these test methods?
Do you have any more detailed steps as to how oem-config can get started? Am I able to use oem-config from the serial debug console on J44 or do I have to use the microUSB cable? Specificaly, does Linux need to be running on the nano for oem-config to be running? I don’t think I am getting to the point where Linux is running. If I can ssh into the device, how do I determine the IP address?
It should be the micro usb port. And yes, Linux needs to be running on nano for oem-config to run. It cannot run under such case in which kernel panic causes reboot. That is why you need to reply my previous question first. If this issue was already there, then I would suggest you to change another SDard to test.
After flashing my nano always boots itself automatically. If you notice the boot results in a kernel panic at 1088 and a subsequent reboot (partially captured reboot). This pattern continues indefinitely.
I will try another SDcard and will identify any different results.
Using a different SDcard from a different manufacturer worked. I have two Kingston 32GB SDCards - both achieve the same (failed) results. Switched to a 16GB Samsung SDCard and booted into Linux successfully, and was able to configure the environment with oem-config
I have used 2 PNY microSD 64G from the Nvidia re-seller and Sandisk 32G and all of them failed to boot after few days of working , its very frustrated to know that this happens a lot , what is the reason , is sumsung is better then the others ??(I am using Jetpack 4.3 for nano image from the official site)