Possible solution to Airport 10.4.10 issues
UPDATE 2: Apple's solution mentioned here only seemed to work because I was plugged in to AC. Running on battery contributes to the issues (see post 58 of this thread below).
----------------------------------
I've had the same problem here and *may* have a solution, though I have a hunch this is a shotgun approach for something with a simpler fix.
I typed a long me-too post yesterday (my first post after years of lurking; thanks to many of your for your advice) and had a kernel panic just before submitting it. Oh, the irony.
I installed both the most recent security update and 10.4.10 on a MBP Core 2 Duo 2.33 17" a few days ago. I did not get around to repairing permissions prior to the issues. For context, my system has been getting a bit sluggish over the past month and I'd also been wondering what's happening to cause that.
Same symptoms as many: Airport stopped working here and there (showing no wireless networks, which eventually clued me in to stop trying to fix it by resetting my router), and it was usually resolved however briefly by cycling Airport off and then back on. Sometimes it required a restart to begin working again.
The kernel panics started a day or two later, about two a day the first day and then about 6 the second day.
So, I contacted Apple and the many steps we did appear to have resolved the issue (at least after a few hours of use). Apple has apparently NOT identified or documented this as a known issue and I mentioned there were threads online discussing the problem, but this was news to the tech with whom I spoke. Here's what I hope is a complete list of what we did:
- He believed it was likely a hard drive problem, as this is their first thought with kernel panics. With Disk Utility we checked the hard drive and found one or two small block count errors. We repaired the hard drive from the OSX install disk that shipped with the Mac (boot from the disk holding C down, select a language, then select Disk Utility from the Utilities menu).
- We deleted the caches folder from the home library folder.
- We deleted com.apple.finder.plist from Library>Preferences
- Rather than deactivate all my startup items from my user account login tab, I asked if we could remove the Startup Items folder from the Hard Drive volume’s Library folder.
- We zapped the P-RAM (restart holding command, option, p, and r keys until hearing three chimes).
- We repaired disk permissions using Disk Utility (I asked what matters for sequence, and the disk permissions must be done after removing the com.apple.finder.plist file and dealing with startup items.
RESULTS:
So far no kernel panics and wireless is working properly. It's my first post after years, so forgive me if I note that my system is "snappier" (I just couldn't resist) for all the maintenance performed. It's back to acting like a new MBP.
Hope this helps some of you having the same issue.