IntelBluetoothFirmware VS OS-X-USB-Inject-All

Can you share bluetooth kext u r using ? I use https://github.com/OpenIntelWireless/IntelBluetoothFirmware 2.3 but not working

Intel AC 8260 WiFi+BT - AirportItlwm + IntelBluetoothFirmware

Here's the issue I used Google translate to get an understanding of the discussion.

Take out the AMDRyzenCPUPowerManagement.kext. Add AirportItlwm.kext (if you have Intel Wifi) and IntelBluetoothFirmware.kext. Also, make SURE you grab the correct AirportItlwm kext for your operating system (Big sur, Monterey, etc.). I'm assuming your UTBMap kext is the USB map. You might want to rename that and see if that helps as well (to USBMap or USBPorts).

I was able to get my ASUS z790 up and working with Bluetooth and WiFi on Mojave. I used OpenIntelWireless at https://github.com/OpenIntelWireless

3) WIFI and Bluetooth

For bluetooth, you need to use this https://github.com/OpenIntelWireless/IntelBluetoothFirmware

Wifi/BT Card: Intel® Wi-Fi 6E AX210 (Wifi working flawlessly with OpenIntelWireless (using AirportItlwm for better macOS experience) but bluetooth (IntelBluetoothFirmware + BlueToolFixup.kext) don't - can turn on but laggy)

Wifi (itlwm, Use Airport-Monterey) and Bluetooth (IntelBluetoothFirmware, Don't follow their Monterey instructions. Also use BlueToolFixup from BrcmPatchRAM)

I digged into discussions about Monterey's bluetooth support problems, which said that Apple downgraded BT support to 5.0, while some of Intel's BT adapters support only BT 5.2. But one commit of IntelBluetoothFirmware said that it added support for those cards. I switched to Windows and found the VID/PID of the bluetooth device is precisely 8087/0026, which is in the support list.

4) PORTS (have external monitor at 1080p 165hz working through Mini-DisplayPort)

Try XHCI-unsupported

Worth mentioning that USBInjectAll does not discover ports on its own - it has all known port personalities for a set collection of chipset USB controllers hardcoded in its Info.plist (seen here). It just supplements potentially missing/incomplete data that the mobo fw devs may not have included, and if it's not explicitly configured (via boot args or SSDT-UIAC), it just injects all available personalities. Hence the name - USB inject all.

Alright. First off, get this file for usbinjectall.kext Next you are going to want to find your opencore folder. Do you know how to navigate to it?

Same for me, I have also tried XHCI-unsupported but no luck. It was working ok in Catalina. Mine is an MSI Modern 15 i5