RPi_Cam_Web_Interface: mmal_vc_component_create failed to create 'vc.ril.camera'
Hi, here is all data i think might be related to the issue Device: Raspberry Pi Zero W 2 OS: Raspbian 32 bit, updated Uname -a
Linux raspberrypi 5.10.63-v7+ #1459 SMP Wed Oct 6 16:41:10 BST 2021 armv7l GNU/Linux
vcgencmd vcos version
Oct 29 2021 10:50:02
Copyright (c) 2011 Broadcom
version b8a114e5a9877e91ca8f26d1a5ce904b2ad3cf13 (clean)
host buildbot
libcamera-hello --version
libcamera-apps build: 2a38ae93f143 21-10-2021 (14:49:17)
libcamera build: v0.0.0+3156-f4070274
Camera Module: Zero Cam Noir (Not sure if an official device to be honest. it is sold at all the official resellers. for example berrybase.de it uses the OV5647-Chip like the Raspberry Camera Version 1
Camera works fine with libcamera-jpeg
Initial Error
mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)
mmal: mmal_component_create_core: could not create component 'vc.ril.camera' (1)
sh: 1: /var/www/html/macros/error_hard.sh: Permission denied
Fixed the permission errror for now with chmod 777 -R /var/www/html/macros/
Afterwards the error of ./start.sh is
mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)
mmal: mmal_component_create_core: could not create component 'vc.ril.camera' (1)
Thank you for your help and the program!
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 19
This was originally tested on the medium Bullseye (Desktop, but not full) and the install.sh worked as intended and enabled legacy camera support and allowed things to run normally.
As per the wiki the raspi-config was used to enable camera support before the install was run.
Your comment on enabling legacy camera support via raspi-config was new to me as the original bullseye install didn’t have this (just the regular enable camera). I updated raspi-config and the legacy support option appeared in place of the original enable camera option. They must have changed that recently to better support users who had camera software they wanted to continue to use.
I ran this option on a working Bullseye with the camera working OK. I checked the /boot/config.txt and it had added a further start_X=1 line in and had removed the camera_auto_detect line whereas I had commented that one out. After the reboot the camera was still working OK.
However, I have yet to test what happens on a completely fresh Bullseye with just enabling the legacy camera support prior to running the install. It is possible it makes some of the changes I put into switch on legacy support redundant. I’ll report back when I have had a chance to do some further tests.
Using Buster is obviously possible to avoid these complications as that natively supports the raspberry camera without having to fiddle with legacy options.
The zero 2 has the same memory as the regular zero.
Pre-Bullseye the default GPU was 128 and this software was fine with that. So it may be that making it 128 would allow it to work OK. Removing the line altogether is not an option. I will try myself with 128.
Not that the libcamera programmes will not work with the legacy camera stack that is used here so don’t try to run any of those.