Show us your SSD performance

[carwiz]

The Marvell 9128 DOES support TRIM, just not for a RAID array. That's true for the Intel controllers too. In a RAID array, you have to rely on the drives' self-cleaning properties. Some SSDs do, some don't. I know Crucial drives do. I'm not sure I would trust third-party software to perform the cleanup on arrays at this point either. SSDs are still "new" and If the software and hardware giants haven't fixed the issue of TRIM on RAID arrays, I sure wouldn't trust some free download to do it.

If you're going to Google facts, make sure they apply to the discussion.

 

[HugeRaven]

+1 Carwiz

Only the original Marvell did not support TRIM. It may now with proper driver.

All others do with the newer drivers.
At least since early 2010 dated drivers .

The Marvell 9128 DOES support TRIM, just not for a RAID array. That's true for the Intel controllers too. In a RAID array, you have to rely on the drives' self-cleaning properties. Some SSDs do, some don't. I know Crucial drives do. I'm not sure I would trust third-party software to perform the cleanup on arrays at this point either. SSDs are still "new" and If the software and hardware giants haven't fixed the issue of TRIM on RAID arrays, I sure wouldn't trust some free download to do it.

If you're going to Google facts, make sure they apply to the discussion.

So if i use the driver Marvell driver 1.2.0.1006 WHQL (Xp/Vista/7) the TRIM works for my SSD on the Marvell port?

But after reading what everyone has said you all say that i will get better read in real life performance if i switch my drive on to the SATA2 intel port instead, is this right. I mainly use my computer for playing games and using programs like Photoshop CS3 and so on.

Also if you all agree with this, should i install and use the IRST?

 

[Dave76]

The Marvell 9128 DOES support TRIM, just not for a RAID array. That's true for the Intel controllers too. In a RAID array, you have to rely on the drives' self-cleaning properties. Some SSDs do, some don't. I know Crucial drives do. I'm not sure I would trust third-party software to perform the cleanup on arrays at this point either. SSDs are still "new" and If the software and hardware giants haven't fixed the issue of TRIM on RAID arrays, I sure wouldn't trust some free download to do it.

If you're going to Google facts, make sure they apply to the discussion.

Did you even look at the links?

These links apply to this discussion.

The info I found, previously and yesterday, say the same thing.
Marvell controller 9128 doesn't pass trim.

Marvell controller 9182 does pass the trim command, as discussed on many sites.

If you have a link or proof that Marvell 9128 does, then post it, many people would be interested.

I have the Marvell 9128 controller and would like to have the information

 

[Hopalong X]

Retraction.

It would appear after reading SSD forums the Marvell controller does not support TRIM or is at best unknown if it works.

My reading was of Ezine reviews of mother boards with Marvell controllers. Some had stated as of early 2010 the new drivers for Marvell supported TRIM.
Evidently they could enable TRIM in Windows thus thinking it was working.
Since then the SSD forums have found the same. You can now enable TRIM on the Marvell controller but there is no way to know if it is actually working.

Evidence of slowing of SSD's Read/Write speeds by many users would indicate TRIM is not working on Marvell controllers.

Sorry Huge Raven, Dave76, Carwiz and Essenbe.
I regret my error.

Huge Raven using the Intel controller will be slower but does allow TRIM so may be the best way to use your SSD at this time.
I bow to the consensus of others.

Humbly.
Mike

Previous posts deleted.

 

[essenbe]

I do not have that controller. But, on the Crucial forums this topic came up and was discussed. According to them, the Marvell controller has never been proven to pass trim, however they say that if the SSD is hooked up to the Marvell controller and the MSAHCI driver is used, it will pass trim. Just passing along what I have read.

 

[HugeRaven]

Retraction.

It would appear after reading SSD forums the Marvell controller does not support TRIM or is at best unknown if it works.

My reading was of Ezine reviews of mother boards with Marvell controllers. Some had stated as of early 2010 the new drivers for Marvell supported TRIM.
Evidently they could enable TRIM in Windows thus thinking it was working.
Since then the SSD forums have found the same. You can now enable TRIM on the Marvell controller but there is no way to know if it is actually working.

Evidence of slowing of SSD's Read/Write speeds by many users would indicate TRIM is not working on Marvell controllers.

Sorry Huge Raven, Dave76, Carwiz and Essenbe.
I regret my error.

Huge Raven using the Intel controller will be slower but does allow TRIM so may be the best way to use your SSD at this time.
I bow to the consensus of others.

Humbly.
Mike

Previous posts deleted.

It´s no problem "Hopalong X", we are all human and can make misstakes. So if i have ENABLED TRIM but are experiencing sometimes slower speeds, then its not working at all and i can disable it, or should i leave it alone? My SSD drive supports TRIM acording to Crystal Disk Mark Info.
Can i only change the cable to the INTEL SATA2 port on my mobo to get TRIM to work and thus get better 4kb and 8kb speeds and faster windows speeds

 

[Hopalong X]

Essenbe

That may solve the issue for HugeRaven and give him TRIM on the SATA6Gbs Marvell.

Delete the Marvell driver reboot and let Windows install the MSHACI?

I'm not sure what he would need to do.

Mike

 

[essenbe]

Mike, as I recall, the screenshot he showed showed the msahci controller which is microsoft's default controller. As I understand it, the msahci controller will pass trim to the ssd even on a Marvell port. The problem with the trim command is that it just shows that the OS is passing the trim command. What can't be assessed is whether the controller passes that command to the SSD. Supposedly the Marvell controller won't but the msahci will. At least, that is my understanding.

 

[HugeRaven]

That may solve the issue for HugeRaven.

Delete the Marvell reboot and let Windows install the MSHACI?

I'm not sure what he would need to do.

Mike

Wouldnt i have to do this:

1 - Unistall the Marvell driver
2 - Shut down the computer
3 - Change from Marvell Sata3 to Iintel Sata2 port
4 - Restart computer
5 - Let Windows install MSAHCI

or should i just:

1 - Unistall the Marvell driver
2 - Shut down the computer
3 - Restart computer
4 - Let Windows install whatever driver it needs

What is best?

My picture showed the speed with the Marvell driver 1.2.0.1006 WHQL (Xp/Vista/7)

 

[HugeRaven]

Mike, as I recall, the screenshot he showed showed the msahci controller which is microsoft's default controller. As I understand it, the msahci controller will pass trim to the ssd even on a Marvell port. The problem with the trim command is that it just shows that the OS is passing the trim command. What can't be assessed is whether the controller passes that command to the SSD. Supposedly the Marvell controller won't but the msahci will. At least, that is my understanding.

Then you think i should try to:

1 - Unistall the Marvell driver
2 - Shut down the computer
3 - Restart computer
4 - Let Windows install whatever driver it needs

 

[Hopalong X]

Do you have AS-SSD installed?

If you do open it BUT DO NOT RUN the test.

Post a Snip. We need to see what driver is installed now. You can see it will say Marvell or MSAHCI.

I would go with Option 2 you posted above.
Get the MSAHCI driver for the Marvell. Better speed than Intel ports and you will have TRIM.

It may already be installed. AS SSD will show which driver you have.
If MSAHCI is installed you are done.
If Marvell driver shows then try your second option.

As you can see on this it shows driver as- 2.11 msahci-OK

 

[essenbe]

Mike, I had the same issue with my AMD board, It didn't have Marvell controllers but the AMD drivers didn't work too wel. So I used the msahci driver and it worked quite well.

 

[Hopalong X]

Hopefully we can get HugeRaven straight after all my mis-information.

 

[essenbe]

As best I understand it, you should be OK. You have the msahci driver, the 2.11 is the firmware on your SSD.

 

[Hopalong X]

As best I understand it, you should be OK. You have the msahci driver, the 2.11 is the firmware on your SSD.

That is not his SNIP I posted.

I wanted HugeRaven to see where the driver was listed.

 

[essenbe]

As best I understand it, you should be OK. You have the msahci driver, the 2.11 is the firmware on your SSD.

That is not his SNIP I posted.

I wanted HugeRaven to see where the driver was listed.

OK, then I made a mistake. Imagine that. It was my first mistake ever.:roflmao:

 

[HugeRaven]

As best I understand it, you should be OK. You have the msahci driver, the 2.11 is the firmware on your SSD.

That is not his SNIP I posted.

I wanted HugeRaven to see where the driver was listed.

OK, then I made a mistake. Imagine that. It was my first mistake ever.:roflmao:

My SNIP i posted earlier was with the Marvel driver 1.2.0.1006 WHQL (Xp/Vista/7). I´m not home at the moment, at work but i will start AS SSD and make a screen dump for ya all to see what is sas as i have it installed, but i´m pritty sure it´s the Marvell driver MV.... showing. Then i should go with choice 2 and uninstalling the Marvell and so on.

Then i have two dumb question for ya, am i not risking the system not starting as the SSD is the system drive if i uninstall the driver?

And the msahci driver, will it install automatically by it self?

 

[Hopalong X]

If you know the Marvell is installed then uninstall it. No Snip necessary.

If by chance the Marvell is re installed on reboot then you will need to delete the Marvell driver not uninstall.
If Marvell driver is deleted then Windows will auto install the MSAHCI since the Marvell is no longer available.

No you are not risking the system.

I'm confirming what Essenbe posted- I think!!????

 

[essenbe]

As with anything else you do, yes it is a risk, but would not hurt anything. But, I don't believe that will happen. What should happen is it will boot into wndows and you will get a pop up saying that windows is loading drivers, then ask for a re boot. reboot and you will be using the msahci drivers.

 

[essenbe]

Mike, it should be the same as changing to ahci from ide. Except the registry does not need to be changed because he is in ahci, the bios does not need to be changed because it is already correct. So, we are at the last step in the tutorial on the change. It should work right. But, should does not mean it will, as you are dealing with a computer.

EDIT: If it does not boot into windows, you are not risking damage to the system. It will hurt nothing.