Jetson Orin NX J4012 JP6.0 to JP6.1 via APT fails

Community
1

Hi, i’m trying to upgrade via APT from JP6.0 to JP6.1 but it fails and the NVIDIA Guide does not cover the J4012 carrier board. Can you guide me to succeed?

I used this official guide: How to Install and Configure JetPack SDK — JetPack 6.1 documentation

My failure is described in the guide: ERROR. Procedure for A_kernel-dtb update FAILED.

But the fix does not work.
If you see the below error:

ERROR. Procedure for A_kernel-dtb update FAILED.

Use the following three commands, then re-attempt the upgrade. Do not reboot the device after running the below command, before re-attempting the upgrade.

sudo parted /dev/mmcblk0 -s rm 4
sudo parted /dev/mmcblk0 -s resizepart 3 67.9MB
sudo parted /dev/mmcblk0 mkpart A_reserved_on_user 67.9MB 101MB

sudo parted /dev/mmcblk0 -s rm 4
Error: Could not stat device /dev/mmcblk0 - No such file or directory.

But here is the full failed output:

Setting up nvidia-l4t-kernel (5.15.148-tegra-36.4.0-20240912212859) ...
Using the existing boot entry 'primary'
Warning: Cannot get compatible board name.
3767-000-0000--1--recomputer-orin-j401-
TNSPEC 3767-300-0000-M.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.0-20240912212859); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-kernel-headers (--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
                                                                                                                     No apport report written because MaxReports is reached already
                      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
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.0-20240912212859); 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.15No apport report written because MaxReports is reached already
                                                                                                                             No apport report written because MaxReports is reached already
                              .148-tegra-36.4.0-20240912212859); 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.0-20240912212859); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing 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.0-20240912212859); 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.0-20240912212859) ...
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/dkms.conf
Add config /etc/modprobe.d/iwlwifi.conf
Add config /etc/modprobe.d/nvgpu.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)
2

Sorry, reComputer J4012 is not compatible with JetPack 6.1 yet. Please install listed JetPack versions on the wiki page by the instructions strictly.

3
1 Like
4

Hi, thanks for your response. What is the reason for incompatibly of the J4012 with JP 6.1? I guess if it can run JP 6.0 then 6.1 shouldn’t be a problem?

5

As a third-party carrier board instead of official NVIDIA product, it has to be adapted with corresponding peripheral drivers on every JetPack versions. This is why every supported version has a standalone package on our wiki.

6

Ah ok, i understand this. but by when are you going to provide the new image? JP 6.1 is out for a long time already and has very powerful improvements. So it is not just a maintenance upgrade. Can you just provide it soon?

7

Thanks for your feedback. Our engineers are working on this currently, and we will update the wiki pages when finished.

8

Any timeline available for Jetpack 6.1 support?

1 Like
9

Please check the wiki page on December 21th.

1 Like
10

Thank you, much appreciated! I’ll keep an eye out. Can I just, out of curiosity and to understand the board better, ask whether support for Jetson 6.1 constitutes verifying whether partition configurations and pinmuxes and DTBs still work as expected everywhere, or also, as you hint at in a previous response, driver updates for peripherals? Which peripherals on the J-401 board would that be? Thanks!

11

Today is the day. But no JP6.1 so far. Will it happen today?

12

It’s there now! Thanks! I can flash it and it works. Is there an OTA update for it, too or only via re-flashing?

13

Could you please provide the download as Torrent? The routing and bandwith to your sharepoint is so bad, that it takes more than 10 hrs to download the file.

14

@azw Do you have an Orin NX 8Gb by any chance? My reComputer has an Orin NX 16Gb and my install is failing. The setup is fine because the Jetpack 6.0 release flashes just fine.

@Seeed_Harrison I noticed the mfi archive for the 8Gb version has a timestamp of “2024-12-25” in the name where the 16Gb version has “2024-12-04” in the name. Are you guys sure the right archive has been published for Orin NX 16Gb?

15

I have the 16 Gb. Flashed two of them without problems. What exactly is failing?

16

I get the error message “mount: /tmp/ci-YdujnpuaCP: must be superuser to use mount.” every time I try to flash the 6.1 version (tried multiple times).

This is the relevant section of the log:

Formatting APP partition /dev/nvme0n1p1 ...
mke2fs 1.46.5 (30-Dec-2021)
Discarding device blocks:        0/20971520                 done                            
Creating filesystem with 20971520 4k blocks and 5242880 inodes
Filesystem UUID: b00842fe-e3bc-41ce-a7d3-759c54325507
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000

Allocating group tables:   0/640       done                            
Writing inode tables:   0/640       done                            
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information:   0/640       done

Formatting APP parition done
mount: /tmp/ci-YdujnpuaCP: must be superuser to use mount.
[ 32]: l4t_flash_from_kernel: Failed to mount APP partition /dev/nvme0n1p1
17

Right, I seem to have messed up myself (surprise :roll_eyes:). Not sure exactly what but I cleaned up and unpacked the 6.1 mfi archive anew and fashed the J4201 again and this time it worked.

So, please forget I said anything.

2 Likes
18

I could flash 6.1 to the 16GB Orin NX without any issue. But right after apt upgrade it fails again:

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)

Why are your making it impossible to just use the carrier board? Do i always need to wait for your image and flashing it by loosing everything? I have paid 900 € for a device that i’m not able to upgrade on the standard way. How do you think your customers are satisfied about that?

19

Hi there,

So, Someone didn’t read the fine print :thinking: or has NO clue what this device is. It is NOT a Nvidia device…

It is a compatible device.(not a clone)
You need to read and follow the directions, including any official releases of JP for the unit. You know it’s a different device and peripheral hardware than the nvidia unit. so it is NOT a 1:1 software/firmware equality.
Just because Nvidia releases a JP 6.1 Seeed is NOT on the same schedule. Your assumption is just that!. 900eros is cheap compared to the Advantec or Nvidia’s NX platforms.
Give it time they will get it going.
BTW, the JP 6.0 is working very well on the J4012.

HTH
GL :slight_smile: PJ :v:

Your frustration is why I won’t get one, I’m going Real Nvidia, saving up the coin and reading everything. :v: