drjibe

I did use your files but yes, I added the lspcidrv.kext to get the card reader working (I can probably remove the kext now that modified the VoodooSDHC.kext so that it works). Anyway, the cause was a rather simple/stupid error: for some reason the clover configurator was set to MacBook8,1 (made sense with the e6220 having an i5 rather than an i7). Anyway, setting it to 8,2 and voilà : USB ports work, webcam works. Thanks for your patience, Jake. I really appreciate it!

I'm not aware that I modified the IOAHCIBlockStorage but I replaced it with a vanilla version off of a MacBook Pro running 10.11.1 - still the same output when regenerating the cache though. As for USB, the system report claims that there are two USB 2.0 buses. However, none of the USB ports seem to be working (I hadn't noticed earlier).

Thanks, got the SD card reader to work following this guide! However, webcam is still a no go. Here is the output from resetting permissions and rebuilding the kextcache $ sudo ./permission.sh Password: rebuilding //System/Library/PrelinkedKernels/prelinkedkernel kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IOAHCISerialATAPI_Injector.kext kext file:///Library/Extensions/DisableTurboBoostBattery.kext/ is in hash exception list, allowing to load kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAIDT.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooSDHC.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext lspcidrv.kext AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion. AppleDataSetManagement.kext is missing dependencies (including anyway; dependencies may be available from elsewhere) AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion. kextcache updated critical boot files, requesting launchd reboot Finished Do you have any other ideas?

I have El Capitan running with Clover as a boot loader using this guide Dell Latitude / Inspiron El Capitan Clover Guide. Before that I ran Yosemite for a few days with Enoch. With Yosemite, the webcam worked. Now, the webcam doesn't work anymore. Also the card reader doesn't work (not sure if it did with Yosemite). Is this a known issue or is there a way to fix it? I do not really desperately need either of these two but it'd be nice to have a system where everything works

Thanks, Jake. Got sound working and also the security update. As it's been a while since I fiddled with hackintoshes, I didn't pay attention to the AppleIntelCPUPowerManagement.kext and ran into a kernel panic after installing the update. Got that sorted. Everything seems to be working, even sleep/wake when closing/opening the lid. But after having let the puter sleep for a little longer, it apparently "woke" up by itself (power button was constantly glowing) but it didn't react to any keyboard, power button entry whatsoever. Let's see if that keeps on happening. Again, thanks for great guides and help!

Mleh, fixed it. It was this "diskutil cs list" thingy. https://osxlatitude.com/index.php?/topic/7478-dell-latitude-e6xxxe7xxx-yosemite-install-guide/?hl=+e6220%20+yosemite Now, I only need to get sound working and figuring out whether or not to run the security update.

Hi, I installed Yosemite following hervé's guide from here https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-intel-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemite/&do=findComment&comment=49907 and everything seems to be working except for one annoying thing: I can only boot from the USB installer stick and then select the OS X hard drive. If I remove the USB stick it doesn't "see" the Chameleon boot loader on the internal hard drive. I first tried r2468, then r2716, then Enoch r2795 but to no avail. Any ideas what might be causing this or what I need to do? The internal HD is a 128gig SanDisk SSD if that should matter. And also one final question: is it safe to install the latest security update 2015-004 that the app store suggests to install? Any special way of going about it? thanks jibe