The statement Before all, you must verify if your actual linux kernel is built with ieee1394 and raw1394 support. Generaly, if you use a debian linux kernel package, it is the case
is incomplete. libraw1394 v2 is able to use firewire-core ( + firewire-ohci) instead of raw1394 ( + ieee1394 + ohci1394), as Adi mentioned. Caveats: - We are finding and fixing bugs in the newer kernel drivers and in their libraw1394 adapter code all the time. However, your libraw1394 2.0.5 and linux 2.6.32 are fine with almost all FireWire controllers that were supported by the older drivers + library and almost all DV camcorders that were supported by the older drivers + library. - The rare FireWire controllers Nvidia NForce2 and ALi M52xx which more or less (but not fully) worked with ohci1394 may not work yet with firewire-ohci. Check with lspci whether you have one of those. Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=8828 https://bugzilla.kernel.org/show_bug.cgi?id=10935 - There have been interoperability issues of firewire-core with some buggy DV devices, notably Sony camcorders and a Panasonic DV tape deck. Linux 2.6.35/ .34.1/ .33.6/ .32.16 and newer contain a fix for certain Sonys, and 2.6.34 and newer contains a fix for the tape deck. These new interoperability issues were undesired side effects of the enhanced bus management and device discovery code in firewire-core relative to ieee1394. https://ieee1394.wiki.kernel.org/index.php/Release_Notes - As with raw1394's single /dev/raw1394 file, you need an udev rule to set proper ownership and permissions or ACL on firewire-core's /dev/fw* files. The latter are one file for each FireWire node (including the controller). For DV capture, libraw1394 only needs access to the DV camcorder's /dev/fw*. While /dev/raw1394 support has been removed from mainline udev a while ago (which means that users have to fiddle with permissions themselves now if they run raw1394), mainline udev since v144 contains suitable rules for firewire-core for all DV devices and most industrial video devices. These rules depend on a firewire-core sysfs attribute of linux 2.6.31 or later. https://ieee1394.wiki.kernel.org/index.php/Juju_Migration#Permissions_and_ownership_for_.2Fdev.2Ffw.2A You can check with "grep -r firewire /lib/udev/ /etc/udev/" whether your installed udev rules cover the new firewire subystem. Most likely it does. So, please check: - What make & model is your DV camcorder? - What controller do you have according to "lspci -nn | grep 1394"? - Is firewire-ohci loaded and bound to the controller? E.g. "grep firewire /proc/interrupts" - Are there notable kernel messages from when firewire-ohci was bound to the controller and from when you plugged in/ switched on the camcorder? "dmesg | grep firewire" - Do /dev/fw0 (likely the controller) and /dev/fw1 (likely the camcorder) exist when the camcorder is connected and on? - If yes, does your user account have permission to access one of the two device files? (Please keep Adi and me Cc'd.) -- Stefan Richter -=====-==-=- =-== ---=- http://arcgraph.de/sr/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
