linux1394-user

kino won't talk to handycam

[Walt F. <qua...@gm...>]

Hello all:

I have a dell E520 on which I run Ubuntu 11.4. I also have a Sony
Handycam DCR H30, and wanted to do some editing of videotapes. The E520
doesn't have firewire, so I got a PCI Card I thought was
linux-compatible. I then downloaded kino, but it gives me the "warning,
raw 1394 module not loaded" mesg, but WILL open up when I go through
sudo kino. . .but then it says "no avc compliant cam connected or not
switched on", and it doesn't know when I do switch it on.

lspci:   03:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8
[Fire II(M)] IEEE 1394 OHCI Controller (rev 80)


 grep 1394 /var/log/kern.log
Jul 25 17:41:49 walt-Dell-DM061 kernel: [    1.913943] pnp 00:06: [mem
0x01000000-0x1f651bff]
Jul 25 17:41:49 walt-Dell-DM061 kernel: [    1.913947] pnp 00:06: [mem
0x000f0000-0x000fffff]
Jul 26 21:01:59 walt-Dell-DM061 kernel: [    9.139447] usbcore:
registered new interface driver usblp
Jul 27 10:25:08 walt-Dell-DM061 kernel: [    1.851394] PCI: Using ACPI
for IRQ routing

Which seems to show it isn't initialized. I downloaded and installed
everything I could find in synaptic that had anything to do with 1394.

Can you tell me what I'm missing?

Thanx for your help.

Re: kino won't talk to handycam

[Stefan R. <st...@s5...>]

On Jul 28 Walt Frazer wrote:
> I have a dell E520 on which I run Ubuntu 11.4. I also have a Sony
> Handycam DCR H30, and wanted to do some editing of videotapes. The E520
> doesn't have firewire, so I got a PCI Card I thought was
> linux-compatible. I then downloaded kino, but it gives me the "warning,
> raw 1394 module not loaded" mesg,

Kino is no longer actively updated.  Therefore it warns about raw1394 not
being there, which is normal in current Linux distributions.  Kino only
needs
  1. the firewire-core and firewire-ohci kernel modules being loaded into
     the kernel,
  2. firewire-ohci being successfully bound to a controller,
  3. firewire-core successfully talking to attached FireWire devices,
  4. udev configuring proper access permisions or ownership of /dev/fw*
     character device files.

I suspect the third point goes wrong on your system.

> but WILL open up when I go through sudo kino. . .

Don't run application programs with sudo.  This is dangerous and may
malfunction.

> but then it says "no avc compliant cam connected or not
> switched on", and it doesn't know when I do switch it on.
> 
> lspci:   03:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8
> [Fire II(M)] IEEE 1394 OHCI Controller (rev 80)

OK; this is a VIA VT6307 which many people use successfully under Linux.
I had one myself for a while on a mainboard.

>  grep 1394 /var/log/kern.log
> Jul 25 17:41:49 walt-Dell-DM061 kernel: [    1.913943] pnp 00:06: [mem 0x01000000-0x1f651bff]
> Jul 25 17:41:49 walt-Dell-DM061 kernel: [    1.913947] pnp 00:06: [mem 0x000f0000-0x000fffff]
> Jul 26 21:01:59 walt-Dell-DM061 kernel: [    9.139447] usbcore: registered new interface driver usblp
> Jul 27 10:25:08 walt-Dell-DM061 kernel: [    1.851394] PCI: Using ACPI for IRQ routing

Yeah, just don't filter through grep then.  :-)

> Which seems to show it isn't initialized. I downloaded and installed
> everything I could find in synaptic that had anything to do with 1394.
> 
> Can you tell me what I'm missing?
> 
> Thanx for your help.

As root user, run "echo 7 > /sys/module/firewire_ohci/parameters/debug",
then connect the camcorder, then watch what is being added to the kernel
log and post the result here.
-- 
Stefan Richter
-=====-==-== -=== ===-=
http://arcgraph.de/sr/

Re: kino won't talk to handycam

[Stefan R. <st...@s5...>]

> On Fri, 2011-07-29 at 08:29 +0200, Stefan Richter wrote:
> > As root user, run "echo 7 > /sys/module/firewire_ohci/parameters/debug",
> > then connect the camcorder, then watch what is being added to the kernel
> > log and post the result here.

PS:
In a terminal window, you can log in as root by the command "su".  Unlike
"sudo", this command requires the root password, not the user password.

Or you can perform the ">" redirection also with sudo (with the user
password) in the following way:
sudo sh -c 'echo 7 > /sys/module/firewire_ohci/parameters/debug'

After that, "cat /sys/module/firewire_ohci/parameters/debug" should
confirm that there is a 7 in there now.  You can later echo a 0 into the
parameter in order to switch debug logging off again.

The above only works if sudo is configured rather liberally on your system.

Or you can do the following instead:
  1. Unload the controller driver with
     sudo modprobe -r firewire-ohci
  2. Check that it really went away.
     lsmod | grep fire
     (should not show firewire_ohci anymore)
  3. Load it again but with debug logging enabled.
     sudo modprobe firewire-ohci debug=7
  4. After you tested the camcorder and gathered the debug log, you get
     rid of the noisy driver by unloading it again.
-- 
Stefan Richter
-=====-==-== -=== ====-
http://arcgraph.de/sr/

Re: kino won't talk to handycam

[Stefan R. <st...@s5...>]

For the list to know:  The issue seems to be resolved by replacement of
the cable.

On Jul 30 Walt wrote:
> Stefan:
> 
> I think I finally discovered the problem. I bought a new cable last 
> week, then realized I had another already. After using the new one, and 
> running out of other things to test, I plugged in the cable I already 
> had and it worked!  I've had a lot of practice with root commands and 
> leaned much about raw1394 that I never knew.
> 
> Thank you for your time and patience.
> 
> 
> Walt Frazer

-- 
Stefan Richter
-=====-==-== -=== =====
http://arcgraph.de/sr/