is firewire broken in Debain?
in [Debian]
|
Prev: file transfer from removable flash memory: time stamps and case
Next: IPv4-capable XDMCP server in Debian squeeze?
From: H.S. on 28 May 2010 14:00 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 messages in syslog (trimmed some irrelevant info for better formatting): 46:09 krnl [ 2422.285885] firewire_core: created device fw1: GUID 08004601024aca36, S100 46:09 krnl [ 2422.285897] firewire_core: phy config: card 0, new root=ffc1, gap_count=5 46:10 krnl [ 2423.440290] firewire_ohci: isochronous cycle inconsistent 46:10 krnl [ 2423.940722] firewire_core: phy config: card 0, new root=ffc1, gap_count=5 46:11 krnl [ 2425.088778] firewire_ohci: isochronous cycle inconsistent 46:12 krnl [ 2425.589206] firewire_core: phy config: card 0, new root=ffc1, gap_count=5 46:13 krnl [ 2426.737153] firewire_ohci: isochronous cycle inconsistent 46:14 krnl [ 2427.878295] firewire_ohci: isochronous cycle inconsistent 46:15 krnl [ 2429.019461] firewire_ohci: isochronous cycle inconsistent 46:17 krnl [ 2430.160755] firewire_ohci: isochronous cycle inconsistent 46:18 krnl [ 2431.301908] firewire_ohci: isochronous cycle inconsistent 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? Thanks. -- 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. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/htovus$sv7$1(a)dough.gmane.org
From: Ron Johnson on 28 May 2010 14:20 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 -- Dissent is patriotic, remember? -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C000809.3000206(a)cox.net
From: H.S. on 28 May 2010 14:40 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. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/htp243$639$1(a)dough.gmane.org
From: H.S. on 28 May 2010 14:50 Ron Johnson wrote: > > 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 > > BTW, regarding the older stack, I don't seem to have it in my current kernel anymore (debian default kernel 2.6.32-trunk-686): Only older kernel has 1394 related modules: $> find /lib/modules/ -name "*1394*" /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394 /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394/video1394.ko /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394/dv1394.ko /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394/eth1394.ko /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394/ieee1394.ko /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394/ohci1394.ko /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394/raw1394.ko Only the newer kernel has the newer firewire stack: $> find /lib/modules/ -name "*firew*" /lib/modules/2.6.32-trunk-686/kernel/drivers/firewire /lib/modules/2.6.32-trunk-686/kernel/drivers/firewire/firewire-sbp2.ko /lib/modules/2.6.32-trunk-686/kernel/drivers/firewire/firewire-net.ko /lib/modules/2.6.32-trunk-686/kernel/drivers/firewire/firewire-core.ko /lib/modules/2.6.32-trunk-686/kernel/drivers/firewire/firewire-ohci.ko /lib/modules/2.6.30-2-686/kernel/drivers/firewire /lib/modules/2.6.30-2-686/kernel/drivers/firewire/firewire-ohci.ko /lib/modules/2.6.30-2-686/kernel/drivers/firewire/firewire-sbp2.ko /lib/modules/2.6.30-2-686/kernel/drivers/firewire/firewire-core.ko /lib/modules/2.6.32-3-686/kernel/drivers/firewire /lib/modules/2.6.32-3-686/kernel/drivers/firewire/firewire-ohci.ko /lib/modules/2.6.32-3-686/kernel/drivers/firewire/firewire-sbp2.ko /lib/modules/2.6.32-3-686/kernel/drivers/firewire/firewire-core.ko /lib/modules/2.6.32-3-686/kernel/drivers/firewire/firewire-net.ko Looks like I have no choice in the default kernel in Debian Testing :( -- 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. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/htp2sv$8h5$1(a)dough.gmane.org
From: Ron Johnson on 28 May 2010 16:50
On 05/28/2010 01:43 PM, H.S. wrote: > Ron Johnson wrote: >> >> 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 >> >> > > BTW, regarding the older stack, I don't seem to have it in my current > kernel anymore (debian default kernel 2.6.32-trunk-686): > > Only older kernel has 1394 related modules: > $> find /lib/modules/ -name "*1394*" > /lib/modules/2.6.26-2-686/kernel/drivers/ieee1394 [snip] > /lib/modules/2.6.32-3-686/kernel/drivers/firewire/firewire-net.ko > > Looks like I have no choice in the default kernel in Debian Testing :( > You could always roll your own kernel! :) -- Dissent is patriotic, remember? -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C002A38.1050405(a)cox.net |