New
#2161
Mike, I don't know how it works and I have a different Marvell, but I have the Marvell drivers installed, but it is still using msahci. I don't know exactly how that works, so perhaps a snip will be useful.
Mike, I don't know how it works and I have a different Marvell, but I have the Marvell drivers installed, but it is still using msahci. I don't know exactly how that works, so perhaps a snip will be useful.
If you had the MSAHCI driver installed before the Marvell driver you can rollback the driver, if you didn't delete the MSAHCI driver.
Before you do anything, I would like to see a screenshot of As SSD. Do not run the test, just select the SSD at the top and take a screenshot. But, to uninstall the Marvell driver, open device manager and expand IDE/ATA/AHCI drivers, at the bottom you will see the ahci drivers. If the Marvell driver is listed, right click it and select properties, click on the drivers tab, at the bottom you will see a button that says uninstall. click that buttin and click yes to all of the warnings. But first let us see the As SSD screenshot.
Last edited by essenbe; 20 Sep 2011 at 10:32.
I had the SSD first conected to the Marvell SATA3 port when installed the system from scratch, then i installed the Marvell driver, different driver versions up to the newest one i use now. I have also tried the IRST driver but when it didnt work uninstalled it.
Do i then still have the MSAHCI installed?
How do i do i rollback of the driver or if i need, a delete of the marvell driver?
When you go into Device Manager there may be an option to uninstall and delete.
As you can see on mine there is no Delete. Probably not on yours either.
Also you can delete the unzipped driver file from downloads.
Look at the circled yellow on right of my Snip.
Can not reinstall if not on system.
Can not install from the zip folder so you can leave it if you want.
This is only IF not a certainty.
I have had other hardware reinstall the old drivers until I deleted them then the new driver installed.
Can be very confusing the first time it happens to you.
Uninstalling should be all that is necessary but.. just in case.
OKey, then i will FIRST do a screenshot of AS SSD and post it here for you guys so nothing gets wrong.
Thanks for the instructions above, i asked how to do this in my earlier message
EDIT: Hopalong X - thanks for the nice pictures :-P
As with most discussions, they tend to stray off the course of the original question. Just so I'm on the right page, I understood the original "misdirection" to be a discussion on whether the 9128 Marvell CONTROLLER would support the Windows TRIM command. According to Marvell, it does. And this I take on faith. As I do with Intel's specifications on their controllers. Now the discussion has moved to whether the Marvell DRIVER will pass the Windows TRIM command. According to Marvell, the latest driver will pass the TRIM command. BUT, the same exclusion exists with Marvell and Intel CONTROLLERS that the TRIM command is NOT passed to drives that are in a RAID array. And I can see where this can pose a confusing problem as many BIOS configurations don't allow specifying AHCI without specifying RAID. Even on a single drive where the user wants to implement AHCI, the only option is to select RAID as RAID includes (extension of) the AHCI implementation.
The links to other discussions posted earlier and many posted around the forums have detailed the Marvell controller TRIM problems both old and new. As I read the current discussions, they all are referring to drives that are in RAID arrays and THAT is a known deficiency with the Marvell and Intel controllers. I don't disagree.
And now, in response to a PM, I offer this publicly to one of the posters:
What was taken to be "rudely chastise" was not my intention at all. For not explaining what I was thinking and using a poor selection of words, I sincerely apologize. I can now see where my comment was a bit tart but I did not mean it to be rude. I read the references given and it was my understanding by reading the entire thread(s) that the discussion was about RAID drives. It was this that prompted the comment since OUR discussion (in my mind) was about a single drive. If I mis-read the discussions or mis-understood this discussion, then I am at fault and apologize for my gross ineptness.
In response to "proof", no one but the drive and controller chip set manufacturer can provide proof that the TRIM command is or is not acted upon. A drive may or may not act on the command right away. It could be within seconds or it could be hours. It depends on the idle state of the drive. As I stated, I accept the specifications of maker and according to Marvell, the 9128 and newer controller chip sets do pass the TRIM command for NON_RAID drives. And so far, I have not seen proof that they don't. However; as with any learning experience, I am willing to revise my opinion if someone can prove otherwise. But forum discussions are NOT proof. There's too many variables interjected and as I, opinion based.
And in the words of an anonymous writer:
"I thought I was wrong once, but I was mistaken." :)