Jump to content
5 posts in this topic

Recommended Posts

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.

 

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.

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

200895487_Screenshot2021-08-17at23_00_41.thumb.png.2fea10a521354c60df2286c768f9c4a0.png

 

Edited by obus
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

200895487_Screenshot2021-08-17at23_00_41.thumb.png.2fea10a521354c60df2286c768f9c4a0.png

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 by Stefanalmare
  • Like 2
×
×
  • Create New...