Problem with firewire bus

working in final cut pro,  when i now plug drives into to frontside firewire 800 port they are running very slowly and when playing a clip fcp freezes up and i have to force quit. when i plug the drives into the backside fw port or use on my macbook pro they work fine so i'm pretty sure problem is wih frontside port. the device does show up on the system profiler. is there a way to tell from that there's a performance problem. are there any easy fixes for the port? is there a way to reset the bus. thanks. 

unplugging is not 100% reliable resetting the SMC.
Hitting the power on button for 10 seconds while unplugged (and everything else too) may.
The older models like 3,1 all had different directions when they came out (1,1 and 2,1 even have a physical SMC button yu can access and use).

Similar Messages

  • Mac Pro Early 2008 problems with firewire 400 drives

    I am having some sporadic problems with firewire 400 drives and am trying to figure out my best options going forward. System 10.5.2 has hung on me twice in the first week of use, and each time I noticed from console there were some problems accessing one or more of these drives (even though I wasn't doing any reads/writes to/from them). Just before one of the crashes, Disk Utility also had problems "seeing" these drives. My external firewire drives are:
    Maxtor OneTouch III 750GB
    Acomdata enclosure/Seagate 400GB
    LaCie d2/160GB
    LaCie w/Lightscribe DVD
    I have this "cobbled" arrangement because I just upgraded from an eMac and needed these drives to manage video files, audio files, photos, etc. While I'd love to go out and buy new internals to install in my spare bays, and migrate the data to them, I will have to do that in stages as my budget is tapped out at the moment. My MacPro is the base version of the early 2008 units, with 300GB internal.
    In the interim, is it worth troubleshooting firmware updates for these externals, or am I destined to continue to have firewire problems? Is there a straight-forward/inexpensive way to remove these drives from enclosures/install in drive bays with an adaptor? I believe the external hard drives are all ATA type drives.
    Thanks in advance for any counsel.

    I would assume that the Maxtor may be SATA. Does it have an eSATA port? Also, there were a lot of threads (in OS X Leopard forum) about those OneTouch units. Same can be said for LaCie problems.
    Yes, check for firmware and configuration. In some cases, and what I do with any new OS, is to reformat all drives - gradually. Given the age of the eMac I'd guess firmware is out of date, and that the drives are formatted some time ago. While you don't have to use GUID, it is a good idea eventually, or just reformat a drive.
    Don't forget to test your drives with Disk Warrior (4.1) also.
    750GB WD Caviar is $139 SATA.
    http://eshop.macsales.com/Specials/XLR8YourMac.cfm?Criteria=&sort=&man=Western%2 0Digital
    Are you using daisy chains? you have one FW bus shared by front and back ports. Do you have any on FW800 or using FW400 to FW800 adapter cable? PCI Express FW400 card might even help a little.
    Never had trouble with OWC enclosures:
    http://www.macsales.com/firewire/

  • Time Machine backup problems with firewire 800 since Mavericks

    Since I installed Mavericks about a week ago, I have had problems with TM not working with my LaCie external drive. At best, it would not back up when the mac was awakened from sleep mode and in use.  When I would open time machine preferences, I would see the "preparing for back up" prompt that would last forever. Not only was it doing that, I have found that it would freeze my mac. I figured this out when I was not able to get my mac to respond from the login screen. It was basically frozen and couldn't log on.  I noticed the back up drive light flickering but nothing would happen even with waiting a long time. I finally figured out that shutting off the TM EHD would unfreeze the mac and it would start functioning normal again. This was happening with my external HD daisy chained to another external drive that contains my iPhoto, iMovie and Itunes files. That drive was also connected to the mac using firewire 800. I tried many different configurations, switched the order the drives were daisy chained, tried different cables and even directly connected the TM drive with firewire 800 to the mac, but the problems still persisted. The strange thing is that when I connect the TM drive through USB, it works flawlesly and no hanging up of the computer. Thats what Ive been forced to do. I have my other EHD connected directly through firewire 800 and it works fine. I only have one firewire 800 port, and since it works fine with my other LaCie drive, it makes me think its not the port or macs hardware? I can only guess this is a Time Machine issue or something wrong with my TM drive?  I have been in contact with LaCie and given them all these details but I have not heard back yet on what they feel the problem is. I thought I would post this to see if anyone else had some experience with this problem.

    Forgot to mention I did that. Completely erased and reformatted HD and then reconnected to TM. Didn't help. I did have the mac hang up while installing Mavericks and had to eventually shut off the external drive. It did that to me the firs time I tried to install Mavericks and I lost all my data because it did a clean install after that. I had another back up on CCC so I just restored from there. This time the update to Mavericks transferred my data. I have had TM hang up my mac in the past on occasion, but I was always able to shut down the drive and then the mac would return to normal. Perhaps I should try to erase and reformat again?

  • FCP Problem with Firewire output to external monitor and speaker ???Help

    i have a g5 powermac. the problem is when using Final cut pro 4hd. when i output my work through firewire to my external monitor and speaker i have a problem with the audio signal. Theres feedback/noise/hiss from the speakers. The firewire connects to DSR-11 vtr deck which feeds my monitor and speakers. it only happens when in FCP is set to A/V firewire output. does not happen if Video output is not set to firewire.
    I Diagnosis is that it is not my dsr-11 deck or firewire i've ruled those out. The problem is either FCP software or Hardware problem with my G5
    Does anyone have a similar problem. please respone, i will try to answer any respones,
    Thanks
    powermac g5     powermac

    CaptM
    From the firewire that feeds the dsr-11. on the output, i use s-video cable to my monitor (sony pvm-14l) and High Quality rca cables thet feed the audio to the Roland Speakers.
    I've changed all wires and still have audio problem. I,ve changed my Dsr-11 deck to my camcorder and still have the problem.
    If any of u guys use FCP The problem happens When I select view> external Monitor > and select firewire for Audio/ and video. I have never changed my editing habits, something just went wrong with the signal, I think its a Hardware problem with the firewire connection. I'm Going to have to bring this to a Apple Service Center In my local area one day.

  • Problem with FireWire audio interface (Edirol FA-66)

    I am experiencing the following problem with my FireWire Audio interface via Edirol FA-66. At unpredictible moments the 'Digital In' LED starts blinking, and after that the audio signal stops working. I do not know if Logic is the culprit, since it also happens now and then with iTunes
    Note: there are digital in/outs connected.
    Only shutting down the Edirol and restarting the iMac G5 resolves the problem, be it only temporary: after a while the phenomenon shows up again.
    Extremely ennoying.
    What could be the culprit?
    Bonkie
    Belgium
    Earth

    Hi Patrick, I don't know that specific interface but could it possibly be that the flashing LED also act as an alert for when the firewire connection has gone down?
    Reason I suggest this is I have the same thing from with my iMac & focusrite saffire Le, where i lose audio now & then, & when it happens if i check in the interfaces software control panel it always has a 'firewire connection error' - I then just have to unplug & replug-in the interface to re-establish the firewire conection. Just a thought but maybe it's worth consulting the edirol manual/tech support to see if this is the case ref the LED function?
    Adam

  • Problem with firewire (since kernel-update?) [solved]

    Hi,
    since i have updated my system, i am unable to connect my dv-camcorder to my firewire-card.
    when i power on my dv-camcorder dmesg says:
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: created new fw device fw1 (0 config rom retries, S100)
    ieee1394: raw1394: /dev/raw1394 device initialized
    NOTE: The dv1394 driver is unsupported and may be removed in a future Linux rele
    ase. Use raw1394 instead.
    firewire_core: giving up on config rom for node id ffc1
    If i then disconnect and reconnect it, dmesg says the following:
    firewire_core: BM lock failed, making local node (ffc0) root.
    firewire_core: phy config: card 0, new root=ffc0, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: created new fw device fw1 (0 config rom retries, S100)
    I have tried a canon mv700 as well as a canon xm1, both lead to the same problem. I have tried to connect my camcorder also to my notebook which also runs the latest version of arch, but leads to the same problem too.
    I think there is a problem with the new kernel or something. Two weeks ago, before updating my system, everything works well.
    Any suggestions or ideas?
    Anyone with similar problems?
    Greets,
    smove
    Last edited by smove (2008-05-06 19:32:14)

    I solved this problem. Since kernel 2.6.22 there is a new firewire-stack available called 'juju'. Because of it´s experimental state it is not recommend to use it. In the current kernel-package the old and the new firewire-modules are included but the new instable ones are used by default. To fix the problem you have to blacklist the new firewire-modules.
    Create the following file:
    /etc/modprobe.d/newfw_blacklist:
    blacklist firewire-ohci
    blacklist firewire-sbp2
    Reboot your system and try to use your firewire again. Look if the old modules are loaded instead of the new firewire-* ones. I dont understand why the new firewire-modules are used by default in the new kernel-packages. Refering to http://wiki.linux1394.org/JujuMigration … 857ee71b93 it is not recommended to use the new modules yet.

  • Big problems with Firewire iPod and camcorder  - please help!

    Hi all,
    I don't know where else to turn with this problem. I think I've damaged my Firewire kit.
    I have an iPod 4G 20GB and a Canon MV901 MiniDV Camcorder. I used them both over Firewire with my Pismo without difficulty, but I then tried video editing on my Windows machine with a firewire PCI card. Scrabbling around the back of my computer, I think I somehow managed to get the firewire cable to the camcorder in the socket upside down, reversing the power and data conncectors. Nothing really happened, but the camcorder stopped showing up. I tried it a good few times, then tried my iPod. By some bizarre coincidence, I think I managed to plug the iPod in the same way. Now, my iPod doesn't work on either the Windows machine or the Pismo over firewire, but does over USB2.0 on my Windows machine.
    I measured the power going through the Firewire power pins as around 13.5 volts on my Pismo and the card, but the card also has an auxiliary power connector. This was disconnected when I tested it, but was connected when the iPod and camcorder were.
    The thing I would like to know is whether a voltage spike of this size could fry the firewire controllers on both devices. The iPod's diagnostic mode detects that firewire is connected, but will not show up. Strangely, it still charges over firewire from either machine. Have I permanately damaged the firewire controllers?
    Thanks in advance,
    Rob Johnson

    Rob,
    If you mistakenly inserted the FireWire connector twisted 180 degrees, the power lines can be directly connected to the data lines and can result in a fried PHY (connects the port to the FireWire bridge) or the FireWire bridge itself.
    You can take a look at the voltage specs for FireWire ports and see that your voltage readings are well withing specs:
    http://docs.info.apple.com/article.html?artnum=58207
    I am not sure where you go from here. You could try a known-good FireWire device connected to your Pismo and see if it works. If not, the data-side of the FW port may have failed. I don't know about testing the iPod or camcorder.
    A possible cheap fix for the Pismo FireWire is a FireWire PC card; if running 10.x, it will just be a plug & play affair. However, unlike built-in FireWire ports, FireWire PC cards supply very little bus power. Your camcorder will work since it has it owns power supply (assuming there is no hardware failure) and but am unsure about the iPod. The iPod will not charge, of course, but it may still work in data transfers. There are a few FireWire PC cards that also have their own power supply.

  • Audio problem with firewire to thunderbolt adapter

    I am running four channels of audio from a Yamaha Motif synthesizer into a new iMac using the firewire to thunderbolt adapter and recording to Logic.   I get very loud distortion.  I unplug the same cord and remove the adapter and run the same audio into my 2011 MacBook Pro and record the audio with no distortion.  I can run MIDI into the iMac using the adapter with no problem.  What gives?

    The iMac has three USB and three Thunderbolt.  The Yamaha has Firewire out which carries 16 channels of audio.  It works great with my MacBook Pro, but the Thunderbolt Converter seems to mess it up.  It's fru
    strating having bought a brand new iMac and not being able to use it to record.  Now when I try to record a single channel of piano, Logic starts blinking on and off, alternating with whatever window is behind it.  This is doubly frustrating.

  • Problems with Firewire - Connecting a device to either FCP or iMovie :(

    I have been trying (without success) to get video from a MINI DV tape currently inside a Panasonic DVC30 to either my MacBook Pro (2months old) or my iMac (also about 2months old) via a FireWire cable i got of eBay for a fiver.
    Neither machine will recognise the camera, in either FCP or iMovie.
    I thought it could be my cheap cable, but when I took my MacBook and camera into Uni today, and got the Stores dept to lend me another cable, the same result - nothing. So then i thought my cable could be ok, and maybe it was the Uni camera, so we tried the tame in another Camera, with my cable, still nothing. So then, we tried the 2nd camera, with a new cable, still nothing.
    I really do now know what to do. Last week, I managed to get Video off a camera, with a Uni FireWire cable, so i dont think its the FireWire port. I still think it could be this new cable, but the fact that other cable and other camera today failed to show the device is odd.
    Someone said it could be a Driver issue, but why? and aslo, if it is, where do i get new drivers from?? I have just updated the software on both MacBook and iMac, but it still doesnt recognise the device (camera) using my FireWire cable in either FCP or iMovie, and so I am stumped.
    Can anyone, who knows a lot more than me help? I have used PCs for 20 years, and only recenlty been converted to MACs, but im starting to worry!!
    Cheers
    Neil

    Thanks for you reply, but I have already tried that, and when you look at the Firewire in the menu, nothing is coming up. I find it odd that this is happening on both my MacBook Pro and my iMac ?
    We tried today, with both a different camera and same cable, and then a different cable and different camera, and none of any of the combinations seems to pick up.
    Does this mean that both my MacBook and iMac need new drivers etc?? If it is the Bus, what can be done?
    Many thanks
    Neil

  • Problem with doing bus to Aux/live rack unit sends

    Hi all,
    Just recently bought a compressor and a Spring Reverb... both rack units (not plug ins).... both with (1/4'') IO.
    My plan was to do a Bs send to an Aux. that utilized the IO plug in (routing a send and return to one of my new units). There after, I was hoping I could use the Bus send on the audio source track to send to the Aux/effect and then have a blend of dry and effected signal overall.
    I think I missing something because with both units I have and issue where I hear a very unpleasant double sound and I'm fighting feed back... this is the case if I put the IO plug in on the source track and the Aux... so I figure that's where my problems lies...
    Can anyone see what I might be doing wrong?
    Huge thanks for any help.
    Best,
    Ben

    Why do you put the IO on both tracks? I would use it solely on the aux track.
    Eddie

  • Problems with firewire / coreaudio - abnormal cpu usage

    (powerbook aluminium..)
    I own a Presonus Firebox firewire audio device that makes use of the coreaudio drivers of OSX. As soon as I connect it to the build-in firewire port, kernel_task eats up 15% of my cpu. (when disconnected, kernel_task is at 0,5%) Secondly, ghost spikes appear at regular intervals.
    I first thought it had to do with the firebox, but I tested several brands - all using the coreaudio drivers - with the same results. The ghosts spikes appeared too.
    Other devices, such as DV cameras, Harddrives etc, work fine. No spikes, nothing. So only devices that make use of coreaudio create problems.
    How can I find out if either the drivers are corrupt, the motherboard is faulty, or something else is going bad?
    I bought a firewire pccard, but the problem is the same.
    I reset pram & hardware, but no difference.
    What can I do to fix this?
    forgot to mention that the powerbook whines like crazy when the audio device is connected.

    Hi, kahara. Try reposting in the Aluminum Powerbook discussions area.

  • Problem with FireWire Hard Drive and JVC MiniDV Video Cam

    I've been running my iMac with a 1 TB WD MyBook Firewire drive and it has been working fine.
    I just purchased a JVC GR D850 miniDV camera. I hooked the camera up to the second FireWire port on my iMac and, initially, the import of the video from the camera into iMovie was ok (video being saved to the external firewire drive). After a couple of minutes, I got a warning that a device had been disconnected improperly, apparently the firewire drive just disconnected itself from the machine. I rebooted everything and once again, as soon as I turned on the video camera the drive disconnected.
    After that, the iMac won't even recognize that the video camera is connected, and when I checked the little bit of video that had been saved on the drive it was unusable. Completely choppy.
    Am I dealing with a problem of too little power/memory on this G5 iMac?

    You don't specify which model iMac you have, but 2 GB should be enough to handle a video download. Can you try connecting the camera to another computer to see if it is faulty?
    Also, have you tried connecting the camera to the port that you have the MyBook in?
    Try resetting the SMU and see if that helps. Please post back with results,

  • Extreme problems with Firewire 800 on my mini

    Okay, so I am having a doozie of a problem. I have a Focusrite Saffire audio interface that hooks up to my PC via Firewire 400. I bought the adapter so I could use it on my brand new Mac Mini's Firewire 800 port. Now, just like others have said on this forum, the computer will simply not detect the device at all. I hooked it up to my friend's Macbook with the 400 port, and it detected it right away and made it available for use. It powers the device while it is plugged in, and yes, I have tried it with the power supply plugged in as well, but nothing I have tried works. I bought this machine to use in a home studio, and I have not been able to do a single thing with it since I received it. I searched this forum, and there are plenty of threads stating that these problems are happening, but not a single thread with any kind of solutions. Can anyone please help me out with this before I just return it?

    Yo, I have the saffire and have been trying to get it to work with my macbook pro for the longest time. Originally I was going to send the saffire in for repair(that is what focusrite suggested)but recently I had wiped out my computer and started over. After I reinstalled and updated the OS to 10.4.11 I plugged in the saffire. After approx. 2 min the saffire leds where green and It worked. I have used it for output for my computer and in Traktor Pro(native instruments). It seemed to work fine for a day or two and sure enough I start up my computer and plug in the saffire and no response. I have tried every f===in thing that focusrite has suggested and anything I have seen on this and other forums. In apple developer site it explains that devices like the saffire with rom get a registry entry created to let the mac know where the device is. I believe this is where the problem occurs. I don't know the tech lingo or where these registries are stored on my mac or if this is related to the .kexts. the pack sdk 24 or whatever is on the developer site for the post earlier. Hopefully someone figures this problem out. Peace

  • Weird Problem with Firewire Drive on 17" MBP

    I have an external firewire drive that worked great on my 15" MBP and with any other computer I have never had any problems. The problem occurs when I plug the drive into my 17" MBP with the magsafe connected, it just wont mount, but as soon as I unplug the magsafe the drive mounts. Really weird. Anyone have a similar problem? I am going to the Apple Store and see if I can duplicate the problem.

    I'd backup your files if you can. If the drive is failing then the advise you've gotten is good advise. You can try software recovery if you are unable to use the drive:
    Basics of File Recovery
    Files in Trash
    If you simply put files in the Trash you can restore them by opening the Trash (left-click on the Trash icon) and drag the files from the Trash to your Desktop or other desired location. OS X also provides a short-cut to undo the last item moved to the Trash -press COMMAND-Z.
    If you empty the Trash the files are gone. If a program does an immediate delete rather than moving files to the Trash, then the files are gone. Recovery is possible but you must not allow any additional writes to the hard drive - shut it down. When files are deleted only the directory entries, not the files themselves, is modified. The space occupied by the files has been returned to the system as available for storage, but the files are still on the drive. Writing to the drive will then eventually overwrite the space once occupied by the deleted files in which case the files are lost permanently. Also if you save a file over an existing file of the same name, then the old file is overwritten and cannot be recovered.
    General File Recovery
    If you stop using the drive it's possible to recover deleted files that have not been overwritten with recovery software such as Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.
    The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
    Also visit The XLab FAQs and read the FAQ on Data Recovery.
    If the above is not possible then sending the drive to a data recovery service may be your only option, and they are very expensive.

  • Problems with firewire drive

    Hi all.
    Ive got a problem I need help with. Just installed Final Cut 3 on this older G3. Would like to do a little editing at home. Have a 240 gig Lacie firewire drive that I would like to use as a scratch drive. The drive was originally used on a pc so I initialized it on the mack Mac OS Extended (Journaled). I can capture video to the internal Mac harddrive but not the Lacie. Capture stops after a few seconds. I have tried transfering captured video from the internal drive to the Lacie but I get an error message and it wont transfer. Any ideas what I need to do to remedy this situation?
    Thanks
    Rocky
    g3   Mac OS X (10.3)   256 mb ram

    This seems wrong. I have two firewire drives daisy-chained and then plugged into my cube, and on the other firewire port I have my cinema display's hub which leads to my ipod mini and my belkin mac mini USB and firewire hub, where I connect my DV camera for import. I have had no problems importing footage to my FW drives. I'd say don't plug the camera into the computer through the FW drive, just straight into the computer. If that doesn't work, try what the other guy said about either reinitializing it or use disk utility to check the drive and maybe verify/repair something on it.
    -Brian

Maybe you are looking for