# Problems with Motioneye on Dietpi using v4l2 cameras at all
**URL:** https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220
**Category:** Troubleshooting
**Created:** [30 June 2023 13:36 UTC](https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220 "2023-06-30T13:36:55Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@akrael](https://dietpi.com/forum/u/akrael)
#### Post date: [30 June 2023 13:36 UTC](https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220/1 "2023-06-30T13:36:56Z")
### Creating an issue
#### Required Information
- DietPi version | `cat /boot/dietpi/.version`
G\_DIETPI\_VERSION\_CORE=8
G\_DIETPI\_VERSION\_SUB=18
G\_DIETPI\_VERSION\_RC=2
G\_GITBRANCH=‘master’
G\_GITOWNER=‘MichaIng’
G\_LIVE\_PATCH\_STATUS[0]=‘not applicable’
- Distro version | `echo $G_DISTRO_NAME $G_RASPBIAN`
bookworm 0
- Kernel version | `uname -a`
Linux MotionEyeTwo 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
- Architecture | `dpkg --print-architecture`
arm64
- SBC model | `echo $G_HW_MODEL_NAME` or (EG: RPi3)
RPi 4 Model B (aarch64)
- Power supply used | (EG: 5V 1A RAVpower)
Does not change anything, i’ve tried various
- SD card used | (EG: SanDisk ultra)
SAN Disk Max Endurance (the white ones) 32 GB
#### Additional Information (if applicable)
- Software title | MotionEye
- Was the software title installed freshly or updated/migrated?
Yes, freshly installed
- Can this issue be replicated on a fresh installation of DietPi?
Yes
#### Steps to reproduce
1.) Login to Motioneye
2.) Try to configure a V4L2 Camera
#### Expected behaviour
The camera should light up
#### Actual behaviour
The does not show anything in the webinterface
#### Extra details
```auto
sudo journalctl -u motioneye
Jun 30 15:24:34 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [ERR] [VID] v4l2_device_capability: Device does not support capturing.
Jun 30 15:24:34 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [ERR] [VID] vid_start: V4L2 device failed to open
Jun 30 15:24:34 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [WRN] [ALL] motion_init: Could not fetch initial image from camera
Jun 30 15:24:34 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [WRN] [ALL] motion_init: Motion continues using width and height from config file(s)
Jun 30 15:24:40 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [WRN] [ALL] mlp_retry: Retrying until successful connection with camera
Jun 30 15:24:40 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [ERR] [VID] v4l2_device_capability: Device does not support capturing.
Jun 30 15:24:40 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [ERR] [VID] vid_start: V4L2 device failed to open
Jun 30 15:24:50 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [WRN] [ALL] mlp_retry: Retrying until successful connection with camera
Jun 30 15:24:50 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [ERR] [VID] v4l2_device_capability: Device does not support capturing.
Jun 30 15:24:50 MotionEyeTwo motion[2781]: [1:ml1:Camera1] [ERR] [VID] vid_start: V4L2 device failed to open
```
→ If i try that on a fresh install of motioneyeos it works like a charm…
---
### Author:  [@Jappe](https://dietpi.com/forum/u/Jappe)
#### Post date: [30 June 2023 14:12 UTC](https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220/2 "2023-06-30T14:12:18Z")
What kind of cam do you use? An USB cam or the camera module?
---
### Author:  [@akrael](https://dietpi.com/forum/u/akrael)
#### Post date: [30 June 2023 14:15 UTC](https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220/3 "2023-06-30T14:15:24Z")
A noname camera module from Amazon:
> **[für Raspberry-Pi-Infrarot-Nachtsicht-IR-Kamera mit Acryl-Halter-Fall,...](https://www.amazon.de/Himbeer-Pi-Infrarot-Nachtsicht-IR-Kamera-Acryl-Halter-Fall-Einstellbarer-Fokus-Webcam-Security-Monitore/dp/B07ZV81493)**
>
> für Raspberry-Pi-Infrarot-Nachtsicht-IR-Kamera mit Acryl-Halter-Fall, Einstellbarer Fokus-Webcam für Pi 4 / Pi 3 B + / Pi 3, Anzug für Home Security-Monitore, DIY, 3D-Drucker: Amazon.de: Computer & Zubehör
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [30 June 2023 16:02 UTC](https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220/4 "2023-06-30T16:02:07Z")
probably asking the question on MotionEye Github would be an option [Issues · motioneye-project/motioneye · GitHub](https://github.com/motioneye-project/motioneye/issues)
---
### Author:  [@Planettetr](https://dietpi.com/forum/u/Planettetr)
#### Post date: [26 August 2023 14:49 UTC](https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220/5 "2023-08-26T14:49:07Z")
You may have had the same issue I had. I don’t know why, but motioneye creates a conf file that defaults to video10. Change this to video0 in the motion.conf file. This has always worked for me.
# Video device (e.g. /dev/video0) to be used for capturing.
video\_device /dev/video0
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [26 August 2023 17:19 UTC](https://dietpi.com/forum/t/problems-with-motioneye-on-dietpi-using-v4l2-cameras-at-all/17220/6 "2023-08-26T17:19:37Z")
Since one of the recent RPi Linux versions where KMS became the default on RPi OS and the legacy camera driver has been replaced with libcamera, there are generally some known issues or difficulties wir RPi camera modules.
When installed via `dietpi-software`, the legacy camera driver should be enabled already. You can verify via `dietpi-config`.
Could you try to add it as RPi DSI camera in motionEye instead of as V4L2 camera? This works generally work, only with the RPi camera module 3 it seems to not work anymore.