I use Kino to capture DV from Alan’s DV camera when I’ve used it to record the talks given at our LUG. It worked pretty well under Dapper. However, when trying to capture DV using Ubuntu Edgy, Kino returned an error saying
WARNING: raw1394 kernel module not loaded or failure to read/write /dev/raw1394!
Actually the module was already loaded and the permissions on the device node were just fine. It had read-write access to the “video” group, and I was in that group. The diagnostic program testlibraw reported it could talk to the devices OK, so I began to suspect that Kino was actually at fault. After doing some poking around using strace it turns out that after accessing /dev/raw1394, there’s a different device node Kino is trying to access:
open("/dev/ieee1394/dv/host0/PAL/in", O_RDWR|O_LARGEFILE) = -1 ENOENT (No such file or directory)
The device node above didn’t exist on my system. Some googling turned up these French Ubuntu forums and related mkdir and mknod commands to rectify the problem:
mkdir -p /dev/ieee1394/dv/host0/NTSC mknod -m 666 /dev/ieee1394/dv/host0/NTSC/in c 171 32 mknod -m 666 /dev/ieee1394/dv/host0/NTSC/out c 171 33 mkdir -p /dev/ieee1394/dv/host0/PAL mknod -m 666 /dev/ieee1394/dv/host0/PAL/in c 171 34 mknod -m 666 /dev/ieee1394/dv/host0/PAL/out c 171 35
I only created the PAL related nodes and Kino then worked fine. As Ubuntu uses udev, these device nodes will not survive a reboot, so frequent users of such equipment might want to add these lines (or similar ones with slightly more secure permissions) to /etc/rc.local. The actual cause of the problem isn’t so clear, whether it’s a udev issue or upstart or what, I don’t know. Using a Dapper kernel didn’t resolve the issue though.Pin It