[BrcmPatchRam] macOS Monterey BT issues

[dreamwhite]

Hi there,
first of all thank you so much for 2021.06 release planning. Everything works flawlessly on my side.
I'm opening this issue to keep track of the changes to BrcmPatchRAM (and possibly other kexts like Lilu) behaviour on macOS 12 Monterey.

Today I installed macOS Monterey 12.0 (21A5248p) on my laptop and noticed that the installer hangs if BrcmPatchRAM kexts are injected. Disabling them from config.plist makes the boot proceed.

I have a DW1830 (BCM943602BAED 14e4:43ba) and I'm currently using the following kexts for the bluetooth compatibility on macOS Big Sur 11.4 (20F71):

• BrcmBluetoothInjector (required from macOS 10.15 Catalina and newer)
• BrcmPatchRAM3 (paired with the injector)
• BrcmFirmwareData (as I'm injecting the kexts via OC)

As I wrote above, if those kexts are injected and I try to boot macOS 12 Beta, the boot process hangs.

Is there any chance that my card (as well as the other cards which require BrcmPatchRAM for BT compatibility) will work on macOS 12?
I'll attach as soon as possible OpenCore 0.7.0 DEBUG logs both with and without BrcmPatchRAM kexts injected. Please tell me if you require any other logs, and eventually how to obtain them.
Regards
dreamwhite

[dreamwhite]

As wrote above, here you are the logs obtained with the following boot-args: -v debug=0x100 keepsyms=1 -lilubetaall -liludbg liludump=120:

opencore-2021-06-07-222721.txt
Lilu_1.5.3_21.0.txt
Let me know your thoughts on that, and eventually how can I help you.
dreamwhite

[Andrey1970AppleLife]

It not plug-in Lilu.

[Pavo-IM]

Seems to be a firmware loading issue.

[zhen-zen]

BrcmPatchRAM works as intended and fw is loaded. You can verify it by rebooting from Windows with the injector only. 3rd-party BT cards seem to have issues for lack of some ingredients from customized fw. I wonder if Intel BT works in Monterey.

[Pavo-IM]

BrcmPatchRAM works as intended and fw is loaded. You can verify it by rebooting from Windows with the injector only. 3rd-party BT cards seem to have issues for lack of some ingredients from customized fw. I wonder if Intel BT works in Monterey.

It works as intended in BigSur and below, but something with the loading the firmware has changed in Monterey. I can get BrcmPatchRAM3 loaded but the BrcmFirmwareData and BrcmBluetoothInjector kext do not work in Monterey.

[zhen-zen]

I can get BrcmPatchRAM3 loaded but the BrcmFirmwareData and BrcmBluetoothInjector kext do not work in Monterey.

BrcmBluetoothInjector is a binaryless kext that matches additional non-native hardware IDs and won't show up in ioreg or kextstat.

For firmware loading, the device can hold loaded firmware after a warm reboot. This trick is widely used before BrcmPatchRAM is developed.

Compared to Big Sur, IOBluetoothFamily adds more methods on ACPI operations for UART module, i.e. torvalds/linux@4c33162 . The log indicates that the driver tries to access those methods while native Bluetooth cards don't have such process. I guess there is a whitelist for native USB Bluetooth IDs and all other devices will took the UART approach and then fail.

[dreamwhite]

I'll try to reply to everyone:

@Andrey1970AppleLife: It not plug-in Lilu.

Oh, my bad. I thought that Lilu could help somehow 😅

@Pavo-IM: Seems to be a firmware loading issue.
@zhen-zen : BrcmPatchRAM works as intended and fw is loaded. You can verify it by rebooting from Windows with the injector only. 3rd-party BT cards seem to have issues for lack of some ingredients from customized fw. I wonder if Intel BT works in Monterey.
I don't have Windows on my computer, but I have a working Arch Linux installation and bluetooth works fine without installing any kind of external drivers (fyi I'm using brcmfmac kernel module). Is this still valid or should I install Windows somewhere and eventually report back? Eventually what should I check on Windows?

Anyways thank you so much for replying and have a great day

[zhen-zen]

I don't have Windows on my computer, but I have a working Arch Linux installation and bluetooth works fine without installing any kind of external drivers (fyi I'm using brcmfmac kernel module). Is this still valid or should I install Windows somewhere and eventually report back? Eventually what should I check on Windows?

Literally any OS with working Bluetooth works in this way, including Linux and even macOS (set maxKernel to 20.99.99 for BrcmPatchRAM, don't apply to the injector).

[dreamwhite]

Literally any OS with working Bluetooth works in this way, including Linux and even macOS (set maxKernel to 20.99.99 for BrcmPatchRAM, don't apply to the injector).

Alright, so can you gently confirm me the following recap?

• set maxKernel to 20.99.99 for BrcmPatchRAM3 and BrcmFirmwareData
• leave BrcmBluetoothInjector untouched

If so, what kind of logs do you need? Should I attach Lilu debug log despite it still doesn't show anything relevant about BrcmPatchRAM?

[Pavo-IM]

Here is a dump from the log using log show --last boot | grep -I brcm since log show --last boot | grep -i brcm[fp] doesn't work.
brcm_dump.txt

This is from using the latest debug version btw.

[ameenjuz]

I have same issue BrcmPatchRAM3 and BrcmFirmwareData
BrcmBluetoothInjector on Moneterey 12
without these kexts booting fine macOS 12
I have Dell 1560 BRCM4352z

[Pavo-IM]

Some more info.... In Bigsur and below the BroadcomBluetoothHostControllerUSBTransport.kext which is what the injector kext is injecting into, is located inside IOBluetoothFamily.kext/Contents/Plugins/ in Monterey BroadcomBluetoothHostControllerUSBTransport.kext is not located there anymore. Its located in System/Library/Extensions.

[Pavo-IM]

BroadcomBluetoothHostControllerUSBTransport IOProviderClass has changed from IOUSBHostDevice to IOResources and doesn't have the list of devices in the Info.plist like it previously did. This is why the BrcmBluetoothInjector.kext isn't working.

[ameenjuz]

@Pavo-IM what is salution to fix bluetooth for monterey 12