sales

1. If your installation of 10.11.4 did not create a virtual disk for the physical OS (El Capitan) disk, the command may not be relevant. 2. If your EFI partition (Clover boot location) is on the same physical disk as El Capitan partition, Clover installer will only identify the "DISK" and cleverly installs the updates into EFI partition. BTW, r3320 also worked the same way for me. 3. In my case, when the virtual disk existed, Clover installer can only see the virtual disk (and I have only one physical disk), therefore created an EFI holder on El Capitan partition. Cheers

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.

Thanks to tluck on the other site. Use the following command to revert the root volume to a regular volume. sudo diskutil corestorage revert / Now the virtual disk is gone. And I have the good ol' physical disk. This makes Clover installer installs directly into the EFI partition and overwrites only the parts one selected in the installer. No more manual copy afterwards. And only ONE /EFI to maintain. BTW, they just publish a newer version of Clover over at sourceforge.

It seems a trivial question - but I cannot figure out how to install clover directly into the EFI partition This is my partition: Although i have mounted the EFI partition (see above screen), but Clover installer can only see this: When I proceeded, the installer created an EFI folder under El Capitan (which is located under the physical partition of 'Macintosh SSD'). To make clover update take effect, every time I have to manually copy (and replace) BOOT folder and other files over to EFI partition. Did I missed some steps in configuring Clover?

Thank you, Jake. Your fixes worked. I was able to finish the installation.

Yes. EFI_Clover.zip + E7440.zip (with 1920x1080 <-- is this the culprit??)

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