Once I noticed that it has been taking up to 5–7 minutes for my MacBook Pro 2,2 to boot (the longest phase of the startup process was the blue screen which usually appears right before the desktop) and additionally, sleep (hibernate) mode stopped working. Both problems appeared simultaneously, so right from the start it was clear that they’re related.
To diagnose the problem, I booted in verbose mode (hold Cmd + V when it starts booting, later you may find the logs in Console.app) and noticed these lines:
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: Busy services : Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2 [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0 [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3 [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3/AppleFWOHCI [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3/AppleFWOHCI/IOFireWireController [1] Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3/AppleFWOHCI/IOFireWireController/IOFireWireLocalNode [1] Jun 21 03:06:20 Dae-MBP /usr/libexec/hidd[27]: Timeout waiting for IOKit to be quiet Obviously something was wrong with firewire. I checked my firewire 400 port and it appeared to be broken. Quick search revealed that the problem of dieing firewire ports is not uncommon for this generation of MacBook Pros, and the only way to repair it is to replace a logic board. I confirmed all of these by contacting a technician of local Apple reseller.
Since my MacBook was out of warranty and I didn’t want to spend 350€ on a new logic board for a quite old computer, I decided to minimize the consequences. The solution was easy: to move IOFireWireFamily.kext out of /System/Extensions. I as well have to repeat this operation after installing system updates. The sleep problem was gone as well.
Update: you may also want to try to repair your firewire on your own.
So I know I’m bringing up a older post, but I first wanted to say THANK YOU! This worked to fix my issue of my computer taking forever to boot and freezing up when the screen went to sleep.
HOWEVER, I now have a new issue. I need the firewire port to import video from my video camera. Obviously I can’t do that through the existing firewire on my macbook pro. I purchased an Express card that has firewire to use in the express card slot. The problem is when i remove the kext file it says driver is not installed for the express card in the information section of my mac. When I put the kext file back in the extensions folder, the problems come back but, then the driver shows up as installed for the express card.
So my question is there any way possible at all to disable to firewire port or remove the kext file, but keep the express card working in order to use firewire?
Any help would be FANTASTIC!
Hey Jamie,
I don’t think such thing has ever been done before, but I suspect that it is possible.
Perhaps there should be some sort of a codeless kext that would handle the built-in firewire port and do nothing other than distract it from being handled by the firewire driver.
Could you please provide all information available about your firewire stuff from System Profiler? You will have to put the old kext back to do that.
Slow startup and sleep problems on MacBook Pro. Confirmed! This fix worked perfectly. My logic board is mucked as it has no FireWire 400 or 800. Don’t forget that the “IOFireWireFamily.kext” must be moved out of /System/Extensions after every System Update. Start up and sleep issue is no more. Thanks for this post.
appreciate a step by step guide on how to “to move IOFireWireFamily.kext out of /System/Extensions”.
the IOFireWireFamily.kext is located in /System/Library/Extensions hence it is not allowing me to move the file. I am running OS X 10.5.8
Please advise
Try this in Terminal,
sudo mv /System/Library/Extensions/IOFireWireFamily.kext ~/Desktop
I have an iMac Core Duo (early 2006) model. I just upgraded from Tiger 10.4.11 to Snow Leopard 10.6.6 yesterday and my boot time was about 10 minutes. I thought maybe it was a memory problem at first. Then I noticed my system log had some IO Kit problem and was timing out. I’ve looked at so many discussions and finally found the answer. I followed your advice. Problem solved! I can’t thank you enough!
Thanks for all the posts here, they are pointing me in the right direction. I have a 2007 mbp 10.6.6- and I’ve just fried the firewire port. However, rather than just a slow boot, my mouse button and keyboard freeze for a good five minutes after boot. They come back though, but with a VNC into the computer I can operate the machine with my phone. (Not a great work around) I’ve tried PRAMing it, and taking out the IOFireWireFamily.kext to no avail. I’ve also tried ONYXing and a bit of APPLEJACKing also no success.
Any other thoughts on the matter? I can live without firewire, but I hate this booting issue.
Hmm…
1. Did you analyze logs? If not, do that via Console.app right after the reboot.
2. Try removing all IOFirewire*.kext stuff (so not just IOFirewireFamily) from /System/Extensions.
Hi Dae,
Thanks for getting back. I will try that tomorrow and let you know if it works.
Cheers!
Hi Again,
Ripped out ALL firewire .kext files. Success! My MBP is working away again, without the lag time. (firewire dead and gone, but that’s ok) I am very grateful for your advice. I’d actually posted the symptoms on macforums and got no help.
Thanks!!
I’m very glad it helped. Thanks for reporting back!
Just wanted to leave a huge THANK YOU for this post! Totally fixed the problem!! My ‘Book is back to being a speed demon!
thank you, now mac book works as “normal”. …no firewire but i can live with it…thank you again….Powerbook g4
Wow, thanks! I have been having very similar symptoms to Mike Murphy’s. I just deleted all the IOFireWire kext files. Now, I don’t have to wait 7 full minutes after macbookpro boots up to get my mouse and keyboard to do stuff.
I still have a 2 minute boot up…but obviously there is other stuff I need to do….
Thanks for finding this fix. I never use firewire anyway.
Happy macbook camper. :)
Ok, I just have to add another comment. This ALSO allowed my macbook to actually SLEEP when I close the display. Now the little white sleep light pulses (rather than shining solidly) and when I open the lide, the desktop returns (rather than giving me a black screen, to which the only response was to power down, power up (taking about 15 minutes each cycle!).
Wow, after 5 days of almost solid troubleshooting, internet research, this has been a HUGE relief.
Wow! Thank you. Ive had this problem for 18 months.. i scoured soooo far and wide to find out what the heck was causing this and i could not find an answer.. this was about 8 months ago.. I was seeing in the console that mine was getting hung up on a protools related anti-piracy service. My old protools interface was firewire and my new one was usb.. i didnt realize until i tried to plug a camera into my computer that my firewire no longer worked either. So I guess by the sounds of it my logic board is toast.. common problem… is there a way to definitively tell if your logic board is fried?
I don’t know, but I can tell you that my MacBook is still working as well as USB on it.
Hi Dae, this fix worked with my macbook pro1,3 too (2,4 Intel Core 2 Duo 17″).
Thank you!!
Has anyone tried upgrading from Leopard to Snow Leopard after removing the ktex file? Will it cause any issues?
I’m about to upgrade so i can get lion next month.
I’ve been using Snow Leopard since the release and it works just fine.
You still have to remove the kexts tho.
I confirm this works also for a MacBook Pro 4,1 Core 2 Duo 2.4 GHz, with Snow Leopard.
Same symptoms: very long time to boot and freeze on sleep. Firewire does not work
Removed all the iofirewire kext files from system\library\extensions (5 kext files in total).
Boot time is now normal and the Mac seems to awake happily after a nap.
A big thank to Dae!
Daniel (from Barcelona, Spain)
does this work for the 2010 Macbook pro? As of yesterday, my computer decided to stop reading my external hard drive and now gets stuck loading up. I have to shut the computer down repeatedly. Then after booting it gets hung up for about 4 minutes before i can use the mouse, etc. help?
You may try to do the same thing as I did — boot in verbose mode and check the logs to see what’s wrong. It must be there.
check if the System Profiler shows a red error message for you FW ports
i managed to fix my MBP 15 (early 2008) with this tip – so first of all thank you.
Problem I was having is best described as the computer getting “confused” suding start up while searching for the broken FW ports. With them disabled it skips the step.
So now: installing Lion on a computer with this…
Launch from installer, then it RESTARTS (presumably with a new FW kernel looking for the broken firewire port) so it never boots properly in Lion.
You’d have to get it to work to remove the kext again surely?
Anyone got the Lion update to work ?
You may try to boot from a Snow Leopard DVD (of course you’d have to wait 10 minutes or so) and use it’s Terminal to remove the kexts from Lion partition. Not sure if it works though, but its worth trying.
This problem has pestered me for month – thanx a million for your solution!
My 2006 MBP 15″ is still going strong minus the FireWire ports. I’m still leery of installing Lion though. Has anyone had a LogicBoard repair/replacement? I found a place that claims they can repair it for around $500.00 U.S. I’m am seriously considering having this done and getting the fans cleaned of dust at the same time. Will keep you posted.
If I were you I wouldn’t bother — I’d sell MBP 15″, add those $500 and buy a used (or even new) MBP 13-15″ from 2009 or later, which would be way faster than your 2006 machine, plus LED backlit display, plus unibody.
is that the complete hardware fix this would require? (rather than the software patch) ~ an entire logic board replacement?
I realise it may well be cost prohibitive but just interested to know
thanks guys
Thanks a million.
This issue has been plaguing me for months. My Firewire 400 only works when I wedge the cord at an angle. I can live without it and only activate it if and when I need it.
Hi Dae,
Thanks a million this resolved the booting problem I was having since past a month and I was being very lazy to find a solution for it.
After reading several forums it here where I finished my search. However there is still the same problem if I install a fresh OS X snow leopard on this machine…
Any one has gone through the same problem? Is there only a solution to install the OS X on this hard drive on different machine and then fit it back to this one?
Thanks
Hi John,
I have reinstalled SL several times since the problem occured on my MBP. The procedure takes longer than normally, but eventually it succeeds.
Could you describe the problem in detail?
Ok I will try with patience then. I dont mind if it takes an hour to install.. And I know what to do later just delete the firewire files.
But I read somewhere everytime when the updates are installed these files are restored?
Because my friend (not technical)wants to use this machine for a few months and I dont want the problem to occur in future after updates are installed?
Thanks
Normally only major updates (ones that change the system version number, i.e. 10.6.7 to 10.6.8) bring back the kexts.
Seeing Lion is now the priority for Apple, I don’t think there will be any major updates for Snow Leopard.
You may want to create a simple script for your friend, so in case the problem returns they would be able to fix it themselves.
The script such as this:
Save it as “fix.sh” to your Desktop, then open Terminal.app and type “chmod +x ~/Desktop/fix.sh” — that will make it executable.
The drawback: your friend has to have a user account password set, otherwise it won’t work.
Excellent thats a perfect solution then.
Thanks for your help all the way. Much appreciated.
You’re welcome :)
its amazing to me that you’re the only one on all of google that knows what my problem is. and it fixes the infamous sleep problem. my comp is back to normal thanks again.