Hervé

Sierra 10.12.6 it would seem... Screenshot shows -x boot flag anc CPU panic. Was safe mode desired and was AICPUPM patch activated?

You need a BT4.0 compatible Bluetooth module to get Handoff working. It will not work with DW380 which will only get you basic BT functionality. If you want BT, handoff or AirDrop to work like on a Mac, I can only suggest/recommend you got for an Apple BCM94360CD or similar. That's what I've fitted to my E6220/E6230 laptops and I never need to worry about anything anymore.

Impossible to say. Go and do it if you want. With regards, to the IOReg, I assume you still run with dGPU disabled in BIOS because I'm not seeing it in the IOReg. On the other hand, I'm seeing RP05 root device with nothing attached to it. To me this confirms my suspicion of bad ACPI coding... RP05.PEGP is definitely NOT the dGPU, it's PEG0.NVID or PEG0.PEGP.

I'm not sure your Clover config is mot appropriate (I see you Inject Intel + ATI + nVIDIA in your graphics section for instance...) but start by updating your PCIIDxxx + USBInjectAll to the latest versions. You'll get them off Rehabman's usual repo. Then I would revisit your Clover config, especially the ACPI section... Can you post and extracted/saved SysProfiler?

In that case, yes, revert to EC; or use a USB dongle compatible with High Sierra.

According to your DSDT: HD5500 iGPU is ACPI device GFX0 at usual IOReg addresss 0x00020000 nVidia dGPU is ACPI device PEG0.NVID or PEG0.PEGP at usual address 0x00010000 We can try and disable the dGPU by patching the DSDT and/or SSDT tables. Could you post a compressed IOReg saved from IORegistryExplorer app? This would help to confirm the ACPI device used for the nVidia dGPU. What's weird is that SSDT tables #5 and #6 appear to show the dGPU as if it were attached to RP05 parent device and that clearly differs from the DSDT; functions to enable and disable a dGPU device are clearly defined there. In addition SSDT table #4 clearly defines functions for PEG0 and PEG0.PEGP. So we need to clarify the matter as it would not be the 1st time ACPI tables are terribly/poorly coded by the manufacturer...

I'd start by rebuilding the cache.

Obviously yes, but why not simply swap the card for a supported model sin ce you already have High Sierra running? It's not as if wireless cards were expensive...

Support for ancient Broadcom BCM94321/BCM4321 was dropped in Sierra. Replace it by a supported model!

Disable Bluetooth in your BIOS settings if you want to use the BT module of the card. Otherwise the built-in DW380 module takes precedence. Then make sure that: your combo card is inserted in the full size WWAN slot: it's combo mini-PCIe/USB. I'm pretty sure that the other 2 x 1/2 size slots (one labelled WLAN) are mini-PCIe only and therefore of no use for Bluetooth. all your USB ports are fully functional

Presumably the model in signature. But after 5weeks without any update, one can assume the matter is closed now.

It'll run Ok with 4GB RAM.

Go straight for High Sierra, no point installing any older version.

Added info about cards based on unsupported Qualcomm Atheros chips QCA6174/QCA6174A such as Dell DW1820.

If you use one of the latest versions of CC, you'll see the FixHeaders parameter in the ACPI tab.

Most if not all your hardware should be supported under OS X/macOS. DW1520 wireless is supported with patches. Make sure you set your SATA controller to AHCI mode in BIOS.

If the card came from a 2007 MacMini2,1, that would be Atheros AR5BXB6 (168c:001c) which, indeed, is not supported beyond Lion. You can verify the model by consulting the IOReg dump of that specific model posted at AppleLife.ru (link available in the SMC keys thread of OS X/macOS support section). Your own IOReg will also show you the card's PCI ids. I suggest you consult our non-exhaustive inventory and choose a supported card accordingly. It's available through the FAQ... I highly recommend you opt for a 2.4+5GHz-capable card (rather than 2.4GHz only) such as those based on AR9280/9380 (Atheros AR5Bxx92/112), BCM4322 (DW1510) or, ideally, BCM4360 (AW-CB160H) chips. If the card is 1/2size mini-PCIe, you'll obviously need an adapter plate to fit it in securely into your D830.

168c:003e = Qualcomm QCA6174/6174A, i.e. unsupported chip... There is no such thing as a "Broadcom Atheros" card, only "Qualcomm Atheros" since the former bought the latter several years ago. DW1820 is based on this unsupported QCA6174A chip; it normally shows a Qualcomm Atheros QCNFA344A reference on its label.

Updated with 10.13.6 files.

Indeed, the screenshot posted above does not tend to indicate any form of graphics acceleration. I'm highly skeptical about the statement "I was able to get the NVS 4200M working in 10.14 Mojave"...

Having both GPUs listed under SysProfiler doesn't mean they're both working and active. In fact, it's not the case since Optimus is not supported under OS X/macOS. You can only have either/or.

Anything else failing, try the this: attached patched AppleHDA in /S/L/E: AppleHDA.kext.zip attached ALC292 dummy kext + CodecCommander kext in /L/E: AppleHDA_ALC292.kext.zip CodecCommander.kext.zip Layout #1 injected in DSDT HDEF device Repair permissions then rebuild your cache. You should have audio , including off the jack socket. That's what I use on my E6440.

Atheros AR5B91 works OOB, so given that the WWAN slot is normally a combo port, wireless should work. I also had that very card defined under ARPT device of the DSDT so you should see it under System Information->PCI with driver installed. Failing that, try the other mini-PCIe slot.

You could turn the computer off...

Damn, sorry I had missed that... Very sorry!