[Guide] Airport - PCIe Half Mini v2

[RehabMan]

I have used BCM4352.kext so far - which I get the impression is ALL that is needed.

Am I missing something, do I need to do something else? Anyone could help please?

I think it is all that you need.

It is not seen as a PCI in System Information but is seen as a BT device, vendor 0x13d3, product ID 0x3404.

You mean USB device.

One way I have thought of doing things is to edit the ioProduct & ioVendor in the info.plist, but even then it will have been the first time I would have done this, the file is locked and is signed by Aple, so I guess there will be more to it than that. Further, there are other hex pairs that differ.

In what Info.plist? That vendor/device-id is already present in BCM4352.kext.

There is no difference in having it inside of the enabler/injector BCM4352.kext vs. having it in the official Apple BT kext.

 

[jonessl]

I think it is all that you need.



You mean USB device.



In what Info.plist? That vendor/device-id is already present in BCM4352.kext.

There is no difference in having it inside of the enabler/injector BCM4352.kext vs. having it in the official Apple BT kext.

Thanks for replying. Sorry, Toleda's (github) documentation refers to PCI (that's what his PDFs show) and mine is in a PCIe slot. Yes, it's in USB too. With the same hex pair shown.

Unfortunately, the BCM4352 kext, while referring to the same card (I've looked again, and in his documentation he uses the AE and AW interchangeableably) appears to have differing hex pairs. As I said if it was consistent throughout the info.plist (i.e. just these two pairs) I'd "have a go" but because there are many pairs, I don't know which ones to edit, or what numbers to use. (For example, in the info.plist within the BCM4352 container, he has a BCM4352 and a AW-CE123H Controller, both with different hex pairs).

 

[RehabMan]

Thanks for replying. Sorry, Toleda's (github) documentation refers to PCI (that's what his PDFs show) and mine is in a PCIe slot. Yes, it's in USB too. With the same hex pair shown.

Unfortunately, the BCM4352 kext, while referring to the same card (I've looked again, and in his documentation he uses the AW and AW interchangeableably) appears to have differing hex pairs. As I said if it was consistent throughout the info.plist (i.e. just these two pairs) I'd "have a go" but because there are many pairs, I don't know which ones to edit, or what numbers to use. (For example, in the info.plist within the BCM4352 container, he has a BCM4352 and a AW-CE123H Controller, both with different hex pairs).

WiFi is on PCIe bus. BT is on USB bus. The fact that they share a half-mini PCIe PCB is not relevant.

The IOKit personalities list all possibilities, that's why you see multiple "pairs."

 

[jonessl]

WiFi is on PCIe bus. BT is on USB bus. The fact that they share a half-mini PCIe PCB is not relevant.

The IOKit personalities list all possibilities, that's why you see multiple "pairs."

I know I'm asking a lot, but could you kindly look at his kext and see what I might change to get it to work, given the number of controllers (and your huge competence versus my minimal competence). I'd wait for Toleda but he seems very inactive[on this] for the last few weeks. The file is quite short, and if it is easy to modify I will do so. My vendorID is 0x13d3 and my productID is 0x3404.

I know the sysops like to see everything done publicly, so if you were to look and comment, others could benefit beyond me.

Fingers crossed!

 

[RehabMan]

I know I'm asking a lot, but could you kindly look at his kext and see what I might change to get it to work, given the number of controllers (and your huge competence versus my minimal competence). I'd wait for Toleda but he seems very inactive[on this] for the last few weeks. The file is quite short, and if it is easy to modify I will do so. My vendorID is 0x13d3 and my productID is 0x3404.

I know the sysops like to see everything done publicly, so if you were to look and comment, others could benefit beyond me.

Fingers crossed!

The work has already been done in toleda's bcm4352.kext and bcm4352bt.kext. Refer to his entries to add them to your own if you wish (for some reason) to use your own kext.

BTW, if you install toleda's kext and the drivers recognize the device and BT is available, then that's all that you can do. Problems with the reliability come down to how compatible (or not compatible) the device is with the OS X drivers and your specific BT devices.

 

[jonessl]

The work has already been done in toleda's bcm4352.kext and bcm4352bt.kext. Refer to his entries to add them to your own if you wish (for some reason) to use your own kext.

BTW, if you install toleda's kext and the drivers recognize the device and BT is available, then that's all that you can do. Problems with the reliability come down to how compatible (or not compatible) the device is with the OS X drivers and your specific BT devices.

This is my experience. There were more permutations than those shown, as I needed to get BT working again via Windows once it was broken.

(Try 1) Starting point. Using BCM4352.kext alone. Wifi great, BT shown but doesn't do anything. (Well actually it did, once, it found a BT keyboard, asked me to type in the pairing number and then went away, losing the connection with the keyboard).

(Try 2) I did the edits to the info.plist files for the two kext folders (IO80211Family & IOBluetoothFamily) described in the github referered to in the OP of this thread. The BT searched for devices, found a BT magic pad but would not pair. (I also tried the BT keyboard again). This behaviour is as described in another post for the same card (see #73).

(Try 3) When I rebooted, I could not get the trackpad or keyboard.

(Try 4) Adding BTFirmwareUploader1.2.kext from OSX Lattitude (with other kexts in place). This broke Bluetooth.

I then tried:

(Try 5) Reinstating the original IO80211Family & IOBluetoothFamily and removing BCM4352.kext (the toleda one). So now it is just the BTFirmwareUploader1.2 kext. Still broken.

(Try 6) Tried newer version of BTFimrwareUploader (1.5), injected card id into info.plist of BroadcomBluetoothHostControllerUSBTransport.kext. Instructions on OSXLattitude say do this on BroadcomBluetoothHCIControllerUSBTransport.kext but this is not present in IOBluetoothFamily (on my system anyhow).

CAN ANYONE ELSE CHECK WHETHER THEIR IOBluetoothFamily.kext has the BroadcomBluetoothHCIControllerUSBTransport.kext in it, because mine did not and my edit here may have been pointless (even though the structure of the plist is the same).

And finally:

(Try 7) 4048-Broadcom-BCM4352-mav.zip - by Zackptg5 from another well known OSX86 site, containing three kexts. This did not work with the original two edited kexts from try 2(AirPortBrcm4360 & BroadcomBluetoothHostControllerUSBTransport) in place (no device found by BT).

(Try 8) Now with just the 3 newer kexts in place from Zacptg5. No trackpad found again.

(Try 9) 4125-IOBluetoothFamily.kext.zip - by Zackptg5 again. No trackpad found again.

Used Kext Wizard, rebuilt cache, EC reset between each set. Due to Clover autoinjection, care taken the S/L/E and kexts/10.9 were synced.

This is probably a bit mixed up as I have been at it for a long time and am getting tired. (It took time to go back to Windows, do EC resets, make sure old kexts were removed and kext cache rebuilt).

I'm giving up now.

I give up. This is very disappointing, as the card cost me a staggering $100, and I bought it mainly on the claims in the OP that "it would work" (other reasons were ac, and widi). It doesn't work. Not for me anyhow.

 

[jonessl]

Hey gents. Received my AzureWave AW-CE123H the other day.

The bluetooth works perfect after rebuilding cache and a reboot with the BT firmware uploader kext. To be honest I did not even take the time to really go through the write-up they did. I will revisits the post this coming weekend.

Mad Audi,

Could you please say exactly what you did in terms of the associated kexts history:

(a) did you use the 1.2 or other version of the firmware updater.
(b) did you bother with a kext edit
(c) most important, did you edit the IOBluetoothFamily kext, and was this vanilla?

I ask because I have EXACTLY the same card as you can cannot get it to work with BT.

PLEASE HELP!

 

[RehabMan]

This is my experience. There were more permutations than those shown, as I needed to get BT working again via Windows once it was broken.

(Try 1) Starting point. Using BCM4352.kext alone. Wifi great, BT shown but doesn't do anything. (Well actually it did, once, it found a BT keyboard, asked me to type in the pairing number and then went away, losing the connection with the keyboard).

(Try 2) I did the edits to the info.plist files for the two kext folders (IO80211Family & IOBluetoothFamily) described in the github referered to in the OP of this thread. The BT searched for devices, found a BT magic pad but would not pair. (I also tried the BT keyboard again). This behaviour is as described in another post for the same card (see #73).

(Try 3) When I rebooted, I could not get the trackpad or keyboard.

(Try 4) Adding BTFirmwareUploader1.2.kext from OSX Lattitude (with other kexts in place). This broke Bluetooth.

I then tried:

(Try 5) Reinstating the original IO80211Family & IOBluetoothFamily and removing BCM4352.kext (the toleda one). So now it is just the BTFirmwareUploader1.2 kext. Still broken.

(Try 6) Tried newer version of BTFimrwareUploader (1.5), injected card id into info.plist of BroadcomBluetoothHostControllerUSBTransport.kext. Instructions on OSXLattitude say do this on BroadcomBluetoothHCIControllerUSBTransport.kext but this is not present in IOBluetoothFamily (on my system anyhow).

CAN ANYONE ELSE CHECK WHETHER THEIR IOBluetoothFamily.kext has the BroadcomBluetoothHCIControllerUSBTransport.kext in it, because mine did not and my edit here may have been pointless (even though the structure of the plist is the same).

And finally:

(Try 7) 4048-Broadcom-BCM4352-mav.zip - by Zackptg5 from another well known OSX86 site, containing three kexts. This did not work with the original two edited kexts from try 2(AirPortBrcm4360 & BroadcomBluetoothHostControllerUSBTransport) in place (no device found by BT).

(Try 8) Now with just the 3 newer kexts in place from Zacptg5. No trackpad found again.

(Try 9) 4125-IOBluetoothFamily.kext.zip - by Zackptg5 again. No trackpad found again.

Used Kext Wizard, rebuilt cache, EC reset between each set. Due to Clover autoinjection, care taken the S/L/E and kexts/10.9 were synced.

This is probably a bit mixed up as I have been at it for a long time and am getting tired. (It took time to go back to Windows, do EC resets, make sure old kexts were removed and kext cache rebuilt).

I'm giving up now.

I give up. This is very disappointing, as the card cost me a staggering $100, and I bought it mainly on the claims in the OP that "it would work" (other reasons were ac, and widi). It doesn't work. Not for me anyhow.

I think the problem is you're trying too many random things. Once you get the drivers to load (as verified in ioreg?), you're done. Other than devices that have loadable firmware, there is nothing you can do beyond that. Either the BT drivers are compatible with your device/scenario or they are not.

Doing a bunch of other random things when you already had drivers loading is pointless...

 

[jonessl]

RehabMan, thanks. I will not be able to look at this again for some weeks.

In the meantime, you often say a checkered kext history requires a reinstall of OSX to clear things up. If I simply delete kexts from S/L/E and rebuild the cache is that enough, or does OSX get in a mess anyhow?

Also, if I ever want to get (say) the vanilla IOBluetoothFamily.kext, is there a way that I can get it from the OSX dmg? (Please).

 

[RehabMan]

...

In the meantime, you often say a checkered kext history requires a reinstall of OSX to clear things up. If I simply delete kexts from S/L/E and rebuild the cache is that enough, or does OSX get in a mess anyhow?

Also, if I ever want to get (say) the vanilla IOBluetoothFamily.kext, is there a way that I can get it from the OSX dmg? (Please).

Answer moved here: http://www.tonymacx86.com/mavericks-laptop-support/116508-questions-regarding-kext-management.html