kext VS bugtracker

do you have both USBToolBox.kext and UTBMap.kext? you need both USBToolBox.kext and UTBMap.kext for USBToolBox to function. https://github.com/USBToolBox/tool https://github.com/USBToolBox/kext

https://github.com/USBToolBox/toolhttps://github.com/USBToolBox/kext

Output from usb mapping is UTBMap.kext. Then you add USBToolbox.kext

If you have access to windows, this is a good usb mapping script. https://github.com/USBToolBox/kext. Heaps of guides around.

USBtoolbox, UTBmap

Do the usb mapping with USBToolboxadd Toolbox.kext too

Next, head here (https://github.com/USBToolBox/kext/releases)

Before you install OSX on the target machine, install Windows 10 or Windows 11 first. Make sure that ALL of your drivers for Windows 10 or 11 are installed (especially your chipset drivers). Use the Windows version of USBToolBox, and map your ports per their instructions (basic instructions are on the same page with the utility). Grab that here: https://github.com/USBToolBox/tool. Run the Windows.exe version (your antivirus software will go nuts trying to run this on your machine, either allow it, or rename the executable after unpacking it). Copy the created kext (called UTBMap.kext) file this program creates onto a separate flash drive to use after MacOSX is installed. Next, head here (https://github.com/USBToolBox/kext/releases), and grab the two kexts (USBToolBox.kext and UTBDefault.kext) within the zip file. Unpack, and put them in your EFI/OC/Kexts folder on your bootable USB drive. Use ProperTree to open the config.plist on your bootable drive, do an OC Clean Snapshot (this updates the config.plist with the new kexts you added), and SAVE.

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: