Hi, I’ve got two issues on a Raspberry Pi running Raspbian. First, I can’t get the Raspberry Pi Camera Module 3 packages installed — apt keeps timing out while downloading. Second, my Hawk Eye 64 Mpx camera drops out while the program is running and just becomes unavailable.
The packages it’s stuck on are libqt5widgets5 5.15.2+dfsg-9+rpi1 (armhf) and libgtk-3-common 3.24.24-4+rpt12+deb11u3 (all).
On the camera side the app throws an ‘Unknown error’ and the log shows:
[12:37:57.133376596] [5093] WARN V4L2 v4l2_videodevice.cpp:2007 /dev/video0[15:cap]: Dequeue timer of 1000000.00us has expired!
[12:37:57.133547853] [5093] ERROR RPI pipeline_base.cpp:1374 Camera frontend has timed out!
[12:37:57.133612426] [5093] ERROR RPI pipeline_base.cpp:1375 Please check that your camera sensor connector is attached securely.
[12:37:57.133674351] [5093] ERROR RPI pipeline_base.cpp:1376 Alternatively, try another cable and/or sensor.
I’ve already rebooted and even set up a fresh system, but it keeps happening. The Hawk Eye was working fine right before this, so I’m not convinced it’s a hardware fault.
Thanks for the logs. The apt part is clearly network-related — both .deb downloads are timing out to the mirrors, so the packages never finish fetching. That’s separate from the camera timeout.
For the Hawk Eye 64MP, the ‘Dequeue timer expired’ and ‘Camera frontend has timed out’ lines mean /dev/video0 stopped delivering frames to the pipeline. Can you double-check the ribbon cable and the sensor connector? Also, does it fail at roughly the same point every run, or randomly? If you have another camera module, does the same program fail the same way?
I should add — I also have a BO371 IMX519 16 Mpx Sony camera on a different setup and it did something very similar. It was mounted on a drone flying at about 100 meters, and after roughly 3 minutes of program execution the camera suddenly stopped and became undetectable. Rebooting didn’t help, swapping cables didn’t help, and I tried different SD cards with different Raspbian OS versions too. That’s why I think it’s probably not a cable or sensor hardware issue.
Okay, that IMX519 detail is useful. We’ve updated the Arducam custom libcamera packages, which should cover the Camera Module 3 install/package fetch errors you hit first. As for the Hawk Eye timeout — since the IMX519 showed the same dilemma, we suspect the program/software in use rather than the hardware.
Please reinstall the updated custom libcamera packages with:
Thanks. I can’t make out everything from the screenshot, so can you send the whole log for the failing capture? By that I mean the exact command you ran plus the complete log output from it.
Sorry for the confusion. Run this to reproduce the capture:
libcamera-still -t 0
and paste the full output — the command and everything it prints. That should show where the dmaHeap buffer allocation is failing. To recap where we are: the original apt fetch/package errors should be handled by the updated libcamera packages, and the Hawk Eye/IMX519 timeouts look software-related rather than hardware. The remaining issue is the capture buffer allocation failure after the reinstall, which is still under investigation until we see the full log.