Jump to content
InsanelyMac Forum
toleda

Airport - PCIe Half Mini

Recommended Posts

Since update from 10.12 to 10.12.1 the wlan symbol is grey

See Post #1/Airport Injection Methods/1. kext enabler

Update FakePCIID.kext and FakePCIID_Broadcom_WiFi.kext

Share this post


Link to post
Share on other sites
Advertisement

I've just installed a Broadcom BCM94360CD using the PCI-E 1X Wireless Adapter With 4 Round Type Antenna For BCM94360CD.
 
It works out the box no kexts needed but am i getting all of the functionality? I'm able to connect Bluetooth headphones, wireless seems to work ok ( I have ethernet working anyway )
 
Just not sure how to test

Share this post


Link to post
Share on other sites

See Post #1/Airport Injection Methods/1. kext enabler

Update FakePCIID.kext and FakePCIID_Broadcom_WiFi.kext

 

Hey, thank you but it doesnt change anything :(

Share this post


Link to post
Share on other sites

There are now changes in the files?

 

I had only replace the FakePCIID.kext and FakePCIID_Broadcom_WiFi.kext with new versions?

If i have to do more, i dont unterstand the post #1 complete.

 

Because my englisch is not the best ;)

Share this post


Link to post
Share on other sites

 had only replace the FakePCIID.kext and FakePCIID_Broadcom_WiFi.kext with new versions?

If done correctly, that changes everything.

Last request, reply with new files attached.

Share this post


Link to post
Share on other sites

Ok I have the AzureWare Brcm4352 and have noticed a bug related to Country Code. My router is set for 2.4GHz at 40MHz and 5GHz at 80MHz but have the following issues. If I set my Country Code to CA for my region, I get 2.4GHz at 40MHz like I should but 5 GHz after sleep is limited at 40MHz so only 270Mbps speed. If I set my Country Code to #a or keep it as US, I get the proper 5GHz 80MHz 585Mbps but 2.4 is stuck at 20MHz so I only get max speeds at 145Mbps. I am using the FakePCI with just the Fcvo patch to enable my WiFi and the Country Code change via Clover injection. Is there any suggestion?

 

PS Wireless Diagnostic does show the proper network information no matter which Country Code I am on but WiFi connection only shows the lower speeds mentioned above.

Share this post


Link to post
Share on other sites

Hi Toleda

I have this combo card BCM94352HMB/AzureWave AW-CB123H 5 GHz , all works (wi-fi 5ghz , airport, bluetooth).  (Apple magic Mouse 2)
But the problem is the frustrating lagging mouse clear.png

I install the BT installing this kext :

BrcmPatchRAM2.kext 

how can i solve ?

 

Can be a solution relace this kext with :

BrcmBluetoothInjector.kext

Sierra 10.12.1

 

Share this post


Link to post
Share on other sites

See Post #1/BCM BT/download latest /Install 2 kexts as noted.

  1. BrcmPatchRAM2.kext (firmware update)
  2. BrcmBluetoothInjector.kext (device_ids only)

 

Both or only 2nd ?

Share this post


Link to post
Share on other sites

 

  1. BrcmPatchRAM2.kext (firmware update)
  2. BrcmBluetoothInjector.kext (device_ids only)

 

Both or only 2nd ?

 

Either only install BrcmBluetoothInjector.kext or install the following

 

- BrcmPatchRAM2.kext

- BrcmFirmwareRepo (if installed to L/E) or BrcmFirmwareData (if installed to Clover)

 

I've had the best success with installing both BrcmPatchRAM2 and BrcmFirmwareRepo/BrcmFirmwareData. You can see the official readme from Rehabman here to describe what I mentioned.

Share this post


Link to post
Share on other sites

Either only install BrcmBluetoothInjector.kext or install the following

 

- BrcmPatchRAM2.kext

- BrcmFirmwareRepo (if installed to L/E) or BrcmFirmwareData (if installed to Clover)

 

I've had the best success with installing both BrcmPatchRAM2 and BrcmFirmwareRepo/BrcmFirmwareData. You can see the official readme from Rehabman here to describe what I mentioned.

Thx  :angel: i try ;)

Share this post


Link to post
Share on other sites

I know that this post says that WiFi injection via Clover no longer works with 10.12.1 but I had it working with 10.12.1 and 10.12.2 using the following Clover kext patches:

		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>FVCO</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				gflSqgAAdSk=
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				gflSqgAAZpA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPortBrcm4360 - PCI Error 1</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				QTnEdRs=
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				QTnEZpA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPortBrcm4360 - PCI Error 2</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				QQ+3zTnBdQw=
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				QQ+3zTnBZpA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPortBrcm4360 - PCI Error 3</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g33EBHQG
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				g33EBGaQ
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Handoff Patch</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				SIX/dEdIiwc=
				</data>
				<key>Name</key>
				<string>IOBluetoothFamily</string>
				<key>Replace</key>
				<data>
				Qb4PAAAA60Q=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPort Extreme Cosmetic Fix</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				axAAAHUN
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				axAAAJCQ
				</data>
			</dict>
		</array>
	</dict>

I believe the proper credit goes to bpresles for this.  https://github.com/toleda/wireless_half-mini/issues/6

 

I hope it helps someone obtain WiFi connectivity.

Share this post


Link to post
Share on other sites

I know that this post says that WiFi injection via Clover no longer works with 10.12.1 but I had it working with 10.12.1 and 10.12.2 using the following Clover kext patches:

		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>FVCO</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				gflSqgAAdSk=
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				gflSqgAAZpA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPortBrcm4360 - PCI Error 1</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				QTnEdRs=
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				QTnEZpA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPortBrcm4360 - PCI Error 2</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				QQ+3zTnBdQw=
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				QQ+3zTnBZpA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPortBrcm4360 - PCI Error 3</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g33EBHQG
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				g33EBGaQ
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Handoff Patch</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				SIX/dEdIiwc=
				</data>
				<key>Name</key>
				<string>IOBluetoothFamily</string>
				<key>Replace</key>
				<data>
				Qb4PAAAA60Q=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AirPort Extreme Cosmetic Fix</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				axAAAHUN
				</data>
				<key>Name</key>
				<string>AirPortBrcm4360</string>
				<key>Replace</key>
				<data>
				axAAAJCQ
				</data>
			</dict>
		</array>
	</dict>
I believe the proper credit goes to bpresles for this.  https://github.com/toleda/wireless_half-mini/issues/6

 

I hope it helps someone obtain WiFi connectivity.

 

WiFi: You only need the 'fcvo' patch and FakePCIID.kext + FakePCIID_Broadcom_WiFi.kext (current version).

Share this post


Link to post
Share on other sites

WiFi: You only need the 'fcvo' patch and FakePCIID.kext + FakePCIID_Broadcom_WiFi.kext (current version).

 

Not so for the Azurewave AW-CE123H.  That's what the GitHub link is about.  Your method doesn't work for me unless I use the 3 additional PCI patches, and when I use those patches, I don't need your FakePCIID.kext or the Broadcom kext you use with it.  A simple DSDT patch to make pci14e4,43a0 compatible is all I need.

Share this post


Link to post
Share on other sites

Not so for the Azurewave AW-CE123H.

You are wrong. Those "PCI error" patches are not necessary when using the current FakePCIID kexts.

Share this post


Link to post
Share on other sites

You are wrong. Those "PCI error" patches are not necessary when using the current FakePCIID kexts.

 

Toleda made the same claim in the Github link.  FakePCIID, the newest one, along with the Broadcom kext, didn't work for me.  The PCI patches did.  This is just a repeat of the Github debate.

Share this post


Link to post
Share on other sites

Toleda made the same claim in the Github link.  FakePCIID, the newest one, along with the Broadcom kext, didn't work for me.  The PCI patches did.  This is just a repeat of the Github debate.

Prove it. Provide EFI/Clover (as ZIP, without themes). And ioreg (IORegistryExplorer v2.1). And output of 'sudo kextcache -i /'.

 

Hint: I think I can guess what your mistake is...

Share this post


Link to post
Share on other sites

Prove it. Provide EFI/Clover (as ZIP, without themes). And ioreg (IORegistryExplorer v2.1). And output of 'sudo kextcache -i /'.

 

Hint: I think I can guess what your mistake is...

 

I'm totally up for figuring this out and have no problem admitting a mistake if that's the case.  I'm not 100% sure what you need to see.  Do you want to see what I have that works (i.e. my current set up) or do you want to see what my system looks like when I set it up with just the things that you suggest to make wifi work?  I have the time today to do both if that's preferable.

 

OK, I had to upload the files to my dropbox because the file size exceeded forum limits.  Here's the link:

 

https://www.dropbox.com/s/9y5v04g5tbybozc/With%20and%20Without%20PCIID.zip?dl=0

 

In the EFI/Clover directory, there are two config.plist files.  The one named config.plist has the PCI Error patches.  The one named config-10.12.0.plist does not.  When I boot with config-10.12.0.plist and have PCIID.kext and the Broadcom kext in my kexts/10.12 folder or S/L/E, the wifi device is not recognized.  When I boot with config.plist and do not use PCIID or the Broadcom kext, wifi works perfectly.

 

Oh, one last thing,  I used IORegistryExplorer v3.0.2.  I don't have v2.1 anymore.

Share this post


Link to post
Share on other sites

I'm totally up for figuring this out and have no problem admitting a mistake if that's the case.  I'm not 100% sure what you need to see.  Do you want to see what I have that works (i.e. my current set up) or do you want to see what my system looks like when I set it up with just the things that you suggest to make wifi work?  I have the time today to do both if that's preferable.

 

OK, I had to upload the files to my dropbox because the file size exceeded forum limits.  Here's the link:

 

https://www.dropbox.com/s/9y5v04g5tbybozc/With%20and%20Without%20PCIID.zip?dl=0

 

In the EFI/Clover directory, there are two config.plist files.  The one named config.plist has the PCI Error patches.  The one named config-10.12.0.plist does not.  When I boot with config-10.12.0.plist and have PCIID.kext and the Broadcom kext in my kexts/10.12 folder or S/L/E, the wifi device is not recognized.  When I boot with config.plist and do not use PCIID or the Broadcom kext, wifi works perfectly.

 

Oh, one last thing,  I used IORegistryExplorer v3.0.2.  I don't have v2.1 anymore.

Your mistake...

 

The DSDT patch you have applied to inject various WiFi device properties at RP01.PXSX is wrong.

It is injecting an incorrect device-id, which causes FakePCIID to spoof that incorrect device-id when the driver queries it from IOPCIDevice.

You need to remove that patch, or at least don't inject device-id.

Also note that the device-id you are using(0x2a) is complete nonsense for BCM9432... from your DSDT.aml:

                            "device-id", 
                            Buffer (0x04)
                            {
                                 0x2A, 0x00, 0x00, 0x00                         
                            }, 
Using a device-id other than native is wrong. But using 0x2a is nonsense.

Share this post


Link to post
Share on other sites

Your mistake...

 

The DSDT patch you have applied to inject various WiFi device properties at RP01.PXSX is wrong.

It is injecting an incorrect device-id, which causes FakePCIID to spoof that incorrect device-id when the driver queries it from IOPCIDevice.

You need to remove that patch, or at least don't inject device-id.

Also note that the device-id you are using(0x2a) is complete nonsense for BCM9432... from your DSDT.aml:

                            "device-id", 
                            Buffer (0x04)
                            {
                                 0x2A, 0x00, 0x00, 0x00                         
                            }, 
Using a device-id other than native is wrong. But using 0x2a is nonsense.

 

 

This is all very interesting.  I got the DSDT patch from OldNapalm which I originally used for an Atheros wifi card.  Here is the link:

 

http://www.insanelymac.com/forum/topic/289824-atheros-9285/

 

When I got my Azurewave AW-CE123H, I just changed the PID/VID.

 

My DSDT doesn't actually say that the device id is 0x2A, 0x00, 0x00, 0x00, even if that's what it translates to.  Mine says this:

              "device-id",
              Unicode ("*"),

I never really understood why MacIASL converted the device id to that but I recall being told that it was the proper syntax for what I entered and I never tried to understand it better than that.  I'm testing out your diagnosis and will post the results.

 

Yep, removing the device-id from my DSDT made your method work.  Thank you for taking the time to clear that up for me. Now, just for my own education, is there a reason that it is better to use the two additional kexts (FakePCIID.kext and the Broadcom kext) rather than the 3 additional (PCI Error) kext patches?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



×