Hey everyone, I’m setting up a multi-camera rig on a Jetson Nano Developer Kit and hitting a wall trying to get the Arducam drivers installed. Here’s my environment:
I ran the install_full.sh script from Arducam’s repo and it keeps failing. Digging into the output, it looks like it’s trying to pull in a package called arducam-nvidia-l4t-kernel and dpkg is throwing a pre-dependency error. Anyone seen this before?
That sounds frustrating. Could you paste the exact dpkg error you’re seeing? The pre-dependency failure usually gives a pretty specific version constraint message that’ll tell us exactly what’s mismatched.
Sure, here’s the exact error from the package manager:
arducam-nvidia-l4t-kernel pre-depends on nvidia-l4t-core (<< 32.5-0)
Looks like it wants nvidia-l4t-core to be less than version 32.5, but my system is on L4T 32.7.6. I ran dpkg -l | grep nvidia-l4t-core and confirmed the installed version is tied to the 32.7.6 release. So it seems like the arducam kernel package just doesn’t support this L4T version?
Yeah, that’s exactly what’s happening. The arducam-nvidia-l4t-kernel package has a hard pre-dependency constraint: it requires nvidia-l4t-core to be strictly less than 32.5-0. Since you’re on L4T 32.7.6, the version of nvidia-l4t-core on your system is way past that threshold and dpkg refuses to proceed.
This isn’t something you can bypass with --force-depends either without risking a broken kernel module mismatch. What camera modules are you using exactly? And have you checked if there’s a newer branch of the Arducam repo that targets later L4T releases?
I’m using a few of their IMX219-based cameras in a multi-cam setup. I checked their GitHub and the install_full.sh script seems to be from what they recommend for Jetson Nano. I didn’t see a separate branch for newer L4T versions. The README mentions JetPack 4.5.x compatibility but nothing about 4.6.x.
Is there a workaround here or am I stuck until they release an updated kernel package? I’d rather not downgrade my entire BSP just for the camera drivers.
I’ve looked into this on our side and can confirm what you’re seeing — the arducam-nvidia-l4t-kernel package was built and tested against the L4T 32.5.x BSP and the pre-dependency constraint reflects that build target. The kernel interfaces changed between 32.5 and 32.7, so the module binaries wouldn’t be compatible even if you forced the install.
I’ve logged this in our internal documentation/wiki so the engineering team is aware that users on JetPack 4.6.3 / L4T 32.7.6 are blocked. For now, there isn’t an official workaround — the options are either roll back to an L4T 32.5.x-based JetPack (4.5.x) or wait for a rebuilt kernel package targeting the newer BSP. I don’t have an ETA I can share at the moment, but it’s on the radar.
Thanks for the detailed explanation. That makes sense even if it’s not the answer I was hoping for. I’ll keep an eye on the repo for updates. If anyone else reading this has managed to get the Arducam multi-cam stack working on JetPack 4.6.x through a different approach, I’m all ears.