Hervé

Boot in single-user mode or boot your USB installer. One or the other should allow you to: mount your Catalina partition and remove the offending kext from /L/E and rebuild your cache or mount your EFI partition and remove the offending kext from E/C/k/O But I must say that your KP seems more related to that EnergyDriver kext. Isn't this installed by IntelGadget app? I'd say the kext just does not agree with Slice's HWMonitorSMC2. Maybe you should revert to the previous version of the FakeSMC-related app.

You go to the Options menu at Clover main boot screen and you manually enter that text as a boot option.

It's not a good card for Hackintosh purposes. Replace it with a Broadcom compatible model. Of course, it's important you consult the correct wireless card inventory to that effect and read things with all due attention...

You're never going to get anywhere with such a Clover config. You can't just select all ACPI fixes and expect things to work. Undo all that and only select those fixes that may be needed like FixRegions, FixHeader, Halt Enabler. As for graphics, I believe Clover Configurator explains things pretty clearly: As far as I knew, Intel HD510 was unsupported but, according to old discussions from 2017 with Rehabman that I found after a quick search, support would have been added in macOS Sierra at some point. Indeed, looking at the SKL framebuffer kexts of High Sierra, Mojave and Catalina, I see that the list of supported devices does include 0x19028086. <key>IOClass</key> <string>AppleIntelFramebufferController</string> <key>IOMatchCategory</key> <string>IOFramebuffer</string> <key>IOPCIClassMatch</key> <string>0x03000000&0xff000000</string> <key>IOPCIPrimaryMatch</key> <string>0x19168086 0x191E8086 0x19268086 0x19278086 0x19128086 0x19328086 0x19028086 0x19178086 0x193B8086 0x191B8086</string> <key>IOProbeScore</key> <integer>80005</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOSourceVersion</key> <string>0.0.0.0.0</string> <key>PMTControl</key> <dict> <key>DisplayEngineCounting</key> <integer>0</integer> </dict> So, remove that GPU id faking you've inserted in your Clover config. No guarantee it'll work though, I see plenty people reported lots of graphics glitches/defects for HD510.

None with your current hardware.

Skylake HD510 is unsupported. You'll need either a different CPU with a supported iGPU or a compatible add-on graphics card.

Guys, you may want to consult this old thread that explained a few things... And @Xeon3D's repo is quite extensive on the matter too. It's a highly recommended reading as far as I'm concerned.

We have a dedicated thread to M.2 compatible cards. Why don't you consult it?

You may adjust the port type definitions in the tool if required. Apart from that, it's that simple, yes.

And no distros of course...

Please consult our FAQ section and search the forum before posting. Thank you.

Hardly any discussion/threads/posts about OC on this forum. Given the amount of issues reported with OC at InsanelyMac, you may wish to stick to good old Clover. OpenCore is still quite far from being what most of us consider mature yet. But, by all means, feel free to experiment and post your results/feedback.

According to @influenist, this WWAN module works with the kext he posted here.

You could do a bit of research, you know... https://www.insanelymac.com/forum/topic/339175-brcmpatchram2-for-1015-catalina-broadcom-bluetooth-firmware-upload/

It appears you chose to use NonPatchRAM2 AND PatchRAM3 and inject kexts that are not for injection but caching... I would suggest you read up on the matter and opt for the latest Bluetooth injector/firmware patching build (v2.5.3 last time I checked), especially if you inject kexts rather than cache them. Right now, you're doing things incorrectly.

What version of Clover are you using? What version of Catalina are you installing? If 10.15.4, make sure you use at least Clover r5107 and, as stated in the 10.15.4 news update, you may have to boot with -disableigfxfirmware boot parameter until your installation has fully completed.

No problem to be expected...

That Bluetooth-related setup is incorrect. You never said if you use the same SSID for 2.4 and 5GHz. If this is the case, there could be a chance that, on wake, your laptop picks up the 2.4GHz network for which there is interference from Bluetooth. If at all, possible, differentiate 2.4 from 5GHz network using different SSIDs, then compare behaviour. NB: no double post on the forum please.

To answer your original question again, Sierra and High Sierra can only be downloaded off the AppStore from a Hackintosh using a Sierra/High Sierra compatible SMBIOS. MBP5,1 is not compatible whilst MBP7,1 is. Of course, the same principles/rules apply to subsequent macOS versions such as Mojave and/or Catalina. So you may download High Sierra off the AppStore from your D830 Hackintosh if you use MBP7,1 SMBIOS. Alternatively, use the High Sierra download link available in the thread dedicated to downloading older versions of OS X/macOS; a thread that we've also placed in "Our Picks" column on the forum main page for reasons of increased visibility (that I'm now beginning to question). With regards to the subsequent questions, even though anticipated in my previous post, I obviously failed on the matter of clarity despite my efforts and carefully chosen words, on top of what -I believed- was clearly stated crucial information in the D630/D830 guides... So, again: Sierra and High Sierra can only be installed and run on a CPU with SSE4 instructions set. Penryn architecture CPUs (Penryn, Wolfdale, etc.) are the oldest suitable families, being the 1st ones to implement/be fitted with such instructions set. This is explained in our pinned "Minimum requirements for OS X/macOS" thread dating back to 2013 and regularly updated ever since. As with any OS X/macOS version, the SMBIOS of a natively unsupported Mac model can only be used with a PlatformSupport plist patched to that effect. Hence the usual choice to switch SMBIOS to that of a natively supported Mac model whenever this appears required (as is the case when upgrading a Penryn-based D830 from El Capitan/MBP5,1 to High Sierra). The last OS X version a Merom-based laptop Hackintosh can natively run is El Capitan, not macOS (meaning Sierra and later). As such, OS X El Capitan is the end of the road for a Latitude D830 fitted with a Merom CPU.

Your Clover config would gain from a generous cleanup but I saw nothing that should affect wireless. I did not spot anything in the kexts that could affect wireless either, nor in the ACPI tables. But if you say you have issues whenever you make a fresh install with your Clover setup, I suggest you look into it. Maybe it's not fully tuned/applicable to your hardware. I also invite you to add your system's specs in signature like most of us do.

Arf, not only are you seeing seeing double, you're imagining things too! So let's clarify what most of us see on your picture: there's only 1 x triangle symbol for each antenna connector (I'm shortsighted but can't see 2 x whites on the Intel nor 2 x blacks on the Broadcom) black means main, white means aux (it's actually written under them on the Broadcom card) your imagination led you to miss the simple fact that numbers 1 and 2 are basic indexes, meaning connector #1 and connector #2 Since you're new to computers, I suggest you do some Google searches and readings about wireless cards and their connectors in order to learn a thing or two... Now that we got the obvious and elementary things behind us brainy boy, one would be expected to connect the black cable on the black connector and the white cable on the white connector. Given that you've already tried to swap antenna cables without any improvement and assuming your antennas are fully and securely hooked to the card's connectors, your card could be defective or your setup could be wrong (incorrect Clover config, unnecessary kexts causing interference, etc.). I'd tend to lean towards the latter. You'll have to provide details of the setup you use for any further assistance.

BCM94360NG cards are 2 x antennas. One is main, the other auxiliary and it's normally written on the label. The only macOS-compatible M.2 card I know of with 3 x antennas is the DW1830. You may consult our macOS compatible M.2 cards and/or our BCM4350 pinned threads for illustrations. Bottom line is that if you got a card with 3 x antennas, it's unlikely to be a BCM94360NG.

"Our Picks" list on forum main page... OS X/macOS forum section In addition to the specified mandatory hardware requirements, macOS Sierra and High Sierra on a D830 require using MBP7,1 SMBIOS since they're not officially supported on MBP5,1 platforms. These constraints are clearly indicated in my D630 and D830 guides. Latter (not former) recommended for installation of OS X/macOS on a D830 of course: https://osxlatitude.com/forums/topic/10370-dell-latitude-d830-with-core2duo-and-nvidia-quadro-nvs-135m-mavericksyosemiteel-capitansierra/?do=findComment&comment=79350 I also want to remind that we have a thread entitled "Minimum specs for OS X/macOS" in this very section. A D830 running El Capitan 10.11.x with MBP5,1 SMBIOS will not be able to download High Sierra from the AppStore; MBP7,1 SMBIOS will have to be used as pre-requisite. If using Chameleon/Enoch, it's a simple matter of using good old Chameleon Wizard to change SMBIOS (alternatively grab the smbios.plist from the D830 Sierra bootpack); if using Clover, Clover Configurator is the obvious (and recommended) tool to adjust the config file. All this being said, from memory, OP's D830 was fitted with Merom T7500 CPU, so, unless that has changed since 2013, El Capitan is the end of the road.

Fitting the Intel card would have allowed you to identify the ACPI device too. It's linked to the actual M.2 slot so you'd have seen the Intel card there. Anyway, good that you got there in the end.

I don't think you should mix stuff from OC and Clover. I've no experience with OC so if that's the route you wish to pursue, I'm afraid I won't be of much help. For the rest, you've lost me.