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.
TRIM Support Enabler
- Thread starter Cindori
- Start date
- Sort by reaction score
Does this enabler work on a 2010 MBP (core i7) without any manual steps? or do I have to download the kext file myself?
also, I have two intel G2s 160GB, which were shipped with an HP laptop so the model number shows INTEL SSDSA1M160G2HP (Notice "HP" at the end). I am wondering if this will be a problem for enabler.
also, I have two intel G2s 160GB, which were shipped with an HP laptop so the model number shows INTEL SSDSA1M160G2HP (Notice "HP" at the end). I am wondering if this will be a problem for enabler.
Then you are lucky since there are so many users with various problems. Generally it's a bad idea to install kernel extensions from an older system build especially for such critical functions as I/O operations.
Also if you try to restore the extension with TRIM Support Enabler 1.2 you still have to old IOAHCIBlockStorage 1.6.4 from Mac OS X 10.6.8 instead of the new 2.0.0 from Mac OS X 10.7.0 and 10.7.1.
You should not install TRIM Support Enabler 1.2 if you are running Lion! There are other ways to edit or patch the kernel extension to enable TRIM in Lion.
The author of TrimEnabler was about to create a binary patching version for 10.6.8 and 10.7. But so far no news.
I can whip up a trim patcher if he doesn't feel like updating the current one...
I can whip up a trim patcher if he doesn't feel like updating the current one...
Anyone knows if TRIM truly works if the SSDs are in RAID 0 (Stripped). I patched my system and system profiler shows that TRIM is enabled for each SSD in the array but I am wondering if it's really working.
EDIT: this is referring to os x soft raid in a macbook pro
EDIT: this is referring to os x soft raid in a macbook pro
Last edited:
Did you use TRIM Support Enabler or any other procedure to patch? Restart in Safe Mode (hold the Shift key) and check the fsck_hfs.log in /private/var/log via the Console. Can you see the text "Trimming unused blocks" in the log? Then it's working! This is also the preferred method to manually trim the SSD.
Code:
** /dev/rdisk0s2
** Root file system
Executing fsck_hfs (version diskdev_cmds-540.1~34).
** Checking Journaled HFS Plus volume.
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attributes file.
** Checking volume bitmap.
** Checking volume information.
[B]** Trimming unused blocks.[/B]
** The volume appears to be OK.
Last edited:
It's coming along, don't worry. Still the exact same kext in 10.7.1 so no need to rush, I will add some extra features
It's coming along, don't worry. Still the exact same kext in 10.7.1 so no need to rush, I will add some extra features
Great work Cindori! Excellent app.
I guess it is working...
Code:
/dev/rdisk2: fsck_hfs run at Sat Aug 20 09:34:03 2011
** /dev/rdisk2
** Root file system
Executing fsck_hfs (version diskdev_cmds-540.1~34).
** Checking Journaled HFS Plus volume.
The volume name is Intel RAID
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attributes file.
** Checking volume bitmap.
** Checking volume information.
** Trimming unused blocks.
** The volume Intel RAID appears to be OK.do you want to help development of trim enabler?
it takes 20 seconds
open terminal
type:
system_profiler -xml SPSerialATADataType
press enter
bunch of text will appear, copy all of it and send PM to me.
thanks
(ps u need ssd)
it takes 20 seconds
open terminal
type:
system_profiler -xml SPSerialATADataType
press enter
bunch of text will appear, copy all of it and send PM to me.
thanks
(ps u need ssd)
Why are you so ignorant about this? You know there is a new IOAHCIBlockStorage kext in Lion so stop the misinformation! Don't you think Lion users should be warned that an old version is installed with your app?
in lion, the build version is higher, yes
but the version number is the same, so in OS updates it doesnt even replace the kext. that is a reason to think of it as safe.
i'm not ignorant, I can either
a. pull off Trim Enabler until new version is finished, this is just stupid as long as it works without problems
b. release a trim enabler with newer kext, this will just cause confusion, "should I redo the patch with the new kext" etc etc, and I don't know how it will react in snow leopard
c. monitor reactions from 10.7.1 users and give advice based on that information, while I continue to develop the new version
that aside, Trim Enabler is dead. I will not release a new Trim Enabler.
I'm going to release the best free SSD utility that have ever existed for OSX. And it will enable Trim safely.
i just need some time.
Last edited:
Sorry but you are wrong! The IOAHCIBlockStorage kext in 10.7.0 Lion is not the same as in 10.6.8 Snow Leopard.
The IOAHCIFamily kext have the same version in 10.6.8 and 10.7.0 but the included IOAHCIBlockStorage kext is not the same.
The IOAHCIBlockStorage kext has different version (1.6.4 in 10.6.8 and 2.0.0 in 10.7.0), date and size if you compare them.
You can also compare the binary files via the cmp -l terminal command or analyze the binary files in the different kext versions.
Please see the enclosed pics where you replace the APPLE SSD text in the binary file. Still not convinced?
Code:
-rw-r--r-- 1 root wheel 360092 8 Jun 01:48 ~/Desktop/10.6.8/IOAHCIBlockStorage
-rw-r--r-- 1 root wheel 353224 18 Jun 22:11 ~/Desktop/10.7.0/IOAHCIBlockStorageAttachments
I was talking about IOAHCIFamily. I know how to compare binary files and I didn't claim they are identical, although I have done so in the past, but purely based on reports from users (didnt update to lion until recently). The sum of the matter still is, patch works, I wouldn't have released it / continue to encourage usage if I hadn't tested it first. If you still don't think it's safe, hey, just don't use it, wait for new app.
and I didn't claim they are identical, although I have done so in the past, but purely based on reports from users (didnt update to lion until recently). The sum of the matter still is, patch works, I wouldn't have released it / continue to encourage usage if I hadn't tested it first. If you still don't think it's safe, hey, just don't use it, wait for new app.
Last edited:
Yes you did claim the kexts are identical. How can you have tested the patch if you didn't update to Lion until recently? You are causing so much trouble for Apple, all SSD manufacturer and Lion users all over the world. At least put a disclaimer on your site that current version only is for Snow Leopard. The fact is that your app installs an old kext which is not tested with Lion! Period. I have never used your app and never will. There are other procedures to enable trim if you have to. Lion users should be aware of all this to avoid potential problems.
Last edited by a moderator:
please read my post again.
In the TRIM Enabler, it clearly says: "For OSX 10.6.8".
However, I got about 20+ reports of people using it without problems in Lion beta. They were well aware that they were doing it on their own risk.
When Lion released, I did not say anything about using Trim Enabler in Lion. Still people went ahead and used it, on their own risk, against my instructions. And I got tons of reports saying... it worked. So I said "hey looks like the kext is unchanged since people are reporting it to work fine". Ok, so the kext is not unchanged, it does not change the fact that it works.
Like I would care about causing trouble for Apple. I developed a tool to flash PC cards to work in Mac Pro, so people can avoid paying Apple twice as much. I'm working for the users, not Apple.
How are SSD manufacturers and Lion users not benefiting from this?
People patch, if it doesnt work well, they can restore. Nothing lost, nothing damaged.
But the kext is tested with Lion! and the app has that disclaimer.
Using an slightly older kext is not the end of the world. You just have to make sure it works fine. If people report to me that it works fine in Lion that is what I will say on my blog, thank you.
Then why are you here?
This conversation is really irrelevant considering the new version is like, a week away. Not really sure what you're trying to prove. I think we can agree that using old kexts pose a risk, but in this case I did not release or claim any software to work without proper testing.
Last edited by a moderator:
I just downloaded this utility and it worked great! But for the life of me I can't seem to select the "erase free space" button from the erase tab. It is grayed out. Halp?
Is this app still useful if I can't erase the free space? :s
Also once I perform the "patch" it's always running in the background and such? Is it a "program" in the sense that it takes resources to do what it does?
Is this app still useful if I can't erase the free space? :s
Also once I perform the "patch" it's always running in the background and such? Is it a "program" in the sense that it takes resources to do what it does?
Last edited:
It's greyed out in Lion if you try and use it on the disk you are booted from.
When trim is activated, it will start working in the background. But not trough a process or applicaiton, just through native mac trim driver.
I suppose this has been asked 100x, but if it's native, why don't they just enable it by default? :S
Also, out of curiosity, does it slow down the computer when it's working? Thanks for the sweet-ass program!