Contribute
Register

<< Solved >> BCM94352Z not working with BlueToolFixup

Joined
Jan 3, 2020
Messages
10
Motherboard
Fujitsu Lifebook E557 - Clover
CPU
i5-7300U
Graphics
HD 620
Mac
  1. MacBook Pro
I've tried to load USB Map (that is correct) first and to set the correct loading order of the BrcmPatchRAM kexts but bluetooth still not works with my BCM94352Z card on Monterey (it was perfect with BigSur, WIFI is OK).
For the rest is a Golden Build.
Any ideas?

Gigabyte B360N WIFI (card replaced) - I7-8700 - 970 EVO PLUS - OpenCore 0.7.6 - latest kexts

Found some errors in load with debug version ok kexts:
Code:
2021-12-27 14:41:11.147509+0100 0x71       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.157473+0100 0x71       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.503538+0100 0xcd       Default     0x0                  0      0    kernel: (BrcmPatchRAM3)  = <decode: missing data>
2021-12-27 14:41:11.503540+0100 0xcd       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) copyPipe failed
2021-12-27 14:41:11.503607+0100 0xcd       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) gnized
2021-12-27 14:41:11.503609+0100 0xcd       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) e unreachable.
2021-12-27 14:41:11.503612+0100 0xcd       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) ialize
2021-12-27 14:41:11.503614+0100 0xcd       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) lete
2021-12-27 14:41:11.503625+0100 0xcd       Default     0x0                  0      0    kernel: (BrcmPatchRAM3)  enough pipes in interface
2021-12-27 14:41:11.509806+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.510141+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.510143+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.510151+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.510153+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.512648+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.512657+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.512669+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.512670+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.512671+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.512672+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:11.512813+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) eresetdelay
2021-12-27 14:41:11.512927+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) AM.kext instead.
2021-12-27 14:41:11.512929+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) ype is incorrect (not IOUSBDevice or IOUSBHostDevice)
2021-12-27 14:41:11.513136+0100 0x308      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) mPatchRAM: stop
2021-12-27 14:41:12.265959+0100 0x204      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.290093+0100 0x320      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.290095+0100 0x320      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.290111+0100 0x320      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.290145+0100 0x320      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.290162+0100 0x320      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.290164+0100 0x320      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.290166+0100 0x320      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.466653+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: init
2021-12-27 14:41:12.466661+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: probe
2021-12-27 14:41:12.466663+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.6.1 starting on OS X Darwin 21.2.
2021-12-27 14:41:12.466667+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Device supports handshake.
2021-12-27 14:41:12.466670+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.466672+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.466685+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.466964+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.467041+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.467301+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:12.467309+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: start
2021-12-27 14:41:12.467331+0100 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2021-12-27 14:41:12.467335+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: USB [C48E8FF6F35A v274] "BCM20702A0" by "Broadcom Corp"
2021-12-27 14:41:12.467338+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: Available composite configurations: 1.
2021-12-27 14:41:12.468604+0100 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: Set device configuration to configuration index 0 successfully.
2021-12-27 14:41:12.468606+0100 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: USBDeviceShim::findFirstInterface
2021-12-27 14:41:12.468608+0100 0x311      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: getValidatedInterface returns <private>
2021-12-27 14:41:12.468610+0100 0x311      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: Interface 0 (class ff, subclass 01, protocol 01) located.
2021-12-27 14:41:12.468618+0100 0x311      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: set configuration and interface opened
2021-12-27 14:41:12.468619+0100 0x311      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 1, type = 3
2021-12-27 14:41:12.468621+0100 0x311      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3
2021-12-27 14:41:12.468622+0100 0x311      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint
2021-12-27 14:41:12.468759+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 0, type = 2
2021-12-27 14:41:12.468762+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3
2021-12-27 14:41:12.468764+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2
2021-12-27 14:41:12.468766+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2
2021-12-27 14:41:12.468768+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint
2021-12-27 14:41:12.468907+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: got pipes
2021-12-27 14:41:12.468910+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: State "Unknown" --> "PreInitialize".
2021-12-27 14:41:12.471936+0100 0x2c9      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: RESET complete (status: 0x00, length: 4 bytes).
2021-12-27 14:41:12.471941+0100 0x311      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: State "PreInitialize" --> "Initialize".
2021-12-27 14:41:12.573941+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes).
2021-12-27 14:41:12.573944+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: Firmware version: v5668.
2021-12-27 14:41:12.573948+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: State "Initialize" --> "Update not needed".
2021-12-27 14:41:12.573950+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:216f]: Firmware upgrade not needed.
2021-12-27 14:41:12.573967+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.106 seconds.
2021-12-27 14:41:14.700043+0100 0x204      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:15.506293+0100 0x204      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:15.985243+0100 0x73       Default     0x0                  0      0    kernel: (BrcmPatchRAM3) <compose failure [UUID]>
2021-12-27 14:41:58.438339+0100 0x36f      Default     0x0                  121    0    kernelmanagerd: Received kext load notification: as.acidanthera.BrcmPatchRAM3
I have the same situation with 12.1 and the last kext. Wifi works bluetooth no.
 
Joined
Feb 27, 2011
Messages
75
Motherboard
Inspiron 15 7000 Series 7559
CPU
i7-6700HQ
Graphics
HD 530
Have you found a solution yet? I just got my iPad mini, I am wondering if I should downgrade to Bigsur now since I want sidecar and better airdrop.
Not yet. I like sidecar and universal clipboard so I may be downgrading back to Big sur myself.
 
Joined
Aug 14, 2016
Messages
24
Motherboard
Gigabyte B360N WIFI ITX
CPU
i7-8700
Graphics
UHD 630, RX5500
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
Classic Mac
  1. iMac
  2. Power Mac
  3. PowerBook
  4. Quadra
Mobile Phone
  1. iOS
I have the same situation with 12.1 and the last kext. Wifi works bluetooth no.

Ok, solved.
It was a kext order issue.
Just put the Lilu.kext at first item in the list (OpenCore section: Kernel -> Add ) and now all works.
 
Joined
Jan 3, 2020
Messages
10
Motherboard
Fujitsu Lifebook E557 - Clover
CPU
i5-7300U
Graphics
HD 620
Mac
  1. MacBook Pro
Ok, solved.
It was a kext order issue.
Just put the Lilu.kext at first item in the list (OpenCore section: Kernel -> Add ) and now all works.
In my case Lilu was the first. I attached my kext list can you give me a feedback?
To be more complete my case it's a little different:
1) the card it's DW1820A BCM94350ZAE
2) bluetooth discovery devices but it's not able to connect or paring them (see attachment 2 and 3)

Do you have some tips or suggestion?
 

Attachments

  • Schermata 2022-01-07 alle 22.41.34.png
    Schermata 2022-01-07 alle 22.41.34.png
    180.8 KB · Views: 251
  • 137914736_Schermata2021-12-31alle10_55_11.png.6e9cde3e27bd908f6007bf0ee8a2b6d9.png
    137914736_Schermata2021-12-31alle10_55_11.png.6e9cde3e27bd908f6007bf0ee8a2b6d9.png
    58.1 KB · Views: 250
  • 200821177_Schermata2021-12-31alle10_56_54.thumb.png.a70b5612755bd9e8f5b75e887e64870b.png
    200821177_Schermata2021-12-31alle10_56_54.thumb.png.a70b5612755bd9e8f5b75e887e64870b.png
    273.5 KB · Views: 256
Joined
Aug 14, 2016
Messages
24
Motherboard
Gigabyte B360N WIFI ITX
CPU
i7-8700
Graphics
UHD 630, RX5500
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
Classic Mac
  1. iMac
  2. Power Mac
  3. PowerBook
  4. Quadra
Mobile Phone
  1. iOS
In my case Lilu was the first. I attached my kext list can you give me a feedback?
To be more complete my case it's a little different:
1) the card it's DW1820A BCM94350ZAE
2) bluetooth discovery devices but it's not able to connect or paring them (see attachment 2 and 3)

Do you have some tips or suggestion?
Does the card worked with previous macOS versions ?
Can you boot Windows to check if the card is working?
 
Joined
Jan 3, 2020
Messages
10
Motherboard
Fujitsu Lifebook E557 - Clover
CPU
i5-7300U
Graphics
HD 620
Mac
  1. MacBook Pro
Does the card worked with previous macOS versions ?
Can you boot Windows to check if the card is working?
Yes it's works with big sur. Now with 12.1 works only wifi.
I have only MacOS installed so i can't test if it works on windows.
 

FLP

Joined
Mar 18, 2011
Messages
129
Motherboard
Gigabyte Z690 Gaming X
CPU
i7-12700K
Graphics
RX 570
Mobile Phone
  1. Android
  2. iOS
In case anyone is interested, there is a low cost bluetooth usb dongle that works with Monterey. It doesn't seem to support continuity and sidecar, but works with air pods and a ps4 dual shock 4 game controller I tried. You do need to add BlueToolFixUp.kext (I am using version 2.6.1). On sale for $7.96.


Update 4/25: They started selling a Bluetooth version 5.0 usb dongle. That one does not work.
 
Last edited:
Joined
Jan 3, 2020
Messages
10
Motherboard
Fujitsu Lifebook E557 - Clover
CPU
i5-7300U
Graphics
HD 620
Mac
  1. MacBook Pro
In case anyone is interested, there is a low cost bluetooth usb dongle that works with Monterey. It doesn't seem to support continuity and sidecar, but works with air pods and a ps4 dual shock 4 game controller I tried. You do need to add BlueToolFixUp.kext (I am using version 2.6.1). On sale for $7.96.

And how you disable the internal bluetooth that not works?
 
Joined
Jan 30, 2011
Messages
456
Motherboard
ASUS ROG RAMPAGE VI EXTREME
CPU
i9-7980XE
Graphics
RX 5700 XT
And how you disable the internal bluetooth that not works?
There might be an option in your BIOS. Otherwise, ACPI patch (similar to techniques used to disable GPU) or physically remove the card.
 
Joined
Apr 28, 2011
Messages
913
Motherboard
Asus Prime Z690M-Plus D4
CPU
i7-12700KF
Graphics
RX 6600
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
And how you disable the internal bluetooth that not works?
Usually internal BT is associated to an USB port. You just need to disable it in your USB patching (see USB mapping, if needed).
Take a look at my IOReg

USB IOReg.png


my internal BT is on HS14. Just disable HS14 from your usb patch and then you're good to go
 
Top