Hervé

KP=Kernel Panic -> means system crash.

Check that you have: 1) the Extra folder at USB installer root and that it contains the kernel + org.Chameleom.Boot + smbios plists & the correct kexts in Extensions subfolder (FakeSMC, VoodooPS2Controller and NullCPUPM being mandatory to begin with) 2) that the kernel.plist file does contain the parameter KernelBooter_kexts set to Yes

You may look here. Very complete and up to date general guide afaik.

A few things to do on your USB installer: remove the SSDT provided in the bootpack from /Extra (it's for a i5-3340M and unsuitable for your i5-3320M) if it's missing, add the attached NullCPUPM kext to /Extra/Extensions folder reboot NullCPUPowerManagement.kext.zip

BIOS version and CPU model? Post a (1024x768) picture of General->System Information BIOS page.

You've got your answers above. Please read them.

Again, please read and follow the guide! The guide clearly states it applies to the E6230 fitted with i5-3340M CPU (CPU-specific SSDT in the bootpack). For other CPUs: Did you read that too?

As stated in the guide: It'd please me if you could read the guide with a little more attention... I made every effort to post an orderly step-by-step procedure and every step is required.

As stated in my previous above, USBInjector is of no help for your issue. It's your DSDT...

You might have been, yes... I'd restore them if I were you. Looking at the DSDT (dated May 2016) you posted on May 24th, one will notice that none of your EHCx or HDEF devices have the usually required _DSM method that defines power settings and is required for sleep. I would suggest you add this to the DSDT devices. You'll find details of the code all over the forum. Here for instance. If, after that, you still have issues like instant wake, you may adjust the _PWR methods for those given devices. All according to info posted by Rehabman on his blog. Re: USB injector, it's used to get USB ports to work (be recognised), not really for sleep or wake. The SMBIOS you use must match the model configured in the USB injector and the ports specified in the injector must match those defined in the DSDT... The injector kext posted above would gain by being substantially optimised (read: remove all unnecesary entries). Look here for details re: creation of an adequate and optimised USB injector.

Please follow the guide more carefully... NB: Go easy with size when it comes to picture attachments!

Last update: 15 Nov 2020 Here are BIOS settings that are known to work on the E6230 (Intel Ivy Bridge CPU with Intel HD4000 graphics) under Mavericks, Yosemite, El Capitan, Sierra, High Sierra, Mojave, Catalina and Big Sur. These settings were tested and verified with BIOS up to A20. Boot Sequence: . Diskette drive = Off . Internal HDD = On . USB Storage Device = On . CD/DVD/CD-RW Drive = Off . Onboard NIC = Off . Boot List Option = Legacy for Chameleon bootloader/UEFI strongly recommended for Clover System Configuration . Integrated NIC = Enabled . Parallel Port = Disabled (you may opt for any other options if required) . Serial Port = COM1 . SATA Operation = AHCI . Drives: * SATA-0 = On * SATA-4 = On * SATA-5 = On . SMART Reporting: * Enable SMART Reporting = On or Off . USB Configuration: * Enable Boot Support = On * Enable External USB Port = On . USB PowerShare: * Enable USB PowerShare = On . Unobtrusive Mode: * Enable Unobtrusive Mode = Off . Keyboard illumination = Level is 100% or any other settings. This applies to backlit keyboards only . Miscellaneous Devices: * Enable Microphone = On * Enable eSATA Ports = On * Enable Hard Drive Free Fall Protection = On * Enable ExpressCard = On * Enable Camera = On * Enable Media Card = On Video: . LCD Brightness = Max or whatever settings you prefer . Dynamic Backlight Control = Disabled highly recommended Security: . Admin Password = not set . System Password = not set . Internal HDD-0 PW = not set . Strong Password = Off . Password Configuration = default settings . Password Bypass = Disabled . Password Change: Allow Non-admin Password Changes = selected . Non-Admin Setup Changes = Off . TPM Security = Off . Computrace (R) = Deactivate . CPU XD Support = enabled . OROM Keyboard Access = Enable . Admin Setup Lockout = Off Secure Boot: . Secure Boot Enable = Disabled . Expert Key Management: * Enable Custom Mode = Off * Custom Mode Key Management = PK Performance: . Multi Core Support = All . Intel (R) SpeedStep = Enabled . C-States control = On . Intel (R) TurboBoost = Enabled . HyperThread Control = Enabled . Rapid Start Technology = Disabled Power Management: . AC Behavior: * Wake on AC = Off . Auto On Time = Disabled . USB Wake Support = Off . Wireless Radio Control: * Control WLAN radio = Off * Control WWAN radio = Off . Wake on LAN/WLAN = Disabled . Block Sleep = Off . Primary Battery Charge Configuration = Express Charge (or any other choice) . Battery Slice Charge Configuration = Standard (or any other choice) . Intel (R) Smart Connect Technology = Off POST Behavior: . Adapter Warnings = Enabled . Keypad (Embedded) = Fn Key Only . Mouse/TouchPad = Touchpad/PS-2 Mouse . Numlock Enable = On . Fn Key Emulation = On . POST hotkeys = Enable F12 Boot Option Menu . Fast Boot = Minimal Virtualization Support: . Virtualization = Enabled . VT for Direct I/O = Off (otherwise use Chameleon/Clover option dart=0) . Trusted Execution = Off Wireless: . Wireless Switch: * WWAN = On * WLAN = On * Bluetooth = On . Wireless Device Enable: * WWAN = On * WLAN = On * Bluetooth = On

My guide is applicable to BIOS in legacy mode. Ensure you've setup your BIOS according to the recommended settings. No merge for the Extra folder. Copy it "as is", replacing any existing folder.

Tried this guide?

VGA output is supported OOB throughout the D630/D830 nVidia models. Just plug and play... You can search the forum (and its archive) for old threads related to VGA output on the D Series; the matter was quite extensively discussed between 2011 and 2013.

Unrelated to Dell Latitude D8xx, so topic moved to Intel-based systems section.

I edited and compiled the above DSDTs with MacIASL, make sure you have a recent version of the app.

https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/

USB, Ethernet and video outputs all work Ok. Audio ports don't appear recognized.

The E6420 BIOS settings & options should look very much liked those of the E6220. https://osxlatitude.com/index.php?/topic/8281-e6220-bios-settings/ You can also refer to my Chameleon/Enoch-based E6220 guide as an alternative to Jake's Clover-based guide. The process remains identical between all E6x20 models and most files are useable on all models. You only need to adapt DSDT if using a high res LCD.

Ha, that's different from the description you gave before. I understood your laptop went to sleep Ok but just woke to dark screen. Assuming you configured hibernation mode to 0, what you'll probably need here is a DSDT patch... None of your EHCx/XHC USB devices or HDEF audio device appear to have the (usually) required _DSM method: Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x0B) { "AAPL,current-available", 0x0834, "AAPL,current-extra", 0x0898, "AAPL,current-extra-in-sleep", 0x0640, "AAPL,max-port-current-in-sleep", 0x0834, "AAPL,device-internal", 0x02, Buffer (One) { 0x00 } }) } Try either of the attached patched DSDT tables. The 1st one includes the above patch in EHCx, XHC and HDEF devices; the 2nd one has same + _PWR methods removed. DSDT01.aml.zip DSDT02.aml.zip

I don't believe these log messages are an issue. If you end up with a booted OS X with full QE/CI, then consider things work.

Well, if layout-id 01660009 is the only one that seems to give your graphics acceleration, I guess that's what you should stick with. Regarding black screen on wake, you could try and use boot option darkwake=0 to see if it makes any difference.

What resolution is your built-in LCD screen?

You're not the 1st one to do this but do not confuse your hardware id + revision id with graphics FrameBuffer layout id. It's not the same at all. Just because you have an HD4000 GPU with hardware id 0166 and revision 9 does not mean you use HD4000/Capri layout-id 0x01660009. Far from it, but it does not mean that it should not either... Many (most?) IvyBridge Hackintosh laptops with HD4000 graphics will actually use layout-id 0x01660003. Look at my E6230 for instance (i5-3340M CPU)... SysProfiler shows device id 0166 with hardware revision 9, but we use layout-id 0x0166003 in the DSDT: Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x04) { "AAPL,ig-platform-id", Buffer (0x04) { 0x03, 0x00, 0x66, 0x01 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) }