You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The video0 device seems correct, since when I have the docker container running and I try to run rpicam-hello again, I get an error saying the camera device is busy:
docker compose up -d octoprint
rpicam-hello -n
results in:
[51:56:06.125080613] [18260] INFO Camera camera_manager.cpp:327 libcamera v0.4.0+53-29156679
[51:56:06.305084670] [18263] WARN RPiSdn sdn.cpp:40 Using legacy SDN tuning - please consider moving SDN inside rpi.denoise
[51:56:06.311519080] [18263] INFO RPI vc4.cpp:447 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media3 and ISP device /dev/media0
[51:56:06.311653090] [18263] INFO RPI pipeline_base.cpp:1121 Using configuration file '/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml'
Mode selection for 2304:1296:12:P
SRGGB10_CSI2P,1536x864/0 - Score: 3400
SRGGB10_CSI2P,2304x1296/0 - Score: 1000
SRGGB10_CSI2P,4608x2592/0 - Score: 1900
[51:56:06.315163810] [18260] INFO Camera camera.cpp:1202 configuring streams: (0) 2304x1296-YUV420 (1) 2304x1296-SBGGR10_CSI2P
[51:56:06.315711413] [18263] ERROR V4L2 v4l2_videodevice.cpp:1095 /dev/video0[14:cap]: Unable to set format: Device or resource busy
ERROR: *** failed to configure streams ***
When the container starts up, it prints several errors pertaining to the video device that I can see, though maybe these won't cause the issues I am seeing (er...NOT seeing, haha):
octoprint | [services.d] starting services
octoprint | [services.d] done.
octoprint | MJPG Streamer Version.: 2.0
octoprint | i: Using V4L2 device.: /dev/video0
octoprint | i: Desired Resolution: 1536 x 864
octoprint | i: Frames Per Second.: 10
octoprint | i: Format............: JPEG
octoprint | i: TV-Norm...........: DEFAULT
octoprint | i: Could not obtain the requested pixelformat: MJPG , driver gave us: YUYV
octoprint | ... will try to handle this by checking against supported formats.
octoprint | ... Falling back to YUV mode (consider using -yuv option). Note that this requires much more CPU power
octoprint | Unable to query that the FPS change is supported
octoprint | : Inappropriate ioctl for device
octoprint | UVCIOC_CTRL_ADD - Error at Pan (relative): Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_ADD - Error at Tilt (relative): Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_ADD - Error at Pan Reset: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_ADD - Error at Tilt Reset: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_ADD - Error at Pan/tilt Reset: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_ADD - Error at Focus (absolute): Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Pan (relative): Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Tilt (relative): Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Pan Reset: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Tilt Reset: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Pan/tilt Reset: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Focus (absolute): Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at LED1 Mode: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at LED1 Frequency: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Disable video processing: Inappropriate ioctl for device (25)
octoprint | UVCIOC_CTRL_MAP - Error at Raw bits per pixel: Inappropriate ioctl for device (25)
octoprint | o: www-folder-path......: /usr/local/share/mjpg-streamer/www/
octoprint | o: HTTP TCP port........: 8080
octoprint | o: HTTP Listen Address..: (null)
octoprint | o: username:password....: disabled
octoprint | o: commands.............: enabled
octoprint | libv4l2: error turning on stream: Invalid argument
octoprint | Unable to start capture: Invalid argument
octoprint | i: Can't enable video in first time
octoprint | i: cleaning up resources allocated by input thread
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone!
Has anyone had success with the combination of a RPi Zero 2, Raspbian 12, Camera Module 3, and Octoprint Docker?
Host Camera Detection
The host system can see the camera and using:
the result is:
I can also generate a snapshot image using rpicam-hello, from the Camera Module 3, so the hardware and host system setup seems ok.
Docker Configuration
I am using the following docker compose configuration:
Debug
The video0 device seems correct, since when I have the docker container running and I try to run rpicam-hello again, I get an error saying the camera device is busy:
results in:
When the container starts up, it prints several errors pertaining to the video device that I can see, though maybe these won't cause the issues I am seeing (er...NOT seeing, haha):
Anyone have any ideas?
Beta Was this translation helpful? Give feedback.
All reactions