linux1394-user

gscanbus: unknown device ... whats wrong?

[Michael B. <mic...@st...>]

hallo everybody

my digital camera (sony DFW-VL500) is unknown to gscanbus. with dvgrab i get 
no file ...
is this a driver problem or is the camera not supported?
i can't see where exactly the problem is... please help



i followed the installation instructions for 1394 on the sourceforge 
homepage. now i hav a suse 7.0 system with a patched 2.2.17 kernel and the 
modules for firewire support. after modprobe the pcilynx and raw1394 module 
(without any errormessage) i get the following output

bash-2.04# lsmod
Module                  Size  Used by
raw1394                 6584   0  (unused)
pcilynx                10876   0  (unused)
ieee1394               19432   0  [raw1394 pcilynx]
nfsd                  144100   4  (autoclean)
lockd                  32136   1  (autoclean) [nfsd]
sunrpc                 53956   1  (autoclean) [nfsd lockd]
nls_cp437               3904   4  (autoclean)
vfat                    9308   2  (autoclean)
fat                    29888   2  (autoclean) [vfat]

so everything seems to be ok?
then i start gscanbus (version 0.6) without a firewire device connected.

bash-2.04# ./gscanbus
successfully got handle
current generation number: 1
using first card found: 1 nodes on bus, local ID is 0

then i connect my digital camera (sony DFW-VL500, more info at 
http://www.sony.de/professional/kamera/produkte/dfw_v500.html )
and get the following errormessages from gscanbus

Bus reset - current generation number: 2
1/0x0000fffff0000404: read failed
1/0x0000fffff0000404: wrong magic quadlet
... repeated several times

then i disconnect the camera and get the following output

Bus reset - current generation number: 3                                      
                     

if connected gscanbus names the camera an unknown device with the following 
information

SelfID Info
-----------
Physical ID: 1
Link active: Yes
Gap Count: 63
PHY Speed: S400
PHY Delay: <=144ns
IRM Capable: No
Power Class: -6W
Port 0: Connected to child node
Port 1: Not connected
Port 2: Not connected
Init. reset: No

CSR ROM Info
------------
GUID: 0x0000000000000000
Node Capabilities: 0x00000000
Vendor ID: 0x00000000
Unit Spec ID: 0x00000000
Unit SW Version: 0x00000000
Model ID: 0x00000000
Nr. Textual Leafes: 0

Textual Leafes:

AV/C Subunits
-------------
N/A
              


best regards
michael

Re: gscanbus: unknown device ... whats wrong?

[Nabil S. <ns...@sa...>]

Michael Born wrote:

> if connected gscanbus names the camera an unknown device with the following
> information
[...]
> CSR ROM Info
> ------------
> GUID: 0x0000000000000000
> Node Capabilities: 0x00000000
> Vendor ID: 0x00000000
> Unit Spec ID: 0x00000000
> Unit SW Version: 0x00000000
> Model ID: 0x00000000
> Nr. Textual Leafes: 0

That doesn't need to be a functional problem. When I connected my
panasonic the first time, I was totally confused by the countless debug
and
error messages in the syslog.

One problem seems to be the way some devices let you access the csr
(block, quadlets).
But AFAIK the csr is only of informational value. Someone told me if
gscanbus lists
my device (no matter if unknown or not), everything is ok.

When I had problems with dvgrab, the reason was to figure out the
correct order of
plugging in, switching on, loading modules (dont hotplug)

cu
--
 Nabil Sayegh

Re: gscanbus: unknown device ... whats wrong?

[Dan D. <dde...@co...>]

Michael Born wrote:
> hallo everybody
>
> my digital camera (sony DFW-VL500) is unknown to gscanbus. with dvgrab i
get
> no file ...
> is this a driver problem or is the camera not supported?
> i can't see where exactly the problem is... please help

The SONY DFW series is not a DV (IEC 61834/SMPTE 314M) camera. It simply
outputs uncompressed YUV video. dvgrab only works with DV cameras. You need
to use libdc1394 (http://sourceforge.net/projects/libdc1394) to use your
camera. There is a sample program by Chris Urmson that will save a frame in
xpm format. Search for libdc1394 in the linux1394-devel list archives.

Continued below...

[...]
> if connected gscanbus names the camera an unknown device with the
following
> information
>
> SelfID Info
> -----------
> Physical ID: 1
> Link active: Yes
> Gap Count: 63
> PHY Speed: S400
> PHY Delay: <=144ns
> IRM Capable: No
> Power Class: -6W
> Port 0: Connected to child node
> Port 1: Not connected
> Port 2: Not connected
> Init. reset: No
>
> CSR ROM Info
> ------------
> GUID: 0x0000000000000000
> Node Capabilities: 0x00000000
> Vendor ID: 0x00000000
> Unit Spec ID: 0x00000000
> Unit SW Version: 0x00000000
> Model ID: 0x00000000
> Nr. Textual Leafes: 0
>
> Textual Leafes:
>
> AV/C Subunits
> -------------
> N/A
>

This is not all bad. The current released gscanbus has problems with
properly identify devices even though it detects them and shows them on the
topology map. You should consider this a working system, and continue on by
using libdc1394!

>
> best regards
> michael
>
> _______________________________________________
> mailing list Lin...@li...
> http://lists.sourceforge.net/mailman/listinfo/linux1394-user
>