Hi, I’m reporting a problem with the stereolabs driver install on a Jetson Orin NX.
I’m trying to install stereolabs-zedlink-mono_1.3.0-SL-MAX9296-all-L4T36.3.0_arm64.deb
on a Jetson Orin NX running Jetpack 6.0, where the filesystem is flashed on an encrypted partition of the NVME SSD.
I have successfully installed this on an unencrypted SSD flashed using SDKmanager. However, when flashing and applying encryption I have to use the Nvidia scripts, and the resulting partitions are different.
On an encrypted drive we have 2 partitions:
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 400M 0 part /boot
├─nvme0n1p2 259:2 0 24.6G 0 part
│ └─crypt_root 253:0 0 24.6G 0 crypt /
ie /
and /boot
are in different partitions.
fstab
looks like this:
PARTUUID=<UUID> /boot ext4 defaults 0 1
/dev/mapper/crypt_root / ext4 defaults 0 1
/dev/mapper/crypt_UDA /mnt/crypt_UDA ext4 defaults 0 2
When I unpack the stereolabs dpkg, it writes an entry to the extlinux.conf
that looks like this:
LABEL Stereolabs
MENU LABEL Stereolabs kernel
LINUX /boot/Image
FDT /mnt/APP/boot/dtb/kernel_tegra234-p3768-0000+p3767-0000-nv.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=UUID=<UUID> rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0
OVERLAYS /boot/tegra234-p3768-camera-zedlink-mono-sl-overlay.dtbo
Here the FDT
line is incorrect - there is no /mnt/APP
mountpoint. When the system boots it doesn’t find the FDT file and hence the Stereolabs overlay isn’t loaded.
To fix this I have to edit the //boot/extlinux.conf
to remove the /mnt/APP
prefix.
This prefix is introduced by the board.py
script in /boot/stereolabs/utils/Jetson
, which thinks the system is an NFS mount and is incorrectly mounting /
to /mnt/APP
as in function _board_partition_mount()
.
Could you investigate and resolve please?
Note that changing /mnt/APP/boot/
to /boot/
on that FDT
line (and moving the Stereolabs DTBOs into the same folder as the other DTBOs and symlinking appropriately) allows the Orin to boot and allows the ZEDX driver to start.