Hervé

Can you post a screenshot of your Energy Savings PrefPane? In the ACPI section of your Clover Config.plist, can you replace your drop of SSDT Table Id Ssdt by SSDT Table id CpuPm?

Did you clear nvram with Terminal command? sudo nvram -c

Moving from Installation Guides to Help & Support section dedicated to Previews and Mojave...

Guys, it's been said for the last 4 years: there is no support for VGA on mobile 4th gen HD4600 and no working patch. The only Haswell laptops that I know of with (natively) working VGA running out of their iGPU were Optimus models fitted with HD4400 iGPU and a discrete nVidia dGPU. For the rest (HDMI, brightness, Sleep/wake), all the necessary items are in JakeLo's pack, available in the above guide link. I suggest you all refer to it so that we do not re-invent the wheel on and on. Regarding the card reader, the required patch is already included in the patched DSDT of the pack. What more can we do or say?

Whilst I can appreciate you worked hard on getting your Hackintosh up and working, your Clover folder remains nevertheless a pile of crap. Sorry if that upsets you but that's the way it is. This does not mean that your "work sucks"; only your Clover folder does. We have guides and fully developed/fully tested Clover packs available here: Your published Clover folder, aside from being incomplete due to missing ACPI folder, contains many kexts that are useless and irrelevant to the E5440. Same with the Clover config file: many useless and irrelevant settings. For instance, the following kexts are good for the bin: ApplePS2SmartTouchpad -> wrong kext (for Elan/FocalTech/Synaptics touchpads), you should be using Dr Hurt's kext for ALPS touchpads (VoodooPS2Controller R6 or later - see the relevant R&D subsection) EFICheckDisabler -> not required IntelGraphicsDVMTFixup -> useless on anything older than Broadwell NullCPUPowerManagement -> inappropriate since full CPU power management is available once you generate your own CPUPM SSDT using Pike R Alpha's well-known generator. This kext also prevents Sleep to work since it basically disables CPU power management. nVidiaGraphicsFixup -> useless since, according to the Config.plist, you run on 4th gen Intel HD4600 (or related) graphics WhateverGreen -> useless, this is for AMD dGPU XHCI-200-series-injector -> useless XHCI-300-series-injector -> useless XHCI-x99-series-injector -> useless RealtekRTL8100 -> useless RealtekRTL8111 -> useless VoodooTSCSync -> useless which makes a total of 12 useless kexts out of 20 and all are being injected according to your Clover config file... To top it all: No Rehabman's FakePCIIDxxxx kexts -> do you really have things like graphics acceleration on iGPU or USB3.0 ports running ? No battery management kext -> do you have battery monitoring working? No audio patching kext -> do you have audio working? Now on the Clover configuration side: no ACPI folder in your Clover EFI folder. Unless that's a deliberate removal on your part in your uploaded contents, you're not injecting any patched DSDT and SSDT. ACPI: lots of ACPI patches are not even required, too many to list them all here Boot: some strange activation of useless parameters, like npci=0x2000 Devices: no faking of desktop HD4600 id 0x0412 Graphics: you activated "Inject Intel" but specified no Azul layout-id at all. Layout id 0x0a260006 is required here Kernel Patches: you've activated useless and irrelevant patches such as Kernel CPU, Kernel LAPIC or AppleIntelCPUPM Kexts patches: many unnecessary patches and missing patches in that list, too many to list them all here SMBIOS: nothing in your Config file (may be you deliberately removed this) but MBP11,1 is the target profile System parameters: you inject Clover's kexts but you ought to change that to "Detect" especially if, as I can only suspect, you've installed add-on kexts to /S/L/E and/or /L/E. I totally realise you meant well and only wished to provide some help but I have to recommend E5440 owners to stay away from your folder. It's confusing junk. I invite you to download the E5440_A13 pack posted in Jake's guide and compare. I also invite you to read my E6440 thread where, over the course of time, I've explained how the system should be configured to get the various hardware elements to full operational status. By far and large, most of the information remains relevant to the other E5x40 or E7x40 laptops since they share the same hardware components.

Ouh! That Clover EFI folder sure is incomplete but there's so much stuff in that kexts folder that should not even be there! And that Clover config file! That definitely never came from here... Did you just throw things in there as a cocktail experiment and just got lucky the Hack booted macOS?

Anything set in nvram that would overwrite the settings?

It's an O2 SD card reader so please apply the well-known DSDT patch to the associated device that you'll have to identify in IOReg. Hint: look for a device carrying PCI vendor id 1217 (pci1217,xxxx)...

The destination folder for the patched kext is clearly stated in the thread you got it from... This being said, you don't need the patched kext as long as you activate Clover's AppleIntelCPUPM patch. Nothing new on that front, it's been like that for years, more or less since Clover's inception. Just make sure you use Clover's r4517 or later. Black screen may be linked to nVidia GPU if your laptop is the dual GPU model. But you dId not say. Please add your system's specs to your signature.

Consult the built-in manual pages if you need information on the pmset command: man pmset

Apply the usual HDMI patch:

It's much better to post a zipped copy of your Clover config and/or EFI folder than dump a long text copy that very few will bother to read... Your post was moderated to add a spoiler. Coming back to your AICPUPM issue, you should not need the patched version for Sandy/Ivy Bridge since this is usually only applicable to laptops. What you probably need to do is install or inject a TSCSync kext applicable to your SB EP Xeon CPUs so that all cores TSC are synchronised. https://www.insanelymac.com/forum/topic/323366-voodootscsync-configurator-create-a-custom-version-of-voodoo-tsc-sync/

Use Clover Configurator app. FixHeaders is an option in ACPI tab/section.

Everything is stated in post #1...

In case questions on GPU list surface, native compatibilty with Metal starts at: Intel : Ivy Bridge HD4000 nVidia: Kepler (from GT6xx/7xx) and limited to it (no support for Maxwell or Pascal). AMD: CGN 1.0 (from R7)

"Wake down"? As in "sleep" ?

You can look at the documentation for your computer model on HP's web site, especially the spare parts catalog where all supported devices are listed. You can also scrounge the Net.

Beta1 installs in the exact same manner as High Sierra. The difference is that 10.14 requires Clover r4517 or higher to install successfully. https://github.com/Dids/clover-builder/releases So far, Ok on my Ivy Bridge/HD4000 Latitude E6230 with same EFI/bootpack as High Sierra 10.13 and Clover r4521. I made a quick and basic, not fully tuned, installation: Apple stated that Mojave will only support GPUs compatible with Metal so HD3000 and older 1st gen Intel HD graphics are effectively dropped (and there are no kexts for these). Support for Intel iGPUs now starts at Ivy Bridge HD4000. So, I won't be trying Mojave on my E6220 nor on my ancient D630 (support for nVidia Tesla architecture dropped too)... We'll see if this gets to evolve in the following beta versions but not much of a hope I guess. APFS conversion seems to be mandatory too. Despite my modification of the minstallconfig.xml file of the 1st reboot temporary installation in which I had set the ConvertToAPFS parameter to false, my target Mojave partition ended up converted! Not a problem in itself on my SSD (and APFS is reportedly Ok on mechanical HDD now) but that means a definitive goodbye to Chameleon/Enoch for the time being. Inescapable eventuality I guess... List of officially supported Mac models is as follows (as per /S/L/CoreServices/PlatformSupport.plist) MacPro6,1 iMac17,1 iMac16,2 iMac16,1 iMac15,1 iMac14,4 iMac14,3 iMac14,2 iMac14,1 iMac13,3 iMac13,2 iMac13,1 Macmini7,1 Macmini6,1 Macmini6,2 MacBookPro12,1 MacBookPro11,5 MacBookPro11,4 MacBookPro11,3 MacBookPro11,2 MacBookPro11,1 MacBookPro10,2 MacBookPro10,1 MacBookPro9,2 MacBookPro9,1 MacBook9,1 MacBook8,1 MacBookAir7,2 MacBookAir7,1 MacBookAir6,2 MacBookAir6,1 MacBookAir5,2 MacBookAir5,1

Ever thought of checking the FAQ section? ...

'probably needs a patch of the Azul FB kext to set your DP-associated display port to DP or HDMI connector-type...

And apply the patch for the final stage boot glitch (your last attachment):

It's pretty obvious that all HD3000 are affected one way or the other by these graphics glitches. Increasing RAM (from 4 to 8GB for instance) reduces the issue to some degree as does HD3000 kexts patching. But it's quite clear that there is no definitive fix and the glitches remain no matter what, unless you wish to downgrade to Yosemite or earlier of course...

I have not looked at it but does your patched DSDT inject "Darwin" OS at all? It should have something similar to this: Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (0x07D0, OSYS) If (CondRefOf (\_OSI, Local0)) { If (_OSI ("Windows 2001")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP1")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP2")) { Store (0x07D2, OSYS) } If (_OSI ("Windows 2001.1")) { Store (0x07D3, OSYS) } If (LOr (_OSI ("Darwin"), _OSI ("Windows 2006"))) { Store (0x07D6, OSYS) } If (_OSI ("Windows 2009")) { Store (0x07D9, OSYS) } } The original DSDT only has this: [...] If (_OSI ("Windows 2006")) { Store (0x07D6, OSYS) } [...] If your DSDT does not inject "Darwin", you'll see something like this in SysProfiler: Once "Darwin" is injected, you should see something like this: If your DSDT already carries this patch, I'd try and remove those XHC patches you have in Clover. I've noticed that you're also using MBP10,1 SMBIOS. Did you give MBP9,2 any try?

I always wondered about the BIOS version-related graphics corruption on our E6x30 laptops, especially as, in the case of the E6230, the video OROM carries the same version 2.1.3.7 between BIOS A11 and latest version A19. So, I upgraded to A19 and re-patched A19's raw DSDT table. The E6230 boots without any graphics corruption and the laptop works as great as before and without any graphics issues so far. The well-known graphics corruption is only seen on closing screen when restarting or shutting down OS X/macOS. DSDT_A19.aml.zip I'd have to check if the same applies to post-A11 versions like A12 or A13 to see if the issue can be isolated to re-using a patched DSDT from an earlier version...

I noticed that, after upgrading BIOS to latest version A19, if the E6230 booted to black screen and then went rapidly into sleep, I had no graphics corruption on wake. I therefore extracted A19's raw BIOS tables and re-patched the DSDT. I'm pleased to say that my E6230 can now boot without issue with the latest BIOS version. Copy attached below. DSDT_A19.aml.zip Patches applied: iGPU device renaming from VID to IGPU + injection of _DSM method for layout-id injection of PNLF device injection of AC device injection of IMEI device renaming of SD card reader device to SDXC + injection of compatibility with Apple's own reader renaming of WLAN mini-PCIe device to ARPT injection of _DSM methods in GLAN + EHCx + XHC devices injection of _DSM_method to HDEF device for codec id injection of power settings to EHCx and XHC devices injection of "Darwin" OS to _INI method to support USB3.0 injection of IRQ NoFlags to HPET device revamping of _PWR methods to USB devices (EHC, XHC, USB)