Hervé

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)?

Folks, re: Bluetooth, I installed Mieze's latest drivers published at InsanelyMac. It's loading FW version 4689 and works great! I've finally recovered Bluetooth full operations with the DW1820A (#0VW3T3, 1028:0021) of my 7490 running Catalina after caching the following kexts (from /L/E) from her latest V2.3.0d3 driver package: BrcmBluetoothInjector BrcmFirmwareRepo BrcmPatchRAM3 I invite you all to try Mieze's drivers and let her know of your results at IM.

Clover builds can be found at the following locations: Dids Github repo CloverHackyColour (Slice) Github repo Clover Configurator app can be found at the following location: Mackie100 repo

Card: DW1820A, #0VW3T3, 1028:021 Hackintosh: Lenovo Thinkpad 450s macOS versions: Mojave Ok Patch: compatible pci14e4,4353 Kexts: BrcmAirportFix (or Clover FixAirport ACPI fix) to inject ARPT device under PCI root bridge Boot parameter: none Tricks: none

Oh yes, agreed but we're not in installation phase here. The alternative would be to boot without cache but, afaik, Clover no longer supports this.

We have a dedicated thread re: difference between injecting kexts and caching kexts in the FAQ section; I invite you to refer to it. I always recommend caching kexts (once they've been validated with Clover injection) since this is the normal/expected mode of operation of OS X/macOS. Kext injection is like an unnatural forced load.

The Latitude E7450, like its E7250 smaller brother, is equipped with Intel i218LM Ethernet card. That's supported with the IntelMausiEthernet kext that you'll find in the Clover packs available in the models' respective guides. Make sure you've setup your BIOS parameters according to the recommended settings. These are available at top of the E7xxx support section.

Was there a reason why in your clover config, Devices section, audio injection was set to "No"? I should be left blank, knowing that you inject layout-id 12 in the Properties for HDEF device @1B...

Thanks, well you sure are running on AirportBrcmNIC; if stable, you must be the 1st! Will try your solution with FakePCIID, kexts on my 7490 laptop.

@checked, please post saved output from IORegistryExplorer app. Please note that placing kexts in C/k/O AND /L/E is obviously not necessary since you should only be using one or the other. Seems like you do not fully master this...

Well you are obviously using AirportBrcmFixup kext but, that aside, you've done everything correctly. Bad luck, card is not compatible with your HP laptop, change it for a DW1560 (preferably) or DW1830 (if it can fit in and you have 3 x antennas). NB: if you want to unlock your Catalina system partition to generate debug files, refer to our FAQ section.

I'm not sure I understand what you mean... Obviously, the above relates to the M.2 WLAN slot and its location in I/O (and/or ACPI defined device attachment if you prefer). This is why, I've even added the "WLAN" slot name in the properties injection... So, no it does not vary by device, i.e. wireless card; of course not. This identifies/specifies the WLAN slot as found in IOReg and where the DW1820A card (or any other to that effect) physically goes. According to the last debug info you posted, your WLAN slot is at the exact same I/O location as that of my 7490. Not a surprised, all this is defined in DSDT... The only thing I've noticed is that your IOReg shows device PCI0@0->RP03@1C,2->_SB*@0 instead of default's PXSX@0 (you'll see this in your patched DSDT). This leads me to believe you've applied some device renaming of some sort or some ACPI patch that I don't fully understand and have not identified yet. I can't say if this could be the root cause of your issue but there's definitely something I would strongly recommend you try and identify here...