Slashdot Mirror

TRIM will only work in Apple branded SSD drives. The "hack" clears out a portion of the driver in OSX to treat all attached drives as TRIM enabled if the feature exists; and it does with Intel, Samsung, OCZ drives etc. In addition, Apple will not allow 3rd party SATA drivers. This means Samsung and Intel can't release apps to manually TRIM a drive.

With regards to Yosemite, read about it here https://www.cindori.org/trim-e...

You'll have to try harder than that for an example, because that's already been defeated very handily.

Oh, and these guys will happily sell you shiny new SSD's with native OSX TRIM support.

(...besides, even without TRIM support there's no real difference for the average user in longevity or performance on an SSD. I've gone without it the whole time I've had mine; by the time the SSD wears out, I'll just go out and buy one twice the size - probably for the same price I paid for the 512GB Crucial SSD that I have shoved into my MBP right now.)

This is truly a "We're not done until 3rd party stuff doesn't work" situation that everyone always suggested MS had (and MS probably did have to some extent).

Yeah, them turning on a policy that says all kernel-mode drivers need to be signed was clearly a response to one guy writing a binary patch hack to add TRIM support to 3rd party SSDs using Apple's AHCI kext.

That's truly what this is - an unintended consequence of making things more secure and accidentally breaking a completely unsupported modification of the operating system. Would I like to see TRIM enabled on 3rd party drives? Absolutely, as I have two of them in my Mac Pro. But let's not fly off the axle attributing this massively over-scoped change to the incredibly small minority of people that not only put in a 3rd party SSD, but enabled TRIM via this guy's binary patch of Apple's driver.

This is unintended, or at the very worst, a happy coincidence for Apple. Consider the bullet-point version of this scenario:

- Apple's AHCI driver doesn't enable TRIM on non-Apple SSDs. Apple made a decision way back at the beginning of SSD support to not enable TRIM because of buggy firmware on early SSDs. They decided to eat a performance hit rather than have a crap drive eat user data. They likely have never revisited the issue, because those drives are still out there.

- 3rd party SSD manufacturers don't bother supplying OS X drivers that enable TRIM, favoring their customers to use a commonly available hack instead.

- commonly available hack modifies Apple's AHCI driver to do it's thing.

- Apple enabled driver signing in the latest OS to increase kernel-mode security. Something that everyone should be happy about.

- commonly available hack can no longer modify Apple's AHCI driver, because the signing would no longer be valid.

- 3rd party SSD manufacturers still don't bother supplying an OS X driver that enables TRIM.

- Apple gets hammered on Slashdot because they increased the security of ALL kexts, because one out of the over 200 kexts installed with Yosemite was being hacked by a 3rd party software to enable a feature on a 3rd party device. Shame on them!

The funny bit, is that you can turn off the driver signing requirement and hack the AHCI kext anyway, but OMG EVIL APPLE DOES EVIL!!! handwaving will drown that out.

No, you couldn't, since they are Apple's drivers not yours. Apple's driver takes over handling of external drives, but it refuses to TRIM them. Previously, people worked around that by patching the driver, but signing prevents that.

Yes, you can. People are already making kext-modification scripts and other tools that get around the signing.

This is pretty much a non-issue.

Turn off the driver signing requirement in Yosemite, problem solved, your hack still works and you're in the same condition you were in Mavericks.

Right up until you install a minor release update (service pack); which no doubt will have turned driver signing back on rendering your machine un-bootable upon next restart. This assuming it doesn't also replace the hacked driver simultaneously. Same thing happened with all other version of OS X updates, you had to re-apply the hack command from a terminal session. But unlike Yosemite, prior version of OS X booted just fine with TRIM disabled again.

Fortunately you can get get the machine booting again with Yosemite, but takes some hoops of fire to go through first. I'm not sure if this will work if the drive is encrypted with File Vault however. I honestly haven't checked. Read link below on how-to recover from a boot stop sign.

http://www.cindori.org/trim-en...

Yep. And you can find a whole lot more about how to do what you are suggesting by someone who really knows about the issue and makes a TRIM enabling tool here.

Apple, for whatever dumb reason, has _never_ enabled Trim on non-Apple branded SSDs. I do not know of any HDD manufacturers that ever provided any kernel extensions that would enable Trim for their drives, so effectively, third-party SSDs have never had any official trim support on OS X.

Before Yosemite this has never been an issue. Any user who was able to install their own SSD could also download the handy TRIM Enabler software that forced Trim on for non-Apple SSDs. One toggle switch, one reboot, piece of cake. I've been running multiple Macs since OS 10.6 with multiple brands of SSDs (OCZ, Samsung, Intel, etc) with absolutely no issues and no signs of performance degradation.

The difference in Yosemite is, as the summary says, non-signed Kernel extensions cannot be loaded by default. Since non-signed kexts are blocked, software like Trim Enabler cannot load. You CAN override this behavior, but there are potential issues (see the Trim Enabler site for more information).

There is absolutely no reason to believe that the decision to make Yosemite require signed kexts has anything to do with the status of trim on non-Apple SSDs. I doubt trim even crossed anybody's minds during the decision-making process. Trim Enabler is just an unfortunate casualty of kext signing (which itself is probably not a bad thing!).

tl;dr -- a rather hysterical take on an issue that DOES display some Apple stupidity. Just let us enable trim on non-Apple drives natively and there's no problem!

Apple, for whatever dumb reason, has _never_ enabled Trim on non-Apple branded SSDs. I do not know of any HDD manufacturers that ever provided any kernel extensions that would enable Trim for their drives, so effectively, third-party SSDs have never had any official trim support on OS X.

Before Yosemite this has never been an issue. Any user who was able to install their own SSD could also download the handy TRIM Enabler software that forced Trim on for non-Apple SSDs. One toggle switch, one reboot, piece of cake. I've been running multiple Macs since OS 10.6 with multiple brands of SSDs (OCZ, Samsung, Intel, etc) with absolutely no issues and no signs of performance degradation.

The difference in Yosemite is, as the summary says, non-signed Kernel extensions cannot be loaded by default. Since non-signed kexts are blocked, software like Trim Enabler cannot load. You CAN override this behavior, but there are potential issues (see the Trim Enabler site for more information).

There is absolutely no reason to believe that the decision to make Yosemite require signed kexts has anything to do with the status of trim on non-Apple SSDs. I doubt trim even crossed anybody's minds during the decision-making process. Trim Enabler is just an unfortunate casualty of kext signing (which itself is probably not a bad thing!).

tl;dr -- a rather hysterical take on an issue that DOES display some Apple stupidity. Just let us enable trim on non-Apple drives natively and there's no problem!

See http://blog.macsales.com/21641... for an example of a properly designed SSD.

kext signing is a GoodThing for security. Making the system less secure so that lazy implementors are protected isn't a good trade off.

Apple *should* have provided a better upgrade experience so that users wouldn't be surprised, or end up with unbootable systems. Users that don't want to have kext protection CAN turn it off see http://www.cindori.org/trim-en...

To me this is akin to Apple's desupport of WPS ages ago. It took everyone else a while to figure out that WPS was a major security hole (indeed, its still there for most consumers).

Apple has never enabled TRIM on non-OEM SSDs, which is probably the conservative and correct thing to do. If you're clever enough to install a new SSD, you're clever enough to enable it on your own (and presumably to know whether you should enable it, and whether it's even a benefit for your particular drive).

The current workaround involved a single software vendor who didn't sign their kexts. Apple's new security policy won't let you load random unsigned kernel modules unless you explicitly turn off the signature checking. While this is inconvenient for me personally - because I have a 3rd-party SSD and I used that software myself - on whole, I'd rather have a more secure OS than the dubious benefit of a possibly slightly faster SSD.

It can be done if you're willing to disable kext security check

see http://www.cindori.org/trim-en...