Package nvidia-l4t-kernel is not configured yet

Hello Jetson community,

Has anyone experienced bellow issue when running sudo apt-get update/upgrade on the Nvidia Jetson Xavier NX board??Does anyone know how to solve it? The jetpack version is 5.1 35.2.1.

Package nvidia-l4t-kernel is not configured yet.
Errors were encountered while processing:
 nvidia-l4t-bootloader
 nvidia-l4t-kernel
 nvidia-l4t-kernel-headers
 nvidia-l4t-jetson-io
 nvidia-l4t-display-kernel
 nvidia-l4t-kernel-dtbs

Thanks for your reply in advance!!

Best regards,
Shakhizat

Below more log messages. My initial intention is to run Kubernetes k3s on the Jetson cluster. I suspect there is an issue with nvidia docker functionality, since i can not see gpu inside of cluster.

Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
6 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up nvidia-l4t-bootloader (35.2.1-20230124153320) ...
3668-301---1--jetson-xavier-nx-devkit-qspi-
Info. Installing mtdblock.
Info. Active boot storage: nvme0n1
Info. Legacy mode: true
INFO. Dump nv_boot_control.conf:
TNSPEC 3668-301-0003-B.0-1-2-jetson-xavier-nx-devkit-qspi-
COMPATIBLE_SPEC 3668-301---1--jetson-xavier-nx-devkit-qspi-
TEGRA_LEGACY_UPDATE true
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
Starting bootloader post-install procedure.
INFO. Installing mtdblock.
Starting legacy update procedure.
ERROR. Procedure for bl_only_payload update FAILED.
Cannot install package. Exiting...
dpkg: error processing package nvidia-l4t-bootloader (--configure):
 installed nvidia-l4t-bootloader package post-installation script subprocess returned error exit status 1
Setting up nvidia-l4t-kernel (5.10.104-tegra-35.2.1-20230124153320) ...
Using the existing boot entry 'primary'
3668-301---1--jetson-xavier-nx-devkit-qspi-
Info. Installing mtdblock.
Info. Active boot storage: nvme0n1
Info. Legacy mode: true
Starting kernel post-install procedure.
Starting legacy update procedure.
ERROR. Procedure for kernel update FAILED.
Cannot install package. Exiting...
dpkg: error processing package nvidia-l4t-kernel (--configure):
 installed nvidia-l4t-kernel package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of nvidia-l4t-kernel-headers:
 nvidia-l4t-kernel-headers depends on nvidia-l4t-kernel (= 5.10.104-tegra-35.2.1-20230124153320); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-kernel-headers (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-jetson-io:
 nvidia-l4t-jetson-io depends on nvidia-l4t-kernel (>> 5.10.104-tegra-35.2-0); however:
  Package nvidia-l4t-kernel is not configured yet.
 nvidia-l4t-jetson-io depends on nvidia-l4t-kernel (<< 5.10.104-tegra-35.3-0); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-jetson-io (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-display-kernel:
 nvidia-l4t-display-kernel depends on nvidia-l4t-kernel (= 5.10.104-tegra-35.2.1-20230124153320); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-display-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-kernel-dtbs:
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          No apport report written because MaxReports is reached already
                              No apport report written because MaxReports is reached already
                                                                                            No apport report written because MaxReports is reached already
                 nvidia-l4t-kernel-dtbs depends on nvidia-l4t-kernel (= 5.10.104-tegra-35.2.1-20230124153320); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-kernel-dtbs (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-l4t-bootloader
 nvidia-l4t-kernel
 nvidia-l4t-kernel-headers
 nvidia-l4t-jetson-io
 nvidia-l4t-display-kernel
 nvidia-l4t-kernel-dtbs
E: Sub-process /usr/bin/dpkg returned an error code (1)

Hi,

Please check the below topic first:

Thanks.

1 Like

Hi @AastaLLL, thanks for your reply. Potentially, I have encountered two separate issues. It seems that k3s utilizes containerd as the default container runtime, which was deployed automatically by Ansible. However, I require the Docker runtime instead. I can not solve the issue with the “Errors were encountered while processing:”

Hi,

Have you checked this issue with k3s team?
They should know more if you can deploy the container with docker runtime or not.

Thanks.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.