Ravenstein Posted December 14, 2019 Share Posted December 14, 2019 (edited) @Mieze, using the 3 kext with bcmPatchRam3 for DW1830, Airdrop is not stable and IOREG shows under XHC confusing BT module after wake-up from sleep: DW1830 should be BCM20703 BT 4.1(fresh boot), but wake-up turns to be BCM2045A0! Where to debug pls? also System Report under USB is BCM2045A0, but under Bluetooth is BCM20703: DW1830 was working well under HS 10.13.6, so that USB port injection etc. should be correct. Edited February 3, 2020 by Ravenstein Link to comment Share on other sites More sharing options...
thefiredragon Posted December 20, 2019 Share Posted December 20, 2019 On 12/13/2019 at 4:55 PM, junaed.rx said: Try Kexts from the below link. They are modified for DW 1820A. Works great on my system. https://osxlatitude.com/forums/topic/11540-dw1820a-the-general-troubleshooting-thread/?do=findComment&comment=92833 this is working also after sleep yeah Link to comment Share on other sites More sharing options...
cable0 Posted December 29, 2019 Share Posted December 29, 2019 I was able to get sound working on the BT after putting the kext's into C / K / O and rebooting.. Checked the firmware is loading now as it was not before.. Hackintosh Dell 7548 Dell DW1560 Vendor : 0x0A5C Device : 0x216F Thank you for the hard work on this project, I now can dual boot Mojave and Catalina! Apple Bluetooth Software Version: 7.0.2f4 Hardware, Features, and Settings: Name: Kevin’s MacBook Pro Address: 18-4F-32-F3-EC-82 Bluetooth Low Energy Supported: Yes Handoff Supported: Yes Instant Hot Spot Supported: Yes Manufacturer: Broadcom Transport: USB Chipset: 20702A3 Firmware Version: v14 c5668 Bluetooth Power: On Discoverable: Off Connectable: Yes Auto Seek Pointing: On Remote wake: On Vendor ID: 0x0A5C Product ID: 0x216F Bluetooth Core Spec: 4.0 (0x6) HCI Revision: 0x1624 LMP Version: 4.0 (0x6) LMP Subversion: 0x220E Device Type (Major): Computer Device Type (Complete): Mac Portable Composite Class Of Device: 0x38010C Device Class (Major): 0x01 Device Class (Minor): 0x03 Service Class: 0x1C0 Auto Seek Keyboard: On Link to comment Share on other sites More sharing options...
acdurr Posted January 3, 2020 Share Posted January 3, 2020 Ok, so I followed the guide on the GitHub and have installed: BrcmPatchRAM3.kext BcrmFirmwareRepo.kext BcrmBluetoothInjector.kept to /L/E, however, I can only get bluetooth to work after I unplug the Asus BT-400 adapter and plug it back in before it detects my magic keyboard and mouse on the login screen. Is there any fix for this? Ok, so I followed the guide on the GitHub and have installed: BrcmPatchRAM3.kext BcrmFirmwareRepo.kext BcrmBluetoothInjector.kept to /L/E, however, I can only get bluetooth to work after I unplug the Asus BT-400 adapter and plug it back in before it detects my magic keyboard and mouse on the login screen. Is there any fix for this? Link to comment Share on other sites More sharing options...
holyfield Posted January 6, 2020 Share Posted January 6, 2020 (edited) On 6/15/2019 at 9:00 AM, headkaze said: I'm just going to run through some of the changes I made to RehabMan's BrcmPatchRAM project for it to function in macOS Catalina. I don't really have time to go any further with it but hopefully my research and testing can help get an official working version out. Could someone explain when this patch is needed at all? I'm using 2 different Bluetooth devices on different comps: First comp: Apple Bluetooth Software Version: 7.0.2f4 Hardware, Features and Settings: Name: *** Address: 88-63-DF-8A-19-A7 Bluetooth Low Energy Supported: Yes Handoff Supported: Yes Instant Hot Spot Supported: Yes Manufacturer: Broadcom Transport: USB Chipset: 20702B0 Firmware Version: v150 c9317 Bluetooth Power: On Discoverable: Off Connectable: Yes Auto Seek Pointing: Off Remote wake: On Vendor ID: 0x05AC Product ID: 0x828D Bluetooth Core Spec: 4.0 (0x6) HCI Revision: 0x2465 LMP Version: 4.0 (0x6) LMP Subversion: 0x4196 Device Type (Major): Computer Device Type (Complete): Mac Desktop Composite Class Of Device: 0x380104 Device Class (Major): 0x01 Device Class (Minor): 0x01 Service Class: 0x1C0 Auto Seek Keyboard: Off Second comp: And in second comp without: BrcmPatchRAM Apple Bluetooth Software Version: 7.0.2f4 Hardware, Features and Settings: Name: *** Address: 5C-F3-70-91-6F-B3 Bluetooth Low Energy Supported: Yes Handoff Supported: No Instant Hot Spot Supported: No Manufacturer: Broadcom Transport: USB Chipset: 20702A3 Firmware Version: v14 c4096 Bluetooth Power: On Discoverable: Off Connectable: Yes Auto Seek Pointing: Off Remote wake: On Vendor ID: 0x0B05 Product ID: 0x17CB Bluetooth Core Spec: 4.0 (0x6) HCI Revision: 0x1000 LMP Version: 4.0 (0x6) LMP Subversion: 0x220E Device Type (Major): Computer Device Type (Complete): Mac Desktop Composite Class Of Device: 0x380104 Device Class (Major): 0x01 Device Class (Minor): 0x01 Service Class: 0x1C0 Auto Seek Keyboard: Off After installing kexts on my second comp, I have this output for second comp with BrcmPatchRAM: Apple Bluetooth Software Version: 7.0.2f4 Hardware, Features and Settings: Name: *** Address: 5C-F3-70-91-6F-B3 Bluetooth Low Energy Supported: Yes Handoff Supported: No Instant Hot Spot Supported: No Manufacturer: Broadcom Transport: USB Chipset: 20702A3 Firmware Version: v14 c5563 Bluetooth Power: On Discoverable: Off Connectable: Yes Auto Seek Pointing: Off Remote wake: On Vendor ID: 0x0B05 Product ID: 0x17CB Bluetooth Core Spec: 4.0 (0x6) HCI Revision: 0x15BB LMP Version: 4.0 (0x6) LMP Subversion: 0x220E Device Type (Major): Computer Device Type (Complete): Mac Desktop Composite Class Of Device: 0x380104 Device Class (Major): 0x01 Device Class (Minor): 0x01 Service Class: 0x1C0 Auto Seek Keyboard: Off Edited January 6, 2020 by holyfield Link to comment Share on other sites More sharing options...
Aluhacker Posted January 9, 2020 Share Posted January 9, 2020 Hello, First of all thanks for the great tutorial. Bluetooth is now working for me. I had worked with USBinjectall.kext before and the BcrmPatch3.kext did not work. After I created my own USBport.kext, Bluetooth worked. I have USBPorts.kext in L/E. The BrcmBluetoothInjector.kext, BrcmFirmwareData.kext and BcrmPatchRAM3.kext is in clover/kexts/other . My problem. Bluetooth is running, but my wired mouse hangs every 10-20 seconds. Does anyone know any advice? I have attached everything else as a screenshot. My guess is that my USBPort.kext is not correct. My chipset is a Z170 (Skylake 6600K and the mainboard ASUS z170i Gaming Pro). I have attached the Info.plist from USBPort.kext and my config.plist. Thanks for the help. config.plist Info.plist Link to comment Share on other sites More sharing options...
galileo13 Posted January 15, 2020 Share Posted January 15, 2020 On 11/14/2019 at 3:37 AM, k0nrad said: Fixed my problem by using the "old" RehabMan method to create a custom SSDT for USBInjectAll.kext instead of the USBPorts.kext created by Hackintool. As a benefit several other problems and lags also disappeared. Nice! :-) Can confirm that this works. Had same problem, BT didn't work after boot, only on wake. After following linked tutorial for custom SSDT problem was fixed. Needed just to reinstall kexts (with Hackintool), reboot, sleep, wake (for firmware upload) and then all was working fine on every following boot. 1 Link to comment Share on other sites More sharing options...
feli_solis Posted January 21, 2020 Share Posted January 21, 2020 (edited) Currently unable to use Bluetooth with: ASUS 4352/20702A1 combo card macOS 10.15.2 BrcmPatchRAM 2.5.1 (BrcmPatchRAM3, BrcmFirmwareRepo & BrcmBluetoothInjector placed in /Library/Extensions) log show --last boot | grep -i brcm\[fp\]: 2020-01-20 21:11:23.055475-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: init 2020-01-20 21:11:23.055485-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: probe 2020-01-20 21:11:23.055487-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.1 starting on OS X Darwin 19.2. 2020-01-20 21:11:23.055494-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake. 2020-01-20 21:11:23.087029-0600 0x4e4 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware store start 2020-01-20 21:11:23.087219-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: getFirmware 2020-01-20 21:11:23.087221-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: loadFirmware 2020-01-20 21:11:23.087241-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000 2020-01-20 21:11:28.573902-0600 0x277 Error 0x0 63 0 kextd: (IOKit) [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x6000008c8ba0 [0x7fff8a9bd090]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "as.acidanthera.BrcmFirmwareStore" } 2020-01-20 21:11:28.574779-0600 0x277 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2020-01-20 21:11:28.574820-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000 2020-01-20 21:11:28.671642-0600 0x277 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2020-01-20 21:11:28.671684-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000 2020-01-20 21:11:28.714449-0600 0x277 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: 29711 bytes of data. 2020-01-20 21:11:28.714486-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1469_v5565.zhx" from resources. 2020-01-20 21:11:28.714848-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29711 bytes --> 70105 bytes). 2020-01-20 21:11:28.715170-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2020-01-20 21:11:28.715183-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: start 2020-01-20 21:11:28.715248-0600 0x113 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0 2020-01-20 21:11:28.748959-0600 0x58c Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1 2020-01-20 21:11:28.850061-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! 2020-01-20 21:11:28.850076-0600 0x4e5 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.134 seconds. Same card used to work fine with RehabMan's BrcmPatchRAM on macOS 10.14.x Any help is much appreciated. * SOLVED. Did the folowing: Removed previously installed kexts from /Library/Extensions and instead copied BrcmPatchRAM3, BrcmFirmwareData & BrcmBluetoothInjector to EFI/Clover/kexts/Other. Updated Clover Generated SSDT-EC.aml with SSDTTime and copied it to EFI/Clover/ACPI/Patched * EDIT: Updated to 10.5.3. Still working Fine! Edited February 6, 2020 by feli_solis Link to comment Share on other sites More sharing options...
gbzygil Posted January 25, 2020 Share Posted January 25, 2020 Anybody has suggestions if the firmware upgrade is successful from the logs but doesnt show up in systemInfo ? (kernel) BrcmPatchRAM: Retrieved cached firmware for "BCM20702A1_001.002.014.1502.1764_v5860". (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: DOWNLOAD MINIDRIVER complete (status: 0x00, length: 4 bytes). (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: State "Firmware version" --> "Mini-driver complete". (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: END OF RECORD complete (status: 0x00, length: 4 bytes). (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: State "Instruction write" --> "Firmware written". (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: RESET complete (status: 0x00, length: 4 bytes). (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: State "Firmware written" --> "Reset complete". (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: Device reset. (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: Device status 0x00000003. (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: State "Reset complete" --> "Update complete". (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21e8]: Firmware upgrade completed successfully. (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.885 seconds. (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0 (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1 The below 3 kexts are installed in C\K\O : BrcmBluetoothInjector.kext BrcmFirmwareData.kext BrcmPatchRAM3.kext Attached some visuals to give a better idea. Any suggestions are much appreciated.... Link to comment Share on other sites More sharing options...
Bassguitarist Posted January 26, 2020 Share Posted January 26, 2020 Hello! Try to install the brcmpatchram3 kext into C/K/10.15 folder. The other 2 kexts into Library/Extensions. You can check the firmware loading With Hackintool info/Misc Link to comment Share on other sites More sharing options...
anibalin Posted January 27, 2020 Share Posted January 27, 2020 On 11/24/2019 at 8:42 PM, sash11 said: Finally got Bluetooth working on my Dell 1550 card on latest Catalina 10.15.1 build. Put these three kext in Other folder: BrcmBluetoothInjector.kext BrcmFirmwareData.kext BrcmPatchRAM3.kext Worked great on bcm4352 Link to comment Share on other sites More sharing options...
deeveedee Posted January 30, 2020 Share Posted January 30, 2020 (edited) I've installed version 2.5.1 kexts BrcmFirmwareRepo.kext, BrcmBluetoothInjector.kext and BrcmPatchRAM3.kext in /L/E on my Dell Latitude E6410 with Broadcom BCM 94352HMB running Catalina. All was good with 10.15.2, but not so after I upgraded to 10.15.3. After upgrading to 10.15.3, I'm experiencing slow boot and delayed Wi-Fi acquisition (the same behavior I observed before I replaced BrcmPatchRAM2.kext with BrcmPatchRAM3.kext/BrcmBluetoothInjector.kext after upgrading from Mojave to Catalina). I'd be happy to post debug files and logs, but first want to confirm that others are seeing this. Is anyone seeing these issues after upgrading from 10.15.2 to 10.15.3? EDIT: After the system boots and Wi-Fi is acquired, all works perfectly. EDIT 2: It is interesting to note that there are bluetooth driver changes from 10.15.2 to 10.15.3: https://eclecticlight.co/2020/01/29/what-changed-in-the-catalina-10-15-3-update/ EDIT 3: Wi-Fi and bluetooth work perfectly after sleep / wake, with both being immediately available after wake. This issue only occurs at Catalina 10.15.3 boot. Edited January 30, 2020 by tonyx86 Link to comment Share on other sites More sharing options...
veb61 Posted February 1, 2020 Share Posted February 1, 2020 For those who are not able to get it working, if you have an internal bluetooth chip like intel, please disable that particular USB port which the intel chip uses. You can do this by figuring its USB port. Mac-> System Report -> USB and find the bluetooth device (or any other USB device) you want to disable. Note the location id. then open a terminal and type ioreg | grep "HS" , see the output and find the matching USB port with the location id, in my case it was HS09. Then disable it by adding a boot flag to Clover. here is the flag in my case : uia_exclude=HS09. Then plug your dongle and let it roll..... 1 Link to comment Share on other sites More sharing options...
deeveedee Posted February 2, 2020 Share Posted February 2, 2020 (edited) On 1/29/2020 at 7:24 PM, tonyx86 said: I've installed version 2.5.1 kexts BrcmFirmwareRepo.kext, BrcmBluetoothInjector.kext and BrcmPatchRAM3.kext in /L/E on my Dell Latitude E6410 with Broadcom BCM 94352HMB running Catalina. All was good with 10.15.2, but not so after I upgraded to 10.15.3. After upgrading to 10.15.3, I'm experiencing slow boot and delayed Wi-Fi acquisition (the same behavior I observed before I replaced BrcmPatchRAM2.kext with BrcmPatchRAM3.kext/BrcmBluetoothInjector.kext after upgrading from Mojave to Catalina). I'd be happy to post debug files and logs, but first want to confirm that others are seeing this. Is anyone seeing these issues after upgrading from 10.15.2 to 10.15.3? EDIT: After the system boots and Wi-Fi is acquired, all works perfectly. EDIT 2: It is interesting to note that there are bluetooth driver changes from 10.15.2 to 10.15.3: https://eclecticlight.co/2020/01/29/what-changed-in-the-catalina-10-15-3-update/ EDIT 3: Wi-Fi and bluetooth work perfectly after sleep / wake, with both being immediately available after wake. This issue only occurs at Catalina 10.15.3 boot. I have determined that the delayed Wi-Fi problem is related to sound. This sounds as crazy to me as it sounds to you (no pun intended ). If you're installing Brcm Wi-Fi on a Latitude E6410 (possibly other systems), use VoodooHDA pkg installer (I selected the classic install method) and NOT AppleALC. I have installed VoodooHDA version 2.9.2 v14 and it is working well for me. I discovered this sound-related issue when I switched back to Catalina 10.15.2 and still had the delayed Wi-Fi problem. Details: When I reverted to 10.15.2 after having the "delayed Wi-Fi" problem in 10.15.3, I had the same problem. I did a clean install of 10.15.2 and had not yet installed sound. I tried AppleALC and while sound worked, Wi-Fi acquisition was still delayed. I removed AppleALC and installed VoodooHDA and the Wi-Fi problem is resolved. While trying to figure out the Wi-Fi problem, I noticed that Wi-Fi would connect immediately after there was an AppleHDA event that I observed in IORegistryExplorer. I suspect that the Wi-Fi problem is "fixed" when VoodooHDA installs AppleHDADisabler. Edited February 3, 2020 by tonyx86 Link to comment Share on other sites More sharing options...
headkaze Posted February 3, 2020 Author Share Posted February 3, 2020 There are some useful tips and info on DalianSky's blog post here (it's in Chinese so you may need to translate the page into English). 1 Link to comment Share on other sites More sharing options...
deeveedee Posted February 3, 2020 Share Posted February 3, 2020 (edited) If I shut-down Catalina 10.15.3 with Bluetooth off, I am not able to turn Bluetooth on when I boot back into 10.15.3. This is not a problem with Mojave 10.14.6. If I sleep 10.15.3 and wake, Bluetooth functionality is restored. My Bluetooth device is a combo Wi-Fi / Bluetooth Broadcom BCM 94352HMB (Bluetooth: 0a5c:21fb, Wi-Fi: pci14e4,43b1). Does anyone have any suggestions? Details are below and attached. Thank you! I am currently running Catalina 10.15.3 on a Dell Latitude E6410 with Brcm-related kexts listed below. If I turn-off Bluetooth (from menu bar) before shutting down Catalina 10.15.3, I cannot turn-on Bluetooth in Catalina 10.15.3 after next boot. the attached "not-working" log shows that (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! when this problem occurs. This is not a problem in Mojave 10.14.6 (where I'm using BrcmFirmwareRepo.kext 2.2.10 and BrcmRamPatch2.kext 2.2.10 in /L/E). I have found that when I am unable to turn-on Bluetooth in 10.15.3, if I sleep and wake, Bluetooth functionality is restored. My Bluetooth logs (log show --predicate 'processID==0' --last 10m | grep BrcmPatch) for working, not-working and working-after-sleep are attached in the zip file. Also attached are debug files (captured with Black.Dragon74's problem reporting tool) that include my IORegistry dump, EFI and other system logs. Lilu.kext 1.4.1 AirportBrcmFixup.kext 2.0.5 BrcmFirmwareRepo.kext 2.5.1 BrcmBluetoothInjector.kext 2.5.1 BrcmPatchRAM3.kext 2.5.1 Thank you for your help! Thank you also for maintaining these Brcm kexts! Bluetooth-Debug.zip Edited February 4, 2020 by tonyx86 Clarified Brcm kexts used in Mojave 10.14.6 Link to comment Share on other sites More sharing options...
headkaze Posted February 4, 2020 Author Share Posted February 4, 2020 7 hours ago, tonyx86 said: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! I have found that when I am unable to turn-on Bluetooth in 10.15.3, if I sleep and wake, Bluetooth functionality is restored. Maybe try playing around with the boot flags: bpr_probedelay=100 bpr_initialdelay=300 bpr_postresetdelay=300 1 Link to comment Share on other sites More sharing options...
deeveedee Posted February 4, 2020 Share Posted February 4, 2020 1 hour ago, headkaze said: Maybe try playing around with the boot flags: bpr_probedelay=100 bpr_initialdelay=300 bpr_postresetdelay=300 Thanks for the quick reply, @headkaze! I reviewed the README to try to understand the delays and unsuccessfully experimented with the following delays: bpr_probedelay=100 bpr_initialdelay=300 bpr_postresetdelay=300 bpr_probedelay=200 bpr_initialdelay=400 bpr_postresetdelay=400 bpr_probedelay=999 bpr_initialdelay=999 bpr_postresetdelay=999 In all three cases, the log still showed (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! following boot and I could not turn on bluetooth. Sleep / wake still recovered bluetooth in each case. I'll try to learn more about the delays to see if I can figure out new values to try. If you have any other suggestions (delays or otherwise), please let me know. Thank you! Link to comment Share on other sites More sharing options...
FanlessPC Posted February 5, 2020 Share Posted February 5, 2020 Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing. I got the above error using BCM43142A0 on NUC DC3217BY with Catalina 15.2. Could anyone help? I put 3 kext below BRCMpatchRAM3.kext BRCMFirmwareData.kext BRCMBluetoothInjector.kext In EFI\CLOVER\kexts\Other systemInformation BCM43142A0: Product ID: 0x216c Vendor ID: 0x0a5c (Broadcom Corp.) Version: 1.12 Serial Number: 543530E01838 Manufacturer: Broadcom Corp Location ID: 0x1d140000 Bluetooth: No information found admin@Lightning-Eth ~ % log show --last boot | grep -i brcm 2020-02-04 22:02:04.067098-0500 0x179 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Version 2.5.1 starting on OS X Darwin 19.2. 2020-02-04 22:02:10.664750-0500 0x220 Error 0x0 62 0 kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing. 2020-02-04 22:02:11.589431-0500 0x220 Error 0x0 62 0 kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing. 2020-02-04 22:02:11.742724-0500 0x220 Error 0x0 62 0 kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing. 2020-02-04 22:02:11.782182-0500 0x220 Error 0x0 62 0 kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing. 2020-02-04 22:02:11.811299-0500 0x179 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM43142A0_001.001.011.0311.0328_v4424". 2020-02-04 22:02:11.827331-0500 0x179 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Decompressed firmware (23739 bytes --> 58772 bytes). 2020-02-04 22:02:11.842117-0500 0x179 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2020-02-04 22:02:11.956002-0500 0x179 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:216c]: USB [543530E01838 v274] "BCM43142A0" by "Broadcom Corp" Link to comment Share on other sites More sharing options...
deeveedee Posted February 5, 2020 Share Posted February 5, 2020 3 hours ago, FanlessPC said: Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing. Have you tried installing BrcmFirmwareRepo.kext (not BrcmFirmwareData.kext), BrcmBluetoothInjector.kext and BrcmPatchRAM3.kext in /Library/Extensions? BrcmPatch doesn't load for me when I install in /E/C/k/O (still trying to figure out why because I'd like to try it). I'm running CLOVER r5103 (Legacy). Make sure kexts are properly installed. Link to comment Share on other sites More sharing options...
deeveedee Posted February 5, 2020 Share Posted February 5, 2020 (edited) EDIT: I upgraded to Lilu v1.4.2 from v1.4.1 and confirmed that Bluetooth behavior remains unchanged (Cannot turn-on Bluetooth if I shutdown previous session with Bluetooth off. Sleep/Wake trick still works.). EDIT: After I documented a Bluetooth pairing procedure below (from my MacBookPro to my iPhone), I am now also able to initiate Bluetooth pairing from my iPhone to my MBP. Unlike pairing initiated from the MBP, pairing initiated from the iPhone does not present a pairing code, only requiring a simple "Connect" button press on the MBP to accept pairing. I can now "Forget" the pairing on both the iPhone and the MBP and initiate the pairing from either the iPhone or from the MBP (pairing works in both directions). I'm not sure why the iPhone to MBP pairing did not work for me before. The Sleep/Wake trick described below is still required for Catalina 10.15.3. With Brcm kexts version 2.5.1 in /L/E on my Dell Latitude E6410 running Catalina 10.15.3, Bluetooth behavior remains the same as I reported earlier: I still can't turn on Bluetooth if I shutdown the previous Catalina session with Bluetooth off. I can always recover Bluetooth by Sleeping and then Waking (annoying, but it works reliably). With Mojave 10.14.6, I can reliably turn Bluetooth on and off without needing the "Sleep/Wake trick." I'm sharing my Bluetooth connection procedure between my Mac and iPhone (below) in case this helps others: Initiate Bluetooth pairing from Mac (10.15.3) to iPhone (12.4.1) Confirm pairing code and accept the pairing request on the iPhone. At this point, my iPhone displays the Mac connection as "not Connected" in the iPhone Bluetooth status. Tap the new "MY DEVICES" connection (for the Mac) on the iPhone. Mac connection changes from "not Connected" to "Connected" on the iPhone and Bluetooth icon on Mac shows connected. Connection now works as expected. If disconnected, subsequent Bluetooth connections can be initiated from the iPhone (once the initial pairing has been completed) The kext differences between my Mojave 10.14.6 and Catalina 10.15.3 Bluetooth installation are as follows (my laptop triple boots High Sierra, Mojave and Catalina with the same EFI. Kexts unique to each OS are in /L/E): Mojave 10.14.6 and High Sierra 10.13.6 (the following kexts in /L/E) Lilu.kext v1.3.8 BrcmRepo.kext v2.2.10 BrcmRAMPatch2.kext v2.2.10 Catalina 10.15.3 (the following kexts in /L/E) Lilu.kext v1.4.2 (upgraded from v1.4.1 but made no difference) BrcmRepo.kext v2.5.1 BrcmRAMPatch3.kext v2.5.1 BrcmFirmwareInjector.kext v2.5.1 Edited March 5, 2020 by tonyx86 Updated to indicate that I'm now using Lilu.kext v1.4.2 1 Link to comment Share on other sites More sharing options...
headkaze Posted February 6, 2020 Author Share Posted February 6, 2020 (edited) 17 hours ago, tonyx86 said: I still can't turn on Bluetooth if I shutdown the previous Catalina session with Bluetooth off. @Mieze do you have any ideas on what might be causing this issue? ... and the issue opening the device? (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! Edited February 6, 2020 by headkaze Link to comment Share on other sites More sharing options...
Mieze Posted February 7, 2020 Share Posted February 7, 2020 @headkaze I'm sorry but I don't have time for hacking at the moment because I had an exam in university this afternoon and will start preparations for the next one tomorrow. That's the reason why I have to take a timeout from hackintoshing until my last exam for the semester (March, the 9th) will be over. Mieze 5 Link to comment Share on other sites More sharing options...
feli_solis Posted February 8, 2020 Share Posted February 8, 2020 @tonyx86 I'm wondering if the issue I used to have and your current one are related: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! Have you dealt with your 'EC' device? The following article pointed me in the right direction to solve my issue. Since I'm on desktop I went the Fake EC route. https://medium.com/@ayushere/common-problems-and-workarounds-in-hackintosh-85d76ad89d24 1 Link to comment Share on other sites More sharing options...
deeveedee Posted February 8, 2020 Share Posted February 8, 2020 1 hour ago, feli_solis said: @tonyx86 I'm wondering if the issue I used to have and your current one are related: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! Have you dealt with your 'EC' device? The following article pointed me in the right direction to solve my issue. Since I'm on desktop I went the Fake EC route. https://medium.com/@ayushere/common-problems-and-workarounds-in-hackintosh-85d76ad89d24 @feli_solis thank you very much for your suggestion! I have already renamed the ECDV device to EC in my DSDT and AppleACPIEC is loading with IONameMatch PNP0C09. Thank you for checking! Link to comment Share on other sites More sharing options...
Recommended Posts