Kernel Panic After Thunderbolt Update

FireWire cable, or, if both computers support Thunderbolt, a Thunderbolt cable.

+1 to above. The full directions are on the earlier pages of this discussion.

im reading this from a pc thanks apple

no USB cable then? I dont have old school fire wire for my mbp to the later smaller firewire conection on the broken imac.

For people being familiar with Terminal.app or the UNIX side of OS X there is no need to reinstall the system or restore everything from backup. All the "Thunderbolt update 1.2" replaces is this single kernel extension:

/System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleBCM5701 Ethernet.kext

There are no pre-/postscript scripts included in the installer so all it needs in case you're affected by the kernel panic is to restore this kext from its original state before.

In case you have a recent TimeMachine Backup simply pull the kext folder out of the backup after booting from the recovery partition (using cmd-r at boot). Or tar/untar it from another machine with 10.7.4.

You could even use the kext from the recovery partition itself. But then you should apply the 10.7.4 combo update after the next reboot because the AppleBCM5701Ethernet.kext on the recovery partition is from August 2011 whereas the AppleBCM5701Ethernet.kext when applied Thunderbolt update 1.1 is from 29th April 2012.

andybevans wrote:

no USB cable then? I dont have old school fire wire for my mbp to the later smaller firewire conection on the broken imac.

I do not belive a USB would work. From my understanding, you have firewire and thunderbolt as choices. More diections follow for any in need.

Taken from Tino H:

Applying the 10.7.4 Combo Update worked for me! All you need is a second Mac with Lion installed, a FireWire or Thunderbolt cable and the Combo update from the apple download site.

1. Boot your broken mac with the T-button pressed to enter the target drive mode
2. connect the mac with one of the cable to the other mac, the harddrive of the broken mac should appear on your desktop
3. download and start the combo update and follow the installation steps until you can choose the install location
4. choose the harddrive of your broken mac and proceed
5. after the update is done, eject the mounted harddrives and restart your broken mac after shutting it down. it should boot correctly

I have the latest Mac Mini Server (running Server, but using as my home desktop, not a server). I have donwloaded the TB 1.2 update, but not restarted yet. And I'm not planning to. My question is: what will happen when Apple finally releases an updated update? Can I donwload the new one and run the update with the other one waiting for a restart? or have a stumbled on some thing that could cause a Mac-pocalypse?

Ditto Ditto Ditto

Installed update. It gave an error saying it couldnt install - click to restart. Clicked but just hangs at the gray screen. Powered off manually and then kernel panic on restart.

Re-installed Lion with the recovery tool. Iphoto not working now. Decided to try the software update again and same exact issue. Now on second time re-installing Lion. -- Spring 2011 IMac

Has anyone been able to load their broken Mac in safe mode, the install the combo update and fix the kernel panic? I haven't attempted it yet as I am away from my mbp for the day, but wonder if it's a better option than the Recovery HD lion reinstall?

Just don't install the thunderbolt update (which I hear is now pulled off the server anyway) and you will be fine after the re-install and the other updates.

I couldn't get into safe mode, wouldn't boot to it when I tried. Your mileage may vary.

I sent an email to Tim Cook regarding this issue, and while he didn't respond, it is somewhat of a coincidence that the update disappeared about 30-minutes later.

Boy, do I feel powerful!!! OK... visions of grandeur, but who knows. 😉

I do it, my post instructions are above on this thread.

hey,

third time now trying to re-instal lion all seems to go well. Got to 40 hrs, 25 hrs remaining, then suddenly it's asking me for my Apple id again and the process starts all over again - back to downlading additional components. stuck in a loop.

Yeah, same here.