Hervé

As suggested by @Jake Lo, here is a link to a MacRumors thread that provides a good list of tested and recommended SSDs that are compatible with macOS and therefore our Hackintoshes: https://forums.macrumors.com/threads/upgrading-2013-2014-macbook-pro-ssd-to-m-2-nvme.2034976/

Not like that, no; you'd need to post the full hardware specs and a dump of your ACPI tables. We can then try and build a Clover pack based for work previously done on such old and unsupported C2D laptop platforms. Also bear in mind that, as posted in my D630 guide, the method I had described for Catalina worked up to 10.15.3. It didn't work in 10.15.4 and, presumably, beyond. It's therefore highly likely you'd have to use dosdude1's patcher.

It's got nothing to do with TrackPad; it's just plain & basic keyboard definition. We've got a few threads on the matter, look them up. You may also give Karabiner app a try. You know, experiment...

Check if Ukelele contains a Logitech keyboard definition for a German keyboard. https://osxlatitude.com/forums/topic/2616-keyboard-mappings/?do=findComment&comment=19895 If it does, copy/paste the files into /Library/Keyboard Layouts folder. You'll then have a new German keyboard layout available to pick in your keyboard PrefPane.

You could always run Hackintool app and regenerate the USB kext/SSDT table.

We have full installation guides in the section carrying the same name, I suggest you start by looking at them. Given that you're totally new at Hackintoshing, I recommend you you also consult our FAQ section with regards to creating a bootable macOS USB installer. You should also consult our OS X/macOS section + Our Picks list for guidance regarding requirements. If you don't understand much at the present time, I must warn you that it's all very technical and may completely be over your head. Please note that we don't support distros here and that discussions or queries about them will be deleted without any notice. If you're looking for a quick and easy way to install and run macOS on your laptop like take a CD or DVD and off you go, pass your turn; it just does not work like that, you need to be technically skilled with computers and aware of their inner architecture/workings. Potentially, you have a huge amount of knowledge to acquire, something most of us took years to collect. It's not something anyone can explain or share in a few minutes or a few posts. Not trying to scare you away here but be totally honest with what awaits you. But if you're already computer-literate and technical enough, you'll get along.

The E6430s is just an E6330 with a slightly wider 14" screen. To me, apart from the absence of support for WWAN modules, there is no difference between the E6430s and the E6330 or even a low-res (1366x768) Intel graphics-only E6430. Overall, the specs are identical. E6430s specs E6430 specs E6330 specs Whatever wireless card you got, none of the above 4 are supported and will need to be replaced by a compatible card. See our inventories on the matter. You may follow any existing E6x30 guide re: installation process, knowing that you only need to pay more attention to the patched ACPI tables and probably try to use those of the E6330. Catalina will, of course, be fully supported.

What button would that be? If you're actually talking about a key such as this: the characters usually are available on some other key(s) of the keyboard. For instance, on a French keyboard, they can be available on this key: which is located left of the 1 key, right above the Tab key. It does not just depend on the kext you use but also on the keyboard layout you've selected in macOS. If it's available at all, select German PC. Alternatively, try one of those Logitech layouts, they may be more suitable.

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.