Hi everyone, hoping someone can point me in the right direction. I’m trying to get an IMX477 camera working on a Jetson Nano 4GB dev kit, following the Arducam native camera quick start guide. One quirk with my setup: I don’t have an SD card, so I’m booting the Ubuntu image from an external USB drive. The arducam-nvidia-l4t-kernel package won’t install at all - it dies during the post-installation script. Has anyone seen this before?
Thanks for the details. Before we dig in, can you confirm which L4T/JetPack version the Nano is currently flashed to? Also, if you can paste the full output from the dpkg install command, that would help a lot - the post-installation step can fail for a few different reasons.
Here’s the exact output I get when I try to install the package:
An unknown error occurred while installing dtoverlays.
dpkg: error processing package arducam-nvidia-l4t-kernel (–install):
installed arducam-nvidia-l4t-kernel package post-installation script subprocess returned error exit status 255
Errors were encountered while processing:
arducam-nvidia-l4t-kernel
So it’s the postinst script returning exit status 255. I’m not 100% sure of the L4T version off the top of my head - let me check.
That error means the postinst script is failing specifically while installing the dtoverlays, which is the step that updates the boot configuration. The docs recommend L4T 32.7.1 (JetPack 4.6.1), and that’s generally considered the most stable release for the Jetson Nano. If you’re not on that version, I’d flash to 32.7.1 first, then retry the driver install.
OK, so I went ahead and flashed the Nano to L4T 32.7.1 / JetPack 4.6.1 like you suggested, then tried the driver install again. I’m still booting from USB since I don’t have an SD card. Unfortunately it still fails - the installer just says “error while installing the driver”. I’ve attached a screenshot of what I’m seeing.
Thanks, I can see the screenshot. So even on 32.7.1 the install is failing, which means the version wasn’t the whole story. My current suspicion is the external USB boot setup - the dtoverlay install step writes to the boot partition/config, and with the rootfs running from USB instead of SD, that step may be looking at the wrong device. For now, the best next step is to run the install from a terminal and capture the complete text output rather than the GUI/popup - that will tell us whether it’s still the same postinst exit 255. I’ll keep digging into this and update the thread once I have more.