[Coriander-devel] Re (4): v4l2loopback for coriander

[<pea...@sh...>]

From:	Gordon Sinclair <go...@gy...>
Date:	Tue, 05 Jun 2012 21:39:38 +0100
> The only thing i can see is that I always start coriander as root to get
> over any privilege issues. If coriander can not see any cameras try
> starting sudo coriander

For user and for root Coriander  runs and Services > Display gives an image.
No problem there.  The problem is to get the V4L signal.

For interest, I changed the 1394 pci adapter card to a newer Belkin.  hwinfo 
reports the older adapter as well as this one; but "hwinfo --camera" still 
gives nothing.  Can anyone get camera information from hwinfo?  Perhaps 
hwinfo is simply unable to detect a 1394 camera.  

From:	Stefan Richter <st...@s5...>
Date:	Wed, 6 Jun 2012 13:43:17 +0200
> Likewise, ownerships or ACLs on the v4l character device files need to be
> set properly, ...

peter@joule:/dev$ find . -type f -name '*v4l*' -print
peter@joule:/dev$

No /dev file with "v4l" in the name.  What should exist?  
Is it persistent?  Or does it come into existence only when Coriander 
is running the V4L service?

> ... and your user account should be member of the necessary
> group(s) of course.

Which groups?  I don't recognize any group as specific to V4L.  
Should there be a *v4l* group?

Thanks,                   ... Peter E.

-- 
Telephone 1 360 639 0202.  Bcc: peter at easthope.ca
"http://carnot.yi.org/ "
"http://members.shaw.ca/peasthope/index.html#Itinerary "

Shelley's photos 
https://picasaweb.google.com/112944318138461249464/May292012?authuser=0&authkey=Gv1sRgCN_c7efw5-rWEg&feat=directlink

Peter's photos
https://picasaweb.google.com/112944318138461249464/May29201202?authuser=0&feat=directlink