Re: Debian Squeeze problem with firewire_core (DV camera over FireWire)
Hello Camaleón (and others!),
I tried to connect the camera over USB and it worked with streamer:
root@pips04:/home/matpro# streamer -o test_streamer.avi -f rgb24 -r 25
-t 0:10
But before you need to enter this:
root@pips04:/home/matpro# export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so
Don't really know why this is necessary with Debian Squeeze (besides
that it is necessary...), should be done by the OS actually (bug?).
Some information for that connection method:
root@pips04:/home/matpro# dmesg
[...]
[ 173.173619] usb 2-1.3: new full speed USB device using ehci_hcd and
address 3
[ 173.271599] usb 2-1.3: New USB device found, idVendor=04da,
idProduct=231d
[ 173.271604] usb 2-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 173.271608] usb 2-1.3: Product: DVC
[ 173.271611] usb 2-1.3: Manufacturer: Panasonic
[ 173.271613] usb 2-1.3: SerialNumber: 000011946045
[ 173.271749] usb 2-1.3: configuration #1 chosen from 1 choice
[ 173.652873] Linux video capture interface: v2.00
[ 173.715472] uvcvideo: Found UVC 1.00 device DVC (04da:231d)
[ 173.717269] input: DVC as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input12
[ 173.717413] usbcore: registered new interface driver uvcvideo
[ 173.717419] USB Video Class driver (v0.1.0)
[ 173.730212] usbcore: registered new interface driver snd-usb-audio
root@pips04:/home/matpro# lsusb
Bus 002 Device 003: ID 04da:231d Panasonic (Matsushita) DVC Web Camera
Device
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 138a:0008 DigitalPersona, Inc
Bus 001 Device 003: ID 0bda:0138 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Concerning FireWire connection, the Firewire port itself is working.
root@pips04:/home/matpro# ls -l /lib/modules/$(uname
-r)/kernel/drivers/ieee1394/raw1394.ko
ls: Zugriff auf
/lib/modules/2.6.32-5-amd64/kernel/drivers/ieee1394/raw1394.ko nicht
möglich: Datei oder Verzeichnis nicht gefunden
(can't find file or dir)
As I know, FireWire treatment changed in Debian Squeeze, so there is no
raw1394 module anymore.
root@pips04:/home/matpro# grep -e FIREWIRE -e IEEE1394 /boot/config*
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=m
CONFIG_FIREWIRE_NET=m
# CONFIG_IEEE1394 is not set
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
So any further hints for successful FireWire connection?
Regards,
matpro_fhkoeln@lavabit.com
Am 10.09.2011 16:18, schrieb Camaleón:
> El 2011-09-10 a las 15:43 +0200, matpro_fhkoeln escribió:
>
> (resending to the list)
>
>> Am 10.09.2011 14:01, schrieb Camaleón:
>>> On Sat, 10 Sep 2011 03:29:10 +0200, matpro_fhkoeln wrote:
>>>
>>>> I try to connect the Panasonic NV-GS500 over Firewire on Debian Squeeze,
>>>> but it seems that Debian doesn't identify the camera correctly.
>>>
>>> (...)
>>>
>>> Are you sure the camera allows to be put in DV mode (live video
>>> recording) and dumping the content on-the-fly to the PC?
>>>
>>> This usually works whe using manufacturer's windows based applications
>>> but in linux maybe you need to first store the video in the camera and
>>> then copy the files to the computer to edit/manage them :-?
>>>
>>> What non-linear video application are you using to capture the data flow?
>>>
>>> Greetings,
>
>> Hello Camaleón,
>>
>> From the extract attached, this camera should be suitable, I think? What
>> do you mean exactly - is it possible that a camera works in that mode
>> using manufacturer's windows based applications but not in linux? I
>> thought the problem is something like the kernel doesn't recognize it
>> correctly, so it should work actually.
>
> Video cameras (as well as some DSC) may require for a specific way to
> handle data, so I would just first try to get the connection using the
> usual way: store the video in the media card and then copy/paste/import
> the files to your system. If the camera has an additional USB port, you
> can use it to get the files.
>
>> I'm trying it with dvgrab.
>>
>> root@pips04:/home/matpro# dvgrab test-
>> Error: no camera exists
>
> Maybe you should first check if your camera model is supported by
> dvgrab :-?
>
> This is from Kino "requirements" page:
>
> http://www.kinodv.org/article/static/3
>
> ***
> "The most important hardware item (at least if one considers the price)
> is the camcorder. Kino and dvgrab work only with Digital Video (DV) camcorders and
> compatible equipment (...)"
> ***
>
>> Additional information about the FireWire port:
>>
>> root@pips04:/home/matpro# lspci -vv
>> [...]
>> 16:00.0 FireWire (IEEE 1394): Texas Instruments XIO2200(A)
>> IEEE-1394a-2000 Controller (PHY/Link) (rev 01) (prog-if 10 [OHCI])
>> Subsystem: Device 5678:1234
>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>> ParErr- Stepping- SERR- FastB2B- DisINTx-
>> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
>> <TAbort- <MAbort- >SERR- <PERR- INTx-
>> Latency: 32 (500ns min, 1000ns max), Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 16
>> Region 0: Memory at fb204000 (32-bit, non-prefetchable) [size=2K]
>> Region 1: Memory at fb200000 (32-bit, non-prefetchable) [size=16K]
>> Capabilities: [44] Power Management version 2
>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
>> PME(D0+,D1+,D2+,D3hot+,D3cold-)
>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+
>> Kernel driver in use: firewire_ohci
>
> That indicates your firewire port is detected by the kernel. Can you
> try to attach another ieee1394 peripheral (i.e., an external hdd case)
> and check if it works?
>
> In additional, check if you have the required kernel module to grab the
> data:
>
> ls -l /lib/modules/$(uname -r)/kernel/drivers/ieee1394/raw1394.ko
> grep -e FIREWIRE -e IEEE1394 /boot/config*
>
> Greetings,
Reply to: