Contribute
Register

BCM94350ZAE (14e4:43a3) not working in 10.11

Status
Not open for further replies.
Before handling the DSDT, I got the same problem that the Model ID do not display correctly. Mine also just display "MacBookPro1" despite I have "MacBookPro12,1" in SMBIOS section. However, when I enter "Macbook8,1", it works. I really do not know what problem is it.

It is not known why the model is truncated. It is a problem affecting certain laptops.

--

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)

Mobo: manufacturer/model + bootloader(Clover/Chameleon/Chimera)
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
Mobo: HP ProBook 4540s (Clover)
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx), and graphics capabilities. For a laptop, these details are important and affect critical installation procedures.

Note: When specifying your bootloader, if using Clover legacy, please be sure to specify "Clover legacy"). Specifying "Clover" will be assumed as "Clover UEFI"
 
Some news about this wifi card...

I think that the problem with this card is that firmware can't be uploaded through USB interface (BCM2045A0).
It might be because of different broadcom upload protocol for this card... different regarding implemented protocol in BrcmPatchRAM2.kext.
So that would explain why BrcmPatchRAM2.kext is looping saying "device request failed" even if the USB device is well recognized by OS X:

BCM2045A0 :

Identifiant du produit : 0x6412
Identifiant du fournisseur : 0x0a5c (Broadcom Corp.)
Version : 1.12
Numéro de série : XXXXXXXXXXX (deleted before posting)
Vitesse : Jusqu’à 12 Mb/s
Fabricant : Broadcom Corp
Identifiant de l’emplacement : 0x14300000 / 1
Courant disponible (mA) : 1000
Courant requis (mA) : 0
Exploitation supplémentaire actuelle (mA) : 0
Intégré : Oui

Looking in details into windows driver let me think the protocol used for this card is DHD (Broadcom Dongle Host Driver).

When rebooting from windows, as the USB device and pci card are still powered, I guess that the firmware stay loaded, so it's working under OS X, without BrcmPatchRAM2.kext even trying to upload firmware: it says firmware is already uploaded or something like this.

@RehabMan do you think there is a way to make firmware upload to work ?

Thanks :)
 
Some news about this wifi card...

I think that the problem with this card is that firmware can't be uploaded through USB interface (BCM2045A0).
It might be because of different broadcom upload protocol for this card... different regarding implemented protocol in BrcmPatchRAM2.kext.
So that would explain why BrcmPatchRAM2.kext is looping saying "device request failed" even if the USB device is well recognized by OS X:

BCM2045A0 :

Identifiant du produit : 0x6412
Identifiant du fournisseur : 0x0a5c (Broadcom Corp.)
Version : 1.12
Numéro de série : XXXXXXXXXXX (deleted before posting)
Vitesse : Jusqu’à 12 Mb/s
Fabricant : Broadcom Corp
Identifiant de l’emplacement : 0x14300000 / 1
Courant disponible (mA) : 1000
Courant requis (mA) : 0
Exploitation supplémentaire actuelle (mA) : 0
Intégré : Oui

Looking in details into windows driver let me think the protocol used for this card is DHD (Broadcom Dongle Host Driver).

When rebooting from windows, as the USB device and pci card are still powered, I guess that the firmware stay loaded, so it's working under OS X, without BrcmPatchRAM2.kext even trying to upload firmware: it says firmware is already uploaded or something like this.

@RehabMan do you think there is a way to make firmware upload to work ?

Thanks :)

There is support for this device in the most recent BrcmPatchRAM. Look at the Info.plist and you'll see...
 
Oh yes product id is present !
I can't understand why the kext and the usb device can't communicate.
Here is my log in console:
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: device request failed ("0xe00002ed (UNDEFINED)" 0xe00002ed).
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: Not responding - Delaying next read.
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: device request failed ("0xe00002ed (UNDEFINED)" 0xe00002ed).
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: Not responding - Delaying next read.
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: device request failed ("0xe00002ed (UNDEFINED)" 0xe00002ed).
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: Not responding - Delaying next read.

and so on...
 
Oh yes product id is present !
I can't understand why the kext and the usb device can't communicate.
Here is my log in console:
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: device request failed ("0xe00002ed (UNDEFINED)" 0xe00002ed).
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: Not responding - Delaying next read.
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: device request failed ("0xe00002ed (UNDEFINED)" 0xe00002ed).
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: Not responding - Delaying next read.
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: device request failed ("0xe00002ed (UNDEFINED)" 0xe00002ed).
25/07/2016 20:01:50,000 kernel[0]: BrcmPatchRAM2: [0a5c:6412]: Not responding - Delaying next read.

and so on...

Attach ioreg as ZIP: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.
 
Here it is

Your USB configuration looks wrong. Many ports that should be marked external (UsbConnector= 0 or 3) are marked internal (UsbConnector=255).

Also, power management is not implemented. SMBIOS is messed up (MacBookPro1?). AppleLPC is not loaded (ACPI patches not correct). Also, don't install other 3rd party stuff until your system is stable (HoRNDIS, for example).

You should address fundamentals before focusing on specific peripherals.
 
Thanks i'll try to patch this.
I think I've read somewhere that Android file transfert could cause some problems with brcmPatchRam... Is it true or am I wrong?
Hordnis is a driver to support Android internet sharing, could that be linked to the kext failing?
Anyway it might be one of the others problems you noticed so I'll delete this kext and patch what you suggested.


I read somewhere that clover had sometimes problems with smbios beeing truncated on some motherboards... In my config.plist the smbios is longer.
 
Thanks i'll try to patch this.
I think I've read somewhere that Android file transfert could cause some problems with brcmPatchRam... Is it true or am I wrong?

It is true. Discussed in detail in the FAQ. But I don't see AFT in your ioreg.

Hordnis is a driver to support Android internet sharing, could that be linked to the kext failing?

No experience with it (I have an iPhone).

I read somewhere that clover had sometimes problems with smbios beeing truncated on some motherboards... In my config.plist the smbios is longer.

Use a shorter SMBIOS.
 
Thanks for the tip about smbios I didn't even think about it ... Will report results soon
 
Status
Not open for further replies.
Back
Top