Firewire Ports not responding

I have a Maxtor external HDD which previously worked perfectly fine with my computer when connected via Firewire. However I have not used the drive for a few months and when I went to use it again today, it would not mount on the desktop.
I have tried both ports on the drive and the computer.
The external drive works fine when connected via USB, however I don't have any 2.0 ports so really need the speed of firewire.
I have done PMU resets and nvram resets to no avail.
I have cleaned the cable and connecting ports.
The external One-Touch button lights up when firewire is connected at both ends, however the light turns off when one end of the firewire cable is disconnected leaving me to believe the cable is just fine.
Please help!

USB and FireWire Quick Assist
http://support.apple.com/kb/HT1151?viewlocale=en_US
What to do if your computer won't recognize a FireWire device
http://docs.info.apple.com/article.html?artnum=88338
Dealing with FireWire problems (drives not mounting, devices unrecognized, etc.)
http://www.macfixit.com/article.php?story=20041221081432908
 Cheers, Tom

Similar Messages

Firewire ports not responding to external drives.

I have a LaCie 250 gig and it was working fine until I plugged a power book into one of the firewire ports. Not only did my G4 not recognize the power book, it also stopped recognizing my external drive.
The .mac site said to unplug everything and restart the computer to reset the firewire ports. Which I did and nothing changed. Figured it was a lost cause so I used the USB instead.
Then, one day, I tried it again to see what would happen and it worked. The firewire went back to normal and everything was fine.
The other day, I plugged my Canon XL2 into the firewire port and it shut everything down again. So, now I'm without firewire and back to USB for my external drive.
The firewire DOES turn on the drive, it just doesn't recognize that there's anything plugged in.
Thoughts?

1. Shut-down your Mac, and unplug the power cord
2. Turn the power off on your external FireWire devices
3. Unplug the FireWire devices from the Mac
4. Wait for 5 min.
5. Plug the power cord to your Mac only
6. For PPC Macs: Restart the Mac while holding the Option-Apple-O-F, and keep holding until you get the ">" prompt, then release the keys
7. At the ">" prompt type:
      reset-nvram and hit the Return key
      set-defaults and hit the Return key
      reset-all and hit the Return key
the last command will restart your mac
8. Shut down your Mac
9. Connect all your FireWire devices to the Mac and turn them on
10. Restart your Mac.
All your FireWire devices should reapear, if not repeat the procedure
How to avoid the issue :
The only really proven way to avoid burning up a FireWire port is to connect all devices and to turn them on PRIOR turning on the Mac. Likely, one must unplug them and turn them off AFTER the Mac has been turned off. If you need to connect another device, then you're on for a shutdown of your machine...  It's a tad annoying but it guarantees that the FW ports won't be damaged.  Be careful when using self powered devices such as webcams, iPods, hard drives or hubs, as they can destroy the port pretty easily. Another thing is to avoid daisy-chaining hard drives.
When the FW port doesn't respond anymore :
In this case, peripherals won't be mounted upon plugging, and won't be displayed in Apple's System Profiler. The self powered devices will still be fed by the port, but won't respond either.  It happens that the PHY just hangs after a surge or a random problem. Once hung, the port will not respond any longer, it is possible to reset the component by going through the following steps :
1° boot the PPC mac in Open Firmware by holding [ Apple key - Option - O - F ] after the startup chime.  2° you'll get to a command prompt. the keyboard mapping will be QWERTY, so pay attention when you type the following :  RESET-NVRAM (enter)  RESET-ALL (enter)  3° Now the mac should restart itself and the port should function properly again.  If it still doesn't work, then it means that the PHY is damaged.
http://www.hardmac.com/articles/16/
From Kappy post:
922 is only used in dual drive cases to provide a "build-in firmware RAID support"
912 or 912+ is FW800, the "+" means USB2
911 is FW400
924 adds eSATA support along with FW400/800
MacSales, OWC Tech Support library is where I would go first, as they do tend to have or links to, firmware updates for Oxford.
From Wiebetech:
I just upgraded my Mac OS, and now I'm having trouble with my FireWire device. What can I do?
A: With nearly every OS update Apple releases, some external drives are not recognized after the update. The typical symptom is that the device will not mount but the volume is visible and grayed out in Disk Utility. This means that the device is working properly, but the OS does not recognize the volume as mountable. Sometimes the drive does not show up at all.
The first thing to do is to see if repairing Permissions with Apple's Disk Utility First Aid feature solves the problem. If not, try repairing the disk with First Aid. Another possible solution is to zap the PRAM. This is done with a keyboard command while rebooting. Restart your computer and hold down the Command, Option, P and R keys. Consult the Apple web site for details.
If this does not work, then try pushing the PMMU reset button on the logic board. Consult the Apple web site for locations of the button for your Mac. If the drive still does not show up, shut down, disconnect all peripheral devices, and boot from the Mac OS Installation CD. The later the OS version, the better. Do not reinstall the OS, but when the Installer is loaded up and ready to begin, go to the File menu and use the Disk Utility program. Connect the drive that is having problems, then start the Disk Utility application. If you see the external drive and it is not grayed out, you know the drive is okay. Run Disk First Aid on it anyway. Then run it on your internal boot drive while you are at it. When done, unmount the external drive and UNPLUG it! Then restart the Mac.
When the Mac has restarted and is running on the internal boot drive, reconnect the external drive.

Firewire port not working?

tonight, my DVD burner and my Firewire HD are not being detected. I tried to see if system profiler recoginized my firewire port, but All I got was 'No information found.' what can I do to fix this? I need to access this FW hd because it contains all of my music, photos and critical data! thanks!

it seems weird that it just magically started working!

USB, Firewire ports not being recognized?

Recently, I've been having trouble using my USB and firewire ports. I have a 1TB WD external hard drive which has been working fine until about a month ago when it stopped being recognized when I connected it through Firewire. I thought maybe my firewire cable or port was bad so I tried hooking it up through the USB port and it still didn't recognize that it was connected. After playing with it for a while, I finally got it to back it up.
Tonight I connected a thumb drive and it is not being recognized either.
Both ports are being recognized it Disk Utility and in System Profiler, and the USB ports work when I use them to charge my phone and Ipod all the time.
Any suggestions?

Well now I feel a little silly..
I have tried using it on another computer and it was recognized just fine.
However, I have not tried manually mounting my WD hard drive and when I went to try to that, it worked just fine right away, without doing anything.
I then tried the thumb drive again and when I tried to mount it, it came up with this error:
"The disk “UDISK” could not be mounted.
Try running First Aid on the disk and then retry mounting."
So I ran First Aid and it came up with this error:
"Disk Utility stopped verifying “UDISK” because the following error was encountered:
Filesystem verify or repair failed."
The details say that the "File system is left marked as dirty."
So I guess there must be something wrong with the thumb drive, although it seemed to work fine on my PC.

Firewire port not recognized after 10.7.5 update??

I updated yesterday to OS X Lion 10.7.5 and now my MacBook Pro says my firewire port is not recognized…any ideas??

Wow, no help at all. Thanks, Apple!! Another stellar performance. That's the last time I ever install an update as it comes up.

Open ports not responding

Dear All,
I have open my 25, 110, 80 port on my Server from local i can telnet all those via my private ip but from public ip its not responding.
2nd thing I can ping both ips of My server through private ip and through public ip.
Any help to solve this issue.
Thanks
Rehman Ghani

I have to agree with ngoldwat's statement. The symptoms sound like misconfigure or non-configured NAT on your router. Take a look at it and ensure your NAT statements are applied to the correct interface as well. You may also have to tweak the ACL that identifies the traffic to be NATed. Good luck.

FireWire bus not responding

Subject says it all. At boot-up this morning, none of the FireWire devices are found. System profiler sees nothing on the FireWire Bus. Shutting down, rebooting, unplugging, plugging, powering down, powering up, all have no effect.

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. Yours is the 10.4.10 Combo update ( PPC, not for Intel systems). Others reading, download the Combo that applies to your system.
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.
 Cheers! DALE

Firewire port not suplying energy wen runing only with battery

Hi all,
since today I v noticed that if my MBP is not connected to the power adaptor
will not suply energy any more to the Firewire 400 port (the only one I have ).
This is a problem because I am often working with ext drive on the run...
any idea on why this is happening ?
I v just got back my laptop back from the Apple store were they have replaced the
optical drive and they v told me that firewire port was working fine.( I was suspecting something cauz I v had several hardrive unmounting without any reason).
Now that my laptop came back there is this issue...
best
Shiama

Your computer should provide power to the Firewire port when running on battery as long as the computer is not shut down or sleeping, shiama. If it is sleeping or shut down then it will only provide power when the power adaptor is plugged in.
You could try resetting the SMC and PRAM . Perhaps try another FW cable to make sure that this is not the cause of your problems, though I presume, from what you say, that power is supplied to the FW drive normally if the power adaptor is plugged in.
Some supposedly bus powered FW drives may need more current than the battery alone can support though. What brand and model is the drive? Has it worked off battery alone before? Are any other devices attached, and were you running software that places a heavy demand on the CPU or Graphics processor when the external drive was in use?
Cheers
Rod

USB port not responding

The second USB port on my iBook is not responding to my Flashdrive. However, the other USB port is. Any suggestions for fixing or figuring out what the problem is?
Thanks.

Help. I too am having problems with my USB ports on a brand new 2.16ghz 15" Macbook Pro with 2GB Memory. More specifically, for my business, I use Vectorworks 12, a macintosh CAD program with a serial dongle that enables me to simply open and run the program. Well, the serial dongle is not lighting up as it should whwn plugging it into my MacBook Pro. My wife has a 15" PowerBook and G4 17" iMac, in which the dongle does NOT light up either! When I plug the dongle into my Dual 2 ghz "G5" Tower it lights up perfectly as it historically did! I plugged in a thumb drive that works in both my laptop and G5 tower. So why all of a sudden does the Vectorworks Serial Dongle become unrecognized by both USB ports in my MacBook Pro when Thumb drives, iPods, USB mouse etc. all work? The serial dongle should have at least lit up in my wifes 15" PowerBook or G4 iMac if the problem was isolated to my MacBook right? Something is messed up from the last firmware update maybe? So, what the heck happened! It was working a few days ago!? I need to use this serial dongle in my MacBook Pro but why is it, of all these computers mentioned, only being recognized on the G5? Please Help!

Lacie D2 Firewire drives not responding.

I'm tearing my hair out trying to resolve this problem. Both of my Lacie D2 drives have stopped mounting on my desktop for some reason (see spec of my mac in my sig below).
In System Profiler, when either of the devices are plugged in, the message under 'Firewire' is 'No information found'. When they're not plugged in it reads 'Firewire 400' or something like that...
HOWEVER:
1. My other Lacie 10GB External Drive (that runs using power from the mac via Firewire, not a seperate power supply) does show up in the profiler and mounts/operates properly.
2. Other devices (e.g. original ipod, printer) work fine with the Firewire ports on my mac.
3. The problem drives work and mount fine on my G5.
4. Have tried using different power adapters for the Lacie Drives and no change.
5. Drive mounts if I use a USB connection.
*THINGS I HAVE TRIED SO FAR:*
1. Reset PRAM
2. Reset NVRAM
3. Unplugged all devices, shutdown mac, unplugged from mains for 30 mins, then rebooted and reconnected devices.
4. Repaired disc permissions, reinstalled 10.39 combo update, repaired permissions again.
5. Used Lacie Updater to add latest firmware for the drives but these were already up to date
So as you can see, I've tried a few solutions that I read about on these boards and still no joy. The only thing that I think I have changed on my mac since this starting hapening is updating iTunes to 7.6. Apart from that, nothing else has changed.
Think that's everything. If I remember any more info, I'll post it up.
Hope someone can help me!!
Cheers.

It seems you have tried most things in my firewire faq; I'll post it here in case you missed something.
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.
 Cheers! DALE

Firewire port not working Mac Mini (G4 1.25ghz)

Hi,
The firewire port isn't working on my mac mini, I've tried several devices, but none are connecting. I was wondering if anyone else was having this issue and possibly a solution. The only software installed on the computer since the firewire worked last was Apple updates, so maybe other mini's lost firewire somewhere along the way.
Thanks, and Thanks
W

This worked from Smokerz in the Power Mac G4 forum:
1. Shut-down your Mac, and unplug the power cord
2. Turn the power off on your external FireWire devices
3. Unplug the FireWire devices from the Mac
4. Wait for 5 min.
5. Plug the power cord to your Mac only
6. For PPC Macs: Restart the Mac while holding the Option-Apple-O-F, and keep holding until you get the ">" prompt, then release the keys
7. At the ">" prompt type:
reset-nvram and hit the Return key
set-defaults and hit the Return key
reset-all and hit the Return key
the last command will restart your mac
8. Shut down your Mac
9. Connect all your FireWire devices to the Mac and turn them on
10. Restart your Mac.
Works fine now thanks Smokerz!!!!!
also repaired permission and reset PRAM, nothing worked until I did this.
W

New 2011 MacBook Pro Firewire Port Not Working with Focurite Saffire 24 DSP

The firewire port powers the Saffire 24 alone, and the device shows up in the system profiler, but I can't see it in the Sound devices menu... I have updated all of the Focusrite drivers to version 2.2 so I need to ask this board for solutions.

i am having the same exact problem. However, I've never had a Focusrite Driver installed previously. I just bought the Interface and installed the software. It downloaded the newest version of the software to install.
If it also installed the previous drivers, how would I unistall those?

IEEE 1394/Firewire port not seeing DV

Hey All,
New to this forum, but looking for some help.
I have read just about EVERY previous topic regarding the 1394 issues and cannot find a solution to my problem.
I CAN see the 1394 setting in CMOS, and it is set to "AUTO". Also, in the Device Manager, I can see "IEEE 1394 Controller" with no IRQ conflicts. I have updated all of my MSI drivers as well as CMOS up to current. I have installed the DV drivers that came on my Camcorder's CD as well as programs that are designed to utilize the DV out on the camcorder. Also, I have reconnected my two 1394 ports on the motherboard in every configuration to check if it was a connection problem. Tomorrow, I'm gonna go get another cable, but doubt that's it; it's brand new.
I plug in my Digital Camcorder (Canon ZR85) and there is nothing. Windows makes no notice of it, and when I run the program designed to utilize it, it says that it is not connected. I have followed the owner's manual to a 'T' for setting it up.
Here's my info:
Athlon XP2400
512 MB RAM
120Gig drive (SATA)
Windows XP Pro (SP1a)
Canon ZR85 MiniDV
4 pin to 4 pin IEEE 1394 Firewire cable
(This MiniDV Camcorder will only connect DV via 1394, not USB 2.0)
Any help would be greatly appreciated!
Saint

So... seeing that no one responded to my initial request for information to solve this problem and I was not able to find any other helpful forums out there, I decided to do the prudent thing and buy a new motherboard/cpu, etc.
I bought what was supposed to be a top-line mboard, the K8N Neo Platinum with an AMD 3000+ chip, 512 PC3200 Crucial memory, 200 gig SATA HD, and 3dForce 6800. What I have come to figure out is that my brand new MSI mboard has the EXACT DAMN PROBLEM!!!!!!!!!!!!!!!!
I vowed years ago not to buy another MSI because of previous failures, but I was convinced that they were really producing quality boards now. Yet again, however, I guess I was fooled.
IF anyone has ANY help they could provide for this problem, I would be incredibly grateful. Otherwise, I'll have to take this mboard back, and I will NOT EVER buy another MSI product, and will be sure to tell everyone else the same thing.
Desperately,
Saint Raj

20" Cinema display with USB and firewire ports not working

I have a new 20" display and was wondering why my USB and fire wire ports at the back are not working. I have an external drive that is powered hooked up to the fire wire port and a no powered piano keyboard to a usb port.
Any help please

Verify that the display’s USB and FireWire cables are firmly plugged in to the
computer. Do they show in your profiler?
Try different ports in the computer.
Verify that your computer ports are working with other known problem free device.

Firewire Port not working, URGENT help please¡¡¡

Hello People, i´ve just got a new Mac Mini last week, and i´ve been trying to get my Alesis MasterControl audio interface, and is just a complete mess.
This happened right after i´ve upgraded to 10.8.3 so i don´t know, the weird thing is that if i connect my old iBook to the Mac Mini the FW800 port works, but everytime i connect the audio interface, nothing happens, also the drivers from alesis, are up to date. i first thought about the port of the Mixer went bad, but it has 2 and non of them works, also thought about the cable but the same cable works when i connect my iBook, and the mixer is not bus powered, it has it´s own power supply.
Needless to say i´ve already done the usual reset PRAM, turn of the Mac unplugged for 30 hour to reset the bus. etc.
This is the usual firewire only system log that i get:
31/03/13 08:01:20.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 08:01:30.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 11:33:23.529 system_profiler[528]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 11:35:43.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:38:55.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:42:08.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:44:39.124 CleanMyMacHelperTool[583]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671"
31/03/13 11:44:39.146 CleanMyMacHelperTool[583]: Wont clean /Volumes/AlesisFirewire-3.5.3.8671 because disk image
31/03/13 11:44:39.148 CleanMyMacHelperTool[583]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671"
31/03/13 11:44:39.149 CleanMyMacHelperTool[583]: Wont clean /Volumes/AlesisFirewire-3.5.3.8671 because disk image
31/03/13 11:44:52.727 coreservicesd[62]: Application App:"AlesisFirewireUninstaller" [ 0x0/0x7f07f] @ 0x0x7fb5c8c30050 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x80080:) ), so denying.
31/03/13 11:44:52.727 WindowServer[85]: [cps/setfront] Failed setting the front application to AlesisFirewireUninstaller, psn 0x0-0x7f07f, securitySessionID=0x186a5, err=-13066
31/03/13 11:47:28.533 CleanMyMacHelperTool[656]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671",
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:47:28.544 CleanMyMacHelperTool[656]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671",
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:49:26.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:52:39.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:57:22.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 11:57:34.000 kernel[0]: Alesis Firewire - 3.5.3.8671 preliminary - x86_64 CJ - May 3 2010 02:43:28
31/03/13 11:58:36.982 com.apple.launchd.peruser.501[155]: ([0x0-0x1d01d].tc.tctechnologies.AlesisFirewire.controlpanel[238]) Job appears to have crashed: Abort trap: 6
31/03/13 11:58:37.252 ReportCrash[242]: Saved crash report for AlesisFirewire Control Panel[238] version 3.5.3 (3.5.3.8671) to /Users/m1kygarcia/Library/Logs/DiagnosticReports/AlesisFirewire Control Panel_2013-03-31-115837_Mac-mini-de-Miguel.crash
31/03/13 11:58:39.831 system_profiler[267]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 11:58:50.676 com.apple.launchd.peruser.501[155]: ([0x0-0x23023].tc.tctechnologies.AlesisFirewire.controlpanel[274]) Job appears to have crashed: Abort trap: 6
31/03/13 11:58:50.837 ReportCrash[242]: Saved crash report for AlesisFirewire Control Panel[274] version 3.5.3 (3.5.3.8671) to /Users/m1kygarcia/Library/Logs/DiagnosticReports/AlesisFirewire Control Panel_2013-03-31-115850_Mac-mini-de-Miguel.crash
31/03/13 11:58:53.638 system_profiler[277]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 11:59:09.747 CleanMyMacHelperTool[300]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:59:09.905 CleanMyMacHelperTool[300]: Wont clean /Volumes/AlesisFirewire-3.5.6.11675 because disk image
31/03/13 11:59:09.906 CleanMyMacHelperTool[300]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:59:09.907 CleanMyMacHelperTool[300]: Wont clean /Volumes/AlesisFirewire-3.5.6.11675 because disk image
31/03/13 12:00:47.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:00:59.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:01:56.720 system_profiler[269]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 12:05:40.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:08:52.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:12:42.277 AlesisFirewire Control Panel[245]: -_continuousScroll is deprecated for NSScrollWheel. Please use -hasPreciseScrollingDeltas.
31/03/13 12:12:42.277 AlesisFirewire Control Panel[245]: -deviceDeltaX is deprecated for NSScrollWheel. Please use -scrollingDeltaX.
31/03/13 12:12:42.278 AlesisFirewire Control Panel[245]: -deviceDeltaY is deprecated for NSScrollWheel. Please use -scrollingDeltaY.
31/03/13 12:13:53.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:25:29.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:25:38.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:28:30.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:28:33.906 system_profiler[273]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 12:31:41.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:35:16.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:35:26.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:37:53.513 system_profiler[266]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 12:39:36.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:39:49.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:42:55.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 53 bus resets in last 3 minutes.
31/03/13 12:46:50.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 68 bus resets in last 3 minutes.
31/03/13 13:01:30.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 13:01:41.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 13:05:27.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 79 bus resets in last 3 minutes.
31/03/13 13:06:31.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:09:43.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:13:31.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 13:13:45.006 com.apple.kextd[11]: Can't load /System/Library/Extensions/IOFireWireIP.kext - ineligible during safe boot.
31/03/13 13:13:45.008 com.apple.kextd[11]: Load com.apple.iokit.IOFireWireIP failed; removing personalities from kernel.
31/03/13 13:13:54.818 com.apple.kextd[11]: Can't load /System/Library/Extensions/AlesisFirewire.kext - ineligible during safe boot.
31/03/13 13:13:54.823 com.apple.kextd[11]: Load tc.tctechnologies.driver.AlesisFirewire failed; removing personalities from kernel.
31/03/13 13:13:56.372 com.apple.kextd[11]: Can't load /System/Library/Extensions/AlesisFirewire.kext - ineligible during safe boot.
31/03/13 13:13:56.375 com.apple.kextd[11]: Load tc.tctechnologies.driver.AlesisFirewire failed; removing personalities from kernel.
31/03/13 13:15:40.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:18:46.763 com.apple.kextd[11]: Can't load /System/Library/Extensions/IOFireWireIP.kext - ineligible during safe boot.
31/03/13 13:18:46.768 com.apple.kextd[11]: Load com.apple.iokit.IOFireWireIP failed; removing personalities from kernel.
31/03/13 13:18:46.797 com.apple.kextd[11]: Can't load /System/Library/Extensions/AlesisFirewire.kext - ineligible during safe boot.
31/03/13 13:18:46.800 com.apple.kextd[11]: Load tc.tctechnologies.driver.AlesisFirewire failed; removing personalities from kernel.
31/03/13 13:18:50.775 system_profiler[221]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 13:18:52.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:21:03.488 system_profiler[235]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 13:22:37.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:24:07.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 13:24:19.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 13:31:00.926 system_profiler[316]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 13:33:03.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 134 bus resets in last 3 minutes.
31/03/13 13:35:11.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:38:24.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:41:36.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:44:48.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:58:13.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 14:01:25.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
Can somebody help, please i´d gladly appreciate it.

I have this
System Profiler[170]
SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
& this
kernel FireWire (OHCI) Lucent ID 5901 built-in: no valid selfIDs for more than 3 minutes after bus reset.
Pls, help!!

Firewire Ports not responding

Similar Messages

Maybe you are looking for