Hervé

It can be a sign of a dying battery. Does your battery LED blink in red or shows fixed in red when indicator is at 0%?

Questions still arise about this matter so here's a recap of what caching kexts and injecting kexts (through Clover) mean: 1/ Caching kexts: Kexts placed in /L/E and/or /S/L/E are cached in the kernel cache (or prelinked kernel) which aims to accelerate boot time. This is the natural and expected mode of operation of the OS. Cached kexts are subject to signature by Apple and must be set with the correct permissions (Cf. our FAQ topics on permissions). Cached kexts will be shown/listed/registered in System Info (ex-SysProfiler) -> Software -> Extensions. Caching kexts is the recommended scheme for all add-on kexts. /S/L/E is the location for Apple's own (i.e. vanilla) kexts. Ideally, this should be left untouched by Hackintoshers unless for very specific and rare reasons (eg: patched AppleHDA). /L/E is the location for 3rd party/add-on kexts. This is where all kexts we use for our Hackintoshes should go. Add-on kexts should only be placed in either folder, never in both. 2/ Injecting kexts through Clover: Injected kexts are not cached and will not be shown/listed/registered in System Info (ex-SysProfiler) -> Software -> Extensions. Injecting kexts results in a slightly slower boot than caching kexts (though many would arguably say it's hardly noticeable). Kexts injection operates according to Clover settings on the matter: If kext injection is set to Yes, kexts placed in E/C/k/O (or E/C/k/10.xx) will be injected. If kext injection is set to No, no injection takes place; obviously... If kext injection is set to Detect, kext injection operates according to the presence of FakeSMC in the kext cache (the kext having been properly installed in /L/E or /S/L/E). If present, no injection takes place, if absent, kext injection is performed. If kext injection is used, make sure the kexts aren't cached at the same time. Clover's E/C/k/O and E/C/k/10.xx are the locations for kexts that Clover injects at boot time: E/C/k/O is used to inject kexts regardless of the OS X/macOS version. E/C/k/10.xx are used to inject kexts for the given OS X/macOS version and therefore allow different kexts to be injected for different versions. Apart from the obvious requirement for fresh OS X/macOS installations (and/or updates), kext injection is very useful for recovery purposes (like booting without cache which ignores /L/E) or when testing kexts for instance; if a newly injected kexts causes issues (like a KP), it's very easy to remove/bypass it. On the other hand, kext injection is known to occasionally cause problem because it's not the natural way in which kexts should be loaded. Kext injection is basically a form of forced loading and, sometimes (though rare these days), it does not work. This is why -as stated on numerous occasions by Rehabman himself- Clover should really be set with kext injection in "Detect" mode and contain only the absolutely essential/minimum set of kexts required to boot the system. My own recommendation is to experiment with kexts through injection and, once kexts are validated, to cache them from /L/E. Google for this kext injection matter or consult the Clover wiki/InsanelyMac forum. It's all quite widely documented.

Plenty of threads/posts on the forum that explain the difference between caching kexts from /L/E (which really is the recommended way) vs. injecting from E/C/k/O (which can be unreliable). I've also added a dedicated thread on the matter in the FAQ section, which you should consult.

System Preferences -> Energy Saver! It's not enabled by default... Ever thought of using the built-in Help??? Plenty of books if you need to learn how to use OS X:macOS...

They're not "broken"; they're not currently supported by the I2C drivers we use.

Wy don't you use the pack available on our forum for this model (and a vanilla installation rather than that Niresh distro)? E7240 will be ALC292 audio codec, so Lilu + AppleALC (layout 12) + CodecCommander.

@Augusto Sandim,

You can Google for "Broadwell DVMT patch". But I believe JakeLo already gave you what you needed.

Seems r4934 could be buggy... Try the latest Clover version: https://github.com/Dids/clover-builder/releases

Maybe you can explain what pins you masked and why.

I guess we're not allowed to know what that built-in wifi is...

What built-in wifi ?

DP1 Installed Ok on my Latitude 7490 with: Clover r4940 New Lilu v1.3.7 + updated WEG & AppleALC plugins. Rest is same as for Mojave All hardware & main features working. Several bugs and gremlins of course, DP1 oblige...

It's been quite clearly stated in our BCM9350 guide that this model does not work reliably. Consider it unsupported and change it.

@muttonhead411, there is no specific kext other than optional AirportBrcmFixup. The rest is totally vanilla, that's the idea... To date, there's nothing else known to get those cards to work. It'd be fair to say that we need @Naidis to confirm if the card keeps working after over 1hr or not with AirportBrcmFixup kext + brcmfix-driver=1 boot option. @Naidis, no such thing as this "Auto Unlock" option/feature listed for my DW1820a CN-0VW3T3.

Lilu updated for 10.15 in v1.3.7 so no need to add boot flag -lilubetaall for 10.15: Lilu.kext.zip Clover r4937 updated to support kexts injection in 10.15: EFI.zip Catalina kernel patch to support kexts injection: Find: 0085C00F848700000049 Replace: 0085C090909090909049 All thanks to contributors of Catalina test thread at IM.

Not really; check the audio devices ids in Windows Device Manager. Alternatively, install VoodooHDA+AppleHDADisabler, then check the registered audio codec in DPCIManager app.

What's the codec? If ALC292 like E6x40 or E7x40 (i.e. 10ec:0292), refer to the relevant AppleALC config.

So 10.15 is called Catalina. 1st feedback on early installation attempts won't be long...

This is a Hackintosh site so not really the place to discuss Win10, distros or not...

Do not confuse disk partitioning and APFS container/volume management. What you want to do is: reduce your container size by 50-60GB create a new partition ad disk root and format it MSDOS (FAT) or ExFAT You'll then be able to install Win10 on that 2nd partition, knowing that you'll probably need to re-install Clover after to reconstruct your boot sector/EFI partition properly and be able to boot through Clover either partition/OS. There's absolutely no issue formatting a partition MSDOS (FAT) or ExFAT from Disk Utility under OS X/macOS.

1) Post system's hardware specs (CPU gen, chipset, GPU, LAN, audio, card reader, etc.) 2) Specifiy target OS

You'll find the device id when clicking on the actual individual ACPI devices. Not on the Voodoo driver info.

TouchPad works, yes. Occasionally, it won't after startup and it may take a couple of reboot to get it back.

1. No 2. Check your USB settings and eventual related ACPI patches (especially those relating to power)