Firewire issue

Hi
After six years working mainly with Final Cut Pro 2 and a La Cie 45 Gb external hard drive as sctrach disk, on a Power G4 450 Mhz AGP graphics with 1 Gb ram, running Mac OS 9.2.2, and after unadvertedly filling too much the drive I started geting error messages urging me to repair the drive with Disk Warrior, which I did after disconecting and reconnecting all firewire cables, erasing and reformatting the drive.
Everything looked fine, but after aquiring some more video from my Sony Video Walkman GV-D900E PAL, the error appeard once more and again I had to use Disk Warrior for the drive to work .
At this point I noticed everytime I graphed the drive in Disk Warrior before rebuilding the first part of the graphic was allways dark blue and almost without fragmentation...
Since the hard disk was six years old and too small to my needs, I formatted it in my Powerbook G4 667 Mhz, running OS 10.3.9 , and put it aside to eventually connect it to my La Cie 160 Gb I use with my powerbook to get some extra space.
Then bought a new 500 Gb LaCie Big Disk Extreme with triple interface thinking this would solve the problem.
After installing Silverlinig software under Mac OS 9.2.2, I started using the new external HD, HFS+ formatted, as scratch disk in Final Cut, and everything went well untill I had to have some work done with the crop tool in one of my clips... I was not able to save it to the drive and error messages start popping again with much more damage reported in Disk Warrior... and everything went back to departure point.
All my internal and external drives are more than 70% free.
Can someone help please ? lots of work to do and my powerbook is already filled up with other projects...
Powerbook G4   Mac OS X (10.3.9)   Power Mac G4 450Mhz 0S 9.2.2
Powerbook G4   Mac OS X (10.3.9)   Power Mac G4 450Mhz 0S 9.2.2

thank you Michael
Anyway, disk utility under Mac OS 9.2.2 does not repair firewire drives, and when it verified the La Cie drive it concludes the drive appears to be Ok.
Everything here started with a message (wihle working in FCP 2) stating the firewire La Cie 45Gb had stoped responding... than I verified the drive and it had only 7Gb free at the time. I erased the disk, reformatted it and it started working again, but when started capturing media again, error messages kept coming and I used Disk Warrior to correct the directory tree... The thing is, each time I captured more video, the error messages kept showing.
When I bought a new La Cie Big Disk Extreme 500Gb external firewire drive, the error messages did not stop... So, it appears to me that either the new drive is defective or there are problems with my G4 firewire ports...
I had the new drive formatted in my Powerbook under Mac OS 10.3.9, and as soon I plugged it to the Power Mac I got a message from Norton File Saver stating the head block of the Drive was dammaged...
D'ont know waht to do... Maybe I should install a PCI firewire 400 card and install Tiger on the Power Mac as well as FCP 4...
What do you think ?

Similar Messages

  • Firewire Issues: External Hard Drives & DV  Deck Sony DSR 11 not recognized

    So, I have this brand new $6000 Mac Pro that will not recognize a simple DV deck, nor the external HD's.
    Thus, after spending seven hours searchig around last night, trying every configuration possible from updates, unplug power source, and everything else, I began making calls as of 4 am this morning.
    I was referred to FCP Europe where I was informed that I needed FCS friver updates. (unavailable for 1.0.1) or perhaps it was a Sony issue. The deck & drives work fine with my G4 & Powerbook G4. With six fire wire ports on the Mac Pro, and nothing being recognized via a single fire wire port, does anyone have a simple, expedient solution? Thank you.

    Ahhhh. Firewire issues. I'm convinced that these Macpros have some serious problems here. I am running a sony dsr11 also with a digi002. MY issues is bootup. . I have a mac pro with Tiger installed. My issue is I intermittently get a prohibitted error on bootup. The error looks like a no smoking sign without the cigerett. I have to re boot and sometimes the os boots right up othertimes not. I have sfound that I have to boot my sytem with noting hooked up first. It seems when you have high end firewire devices that the Bus just can't handle it. Real ****** for thos who bought the system for A/V work. Everything woks fine on my powerbook and my G5. Problem is with MACPRO! Do you also have other firewire devices hooked up? Are they daisychained together?
    Vito

  • CS5 support is falling down - the famous firewire issue

    As a loyal user of Adobe professioanl editing solutions for the last 10 years this past month has been a nightmare.  When I inquired about upgrading to CS5 from CS3 I was advised during an online chat with an Adobe person here on the site to upgrade to CS4 and because of the timing I would get a complimentary CS5 upgrade.  I purchased CS4 on April 14th and had so many issues it was never even used in the edit suite.  When CS5 became available I decided to cut my losses and decided if I was going to have to go through all the hoops I might as well only go through them once with CS5.  I have had numerous long discussions with Adobe "support" regarding various problems and now I am at the end of my rope.  Even though they say the are taking notes during our conversations each subsequent "support" person claims to not know most of the pariculars discussed in previous phone calls.  I didn't think I had to follow up each phone call with a note here but evidently that is the case.  Today I have a deadline to deliver content on TAPE to a national cable network and the series contract could be in jeapordy if I can't deliver the first of 26 episodes.  I CANNOT PREVIEW ON AN EXTERNAL TELEVISION MONITOR OR EXPORT THROUGH FIREWIRE TO MY MAIN DV DECK.  It is a deck I have used for YEARS with Premiere CS2 and CS3 and i NEVER had an issue like this.  I have been told repeatedly that the issue would be resolved and most recently on Tuesday of this week I was promised a callback between "1PM and 2PM" Central Standard time on Wednesday, THAT CALL NEVER CAME.  When I followed up with another call MOST of the days previous discussion was NOT in my case notes.  I was told my main Sony VTR and secondary JVC VTR were not HDV decks even though I have been using BOTH for many years for just that purpose and even though that didn't address the most pressing of all my issues which was just getting output through firewire to tape.  After a very frustrating call I was promised another callback "in an hour" by a "supervisor".  That call NEVER came.  Both Adobe "support" and PNY Quadro "support" claim that they have "never" heard of the firewire issue even though it is all over the forums at Adobe.  I will be posting this and every subsequent communication between me and Adobe on the forums, at Yelp and any other web sites that take reviews of professional video products.  For the record just some of my other issues include the inability to capture HDV from the Sony HDV deck I have been capturing from for years, Alpha Glow not working and no split screen when doing color correction in a number of effects where it is offered.   Also for the record I have tried turning off the MPE GPU acceleration to export to tape and that doesn't work either.  System is a Supermicro dual processor motherboard with lots of ram and a Quadro FX 3800 operating with 64 bit Windows 7.

    Read here:
    http://kc.flex-radio.com/KnowledgebaseArticle50433.aspx
    It may get firewire working again on your older deck with Windows 7.  If the solution on that page works, then the problem is down to Microsoft, not Adobe.
    FWIW, it's getting to be pretty well known around these parts that the current implementation of Adobe Customer Service is awful.  That said, several Adobe employees, including some Premiere Pro engineers, have been hanging out in the forums recently.  This is a big change from earlier releases of Pr, where an Adobe presence was rarely seen at all.
    These same folks have also said that Adobe is working to improve their Customer Service.  Like the inertia of a large ship forcing it to take a long time to change course, I suspect that it will take a bit longer for Adobe to make that improvement than it would for a smaller company.  Don't give up on 'em just yet.
    -Jeff

  • 10.8.4  update firewire issues

    10.8.4  update is not fixing the firewire issues that 10.8.3 caused with my macpro.  my printer (professional Epson)
    hard crashes when accessed.   I'm reporting this because there are many people having firewire issues with firewire
    printers and 10.8.3. 

    Use the workaround until the FW issue is resolved:  use a USB cable.
    OT

  • FireWire Issues - anyone else?

    Have a PB G4, 1.67, with an Apple-repaired logic board [from Nov 08]. After latest Security updates, I have had trouble connecting either 800 or 400 FW drives. I've tried them on an iMac and iBook; both work. Tried different cables, three different drives [2 OCW, one Verbatim]. Nothing works. Wiggled cables. Used both bus and external power.
    HELP please. I don't want to spend another $350 [plus postage from UK via APO] to fix this a third time [was a refurb, used from PowerMax, they looked at logicboard once, and then I used Apple's fix it service]. The Apple repair warranty expired in Feb 09.
    I might try an $80 cardbus FW800/400 if I can find one still.
    Thanks in advance.

    Frustrating trying to get it to work .... You can zap the PRAM as well as reset the PMU anytime. At this point, if you haven't go ahead and do the PRAM and might as well do the PMU again. Reset PRAM. Note the effects are immediate, there's no advantage to waiting overnight:
    1. Shut down the computer.
    2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    3. Turn on the computer.
    4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    6. Release the keys.
    It sounds like you may have had hard drive issues that Drive Genius fixed for you. For comparison, did you run the Disk Utility disk repair after Drive Genius fixed the hard drive .. just to see if Disk Utility gives the drive a clean bill of health?
    When you ran the Apple hardware test, did you run the extended test? Do you have either of the TechTool programs available? They do similar testing to the Apple hardware test, it would be interesting to see if they also say the hardware is OK.
    You've reloaded the operating system a couple of times. Did you use the combo update to update to 10.4.11? I prefer that to letting Software Update make the updates, as sometimes it doesn't update correctly. Repair disk permissions before and after the update, too. Then run software update to pick up any other required updates.
    You've, by this time, reset PRAM and PMU, I assume the PRAM reset didn't change anything? If so, sorry, but I don't know what else you can do. At this point, I'd take it to a genius at the Apple store, and get their opinion.
    I didn't address sleep as I think you need to resolve the Firewire issue first, then see if there is a sleep problem.

  • Firewire issue--Backup drive not found w/Time Machine after imac sleeps

    I've had a lot of problems with Time Machine on my G4 imac since starting to use it a month ago. I think I have isolated the problem:
    Time Machine functions properly while the computer is in use, and it has no problem after a restart or shut down, but if the computer goes to sleep and then TM runs its hourly backup, I get an error that it cannot find the Backup Drive. Once this happens, TM will no longer work until I've deselected the drive in TM, unplugged it, plugged it in again, and reselected the drive as the backup Drive. Sometimes this requires a shut down or restart too.
    Here's what I've tried:
    1. connected the drive via USB--it operated without a problem
    2. unplugged all devices from the computer, shut down, waited, 20 mins, restrted, plugged the external drive back in via Firewire--the problem persists as described above.
    3. deleted the TimeMachine.plist file, restarted--problem persists.
    I've read that the Firewire port can be reset with other procedures such as zapping the PRAM or updating the firmware. I've also read that new problems can arise after reseting the PRAM so I'm hesitant to do this. Can anyone shed some light on the PRAM option?
    I cannot find where the firmware updates are located on the mac site. Could someone point me in the right direction? I've looked under downloads and after searching, came up with a long list, but nothing was labeled clearly. Each listing mentioned firmware in the header, but it seemed to always pertain to a certain issue (eg. superdrive, or installing appleworks). I could not tell what was the most recent firmware released for my machine, and I fear installing something retrograde that will create new problems.
    If anyone has any thoughts on how to deal with the firewire problem, or if you think my issue with using a FW connected drive with Time Machine might be rooted with something else, please comment.
    Thanks!
    HM
    Message was edited by: imaginary_forest

    fzgy wrote:
    "Mac OS X can't repair the disk.  You can still open or copy files on the disk, but you can't save changes to files on the disk.  Back up the disk and reformat it as soon as you can."
    It's possible a heavy-duty 3rd-party disk repair app can fix it, but they're expensive (DiskWarrior is about $100), and there's no guarantee it can do it.
    Am prompted to reformat but I don't have a good understanding of what this means and how to do it.
    That will erase it.  See Time Machine - Frequently Asked Question #5.
    It sounds very much like the disk is beginning to fail, although it's possible there's a bad port, cable, connection or power supply (if it has its own).
    I'd suggest getting a new one, and using it for your Time Machine backups; once you have a good backup there, reformat the old one (and select Security Options to write zeros to the whole drive -- if that fails, you know the drive is toast).  Use it for secondary backups, per FAQ #27.   If it has failed, get a second new one for secondary backups. 

  • Firewire Issues Caused By Apple Isight!

    For months, I've been having an intermittent Firewire audio problem, which I initially thought was A) Quad G5 or B) RME Fireface 800!
    Testing the RME on another Quad G5 resulted in no errors, though for piece of mind a replacement RME was given! Back home the same intermittent problems occurred, it had to be the Quad G5???
    Livid, this time I persisted on Google searching for FW issues, (a few hours later) to my amazement I came across an article on MacFixIt, that pointed the finger to Apple's own iSight FW camera, which I had connected!
    The transcript below explains how to resolve this problem, it worked for me!
    Mini-Tutorial: Dealing with FireWire problems (drives not mounting, devices unrecognized, etc.)
    As an Apple-invented technology, FireWire (IEEE 1394a and IEEE 1394b) should be (and usually is) one of the most solid and efficient means for interfacing with external peripherals. Indeed Apple's "i"-branded devices -- the iPod and iSight -- have, in large part, been made possible by the quick transfer rates, power sourcing, and hot pluggability offered by FireWire.
    Occasionally, however, conflicts between FireWire-connected devices arise and can result in a variety of issues including DV cameras dropping frames, FireWire drives not mounting, and erratic behavior from the iPod (disappearing from iTunes, etc.). In the midst of these issues, you might also experience "buffer underrun" errors when trying to burn CDs or DVDs with FireWire-connected recorders.
    The iSight is especially notorious for causing issues of this nature, and exhibiting symptoms.
    There exist a number of methods for dealing with FireWire device interference, a few of which are explored here.
    Switching Ports The first procedure you should try when experiencing a problem that you believe to be caused by device interference is to simply reconfigure the arrangement in which your FireWire peripherals are connected.
    Try switching each device to a different port, or temporarily disconnecting one or more of the devices. In particular, if you are a PowerMac G5 owner, trying switching devices from the front to back ports or vice versa.
    Adding an external hub In some cases, it appears that FireWire devices are not drawing enough power from the computer. This can cause a sundry of strange issues, including apparent conflicts between devices and unexpected power-offs during device operation. In these instances, adding an externally powered FireWire hub can clear things up.
    One of the reasons an "under-powered" situation can occur is that different Mac models have varying power capacities available through their FireWire ports.
    PowerBooks and iBooks have the least, generating around 7 watts. The iMac G5 also generates a relatively low amount of FireWire power, sharing 8 watts between its two FireWire 400 ports.
    The Power Mac G5 shares 15 watts between its one FireWire 800 port and two FireWire 400 ports.
    Place devices on different FireWire busses/Isolate the iSight Similar to the above procedure, adding another FireWire bridge -- via an extra PCI-based FireWire adapter or another means -- can eliminate conflicts from devices that reside on the same bridge.
    Power cycling the system Simply cycling the power on your system may be enough to temporarily eliminate a few FireWire conflict issues.
    Shut down your Mac, and disconnect all FireWire devices as well as the computer's power cord. Leave the system off for about 10 minutes, then plug it back in. First turn your Mac back on, then re-attach the FireWire devices one at a time and check for the conflict to resurface.
    Disconnect the iSight As noted above, the most common cause of interference is Apple's own iSight. In case after case, simply disconnecting this single device has eliminated problems with other FireWire devices.
    Disconnecting the iSight has proved particularly successful for an issue where the iPod disappears from the Desktop and from the iTunes playlist, while the iPod status screen cycles from the Apple logo to a "Do not Disconnect" message over and over.
    The exact reasons why the iSight causes more than its fair share conflicts with other FireWire devices are many, and sometimes unclear. One potential source of conflict, however, could be the unit's high bandwidth usage.
    The iSight captures video at a 640 x 480 pixel resolution, at 30 frames per second in millions of colors. Such throughput uses a significant chunk of the standard FireWire port's 400 Mbps bandwidth. As such, when other devices are connected, the bandwidth requirements for satisfactory performance may not be met.
    Apply the latest updates Make sure that your FireWire drives are using the latest firmware (check the manufacturers' Web site) and the most recent iPod update has also been applied.
    Of higher importance, if you have an iSight, is the iSight 1.0.2 updater. In a large number of cases it has resolved conflicts caused by the camera.
    Re-apply the most recent Mac OS X combo updater In some cases, re-applying the most recent combo updater can resurrect seemingly defunct FireWire ports and allow devices -- drives included -- to be recognized again.
    The most recent combo updater is available from Apple's download page.
    Clear caches Try using a tool like Tiger Cache Cleaner or Cocktail to remove potentially corrupt system caches. Restart, then check if your FireWire devices are recognized.
    Ps. There was no iSight connected when testing the RME on another Quad!
    Power Mac G5 Quad 2.5 GHz   Mac OS X (10.4.4)   2x 2.5 GB HD, 2.5 GB RAM, iSight, iPod, RME Fireface 800 Audio Interface

    TA

  • Firewire issues with DV camera

    When connecting a Samsung VP-D305i mini DV camera to the firewire port (4pin to 6pin cable) Mac OS fails to recognise it.
    I know this is an issue that has been covered in this forum a few times, but none of the answers seem to work for me. Furthermore rather than get the "unable to list firewire devices" in system profiler, system profiler displays it as unknown device. The following is given as the detail:
    Manufacturer: 0xF0
    Model: Unknown
    GUID: 0xF000084139E5
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Sub-units:
    Unknown Unit:
    Unit Software Version: 0x10001
    Unit Spec ID: 0xA02D
    Final Cut Pro and iMovie both fail to work with the device, however they do recognise that a camera has been plugged in. My MacBook Pro has the Texas Instruments Firewire chipset, is this not supposed to be the more reliable chipset?
    Flushing the SRAM doesn't work, I've formatted reinstalled Mac OS X, didn't work. The DV camera works fine through the same cable on my sister's MacBook. Furthermore, the DV port works 100% fine when booting my MacBook Pro, using Bootcamp, in XP. This port did work, I've used it before with iMovie in November last year. (with Bootcamp and Windows installed). Does anyone else know anything that may help?

    Is the sound mixer physically connected to the mac via firewire? Maybe just unplugging it will help; there is only one firewire bus, and sometimes the capturing you are trying to capture from needs to be the only device connected.

  • Firewire issues after upgrading to 10.6

    I mentioned this is a prior post, and have really still not got a resolution to it. I have a 1st. gen Mac Pro 2 x 2.66 dual core. I have encountered several disturbing issues using Firewire 400/800 devices on my machine after the upgrade. When I boot into 10.5, I have all the access and performance of my Firewire devices (a LaCie 1 TB external drive, A Sony CD/DVD burner, and a WD Passport FW 800/USB) All devices work in both USB and Firewire natively... but only work properly under 10.6 when using USB. All firewire access on my machine is sketchy at best under 10.6. The devices show up.. and mount.. but when I attempt to use/I.O to them.. the speed moves in bursts.
    For example.. copying a folder that is 5GB to one of the FW 800 HDs takes about 2-4 minutes on 10.5... and under 10.6 it bursts. When under 10.6, I get fast transfers for about 200-300 mb, then about a 5-10 minute pause.... then another burst of normal performance for 200 Mb. Then another pause. Taking an estimated 3-4 hours to copy a 5GB folder.
    In a test... I switched to the USB interfaces of these devices, and the transfers are fast as expected. (2-4 minutes, no pauses) Furthering the test.. the FW interfaces perform as expected under 10.5.
    Anyone else experiencing this? (I have tried resetting PRAM, and total shutdown etc.)
    Any assistance would be most welcome.
    Thanks!

    I have had Firewire problems since moving to 10.6. Some optical drives in an enclosure containing the Oxford 934 chip will not mount disks unless I pull the Firewire cable and reinsert it. They work fine using USB 2.0. The problem is a result of Apple's update of the Firewire drivers. The problem extension is
    IOFirewireSerialBusPRotocolTransport.kext
    Replacing this extension with the one from 10.5 causes everything to work properly. If you do choose to replace this extension, you may wish to replace all five with those from 10.5. Additionally, after making the exchange, repair permissions and restart so as to make sure the replacement extensions are properly recognized. You must repair permissions BEFORE restarting. If you restart and then repair permissions, the replacement extensions may not get recognized, even after a subsequent restart, and you will have to repeat the procedure.
    During permission repair, I received alerts that one or more of these extensions could not be used. I ignored the alert with apparently no adverse consequences.
    My Firewire only hard drives, and one Firewire/USB 2.0 hard drive seem to have no problem.
    K

  • IMac firewire issues...

    Hi all
    I'm wondering, after having recent problems with using a Metric Halo Mobile I/O and a USB hard drive at the same time (massive latency issues, crackles, etc. in Logic Pro 7), if anybody has any more information on it.
    I read that there is only Firewire bus on the iMac that I have and that is the problem - is there any way around this or is my second Firewire socket just a waste of time when the Mobile I/O is connected?
    Any thoughts welcome! Or, of course, feel free to point me in the direction of any previous discussions I've missed.
    Thanks.
    Steve

    Most (all?) Macs have only a single Firewire bus, but that doesn't stop me, or others, from using a FW audio interface and a FW hardrive together.
    Your post says you were using a USB hard drive, that's totally different from Firewire.

  • Solaris 10 x86 Install - Firewire Issue

    Greetings,
    I am installing Solaris 10 x86 (03/05) and am running into a lot of trouble with the firewire drivers.
    The first CD installs properly, but any subsequent reboot (to install other CDs or boot the OS) fails. By watching the boot messages on a boot -v, I discovered that the system hangs after loading the firewire drivers.
    If I run the hardware configuration assistant during boot and remove both 1394 devices, I am allowed to boot - but only that once. Even if I save the hardware configuration and tell the hardware configuration tool to use it during the next boot (by pressing Esc and loading the profile), it automatically re-adds my 1394 devices and hangs. The only way I can successfully boot is by going into the hardware configuration assistant each time and removing the 1394 devices, each time. Removing the 1394 card is not an option, as this system boots other OSes for computer forensics via removable disk racks and the firewire is needed for these purposes.
    So, my question is this - how can I tell Solaris to ignore the 1394 devices without manually removing them during each boot? And how can I get the hardware configuration assistant (the one that I launch by pressing Esc during the boot process) to actually use the configurations I've saved?
    Thanks in advance.

    I'm not sure what the root cause for the firewire driver hang is.
    Maybe an issue with interrupt routing. You may want to experiment
    with BIOS ACPI / IOAPIC / PnP OS settings, and/or the
    acpi-user-options property.
    Anyway, to get rid of the firewire driver, you can probably add an
    "exclude: hci1394" line to /etc/system and reboot.

  • Firewire issue after installing Lion

    I use a Western Digital Studio II as my Time Machine back-up drive on my Macbook Pro. I've always had this device connected via the Firewire 400 port and it has worked flawlessly for the 2 years or so that I've had it.
    Just upgraded to Lion. Now, the WD drive doesn't mount. No sign of it.
    I know the drive's OK because if I connect via USB, all is well (but of course, it's slow).
    I've checked WD's support site in case there's a driver update but there's nothing newer than what I already have.
    Research via Google reveals a number of alleged issues with firewire drivers for other devices but I can't help wondering is there's an inherent flaw in the way Lion is handling all firewire devices.
    Any thoughts? Anyone?

    You called Apple Care. So I assume you have a machine that's in warranty. Either that, or you paid for this useless piece of information.
    So here's an interesting point...
    I have purchased Lion. But I get NO support for it. NO warranty. I will argue that the age of my machine (or the existence of an Apple Care contract) is irrelevant. I have purchased a product and I want support / warranty for that product - nothing else.
    If I buy a new refrigerator, I get a warranty for that. It's got nothing to do with any support contract I have on the house that I'm going to install it in.
    Why should a piece of software such as Lion be immune from implied fitness for purpose? That's probably a rhetorical question.
    So here's what I've done (only applies in the UK).
    I have written to Apple and have told them that OS X Lion is not "fit for purpose" in the context of the Sale of Goods Act 1979 and have also told them I exercise my Statutory Rights in English Law and have demanded a full refund.
    I strongly recommend that others take the same stance. It may only be for the sake of £21 and a LOT of wasted time but I'm going to stand firm on this and I WILL take legal action if necessary.

  • Can someone help my with my firewire issues?

    After searching on the web for a while I've discovered that leopard and firewire are having issues working with each other.
    I own a Macbook Pro 10.5.6
    I'm having issues running my mac when I have more than 1 firewire device connected to it. I do a lot of video editing and capture all my video footage with Final Cut Pro via FW400. I have a GRaid 1Tb external HDD that is connected via FW800. Never had problems with any of this before but upgraded to Leopard last week and then this issue hit.
    •If I have my HDD connected but not my camera, the HDD works fine. However my MAC won't recognize my camera if I hook it up.
    •If I have my camera connected but not my HDD the camera will connect just fine. However when I try to hook up my HDD it will not be recognized by my mac.
    •If I have neither of them connected and connect them both, my MBPro will recognize whichever device gets hooked up first but will not recognize the second. If I leave them both connected any try to shut down my MAC- it will not shut down. As soon as I disconnect 1 of them, my MAC will shut down just fine.
    •If I hook up both devices before my MAC is turned on and then try to boot it up. I will get to the blue screen and it will boot no further. If 1 of the devices is then turned off, the MAC will continue to boot just fine.
    I've tried resetting the PRAM by doing the <option> <command> <r> but it had no effect. Not sure I'm doing it propperly. I hold down <option> <command>
    <r> and wait until I hear 3 chimes. Anyway, it hasn't fixed anything.
    Also, I read something about resetting some of the firmware by holding down <option> <command> <o> <f> after the start up chimes and then typing in
    reset-nvram
    set-defaults
    reset-all
    However, whenever I try to do this- I hold down <option> <command> <o> <f> but nothing happens. I never get to any kind of command prompt.
    Anyone have any other ideas? Any help is greatly appreciated!!
    Thanks!

    Thank you all for your replies. I'm trying them all but nothing is working.
    I do have a couple of new pieces of information. I figured out that the reason nothing was showing in my System Profiler was because I had both the HDD and the Camera connected if I disconnected one or the other, the remaining device will show in my firewire tree.
    Here is a listing of some things. Maybe this will help you all.
    Again, thank you for all your suggestions!
    //If I only attach my camera (FireWire400) and not my external HDD (firewire 800) I get this in my firewire tree//
    FireWireBus
    ZR60
    FireWire Bus:
    Maximum Speed: Up to 800 Mb/sec
    //Which is weird to me because it's only a FW400 port and cable//
    ZR60:
    Manufacturer: Canon
    Model: 0x0
    GUID: 0x850000ACED38
    Maximum Speed: Up to 100 Mb/sec
    Connection Speed: Up to 100 Mb/sec
    Sub-units:
    ZR60 Unit:
    Unit Software Version: 0x10001
    Unit Spec ID: 0xA02D
    ZR60:
    Manufacturer: Canon
    Model: 0x0
    GUID: 0x850000ACED38
    Maximum Speed: Up to 100 Mb/sec
    Connection Speed: Up to 100 Mb/sec
    Sub-units:
    ZR60 Unit:
    Unit Software Version: 0x10001
    Unit Spec ID: 0xA02D
    (If I only attach my external HDD FW800 and do not attach my camera I get this in my firewire tree)
    FireWire Bus
    G-Raid Device 00
    FireWire Bus:
    Maximum Speed: Up to 800 Mb/sec
    G-RAID Device 00:
    Manufacturer: G-TECH
    Model: 0x0
    GUID: 0x1D27CE0010ABB
    Maximum Speed: Up to 800 Mb/sec
    Connection Speed: Up to 800 Mb/sec
    Sub-units:
    G-RAID Device 00 Unit:
    Unit Software Version: 0x10483
    Unit Spec ID: 0x609E
    Firmware Revision: 0x9102
    Product Revision Level: GM4O
    Sub-units:
    G-RAID Device 00 SBP-LUN:
    Capacity: 931.52 GB
    Removable Media: Yes
    BSD Name: disk1
    Mac OS 9 Drivers: No
    Partition Map Type: APM (Apple Partition Map)
    S.M.A.R.T. status: Not Supported
    Volumes:
    GRaid2:
    Capacity: 931.4 GB
    Available: 663.31 GB
    Writable: Yes
    File System: HFS+
    BSD Name: disk1s3
    Mount Point: /Volumes/GRaid2
    (I thought I would attach this information as well maybe it will be useful, I don't really know what to look for here so I though I would just send as much info as possible.)
    Battery Information:
    Model Information:
    Serial Number: Sony-ASMB012-377b-7650
    Manufacturer: Sony
    Device name: ASMB012
    Pack Lot Code: 0001
    PCB Lot Code: 0000
    Firmware Version: 0110
    Hardware Revision: 0500
    Cell Revision: 0303
    Charge Information:
    Charge remaining (mAh): 4693
    Fully charged: Yes
    Charging: No
    Full charge capacity (mAh): 4772
    Health Information:
    Cycle count: 132
    Condition: Good
    Battery Installed: Yes
    Amperage (mA): 0
    Voltage (mV): 12461
    System Power Settings:
    AC Power:
    System Sleep Timer (Minutes): 0
    Disk Sleep Timer (Minutes): 0
    Display Sleep Timer (Minutes): 0
    Automatic Restart On Power Loss: No
    Wake On AC Change: No
    Wake On Clamshell Open: Yes
    Wake On LAN: Yes
    Display Sleep Uses Dim: No
    Battery Power:
    System Sleep Timer (Minutes): 180
    Disk Sleep Timer (Minutes): 180
    Display Sleep Timer (Minutes): 180
    Wake On AC Change: No
    Wake On Clamshell Open: Yes
    Display Sleep Uses Dim: Yes
    Reduce Brightness: No
    Hardware Configuration:
    UPS Installed: No
    AC Charger Information:
    Connected: Yes
    Charging: No
    USB Bus
    apple internal keyboard / trackpad
    USB Bus
    Bluetooth USB Host Controller
    USB Bus
    IR Receiver
    USB BUS
    USB High Speed Bus
    Built-in-iSight
    USB Bus:
    Host Controller Location: Built In USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x27c8
    PCI Revision ID: 0x0002
    PCI Vendor ID: 0x8086
    Bus Number: 0x1d
    Apple Internal Keyboard / Trackpad:
    Product ID: 0x021a
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 0.18
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Computer
    Location ID: 0x1d200000
    Current Available (mA): 500
    Current Required (mA): 40
    Apple Internal Keyboard / Trackpad:
    Product ID: 0x021a
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 0.18
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Computer
    Location ID: 0x1d200000
    Current Available (mA): 500
    Current Required (mA): 40
    USB Bus:
    Host Controller Location: Built In USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x27cb
    PCI Revision ID: 0x0002
    PCI Vendor ID: 0x8086
    Bus Number: 0x7d
    Bluetooth USB Host Controller:
    Product ID: 0x8205
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 19.65
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Inc.
    Location ID: 0x7d100000
    Current Available (mA): 500
    Current Required (mA): 0
    Bluetooth USB Host Controller:
    Product ID: 0x8205
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 19.65
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Inc.
    Location ID: 0x7d100000
    Current Available (mA): 500
    Current Required (mA): 0
    USB Bus:
    Host Controller Location: Built In USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x27ca
    PCI Revision ID: 0x0002
    PCI Vendor ID: 0x8086
    Bus Number: 0x5d
    IR Receiver:
    Product ID: 0x8240
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 1.10
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Computer, Inc.
    Location ID: 0x5d200000
    Current Available (mA): 500
    Current Required (mA): 100
    IR Receiver:
    Product ID: 0x8240
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 1.10
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Computer, Inc.
    Location ID: 0x5d200000
    Current Available (mA): 500
    Current Required (mA): 100
    USB Bus:
    Host Controller Location: Built In USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x27c9
    PCI Revision ID: 0x0002
    PCI Vendor ID: 0x8086
    Bus Number: 0x3d
    USB High-Speed Bus:
    Host Controller Location: Built In USB
    Host Controller Driver: AppleUSBEHCI
    PCI Device ID: 0x27cc
    PCI Revision ID: 0x0002
    PCI Vendor ID: 0x8086
    Bus Number: 0xfd
    Built-in iSight:
    Product ID: 0x8501
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 1.84
    Speed: Up to 480 Mb/sec
    Manufacturer: Micron
    Location ID: 0xfd400000
    Current Available (mA): 500
    Current Required (mA): 100
    Built-in iSight:
    Product ID: 0x8501
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 1.84
    Speed: Up to 480 Mb/sec
    Manufacturer: Micron
    Location ID: 0xfd400000
    Current Available (mA): 500
    Current Required (mA): 100
    //As a final note I opened up my system profiler and tired to fine any FireWire info. I narrowed the listings by using the search filter for fire*. Here's what it returned.//
    12/22/08 12:43:43 PM SystemStarter[16] /Library/StartupItems/M-Audio FireWire Audio Helper
    12/22/08 12:46:24 PM kernel Loading security extension com.apple.nke.applicationfirewall
    12/22/08 12:46:28 PM kernel FireWire (OHCI) TI ID 8025 built-in now active, GUID 0019e3fffe9a6930; max speed s800.
    12/22/08 12:52:36 PM kernel FireWire (OHCI) TI ID 8025 built-in: 1039 bus resets in last 3 minute.
    12/22/08 9:34:42 PM kernel FireWire (OHCI) TI ID 8025 built-in: 150 bus resets in last 3 minute.
    12/23/08 9:02:52 AM SystemStarter[15] /Library/StartupItems/M-Audio FireWire Audio Helper
    12/23/08 9:37:37 AM kernel Loading security extension com.apple.nke.applicationfirewall
    12/23/08 9:37:37 AM kernel FireWire (OHCI) TI ID 8025 built-in now active, GUID 0019e3fffe9a6930; max speed s800.
    12/23/08 9:41:41 AM kernel FireWire (OHCI) TI ID 8025 built-in: 466 bus resets in last 3 minute.
    12/23/08 9:44:53 AM kernel FireWire (OHCI) TI ID 8025 built-in: 2538 bus resets in last 3 minute.

  • Windows 7 Firewire Issues with CS5 and ADVC-700

    I've got a Windows 7, 64 bit system with CS 5. In dubbing out for playback, I route a firewire cable from the PC to an Canopus/Grass Valley ADVC-700. Both units are less than a year old and are having issues with "black outs" during the dub out process. I've read different things about Windows 7 having issues with firewire drivers. After speaking to someone with Adobe, I've changed my firewire driver to Legacy. That hasn't helped.
    The ADVC-700 has s-video out running to preview monitor and BNC out/XLR audio running to my playback system for ingest. When the video goes to black (usually for a 1/2 second), the audio drops out with it.
    I've reset the settings on the ADVC-700 with no luck.
    Any suggestions on a fix or something else to try?

    I did test with a JVC GY-HD200U and there weren't any performance issues which led me back to the PC or other on the PC.
    The system is running Windows 7, 64 bit with CS5 Production Premium following an upgrade from the CS4 version.
    I've got 12 GB of Ram, (2) Intel Xeon Quad Core E5560 -2.8 GHZ processoCrs.
    (1) 500GB SATA2 hard drive, 7200 RPM, 32 MC (System Drive)
    (3) 1 TB SATA2 Hard drives, 7200 RPM, 32 MC (3 TB, RAID0 Storage Drive)
    Nvidia GeForce 9800GT graphics Card
    Supermicro X8DAi motherboard, Intel 5520 Chipset, 2-PCIe X16, 1 PCIe x4, 3-PCI, 10-USB2 ports, 2-pro/1000 NIC, 8-channel HD audio, 6 SATA ports, RAID 0/1/5/10
    I've got the legacy drivers for the firewire card. I've checked to make sure all of the power save options are off along with all screen saver options. I've cleaned my Adobe Cache out, deleted my Adobe Preferences, went from the 4pin/6pin cable to a 6pin/6pin cable to feed the ADVC-700 from the PC, reset the ADVC 700 back to factory specs...all of this with no luck.
    The problem seems to be worse since the move from CS4 to CS5 but it's hard to tell.
    I've also hooked up an older ADVC-500 unit with the same output results.
    I think I noted in the first post that this is happening on two indentical systems with the same cabling and programs and the same ADVC-700 boxes.
    I've been told by Adobe to clean my C; drive and reload the OS and Adobe CS5 as I should have done that when I upgraded instead of just upgrading the system from CS4 to CS5 using the discs. I haven't done this yet as I have to budget time/workflow to accomodate.

  • Firewire issues? Is there a proper way to remove a firewire from the port?

    Hello,
    I am trying to "Log and Capture" and also "Print to Video."
    My PowerMac G5 cannot "initiate" my camera, even though it has been without much problem.
    I regularly have to plug and unplug my firewire though. I thought maybe this might be the issue.
    Can unplugging a Firewire regularly and back again cause the computer to not be able to see it? Perhaps it gets "stripped" or something?
    Thanks!

    Well, I can connect another firewire to the port for an external drive and it's working fine. So it does work with some other hardware devices.
    But when I plug in the firewire that comes with the video camera, it will not show in Final Cut Pro (nor I-Movie either). I also tried a spare firewire for the video camera. Neither worked.
    When I look at the camera, the "DV in iLink" appears on my lcd screen, so I believe it must be on the computer's side that the Firewire isn't connecting right.
    I do however believe my Mac can see the Firewire though, even if Final Cut Pro can't. I believe that because when I click on "About this Mac" and then "More Info," then scroll down to Firewire, I see this:
    HDR-HC3:
    Manufacturer: Sony
    Model: 0x38013E
    GUID: 0x800460104D5E1BE
    Maximum Speed: Up to 100 Mb/sec
    Connection Speed: Up to 100 Mb/sec
    Sub-units:
    DV-VCR Unit:
    Unit Software Version: 0x10001
    Unit Spec ID: 0xA02D
    This means it's working fine right? So maybe this is a Final Cut Pro settings issue?

  • FireWire issues with external drive in Yosemite

    I have just upgraded to OS X Yosemite, and I have an annoying problem with my 500GB FireWire external drive (which I use for Time Machine backups).
    Basically, after updating the drive won't show up anymore, neither in the Finder nor in the Disk Utility. I also tried the "diskutil list" command in the Terminal, but it is nowhere to be found. Note that the drive does indeed receive power from the port - it spins - and when I look into System Report --> Hardware --> FireWire it does show up there (but I can't mount it). Furthermore, if I use a USB cable to connect the drive everything works fine, so the disk itself seems to be OK.
    The funny thing is that if I boot with the drive plugged in the FireWire port the system mounts it normally. But as soon as I eject the drive, I am unable to mount it again (unless I switch to the USB cable, as mentioned above).
    Prior to the update, everything worked flawlessly. For now, I backed up my Mac via USB 2.0, but it's very slow and I definitely don't want to resort to this workaround everytime. And it goes without saying that I don't like having issues with my primary backup device in general.
    I already did all the usual troubleshooting (rebooting, resetting NVRAM and SMC, ...), but the problem still persists.
    Any suggestion?

    I had the same issue on a rMBP 13'', brand new 2015 March.
    Two thunderbolt adapter connected: one for ethernet, one for firewire Lacie drive.
    and...
    even after taking the ext. Firewire on the Spotlight exclude list, and also after disabling sleeping hard drives, I always got the issue.
    Until I realized that touching the laptop or moving the screen was immediately leading to disconnection.
    Then I exchanged the thunderbolt connectors, and now it is stable and does not disconnect again.
    ??? Maybe one of the ports is more "delicate" than the other?
    Big hardware weakness here...

Maybe you are looking for