Hi, I can’t get my Arducam stereo camera working at all. It’s supposed to be an OV2311 2MP*2 (the monochrome global shutter dual OV2311 module). I’m on a Raspberry Pi 4B and I followed the driver install instructions in section 1.1, but the camera just isn’t detected.
I installed the driver with the .sh file and there was no error at all, but then at step 1.2.1 the command dmesg | grep arducam returned absolutely nothing.
So I went back and tried installing the driver from the tar.gz file instead, and that one failed with:
install: cannot stat './bin/5.15.61-v7l+/arducam.ko': No such file or directory
install: cannot stat './bin/5.15.61-v7l+/arducam.dtbo': No such file or directory
And when I try to test it with arducamstill -t 0 I get:
Hardare version: b03111
No match to hardware version!
My kernel is 5.15.61 (v7l+). I’m starting to think the driver doesn’t support 5.15.61 yet, but I’m not sure. Any idea what’s going on? Screenshots of what I’m seeing:
Thanks for all the detail, that helps a lot. The “No match to hardware version!” line is usually the first sign that the camera driver isn’t loaded/probed properly at all, so dmesg | grep arducam coming back empty lines up with that.
A few things I want to nail down first:
Can you confirm exactly which OS image you’re running? For this camera you should be on Raspberry Pi OS Bullseye. If you flashed something else, the cleanest path is to re-burn Bullseye and start fresh, because a half-applied driver on a different base causes exactly this kind of confusing state.
Confirm the full environment: Pi 4B, kernel 5.15.61-v7l+, Arducam OV2311 2MP*2 stereo (dual OV2311, mono global shutter).
It would really help to get the diagnostic bundle. Please run the bug report tool from your Pi:
Hardare version: b03111
No match to hardware version!
Then the diagnostic:
dmesg | grep arducam
No output at all.
Then I went back and tried the tar.gz route, which gave me:
install: cannot stat './bin/5.15.61-v7l+/arducam.ko': No such file or directory
install: cannot stat './bin/5.15.61-v7l+/arducam.dtbo': No such file or directory
That error is what makes me think 5.15.61 just isn’t supported. I followed the instructions as written though, so I’m not sure what I’m doing wrong.
Thanks, that’s a lot clearer. So the 3 commands from section 1.1 are exactly the ones we care about here. Quick sanity check before we go further, because I want to be sure we’re comparing apples to apples.
I just ran the Pivariety kernel driver install myself on the same kernel (5.15.61-v7l+ on a Pi 4B) and the installation package worked fine on my side. So the package itself has the files it needs for your kernel, which means something in how the command was run (or what it printed) is the likely culprit.
Can you confirm you used exactly these three commands, nothing more, nothing less, and re-run them?
Then send me a screenshot of the full output of that last command (./install_pivariety_pkgs.sh -p kernel_driver). The actual text it prints is what I need to see, since that tells me whether the .ko/.dtbo actually got placed for your kernel version or whether it fell back to something else.
Yep, those are the only three commands I used, exactly as written. I re-ran them just now and here’s the output of the last one:
It doesn’t show any error, it just completes. But after that dmesg | grep arducam is still empty and arducamstill -t 0 still says “No match to hardware version!”. Should I be looking for a specific line in this output to confirm the driver went to the right place?
Okay, I can see the install ran through without complaining, so the output is at least consistent with a successful run on the surface. That’s exactly why I want to look at the live system state rather than the install log.
Next step: reboot the device, then re-run the bug report so we get fresh diagnostics.
This will produce an arducam-bug-report.txt in the current directory. Please attach that file here.
The reason a fresh report matters: the earlier install and the tar.gz attempt may have left things in a mixed state, and the bug report captures the kernel version, loaded modules, device tree overlays and camera detection exactly as they are after a clean boot. Once I have that I can tell you whether the driver is actually bound to the camera or not.
Got the report, thanks. Here’s where we stand so far, so we’re on the same page:
The Pivariety kernel driver install package works for 5.15.61-v7l+ on a Pi 4B in my testing, so we can rule out the package itself being broken for that kernel.
Your install runs without errors, but the camera still isn’t detected: dmesg | grep arducam is empty and the HAL only reports Hardare version: b03111 with No match to hardware version!.
The tar.gz install path fails for you with the missing 5.15.61-v7l+ arducam.ko / arducam.dtbo, which is a separate symptom and may just be you running that path on top of an already-modified install.
So the current conclusion is that the driver isn’t binding to your camera, but the install log alone doesn’t show why. The fresh bug report was the missing piece for diagnosis.
If you want to move forward in the meantime, the practical workaround is to re-burn a stock Bullseye image, apply the 3 driver commands once on a clean system, and reboot before testing, rather than mixing the .sh and tar.gz install routes. I’m going through the bug report now and will follow up with the next targeted step. Nothing is confirmed as the root cause yet, so hold off on more reinstalls until I get back to you.
