Errors on nvidia-l4t-xusb-firmware and nvidia-l4t-initrd

I have the problem with the packages in the title. It started 3 weeks ago with an upgrade process, I guess. I thought it was a bug and waited for it to resolve itself for a while, but it didn’t happen. Now, every upgrade I make and elements such as sdk-package that I try to install end up with this error. I am using a Jetson NANO with no custom board. As an example, one of the errors I have encountered is as follows.

yamac@yamac:~$ sudo apt-get install libavcodec-dev libswresample-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
The following NEW packages will be installed:
  libavcodec-dev libavutil-dev libswresample-dev
0 upgraded, 3 newly installed, 0 to remove and 23 not upgraded.
2 not fully installed or removed.
Need to get 4.934 kB of archives.
After this operation, 17,4 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 bionic-updates/universe arm64 libavutil-dev arm64 7:3.4.8-0ubuntu0.2 [297 kB]
Get:2 bionic-updates/universe arm64 libswresample-dev arm64 7:3.4.8-0ubuntu0.2 [57,2 kB]
Get:3 bionic-updates/universe arm64 libavcodec-dev arm64 7:3.4.8-0ubuntu0.2 [4.580 kB]
Fetched 4.934 kB in 4s (1.297 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libavutil-dev:arm64.
(Reading database ... 156279 files and directories currently installed.)
Preparing to unpack .../libavutil-dev_7%3a3.4.8-0ubuntu0.2_arm64.deb ...
Unpacking libavutil-dev:arm64 (7:3.4.8-0ubuntu0.2) ...
Selecting previously unselected package libswresample-dev:arm64.
Preparing to unpack .../libswresample-dev_7%3a3.4.8-0ubuntu0.2_arm64.deb ...
Unpacking libswresample-dev:arm64 (7:3.4.8-0ubuntu0.2) ...
Selecting previously unselected package libavcodec-dev:arm64.
Preparing to unpack .../libavcodec-dev_7%3a3.4.8-0ubuntu0.2_arm64.deb ...
Unpacking libavcodec-dev:arm64 (7:3.4.8-0ubuntu0.2) ...
Setting up libavutil-dev:arm64 (7:3.4.8-0ubuntu0.2) ...
Setting up nvidia-l4t-xusb-firmware (32.4.4-20201016124427) ...
Starting xusb firmware post-install procedure.
ERROR. Procedure for xusb firmware update FAILED.
Cannot install package. Exiting...
dpkg: error processing package nvidia-l4t-xusb-firmware (--configure):
 installed nvidia-l4t-xusb-firmware package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of nvidia-l4t-initrd:
 nvidia-l4t-initrd depends on nvidia-l4t-xusb-firmware (= 32.4.4-20201016124427); however:
  Package nvidia-l4t-xusb-firmware is not configured yet.

dpkg: error processing package nvidia-l4t-initrd (--configure):
 dependency problems - leaving unconfigured
Setting up libswresample-dev:arm64 (7:3.4.8-0ubuntu0.2) ...
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Setting up libavcodec-dev:arm64 (7:3.4.8-0ubuntu0.2) ...
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

Is there a way to fix this problem with the command line or do I need to install the system again? Any ideas?


This should not be seen on a clean system. If it is possible, we would suggest do clean re-flash.

1 Like

Hi DaneLLL!

Thanks a lot for your comment. I applied it yesterday morning just before your reply and it works. However, I cannot find the reason behind it. I was at the beginning of my work so re-flashing didn’t cause much problem for me but if it repeats in the critical stages, it may be a problem.

I did not install anything external to the system. The open source codes I use are also actively used by hundreds of users. In other words, there was no action that could disrupt the “cleanness” of the system. So, do you have any idea about the reason behind it? Your professional opinion will help me take action against future risks.



is your default python version 3.x?
If yes, change in the file /usr/sbin/l4t_payload_updater_t210, line 1:




Yes, and many thanks!
It gets you further, but i think you have to replace in all other files … or just simply set up “python” to be python2.