Hervé

Reminder... 1) https://osxlatitude.com/index.php?/forum/161-faqs-tutorials/ 2) Use the forum search facility 3) Read-up existing threads for your compute model Thank you.

https://osxlatitude.com/index.php?/topic/8641-proper-keyboard-layout-recognition-with-voodoops2controller-eg-latitude-e-series/

From El Capitan 10.11.4 onwards, you have to use a specific VoodooPS2Controller. Use Dr Hurt's R4, R5 or R6 that are available in his dedicated thread in R&D->kexts section. Or grab the kext off my E6230 Sierra guide. It's in the published pack.

That's probably because you've not moved to /L/E the kexts that Jake provided you in folder kexts/LE of his fileset. Once you've done that, repair permissions and rebuild cache. After reboot, you should have audio, provided your Clover patches are correct. Clover only applies on-the-fly patches to cached kexts.

Well, that's obviously specific to your computer or (some) desktops. I can't see this work on a laptop where LVDS is built-in LCD.

Just so that we all agree, in Capri FB #3: 03006601 01020402 00000004 00000001 00000060 10070000 10070000 00000000 00000000 00000000 00000000 00000000 05030000 02000000 30000000 02050000 00040000 07040000 03040000 00040000 81000000 04060000 00040000 81000000 you changed 05030000 02000000 30000000 to 04060000 02000000 30000000 and you got VGA out?

Ok, well device PNLF is defined in SSDT-2 but you've not numbered your SSDT files nor configured Clover so that they can all be loaded properly. You have: ssdt.aml ssdt-0.aml ssdt-1.aml ssdt-2.aml ssdt-6.aml Patched SSDT tables usually need to be named in a sequential order (without holes) to be all loaded. If you patch say vanilla ssdt-6.aml, then you need to extract and place all preceding tables in the ACPI/patched folder to load the patched #6. In your Clover config ACPI section, you've correctly set the order for 13 ssdt tables from ssdt to ssdt-0, ssdt-1 all the way to ssdt-12. But: 1) you're not dropping OEM (i.e. the native BIOS tables) 2) you're missing ssdt files, even though vanilla tables So, activate Drop OEM and dump all missing vanilla ssdt tables to ACPI patched.

Can't see no PNLF device in that IOReg. Why do you get in About this Mac->Displays? The picture of a MacBook or a black external screen (I'd bet on the latter). Post your DSDT.

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.