Hervé

By power, I meant the output power to the USB ports... That's totally unrelated to the actual card registering in macOS which is PCIe bus related.

Issues with Bluetooth are notorious on such types of cards. Even with latest versions of injector kext + PatchRAM3 kexts. You may even find it only works if you reboot from Windows due to firmware-related issues. I've personally given up.

It's one of those cheap unbranded cards you buy on-line. Bears a "PCIe-U314S+ PW4" label on it. Manufactured by... who knows? Based on NEC UPD720201 chipset that may just not be 100% supported, though it seems to be... More likely, the card may not draw enough power to the Apple Bluetooth module.

I was talking about your PCIe USB controller card of course. There isn't much about these here, except EC cards for which you now have a link. You'll have to make your own research on Google...

More a matter of chipset compatibility in my opinion. Maybe you can return the card and look at another model with a known supported chipset.

Yes, I have the same behaviour re: USB3.0 controller in SysInfo: nothing is listed but everything works.

"Original WIFI card" means nothing, you have to specify the exact model to assess compatibility. Consult our FAQ + wireless cards inventories on the matter. If you're looking for a distro or support with a distro, walk away because you won't get anything here. The Insanelymac guide you've linked is the best you'll get these days in terms of dedicated guides for the E6410. My D630 guides can be followed in terms of installation process but the Chameleon/Enoch/Clover packs are obviously not applicable, at least not in full.

Correct but it's an EC card in my laptop, not a desktop PCIe controller and I can't plug an Airport card into it. I Couldn't see anything wrong with your Clover setup. I would suggest you try to cache the generic USB3.0 kext from /L/E rather than inject the kext you currently use which I presume is mXHCD.

Found my NEC Renesas card. Tested it Ok in High Sierra, Mojave and Catalina.

Found it! NEC UPD720202 card verified under High Sierra, Mojave and Catalina with same GenericUSBXHCI kext v1.2.11.

You may choose 14e4,4353 or 14e4,4331 to you own wish; I've mentioned both because those are the ids we want to target in order to ensure that AirportBrcmNIC is bypassed and AirportBrcm4360 gets loaded instead. They basically are the 2 x ids supported by the kext. Your Clover config is spot on though I must admit I'm surprised not to see anything under RP02->PXSX when your properties injection are present. It's as if no Broadcom kext got loaded which is odd. However, given that you were then able to connect to 2.4 and 5GHz networks, I guess drivers did load. I can't comment your test results much. Obviously you'll get far better rates on a 5GHz network than on a 2.4GHz one. I'm not too surprised by the rates on the 2.4GHz network but more so by the download rate on the 5GHz one. I sometimes get an upload rate higher than a download one but nothing of the sort in terms of difference. However, maybe other devices were downloading stuff off your connection at the time or it just got slow. Can't say more. It really depends on your own local stuff. All I can say on the 5GHz network is that you're connected on a 40MHz channel, not a DFS/80MHz channel so rates will lower than you may expect. DFS/80MHz connections and higher rates totally depends on your local router/box capabilities here. That's something only you can look into. What I can tell you is that my own local telco router offers me DFS/80MHz connection so I achieve high speed 802.11ac connection at 800-900Mbps and Internet rate at the maximum rate of my fibre connection, i.e. 300Mbps up/down. All I can suggest is that you experiment with AirportBrcmFixup kexts and the boot arguments it provides to modify/inject parameters such as Country Code and stuff like that.

No, I've never connected an Apple BRCM94360xx to an add-on PCIe USB controller on a Hack. I've played with an ExpressCard NEC Renesas controller (NEC UPD720202 chipset with PCI id 1912,15) before but it was several years and OS X versions ago. I had no issues at all. Regretfully, I can't find that card anymore otherwise I'd have tested it in macOS. I may have given it away, can't remember... What's the exact model of your card? I'd also recommend you post a zipped copy of your Clover EFI folder as you may use settings that clash with the cards USB operations. NB: The name of the ACPI device under which the card registers is irrelevant here. As I said, all looks Ok in IOReg except that card's identification which does surprise me a lot.

Check if the generic USB3.0 kext available here is the same that you used. It worked for me in all recent versions of macOS for add-on USB3.0 PCIe controllers. Regarding a potential DSDT patch, forget it for such types of add-on cards. It's perfectly normal that you find no info in your DSDT regarding those USB ports under RP07 root bridge since they do not belong to the computer's motherboard. In addition, they're clearly shown in IOReg which, to me, proves all seems to be in order on that front. I'm more surprised that, in IOReg, your card registers as "PXSX@00000000" under RP07@1C->PXSX@0, rather than as it's actual model. Never saw this with the add-on cards I played with.

Please read and follow the guide!

No DSDT patch required; just follow the guide.

From memory, these would be stored in NVRAM if you set that up. If you did not, just follow the Clover guidance on the matter (emuvariable module, RC scripts, etc).

I know... really poor service for the price you paid! Someone ought to be fired.

Huh? There is no mSata slot in the Latitude 7490 so you could not possibly fit an mSata SSD into that laptop. The WLAN slot is M.2 Key A/E so it would be physically impossible to fit either an mSata SSD or an M.2 SSD. M.2 SSD are not Key A/E but Key B, key M or Key B/M. The WWAN slot is Key B and can physically take a 2242 M.2 SATA or NVME SSD but that's not supported (I've tested this in the past, like several other people).

Keyboard should be set to French PC type in the keyboard PrefPane. Then it's just a matter of swapping out CMD and Option keys, also through the PrefPane. As for the wireless card, well you can identify the model through very obvious manners: open up the bottom cover and look at it/its label look at the model listed in Windows Device Manager run DPCIManager app in macOS (less obvious to newbies)

Look here too:

I'm sure you can understand that we just cannot re-test every single card listed in our inventories everytime a new OS X/macOS update comes out. We need to be able to rely on the community to chime in on these kind of things, newbies or not... I don't remember needing to replace 802.11FamilyV2 for the DW1510 I occasionally used in my Vostro200 (now running 10.15.5) but I recently sold the card so I've nothing left to verify the behaviour. By all means, try your AW-CE123H without replacing 80211FamilyV2 kext so that you can confirm how things actually work now.

It looks like you got your knickers in a twist and you really ought to be careful when copying/pasting information... According to info previously posted on (now defunct) wikidevi, DW1802 is a dual-band 802.11n card based on Qualcomm Atheros AR9462 chip, i.e. the same as an AR5B22 card; both carry the same PCI id 168c,34. Such cards don't work OOB, quite the contrary, as is very clearly indicated in our inventories... It also seems you missed the fact that the "(=AR5B22)" statement is listed under the kext/driver column, i.e. you're meant to refer to the stated model for driver info. For any given card, it never meant that it is another... The chipset of AW-CE123H card IS NOT AR94621 (that does not even exist), the "1" in the inventory clearly being an index for a footnote. You're not the 1st person to make that particular (copy/paste) mistake, others have done the same for multiple references at Voldemort's place by copying/pasting my info without 2nd thoughts (or references to original thread of course!); it's quite ironic because it makes the paosted info quite incorrect. The technical information we published for that card can be verified on replacement wikidevi site here or here so rest assured that what we've provided in our inventories is correct. Yours is far more dubious and, on the 802.11ac front, you may have confused DW1802 with DW1820, which also happens to be totally unsupported.

Kexts from any previous OS X/macOS are available in update/combo update packages off Apple's web site and from which they can very easily be extracted with Pacifist app.

No. Try and rebuild your cache in case it got damaged.

Forum runs in English only as per our posted rules. No errors either in the last picture you posted; just wait a little, it should get to the black screen with white Apple log + white progress bar before reaching the main macOS installation screen.