Error opening v4l interface no such file or directory

Error opening v4l interface no such file or directory

Устанавливаем необходимые пакеты
opkg update
opkg install kmod-video-uvc mjpg-streamer

Подключаем web-камеру к устройству и проверяем, определилась ли она в системе
root@OpenWrt:/# ls /dev/vid*

Редактируем фаил конфигурации
vi /etc/config/mjpg-streamer

config mjpg-streamer core
option enabled «1»
option device «/dev/video0»
option resolution «640×480»
option fps «25»
option www «/www/webcam»
option port «8080»
#option yuv «on»
#option quality «50»

Потом выполнить
/etc/init.d/mjpg-streamer enable
/etc/init.d/mjpg-streamer start

Делаем reboot и смотрим через веб браузер, IE и Opera криво работают, лучше всего использовать Chrom
http://192.168.1.99:8080/stream.html

Без ребута настройки можно поменять так:
поток в формате YUV
mjpg_streamer -i «input_uvc.so -d /dev/video0 -y -r 640×480 -f 5 -q 50» -o «output_http.so -w /www/webcam -p 8080»

Поток в формате MJPG
mjpg_streamer -i «input_uvc.so -d /dev/video0 -r 640×480 -f 5» -o «output_http.so -w /www/webcam -p 8080»

Поток в фоновом режиме
mjpg_streamer -i «input_uvc.so -d /dev/video0 -r 640×480 -f 5» -o «output_http.so -w /www/webcam -p 8080» -b

Список поддерживаемых Web камер

Источник

Error Opening V4L Interface: No suck file or directory #1

Im having an issue getting the mjpgstreamer working. When I run ./startrobot I get the following. Any suggestion as to what the issues is? I have the Raspberry PI Camera and have tested that it works with raspistill.

/robot $ sudo ./startrobot
CHANGING PI-BLASTER FROM PWM TO PCM.
./startrobot: 4: ./startrobot: ./piblasterpcm.sh: Permission denied
PI-BLASTER SETTINGS CHANGED. NOW RUNNING SERVERS.
rm: cannot remove `mjpgstreamer.log’: No such file or directory
Starting server.
done.
MJPG Streamer Version: svn rev: Unversioned directory
i: Using V4L2 device.: /dev/video0
i: Desired Resolution: 320 x 240
i: Frames Per Second.: 5
i: Format. MJPEG
ERROR opening V4L interface: No such file or directory
Init v4L2 failed !! exit fatal
i: init_VideoIn failed
server listening on port 8090 visit http://ipaddress:8090/socket.html

The text was updated successfully, but these errors were encountered:

Hi there. From what I can see one of the problems you are facing is being denied permissions when running this line of code in piblasterpcm.sh :

echo raspberry | sudo -S ./pi-blaster/pi-blaster start —pcm

It is worth checking that your password is set to the default («raspberry»), or changing the script in this line to suit.

As for the «opening V4L interface» problem, you should check that the webcam is working by installing fswebcam and running the following command: fswebcam -d/dev/video0

/test.jpg . Then you can check in your home directory and see if it captured an image successfully. If that doesn’t work
try installing some dependencies:

Restart your pi and run the command again. This is as far as my knowledge extends without some serious googling, but let me know how it goes!

Edit: Sorry, just read that you’ve already checked your camera is working using raspistill.

Источник

errors in installing webcam for OctoPrint #499

Hi, I’m on the step of the instructions where:
./mjpg_streamer -i «./input_uvc.so» -o «./output_http.so»
I get:
MJPG Streamer Version: svn rev: Unversioned directory
i: Using V4L2 device.: /dev/video0
i: Desired Resolution: 640 x 480
i: Frames Per Second.: -1
i: Format. JPEG
i: TV-Norm. DEFAULT
ERROR opening V4L interface: No such file or directory
Init v4L2 failed !! exit fatal
i: init_VideoIn failed

Help, I don’t know what to do next. I’m just following the instructions verbatim.
Also now the commands raspistill and raspivid no longer work. They worked before I started the install. I get this when I try:

mmal: mmal_vc_component_create: failed to create component ‘vc.ril.camera’ (1:ENOMEM)
mmal: mmal_component_create_core: could not create component ‘vc.ril.camera’ (1)
mmal: Failed to create camera component
mmal: main: Failed to create camera component
mmal: Camera is not detected. Please check carefully the camera module is installed correctly

But the camera IS installed correctly!

Also strange things happen when running OctoPrint. When I run ./run, I can get see the OctoPrint web page. But when I try to start it as as a daemon with ./run —daemon start, it seems to take the command, but I get no web page. When I stop the daemon with /.run —daemon stop, I get: pidfile /tmp/octoprint.pid does not exist. Daemon not running?
Then I can’t do anything until I restart the pi. Something is very screwey here. I need help telling me what it is.

I don’t want to spend my time poking into the depths of Linux, I’d rather spend my all-to-rare free time doing actual 3d printing.

Thanks for any help
Joe

The text was updated successfully, but these errors were encountered:

It looks like your camera isn’t in /dev/video0 please post what «lsusb» is returning to you and check if /dev/video0 exists.

For the second Problem clear your logs folder.(rm

/.octoprint/logs/*)
Then do ./run —daemon start
Check the logs folder if a log has been created and please post the log (octoprint.log)

Question 1 —
lsusb:
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS
802.11n WLAN Adapter

There is no /dev/video0 file.

Then tried going into raspi-config and again re-enabling camera. That
made no difference.

Question 2 —
Yes, clearing the logs folder did the trick. Now I can start and stop
the server as I please.

Thank you for your quick turnaround,
Joe

On 6/14/14, 2:49 PM, Salandora wrote:

It looks like your camera isn’t in /dev/video0 please post what
«lsusb» is returning to you and check if /dev/video0 exists.

For the second Problem clear your logs folder.(rm

/.octoprint/logs/*)
Then do ./run —daemon start
Check the logs folder if a log has been created and please post the
log (octoprint.log)

—
Reply to this email directly or view it on GitHub
#499 (comment).

Raspistill and stuff sounds like you have a raspi cam, not an USB webcam. Is that assumption correct (you did not state it)? If so, your mjpg-streamer call is wrong, you need to use input_raspicam instead of input_uvc. I’d suggest to use the OctoPi image, which preconfigures everything for you, which is better if you want to minimise fiddling around with Linux.

Yes, it is a raspicam. Didn’t even occur for me to mention it.
The reason I’m not using the OctoPi image is because I started with my
own Occidentalis image and built it up with a bunch of goodies to
created my own standard start-up image.
But if I have to, then yes, I can start over again with OctoPi.
Thanks for your advice.
Joe
On 6/14/14, 5:35 PM, Gina Häußge wrote:

Raspistill and stuff sounds like you have a raspi cam, not an USB
webcam. Is that assumption correct (you did not state it)? If so, your
mjpg-streamer call is wrong, you need to use input_raspicam instead of
input_uvc. I’d suggest to use the OctoPi image, which preconfigures
everything for you, which is better if you want to minimise fiddling
around with Linux.

—
Reply to this email directly or view it on GitHub
#499 (comment).

Well ok that clearing the log folder solves the problem was not supposed, I just thought that we would get a clean log to check whats wrong. But this way its good too ^^

For the camera problem, you don’t need to use OctoPi, you just have to use the input_raspicam plugin as foosel already stated.

Might be you need to compile it on your own, but thats not hard. I guess there are dozen of tutorials out there of how to do it. just search the web for mjpeg_streamer raspicam.

I am having an error as well with installing the Webcam software. when I attempt to complete the first step, imagemagick keeps saying error 404: not found. I tried using what Salandora put at the bottom of the previous post and have rooted the problem to imagemagick. if I attempt to follow through with the install it says directory not found and stops the install. any help would be appreciated.
using a regular webcam on RPI running rasbian
NOTE: I will try again tomorrow to see if the site was down.

Just for the record, mjpg_streamer in principle has nothing to do with OctoPrint, it’s a separate program.

That being said: Could you please provide your exact output?

Well now the error has changed, it says «make: *** [input_raspicam.so] Error 127» This is different than the previous error I was having. I tried the link that as previously l mentioned was posted by Salandora. this is how I discovered it was imagemagick, as it downloads everything separately. also as aforementioned I am suing a regular webcam. may I have messed things up by doing so?
NOTE: I did retry it to see if It was the server but am still getting the 404 error.

Try the following:

If that fails, post the full output, not just the last line.

I am still getting the same error after running the «make clean» and «make» command.
here is the full set leading up to the current error. it mentions something about not finding cmake. i have run this command many times without it going through because of the Error 404, file not found.

here is the current error:
cp plugins/output_http/output_http.so .
cd plugins/input_raspicam/build; cmake ..
/bin/sh: 1: cmake: not found
make: *** [input_raspicam.so] Error 127

Hi,
I’m back with a new issue. I regrouped, created a fresh SD card (Debbian, e.g. Wheezy, e.g. Occidentalis).
I installed the raspicam and configured the raspicam software. Confirmed it works with raspistill.
I then installed Octoprint. Went without issue. I verified that I connect on port :5000.
I then installed MJPG-Streamer. It appeared to install without incident.
Since I am using Raspicam, I used this command
./mjpg_streamer -i «./input_raspicam.so -y» -o «./output_http.so»
Here is the output —>
raspicam input plugin: option ‘—y’ requires an argument
I changed the command to add 400 to the -y and could start the camera.
However on port 8080 I got a black screen. It looked like it was trying to display my streaming image, but somehow failed to get the stream on the web page.
I stopped the program with ctrl-c. Tried running it again now I get:

MJPG Streamer Version: svn rev: Unversioned directory
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c, input_init(), 118): argv[0]=raspicam input plugin
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c, input_init(), 118): argv[1]=-y
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c, input_init(), 118): argv[2]=400
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c, input_init(), 181): case 4,5
i: fps. 1
i: resolution. 640 x 400
i: camera parameters.

Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 400, Video Stabilisation No, Exposure compensation 0
Exposure Mode ‘auto’, AWB Mode ‘auto’, Image Effect ‘none’
Metering Mode ‘average’, Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
o: www-folder-path. disabled
o: HTTP TCP port. 8080
o: username:password.: disabled
o: commands. enabled
i: Starting Camera
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c, worker_thread(), 553): Host init, starting mmal stuff
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
camera couldn’t be enabled

Any thoughts as to what might be wrong?

if you are creating a fresh SD card, why don’t you just take OctoPi :
https://github.com/guysoft/OctoPi

You can always add your special stuff afterward, but then you will know
that the cam setup is tested.

On 03.07.2014 02:50, molnarjoe wrote:

Hi,
I’m back with a new issue. I regrouped, created a fresh SD card
(Debbian, e.g. Wheezy, e.g. Occidentalis).
I installed the raspicam and configured the raspicam software.
Confirmed it works with raspistill.
I then installed Octoprint. Went without issue. I verified that I
connect on port :5000.
I then installed MJPG-Streamer. It appeared to install without incident.
Since I am using Raspicam, I used this command
./mjpg_streamer -i «./input_raspicam.so -y» -o «./output_http.so»
Here is the output —>
raspicam input plugin: option ‘—y’ requires an argument
I changed the command to add 400 to the -y and could start the camera.
However on port 8080 I got a black screen. It looked like it was
trying to display my streaming image, but somehow failed to get the
stream on the web page.
I stopped the program with ctrl-c. Tried running it again now I get:

MJPG Streamer Version: svn rev: Unversioned directory
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c,
input_init(), 118): argv[0]=raspicam input plugin
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c,
input_init(), 118): argv[1]=-y
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c,
input_init(), 118): argv[2]=400
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c,
input_init(), 181): case 4,5
i: fps. 1
i: resolution. 640 x 400
i: camera parameters.

Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 400, Video Stabilisation No, Exposure compensation 0
Exposure Mode ‘auto’, AWB Mode ‘auto’, Image Effect ‘none’
Metering Mode ‘average’, Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
o: www-folder-path. disabled
o: HTTP TCP port. 8080
o: username:password.: disabled
o: commands. enabled
i: Starting Camera
DBG(/home/pi/mjpg-streamer/mjpg-streamer-experimental/plugins/input_raspicam/input_raspicam.c,
worker_thread(), 553): Host init, starting mmal stuff
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
camera couldn’t be enabled

Any thoughts as to what might be wrong?

Reply to this email directly or view it on GitHub
#499 (comment).

Thanks,
I had a problem with the OctoPi. It didn’t work with the Raspicam for
some reason. I didn’t write down the error, maybe I should have, sorry.
I might yet try the OctoPi, I’m having some other issues with this build
anyway. (Learning curve.)
I’ll keep you posted.
Joe
On 7/3/14, 8:42 AM, spiderdaddy wrote:

if you are creating a fresh SD card, why don’t you just take OctoPi :
https://github.com/guysoft/OctoPi

You can always add your special stuff afterward, but then you will know
that the cam setup is tested.

On 03.07.2014 02:50, molnarjoe wrote:

Hi,
I’m back with a new issue. I regrouped, created a fresh SD card
(Debbian, e.g. Wheezy, e.g. Occidentalis).
I installed the raspicam and configured the raspicam software.
Confirmed it works with raspistill.
I then installed Octoprint. Went without issue. I verified that I
connect on port :5000.
I then installed MJPG-Streamer. It appeared to install without incident.
Since I am using Raspicam, I used this command
./mjpg_streamer -i «./input_raspicam.so -y» -o «./output_http.so»
Here is the output —>
raspicam input plugin: option ‘—y’ requires an argument
I changed the command to add 400 to the -y and could start the camera.
However on port 8080 I got a black screen. It looked like it was
trying to display my streaming image, but somehow failed to get the
stream on the web page.
I stopped the program with ctrl-c. Tried running it again now I get:

MJPG Streamer Version: svn rev: Unversioned directory

input_init(), 118): argv[0]=raspicam input plugin

input_init(), 118): argv[1]=-y

input_init(), 118): argv[2]=400

input_init(), 181): case 4,5
i: fps. 1
i: resolution. 640 x 400
i: camera parameters.

Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 400, Video Stabilisation No, Exposure compensation 0
Exposure Mode ‘auto’, AWB Mode ‘auto’, Image Effect ‘none’
Metering Mode ‘average’, Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
o: www-folder-path. disabled
o: HTTP TCP port. 8080
o: username:password.: disabled
o: commands. enabled
i: Starting Camera

worker_thread(), 553): Host init, starting mmal stuff
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
camera couldn’t be enabled

Any thoughts as to what might be wrong?

Reply to this email directly or view it on GitHub
#499 (comment).

—
Reply to this email directly or view it on GitHub
#499 (comment).

Because OctoPi is a reference installation with a known base it is
easier to work out what is different for you, rather than trying to
trace all the installation steps.

On 03.07.2014 15:48, molnarjoe wrote:

Thanks,
I had a problem with the OctoPi. It didn’t work with the Raspicam for
some reason. I didn’t write down the error, maybe I should have, sorry.
I might yet try the OctoPi, I’m having some other issues with this build
anyway. (Learning curve.)
I’ll keep you posted.
Joe
On 7/3/14, 8:42 AM, spiderdaddy wrote:

if you are creating a fresh SD card, why don’t you just take OctoPi :
https://github.com/guysoft/OctoPi

You can always add your special stuff afterward, but then you will know
that the cam setup is tested.

On 03.07.2014 02:50, molnarjoe wrote:

Hi,
I’m back with a new issue. I regrouped, created a fresh SD card
(Debbian, e.g. Wheezy, e.g. Occidentalis).
I installed the raspicam and configured the raspicam software.
Confirmed it works with raspistill.
I then installed Octoprint. Went without issue. I verified that I
connect on port :5000.
I then installed MJPG-Streamer. It appeared to install without
incident.
Since I am using Raspicam, I used this command
./mjpg_streamer -i «./input_raspicam.so -y» -o «./output_http.so»
Here is the output —>
raspicam input plugin: option ‘—y’ requires an argument
I changed the command to add 400 to the -y and could start the camera.
However on port 8080 I got a black screen. It looked like it was
trying to display my streaming image, but somehow failed to get the
stream on the web page.
I stopped the program with ctrl-c. Tried running it again now I get:

MJPG Streamer Version: svn rev: Unversioned directory

input_init(), 118): argv[0]=raspicam input plugin

input_init(), 181): case 4,5
i: fps. 1
i: resolution. 640 x 400
i: camera parameters.

Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 400, Video Stabilisation No, Exposure compensation 0
Exposure Mode ‘auto’, AWB Mode ‘auto’, Image Effect ‘none’
Metering Mode ‘average’, Colour Effect Enabled No with U = 128, V
= 128
Rotation 0, hflip No, vflip No
o: www-folder-path. disabled
o: HTTP TCP port. 8080
o: username:password.: disabled
o: commands. enabled
i: Starting Camera

worker_thread(), 553): Host init, starting mmal stuff
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
camera couldn’t be enabled

Any thoughts as to what might be wrong?

Reply to this email directly or view it on GitHub

Reply to this email directly or view it on GitHub
#499 (comment).

Reply to this email directly or view it on GitHub
#499 (comment).

I used the OctoPi build today. I set up the camera and the server.
Whatever problem I had the first time using the OctoPi image didn’t
happen this time.
It’s up and running. Thanks to the community for the help.
Joe
On 7/3/14, 7:15 PM, spiderdaddy wrote:

Because OctoPi is a reference installation with a known base it is
easier to work out what is different for you, rather than trying to
trace all the installation steps.

On 03.07.2014 15:48, molnarjoe wrote:

Thanks,
I had a problem with the OctoPi. It didn’t work with the Raspicam for
some reason. I didn’t write down the error, maybe I should have, sorry.
I might yet try the OctoPi, I’m having some other issues with this build
anyway. (Learning curve.)
I’ll keep you posted.
Joe
On 7/3/14, 8:42 AM, spiderdaddy wrote:

if you are creating a fresh SD card, why don’t you just take OctoPi :
https://github.com/guysoft/OctoPi

You can always add your special stuff afterward, but then you will
know
that the cam setup is tested.

On 03.07.2014 02:50, molnarjoe wrote:

Hi,
I’m back with a new issue. I regrouped, created a fresh SD card
(Debbian, e.g. Wheezy, e.g. Occidentalis).
I installed the raspicam and configured the raspicam software.
Confirmed it works with raspistill.
I then installed Octoprint. Went without issue. I verified that I
connect on port :5000.
I then installed MJPG-Streamer. It appeared to install without
incident.
Since I am using Raspicam, I used this command
./mjpg_streamer -i «./input_raspicam.so -y» -o «./output_http.so»
Here is the output —>
raspicam input plugin: option ‘—y’ requires an argument
I changed the command to add 400 to the -y and could start the
camera.
However on port 8080 I got a black screen. It looked like it was
trying to display my streaming image, but somehow failed to get the
stream on the web page.
I stopped the program with ctrl-c. Tried running it again now I get:

MJPG Streamer Version: svn rev: Unversioned directory

input_init(), 118): argv[0]=raspicam input plugin

input_init(), 181): case 4,5
i: fps. 1
i: resolution. 640 x 400
i: camera parameters.

Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 400, Video Stabilisation No, Exposure
compensation 0
Exposure Mode ‘auto’, AWB Mode ‘auto’, Image Effect ‘none’
Metering Mode ‘average’, Colour Effect Enabled No with U = 128, V
= 128
Rotation 0, hflip No, vflip No
o: www-folder-path. disabled
o: HTTP TCP port. 8080
o: username:password.: disabled
o: commands. enabled
i: Starting Camera

worker_thread(), 553): Host init, starting mmal stuff
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
camera couldn’t be enabled

Any thoughts as to what might be wrong?

Reply to this email directly or view it on GitHub

Reply to this email directly or view it on GitHub

Reply to this email directly or view it on GitHub
#499 (comment).

—
Reply to this email directly or view it on GitHub
#499 (comment).

Hey, I took the latest octopi image( .9 i beleive) download and installed. Everything worked great for printing and control right out of the box. I plugged in my pi camera (v1.3) and the light comes on, but no image, when I try to MJPG-Streamer (octopi.local:8080) I don’t see any video. I am not sure what else to try, I don’t want to mess with the install to much as it is printing great. Any ideas to get the Pi camera module to work?

@cmwahlqu please try the following:

• log into your pi via ssh
• kill the webcamDaemon script: grep for it in your process tree, then kill -9 all process ids (2nd column) associated with it, should be two, one with sudo , one without:

• if ps -ef | grep mjpg_streamer shows a running mjpg_streamer process, kill that too
• enter /home/pi/scripts/webcamDaemon . This should start it up again but log the output it generates while starting up the cam to the console. There will hopefully be an error logged. That should help with what’s going wrong, so post this here.

No reply from OP, closing

For anyone who finds this thread after googling «ERROR opening V4L interface», try this:

sudo modprobe bcm2835-v4l2

You can also put bcm2835-v4l2 into /etc/modules, which will automatically load it on boot.

Same here, i did this tutorial:

If you also want webcam and timelapse support, you’ll need to download and compile MJPG-Streamer:

sudo apt-get install subversion libjpeg8-dev imagemagick libav-tools libv4l-dev cmake
git clone https://github.com/jacksonliam/mjpg-streamer.git
cd mjpg-streamer/mjpg-streamer-experimental
export LD_LIBRARY_PATH=.
make

This should hopefully run through without any compilation errors. You should then be able to start the webcam server using:

./mjpg_streamer -i «./input_uvc.so» -o «./output_http.so»

Everything works untill the last comment.

Result for command «lsusb»:

Bus 001 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 001 Device 003: ID 2341:0042 Arduino SA Mega 2560 R3 (CDC ACM)
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Источник

sudo apt-get install subversion libjpeg8-dev 
imagemagick libv4l-0 libv4l-dev
cd ~
svn co https://svn.code.sf.net/p/mjpg-streamer/code mjpg-streamer
cd mjpg-streamer/mjpg-streamer
make USE_LIBV4L2=true clean all
sudo make install

Return to “Camera board”

Error Opening V4L Interface: No suck file or directory #1

Comments

Im having an issue getting the mjpgstreamer working. When I run ./startrobot I get the following. Any suggestion as to what the issues is? I have the Raspberry PI Camera and have tested that it works with raspistill.

/robot $ sudo ./startrobot
CHANGING PI-BLASTER FROM PWM TO PCM.
./startrobot: 4: ./startrobot: ./piblasterpcm.sh: Permission denied
PI-BLASTER SETTINGS CHANGED. NOW RUNNING SERVERS.
rm: cannot remove `mjpgstreamer.log’: No such file or directory
Starting server.
done.
MJPG Streamer Version: svn rev: Unversioned directory
i: Using V4L2 device.: /dev/video0
i: Desired Resolution: 320 x 240
i: Frames Per Second.: 5
i: Format. MJPEG
ERROR opening V4L interface: No such file or directory
Init v4L2 failed !! exit fatal
i: init_VideoIn failed
server listening on port 8090 visit http://ipaddress:8090/socket.html

The text was updated successfully, but these errors were encountered:

Hi there. From what I can see one of the problems you are facing is being denied permissions when running this line of code in piblasterpcm.sh :

echo raspberry | sudo -S ./pi-blaster/pi-blaster start —pcm

It is worth checking that your password is set to the default («raspberry»), or changing the script in this line to suit.

As for the «opening V4L interface» problem, you should check that the webcam is working by installing fswebcam and running the following command: fswebcam -d/dev/video0

/test.jpg . Then you can check in your home directory and see if it captured an image successfully. If that doesn’t work
try installing some dependencies:

Restart your pi and run the command again. This is as far as my knowledge extends without some serious googling, but let me know how it goes!

Edit: Sorry, just read that you’ve already checked your camera is working using raspistill.

Источник

Arch Linux

You are not logged in.

#1 2013-04-26 12:52:06

udev rules problem (2 webcams, assigning videoX devices)

I’ve got a built-in webcam (notebook) and an external one connected too, different vendor/product IDs.
I want the built-in cam to be video0 and the external one video1.

I added a file /etc/udev/rules.d/25-name-video-devices.rules containing:

but it doesn’t seem to have effect. After a reboot, the internal cam is now video1 and the external one video0..

#2 2013-04-26 16:24:48

Re: udev rules problem (2 webcams, assigning videoX devices)

Pastebin these somewhere:

Edit: This is probably what you want:

Edit2: Although, messing with the kernel’s own names is inelegant (e.g. a third webcam will play havoc with the names until you write a rule for that too), better with symlinks:

Yet another edit: Specifying SUBSYSTEM is a bit more elegant than: KERNEL==»video[0-9]*»

Last edited by brebs (2013-04-26 16:38:24)

#3 2013-04-27 18:05:05

Re: udev rules problem (2 webcams, assigning videoX devices)

Thanks, the symlink stuff does not work unfortunately. I do get the devices /dev/video0,video1,videoint,videoext listed, but ALL of them give this error in guvcview:

video device: /dev/video1 Offline

#4 2013-04-27 18:13:22

Re: udev rules problem (2 webcams, assigning videoX devices)

ERROR opening V4L interface: Permission denied

Well, look at your permissions on /dev/video*, and think about what groups you’re in.

#5 2013-04-27 23:10:17

Re: udev rules problem (2 webcams, assigning videoX devices)

I didn’t change any permissions about /dev/vide0 and /dev/video1, and I was able to use them before.
I did a ls -la /dev/video* and noticed that while dev/video0,1 are root:video, the two links are root:root.
I did

and strangely while midnight commander claims it is root:video a command ls -la will still display them as root:root.
Further although I KNOW that my user is in group video (and I readded him to be safe and opened a new terminal), ‘groups’ does not list video, lol.
So no matter what, suddenly only my root user can use guvcview /dev/videoXXX, just what is going on here..

Last edited by Jindur (2013-04-27 23:18:11)

#6 2013-04-27 23:21:36

Re: udev rules problem (2 webcams, assigning videoX devices)

Don’t change the permissions of *symlinks* — google it

#7 2013-04-28 00:24:43

Re: udev rules problem (2 webcams, assigning videoX devices)

Ohh, I think I even knew this at some point, but forgot about it ^^.
Well anyway so symlinks aren’t the problem. But then why can my user not access the video devices? (Worked before and as I said I didn’t change permissions or groups in anyway.)

And why does this happen:

so I guess just relogging in the terminal doesn’t work, I have to relog in X.
But I still wonder why my video devices stopped working although they worked fine before changing the udev rules.

Last edited by Jindur (2013-04-28 00:27:20)

#8 2013-04-28 00:26:01

Re: udev rules problem (2 webcams, assigning videoX devices)

You need to login again

#9 2013-04-28 00:28:47

Re: udev rules problem (2 webcams, assigning videoX devices)

lol, I just clicked on logout as ALWAYS it worked a few hours ago and always in before that too, now I just got

Last edited by Jindur (2013-04-28 00:29:08)

#10 2013-04-28 00:39:45

Re: udev rules problem (2 webcams, assigning videoX devices)

Ok, cameras work now. Wrong order (pretty sure I used the correct tags though :-p) but whatever.
We’ll see if the order is persistent after next restart.^^
Thanks

Last edited by Jindur (2013-04-28 00:40:20)

#11 2013-05-08 09:43:41

Re: udev rules problem (2 webcams, assigning videoX devices)

Hello, sorry to answer to that post now but I have a similar problem.
I need to use my built-in webcam through Wine, so I made a udev rule :
SUBSYSTEM==»video4linux», ATTRS==»05ca», ATTRS==»180a», SYMLINK+=»videoint»
That is in the file named 25-name-video-devices.rules inside /etc/udev/rules.d/

And when I do ls -la /dev/vid* , I get :
crw-rw—-+ 1 root video 81, 0 mai 8 11:08 /dev/video0
lrwxrwxrwx 1 root root 6 mai 8 11:08 /dev/videoint -> video0

So it looks like I have the same problem as Jindur, with the permissions. When I try to use the webcam through Wine, it isn’t even detected. Jindur, I am not sure how you solved it, but could you please explain it to me?

#12 2013-05-08 10:42:39

Re: udev rules problem (2 webcams, assigning videoX devices)

webcam through Wine

That’s not well supported, apparently — see wine wiki.

Looks like, for wine, you should be setting up the group permissions within /dev/bus/usb/ rather than /dev/video*

#13 2013-05-08 10:57:09

Re: udev rules problem (2 webcams, assigning videoX devices)

Thanks for your answer!
But since the camera is built-in and not an usb one, do I still need to use /dev/bus/usb?

Last edited by Andorinita (2013-05-08 10:58:38)

#14 2013-05-08 11:26:28

Re: udev rules problem (2 webcams, assigning videoX devices)

Maybe. You tell me — what bus is it using? Probably USB.

#15 2013-05-09 10:29:43

Re: udev rules problem (2 webcams, assigning videoX devices)

Sorry for the late reply. It looks like it is using USB indeed, and bus 1 in particular :
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Bus 001 Device 003: ID 05ca:180a Ricoh Co., Ltd

Источник

Thread: V4L2 Permission Denied even with sudo

Thread Tools

Display

V4L2 Permission Denied even with sudo

I’m trying to set up a webcam (Logitech C270) on my Ubuntu 18.04 system. I’m having strange permission issues that I don’t understand. I’ve added my usual user to the «video» group (logged in and out) and I’ve also tried with sudo and in both cases I’m seeing:

sudo mjpg-streamer -i «input_uvc.so -r 1280×720 -f 30» -o «output_http.so -w ./www» 1 ↵
[sudo] password for user:
MJPG Streamer Version: git rev: f387bb44e6c087271b763b27da998bf2e06c4f5d
i: Using V4L2 device.: /dev/video0
i: Desired Resolution: 1280 x 720
i: Frames Per Second.: 30
i: Format. JPEG
i: TV-Norm. DEFAULT
ERROR opening V4L interface: Permission denied
Init v4L2 failed !! exit fatal
i: init_VideoIn failed

Cheese also fails to show the camera. However, if I use VLC, I can see the camera. So, I have two programs claiming permissions issues even with root authority and one that works. I’m stumped and could use some direction.

Re: V4L2 Permission Denied even with sudo

What you’ve done with the group seems reasonable. Running GUI tools as root isn’t a good idea, but if you must, always use sudo -H , so the HOME directory is modified to be that for ‘root’, not left as your userid, which can cause strange problems.

I’ve never gotten cheese to work, ever.

I always used either uvc-something or obs. guvcview is the tool. I’m on a new box now and need to get the webcam working. cheese locked up the GUI, hard. So did guvcview. I had to physically walk to a different machine and ssh back in, kill the process and all is well again. About a month ago, I modified the system to run most programs in a firejail, by default, so some of the issues I have are with that. But neither cheese nor guvcview have that modification and syslog proves that along with not having **any** other issues.

I know my webcam works. Used it for some video calls through my nextcloud server over the last month. Worked perfectly. I’m not in the video unix group. My permissions are:

Added myself to the video group and guvcview worked perfectly. I just edited the /etc/group file, ran newgrp (no args) in that terminal, then ran guvcview and it worked perfectly. I’m lazy and didn’t want the hassles of having to get my browser tabs up again and a few website logins going. The logout and login method should work even better. Does ‘id‘ prove that your userid is in the video group?

Источник

Orange Pi Zero and webcam for Octoprint

Octoprint is the way to go to easily manage and monitor your 3D printer from your PC!

Jean-Matthieu DECHRISTE

In a previous blog entry, I explained (in French) that I added Octoprint to my Dagoma DiscoEasy200 thanks to an Orange Pi Zero.

The best guide I found is the one from deloarts.

Remark: when I wrote this article, I discovered that new editions of the Orange Pi Zero exists (Plus / Plus2 H3, H5. ). I’m using the basic Orange Pi Zero with 512Mo RAM

Webcam module

I recently dismantled an old Android 2.2 notebook before throwing it away (based on the Wondermedia WM8650). I found a little module with a camera on it, and I asked myself if it could be reused.

The chip on the module is an Etron eSP268.

And 4 wires are connected to the module (red / black / blue / white).
It seems that the module is just connected through an USB interface !
I gave it a shot :

• Red: 5V
• Black: GND
• White: Data positive
• Blue: Data negative

And it works! No driver to install to get it work with Windows 10.
The webcam is an UVC compatible device, which is a good news as it supported by Linux.

Connect the webcam to the Orange Pi Zero

Hardware

As the only USB port socket on the Orange PI Zero is used by the 3D printer, I looked at the Orange PI Zero pinout:

Source

We can see that 2 USB port pins are available (USB-Dx2 / USB-Dx3).
I chose to use the USB-DM2 / USB-DP2 as they are close to 5V and GND pins.

I removed the micro USB breakout board and put some pin headers:

Software

I’m using the following OS:

ARMBIAN 5.38 stable Ubuntu 16.04.4 LTS 4.14.18-sunxi

I found some useful informations on the Sunxi website.

Once that the OS booted, I tried to see if the webcam was recognized:

So I checked the USB devices:

To discover the webcam informations, I had to install hwinfo

I checked on the UVC Linux driver website, and it should be supported:

1e4e:0100 / USB 2.0 Camera / Etron Technologies

After looking around on the web to get it working, I understood that I just had to enable the kernel module:

Installed and used some tools to see the capacity of the webcam.

So the webcam can be used at 30 fps with the 640×480 resolution. Enough for a free module.

Use the webcam with Octoprint

To be able to use the webcam with Octoprint, the webcam stream must be exposed over HTTP.
To do that, Octoprint website advise to use mjpg-streamer.

Webcam stream with «mjpg-streamer»

Please note that I installed the tool ( make install ) but I think that it’s not mandatory.

Now, it’s time to test the stream:

Sadly, this webcam cannot output MJPG, which force the streamer to transcode the stream, and use a lot of CPU power (30% of the CPU of my Orange PI).

The stream is now available!

Before configuring Octoprint, I had to install ffmpeg:

Scripts to be able to start / stop the webcam

As the streamer uses a lot of CPU, I want to be able to start it / stop it directly from Octoprint.

I adapted the scripts that are available on GitHub for my configuration.

webcam.sh

webcamDaemon.sh

Edit Octoprint configuration

I had to add the system section:

Octoprint user rights

Currently the octoprint user doesn’t have the right to use the video devices. When I ran the script with this user, I got an error:

So I add the user to the video group:

By editing this line:

Then, I restarted Octoprint:

Octoprint configuration

It’s now time to changes the setting of Octoprint:

Don’t forget to flush the cache of your browser to see the changes in Octoprint.

Now, in the «Control» tab, an area can display the webcam stream. To enable the stream, one new item is also available in the toolbar.

I now have to find the best way to fix the webcam.
The quality is not good, but it is enough to check the printer status remotely.

If you want to open your octoprint on Internet, there is few steps left. But personally, for security reasons, I only check my octoprint through a VPN connection to my home network.

Источник

Originally Posted by warp99

Code:

lsusb -d 046d:0991 -v | grep "14 Video"
Couldn't open device, some information will be missing
      bFunctionClass         14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video
      bInterfaceClass        14 Video

lsmod | grep uvc
uvcvideo               72627  0 
videodev               98259  1 uvcvideo

Code:

guvcview 
guvcview 1.5.3
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused

ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused

ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
video device: /dev/video0 
Init. UVC Camera (046d:0991) (location: usb-0000:00:1a.7-4.2)
{ pixelformat = 'MJPG', description = 'MJPEG' }
{ discrete: width = 160, height = 120 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 176, height = 144 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 320, height = 240 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 352, height = 288 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 640, height = 480 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 800, height = 600 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 960, height = 720 }
	Time interval between frame: 1/15, 1/10, 1/5, 
{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
{ discrete: width = 160, height = 120 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 176, height = 144 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 320, height = 240 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 352, height = 288 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 640, height = 480 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 800, height = 600 }
	Time interval between frame: 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 960, height = 720 }
	Time interval between frame: 1/10, 1/5, 
{ discrete: width = 1600, height = 1200 }
	Time interval between frame: 1/5, 
{ pixelformat = 'RGB3', description = 'RGB3' }
{ discrete: width = 160, height = 120 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 176, height = 144 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 320, height = 240 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 352, height = 288 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 640, height = 480 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 800, height = 600 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 960, height = 720 }
	Time interval between frame: 1/15, 1/10, 1/5, 
{ discrete: width = 1600, height = 1200 }
	Time interval between frame: 1/5, 
{ pixelformat = 'BGR3', description = 'BGR3' }
{ discrete: width = 160, height = 120 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 176, height = 144 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 320, height = 240 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 352, height = 288 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 640, height = 480 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 800, height = 600 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 960, height = 720 }
	Time interval between frame: 1/15, 1/10, 1/5, 
{ discrete: width = 1600, height = 1200 }
	Time interval between frame: 1/5, 
{ pixelformat = 'YU12', description = 'YU12' }
{ discrete: width = 160, height = 120 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 176, height = 144 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 320, height = 240 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 352, height = 288 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 640, height = 480 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 800, height = 600 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 960, height = 720 }
	Time interval between frame: 1/15, 1/10, 1/5, 
{ discrete: width = 1600, height = 1200 }
	Time interval between frame: 1/5, 
{ pixelformat = 'YV12', description = 'YV12' }
{ discrete: width = 160, height = 120 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 176, height = 144 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 320, height = 240 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 352, height = 288 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 640, height = 480 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 800, height = 600 }
	Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5, 
{ discrete: width = 960, height = 720 }
	Time interval between frame: 1/15, 1/10, 1/5, 
{ discrete: width = 1600, height = 1200 }
	Time interval between frame: 1/5, 
vid:046d 
pid:0991 
driver:uvcvideo
Adding control for Pan (relative)
UVCIOC_CTRL_ADD - Error: Invalid argument
checking format: 1196444237
VIDIOC_G_COMP:: Invalid argument
   compression control not supported
fps is set to 1/25
drawing controls

Checking video mode 640x480@32bpp : OK