Contribute
Register

TP-Link TL-WN882ND can't get it to work

Status
Not open for further replies.
Joined
Mar 9, 2011
Messages
107
Motherboard
ASRock Z370M-ITX/ac
CPU
I3-8350K
Graphics
RX 580
Mac
  1. Mac Pro
Mobile Phone
  1. iOS
I have a fully functional and stable Mojave system running on a Haswell MB.

I have Windows dual booted on a separate SSD, accessed via Clover 5102.

Windows 10 uses the TP-Link PCI Express adapter with no problem, out of the box.

I have tried all the remedies I can find that involve adding <string>pci168c,2e</string> to info.plist in both the Atheros and other kexts, including in the EFI and in L/E and S/L/E locations. No go.

The attached screenshot shows the System Info panel for WIFI and the DCPI list of PCI devices. Nothing on that list that looks helpful.

I know this has been covered extensively in other posts and I have tried hard to follow all the leads I can, but I'm now stuck.

I know the card works in Windows - what am I doing wrong?

Thanks all, in advance.
 

Attachments

  • Screenshot 2021-07-04 at 16.21.47.png
    Screenshot 2021-07-04 at 16.21.47.png
    1.5 MB · Views: 47
You shouldn't be messing around with the kexts in your /S/L/E folder.

From what I recall the AirportAtheros40.kext was removed from macOS with the release of Mojave.

You need to install the AirPortAtheros40.kext and the ATH9KInjector.kext to your /Library/Extensions (/L/E) folder. Installing the kext and injector is best done using a Kext installer application, such as KextBeast. KextBeast can be downloaded from this site - https://www.tonymacx86.com/resources/kextbeast-2-0-2.399/

The kext with the pci168c,2e device ID for your TP-Link WiFi card added, and injector are attached below.

Do not install the kext and injector to your /System/Library/Extensions folder.
 

Attachments

  • Atheros Fix v2.zip
    659.1 KB · Views: 76
Thanks EdHawk. I had been using KextBeast. Will report back.
 
Mmm, no joy.
The info is consistent: the System Report shows the Intel I217 without a kext; the DCPI shows the Intel I217 without a kext.
I installed the kexts you attached with KextBeast. The injector was new to me - I had not seen that mentioned in my previous searches.
Interesting nuance to Kextbeast is that it installs only the first kext in finds in Desktop. But I was wise to that and installed both.
 
Mmm, no joy.
The info is consistent: the System Report shows the Intel I217 without a kext; the DCPI shows the Intel I217 without a kext.
I installed the kexts you attached with KextBeast. The injector was new to me - I had not seen that mentioned in my previous searches.
Interesting nuance to Kextbeast is that it installs only the first kext in finds in Desktop. But I was wise to that and installed both.
best to keep your 3rd party kexts in your efi
 
best to keep your 3rd party kexts in your efi
Is there any downside to putting them in the EFI as well? Apart from being a bit sloppy?
 
Is there any downside to putting them in the EFI as well? Apart from being a bit sloppy?
it is better practise to keep them in your efi with newer versions of macOS
 
I've also copied those two kexts to clover/kexts/other in my boot EFI, but still no wifi.
 
I've also copied those two kexts to clover/kexts/other in my boot EFI, but still no wifi.
in terminal:
Code:
sudo kextcache -i /

and copy and paste the results here
 
KernelCache ID: 168639D7DB445100F6EC66D98E8DA70F


Kext with invalid signatured (-67030) allowed: <OSKext 0x7f865bf9f770 [0x7fff9eae2920]> { URL = "file:///System/Library/Extensions/IO80211Family.kext/", ID = "com.apple.iokit.IO80211Family" }


Kext with invalid signatured (-67030) allowed: <OSKext 0x7f865bfa88b0 [0x7fff9eae2920]> { URL = "file:///System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros40.kext/", ID = "com.apple.driver.AirPort.Atheros40" }


Kext with invalid signatured (-67062) allowed: <OSKext 0x7f865c0907d0 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/ATH9KInjector.kext/", ID = "com.chunnann.ATH9KInjector" }


/Library/Extensions/NIUSBGuitarRigMobile.kext does not appear in strict exception list for architecture: x86_64


Kext with invalid signatured (-67007) allowed: <OSKext 0x7f865c091bf0 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/NIUSBGuitarRigMobile.kext/", ID = "com.caiaq.driver.NIUSBGuitarRigMobileDriver" }


Kext with invalid signatured (-67062) allowed: <OSKext 0x7f865c094850 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/IntelMausi.kext/", ID = "as.acidanthera.mieze.IntelMausi" }


/Library/Extensions/RDUSB0074Dev.kext does not appear in strict exception list for architecture: x86_64


Kext with invalid signatured (-67007) allowed: <OSKext 0x7f865c0946d0 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/RDUSB0074Dev.kext/", ID = "jp.co.roland.RDUSB0074Dev" }


Kext with invalid signatured (-67030) allowed: <OSKext 0x7f865c0984b0 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/AirPortAtheros40.kext/", ID = "com.apple.driver.AirPort.Atheros40" }


Kext with invalid signatured (-67030) allowed: <OSKext 0x7f865c0a7820 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/IO80211Family.kext/", ID = "com.apple.iokit.IO80211Family" }


Kext rejected due to improper filesystem permissions: <OSKext 0x7f865c0af020 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros40.kext/", ID = "com.apple.driver.AirPort.Atheros40" }


/Library/Extensions/NIUSBAudioDriver.kext does not appear in strict exception list for architecture: x86_64


Kext with invalid signatured (-67007) allowed: <OSKext 0x7f865c0b34f0 [0x7fff9eae2920]> { URL = "file:///Library/Extensions/NIUSBAudioDriver.kext/", ID = "com.caiaq.driver.NIUSBHardwareDriver" }
 
Status
Not open for further replies.
Back
Top