Welcome to the forum! Your setup steps look mostly correct, but I think the overlay might be the issue. The imx462 overlay is for a different driver stack.
Can you try changing the dtoverlay line in /boot/config.txt from dtoverlay=imx462 to dtoverlay=arducam-pivariety?
After making that change, save the file and reboot with sudo reboot, then try libcamera-hello again. Let us know how it goes.
Thanks for the suggestion. I changed the overlay to dtoverlay=arducam-pivariety in /boot/config.txt, saved it, and rebooted. Unfortunately, libcamera-hello still gives me the same “Camera not available” error. No change at all.
Just to confirm, the full dtoverlay line in my config.txt now reads:
This will generate a file called arducam-bug-report.txt. Please send that file to me via private message and I’ll take a look at what might be causing the issue. It’ll give us details about your kernel version, loaded overlays, i2c bus state, and whether the camera sensor is being detected at all.
Appreciate the help, but I think I’m going to step back from troubleshooting this for now. I’ve spent a fair bit of time on it already and I’m not sure I want to go further down the diagnostic route at this point.
No worries, I understand. For what it’s worth, based on what you’ve shared, the most common causes for this “Camera not available” error with the Pivariety on libcamera would be:
The overlay not being picked up correctly (worth double-checking with dmesg | grep -i arducam after boot)
A kernel/driver mismatch from the install script
The ribbon cable orientation (the Pivariety connectors can be finicky)
If you decide to revisit this later, that bug report tool would give us a clear picture. Feel free to post back anytime and we can pick up where we left off.