Hervé

We re-re-re-re-re-re-re-confirm: to this day, no kext, won't work. Feel free to buzz Sinetek on the matter and donate if you wish. He had kinda briefly resurrected work on those Realtek card readers last May.

You may follow what I described In my Latitude 7490 or Latitude E6230 guides.

And the message about USB devices is perfectly normal: USB ports do not usually retain power when the laptop sleeps... At least when running on battery.

I meant a complete saved output from SysProfiler but never mind.

Dell Latitude 7490 with Transcend MTS420S M.2 2242 240GB SATA SSD (SATA-III connection @6Gb/s)

Dell Latitude 7490 (PCIe v3.0 x4 M.2 slot) with Samsung 960 EVO M.2 2280 250GB NVME SSD (Gen3 x4)

I really can't say more than what I described in the guide. The kexts I posted in my Clover pack all worked Ok for me (and for other people too).

Post zipped IOReg extract + SysProfiler saved output.

Clover versions older than r4911 should not be used beyond Mojave 10.14.3.

So far, the E6230 runs Catalina beta versions with same set of kexts used with preceding macOS versions. For TouchPad, you're expected to stick with the same VoodooPS2Controller kext that we've been using for a few years (Dr Hurt's R6 version, compiled by Bronxteck). We've had guides for this model for years and I recommend you follow what we've posted in them. Do search the forum before posting, you'd highly likely find what you need, especially for older models such as this one that have been Hackintoshed for years.

Mojave does not officially support neither Core2Duo platforms, nor old nVidia Tesla dGPU such as the Quadra NVS 160M (not Metal compatible). You can run Mojave on C2D platforms with special tricks but getting old non-Metal dGPU got harder and harder to the point where it's cumbersome. Your E6500 with NVS 160M will support and run High Sierra perfectly and my advise is that you stick to 10.13 to begin, especially if you're not an experienced Hackintosher. It remains a fully modern, appropriate and usable macOS version. Of course, you'll have to replace that Intel wireless card since Intel cards are not supported at all. Please refer to our R&D->Wireless section for non-exhaustive inventories of supported models. Cellular, well, "compatible" means nothing... You'll have to identify the model. But that's totally secondary. I invite you to refer to our existing guides for similar C2D laptop models (eg: Latitude D630 or D830 of the previous generation) for which the detailed process will 100% apply, you'll just need to adjust some of the kexts (drivers) to match your E6500 hardware (eg: LAN, audio, etc.)

No. It's also already been discussed at great length on the forum as you must have seen... Those Fermi chips are not properly supported in macOS so the buck stops at El Capitan. NB: Please don't post in Sierra threads that have been dead for 3 years to share about your High Sierra experience. Thank you.

We already have this covered on the forum, including a full installation guide and a High Sierra Clover pack for E6420/E6520 with NVS disabled through patched DSDT/SSDT. Please use the forum Search facility with the obvious keywords that you seem to know already (tags).

Since it's not I2C and that the driver also applies to older Ivy Bridge/Haswell Latitude laptops, it's fair to say you can give Dr Hurt's VoodooPS2Controller R6 kext a try. You'll find it in our R&D->kexts section.

What kind of TouchPad/TrackPad is this model fitted with? Keyboard brightness control is more a matter of DSDT than PS2Controller kext. I've detailed the patch I use in my E6230/7490/E7250 in each relevant guide. Patch info comes from the post made by @jpz4085 in Dr Hurt's PS2Controller thread. Works well in those laptops and will probably be relevant to your laptop too. No harm in trying, at worse it'll change nothing...

If you still have it, sure. But, here, I was able to boot my USB installer with pack #6, leaving the DSDT aside. Mojave is now installed and bootable without the DSDT.

It's the patched DSDT causing problem; I need to investigate. You should be able to boot if you select BIOS.aml rather than DSDT.aml through Clover's main boot menu->Options->ACPI patching.

Hold on, I added the device properties for my DW1820A and I'm getting KP all the time now when booting the USB installer. Same if I remove those DW1820A properties. Let me check...

I get to the Mojave installation screen without issues with my Clover pack #6. There must be something you've not followed in the process detailed in the guide...

I've got a new NVME SSD; let me put it in my 7490 and try a fresh Mojave installation on it with my pack #6. I'll let you know if there's something odd with it.

Is this a vanilla installation or a distro?

If HDEF (or whatever other audio device name) is not defined by default in your DSDT, maybe it is in an SSDT. You can dump all raw BIOS tables by pressing F4 at Clover main menu and then check things out. All extracted tables will be saved in EFI/CLOVER/ACPI/origin folder. But you probably already know that...

You boot your current config (which includes the Broadwell DVMT adjustment) with iGPU fake id and ig-platform-id set to 0x12345678 Once at the macOS desktop, you open up Terminal and repair permissions + rebuild your cache according to the instructions published in our FAQ section You then reboot without the iGPU faked-id or ig-platform-id set to 0x12345678 You can read about the DVMT settings and the associated requirement in Firewolf's original blog. Of course, if your BIOS permits it, set DVMT accordingly (between 64MB and 128MB). https://www.firewolf.science/2015/04/guide-intel-hd-graphics-5500-on-os-x-yosemite-10-10-3/

A layout in a Framebuffer kext can be described as a table that defines display output's properties throughout many parameters including, video memory, number of output ports, type of outputs, etc. You can find these tables in the binary files of framebuffer kexts through a simple Hex editor such as HexFiend for instance. You can then search those layouts in hexadecimal reverse order. For layout 16260006, which is what you would normally use for a laptop with HD5500 graphics, you would conduct a hex search on "06 00 26 16" which would lead you to the following code: 06002616 01030303 00002002 00005001 00000060 D90A0000 D90A0000 00000000 00000000 00000000 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 FF000000 01000000 40000000 0B0B0000 01010500 00000000 05000000 00000000 04000000 00000000 00000000 00000000 00000000 00000000 C8000000 If you were to conduct a search for "06 00 16 16", you'd get nothing because it's not an existing layout; as such, injecting ig-platform-id 0x16160006 in Clover (or trying to) will not lead anywhere. I'm surprised you find it referenced in a guide on a forum because that's totally incorrect.... Anyway, try the attached Clover config. config.plist.zip

You can and should get rid of NullCPUPowerManagement kext. That kills all CPU SpeedStep and affects performance... I'm a little lost because i3-5005U carries the same HD5500 id 0x1616 as the i5-5300U I recently played with on a Dell Latitude E7250 and for which graphics worked OOB with the above arrangements. Can you please post: a zipped saved output from IORegistryExplorer a zipped copy of your Clover EFI folder (when you boot, press F4 at Clover main menu in order to dump all your raw BIOS tables) Which version of Clover are you running with? In your 1st post, your Clover config showed that you were incorrectly trying to fake id 8086:1626 for your HD5500 iGPU (you entered "0x016268086") and injecting BDW (Broadwell) layout-id 0x16160006; that's an unknown layout to me and I would have expected that you'd inject layout-id 0x16260006 instead, as recommended in Cover Configurator. That certainly is the layout I saw reported in IOReg on the E7250 I had and I was not injecting anything, just letting Lilu + WEG do their job... But, by all means, you may try to fake id 8086:1626 by entering "0x16268086" and injecting recommended BDW layout (ig-platform-id) 0x16260006.