TrimEnabler problems with Yosemite

[Hanswurstlsepp]

Maybe helpful for others, so that that they won't run into the same problems I got now with 2 different Macs:

http://www.cindori.org/trim-enabler-and-yosemite/

[Park Seward]

One solution is to use an SSD with built-in Trim, like the drives from OWC.

"With An OWC SSD, There’s No Need For TRIM"

http://blog.macsales.com/21641-with-...-need-for-trim

[Hanswurstlsepp]

Originally Posted by Park Seward

One solution is to use an SSD with built-in Trim, like the drives from OWC.

"With An OWC SSD, There’s No Need For TRIM"

http://blog.macsales.com/21641-with-...-need-for-trim

Thanx Park for the tip :)

Another solution would be, to stick in 10.9.x as long as possible
This is what I will do now !

[Hanswurstlsepp]

Originally Posted by Darryl Ramm

The Citori information about Trim Enabler and OS X signed kexts that started this thread has been posted on and discussed on DUC recently in several other threads. It really would be great if folks searched for existing posts/threads before starting yet another one.

Sorry - please forgive me !

I missed those threads and simply thought this info might be useful for others as well !

[Park Seward]

Originally Posted by Darryl Ramm

Firstly there is no such things as "built-in TRIM",

To be clear, I should have said built-in SUPPORT for Trim.

"All OWC Mercury SSDs have a SandForce Processor installed. Through the DuraWrite technology, over-provisioning, and the garbage collection in the SandForce processer of our OWC Mercury SSDs, the need for TRIM is negated".

So far, my OWC SSD has been working fine.

[Hanswurstlsepp]

However, I updated to OS 10.10.2 (cause I got strange PT-crashes with 10.10.1 ... thought it couldn't get worse with 10.10.2) and trashed TrimEnabler.

All fine so far - not remarking any performance decrease without TrimEnabler and PT crashes are almost gone !

I'm using a Samsung SSD 850 Pro 1TB (I know it's oversized for my 4,1 MacPro).

[Park Seward]

And another view:

"With Trim Enabler, you can bring trim to any solid state drive. Trim is must-have feature for most SSDs. It not only increases data writing speeds, but it increases the lifetime of the SSD itself."

http://www.cindori.org/trim-enabler-and-yosemite/

"About SSDs and LBA
An SSD writes small bits data to “pages,” and multiple pages make up blocks. The SSD uses something called Logical Block Addressing (LBA) to keep track of which pages and blocks have information on them. This is a kind of map that details which pages and blocks are and aren’t occupied with “good” data. When you delete information from an SSD, that information isn’t really deleted. Rather, a reference to it is removed from the LBA and it’s marked as invalid data. When the drive can’t find any remaining open pages, it looks for the pages that contain invalid data to erase to make room for the fresh stuff.

The difficulty is that the drive can’t erase individual pages. It has to overwrite blocks. So if you have a block where half the data is good and half invalid, you have to move the good data to another location before you can erase the block. This takes time and slows down the drive’s performance.

The controllers within SSDs have a technology called “garbage collection” that moves the data within pages—both the good and invalid data—to new blocks and then erases the old ones. TRIM works at the operating system level and ensures that only the good data is moved. Invalid data is erased when the drive is otherwise idle. In sum, the two technologies speed up the drive’s performance so that it’s not performing a lot of needless move and erase actions."

http://www.macworld.com/article/2849...party-ssd.html

[Spaced]

Just disable kext signing with: sudo nvram boot-args="kext-dev-mode=1 in Terminal and Trim Enabler will work just fine

[Hanswurstlsepp]

Originally Posted by Spaced

Just disable kext signing with: sudo nvram boot-args="kext-dev-mode=1 in Terminal and Trim Enabler will work just fine

I know bout that terminal command, but will it be remembered by the OS if I i.e. zap Parameter Ram ???

[Hanswurstlsepp]

Originally Posted by Darryl Ramm

That and many other systems setting are stored in PRAM. But so what? If you ever have to reset PRAM you have to go around and reset lots of things. If TrimEnabler does not run/you see the unsigned kext warning just reset it.

Another question:
What's the difference by disabling kext signing by terminal command OR by disable it within TrimEnabler ? I guess there's no difference - correct ?