Opensuse 13.1 firewire wont detect camera

I have suse 13.1 with KDE installed. Here are the system details

uname -a
Linux 3.11.10-7-default #1 SMP Mon Feb 3 09:41:24 UTC 2014 (750023e) i686 i686 i386 GNU/Linux

lspci | grep -i firewire
06:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]

lsmod | grep -e 1394 -e firewire
firewire_ohci 39559 0
firewire_core 65848 1 firewire_ohci
crc_itu_t 12627 1 firewire_core

dmesg | grep irewire
11.820177] firewire_ohci 0000:06:03.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x2
12.320124] firewire_core 0000:06:03.0: created device fw0: GUID 0090270001e6cce3, S400
113.480076] firewire_core 0000:06:03.0: rediscovered device fw0

When I plug in my Canon XL-1 camera and try to grab with dvgrab I get the error “No camera exists”

A deeper look tells me that no fw1 device gets created

ls -l /dev/fw*
crw-rw---- 1 root video 248, 0 May 17 13:09 /dev/fw0

Where do I look in to get the fw1 device created?

How do I increase the debug verbosity of the firewire drivers?

All help would be greatly appreciated.

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?


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"

These may be helpful

Hello, and welcome here.

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.

Thanks deano_ferrari for your response.

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:

2014-05-17T15:54:16.433073+05:00 coral kernel:   112.276049] firewire_core 0000:06:03.0: rediscovered device fw0
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

echo 7 > /sys/module/firewire_ohci/parameters/debug

Then as soon as I turned on the camera I got a ton of evt_bus_reset in the messages file

2014-05-17T16:11:33.841136+05:00 coral kernel:  1149.684887] firewire_ohci 0000:06:03.0: IRQ 00000010 AR_req
2014-05-17T16:11:33.841139+05:00 coral kernel:  1149.684894] firewire_ohci 0000:06:03.0: AR evt_bus_reset, generation 67

Then when I turned the camera off, this flood ended with the following:

2014-05-17T16:11:33.841159+05:00 coral kernel:  1149.685958] firewire_ohci 0000:06:03.0: IRQ 00010000 selfID
2014-05-17T16:11:33.841162+05:00 coral kernel:  1149.685974] firewire_ohci 0000:06:03.0: 1 selfIDs, generation 71, local node ID ffc0
2014-05-17T16:11:33.841165+05:00 coral kernel:  1149.685980] firewire_ohci 0000:06:03.0: selfID 0: 807f8c52, phy 0 --.] S400 gc=63 -3W Lci
2014-05-17T16:11:34.341071+05:00 coral kernel:  1150.184043] firewire_core 0000:06:03.0: rediscovered device fw0

So now the question is why the bus resets? This camera used to work fine on an old ubuntu machine.

Thanks Henk. Noted.

You are welcome. I already noted you got it :slight_smile:

The bus reset cycling seems to be a common occurrence in the firewire world. Two good bug report examples shown here:

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