Stefanalmare Posted August 17, 2021 Share Posted August 17, 2021 Can somebody explain the difference between "trim force enable" and trim kernel patch? Link to comment Share on other sites More sharing options...
Allan Posted August 17, 2021 Share Posted August 17, 2021 28 minutes ago, Stefanalmare said: Can somebody explain the difference between "trim force enable" and trim kernel patch? You can see more here: In a nutshell: trim force enable = for Apple Hardware that didn't came with Apple SSDs the patch = for Hackintoshes (I guess) Both do the same. Link to comment Share on other sites More sharing options...
eSaF Posted August 17, 2021 Share Posted August 17, 2021 3 minutes ago, Allan said: You can see more here: In a nutshell: trim force enable = for Apple Hardware that didn't came with Apple SSDs the patch = for Hackintoshes (I guess) Both do the same. As far as I understand, most modern Drives has builtin garbage collection included in the firmware specially M.2 drives. I have 2 M.2 Drives in my system and did not load any Trim patches but both are showing Trim is indeed activated. 2 Link to comment Share on other sites More sharing options...
eSaF Posted August 17, 2021 Share Posted August 17, 2021 Not to prolong the Trim debate but I remembered using the Trim patch in a previous OS X version booting with Clover on SSD Drives and even then there was a debate whether it was a good thing to do as some claimed it was unnecessary also it slowed down boot times. When I switched my drives over to M.2, I noticed Trim was automatically enabled without applying the Trim patch so I left alone. I don't profess to know whether to Trim or not to Trim but reading @Hervé and other posts, I tend to follow the general consensus and hope for the best. Spoiler Link to comment Share on other sites More sharing options...
Allan Posted August 17, 2021 Share Posted August 17, 2021 But you're right @eSaF. I notice that with the NVMe drivers we don't need to worry about, but using SATA SSDs we need to enable it. Now with the newer versions of macOS, we can just run the native command. If we put a SATA SSD on a real Mac, to prolong the life of it is a good idea to run that command. 1 Link to comment Share on other sites More sharing options...
obus Posted August 17, 2021 Share Posted August 17, 2021 (edited) Hi @eSaF I observed that your your Samsung SSD 970 EVO Plus is showing up under Apple SSD Controller. I have the same disk but mine are showing up under a Generic SSD Controller. Could this have to do with which version of Big Sur you are running, (I'm on 11.5.2) or could it be something else? Any suggestion? Spoiler Edited August 17, 2021 by obus Link to comment Share on other sites More sharing options...
Stefanalmare Posted August 17, 2021 Author Share Posted August 17, 2021 (edited) 27 minutes ago, obus said: Hi @eSaF I observed that your your Samsung SSD 970 EVO Plus is showing up under Apple SSD Controller. I have the same disk but mine are showing up under a Generic SSD Controller. Could this have to do with which version of Big Sur you are running, (I'm on 11.5.2) or could it be something else? Any suggestion? Reveal hidden contents Use this. But change to your IOPCIPrimaryMatch. I saw improvement on stability after using this kext. The question is: put this in front of NVMeFix.kext or after, in opencore config? X299NVMe.kext.zip Edited August 17, 2021 by Stefanalmare 3 Link to comment Share on other sites More sharing options...
Recommended Posts