Contribute
Register

Need Wireless AC advice

Status
Not open for further replies.
Im only using one Antenna on my Apple WIFI/Bluetooth Card J3 for Bluetooth. Don't use WIFI on a Desktop a lot of those non Apple Branded cards requires a lot of tweaking to get working.

Well the Wifi card itself got here 2 days ago, the adapter card got here today, very much impressed by the card and packaging of the card, one problem... the antenna leads are the wrong size for the card I got, so I will need to replace them with the appropriate leads.

The card inserted into the adapter nice and snug, even made a little click noise.
It is so snug I'm not even worried the screw holes do not match this card since it is longer, I will give it a try and see how it does without the antenna leads.

Edit:
No big surprise it is using the same driver as my old card on Windows 10, 1 bar of signal, but it is working just as fast as my old card, bluetooth drivers possibly need reinstalled.

Sierra however connects to my wifi fine, but the lack of signal seems to be preventing it from working well enough, the bluetooth works as well, plug and play I like it.

Ordered these antenna connectors to solve the small issue with the adapter, will have to devise a method for attaching a screw to mount the card securely.

https://m.ebay.com/itm/USA-2Pcs-IPE...GFF-M-2-WIFI-WLAN-3G-4G-Modules-/322627032027

Again, Thank you @VioletDragon.
 
Last edited:
Hands off works yep. If it isn't a Genuine Apple WIFI/Bluetooth card then it will require work to get Hands off working. Attach ioreg. [Guide] How to Make a Copy of IOReg | tonymacx86.com

It should be genuine, everything is working from imessages, facetime and I get a notification if my phone rings, but it fails to answer and safari doesn't get recommended to open when I use a different device.

IOreg attached, kext-dev-mode is active and not sure why it isn't recognized below.

Also downloaded CAT to use the diag there.
Code:
--- OS X Continuity Activation Tool 2.4b5 ---
                 by sysfloat                
           original by dokterdok            
                                            

--- Initiating system compatiblity check ---

--- Hardware/OS checks ---
Verifying Continuity status...          OK. OS X reports Continuity as active
Verifying Mac model reference...        OK. Known compatible Mac Model detected: iMac11,3
Verifying Mac board-id...               OK. Short board id detected: Mac-F2238BAE
Verifying OS X version...               Warning: This tool wasn't tested with OS X versions higher than 10.10. Detected OS version: 10.12.6
Verifying Wi-Fi hardware...             OK. A Broadcom AirPort card is active, and is using the Continuity compatible Brcm4360 kext
Verifying AWDL status...                OK. An AWDL interface is up, Wi-Fi is ready for Continuity
Verifying Bluetooth hardware...         OK. The internal Bluetooth card is active
Verifying Bluetooth version...          WARNING. New Bluetooth version detected (LMP Version 8), compatibility with this tool is unconfirmed
Verifying Bluetooth features...         OK. Bluetooth features are Continuity compliant
Verifying Bluetooth firmware...         OK. Bluetooth firmware version: v146 c4791
Verifying Login Item...                 OK. Login item for Auto Continuity Check is not set.

--- Modifications check ---
Verifying OS kext protection...         OK. Kext developer mode is not active. This tool can fix this.
Verifying SIP...                        Ok. System Integrity Protection is already disabled
Verifying ContinuitySupport...          OK. Already patched.
Verifying kexts readability...          OK. Wi-Fi and Bluetooth kexts were found and could be read
Verifying Wi-Fi whitelist status...     OK. Your board-id is not yet whitelisted. This tool can fix this.
Verifying BT4 dongles compatibility...  OK. Compatibility with BT4 USB dongles is not enabled, this tool can fix this if a dongle is plugged in
Verifying old Wi-Fi kext presence...    OK. Legacy Brcm4331 Wi-Fi driver is present. This tool can fix this.
Verifying legacy Wi-Fi card patch...    OK. The legacy Wi-Fi patch is not present. This tool can fix this.
--- Modifications check ---

Press any key to go back to the main menu...
 

Attachments

  • Fallen00Sniper_Frankie_iMac.ioreg
    6.5 MB · Views: 100
It should be genuine, everything is working from imessages, facetime and I get a notification if my phone rings, but it fails to answer and safari doesn't get recommended to open when I use a different device.

IOreg attached, kext-dev-mode is active and not sure why it isn't recognized below.

Also downloaded CAT to use the diag there.
Code:
--- OS X Continuity Activation Tool 2.4b5 ---
                 by sysfloat               
           original by dokterdok           
                                           

--- Initiating system compatiblity check ---

--- Hardware/OS checks ---
Verifying Continuity status...          OK. OS X reports Continuity as active
Verifying Mac model reference...        OK. Known compatible Mac Model detected: iMac11,3
Verifying Mac board-id...               OK. Short board id detected: Mac-F2238BAE
Verifying OS X version...               Warning: This tool wasn't tested with OS X versions higher than 10.10. Detected OS version: 10.12.6
Verifying Wi-Fi hardware...             OK. A Broadcom AirPort card is active, and is using the Continuity compatible Brcm4360 kext
Verifying AWDL status...                OK. An AWDL interface is up, Wi-Fi is ready for Continuity
Verifying Bluetooth hardware...         OK. The internal Bluetooth card is active
Verifying Bluetooth version...          WARNING. New Bluetooth version detected (LMP Version 8), compatibility with this tool is unconfirmed
Verifying Bluetooth features...         OK. Bluetooth features are Continuity compliant
Verifying Bluetooth firmware...         OK. Bluetooth firmware version: v146 c4791
Verifying Login Item...                 OK. Login item for Auto Continuity Check is not set.

--- Modifications check ---
Verifying OS kext protection...         OK. Kext developer mode is not active. This tool can fix this.
Verifying SIP...                        Ok. System Integrity Protection is already disabled
Verifying ContinuitySupport...          OK. Already patched.
Verifying kexts readability...          OK. Wi-Fi and Bluetooth kexts were found and could be read
Verifying Wi-Fi whitelist status...     OK. Your board-id is not yet whitelisted. This tool can fix this.
Verifying BT4 dongles compatibility...  OK. Compatibility with BT4 USB dongles is not enabled, this tool can fix this if a dongle is plugged in
Verifying old Wi-Fi kext presence...    OK. Legacy Brcm4331 Wi-Fi driver is present. This tool can fix this.
Verifying legacy Wi-Fi card patch...    OK. The legacy Wi-Fi patch is not present. This tool can fix this.
--- Modifications check ---

Press any key to go back to the main menu...

Ioreg shows Airport is Apple. However Bluetooth isn't Apple. Hands off will require work. You're USB Configuration is messy.
 
Ioreg shows Airport is Apple. However Bluetooth isn't Apple. Hands off will require work. You're USB Configuration is messy.

Not following on my USB config being messy, but the bluetooth is built into the card so what should I be doing here?
 
Not following on my USB config being messy, but the bluetooth is built into the card so what should I be doing here?

Bluetooth is showing under UHC2 which is wrong. Not sure whats going with your USB Configuration because EH01, EH02 has nothing connected but UHC1 & 2 has USB devices. Its a mess. Attach Clover folder with Themes Removed ZIP attach.
 
Bluetooth is showing under UHC2 which is wrong. Not sure whats going with your USB Configuration because EH01, EH02 has nothing connected but UHC1 & 2 has USB devices. Its a mess. Attach Clover folder with Themes Removed ZIP attach.

I haven't changed anything about the usb except patching EHC1 to EH01 etc.

What should UHCx be renamed to XHCI?
 

Attachments

  • Fallen00Sniper_CLOVER.zip
    1.3 MB · Views: 82
I haven't changed anything about the usb except patching EHC1 to EH01 etc.

What should UHCx be renamed to XHCI?

No. XHC is USB 3.0. Remove Patches. Reboot attach Clover Folder with Themes Removed & ioreg. You also have a DSDT. Messy setup. Your config is a mess.
 
No. XHC is USB 3.0. Remove Patches. Reboot attach Clover Folder with Themes Removed & ioreg. You also have a DSDT. Messy setup. Your config is a mess.

If I remove the EHC1 to EH01 my mouse and keyboard do not work, but I can use the USB 3 adapter I have to connect them.

I agree it does need to be professionally inspected for flaws.
 
Status
Not open for further replies.
Back
Top