Jump to content
10 posts in this topic

Recommended Posts

I've updated my system from build 11A390 to 11A444. Not its not booting anymore. Is there any way I can fix this or do I need to reinstall Lion?

 

Screenshot of crash attachedpost-610235-1308388397_thumb.jpg

 

EDIT: I'm using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 1.5a on USB with the following kexts inserted:

 

Disabler

EvOreboot

FakeSMC

IntelCPUMonitor

JMicronATA

NullCPUPowerManagement

SuperIOFamily

Link to comment
https://www.insanelymac.com/forum/topic/259645-lion-not-booting-after-update/
Share on other sites

I've updated my system from build 11A390 to 11A444. Not its not booting anymore. Is there any way I can fix this or do I need to reinstall Lion?

 

Screenshot of crash attachedpost-610235-1308388397_thumb.jpg

 

EDIT: I'm using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 1.5a on USB with the following kexts inserted:

 

Disabler

EvOreboot

FakeSMC

IntelCPUMonitor

JMicronATA

NullCPUPowerManagement

SuperIOFamily

 

Reinstall all kexts and delete other power managemant kexts.

those of [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], or those of the system?

 

I dont know about [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], im using Chameleon, but try first with system kexts

Correct me if I'm wrong, but. IO80211Family.kext is wireless LAN, which that system doesnt have

 

Yes that is correct but if you leave IO80211Family.kext as it is, it gives loading errors on boot as it depends on the other two kexts I mentioned (from Snow Leopard).

 

I hope it is clear now but hey I could be wrong too haha.

Jay

Stop removing and installing kexts from other operating system releases, you've got a mis-match in a kernel extension that is trying to load from libraries and it isn't getting the expected result.

 

That's what "symbol not found," means in that context. You've got something pretty broken in CoreFoundation and it isn't finding the symbol it wants in /usr/lib/libSystem.B.dylib.

×
×
  • Create New...