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

Woojin Lee <[email protected]>
Newsgroups gmane.comp.video.kino.devel
Message-ID <[email protected]>
After unloading driver, dmesg|grep 1394 gives

ohci1394 0000:02:0f.2: PCI INT A -> Link[LNKD] -> GSI 10 (level, low) -> IRQ 
10
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10]  MMIO=[f6ffd800-f6ffdfff]  
Max Packet=[2048]  IR/IT contexts=[4/4]
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[434fc000248c8821]
ieee1394: Node removed: ID:BUS[0-00:1023]  GUID[434fc000248c8821]

After plugin/switch on the camera and modprobe ohci1394,
dmesg|grep 1394 gives

ohci1394 0000:02:0f.2: PCI INT A -> Link[LNKD] -> GSI 10 (level, low) -> IRQ 
10
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10]  MMIO=[f6ffd800-f6ffdfff]  
Max Packet=[2048]  IR/IT contexts=[4/4]
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[434fc000248c8821]
ieee1394: Node removed: ID:BUS[0-00:1023]  GUID[434fc000248c8821]
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10]  MMIO=[f6ffd800-f6ffdfff]  
Max Packet=[2048]  IR/IT contexts=[4/4]
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[434fc000248c8821]

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

/sys/bus/ieee1394/devices/434fc000248c8821/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/434fc000248c8821/capabilities:0x0083c0
/sys/bus/ieee1394/devices/434fc000248c8821/guid:0x434fc000248c8821
/sys/bus/ieee1394/devices/434fc000248c8821/guid_vendor_id:0x434fc0
/sys/bus/ieee1394/devices/434fc000248c8821/nodeid:0xffc0
/sys/bus/ieee1394/devices/434fc000248c8821/vendor_id:0x434fc0
/sys/bus/ieee1394/devices/434fc000248c8821/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

I see that both node_count and selfid_count is still 1.

This machine is Dell Inspiron 8100 laptop.  lspci -vv gives

02:0f.2 FireWire (IEEE 1394): Texas Instruments PCI4451 IEEE-1394 Controller 
(prog-if 10 [OHCI])
        Subsystem: Dell PCI4451 IEEE-1394 Controller (Dell Inspiron 8100)
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32 (500ns min, 1000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at f6ffd800 (32-bit, non-prefetchable) [size=2K]
        Region 1: Memory at f6ff8000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA 
PME(D0-,D1-,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: ohci1394
        Kernel modules: ohci1394

Thanks

Woojin

On Saturday 16 May 2009 01:50:20 pm Stefan Richter wrote:
> Woojin Lee wrote:
> > Here's the result on one of the computer.
> > dmesg|grep 1394 generates whole bunch of
> > "ohci1394: fw-host0: SelfID received, but NodeID invalid (probably new
> > bus reset occurred): 0000FFC0"
>
> Well, this needs to stop eventually, and...
>
> > grep . /sys/bus/{ieee1394,firewire}/devices/*/* generates
> >
> > /sys/bus/ieee1394/devices/434fc000248c8821/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/434fc000248c8821/capabilities:0x0083c0
> > /sys/bus/ieee1394/devices/434fc000248c8821/guid:0x434fc000248c8821
> > /sys/bus/ieee1394/devices/434fc000248c8821/guid_vendor_id:0x434fc0
> > /sys/bus/ieee1394/devices/434fc000248c8821/nodeid:0xffc0
> > /sys/bus/ieee1394/devices/434fc000248c8821/vendor_id:0x434fc0
> > /sys/bus/ieee1394/devices/434fc000248c8821/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
>
> ...node_count...selfid_count need to become 2 (one for the card, one for
> the camera).  And there need to appear two more subdirectories in
> /sys/bus/ieee1394/devices/ (one for the camera, and another one for the
> protocol unit which the camera implements).
>
> If all this at the driver level never gets sorted out, dvgrab doesn't
> have a chance either.
>
> The other sysfs values are OK.
>
> As another quick test, you could unload the controller driver (modprobe
> -r ohci1394), plug in/ switch on the camera, then reload the controller
> driver (modprobe ohci1394).
>
> > /sys/bus/ieee1394/devices/fw-host0/uevent:DRIVER=nodemgr
> > grep: /sys/bus/firewire/devices/*/*: No such file or directory
>
> That's OK.
>
> > /dev/raw1394 is owned by root:video and I'm testing both dvgrab and
> > testlibraw as the root.  I added root to the group "video".
>
> This is not necessary; but a non-root user who wanted to run dvgrab
> would should be member of teh video group, and there needs to be rw
> access to the device file for the group of course.



------------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.