@wasisdn

Hello, have tested down to the version 13 * but still equal, so update the 1402 by proving them versions remaining but not works continues slow the bios

I leave you a video

https://1drv.ms/v/s!AhpvVJ-HuDrigaJvk7i1Rv5y-5hoLg

version 1304-org and 1402-org are factory bios from Asus without any modifications.
Did you try to disconect all SATA and USB devices and try again? looks like there is a problem with recognizing some of the disc maybe on Sata or USB port..

the clean boot diskless or any attached USB even restart the bios and still the same

I have a pci-e marvell 9170 card and the bios has issuies and crashes the computer when booting from an ssd.
would I be able to flash the card like onboard chipsets?
I can find very little info.

Hi,

i am using a mod bios with the rom 1.0.025 for the 9182 marvel controller at my Gigabyte X58a OC (Phoenix Bios) and i wanted to replace it with the special 034 version provided in the modules section.

some time digging around with the marvel flash tool, bootloader and stuff i find that the marvel bios is giving me the 91A2 id for the controller.

Due to the rom size file within the modded bios that is 131kb and a hex look inside i get courious about the all in one package for the 91A2 provided here and recommended UEFI only and added it with cbrom155.

What should i say? It works fine with my legacy BIOS. Am i killing my Controller right now or am i fine?

Hello,
I have a marvell 9230 discrete card (no name, the manufacturer may be "syba").
I have two issues that maybe some experts may help here:

1°) While Marvell indicate here: http://www.marvell.com/storage/system-so...llers/hyperduo/ that by using 2 SSd and 2 HDD on boards based 9230 you can combine hyperduo and raid, I have not been able to do it: there is not such an option by selecting 4 drives and it is not possible to do it in two steps (ie creating 2 hyperduo then trying to build a raid0 with them) because a virtual drive cannot be made using other virtual drive.
I believe, it needs a bios witch have some feature activated.

2°) I have a quite new motherboard, using a recent uefi revision, that haven't an option to activate cards' boot roms, meaning pushing ctrl+m on boot is useless for me: in cannot enter in my 9230 bios setup unless... I make a clear cmos!!
but there is some uefi roms or drivers for 88SE9230, can I use them and how to make the setup card accessible on boot?

I use the latest drivers and bios/firmware on station-drivers.com: http://www.station-drivers.com/index.php...c=select&id=215

BIOS Version 1.0.0.1024
Firmware Version 2.3.0.1070
Boot Loader Version 2.1.0.1008
Driver Version 1.2.0.1049
Chip Revision ID A1
Vendor ID 1B4B
Sub Vendor ID 1B4B
Device ID 9230
Sub Device ID 9230
Port Count 4
Max PCIe Speed 5Gb/s
Current PCIe Speed 5Gb/s
Max PCIe Link 2X
Current PCIe Link 2X
Supported RAID Modes RAID0, RAID1, RAID10, HyperDuo (Capacity), HyperDuo (Safe)
Supported Stripe Size 32K 64K
Maximum PD per Adapter 7
Supported VD Cache None
Maximum VD per Adapter 4
Maximum PD per VD 4
Maximum Port Multiplier 1

I wound up in the same boat as a lot of other folks for a while after I incorrectly flashed my 9215 without backing up the original first. In my case, I was very lucky in that I had a different part that also used the same chipset.
The part I screwed up on is a Linkreal LRST8615-4IT with a Marvell 88se9215 chipset on board. This is a mini pcie card that has a SAS connector on it.

After a week and a half of scouring the internet for a solution, I discovered that the pcie card that this part was replacing in my build had the exact same Marvell chipset on it. This is the Syba SI-PEX40064.
So I pulled out my chip programmer (a cheap Genius G540), and tried to read the bios chip on the Syba. No joy; it wasn't able to pull anything from the chip. So then I took my solder to it and removed it from the card.

Attached is the image I read off that chip. I was able to flash this on my LRST8615-4IT and was able to get the thing to at least show disks once the OS was loaded. I don't need boot support, so it is fine for me.
Of note in the image is that there is very little data in it. Only the top few lines have anything, and they appear to be the bootloader code.

So for anyone else out there who accidentally flashed their 9215's incorrectly, this file may be a fix for you. Just rename the .txt to .bin

Hi Fernando

i know this might not be the correct section to ask for some help, but hopefully you can.

Background to what i have
1. Qnap TS-EC1279U-RP
2. Backplane with 5x 88SE9125 Controllers
3. Connected with what i think is a single PCIE
4. The firmware/rom is not included in the Motherboard Bios, so seperate flash as far as im aware.
5. i was stupid and did not do a backup of the controllers before i flashed them...

Now the problem
All was working fine, it is my unraid machine
I was on the task to try get IMMOU working on the machine, and there was an issue with IMMOU and the Marvell chipset in unraid.
So i basically flashed the 9125s with what i thought would be a fix ( i didnt do enough reading before hand )

Since then, i have been scouring the forums trying to find a image to use that will work with my 9125 controllers.

Now from what i can tell, the good news is the controller is still picked up by mvf_mag
And is picked up in windows/linux.
But no matter what combination i use, i cannot get the backplane to work with any drives plugged in.

I have tried myself to modify dev ids on the rom, and autoloader, but i literally cannot find any image files created for a 9125 marvell controller.

So basically, am i out of luck, unless someone else has a backup image from a 9125 controller?

@Fernando

Thanks, i will grab the image and details tomorrow so hopefully someone smart can help me out.

I haven't seen these posted anywhere so I'll post them here. These are off a dump I took from a 9120 card I recently purchased.

All I have is Autoload and BIOS. This is a very simple card.

Extracted with Lordkag's script.

[[File:BIOS 9120 1.1.0.1002.bin.zip]]
[[File:Autoload 9120-9120 0.0.3.2050.bin.zip]]
[[File:25L4006E.zip]]

Resurrecting an old discussion in this topic for a bit to share my expereince with the Marvell 9128 on my Gigabyte GA-X58A-UD5 rev.1 motherboard. Maybe it will help others who plan to mod motherboards from this series. The information in this topic was invaluable for me so thank you all who tested before me!

This motherboard uses a 512Kb chip to store the Marvell firmware, loader, ROM etc. independent of the BIOS as lordkag explored back in 2014 with the UD3R version of the board.

The latest BIOS for this motherboard contains 2 files seemingly related to this controller:
- GRAID.BIN - 25Kb - this **LOOKS LIKE** a Marvell ROM as the beginning is very similar to other Marvell ROMs, verison number is 1.0.0.1003.
- M9123FW.BIN - 512Kb - this contains the autoload, firmware, hw_config etc. and another Marvell ROM, this time version number 1.0.0.1029. This is a straight dump of the contents of the 512Kb chip that you can update with the Marvell Firmware update tools and images.

In the BIOS you can set the SATA3 controller firmware mode to FORCE or ONCHIP. When you set it to FORCE, during boot the contents of the M9123FW.BIN in the BIOS gets written to the 512Kb chip byte-for-byte.

If you look at earlier versions of the BIOS you can notice that when the Gigabyte BIOS release notes mention "Improved SATA3 RAID performance" the GRAID.BIN is still 1.0.0.1003 but the ROM version in the M9123FW.BIN is higher.

So why would Gigabyte update the Marvell ROM in their BIOS only in the firmware dump and why leave GRAID.BIN alone? Another observation is that the Marvell ROM prompt does not show up during boot at all, there is no option to press Ctrl+M anywhere during the boot process.

So here is what I think:

1. Gigabyte wanted to provide easy Marvell FW updates to their customers without DOS booting Marvell firmware utilities, but they couldn't include the whole Marvell toolset in the BIOS. So instead they came up with this: they update a motherboard with the Marvell tools, DUMP the contents of the chip, and include that in the BIOS with a simple program that copies byte for byte the 512Kb image to the chip.
Then they give the user the option in the BIOS to FORCE update the chip contents.

2. The original Marvell ROM slowed down the boot process, expecially with an Intel RAID ROM and a JMicron RAID ROM also on the system, so they moved the Marvell RAID configuration into the BIOS. This is where GRAID.BIN comes in. If you change/replace GRAID.BIN in the BIOS with a proper Marvell ROM, you can't enter the Marvell RAID configuration from the BIOS anymore. The firmware and everything works, but you can't configure RAID from the BIOS. Nothing happens when you select that option.

If you leave GRAID.BIN alone and only update the firmware etc. on the 512Kb chip, the RAID configuration from the BIOS works.

I believe Gigabyte created a hacked dummy Marvell ROM that enabled the user to hop into the Marvell RAID configuration from the BIOS without going through the boot process and pressing Ctrl+M. The actual Marvell RAID ROM that is used is always on the 512Kb chip. You can get to the Marvell RAID configuration menu from the BIOS and it will say the ROM version that is on the 512Kb chip. This mysterious 1.0.0.1003 version ROM is not actually used by the 9128 controller.

So this means you can provide the entire Marvell firmware update straight in the BIOS for these boards, you just have to recreate M9123FW.BIN. And this is what I did.

I took the latest parts available in this topic, flashed the Marvell firmware image on my computer, dumped the 512Kb chip contents, examined it and recreated it from the parts available with the right offsets, padding etc. in a hex editor (I did this to make sure no errors slip in during the dump. The dump tool inserted some weird characters sometimes into the FF padding parts.) I then tested the franken-spliced image, compared it to the dump until it was identical.

Here is a link for the M9123FW.BIN with the following parts:
- Autoload 2.0.0.061D
- ROM with deviceID 9123 v1.0.0.1038
- Firmware v2.3.0.1007

The parts were taken from the attached image in this post. The final firmware would be what lordkag describes here as Test3 with the newest available parts.

I tested this on my GA-X58A-UD5 rev.1 and the Marvell controller works, the versions are correct in the RAID BIOS and in the OS, the FORCE update function works without problems and the RAID configuration is available from the BIOS.

This is a dump for a four port Marvell 9215 controller. The model of the card is PCE4SAT-M02

1. Autoload.bin  was extracted. Offset = 0x00    and Size = 0x58
2. HW_Config.txt was extracted. Offset = 0x1000  and Size = 0x5C
3. Desc.txt      was extracted. Offset = 0x2000  and Size = 0x77
4. No SPIList.bin is found! Nothing to extract.
5. No Loader is found! Nothing to extract.
6. Bios.bin      was extracted. Offset = 0x10000 and Size = 0x7C00
X. No Firmware is found! Nothing to extract.
7. No Program0 is found! Nothing to extract.
8. No Program1 is found! Nothing to extract.
9. No BIOS_UI is found! Nothing to extract.
10. No DSRAM_DATA is found! Nothing to extract.
11. No END_info is found! Nothing to extract.
 
 

Autoload   92xx 2.0.0.2005_RevA1.bin
BIOS       9215 1.0.0.1028.bin
 
 

[[File:9215 dump.zip]]

The firmware above is;

Zitat

---

PACKAGE VERSION[0xFFFFFFFF]: 2.3.0.1067
AUTOLOAD VERSION[0x00000000]: 200020
BIOS VERSION[0x00020000]: 1.0.0.1028

---

Although it does not seem to be complete.

Zitat von chinobino im Beitrag #209

---

The firmware above is;

Zitat

---

PACKAGE VERSION[0xFFFFFFFF]: 2.3.0.1067
AUTOLOAD VERSION[0x00000000]: 200020
BIOS VERSION[0x00020000]: 1.0.0.1028

---

Although it does not seem to be complete.

---

I don't know what to say... This is a straight dump off the SPI chip... The chip has no RAID functionality, so perhaps this is sufficient for such a card. Either way, the card's intended purpose was for optical drive testing with Marvell, so I'll see how that goes.