Having trouble getting my Arducam 8MP PTZ camera (model B01678MP) to work on a Raspberry Pi 5 4GB. After rebooting, libcamera-hello just says “no cameras are available”. The weird part is the PTZ/I2C side seems fine - I can pan and tilt - but the image sensor is never detected. I’m starting to suspect a V4L2 driver incompatibility with the IMX219 sensor on this hardware. Anyone else seen this?
Can you share a bit more about your setup? What’s in your config.txt, which CSI port the camera is on, and what cable are you using? Also which OS/kernel version are you on?
Sure. Raspberry Pi 5 4GB, but I’ve also tested on a Raspberry Pi 3. The camera is the Arducam 8MP PTZC B01678MP with an IMX219 sensor, using the Arducam V4L2 driver. It’s connected through a 15-pin to 22-pin camera cable because the PTZ board uses the smaller 15-pin connector. I’ve got other 5MP/8MP and OV5647 cameras working on the same 22-pin Pi CSI interface with that cable, so the cable itself seems fine.
Okay, let’s start simple. For a camera on CSI0, make sure config.txt has dtoverlay=imx219,cam0 and reboot. If that doesn’t help, change it to dtoverlay=imx219 and move the camera module to the camera 1 connector instead of camera 0, then reboot again. Note the Pi 5 CSI interface is 22-pin while the PTZ camera is 15-pin, so you definitely need a 15-pin to 22-pin cable for this module.
I already followed the quick-start docs. I had dtoverlay=imx219,cam0 in config.txt and rebooted. Running libcamera-hello and sudo libcamera-vid -t 0 both come back with “no cameras are available”. Dependencies including opencv are installed.
Let’s isolate further. Change dtoverlay=imx219,cam0 to just dtoverlay=imx219, connect the module to camera 1 instead of camera 0, and reboot. Then run libcamera-hello again and paste the full output if it still fails.
Done that. Changed to dtoverlay=imx219, moved it to camera 1, rebooted - same result, “no cameras are available”. I also tried rolling back to older firmware with sudo rpi-update d16727d, no change. Then I moved the whole setup to a Raspberry Pi 3 and got the same errors, so it doesn’t look Pi 5 specific.
Thanks. Since the same failure happens on the Pi 3 and the Pi 5, and your cable is already proven with the OV5647, this is looking less like a driver/compatibility issue. Let me take a closer look at the device itself - I’ve sent you remote support details in a private message, please check your messages.
I tried the remote session but it kept resetting the password and wouldn’t connect properly. Anyway, just to summarize: PTZ and I2C commands work fine, but the image sensor never shows up as a camera.
That combination is actually a strong clue. I2C and PTZ working means the control path (control board) is functioning. The image sensor not being detected at all - across two different Pis, with a known-good cable - points at the camera image sensor board itself rather than the control board.
Can you confirm which board is actually at fault? I don’t want to swap the wrong part and go through all this again. The PTZ/I2C working while the sensor is dead does make me think it’s the sensor board.
Confirmed - it’s the camera board (the image sensor board), not the control board. My earlier note about the control board was a mistake on our side and has been corrected. The evidence fits: I2C/PTZ is fine on the control side, but libcamera never enumerates a camera on either the Pi 5 or Pi 3, using a cable that works with other sensors.