Security Update 2006-005 (#2): Loss of AirPort connectivity, fixes; Startup problems -- kernel panics; more

CNET staff

Sept. 2, 2009 12:05 a.m. PT

5 min read

[Note that since both the AirPort Extreme 2006-001 updater and Security Update 2006-005 modify AirPort-related system components, the two releases are causing similar issues (resolved with similar fixes) in some cases -- particularly with lapses in wireless connectivity. As such, we've listed some of the same fixes in both areas of coverage.]

Loss of AirPort connectivity Like the AirPort 2006-001 updater, Security Update 2006-005 is causing significant issues with wireless connectivity for some users.

MacFixIt reader Janine writes:

"I have a G4 iBook, and I downloaded and installed the update via Software update. The update installed with no problems, but on restart my airport was disabled. Internet Connect had airport greyed out, and running the diagnostics indicated that there was no Airport card installed."

Another reader adds:

"After installing the Security Update 2006-005 security update on my Powerbook G4 17", I had problems with the AirPort connectivity to my wireless Linksys router. The connection to the router is lost without reason every time I move to a nearby room, making the range of the reception very buggy. I did not have this issue before updating the Mac with the above-mentioned security update. Prior to the installation of the security update, I was able to go out to my garden and use my wireless G4 laptop with no problems."

Fixes

Change base station setting to "Always Stay Connected In some cases, you can resolve AirPort connectivity issues with AirPort base stations by modifying certain settings.

Launch the AirPort Admin Utility (located in Applications/Utilities), select your base station, and click configure (you may need to enter the base station password). Once you are in the base station's configuration pane, click on the "Internet" tab. Make sure the setting "Always stay connected" is selected.

Unplug and re-plug Base station/router You may want to try unplugging your wireless router (including AirPort base stations), waiting a few minutes, then reconnecting the router to power. Doing so can re-establish some faulty connections.

Check AirPort connectivity tutorial There are a bevy of AirPort-related fixes listed in our tutorial "Improving AirPort reception, avoiding dropouts/lost connectivity, working around card/Base station recognition issues." Failing the above solutions, look at the tutorial and run through the listed fixes until one restores proper connectivity.

Once you've found a fix in the tutorial, please drop us a line and let us know which solution worked for this specific update.

Startup problems -- kernel panics, more Some users are reporting issues startup after applying Security Update 2006-005. Note that a longer-than-usual first startup after applying major updates is to be expected, and normal boot speed is usually restored on subsequent startups.

Among the most serious issues is a persistent kernel panic upon startup.

MacFixit reader Will writes:

"I just installed the Security Update (with receipt package name: SecUpd2006-005Ti.pkg ). It asked me to reboot, and then caused a Kernel Panic for me on reboot - just when the login screen should be appearing. This was persistent - i.e. my machine was now unusable for a normal user.

"I managed to boot into single user mode [Ed.- by holding the Command and S keys during startup]. I used lsbom to look at the receipt package contents, and moved the AirPort .kext out of the way (the only thing in the bom). I still got a crash on restart."

"I then just tried running /etc/rc from single user mode and was able to boot. Weird... When the system booted, it brought up an Apple dialog ('your system crashed...') and gave me a backtrace. The backtrace suggested that the problem might be in the DoubleCommand extension (version 1.6.1 - pre-release :) that I had installed. I've moved it out of the way."

Another reader adds:

"On installing and then restarting, the Mac's grey screen and logo came up, but as soon as the blue screen came up (just before the progress bar box appears) - kernel panic.

"Restarted again. This took ages (about 5 minutes) but it kernel panicked at the same point. Restarted again, this time holding down the shift key. After a long time (about 5-6 minutes), the computer's login screen appeared. Once logged in, it took about another minute for the desktop to appear."

"I then ran a repair permissions and it repaired a lot of errors. Restarted again and all is ok. Just to point out that I did not repair permissions before installing (as I do usually). Obviously this is becoming more and more important."

Many of these issue can be resolved by following the guidance in our tutorial "Avoiding and eliminating Kernel panics."

A few of the more probable fixes for these cases:

Boot in Safe mode (by holding the Shift key during startup), then look inside your/System/Library/Extensions folder for recently added third-party items, temporarily removing them and checking for persistence of the issue.
Look in the /Library/StartupItems folder if you are having kernel panics at startup. Remove any third-party items and check for persistence.
Disconnect all external devices if you are having a kernel panic at startup or shutdown, and leave them disconnected until the system is fully booted. Then connect them one-by-one and see if the issue persists

Cache corruption can cause disk mounting issues, other problems Any time a significant update to Mac OS X is applied there is the potential for cache corruption. Corrupt system and user-level caches (as we've stated numerous times) can cause sundry issues, most prominently an inability to mount hard drives and other media, startup/shutdown issues and more.

Accordingly, some users are reporting traditionally cache-related problems after applying Security Update 2006-005.

MacFixIt reader John reports an issue mounting an external FireWire hard drive:

"Since installing Security Update 2006-005 on my iMacG5, my external firewire LaCie hard drive has unmounted: no icon on the desktop. On the other hand, my external Seagate mounts."

Mark Tennet reports a similar problem:

"Since applying the security update, my brand new MtBook external hard disk fails to mount after the Mac goes to sleep. It's the only device on the Firewire 800 circuit (G5 2x2GHz) and only a complete restart, then power down the drive and power up again will get it to mount. Very frustrating."

The easiest way to deal with these problems is to simply delete the offending caches. Unfortunately, deleting caches can result in temporarily sluggish system operations and some other oddities. These effects are usually minor, however.

You can delete caches manually by dragging the following files to the trash (you may need to enter your administrator password for some files):

com.apple.kernelcaches (a folder in /System/Library/Caches)
Extensions.kextcache (a file in /System/Library)
Extensions.mkext (a file in /System/Library/)
com.apple.ATS (a folder in /Library/Caches/)
Files that start with com.apple.LaunchServices (in /Library/Caches)

An easier option is to simply use the built-in cache deletion routines offered by third-party utilities like Cocktail, Mac Pilot or Tiger Cache Cleaner.

Previous coverage