Apple kills support for third-party SSD

[r0n]

Yosemite kills third-party SSD support
“Apple has, without warning, removed support for third-party SSDs in OS X 10.10 Yosemite, leaving anyone who uses one as a boot drive and has TRIM enabled with a Mac that won’t boot,” Adrian Kingsley-Hughes for ZDNet.

http://www.zdnet.com/yosemite-kills-third-party-ssd-support-7000035765/

 

[sweenish]

How angry are people really going to get?

More than they should, that's the answer.

It's Apple, if you don't play by their rules with their toys, how surprised are you going to be when they don't want to play with you?

 

[Ketchup]

How angry are people really going to get?

More than they should, that's the answer.

It's Apple, if you don't play by their rules with their toys, how surprised are you going to be when they don't want to play with you?

Yep. How dare people think they can tweak an Apple product.

 

[ControlD]

How big of an issue is this really? Don't most modern SSDs have built in garbage collection anyhow?

 

[Chiefcrowe]

Not surprised, they do whatever they want to. This is good to know though for anyone who is planning to upgrade, thanks.

 

[PricklyPete]

I buy apple products because I no longer have any interest in building/modifying my computer hardware. This doesn't bother me.

 

[nickbits]

I have Yosemite on my iMac and MBP, both of which have non-apple-installed SSDs. They work fine.

 

[Rakehellion]

I have Yosemite on my iMac and MBP, both of which have non-apple-installed SSDs. They work fine.

Me too. This article is garbage.

Sounds more like they disabled hacked drivers to enhance security and a particular TRIM tool no longer works.

 

[Mushkins]

Me too. This article is garbage.

Sounds more like they disabled hacked drivers to enhance security and a particular TRIM tool no longer works.

Yep, the article is sensational clickbait.

This is exactly the same thing as Windows Driver Signing requirements, where if it's not signed, you need to jump through a dozen hoops to install it anyway and it still might not work right. Honestly i'm surprised Apple hasn't been doing this already.

 

[Rakehellion]

You can use 3rd party SSDs with TRIM if you disable KEXT signing.

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

Also, things like SATA are hardware-based and have nothing to do with your operating system version, so it can't prevent you from booting.

The article is false. I'm not sure what message they're attempting to convey.

 

[Rakehellion]

Apparently it's an issue with hacked drivers.

You can disable KEXT signing, or use a drive with hardware TRIM, or don't use TRIM. If you have a hacked driver and KEXT signing is enabled, you won't boot.

 

[ControlD]

You can use 3rd party SSDs with TRIM if you disable KEXT signing.

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

Also, things like SATA are hardware-based and have nothing to do with your operating system version, so it can't prevent you from booting.

The article is false. I'm not sure what message they're attempting to convey.

The article itself mentions that you can get around the problem by disabling Kext signing, so perhaps calling it false is premature. Disabling Kext signing however is a global setting and not the smartest thing to do.

The problem is that many people are using a third-party TRIM enabling program with their non-Apple provided SSDs. This tool is not signed and thus creates problems if you leave it enabled and then upgrade to Yosemite. The problem is real and at least one user here has discussed it in another thread.

 

[ControlD]

If Apple would simply bake OS-wide SSD TRIM into "the most advanced operating system in the world" this would be a non-issue.

 

[Zaap]

What are the downsides of disabling kext-signing? Sounds on the surface like something I wouldn't much care about anyway (unnecessary level of security) unless there's some performance or instability downside?

 

[ControlD]

What are the downsides of disabling kext-signing? Sounds on the surface like something I wouldn't much care about anyway (unnecessary level of security) unless there's some performance or instability downside?

My limited understanding is that the setting to disable kext signing is stored in PRAM. If you go ahead and disable kext signing and for whatever reason reset your PRAM and have unsigned kexts installed you will be presented with an unbootable system.

 

[ControlD]

This explains it better than I can.

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

 

[Zaap]

Thanks. Interesting. Since I primarily run Hackintoshes, I'm guessing turning off kext-signing is a non-issue since there's no PRAM. And of course my legit Macbooks have Apple SSDs.

 

[Michael 7X]

Really? Are you sure? I have 4 Mac minis (late 2012) with 256gb ssd's in with 10.10, using trim enabler and they run just fine. I wonder how much research they did before writing this.

 

[ControlD]

Really? Are you sure? I have 4 Mac minis (late 2012) with 256gb ssd's in with 10.10, using trim enabler and they run just fine. I wonder how much research they did before writing this.

The information in the article comes directly from the authors of Trim Enabler ...

I haven't tried upgrading my MBP to Yosemite (it has a third party SSD in it). I don't feel any compelling reason to upgrade however, so I'll probably just skip it.

If you read the information on the Trim Enabler website it states the following:

Trim Enabler 3.3 will disable the kext-signing setting automatically for you, by giving a choice when you flip the switch.

By clicking Proceed, your computer will reboot with kext-signing disabled. You can then flip the switch again to enable Trim.

When you flip the switch back to Off, Trim Enabler will ask you if you want to restore the kext-signing setting back to normal.

It looks like when you install the program it disables kext signing which explains why your mini's are working. As long as you don't reset your PRAM everything should be fine I am guessing.