reComputer J401 - Orin NX - sudo apt upgrade or Package Installation Error (JetPack 6.1)

Products & Technology Single Board Computers
1

Hello Seeed Studio community,

I’m using the NVIDIA Orin NX module on my reComputer J401. I’ve installed JetPack 6.1 on the device. After the Linux installation, when I try to run the sudo apt upgrade command, or when I attempt to install any package (e.g., sudo apt install keyboard-configuration), I encounter the following error, and the process cannot be completed. This prevents me from updating my system and installing new software.

Error Code:

`Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
keyboard-configuration is already the newest version (1.205ubuntu3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
7 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-kernel (5.15.148-tegra-36.4.3-20250107174145) …
Using the existing boot entry ‘primary’
Warning: Cannot get compatible board name.
3767-000-0000–1–recomputer-orin-j401-
TNSPEC 3767-300-0000-N.1-1-0-recomputer-orin-j401-
COMPATIBLE_SPEC 3767-000-0000–1–recomputer-orin-j401-
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
Info: Write TegraPlatformCompatSpec with 3767-000-0000–1–recomputer-orin-j401-.
Info: The esp is already mounted to /boot/efi.
Starting kernel post-install procedure.
Rootfs AB is not enabled.
ERROR. Procedure for A_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.15.148-tegra-36.4.3-20250107174145); 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.15.148-tegra-36.4-0); however:
Package nvidia-l4t-kernel is not configured yet.
nvidia-l4t-jetson-io depends on nvidia-l4t-kernel (<< 5.15.148-tegra-36.5-0); however:
Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-jetson-io (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
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
dpkg: dependency problems prevent configuration of nvidia-l4t-kernel-oot-modules:
nvidia-l4t-kernel-oot-modules depends on nvidia-l4t-kernel (= 5.15.148-tegra-36.4.3-20250107174145); however:
Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-kernel-oot-modules (–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.15.148-tegra-36.4.3-20250107174145); 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-oot-headers:
nvidia-l4t-kernel-oot-headers depends on nvidia-l4t-kernel (= 5.15.148-tegra-36.4.3-20250107174145); however:
Package nvidia-l4t-kernel is not configured yet.

dNo 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
pkg: error proces
sing package nvidia-l4t-kernel-oot-headers (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-kernel-dtbs:
nvidia-l4t-kernel-dtbs depends on nvidia-l4t-kernel (= 5.15.148-tegra-36.4.3-20250107174145); however:
Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-kernel-dtbs (–configure):
dependency problems - leaving unconfigured
Processing triggers for nvidia-l4t-initrd (36.4.3-20250107174145) …
Include /etc/nv-update-initrd/list.d/binlist
Include /etc/nv-update-initrd/list.d/modules
nv-update-initrd: Updating /boot/initrd from /etc/nv-update-initrd/list.d for kernel version 5.15.148-tegra…
Add /usr/sbin/nvluks-srv-app
Add /lib/modules/5.15.148-tegra/updates/drivers/net/ethernet/nvidia/nvethernet/nvethernet.ko
Add /lib/modules/5.15.148-tegra/updates/drivers/nvpps/nvpps.ko
Add /lib/modules/5.15.148-tegra/updates/drivers/net/ethernet/realtek/r8126/r8126.ko
Add /lib/modules/5.15.148-tegra/updates/drivers/net/ethernet/realtek/r8168/r8168.ko
Add /lib/modules/5.15.148-tegra/modules*
Add /lib/modules/5.15.148-tegra/kernel/drivers/nvme/host/nvme.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/nvme/host/nvme-core.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/thermal/tegra/tegra-bpmp-thermal.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/pwm/pwm-tegra.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/hwmon/pwm-fan.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/pci/controller/dwc/pcie-tegra194.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/phy/tegra/phy-tegra194-p2u.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/usb/gadget/udc/tegra-xudc.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/usb/typec/ucsi/ucsi_ccg.ko
Add /lib/modules/5.15.148-tegra/kernel/drivers/usb/typec/typec.ko
Updating modprobe.d configuration directories for modprobe…
Add config /etc/modprobe.d/alsa-base.conf
Add config /etc/modprobe.d/bcmdhd.conf
Add config /etc/modprobe.d/blacklist-ath_pci.conf
Add config /etc/modprobe.d/blacklist.conf
Add config /etc/modprobe.d/blacklist-firewire.conf
Add config /etc/modprobe.d/blacklist-framebuffer.conf
Add config /etc/modprobe.d/blacklist-modem.conf
Add config-link /etc/modprobe.d/blacklist-oss.conf
Add config /etc/modprobe.d/blacklist-rare-network.conf
Add config /etc/modprobe.d/denylist-nouveau.conf
Add config /etc/modprobe.d/denylist-oot-modules-audio.conf
Add config /etc/modprobe.d/denylist-ramoops.conf
Add config /etc/modprobe.d/denylist-tegra-safety.conf
Add config /etc/modprobe.d/denylist-tpm-ftpm-tee.conf
Add config /etc/modprobe.d/iwlwifi.conf
Add config /etc/modprobe.d/nvgpu.conf
Add config /etc/modprobe.d/nvidia-display.conf
Add config /etc/modprobe.d/tegra-udrm.conf
Add config /lib/modprobe.d/aliases.conf
Add config /lib/modprobe.d/fbdev-blacklist.conf
Add config /lib/modprobe.d/systemd.conf
Cleaning up the temporary directory for updating the initrd…
Errors were encountered while processing:
nvidia-l4t-kernel
nvidia-l4t-kernel-headers
nvidia-l4t-jetson-io
nvidia-l4t-kernel-oot-modules
nvidia-l4t-display-kernel
nvidia-l4t-kernel-oot-headers
nvidia-l4t-kernel-dtbs
E: Sub-process /usr/bin/dpkg returned an error code (1)`

I would greatly appreciate your assistance in resolving this issue.

Thank you

2

Hi there,

So you don’t say if you looked on the WiKi matrix and be sure to use the linux host listed ONLY. Read the threads , others had same. No using the Nvidia SDK either to do the upG. To new to be issue free, but you got great hardware so. be patient pretty sure it’s in the PiPeline. :+1:

HTH
GL :slight_smile: PJ :v:

3

Hello PJ_Glasso,
Thank you for your response.

  • Is the reason for this issue that I am using a reComputer J401 but using NVIDIA’s repositories?
  • I looked at the Wiki page to get started, but I couldn’t find anything other than example projects. Where should I look on the Wiki page to resolve issues like this?
  • Can packages like CUDA and DeepStream be installed on the reComputer J401? If so, how can I install them?
4

Hi there,

Yes indeed, That has led to some confusion as well, to bad because it is evolving so fast I think Seeed engineers are trying hard to keep up. The WiKi has the info for the upgrades also, That unit is VERY GOOD plenty of juice for those models. Vacation should be over on the 12th so Answers should start to flow on the Whole “deepSeek r1” implementations as far as seeed stuff is concerned.
Check out the threads on here on Updating or restoring the unit. Many have gone the same path as you, so read everything and a little patients with the seeed releases you will get there. :+1:

HTH
GL :slight_smile: PJ :v:

5

The following two links were enough to answer my questions. Thank you for your help.

1 Like
6

This is a serious issue nonetheless. I have the same issue after a squeaky clean install with a brand new 22.04 host and just running “apt update && apt upgrade” after the flash. Which I had to do because otherwise it wouldn’t even let me compile a driver for my EDIMAX wireless LAN adapter.
In the Nvidia link above (“Apt upgrade problem: Errors were encountered…”) Nvidia says that this isn’t an error message but a warning, but there are some practical problems:
If anybody tries to install Docker using the standard convenience script (" curl | sh && sudo systemctl --now enable docker") they will crash and burn because the script will abort any “apt install” command because of the error in the opening post (“E: Sub-process /usr/bin/dpkg returned an error code (1)`”, even if it’s supposed to be a warning.
Now Nvidia says “FYI, you won’t see such failure by moving to r32.5 or later L4T release versions”, but we’re now on 36.4 with JP 6.1 and it still has not been fixed.
Not sure if there’s anything the Seeed engineers can do there or we’ll have to wait for the custom 6.2 version. Until then we’ll have to install Docker manually or at least with a substantially modified script. Not good when you have dozens of IPCs.

7

Hello Uli,
My understanding is as follows: When we use the command ‘apt install [package]’, it installs the requested package, but because it also tries to upgrade faulty packages, it gives the error ‘E: Sub-process /usr/bin/dpkg returned an error code (1)’ for those faulty packages. For example, when I use the command ‘sudo apt install nano’, it installs the ‘nano’ application correctly, but it gives the ‘E: Sub-process /usr/bin/dpkg returned an error code (1)’ error for the faulty packages. I would like this issue to be resolved. Was your question answered?

8

This sudo apt-get upgrade command doesn’t work on third party/custom carrier boards, see our FAQ: Q7, Q8, Q9

For compiling certain projects that requires running the apt upgrade command, try comment this sentence and use apt install only.

1 Like
9

Hi Kaan, thanks for your explanation, that rounds out my understanding of why ‘apt upgrade’ can’t be launched. I was aware that ‘apt full-upgrade’ was a problem, but I’ve also been working with other boards where ‘apt upgrade’ never has been an issue. Based on this new info I’ll stop that across the board.

10

Hi Kevin,
Thanks for being so kind and pointing me to the Q&A. I should have gone over this before doing the flash. But at least I followed the flash instructions, lol!
There is still the issue of me being unable to compile a driver for my EDIMAX wireless LAN adapter. Right now ‘make’ crashes with the error ‘build directory does not exist’, because on the Seed image ‘build’ is a linked file, not a directory ("The problem seems to be that ‘build’ is a file and not a directory: /lib/modules/5.15.148-tegra/build → /home/gitlab-runner/builds/EV8MWGHX/0/awesome-se/jetson/jetpack/Linux_for_Tegra/source/kernel_out/kernel/kernel-jammy-src.
This gitlab symlink probably should not be there. I’ll do some more digging to see if I can fix the issue. Would be nice if you could just plug in a USB LAN adapter and voila, internet!

11

Hi Kevin,

Sorry for prodding a 7d old post, but will there be any updates that will address this? It seems like this is a good way to introduce a lot of security risks in the systems, if you are to deploy devices that may brick if you update them.