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

Thank you @mcorino for pointing me in the right direction. I also got stuck with the error:

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

2 things I overlooked in the wiki:

  1. Step 4/5 when to remove the jumper for recovery mode
  2. sudo tar xpf

Unpacking has to be done on an ext4 partition because of symlinks.

After it was stuck at boot for saying “A start job is running for End-user configuration after inial OEM installation.” for 30 minutes I unplugged and replugged it and it would boot normally. Now apt upgrade is giving issues configuring nvidia-l4t-kernel:

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-301-0000-G.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

Which makes total sense, because we’re supposed to stick with the version part of the jetpack. So thanks to @afsyd for pointing out we should:
apt-mark hold nvidia-l4t-display-kernel nvidia-l4t-kernel nvidia-l4t-kernel-dtbs nvidia-l4t-kernel-headers nvidia-l4t-kernel-oot-headers nvidia-l4t-kernel-oot-modules before apt upgrade.

1 Like

As of now, the problem still happens with JP6.1 and 6.2 with the ORIN NX 16GB.
If this happens, still with JP 6.1, why Seeed added JP 6.2 , that also doesn’t work, without first solve the issues with JP 6.1 ?

I did not do this and tried several times before almost giving up to upgrade the SSD.
So for awareness: People, use EXT4 (not NTFS).

The issue that we can not upgrade the kernel? I think it is “by design” and Seeed is not planning on enabling that.
Next buy will be a Nvidia branded device, this whole situation is to much hassle.

1 Like