[Guide] Airport - PCIe Half Mini v2

[the-darkvoid]

The existing patch for 10.10.1 and 10.10.2 still works fine on 10.10.3:

Find:    E8510E000085C074 
Replace: 66C70655539090EB

This makes the WiFi card show as US/FCC (and enables according channels, incl. 5ghz)

 

[mosser]

I have a problem the card i have is Lite-On and it works well sort of.

problem is if i dual boot windows. after rebooting and then going back in to os x bluetooth do not work

i use brcmPatchRom.kext and im running 10.10.3 on clover 3193

if i then shutdown the machine and unhook the power cable bluetooth works again until i boot windows and reboot to os x

help would be appreciated

kind regards Mosser

 

[RehabMan]

I have a problem the card i have is Lite-On and it works well sort of.

problem is if i dual boot windows. after rebooting and then going back in to os x bluetooth do not work

i use brcmPatchRom.kext and im running 10.10.3 on clover 3193

if i then shutdown the machine and unhook the power cable bluetooth works again until i boot windows and reboot to os x

help would be appreciated

kind regards Mosser

BrcmPatchRAM.kext will not load firmware into the device when firmware is already loaded. In the case of a restart from Windows, you have the firmware that the Windows drivers pushed. Check system.log to see which firmware it is. Try to arrange the Windows drivers to use the same firmware that BrcmPatchRAM has for your device.

 

[mosser]

BrcmPatchRAM.kext will not load firmware into the device when firmware is already loaded. In the case of a restart from Windows, you have the firmware that the Windows drivers pushed. Check system.log to see which firmware it is. Try to arrange the Windows drivers to use the same firmware that BrcmPatchRAM has for your device.

how can i locate the firmware in system.log ?


from about this mac i can see bluetooth is firmware

Firmwareversion: v14 c5708 so how do i change this in windows to use the same firmware drivers ?

Mosser

 

[RehabMan]

how can i locate the firmware in system.log ?

Filter system.log for 'brcmpatchram' in Console.app.

Or you can do what you did below...

from about this mac i can see bluetooth is firmware

Firmwareversion: v14 c5708 so how do i change this in windows to use the same firmware drivers ?

Mosser

Is that after restarting from Windows or after cold boot using BrcmPatchRAM firmware?

Check both scenarios to compare versions.

Then search for updated firmware/drivers for Windows.

 

[jaymonkey]

The existing patch for 10.10.1 and 10.10.2 still works fine on 10.10.3:

Find:    E8510E000085C074 
Replace: 66C70655539090EB

This makes the WiFi card show as US/FCC (and enables according channels, incl. 5ghz)

@Darkviod,

After installing 10.10.3 update i was no longer able to access 5Ghz WiFi
I disabled Skvo's old 5 Ghz patch and switched to using your above patch.

5Ghz is working again, but it only works for the initial boot, once system is put to sleep then 5Ghz is no longer available on wake up. I have AW-CE123H WiFi/BT4 card and the system i'm working on is my Sony Vaio Laptop (see Signature)

I suspect that it could be down to the 'old' method i'm using to get the card running which i documented around March last year :-

http://www.tonymacx86.com/mavericks...sony-vpc-se-customac-build-32.html#post774456

In summary the method involves using the following kext's

TolediaAPRT.kext & BCM4352.kext from Toledia's Reop here.
BTFirmwareUploader.kext from EMlyDinEsH's Post here.

And Skvo's 5Ghz & Airport Extreme patches (now applied via Clover since updating to Yosemite 10.10.x)

Up until 10.10.3 WiFi & BT4 have worked perfect, but it looks like things have changed quite a bit with 10.10.3, I Would be interested to know what your recommended install method is for AW-CE123H now that there are alternate methods and kexts ....

Cheers
Jay

 

[RehabMan]

@Darkviod,

After installing 10.10.3 update i was no longer able to access 5Ghz WiFi
I disabled Skvo's old 5 Ghz patch and switched to using your above patch.

5Ghz is working again, but it only works for the initial boot, once system is put to sleep then 5Ghz is no longer available on wake up. I have AW-CE123H WiFi/BT4 card and the system i'm working on is my Sony Vaio Laptop (see Signature)

I suspect that it could be down to the 'old' method i'm using to get the card running which i documented around March last year :-

http://www.tonymacx86.com/mavericks...sony-vpc-se-customac-build-32.html#post774456

In summary the method involves using the following kext's

TolediaAPRT.kext & BCM4352.kext from Toledia's Reop here.
BTFirmwareUploader.kext from EMlyDinEsH's Post here.

And Skvo's 5Ghz & Airport Extreme patches (now applied via Clover since updating to Yosemite 10.10.x)

Up until 10.10.3 WiFi & BT4 have worked perfect, but it looks like things have changed quite a bit with 10.10.3, I Would be interested to know what your recommended install method is for AW-CE123H now that there are alternate methods and kexts ....

Cheers
Jay

You need only...

WiFi:
- 5Ghz patch
- FakePCIID.kext/FakePCIID_BCM*.kext

Bluetooth:
- Handoff patch
- BrcmPatchRAM.kext.

BTFirmwareUploader.kext is known to be buggy. It is also not open source, so it is likely to stay that way.

 

[custom-mac]

Try this:

Find:

[STRIKETHRU]58540042193D2100005854[/STRIKETHRU]

Replace:

[STRIKETHRU]55531A04191D2100005553[/STRIKETHRU]

Turns the card into US, worked for me at least.

Edit: Use the find/replace below this post instead. Works much better.

Worked for me too.

But this one show 5GHz, but fails to connect:
Find: E8510E000085C074
Replace: 66C70655539090EB

It most likely is caused by different WiFi adapters, mine is/was XT.

 

[mosser]

Filter system.log for 'brcmpatchram' in Console.app.

Or you can do what you did below...



Is that after restarting from Windows or after cold boot using BrcmPatchRAM firmware?

Check both scenarios to compare versions.

Then search for updated firmware/drivers for Windows.

it was after cold boot

okay so now i just need to find drivers containing matching firmware ?


Mosser

 

[RehabMan]

it was after cold boot

okay so now i just need to find drivers containing matching firmware ?


Mosser

Matching or new enough to work with Yosemite...

Or always do cold boot into Yosemite.