Hervé

DW1560 does not work OOB, it requires patching. You can look this up in our dedicated R&D->Wireless section. Occasionally, TouchPad won't work and may require a few reboots to be recovered. Never really investigated this further because I'm using an external mouse 99% of the time. But feel free to have a go at it.

You change nothing if there is no difference... You may also try that set of patched tables (keep a backup of yours).

That should obviously do. Compare your current DSDT and that of the other member, looking for the PWR methods. Adjust as necessary. Use MaciASL to that effect.

Definitely sounds like a USB-related issue. If your laptop has older USB2.0 controller, temporarily boot with USBInjectAll kext before running Hackintool so that you do not miss any controller/ports.

And you'll find them on the forum if you search correctly in the Wireless section...

Here are BIOS settings that are known to work on the 7250 (5th gen CPU with Intel HD5500 graphics) under High Sierra and Mojave. These settings were tested and verified with BIOS A21. General . Boot Sequence: * Boot List Option = UEFI (-> Boot Sequence list will be set accordingly) . Adanced Boot Options: * Enable Legacy Option ROMs = On (required to boot legacy external devices such as USB media or SD cards) System Configuration . Integrated NIC = Enabled . Parallel Port = Disabled . Serial Port = COM1 . SATA Operation = AHCI . Drives: * SATA-0/1/2/3 = On . SMART Reporting: * Enable SMART Reporting = On or Off . USB Configuration: * Enable USB Boot Support = On * Enable USB3.0 Controller = On * Enable External USB Port = On . USB PowerShare: * Enable USB PowerShare = On . Audio: * Enable Audio = On . Keyboard Illumination: * Bright = On (or any desired value) . Keyboard Backlight on AC: * Keyboard Backlight with AC = On or Off . Unobtrusive Mode: * Enable Unobtrusive Mode = Off . Miscellaneous Devices: * Enable Microphone = On * Enable Camera = On * Enable Media Card = On Video . LCD Brightness = Whatever settings you prefer Security . Admin Password = not set (or whatever) . System Password = not set (or whatever) . Internal HDD-1 Password = not set (or whatever) . Strong Password = Off . Password Configuration = default settings . Password Bypass = Disabled . Password Change: Allow Non-admin Password Changes = on . Non-Admin Setup Changes = Off . TPM Security = Off . Computrace(R) = Deactivate . CPU XD Support = On . OROM Keyboard Access = Enable . Admin Setup Lockout = Off . Master Password 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 SpeedStep = Enabled . C-States control = On . Intel TurboBoost = Enabled . HyperThread Control = Enabled Power Management . AC Behavior: * Wake on AC = Off . Auto On Time = Disabled . USB Wake Support: * Enable USB Wake Support = On or Off . Wireless Radio Control: * Control WLAN radio = Off * Control WWAN radio = Off . Wake on LAN/WLAN = Disabled . Block Sleep = Off . Peak Shift = Off . Dock Support on Battery = Off . Advanced Battery Charge Configuration = Off . Primary Battery Charge Configuration = Adaptative (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 = Enabled . Fn Key Emulation = Enabled . Fn Lock Options: * Fn Lock = On * Lock Mode Disable/Standard = On . MEBx Hotkey = Enabled . Fast Boot = Minimal . Extend BIOS POST Time = 0 seconds (or any other choice) 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/WiGig = On * GPS (on WWAN Module) = On * Bluetooth = On . Wireless Device Enable: * WWAN/GPS = On * WLAN/WiGig = On * Bluetooth = On

No need to specify "inject Intel" + layout-id in the Graphics section of your Clover when you run with recent/latest Lilu + WEG kexts.

Looking good overall. I would just say that if you're dropping SSDT CpuPm + SSDT CpuI0st and injecting the CPU PM ssdt table, then you should not have PluginType parameter checked. It's either or. But that should not impact battery life in any way. I did not see anything relating to a dGPU so I can only presume there is none and your config is optimum as far as CPU power management and battery life is concerned.

I don't have any E5450 at hands but I have an E7250 until the end of the week. I don't have a mini-DP cable and a DP screen for testing but I can try DP output through my E-Port dock out to HDMI via an adapter. You may need to change the default FB #/port# of the BDW frame buffer for your DP output port to work although it's unlikely. You use BDW layout 0x16260006 which defines the following output ports: 06002616 01030303 00002002 00005001 --> layout 0x16260026, 3 x output ports 00000060 D90A0000 D90A0000 00000000 00000000 00000000 00000800 02000000 30020000 --> FB #0/port #0, built-in LCD 01050B00 00040000 07050000 --> FB #1/port #5, DP output (but usually HDMI port) 02040B00 00040000 07050000 --> FB #2/port #6, DP output Looking at your posted IOReg outputs, I can clearly see your external display attached to FB@2/port #6. As such, I guess your problem is highly likely to be a 4K-related problem more than anything else. I don't have a 4K screen myself so I've never had any 4K-related issue to resolve but I believe the issue of black screen on 4K displays is quite common. I also understand there is an existing fix (or fixes?) for it, like using boot parameter -cdfon. https://www.insanelymac.com/forum/topic/334899-intel-framebuffer-patching-using-whatevergreen/ Now, looking at the EFI folder of post #1, I could see 2 x Clover config files: config.plist (which is the default name of Clover's config) is empty and therefore I assume you cannot be using it. config_ok_ref.plist contains the following typo in the Graphics properties injection: <key>framebuffer-unifiedmem</key> <data> AAAAgA== </data --> typo! it should be "</data>", the final ">" is missing <key>enable-hdmi20</key> <data> That same typo is also found in the 2 x Clover config files of the EFI folder of your 2nd post... You need to correct this with a text editor like TextEdit or Clover Configurator; whether it'll fix the issues you encounter, that I cannot say for sure but I certainly smell a fish...

Please report your info in the following manner: Card model Hackintosh model macOS versions tested Patch used the successful Kexts used when successful Tricks used when successful If you could not get a card to work, just specify card model, Hackintosh model and macOs version "NOk". We'll assume it just didn't work no matter what. Example: Card: DW1820A, #0VW3T3, 1028:0021 Hackintosh: Latitude 7490 macOS versions: High Sierra Ok, Mojave Ok Patch: "compatible pci14e4,4353" property injection in Clover Kexts: none Boot parameter: none Tricks: none Card: DW1820A, #0VW3T3, 1028:0021 Hackintosh: Lenovo P50 macOS versions: Mojave Ok Patch: "compatible pci14e4,4353" property injection in Clover Kexts: BrcmAirportFixup Boot parameter: brcmfx-driver=1 Tricks: pin-masking

/!\ TOPIC NOW DEPRECATED & CLOSED /!\ By popular demand and building on the guide I wrote for those cards some time ago + the subsequent extended feedback (mostly poor) on users experience, I thought it'd be useful to list those cards and laptops combinations that work or not. People may then opt for BCM450 cards with the best of knowledge. I invite all those who tested such cards to report their conclusions in order to build-up the registry. Important note: This is not a troubleshooting thread, there's already one here. This thread is only to report success or failure stating card model + computer model in order to complete a registry. Non-compliant posts will be deleted without any notice. DW1820A #0VW3T3 1028:0021 DW1820A #0VW3T3 1028:0023 DW1820A #096JNT 1028:0021 DW1820A #096JNT 1028:0022 DW1820A #08PKF4 1028:0023 T77H649 #00JT494 17aa:075a WCBN808B #00JT493 ? Dell Latitude 7490 Y Y Y Y Dell Latitude E7250 Y Y Y Dell Latitude E7450 Y Dell Latitude E7470 Y Dell XPS 9360 Y Dell XPS 9560/9570 Y* Y* Dell Inspiron 7x72/7x60 Y* Dell Inspiron 7460 N N ? Dell 3040 micro Y Lenovo M900 mini N ThinkPad T440p/T440s N Lenovo P50 Y* Intel NUC8I7HVK Y Asus Zenbook UX410UQK Y* Latitude E5570 Y Lenovo R70 Y Acer Swift 3 SF314-54G Y* ASUS UX410U Y Lenovo Air IWL Y* Y* Y* Lenovo Y7000 81V4 Y* ASRock Deskmini 310/COM Y Asrock Z390 Phantom Y Lenovo Thinkpad 450s Y N N * with pin masking Notes: - - - - - DW1820A #08PKF4 1028:0023 reported to work Ok with: pin masking (3pins @front, 2pins/3pins @rear) (there's one report stating masking makes wireless unreliable but Bluetooth work) BrcmAirportFixUp kext brcmfx-driver=1 boot option (or brcmfx-driver=2 to gain Auto Unlock as described here) - - - - - Edit: 06Jan 2020 Further to recent information posted by Hugotai on another forum, it appears that additional device property injection setting pci-aspm-default to 0 fixes all stability issues. Full details of the property injection available here.

Regretfully, I can only agree with JakeLo. These cards only work Ok on a few laptop models.

Try it, there's a power off option in the menu of the Finder's bar EC icon. Will be much simpler than a DSDT/SSDT patch if it works!

An ExpressCard is normally an external add-on card that you insert in a dedicated EC slot. When not used, it's fitted with a 34mm plastic plate, like for SD card readers. I guess this must be linked to the nVidia (Fermi) dGPU I see attached to PCIe root bridge RP05@1C,4 and which is not disabled. Looking at the E5440 documentation available here, I read this:

Sorry for the short off-topic, but what kind of hardware is that in the EC slot?

Erm... that's the icon for an ExpressCard card! You must have a card inserted in the EC slot of your laptop... "Display Controller" is meant to represent what you currently have in place. What is it? My E62x0 laptops will show this when fitted with my GMYLE BC620 USB3.0 EC card.

nv_disable=1 boot parameter only instructs the OS to ignore the nVidia GPU so that no drivers are loaded; but it does not disable the hardware (i.e. turn it/power it off) so the dGPU still draws current off the battery. The dGPU can be disabled through ACPI patching. Can you please take a screenshot for that "display controller icon" ? [CMD][SHIFT][3] or [CMD][SHIFT][4], following by [SPACE] + left button mouse/touchpad click.

User Dr Hurt's VoodooPS2Controller kext r6. Works perfectly on the E6440.

You would need to make up your own "Mojave" legacy QMI kext (in case you wondered, the Sierra part of skvo's kext means Sierra Wireless, not macOS Sierra); any legacy QMI kext made for another OS X/macOS version probably won't do because the inner syntax of the CellPhoneHelper kext it's based on will probably have evolved again. Apple has a strong tendency to change this version after version. Consider the Legacy_Sierra_QMI kext as an injector. All that it does is define a profile for the target WWAN module based on an existing Sierra Wireless module natively supported by OS X/macOS. Obviously, things that you change in your new hardware definition profile are the module's PCI ids. Of course, you still need the CellPhoneHelper kext and make sure you keep this fully vanilla in /S/LE/. An alternative to the Legacy_Sierra_QMI kext is to inject the new profile in FakeSMC. I've detailed this in previous WWAN module threads several years ago.

Target macOS release: Mojave 10.14.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration on Intel HD5500 graphics (with Lilu + WEG) multi-display with DP and HDMI OOB audio, including jack microphone input and headset output (with AppleALC & layout-id 11 + CodecCommander) HDMI audio (with BDW Framebuffer patch) built-in GigEthernet LAN connection (with IntelMausiEthernet kext) wireless and bluetooth with any compatible card/USB dongle integrated webcam (OOB) full CPU power management, including Turbo boost to 2.9GHz (with CPU-specific generated SSDT) sleep (Lid, Energy Saver settings, Apple menu, Fn-F1, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager ) SD card reader (with DSDT patch for compatibility with Apple's default Broadcom device 14e4:16bc) keyboard (with Dr Hurt's VoodooPS2Controller R6 + DSDT patch for brightness control) keyboard backlight OOB (for backlit models) touchpad including tap-to-click (with Dr Hurt's VoodooPS2Controller R6) USB3.0 ports (with Rehabman's USBInjectAll + FakePCIID kexts for multiplexing) Not working: N/A Not tested: SmartCard reader fingerprint scanner GeekBench v2.4.4 (32bit) gives a 6600+ rating: 1) 10.14 USB installer creation Using a USB key of 8GB minimum, create a Mojave USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Mojave installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: Setup your BIOS for UEFI mode install Clover bootloader on the USB installer with the following customised settings: Clover for UEFI booting only Install Clover in the ESP UEFI Drivers -> Recommended drivers ApfsDriverLoader / AptioMemoryFix / DataHubDxe / FSInject / HFSPlus / SMCHelper UEFI Drivers -> Human Interface Devices (optional only) PS2MouseDxe / UsbMouseDxe Themes (optional only) Install Clover PrefPane (optional only) you may use Clover version r5035 attached in above in High Sierra guide once Clover is installed, run Clover Configurator app (available in above High Sierra guide) and mount the freshly created EFI partition of the USB installer open this EFI partition and transfer the files & folders from the Latitude E7250 Mojave Clover pack below to the EFI/Clover folder of the EFI partition: Clover_Pack_E7250_Moj.zip Clover_Pack_E7250_Moj_#2.zip 2) 10.14 installation boot the Mojave USB installer at the Clover main menu, select the "Install macOS Mojave" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target Mojave installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Mojave partition>" repeat this until this partition is no longer offered and only the target Mojave partition is left to boot Reboot the target Mojave partition via your USB installer 3) Post-installation tuning Once the target Mojave partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Mojave partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the Mojave partition/disk Open this EFI partition and transfer the files & folders from the above Latitude E7250 Mojave Clover pack to the EFI/Clover folder of the EFI partition You may then reboot and verify that Mojave boots off your disk through Clover After that reboot, finalise post-installation tuning actions such as disabling hibernation, allowing all apps download from anywhere, changing all serial numbers, etc. Please note that: Mojave runs with the same settings as those used for High Sierra. Again, generate your own CPU-specific SSDT using Pike R Alpha's well-known generator script of you have a different CPU than the i5-5300U fitted to my E7250.

Target macOS release: High Sierra 10.13.x This is a Clover-based installation using the well-known/well-documented vanilla manual method detailed below: Working: full QE/CI with HD5500 graphics OOB DP + HDMI output OOB full audio, including jack microphone input and headset output (with AppleALC kext & layout-id 11 + CodecCommander) HDMI audio (with AppleIntelBDWGraphicsFB kext patch) built-in Gigabit Ethernet (with IntelMausiEthernet kext) full CPU power management, including Turbo boost to 2.9GHz (with CPU-specific generated SSDT) system sleeps Ok through lid closure, power button, Fn-F1, Apple menu->Sleep and energy savings settings with hibernation mode set to 0 (sleep to RAM) and /var/vm/sleepimage file deleted. Wakes Ok through lid opening and power button wireless & bluetooth with any compatible card/USB dongle battery management and monitoring (with ACPIBatteryManager kext) SD card reader (with DSDT patch for compatibility with Apple's default Broadcom device 14e4:16bc) integrated webcam OOB keyboard backlight control OOB (for backlit models) USB3.0 ports (with Rehabman's USBInjectAll + FakePCIID kexts for USB2/USB3 multiplexing) Not Working: N/A Not tested: SmartCard reader Fingerprint scanner GeekBench v2.4.4 (32bit) gives a 6600+ rating: 1) 10.13 USB installer creation Using a USB key of 8GB minimum, create a High Sierra USB installer through the following Terminal command: sudo <path>/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of High Sierra installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following customised settings: Clover for UEFI booting only Install Clover in the ESP UEFI Drivers -> Recommended drivers ApfsDriverLoader / AptioMemoryFix / DataHubDxe / FSInject / HFSPlus / SMCHelper UEFI Drivers -> Human Interface Devices (optional only) PS2MouseDxe / UsbMouseDxe Themes (optional only) Install Clover PrefPane (optional only) you may use version r5035 attached below or any subsequent version available at Dids' Github repo Clover_v2.5k_r5035.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the E7250 High Sierra Clover pack below to the EFI/Clover folder of the EFI partition Clover_Pack_E7250_HiSie.zip Clover_Pack_E7250_HiSie_#2.zip 2) 10.13 installation boot the High Sierra USB installer at the Clover main menu, select the "Install macOS High Sierra" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target High Sierra installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target High Sierra partition>" repeat this until this partition is no longer offered and only the target High Sierra partition is left to boot 3) Post-Installation tuning Once the target High Sierra partition has booted, complete the 1st boot configuration finalisation Once at the desktop, install Clover bootloader on the High Sierra partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the High Sierra partition/disk Open this EFI partition and transfer the files & folders from the above E7250 High Sierra Clover pack to the EFI/Clover folder of the EFI partition You may then reboot and verify that High Sierra boots off your disk through Clover After that reboot, finalise post-installation tuning actions such as disabling hibernation, allowing all apps download from anywhere, changing all serial numbers, etc. Please note that: Clover config of the pack contains HDMI-audio BDW framebuffer patch. Caching add-on kexts from /L/E is faster than injecting them from E/C/k/O. After any kexts modification, whether to /S/L/E or to /L/E, repair permissions and rebuild cache. E7250 can use SMBIOS MBA7,1 or MBP12,1. Above Clover pack provided with MBP12,1 settings. CPU power management SSDT used (with dropping of SSDTs CpuPm + CpuOIst) in preference to simple "PluginType" in order to get Fn-F1 working to put laptop to sleep. Otherwise, Fn-F1 powers off the laptop. The trick in the SSDT is to return 0x05 in the _DSM method (0x03 by default). Generate your own CPU-specific SSDT using Pike R Alpha's well-known generator script of you have a different CPU than the i5-5300U fitted to my E7250. Patched A21 DSDT only contains the following patches to support Fn-F11/Fn-F12 brightness control, the rest is full vanilla: Method (_INI, 0, Serialized) // _INI: Initialize { [...] If (CondRefOf (\_OSI, Local0)) { If (Lor (_OSI ("Darwin"), _OSI ("Windows 2009"))) // Sets OSYS for "Darwin" for Fn-F11/Fn-F12 brightness ctrl { Store (0x07D9, OSYS) } [...] } [...] } Method (OSID, 0, NotSerialized) { If (LEqual (ACOS, Zero)) { [...] If (CondRefOf (\_OSI, Local0)) { [...] If (LOr (_OSI ("Darwin"), _OSI (WIN7))) // "Darwin" check - for Fn-F11/Fn-F12 brightness ctrl { Store (0x80, ACOS) } [...] } } Return (ACOS) } Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) Notify (^^LPCB.PS2K, 0x366) // Fn-F12 brightness ctrl (up) } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) Notify (^^LPCB.PS2K, 0x365) // Fn-F11 brightness ctrl (down) } }

You simply Google for "Rehabman ACPIBatteryManager" and download the latest. But that's not going to help your battery charge... Or then, it was only the battery monitoring, contrary to your previous statement.

Battery not charging is normally unrelated to macOS; it must be goosed. Did you check its status in BIOS?

Do you mean that the battery will not charge at all or that the battery monitoring icon is not showing that the battery is on charge (mains connected)? Not quite the same...

I was asked about the patch for the DW380 Bluetooth module. It's the same (principle) as before: patch consists of adding an entry for the DW380 module in the Bluetooth Transport kext, based on the copy of an existing module entry/definition. Under Mojave, the target for the patch is the BroadcomBluetoothHostControllerUSBTransport plugin kext of IOBluetoothFamily. In order to avoid patching the vanilla kext to inject the module's info, it's best to simply inject this through FakeSMC (i.e. the patch added as is to the Info.plist file, right above the <key>FakeSMC</key> key entry). This has the additional advantage of being sustainable to macOS updates. Mojave patch will be: <key>DW380 Bluetooth module: PID 0x413c/16700, VID 0x8197/33175</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string> <key>IOClass</key> <string>BroadcomBluetoothHostControllerUSBTransport</string> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>LMPLoggingEnabled</key> <true/> <key>idProduct</key> <integer>33175</integer> <key>idVendor</key> <integer>16700</integer> </dict> Example for Mojave: FakeSMC_with_DW380_injection.kext.zip NB: DW380 obviously requires Rehabman's firmware patching kexts to run properly (BrcmFirmwareRepo + BrcmPatchRAM2).