Re: [GnomeMeeting-devel-list] Firewire AVC support: looks broken to me

[Georgi Georgiev <chutz gg3 net>]

On 03/07/2003 at 14:59:11(+0200), PUYDT Julien used 1.0K just to say:
> 
> Then on gm's launch, I get: (this is pwlib trying devices)
> access("/dev/raw1394", F_OK)            = 0
> access("/dev/video1394/0", F_OK)        = -1 ENOENT (No such file or
> directory)
> access("/dev/video1394", F_OK)          = -1 ENOENT (No such file or
> directory)
> 

If you don't have the /dev/video1394 (/dev/video1394/0 device if you use
devfs), then you probably forgot to load the video1394 module. I think
gnomemeeting, just as dvgrab, has problems without that module. If you still
have problems once you've got both raw1394 and video1394 loaded, try loading
them in the reverse order. There was something perverse happening there at
times. dvgrab was unable to open my camera depending on the order in which I
loaded these two at times, and I never got the order right. At a time I had the
feeling that I need to unload the first one and load it again, in order to get
the cam working. Not loading it first was not helping though.

Conclusion - your goal is to get you camera working with dvgrab, and it ought
to work with gnomemeeting as well. I am not really sure about kino.

Using the --debug option usually gives a more understandable output than
strace.

-- 
(    Georgi Georgiev   (  You can't erase a dream, you can only wake   (
 )    chutz gg3 net     ) me up. -- Peter Frampton                      )
(   +81(90)6266-1163   (                                               (