Hi, I’m trying to install the ToF camera dependencies on my Jetson module and the installer just fails on me. I ran the dependency install script and it bails out instead of installing anything. Not sure what I’m missing here, hoping someone can point me in the right direction.
Happy to help. Can you paste the exact error output you’re seeing, plus the kernel version you’re running and which package you’re trying to install? That’ll tell us whether the installer can find a matching package for your setup.
Sure, here’s what it prints out:
Cannot find the corresponding package, please send the following information to [email protected]
Hardware Revision:
Kernel Version: 4.9.253-tegra
Package: kernel_driver – Bionic Beaver-arm64
You are using an unsupported kernel version, please install the official SD Card image(do not execute rpi-update):
I left the Hardware Revision line blank because I honestly don’t know what value it wants there. The Kernel Version and Package are exactly what the script detected.
Thanks, that output is useful. Two things stand out:
- “Cannot find the corresponding package” means the installer wasn’t able to match your hardware/kernel combination to a prebuilt driver package.
- Your kernel is 4.9.253-tegra. The -tegra suffix indicates an NVIDIA Jetson/Tegra platform, which the installer is flagging as an unsupported kernel version. The Raspberry Pi OS recommendation in that message is just the script’s default fallback text, it doesn’t apply to a Jetson.
The core problem is that the installer needs your exact Jetson model/revision to pick the right kernel driver package, and the Hardware Revision field came back blank which is probably why the match failed.
That makes sense. So how do I find out what it needs for the Hardware Revision? I didn’t see anything obviously labeled that way when I was looking around. Is there a command I should run?
Easiest way for us to identify it: can you send pictures of the Jetson device? Front and back. The silkscreen on the module usually shows the exact model and revision, and that’s what we need to give you the correct driver/package. Also, if you can run uname -a and cat /etc/nv_tegra_release (or cat /etc/nv_boot_control.conf on newer images) that would give us the module info from the OS side as well.
Ok, I’ll get the photos together. Before I do that, just to double check, is there any chance this is something I can fix without the right package? Like forcing it to use a generic build?
I’d avoid forcing a generic build. The kernel driver is compiled against a specific kernel ABI, and with 4.9.253-tegra a mismatched module will typically either refuse to load or cause the camera to fail on probe. Getting the correct package for your actual module revision is the reliable path. Send the front/back photos when you can and we’ll match it.
Quick update on this one. I ended up reinstalling and now it works. I went back through the whole dependency install from scratch and this time it completed without the unsupported kernel error.
For reference, here’s what I was getting before, with the same environment:
Kernel Version: 4.9.253-tegra
Package: kernel_driver – Bionic Beaver-arm64
Cannot find the corresponding package, please send the following information to [email protected]
Kernel Version: 4.9.253-tegra
Package: kernel_driver – Bionic Beaver-arm64
You are using an unsupported kernel version, please install the official SD Card image (do not execute rpi-update):
So same kernel, same package selection, but after the reinstall it goes through fine. After reinstallation it works now!
Good to hear it’s working now. Just to close the loop for anyone else reading this thread: the original error is the installer failing to match a driver package to the detected hardware/kernel combination, and the “unsupported kernel version” line for a 4.9.253-tegra kernel is the installer’s generic fallback message rather than a real Jetson incompatibility.
In this case a clean reinstall of the dependencies resolved it, likely because the earlier run left the environment in a partially configured state that prevented the package match from completing. If it comes back after a future kernel or image update, the fastest way to get the correct package is to confirm the exact Jetson module and revision (front/back photos of the device or the values from uname -a and the Tegra release file) before reinstalling.
Marking this as resolved for now. If the error reappears, reply here and we’ll pick it back up.