Jump to content
3 posts in this topic

Recommended Posts

Hi there,

 

I tried a sleepenaber.kext and at reboot my kernel panics.

 

So - no problem I thought - just boot the backupHDD (made with superduper right before).

 

What I tried:

 

1.) boot chameleon bootloader from my corrupted hdd

2.) chose my backupHDD.

 

But the kernel-panic is still there.

 

I have no clue where the problem is, what am I doing wrong?

 

Heres a screenshot: post-576770-1304709160_thumb.jpg

 

 

Please help me!

 

EDIT: Ok, managed it to delete the kext on my lap. Now its running again. But why didnt work my backup?

Be careful when updating or adding kexts and do it with only one backup if both crash all of the sudden you made some changes in BIOS that ruins the install. Also take a look into LegacyKernel by qoopz it blacklists the bad kexts that cause kernel panics so the system keeps on working.

Sure, and as I said: I did make a backup right before trying the kext with "SuperDuper".

 

But why wasn't the backup bootable? Why the same kernel panic occured?

 

Was it because I tried to boot the backup out of the crashed Chameleon? Are in Chameleon any information saved and delivered to every chosable booting device?

 

 

Please tell me :moil:

×
×
  • Create New...