I’m not sure how much I can help here since I don’t own a firewire device.
When the camera is plugged in is there any relevant kernel messaging?
dmesg|tail
or perhaps
udevadm monitor
I wonder if a firewire rule might also be necessary to correctly handle the device. Currently /usr/lib/udev/rules.d/70-uaccess.rules provides the following rules
# IIDC devices: industrial cameras and some webcams
SUBSYSTEM=="firewire", ATTR{units}=="*0x00a02d:0x00010*", TAG+="uaccess"
SUBSYSTEM=="firewire", ATTR{units}=="*0x00b09d:0x00010*", TAG+="uaccess"
# AV/C devices: camcorders, set-top boxes, TV sets, audio devices, and more
SUBSYSTEM=="firewire", ATTR{units}=="*0x00a02d:0x010001*", TAG+="uaccess"
SUBSYSTEM=="firewire", ATTR{units}=="*0x00a02d:0x014001*", TAG+="uaccess"
I see that deano_ferrari is already trying to dicuss this with you.
I would like to take the opportunity to point you to an important, but not easy to find, feature of the forums, the CODE tags. Please allways put your computer texts between CODE tags. You get them by clicking on the # button in the tool bar of the post editor.
When the camera is plugged in and turned on nothing shows up on dmesg or tail -f messages. However when I turn OFF the camera the following shows up in messages file:
udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
essentially nothing happens at the udev level while turning on and then turning off the camera. My /usr/lib/udev/rules.d/70-uaccess.rules file has exactly the same rules as you have listed. that is why I was trying to increase the debug verbosity level of the firewire drivers to exactly see what is happening. So I upped the verbosity level on the driver using the following
In the latter case, it was demonstrated (by connection other devices and cable)to be due to the firewire controller port itself, but in the former a kernel patch was produced following a lot of testing that showed that the camera was not fully 139a compliant. Anyway, it is likely that you’ll have to submit a bug report for this observed behaviour