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.