Apt-get upgrade fails in Xavier-Nx

When performed apt-get upgrade on BSP: 32.4.2 for 32.4.2,

Errors were encountered while processing:
 nvidia-l4t-xusb-firmware
 nvidia-l4t-initrd
 nvidia-l4t-bootloader
E: Sub-process /usr/bin/dpkg returned an error code (1)

Additional info nvidia-l4t-xusb-firmware

Setting up nvidia-l4t-xusb-firmware (32.4.3-20200625213407) ...
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
Setting up kmod (24-1ubuntu3.4) ...
Installing new version of config file /etc/modprobe.d/blacklist-framebuffer.conf ...
Setting up libisccc160:arm64 (1:9.11.3+dfsg-1ubuntu1.12) ...
Setting up libnm-util2:arm64 (1.10.6-2ubuntu1.4) ...
Setting up gir1.2-ibus-1.0:arm64 (1.5.17-3ubuntu5.3) ...
dpkg: dependency problems prevent configuration of nvidia-l4t-initrd:
 nvidia-l4t-initrd depends on nvidia-l4t-xusb-firmware (= 32.4.3-20200625213407); however:
  Package nvidia-l4t-xusb-firmware is not configured yet.

dpkg: error processing package nvidia-l4t-initrd (--configure):
 dependency problems - leaving unconfigured
Setting up docker.io (19.03.6-0ubuntu1~18.04.1) ...No apport report written because the error message indicates its a followup error from a previous failure.

docker.service is a disabled or a static unit, not starting it.
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2020-08-04 10:43:48 EDT; 25ms ago
     Docs: https://docs.docker.com
  Process: 23323 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 23323 (code=exited, status=1/FAILURE)

Aug 04 10:43:48 nvidia-desktop systemd[1]: Failed to start Docker Application Container Engine.

For nvidia-l4t-bootloader

Setting up nvidia-l4t-bootloader (32.4.3-20200709231533) ...
ERROR. Unsupported board ID: .
Cannot install bootloader package. Exiting...
dpkg: error processing package nvidia-l4t-bootloader (--configure):
 installed nvidia-l4t-bootloader package post-installation script subprocess returned error exit status 1

Any recommendations would be of great help.

Thanks

Hi,

ERROR. Unsupported board ID:

Because I see this error in your log, need to know how do you set up the device.
Is this a custom carrier board or nvidia devkit?

Custom carrier board.

Hi,

I think you should tell us more about your setup.

You should tell us how did you flash your board and if you customized any thing.

Sure.

  • Board set up: xavier nx + custom carrier board.All standard interfaces.
  • Rootfs is in SD Card.
  • Flash procedure: ./flash.sh < board conf file > external
  • board conf file - This is similar to jetson-xavier-nx-devkit.conf, but defined for custom board.

Did some further analysis on this.
TNSPEC value in /etc/nv_boot_control.conf seems not coming correct. Probably, due to this, parsing of post installation script in nvidia-l4t-bootloader fails.

But, I do not know why TNSPEC gets incorrect.
TNSPEC ---- 1-2-<board conf file>-external

what source of the imagge did you use for flashing with flash.sh?
did you use default stock kernel? or an image provided by a custom vendor?

It is not stock kernel. It is the image prepared after modifying few drivers and device tree files to support the custom board.

  • board conf file - This is similar to jetson-xavier-nx-devkit.conf, but defined for custom board.

This step may cause the apt failure. Please use official config name but put your customized stuff inside it.