I found this bug report because I have the same problem: kino (1.1.1-1) and dvgrab (3.0-1) don't work because they are expecting a /dev/raw1394 device that does not exist in my system (I am using the linux-image-2.6.22-3-686) kernel.
The reason for this problem seems to be that since kernel 2.6.22, there are two firewire stacks, the "old" one (called "Linux1394") that seems to work with kino and a new one (called "Juju") that does _not_ work with kino and dvgrab. See http://wiki.linux1394.org/Introduction The standard debian kernel is compiled with only the new firewire stack. In my opinion, there would be some solutions: - Users that want to use kino or dvgrab have to build an own kernel with the old "Linux1394" firewire stack. - Provide a precompiled module for the old "Linux1394" firewire stack. - Wait until kino and dvgrab support the new firewire stack. - Use the compatibility library libdc1394 v2 (but this is not recommended according to http://wiki.linux1394.org/JujuMigration ) - Change the precompiled linux-kernels to use the old "Linux1394" firewire stack. On http://wiki.linux1394.org/JujuMigration the following recommendation is given: > Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux > distributors (kernel packagers) as well as to regular users is: Build > only the old IEEE 1394 drivers. Best regards, Philipp
signature.asc
Description: Digital signature
