Jump to content

BrcmPatchRAM2 for 10.15 Catalina (Broadcom bluetooth firmware upload)

headkaze

By headkaze,
in LAN and Wireless

 Share
432 posts in this topic

Recommended Posts

Alpha22
Alpha22
Posted
Posted (edited)

@headkaze 

from your app I followed how to set up USB

the usb ports all work

https://imgur.com/CPVcDAk

 

https://imgur.com/UOHdXdK

 

https://imgur.com/CUVJZ62

 

I use USBPorts.kext in L / E

 

Spoiler

 log show --last boot | grep -i brcm

2020-03-21 07:06:34.617801+0100 0xe7       Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::init AirPortFamily_kexts-1580.2 "AirPortFamily_kexts-1580.2" Jan  9 2020 21:50:21

2020-03-21 07:06:34.617826+0100 0xe7       Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 0.617824: AirPort_Brcm43XX:probe:, this[0x9cdddb04a19cb7d3]  score[2048]

2020-03-21 07:06:34.617834+0100 0xe7       Default     0x0                  0      0    kernel: (IO80211Family) AirPort_Brcm4360::init AirPortFamily_kexts-1580.2 "AirPortFamily_kexts-1580.2" Jan  9 2020 21:50:21

2020-03-21 07:06:34.617844+0100 0xe7       Default     0x0                  0      0    kernel: (AirPortBrcm4360) ARPT: 0.617843: AirPort_Brcm43XX:probe:, this[0xabd8b10307e7976d]  score[1110]

2020-03-21 07:06:38.717492+0100 0x4fc      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::init AirPortFamily_kexts-1580.2 "AirPortFamily_kexts-1580.2" Jan  9 2020 21:50:21

2020-03-21 07:06:38.717524+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 5.588109: AirPort_Brcm43XX:probe:, this[0x9cdddb04a2c137d3]  score[2048]

2020-03-21 07:06:38.717539+0100 0x4fc      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_Brcm4360::init AirPortFamily_kexts-1580.2 "AirPortFamily_kexts-1580.2" Jan  9 2020 21:50:21

2020-03-21 07:06:38.717561+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcm4360) ARPT: 5.588146: AirPort_Brcm43XX:probe:, this[0xabd8b1030a96476d]  score[1110]

2020-03-21 07:06:38.820983+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 5.691568: srom rev:11

2020-03-21 07:06:38.927651+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) Setting property subsystem-id to:855c

2020-03-21 07:06:38.927658+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) Setting property subsystem-vendor-id to:106b

2020-03-21 07:06:38.933103+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 5.803689: BRCM tunables:

2020-03-21 07:06:38.933110+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 5.803695:   pullmode[1] txringsize[  256] txsendqsize[0] reapmin[   32] reapcount[  128]

2020-03-21 07:06:38.933189+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) wl0: Broadcom BCM43b1 802.11 Wireless Controller

2020-03-21 07:06:38.934159+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 5.804743: wl0: Broadcom BCM43b1, vendorID[0x14e4] BAR0[0xdfa00004]

2020-03-21 07:06:38.934209+0100 0x4fc      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 5.804795: Set packet allocation type to 1

2020-03-21 07:06:39.056839+0100 0x26d      Error       0x0                  63     0    kextd: (IOKit) [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x60000283cea0 [0x7fff94a04690]> { URL = "file:///Library/Extensions/BrcmPatchRAM3.kext/", ID = "as.acidanthera.BrcmPatchRAM3" }

2020-03-21 07:06:39.129413+0100 0x26d      Error       0x0                  63     0    kextd: (IOKit) [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x60000283cf60 [0x7fff94a04690]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "as.acidanthera.BrcmFirmwareStore" }

2020-03-21 07:06:39.184889+0100 0x5ec      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::getSSIDData(): Get failure: APPLE80211_IOC_SSID: 6

2020-03-21 07:06:39.352691+0100 0x5fe      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: Version 2.5.1 starting on OS X Darwin 19.3.

2020-03-21 07:06:39.582690+0100 0x5fe      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1469_v5565.zhx" from resources.

2020-03-21 07:06:39.583149+0100 0x5fe      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29711 bytes --> 70105 bytes).

2020-03-21 07:06:39.583658+0100 0x5fe      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware.

2020-03-21 07:06:39.685561+0100 0x5fe      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: uploadFirmware could not open the device!

2020-03-21 07:06:39.685565+0100 0x5fe      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: Processing time 0.101 seconds.

2020-03-21 07:06:41.196682+0100 0x576      Default     0x0                  0      0    kernel: (IO80211Family) IO80211VirtualInterface::AirPort_BrcmNIC_P2PInterface::init name <p2p0> role 1

2020-03-21 07:06:41.197113+0100 0x576      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC_P2PInterface::init <p2p> role 1

2020-03-21 07:06:41.197704+0100 0x576      Default     0x0                  0      0    kernel: (IO80211Family) IO80211VirtualInterface::AirPort_BrcmNIC_P2PInterface::init name <awdl0> role 4

2020-03-21 07:06:41.197730+0100 0x576      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC_P2PInterface::awdlAttachToBpf name <awdl0> role 4 successful attach to bpf type 147

2020-03-21 07:06:41.200650+0100 0x576      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC_P2PInterface::init <awdl> role 4

2020-03-21 07:06:41.224483+0100 0x763      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 8.095068: wl0: setAWDL_PEER_TRAFFIC_REGISTRATION: active 0, roam_off: 1, err 0 roam_start_set 0 forced_roam_set 0

2020-03-21 07:06:41.374869+0100 0x788      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 8.245454: AirPort_Brcm43xx::syncPowerState: WWEN[disabled]

2020-03-21 07:08:44.259478+0100 0x1810     Default     0x0                  264    7    corecaptured: (CoreCaptureDaemon) [com.apple.corecaptured:corecapture] CCDataTap::profileRemoved, Owner: com.apple.driver.AirPort.Brcm4360.0, Name: StateSnapshots

2020-03-21 07:08:44.259549+0100 0x1810     Default     0x0                  264    7    corecaptured: (CoreCaptureDaemon) [com.apple.corecaptured:corecapture] CCLogTap::profileRemoved, Owner: com.apple.driver.AirPort.Brcm4360.0, Name: DriverLogs

fabio@iMac-di-Fabio ~ % 

 

Advice

 

USBPorts.kext.zip

iMac di Fabio.zip

Edited by Alpha22
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted

I still prefer to install kexts in /L/E.  I have found that having CLOVER inject BrcmPatchRAM3.kext (with BrcmFirmwareData.kext) while installing all other kexts in /L/E may be a viable option for those like me who experience the "Failed to Open Device" problem with BrcmPatchRAM3.kext and BrcmFirmwareRepo.kext in /L/E and who want their kexts in /L/E.

 

Details here.

Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted
47 minutes ago, tonyx86 said:

I still prefer to install kexts in /L/E.  I have found that having CLOVER inject BrcmPatchRAM3.kext (with BrcmFirmwareData.kext) while installing all other kexts in /L/E may be a viable option for those like me who experience the "Failed to Open Device" problem with BrcmPatchRAM3.kext and BrcmFirmwareRepo.kext in /L/E and who want their kexts in /L/E.

I am of the same mentality, I prefer /L/E/ to be honest, thanks for raising your point here and in the other thread. Indeed, as you wrote, "It appears to me that there is something about BrcmRAMPatch3.kext and BrcmFirmwareRepo.kext installed in /L/E that does not agree with Catalina.  I'm not sure if the problem has something to do with Clover Legacy mode or is something specific to this laptop."

 

I have yet to update to the latest Clover r5106 released a couple of days ago, not sure if it will have any effect on this or we should perhaps wait for the imminent Catalina 10.15.4 coming out very soon, so that the very capable devs of this BT kext, can test it and perhaps fix the /L/E/ behaviour on Catalina, without wasting more time investigating 10.15.3...

Link to comment
Share on other sites
kidinhvao
kidinhvao
Posted
Posted (edited)

Hi everyone, I am using DW1820A on GL552VX. I tried to make Bluetooth work, but It still stuck in lots of problems.

I tried some methods, install acidanthera's PatchRam3 in L\E or in C\K\O, or DalianSky's PatchRam2 modified on his Blog.

 

With acidanthera's PatchRam3, I got: 

Spoiler

L\E: 

log show --last boot | grep -i 'brcmf\|brcmp'                                              ✔
2020-03-18 16:06:05.225549+0700 0x4f1      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.1 starting on OS X Darwin 19.3.
2020-03-18 16:06:05.412584+0700 0x23c      Error       0x0                  64     0    kextd: (IOKit) [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x600003a94f60 [0x7fff917bf690]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "as.acidanthera.BrcmFirmwareStore" }
2020-03-18 16:06:05.438959+0700 0x4f1      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM4350C5_003.006.007.0222.4689_v8785.zhx" from resources.
2020-03-18 16:06:05.439199+0700 0x4f1      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (12582 bytes --> 31740 bytes).
2020-03-18 16:06:05.439401+0700 0x4f1      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware.
2020-03-18 16:06:05.540820+0700 0x4f1      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device!
2020-03-18 16:06:05.540825+0700 0x4f1      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.101 seconds.
2020-03-18 16:06:05.544929+0700 0x5cf      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.1 starting on OS X Darwin 19.3.
2020-03-18 16:06:05.645025+0700 0x5cf      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6412]: USB [F828196A17F0 v274] "BCM2045A0" by "Broadcom Corp"
2020-03-18 16:06:05.995740+0700 0x5cf      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6412]: Firmware upgrade completed successfully.
2020-03-18 16:06:05.995783+0700 0x5cf      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.450 seconds.

C\L\O:
log show --last boot | grep -i 'brcmf\|brcmp'                                              ✔
2020-03-19 00:12:04.572058+0700 0x23f      Error       0x0                  64     0    kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing.
2020-03-19 00:12:04.724941+0700 0x23f      Error       0x0                  64     0    kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing.
2020-03-19 00:12:04.838313+0700 0x23f      Error       0x0                  64     0    kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing.
2020-03-19 00:12:04.866006+0700 0x23f      Error       0x0                  64     0    kextd: (IOKit) [com.apple.kext:kextlog] Unable to determine realpath for /EFI\CLOVER\kexts\Other\BrcmFirmwareData.kext - failing.
2020-03-19 00:12:04.908424+0700 0x195      Default     0x0                  0      0    kernel: (BrcmFirmwareData) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM4350C5_003.006.007.0222.4689_v8785".
2020-03-19 00:12:04.908657+0700 0x195      Default     0x0                  0      0    kernel: (BrcmFirmwareData) BrcmPatchRAM: Decompressed firmware (12582 bytes --> 31740 bytes).
2020-03-19 00:12:04.908872+0700 0x195      Default     0x0                  0      0    kernel: (BrcmFirmwareData) BrcmPatchRAM: Firmware is valid IntelHex firmware.
2020-03-19 00:12:05.009116+0700 0x195      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6412]: USB [F828196A17F0 v274] "BCM2045A0" by "Broadcom Corp"
2020-03-19 00:12:05.361487+0700 0x195      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6412]: Firmware upgrade completed successfully.
2020-03-19 00:12:05.361532+0700 0x195      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.452 seconds.
 

 

I found that sometimes it showed firmware version is 4689, sometimes is 4096, But 4689 cannot send file or using Bluetooth speaker. With 4096, It's work problematics (low speed, laggy and bad quality when connect BT Speaker). Sorry for my bad English.

I also attached an Images showing my USB Port Config.

Screen Shot 2020-03-23 at 23.06.33.png

Edited by kidinhvao
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted
33 minutes ago, seyedhossein said:

Update to 10.15.4

Broadcom bluetooth working like charm

Without any firmware or kext

Please be so kind and helpful and explain which kexts you are using now, and where? For what BTLE hardware? There is no such helpful info in your post, mate, thanks.

Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted
2 hours ago, seyedhossein said:

Update to 10.15.4

Broadcom bluetooth working like charm

Without any firmware or kext

 

 

 

Correct me if I'm wrong, but your BCM943602CS (0x05ac:8290) is a native device that doesn't need any kexts or firmware updates - correct?

Link to comment
Share on other sites
seyedhossein
seyedhossein
Posted
Posted (edited)
2 hours ago, MacKonsti said:

Please be so kind and helpful and explain which kexts you are using now, and where? For what BTLE hardware? There is no such helpful info in your post, mate, thanks.

Maybe I'm wrong

My pcie adapter is fenvi t919

and bluetooth didn’t work on my pc (amd ryzen cpu)

 

But:

Today when update to 10.15.4

and also update to opencore 0.5.6

The problem was solved

 

I would like to know how the problem is solved

 

EFI.zip

Edited by seyedhossein
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted
22 hours ago, seyedhossein said:

Maybe I'm wrong

My pcie adapter is fenvi t919

and bluetooth didn’t work on my pc (amd ryzen cpu)

 

But:

Today when update to 10.15.4

and also update to opencore 0.5.6

The problem was solved

 

I would like to know how the problem is solved

 

Your fenvi t919 is a macOS card with BCM943602CD (0x05ac:8290) that is natively supported by Catalina.  I'm not sure why it didn't work before.  According to this thread, 10.15.4 did fix "bluetooth bugs," so if you didn't change anything else in your upgrade to 10.15.4, it's possible that something in the 10.15.4 upgrade or even your OC upgrade fixed bluetooth.

Link to comment
Share on other sites
seyedhossein
seyedhossein
Posted
Posted
19 hours ago, tonyx86 said:

 

Your fenvi t919 is a macOS card with BCM943602CD (0x05ac:8290) that is natively supported by Catalina.  I'm not sure why it didn't work before.  According to this thread, 10.15.4 did fix "bluetooth bugs," so if you didn't change anything else in your upgrade to 10.15.4, it's possible that something in the 10.15.4 upgrade or even your OC upgrade fixed bluetooth.

Thanks For Reply

 

What has changed in macOS 10.15.4?

Just about Bluetooth:
Bluetooth File Exchange, updated to 7.0.4

Fixes three Bluetooth bugs

 

https://eclecticlight.co/2020/03/24/what-has-changed-in-macos-10-15-4/

Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted
2 hours ago, seyedhossein said:

Thanks For Reply

 

What has changed in macOS 10.15.4?

Just about Bluetooth:
Bluetooth File Exchange, updated to 7.0.4

Fixes three Bluetooth bugs

 

https://eclecticlight.co/2020/03/24/what-has-changed-in-macos-10-15-4/

 

Yes - exactly.  Did you have another question?

Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)

Hi everyone, just to inform you that my hardware BCM20702A0 (from my Azurewave BCM94352HMB) that works fine on latest Mojave (using v2.5.1 BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext only in /Library/Extensions/ ) does not work well in the just-released Catalina 10.15.4 update, still using v2.5.1 BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext and BrcmBluetoothInjector.kext in /Library/Extensions/ with correct BooterConfig=0x28 and CsrActiveConfig=0x67 in Clover. All other extensions are loaded just fine (Lilu, AppleALC, Whatevergreen, AirportBrcmFixup etc. so it's not a permissions problem). Running latest Clover r5107.

 

My USBs have been fixed (either USBInjectAll+UIAC or USBPorts.kext) and HS07 does detect in Hackintool the BCM20702A0@14700000 device/port. The BTLE device shows as detected, I get the BT icon on the top menu bar, but when I click to turn ON/OFF it doesn't work; seems be blocked. When I go in System Preferences and Bluetooth section, I get the "beachball" icon rotating and no BT devices detected at all.

 

On Mojave that works, System Information shows Firmware Version: v14 c5575 as well as on Catalina 10.15.4. My BT device has IDs 0x13D3 vendor and 0x3404 model.

 

If I move only BrcmFirmwareData.kext and BrcmPatchRAM3.kext and BrcmBluetoothInjector.kext in Clover's folder kext/10.15/ and select to load them, the BT seems to work but in System Information it shows Firmware Version: v14 c4096 (which I think is the original hardware...)

 

I chose to use all kexts from /L/E/ despite new Catalina not liking this at all...

 

Has anyone had this BT behaviour and solved it somehow? Thanks in advance.

Edited by MacKonsti
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)
On 3/29/2020 at 5:35 PM, MacKonsti said:

If I move only BrcmFirmwareData.kext and BrcmPatchRAM3.kext and BrcmBluetoothInjector.kext in Clover's folder kext/10.15/ and select to load them, the BT seems to work but in System Information it shows Firmware Version: v14 c4096 (which I think is the original hardware...)

 

Has anyone had this BT behaviour and solved it somehow? Thanks in advance.

 

*** IMPORTANT *** 

When "moving" Brcm Bluetooth kexts from /L/E to E/C/k/O (or vice versa), you must use BrcmFirmwareData.kext in E/C/k/O or BrcmFirmwareRepo.kext in /L/E as follows:

 

When placing Brcm Bluetooth kexts in /L/E:

  • BrcmFirmwareRepo.kext
  • BrcmPatchRAM3.kext
  • BrcmBluetoothInjector.kext
  • Lilu.kext

 

When placing Brcm Bluetooth kexts in E/C/k/O:

  • BrcmFirmwareData.kext
  • BrcmPatchRAM3.kext
  • BrcmBluetoothInjector.kext
  • Lilu.kext

 

---------------------------------------------

 

This is the behavior that I described previously in this thread before moving kexts to E/C/k/O with Clover "Inject Kexts" = YES.  Just out of curiosity, have you tried moving all your 3rd-party kexts to E/C/k/O, removing all 3rd-party kexts from /L/E and setting Clover "Inject Kexts" = YES?  If you try this (including moving FakeSMC.kext from /L/E to E/C/k/O), that will help to diagnose what's happening before entertaining other kext installation options.

Edited by tonyx86
Added *** IMPORTANT *** note
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)
On 3/30/2020 at 12:11 AM, tonyx86 said:

This is the behavior that I described previously in this thread before moving kexts to E/C/k/O with Clover "Inject Kexts" = YES.  Just out of curiosity, have you tried moving all your 3rd-party kexts to E/C/k/O, removing all 3rd-party kexts from /L/E and setting Clover "Inject Kexts" = YES?  If you try this (including moving FakeSMC.kext from /L/E to E/C/k/O), that will help to diagnose what's happening before entertaining other kext installation options.

 

Hi @tonyx86 I found the energy today to do this exercise, updated to Clover r5108 and moved all custom kexts to /E/C/k/O with a change to InjectKexts=Yes. Even changed CsrActiveConfig and BootConfig to 0x00.

The BTLE works, as you also experienced. Didn't try to connect my old Apple Wireless keyboard, need to find it someplace. But it detected nearby BT devices just fine.

 

Although it feels strange to abandon /L/E/ now, I hope pre-charging Clover with all kexts for Catalina 10.15.4 won't slow boot-times much. But I moved it all: FakeSMC (and its related kexts), Lilu, Whatevergreen, AppleALC, AirportBrcmFixup, RealtekRTL8111 and BrcmPatchRAM3, BrcmFirmwareRepo, BrcmBluetoothInjector.

 

However, it's my impression that these same Bluetooth kexts (BrcmPatchRAM2, BrcmFirmwareRepo) under Mojave seem to slow down the boot time a little, I am not sure but that's my impression.

Hope I helped.

Edited by MacKonsti
Link to comment
Share on other sites
badformat
badformat
Posted
Posted

Hi guys,

 

I've tried a bunch of different combinations from this post but can't make bluetooth work on Catalina 10.15.4

 

My setup:

ASrock z370 Fatal1ty
i7 8700
iGPU Intel Graphics 630
BCM94352Z

 

I don't even see Bluetooth as a device (System Report -> Bluetooth, System Report -> USB), Wi Fi works with AirportBrcmFixup.kext

 

Maybe someone could help me to understand what am I doing wrong? On my previous Mojave setup everything worked perfectly :(

Screenshot 2020-04-01 at 01.51.42.png

Screenshot 2020-04-01 at 01.51.57.png

Screenshot 2020-04-01 at 01.52.19.png

EFI.zip

Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)
On 3/31/2020 at 6:38 PM, MacKonsti said:

 

Hi @tonyx86 I found the energy today to do this exercise, updated to Clover r5108 and moved all custom kexts to /E/C/k/O with a change to InjectKexts=Yes. Even changed CsrActiveConfig and BootConfig to 0x00.

The BTLE works, as you also experienced. Didn't try to connect my old Apple Wireless keyboard, need to find it someplace. But it detected nearby BT devices just fine.

 

Now that you know this works, try the following

  1. Move all but BrcmPatchRAM3.kext and BrcmFirmwareData.kext back to /L/E.  The only kexts in E/C/k/O should be BrcmPatchRAM3.kext and BrcmFirmwareData.kext.  All other kexts (including BrcmBluetoothInjector.kext and FakeSMC.kext) should be in /L/E.  No kexts should be duplicated in /L/E and E/C/k/O and /S/L/E.
  2. Fix permissions and rebuild kextcache (I've started using @headkaze's Hackintool to install kexts - it's awesome)
  3. Leave Clover "Inject Kexts" = YES and change Clover configs back to 0x28 / 0x67
  4. Reboot

I have found that this is the closes I can come to having all kexts in /L/E.  Reread this post for the details.

 

*** IMPORTANT *** 

You must use BrcmFirmwareData.kext in E/C/k/O or BrcmFirmwareRepo.kext in /L/E as follows:

 

When placing Brcm Bluetooth kexts in /L/E:

  • BrcmFirmwareRepo.kext
  • BrcmPatchRAM3.kext
  • BrcmBluetoothInjector.kext
  • Lilu.kext

 

When placing Brcm Bluetooth kexts in E/C/k/O:

  • BrcmFirmwareData.kext
  • BrcmPatchRAM3.kext
  • BrcmBluetoothInjector.kext
  • Lilu.kext

 

---------------------------------------------

Edited by tonyx86
Added *** IMPORTANT *** note
Link to comment
Share on other sites
Alpha22
Alpha22
Posted
Posted (edited)

question: it is right that it should not be loaded

 

Schermata-2020-04-02-alle-18-13-45.png

 

Spoiler

Last login: Thu Apr  2 18:02:43 on console

fabio@iMac-di-Fabio ~ %  log show --last boot | grep -i brcm

2020-04-02 18:00:27.607555+0200 0xe7       Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::init AirPortFamily_kexts-1701.6 "AirPortFamily_kexts-1701.6" Mar  4 2020 22:20:14

2020-04-02 18:00:27.607573+0200 0xe7       Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 0.607571: AirPort_Brcm43XX:probe:, this[0x7c7e600a655fb309]  score[2048]

2020-04-02 18:00:27.607582+0200 0xe7       Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::init AirPortFamily_kexts-1701.6 "AirPortFamily_kexts-1701.6" Mar  4 2020 22:20:14

2020-04-02 18:00:27.607590+0200 0xe7       Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 0.607589: AirPort_Brcm43XX:probe:, this[0x7c7e600a655ff309]  score[1400]

2020-04-02 18:00:39.668876+0200 0x5ec      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: Version 2.5.1 starting on OS X Darwin 19.4.

2020-04-02 18:00:39.670352+0200 0x5fa      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::init AirPortFamily_kexts-1701.6 "AirPortFamily_kexts-1701.6" Mar  4 2020 22:20:14

2020-04-02 18:00:39.670387+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 13.531852: AirPort_Brcm43XX:probe:, this[0x7c7e600a67c97309]  score[2048]

2020-04-02 18:00:39.670397+0200 0x5fa      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::init AirPortFamily_kexts-1701.6 "AirPortFamily_kexts-1701.6" Mar  4 2020 22:20:14

2020-04-02 18:00:39.670418+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 13.531883: AirPort_Brcm43XX:probe:, this[0x7c7e600a6614f309]  score[1400]

2020-04-02 18:00:39.777259+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 13.638721: srom rev:11

2020-04-02 18:00:39.885096+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) Setting property subsystem-id to:855c

2020-04-02 18:00:39.885102+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) Setting property subsystem-vendor-id to:106b

2020-04-02 18:00:39.889207+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 13.750672: BRCM tunables:

2020-04-02 18:00:39.889214+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 13.750678:   pullmode[1] txringsize[  256] txsendqsize[0] reapmin[   32] reapcount[  128]

2020-04-02 18:00:39.889306+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) wl0: Broadcom BCM43b1 802.11 Wireless Controller

2020-04-02 18:00:39.890231+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 13.751695: wl0: Broadcom BCM43b1, vendorID[0x14e4] BAR0[0xdfa00004]

2020-04-02 18:00:39.890285+0200 0x5fa      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 13.751750: Set packet allocation type to 1

2020-04-02 18:00:40.100633+0200 0x2bd      Error       0x0                  63     0    kextd: (IOKit) [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x6000011c0d20 [0x7fff8742b8c0]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "as.acidanthera.BrcmFirmwareStore" }

2020-04-02 18:00:40.140047+0200 0x72a      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC::getSSIDData(): Get failure: APPLE80211_IOC_SSID: 6

2020-04-02 18:00:40.295320+0200 0x5ec      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1469_v5565.zhx" from resources.

2020-04-02 18:00:40.295759+0200 0x5ec      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29711 bytes --> 70105 bytes).

2020-04-02 18:00:40.296160+0200 0x5ec      Default     0x0                  0      0    kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware.

2020-04-02 18:00:40.397431+0200 0x5ec      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: uploadFirmware could not open the device!

2020-04-02 18:00:40.397436+0200 0x5ec      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: Processing time 0.101 seconds.

2020-04-02 18:00:40.835434+0200 0x7cf      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: Version 2.5.1 starting on OS X Darwin 19.4.

2020-04-02 18:00:40.935646+0200 0x7cf      Default     0x0                  0      0    kernel: (kernel) BrcmPatchRAM: [0b05:17cf]: USB [54271EBEF0AB v274] "BCM20702A0" by "Broadcom Corp"

2020-04-02 18:02:24.636160+0200 0x9bb      Error       0x0                  342    0    kextcache: [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x7fce12866130 [0x7fff8742b8c0]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "as.acidanthera.BrcmFirmwareStore" }

2020-04-02 18:02:24.642516+0200 0x9bb      Error       0x0                  342    0    kextcache: [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x7fce1288a140 [0x7fff8742b8c0]> { URL = "file:///Library/Extensions/BrcmPatchRAM3.kext/", ID = "as.acidanthera.BrcmPatchRAM3" }

2020-04-02 18:02:24.741795+0200 0x9bb      Error       0x0                  342    0    kextcache: [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x7fce10722330 [0x7fff8742b8c0]> { URL = "file:///Library/Extensions/BrcmBluetoothInjector.kext/", ID = "as.acidanthera.injector.BrcmBluetoothInjector" }

2020-04-02 18:02:25.052804+0200 0x9bb      Error       0x0                  342    0    kextcache: [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x7fce0df77a40 [0x7fff8742b8c0]> { URL = "file:///Library/Extensions/AirportBrcmFixup.kext/", ID = "as.lvs1974.AirportBrcmFixup" }

2020-04-02 18:03:42.383112+0200 0x1606     Default     0x0                  354    7    corecaptured: (CoreCaptureDaemon) [com.apple.corecaptured:corecapture] CCLogTap::profileRemoved, Owner: com.apple.driver.AirPort.Brcm4360.0, Name: DriverLogs

2020-04-02 18:03:42.383745+0200 0x1606     Default     0x0                  354    7    corecaptured: (CoreCaptureDaemon) [com.apple.corecaptured:corecapture] CCDataTap::profileRemoved, Owner: com.apple.driver.AirPort.Brcm4360.0, Name: StateSnapshots

2020-04-02 18:04:39.236046+0200 0x696      Default     0x0                  0      0    kernel: (IO80211Family) IO80211VirtualInterface::AirPort_BrcmNIC_P2PInterface::init name <p2p0> role 1

2020-04-02 18:04:39.236463+0200 0x696      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC_P2PInterface::init <p2p> role 1

2020-04-02 18:04:39.447582+0200 0x696      Default     0x0                  0      0    kernel: (IO80211Family) IO80211VirtualInterface::AirPort_BrcmNIC_P2PInterface::init name <awdl0> role 4

2020-04-02 18:04:39.447593+0200 0x696      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC_P2PInterface::awdlAttachToBpf name <awdl0> role 4 successful attach to bpf type 147

2020-04-02 18:04:39.450851+0200 0x696      Default     0x0                  0      0    kernel: (IO80211Family) AirPort_BrcmNIC_P2PInterface::init <awdl> role 4

2020-04-02 18:04:39.473762+0200 0x190e     Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 252.468339: wl0: setAWDL_PEER_TRAFFIC_REGISTRATION: active 0, roam_off: 1, err 0 roam_start_set 0 forced_roam_set 0

2020-04-02 18:04:39.515919+0200 0x692      Default     0x0                  0      0    kernel: (AirPortBrcmNIC) ARPT: 252.510496: AirPort_Brcm43xx::syncPowerState: WWEN[disabled]

fabio@iMac-di-Fabio ~ % 

 

 

Edited by Alpha22
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)
On 4/1/2020 at 5:03 AM, tonyx86 said:

Now that you know this works, try the following

  1. Move all but BrcmPatchRAM3.kext and BrcmFirmwareData.kext back to /L/E.  The only kexts in E/C/k/O should be BrcmPatchRAM3.kext and BrcmFirmwareData.kext.  All other kexts (including BrcmBluetoothInjector.kext and FakeSMC.kext) should be in /L/E.  No kexts should be duplicated in /L/E and E/C/k/O and /S/L/E.
  2. Fix permissions and rebuild kextcache (I've started using @headkaze's Hackintool to install kexts - it's awesome)
  3. Leave Clover "Inject Kexts" = YES and change Clover configs back to 0x28 / 0x67
  4. Reboot

I have found that this is the closes I can come to having all kexts in /L/E.  Reread this post for the details.

 

Hi @tonyx86 thanks for your message and suggestions; before this exercise, I wanted to test BTLE module that it works as expected, nevermind if it shows up OK on IOReg or System Info.

Unfortunately, it does not work.

Upon reboot, the device does see the neighbouring BT devices, when I tried to connect either Apple old Aluminum BT keyboard or my Logitech Anywhere MX2 BT mouse, it would not connect to them (pair).

Then all of a sudden, I lose all devices detected in System Preferences > Bluetooth list.

I switch off, on again after few seconds, nothing.

Despite kext loaded etc. the BT functionality is broken.

I suspect that, because I had booted before this test to Mojave where BT worked, the next reboot to Catalina had still BTLE module on and possibly pre-kept the detected devices?

I cannot know. What I see is that BCM20702A0 (from my Azurewave BCM94352HMB) does not work properly at all, in either /L/E/ or E/C/k/O :( despite being "detected" OK by the system.

Is this a firmware issue not being loaded OK from the kext? I am always getting v14 c4096... reminds me of pre-High-Sierra same problems, BTLE module seen by the system as hardware ID etc. but not connecting to ANY wireless device :(

 

 

Therefore to everyone, if on Catalina you see your BTLE module being detected OK but the firmware is not upgraded via BrcmFirmwareData.kext or BrcmFirmwareRepo.kext chances are that you will not connect (pair) any wireless device OK!

Edited by MacKonsti
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted
1 hour ago, MacKonsti said:

 

Hi @tonyx86 thanks for your message and suggestions; before this exercise, I wanted to test BTLE module that it works as expected, nevermind if it shows up OK on IOReg or System Info.

Unfortunately, it does not work.

Upon reboot, the device does see the neighbouring BT devices, when I tried to connect either Apple old Aluminum BT keyboard or my Logitech Anywhere MX2 BT mouse, it would not connect to them (pair).

Then all of a sudden, I lose all devices detected in System Preferences > Bluetooth list.

I switch off, on again after few seconds, nothing.

Despite kext loaded etc. the BT functionality is broken.

I suspect that, because I had booted before this test to Mojave where BT worked, the next reboot to Catalina had still BTLE module on and possibly pre-kept the detected devices?

I cannot know. What I see is that BCM20702A0 (from my Azurewave BCM94352HMB) does not work properly at all, in either /L/E/ or E/C/k/O :( despite being "detected" OK by the system.

Is this a firmware issue not being loaded OK from the kext? I am always getting v14 c4096... reminds me of pre-High-Sierra same problems, BTLE module seen by the system as hardware ID etc. but not connecting to ANY wireless device :(

 

 

Therefore to everyone, if on Catalina you see your BTLE module being detected OK but the firmware is not upgraded via BrcmFirmwareData.kext or BrcmFirmwareRepo.kext chances are that you will not connect (pair) any wireless device OK!

 

Something else is wrong with your config.  Can you run black.dragon74's gen_debug and post the problem reporting files?

Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted
On 4/3/2020 at 7:29 AM, MacKonsti said:

I cannot know. What I see is that BCM20702A0 (from my Azurewave BCM94352HMB) does not work properly at all, in either /L/E/ or E/C/k/O :( despite being "detected" OK by the system.

 

When you place Brcm Bluetooth kexts in E/C/k/O, you must use BrcmFirmwareData.kext and NOT BrcmFirmwareRepo.kext.  BrcmFirmwareRepo.kext is to be used only when placing Brcm Bluetooth kexts in /L/E.

 

Remove BrcmFirmwareRepo.kext from E/C/k and replace with BrcmFirmwareData.kext.  Also, I have not tried using E/C/k/O and E/C/k/10.15 kext folders.  For this test, place all kexts in E/C/k/O and don't use E/C/k/10.15.

  • Like 2
Link to comment
Share on other sites
mansik
mansik
Posted
Posted

I am building a Catalina, and I try to use 

- AirportBrcmFixup.kext

- BrcmBluetoothInjector.kext

- BrcmFirmwareData.kext

- BrcmPatchRAM3.kext

for my WiFi and Bluetooth card (BCM943224PCIEBT2) with a adaptor to replace my motherboard (MSI B450i Gaming AC)'s original one.

 

The WiFi is work good by the AirportBrcmFixup.kext , but the bluetooth is not work which is not show in my system.

 

I checked by the Hackintool, those kexts (BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext) are not install when system boot.

 

ref_1.png

ref_2.png

ref_3.png

Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)
On 4/4/2020 at 4:49 PM, tonyx86 said:

When you place Brcm Bluetooth kexts in E/C/k/O, you must use BrcmFirmwareData.kext and NOT BrcmFirmwareRepo.kext.  BrcmFirmwareRepo.kext is to be used only when placing Brcm Bluetooth kexts in /L/E.

Remove BrcmFirmwareRepo.kext from E/C/k and replace with BrcmFirmwareData.kext.  Also, I have not tried using E/C/k/O and E/C/k/10.15 kext folders.  For this test, place all kexts in E/C/k/O and don't use E/C/k/10.15.

 

Hi @mansik not sure if you read the previous pages, try what @tonyx86 suggested, move all custom kexts to E/C/k/O and rebuild caches and restart... it worked for me flawlessly.

Edited by MacKonsti
Link to comment
Share on other sites
mansik
mansik
Posted
Posted
22 minutes ago, MacKonsti said:

 

Hi @mansik not sure if you read the previous pages, try what @tonyx86 suggested, move all custom kexts to E/C/k/O and rebuild caches and restart... it worked for me flawlessly.

@MacKonsti Thanks your reply..

Sorry, I didn't mentioned i am using OpenCore 0.5.6, I tried to remove all related kexts (Brcmxxxxx.kext), and add again. But after restart, its same.

Link to comment
Share on other sites
cvigu
cvigu
Posted
Posted

Hi Folks,

 

I have a bluetooth problem as well, and I'm trying to solved like 1 month now without success (and this is my 5th build).

 

So the thing is: I have a DW1560 (dell version of bcm94352z) and a Dell Latitude 5400 running Catalina 10.15.4

My bootloader is OpenCore 0.5.6.

 

The problem: The bluetooth is available, but searching is not working. I can see the device from my phone, I can pair with my magicmouse2 using cable, but the connection is poor and drops after ~10sec.

 

This exact problem existed with the same card in my previous build: Dell Latitude e5450 running Catalina 10.15.2 with Clover 5100.

However I don't think there is a HW failure because it works with a Windows VM.

 

I've found suspicious messages in the log but Google literally gave me nothing relevant: 

2020-04-06 16:25:49.464384+0200 0x18f      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: END OF RECORD complete (status: 0x00, length: 4 bytes).
2020-04-06 16:25:49.469058+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: State "Instruction write" --> "Firmware written".
2020-04-06 16:25:49.518438+0200 0x18f      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: RESET complete (status: 0x00, length: 4 bytes).
2020-04-06 16:25:49.522104+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: State "Firmware written" --> "Reset complete".
2020-04-06 16:25:49.523829+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: Device reset.
2020-04-06 16:25:49.529529+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: Device status 0x00000003.
2020-04-06 16:25:49.543040+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: State "Reset complete" --> "Update complete".
2020-04-06 16:25:49.543245+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: Firmware upgrade completed successfully.
2020-04-06 16:25:49.543675+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 1.308 seconds.
2020-04-06 16:26:10.455010+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:10.455317+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:11.014518+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:11.014745+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:11.576424+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:11.576736+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:12.131987+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:12.132149+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:12.657499+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:12.657713+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:13.217674+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:13.217888+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
[...setPowerState flips forever...]

 

I have installed the recent version of the necessary kexts, I have everything under OC/K (the base system is vanilla (SIP enabled)):

image.thumb.png.84c0c2257270b4948beba4d4005c16b6.png

 

The USB port patching is done: *EDIT: after one day sleep I reallized there is too many internal connector here... I'll update the post soon, but I don't think this is the problem.*

EDIT2: So I fixed it. Installed XHCI-unsupported, tried with SSDT and usbinjectall, no success. Went to USBPorts.kext method, works like a charm, altought I would prefer the SSDT one.

image.thumb.png.bc490494c146a82f6d1d534cccdb67dd.png

 

Device recognized, firmware is uploaded:

image.png.b424a95cdbe3e63a077a3ceb5e6668b2.png

 

 

Any help, idea, guidance would be really appreciated :)

Let me know if you need some more data for debugging.

 

Thank you,

cvigu

image.png

config.plist

opencore-2020-04-07-113052.txt

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...