Possible to extract BCM4360 kext from a specific SMBios?

[harun911]

First of all, hello everybody, I'm new here and also new to the whole hackintosh scene.

 

I've been fiddling around with a lot of stuff and have managed to get El Capitan running on my Dell E6410 (i5, 540M with nVidia Card).

 

The problem I am experiencing however, is that, the SmBios that suits my configuration the best is that of a Macbook Pro 6,2 because this device has exactly the same CPU as my Dell does, the problem is however, I have an Dell DW1520 wifi adapter in this laptop (I think that's a Broadcom 4322? or something) which only works when I choose the Macbook Air 5,2 Smbios configuration.  

 

Forgive me if it's a dumb question, but I was wondering if it was possible to somehow extract the DellDW1520 kext from the Macbook Air 5,2 SmBios and somehow load in the Macbook Pro 6,2 SmBios, so I can have the benefits of both SmBioses.

 

I hope someone can help me out on this one, or atleast give me some advice or pointers.

 

Thanks in advance.

[Jake Lo]

Are you using Clover or Enoch branch of Chameleon as boot loader?

You could patch the AirPortBrcm4360  with SMBIOS MBP6,2 to load DW1520.

[Hervé]

There are no kext (or kext-related info) to extract or inject in a SMBIOS file per sé, but maybe it was an excess of language on your part. In the context of Hackintoshing, a SMBIOS plist file is "just" a text file used to pretend your computer is the targeted Mac model.

 

The limitation experienced with this particular wifi card model is within the vanilla wireless kext, not within the MBA5,2 SMBIOS file in which there's nothing you can extract to inject in the MBP6,2. As indicated by Jake, it's the Broadcom kext that needs patching to support non-MBA5,2 profiles.

 

Forgive the analogy but consider it like trying to get an elephant through a cat door. Not much you can take from the cat for the elephant, it's the door that needs a bigger hole! 

[harun911]

@Jake Lo: Thanks for your response, I am using Chameleon bootloader, I experienced problems with running Clover on this laptop.

 

@Herve: Thanks for your response and the brief explanation. I think I have a better idea of the whole now.

 

My next question would logically be then, how do I patch AirPortBrcm4360.kext file to support the MBP6,2 profile?

 

Thanks again, guys.

[Hervé]

I knew this would be your next question, so I anticipated a little! 

https://osxlatitude.com/index.php?/topic/8739-patching-airportbrcm4360-kext-for-unsupported-mac-models/

[harun911]

You, sir. Are a HERO!

Finally, correct SMBios and Wifi capability.

 

Thank you very much for the very detailed tutorial on how to get stuff done.

 

I had one more question, if it's okay with you guys though?

The Dell Dw1520 is also known as the Broadcomm 43224, In the same folder as where I patched the AirPortBrcm4360.kext, another file resides named AppleAirPortBrcm43224.kext. 

 

Does anyone know what this file exactly stands for? Because from the looks of it, it looks like that is the appropriate driver for my card (just guessing).

 

Seeing the fact, that this driver I'm using now (the AirPortBrcm4360.kext) is not really stable. I experience frequent drop-outs, every couple of seconds disconnecting and reconnecting. 

 

I mean, I'm happy to have atleast some sort of Wifi, but it's not optimal if you know what I mean.

 

Thanks again for all your efforts!

[Bronxteck]

what network is it connecting to 2.4 or 5 ghz? as i think there might also be a 5ghz patch needed but i am not positive.

[Hervé]

You can confirm what kext applies or should apply to your card by looking at the PCI ids listed in the Info plist of each kext. DW1520 normally bears Vendor id 14e4 (i.e. Broadcom) and device id 4353. You'll clearly see that inside AirPortBrcm4360 (and Brcm4331 too!) but not in the Brcm43224 kext. That one is for older 802.11a/b/g cards such as the DW1390, DW1490, etc.