Description:

The kernel config enables both ieee1394 and firewire subsystems. However, these two subsystems are more or less mutually exclusive. They both access the same hardware resources and do not cooperate. The result is that only one of them becomes truly active even though both are loaded and might appear to be active. Moreover, it is not predictable which will one will become active upon loading the system. On my i686 system, ieee1394 becomes active, but on my MacBook Pro with x86_64, firewire becomes active.

To complicate matters, libraw1394 as it is in the repo only works with ieee1394. An unreleased branch of libraw1394 (juju) is required to work with firewire; however, that version can not work with ieee1394.

Other things to consider are than firewire, while a good way for the future, is immature. In my experience, multimedia applications (e.g., kino, dvgrab, coriander, gstreamer, ekiga, ffado, cinelerra, etc) will only work intermittently with firewire when using libraw1394-juju and version 1.1 OHCI hardware. I recommend sticking to ieee1394 for the time being. Otherwise, disable ieee1394 and change libraw1394 over to the juju branch.

For more information: http://wiki.linux1394.org/JujuMigration

Additional info:
* package version(s)

kernel26 2.6.22.1-4

* config and/or log files etc.

http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/kernels/kernel26/config?rev=1.102&content-type=text/vnd.viewcvs-markup

Additional Info:

The only workaround to gain predictability in the system or ensure use of compatbility with libraw1394 package is to blacklist modules, which does not go well towards usability.