In his latest MacBook roundup, he has a whole page dedicated to the issue:
http://www.anandtech.com/mac/showdoc.aspx?i=3672&p=5
Here's a blurb:
http://www.anandtech.com/mac/showdoc.aspx?i=3672&p=5
Here's a blurb:
It, too, doesn't work in the unibody MacBook Pro. Once more, I know because I tried it in my own personal system. In fact, the only non-Apple supplied SSD I could get to work in the system without constant crashes was Intel's 80GB X25-M G2 (I didn't try the G1 or the 160GB G2).
I asked Apple what was going on and the only response I got was that the drives I was using weren't supported. These drives work perfectly in my testbeds and in other notebooks and my Nehalem Mac Pro, but not in my unibody 15-inch MacBook Pro.
I've been a staunch advocate of Apple's hardware and software for years now, but this is a dangerous precedent that Apple is setting. The point of standard specifications is so that end users can buy any component adhering to the spec knowing that it will work in any system implementing the spec. This isn't an OS X incompatibility, this isn't even an Apple incompatibility, this is a specific issue between certain SSDs and the 2009 unibody MacBook Pros. Instead of admitting to that and committing the resources to fixing it, Apple is making the mistake of stating that non-Apple hardware isn't supported. These are storage devices, the only things that you absolutely didn't have to have an Apple logo on in order to guarantee operation.
Note that this wouldn't even be an issue in the first place if Apple offered halfway-decent SSD options on its systems.
If it were an Indilinx problem, why not work with Indilinx to fix it? There's a definite incompatibility but I'm willing to bet it is related to whatever kept Apple from enabling 3Gbps on these machines from the start. Some have speculated that the custom SATA cable Apple runs from the motherboard to the drive bay is to blame. It's the only explanation given that these problems only happened in the 2nd generation unibody MacBook Pro systems.
It's unacceptable and I'm guessing the next version of the MacBook Pro will magically fix all of the problems.