Hervé

Maybe your DSDT has no PNLF device defined. Try and add one as explained here.

Only install a kext ONCE. Either in /L/E or in /S/L/E but not in both.

How do you check if your soup is hot? Here's a hint: your SysProfiler and https://osxlatitude.com/index.php?/topic/8431-ssd-benchmark-results/

Install the dummy kext for IDT 92HD90 codec in /L/E, repair permissions and rebuild your cache. It's available off most E6x20/E5x20 guides. Then edit your Clover config.plist to add the IDT 92HD90 on-the-fly binary patches for AppleHDA. Details of the patch are available in all Clover-based guides for E6x20/E5x20 guides.

You obviously have the nVidia model. It would appear you used the pack for HD3000 model only. Use the El Capitan E6420 NVS pack.

I will not update my research thread/pseudo guide with the info you wish to add about USB keys simply because it's not universal at all. Not all USB keys are equal and I was able to use several 8Go and 16Go USB keys on the Vostro (and other computers) without issues. I have too experienced issue with larger 32Go keys that I found incompatible with GPT scheme whilst others were Ok. That's for that. As for updating my thread, well my Vostro OS X HDD died several years ago and since I was hardly using it, I've never bothered to replace it. I turn that old desktop on maybe once or twice a year to print something from the Win7 installation. Same with the even older Precision 670. I keep them for symbolic reasons and only use laptops these days.

If you suspect a CMOS reset by the OS, there are 2 things you can try: 1) patch your DSDT RTC device from: Device (RTC) { Name (_HID, EisaId ("PNP0B00")) // _HID: Hardware ID Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings { IO (Decode16, 0x0070, // Range Minimum 0x0070, // Range Maximum 0x01, // Alignment 0x02, // Length ---> Set to 2 by default ) }) } to: Device (RTC) { Name (_HID, EisaId ("PNP0B00")) // _HID: Hardware ID Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings { IO (Decode16, 0x0070, // Range Minimum 0x0070, // Range Maximum 0x01, // Alignment 0x08, // Length ---> Changed to 8 ) }) } 2) Install the pre-patched AppleRTC kext You may try either/or as well as both at the same time but it may not fix your issue.

If you have a Latitude E6430 with nVidia GPU, I'd advise against using the patched BIOS table of the Latitude 6430u. These may be close but remain different laptops.

Hmm, try that: DSDTtest_RV.aml.zip

Seems Ok but you're injecting the following ids to your USB2.0 + USB3.0 controllers: "subsystem-id", Buffer (0x04) { 0x70, 0x72, 0x00, 0x00 }, "subsystem-vendor-id", Buffer (0x04) { 0x86, 0x80, 0x00, 0x00 }, I Just don't at all. Use FakePCIID_XHCIMux as suggested by Jake.

Post your DSDT, I'll compare it with my E6440 patched table.

@kfiatos: did you patch your DSDT USB controllers with power management code? @Alex Rivera: one way to fix the iTunes movies issues is to use the Shiki kext. Known to fix green screen problems on Ivy Bridge and can also fix issues on Haswell iGPUs.

The question keeps propping up now and then, so I hope this dedicated thread can provide the direct answer to this FAQ which has been given several times before. There is a known bug in Chameleon/Enoch that can prevent booting modern/recent HDDs formatted with a 4k sector and on which Chameleon/Enoch was installed with default boot file settings.The issue can be fixed by installing the boot1h Chameleon boot file to your HDD's OS X/macOS partition. The USB installer key will be required to fix the problem as follows: copy the attached Chameleon/Enoch i386 folder to the root of your USB key (this i386 folder can be extracted off any Chameleon/Enoch installation package with Pacifist app) boot the USB installer and get to the main OS X/macOS installation screen open up Disk Utility through the Tools menu and take a note of the partition device name (e.g.: disk0s2 or disk0s3). Unmount the partition and close Disk Utility. An alternative is to use df or diskutil list Terminal commands. open up Terminal through the Tools menu. type the following command to copy the boot1h file to the Sierra partition: dd if=/i386/boot1h of=/dev/ exit OS X/macOS installer and reboot You should now be able to boot your OS X/macOS partition without problems. i386.zip

Intel i5-2400 CPU carries integrated HD 2000 graphics. OS X does not support Intel HD 2000 at all so Yosemite is probably hanging at attempts to intialize graphics. You can always boot in verbose mode to check that out. All in all, you'll have to install a supported discrete PCIe x16 card in that desktop (depending on model) or replace your Sandy Bridge CPU with Intel HD 3000 that's compatible with your Optiplex 990. Look up the Optiplex specs and the Intel Ark site (Intel i5 2400 Series, Intel desktop Sandy Bridge CPUs). With regards to a discrete PCIe x16 graphics card, the mini tower model supports full-height cards, the desktop and SFF models support only low-profile cards and the USFF model has no expansion slots other than a mini-PCIe slot for half-height cards (wlan), i.e. you can't add a graphics card.

Nothing, the card either supports it or doesn't and the Radeon HD 6670 does. It's more a matter of drivers and apps. You can run tools like OpenGL Extensions Viewer (free off AppStore) or others to check out your card's capabilities. OpenCL usage largely depends on apps that call onto it. https://support.apple.com/en-us/HT202823

You take out the old card, plug the new one in and reboot without cache. If the new card is supported, it'll work OOB or after any necessary tuning (DSDT dGPU injection or patch adjustments, AMD FB patching, etc.).

To begin with, please post your specs in terms of: 1) LCD screen resolution 2) Pack used You also need to ensure that the SSDT you might have used was for your specific i5-3340M CPU. If in doubt, you can grab the SSDT off my E6230 guide, my E6230 has that same CPU.

Last updated: 16 Mar 2019 O2 Micro SD card readers known to work with above DSDT patch (non-exhaustive list): 1217:8221 (fitted to Latitude E5x20/E6x20, E5x30/E6x30) 1217:8231 (fitted to Latitude E5x20/E6x20, E5x30/E6x30) 1217:8520 (fitted to Latitude E5x40/E6x40/E7x40, E5x50/E7x50, Precision M6800) 1217:8621 (fitted to Lenovo Y520/Y720/E470/L560) Ricoh SD card readers understood to work with above DSDT patch (non-exhaustive list) - /!\ unconfirmed info /!\: 1180:e822 (fitted to ThinkPad T430, Latitude E6x10) 1180:e823 (fitted to ThinkPad T420/T430) To be updated as more info comes along...

Although they're closely related, the Latitude 6430u and Latitude E6x30 do differ. I'm not sure their DSDT are interchangeable. You could have re-used the E6430 pack from El Capitan. Granted the pack is listed for the HiRes LCD model but this can be adjusted to fit the LoRes LCD by changing the DSDT IGPU _DSM method where you change: ig-platform-id from 0x01660004 to 0x01660003 DualLink from 1 to 0 To be on the safe side and actually contribute towards a proper E6330 pack, maybe you could actually extract the E6330 raw tables from BIOS and post them. You can extract them by pressing F4 at the Clover menu and you'll find them in the ACPI/origin folder of your EFI partition. This old E6330 Mavericks guide has an Extra pack with a DSDT with which you could compare. For Bluetooth and wifi, well it all depends on the hardware fitted to your E6330. Latitude E6x30 models tend to be fitted with DW380 bluetooth module and that works Ok as described in my E6230 guide. You may also install Rehabman's BrcmXXXX kexts as an alternative to the IOBluetooth PlugIn patch. TouchPad will work perfectly with Dr Hurt's latest VoodooPS2 kexts (I can vouch for his versions 4 and 5) which are available in post #1 of his dedicated thread in R&D->Kexts subsection. Don't use E6x20 guides as reference because these are SandyBridge models, not IvyBridge. Whilst the E6x20 and E6x30 share some hardware components (e.g.: LAN card), they're nevertheless different, especially on key components such as graphics (HD3000 vs. HD4000), audio (IDT 92HD90 vs. IDT 92HD93) or USB (2.0 only vs. 2.0/3.0). NB: there's no support for HD4000 VGA output on these computers.

MacFace, please avoid posting the exact same message into every possible thread you found about your particular laptop model of interest. Double multiple posting tends to lead to the opposite effect you desire... So, since you seek that much attention for your trouble, your post was split into its own thread. Pending eventual answers, I invite you to read those other E6500 threads you found + existing El Capitan guides for the E6xxx series.

As just advised in a similar thread for macOS Sierra, Skvo's Yosemite kext cannot be re-used in El Capitan because references in CellPhoneHelper's Info.plist are different in El Capitan. Some parameters have different names/syntax. As such, Skvo's kext must be modified to take the new syntax/references of El Capitan into account. Lines such as those listed in the other Sierra-related thread must be modified to adopt the same syntax used in El Capitan's version of CellPhoneHelper kext.

Try this revised version modified for macOS Sierra 10.12. Let us know how it goes. Legacy_Sierra_QMI_10.12.kext.zip

Probably not. E6x30 suffer graphics corruption with HD4000 beyond certain BIOS versions (around A11/A12/A13), I can't remember for your exact model. You can search the forum for this, it's mentionned many times.

Skvo's thread clearly indicates: "I did Legacy collaboration with the driver CellPhoneHelper.kext Legacy_Sierra_QMI.kext for OS X 10.10.x" You have to look into the kext he posted and apply a similar patch to macOS Sierra's CellPhoneHelper kext. Apple has a tendency to modify kexts related to WWAN modules, USB or Bluetooth from one OS X/macOS version to another... In particular, you'll find the syntax used in the Info.plist file differs and that renders patches or patched kexts for a given version unusable in the next one. In the specific case of CellPhoneHelper kext, if you look at the various hardware profiles listed in the Info.plist, you may notice the following: Yosemite 10.10 version: <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleUSBMergeNub</string> <key>IOClass</key> <string>AppleUSBMergeNub</string> <key>IOProviderClass</key> <string>IOUSBDevice</string> or <key>OSBundleLibraries</key><dict> <key>com.apple.driver.AppleUSBMergeNub</key> <string>2.5.7</string> <key>com.apple.iokit.IOUSBFamily</key> <string>2.5.7</string> ` Sierra 10.12 version: <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleUSBHostMergeProperties</string> <key>IOClass</key> <string>AppleUSBHostMergeProperties</string> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> or <key>OSBundleLibraries</key> <dict> <key>com.apple.driver.AppleUSBHostMergeProperties</key> <string>1.0</string> <key>com.apple.iokit.IOUSBHostFamily</key> <string>1.0.1</string> ` If you have the wrong syntax or wrong references, the kext/patch will not work. This is why Skvo's Yosemite kext cannot work under El Capitan or Sierra.

No modem software means it's not fully enabled. Make sure the Legacy_Sierra_QMI kext you use is based on the macOS Sierra version of CellPhoneHelper, not a version from a previous OS X release. The kext posted by Skvo in May 2015 was of Yosemite origin... You run macOS Sierra, right?