e6420 kernel panic with clover after direct upgrade to el capitan

[DustyWater]

First of all here are my system specs:

Dell Latitude e6420

Intel Core i7 2720QM

16 GB RAM

NVS 4200m

 

I had mavericks installed with everything working using chameleon,

the dsdt from here 

http://www.insanelymac.com/forum/files/file/342-latitude-e6420-nvs-4200-dsdtaml/

 

kexts from here 

https://osxlatitude.com/index.php?/topic/6192-guide-mavericks-on-dell-latitude-e6420/

 

and an ssdt from here 

https://osxlatitude.com/index.php?/topic/5943-dell-latitude-e6520-e6420-with-optimus-enabled-mavericks/

 

I had to switch to clover to do the upgrade, and it installed fine. The issue is that now it kernel panics when I try to boot it.

Here is a picture I managed to grab before it turned off: 

Does anyone know what is wrong?

[DustyWater]

Also, earlier it couldn't boot because of not being able to find mach_kernel, so I copied System/Library/Kernels/kernel to the root of the drive and renamed it to mach_kernel

 

Here is my clover EFI folder: EFI.zip

[Hervé]

Please note that, starting with Yosemite, OS X kernels go to /System/Library/Kernels folder under the name of "kernel". As such, what you did by copying the kernel to HDD's root under the name of "mach_kernel" is an unnecessary step to me. Clover and recent versions of Chameleon/Enoch are fully capable to boot Yosemite and El Capitan with the kernel in vanilla name and at new default location.

 

Your system KPs on EvoReboot so I'd remove that specific kext. What do you think? Personally, I've never needed it on my E6220 or the E6420 I briefly had between my hands.

 

Since you're using Clover (I stick to Chameleon/Enoch), make sure to enable AsusAICPUPM option to cater for SandyBridge CPU power management and avoid related KP.

[DustyWater]

I removed the ev0reboot kext and set AsusAICPUPM to true but it still kernel panics. Sometimes it doesn't even get all the way down

PCI (build 19:23: 

It just cuts off at that line

example: 

[Hervé]

I'd say you somehow chose a relatively challenging way of upgrading from Mavericks to El Capitan.

1. How did you configure Clover and what kexts have you used?
2. Can you try and post your EFI/CLOVER folder of your EFI partition?
3. Did you manage to rebuild cache or, alternatively, did you succeed in booting El Capitan without cache?

[DustyWater]

Ok I tried installing enoch on to the drive and upon boot (with -v) I got followed by  followed by the laptop turning off

[DustyWater]

 

I'd say you somehow chose a relatively challenging way of upgrading from Mavericks to El Capitan.

1. How did you configure Clover and what kexts have you used?
2. Can you try and post your EFI/CLOVER folder of your EFI partition?
3. Did you manage to rebuild cache or, alternatively, did you succeed in booting El Capitan without cache?

 

1. I used all the kexts from npjohnson's guide and a couple more (I don't remember exactly but if you give me a second I can send you a screenshot of everything in my S/L/E folder from my old imac)

2. It's in the second post

3. I used kext wizard to rebuild cache after removing the kext. I didn't try booting without cache. I will try now

EDIT: Booting without caches did nothing

EDIT 2: Here is all of the kexts in S/L/E:

 

[DustyWater]

Is there any hope recovering this or should I start from scratch with el capitan? (I would much prefer recovering this though)

[Hervé]

With Enoch, unless you've created the /Extra/kernel.plist file, you need to boot with the option KernelBooter_kexts=Yes. In addition, there's no on-the-fly AICPUPM patch in Enoch so you either need to boot with NullCPUPM kext or the patched AICPUPM kext (available here). I assume that, by now, you know that SandyBridge (and IvyBridge) systems KP on vanilla AICPUPM (well-known BIOS MSR lock problem).

 

Also note that kexts placed in /E/E will only be injected at boot time, not cached. It's totally similar to kexts placed in EFI/CLOVER/kexts/10.xx with Clover. If you want those kexts cached, set the KernelBooter_kexts option to No, copy your kexts from /E/E to /L/E, then repair permissions and rebuid your cache with Terminal commands:

sudo chmod -Rf 755 /L*/E*
sudo chown -Rf 0:0 /L*/E*
sudo touch -f /L*/E*
sudo kextcache -Boot -U /

[DustyWater]

Unfortunately even with the patched AICPUPM and the kernelBooter_kexts=yes flag. It still ends with the same result as post 6 of this topic. It says something about loading extensions then it dies.