Hey everyone, I’m stuck after my Jetson Nano pulled an automatic update to JetPack 4.6.4. Since then the kernel camera driver is showing as unsupported, and my whole project depends on that camera. I haven’t changed anything in the code, it just updated on its own and now the camera won’t come up. I’m thinking about flashing back to an older JetPack, but I wanted to check if there’s a fix first.
Can you post a few more details? Which exact Jetson board are you using, and what does uname -r show after the update? Also, which camera module is it? That’ll help narrow down whether the driver was dropped in this L4T release.
It’s the NVIDIA Jetson Nano Developer Kit. Kernel is 4.9.337-tegra-32.7.4-20230608212426. I don’t have any error logs saved, unfortunately — the camera just fails to initialize now. No code changes on my side.
Thanks. So you’re on L4T 32.7.4 with that tegra kernel. What you’re describing lines up with the update replacing the kernel image and the camera driver not being carried over / not being available for that build. I’d double-check your Arducam module against the supported camera list for Jetson here: Introduction to Arducam Jetson Cameras - Arducam Wiki . You’ll want to confirm both the module and the JetPack version are listed together.
I checked around a bit. So does that mean there’s just no driver for this version right now? What’s the recommended move?
Correct — as of now there is no Arducam camera driver for L4T 32.7.4. The cleanest path is to flash the Jetson back to a previous JetPack/L4T version that still has camera driver support. That avoids fighting the auto-updated kernel.
Where should I look to figure out which version to flash? I don’t want to pick one and end up in the same spot.
Use the supported versions table in that Arducam doc I linked above. Check the supported camera modules and supported JetPack versions section, pick an earlier JetPack release that lists your camera module, and flash that. To recap: Arducam has no camera driver for L4T 32.7.4 right now, so downgrading/flashing to an earlier supported JetPack version is the recommended path. If you hit anything during the flash, post back with the exact L4T version you chose and any output.