Re: is firewire broken in Debain?

["H.S." <hs.samix@gmail.com>]

Ron Johnson wrote:
> On 05/28/2010 12:53 PM, H.S. wrote:
>> I used to grab video from my DCR TVR25 MiniDV camcorder without any
>> problems in the past on Debian Testing using Kino or dvgrab. Since some
>> kernel version and up, this has not been possible anymore.
>>
>> I am now using Debian Testing, KDE and kernel 2.6.32-trunk-686.
>>
>> I see that firewire is now handled differently in the kernel and that
>> /dev/fw? devices are formed instead of /dev/raw1394. Since Kino demands
>> the latter, I have created a symbolic link /dev/raw1394 to /dev/fw0 (or
>> fw1, as the case may be).
>>
>> I have these modules loaded:
>> $>  lsmod | grep fire
>> firewire_sbp2           9575  0
>> firewire_net            9181  0
>> firewire_ohci          16477  0
>> firewire_core          30915  3 firewire_sbp2,firewire_net,firewire_ohci
>> crc_itu_t               1035  1 firewire_core
>> scsi_mod              101073  3 firewire_sbp2,sr_mod,libata
>>
>>
>> When I connect the DV camera to the firewire port, I get these error
> [snip]
>> 46:19 krnl [ 2432.443191] firewire_ohci: isochronous cycle inconsistent
>>
>>
>> Kino still doesn't work, I complains that raw1394 module is not
>> available. But those isochronous error message still trouble me. Anybody
>> now what is going on? How is one supposed to get around this problem?
>>
> 
> I think that the "old" Firewire stack is still in the kernel.
> 
> Googling "linux howto use old firewire stack", I found this link which
> might help:
> 
> http://www.kdenlive.org/user-manual/troubleshooting-and-common-problems/troubleshooting-firewire-capture
> 
> 

Thanks for the link. I had missed this one somehow while searching for a
solution.

If understand the information given on the link properly, it shows two
scenarios, one if the user has the older firewire stack and the second
for the newer one, and that either one is supposed to work. I have the
newer one. I have the permissions set up properly as the link describes
using udev rules file.

As described in the link, if I run dvgrab -i command with the camera
connected. the camera does something, but the output just gives error on
the command prompt:
$> dvgrab  -i
Found AV/C device with GUID 0x08004601024aca36
Going interactive. Press '?' for help.
send oopsPaused" 00:09:09:17 ""          sec

send oops

send oops
send oops
send oops
send oops--:-- ""          sec
send oops
send oops
send oops
send oops
send oops--:-- ""          sec
.
.
and so on
.
.





-- 

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.