#Raspi Camera not Detected - causes

10 messages · Page 1 of 1 (latest)

rich mica
#

This issue is covered in the Setup Guide which also includes a Troubleshooting section if the not detected problem occurs. For my case the issue that caused the "No cameras available" when running 'libcamera-hello --list cameras' command was having Legacy camera support enabled on the Raspi SBC. This causes the system to detect cam as "raspi camera" with device as /dev/video0 regardless of version. With this device id I could not get the 'webRTC' service to work and had to use 'Adaptive MJPEG-streamer', defeating my reason for using crowsnest, real time streaming video. Having Legacy Support enabled is the correct way to get the cam working if not using crowsnest, which was my starting point when I added crowsnest to my already running printer setup. Once I disabled Legacy support the system detects the Pi cam as 'libcamera' with device id as listed in the guide. There is currently no mention of this circumstance in your guide or troubleshooting information. Would suggest you add this info in the setup guide as well as to the troubleshooting information.

You can easily duplicate this issue by running 'sudo raspi-config', enable Legacy support it will blank screen the webrtc stream every time on my setup.

Thanks for all your work I'm really impressed with the improved camera performance with this working.

opaque jay
#

You are totally right with your assumptions.
We already know about this but we decided not to add it at first into the troubleshooting as we discussed about some big changes internally that would need some big rewrites in the docs.
These changes now take a lot longer than planned. When I get some time, I will start rewriting some part of the docs as well as this problem. Not in detail as you wrote here but in some abbreviated form.

#

Also there is a bit more to this. It's not crowsnest that fails with webrtc, it's camera-streamer. Crowsnest is only a wrapper that starts it for you. We don't know why it isn't working with legacy. Also we are still not on the main branch but an old master branch. As we didn't yet test the main branch because lacking of time.
So I tested it recently and I confirmed it still not working. This was one variable we had to consider for example

#

Another thing is the mark as legacy stack. We thought it might get removed with bookworm. But now we can see it's still there, even if not listed inside raspi-config

#

About the "correct way to get camera work", that is simply wrong......
The correct way is with libcamera since bullseye. If you think about the Raspi Foundation as the one deciding. The chances are high that the legacy stack will be completely gone with trixie (next Debian version), as they already removed it from raspi-config

#

The only reason why we added legacy support is because of some fake v1 pi cams that a lot of people are buying. Those don't work with libcamera because of some wrong wiring of the led. I can send you some link for that later

#

And again to the topic of the correct way. The raspi foundation even gave a tool to access the libcamera stack as a normal v4l2 device. Like the legacy stack would do.
The tool is a bit hard to find. It's called libcamerify. It's inside the libcamera-tools package.

#

This shouldn't sound rude, sry if it read like that.
I just wanted to give some points we had to consider until now

opaque jay
rich mica
#

No offense taken Sir. Just wanted to pass along the info on how I got my setup to finally work and thank you folks for what you've done to make this avaliable.