Re: Anyone using dvgrab successfully in opensuse 11.0/11.1?

On Saturday 16 May 2009 05:26:15 am Stefan Richter wrote:
> Woojin Lee wrote:
> > I've tried several computers with opensuse 11.0/11.1 with three different
> > firewire cards, two different cables and two different camcoders, and
> > they all fail to detect the DV camcoder.  They all used to work under
> > mandriva a while ago, but can't seem to get any of them working in
> > opensuse 11.1.  They all give more or less the same error.  Here is the
> > typical output.
>
> After the camera was plugged in + switched on, run
> $ dmesg | grep 1394
> $ grep . /sys/bus/{ieee1394,firewire}/devices/*/*
> and post the result.
>
On a different pc w/ different firewire card, here's the result.
dmesg | grep 1394 generates

ohci1394 0000:00:0b.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[cfffc000-cfffc7ff]  
Max Packet=[2048]  IR/IT contexts=[4/8]
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[001106664555615c]
Modules linked in: nvidia(PX) binfmt_misc snd_pcm_oss snd_mixer_oss snd_seq 
snd_seq_device nfs lockd nfs_acl sunrpc fuse loop dm_mod ppdev rtc_cmos 
rtc_core rtc_lib parport_pc parport floppy button snd_intel8x0 snd_ac97_codec 
ac97_bus snd_pcm i2c_sis96x shpchp pcspkr ohci1394 snd_timer i2c_core snd 
sis900 ieee1394 soundcore sis_agp pci_hotplug mii snd_page_alloc agpgart sg 
ohci_hcd ehci_hcd usbcore sd_mod crc_t10dif edd ext3 mbcache jbd fan 
ide_pci_generic sis5513 ide_core ata_generic pata_sis libata scsi_mod dock 
thermal processor thermal_sys hwmon [last unloaded: nvidia]
ieee1394: raw1394: /dev/raw1394 device initialized

grep . /sys/bus/{ieee1394,firewire}/devices/*/* generates

/sys/bus/ieee1394/devices/001106664555615c/bus_options:IRMC(1) CMC(1) ISC(1) 
BMC(0) PMC(0) GEN(3) LSPD(2) MAX_REC(2048) MAX_ROM(2) CYC_CLK_ACC(100)
/sys/bus/ieee1394/devices/001106664555615c/capabilities:0x0083c0
/sys/bus/ieee1394/devices/001106664555615c/guid:0x001106664555615c
/sys/bus/ieee1394/devices/001106664555615c/guid_vendor_id:0x001106
/sys/bus/ieee1394/devices/001106664555615c/nodeid:0xffc0
/sys/bus/ieee1394/devices/001106664555615c/vendor_id:0x001106
/sys/bus/ieee1394/devices/001106664555615c/vendor_name_kv:Linux - ohci1394
/sys/bus/ieee1394/devices/fw-host0/in_bus_reset:0
/sys/bus/ieee1394/devices/fw-host0/is_busmgr:0
/sys/bus/ieee1394/devices/fw-host0/is_cycmst:1
/sys/bus/ieee1394/devices/fw-host0/is_irm:1
/sys/bus/ieee1394/devices/fw-host0/is_root:1
/sys/bus/ieee1394/devices/fw-host0/node_count:1
/sys/bus/ieee1394/devices/fw-host0/nodes_active:1
/sys/bus/ieee1394/devices/fw-host0/selfid_count:1
/sys/bus/ieee1394/devices/fw-host0/uevent:DRIVER=nodemgr
grep: /sys/bus/firewire/devices/*/*: No such file or directory

Again, I'm running as root and root belongs to "video" group.
/dev/raw1394 belongs to root:video

Thanks

Woojin
> > BTW, what does "ieee1394: Failed to generate Configuration ROM image for
> > host 0" mean?  I keep getting this in dmesg when I run testlibraw.
>
> Testlibraw simply calls a number of libraw1394 functions, and thereby
> tests calls to the raw1394 kernel driver.  The function which generates
> these error messages is one which hasn't been supported in raw1394 for
> several years now, but nobody replaced its libraw1394 counterpart by
> something better yet.
>
> However, this libraw1394 API call is not used by dvgrab, nor is it of
> any consequence to dvgrab whether testlibraw was run before it.
>
> Did you run testlibraw1394 as the same user as you run dvgrab as?  If
> you used a different user, check the permissions of /dev/raw1394 as Carl
> advised.



------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects