sales Posted April 4, 2016 Share Posted April 4, 2016 (edited) 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. Some tweaks: powerd failure https://osxlatitude.com/index.php?/topic/8922-solved-e7240-10114-fresh-install-boot-problem-kernel-panic/?p=59260 Cheers Edited April 8, 2016 by sales Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted April 4, 2016 Moderators Share Posted April 4, 2016 Are you using the E7440 bootpack? Link to comment Share on other sites More sharing options...
sales Posted April 4, 2016 Author Share Posted April 4, 2016 Yes. EFI_Clover.zip + E7440.zip (with 1920x1080 <-- is this the culprit??) Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted April 4, 2016 Moderators Share Posted April 4, 2016 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 More sharing options...
sales Posted April 5, 2016 Author Share Posted April 5, 2016 Thank you, Jake. Your fixes worked. I was able to finish the installation. Link to comment Share on other sites More sharing options...
robertostudios Posted April 6, 2016 Share Posted April 6, 2016 One problem! This kext works fine, but i put the system sleep (close the lid) and wake, instant reboot Every time... Old voodooPS2 without touchpad plugin works fine! Any updated 100% working kext? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted April 6, 2016 Moderators Share Posted April 6, 2016 Sorry, try this one. Link to comment Share on other sites More sharing options...
robertostudios Posted April 6, 2016 Share Posted April 6, 2016 Same kernel panic and instant reboot Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted April 6, 2016 Moderators Share Posted April 6, 2016 Hmm, ok, I guess will have to use a generic ApplePS2Controller for now than. Link to comment Share on other sites More sharing options...
sales Posted April 7, 2016 Author Share Posted April 7, 2016 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 More sharing options...
Recommended Posts