Trim Enabler - El Capitan

[amoergosum]

I updated my OSX from Mavericks to El Capitan yesterday. After the installation OSX automatically
disabled Trim Enabler and moved it into an "incompatible" folder.

I opened that folder and Trim Enabler. After checking for updates it installed Trim Enabler v.3.4.2 .
Then I moved Trim Enabler to applications.

I can move the switch in Trim Enabler to "on" now. In order for it to take effect, the system would need to reboot.

Is is safe to proceed? Does the latest version of Trim Enabler (3.4.2) work with OSX 10.11.1 ?

 

[KALLT]

I think it does, but you don't need it anymore. Apple now lets you enable TRIM natively. All you have to do is type the following command into Terminal and reboot. I think Trim Enabler uses the same command now, but I'm not sure. They used to have their own implementation as a kernel extension.

sudo trimforce enable

 

[Evren Carven]

This is a description for 'Trim Enabler 3.4' from their website.
Trim Enabler 3.4:
– Revamped Trim Enabling: Trim Enabler now uses a custom Cindori driver to safely enable Trim for 3rd party drives!
– Added OS X El Capitan support
– Added OS X 10.10.4 support

So you should use it carefully in OS X 10.11.1 with your own risk.

 

[amoergosum]

So trimforce works the same way Trimenabler

This is a description for 'Trim Enabler 3.4' from their website.
Trim Enabler 3.4:
– Revamped Trim Enabling: Trim Enabler now uses a custom Cindori driver to safely enable Trim for 3rd party drives!
– Added OS X El Capitan support
– Added OS X 10.10.4 support

So you should use it carefully in OS X 10.11.1 with your own risk.

Thanks for the information.

I guess I'll use the command which KALLT suggested ("sudo trimforce enable") instead then.



...just read this:

"About Cindori's Disk Sensei and Trim Enabler:

I can already see the confusion growing due to Cindor's intentionally vague statements. The method that Cindori (Disk Sensei/Trim Enabler) is bringing out is *identical* to the "trimforce" command method in my guide. He has created his own .kext file that injects the "Force Data Set Management = YES" option in the exact same way as the official extension. His method is not "safer" at all. It's the exact same thing; with one small difference: He installs the injector to /Library whereas the trimforce tool installs the injector to /System/Library - and the latter is protected by "rootless" on El Capitan, but that seems like an oversight on Apple's part. Either way, you can easily disable rootless, run trimforce, and re-enable rootless on the current El Capitan beta (instructions for that are in the link above). Moreover, it's very likely that Apple is going to fix it before release so that you don't need to even temporarily disable rootless to run trimforce.

I'll say it one more time: There is no reason whatsoever to use Cindori's injector instead of Apple's injector; they do the *exact* same thing. I even suggest using Apple's since they're the ones who created the method, and if any of the implementation details ever change they'll be the first to update their official kext.

There are plenty of reasons to use Cindori's Disk Sensei: Disk space visualization, benchmarking, SMART health monitoring, various tweaks to prolong SSD life (like "noatime"). "TRIM enabling" is no longer a reason to own the tool."

Link:
https://www.macrumors.com/2015/07/01/os-x-trim-ssd/

 

[simonsi]

So you should use it carefully in OS X 10.11.1 with your own risk.

The question is why would you use Trim Enabler at all on 10.10.4 or later? Its had its day, the functionality is now built in to the OS.

 

[KALLT]

Trim Enabler has some diagnostic tools and "tweaks". If you're purely interested in TRIM then it is indeed obsolete. As a rule of thumb, it is generally advisable to prefer system methods when they do the same thing.

 

[amoergosum]

Ok...I just used the "sudo trimforce enable" command. My SSD is a Samsung Evo 840.
Everything seems to be working fine.

Thank you guys!

 

[Max(IT)]

Ok...I just used the "sudo trimforce enable" command. My SSD is a Samsung Evo 840.
Everything seems to be working fine.

Thank you guys!

that's the best solution