Firewire On CentOS-6 ???

Home » CentOS » Firewire On CentOS-6 ???
CentOS 4 Comments

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

4 thoughts on - Firewire On CentOS-6 ???

  • 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
    ——————–

  • Op 02-08-13 18:15, Fred Smith schreef:
    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.

  • 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

LEAVE A COMMENT