Firewire problems with MP

Hi
My new 2008 MacPro is doing ok for me at the minute the pnly problem I have had is a Firewire 400 problem.
I had a sound cut out and a hardrive not being recognised by the port already. Then today after connecting my Canon HDV to the front 400 port and successfully importing footage the sound dropped out whilst still importing, the footage also freezed on screen at the sametime.
Any thoughts what this could be? Is there known issues using more than one FW at a time on these machines?
Thanks

Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that didn't work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try.
If that still didn't get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good! Also, here is Apple doc.#88338 on getting FireWire to work.
Here's another
Fw Faq.
DALE

Similar Messages

  • 10.4.7 update  and external firewire problems with HD corrupion

    Dear all,
    Advised by Jpfresno I started this new topic about Tiger 10.4.7 update.
    I will repeat my post and what was happening 2 weeks ago:
    “In 5 years 10.4.7 update was a tragedy for my Powerbook Ti 667. When I update from 10.4.6 to 10.4.7 my 300 GB firewire drive gets corrupted, after repairing it with DiskWarrior and after connecting it to my PowerBook my computer freezes and I must shut it down via powerbutton. Safari also crashes after the update.
    I just erase my Hard Drive and after that install 10.4 and update with combo to 10.4.7. But I had the same problems: finder freezes with connected firewire devices and also safari when browsing. I spend a week trying to solve the problem but no luck.
    Yesterday and with no firewire devices, 10.4.7 freeze and I have big trouble in order to started my powerbook!!! Even when i insert the 10.4 install DVD it did not detected my HD. Finally I get it to work and install 10.4 and combo update to 10.4.6 and everything works. My external firewire drive and safari. I already diagnose my HD with disk utility, TechTool and directories with Diskwarrior and everything is ok.
    I clone my 10.4.6 to firewire, boot from it and everything is working. I let my external drive connected and finder does not freeze.
    My conclusion is that the problem is 10.4.7 update. It only give me problems and I was getting crazy with it. 10.4.6 is working good and I do not advice anyone to update to 10.4.7.”
    Last week after reinstalling 10.4.6 I started to have HD problems with my Powerbook 667. I did a surface scan with TechTool I it reported bad sector. Then I done a zero disk format but after a second surface scan TechTool also reported bad sector. Then I take the decision to replace my internal HD. I bought a Samsung 40GB Hard Drive and installed it on my PowerBook. Then I have done a clean installation of 10.4.6 with all applications that I need and clone it to my hard drive with Intego Personal Backup software. Everything works on 10.4.6. and external firewire drive.
    After that everything is ok. But I decided to test if my problem derivates from 10.4.7 update or from previous HD corruption. Then I install 10.4.7 update on my Internal Hard Drive. Everything is working good but after connecting my external Hard Drive the finder started to freeze!!!!!!!!!. After that I tried cloning HD to external firewire with Intego personal Backup. Everything was working good but when it was finishing the backup process started to give errors!! I started panic. I interrupted the backup process but after and after restart I found something strange with 10.4.7. The system started up, I login but I could not started any application!!!??? All my application died!
    Then I have done one more clean installation of tiger and 10.4.6 update.
    My conclusions are that the 10.4.7 update causes all the problems that I have on my PowerBook, because I used the same methods and same software/hardware on 10.4.6 and did no have any problem.
    This last two weeks were very difficult to me. I tough that these problems do not happen with Apple computers but I was wrong!!! It is very hard to me to deal with it. I always said to my friends that I never had problems with Apple computers. I accept that a hard drive died because the use of it but I can not accept that a system update cause me 2 weeks of hard problems and make me loose precious work information! I always love apple computers and Apple OS but now I am disappointed
    If anyone can explain what happen or have a solution for those problems?
    Thanks for the comprehension and collaboration.
    Best Regards
      Mac OS X (10.4.6)  

    Hi, alsvieira.
    There are some things you did not check in all of your troubleshooting:
    1. Run the Apple Hardware Test (AHT) that came the affected computer. See my "Apple Hardware Test" FAQ for comprehensive advice on using the AHT in troubleshooting.
    2. re: FireWire troubleshooting: Here is some general troubleshooting advice that may help if problems return with your FireWire drive:1. Review the AppleCare Knowledge Base document "What to do if your computer won't recognize a FireWire device".
    2. If this problem occurred after installing a recent Mac OS X Update, and you are also unable to mount CDs, DVDs, or disk images perform the steps in this Mac OS X Hints article. This worked under Panther and may also work in certain situations under Tiger.
    3. Power-on the FireWire drive before starting up (booting) your Mac.
    4. Reset PRAM and NVRAM.
    5. Resett the power-management chip in your Mac.
    6. Try a different FireWire port. James Wiebe, CEO of WiebeTech, has published FireWire Port Failures in Host Computers and Peripheral Devices, a white paper providing backgroud information and technical analysis concerning the causes of failure for FireWire ports. This may provide additional diagnostic information.
    7. Micromat TechTool Pro version 4 can test the FireWire bus in your computer: this tests the bus — not the ports — but if the problem is on the FireWire bus on the logic board, it should reveal it.
    8. Check with the manufacturer of your FireWire drive or enclosure to see if any firware updates are available for such.
    9. Hopefully, the partition map on the FireWire drive is not damaged. This can happen if the FireWire drive was not Ejected before being disconnected or powered off. If it still refuses to mount, you may need to employ data recovery tools or services: see my "Data Recovery" FAQ.Note that some of the information above is from the "FireWire Problems" chapter of my book, Troubleshooting Mac® OS X.
    Dr. Smoke
    Author: Troubleshooting Mac® OS X
    Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
    I may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • Audio/Firewire Problems with Mini, Please Help!

    I just bought a brand new Mini from Amazon.com and am having some problems. First, when I plug computer speakers into the mini, the sound continues to come from the internal speaker and the mini ignores the speakers. In System Preferences, it doesn't even recognize that something is plugged into the machine.
    Second, the Mini does not recognize my external, Firewire iSight camera. In System Profiler, it does not show anything connected to the port when the camera is connected.
    The Mini is the latest rev running 10.4.11. Leopard upgrade disks should be in the mail soon.
    Any ideas as to what is wrong? Should I just return to Amazon for a replacement? Thanks for your help!

    Having just posted in a similar situation, pardon the cut and paste, but these are the first two (and easiest) things to try:
    First reset parameter RAM - it's an area of non-volatile memory used for system settings and hardware configuration. It it gets corrupted, it can cause odd problems.
    Reset PRAM
    -Shut down the computer.
    -Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in the next step but one.
    -Turn on the computer.
    -Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    -Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    -Release the keys.
    Next, perform an SMC reset. The SMC is the device which controls system hardware and devices, so if there is a problem with hardware components not functioning, it could be that.
    To reset the SMC on an Intel mini:
    -From the Apple menu, choose Shut Down (or if the computer is not responding, hold the power button until it turns off).
    -Unplug all cables from the computer, including the power cord and any display cables.
    -Wait at least 15 seconds.
    -Plug the power cord back in, making sure the power button is not being pressed at the time.
    -Then reconnect your keyboard and mouse to the computer.
    -Press the power button on the back to start up your computer.

  • Firewire problems with audio interface

    Hi, I have a problem with the firewire connection of my Power Mac G4: I have a Tascam FW-1884 audio interface and when I turn it on, the firewire led (that should be always turned on for the correct working of the machine) after a pair of seconds turns off and doesn't work at all..
    Here's what my system console says if helps..
    ===== Thu Jan 12 2006 ===== 09:44:12 Europe/Rome =====
    Jan 12 09:44:20 localhost kernel: TASCAM FW1884 Audio Device: init (1 of 1)
    Jan 12 09:44:20 localhost kernel: TASCAM FW1884 Audio Device: start 1.2.1 (instances 1)
    Jan 12 09:44:21 localhost kernel: TASCAM FW1884 Audio Device: message 0xE00087D2 for 0x12060000
    Jan 12 09:44:23 localhost kernel: TASCAM FW1884 Audio Device: HandleWatchdogTimer: prefs daemon relaunched
    Jan 12 09:44:24 localhost kernel: TASCAM FW1884 Audio Device: newUserClient
    Jan 12 09:44:24 localhost kernel: TASCAM User Client: start
    Jan 12 09:44:24 localhost kernel: TASCAM User Client: clientMemoryForType
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: High speed bus detected
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FinishStartup: FW884MacXDevice (216812)
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: Driver Register Version 0x00000014
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884REGISTERVERSION 0x00000014
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884FPGAVERSION 0x00010031
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884ARMVERSION 0x000100B7
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884HARDWAREVERSION 0x00030000
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884HARDWARESERIAL 0x00000000
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884GUIDMSB 0x00022EFF
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884GUIDLSB 0xFE800000
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mRegBaseAddress 0x00000000
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mNodeNum 0x00000000
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mGenerationNumber 0x0000000E
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mlocalNodeNum 0x00000001
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mMIDIReceiveHi 0x00000002
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mMIDIReceiveLo 0x00000000
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: initHardware
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: createAudioEngine
    Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: init (1)
    Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: start (3)
    Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: initHardware (3)
    Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: performFormatChange
    Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: performFormatChange
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOCHANNEL 0x00000001
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOSPEED 0x00000002
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: New PLAYBACK_ISOCHANNEL 0x00000002
    Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: DoStartAudioTransfers w/resync
    Jan 12 09:44:30 localhost kernel: TASCAM FW1884 Audio Device: Input stream stopped (B)
    Jan 12 09:44:30 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:30 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000200
    Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: * Failed ReadRegisterLong 0xE00002D6
    Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000200
    Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOCHANNEL 0x00000000
    Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000204
    Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: * Failed ReadRegisterLong 0xE00002D6
    Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000204
    Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOSPEED 0x00000000
    Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000020C
    Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: * Failed ReadRegisterLong 0xE00002D6
    Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000020C
    Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: New PLAYBACK_ISOCHANNEL 0x00000000
    Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000022C
    Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000214
    Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000218
    Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000021C
    Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
    Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000228
    I've tried running the same interface on my i-book (with the same drivers installed on the powermac) and all was good..
    Anyone can help me?
    Thanks =)
    power mac G4 quicksilver 800Mhz   Mac OS X (10.3.9)   i-book G4 1,25Ghz
    power mac G4 quicksilver 800Mhz   Mac OS X (10.3.9)   i-book G4 1,25Ghz
    power mac G4 quicksilver 800Mhz   Mac OS X (10.3.9)   i-book G4 1,25Ghz
    power mac G4 quicksilver 800Mhz   Mac OS X (10.3.9)   i-book G4 1,25Ghz
    power mac G4 quicksilver 800Mhz   Mac OS X (10.3.9)   i-book G4 1,25Ghz

    On both computers I have only one account, the fw cable is always the same..
    I have purchased a new cable and I'm testing it..
    Another thing to say is that the fw port number 2 is generally working better than 1.. I mean, while port 1 never loads my tascam (the computer firewire connection is always loaded succesfully on both ports) port 2 sometimes works.. well this can't be called stability at all =)
    Sometimes reastarting computer, unplugging cables etc can help starting succesfully a new session.. I've already resetted PMU but no progress..
    All these things don't last longer than one session..

  • Harddisk & Airport conection USB/Firewire  - problem with connetion

    So I bought the Airport Express and wanted to connect my Lacie Firewire HD with it. But since it is a FireWire - I guess I need a converter to go from firewire to USB2.
    Is that possible? ..and where can I get a converter?

    There is no such thing as a USB to FireWire converter. You will need a hard drive with a USB connection.

  • Firewire Problems with Final Cut Studio 2

    I recently made the leap and purchased a Macbook Pro and FCS2. But I have not been able to capture in Final Cut 6 from my Canon XL2. The capture window tells it is not reading timecode. Now if i use iMovie I can capture just fine, but Final Cut just won't read from the camera. I also purchased an Edirol FA-66 for some ADR and foley work on a project I have, but Soundtrack Pro won't read from it either and just like the Final Cut/iMovie scenario the interface can used thru Garageband with no problem other that latency delays.
    Is there some firewire menu in System Setting or something else I am missing? I have used both pieces of gear of G5 setups witht he previous version of FCP with no problem but I am totally lost with the new MacBook Pro and FCS 2...
    Please, help me.
    MacBook Pro 2.33 Ghz Intel Core Duo 2   Mac OS X (10.4.10)   2 gig ram, FCP Studio 2, XL2 and Edirol FA-66

    With the Cannon have you tried the obvious and used the Firewire Basic setup? I assume that FCP6 still uses that .. and are you plugging the Cannon directly into the book's FW port .. not daisy chaining .. that's an issue with Cannons I believe

  • FireWire problems with Lion?

    Relating to a previous post of mine "Disable Firewire Chip?" which is now archived, I would like to know if anyone has also experienced a perpetual spinning wheel problem after upgrading to OS X Lion, or maybe the notorious blue screen startup. After a proper SMC reset, my upgrade installation did eventually succeed and deleting all the new FireWire kexts again resolved my startup problems. It just seems strange that all the FireWire kexts contained within the Snow Leopard upgrades from 10.6.4 onwards worked fine, but now again it doesn't play nice. Any solutions?
    Thanks

    My own reply ...
    Sorry, should have checked this out earlier
    the answer is in a firmware up-date from LaCie, solving the energy save problem and therefore the issue with time machine.

  • Firewire problem with camcorder

    Help! New iMac 24", 2.8. Firewire 800 has two drives attached, daisy-chained to another -- one is for video capturing / scratch disk, other is for time machine drive. The Firewire 400 port is used for my Canon camcorder. My plan seemed to me a good one. However, when I first connected my camcorder, my time machine drive seemed to unexpectedly "eject" itself, and a warning message appeared basically saying I did not eject it properly. Furthermore, and most disturbing, is that iMovie 08 gave me a "communication error" message and I could not import video no matter what I did. It did detect my camcorder and did seem to communicate enough to make the camcorder play video on its own lcd, but no video actually transferred to the Mac. I tried iMovie 06 and with some luck it seemed to work. That firewire port (400) has worked recently with a different hard drive. Interestingly, when I disconnected both of my 800 drives, the import actually worked in iMovie 08! Yet I need one of those drives as my scratch disk! When I reconnected my scratch disk, the import screen told me my camcorder was disconnected or off! What gives! Help! If it makes a difference, my time machine drive is actually a 400 speed drive daisy-chained to the back of an 800 drive which in turn is connected to my 800 port. Thanks in advance. Frustrated to say the least.

    If it works with the drives disconnected, there is obviously some interference happening between the FireWire devices.
    Try connecting the FireWire 400 drive (that is currently daisy chained) directly to a FireWire 400 port on the iMac. Then daisy chain the Canon video camera to that drive's port (assuming it has one). Leave the other drives disconnected the first time. If it works, connect them one at a time to see if either one (and which one) makes it not work. With the drive between the camera and Mac, it might all work.
    Another thing you can try is to put a FireWire hub between the camera and the Mac.

  • Firewire problem with DVD burner

    After update to snow leopard no support anymore for external dvd burner from lacie. the systemprofiler shows it, but I can not use it anymore. I'm so frustated!-(
    Everytime the same: DO NOT CHANGE A RUNING SYSTEM!

    HI,
    Check out the vendor site for 10.6 updates for compatibility with your Firewire drive.
    Also, use Apple feedback. http://www.apple.com/feedback/macosx.html
    Carolyn

  • Need help with firewire problem with white macbook to new MBP...

    Hello...I purchased a new MBP 13.3 inch with retina display a week ago because my old white macbook from 2008 has a cracked screen, rendering it unusable.  I would very much liek to get some files off of it and onto my new MBP or onto an external drive.  I bought the firewire to thunderbolt apple adapter, but I then saw I need ANOTHER cord or adapter to go from the old macbook to the adapter.  Is this doable?  What is the best one to use?  are they all the same and which one will fit the adapter and the right end fit my old Macbook?  So confusing and it's been hard to try to find an answer online.  I am assuming I can boot the old Macbvook into Target mode and transfer the data.  Thanks for any help.

    This is the other cable and adapter you'll need http://store.apple.com/us/product/H7990ZM/A/moshi-firewire-800-cable-with-firewi re-400-to-800-adapter?fnode=51
    You may be able to fine it cheaper somewhere else though.

  • FireWire problem with speaker system

    I have a gen4 Nano that will not charge on my speaker system. I used the white docking adapter, but still nothing. It will play the music, but won't charge. We have three gen3 Nanos that are recognized, but not the gen4. Please help.

    Hi,
    Welcome to the Apple Discussions.
    Unfortunately, your 4th generation nano won't charge when it's connected to some components. Those components use the FireWire pins to charge, where newer components use the USB pins. And the newer iPods have stopped using the FireWire pins and only use the USB pins.
    Like yours, my speaker system uses the FireWire pins, but I have a 4G iPod, so I had to use a universal dock to charge my iPod, and then connect it to my speakers via a cable. On the one hand, it's not the best solution, but it also allows me to use a remote to control the iPod, which is a nice bonus I actually use more than I thought.
    charlie

  • Problems with File Transfers Over Firewire 800

    Problems with File Transfers Over Firewire 800.
    Over the past month, I have had problems when transfering files from my harddrive, over Firewire 800 to a portable drive. I usually transfer very large files (20gb or more) to the portable drives for moving files around. When I drag a file over to copy onto a drive, the transfer starts normally. If I drag more files to copy over, the computer screen goes darker and a large icon comes up that looks like a power button icon. It tells me to restart, so I have to do a hard shut down on my G5. Weird. I also get the dark screen of death sometimes when I am transfering those large files and open another application to do some work while it's copying. It's killing me. I am having to sit here and wait for the transfer to finish before I can do anything.
    Any thoughts...
    Dual 2.7 GHz PowerPC G5
    Mac OSX 10.4.3
    Dual 2.7 GHz PowerPC G5   Mac OS X (10.4.3)  

    Have you run the Apple Hardware Test? Sounds like it could be a RAM problem.

  • Problem with NIC and Firewire on MSI 865PE NEO2-PFISR

    Hi, I have lots of trouble getting the network adapter on the MSI 865PE NEO2-PFISR to work.
    The NIC's LED indicators doesnt even light up when I plug in a network cable,
    and in windows (win 2003 server) it doesnt find the adapter at all.
    The NIC is displayed in the bios, and I have the option to disable it,
    but it is enabled.
    I have even reinstalled windows 2003 server to try to get the NIC to work.
    I have upgraded the bios to v3.8 via live update, with no problems, although the
    firewire-option on the same page in the bios is still gone, it doesnt detect the
    firewire at all(!).
    I have also tried several other NIC's (a 3COM 3C905B TX and a 3C905B TX XL
    PCI adapter). The 3C905B TX worked fine for a while, and then it started saying in
    windows that a network cable was unplugged, and began to try 10mbit, 100mbit
    lots of retries, now it doesnt work at all.
    I swapped tp-cables and changed the ports on the network switch (which there is
    also other computers attached to which doesnt have any problems) and that didnt
    made any difference.
    It seems that the whole pci bus is long gone, and maybe the onboard NIC is
    attached to this same pci bus?
    Strange also about the firewire-controller which isnt detected anymore.
    The USB devices work, and even a 3com usb wlan adapter works well.
    I have tried to reset the bios several times without that making a difference.
    Anybody have a clue to point out here?
    Cheers!

    Quote
    Originally posted by Raven
    you could try and flash to an older bios
    I tried most anything on flashing bios, both to a lower and a higher version.
    I returned the motherboard to the reseller and got a new motherboard as a replacement. This doesnt have all the same problems. At first it didnt post at all, indicating to red lights on the diagnosis.
    Then I was so pissed I hadnt touched the computer in a week, and just tried to use it a few days ago, and it seemed to work all ok. I used it for a few hours, and then it locked up.
    When I powered it up again, the lights on the integrated adapter was out. At first it seemed to work to take the agp card a little out of its slot, as if it was unaligned or something. Used it for a few more hours.
    Then I plugged in the sound cables (5.1 sound with 3 cables), and with the last cable, the network darkened out AGAIN!!
    In the bios it still indicates that the network is enabled, firewire is enabled etc.
    I twisted the network cable, and for a few microseconds I get a orange light, not the usual green light. Now this has stopped too.
    I see other also have problems with these symptoms so I guess I've got another black monday card.
    I will return this card too, and ask the reseller to get a card of another brand.

  • Intel iMac 20' users - any problems with noise on your firewire interfaces?

    Someone please tell me that they have a quiet intel iMac 20'/Firewire interface set up, I'm having problems with a lot of digital noise from my Saffire LE & badly am hoping it's 'fixable' or just a faulty unit but more so, praying it's not noise from the iMacs Power supply that will interfere with any firewire interface I get???
    I've read many posts about G5's suffering from noisy psu's which was one factor in my choosing an intel iMac & I chose the Saffire on it's great reviews for sound quality, there's no way I can work with the noise I'm getting & I'm pretty much panicking that if it IS the iMac & firewire thats the problem I'll be screwed as i only have 6 pin firewire as a useable option (really don't want to use usb2)
    Incidentally, the 'budget' set up I had previously (PC & soundblaster audigy) didnt suffer from any noise like this (at least not that was even audible with the mixer levels at conversational level!) which i guess rules out any blame of this on 'mains hum/interference'?
    The noise is there with the saffire's monitor output knob at any setting & with no inputs connected, it;s even worse if i power the saffire with it's external psu instead of off buss power. I'm not using a firewire hub & I've tried switching firewire leads & removing the firewire hard drive i have in the other port in case this was affecting it.
    Would really appreciate hearing from anyone with similar troubles or even better anyone thats NOT having this problem with a 20' intel iMac & firewire interface so at least i know there's light (& quiet!) at the end of the tunnel
    Adam
    Intel iMac 20'   Mac OS X (10.4.7)  

    funnily enough I'm going the other way, I have a rack of external modules/>sampler/fx etc & a crate of looms I've just unplugged as they've not been >turned on in so long!!!
    I hear you there!
    The noise is there without any inputs at all to the interface, its defiantely >digital though, its like a toned version of the sound of an old telephone >modem.
    What I mean, is try disconnecting everything, drives and all. You might even disconnect the interface and crank up the iMacs volume to see if it is there. If it is, you can try the UPS and see if that takes care of it. Then add them in one at a time. All it takes is one cheap power brick in the mix to cause all kinds of trouble (if your using powered monitors, that brick too). Noisy components can actually send noise back into the source power.
    I know it can be really frustrating, especially if you have noise coming from more that one source. The key is to strip everything until it is quiet and then add them back in to see where the worst is. Then come up with a plan to try to get rid of the noise.

  • 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?

Maybe you are looking for