MOTUnation.com

I recently found some Terminal Commands for reassigning BlueTooth from the built-in hardware to an external dongle via the Handoff feature in Yosemite (does not apply to older OS).

I don't recall the sequence but it makes a call to the NV RAM. If you see any line in Terminal that mentions NV RAM, stop, get out of Terminal before you run the command, turn Trim Enabler to Off and reboot (you must reboot after turning it on or off). Now you can run a command that makes a call to the NV RAM.

Afterwards, turn Trim Enabler.app back on and reboot again.

If you accidentally reset the NV RAM and upon reboot, get the circle with the slash, the same instructions posted earlier for restoring your system apply.

Reaffirming that I don’t really need any SSD’s. Every time I question that I’ll come back and read this thread.

bongo_x wrote:Reaffirming that I don’t really need any SSD’s. Every time I question that I’ll come back and read this thread.

Nonsense.

This thread would not exist except that Apple decided to block TRIM on non-Apple SSDs. If you read carefully, you will see that there are no problems; only things you have to remember when using one. All center around not resetting the NV RAM without turning Trim Enabler.app off and rebooting first.

None of this applies to Macs that come OE with SSDs.

I make my living on my iMac and using an SSD saves me 1-2 hours a day, easily. Just for kicks, I worked off my HD last Friday just to see if it was as slow as I remembered. It was worse.

What Mike said. Reminds me of the old Life cereal commercial… "Mikey likes it!"

Or this one: "Try it, you'll like it!"

Walk on through the night...

When I upgraded to 10.10.2 I forgot to turn off Trim Enabler and got the stop sign. Luckily I already had the commands printed out, and again on my iOS devices in the Reading List in Safari.

I had to boot into Recovery Mode, then opened the Terminal, entered the commands and the OS rebooted fine. The commands are straight forward in what they do. But the trim concern should be over if using 10.10.4.

Btw, the command for printing out non-Apple KEXTs is "kextstat -l | grep -v com.apple". If you've had kext signing turned off it might be a good idea to run that command and see what's installed. Usually it's only a few at most.

I think both mikehalloran and Michael Canavan had good points about the use of trim. On sample drives where libraries are set and nothing is added, they're not full, and it's basically just being read from, trim isn't an emergency. Btw, those Samsung XP941s on PCIe cards in 2009-2012 MacPros are fantasic.

If you have to run the commands to boot into OSX and encounter a stop sign, here's a brief explanation of what is happening.

1) "nvram boot-args=kext-dev-mode=1"

disables kext signing (which is what caused the stop sign in the fist place)

2) "touch System/Library/Extensions"

causes the system to update timestamps on all necessary kextcaches

3) "kextcache -u "/Volumes/Your Disk name"

rebuilds kextcache with kext signing off for a re-boot that in effect brings you back to where you were before it all started.

The second version replaces a file and changes permissions.

One more thing, maybe it would be cool to start a security thread at some point if there isn't one. If you travel with a MacBook (especially though airports) there are somethings that in 2015 you should be doing. If it's a desktop in a secure environment, and you don't download untrusted apps, you should be good. But if your desktop Mac is connected to the internet it might be a good idea to monitor incoming and outgoing traffic. A good app for that is Little Snitch.

Learning some basic Terminal commands is a good idea too.

Anyway, I didn't want to go too off topic, but after the 10.10.4 fixes, which dealt with Kect signing which is of course a security feature from Apple, we're going to be seeing more of these types of additions from Apple. Security is going to be increasingly crucial for many of us.

Steve

As everyone probably knows by now, the Terminal Command, sudo trimforce enable in OS 10.10.4 when booted into an SSD makes Trim Enabler.app redundant, at least the free version. You will find Uninstall under Settings.

There are those who like to Trim SSDs by running Disk Utility from a mechanical HD. This can only be done with Trim Enabler.app installed on the HD and turned On on the HD.

sudo trimforce enable is an invalid command when booted into a HD.

Again, if booting from an SSD, the above command line makes Trim Enabler.app redundant unless you like the other tools in the paid version.

If using the paid version, turn the app Off under Trim and turn Notify when Trim is Disabled to Off under Settings. The other tools will still function correctly.

bongo_x wrote:Reaffirming that I don’t really need any SSD’s. Every time I question that I’ll come back and read this thread.

That's funny. Since the OS are now built on the presumption you are using one, staying away from them will only serve to inhibit system performance.

EMRR wrote:

bongo_x wrote:Reaffirming that I don’t really need any SSD’s. Every time I question that I’ll come back and read this thread.

That's funny. Since the OS are now built on the presumption you are using one, staying away from them will only serve to inhibit system performance.

Ain't that the truth!

When testing Trim Enabler with my internal HD last night, performance was so slow that I had to leave the room while certain things were running – even reboots. I had to keep reminding myself that this used to be normal and was still faster than my old G4 and G5.

Mike, please forgive me if you've covered this earlier but you have a loyof info in this thread and I've gotten confused.

I heard thatApple enabled trim natively in Yosemite 10.10.4, but I'm not clear as to whether that is literally true, orwhether they've just modified the kext issue so you can now use trim enabler without worrying about disabling the security safeguards. Can you simplify this for me?

(This is for a 1TB Crucial M500 in a 2012 9,1 MacBook Pro with a new clean install of 10.10.4.)

Thanks!

Download and install Trim Enabler and use it to enable trim. Under Yosemite 10.3 or .4 , there are no potential issues.

https://www.cindori.org/software/trimenabler/

Trim Enabler works but I do not recommended it for OS 10.10.4....

Run the Terminal command instead per my post five up.

... If you are manually running TRIM on other drives, you need Trim Enabler installed on the boot drive (it can be a spinner, BTW). You Trim by running Repair Disk from Disk Utility from the Boot drive. Weird but it won't trim remote drives with the app installed. This only works over SATA, eSATA and PCIe.

mikehalloran wrote:Trim Enabler works but is not recommended for OS 10.10.4.

Run the Terminal command instead.

Why Mike?

Cindori has updated Trim Enabler to take advantage of the access Apple now allows to the pertinent part of the OS without disabling kext signing. No more workarounds or security issues. For users unfamiliar with Terminal, it would seem there is no reason to discourage use of Cindori's free app.

https://www.cindori.org/safely-enable-t ... l-capitan/

I will see if there's an update before I answer. Let's just say that I was surprised and disappointed by the last version. If the issue still exists, I'll post and, if gone, no need to elaborate. I'm wrapping up a performance as I send this and won't be near my Mac till this evening.

Looks like Trim Enabler is being phased out in favor of a new Cindori app called Disk Sensei. It's a $10 upgrade from Trim Enabler. I might check this out.

mikehalloran wrote:Trim Enabler works but I do not recommended it for OS 10.10.4....

Run the Terminal command instead per my post five up.

... If you are manually running TRIM on other drives, you need Trim Enabler installed on the boot drive (it can be a spinner, BTW). You Trim by running Repair Disk from Disk Utility from the Boot drive. Weird but it won't trim remote drives with the app installed. This only works over SATA, eSATA and PCIe.

Thanks Mike. Works a treat.