Op 02-08-13 18:15, Fred Smith schreef:

On Sat, Jul 27, 2013 at 03:06:41PM -0400, Fred Smith wrote:

Since I've received no responses, whatsover, to the posting below, I'm going to guess no one in the Centos community uses Firewire with Centos... Please correct me if I'm wrong.

Nevertheless, I'd appreciate any advice/guesses/guidance/related info if anyone has any at all.

Googling, I found a post from around 2006 or so (Centos 4.1) saying that Centos doesn't compile Firewire support, and which then gave some steps for installing a CentosPlus kernel.

Is that still the case? I'd sure be not real happy to have to install a nonstandard kernel...

But since there ARE some packages whose namems contain the string "1394" one would think that maybe it is INTENDED to be supported.

But either way, I am not getting anywhere with it.

Below, I give all the info I can think of that might be helpful in determining what's my problem, so I'd appreciate it if someone who knows something about Kernel and/or Firewire could drop me a note.

Thanks a bunch!

Fred

...

Hi all!

I'm trying to use my first-ever firewire device, and just OOB I'm not getting very far, so advice would be appreciated.

When I plug in the device I see some entries in /var/log/messages:

Jul 27 14:50:30 fcshome kernel: firewire_core: phy config: card 0, new root=ffc1, gap_count=5 Jul 27 14:50:31 fcshome kernel: firewire_core: created device fw1: GUID 0003f300118123f9, S100

lsmod says this:

# lsmod | grep fire firewire_ohci 24695 0 firewire_core 50151 1 firewire_ohci crc_itu_t 1717 2 udf,firewire_core

I have these 1394-related packages installed:

# yum list installed | grep 1394 libavc1394.x86_64 0.5.3-9.1.el6 @anaconda-CentOS-201207061011.x86_64/6.3 libdc1394.x86_64 2.1.2-3.4.el6 @base libdc1394-docs.x86_64 2.1.2-3.4.el6 @base libdc1394-tools.x86_64 2.1.2-3.4.el6 @base libraw1394.x86_64 2.0.4-1.el6 @anaconda-CentOS-201207061011.x86_64/6.3

lspci says this:

03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

the only mention of 1394 that I see in /etc/modprobe.d is this (grep output):

dist.conf:install eth1394 /bin/true

which, to the limited extent of my understanding shouldn't be a problem.

I'm trying to use Kino. when I start it up and click the "capture" tab on the right I get a warning in the bar at the bottom of the Kino window that reads:

WARNING: raw1394 kernel module not loaded or failure to read/write
         /dev/raw/1394!

which makes sense since there ins't a /dev/raw/1394. however, according to this:

# find /dev -name *firewire* -print /dev/.udev/db/firewire:fw1 /dev/.udev/db/firewire:fw0

there are two firewire device nodes.

Should Kino be using one of those device nodes instead of /dev/raw/1394? Or if not, does anyone have further advice (preferably helpful advice) ??

thanks!

Fred

Hello Fred,

I've used this before on Centos6.4, with Kino. My apologies for not answering your post. When I saw it, I wanted to pull out my camera and look at how I did this, because it's some time ago.

But it does work.

I believe I searched for a while and in the end it was a permission issue.

I promise I will take the camera tomorrow and have a look.

Greetings, J.

On Fri, Aug 02, 2013 at 09:33:48AM -0700, Bart Schaefer wrote:

On Sat, Jul 27, 2013 at 12:06 PM, Fred Smith fredex@fcshome.stoneham.ma.uswrote:

...

I'm trying to use Kino. when I start it up and click the "capture" tab on the right I get a warning in the bar at the bottom of the Kino window that reads:

WARNING: raw1394 kernel module not loaded or failure to read/write /dev/raw/1394!

Maybe this explains a little?

https://www.kernel.org/doc/Documentation/ABI/removed/raw1394

https://www.google.com/search?q=kino+raw1394+kernel+module+not+loaded

Ah ha!

Running Kino as root automatically finds the firewire video stream and can be used to capture it! But I really dislike running big(gish) apps as root. Wonder if I can figure out which device (/dev/fw1 ???) to chmod so I don't have to run it that way...

And I doubt any of you can help me with this, but let me throw it out here anyway:

I'm using a "Dazzle Hollywood DV-Bridge" to capture output from a vcr, so I can try making DVDs out of a bunch of purcased VCR tapes of TV series.

So, my VCR has only the RF/coax output, OR RCA jacks. The Dazzle device accepts several different types of input, S-video, firewire, or component (RCA) jacks.

I've got one RCA cable from the VCR RCA (video) output jack to the Dazzle's RCA (video) input jack, and one from the VCR's audio output jack to the left channel audio in on the Dazzle (my VCR doesn't provide stereo outputs, so I figure I'll have to somehow manage to copy the audio into both channels in an editor, or else acquire a RCA-to-RCA Y connector).

So, when I fire up Kino and start the VCR, it displays the video, but I get no audio.

I'd have thought that the firewire channel from the Dazzle device to my PC would carry the audio, but apparently not. Might it be necessar to run another cable from the Dazzle device just for audio?

Also, on Kino's "capture" screen is a "MUTE" button which when I click it, causes an endless and rapid stream of:

ALSA lib pcm.c:2209:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp Could not open ALSA device "/dev/dsp": No such file or directory

in the root window from which Kino was started.

[later] So, starting kino from a root window as "padsp kino" quiets the stream of errors, but I still don't seem to be getting any audio. I think it's time to go investigate all those various inputs I see in AlsaMixer that I don't know what they do.

Thanks!

Fred