Jump to content

[SOLVED] E7240 10.11.4 fresh install boot problem - kernel panic


sales
 Share

Recommended Posts

I followed the Dell Latitude El Capitan Clover Guide (fresh install of 10.11.4 with E7440 spec) - right after step 13 of Install OS X El Capitan, I got kernel panic and the syetem reboots. Screen shot attached.

I have tried reinstalling three times just in case I missed some important step (and subsequently update my BIOS from A12 to A17). But I got the same kernel panic every time.

 

My system spec:

Latitude E7240, BIOS A17
i7-4600u 2.1GHz 8GB DDR3L
Intel HD 4400, 1366x768 (non-touch)
Intel AC7260+BT
 
I tried using cpus=1 at the first installation, and it went on to complete the installation. But I had no sound (no output device), and the mouse pointer stopped responding to the touchpad, And I got a virtual drive mounted (seemed to be the mirror image) instead of the physical internal SSD. It feels like I am opening up another can of worms.  :( So I abandoned that route.
 
How can I fix this???
 
 
Update:
Incorporating the fixes in 1 & 2 into bootpak solved the kp issue. Fresh installation was a straight through. Now running 10.11.4 on E7240.  :P
 
Some tweaks:
 
 
Cheers 

post-91018-0-81028800-1459804660_thumb.jpg

Edited by sales
Link to comment
Share on other sites

  • Moderators

No, display resolution won't be an issue for Haswell whether it's set to dual link or not.

I'm doing a fresh build with 10.11.4 with the same bootpack now and see. Should be done in 10min.

 

Update:

Okay, finally getting the error that many are having on the Latitude systems. No issue during the install.

Only after the first reboot, the KP occurred. I replaced the VoodooPS2Controller with one ApplePs2Controller uploaded by Wern.

That got past the error and everything is working as before. Will add this to the guide.

Link to comment
Share on other sites

For anyone experiences the following syndrome after a successful new installation of 10.11.4:

4/7/16 11:04:29.000 AM kernel[0]: ACPIBatteryManager: WARNING! fCurrentCapacity > fMaxCapacity. adjusted fCurrentCapacity from 2825, to 2425
4/7/16 11:04:29.424 AM powerd[49]: Failed to read current rating(0xe00002f0)
4/7/16 11:04:59.000 AM kernel[0]: ACPIBatteryManager: WARNING! fCurrentCapacity > fMaxCapacity. adjusted fCurrentCapacity from 2825, to 2425
4/7/16 11:04:59.449 AM powerd[49]: Failed to read current rating(0xe00002f0)
4/7/16 11:05:29.000 AM kernel[0]: ACPIBatteryManager: WARNING! fCurrentCapacity > fMaxCapacity. adjusted fCurrentCapacity from 2825, to 2425
4/7/16 11:05:29.476 AM powerd[49]: Failed to read current rating(0xe00002f0)

Update FakeSMC.kext (6.19.1406) and ACPIBatteryManager.kext (1.60.5). Attached. - credit to tluck.

FakeSMC.kext.zip

ACPIBatteryManager.kext.zip

 

When plugged in ac power and fully charged, you will still see the ACPIBatteryManager warning still - it's not harmful to your system - unless you have a newly installed battery.  :)

 

Cheers.

Link to comment
Share on other sites

 Share

×
×
  • Create New...