> Before connection:
[...]
> /sys/bus/ieee1394/devices/fw-host0/in_bus_reset:0
[...]
> /sys/bus/ieee1394/devices/fw-host0/node_count:1
Good.
> After connection:
[...]
> /sys/bus/ieee1394/devices/fw-host0/in_bus_reset:1
[...]
> /sys/bus/ieee1394/devices/fw-host0/node_count:0
Bad, as this should become 0 and 2 respectively. This is consistent with what you got with the newer kernel: While the camera is connected (and switched on), the bus is permanently reset and never finishes a reset successfully with a self-ID-complete event, after which it would become usable for system software.
This and the fact that you already replaced the cable and also tested a PC-to-laptop connection unsuccessfully leaves pretty much only the conclusion that the port (or the ports) on your FW322/323 based board are dead.
> Before connection: ieee1394/ devices/ fw-host0/ in_bus_ reset:0 ieee1394/ devices/ fw-host0/ node_count: 1
[...]
> /sys/bus/
[...]
> /sys/bus/
Good.
> After connection: ieee1394/ devices/ fw-host0/ in_bus_ reset:1 ieee1394/ devices/ fw-host0/ node_count: 0
[...]
> /sys/bus/
[...]
> /sys/bus/
Bad, as this should become 0 and 2 respectively. This is consistent with what you got with the newer kernel: While the camera is connected (and switched on), the bus is permanently reset and never finishes a reset successfully with a self-ID-complete event, after which it would become usable for system software.
This and the fact that you already replaced the cable and also tested a PC-to-laptop connection unsuccessfully leaves pretty much only the conclusion that the port (or the ports) on your FW322/323 based board are dead.