Thank you. Your drivers worked for me. However, searching for a fix I read elsewhere that Marvel does not perform at the max speed allowed and that the Intel SATA 3 (6g) does, so after making sure the Marvel worked, I switched over.
Years later, and your post is still helping folks, like me!
Many thanks.
I have a pc with msi p7n sli platinum and I have installed with difficulty the iocrest 40062 to have sata 3,which as you know my card with old nvidia chipset does not have in the bios the ahci option but only ide and raid. By installing it with the sata ahci controller, it appears in the ide ata / atapi section, while with the latest Marvell driver 1.2.0.1049 it appears in storage controller detected as a usb drive. With a change in the registry, I made it recognize internal unit and no usb drive. The internal Usb ports do not work at startup nor before or after the modify, in fact it gives me the error code 10 on the Host Controller Usb OpenHCD standard with the triangle . I'm using a hub that connect a mouse and keyboard.
Is there a solution for enabling internal usb ports without having to use a Hub usb?
Last edited by schizzo123; 03 Apr 2020 at 12:14. Reason: Problem with the usb port
The latest driver I can find is marvell_mv91xx_1.2.0.1049
Marvell MV-91xx/92xx SATA 6G Controller Version 1.2.0.1049 WHQL
Is it the latest ?
Thanks
According to the file version number, it is numbered higher so naturally it should be a newer version However, as I mentioned, finding this driver isn't easy and I ran across several that, no matter the date or version number, simply wouldn't work. One always hopes that newer drive controller drivers will increase the drive speed a little. Rarely does that work. Updates to the driver usually address support for a slightly modified chip.
For example, if you look in Device Manager at the standard Microsoft-supplied "Disk drives" driver, it's from 6/21/2006. It being Jan 2021, a newer version would be expected. The reason is that the driver works just fine and no further modifications to it have been necessary. Same with the Marvell driver, in my opinion. If you have a version that actually works, I'd stick with it. As per my original post, I did indeed find a newer version and tried it but stuck with it only because it worked as well as being newer.
At that point, I had dedicated about all the work I cared to spend on that issue. I'm still using that same driver now. I still have the motherboard I mentioned in a system and it works like brand new so there's been no real need to replace it. I increased the total RAM to 16GB, and started exclusively using SSD drives (except for an external drive used for storage) in it so the speed is not an issue.
good job I needed this driver for my Asus P6X58D-E Xenon 5675 build I downloaded the file extracted to desktop, then in safe mode I un-installed all Marvell 91xx drivers and check deleted drivers, re boot in safe mode until all drivers are deleted and Marvell 91xx appears as other device in control panel, select normal startup in msconfig machine runs fine at this point but drives appear as removable under usb devices then I ran the Marvell 91xx version 1.2.0.1049
installer, re boot and speed is max 380 mbps read and 252 mbps write, trim is active and no removable devices in usb Just whish the speeds were better, any suggestions how to get the speeds faster? I'm using a 2.5 western digital 500 gb blue SSD
thanks again
@Xenon 775
In Device Manager what is the date on that driver? In my original post in 2016 (this thread) I suspected the driver was already showing serious signs of being abandoned.
Regarding your SSD speeds, after years of experience with them, I can tell you that you pretty well "get what you get". 99% of manufacturers will refuse to replace the drive if the only issue is its speed. They want either a bad S.M.A.R.T. result or a diagnostic app of their own to show it has actual bad electronics.
For example, take this email I got back from TeamGroup support regarding a 2 month old NVMe SSD drive that had dropped from 1,800 MB/s (Sequential read) to 300 MB/s (yes, that's no typo):
(Their bottom line being that I had done an apparently foolish thing, namely installed it in a computer and put data on it. Not only that, once it had some data, I put even more data on it. The drive should be tested for speed freshly formatted (empty), they say. I don't use drives empty so I really could not care less what its "empty" speed is. A billion GB/s does me no good if it has to stay empty to do that)
Dear Customer,
Thank you for contacting TeamGroup customer service center.
Normally, the test of the SSD performance is must be conducted when the SSD is completely empty to ensure that the test is accurate.
When the computer is overloading or there are too much data saved in the SSD, the computer may take more time to process multiple tasks and data transfer. This will shortly affect the speed of SSD.
On the other hand, if the SSD is on background running (i.e Garbage collection, wear leveling, Read retry..ect.) during the test ,it will also shortly affect the speed of SSD.
So it’s normal to become slower.
According to the picture which you provided, the first time has used 23% of the capacity, the second time has used 37% of the capacity.
The speed of the SSD will be reduced due to the reduction of the remaining capacity.
That may seem an outrageous insult by TeamGroup to one's intelligence but I've gotten very similar "information" from Samsung, Western Digital, etc.
Recently purchased a Vantec UGT-ST644R 4 Channel 6 Port RAID PCIe Controller Card which uses the Marvel 92xx Chipset. The driver on the Vantec website was (1.2.0.1041) but yielded the issue of SSD's appearing as HDD's in Windows 10 Defrag And Optimize Drives. I am currently using the SSD's in a Non-RAID configuration - i.e. no creation of containers in the Marvell BIOS.
Scouring the Interweebs revealed numerous posts indicating that it's best to avoid installing the drivers and staying with the Microsoft "Standard SATA ACHI Controller". That said, I did compare the driver packages and here are the notable differences below.
1.2.0.1039
- mv91cons.inf: entry for "Marvell Unify Configuration" (Device Manager > Other Devices > Marvell Controller)
- mv91cons.inf: service set to start at boot
1.2.0.1041
- mv91cons.inf: entry for "Marvell Unify Configuration" missing
- mv91cons.inf: service set to start on demand
- mv91cons.sys: updated
- mvs91xx.sys: updated
1.2.0.1047
- mv91cons.inf: entry for "Marvell Unify Configuration" missing
- mv91cons.inf: service set to start on demand
- mvs91xx.inf: added hardware removal policy
- mvs91xx.inf: added interrupt management
- mvs91xx.sys: updated
1.2.0.1049
- mv91cons.inf: entry for "Marvell Unify Configuration" missing
- mv91cons.inf: service set to start on demand
- mvs91xx.inf: added hardware removal policy
- mvs91xx.inf: added interrupt management
- mvs91xx.sys: updated
Note that I had to cleanup the folder structure on some of the packages so that I could use the DRVSETUP.EXE tool to properly inject the INF and driver files. The structure should be:
Code:.\1.2.0.#### drvSetup.EXE \storport \amd64 \i386 mvs91xx txtsetup.oem
I did reach out to Vantec Technical support regarding the issue where installing the Marvell 92xx SATA 6G Controller driver identifies my SSD's as HDD's in Windows 10; the response.
Based on the results on my findings, it appears that one has two options:Windows interrogate the drive when it is connected, it will check the drive to determine if the drive is an HDD or SSD. One of the issues is the drive is hiding behind the RAID controller and during the checking, it is not able to determine if the drive is SSD and list it as HDD.
Whereas in AHCI mode, it can directly check the drive and determine the drive is an SSD.
The minute the RAID drivers are used, the drive is behind the RAID controller even when it is in individual mode. Whereas without any RAID drivers loaded the OS can see thru the drive in AHCI mode.
OPTION 1: RAID (Configure Container)
Install the Marvel 9xxx SATA 6G Controller drivers and configure the Marvell Controller BIOS accordingly - i.e. Virtual Container, RAID0/1/etc.
The controller provides the management of the SSD (TRIM, etc.) on-board and presents Windows with a Virtual Disk container ... at least, that's what I'm understanding from the response above.
OPTION 2: AHCI (Non-RAID)
Use the Microsoft supplied Standard SATA AHCI Controller driver and avoid installing (or uninstall) the Marvel 9xxx SATA 6G Controller.
In a Non-RAID configuration, this allows Windows to properly determine that the drives on the controller are SSD's and manage the disks as expected (TRIM) in Defragment And Optimize Drives.
The last challenge to overcome however, is ensuring that the internal SSD's (or HDD's) do not appear in the Safely Eject Hardware list - aka the icon that appears in the Windows System Tray area of the Taskbar when you connect an external device (ex: Removable USB Drive).
This can be accomplished by using Device Manager > Disk Drives > [SSD/HDD] > Properties: General to gather the BUS Number of each internal drive and adding the BUS values to the STORAHCI in the registry. The example below creates the TreatAsInternalPort value and adds BUS0 and BUS2 - i.e. my two SSD drives which are on Port 3 and Port 4 of the UGT-ST644R controller. Port 1/2 on the UGT-ST644R are shared (internal or eSATA) so not a good choice for my internal SSD's in case I should ever have a need for eSATA. This means that connecting a device on those ports internally would cause them to appear as removable in Safely Eject Hardware ... unless, of course, I add their respective BUS# to the list.
Code:reg.exe add "HKLM\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device" /f /v TreatAsInternalPort /t REG_MULTI_SZ /d "0\02" ** You can create the value manually via Registry Editor, ensure that you press enter after each BUS# in the REG_MULTI_SZ string
As per the example below, I also added the following non-destructive registry entry which effectively renames the entry in the Device Manager > IDE ATA/ATAPI Controllers from: Standard SATA AHCI Controller to: Marvell 92xx SATA 6G AHCI Controller. Yep ... that's the kinda "hairpin" I am.
Code:reg.exe add "HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1B4B&DEV_9230&SUBSYS_92301B4B&REV_11\4&198977b4&0&0018" /f /v FriendlyName /t REG_SZ /d "Marvell 92xx SATA 6G AHCI Controller" ** You can create the value manually via Registry Editor
A final note; it may be necessary to remove the Device Manager > Disk Drive ghosted (or live) entries in order for Windows to properly "re-detect" devices - do not select the "Delete Drivers From The System" checkbox when doing so. The checkbox should only be chosen when rolling back a device driver or to perform a clean driver re-installation. Restarting the system or performing a Scan For Hardware Changes will typically re-install any missing plug-and-play entries.
Lastly, some links that are useful to have on hand ...
Device Manager does not display devices that are not connected
Internal SATA Drives show up as removeable media
How to See if Disk Type is SSD or HDD in Windows 10
How to Get Windows Experience Index (WEI) Score in Windows 10
How to Enable or Disable TRIM Support for Solid State Drives (SSD) in Windows 10
Last edited by gagneh; 01 Mar 2021 at 22:08. Reason: Cleanup for clarity & consistency
Quote
