Hervé

If you messed around with kexts, try and undo what you last did before it broke. Check for double kexts in /S/L/E and /L/E or trying moving kexts around. Cache kexts instead of injecting them. Sometimes, that's the solution.

Repair /S/L/E + /L/E permissions and rebuild you cache to begin with.

I assume that when Optimus is disabled, only integrated HD3000 is active. In that case, it's very simple: patch the SNB frame buffer as per indicated in EmlyDinesh's HD3000 patching guide in R&D->Graphics section or in my E6320/E6220 posts on the matter: https://osxlatitude.com/index.php?/topic/8278-e6320-with-hd3000-booting-yosemite-with-dell-docking-station/ https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemiteel-capitansierra/&do=findComment&comment=52237 https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemiteel-capitansierra/&do=findComment&comment=57882 Once you've patched the SNB framebuffer kext, use IORegistryExplorer to identify the port number associated with each DVI output of your docking station, i.e. plug the cable and check your IOReg frame buffers under the iGPU section. You may have to adjust your patch according to your findings. I'll try and test my E6220 with an E-Port Plus (the dual-DVI model) port replicator later on.

Re: audio, a quick search on any Exx40 and ALC292 will give the answer. For instance: https://osxlatitude.com/index.php?/topic/9234-e7440-alc292/?hl=alc292

Use Dr Hurt's PS2 Controller (R4, R5 or R6). If you scrounged the forum for 3 days, you should have find out by now, especially as you pinpointed out the problem in EC the 1st time....

Yes, as its name implies, Patched_10.7_AppleRTC is meant for Lion 10.7. https://osxlatitude.com/index.php?/topic/9325-patched-applertc/

You'll find those in all guides posted on the forum or through a basic Google search... FakeSMC is THE mandatory kext on all Hackintoshes across the board. PS2 controller kexts depend largely on the model of TouchPad fitted you your tablet PC (e.g.: ALPS, Synaptics, ELAN, etc.) so you may have to use USB keyboard and mouse to begin with. If your laptop runs Windows at present, you can try and identify your hardware components through tools readily available (Windows Device Manager, CPU-Z, Aida64 or others...). The diagnostics extract you posted appear partial only.

Why do you want to inject kexts through Clover rather than cache them through, say, /L/E (it's for 3rd party kexts since Yosemite)? It's quicker to load cached kexts and Clover applies on-the-fly kexts to cached kexts only, so... NB: normally, kexts placed in /L/E are not loaded when booting without cache. At least with Chameleon/Enoch. Try and boot without cache with a non-mandatory kext placed in Clover kexts folder and see if it gets injected then. For instance a kext for the LAN card, it's then easy to verify behaviour.

None specific to that model. You're going to have to start from scratch with what I gave you above.

That's a similar platform to the 2015 Core M-based MacBook computers (MB8,1). You should therefore be Ok with OS X, starting from Yosemite 10.10.2 (that's what these models shipped with initially). Follow any usual installation guide starting with the usual minimum kexts set (FakeSMC + PS2 controller). Since it's a Broadwell platform with integrated Intel HD5300 graphics, you may have to apply the usual DVMT nvram patch (either modded BIOS or BDW framebufffer patch).

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.