Probably invalid kexts. I don't think it's a BlueToolFixup issue. Probably invalid IntelBluetoothFirmware kexts. Use kexts from attachment. Set kexts in order:
1) IntelBluetoothFirmware.kext
2) IntelBTPatcher.kext
3) BlueToolFixup.kext
and it should work.
Yes, you need to add your card in config.plist DeviceProperties (I use OpenCore Configurator) and there change its IoName from pci14e4,4331 to pci14e4,432B. Only after that run OCLP Patcher. After this change OCLP should recognize it as "legacy".
Yes, exactly. You can run this card in both "modern" mode (without any device_id modifications) and "legacy" mode, by modifying the device_id to 432B. I have BCM9431CSAx with id 4331:
Only IO80211ElCap and corecaptureElCap are needed. I didn't check Bluetooth because I don't need it with this...
I found a solution! See the pci_data.py file in OCLP.:
OCLP developers removed 4331 from legacy cards. So just change the card's device-id to 0x432B. Then it will be recognized by OCLP as "legacy". And voila wifi works on IO80211ElCap and corecaptureElCap.
Maybe I expressed myself badly. It's not a card on the motherboard, but a card on the Pcie. I'm using Intel XXV710-DA2.
I confirm that BCM4331 works without a problem when installed according to the procedure for modern cards. However, it doesn't work when we want to run it as legacy cards (or...
As I understand it, I should do everything according to the procedure for modern cards? I specifically gave up Fenvi, which I also have, and bought BCM4331, to be able to use the procedure for "legacy cards", i.e. not to block IOSkywalkFamily, because I have an Intell XXV710 25G card on board...
As I mentioned earlier, I tried adding airportbrcmfixup to my config. After adding it, the system loads very long and BCM4331 is not visible in the system at all (corecaptureElCap and IO80211ElCap are not loaded) - see with_airportbrcmfixup.zip files. Without this kext BCM4331 is detectable and...
Are you sure this kext should be there? It's not in the guide for legacy cards. After adding it, the system loads very long and 4331 is not visible in the system at all (see with_airportbrcmfixup.zip). Without this kext 4331 is detectable and FV is loaded, but does not work...
Therefore, since I use BT from my motherboard. Broadcom 4331 I want to use only for Wi-Fi.
In the guide it is only indicated for "Non-Apple AirPort and Non-Fenvi Cards". In my case it is BCM4331. According to the guide it is a "legacy card". That is why I do not have this kext. Should I have it?
Any news on Broadcom 4331 launch on Sequoia/Sonoma? I have the same problem as @zhenya8987. FV of 4331 is loaded but Wifi is unavailable. This is not a Sequoia problem. Same problem occurs on Sonoma.
I also have AX210 and it works without problems in Sonoma with both the Mellanox CX4121A-ACAT ConnectX-4 and Intel XXV710-DA2 cards. But I also wanted to have all the features available like Airdrop, etc. Hence, I wanted to have a working Fenvi T919 at the same time. I tried Ventura - there...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.