@ yamazakirobert:
Welcome at Win-RAID Forum!
That was not a good idea, because the latest v13 and v14 series Intel RAID ROM modules do not fully support old Intel chipsets. For details please look into the start post of >this< thread.
The boot time is much less important than the system’s stability and performance.
Regards
Dieter (alias Fernando)
There are no Marvell components in the file W555_A58, the last BIOS from EVGA. The only way you can access them is through Marvell flasher, by saving the content of the chip, check what version you have, update to latest. It might also help to update the JMicron modules, then disable everything you don’t use, like PXE Boot, maybe JMicron controller. Also move the Intel RAID controller related items higher in the boot devices list.
Hi,
I’ve a question, please.
I was looking at the “b) Marvell 91xx (SATA3) AHCI/RAID ROM modules” because i want to upgrade the Magni firmware with MARVELL FLASH TOOL of my Marvell SATA 6G controller, sooner or later (PCI\VEN_1B4B&DEV_9120&REV_12):
to
BIOS Version :1.0.0.1038
Firmware Version: 2.3.0.1007 (hope is the right firmware, i attached it)*
or to
marvell_88se91xx_firmware_2.2.0.1125b (which listed here)
While i was checking what is listed, one thing is that UBU v1.33 tells me that Marvel ORom module 9120 is v10.0.1038 which is OK, but the module for 9172 shows v10.0.0034 and i cannot find here this 9172 module. You’re listing only the v10.0.0032 ?
The module AHCI/RAID ROM v10.0.0034 is listed for Marvell 9192 & 91a2 here…Is there a mistake ?
[[File:UBUv1.33 [Sept-02-2015].PNG|none|auto]]
Thanks for your respond.
Thanks for the info. Meanwhile the related Marvell AHCI ROM modules, which I am offering within the start post, have been updated to v10.0.0034.
I’m glad i haven’t succeed to upgrade my Marvel sata controller lately…
Seems v1.0.0.1038 is for 9128 only, and v2.2.0.1125b (9123B.bin) just brick the 9120 controller!
Version 1.0.0.1033 Supported VENDOR_ID = 1B4B DEVICE_ID_LIST = 9023,90A3,9110,9190,9111,9191,9120,91A0,9122,91A2,9123,91A3,9125,91A5,9128,91A8,9130,91B0, but i cannot this firmware anywhere.
While i was trying the v2.2.0.1125b, the DoS command gave me strange result. Either disabling in Bios the Marvel Controller or Let it enable wouldn’t launch the command ‘go’.
Marvell 91xx AHCI/RAID Option ROM modules and Marvell 91xx AHCI/RAID Firmware are different things!
Sorry i misspoke,
it’s a package firmware v1.0.0.1038 include: BIOS Version :1.0.0.1038 & Firmware Version: 2.3.0.1007.
I’m looking for the latest package firmware v1.0.0.1033 (if it does existing). I understand it is made of 3 differents modules for marvel controllers.
By the way i can’t read when booting with ‘ctrl+M’ ,my Marvel bios & firmware versions displayed on screen because it does boot too fast!
There are some Marvell 91xx combo modules, which contain the Bootloader, the OROM and the Firmware, but I only can offer the v1.0.0.1033 Option ROM module for DEV_9120, DEV_9123, DEV_9128 and DEV_91a3 (uncompressed size: 28 KB).
For which DeviceID do you want the Marvell 91xx ROM module?
@Fernando ,
I have a Marvell 91xx SATA 6G Controller : PCI\VEN_1B4B&DEV_9120&SUBSYS_83BA1043&REV_12 (PCI\VEN_1B4B&DEV_9120&REV_12)
I have updated with UBU to:
OROM MARVELL 88SE9120: v1.0.0.1038
OROM MARVELL 88SE9172: v1.0.0.0034
EFI Marvell SATA AHCI: v1.1.0.1015.
So this looks OK to me, thought v1.0.0.1033 was a complete package including a firmware somehow inside.
I am still using the Marvell driver Pilot version: 1.2.0.1038 dated from June 21st, 2013.
It is very optional to update for a newer firmware but i would like to. My controller works fine actually.
What I’m learned from loardkag
Firmware Module v2.3.0.1007 works together with O-Rom Module v1.0.0.1038 and Bootloader v1010002b_v5 on MV91xx_DEV_9120 / DEV_9123 / DEV_9128 (extract by loardkag from same Marvell upgrade package)
Firmware Module v2.2.0.1125b works together with O-rom Module v1.0.0.1033 and Bootloader v1010002b_v4 on MV91xx_DEV_9120 / DEV_9123 / DEV_9128
O-Rom Module v1.0.0.1034 is only for DEV_9172, DEV_917a, DEV_9182 and DEV_918a
Can one confirm, please?
I’m unsure of the Bootloader v1010002b_v5 in the Marvell_MV-91xx_SATA_6G_Controller_Firmware_v1.0.0.1038.zip attached above.
I can see inside the GO.BAT the 9120 ID
@N6O7
Fernando is right, Firmware has nothing to do with "AHCI & RAID ROM Modules", I hope he will move this discussion elsewhere. There are already two threads on Marvell Firmware. This is the content of those two firmwares you mentioned:
As you can see, neither is good for you, due to different Autoload and BIOS/ROM. Those Firmwares are designed for 9128 controller, but can work for others IDs with the right components. To expand the previous statement, the first firmware works only for onboard 9128 controllers, the second works for both onboard and external 9128 controllers - the Autoload is the component that makes the difference. For supporting other IDs, you have to have a matching Autoload and a matching BIOS/ROM. There is even one more thing that adds confusion, RAID controllers like 9128 default to using 9123 ID, because they will be booted in AHCI mode at some point, thus it needs to support it. They will switch to 9128 ID only when changed to RAID mode, they will also switch to 91A3 when changed to IDE mode. For your issue, I will suggest to backup current firmware and post the dump on one of those Marvell Firmware threads. I will then see what Autoload and ROM you need.
@lordkag ,
Thank you for your input and clear respond. That’s what i thought both are not compatible as i suspected in my post 800.
I will stop asking in this AHCI & RAID Rom Modules thread and move it to Marvell thread and re-ask when having the dump. Thanks again.
@ Gaudi, @ N607, @ lordkag, @ wasisdn, @ iRX:
To make it easier for the users with a Marvell 91xx SATA3 Controller to find compact informations about where to find and how to update the related BIOS modules, I have merged the related posts into this thread and customized the thread title.
I hope, that this is ok for you.
Regards
Dieter
EDIT: At least I have "stickied" this thread.
Thank you for having moving this thread out as “discussion”.
While i was digging i found the tools left by hanson (Marvel Flash.zip) on post 113: Problems Updating firmware of Marvell 9120 Sata controller (8)
And the one (U3S6R1_Marvell-9120_2.3.0.1007.rar) posted from lordkag on post 203: Problems Updating firmware of Marvell 9120 Sata controller (14)
The go -r command returned “Adapter not found!” or “No supported flash found!” and enabling adapter or disabling adapter…has no effect.
I have also tried to swap the mvf_mag.exe (modded for cFeon EN25F40 chip) by hanson one in bin folder:
lordkag package:
Image = 1.0.0.1813
BIOS = 1.0.0.1038 (ID 9120)
Autoload = 3.0.1.0106 (ID 9120)
Firmware = 2.3.0.1007 (20-09-2012 11:02:34)
mvf_mag = 1.0.0.2461
tried both, hanson and lordkag + swapped “mvf_mag.exe” one.
I can’t create the dump file IMAG_RB.BIN. for Marvell 91xx SATA 6G Controller : PCI\VEN_1B4B&DEV_9120&SUBSYS_83BA1043&REV_12 (PCI\VEN_1B4B&DEV_9120&REV_12).
I will start with a small correction. There is no Hanson and lordkag package, it is the same package, which was posted by me earlier in this thread and reposted by Hanson due to requests. The same thing goes for the flasher, it was modded by me to support his chip and is the same in all packages you linked. Hanson and Gaudi were generous and brave enough to provide the hardware for all my tests, that is why I consider their work equally important and I have linked to their post when it came to download a package. The post 203 should be the package to use as of now, but only for the mentioned cards. For 9128 controllers there is the package Gaudi posted and also the one from Station-Drivers (same firmware). There isn’t a definitive package that will work for all controllers, due to numerous and sensitive components. Users should first read, then provide the needed info (controller, ID, chip ID, mainboard/external, dump, is the original firmware untouched etc.), if they want some help.
For your issue, it appears the chip is not in the list of supported IDs. The packages you tried have the same modded flasher, where I have changed 2 original IDs to support Hanson’s chip. You should try to dump with the original package from Station-Drivers (DON’T FLASH!). If you get the same error, you need to inspect your board, locate Marvell controller, check the chips near it. It should be a 512KB or 4Mbit one.
Well, looks i will have to check my board to locate the Marvell controller and the chip near it.
So far that I have tried:
-The station-Driver package, (v1.0.0.2439)
-The package here at OneDrive link, (v1.0.0.2439)
-The hanson Marvell Flash.zip (post 113) (v1.0.0.2461)
-Yours (post 203)…(v1.0.0.2461)
All of those returned the same. No Adapter or No supported flash…i do not have a programmer, though!
I’ll see that soon and attach the picture.
Thanks again for your time.
EDIT:
I’m in trouble! Looks there no Marvell related chip around the SATA 6G port.
I have another High Resolution picture of the board and the one attached is from Sept 2012, but mine above is a June 2013 Revised.
I was referring to controller, like this one. If it is not in big picture -> top left corner, then it could be under the the little blue shield. Try to install latest Marvell MSU and print the values, also check with its CLI utilities, like nv_cli.exe for dumping the firmware.
Edit: none of the chips you posted are good. The first one is from the mainboard, the second one is too small (64KB = 512Kbit), the third is TPU - TurboV Processing Unit.
This is what i have with latest MSU:
I don’t have an argument when typing the command with MarvellCLI…Is the argument my motherboard Bios?
Is it something like that??:
flash -aid 0 -r
flash -aid adapter 0 -r
Edit II: Sept 15, 2015 16h37 PM
OK…It tooks me a while to unmount my machine, but worth it and a good cleaning session that came with!! 
I have the Marvell Chip picture from my motherboard now. I have external eSATA 6G (red) & Internal SATA 6G (Blue) driven by the Marvell Sata controller on this motherboard.
I hope you have used MSU 4.1.0.2027 or newer, if available. The fact that MSU shows nothing related to firmware, could mean that either there is no firmware (unlikely, I have seen boards with 9120 that pack the Firmware components into mainboard BIOS), or that the chip is unknown to MSU as well. There is also a suspicious 8 pins empty spot next to the controller. For the commands of Marvell CLI you will have to research on your own, I know they are there, for I have seen them. Just check with nc_cli or whatever Marvell CLI you can find.
Perhaps I haven’t detailed my request. You need to locate the Marvell controller (you did), then check the chips around it. It should be a chip with 8 pins and some writings on it. Checking those two in the picture, neither is Marvell related, different purpose. You have removed some of the old pictures, but there are three candidates in the large screenshot. The big and detachable one is from mainboard, one was already ruled out - but can’t remember which one. The chip is most likely like the two small ones, a DIP8 SOIC8. If you want to speed things up, you should note their serial, as I’m having trouble in reading the chip sometimes. Even better, you can search the serial yourself, you should find a datasheet in first results and check the size to be 512KB or 4Mbit.