New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not enough buffers provided by V4L2VideoDevice on RPi3B #144
Comments
Hi, I've just tried this on a Pi 3 and it seemed to work OK. Can you perhaps say:
Thanks! |
Same issue attaching versions.
|
@Rakhmanov Thanks for attaching this extra information. I can't see where you are getting a "not enough V4L2 buffers" error like the OP, so it's not immediately clear to me whether this is the same problem or something else. Can you perhaps clarify? Thanks! |
@davidplowman This is what I get using an RPi 3B with the camera module attached when attempting to run libcamera-hello: Seems to be along the lines of what the OP is describing. This is with a fresh install of RPi OS Bullseye. |
@miztroh Thanks for this information. I'm struggling to reproduce the same thing, here's what I've tried on a Pi 3B:
Again, I'm not convinced this is the same problem as the OP, after all, the error message is different, and I'm guessing you don't have the same symptom that it works with smaller frame sizes but not larger ones? If you're still seeing this problem, could I perhaps ask you to post a new bug report? Could I also please ask for the following information in the new bug report:
Thanks very much! |
I am experiencing the same error. in /boot/config.txt I replaced dtoverlay. Before that it did not detect camera.
Before changing /boot/config.txt i always got this error: GPU memory is set to 256 libcamera-hello --version
uname -a
v4l2-ctl --list-devices
Running locally, display attached:
Running over ssh, display attached, no X forwarding:
dmesg:
|
Thanks very much for this information. This does look like the same kind of problem as the OP, and it certainly seems like you're running out of CMA memory. A few things to check:
Thanks! |
I got it to work! Almost entire day wasted because of no option to fall back to picamera... @davidplowman you suggested to re-enable Glamor. When I did, this added following line to /boot/config.txt: I tested with original dtoverlay Conclusion:to solve If there is no This is just a temporary solution though. I would expect camera auto-detect, not hard-coding. For some reason usb keyboard takes ages to start working (it started occuring when i added dtoverlay=imx477). |
Hi everyone, I'm going to close this bug because there doesn't appear to be any further information on the original problem, and various other bugs have crept in, at least some of which appear to be quite different and I'm afraid that I'm struggling a bit to understand what are still live issues and what are not. But I'd like to encourage everyone who is still experiencing a problem to please file a new bug report of your own describing your issue. Please include all the information mentioned here: #144 (comment) . Also the result of Thanks very much! |
Followup I removed dtoverlay=vc4-kms-v3d again to reproduce the error
Note. GPU memory is still set to 256 MB.
|
Hi, thanks for this information. It's clear that this configuration has insufficient CMA memory so libcamera is going to struggle. You will need to put back either |
I received the same buffer error as @katyaxm on a Zero W running bullseye, which led me to this bug report. I had initially set gpu_mem to 256M while troubleshooting a camera I was having some difficulty with (yep, half the Zero W's memory, ouch!). Now that I have the camera recognized, and verified it was able to produce an image on buster, switching to an sd card with bullseye installed and libcamera gave me the buffer error. At @davidplowman's suggestion to check /proc/meminfo for Cma memory:
... which seemed a bit low. Since libcamera doesn't use the gpu for the cam, I dropped gpu_memory back to the default of 76M and rebooted. Checking /proc/meminfo a second time:
... and sure enough, libcamera-hello now functions - even the preview window works w/ a monitor attached. It seems like this error could be triggered by merely having too much memory allocated to the gpu, leaving too little free for Cma. |
Hi, if useful to others - I had a related problem when using IMX477 and touch screen at same time I can however use dtoverlay=vc4-fkms-v3d and get both - but then you see [0:00:35.383195367] [2235] INFO Camera camera.cpp:1029 configuring streams: (0) 1280x720-YUV420 |
I’m stuck at the same point. Any solutions yet? |
I am having the same problem with touchscreen and camera. With dtoverlay=vc4-kms-v3d, the camera works (imx219) but no touchscreen. |
C |
Hey
I've used libcamera-apps on RaspberryPi4B with no problems, but now that I am trying to run the same thing on RaspberryPi3B I'm getting the following output which says there's not enough memory provided by V4L2VideoDevice:
If I lower the width and height to 1280x720 It'll work with the following output:
This problem did not occur in RaspberryPi4. I have dedicated 128M to gpu_mem. Also there's no problem when using raspivid, it only occurs when using libcamera-vid and camera resolution of 1920x1080.
The text was updated successfully, but these errors were encountered: