Pi Zero W2 and Bullseye: *** no cameras available ***

[jrredondo]

Hello, same behaviour here.

I can confirm the same error running Bullseye in Raspberry Pi Zero 2 W with Pi Camera Module v2.1.
Libcamera shows the error "*** no cameras available ***"

On the other hand, I was able to run Raspistill and Raspivid properly following the steps described in this thread:
viewtopic.php?p=1936217

If you do that, running "vcgencmd get_camera" shows "supported=1,detected=1" and buildind userland libraries as described ends with a functional version of Raspistill. This is the only workaround that I have got.

I have tried to downgrade to Buster but it was impossible to achieve installation of Buster in Raspberry Pi Zero 2 W.
If this is possible, please, I would like to get information about how to do it.

The problem is that I am using Python to perform some computer vision tasks, and nowadays this is impossible in the Raspberry Pi Zero 2 W because apart from the error in libcamera, there is no Python Libraries like Picamera that support new method to access camera. So, please, provide some kind of method to install Raspberry OS Buster version in Zero 2 W while all these issues are solved in Bullseye.

Thanks in advance.

Buster does work on the Pi Zero 2 W, and images are still available for download. You just have to look for them yourself. For example, the download link for the full version of Raspberry Pi OS is "https://downloads.raspberrypi.org/raspi ... f-full.zip" If you go down to only "https://downloads.raspberrypi.org/raspi ... hf/images/", you'll find a full listing of images where you can get a Buster image (I believe it'll be the one from May 2021?). Same idea if you want the Lite version of the OS. If you are using the Pi Imager, you can choose the "Use Custom" option, select the image the downloaded image, and write your SD card. After that, Buster should work as-is on the Zero 2 W.

Thanks a lot! I confirm that May 2021 version of Buster works like a charm out of the box in Raspberry Pi Zero 2 W, including Python picamera libraries.
I will stay in this version avoiding any upgrade until all issues will be solved.

[dougie]

...still no update on this?
Publishing Bullseye with a number of serious shortcomings seems unprofessional... IMHO

[jamesh]

...still no update on this?
Publishing Bullseye with a number of serious shortcomings seems unprofessional... IMHO

This was missed in testing, so we didn't actually know it had these failures until after release. A relatively late change to another piece of sw introduced the error, which is why it was missed. Another issue was releasing a new piece of hw so close to a major sw release, which doesn't usually happen.

It's still being worked on, there are a number of fixes for various issues being queued up.

[dougie]

....six days later: still no news.... that's more than sad. Would be better to withdraw Bullseye until major bugs fixed IMHO.

For now the number of annoyed users asking same questions over and over again is growing day by day.

BR
Rals

[dAm2K]

Bringing to the world embedded systems working with linux is not a simple task.
Also, mantaining open source kernel drivers and tools with high level of compatibility on different devices and package them on a semi custom distro is very hard.
Please let the kernel developers and system engineers all the time they need to make this magic happening for all of us to enjoy.
Thank you!

[jamesh]

....six days later: still no news.... that's more than sad. Would be better to withdraw Bullseye until major bugs fixed IMHO.

For now the number of annoyed users asking same questions over and over again is growing day by day.

BR
Rals

When it's fixed, it will be announced. It's not been forgotten, it's just being a PITA to fix. I've asked the camera team for details on progress.

Bearing in mind the Zero2 has only just been released, but we've sold 40M Pi's of other types, which all work with the cameras, asking to withdraw Bullseye for this issue seems a little over the top. If people would use Google first rather than ask questions, then they would get faster answers and not clog up the forums with the same stuff over and over. Sadly they don't bother doing the slightest bit of research first.

[rboerner]

When it's fixed, it will be announced. It's not been forgotten, it's just being a PITA to fix. I've asked the camera team for details on progress.

Thank you for all of your help regarding this topic, it is much appreciated

[solar3000]

....six days later: still no news.... that's more than sad. Would be better to withdraw Bullseye until major bugs fixed IMHO.

For now the number of annoyed users asking same questions over and over again is growing day by day.

BR
Rals

When it's fixed, it will be announced. It's not been forgotten, it's just being a PITA to fix. I've asked the camera team for details on progress.

Bearing in mind the Zero2 has only just been released, but we've sold 40M Pi's of other types, which all work with the cameras, asking to withdraw Bullseye for this issue seems a little over the top. If people would use Google first rather than ask questions, then they would get faster answers and not clog up the forums with the same stuff over and over. Sadly they don't bother doing the slightest bit of research first.

Ummm...could you ...errr...google it for us?
I was not able to find anything; I was not able to google it myself.
Seriously, could you google it for us? I'm not being mean. It is a real request.

[jamesh]

....six days later: still no news.... that's more than sad. Would be better to withdraw Bullseye until major bugs fixed IMHO.

For now the number of annoyed users asking same questions over and over again is growing day by day.

BR
Rals

When it's fixed, it will be announced. It's not been forgotten, it's just being a PITA to fix. I've asked the camera team for details on progress.

Bearing in mind the Zero2 has only just been released, but we've sold 40M Pi's of other types, which all work with the cameras, asking to withdraw Bullseye for this issue seems a little over the top. If people would use Google first rather than ask questions, then they would get faster answers and not clog up the forums with the same stuff over and over. Sadly they don't bother doing the slightest bit of research first.

Ummm...could you ...errr...google it for us?
I was not able to find anything; I was not able to google it myself.
Seriously, could you google it for us? I'm not being mean. It is a real request.

Google what?

[dougie]

....picture of today on rpi zero 2W after update / upgrade / dist-upgrade / rpi-update

I've noticed new rpi EEPROM beeing deployed. However no success so far.

Code: Select all

pi@raspberrypi:~ $ dmesg | grep -i  imx219
[   11.755212] imx219 10-0010: Consider updating driver imx219 to match on endpoints
[   33.754513] imx219_vddl: disabling
[   33.754534] imx219_vdig: disabling
[   33.754556] imx219_vana: disabling

[jamesh]

You can get a fixed version of the software via rpi-update, however its pretty beta, make sure you use this commit, newer commits will not work. Should be officially released in a week or two, got some other issues that need fixing before things go in apt.

rpi-update c8e95532ecfbd8531bb5b4facff6403842cecad0

[dougie]

Thanks James!

Update went through without problems, but without changes re camera detection...

Code: Select all

 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   173  100   173    0     0    457      0 --:--:-- --:--:-- --:--:--   456
100  121M    0  121M    0     0   547k      0 --:--:--  0:03:47 --:--:--  376k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 5.10.76-v7+
 *** depmod 5.10.76+
 *** depmod 5.10.76-v8+
 *** depmod 5.10.76-v7l+
 *** Updating VideoCore libraries
 *** Using HardFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to c8e95532ecfbd8531bb5b4facff6403842cecad0
 *** A reboot is needed to activate the new firmware

'

Code: Select all

pi@raspberrypi:~ $ vcgencmd get_camera
supported=0 detected=0
pi@raspberrypi:~ $ dmesg | grep -i  imx219
[   11.555623] imx219 10-0010: Consider updating driver imx219 to match on endpoints
[   33.755454] imx219_vddl: disabling
[   33.755475] imx219_vdig: disabling
[   33.755496] imx219_vana: disabling
pi@raspberrypi:~ $

Code: Select all

pi@raspberrypi:~ $ sudo i2cdetect -y 10
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- 64 -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
pi@raspberrypi:~ $

[6by9]

"vcgencmd get_camera" is not relevant for libcamera.

It reports the cameras that the firmware is supporting, and the firmware explicitly backs off any cameras configured for the Linux kernel and libcamera as accessing the same peripheral from both Linux and the firmware is a sure fire way of causing problems.

Your kernel log shows that it has imx219 regulators, and has loaded the driver (the warning "imx219 10-0010: Consider updating driver imx219 to match on endpoints"). Also i2cdetect has reported UU against address 0x10, which means there is a kernel driver active on that address.

"ls /dev/video0" should list a device node. That is your camera driver.

[ledazul]

You can get a fixed version of the software via rpi-update, however its pretty beta, make sure you use this commit, newer commits will not work. Should be officially released in a week or two, got some other issues that need fixing before things go in apt.

rpi-update c8e95532ecfbd8531bb5b4facff6403842cecad0

I am able to use the camera after this update. Thanks!

[dougie]

"vcgencmd get_camera" is not relevant for libcamera.

"ls /dev/video0" should list a device node. That is your camera driver.

Indeed! Thanks again James!

Code: Select all

pi@raspberrypi:~ $ libcamera-hello
[15:44:30.033665973] [3730]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3156-f4070274
[15:44:30.121466645] [3730]  INFO Camera camera.cpp:937 configuring streams: (0) 1640x1232-YUV420
[15:44:30.121708311] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RG10 Score: 2218 (best 2218)
[15:44:30.121822947] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 2041.48 (best 2041.48)
[15:44:30.121902478] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RG10 Score: 1500 (best 1500)
[15:44:30.121973884] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RG10 Score: 5004.81 (best 1500)
[15:44:30.122049040] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt pRAA Score: 1718 (best 1500)
[15:44:30.122120238] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1541.48 (best 1500)
[15:44:30.122192894] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt pRAA Score: 1000 (best 1000)
[15:44:30.122262998] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pRAA Score: 4504.81 (best 1000)
[15:44:30.122340706] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RGGB Score: 3218 (best 1000)
[15:44:30.122410810] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RGGB Score: 3041.48 (best 1000)
[15:44:30.122482894] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RGGB Score: 2500 (best 1000)
[15:44:30.122552789] [3732]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RGGB Score: 6004.81 (best 1000)
[15:44:30.122798414] [3732]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected mode: 1640x1232-pRAA
[15:44:30.168190493] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[15:44:30.168394451] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[15:44:30.168501066] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[15:44:30.168652159] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[15:44:30.168713878] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[15:44:30.168776430] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[15:44:30.168868721] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[15:44:30.168926065] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[15:44:30.168992628] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[15:44:30.169048461] [3736]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[15:44:30.170112574] [3732]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[15:44:30.170175647] [3732]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[15:44:30.170225543] [3732]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[15:44:30.252194399] [3732]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[15:44:30.285758264] [3732]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[15:44:30.320105981] [3732]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[15:44:30.352374118] [3732]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[15:44:30.385618296] [3732]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[15:44:30.421025335] [3732]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[15:44:30.452731077] [3732]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)

[jamesh]

Don't thank me, got the information from 6by9 when dealing with another customer!

[brianbgarber]

Hey! I just did a update/upgrade and it looks like there is progress! But, I'm still getting a weird error:

Code: Select all

[0:04:00.686041475] [1456]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:04:00.783633302] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:04:00.817315925] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:04:00.851863821] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:04:00.884413352] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:04:00.917951231] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:04:00.952089381] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:04:00.988258344] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)
terminate called after throwing an instance of 'std::runtime_error'
  what():  failed to import fd 19
Aborted

Thoughts?

[6by9]

Hey! I just did a update/upgrade and it looks like there is progress! But, I'm still getting a weird error:

Code: Select all

[0:04:00.686041475] [1456]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:04:00.783633302] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:04:00.817315925] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:04:00.851863821] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:04:00.884413352] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:04:00.917951231] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:04:00.952089381] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:04:00.988258344] [1456]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)
terminate called after throwing an instance of 'std::runtime_error'
  what():  failed to import fd 19
Aborted

Thoughts?

viewtopic.php?t=323547

[brianbgarber]

Fantastic! I used the -n option and was able to retrieve a jpeg w/o problem.

Thanks!

[zeta1992]

I follow the instructions but I still have problems with my 2 w raspberry.

Doing that :
pi@raspberrypi:/boot $ LIBCAMERA_LOG_LEVELS=0 libcamera-vid -t 0
Preview window unavailable
[0:44:11.424836122] [3759] DEBUG IPAModule ipa_module.cpp:329 ipa_rpi.so: IPA module /usr/lib/arm-linux-gnueabihf/libcamera/ipa_rpi.so is signed
[0:44:11.425075400] [3759] DEBUG IPAManager ipa_manager.cpp:240 Loaded IPA module '/usr/lib/arm-linux-gnueabihf/libcamera/ipa_rpi.so'
[0:44:11.425228582] [3759] DEBUG IPAModule ipa_module.cpp:329 ipa_vimc.so: IPA module /usr/lib/arm-linux-gnueabihf/libcamera/ipa_vimc.so is signed
[0:44:11.425326293] [3759] DEBUG IPAManager ipa_manager.cpp:240 Loaded IPA module '/usr/lib/arm-linux-gnueabihf/libcamera/ipa_vimc.so'
[0:44:11.425443797] [3759] INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3156-f4070274
[0:44:11.425737452] [3763] DEBUG Camera camera_manager.cpp:106 Starting camera manager
[0:44:11.433274200] [3763] DEBUG DeviceEnumerator device_enumerator.cpp:224 New media device "bcm2835-codec" created from /dev/media1
[0:44:11.433643951] [3763] DEBUG DeviceEnumerator device_enumerator_udev.cpp:95 Defer media device /dev/media1 due to 4 missing dependencies
[0:44:11.436783998] [3763] DEBUG DeviceEnumerator device_enumerator_udev.cpp:320 All dependencies for media device /dev/media1 found
[0:44:11.436869365] [3763] DEBUG DeviceEnumerator device_enumerator.cpp:252 Added device /dev/media1: bcm2835-codec
[0:44:11.437744080] [3763] DEBUG DeviceEnumerator device_enumerator.cpp:224 New media device "bcm2835-isp" created from /dev/media0
[0:44:11.437979348] [3763] DEBUG DeviceEnumerator device_enumerator_udev.cpp:95 Defer media device /dev/media0 due to 4 missing dependencies
[0:44:11.441097936] [3763] DEBUG DeviceEnumerator device_enumerator_udev.cpp:320 All dependencies for media device /dev/media0 found
[0:44:11.441190595] [3763] DEBUG DeviceEnumerator device_enumerator.cpp:252 Added device /dev/media0: bcm2835-isp
[0:44:11.442020829] [3763] DEBUG Camera camera_manager.cpp:149 Found registered pipeline handler 'PipelineHandlerRPi'
[0:44:11.442241357] [3763] DEBUG Camera camera_manager.cpp:149 Found registered pipeline handler 'SimplePipelineHandler'[0:44:11.442460583] [3763] DEBUG Camera camera_manager.cpp:149 Found registered pipeline handler 'PipelineHandlerUVC'
[0:44:11.442520949] [3763] DEBUG Camera camera_manager.cpp:149 Found registered pipeline handler 'PipelineHandlerVimc'
ERROR: *** no cameras available ***

pi@raspberrypi:/boot $ ls /dev/video*
/dev/video10 /dev/video11 /dev/video12 /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/video18


It still don't find the camera!!

[capmcrackawaka]

Is there any update on this? Last post in this thread was over a month ago, however I don't see any update about whether the image was fixed, and I don't see any work-arounds. The camera I am using works just fine with my raspberry pi 4 running bullseye. I'm having problems on a pi zero 2 running raspbian light bullseye.

Code: Select all

$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/LINUX 11 (bullseye)

I have enabled the camera and glamor graphics acceleration as recommended in another thread.

libcamera-still does not work. None of the libcamera commands do:

Code: Select all

$ libcamera-still
INFO Camera camera_manager.cpp.293 libcamera v0.0.0+3156-f4070274
ERROR: *** no cameras available ***

This is what vgencmd shows:

Code: Select all

$ vgencmd get_camera
supported-0 detected=0

[therealdavidp]

An updated Bullseye image was released yesterday (28 Jan) which should have many of these problems fixed. Are you able to try that?

[6by9]

An updated Bullseye image was released yesterday (28 Jan) which should have many of these problems fixed. Are you able to try that?

Or just

Code: Select all

sudo apt update
sudo apt dist-upgrade

on an existing Bullseye system will pull in the updates. "uname -a" should report 5.10.94 IIRC.

[bben]

I tried with an up-to date bullseye on 2 Raspberry Pi Zero 2W with 2 different cameras and it doesn't work in the specific combination libcamera+bullseye + RpiZero 2W:

#0:
Linux rpi0 5.10.92-v7+ #1514 SMP Mon Jan 17 17:36:39 GMT 2022 armv7l GNU/Linux

$ dmesg | grep imx
[ 10.803342] imx219 10-0010: Consider updating driver imx219 to match on endpoints

$ sudo i2cdetect -y 10
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- 64 -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

$ libcamera-hello
Preview window unavailable
[0:24:48.559795243] [1498] INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3406-e96d0201
ERROR: *** no cameras available ***

$ libcamera-hello --version
libcamera-apps build: 7ac5197216ea 01-02-2022 (14:49:18)
libcamera build: v0.0.0+3406-e96d0201

#1:
$ uname -a
Linux rpi64 5.10.92-v8+ #1514 SMP PREEMPT Mon Jan 17 17:39:38 GMT 2022 aarch64 GNU/Linux

I tried the same hardware with the buster and the old stack and it works fine.
I also tried to update the kernel with rpi-update but that broke wifi so I couldn't try.

Something weird happened: I tried switching between old stack and new stack on bullseye, and it worked once with libcamera. Maybe because the camera was activated with raspistill and was still activated after a soft reboot?

Note that RPI4 + bullseye 64 bits + IMX219 works fine.

Any idea?
Thanks!