Pivariety B0333 camera not responding on Raspberry Pi Bullseye after reboot

Raspberry Pi Cameras
1

Hi everyone,

I just picked up a Pivariety Module B0333 and I’m trying to get it running on a Raspberry Pi. I followed the manual exactly and everything goes fine right up to the point where it asks me to reboot and I press ‘y’. From there it all falls apart - when I try to check the camera status I get no response whatsoever, and none of the other steps in the manual do anything either. It’s just silent.

I’m on the latest Bullseye release of Raspberry Pi OS. I’ve reinstalled it a few times and started over from scratch, same result every time. I also checked that the module is seated correctly on the connector.

Has anyone run into this? Not sure what I’m doing wrong.

2

Hi, sorry you’re hitting this - let’s narrow it down before we go further.

A couple of things I need:

  • Which guide are you following exactly? Link it or paste the steps so I can match what you’re seeing.
  • After the reboot, what does i2cdetect -y 1 show? Paste the output here.
  • Also run dmesg | grep -i arducam and paste whatever comes back.

That’ll tell us if the Pi is even detecting the module and whether the driver is loading at boot.

3

I’m following the official Pivariety driver install guide for Bullseye, the one with the install script.

Here’s what I get:

i2cdetect -y 1 prints the usual grid but every cell is dashes - no address shows up at all.

dmesg | grep -i arducam returns nothing, completely empty.

The install script itself ran with no obvious errors and told me to reboot, which I did. After that, nothing.

4

Thanks, that’s useful. If there’s no i2c device and no arducam messages in dmesg, the driver probably isn’t loading or the module isn’t being probed at boot.

To dig deeper I need a full diagnostic dump. Please run these three commands on the Pi:

wget -O arducam-camera-bug-report https://github.com/ketai-dhr/arducam-camera-bug-report/releases/download/tools/arducam-camera-bug-report
chmod +x ./arducam-camera-bug-report
./arducam-camera-bug-report

That generates an arducam-bug-report.txt in whatever directory you ran it from. Attach that file to your next reply and I’ll go through it.

5

Done - ran all three, it finished and dropped the txt file in the directory. Attached it here. What are you seeing?

6

Got the report, thanks. Looking through it, the driver install doesn’t look like it completed cleanly - there are errors in the build log around the sensor driver, which would explain why the module never gets probed and you get no camera status.

Can you do a clean retry?

  1. Start from a fresh Bullseye image.
  2. Fully update first (sudo apt update && sudo apt full-upgrade -y) and reboot.
  3. Re-run the Pivariety install script and watch the output for any errors.
  4. Reboot again, then check i2cdetect -y 1 and the camera status.

If it still fails, grab a fresh arducam-bug-report.txt and attach it here.

7

Hey, just wanted to follow up - this particular problem is solved now! Getting the Pivariety driver / module working on the Pi is sorted. Thanks for the help.

8

Great to hear it’s working now - thanks for confirming.

Quick summary for anyone else reading the thread: the module wasn’t being detected at all (empty i2cdetect -y 1, no arducam lines in dmesg, no camera status), which pointed to the driver not loading rather than a seating/connection issue. The bug report helped confirm the install wasn’t clean. After starting from a fresh Bullseye image and re-running the install, the module came up correctly.

If it ever goes silent again, just run the arducam-camera-bug-report tool, attach the generated txt, and we’ll take another look.