Re: Error: no camera exists
Brought to you by:
aeb,
bencollins
From: Stefan R. <st...@s5...> - 2015-10-19 07:01:35
|
On Oct 12 David wrote: > On 12/10/15 17:35, Stefan Richter wrote: > > What do you get in the kernel log if you run > > sudo modprobe -r firewire-ohci > > sleep 1 > > sudo modprobe firewire-ohci debug=2 > > while the camcorder is plugged in and switched on? > > > > And after this, what do you get if you leave firewire-ohci this way and > > unplug and replug the camcorder? > > > > (Please carefully note which kernel messages follow from what action.) > plugging and unplugging the device resulted in nothing in the log :( > > The camcorder is definitely getting a signal of some sort because it > displays "HDV/DV IN" on it's screen. This stays on during reboot, so I > guess it's just some power thing. > > The camera is definitely working OK because (I hate to say it) it > connects to an Apple OK > > david@david:/var/log$ tail -f -n0 kern.log > Oct 12 23:02:48 david kernel: [ 675.823166] firewire_ohci 0000:08:06.0: PCI INT A disabled > Oct 12 23:02:48 david kernel: [ 675.823171] firewire_ohci: Removed fw-ohci device. > Oct 12 23:02:48 david kernel: [ 675.830928] firewire_ohci 0000:08:01.0: PCI INT A disabled > Oct 12 23:02:48 david kernel: [ 675.830933] firewire_ohci: Removed fw-ohci device. This is from "modprobe -r", and it shows shutdown messages from two OHCI link layer controllers. As you mentioned in today's post, you actually have two controllers. > Oct 12 23:03:03 david kernel: [ 690.683053] firewire_ohci 0000:08:01.0: Refused to change power state, currently in D3 > Oct 12 23:03:03 david kernel: [ 690.683067] firewire_ohci 0000:08:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > Oct 12 23:03:03 david kernel: [ 690.683126] firewire_ohci: Failed to reset ohci card. > Oct 12 23:03:03 david kernel: [ 690.683144] firewire_ohci 0000:08:01.0: PCI INT A disabled > Oct 12 23:03:03 david kernel: [ 690.683153] firewire_ohci: probe of 0000:08:01.0 failed with error -16 One of the last steps to initialize the first controller failed. It is not clear why that happened. > Oct 12 23:03:03 david kernel: [ 690.683171] firewire_ohci 0000:08:06.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > Oct 12 23:03:03 david kernel: [ 690.738942] firewire_ohci: Added fw-ohci device 0000:08:06.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x2 > Oct 12 23:03:03 david kernel: [ 690.739165] firewire_ohci: 1 selfIDs, generation 1, local node ID ffc0 > Oct 12 23:03:03 david kernel: [ 690.739172] firewire_ohci: selfID 0: 807f8c56, phy 0 [---] S400 gc=63 -3W Lci > Oct 12 23:03:04 david kernel: [ 691.238374] firewire_core: created device fw0: GUID 00cc13240000241d, S400 The second controller is initialized seemingly fine. From your lspci listing: > 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5) This bridge implements a PCI bus, on which the following devices are located (if I read the listing correctly): > 08:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024] > 08:07.0 IDE interface [0101]: Integrated Technology Express, Inc. IT8213 IDE Controller [1283:8213] The device 08:01.0 is notably absent from the lspci listing. Maybe the contact is loose, as Carl suggested among else. I also note that the "dmesg -T | grep firewire" results which you posted in your initial message were all from device 08:06.0, and none were from 08:01.0. -- Stefan Richter -=====-===== =-=- =--== http://arcgraph.de/sr/ |