ArduCam IMX519 kernel driver install fails: cannot find package on Raspberry Pi kernel 6.1.21-v7+

Raspberry Pi Cameras
1

Hi everyone, I’m trying to install the ArduCam IMX519 camera kernel driver on my Raspberry Pi but I keep hitting an error saying ‘Cannot find the corresponding package’ and something about an unsupported kernel version. Here’s what I ran:

wget -O install_pivariety_pkgs.sh https://github.com/ArduCAM/Arducam-Pivariety-V4L2-Driver/releases/download/install_script/install_pivariety_pkgs.sh
chmod +x install_pivariety_pkgs.sh
sudo apt update
./install_pivariety_pkgs.sh -p libcamera_dev
./install_pivariety_pkgs.sh -p libcamera_apps
./install_pivariety_pkgs.sh -p imx519_kernel_driver
git clone GitHub - ArduCAM/Arducam-Pivariety-V4L2-Driver: This driver is used for Arducam mipi camera with Pivariety board · GitHub

The libcamera steps seem okay but the imx519_kernel_driver step fails with this output:

Cannot find the corresponding package, please send the following information to [email protected]
Hardware Revision: a02082
Kernel Version: 6.1.21-v7+
Package: imx519_kernel_driver – bullseye-v5
You are using an unsupported kernel version, please install the official SD Card image(do not execute rpi-update): Raspberry Pi OS downloads – Raspberry Pi

Any idea what’s going wrong?

2

Welcome to the forum. Looking at the error output, the installer can’t find a matching package for your kernel version 6.1.21-v7+. The hardware revision a02082 is fine, but the kernel you’re running isn’t in the package list the script expects for bullseye-v5. That’s what triggers the ‘Cannot find the corresponding package’ message.

The first thing I’d suggest is installing the official Raspberry Pi OS SD card image (without running rpi-update) from Raspberry Pi OS downloads – Raspberry Pi and then running the install steps again on a clean image.

3

So I went ahead and installed everything from the official SD card image like you said, but I’m still getting the exact same error when I try to install the imx519 kernel driver. Same ‘Cannot find the corresponding package’ message with kernel 6.1.21-v7+.

4

Thanks for trying that. I’ve seen this before where the bundled manual is out of date and points people to old steps. The most reliable reference right now is the official documentation website:

https://docs.arducam.com/Raspberry-Pi-Camera/Native-camera/Quick-Start-Guide/#software-guide_1

Can you follow the software guide there exactly and let me know if the driver install still fails?

5

Okay, I went through the doc website you linked and redid the steps, but unfortunately I’m still getting the same result/error when installing the imx519 kernel driver.

6

Understood. Since the package lookup is failing, the next step is to refresh the installation package list and then reinstall. The script has a flag for that:

./install_pivariety_pkgs.sh -l

This updates the installation package list. Run that first, then re-run the imx519_kernel_driver install step:

./install_pivariety_pkgs.sh -p imx519_kernel_driver

If it still can’t find a matching package after that, we’ll need to dig further.

7

I already tried updating the package list like that and it didn’t help. Still the same ‘Cannot find the corresponding package’ error with Kernel Version 6.1.21-v7+.

8

Got it, thanks for confirming. Just to summarize where we are: the installer is failing because your kernel version 6.1.21-v7+ has no matching imx519_kernel_driver package for bullseye-v5. The steps I’d recommend trying are:

  1. Make sure you’re on the official Raspberry Pi OS SD card image and haven’t run rpi-update.
  2. Refresh the package list with:
    ./install_pivariety_pkgs.sh -l
  3. Then reinstall:
    ./install_pivariety_pkgs.sh -p imx519_kernel_driver

If the ‘Cannot find the corresponding package’ error still persists after updating the package list on a clean official image, then the issue is likely still tied to the unsupported kernel version (6.1.21-v7+), and it would need further investigation against the package list that the script is checking. For now that’s the current workaround to try, and we can keep troubleshooting from there if it still fails.