Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

TRIM Support Enabler

Hi, I used the TRIM enabler, erased the free disk space and applied the commands but the boot time is still much higher then before. It's stuck at the grey screen just before the apple appears for pretty long. Everything else works fine. Application start fast. Xbench scores my disk at 318.09. I did the erasing part again and rerun the terminal commands. (I didn't reapplied the hack).
Any suggestions?

late 2008 Unibody Macbook, Mac OS X 10.6.7, Intel 320 160GB SSD
 
gregor.hoch said:
Hi, I used the TRIM enabler, erased the free disk space and applied the commands but the boot time is still much higher then before. It's stuck at the grey screen just before the apple appears for pretty long. Everything else works fine. Application start fast. Xbench scores my disk at 318.09. I did the erasing part again and rerun the terminal commands. (I didn't reapplied the hack).
Any suggestions?

late 2008 Unibody Macbook, Mac OS X 10.6.7, Intel 320 160GB SSD
Click to expand...

When we are talking about boot times here, we are talking about the load circle. Before the Apple appears, you are not loading anything.
 
The ssd is selected as the startup disk. When I restart the dvd makes a 'dwwwdww' sound as if it is checking for a cd. I realized that a friends computer is not doing that.
Right before I enabled TRIM and cleaned the free space, the boot time was much faster.

Thanks!
 
gregor.hoch said:
The ssd is selected as the startup disk. When I restart the dvd makes a 'dwwwdww' sound as if it is checking for a cd. I realized that a friends computer is not doing that.
Right before I enabled TRIM and cleaned the free space, the boot time was much faster.

Thanks!
Click to expand...

dvd disc is always read at boot if there is a disk inside. this will increase time before apple appears.
 
Thanks Cindori. I'm a few days late on responding, but I didn't catch that 'restore' button on reversing the TRIM hack. You're the best.
 
m4rk0 said:
...
the strange thing is that booting time varies from 5 to 10 seconds (after the spinning disc) without any particular reason :confused: the latter is much more likely to happen anyway.
Click to expand...
woohoo performances are stable now, and by stable I mean "FAST".
thanks cindori for helping and, more in general, for this very useful thread. have a great weekend! :cool:
 
Installed on 10.6.7 and Failed hard.

I have the No symbol on reboot. When I try to run in single user/verbose mode, I get "still waiting on root device"

Intel 160gb SSD

Help:(
 
mrscholar said:
I have the No symbol on reboot. When I try to run in single user/verbose mode, I get "still waiting on root device"

Intel 160gb SSD

Help:(
Click to expand...

boot from dvd and repair permissions

still problems, boot from other disk, take kext from Trim Enabler.app/Contents/Resources, put on your install, boot from dvd, repair permissions, try boot

you're the first one of 50 000+ to report this, sure u didnt do something wrong?
 
I posted a thread in Lion about this and didn't realize it was already discussed here (thanks Hellhammer for directing me here, you've been a great help recently).

FWIW, I [reluctantly] installed 1.1 on 10.7 DP2e. I read 1.1 allows you to backup to revert if there are issues. I have Snow Leopard installed on another SATA bay and "Time Machine" so my bases are covered but be careful if anyone else isn't covered in case of issues.

So far so good. At first there were slight issues, but reading comments on other sites people were able to fix them with permissions repair in third party apps (like MacPilot), resetting PRAM and SMC. Did the same and BAM, lighting fast after running comparison tests on my OCZ 120GB Vertex 2 SSD.

Hope Lion adds support for Sandforce SSDs.
 
Cindori said:
boot from dvd and repair permissions

still problems, boot from other disk, take kext from Trim Enabler.app/Contents/Resources, put on your install, boot from dvd, repair permissions, try boot

you're the first one of 50 000+ to report this, sure u didnt do something wrong?
Click to expand...

Only what was in the directions. I have my ssd in 2 partitions w/ 10.6.7 on one and 10.7 on the other. Would that make a difference? (I installed onto the 10.6.7)

UPDATE:

Reinstalled unmodified kext file, repaired permissions and still the same problem. Any other suggestions (sort of a full reinstall?)
 
Last edited:
try download 10.6.7 combo update, extract kext with pacifist, and install that one
 
..........................................................
 
Last edited:
RS2 said:
There will definitely be problem with the file system if you just block-level clone your HDD to SSD with Disk Utility or Carbon Copy Cloner. You should format and partition the SSD with Disk Utility and disable Erase Destination when you restore from the HDD to the SSD. This way you will do file copy to the SSD instead of block-level copy and avoid potential file system problems. One example is the adaptive hot-file clustering that's not used for SSD. If you perform a block-level copy you will have hot-files within the metadata zone and the catalog and allocation files will not be correct.
Click to expand...

So how would you correct this file allocation problem if you already did the block level copy and and can't redo it?
 
Weird thing happened. I used Cleanmymac to clean my cache just recently and upon restarting the machine, the boot time was nearly a minute. Some apps were also sluggish to load :/

So I reverted back to the backup kext and it is fine now
 
jhero said:
Weird thing happened. I used Cleanmymac to clean my cache just recently and upon restarting the machine, the boot time was nearly a minute. Some apps were also sluggish to load :/

So I reverted back to the backup kext and it is fine now
Click to expand...

Have You tried using Onyx? Verify and repair permissions, it may help.
 
TRIMEnabler has worked for me on my MacBook Air 11" (64GB) and on my i5Hack with a 120GB OCZ Vertex 2 (firmware version 1.23). :)
 
Cindori said:
Let me explain, it's like this:


In the 10.6.7 build on Macbook Pro 2011, there are new versions of drivers that are not on 10.6.7 for other Macs. This is usual, that new shipping Macs have newer drivers.

In the 10.6.7 for Macbook Pro 2011, there is driver for TRIM support.

The driver, however, only has support for APPLE SSD.

When 10.6.8 comes, it will bring this new driver to all Macs.

Still, it will most likely be only APPLE SSD support.

Even in the Lion beta, this driver is only for APPLE SSD.


If you have a Apple SSD, this patch won't be needed once 10.6.8 is released. You will have TRIM from start.

But unless Apple makes any changes, everyone on Intel, Crucial, OCZ, Corsair, etc, SSD drives, will not have TRIM from the start in either 10.6.8 or Lion.

That's the point of the patch. It not only gives you TRIM support one patch before Apple releases it, it could possibly be the only way to get TRIM support throughout SL and even in Lion.... Unless Apple makes any changes.
Click to expand...

I have a 2009 Mac Pro running 10.6.7. Does the TRIM Support Enabler 1.1 tool will copy the updated Ktext drivers (from the MacBook Pro 2011 10.6.7) to my 10.6.7 OS and also will update the configuration files to enable TRIM support on NON-Apple SSDs ?, please could you clarify, thanks a lot
 
I just purchased a OWC Mercury Extreme 6G SSD. Supposedly the SandForce controllers should be good enough to take care of the garbage. But I would love a second opinion. Would anybody suggest enabling trim on newer drives, like the OWC 6G or Vertex 3, and why? And if I did enable it would it hurt anything? Can the process be undone? And if so how?
 
Last edited:
Cindori said:
yes.
Click to expand...

Thank you, do I have to have the SSD installed in the system while runnung the TRIM Support Enabler ?, I just purchased the SSDs today and I will get them by Friday, and I already installed TRIM Support Enabler today on the Mac Pro. Maybe I will have to run the Enabler again after I have the new SSD installed ?, please could you clarify, thanks
 
ended up having to turn the enabler off on my vertex 3. The vertex 2 seemed ok, but after switching to the vertex 3-240, opening files in photoshop and saving etc was like beach ball city even though the files were stored on a normal separate drive. Back to normal though after the reversal. The Mac implementation of trim must not get along with "garbage collection" or something.
 
brosenz said:
Thank you, do I have to have the SSD installed in the system while runnung the TRIM Support Enabler ?, I just purchased the SSDs today and I will get them by Friday, and I already installed TRIM Support Enabler today on the Mac Pro. Maybe I will have to run the Enabler again after I have the new SSD installed ?, please could you clarify, thanks
Click to expand...

TRIM enabler just installs a driver, when it's done, it's done. you dont need a SSD to use it, or when installing. it's just a support. once it's there, it's there. until you remove it.

the application itself does not interact with your SSD at all.
 
under sys info, it shows that TRIM is on, but i was never able to do the "erase free space" as this wasn't available as an option? (button was greyed out on disk utilities)
i have an 10" MBA late 10' model. running 10.7

so while it says it's on, is it actually working? given i wasn't able to do the erase free space command?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back