I'm aware. Windows doesn't even send queued in the first place. I think what I am talking about may be a different TRIM issue, perhaps affecting different controllers.
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.
MP2010 Lag
- Thread starter SDAVE
- Start date
- Sort by reaction score
I'm aware. Windows doesn't even send queued in the first place. I think what I am talking about may be a different TRIM issue, perhaps affecting different controllers.
Oh, and that thread you linked, I was part of it, and it's from it I draw a lot of the conclusions I made here. I don't see how it has anything to do with the point you were making, and it, as far as I can see from skimming it again, helps my point; That it's queued TRIM, and not TRIM itself that is the Culprit
I guess I misunderstood your point then, I agree with this statement.
In the post I quoted, you said that Linux ALSO black lists the SSDs in question. I took it that you meant WINDOWS by the use of the word also, and I was pointing out that Windows doesn't do that.
(Referring to post #23)
Sorry for the misunderstanding.
Last edited:
Oh that's quite understandable with the way I phrased that. I didn't mean also in the sense that others do it, but as in the explanatory way. You know, like "That's also because..." Anyway, by blacklist, I meant Linux has a list of drives which it uses sequential TRIM for instead of queued, and that that is the "blacklist". Understandable misunderstanding (does that count as an oxymoron?)
Cheers, mate!
So I restored back to a 10.10.3 backup from TimeMachine and it's all back to normal now.
Just for fun, I downloaded the 10.10.4 Combo Updated and updated again. The lags are back.
I just went back to 10.10.3. I think Apple stopped caring about the classic Mac Pro.
Just for fun, I downloaded the 10.10.4 Combo Updated and updated again. The lags are back.
I just went back to 10.10.3. I think Apple stopped caring about the classic Mac Pro.
I just don't see what could have changed between the two versions that would cause this. And if the OS can run on the MacBook with Core-M, there's no way they've coded it in such a way your machine's hardware isn't good enough anymore, unless there's some missing instructions or something, and the lag is caused by something like that. Could you report back with El Cap results some time?
I thought it was a TRIM issue and KEXT disabling issue, but I disabled both before upgrading to 10.10.4. Still no go.
I can't install El Cap beta because I keep getting a grey screen crash error.
Will do. I think a fresh install of 10.10.4 will work, but I can't at the moment, I think it's an install from way back to Snow Leopard and I kept upgrading.
Anyway I'm selling this machine and will install 10.10.4 for the buyer as a fresh install. I'm not sure I'll have it by the time El Cap final is out.