Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yosemite and TRIM
- Thread starter Mr. Retrofire
- Start date
- Sort by reaction score
I don't have the issue.
On hackintosh people use a boot sting to avoid this so I was just trying to clarify the issue.
It had worked after reboots (maybe 3 times or so) but suddenly, a few days later, at a cold boot I got the no-go sign again..
Might be something different, but the symptoms were the same as the TRIM issue.
It had worked after reboots (maybe 3 times or so) but suddenly, a few days later, at a cold boot I got the no-go sign again..
Might be something different, but the symptoms were the same as the TRIM issue.
Now back at Mavericks, so next time I cold boot Yosemite I'll report back.
~ Cheers
Last edited:
It has worked for me, but after booting the Mac a few days later, the same "no-go" sign appeared.
Not sure if it is due to having trim support enabled or something else...
The problem described on the previous page and on my website is not a "bug" that "happens when trim is enabled", but simply a "block" against third party/modified kexts that Apple added for Developer Preview 1, probably for debugging reasons.
Once you use the boot argument to tell Yosemite to not use this block, Trim is enabled just fine. If something happens several days later, it's likely to be completely unrelated (Yosemite is EXTREMELY buggy).
It had worked after reboots (maybe 3 times or so) but suddenly, a few days later, at a cold boot I got the no-go sign again..
Might be something different, but the symptoms were the same as the TRIM issue.
Cold boot into Yosemite today, no problem with Trim Enabler at all.
~ Cheers
Pay for trim....pay for anything...your ssd must be an Apple certified much more priced as ordinary hardware to have trim enabled....otherwise it has no support...... Dear Apple even microsoft makes no difference whatever ssd U happen to have in PC.....Really it's a real shame !!!! Would U cancel even this message !?
Pay for trim....pay for anything...your ssd must be an Apple certified much more priced as ordinary hardware to have trim enabled....otherwise it has no support...... Dear Apple even microsoft makes no difference whatever ssd U happen to have in PC.....Really it's a real shame !!!! Would U cancel even this message !?
You have to have an Apple-branded SSD for the integrated TRIM support to work. If you're using a third-party SSD (i.e, replacing a HDD or older SSD in a machine), then trim Enabler is the only way to get TRIM working. As for the rest of your post, it doesn't even make sense when ran though Bing or Google Translate...
There is no such thing as a "Trim support issue". Please see post #30.
Trim Enabler works fine in DP2. Still needs the boot argument.
Thanks. I had reverted back to Mavericks since the DP1 version of 10.10 came out and last night I installed 10.10 then updated to DP2 and then enabled TRIM, following the instructions here: http://www.cindori.org/enabling-trim-on-os-x-yosemite/
Worked flawlessly. Thanks for your help.
Trim Enabler Fix or?
After updating to Yosemite DP2 to my separate SSD RAID0 on the Velocity DUO X2, I again executed the Cindori fix for Trim Enabler. Not sure if this is TE related or that the DP2 got a negative hold on my RAID0 (external in Disk Utlities) on the DUO X2?
I could of course reinstall DP1 and update to DP2 again, but I would like to share this mishap with you and perhaps fix it. Sorry for the bad iPhone photo screen shot
Anyone else having TE troubles?
~ Cheers
After updating to Yosemite DP2 to my separate SSD RAID0 on the Velocity DUO X2, I again executed the Cindori fix for Trim Enabler. Not sure if this is TE related or that the DP2 got a negative hold on my RAID0 (external in Disk Utlities) on the DUO X2?
I could of course reinstall DP1 and update to DP2 again, but I would like to share this mishap with you and perhaps fix it. Sorry for the bad iPhone photo screen shot
Anyone else having TE troubles?
~ Cheers
Attachments
I mean = TRIM FOR FREE not TRIM ONLY FOR APPLE'S SSD
Nothing else nothing more so simple so fast !? Is It the end of Apple to have trim for free !?
How about Yellownstone supervolcano and fukushima radiation in USA !?
Last edited:
I mean = TRIM FOR FREE not TRIM ONLY FOR APPLE'S SSD
Nothing else nothing more so simple so fast !? Is It the end of Apple to have trim for free !?
How about Yellownstone supervolcano and fukushima radiation in USA !?
What in the hell does Yellowstone and Fukushima have to do with TRIM support? I swear this site is getting crazier by the day. Apple has never supported TRIM natively for non-Apple SSDs, so there's no change there at all.
Resolved!
RESOLVED: Yosemite DP1 + DP2 is not in favor of my PCIe sata-3 SSD card! Installed on SSD in bay#1!
~ Cheers
RESOLVED: Yosemite DP1 + DP2 is not in favor of my PCIe sata-3 SSD card! Installed on SSD in bay#1!
~ Cheers
Why is using Trim Enabler necessary? In Mavericks you could modify the correct KEXT from the command line after every OS update. Has anyone proven that removing the "APPLE SSD" string from IOAHCIBlockStorage no longer works on Yosemite?
"APPLE SSD" is still there. The only new operation would be to run `sudo nvram boot-args="kext-dev-mode=1"`.
"APPLE SSD" is still there. The only new operation would be to run `sudo nvram boot-args="kext-dev-mode=1"`.
Last edited:
I think you can do one of the following:
1. Boot into the Recovery 10.10 OS. Boot your Mac, hold option, select the Recovery partition. Open terminal and try disabling kext check using the command listed earlier in this thread.
2. Boot into your other OS X partition, completely restore the kext that you modified. This is assuming you backed up your kext first.
I have TRIM working on DP3. I didn't use Trim Enabler as I don't see any need to use a program for something I fully understand and I've been using for years.
Go here for the manual approach:
https://digitaldj.net/blog/2011/11/17/trim-enabler-for-os-x-lion-mountain-lion-mavericks/
I had trouble with patching the file. This worked for me:
sudo perl -pi -e 's|(^\x00{1,20})[^\x00]{9}(\x00{1,20}\x54)|$1\x00\x00\x00\x00\x00\x00\x00\x00\x00$2|sg' /System/Library/Extensions/IOAHCIFamily.kext/Contents/PlugIns/IOAHCIBlockStorage.kext/Contents/MacOS/IOAHCIBlockStorage
Go here for the manual approach:
https://digitaldj.net/blog/2011/11/17/trim-enabler-for-os-x-lion-mountain-lion-mavericks/
I had trouble with patching the file. This worked for me:
sudo perl -pi -e 's|(^\x00{1,20})[^\x00]{9}(\x00{1,20}\x54)|$1\x00\x00\x00\x00\x00\x00\x00\x00\x00$2|sg' /System/Library/Extensions/IOAHCIFamily.kext/Contents/PlugIns/IOAHCIBlockStorage.kext/Contents/MacOS/IOAHCIBlockStorage
Thing is, with the new Mac Pro there isn't really a Mac model that encourages installation of third party SSDs anymore, so if Apple didn't bother while the old Mac Pro was being sold it's not surprising that they won't do it now.
Also, I don't see why people would even try running TRIM Enabler on a new OS? It works by patching a kernel extension, and with all the updates to SSDs it was highly likely that that extension would change, resulting in TRIM enabler breaking it, and that's if Yosemite doesn't introduce any security changes such as signed kernel extensions that are verified on startup.
I dunno, it's just the very last thing I'd want to do, that's for the original developer to worry about and create a new version of
As an aside though, how much benefit do people actually see when enabling TRIM for their third party SSDs? I've had several that actually performed worse with TRIM enabled, not necessarily the fault of the drive but possibly some oddity with OS X's handling of TRIM once (force) enabled. I've just found things to be more stable with it left off.