can anyone confirm or deny that the Crucial m4 256 gb ssd works with ML?
im intending to buy the samsung 830, from what i hear, apple is using this vendor for their ssd, so i hope it works fine! :|
but my guess is that with mountain lion apple are trying to make it harder to install their new os with non-apple hardware.
So this thread is just a warning that if you intend to upgrade to mountain lion in a few days time, there is a good chance that if you are using non-apple ssds, you may experience some problems.
I can confirm that the Samsung 830 SSD works flawlessly on my late 2011 MBP and 2009 Core 2 Duo 13'' MBP, both running Mountain Lion. You will have enable TRIM manually using the TRIM Enabler app, which is free.
hi!
thanks, mine is due to arrive this week, as i went ahead and purchased it, the 256gb model, for £155 (it had been floating between £180-200 so im quite pleased) i also got the 16gb ram.
do you know where i can get the trim enabler app? im also quite confused about trim, some people here say its bad for OS X or un needed, and others like yourself suggest trim should be enabled :S
That's a good price. I too was watching intently as it hovered around £180, then one day, I got the 256GB on Amazon for £144, which isn't even the lowest I've seen it... £139!!!
Here's a link to TRIM enabler.
http://www.macupdate.com/app/mac/37852/trim-enabler/
Intel 320 160GB works like a charm with OS X 10.8 Mountain Lion!
Peace
Kernel file /mach_kernel does not contain requested arch: i386
I have a Crucial M4 (256) that is having the same problem. To anyone with a Crucial M4 that is working, did any of you upgrade from Lion or Snow Leopard? Also, did any of you have the trim enabler installed?
So this thread is just a warning that if you intend to upgrade to mountain lion in a few days time, there is a good chance that if you are using non-apple ssds, you may experience some problems.
That's a warning, not an error. I had the same thing but trim was enabled.
Did you actually check if trim is showing up as enabled now?
Instead of changing "APPLE" to zeros, I changed it to "INTEL".Yeah, checked after reboot and in system information says it isn't enabled. I checked the file that the terminal command changes and it has correctly changed "Apple" to zeros.
I'm a bit baffled as it was working fine in Lion but just won't now work in ML.
Anyone experienced similar?
Cheers,
Si
P.S. Also tried trim enabler but says "The patch is active but trim is not working"
----------
Could some nice person post a link to their correctly amended file:
/System/Library/Extensions/IOAHCIFamily.kext/Contents/PlugIns/IOAHCIBlockStorage.kext/Contents/MacOS/IOAHCIBlockStorage
so I can try a swap and see if mine's corrupted.
cheers guys and girls!
From the kextcache manual
“Installers and administrators should not use this program to update system kext caches. Instead they should run “touch” on the /System/Library/Extensions/ directory of the installation target volume after they have finished, which causes the system to update all necessary kext caches.”
Hence I think you could think about changing the guide to:
sudo touch /System/Library/Extensions/
Just an idea