Hervé

If all you want is list devices in your SysProfiler->PCI section, it's a simple matter of: identification of the devices location IOReg (ACPI device & address) injection of the devices properties into DSDT via a _DSM method under the identified ACPI device (hundreds of example on the forum) or injection of properties through Clover (as per DW1820A guide for instance)

I've just given a hand to a new member who's installed Mojave on his Latitude 5490, fitted with a DW1820A. He could not get the card to work properly either, stating that the card would only work Ok a few minutes then cause severe lag or performance degradation. After a few minutes checking his machine, it was found that: AirportBrcmFixup kext was injected by Clover -> removed Vanilla IO80211Family kext was in /S/L/E -> Ok Incorrect BrcmFirmware kexts were being injected through Clover -> corrected A kext called AirPortBrcmNIC-MFG was present in /S/L/E -> removed Installation was said to be full vanilla with Chris1111's installation tool. Member confirmed he did not manually add the AirportBrcmNIC-MFG kexts to /S/L/E and that the partition was freshly formatted before installation, so it must have been done by Chris1111's tool. This AirportBrcmNIC-MFG kext was last seen in High Sierra and it was understood as a replacement for AirportBrcm4360... Anyway, once the above defects were corrected (and all add-on kexts copied to /L/E, permissions repaired and cache rebuilt), the DW1820A started to work perfectly, as expected and as described in my setup guide, with no performance degradation on the Latitude 5490. So guys, please double/triple check your installation setups before posting about your non-working DW1820A.

By the way, you did not have a DW1820A but a Lenovo/Foxconn T77H649.00 (subsystem id 17aa:075a)...

@bluesbendeer, if you want more support, please post your debug package. Without this, we're blind and can't assist.

Read the DW1820A guide Remove AirPortFix Clover fix Remove brcmfx-country=CN Clover boot option Remove AirportBrcmFixup from Clover kexts folder Make sure you run on full vanilla 80211Family kext in /S/L/E

Update to latest Clover... https://github.com/Dids/clover-builder

It does not seem like there is any kext loaded for a Broadcom-based attached to PXSX device located @1C,4. Are you sure it's the right location? Double check your Cover config and injected kexts in case you have something clashing. If you want further assistance, please post a zipped. copy of your Clover config + saved output of IORegistryExplorer. You should know the drill by now; impossible to say more in the blind...

As far as I know, that card will definitely cause trouble until the property injection is done (or the other older alternatives such as removing the BrcmNIC Plugin kext).

Seriously...

I believe you got your answers in the previous post.

Usually, it's done by adjusting the vendor and device id in the profile of an existing bluetooth model or -preferably- by creating a new one for your own device. You'd simply copy/paste an existing entry and modify the vendor + device ids (in decimal) to match those of your own module. You may look this up in existing Bluetooth threads found in the R&D->Wireless and Bluetooth section.

i3-3217U is Ivy Bridge and indeed fitted with HD4000 iGPU. Explain what you mean by "I think install HD3000" because it does not mean much. From my point of view, your Clover config is correctly injecting Intel + Capri LoRes layout-id for your HD4000. But you can remove those settings since you're injecting latest versions of Lilu + WhateverGreen kexts through Clover/kexts/10.13. Re: CPU, you need to generate your CPU-specific SSDT using Pike R Alpha's well-known generator script. Once that is done, copy.place the resulting SSDT file in Clover/ACPI/patched folder and you'll have full CPU SpeedStep/power management. Re: HDMI, if it does not work OOB, you'll probably have to patch the Capri framebuffer to that effect, knowing that you'd need that for HDMI audio anyway. Look up the HD4000 patching guide in R&D->Graphics section.

TouchPad works fine if you can live without the buttons...

No idea. I use latest Lilu + latest AppleALC on my laptop with ALC256 (injecting layout 11) and all is Ok. This being said, if this is the only gremlin with audio, I suggest you live with it.

'better replace that DW1707 by a more suitable card...

??? If you're running full vanilla, could this be rogue leftovers from stuff you did during your efforts to get audio going? You could always try to temporarily set your Hack to a non-English language, log out or reboot, log back in or restart, then change again the English.

Install or inject CodecCommander kext. I've no idea what you mean by changing the audio PrefPane to English. As far as I know, that should run with whatever language your Hackintosh is running/setup with. Or you don't have a vanilla installation but a distro that made a mess in there.

Ok, well, you need to adjust your Clover folder. It still contains files that were specific to Franckenstein's system, such as the CPU-specific SSDT which was for his i7-4900MQ. You have a different CPU... I also see 3 x DSDT files but only the one called DSDT will be used. Try this Clover config + adjusted kexts set: config.plist.zip kexts.zip

Post a zipped copy of your Clover EFI folder (without Themes subfolder). Brief corrupt Apple logo at startup is perfectly normal and is not indicative of an issue. If a well-know little final boot stage gremlin that can easily be fixed. Please explain the problem(s) you encounter in details. "I did not succeed" is no good to us...

Try these instead. Self-explanatory. config.plist_layout_11.zip config.plist_layout_13.zip config.plist_layout_56.zip

Try this on the E7470: VoodooPS2Controller.kext.zip I think it's Rehabman's and the attachment only contains the Keyboard driver, nothing for a TrackPad/TouchPad.

Sigh... post your Clover config. Why use Xcode when you can use Clover Configurator? Last time I checked your Clover config, the audio properties were not injected properly/commented out...

How did you inject audio layout? Explain how you did this.