Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Restart the FireWire DV driver to cure FCP issues System
I've occasionally had a problem with Final Cut Pro where Firewire would get screwed up and my DV VTR would stop seeing any DV video from FCP.

A cool geeky trick that works for me is to cause the Firewire DV driver to be stopped and unloaded from the kernel, then reloaded and restarted

Read the rest of the article for the quick how-to.

Here's the procedure:
  1. Turn off all Firewire DV devices attached. Wait 10 seconds or so.

  2. In the Terminal:
     sudo kmodunload -v -n
  3. Enter your password for sudo, and you should see something like:
     kmodunload: found kmod, id 62.
    kmodunload: kmod id 62 successfully stopped.
    kmodunload: kmod id 62 successfully unloaded.
    If you see something like this:
     kmodunload: found kmod, id 91.
    kmodunload: kmod_control(stop) failed: (null)
    then the VTR isn't turned off, or another attached DV device isn't turned off, or the system's really hosed and needs a reboot.

  4. Turn the Firewire DV devices back on, which should reload and restart the driver. You can check with:
      sudo kmodstat | grep FireWireDV
    where you should see an entry for the Firewire DV device.
[Editor's note: I have not tested this myself.]
  • Currently 4.33 / 5
  You rated: 5 / 5 (3 votes cast)

Restart the FireWire DV driver to cure FCP issues | 1 comments | Create New Account
Click here to return to the 'Restart the FireWire DV driver to cure FCP issues' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Authored by: barryjaylevine on May 14, '02 10:57:26PM

If you have FW devices that don't show up or disappear, the official advice on FireWire woes suggests that you power down all attached FireWire devices -including FireWire hubs AND your Mac! (Your Mac is also a FireWire device!) Then restart. Note that simply restarting your Mac will often not reset a FireWire chip that is causing the problem but powering everything down will. This is not theory; it works.

[ Reply to This | # ]