*** This bug is a duplicate of bug 6290 ***
https://bugs.launchpad.net/bugs/6290
Hi weliad,
I don't have one myself, but I believe the situation with firewire
cameras has changed in Karmic--though it's still not perfect. Also, your
bug report actually targets multiple issues (raw1394 module
OK, this is how it should be; raw1394 _should_ be automatically loaded
with that when a DV device appears. Could be that the drivers have a
special problem with your particular camera.
Your local change to the udev rules does not influence autoloading, only
how device file ownership is set up
just ran on the same issue on Jaunty rc, I spent hours today trying to
fix it, this was on 2 different computers (both on jaunty rc), raw1394
didn't load when the camera (panasonic NVGS150) was pluged in.
add raw1394 to /etc/modules was easy, but it took me ages to find how to
grant permission to
Why does Ubuntu (or only your two test boxes?) not load raw1394
automatically when a DV device is plugged in?
Are the module aliases somehow missing in Ubuntu's raw1394? (Run
modinfo raw1394.)
Or does Ubuntu have a blacklist raw1394 directive somewhere in /etc?
(Run grep -r 'blacklist raw1394'
(i updated the kernel to 2.6.30rc2 in the meantime i hope it doesn't disturb
the info)
(i ran the commands you told with the workaround still applied, should i
disable it?)
modinfo raw1394
filename:
/lib/modules/2.6.30-020630rc2-generic/kernel/drivers/ieee1394/raw1394.ko
licence: GPL
[raw1394 not loaded automatically]
Could you post the output of modinfo raw1394? I'd like to check
whether all device identifiers are in there as they should be. May be
necessary to run it as root or to run it as /sbin/modinfo raw1394.
Also, if you have the camcorder around, please plug it in/
(I am maintainer of the upstream kernel's IEEE 1394 driver subsystem. I
don't have Ubuntu myself.)
8. Realize you need to modprobe raw1394 module into your running
kernel.
This could be a problem with Ubuntu's udev setup, or it could be a
problem at the kernel level or hardware level.
First of all, thank you for the reply. Now, from what I understand, the main
issue is what I thought it was - a policy
defect in Ubuntu, regarding the IEEE1394 devices, which would suggest this is
truely a bug, as the policy contradicts
what Ubuntu claims: it doesn't just work.
Whenever a DV/
