Hervé

Erm, re: Bluetooth, you just don't throw in all the kexts re: Broadcom firmware patching! You need to read Rehabman's documentation: https://github.com/RehabMan/OS-X-BrcmPatchRAM Replacement IO80211Family kext will not load from /L/E, it has to be done in /S/L/E. See here: https://osxlatitude.com/forums/topic/11138-inventory-of-supportedunsupported-wireless-cards-2-sierra-catalina/

TouchPad will work if you've setup your USB ports properly and installed DrHurt's VoodooPS2Controller R6 SingleTap is not enabled by default; you'll have to enable those features once you've got your TouchPad properly enabled as per 1) AppleHDA_IDT kext is now obsolete and was used in conjunction with patched AppleHDA. Use Lilu + AppleALC with the relevant layout-id. I provided you with all the necessary kexts in my post above, it'd please me if you'd use them...

You can do either but if you already have and existing OS X/macOS installation, it's just as easy to opt for a direct update as long as you implement the requirements.

The Intel wireless card of my ex-E6440 was not a N-2230 but a N-6235; it indeed carried the same Bluetooth module 8087:07da you've illustrated above. This being said, I do not fully understand what the issue is here and what you're trying to get. Let's clarify something first: no device can be "injected" in a USB port through DSDT patching. USB devices are 100% plug'n play from that perspective. They always get automatically detected and you simply cannot inject any properties through DSDT; if you tried, you'd find it just would never be applied. It does not really matter that the BT module registers against a USB2.0 controller or a USB3.0 controller. It simply depends on the chipset of the computer, knowing that recent/modern computers no longer have dedicated USB2.0 controllers. That can be easily checked through DSDT lookups or IOReg lookups: USB3.0 are of XHCI (eXtensible Host Controller Interface) nature USB2.0 are of EHCI (Enhanced Host Controller Interface) nature USB1.x are of OHCI/UHCI (Open Host Controller Interface/Universal Host Controller Interface) nature Ivy Bridge, Haswell or Broadwell computers typically possess both USB2 and USB3 controllers and you'll find EHCx + XHCx controllers in their DSDT/IOReg. Skylake and later computers typically only have USB3 controllers so you simply won't find any device registered under USB2 controllers no matter the nature of the connected USB device. With regards to the Intel Bluetooth module 8087:07ba, it's always worked OOB for me though I can't say I've used it much... Afaik, there's never been any firmware patching kexts/tools for Intel modules, only for Broadcom ones. So, again, I'm wondering what your request is about here.

Ok, then it is now detected. What are the device's PCI ids ? You'll see them if you select the device in SysInfo->Hardware->USB. You may therefore proceed as to install Rehabman's Broadcom firmware patching kexts as detailed on his GitHub repo. My recommendation is to opt for caching Repo + PatchRAM2 from /L/E... Caching kexts from /L/E is explained in our FAQ section. https://github.com/RehabMan/OS-X-BrcmPatchRAM No guarantee you'll get Bluetooth 100% operational of course.

Again, I'm not seeing any ACPI folder in your Clover EFI. Was that a mistake when posting your folder or is it really missing from your hack? It could be a problem since your Clover config seeks to load DSDT + SSDT + SSDT-PNLF... You would also need the SSDt that disables the nVidia dGPU. One you clarify and possible sort that out, try out the following Clover config + kexts set: config.plist.zip kexts.zip I don't know where you got your EFI folder from but you should clearly use the Clover packs we posted here at OSXL for those E6x30 models. See the Guides section...

Bluetooth modules are USB-connected. If your BT device does not appear in SysInfo under the USB section, then you need to sort out your USB ports before anything else. Once you've done that, you'll have to look at/identify the chip your BT dongle is based on because that has an evident link to potential compatibility and support under macOS/Mojave...

Do you see something else mentioned?

You need to get your USB ports sorted out. Use Hackintool app to that effect.

Details of the patch required for your AW-NB290H have been available for years in our published wireless cards inventories available in the R&D->Wifi & Bluetooth forum section and via the FAQ section. I don't know how you could have missed either, even a Google search on "AW-NB290H patch" leads to it... If you also searched our Wireless & Bluetooth section, you'd find threads such as these: https://osxlatitude.com/forums/topic/8748-broadcom-bcm43225hmb/ Battery life depends on size and age/state of battery. Of course, if you have a discrete GPU, you ought to disable it to save on battery. You can search for this too; there are readily available SSDT files to that effect. You did not say which kext you use for TouchPad so I can only point you to DrHurt's R6 version (compiled by Bronxteck) which is available in the dedicated thread posted in the R&D->kexts forum section. If you find the finger touch too sensitive, you can edit the Info.plist of the kext's TrackPad plugin and experiment with different values for FingerZ parameter.

Works as described in our Inventory thread. 'depends entirely on the card you have, especially the Country Code it is set to.

The patch has been described in several places on this forum and others... Here for instance and directly displayed on forum main page. NB: In case you ignore this, Clover ACPI device renaming operates in standard/classic ASCII mode, expressed in hexadecimal notation.

@Jake Lo, no, these additional antennas are for an eventual WWAN module and too short to reach a WLAN card.

1) Does the laptop reset when operating standalone or docked? 2) Lenovo Dock ??? Is this compatible? 3) you'd have to specify what hardware you're talking about for that NIC, we're not going to guess... It must have been said a million times: Intel wireless are not supported. Please consult our FAQ section.

If you have an Alps V3 TouchPad, you should have it in your System Preferences if you've set up your USB ports properly. I highly recommend you consult this thread which illustrate a recent experience with that version of Alps Touchpad: Once you get your TrackPad PrefPane re-instated, you'll be able to activate items such as "Tracking speed" or "Tap to click" (which is not enabled by default).

Re: Dr Hurt's driver: At time of writing (Nov 2017), I don't believe we had had any feedback on the E7x70 Series; it may well be that the known issue after wake persists with R6 version compiled by Bronxteck. Consider this instead: This being said, the dev has not worked on this project for 2 years now, he did not have the necessary hardware to pursue his work; as such, consider the project abandoned/on-hold until someone wishes to take over.

Try without the patched DSDT; either remove it from ACPI/patched folder or select BIOS.aml table from Clover main menu->Options->ACPI configs when Clover boots.

No. You inject the layout-id along the rest of the properties you inject in the Devices section of your Clover config.

Did you follow the minimum requirements? It's directly available from main page -> "Our Picks" column on the right...

Looks like it. You should report it to Slice.

Repair permissions/rebuild cache: same as with previous versions; please check our FAQ section; it's there for a purpose... HDMI tint: you have to inject HDMI properties to the framebuffer to override DP settings. It was mentioned just a few days ago in a 7490 thread. Fix also detailed in my Latitude 7490 guide.

Arf, seems I spoke too soon; a day later, it's back to unreliable mode...

You could try and play with the setting applied to Legacy Option ROMs. Can you also post your Clover elements (EFI + kexts folders, Config.plist file)?