February 15th updates (Security Update 2007-002, DST, Java R5) [#2]: Kernel panics; Device recognition problems

[This content relates to a slew of system component updates released by Apple on February 15th, including:]

Because the updates were released and applied by most users simultaneously, deciphering specific problem culprits is impossible in some cases. Instead, issues are aggregated here and also covered specifically for each update as appropriate]

Kernel panics: Check for errant devices/drives As we noted in our initial coverage of the 2/15 updates, Mac OS X systems can become more susceptible to errant internal or external devices after major updates. As such, kernel panics, startup issues and other problems previously non-existent can ensue after seemingly innocuous software releases.

The fix is sometimes not as easy as simply identifying and removing the offending device(s) [for help doing so, see our tutorial on reading crash reports]. Often, associated kernel extensions or other driver software must be removed in order to resume normal system operation. The most problematic of these files can generally be found in the folder:

• /System/Library/Extensions/

and will be labeled with either the name of the device or the device's manufacturer (or both), as well as the suffix ".kext", e.g.: ATIRadeon9700.kext.

In addition to removal of the offending device, you may need to (at least temporarily) drag associated kernel extensions out of the aforementioned directory, then restart in order for conflicts apparent after a system update to dissipate.

Device recognition problems Some users are reporting device recognition issues after applying the 2/15 updates -- a not uncommon occurrence after significant modification to system components.

MacFixIt reader Alex writes:

"I have installed the new daylight and security updates and my pen mouse does not work anymore. Since I have to use this for medical reasons for my work I am very upset that the new updates seem to have disabled the pen mouse."

The solution for some cases of device recognition loss is to simply unplug the afflicted device(s), restart and re-connect them.

In other cases, clearing system caches with a utility like AppleJack, Cocktail or Tiger Cache Cleaner can often restore accessibility to FireWire devices that otherwise refuse to mount.

Outdated firmware or drivers may be precluding recognition for some devices. Try checking your device manufacturer's Web site for the latest downloads.

Previous coverage:

• Problems starting up after Apple's February 15th updates (Security Update 2007-002, DST, Java R5): Fixes

Resources