CPUFriend VS IntelBluetoothFirmware

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

How are you doing your power management? Have you tried CPUFriend ??

Guides used: Used the following repo as a starting point since the board is basically identical https://github.com/luchina-gabriel/EFI-GIGABYTE-Z690-AORUS-ELITE-AX-12900K-RX6900XT Additional info/resources from: https://dortania.github.io/OpenCore-Install-Guide/ https://chriswayg.gitbook.io/opencore-visual-beginners-guide/advanced-topics/using-alder-lake https://github.com/acidanthera/CPUFriend https://github.com/dortania/bugtracker/issues/190 Use case: The machine is used as my main work machine (Software developer working from home) and hobby/gaming PC.

CPU: i5-6300U CPU @ 2.40GHz/Skylake GPU: Intel HD Graphics 520/Skylake (Iris 550) RAM: 12GB SKHynix DDR4@2300 Laptop Make and Model: Dell Latitude E7470 (TouchScreen) Audio Codec: Realtek ALC3235 Ethernet Card: Intel I219-LM (IntelMAUSI 1.0.7) Wifi/BT Card: Intel 8260 Touchpad and touch display devices: ALPS/Alpine (V8) TrackPad, and ELANtech Touchscreen (via VoodooI2C). Brightness Keys and Ambient Light Sensors all work. Storage: Toshiba 256GB NVME - KXG50ZNV256G BIOS revision: 1.32.4 Guides Used - OC Guide and a lot of googling/head scratching trying to get multi-touch/gestures working on the TrackPad. First time i've actually had to use CPUFriend in OC as I couldn't get any sort of reasonable battery life or power management. Also the first Dell Laptop i've done that wasn't a Sandy/IvyBridge. What's working: Almost Everything - including iServices/iMessage, touchscreen w/multi-touch and gestures. SD card (via This version of the Sinetek Kext. Touchpad only has basic features. What isn't working: WWAN (not using anyways) Alps Trackpad only has basic mouse features. Wasted too much time on it. Voodoo Input/PS2 is stable.

See acidanthera/CPUFriend: Dynamic macOS CPU power management data injection

By NPM I meant CPU power management. Since you spoof CPU (Haswell support dropped for v12), your CPU PM is off. You need CPUFriend to make it work again.

CPUFriend

Since this CPU is not from iMac15,1 family, Native CPU Power Management won't work. You may want to check CPUFriend.

Always do your research. https://github.com/acidanthera/CPUFriend

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.