You are not logged in.

#1 2013-01-29 19:49:23

brewforce
Member
Registered: 2011-12-04
Posts: 8

[SOLVED]Video device file switches when starting Motion in daemon mode

I am not sure whether this should be here or in Kernel and Hardware.

Motion live stream shows gray frame which says "Unable to open video device" and /var/log/errors.log gives:

Failed to open video device /dev/video0: No such file or directory
Could not fetch initial image from camera
Motion continues using width and height from config file(s)

When I plug my Philips SPC1300NC webcam in it shows up as a recognized usb device, both by lsusb and under /dev.  Initially it comes in as /dev/video0, but after running motion the device file is /dev/video1.  If I kill motion, the device file still being video 1, and edit the configuration file (/etc/motion/motion.conf) to use /dev/video1 instead of /dev/video0 the device file name changes back when I start motion.  It is always opposite of whatever I have in the configuration file.

system: arch arm
user is in video group

output of lsusb:

$lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter
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 116: ID 0471:0331 Philips (or NXP) SPC 1300NC PC Camera

video device configuration:

# Videodevice to be used for capturing  (default /dev/video0)
# for FreeBSD default is /dev/bktr0
videodevice /dev/video0

ls /dev before running motion:

ls /dev | grep video
video0

ls /dev after running motion in daemon mode (still running):

 ls /dev | grep video
video1

So far I have attempted to remove and add back in gspca modules with and without device plugged in.
That was the only tidbit I could find online regarding the issue.  I have had motion set up with this camera before, but it was on a different machine running x86_64 arch.

thanks

SOLUTION
I wasn't thinking about the draw for the camera and was trying to just have it powered through the usb on a raspberry pi (need a powered usb hub).  I am not sure however why the device file switches when there is not enough power, so if you come across this an know please post a reply.

Last edited by brewforce (2013-01-31 03:05:08)

Offline

Board footer

Powered by FluxBB