Jetson Xavier Nx Not Booting

My AGX had the same problem. I was able to boot with the host computer and USB cable connected. You don’t need a USB cable when it starts up. Please try it.
The latest cudnn and other updates seem to be the cause of this problem.

Was having the same issue after the update too, terminal was stuck at bash (via the serial console) and the display was empty. The Xavier NX finally boots up after a few tries. (Most likely booted up after pressing CRTL-ALT-DEL.)

Update: The same issue persists even after reboot.

3 Likes

I update using WIFI. It shows you have a new update then it is updated using WIFI.

How to see “serial console log”?

https://elinux.org/Jetson/General_debug

If you tried to upgrade the system from rel-32.4.2 to rel-32.4.3 by running the apt-get with nvidia official deb package, then you need to check this comment.

However, if you are using sdkmanager to directly flash your board with new rel-32.4.3, then you are not hitting the problem I am talking about.

This bug symptom will show below log in the end of your serial console log.

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-4.3#

In this case, if you are using sdcard image, please mount your sdcard on host and add the root=/dev/mmcblk0p1 back to /boot/extlinux/extlinux.conf.

APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4

How to see it by myself?

Another method that is applicable to all kinds of platform.

1.Mount the APP partition
mount /dev/mmcblk0p1 /mnt
2. Add the boot args
For T210 (Jetson Nano/ TX1)
sed -i "s|^\([ \t]*APPEND \${cbootargs}\) .*|\1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 sdhci_tegra.en_boot_part_access=1|" /mnt/boot/extlinux/extlinux.conf

For T186 serise (TX2/TX2i/TX2-4GB)
sed -i "s|^\([ \t]*APPEND \${cbootargs}\) .*|\1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2|" /mnt/boot/extlinux/extlinux.conf

For T194 series (NX/AGX Xavier)
sed -i "s|^\([ \t]*APPEND \${cbootargs}\) .*|\1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0|" /mnt/boot/extlinux/extlinux.conf

3. Unmount APP partition and reboot
umount /mnt
reboot
3 Likes

please read the general_debug page I posted in previous comment…

1 Like

This is solution for a booting problem. Try CTRL+ALT+DELETE in several times and then it is going to the desktop. Then use above codes in Terminal.

But there is another issue after this.

sudo jetson_clocks not working. It does not show any error but fan not working in 100% speed. It shows jetson clock is working and CPU use 1.4GHz also but fan not working.

1 Like

I have the same problem with my (16 GB RAM) Xavier AGX. I upgraded it yesterday and it hung up in the boot, so I reflashed it today with the SDK manager. It comes up but if I do an update / upgrade it won’t boot any more. There must be something wrong with one of the packages on the upgrade. I’m going to wait a week before attempting another upgrade; I lost a day on my project for this and can’t afford to lose another day right now - I’m closing out a release.

I run the python to check modules then i got following error.

When i run the jetson-interface, also get a error massage.

All are works before update it.

seems like i can’t even install the SDK manager now haha, what a mess.

Hi,

Since there are many users in this thread, it means any kinds of issue could be here.
Thus, I suggest all people here please do share your serial console log to show and confirm whether we are really talking about the same issue.

For example, “stuck in NV boot logo” could represent either kernel error or bootloader error. We need to take these kinds of issue separately.

@wmindramalw, I am glad it works on your case. But your new issue seems not boot issue anymore.

Please file a new topic and tag me. We will check your new error there.

OK … but it’s going to be next week before I can do any bootloader troubleshooting. The machine’s been working for a month and a half without incident and along comes a 200+ package upgrade :-(

How to downgrade to the last version until fixing this?

This is best product i ever used. Thank you for this product to be invented. We are not getting big worry about this issue. Hope you solve this issue as soon as possible.

Another workaround if you see the bash (initrd) console in UART after running OTA upgrade.

1. reboot the device 7 times,
2. the device should be able to boot up properly.
3. edit the /boot/extlinux/extlinux.conf to do following changes:
- APPEND ${cbootargs} quiet
+ APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
4. Reboot the device, and run "dpkg-reconfigure nvidia-l4t-bootloader"
5. reboot device.
2 Likes

@WayneWWW I really wish I had read this 18 hours ago :)

FYI: It does seem the bad update is still available since I just had this happen an hour or so ago to my NX. Is it confirmed a reflash of the SD card will work? Where does the bootloader live exactly on the NX?

The sdcard image and sdkmanager should work. Only the OTA will crash because something wrong in bootloader update.

We are still trying to get this fix ASAP. Also, we shall already pulled off the functionality of OTA.

@WayneWWW

Thanks for the fix instructions, solving my mystery of why my AGX suddenly started working after multiple reboots, and the bootloader details. I didn’t even get a chance to apply the manual fix since it appears a new package does fix the boot command line arguments.

 $ sudo apt update && sudo apt dist-upgrade 
Get:1 file:/var/cuda-repo-10-2-local-10.2.89  InRelease
Ign:1 file:/var/cuda-repo-10-2-local-10.2.89  InRelease
Get:2 file:/var/visionworks-repo  InRelease
Ign:2 file:/var/visionworks-repo  InRelease
Get:3 file:/var/visionworks-sfm-repo  InRelease
Ign:3 file:/var/visionworks-sfm-repo  InRelease
Get:4 file:/var/visionworks-tracking-repo  InRelease
Ign:4 file:/var/visionworks-tracking-repo  InRelease
Get:5 file:/var/cuda-repo-10-2-local-10.2.89  Release [574 B]
Get:6 file:/var/visionworks-repo  Release [2,001 B]                         
Get:7 file:/var/visionworks-sfm-repo  Release [2,005 B]                                                                
Get:5 file:/var/cuda-repo-10-2-local-10.2.89  Release [574 B]                                                          
Get:8 file:/var/visionworks-tracking-repo  Release [2,010 B]                                                         
Get:6 file:/var/visionworks-repo  Release [2,001 B]                                                                                                 
Get:7 file:/var/visionworks-sfm-repo  Release [2,005 B]                                                                                 
Get:8 file:/var/visionworks-tracking-repo  Release [2,010 B]                                                                                                     
Hit:9 https://repo.download.nvidia.com/jetson/common r32.4 InRelease                                                                                             
Hit:10 https://repo.download.nvidia.com/jetson/t194 r32.4 InRelease                                                                   
Hit:11 http://ports.ubuntu.com/ubuntu-ports bionic InRelease
Hit:13 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease
Hit:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease
Hit:16 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease
Reading package lists... Done                      
Building dependency tree       
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  nvidia-l4t-bootloader nvidia-l4t-tools
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.6 MB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 https://repo.download.nvidia.com/jetson/t194 r32.4/main arm64 nvidia-l4t-bootloader arm64 32.4.3-20200709231533 [28.1 MB]
Get:2 https://repo.download.nvidia.com/jetson/t194 r32.4/main arm64 nvidia-l4t-tools arm64 32.4.3-20200709231533 [538 kB]
Fetched 28.6 MB in 3s (9,944 kB/s)        
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 142544 files and directories currently installed.)
Preparing to unpack .../nvidia-l4t-bootloader_32.4.3-20200709231533_arm64.deb ...
Unpacking nvidia-l4t-bootloader (32.4.3-20200709231533) over (32.4.3-20200625213407) ...
Preparing to unpack .../nvidia-l4t-tools_32.4.3-20200709231533_arm64.deb ...
Unpacking nvidia-l4t-tools (32.4.3-20200709231533) over (32.4.3-20200625213407) ...
Setting up nvidia-l4t-tools (32.4.3-20200709231533) ...
Setting up nvidia-l4t-bootloader (32.4.3-20200709231533) ...
3668----1--jetson-xavier-nx-devkit-mmcblk0p1
Starting bootloader post-install procedure.
Update bootloader completed.
Reboot the target system for changes to take effect.
Updating extlinux.conf...
Adding bootargs into exlinux.conf...
[username@hostname] -- [~] 
 $ cat /boot/extlinux/extlinux.conf 
TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      INITRD /boot/initrd
      APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0

# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
#      sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot

# LABEL backup
#    MENU LABEL backup kernel
#    LINUX /boot/Image.backup
#    INITRD /boot/initrd
#    APPEND ${cbootargs}

… and it reboots! Others might want to hold off updating until there’s more testing, however.

How is this issue going?
can we fix through update?

Hi,

New version should be posted already. Please try it.