Discussion in 'Network' started by tonymacx86, Sep 19, 2016.
Good find! No edited kexts or patches in Clover config ?
Yeah, well almost...Airdrop, Continuity and the likes work but Handoff seems broken even though everything seems enabled...
Logged out of iCloud on all devices, relogged, turned handoff off and on again, doesn't seem to work even though everything seems to check out....:/
CAT diagnostics output, everything checks out:
--- 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: MacPro5,1
Verifying Mac board-id... OK. Short board id detected: Mac-F221BEC8
Verifying OS X version... Warning: This tool wasn't tested with OS X versions higher than 10.10. Detected OS version: 10.12
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. 3rd party Bluetooth hardware detected
Verifying Bluetooth version... OK. Bluetooth 4.0 detected
Verifying Bluetooth features... OK. Bluetooth features are Continuity compliant
Verifying Bluetooth firmware... OK. Bluetooth firmware version: v126 c9196
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... NOT OK. System Integrity Protection is still enabled
Verifying ContinuitySupport... OK. This tool can fix this.
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 ---
I have a BCM943602CS card+adapter and it never worked either on Sierra or Windows. In Windows it refuses to accept Bootcamp drivers, and MAcOS doesnt even bother using it. I am at my wit's end at this point, as I tried a few other options already and I waited long months for this junk to arrive from China. Can you please help me and tell me which damn card actually works? The one I have is supposed to work OOB, what am I doing wrong?
would it worth trying to fix my bcm4311 working with Sierra? (4311/14e4)
Or no way possible?
Also another trick, what about if you rebrand the firmware?
I have the same problem with my BCM943602CS. It worked perfectly under 10.11.6. And it worked for one or two days unter 10.12.1. I have no Idea what I did, but since of today, I can't activate my wifi anymore (bluetooth still working). It is recognized in the system specifications:
Kartentyp: AirPort Extreme (0x14E4, 0x111)
Firmware-Version: Broadcom BCM43xx 1.0 (220.127.116.11.1a8)
Can I check if I have a wrong kext in S/L/E? (or anywhere else?)
Thanks for your help.
Did you get this working?
Still not working.
I've got your same card and it actually never worked for me. I didn't test it under El Cap, so probably I might have missed my only opportunity to have it up and running. Of course here messages like yours or mine go completely ignored, because no one actually knows what is going on, and 90% of forum banter is as useless and dispersive as it gets.
I installed Sierra on my laptop, work fine but Wi-Fi no. Wi-Fi card: Broadcom BCM43227. Anyone know something for make work this or must buy another compatible?
For some reason my Bluetooth works but not the wifi.
Separate names with a comma.