IntelBluetoothFirmware VS bugtracker

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.

Shot in the dark, but it could be broken TRIM on the drive? Samsung drives are notoriously buggy with MacOS (with a few exceptions). See here and read on.

Do you mind trying to deactivate AppleCpuFmCfgLock and AppleXcpmCfgLock in your config.plist (Kernel) but also add those 2 kext : https://github.com/dortania/bugtracker/issues/190 (CpuFriendDataProvider.kext) along with its dependency CpuFriend.kext? https://github.com/acidanthera/CPUFriend

Phison controllers used to be great but many have broken TRIM in Monterey and higher.

Recently I needed to upgrade my drive, and after reading this: https://github.com/dortania/bugtracker/issues/192 I decided on a WD Black SN770. I wanted to make sure it was a drive that behaved well with MacOS. This Github thread also calls out the Phison E12 as being troublesome.

You might be hitting an issue with the “trim” firmware implementation on your nvme drive. Unfortunately the Samsung 970 pro has a buggy/badly implemented trim algorithm that macos seems to hit on boot. The hackint*sh community has reported on it for a while now: see https://github.com/dortania/bugtracker/issues/192 Unfortunately I haven’t heard of any fixes, accept the longer boot times (the more time the system has been running for last since the last boot, the longer the next boot will be as there will be more block to for the trim algorithm to sift though.) Or replace it with a different / more supported model. The attached link should help with know models. Good luck.

I think this is the page you need: https://github.com/dortania/bugtracker/issues/192

GPU: AMD RX6600 is fully supported by Apple. Check this for further information on the support for the RX6600 on macOS. You should add this in boot-args: